HP StorageWorks SAN Virtualization Services Platform Administrator Guide (5697-0934, May 2011)

VSM server zoning
To verify proper back-end zoning for the VSM server, open the VSM management interface. Go
to the Data Path Module and verify the number of back-end HBAs listed for each DPM. To check
the settings of the second VSM, failover the passive VSM. Check the back-end HBAs for that DPM
on the newly-active VSM.
DPM zoning
To verify proper zoning from the DPM side, extract the VSM Snap package (the file is named
save_state...tgz), and open the wwpn file located in the \proc\kahuna\fps\ folder. Use your
preferred editor application, such as Microsoft Notepad. Below is an example of the file content:
Prt WWPN T FC_ID S
=== ================ = ====== =
0 50001fe100002001 L 010000 U
0 20fd00606951a322 R fffc01 D
0 210000e08b813001 R 010d00 U
1 50001fe100002002 L 010100 U
This file shows the WWN of all ports known to the DPM. The “Prt” column shows the port number
on the DPM. The “WWPN” column shows the WWPN seen from this DPM port. This includes the
ports local to the system (designated with “L” in the third column), and all visible remote host/HBA
or target/disk ports (designated with “R” in the third column). The fourth column shows the Fibre
Channel ID. In the fifth column, an entry is marked “U” if it is both visible and currently logged in
with the DPM, while an entry marked “D” is either down or failed the login negotiation.
Use this file to verify that the host or target device HBA port is visible through the expected DPM
port. These entries can be correlated with the name server entries of the fabric switch to determine
whether cabling or the zoning configuration is correct.
For each DPM port, the first entry is the port itself (marked as ‘L’). For each even port (front-end
port), verify that the DPM can see the host HBAs zoned with this port. Similarly, for each odd port
(back-end port), verify that the DPM is connected to the VSM server and EVA or MSA ports as
expected. Repeat the process for all DPMs.
VSM server LUN masking
To verify a proper LUN masking configuration on the VSM server, open the VSM management
interface and go to the back-end LUs. Make sure that VSM can see all the back-end LUs provisioned
to the VSM HBAs. For each back-end LU, verify that the number of paths is correct. To check the
settings of the second VSM, failover the passive VSM server, and then repeat the process.
DPM LUN masking
To verify proper LUN masking from the DPM side, extract the SaSnap package and open the pscs
file located in the \proc\kahuna\css folder. Use your preferred editor application, such as
Microsoft Notepad. Below is an example of the file content:
Index PSCObjP Initiator WWPN Target WWPN LUN Type IOCR
MXSZ
===== =========== ================ ================ ===== ===== ====
====
0 0x4829b008 50001fe100002002 50001fe15000c8a9 1 FCP SOFT
--
1 0x4829b18c 50001fe100002002 50001fe15000c8a9 2 FCP SOFT
--
This file shows the current accessible paths for physical disks (virtual disks) presented to the DPM
from the EVAs or MSAs. An entry is created only if the path (for example, Initiator port – Target
port – LUN) is visible to the DPM (in other words, logged in and responding to I/Os). Missing
entries typically indicate that a physical disk is not properly connected (check cabling and zoning)
or enabled (check LUN masking).
108 Basic maintenance and troubleshooting