ServerNet Cluster Manual

Installing and Configuring a ServerNet Cluster
ServerNet Cluster Manual—520575-003
3-11
Task 7: Verify That $ZEXP and $NCP Are Started
Starting MSGMON, SANMAN, and SNETMON
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.*
Task 7: Verify That $ZEXP and $NCP Are Started
Subsequent tasks configure Expand line-handler processes that enable nodes to
communicate with each other using the ServerNet protocol. For these processes to be
configured, the Expand manager process ($ZEXP) and the network-control process
($NCP) must be started.
1. At a TACL prompt, use the STATUS command to verify that $ZEXP and $NCP are
started:
> STATUS $ZEXP
> STATUS $NCP
2. If $ZEXP or $NCP are not started or not present, refer to the Expand Configuration
and Management Manual for information about configuring and starting these
processes before continuing.
3. Verify that the $NCP ALGORITHM modifier on the system you are adding is set to
the value used by all other nodes in the cluster. Note that this modifier must be set
to the same value not only for all nodes in the cluster, but also for all nodes in other
networks that use Expand to communicate with the cluster. You can use the SCF
INFO PROCESS command to check the modifier value:
-> SCF INFO PROCESS $NCP, DETAIL
For more information, refer to the Expand Configuration and Management Manual.
Note. After typing the START PROCESS $ZZKRN.#MSGMON command, it is normal to
receive error messages indicating that one or more processors did not start due to CPU
down. The command attempts to start a MSGMON process in 16 processors but cannot
start the process if some processors are not present in your system.
Note. You do not need to start the subsystem object for the ServerNet cluster monitor
process yet. The subsystem cannot be started until the ServerNet cables are attached
from the node to the cluster switch. The guided procedure for configuring a ServerNet
node instructs you when to connect the cables and also brings the subsystem to the
STARTED state if it is not already started.