ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-78
Example: Merging A Split-Star Topology and a Star
Topology to Create a Tri-Star Topology
Example: Merging A Split-Star Topology and a Star Topology to
Create a Tri-Star Topology
The following example begins with two ServerNet clusters running any of the following
RVUs:
•
G06.09
•
G06.10
•
G06.11
•
G06.12
•
G06.13
One cluster uses the star topology and includes up to eight nodes. The other cluster
uses the split-star topology and includes up to 16 nodes. (However, the same
procedure applies if you are merging any cluster using one cluster switch per fabric
with another cluster using two cluster switches per fabric to create a tri-star topology.)
The upgrade:
•
Installs new versions of the software listed in Table 4-6 on page 4-8 on all nodes
•
Upgrades the firmware and configuration in the cluster switches
•
Reconfigures one of the clusters to use ServerNet node numbers 17 through 24
Following the upgrade, the merged cluster uses the tri-star topology and supports up to
24 nodes.
Note. The upgrade of a pre-G06.13 cluster to a G06.13 or G06.14 cluster using X1/Y1, X2/Y2,
and X3/Y3 cluster switches requires shutting down ServerNet cluster communications for all
nodes in one of the clusters. This action is required because the ServerNet node numbers in
the cluster must be changed from 1 through 8 or 9 through 16 to numbers 17 through 24 when
the X-fabric and Y-fabric cluster switches in that cluster are upgraded to the new configuration.