Veritas Volume Manager 5.1 SP1 Release Notes HP-UX 11i v3 (5900-1518, August 2011)
Table Of Contents
- Veritas Volume Manager 5.1 SP1 Release Notes
- Contents
- 1 Veritas Volume Manager 5.1 SP1 Release Notes
Workaround
There is no workaround for this issue. Patch will be released in future to fix the issue.
• Problem
When the system boots for the first time, after installing VxVM 5.1 SP1 or after an upgrade
from any older VxVM version to VxVM 5.1 SP1, the following warning messages may be
displayed on the console:
Aug 17 19:26:28 vxvm:vxconfigd: V-5-1-0 ddl_migrate_to_devlist_instr:
Turning off NMP Alua mode failed for dmpnode 0x0 with ret = 13
Aug 17 19:26:28 vxvm:vxconfigd: V-5-1-0 ddl_add_disk_instr: Turning
off NMP Alua mode failed for dmpnode 0xffffffff with ret = 13
Aug 17 19:26:28 vxvm:vxconfigd: V-5-1-0 ddl_add_disk_instr: Turning
off NMP Alua mode failed for dmpnode 0xffffffff with ret = 13
Aug 17 19:26:28 vxvm:vxconfigd: V-5-1-0 ddl_add_disk_instr: Turning
off NMP Alua mode failed for dmpnode 0xffffffff with ret = 13
Workaround
These messages do not impact the setup and can be safely ignored. There is no workaround
for this issue.
• Problem
When the system boots after installing VxVM 5.1 SP1, it may hang under the following
conditions:
◦ The system has VxVM as root
◦ The boot disk of the system is connected through an interface that responds slowly.
For example, when the VxVM root disk is connected via the Magellan FC AH401A HBA and
there are 3 or more SAN switches between the server and disk array. This configuration may
result in Magellan driver timeout.
Workaround
◦ If VxVM 5.1 SP1 is not installed, complete the following steps on the system before
beginning the installation process:
1. /usr/lib/vxvm/bin/vxpfto -t 120 -g rootdg
2. vxdmpadm settune dmp_lun_retry_timeout=120
◦ If VxVM 5.1 SP1 is cold installed without applying the settings mentioned in the previous
point or the boot disk is connected through SAN interface, there is no workaround
available.
• Problem
On some hardware configurations, VxVM 5.1 SP1 cannot initialize LUNs of size greater than
2 TB in cdsdisk format. If the initialization is attempted, an error similar to the following is
displayed:
VxVM vxdisk ERROR V-5-1-5433 Device c17t0d1: init failed: Disk is
not useable, bad format
Workaround
For such hardware configurations, there is no workaround for initializing LUNs of size greater
than 2 TB in cdsdisk format.
As an alternative, you can initialize LUNs of size greater than 2 TB in hpdisk format. But,
disks of size greater than 2 TB cannot be set as the root disk.
Known Problems And Workarounds 15