BladeCluster Solution Manual

Start MSGMON, SANMAN, and SNETMON
CAUTION: You should neither configure nor start the $ZZSMN (SANMAN) process unless the
BladeCluster will be connected to a 6700 series ServerNet cluster. The SANMAN process supports
6770 or 6780 ServerNet cluster switches and is not useful unless these switches are present.
NOTE: When $ZZKRN.#MSGMON is started, it is normal to receive error messages indicating
that one or more processes did not start due to CPU down. The command attempts to start a
MSGMON process in 16 processors but cannot start the process for the processors that are not
present in the node.
You cannot start the ServerNet cluster subsystem until the fiber-optic cables are attached from the
node to the Advanced Cluster Hub. The OSM Add Node to ServerNet Cluster guided procedure
instructs you when to connect the cables and also brings the ServerNet cluster subsystem to the
STARTED state if it is not already started.
1. Use the SCF START PROCESS command to start MSGMON, SANMAN, and SNETMON:
START PROCESS $ZZKRN.#MSGMON
START PROCESS $ZZKRN.#ZZSMN
START PROCESS $ZZKRN.#ZZSCL
2. Use the SCF STATUS PROCESS command to verify that MSGMON ($ZIMnn), SANMAN
($ZZSMN), and SNETMON ($ZZSCL) are started:
STATUS PROCESS $ZZKRN.*
90 Configuring MSGMON, SANMAN, and SNETMON