drive-cage/node-port/FC-loop problems; focus on troubleshooting those. If a node is offline due to a
service action, such as hardware or software upgrades, these exceptions can be ignored until that action
has finished and the node is online.
In this example, LD 35, with a name of R1.usr.3, is owned (Own) by nodes 3/2/0/1, respectively, and the
primary/secondary physical paths to the drives (chunklets) in this LD are from nodes 3 and 2,
respectively. However, the FC path (Port B) from node 3 to PD 91 is failed/missing, so node 2 is
performing the I/O to PD 91. When the path from node 3 to cage 3 gets fixed (N:S:P 3:0:4 in this
example), this condition should disappear.
cli% showld
Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru
MapV
35 R1.usr.3 1 normal 3/2/0/1 256 256 V 0 ---
N Y
cli% showldch R1.usr.3
cli% showpd -s -failed -degraded
cli% showcage
Normal condition (after fixing):
cli% showpd 91 63
----Size(MB)---- ----Ports----
Id CagePos Type Speed(K) State Total Free A B
63 2:2:3 FC 10 normal 139520 124416 2:0:3* 3:0:3
91 3:8:3 FC 10 normal 139520 124416 2:0:4 3:0:4*
port
Checks for the following port connection issues:
• Ports in unacceptable states
• Mismatches in type and mode, such as hosts connected to initiator ports, or host and Remote Copy
over Fibre Channel (RCFC) ports configured on the same FC adapter
• Degraded SFPs and those with low power; perform this check only if this FC Adapter type uses SFPs
• Ports listed as hosts in "showhost" that are not ready or not configured as host
• Host ports or systems with too many initiators connected
Format of Possible port Exception Messages
port 87
To Next Page
Loading...
