ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-96
Considerations for Upgrading SNETMON/MSGMON
and the Operating System
•
If SNETMON/MSGMON abends due to a version mismatch error, it cannot start
direct ServerNet connectivity between the local node and other remote nodes.
However, this condition does not interfere with ServerNet connectivity between
those other remote nodes.
•
All nodes in a split-star topology containing 1-kilometer four-lane links must run
G06.11 or a subsequent G-series RVU. The migration technique described in
Upgrading Software With System Loads to Obtain G06.12 Functionality on
page 4-25 is required for any users who migrate from G06.09 or G06.10 to G06.11
or G06.12 to achieve the longer distances provided by the split-star (16-node)
topology. Changes in the G06.11 and G06.12 RVUs ensure safe usage of longer
ServerNet cables.
All nodes in a split-star topology containing 5-kilometer four-lane links must run
G06.16 or a subsequent G-series RVU and contain only NSR-X or NSR-Y
processors.
Table 4-29 describes the relationship between the four-lane links and the RVU
running on the node in a split-star topology.
•
The tri-star topology requires that all nodes run G06.14 (or a G-series RVU) or
G06.13 with SPRs. If all processors in the cluster are processor type NSR-X or
NSR-Y, the two-lane links used in a tri-star topology can be up to 5 kilometers long.
Otherwise, the two-lane links can be up to 1 kilometer long.
Table 4-29. Length of Four-Lane Link and Operating System
If the split-star topology consists of . . . The four-lane link can be . . .
At least one G06.09 or G06.10 node Up to 80 meters
Nodes containing G06.11 or a later G-series
RVU and at least one processor in the
cluster is not processor type NSR-X or
NSR-Y.
Up to 1 kilometer
Nodes containing G06.16 or a later G-series
RVU and all processors in all nodes are
processor type NSR-X or NSR-Y.
Up to 5 kilometers