OpenVMS Cluster Systems - OpenVMS Systems - HP

Cluster Troubleshooting
C.1 Diagnosing Computer Failures
C–2 Cluster Troubleshooting
The normal sequence of events is shown in Table C–1.
Table C–1 Sequence of Booting Events
Step Action
1 The computer boots. If the computer is a satellite, a message like the following shows
the name and LAN address of the MOP server that has downline loaded the satellite.
At this point, the satellite has completed communication with the MOP server and
further communication continues with the system disk server, using OpenVMS Cluster
communications.
%VAXcluster-I-SYSLOAD, system loaded from Node X...
For any booting computer, the OpenVMS ‘‘banner message’’ is displayed in the following
format:
operating-system Version n.n dd-mmm-yyyy hh:mm.ss
2 The computer attempts to form or join the cluster, and the following message appears:
waiting to form or join an OpenVMS Cluster system
If the computer is a member of an OpenVMS Cluster based on the LAN, the cluster security
database (containing the cluster password and group number) is loaded. Optionally, the
MSCP server and TMSCP server can be loaded:
%VAXcluster-I-LOADSECDB, loading the cluster security database
%MSCPLOAD-I-LOADMSCP, loading the MSCP disk server
%TMSCPLOAD-I-LOADTMSCP, loading the TMSCP tape server
3 If the computer discovers a cluster, the computer attempts to join it. If a cluster is found, the
connection manager displays one or more messages in the following format:
%CNXMAN, Sending VAXcluster membership request to system X...
Otherwise, the connection manager forms the cluster when it has enough votes to establish
quorum (that is, when enough voting computers have booted).
4 As the booting computer joins the cluster, the connection manager displays a message in the
following format:
%CNXMAN, now a VAXcluster member -- system X...
Note that if quorum is lost while the computer is booting, or if a computer is unable to join
the cluster within 2 minutes of booting, the connection manager displays messages like the
following:
%CNXMAN, Discovered system X...
%CNXMAN, Deleting CSB for system X...
%CNXMAN, Established "connection" to quorum disk
%CNXMAN, Have connection to system X...
%CNXMAN, Have "connection" to quorum disk
The last two messages show any connections that have already been formed.
(continued on next page)