J06.09 Release Version Update Compendium

8 Networking Products
BladeCluster Solution Supports Multi-Zone and Long Distance Topologies
The BladeCluster Solution has been enhanced to support:
• Multi-zone topologies:
— Up to 8 BladeSystems and/or NS16000 series nodes per zone (however, at most 5 out
of the 8 nodes in a BladeCluster zone can be NS16x00 servers)
— One to three zones for a maximum of 24 nodes per cluster
• Longer distances:
— Up to 125 meters between nodes
— Up to 25 Kilometers between zones
Migration Considerations
These features are available as a set of SPRs that implement Release 1.2 of the BladeCluster
Solution product. These SPRs ship with the J06.09 RVU, but they can also be installed on top of
J06.04 or later RVUs without requiring a system load. BladeCluster Solution Release 1.2 supports
all of the functionality available in previous BladeCluster Solution releases, such as connectivity
options for 6770 and 6780 cluster switches, NonStop S-Series nodes, and NonStop NS14000 series
nodes.
• Multi-zone topologies require an inter-zone software license for the anchor node in each
BladeCluster zone.
• Adding zones to an existing BladeCluster requires the reconfiguration of the anchor nodes.
• The anchor nodes of a multi-zone BladeCluster topology must be BladeSystems.
• The anchor nodes of a multi-zone BladeCluster topology can be optionally configured to
provide increased fault tolerance for the topology.
• Multi-zone topologies with a zone-to-zone distances greater than 125 meters require Dense
Wavelength Division Multiplexers (DWDMs).
Please refer to the BladeCluster Solution Manual for more information on the required hardware
and software, as well as installation and migration considerations.
Fallback Considerations
The following considerations apply if there is a need to fall back to a previous RVU after installing
a BladeCluster Solution topology and the node must remain connected to that topology:
• A minimum fallback RVU of J06.04 is required for the BladeCluster Solution topology.
• Certain SPRs must also be installed on top of the fallback RVU. Please refer to the BladeCluster
Solution Manual for details on the required software.
New Cluster I/O Protocols (CIP) Features
As of J06.09, the Cluster I/O Protocols (CIP) support these enhancements:
• The climconfig slaveinterface command allows users to manually configure the primary
slave of a bond interface.
• The climconfig interface command supports configuration of the Maximum Transmission
Unit (MTU) size and the configured MTU size is preserved across CLIM reboots.
For more information, see the Cluster I/O Protocols (CIP) Configuration and Management Manual.
BladeCluster Solution Supports Multi-Zone and Long Distance Topologies 23