Veritas Volume Manager 5.1 SP1 Release Notes HP-UX 11i v3 (5900-1518, August 2011)

Example 2 Sample device names on a system using the Legacy Device Naming Scheme
DEVICE TYPE DISK GROUP STATUS
c0t6d0 auto:hpdisk rootdisk01 rootdg online
c3t6d0 auto:LVM - - LVM
c4t0d0 auto:cdsdisk c4t0d0 dg1 online
c4t3d0 auto:LVM - - LVM
c4t9d0 auto:LVM - - LVM
To change the default naming scheme to the Agile Device Naming Scheme, use the
following command:
# vxddladm set namingscheme=osn mode=new
The following example shows some sample device names on a system using the Agile
Device Naming Scheme:
Example 3 Sample device names on a system using the Agile Device Naming Scheme
DEVICE TYPE DISK GROUP STATUS
disk6 auto:hpdisk rootdisk01 rootdg online
disk7 auto:LVM - - LVM
disk11 auto:cdsdisk c4t0d0 dg1 online
disk10 auto:LVM - - LVM
disk9 auto:LVM - - LVM
Only in cases where customers upgrade from an earlier version to this version, Operating
System Native Naming Scheme(osn) or the setting from the earlier release will override
ebn. So, customers will continue to see the osn naming scheme.
New features included in CVM 5.1 SP1
• Issuing CVM commands from the slave node
In releases prior to VxVM 5.1 SP1, CVM required that you issue configuration commands for
shared disk groups from the master node of the cluster. Configuration commands change the
object configuration of a CVM shared disk group. Examples of configuration changes include
creating disk groups, importing disk groups, deporting disk groups, and creating volumes.
Starting with the VxVM 5.1 SP1 release, you can issue commands from any node, even when
the command changes the configuration of the shared disk group. You do not need to know
which node is the master to issue the command. If you issue the command on the slave node,
CVM ships the commands from the slave node to the master node. It then executes the command
on the master node. CVM does not support executing all commands on the slave node.
• Changing the CVM master online
CVM now supports changing the CVM master from one node in the cluster to another node,
while the cluster is online. CVM migrates the master node, and re-configures the cluster. HP
recommends that you switch the master when the cluster is not handling VxVM configuration
changes or cluster re-configuration operations. In most cases, CVM aborts the operation to
change the master, if CVM detects that any configuration changes are occurring in the VxVM
or the cluster. After the master change operation starts re-configuring the cluster, other
commands that require configuration changes will fail.
For more information on changing the CVM master while the cluster is online, refer to the
Veritas Volume Manager 5.1 SP1 Administrator's Guide. To locate this document, go to the
6 Veritas Volume Manager 5.1 SP1 Release Notes