VERITAS Volume Manager 4.1 Release Notes (5900-0591, March 2010)

VERITAS Volume Manager 4.1 Release Notes
Known Problems and Workarounds
Chapter 1 29
Target N_Port_id is = 0x000075
Target N_Port_id is = 0x000076
2. Run the following command on each disk found in step 1, specified by its N_Port_id
setting:
# fcmsutil TD_device_file replace_dsk nport_ID
This is illustrated by the following example:
# for nport in 6b 6c 6d 6e 71 72 73 74 75 76
> do
> fcmsutil /dev/td0 replace_dsk 0x0000$nport
> done
3. Repeat steps 1 and 2 for all other paths that are affected, such as /dev/td1.
DMP Lists Disabled Paths That Have Been Reused
• Problem: When one of multiple paths or cables to a disk array is disconnected, fails, or is
swapped with another path, and then that same path or cable is reconnected or replaced,
it is possible that HP-UX will recognize the recovered path as a new path, not as the same
path that has simply recovered. In this case, DMP will list twice as many paths: the new
ones in the ENABLED state and the old ones (that is, from before the paths were
swapped, removed or replaced) in the DISABLED state. I/O continues to be routed
correctly.
• Workaround: None necessary. VxVM DMP will not automatically clean up the paths that
are no longer in use, or that are in the DISABLED state. When the host is rebooted, the
DMP database will be rebuilt without the DISABLED path definitions.
Disabling DMP
The disabling of DMP is not supported. The vxdmpdis and vxdmpen utilities that were
provided prior to VxVM 3.2 to disable and enable DMP are no longer provided.
Removing DMP Disks
• Problem: The vxdiskrm command only logically removes a disk. It does not remove the
disk from DMP. Therefore, the disk may re-appear after a vxdctlenable even if the disk
has been physically removed.
• Workaround: Restart using vxconfigd. This causes the DMP database to be updated, and
the physically removed device will no longer appear.