On Sun, Apr 20, 2008 at 10:11:29PM -0500, Mike Christie wrote:
> Hey Erez and Or and list,
> 
> I do not remember which one of you requested it, but I added code to 
> support multiple initiator names. You can create multiple sessions from 
> the same host to the same target portal. It is in the head of the 
> open-iscsi git tree. This could be used for your virtualization stuff.
> 
> Pasi, you could create multiple ifaces with different initiatornames, 
> but the problem is that some targets like I think Equalogic take that 
> into account when load balancing. So Pasi, I am working on extending 
> this to what we discussed before where we use the one initiator name and 
> just change the isid. It should be done soon. I goofed up on some string 
> handling stuff though so I have to redo it this weekend.
> 

Hi!

Nice! Just let me know when you get the isid stuff done so I can then test
it.. 

Thanks!

-- Pasi

> To make it work you need the kernel modules and tools from 
> open-iscsi.git (I have patches to make it work for the linux-2.6-iscsi 
> git tree too, but have not uploaded them and ported them yet).
> 
> This works exactly like the iscsi_tcp iface binding, but you do not need 
> to pass in a hardware/netdev value for binding (we bind by initiator name).
> 
> 1. create shell iface
> iscsiadm -m iface -I $some_name_like_my_iname0 -o new
> 2. set binding
> iscsiadm -m iface -I $some_name_like_my_iname0 -o update -n 
> iface.initiatorname -v iqn.2005-09.com.test
> 3. The default is to use iscsi tcp, so if you want to do iser (you will 
> need the linux-2.6-iscsi git tree stuff, because it requires a new sysfs 
> attr, so you can only do iscsi_tcp with the open-iscsi.git stuff):
> 
> iscsiadm -m iface -I $some_name_like_my_iname0 -o update -n 
> iface.transport_name -v iser
> 
> 4. Then discover storage and bind
> iscsiadm -m discovery -t st -p ip -I $some_name_like_my_iname0
> 
> or bind to existing portals
> 
> iscsiadm -m node -T target -p ip -I $some_name_like_my_iname0 -o new
> 
> (if you look in the README you can see other binding options).
> 
> 5. Go back to step 1 to create more ifaces with different initiator names.
> 
> 6 login.
> 
> login to specific port through specific iface that was bound above:
> iscsiadm -m node -T target -p ip -I $some_name_like_my_iname0 -l
> login to all portals that are bound to iface
> iscsiadm -m node -I $some_name_like_my_iname0 -l
> 
> There are other combos see the iface binding stuff in the README. It is 
> the same for this.
> 
> 
> 
> 
> I also made it easier to bind iser to the records. With the iscsi_tcp 
> iface binding you can do
> 
> iscsiadm -m discovery -t st -p ip -I iface -I iface1 -I ...
> 
> and this will bind the portal records to the interfaces passed in. If 
> none are passed in we will use the ones in /etc/iscsi/ifaces.
> 
> I extended this so iser has its own special iface like how iscsi_tcp 
> with no binding does.
> 
> If you do
> 
> iscsiadm -m discovery -t st -p ip -I iser
> 
> it will setup the discovered portals to use iser. You can then use the 
> iser iface for other commands like with normal ifaces:
> 
> example:
> iscsiadm -m node -I iser -o update/new/delete ....
> 
> execute operation on all node records that are bound to iser
> 
> iscsiadm -m node -I iser -u/l
> 
> log into or out of every portal using iser. And like above there other 
> combos that you can do like with the other iface binding.
> 
> There is a weird hicup I am still working on - not sure if it is a good 
> thing or not.
> 
> If you do
> 
> iscsiadm -m discovery -t st -p ip
> 
> then iscsiadm will bind the portals found to interfaces that have 
> modules loaded. So for example if you have only ib_iser loaded and you 
> run that command then iscsiadm will set things up so that the portals 
> found will user iser. If you have iscsi_tcp and ib_iser loaded then the 
> portals will be setup for both modules. You can override this by passing 
> in the interfaces you want to use.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to