No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


A Server Running AIX Fails to Set Up iSCSI Connections to the S5500T

Publication Date:  2013-12-12 Views:  96 Downloads:  0
Issue Description
An IBM Power 7 server that runs the AIX 7.1 operating system is connected to the S5500T. iSCSI connections are configured and LUNs are mapped to the server. However, the LUNs cannot be detected. The iSCSI connections fail. The version of the S5500T is V100R002C00SPC013 and the iSCSI initiator is built in the system.
Alarm Information
Handling Process
Accomplish the following steps to set the initiator name of the server:
Step 1 Log in to the server using SSH and run the smit iscsi command.
Step 2 Select iSCSI Protocol Device and press Enter.
Step 3 Select Change/Show Characteristics of an iSCSI Protocol Device and press Enter.
Step 4 Select iSCSI Initiator Name and press Enter.
Change iSCSI Initiator Name to
Then configure the targets file on the server as follows:
Step 1 Obtain the S5500T's target information.
On the command-line interface (CLI), run the showsys command to obtain the iSCSI Device Name information.
For example:
Step 2 Configure the targets file.
Open the /etc/iscsi/targets configuration file and add 3260 is the IP address of the iSCSI host port on the disk array.
Root Cause
On the server, run the cfgmgr -l iscsi0 command to scan disks. Then open disk array logs to view information exchanged between the server and the storage system:
[2012-08-31 16:23:30][1774892][15000002905a2][INFO][Login process jump to next stage with login_flags:a00000000 and session type(Normal).][ISCSI][target_c._login,1118]
[2012-08-31 16:23:30][1774892][15000002905a3][INFO][Check remote iSCSI initiator version 0][ISCSI][target_c._login,1175]
[2012-08-31 16:23:30][1774892][15000002905a0][INFO][Created session with  with ISID(Initiator Session ID) is  80 aa aa aa ab cd, TSIH (Target Session Identifying Handle) is 375][ISCSI][print_is.essage,396]
[2012-08-31 16:23:30][1774892][1500000290481][INFO][Vendor name in DB is () and brand name in DB is ().][ISCSI][ISCSI_Ge.etName,330]
[2012-08-31 16:23:30][1774892][1500000290a74][WARN][ISCSI_LINK_EVENT :invalid TargetName(ipv4): wanted:, transed :][ISCSI][ISCSI_Ju._valid,7161]
[2012-08-31 16:23:30][1774892][15000002901ec][ERR][Target name check failed][ISCSI][target_p.otiate,2554]
[2012-08-31 16:23:30][1774892][15000002901e7][ERR][FrontRdy_378_1 Parameter negotiation failed][ISCSI][handle_login,7503]
[2012-08-31 16:23:30][1774892][15000002901a7][ERR][FrontRdy_378_1 return failed,login failed.][ISCSI][iscsi_rd.thread,4092]
[2012-08-31 16:23:30][1774892][150000029049a][INFO][FrontRdy_378_1 exit, total command in list is 0 , total command in array is 0.][ISCSI][iscsi_rd.thread,4393]
The log in red indicates that the IP address of the target name that the storage system wants to obtain is in the format of (a port ID is added to the original IP address). However, only the IP address is specified in the configuration file, so the disk array cannot detect the server.
This fault occurs because the format of the target name is changed for the current version. Therefore, the iSCSI connections must be reconfigured.
Currently, the product is being optimized. Therefore, the port ID changes with the conditions. If the port ID changes, you can rectify the fault using the method provided in this article.