ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-30
Fallback for Upgrading ServerNet Cluster Software
With System Loads to Obtain G06.12 Functionality
Fallback for Upgrading ServerNet Cluster Software With System
Loads to Obtain G06.12 Functionality
Use this procedure if you need to restore the ServerNet II Switch firmware and
configuration files after upgrading the nodes to the G06.12 SUT:
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. Select a node to load down-rev firmware and configuration files on the cluster
switches. Use this downloader node to restore the down-rev firmware and
configuration files to the X- and Y-fabric cluster switches:
a. Use DSM/SCM to retrieve T0569AAA from the archive, replacing the M6770
and M6770CL firmware and configuration files in $SYSTEM.SYSnn.
b. Use the Configuration Update action of the TSM Service Application to
download the T0569AAA M6770CL configuration to the nearest X-fabric cluster
switch. For detailed steps, refer to Using the TSM Service Application to
Download the ServerNet II Switch Firmware or Configuration on page 4-99.
c. Use the Firmware Update action of the TSM Service Application to download
the T0569AAA M6770 firmware file to the nearest X-fabric cluster switch. For
detailed steps, refer to Using the TSM Service Application to Download the
ServerNet II Switch Firmware or Configuration on page 4-99.
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 links until you are instructed to do so by the Add Switch guided procedure.
Connecting a 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.
Note. Note the following considerations for downloading the T0569AAA configuration:
•
Downloading the configuration disrupts ServerNet communications across the X-
fabric cluster switch.
•
The T0569AAA configuration does not support Configuration 2 (0x10001). If the
cluster switch uses Configuration 2, you must change the configuration tag to
Configuration 1 (0x10000) in order to download the T0569AAA configuration. The
guided procedure allows you to change the configuration tag.