ServerNet Cluster Manual

Troubleshooting and Replacement Procedures
ServerNet Cluster Manual—520575-003
7-19
Troubleshooting MSGMON
4. If you continue to have problems, contact your service provider.
Troubleshooting MSGMON
For general information about MSGMON, refer to Section 1, ServerNet Cluster
Description. A MSGMON process must be running in every processor of a system.
$ZZKRN.#MSGMON is a persistent process that should be configured to be started at
all times. Use the following steps to troubleshoot MSGMON:
1. Verify that MSGMON is started. At an SCF prompt type:
-> STATUS PROCESS $ZZKRN.#MSGMON
2. If $ZZKRN.#MSGMON is not configured, refer to Section 3, Installing and
Configuring a ServerNet Cluster, for information about configuring it.
3. If $ZZKRN.#MSGMON is configured but not started, you can start it by typing the
following at an SCF prompt. This command will start a copy of MSGMON on every
available processor on the system:
-> START PROCESS $ZZKRN.#MSGMON
4. If you continue to have problems, contact your service provider.
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.
Note. If $ZZKRN.#MSGMON 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.