ServerNet Cluster Manual

Installing and Configuring a ServerNet Cluster
ServerNet Cluster Manual—520575-003
3-7
Task 6: Add MSGMON, SANMAN, and SNETMON
to the System-Configuration Database
Task 6: Add MSGMON, SANMAN, and SNETMON to the System-
Configuration Database
Unless the system is new, you must add MSGMON, SANMAN, and SNETMON as
generic processes to the system-configuration database. (These processes are
preconfigured on new systems.) You must configure these processes to start
automatically at system load and be persistent (that is, restart automatically if stopped
abnormally).
1. Log on to the local system using the super ID (255, 255). (You must be logged on
using the super ID when you add MSGMON, SANMAN, and SNETMON to the
system-configuration database.)
2. Check to see if MSGMON, SANMAN, and SNETMON have already been added to
the system-configuration database. Use the Kernel subsystem SCF INFO
PROCESS command to display a list of the generic processes:
-> INFO PROCESS $ZZKRN.*
Under the *Name column of the display, look for the following:
•
$ZIMnn (MSGMON)
•
$ZZSMN (SANMAN)
•
$ZZSCL (SNETMON)
3. Gather more information about MSGMON, SANMAN, and SNETMON by using the
SCF INFO PROCESS command. For example:
-> INFO PROCESS $ZZKRN.#MSGMON, DETAIL
-> INFO PROCESS $ZZKRN.#ZZSMN, DETAIL
-> INFO PROCESS $ZZKRN.#ZZSCL, DETAIL
You can verify that MSGMON, SANMAN, and SNETMON are configured correctly
by comparing the configured modifiers with the recommended modifiers shown in
Adding MSGMON, SANMAN, and SNETMON Using SCF Commands on page 3-9.
If MSGMON, SANMAN, and
SNETMON are . . . Then
Present Go to the next step.
Not present Configure them. (See Configuring
MSGMON, SANMAN, and SNETMON on
page 3-8.)
Note. MSGMON, ZZSMN, and ZZSCL are the recommended symbolic names for these
processes. They are also the names used as examples in this manual. However, these
processes can be configured using other symbolic names.