ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-26
Fallback for Upgrading Software to Obtain G06.12
Functionality
Fallback for Upgrading Software to Obtain
G06.12 Functionality
The fallback procedure you use depends on whether or not your system can be
stopped temporarily for a system load:
•
Fallback for Upgrading ServerNet Cluster Software Without a System Load to
Obtain G06.12 Functionality on page 4-26
•
Fallback for Upgrading ServerNet Cluster Software With System Loads to Obtain
G06.12 Functionality on page 4-30
Fallback for Upgrading ServerNet Cluster Software Without a
System Load to Obtain G06.12 Functionality
Use this procedure if you need to restore the ServerNet II Switch firmware and
configuration files to an earlier version (G06.09, for example). This procedure uses one
of the nodes to restore the old firmware and configuration files. The other nodes can
continue operating as members of the cluster.
Choose a node from which to reconfigure the cluster switches, and use the system
console for that node to complete the following steps:
1. If the cluster is connected in a split-star topology, follow one of the procedures in
Fallback for Merging Clusters to Create a Split-Star Topology on page 4-66 to
disconnect the four-lane links.
2. Use DSM/SCM to retrieve T0569AAA from the archive so that you have access to
the M6770 and M6770CL firmware and configuration files.
3. Use the Configuration Update action of the TSM Service Application to download
the T0569AAA M6770CL configuration to the nearest X-fabric cluster switch. For
Caution. When the four-lane links have been disconnected, they should remain disconnected
unless the cluster switch needs to be added to another cluster. In that case, do not connect the
four-lane link until you are instructed to do so by the Add Switch guided procedure. Connecting
the four-lane link between two cluster switches running the T0569AAA configuration can cause
an outage on every node in the cluster if the NNA Version is 5. (FCO 39746B replaced Version
5 NNAs with NNA Version 22.) 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.