VxVM:xxxx: ERROR: IPC Failure: Configuration daemon is not accessible

After the installation of Storage Foundation or Volume Manager  (VxVM) an error similar to the following is encountered:

vxvm:xxxx: ERROR: IPC Failure: Configuration daemon is not accessible

For example:
 

VxVM vxdmpadm ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible
 

This may be due to an error during the installation process or the installer may not have completed the installation as expected. An error in the installation logs may not be reported.

.

The " install-db" file prevents the vxconfigd daemon from starting on system boot.
Verify if the file " install-db" is present.

# ls /etc/vx/reconfig.d/state.d/install-db

If the file is present, remove the install-db file using the following command:

# rm /etc/vx/reconfig.d/state.d/install-db

Restart the Volume Manager configuration daemon, setting the boot and enable modes for startup of vxconfigd after reboot:

# vxconfigd -k -m boot
# vxconfigd -k -m enable

When attempting to start vxconfigd, if the following error is encountered:

VxVM vxconfigd ERROR V-5-1-1589 enable failed: Volboot file not loaded
       transactions are disabled.

The ' /etc/vx/volboot' file is missing or was not created during the installation process.
Create the volboot file manually and restart vxconfigd with the following commands:

# vxdctl init <hostname>
# vxconfigd -k

Verify proper operation of VxVM by issuing the command 'vxdisk list'. If output is created upon the above command execution, VxVM is operating correctly. Additionally, best practice would be to restart the host and then verify VxVM starts after the system is rebooted.