OpenVMS Cluster Systems - OpenVMS Systems - HP

Table C–1 (Cont.) Sequence of Booting Events
Step Action
Cluster Troubleshooting
C.1 Diagnosing Computer Failures
5 If the cluster includes a quorum disk, you may also see messages like the following:
%CNXMAN, Using remote access method for quorum disk
%CNXMAN, Using local access method for quorum disk
The first message indicates that the connection manager is unable to access the quorum disk
directly, either because the disk is unavailable or because it is accessed through the MSCP
server. Another computer in the cluster that can access the disk directly must verify that a
reliable connection to the disk exists.
The second message indicates that the connection manager can access the quorum disk
directly and can supply information about the status of the disk to computers that cannot
access the disk directly.
Note: The connection manager may not see the quorum disk initially because the disk may
not yet be configured. In that case, the connection manager first uses remote access, then
switches to local access.
6 Once the computer has joined the cluster, normal startup procedures execute. One of the first
functions is to start the OPCOM process:
%%%%%%%%%%% OPCOM 15-JAN-1994 16:33:55.33 %%%%%%%%%%%
Logfile has been initialized by operator _X...$OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;17
%%%%%%%%%%% OPCOM 15-JAN-1994 16:33:56.43 %%%%%%%%%%%
16:32:32.93 Node X... (csid 0002000E) is now a VAXcluster member
7 As other computers join the cluster, OPCOM displays messages like the following:
%%%%% OPCOM 15-JAN-1994 16:34:25.23 %%%%% (from node X...)
16:34:24.42 Node X... (csid 000100F3)
received VAXcluster membership request from node X...
As startup procedures continue, various messages report startup events.
Hint: For troubleshooting purposes, you can include in your site-specific startup
procedures messages announcing each phase of the startup process—for example,
mounting disks or starting queues.
C.2 Computer on the CI Fails to Boot
If a CI computer fails to boot, perform the following checks:
Step Action
1 Verify that the computer’s SCSNODE and SCSSYSTEMID parameters are unique in the
cluster. If they are not, you must either alter both values or reboot all other computers.
2 Verify that you are using the correct bootstrap command file. This file must specify the
internal bus computer number (if applicable), the HSC or HSJ node number, and the
disk from which the computer is to boot. Refer to your processor-specific installation
and operations guide for information about setting values in default bootstrap command
procedures.
3 Verify that the PAMAXPORT system parameter is set to a value greater than or equal to
the largest CI port number.
4 Verify that the CI port has a unique hardware station address.
5 Verify that the HSC subsystem is on line. The ONLINE switch on the HSC operator
control panel should be pressed in.
6 Verify that the disk is available. The correct port switches on the disk’s operator control
panel should be pressed in.
Cluster Troubleshooting C–3