Veritas Volume Manager 5.0 Release Notes HP-UX 11i v3 (5992-1952, August 2011)

# vxdmpadm settune dmp_lun_retry_timeout=interval
Where the interval value is in seconds. The default value of the tunable is 0, which means
that the paths are probed only once.
• Problem
Rootability support and option to reboot when adding or removing boot disk into foreign
category.
The vxddladm addforeign command is used to add a device into a foreign device category
and the vxddladm rmforeign command is used to remove a device from a foreign category.
With VxVM 5.0 for HP-UX 11i v3, boot devices can be added into a foreign device category
but it requires a reboot to make the migration effective.
Workaround
You can use the -r option when either adding or removing the boot disk into a foreign device
category so that the system will automatically reboot on completion of the task. It is
recommended that this option be specified when adding the boot disk to a foreign category.
Following is an example of using rootability support:
Run the following command to bring the current VM rootdisk under nMP control:
# Vxddladm addforeign blockpath=/dev/disk/diskname
charpath=/dev/rdisk/diskname
Run the following command to bring the rootdisk back to DMP control:
# Vxddladm rmforeign blockpath=/dev/disk/diskname
charpath=/dev/rdisk/diskname
Where diskname is the new device name of the current boot disk without the slice part.
Run the following command to transfer control of all devices to nMP:
# vxddladm addforeign blockdir=/dev/disk/ chardir=/dev/rdisk/
Run the following command to transfer control of all devices back to DMP:
# vxddladm rmforeign blockdir=/dev/disk/ chardir=/dev/rdisk/
To automatically reboot the system, users can specify the –r option along with the above
commands. The –r option is only applicable if the current migration involves the boot disk,
otherwise it is ignored. For example:
# vxddladm –r addforeign blockdir=/dev/disk/ chardir=/dev/rdisk/
# vxddladm –r rmforeign blockdir=/dev/disk/ chardir=/dev/rdisk/
The above commands will wait 15 seconds before rebooting the system. You can interrupt
this command by pressing ctrl+c to abort the system reboot.
Cluster Functionality Issues
The following cluster functionality issues are known and applicable for Serviceguard clusters as
well as VCS clusters:
• Problem
If a node leaves the cluster while a plex is being attached to a volume, the volume can remain
in the SYNC state indefinitely.
Workaround
Resynchronize the volume manually using the following command:
Known Problems And Workarounds 29