SAN with multiple interfaces in the same subnet
I've got an iSCSI SAN with two controllers (IBM DS3300). Both controllers are in the same subnet (lets say 192.168.0.0/24). I have the same targets / nodes with the same IQN available on both controllers (lets say 192.168.0.2 and 192.168.0.3), but I've only figured out how to attach my servers (running CentOS 5.5) to attach to one controller at a time. I'm not using any authentication or anything, and when I run discover, I see both portals. I'd like iscsid on the servers to either load-balance or fail over from one to the other, but it's not working that way. How can I make this work? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Adding New ISCSI LUN to Target, How does client iSCSI initiator access new Lun
Hello All, I have a question, when you add a new lun to iscsi target, if client iSCSI initiator is already logged in to target, do i have to restart the client iSCSI initiator for it to see the new lun? how can i make client iSCSI initiator see new lun with out restarting iSCSI initiator and losing connection to current Target and Lun's? Thanks --Rahsaan -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Setting up iSCSI targets: iscsiadm: No records found! problem
Hi all, I am trying to setup a backup partition on a 40TB storage server. There are already partitions setup on that server that are working, so the storage server configuration is ok. So I have another server where I need the storage, which I will call worker-server for the sake of explanation and storage-server is the 40TB one. Using openfiler: * I created a 4TB partition on the storage-server * created a target * did LUN mapping * created a network entry (255.255.255.255 mask, ok?) * allowed access to it. So I log into the worker-server: * I install iscsi-initiator-utils * chkconfig iscsi on * I checked initiatorname.iscsi, there is something there, so should be ok? * I run service iscsi start - Setting up iSCSI targets: iscsiadm: No records found! ... * Needless to say, discovery is blank as well when I run iscsiadm -- mode discovery --type sendtargets --portal ip_address Am I doing something completely wrong? Anyone any suggestion? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: SAN with multiple interfaces in the same subnet
On 10/01/2010 04:28 PM, JonathanGnagy wrote: I've got an iSCSI SAN with two controllers (IBM DS3300). Both controllers are in the same subnet (lets say 192.168.0.0/24). I have the same targets / nodes with the same IQN available on both controllers (lets say 192.168.0.2 and 192.168.0.3), but I've only figured out how to attach my servers (running CentOS 5.5) to attach to one controller at a time. I'm not using any authentication or anything, and when I run discover, I see both portals. I'd like iscsid on the servers to either load-balance or fail over from one to the other, but it's not working that way. How can I make this work? There is not iscsi level multipath. You have to log into both portals, then use something like dm-multipath and multipath-tools (in RHEL the rpms is called device-mapper-multipath-tools) to load balance or failover across the iscsi paths. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Adding New ISCSI LUN to Target, How does client iSCSI initiator access new Lun
On 10/03/2010 02:08 PM, Rahsaan Page wrote: Hello All, I have a question, when you add a new lun to iscsi target, if client iSCSI initiator is already logged in to target, do i have to restart the client iSCSI initiator for it to see the new lun? how can i make client iSCSI initiator see new lun with out restarting iSCSI initiator and losing connection to current Target and Lun's? If you use a target that sends the iscsi async pdu with REPORT_LUNS_DATA_CHANGED then the new luns should be added automatically for you (deleted luns are not removed though and need to be manually deleted). If it is not getting automatically added then you need to run either //rescan all sessions for new luns iscsiadm -m session --rescan // rescan specific session iscsiadm -m session -R $SID --rescan (see the README for other variants) This commands only add new luns. If you want something that adds and deletes luns then use the rescan-bus.sh script in the sg utils. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Setting up iSCSI targets: iscsiadm: No records found! problem
On 10/04/2010 11:51 AM, joachim.deschrij...@ugent.be wrote: Hi all, I am trying to setup a backup partition on a 40TB storage server. There are already partitions setup on that server that are working, so the storage server configuration is ok. So I have another server where I need the storage, which I will call worker-server for the sake of explanation and storage-server is the 40TB one. Using openfiler: * I created a 4TB partition on the storage-server * created a target * did LUN mapping * created a network entry (255.255.255.255 mask, ok?) * allowed access to it. So I log into the worker-server: * I install iscsi-initiator-utils * chkconfig iscsi on * I checked initiatorname.iscsi, there is something there, so should be ok? * I run service iscsi start - Setting up iSCSI targets: iscsiadm: No records found! ... * Needless to say, discovery is blank as well when I run iscsiadm -- mode discovery --type sendtargets --portalip_address Am I doing something completely wrong? Anyone any suggestion? That last time this was reported the user had to modify the target a little more. Here is what they said they had to do: Thanks for your reply. I was able to resolve the issue by modifying /etc/initiator.deny and commenting all the lines that were denying access to configured disk. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
