Home > Veritas Storage Foundation™ Volume Manager Manual Pages
VXDCTL (1M) |
Maintenance Commands |
vxdctl debug level [pathname]
vxdctl defaultdg diskgroup
vxdctl disable
vxdctl [-f] enable
vxdctl hostid hostid
vxdctl init [hostid]
vxdctl initdmp
vxdctl license [init]
vxdctl list
vxdctl [-c] mode
vxdctl protocolrange
vxdctl protocolversion
vxdctl [-f] set attribute[=value]
vxdctl [-k] stop
vxdctl support
vxdctl [-F] unset attribute
vxdctl upgrade
The volboot file forms a key element in managing the state of vxconfigd and importing the boot disk group. This file contains a host ID that VxVM uses to establish ownership of physical disks. The host ID is used to ensure that two or more hosts do not interfere with each other when accessing disks on a shared SCSI bus or Storage Area Network (SAN). VxVM also uses host IDs to generate unique ID strings for stamping disks and disk groups.
The volboot file contains the name of the system-wide default disk group if this has been configured. If the root disk is under VxVM control, the volboot file also contains the name of disk group, the boot disk group, to which the root disk belongs.
Note: The purpose of the cluster environment is to allow hosts that can access disks on a shared bus to do so in a coordinated way. In this environment, the host ID is not used to prevent shared access; however, it is used for other internal functions.
vxconfigd operates in one of the following modes: enabled, disabled or booted.
The enabled state is the normal operating state. Most configuration operations are allowed in this state. Entering the enabled state imports all disk groups, and begins the management of device nodes stored in the /dev/vx/dsk and /dev/vx/rdsk directories.
In the disabled state, vxconfigd does not retain configuration information for the imported disk groups, and does not maintain the volume device directories. Most operations are disallowed in this state. Certain failures, such as the volboot file not being loaded or devices not being auto-configured, cause vxconfigd to enter the disabled state automatically.
The booted state is entered as part of normal system startup, prior to checking the root file system with fsck. If the root disk is under VxVM control, entering the booted mode imports the boot disk group. If the root disk is not under VxVM control, no disk groups are imported. vxconfigd then waits for a request to enter the enabled mode. The volume device node directories are not maintained in booted mode, because it may not be possible to write to the root file system.
The action performed by vxdctl depends upon the specified keyword operand(s).
If bootdg is specified as the argument to this command, the default disk group is set to be the same as the currently defined system-wide boot disk group. You can use the command vxdg bootdg to display the currently defined boot disk group.
If nodg is specified as the argument, the default disk group is undefined.
Note: The specified disk group need not currently exist on the system.
By default, VxVM performs a full scan of the device tree when performing device discovery. To discover only newly added disks that are not already known to VxVM, specify the -f option.
If some disks are inaccessible at the time of a hostid operation, it may be necessary to use the vxdisk clearimport operation to clear out the old host ID on those disks when they become reaccessible. Otherwise, you may not be able to re-add those disks to their disk groups.
Note: Be careful when using this command. If the system crashes before the hostid operation completes, some disk groups may not reimport automatically.
If a hostid operand is specified, this string is used; otherwise, a default host ID is used. The default host ID is normally taken as the network node name for the host (see uname(1M)). On systems with a hardware-defined system ID, the default host ID might be derived from this hardware ID.
Note: If only a Base VxVM license is installed, the vxdctl license command displays "DMP (single path enabled)". If either the Full VxVM license or an automatically generated license (such as that for the PHOTON array) is installed, the command displays "DMP (multipath enabled)".
With the init argument specified, the vxdctl license init command requests that vxconfigd re-read any persistently stored license information. If licenses have expired, this can make some features unavailable. If new licenses were added, but are not yet recognized by vxconfigd, this command forces vxconfigd to rescan the licenses, and to make the new licenses available.
mode: operating_mode
where operating_mode is one of enabled, disabled, booted, or not-running.
If the -c flag is specified and vxconfigd is in the enabled mode, the clustered state of vxconfigd is displayed. The output format is:
mode: enabled: clustered_state
where clustered_state is one of cluster inactive, cluster active - role not set, cluster active - MASTER, cluster active - SLAVE. This information is only available if the VxVM cluster feature is enabled.
minprotoversion:minimum protocol version, \maxprotoversion:maximum protocol version
cluster running at protocolprotocolversion
The protocolversion is a value in the range listed by vxdctl protocolrange. This information is only available if the VxVM cluster feature is enabled.
If a site name is already defined for any imported disk groups, the operation fails unless the -f option is specified.
- \f(CWvxconfigd_vrsn
- Version of vxconfigd that is currently running.
- \f(CWdg_minimum
- Lowest disk group version supported by vxconfigd.
- \f(CWdg_maximum
- Highest disk group version supported by vxconfigd.
- \f(CWkernel
- Highest kernel version supported by vxconfigd.
- \f(CWprotocol_minimum
- Lowest cluster protocol version supported by the node.
- \f(CWprotocol_maximum
- Highest cluster protocol version supported by the node.
- \f(CWprotocol_current
- Cluster protocol version currently running on the node.
The protocol version information is only meaningful for the VxVM cluster feature.
Last updated: 17 Jul 2008
Copyright ©2009 Symantec Corporation
All rights reserved.