HP-UX vPars and Integrity VM V6.3 Administrator Guide

cluster is reconfigured, or the VSP system is rebooted. You must ensure that all SLVM volume groups
are activated after a VSP reboot or Serviceguard cluster reconfiguration.
14.4 Matrix OE troubleshooting
This section lists some common CLI commands that helps when troubleshooting the issues when
using vPars and Integrity VM with Matrix OE.
14.4.1 Adding and removing devices
Most of the VSP devices get added into vPars and Integrity VM device database automatically.
You can add devices that are not automatically added by using the hpvmdevmgmt gdev
PRESERVE attribute. The following device types require manual addition:
• File backed disks
• File backed DVDs
• VxVM volumes
The following examples show how to add various device types to the storage pool:
• File:
# hpvmdevmgmt -a gdev:/var/opt/hpmv/ISO-images/hpux/112350GOLD.ISO:attr:PRESERVE=YES
• VxVM volume:
# hpvmdevmgmt -a gdev:/dev/vx/rdisk/guestdg/vxvm_g2:attr:PRESERVE=YES
To remove a device from the storage pool, run the following command:
# hpvmdevmgmt -d gdev:/dev/rdisk/disk23
NOTE: Adding devices to the storage pool does not prevent them from being used by the HP-UX
operating system or other Integrity VM commands.
The storage pool does not fully support lunpaths or directories. In addition, Virtual Machine
Management (VMM), a layer between Integrity VM and LSM, has no way to insert or eject a DVD,
because this is done from the virtual console.
14.4.2 Registering and unregistering a VM
The following vPars and Integrity VM properties are set when a guest is registered in Matrix OE.
• runnable_status=enabled
• modify_status=enabled
• visible_status=enabled
HP Matrix OE ensures that a VM is registered (and, therefore, runnable) on only one VSP at a
time.
When a VM is unregistered in Matrix OE, the following attributes are set:
• runnable_status=disabled
• modify_status=disabled
• visible_status=disabled
When Matrix OE queries the register_status, the value of visible_status is returned. If
the VM is not visible, you cannot visualize it with the graphical tools, and therefore; you cannot
modify it or run it.
You can set the register_status, modify_status, visible_status and
runnable_status of a VM to enabled or disabled with the hpvmmodify –P vmname -x
command. The following are the examples:
258 Managing vPars and VMs using GUI