Troubleshooting VCS Startup

This section includes error messages associated with starting VCS (shown in bold text), and provides descriptions of each error and the recommended action.

  "VCS:10622 local configuration missing"

  "VCS:10623 local configuration invalid"

  "VCS:10624 local configuration stale"

The local configuration is invalid.

Recommended Action: Start the VCS engine, HAD, on another system that has a valid configuration file. The system with the configuration error "pulls" the valid configuration from the other system.

Another method is to correct the configuration file on the local system and force VCS to reread the configuration file. If the file appears valid, verify that is not an earlier version. It is possible that VCS marked the configuration stale by creating a .stale file because the last VCS shutdown was not graceful. The .stale file is created in the directory /etc/VRTSvcs/conf/config.

Type the following commands to verify the configuration and force VCS to reread the configuration file:

  "VCS:11032 registration failed. Exiting"

GAB was not registered or has become unregistered.

Recommended Action: GAB is registered by the gabconfig command in the file /etc/gabtab. Verify that the file exists and that it contains the command
gabconfig -c.

GAB can become unregistered if LLT is set up incorrectly. Verify that the file is correct in /etc/llttab. If the LLT configuration is incorrect, make the appropriate changes and reboot.

  "Waiting for cluster membership."

This indicates that GAB may not be seeded. If this is the case, the command gabconfig -a does not show any members, and the following messages may appear on the console or in the event log.