ServerNet Cluster 6780 Operations Guide (G06.28+, H06.05+)
Controlling ServerNet Cluster Processes
ServerNet Cluster 6780 Operations Guide—525606-003
2-8
Stopping ServerNet Cluster Services
Stopping ServerNet Cluster Services
You can use OSM or SCF to stop ServerNet cluster services.
Using OSM to Stop ServerNet Cluster Services
1. In the tree pane of the OSM Management window, right-click the ServerNet Cluster 
resource, and select Actions.
2. From the Actions list, select Set ServerNet Cluster State and click Perform 
Action.
3. In the drop-down list, select Stopped and click OK. The Action Status box shows 
the progress of the action.
4. Click Close to close the Actions dialog box.
Verify that ServerNet cluster services are stopped. (See Using OSM to Check the 
Status of the ServerNet Cluster Subsystem on page 1-14
Using SCF to Stop ServerNet Cluster Services
To stop ServerNet Cluster services on the local system, use the SCF STOP SUBSYS 
$ZZSCL command:
> STOP SUBSYS $ZZSCL
When ServerNet Cluster Services Are Stopped
When you stop ServerNet cluster services, the ServerNet cluster monitor process 
brings ServerNet cluster services to a STOPPED logical state. The ServerNet cluster 
monitor process itself does not stop but remains an active process. Terminating access 
to the ServerNet cluster proceeds:
1. The ServerNet cluster monitor process sets the ServerNet cluster subsystem state 
to STOPPING and logs the state change.
2. The ServerNet cluster monitor process informs each remote ServerNet cluster 
monitor process that the subsystem is stopping.
3. The ServerNet cluster monitor process instructs each local processor to terminate 
ServerNet connectivity.
4. When the processors have finished terminating connectivity, the ServerNet cluster 
monitor process moves the subsystem to the STOPPED state and logs the 
Note. The STOP SUBSYS command stops ServerNet data traffic for a node on both external 
fabrics (X and Y). By contrast, the SCF STOP SERVERNET $ZSNET command, when used 
on a ServerNet node, stops internal and external ServerNet data traffic for only one fabric (X or 
Y). No SCF command can stop ServerNet data traffic on only one external fabric. 










