NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dh1760
May 26, 2014Aspirant
Connecting iscsi disk to CentOS 6.5 system
For testing purposes, I created a LUN group, set authentication open (no CHAP), and am following the steps outlined in https://ezunix.org/index.php?title=Connect_to_an_iSCSI_Volume_with_RedHat,_Fedora_or_CentOS_Linux to configure and initiate the disk. Everything flows as outlined until restarting /etc/init.d/iscsi to attach the drive. The restart stalls and I can see repeated log entries of "May 26 09:43:00 uka4-ob iscsid: connect to 192.168.168.252:3260 failed (Connection refused)" until I ctrl-c to stop the script.
I was able to discover the LUN groups using "iscsiadm -m discovery -t sendtargets -p 192.168.168.252", so it seems like connections should be accepted (assuming discovery happens on the same port 3260 as connections). I have CHAP disabled on the readyNas LUN group and CHAP username/password commented in iscsid.conf.
Any advice or assistance would be greatly appreciated.
I was able to discover the LUN groups using "iscsiadm -m discovery -t sendtargets -p 192.168.168.252", so it seems like connections should be accepted (assuming discovery happens on the same port 3260 as connections). I have CHAP disabled on the readyNas LUN group and CHAP username/password commented in iscsid.conf.
Any advice or assistance would be greatly appreciated.
2 Replies
- dh1760AspirantA bit more info: the readyNas has 2 network interfaces on 192.168.1.0.24 and 192.168.168.0/24. I am attempting this connection via the 192.168.1.0/24 interface (target address is 192.168.1.252), as that is on the same network as the client. The discovery reported the 2 target groups via each interface:
192.168.168.252:3260,1 iqn.1994-11.com.netgear:ngnas1:a901f7d2:group1
192.168.1.252:3260,1 iqn.1994-11.com.netgear:ngnas1:a901f7d2:group1
192.168.168.252:3260,1 iqn.1994-11.com.netgear:ngnas1:fbc542ca:group2
192.168.1.252:3260,1 iqn.1994-11.com.netgear:ngnas1:fbc542ca:group2
I set the node login to the group2 target via the 192.168.1.252:3260 portal, however the "connection refused" messages are being reported as coming from the other (192.168.168.252) interface. It looks like the problem is that when restarting iscsi, the connection is being attempted via the wrong interface.
[root@uka4-ob ~]# iscsiadm --mode node iqn.1994-11.com.netgear:ngnas1:a901f7d2:group1 --portal 192.168.1.252:3260 --login
[root@uka4-ob ~]# /etc/init.d/iscsi restart
Stopping iscsi: [ OK ]
Starting iscsi: iscsiadm: Could not login to [iface: default, target: iqn.1994-11.com.netgear:ngnas1:fbc542ca:group2, portal: 192.168.168.252,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not login to [iface: default, target: iqn.1994-11.com.netgear:ngnas1:a901f7d2:group1, portal: 192.168.168.252,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals
Is there a way for me to configure the system so that it only tries to login to the portal that I specify? - dh1760AspirantFigure it out... I had mistakenly connected 2 nodes, one for the (wrong) portal on 192.168.168.252 and the other on the (correct) portal 192.168.1.252.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!