When you use the postcheck option, it can help you troubleshoot the following VCS-related issues:

• The heartbeat link does not exist.

• The heartbeat link cannot communicate.

• The heartbeat link is a part of a bonded or aggregated NIC.

• A duplicated cluster ID exists.

• The VRTSllt pkg version is not consistent on the nodes.

• The llt-linkinstall value is incorrect.

• The llthosts(4) or llttab(4) configuration is incorrect.

• the /etc/gabtab file is incorrect.

• The incorrect GAB linkinstall value exists.

• The VRTSgab pkg version is not consistent on the nodes.

• The main.cf file or the types.cf file is invalid.

• The /etc/VRTSvcs/conf/sysname file is not consistent with the hostname.

• The cluster UUID does not exist.

• The uuidconfig.pl file is missing.

• The VRTSvcs pkg version is not consistent on the nodes.

• The /etc/vxfenmode file is missing or incorrect.

• The /etc/vxfendg file is invalid.

• The vxfen link-install value is incorrect.

• The VRTSvxfen pkg version is not consistent.

The postcheck option can help you troubleshoot the following SFHA or SFCFSHA issues:

• Volume Manager cannot start because the /etc/vx/reconfig.d/state.d/install-db file has not been removed.

• Volume Manager cannot start because the Volboot file is not loaded.

• Volume Manager cannot start because no license exists.

• Cluster Volume Manager cannot start because the CVM configuration is incorrect in the main.cf file. For example, the Autostartlist value is missing on the nodes.

• Cluster Volume Manager cannot come online because the node ID in the /etc/llthosts file is not consistent.

• Cluster Volume Manager cannot come online because Vxfen is not started.

• Cluster Volume Manager cannot start because gab is not configured.

• Cluster Volume Manager cannot come online because of a CVM protocol mismatch.

• Cluster Volume Manager group name has changed from "cvm", which causes CVM to go offline.