ServerNet Cluster Manual

Troubleshooting and Replacement Procedures
ServerNet Cluster Manual—520575-003
7-17
Troubleshooting SNETMON
•
SRAM Memory Test Failure
•
Too Many ServerNet Switch Automatic Resets Because of Backpressure
•
Upper Boot Block Section of FLASH Locked
•
UPS Failure
•
UPS Not Responding
•
X Fabric Not Connected to the Same ServerNet Switch Port as Y Fabric
Troubleshooting SNETMON
For general information about SNETMON, refer to Section 1, ServerNet Cluster
Description. The SNETMON process ($ZZKRN.#ZZSCL) and the ServerNet cluster
subsystem ($ZZSCL) must be in the STARTED state on a system in order for the
system to join a ServerNet cluster. $ZZKRN.#ZZSCL is a persistent process that
should be configured to be started at all times.
Use the following steps to troubleshoot SNETMON:
1. Verify that SNETMON and the ServerNet cluster subsystem are started. Do one of
the following:
•
Using the TSM Service Application, click the ServerNet Cluster resource in the
tree pane to select it. In the attributes pane, check the SNETMON Process
State and ServerNet Cluster State attributes. See Figure 7-6.
•
At an SCF prompt:
-> STATUS PROCESS $ZZKRN.#ZZSCL
-> STATUS SUBSYS $ZZSCL
Note. If SNETMON ($ZZKRN.#ZZSCL) does not appear to be available, it might be
configured using a different symbolic name. Use the SCF INFO PROCESS $ZZKRN.*
command to display a list of all currently configured generic processes.