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.
In the Solaris OS versions, only PW008FC2A, PW008FC2-G, PW008FC3, GP7B8FC1A, GP7B8FC1-G, GP7B8FC1, SE0X7F11F and SE0X7F12F can display access paths with FC-AL connections. In the Windows versions, only Fujitsu GP5-FC102, PG-FC102, PG-FCD101, PG-FCD102 and Qlogic HBAs can display access paths. If the server node operates under the Solaris OS and the storage system is a library, tape, or bridge device, only the following tape driver can display access paths:
st, ftla, fsct, IBMtape, mt, lb, sg.
The "Server Node view" and "Storage view" can be used to check access path display. In each view, enable access path display by selecting [View] - [Show/Hide] from the menu and checking [Access Path View]. Physical paths are displayed in black, and access paths are displayed in blue, yellow, or red.
Clicking an HBA displays in light blue all access paths managed by the HBA and the area allocated to the HBA for storage (for the ETERNUS8000, ETERNUS6000, ETERNUS4000, ETERNUS3000, ETERNUS2000, ETERNUS DX60/DX80 and GR series, items up to the Affinity Group (zone) number are displayed).
To determine which device file in the server node is associated with one of these displayed access paths, check "Properties" of the HBA, or open an access path dialog box from the list in "Access Path Information" shown in the following figure.
If the Solaris OS device file is cxtyd*s*, for example, the control number is x and the target ID of access path information is y in HBA "Property". (If the HBA is XSEFC401AF, XSEFC402AF, SG-XPCI1FC-QF2,SG-XPCI2FC-QF2,SG-XPCI1FC-QL2 or SG-XPCI2FC-QF2-Z, however, the controller number, target ID, and LUN cannot be displayed.) In the following figure, the correlation of device files c2t0d0 to c2t0d15 can be recognized because the controller number of the selected HBA is 2, the target ID is 0, and LUN is 0-15.
Also, you can determine the target ID and LUN by selecting [Property] on the pop-up menu. (If the HBA is XSEFC401AF, XSEFC402AF, SG-XPCI1FC-QF2, SG-XPCI2FC-QF2, SG-XPCI1FC-QL2 or SG-XPCI2FC-QF2-Z, however, the target ID and LUN cannot be displayed.) As shown in the figure below, the pop-up menu is displayed by clicking and then right-clicking on an access path. In "Property", "Error Description" can be displayed. The reason for the abnormal access path is written in "Error Description". (No reason may be partially written.)
Clicking on a selected access path displays in light blue the physical paths constituting the access path, as shown in the figure below. However, if several Fibre Channel switches in the access path are cascaded, intermediate paths between the Fibre Channel switches cannot be displayed.
When the Fujitsu multipath disk control mechanism or msdsm (the multi path driver that is built into Windows operating system since Windows Server 2008 by the standard) is used in Solaris OS, Windows or Linux environment, the device file name of the multipath disk mechanism is displayed on the server node. In Solaris OS, Windows (In case of SSC agent, only using the HBA produced by QLOGIC Co.), and Linux (unless the HBA is PG-FC105 (driver version:V4.20q-1), PG-FC106 (driver version:V4.20q-1), PG-FCD101, or PG-FCD102) environments, it is possible to display the access path that configures the device file and the storage area information in turquoise by left-clicking this device file name to select it. With this function, you can visually determine the relationship between storage media and the device files in the server node, so the function improves the efficiency of storage system operation management.
With only the side view displayed, the FcHba-FcHba (or FcCa-FcCa) access path is not displayed. When FcHba (or FcCa) with the FcHba-FcHba (or FcCa-FcCa) access path is clicked, the access path destination FcHba (or FcCa) and its access path are highlighted.
Clicking a channel adapter (FC port) of a storage system where access paths are created displays in light blue all access paths and HBAs managed by the channel adapter.
By left-clicking the representation of the storage area (Affinity Group (zone)/indicated as the colum in the figure), all access paths and HBAs that are managed by the related CA are displayed in blue. In Solaris OS, Windows (In case of SSC agent, only using HBA by QLOGIC Co.) and Linux (only using HBA except for PG-FC105 (driver version:V4.20q-1), PG-FC106 (driver version:V4.20q-1), PG-FCD101, PG-FCD102) environment, if the Fujitsu multipath disk control mechanism or msdsm is set up, the corresponding device file name is also displayed in light blue.
Access path status | Color | Description | Action to be taken | |
|---|---|---|---|---|
OK | (WWPNBINDING) | Green | The access path is normal.
| None |
(ANOTHERBINDING) | Blue | The access path is normal.
| None. However, the LUN cannot be accessed if there is a Fibre Channel switch environment and the HBA is of a type shown in a) or b). Take the action shown indicated below. a) If the HBA is PW008FC2A, PW008FC2-G, PW008FC3, GP7B8FC1A, GP7B8FC1-G, GP7B8FC1, SE0X7F11F, or SE0X7F12F 1) Configure the HBA N-port settings. Refer to "4.1.1.2 N-port settings", and check the N-port settings. If the settings are incorrect, correct them. The N-port settings may be deleted by use of the ETERNUS multipath driver path remove command. 2) Set the access path If the path status does not change to Green after configuring the N-port settings, refer to "6.3.3 Access path setting", select this path, and set the access path. If the HBA is XSEFC401AF or XSEFC402AF, the following action is required to make the LUN be recognized by the OS: 1) Set the HBA N-port(This procedure is a necessary procedure only for the fiber channel switch environment.) Refer to "4.1.1.2 N-port settings", and check the N-port settings. If the settings are incorrect, correct them. 2) Make the OS recognize the LUN Check the storage Ap_id using the cfgadm -al command, and make the OS recognize the LUN using the cfgadm -c configure Ap_id command. For details about the commands, check the man command. When HBAis SG-XPCI1FC-QF2,SG-XPCI2FC-QF2,SG-XPCI1FC-QL2,SG-XPCI2FC-QF2-Z, the following actions are required to make the OS recognize the LUN. 1) Check the storage Ap_id by the cfgadm -al command which makes the OS recognize the LUN and then make the OS recognizes the LUN. Command details can be checked by the man command. | |
Access path error | Red | The access path is disconnected due to an error (if the multipath control mechanism is installed). Or Another part failure caused or may have caused an access path error. (This state also occurs if a device in the access path is faulty.) Moreover, this state also occurs when the Fibre Channel cable on a route is disconnected. | Replace the faulty part, and execute recovery processing. -> "8.1 Windows Displayed in the Event of a Fault and Troubleshooting" | |
Config miss Match and The access path must be inherited. | Yellow | "Yellow" indicates "Config miss Match" or "The access path must be inherited". Right-click the access path, and select [Properties] on the pop-up menu. Check the access path status. | ||
"Config miss Match" Access path settings are incorrect. (Example: WWPN binding is set on the server node side but zoning is not set on the Fibre Channel switch side.) Or the access path cannot be confirmed because the Fibre Channel switch is not registered. For example, one possible cause is that the Fibre Channel switch has erroneous zoning information. | If the Fibre Channel switch is not registered, register it. Right-click the access path, open "Properties" from the pop-up menu, and check "Error contents". Set or delete the access path as required. | |||
"The access path must be inherited". The access path must be inherited because the HBA has been replaced. | ||||
You can know the reason of the Access Path error or the Config miss Match from the Access Path Properties. (see "B.7.5 Access path properties".)
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:
For Solaris 2.6 OS
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 (server node restart processing)
Solaris 7, 8, 9,10 OS (For the environment which uses hard disk driver (HDDV), and does not use multipath control (ETERNUS/GR 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 7, 8, 9,10 OS (For the environment which uses both hard disk driver (HDDV) and multipath control (ETERNUS/GR Multipath Driver, MPLB, MPHD), or uses neither.)
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 (server node restart processing)
After the server node has been restarted
# disks -C
