Veritas Volume Manager 5.0.1 Release Notes, HP-UX 11i v3, First Edition, November 2009

Running the vxdisk scandisks command before the Disk Group (DG) deport operation
triggers DMP reconfiguration that updates the DMP database such that a disk is accessible
through active paths.
• Problem
I/O failures result in the disk failing flag
In some DMP failover scenarios, I/O retry causes the disk failing flag to be set, although
there is nothing wrong with the disks except for the failing flag.
Workaround
Clear the failing flag using the vxedit command.
• Upgrading external ASLs and APMs
The Storage Foundation 5.0.1 release only supports upgrading external ASL and Array
Policy Module (APM) packages from release 5.0 or later.
If your system uses any existing ASLs and APMs from the 4.x release, you may need to
download a 5.0 version of the ASL and APM.. Check the latest array support information
to determine whether an updated ASL or APM package is available for your arrays.
For information about supported arrays, see the Hardware Compatibility List for 5.0.1:
http://docs.hp.com/en/5900-0354/5900-0354.htm
Before upgrading a Storage Foundation product, you must manually remove any existing
external ASL or APM packages That are lower than release 5.0.
After completing the upgrade, obtain the required updated ASLs or APMs to ensure that
the array is claimed correctly.
• Rootability support for native multipathing
The following are software limitations for native rootability support:
— Migration of disks from DMP to native multipathing or vice versa is dependent on the
current boot disk. Therefore, changes may not be reflected if the system is started with
a different disk.
— Target devices must be under DMP control when executing any of the rootability scripts.
— After performing the vxrootmir operation in native multipathing mode, the mirrored
disk is not capable of booting until the mirror is broken from the original root disk.
• Problem
Incorrect paths for the vxvm-iscsi script in the /sbin/init.d/iscsi startup script
The HP-UX operating system uses the /sbin/init.d/iscsi startup script to enable iSCSI
services. During system startup with an iSCSI configuration, the /sbin/init.d/iscsi
script invokes the vxvm-iscsi script. The vxvm-iscsci script is required to perform
appropriate VxVM discovery of iSCSI devices, import diskgroups on those devices, and
start the volumes. In the HP-UX 11i v3 0903 OEUR release, the /sbin/init.d/iscsi
script contains the incorrect path for the vxvm-iscsi script. This issue leads to iSCSI
diskgroups not being automatically discovered and imported.
Workaround
The /sbin/init.d/iscsi script is now corrected by changing all occurrences of /sbin/
init.d/vxvm-iscsi to /sbin/vxvm-iscsi.
• Problem
Issues with persistent disk access records
If you initialize a disk using the following commands, VxVM creates persistent disk access
records.
# vxdisk rm disk_access_name
# vxdisk -f init disk_access_name
18 Veritas Volume Manager 5.0.1 Release Notes