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

LUN Detection Error Occurs When the S2600 Is Accessed by FreeBSD

Publication Date:  2012-07-22 Views:  2 Downloads:  0
Issue Description
The FreeBsd OS accesses the S2600 storage device through an iSCSI host port. However, when the LUN scanning command is executed on the OS, the following error message appears, causing the scanning of LUNs fails:
freebsd-ak# iscontrol -c /etc/iscsi.conf -n target0  0x0200: Initiator error 
Product and version information:
  • S2600
  • The OS is FreeBSD
Alarm Information
None
Handling Process
  1. Run the following commands to change initiatorname in /etc/iscsi.conf to a value that is different from the host name.

     

    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
    

     

  2. Run the following commands to scan LUNs.

     

    freebsd-ak# camcontrol devlist
    <COMPAQ RAID 0  VOLUME OK> at scbus0 target 0 lun 0 (pass0,da0)
         <HUAWEISYMANTEC S2600 1>  at scbus5 target 0 lun 0 (da1,pass1)
         <HUAWEISYMANTEC S2600 1>  at scbus5 target 0 lun 1 (da2,pass2)
    
Root Cause
  1. By checking the network connections, the IP addresses of the iSCSI host ports on the S2600 can be pinged through by the host.
  2. Check the /etc/iscsi.conf configuration file to make sure that all the options meet the standards.
  3. After the rescanning is performed when all the options are modified, initiatorname appears to be consistent with the host name, as shown below:
    target0 {
    
            #authmethod      = CHAP
    
            #chapIName       = YOUR-ISCSI-USERNAME
    
            #chapSecret      = YOUR-ISCSI-PASSWORD
    
            initiatorname   = freebsd-iscsi
            TargetName      = iqn.2006-08.com.huaweisymantec:Oceanspace:2100111111222222:notc
    
    onfig:5.5.5.6
    
            TargetAddress   = 5.5.5.6:3260,2
    
Conclusion:
  • When initiatorname is set to be consistent with the host name, error messages appear once the scanning is performed.
Suggestions

During the configuration of iSCSI initiators, make sure the names of initiators and hosts are different, or conflictions can occur.

END