Unable to Identify the Initiators to Be Added When Multiple Initiators Exist

Publication Date:  2012-07-22 Views:  230 Downloads:  0
Issue Description

When an initiator is to be added to a host on the ISM, too many initiators are available to choose from.

Product and version information:
  • S2600
  • S5000 series
  • The OS is Windows 2003
Alarm Information
None
Handling Process
  1. Check the information of the initiators on the host.
    1. Double-click the initiator icon on the desktop to launch Microsoft iSCSI Initiator.
    2. Click the General tab to view and record the initiator names.
  2. Log in to the ISM to add those initiators for the host.
Root Cause

The available initiators are excessive and without classification, preventing users from choosing what they need to be added.

Suggestions
  • The OS of the host is either SUSE 9 or Red Hat 4, and you can view the initiator status on different OSs as shown in Table 1.
    Table 1 Checking the information about initiators (for SUSE 9 or Red Hat 4)

    Initiator Type

    Procedure

    FC initiator

    1. Run the command cd /proc/scsi/qla2xxx to go to the qla2xxx directory.
    2. Run the command ls to display the file that corresponds to the initiator, such as 3, 4.
      NOTE:
      When the host contains two initiators, two directories exist in the system. In this case, users have to view and record the initiator names in both directories.
    3. Run the command less X to view and record the initiator names. X stands for the file name that corresponds to the initiator. The initiator name is like scsi-qla0-adapter-port=21000018822a3c1e.
    4. Enter q to complete the procedure.

    iSCSI initiator

    1. Run the command cd /etc to go to the etc directory.
    2. Run the command less initiatorname.iscsi to view and record the initiator names, such as /etc/initiatorname.iscsi.
    3. Enter q to complete the procedure.

    SAS initiator

    1. Run the command cd /proc/mpt to go to the mpt directory.
    2. Run the command ls to display the directory that corresponds to the initiator, such as ioc0, ioc1.
      NOTE:
      When the host contains two initiators, two directories exist in the system. In this case, users have to view and record the initiator names in both directories.
    3. Run the command cd ioc0 to go to the ioc0 directory.
    4. Run the command less info to view and record the initiator names.
    5. Enter q to complete the procedure.
  • For SUSE 10 or Red Hat 5

    Initiator Type

    Procedure

    FC initiator

    1. Run the command cd /sys/class/fc_host to display the directory that corresponds to the initiator, such as host1, host2.
      NOTE:

      When the host contains two initiators, two directories exist in the system. In this case, users have to view and record the initiator names in both directories.

    2. Run the command cd hostX to go to the directory where the initiators reside.
    3. Run the command less port_name to view and record the initiator names, such as 0x210000188246d33a.
    4. Enter q to complete the procedure.

    iSCSI initiator

    1. Run the command cd /etc/iscsi to go to the iscsi directory.
    2. Run the command less initiatorname.iscsi to view and record the initiator names, such as iqn.1996-04.de.suse:01:2e5531e59c3.
    3. Enter q to complete the procedure.

    SAS initiator

    Contact technical support engineers.

  • For Windows

    Initiator Type

    Procedure

    FC initiator

    Contact technical support engineers.

    iSCSI initiator

    1. Launch the Microsoft iSCSI Initiator software.
    2. Click the General tab to view and record the initiator names, for example, the Initiator Node Name is iqn.1991-05.com.microsoft:w90002877.china.huaweisymantec.com.

    SAS initiator

    Contact technical support engineers

END