VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Cluster Error Messages
74 VERITAS Volume Manager Troubleshooting Guide
Error in cluster processing
◆ Description: This may be due to an operation inconsistent with the current state of a
cluster (such as an attempt to import or deport a shared disk group to or from the
slave). It may also be caused by an unexpected sequence of commands from
vxclust.
◆ Action: Make sure that the operation can be performed in the current environment.
ERROR: upgrade operation failed: Already at highest version
◆ Description: An upgrade operation has failed because a cluster is already running at
the highest protocol version supported by the master.
◆ Action: No further action is possible as the master is already running at the highest
protocol version it can support.
Incorrect protocol version number in volboot file
◆ Description: A node attempted to join a cluster where VxVM software was incorrectly
upgraded or the volboot file is corrupted.
◆ Action: Verify the supported cluster protocol versions using vxdctl protocol version,
and reinstall VxVM if necessary.
Incorrect protocol version (number) in volboot file
◆ Description: The volboot file contains an incorrect protocol version. It has been
corrupted, possibly by being edited manually. The volboot file should contain a
supported protocol version before trying to bring the node into the cluster.
◆ Action: Run vxdctl init. This writes a valid protocol version to the volboot file.
Restart vxconfigd and retry the join.
Insufficient DRL log size: logging is disabled.
◆ Description: A volume with an insufficient DRL log size was started successfully, but
DRL logging is disabled and a full recovery is performed.
◆ Action: Create a new DRL of sufficient size.
Join in progress
◆ Description: An attempt was made to import or deport a shared disk group during a
cluster reconfiguration.
◆ Action: Retry when the cluster reconfiguration has completed.