ServerNet Cluster Manual
Troubleshooting and Replacement Procedures
ServerNet Cluster Manual—520575-003
7-20
Troubleshooting SANMAN
Troubleshooting SANMAN
For general information about SANMAN, refer to Section 1, ServerNet Cluster
Description. $ZZKRN.#ZZSMN is a persistent process that should be configured to be
started at all times. SANMAN must be in the STARTED state on a system in order for
the system to join a ServerNet cluster.
Use the following steps to troubleshoot SANMAN:
1. Verify that SANMAN is started. Do one of the following:
•
Using the TSM Service Application, click the ServerNet Cluster resource to
select it, and check the SANMAN Process State attribute. See Figure 7-6 on
page 7-18.
•
At an SCF prompt type:
-> STATUS PROCESS $ZZKRN.#ZZSMN
2. If $ZZKRN.#ZZSMN is not configured, refer to Section 3, Installing and Configuring
a ServerNet Cluster, for information about configuring it.
3. If $ZZKRN.#ZZSMN is configured but not started, use SCF to start it:
-> START PROCESS $ZZKRN.#ZZSMN
4. If you continue to have problems, contact your service provider.
Note. If $ZZKRN.#ZZSMN 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.
Note. Systems using the Tetra 8 topology must have a version of SP firmware that supports
clustering to participate in a ServerNet Cluster. Otherwise the ServerNet cluster processes
$ZZKRN.#ZZSCL (SNETMON) and $ZZKRN.#ZZSMN (SANMAN) will abend repeatedly when
a system load is performed with G06.09 or later. Installing a version of the SP firmware that
supports clustering after the cold load and subsequently trying to start $ZZSCL and $ZZSMN
does not correct the problem.
To correct the problem, you must install a version of SP firmware that supports clustering and
then perform a system load. To determine which version of SP firmware you need, see
Checking SPR Levels
on page 2-24.
This problem does not affect systems that use the Tetra16 topology.