This software gathers information from each device and displays the status of access paths or the status of logical access paths from the server node. This function is effective for verifying the validity of system configuration setup and recognizing the effect of a resource error because it enables the logical relationship in the more complicated SAN environment to be easily determined.
If the server node operates under a Solaris OS environment and the storage system is a library or tape device, the tape-type drivers for which access paths can be displayed are as follows:
st, ftla, fsct, IBMtape, mt, lb, sg, sgen
Note
The Solaris OS server node uses special file /dev/rdsk/cXtX, /dev/rmt to obtain WWPN binding information. For this reason, to recognize WWPN binding, this special file (device file) must be created in advance. If any unused special file is in /dev/rdsk/, /dev/rmt, it causes the access path display to be incorrect. If access path display by this software differs from that by system equipment, clarify the special files defined in the following operations:
Solaris OS (For the environment which uses hard disk driver (HDDV), and does not use multipath control (ETERNUS Multipath Driver, MPLB, MPHD))
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 (server node restart processing)
After the server node has been restarted
# format (Loading processing to HDDV driver's kernel) # disks -C
Solaris OS (For the environment which uses both hard disk driver (HDDV) and multipath control (ETERNUS Multipath Driver, MPLB, MPHD), uses only multipath control or uses neither.)
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 (server node restart processing)
After the server node has been restarted
# disks -C
You can check the access path status connected by the Fibre Channel on the [status] column on the [Access Path] screen.
The status of access paths are displayed as the following icons. When you click the each status, the corresponding error content message is displayed.
In addition, if you check the access path status, click Refresh in the access path status to make the status up-to-date.
Access Path Status | Description | Action |
---|---|---|
| The access path is normal. | None. However, for HBA shown below, you must take actions for making the operating system recognize LUN.
|
| The following possibilities are considered.
|
|
| The following possibilities are considered.
| Click status to display the error content message. Refer to "Error Messages of Access Path" in the ETERNUS SF Messages, take actions according to the instructions for the error message. In addition, if a part failure is suspected, click Reload Conf.: Reload the configuration to the device defined as an access path for identify whether a failure occurs or not. When the access path is set to "Offline", set it to "Online" as necessary. If HBA was reduced, delete the access path on the [Access Path] screen. Refer to "Delete Access Path" in the ETERNUS SF Web Console Guide for details on how to delete. If HBA was replaced, it is required to take corrective action that corresponds to the HBA status displayed on the [Server Detail] screen. Execute [Reload Conf.] as to the replaced HBA-installed device to perform the following steps:
|
| The following possibilities are considered.
| Click Refresh in the access path status to make the status up-to-date. In the following configuration, display "Unknown" because the access path status cannot be obtained.
For displaying the access path status, install Storage Cruiser's agent and register the server on the Management Server. If HBA was replaced, it is required to take corrective action that corresponds to the HBA status displayed on the [Server Detail] screen. Execute [Reload Conf.] as to the replaced HBA-installed device to perform the following steps:
|
(-) hyphen | Access path cannot be displayed because the interface is iSCSI. | None. |
Note
The access path status is not updated automatically. When you check the access path status, click Refresh in the access path status to make the status up-to-date.
In an environment not connected to a Fibre Channel switch, the access path status is not displayed correctly.
It may take a few minutes to update the access path status. You can confirm the completion of the processing on the [Operation History] screen.