ServerNet Cluster 6780 Operations Guide (G06.24+, H06.03+)

Controlling ServerNet Cluster Processes
ServerNet Cluster 6780 Operations Guide—525606-002
2-9
Switching SNETMON or SANMAN Primary and
Backup Processes
change. Only the subsystem state changes are logged. Individual path state
changes are not logged.
5. On remote systems, as the ServerNet cluster monitor processes receive word that
a ServerNet cluster member has departed, they instruct their local processors to
bring down the ServerNet connections with the departing system. These remote
ServerNet cluster monitor processes then log the node disconnection to the event
log.
To fully terminate ServerNet cluster services on a system and stop the ServerNet
cluster monitor process, you must issue two SCF commands:
> STOP SUBSYS $ZZSCL
> ABORT PROCESS $ZZKRN.#ZZSCL
Stopping the ServerNet cluster monitor process by using the SCF ABORT PROCESS
command alone terminates the $ZZSCL process but does not bring down ServerNet
cluster services on the local system.
If you use only the SCF ABORT PROCESS command, the system remains joined to
the ServerNet cluster for up to 30 seconds if the ServerNet cluster state for the node is
STARTED (as represented by the SUBSYS $ZZSCL object for the node). After 30
seconds, the Expand-over-ServerNet line handlers, which periodically exchange status
messages with the local ServerNet cluster monitor process, terminate the Expand-
over-ServerNet connections.
Switching SNETMON or SANMAN Primary and
Backup Processes
You can use OSM or SCF to cause either the SNETMON or SANMAN primary and
backup processes to switch roles. For example, if the primary process is configured to
run in processor 0 and the backup process is configured to run in processor 1, you can
switch the primary to processor 1 and the backup to processor 0.
You can switch SANMAN or SNETMON primary and backup processes to repair
ServerNet connectivity problems. See Methods for Repairing ServerNet Connectivity
Problems on page 3-18.
Using OSM to Switch the Primary and Backup Processes
To switch the primary and backup processes using the OSM Service Connection:
1. In the tree pane, right-click the ServerNet Cluster resource, and select Actions.
The Actions dialog box appears.
2. In the Available Actions list, select the Switch SNETMON Process Pair action or
the Switch SANMAN Process Pair action.
Note. Normally, you should not need to abort SNETMON—even if a system is no longer a
member of a ServerNet cluster.