BladeCluster Solution Manual

Checking That Automatic Line-Handler Generation is Enabled
Use one of these methods to determine if the automatic line-handler generation is enabled in the
nodes:
• Check for the presence of $ZZKRN.#OSM-CONFLH-RD. If it is present, the automatic
line-handler configuration is enabled.
• Check the status of the routing distributor ($ZOLHD). If this process is running (but in a STOPPED
state), automatic line-handler configuration is enabled. Although the routing distributor is
running, the #OSM-CONFLH-RD process remains in a STOPPED state until a node is added
to the cluster.
Checking 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.
Perform this procedure:
• Before adding a node to a BladeCluster
• If you cannot start the ServerNet cluster subsystem
• If you cannot connect to a remote node
• If you cannot display information about the ServerNet cluster in the OSM Service Connection
To avoid conflicts with OSM and the guided procedures, you must configure $ZZKRN.#MSGMON,
$ZZKRN.#SMN, and $ZZKRN.#ZZSCL to be the symbolic names for MSGMON, SANMAN, and
SNETMON.
Use the SCF interface to the Kernel subsystem to check that these processes are configured correctly
and in the STARTED state:
1. Display a list of all currently configured generic processes:
INFO PROCESS $ZZKRN.*
2. Check that the MSGMON, SANMAN, and SNETMON processes are displayed in the *Name
column with these required SCF symbolic names:
Required SCF Symbolic NameProcess NameProgram File Name
$ZZKRN.#ZZSMN$ZZSMNSANMAN
$ZZKRN.#ZZSCL$ZZSCLSNETMON
$ZZKRN.#MSGMON$ZIMnnMSGMON
3. If the processes are not configured with the required names, configure each process as
described in Configuring MSGMON, SANMAN, and SNETMON (page 87).
4. Check that MSGMON, SANMAN, and SNETMON are configured correctly:
INFO PROCESS $ZZKRN.#MSGMON, DETAIL
INFO PROCESS $ZZKRN.#ZZSMN, DETAIL
INFO PROCESS $ZZKRN.#ZZSCL, DETAIL
Compare the configured modifiers for MSGMON, SANMAN, and SNETMON with the
recommended modifiers shown in Configuring MSGMON, SANMAN, and SNETMON
(page 87).
Checking That Automatic Line-Handler Generation is Enabled 71