ServerNet Cluster Manual

SCF Commands for SNETMON and the ServerNet
Cluster Subsystem
ServerNet Cluster Manual—520575-003
8-3
SCL SUBSYS Object Summary States
SCL SUBSYS Object Summary States
The ServerNet cluster (SCL) subsystem state is maintained by the ServerNet cluster
monitor process (SNETMON). There is no aggregate ServerNet cluster subsystem
state; each ServerNet cluster monitor process maintains the state of objects relevant to
the local system and its connection to the ServerNet cluster.
Table 8-3 lists the summary states for the SUBSYS object supported by the SCL
subsystem.
Figure 8-1 illustrates the state transitions and the commands that trigger them.
Table 8-3. SCF Object Summary States
Summary State Description
STARTING The ServerNet cluster subsystem is attempting to establish ServerNet
connectivity with the other nodes in the ServerNet cluster.
STARTED The STARTING phase is complete. For all ServerNet nodes, either
connectivity has been established or the attempt failed. It is possible to
be in the STARTED state with no connectivity.
When the ServerNet cluster subsystem moves to the STARTED state, it
automatically detects all other nodes in the ServerNet cluster and
establishes connections with those that have a ServerNet cluster monitor
process in the STARTED or STARTING states.
STOPPING Connectivity is in the process of being brought down.
STOPPED The STOPPING phase is complete; there is no ServerNet cluster
connectivity. This is also the initial state of the ServerNet cluster monitor
process.
When the ServerNet cluster subsystem is running but in a STOPPED
summary state, it responds to SCF requests and status queries from local
Expand-over-ServerNet line-handler processes. ServerNet connections
with remote processors remain disabled, and discovery requests from
remote ServerNet cluster monitor processes are not accepted. Status or
statistics for remote connections are not available because these
connections do not exist. However, statistics for the local nodes are
provided.