VXVM 6.1 – How to Interpret veritas Configuration Daemon (vxconfigd) States from vxdctl output?

vxvm-how-toThe vxdctl utility manages aspects of the state of the volume configuration daemon, vxconfigd, sets the default disk group for the system, and also sets up the boot disk group if the root disk is under Veritas Volume Manager (VxVM) control.
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.
Ramdev

Ramdev

I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

1 Response

  1. September 18, 2015

    […] Read – How to Interpret veritas Configuration Daemon (vxconfigd) States from vxdctl output? […]

What is in your mind, about this post ? Leave a Reply

Close
  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us