ServerNet Cluster Manual

Installing and Configuring a ServerNet Cluster
ServerNet Cluster Manual—520575-003
3-27
Task 4: Use the Guided Procedure to Prepare to
Join the Clusters
You can save time by configuring one cluster to use X1/Y1 cluster switches and the
other cluster to use the X2/Y2 cluster switches, but this practice is not required. The
Add Switch guided procedure detects the cluster switch configuration and gives you an
opportunity to change it before connecting the four-lane links.
Task 4: Use the Guided Procedure to Prepare to Join the
Clusters
Before joining the two halves of the split-star topology, you must use the Add Switch
guided procedure to verify that the hardware and software is ready. You must run the
guided procedure at least once on both clusters.
From the system console of any node connected to the cluster, for TSM choose
Start>Programs>Compaq TSM>Guided Configuration Tools>Add Switch. For
OSM, the procedure is launched from within the OSM Service Connection by
performing the Replace action from the switch you want to replace. Online help is
available to assist you in performing the procedure.
The guided procedure and its online help allow you to:
•
Update the switch firmware files, if necessary
•
Update the cluster switch configuration, if necessary
•
Perform the hard reset action required to complete the configuration update
•
Connect the four-lane links between the X1/Y1 and X2/Y2 cluster switches
When the guided procedure indicates that both clusters meet the requirements for
connecting a remote cluster switch, you can connect the four-lane links.
Task 5: Connect the Four-Lane Links
To connect the four-lane links between the X1/Y1 and X2/Y2 cluster switches:
1. Remove the black plugs from ports 8 through 11 of the double-wide PICs inside
each cluster switch.
Caution. Do not connect the four-lane links until you are instructed to do so by the guided
procedure for adding a cluster switch (Add Switch). Connecting a four-lane link between two
cluster switches running the T0569AAA configuration can cause an outage on every node in
the cluster. Power cycling each node might be necessary to recover from this outage.
Outages can occur because the cluster is unprotected by the neighbor-checking logic if cluster
switches running the T0569AAA configuration are connected. Connecting two cluster switches
running the T0569AAA configuration can create an invalidly configured split-star topology in
which ServerNet packets sent by nodes 1 through 8 to nodes 9 through 16 loop indefinitely
between the two cluster switches.