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.
•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.
•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
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
VxVM 5.1 SP1 on HP–UX 11i v3
For more information on features that VxVM 5.1 SP1 supports on
Architecture of VxVM
VxVM operates as a subsystem between the
•Physical access to disks
•Device handles
•VM disks
•Multipathing