BladeCluster Solution Manual

NOTE: It might take a few minutes for the node that received the RVU upgrade to restore
ServerNet Cluster connectivity to all other nodes.
a. The STATUS SUBNET $ZZSCL command also shows the state of the
Expand-over-ServerNet lines to/from the node receiving the RVU upgrade. The
Expand-over-ServerNet lines should restart automatically if the OSM Automatic Line
Handler generation feature is enabled as described in “Checking That Automatic
Line-Handler Generation is Enabled” (page 71).
b. If necessary, you can restart the previously stopped Expand-over-ServerNet lines. Refer
to “Starting the Expand-Over-ServerNet Line-Handler Processes and Lines” (page 82).
Removing a Node From a BladeCluster Topology
To remove a BladeSystem node from a BladeCluster:
1. Record the Expand-over-ServerNet lines to be stopped. Refer to “Expand Lines Form” (page 91).
2. Shut down any applications using Expand-over-ServerNet connections between the node and
the rest of the cluster.
3. Stop the Expand-over-ServerNet lines. Refer to “Stopping Expand-Over-ServerNet Lines”
(page 80).
4. On the node you are removing, stop the ServerNet cluster subsystem. Refer to “Stopping the
ServerNet Cluster Subsystem” (page 80).
5. If you are moving the fiber-optic cables to different Advanced Cluster Hub (ACH) ports on the
same BladeCluster, disconnect all the X-fabric and Y-fabric fiber-optic cables (only for the node
you are removing) from the ACHs.
NOTE: Disconnect all cables at roughly the same time. If you disconnect one cable and then
allow more than two minutes to pass before disconnecting the remaining cables, OSM
generates alarms. If value-added diagnostics are enabled, these alarms are dialed out to the
service provider.
Removing a Zone From a BladeCluster Topology
1. Select the zone to be removed. You can select the zone with the fewest number of nodes or
one that is least critical to your application.
2. Record the Expand-over-ServerNet lines to be stopped. Refer to “Expand Lines Form” (page 91).
3. Check that the cluster is operating properly on both ServerNet fabrics. Refer to “Checking the
External Fabric for All Nodes” (page 70). Resolve any problems before you proceed.
4. Shut down any applications using Expand-over-ServerNet connections between all nodes in
the zone and nodes in other zones of the cluster.
5. In all nodes of the zone you plan to remove, stop Expand connectivity to the nodes in the other
zones. Refer to “Stopping Expand-Over-ServerNet Lines” (page 80).
6. In all other nodes, stop Expand connectivity to the nodes of the zone you are removing. Refer
to “Stopping Expand-Over-ServerNet Lines” (page 80).
7. In all nodes of the zone you plan to remove, stop the ServerNet cluster subsystem. Refer to
“Stopping the ServerNet Cluster Subsystem” (page 80).
8. Disconnect the zone cables to the zone being removed on both fabrics. You must disconnect
the cables from both sides before proceeding to the next step. Otherwise, errors can occur.
9. If you removed zone 3 from a 3-zone long-haul topology, and the desired final topology is a
2-zone long-haul topology, then consider connecting the zone cables you removed from zone
3 between zones 1 and 2. This will provide two additional links per fabric between zones 1
78 Changing the BladeCluster Topology