pd Suggested Action 6
Check the release notes for mandatory updates and patches to the HP 3PAR OS version that is
installed and install as needed to support this PD in this cage.
pdch
• Displays chunklets state issues
• Checks LD connection paths, remote chunklets, and remote disks
Format of Possible pdch Exception Messages
pdch LD:<ldid> "Connection path is not the same as LD ownership"
pdch ch:<initpdid>:<initpdpos> "Chunklet is on a remote disk"
pdch LD:<ldid> "LD has <count> remote chunklets"
pdch Example 1
Component ------------Summary Description------------ Qty
pdch LDs wwith connection path different than ownership 1
Component -Identifier- -------Detailed Description--------
pdch ld:tp-0-sd-0.1 Connection path is not the same as LD ownership
pdch Suggested Action 1
Use the CLI showld, showpd, and shownode commands. If the ownership issue is not created
due to a node missing or failed PD, Contact HP support to request support for moving the LDs to
the desired location for your system. See “Contacting HP Support about System Setup” (page 73).
cli% showld
Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru MapV
19 pdsld0.0 1 normal 1/0 256 0 P,F 0 --- Y N
20 pdsld0.1 1 normal 1/0 7680 0 P 0 --- Y N
21 pdsld0.2 1 normal 1/0 256 0 P 0 --- Y N
pdch Example 2
Component -------------------Summary Description------------------- Qty
pdch LDs with connection path different than ownership 23
pdch LDs with chunklets on a remote disk 18
Component -Identifier- ---------------Detailed Description--------------
pdch LD:35 Connection path is not the same as LD ownership
pdch ld:35 LD has 1 remote chunklet
pdch Suggested Action 2
The primary I/O paths for drives are balanced between the two nodes that are physically connected
to the drive cage. The node that normally has the primary path to a drive is considered the owning
node. If the secondary node's path has to be used for I/O to the drive, that is considered remote
I/O.
These messages usually indicate a node-to-cage FC path problem because the drives (chunklets)
are being accessed through their secondary path. These are usually a by product of other conditions
such as drive-cage/node-port/FC-loop problems; focus on troubleshooting those. If a node is offline
58 Troubleshooting
To Next Page
Loading...
