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

WARNING: The installed kernel modules include multiple versions of
module 'llt'. Version 1.500.[447C70B3] will be ignored.
WARNING: The installed kernel modules include multiple versions of
module 'gab'. Version 1.500.[447C7115] will be ignored.
You can ignore these messages.
Workaround
Before you begin the upgrade process, you can enter the following commands to ensure that
these messages are not displayed:
# rm /usr/conf/mod/gab-dbg
# rm /usr/conf/mod/llt-dbg
After you run these commands, you must upgrade to 5.0 on HP-UX 11i v3. You cannot revert
to 5.0 on HP-UX 11i v2.
• Problem
VEA action agent starts immediately after a MANAGED host installation.
Workaround
When installing in MANAGED mode you must execute the following script after installing the
Veritas packages:
/opt/VRTSaa/config/remove_vxaa.sh
This script unconfigures the VEA Action Agent and prevents it from starting on a MANAGED
host installation.
• Problem
When upgrading from a system running VxVM 3.5 that does not have the PHCO_30834
patch, some VxVM disks may have its public region extend beyond the end of the physical
disk.
Workaround
Before upgrading a system that is running under VxVM 3.5 at a patch level prior to Command
Cumulative Patch 06 (PHCO_30834), it is strongly recommended that you download and
apply this patch, and then run the ckpublen.sh utility script as documented in TechNote
270407, available at: http:// support.veritas.com/docs/270407. If the script reports that
any disks need to be re-initialized, back up the file systems and data residing on the volumes
on those disks, and restore them after re-initializing the disks and recreating the volumes. You
can then proceed to upgrade the system with the Veritas Volume Manager 5.0 software.
• Problem
Failure to remove obsolete Array Support Libraries.
Workaround
VxVM 5.0 will attempt to detect and obsolete any pre-5.0 array support library (ASL) packages.
Once the upgrade is complete, you should not see the obsolete ASL packages in the swlist
output. If the upgrade fails, enter the following command to remove obsolete ASL packages:
#swremove <ASL-package-name>
• Problem
After updating to VxVM 5.0, and rebooting the system, sometimes a core file called /core
is found.
Workaround
You can ignore this core file as it does not impact system operations. To prevent the core file,
install the updated FibrChanl-00 B.11.31.0712 product from the December 2007 Application
Release media.
Known Problems And Workarounds 21