OpenVMS Cluster Systems - OpenVMS Systems - HP

Cluster Troubleshooting
C.4 Computer Fails to Join the Cluster
Step Action
3 If you find it necessary to modify the computer’s bootstrap command procedure (console
media), you may be able to do so on another processor that is already running in the
cluster.
Replace the running processor’s console media with the media to be modified, and use the
Exchange utility and a text editor to make the required changes. Consult the appropriate
processor-specific installation and operations guide for information about examining and
editing boot command files.
C.4.3 Verifying SCSNODE and SCSSYSTEMID Parameters
To be eligible to join a cluster, a computer must have unique SCSNODE and
SCSSYSTEMID parameter values.
Step Action
1 Check that the current values do not duplicate any values set for existing OpenVMS Cluster
computers. To check values, you can perform a conversational bootstrap operation.
2 If the values of SCSNODE or SCSSYSTEMID are not unique, do either of the following:
• Alter both values.
• Reboot all other computers.
Note: To modify values, you can perform a conversational bootstrap operation. However, for
reliable future bootstrap operations, specify appropriate values for these parameters in the
computer’s MODPARAMS.DAT file.
WHEN you change... THEN...
The SCSNODE parameter Change the DECnet node name too, because both names
must be the same.
Either the SCSNODE parameter
or the SCSSYSTEMID
parameter on a node that was
previously an OpenVMS Cluster
member
Change the DECnet node number, too, because both
numbers must be the same. Reboot the entire cluster.
C.4.4 Verifying Cluster Security Information
To verify the cluster group code and password, follow these instructions:
Step Action
1 Verify that the database file SYS$COMMON:CLUSTER_AUTHORIZE.DAT exists.
2 For clusters with multiple system disks, ensure that the correct (same) group number and
password were specified for each.
Reference: See Section 10.9 to view the group number and to reset the password in the
CLUSTER_AUTHORIZE.DAT file using the SYSMAN utility.
C.5 Startup Procedures Fail to Complete
C–14 Cluster Troubleshooting
If a computer boots and joins the cluster but appears to hang before startup
procedures complete—that is, before you are able to log in to the system—be sure
that you have allowed sufficient time for the startup procedures to execute.