Why does an iSCSI initiator keep trying to establish a connection to a storage array although the related iSCSI host port can be pinged through?

0

The cause of this situation is that the 3620 port is suppressed, resulting in that the iSCSI initiator cannot be connected to the storage system. For security reasons, the hardware firewalls on networks, software firewalls on hosts, or other security software suppress certain ports. To rectify the fault, you simply need to remove the suppression on port 3620.

Other related questions:
How to configure a switch after the iSCSI host ports on a storage array are bound?
Storage arrays support only the 802.3ad binding mode. The 802.3ad mode is also known as the dynamic link aggregation policy. Under this policy, multiple ports on a network adapter work in the same activated aggregation group and share the same rate and duplex mode. After the iSCSI host ports on a storage array are bound, dynamic link aggregation needs to be configured for the ports on the switch connecting to the storage array. For example, on a switch, ports 19 and 20 are connected to a storage array, and then the method for configuring link aggregation of the dynamic LACP mode is as follows: system-view System View: return to User View with Ctrl+Z. [S-Switch]interface GigabitEthernet 1/0/19 [S-Switch-GigabitEthernet1/0/19]lacp enable LACP is already enabled on the port! [S-Switch-GigabitEthernet1/0/19]quit [S-Switch]interface GigabitEthernet 1/0/20 [S-Switch-GigabitEthernet1/0/20]lacp enable LACP is already enabled on the port! [S-Switch-GigabitEthernet1/0/20]quit NOTE: After the dynamic link aggregation is enabled for some ports on a switch, the switch automatically adds the ports to an aggregation group.

Method used to configure the iSCSI initiator in SLES 9
The basic iSCSI configuration and CHAP authentication configuration in SLES 9 are the same as those in Red Hat 4. Refer to iSCSI initiator configuration in Red Hat 4.

Method used to configure the iSCSI initiator in Windows
You can configure the iSCSI initiator in Windows as follows: Perform basic iSCSI configurations as follows: 1. Check whether the Microsoft iSCSI service has been started. If the iSCSI service has not been started, set the service to automatically start. 2. Open the iSCSI initiator configuration tool. Choose Start > Control Panel and double-click the iSCSI Initiator icon. 3. (Optional) Change the initiator name. On the General tab page, click Change... and modify Initiator node name. The node name must be unique. Note: When the service is running properly, do not modify the node name. Otherwise, services will be interrupted. 4. Add targets. Under Target Portal of the Discovery tab page, click Add. In the Add Target Portal dialog box that is displayed, configure Target IP and the port number. The port number of iSCSI is 3260 by default. 5. On the Targets tab page, click Refresh. You can see all targets. Select all targets in the inactive status and click Logon. Select the first item. 6. On the Computer Management page, choose Storage > Disk management. You can view the LUNs on the disk array. Configure Challenge Handshake Authentication Protocol (CHAP) as follows: 1. On the disk array, configure the CHAP name and password of the initiator. 2. In the Log On to Target dialog box, click Advanced... and configure the CHAP user name and password.

Method used to configure the iSCSI initiator in Solaris 10
Method used to configure the iSCSI initiator in Solaris 10: 1. Check whether iSCSI services have been started. Run svcs -a |grep iscsi to check the status of iSCSI. If the status of iSCSI is online, iSCSI services have been started. Otherwise, run svcadm enable iscsi_initiator to start iSCSI services. 2. Configure the Solaris iSCSI initiator. Run iscsiadm add discovery-address [ip addr:portal no] # iscsiadm add discovery-address xxx.xxx.xxx.xxx:3260 to configure the Solaris iSCSI initiator. 3. Add an initiator corresponding to the host on the array side and map it to the LUN. 4. (Optional) Methods used to search for the iSCSI target: a. If a dynamic discovery device (SendTargets) has been configured, run the following command: # iscsiadm modify discovery --sendtargets enable b. If a dynamic discovery device (iSNS) has been configured, run the following command: # iscsiadm modify discovery --isns enable c. If a static discovery device has been configured, run the following command: # iscsiadm modify discovery --static enable 5. Run devfsadm -i iscsi to create links for iSCSI devices. 6. Run format to check iSCSI disks.

Method used to configure the iSCSI initiator in SLES 10
Method used to configure the iSCSI initiator in SLES 10: Basic iSCSI configuration: 1. Run /etc/init.d/open-iscsi start to start iSCSI services. 2. Modify the configuration file /etc/iscsi/iscsid.conf and set node.startup to automatic to enable automatic logins to the target. 3. Run iscsiadm -m discovery -t st -p [targetip] to add the target. 4. Add ports detected on the storage array to corresponding hosts and map these ports to LUNs. 5. Run iscsiadm -m node -p [targetip] -l to register the target. 6. Run chkconfig -add open-iscsi to enable automatic startup of the server. 7. Run fdisk -l to scan for the LUN mapped to the host. CHAP configuration: 1. Run the following three commands in sequence to add the CHAP authentication for a target: iscsiadm -m node -o update -p [targetip] -n node.session.auth.authmethod -v CHAP iscsiadm -m node -o update -p [targetip] -n node.session.auth.username -v [chap user name] iscsiadm -m node -o update -p [targetip] -n node.session.auth.password -v [Chap auth passwd] 2. Configure the same user name and password for the target on the storage side by referring to the array operation guide. 3. Run iscsiadm -m node -p targetip -l to register the target. After registration, LUNs can be detected. 4. If CHAP authentication for multiple targets is required, repeat the preceding steps.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top