BladeCluster Solution Manual

9 Starting and Stopping ServerNet Cluster Processes and
Subsystems
When the ServerNet cluster subsystem is stopped, the BladeSystem node informs other nodes that
it is leaving the BladeCluster. Stopping the ServerNet cluster subsystem destroys interprocessor
connectivity between the node that receives the command and all other nodes over both external
fabrics. The ServerNet cluster monitor process $ZZSCL itself does not stop but remains an active
process.
Stopping the ServerNet Cluster Subsystem
NOTE: HP recommends that you do not stop and restart the ServerNet cluster subsystem as a
method to repair ServerNet connectivity.
Stopping the ServerNet Cluster subsystem is normally used prior to:
• Physically disconnecting a node from the topology
• Halting the processors on a node
• The DSM/SCM ZPHIRNM step when installing a new release version update (RVU)
• Aborting the SNETMON process pair for the purpose of upgrading the SNETMON software,
unless recommended otherwise by HP
Using SCF
1. At an SCF prompt, stop the ServerNet cluster subsystem:
STOP SUBSYS $ZZSCL
2. Confirm that the ServerNet cluster subsystem is stopped:
STATUS SUBSYS $ZZSCL
Using the OSM Service Connection
1. Right-click the ServerNet Cluster resource, and select Actions.
2. From the Available Actions drop-down list, select Set ServerNet Cluster State.
3. Click Perform Action.
4. From the drop-down list of ServerNet cluster states, select Stopped.
5. Click OK. The Action Status window shows the progress of the action.
6. Click Close to close the Actions dialog box.
7. From the details pane, select the Attributes tab.
8. From the Attributes tab, check that the ServerNet Cluster State is stopped.
Stopping Expand-Over-ServerNet Lines
Stopping Expand-over-ServerNet lines is required when you add, move, or remove a node.
Use these SCF commands to identify and stop Expand-over-ServerNet lines and also refer to the
“Expand Lines Form” (page 91).
1. For the affected node, identify the currently configured Expand-over-ServerNet lines. For
example:
LISTDEV TYPE 63,4
2. For all other nodes in the cluster, list the Expand-over-ServerNet lines that must be stopped for
the affected node:
INFO PROCESS $NCP, LINESET
80 Starting and Stopping ServerNet Cluster Processes and Subsystems