BladeCluster Solution Manual
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued)
d) If you adding a single-zone BladeCluster and do not plan to add zones to this configuration in the future, skip
these bulleted steps and proceed to substep “e” following. If you are adding an anchor node to a multi-zone
BladeCluster, or, you are planning to scale up a single-zone BladeCluster by configuring the anchor node with
the high-availability option, perform these steps:
• From the Zone Number list, select the zone number for the anchor node that is being added.
• From the Number of Zones list, select the appropriate number of zones in the BladeCluster. This selection is
only available for the first BladeSystem anchor node in a zone.
• From the Inter-Zone Distance list, select between Short-Haul or one of the Long-Haul options: Long-Haul at
ServerNet3 (25 km), Long-Haul at ServerNet 2 (50 km), or Long-Haul at throttled ServerNet 2 (65 km). This
selection is only available if the NonStop BladeSystem's Node Position in the Zone is 1 and the Number of
Zones is greater than 1.
e) When asked if you want to continue with the BladeCluster configuration, click Continue.
f) Complete the Add Node to Cluster task.
NOTE: The Add Node guided procedure is expected to take 15 minutes to complete when adding a BladeCluster
node.
NOTE: Anchor nodes within a multi-zone topology and NonStop NS16000 Series nodes within a single-zone
topology are limited to certain ServerNet node numbers. Depending on your configuration, refer to ServerNet
Node Positions in a Single Zone (page 14) or ServerNet Node Restrictions in a Multi-Zone Blade Cluster (page 69).
Task 4: Connect the Node to the Advanced Cluster Hubs (ACHs) and Verify the Automatic Line-Handler Configuration
Action or CommandInstallation/Migration Tasks
Refer to Connections to the Advanced Cluster Hubs (page 43)Connect the processor switches or ServerNet
switches to the Advanced Cluster Hubs (ACHs).
CAUTION: Do not connect the fiber-optic cables
until the Add Node to ServerNet Cluster guided
procedure instructs you to do so.
Refer to the OSM Add Node to ServerNet Cluster online help.Use one of these methods to determine if the
automatic line-handler configuration is enabled in
the nodes:
• Check for the presence of
$ZZKRN.#OSM-CONFLH-RD. If it is present, the
automatic line-handler configuration is enabled.
• Check the status of the routing distributor
($ZOLHD). If this process is running (but in a
STOPPED state), automatic line-handler
configuration is enabled. Although the routing
distributor is running, the #OSM-CONFLH-RD
process remains in a STOPPED state until a node
is added to the cluster.
Task 5: Connect the BladeSystem Anchor Nodes in a BladeCluster/Multizone Solution
TIP: This task is required only if you are configuring a multi-zone BladeCluster. Skip to Task 6 if you are configuring
a single-zone BladeCluster.
To connect the BladeSystem anchor nodes, refer to “Connections to BladeCluster/Multi-Zone Solution Topologies”
(page 63).
32 Installation and Migration Tasks










