ServerNet Cluster 6780 Operations Guide (G06.24+, H06.03+)

Troubleshooting and Replacement Procedures
ServerNet Cluster 6780 Operations Guide—525606-002
3-15
Troubleshooting SANMAN
1. Verify that MSGMON is started. At an SCF prompt, type:
-> STATUS PROCESS $ZZKRN.#MSGMON
2. If $ZZKRN.#MSGMON is not configured, refer to the ServerNet Cluster 6780
Planning and Installation Guide for information about configuring it.
3. If $ZZKRN.#MSGMON is configured but not started, you can start it by typing this
command at an SCF prompt. This command starts 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.
Troubleshooting SANMAN
SANMAN must be in the STARTED state on a system in order for the system to join a
ServerNet cluster. $ZZKRN.#ZZSMN is a persistent process that should be configured
to be started at all times.
Use these steps to troubleshoot SANMAN:
1. Verify that SANMAN is started. Either:
•
Using the OSM Service Connection, click the ServerNet Cluster resource to
select it, and check the SANMAN Process Pair attributes. See Figure 3-5 on
page 3-14.
•
At an SCF prompt, type:
-> STATUS PROCESS $ZZKRN.#ZZSMN
2. If $ZZKRN.#ZZSMN is not configured, refer to the ServerNet Cluster 6780
Planning and Installation Guide 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.#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.
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
.