BladeCluster Solution Manual

Table 8 Checklist of Installation and Migration Tasks Tasks 1 through 8 (continued)
For more information, see...Installation/Migration Tasks
TIP: This step is only required for multi-zone
topologies. Skip this step if you are configuring a
single-zone BladeCluster.
“Software Requirements for the Current Release of
BladeCluster” (page 22)
If the BladeCluster will participate in a multi-zone
topology, verify that every BladeSystem anchor node
(either node 1, 9, or 17) to be added has its own
interzone license file and that it is the correct file for
your distance option. The long distance options
supported by the interzone license files are:
Up to 25 Km distance option — uses the
Interzone License File (T0999H01) — this license
file is supported on H06.14 and later RVUs and
J06.04 and later RVUs
Up to 25 Km and greater than 25 Km distance
options — use the Extended Long-Haul License
File (T0930H01) — this license file is supported
on H06.23 and J06.12 and later RVUs only
All BladeCluster license files are in either of these
subvolumes:
$SYSTEM.SYSTEM
$SYSTEM.SYSnn
If there is no interzone license file, order, and then
copy this file to either of the above subvolumes of
each BladeSystem anchor node.
Verify all nodes to be added to the BladeCluster
topology have met the minimum software
requirements.
“Software Requirements for the Current Release of
BladeCluster” (page 22)
Softdoc for the SPR that is being installed.If software installation is required on any nodes,
follow all the installation instructions in each SPR's
softdoc to install the SPR on the nodes.
NOTE: H06.23 and J06.12 and later RVUs are
required for all nodes connected to a multi-zone
topology with inter-zone distances greater than 25
km.
“BladeCluster Solution Topologies” (page 12)Verify that you have not exceeded the maximum
nodes per zone:
No more than 5 nodes for a
BladeCluster/NonStop NS16000 Series Solution
No more than 8 nodes for all other BladeCluster
Solution topologies
TIP: If your topology contains a combination of
BladeSystems and NS16000 series nodes or is a
multi-zone topology, there are restrictions on
ServerNet node positions. Depending on your
configuration, refer to either:
ServerNet Node Positions in a Single Zone
(page 14)
ServerNet Node Restrictions in a Multi-Zone
Blade Cluster (page 69)
“Hardware Overview” (page 18)Verify each zone that contains the nodes has two
Advanced Cluster Hubs (ACHs) to connect the
nodes. If necessary, order the ACHs.
Checklist for Required Installation and Migration Tasks 29