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>

Reminder

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

upgrade
MENU

The configuration of the initiator is wrong causes there reports error while scanning the LUN

Publication Date:  2012-11-23 Views:  16 Downloads:  0
Issue Description
The FreeBsd operating system creates connection with the S2600 storage device via the iSCSI host port, while implementing the command to scan the LUN there reports the following error, and it can’t scan the LUN:
freebsd-ak# iscontrol -c /etc/iscsi.conf -n target0  0x0200: Initiator error

Alarm Information
None

Handling Process
Step1. Execute the following command to modify the “initiatorname” item in the “/etc/iscsi.conf” as to the name which is different with the one of application server.
freebsd-ak# iscontrol -c /etc/iscsi.conf -n target0
iscontrol[707]: running
freebsd-ak# iscontrol[707]: (pass1:iscsi0:0:0:0):  tagged openings now 0
iscontrol[707]: (pass2:iscsi0:0:0:1):  tagged openings now 0
iscontrol[707]: cam_open_btl: no passthrough device found at 5:0:2
iscontrol[707]: cam_open_btl: no passthrough device found at 5:0:3
iscontrol: supervise starting main loop

Step 2. Execute the following command to scan the LUN.
freebsd-ak# camcontrol devlist
  VOLUME OK> at scbus0 target 0 lun 0 (pass0,da0)
       at scbus5 target 0 lun 0 (da1,pass1)
       at scbus5 target 0 lun 1 (da2,pass2)

Root Cause
1. Firstly, check the network connection, the application server can ping through the IP address of the S2600 storage system’s iSCSI host port.
2. Check the “/etc/iscsi.conf” configuration file, and confirm each option is accord with the standard.
3. Modify the options one by one, and then implement the scan, we find the name of the “initiatorname” is consistent with the application server’s name, the information displays as:
target0 {
#authmethod      = CHAP
#chapIName       = YOUR-ISCSI-USERNAME
  #chapSecret      = YOUR-ISCSI-PASSWORD
initiatorname   = freebsd-iscsi
TargetName      = iqn.2006-08.com.huawei:oceanstor:2100111111222222:notc
onfig:5.5.5.6
TargetAddress   = 5.5.5.6:3260,2

Hence, we conclude that it’s the name of the “initiatorname” is configured as the same with the application server’s name that causes there reports error when implementing scan.

Suggestions
While configuring the iSCSI initiator, don’t configure it as the same name with the application server, or there will appear conflict.


END