ServerNet Cluster Manual

Managing a ServerNet Cluster
ServerNet Cluster Manual—520575-003
5-31
Starting ServerNet Cluster Services
Aborting SNETMON on a node does not change the state of ServerNet Cluster IPC
connectivity to and from that node. However, while SNETMON is not running, the node
will not be able to bring up or automatically repair remote IPC connectivity. This
includes bringing up remote IPC connectivity to any processor that is reloaded in the
cluster, bringing up IPC connectivity to any new node that is added to the cluster, and
automatically repairing any failed remote IPC connections. Expand-over-ServerNet
lines to any new node that is added to the cluster while SNETMON is not running
cannot be brought up either.
Although ServerNet Cluster IPC connectivity is not brought down when the SNETMON
process is aborted, Expand-over-ServerNet lines tolerate only temporary absences of
SNETMON. Typically, Expand-over-ServerNet lines for the node is brought down if
SNETMON is aborted and is not restarted within five minutes.
Starting ServerNet Cluster Services
You can use TSM or SCF to start ServerNet cluster services.
Using TSM to Start ServerNet Cluster Services
1. Log on using the TSM Service Application.
2. Click the Cluster tab to view information about the ServerNet cluster.
3. In the tree pane, right-click the ServerNet Cluster resource, and select Actions.
4. From the Actions list, click Start ServerNet Cluster Services.
5. Click Perform action. The Action Status box shows the progress of the action.
6. Click Close to close the Actions dialog box.
7. Verify that ServerNet cluster services are started. (See Using TSM to Check the
ServerNet Cluster Subsystem Status on page 5-16.)
Using SCF to Start ServerNet Cluster Services
To start ServerNet Cluster services on the local system, use the SCF START SUBSYS
$ZZSCL command:
> START SUBSYS $ZZSCL
When a System Joins a ServerNet Cluster
The following steps describe what happens when a system joins a ServerNet cluster:
1. First the ServerNet cluster monitor process is started (by the persistence manager
$ZPM or with an SCF START PROCESS command, depending on the
STARTMODE configuration).
Note. You will receive an error if you try to start ServerNet cluster services before the fiber-
optic cables are connected from the MSEBs in group 01 to the cluster switches.