VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes
Patches and Fixes in This Version
Chapter 128
Installation Issues
Removal of HPvxvm Product after Installing VxVM 3.5 Products
Causes License Files to be Removed
• Problem: The HPvxvm postremove script removes directories in
/etc/vx, apart those named /etc/vx/elm, /etc/vx/type or /etc/vx/emc.d.
Thus VxVM 3.5 products installed on the system lose their licensing
files since they get installed in /etc/vx/licenses. Also, files created
with the VRTSvlic product also get removed.
• Workaround: Reinstall the VRTSvlic product if it had been installed.
Remember to use the "-x reinstall=true" flag for the swinstall. For
product specific licenses, simply reapply the licenses using the
vxlicinst(1) command.
(See also Technote at
http://seer.support.veritas.com/docs/244257.htm.)
Machine Apparently Hangs After Installing AR1201 If you have a
machine that has AR0902 installed with VxVM root, and then you
attempt to install 11i AR1201 to a different disk; then rebooting the
machine after the AR1201 installation will initiate a question that will
wait for user input.
• Problem: If you are installing from an Ignite_UX server, you will not
see the question and it will appear that the machine is hung.
The question should appear after the following message on the
console:
* Bringing up Network (lan0)
* NFS mounting clients directory.
The question that is being asked is:
This appears to be a VxVM boot disk device.
Overwriting it will destroy the current LIF directory
Should the current LIF directory be destroyed [y/n]?
• Type “n” after the console message, if you suspect that the system is
waiting for an answer.