ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-92
Fallback for Merging a Split-Star Topology and a Star
Topology to Create a Tri-Star Topology
9. Repeat Step 3 on the other Y-fabric cluster switch that will be used for the split-star
topology. You must change the configuration tags to support the split-star topology.
10. On all Y-fabric cluster switches in the tri-star topology, disconnect the two-lane links
(the switch-to-switch cables connected to ports 8 through 11).
11. Connect the four-lane links between the Y-fabric cluster switches that will be used
for the split-star topology. (These are the cluster switches whose configuration tags
you changed in Step 8.) For more information, refer to Connecting the Four-Lane
Links on page 4-64.
12. Wait 4 to 5 minutes for the Y fabric to come up, and then verify that the fabric is
operational:
a. Use the SCF STATUS SUBNET $ZZSCL, PROBLEMS command to check for
connectivity problems.
b. Use the SCF STATUS SWITCH $ZZSMN command to verify that the ports are
enabled.
c. Use the TSM Service Application to check for alarms on the X fabric.
13. Use the SCF PRIMARY PROCESS $ZZSMN command to refresh the TSM
display.
14. If necessary, refer to Fallback for Upgrading Software to Obtain G06.14
Functionality on page 4-50.
Note. Unless your applications require it, you do not need to fall back to an earlier RVU on
individual nodes. The TSM client and server software are backward compatible, and
SNETMON (T0294AAG) and SANMAN (T0502AAG) support all topologies.