About using the postcheck option

Last published : Sep 28, 2026
You can use the installer's post-check to determine installation-related problems and to aid in troubleshooting.
Note: This command option requires downtime for the node.
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 (if LLT is not running at the check time).
  • The VRTSllt pkg version is not consistent on the nodes.
  • The llt-linkinstall value is incorrect.
  • The /etc/llthosts and /etc/llttab 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.
You can use the installer's post-check option to perform the following checks:
General checks for all products:
  • All the required packages are installed.
  • The versions of the required packages are correct.
  • There are no verification issues for the required packages.
Checks for Volume Manager (VM):
  • Lists the daemons which are not running (vxattachd, vxconfigbackupd, vxesd, vxrelocd ...).
  • Lists the disks which are not in 'online' or 'online shared' state (vxdisk list).
  • Lists the diskgroups which are not in 'enabled' state (vxdg list).
  • Lists the volumes which are not in 'enabled' state (vxprint -g <dgname>).
  • Lists the volumes which are in 'Unstartable' state (vxinfo -g <dgname>).
  • Lists the volumes which are not configured in /etc/vfstab.
Checks for File System (FS):
  • Lists the VxFS kernel modules which are not loaded (vxfs/fdd/vxportal.).
  • Whether all VxFS file systems present in /etc/vfstab file are mounted.
  • Whether all VxFS file systems present in /etc/vfstab are in disk layout 12 or higher.
  • Whether all mounted VxFS file systems are in disk layout 12 or higher.
Checks for Cluster File System:
  • Whether FS and ODM are running at the latest protocol level.
  • Whether all mounted CFS file systems are managed by VCS.
  • Whether cvm service group is online.
Related information