BladeCluster Solution Manual

B Configuring 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.
This appendix provides an example of how to configure MSGMON, SANMAN, and SNETMON
as generic processes in the system configuration database. You can use either the ZSCCONF
macro or create your own SCF command file. The ZSCCONF macro is typically located in $SYSTEM.
ZSUPPORT.
ZSCCONF TACL Macro
NOTE: Before using the ZSCCONF macro:
• You must log on using the super ID (255, 255) in order to run the macro successfully.
• Do not run the macro on a node that is currently an active member of a BladeCluster.
MSGMON, SANMAN, and SNETMON will be aborted, and the connection to the cluster
will be lost temporarily.
• This macro is intended as an example and might not be appropriate for all systems.
The ZSCCONF macro automates the process of adding MSGMON, SANMAN, and SNETMON
to the system-configuration database. The macro:
• Detects the number of processors currently loaded and prompts you to confirm this number (if
your system has fewer than four processors)
• Aborts and deletes the MSGMON, SANMAN, and SNETMON processes if they are already
present
• Returns error messages if the processes could not be successfully deleted
• Adds the processes using a processor list that is appropriate for the system size
• Starts MSGMON, SANMAN, and SNETMON and attempts to start the ServerNet cluster
subsystem
Run the ZSCCONF Macro
NOTE: Do not run the ZSCCONF macro on a node that is currently an active member of a
BladeCluster. MSGMON, SANMAN, and SNETMON will be aborted, and the connection to the
cluster will be lost temporarily.
The ZSCCONF macro leaves the ServerNet cluster subsystem (also known as ServerNet cluster
services) in the STARTED state. If you use the Add Node to ServerNet Cluster action from the OSM
Service Connection, the action automatically starts the subsystem. Optionally, too, you can also
use the SCF START SUBSYS $ZZSCL command to start the subsystem.
1. Log on using the super ID (255, 255). The macro will not run successfully if you use another
user ID.
2. From the $SYSTEM.ZSUPPORT subvolume, run the ZSCCONF macro:
RUN ZSCCONF
3. When the macro finishes, check that the SCF state of $ZZSCL is in the STARTED state:
STATUS PROCESS $ZZKRN.#ZZSCL
4. Start $ZZSCL if needed:
START PROCESS $ZZKRN.#ZZSCL
5. Check that the SCF state of the $ZZSMN process is in the STARTED state:
STATUS PROCESS $ZZKRN.#ZZSMN
ZSCCONF TACL Macro 87