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: iscsiadm: exiting due to configuration error
On Mon, 2008-10-13 at 12:53 -0500, Mike Christie wrote: DrBidwell wrote: I am running iscsid version 2.0-730 on debian. I have the default / etc/iscsid.conf (also symbolically linked to /etc/iscsi/scsid.conf). iscsid starts fine, but iscsiadm always give the above configuration error. /etc/initiatorname.iscsi (also symbolically linked to /etc/iscsi/ initiatorname.iscsi) contains: InitiatorName=iqn.1989-09.edu.andrews:01.56e12c552ac3 InitiatorAlias=webdb.cc.andrews.edu An strace makes it look like it hasn't even tried to open any of the config files yet. Any ideas? You have to start iscsid first. iscsid was running, but there was some interaction with ldap. We removed the ldap entries from nsswitch.conf and it started working. I haven't had the time to go back and figure out what was really the problem. -- Daniel R. Bidwell | [EMAIL PROTECTED] Andrews University | Information Technology Services --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
AW: iscsi udev problem
Hallo, thanks for your help but i've fixed this problem. After reinitializing the luns on san, it was possible to get a block-device, which I can mount. Thanks maddin -Ursprüngliche Nachricht- Von: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] Im Auftrag von Konrad Rzeszutek Gesendet: Dienstag, 14. Oktober 2008 15:23 An: open-iscsi@googlegroups.com Betreff: Re: iscsi udev problem On Tue, Oct 14, 2008 at 11:53:25AM +0200, Mega Mailingliste wrote: Hi dudes, i've got a problem with iscsid (2.0-868) under centos (5.2) and a infortrend iscsi san (s12e-r1132-4). After mapping some partitions of a logical volume to our server, I can login via iscsiadm to this luns. The problem is that udev (or anything else, but I think it's udev) won't make a mapping from /dev/sgx to /dev/sdx, thus I The sg devices are very different from the sd ones. Or when you say mappings are you referring to the /sys/block/sdX/device/generic link? (and vice- versa)? That is the kernel constructing those. can't mount that device. I have no idea why :/ You can't mount the /dev/sdX device? Or is it that the /dev/sdX don't exist but only the /dev/sgX show up? Can you provide the 'lsscsi -v' output? Some strange behavior before was, that I've got the same problem on another test server, but after some reboots the block-device /dev/sdx exists. Cheers Martin --~--~-~--~~~---~--~~ 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: iscsi udev problem
On Tue, Oct 14, 2008 at 11:53:25AM +0200, Mega Mailingliste wrote: Hi dudes, i've got a problem with iscsid (2.0-868) under centos (5.2) and a infortrend iscsi san (s12e-r1132-4). After mapping some partitions of a logical volume to our server, I can login via iscsiadm to this luns. The problem is that udev (or anything else, but I think it's udev) won't make a mapping from /dev/sgx to /dev/sdx, thus I The sg devices are very different from the sd ones. Or when you say mappings are you referring to the /sys/block/sdX/device/generic link? (and vice-versa)? That is the kernel constructing those. can't mount that device. I have no idea why :/ You can't mount the /dev/sdX device? Or is it that the /dev/sdX don't exist but only the /dev/sgX show up? Can you provide the 'lsscsi -v' output? Some strange behavior before was, that I've got the same problem on another test server, but after some reboots the block-device /dev/sdx exists. Cheers Martin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Omega replica watch Same quality at lower price
Omega replica watch Same quality at lower price http://chocclue.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
iscsi udev problem
Hi dudes, i've got a problem with iscsid (2.0-868) under centos (5.2) and a infortrend iscsi san (s12e-r1132-4). After mapping some partitions of a logical volume to our server, I can login via iscsiadm to this luns. The problem is that udev (or anything else, but I think it's udev) won't make a mapping from /dev/sgx to /dev/sdx, thus I can't mount that device. I have no idea why :/ Some strange behavior before was, that I've got the same problem on another test server, but after some reboots the block-device /dev/sdx exists. Cheers Martin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
