ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-41
Steps for Upgrading Software Without System Loads
to Obtain G06.14 Functionality
This scenario does not change the ServerNet node number range for the
cluster switch.
c. Use the TSM Service Application to verify that the X-fabric cluster switch is
operational.
d. Use the SCF STATUS SUBNET $ZZSCL command on all nodes to verify that
direct ServerNet connectivity has been restored on the X fabric.
6. Repeat Step 5 for the Y-fabric cluster switch.
7. If you are upgrading a cluster that uses a split-star topology, repeat Step 5 and
Step 6 using the X2/Y2 downloader node.
8. Restart any applications using Expand-over-ServerNet connections between the
nodes in the cluster.
Note. Downloading the firmware and configuration disrupts ServerNet connectivity
through the X-fabric cluster switch temporarily.
Note. Direct ServerNet connectivity is automatically restored after an interval of
approximately 50 seconds times the number of nodes in the cluster (25 seconds for
nodes running G06.14 or a later G-series RVU). For faster (but manual) recovery of
ServerNet connectivity, use the SCF START SERVERNET
\REMOTE.$ZSNET.FABRIC.* command on all affected nodes after you have used the
TSM Service Application to verify that the X-fabric cluster switch is operational.
The START SERVERNET command works only for nodes running G06.12 or a later
G-series RVU. For nodes running G06.09 through G06.11, you can use the following
commands:
SCF STOP SUBSYS $ZZSCL
SCF START SUBSYS $ZZSCL
Stopping and restarting the ServerNet cluster subsystem destroys and restarts
interprocessor connectivity between the node that receives the commands and all
other nodes over both external fabrics.