Fwparam tool limitation (multiple session at boot time.)
The open-iscsi fwparam tool does not connect through all the initiators in the initiator structure exported by the iBFT. I ask this because though the Nic fw can connect twice to the same target using both the initiators(Dual port card) but then the OS makes only one connection with the last(I hope I got this right) initiator with the Firmware boot selected flag set. Now, I would think we should have both ports(dual port NIC) with an iqn should be able to connect to a target portal and thus have two sessions to the same target portal. Is there a specific reason for this design or it just needs some coding? -Shyam Iyer --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Fwparam tool limitation (multiple session at boot time.)
On Tue, Oct 07, 2008 at 07:48:58PM +0530, [EMAIL PROTECTED] wrote: > > The open-iscsi fwparam tool does not connect through all the initiators > in the initiator structure exported by the iBFT. > > I ask this because though the Nic fw can connect twice to the same > target using both the initiators(Dual port card) but then the OS makes > only one connection with the last(I hope I got this right) initiator > with the Firmware boot selected flag set. > > Now, I would think we should have both ports(dual port NIC) with an iqn > should be able to connect to a target portal and thus have two sessions > to the same target portal. I think you are asking two questions here: 1). Should we connect to all portals listed in the iBFT irregardless if some of the flag. 2). Should we connect to the portals on both ports. The second is much easier to answer - that depends on the iBFT structure. There is a linkage between the target portal and the NIC entry (each target portal can only specify _one_ NIC however). If that is not set, we would not connect. However if the iBFT specifies two NIC entries and four targets, where one is associated with the first NIC, while the three other are with the second NIC, we ought to: a). During bootup login to only the boot-up portal b). Later on we can connect to the other target portals. But I think we haven't even done that as the purpose of iBFT is to be the 'iSCSI _Boot_ Format Table' - so we only use it during bootup. In regards to the first 1) question the spec does not specify (this is from my memory so I might be wrong here) whether you need to log-in or not. If you are interested in doing some of this work to have it working properly contact me off-line and we can work together on improving the iscsiadm ibft sysfs handling (or rather the lack of it right now and add the correct sysfs handling) and adding this in. > > Is there a specific reason for this design or it just needs some coding? Coding. You volunteering? > > -Shyam Iyer > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Fwparam tool limitation (multiple session at boot time.)
On Mon, Oct 13, 2008 at 10:39:32AM -0400, Konrad Rzeszutek wrote: > > On Tue, Oct 07, 2008 at 07:48:58PM +0530, [EMAIL PROTECTED] wrote: > > > > The open-iscsi fwparam tool does not connect through all the initiators > > in the initiator structure exported by the iBFT. > > > > I ask this because though the Nic fw can connect twice to the same > > target using both the initiators(Dual port card) but then the OS makes > > only one connection with the last(I hope I got this right) initiator > > with the Firmware boot selected flag set. > > > > Now, I would think we should have both ports(dual port NIC) with an iqn > > should be able to connect to a target portal and thus have two sessions > > to the same target portal. > > I think you are asking two questions here: > > 1). Should we connect to all portals listed in the iBFT irregardless if some > of the flag. > > 2). Should we connect to the portals on both ports. > For example Equallogic iSCSI storage only has a single portal that you log into.. to the same portal from all ports/NICs (if using multipathing). That portal then does loadbalancing/redirection to some real interface.. -- Pasi --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Fwparam tool limitation (multiple session at boot time.)
On Mon, Oct 13, 2008 at 05:52:27PM +0300, Pasi Kärkkäinen wrote: > > On Mon, Oct 13, 2008 at 10:39:32AM -0400, Konrad Rzeszutek wrote: > > > > On Tue, Oct 07, 2008 at 07:48:58PM +0530, [EMAIL PROTECTED] wrote: > > > > > > The open-iscsi fwparam tool does not connect through all the initiators > > > in the initiator structure exported by the iBFT. > > > > > > I ask this because though the Nic fw can connect twice to the same > > > target using both the initiators(Dual port card) but then the OS makes > > > only one connection with the last(I hope I got this right) initiator > > > with the Firmware boot selected flag set. > > > > > > Now, I would think we should have both ports(dual port NIC) with an iqn > > > should be able to connect to a target portal and thus have two sessions > > > to the same target portal. > > > > I think you are asking two questions here: > > > > 1). Should we connect to all portals listed in the iBFT irregardless if some > > of the flag. > > > > 2). Should we connect to the portals on both ports. > > > > For example Equallogic iSCSI storage only has a single portal that you log > into.. to the same portal from all ports/NICs (if using multipathing). Right. During discovery we learn of that - and I believe that the code picks the target portal IP, and then does a discovery and logs on the IPs associated with the target portal. This meaning it should work fine with your setup. > > That portal then does loadbalancing/redirection to some real interface.. Are we talking about the same issue that Shyam raised? > > -- Pasi > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Fwparam tool limitation (multiple session at boot time.)
On Mon, Oct 13, 2008 at 11:04:02AM -0400, Konrad Rzeszutek wrote: > > On Mon, Oct 13, 2008 at 05:52:27PM +0300, Pasi Kärkkäinen wrote: > > > > On Mon, Oct 13, 2008 at 10:39:32AM -0400, Konrad Rzeszutek wrote: > > > > > > On Tue, Oct 07, 2008 at 07:48:58PM +0530, [EMAIL PROTECTED] wrote: > > > > > > > > The open-iscsi fwparam tool does not connect through all the initiators > > > > in the initiator structure exported by the iBFT. > > > > > > > > I ask this because though the Nic fw can connect twice to the same > > > > target using both the initiators(Dual port card) but then the OS makes > > > > only one connection with the last(I hope I got this right) initiator > > > > with the Firmware boot selected flag set. > > > > > > > > Now, I would think we should have both ports(dual port NIC) with an iqn > > > > should be able to connect to a target portal and thus have two sessions > > > > to the same target portal. > > > > > > I think you are asking two questions here: > > > > > > 1). Should we connect to all portals listed in the iBFT irregardless if > > > some > > > of the flag. > > > > > > 2). Should we connect to the portals on both ports. > > > > > > > For example Equallogic iSCSI storage only has a single portal that you log > > into.. to the same portal from all ports/NICs (if using multipathing). > > Right. During discovery we learn of that - and I believe that the code picks > the target portal > IP, and then does a discovery and logs on the IPs associated with the target > portal. > > This meaning it should work fine with your setup. > > > > > That portal then does loadbalancing/redirection to some real interface.. > > Are we talking about the same issue that Shyam raised? > Good question.. I was tired when I wrote that :) Anyway, I guess my point was that you might have the same target portal (IP) for both ports. Some storage has different target portal/IP per controller, and others do not.. -- Pasi --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Fwparam tool limitation (multiple session at boot time.)
[EMAIL PROTECTED] wrote: > The open-iscsi fwparam tool does not connect through all the initiators > in the initiator structure exported by the iBFT. > > I ask this because though the Nic fw can connect twice to the same > target using both the initiators(Dual port card) but then the OS makes > only one connection with the last(I hope I got this right) initiator > with the Firmware boot selected flag set. > > Now, I would think we should have both ports(dual port NIC) with an iqn > should be able to connect to a target portal and thus have two sessions > to the same target portal. > > Is there a specific reason for this design or it just needs some coding? > Ok I finally got around to fixing up Konrad's iscsi_sysfs ibft patch and merging it and fixing up the related code. I sort of implemented what you want now. A lot of the pieces are now done, and we just have to put the last ones together. In the git tree we now log into all the targets that are present (instead of the first one with the boot flag set), and you can bind a iface to portals found in the firmware. The missing pieces are doing the iface binding automatically: 1. If the initiator name is the same for all ports but the user wants to bind a session through the nic that the portal was set up with in the firmware, we currently do not support this with the firmware commands. This is the normal old style iface binding by hwaddress or netdev name, so we can do it. - if you have port0 with initiator-nameA and the ibft info for that port has target-portalZ, and port1 has a different initiator-nameB but its ibft info also has target-portalZ, we only log in to the target portal once right now. We probably wanted to at least log into once for each initiator-name (initiator-nameA and initiator-nameB). This is the newer initiatorname iface binding feature. I am not sure if this also means that we want to bind the session to a specific nic port. This would be iface binding with initiatornames and (hwaddress or netdev names), and we support this today too. So maybe we need one new super flag for the firmware related commands that takes in the binding preferences. iscsistart -b --create-iface-binding=INITIATORNAME | (HWADDRESS | NETDEV) iscsiadm -m discovery -t fw --create-iface-binding=INITIATORNAME | (HWADDRESS | NETDEV) -l iscsiadm -m fw -l --create-iface-binding=INITIATORNAME | (HWADDRESS | NETDEV) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Fwparam tool limitation (multiple session at boot time.)
On Wed, Nov 26, 2008 at 06:06:41AM -0600, Mike Christie wrote: > > [EMAIL PROTECTED] wrote: > > The open-iscsi fwparam tool does not connect through all the initiators > > in the initiator structure exported by the iBFT. > > > > I ask this because though the Nic fw can connect twice to the same > > target using both the initiators(Dual port card) but then the OS makes > > only one connection with the last(I hope I got this right) initiator > > with the Firmware boot selected flag set. > > > > Now, I would think we should have both ports(dual port NIC) with an iqn > > should be able to connect to a target portal and thus have two sessions > > to the same target portal. > > > > Is there a specific reason for this design or it just needs some coding? > > > > Ok I finally got around to fixing up Konrad's iscsi_sysfs ibft patch and > merging it and fixing up the related code. Thank you for doing that. By now, I think I owe you a box of your favorite beverage. Perfect timing too - X-Mas is coming around the corner :-) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: Fwparam tool limitation (multiple session at boot time.)
Mike Christie wrote: > [EMAIL PROTECTED] wrote: > > The open-iscsi fwparam tool does not connect through all the > > initiators in the initiator structure exported by the iBFT. > > > > I ask this because though the Nic fw can connect twice to the same > > target using both the initiators(Dual port card) but then the OS makes > > only one connection with the last(I hope I got this right) initiator > > with the Firmware boot selected flag set. > > > > Now, I would think we should have both ports(dual port NIC) with an > > iqn should be able to connect to a target portal and thus have two > > sessions to the same target portal. > > > > Is there a specific reason for this design or it just needs some coding? > > > Ok I finally got around to fixing up Konrad's iscsi_sysfs ibft patch and merging it and fixing up the related code. > I sort of implemented what you want now. A lot of the pieces are now done, and we just have to put the last ones together. In the git tree we now log into all the targets that are present (instead of the first one with the boot flag > set), and you can bind a iface to portals found in the firmware. The missing pieces are doing the iface binding automatically: > 1. If the initiator name is the same for all ports but the user wants to bind a session through the nic that the portal was set up with in the firmware, we currently do not support this with the firmware commands. > This is the normal old style iface binding by hwaddress or netdev name, so we can do it. > - if you have port0 with initiator-nameA and the ibft info for that port has target-portalZ, and port1 has a different initiator-nameB but its ibft info also has target-portalZ, we only log in to the target portal once right now. > We probably wanted to at least log into once for each initiator-name (initiator-nameA and initiator-nameB). This is the newer initiatorname iface binding feature. > I am not sure if this also means that we want to bind the session to a specific nic port. This would be iface binding with initiatornames and (hwaddress or netdev names), and we support this today too. > So maybe we need one new super flag for the firmware related commands that takes in the binding preferences. > iscsistart -b --create-iface-binding=INITIATORNAME | (HWADDRESS | NETDEV) > iscsiadm -m discovery -t fw --create-iface-binding=INITIATORNAME | (HWADDRESS | NETDEV) -l > iscsiadm -m fw -l --create-iface-binding=INITIATORNAME | (HWADDRESS | NETDEV) Now, I guess iface binding here is an abstraction to address multiplicity and the spec does not address that. So, there is not going to be a standard implementation unless the iBFT spec addresses this.So, we are goind to see different policies here. This also means that to change the iface-binding from INITIATORNAME to say HWADDRESS it would require creating a new initrd unless the iBFT table provides a flag. -Shyam --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: Fwparam tool limitation (multiple session at boot time.)
Konrad wrote: >On Wed, Nov 26, 2008 at 06:06:41AM -0600, Mike Christie wrote: > > > > [EMAIL PROTECTED] wrote: > > > The open-iscsi fwparam tool does not connect through all the > > > initiators in the initiator structure exported by the iBFT. > > > > > > I ask this because though the Nic fw can connect twice to the same > > > target using both the initiators(Dual port card) but then the OS > > > makes only one connection with the last(I hope I got this right) > > > initiator with the Firmware boot selected flag set. > > > > > > Now, I would think we should have both ports(dual port NIC) with an > > > iqn should be able to connect to a target portal and thus have two > > > sessions to the same target portal. > > > > > > Is there a specific reason for this design or it just needs some coding? > > > > > > > Ok I finally got around to fixing up Konrad's iscsi_sysfs ibft patch > > and merging it and fixing up the related code. >Thank you for doing that. By now, I think I owe you a box of your favorite beverage. Perfect timing too - X-Mas is coming around the corner :-) I will second that. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
