ServerNet Cluster Manual

SCF Commands for SNETMON and the ServerNet
Cluster Subsystem
ServerNet Cluster Manual—520575-003
8-9
Example
If the configured STARTSTATE is STOPPED, the ServerNet cluster monitor
process must wait for a START SUBSYS command before proceeding to start
ServerNet cluster services.
Once ServerNet cluster services on the local system have been started, the
ServerNet cluster monitor process establishes ServerNet connections with all other
systems in the ServerNet cluster that are in the STARTED or STARTING states,
and moves the subsystem to the STARTED state.
If the Expand-over-ServerNet line-handler processes are configured and are in the
STARTED state, Expand connectivity is established with the other systems in the
ServerNet cluster.
When the START SUBSYS is completed:
•
The subsystem state is STARTED.
•
The ServerNet cluster monitor process has a list of all systems known to be in
the ServerNet cluster.
•
ServerNet connections are established with each system.
If ServerNet connection attempts fail or if successful connections subsequently fail,
periodic attempts are made to establish or reestablish the connection. Failures and
successful reconnections are logged to the event log. Failures to connect are
logged as path or other failures. In addition, each ServerNet cluster subsystem
state change (to STARTING and then to STARTED) is logged. If no other systems
are discovered, that fact also is logged.
Example
The following SCF command moves the ServerNet cluster subsystem into the logical
STARTED state and joins the system to the ServerNet cluster:
> START SUBSYS $ZZSCL
STATUS Command
The STATUS command returns information about the cluster connections and the state
of the ServerNet cluster subsystem. STATUS is a nonsensitive command.
The STATUS command syntax is:
STATUS [/OUT file-spec/] { SUBNET } $ZZSCL [, DETAIL]
[, LOCAL]
[, NODE ServerNet
node number]
[, ACTIVE ]
[, SUMMARY ]
[, PROBLEMS ]
{ SUBSYS } $ZZSCL [, DETAIL]