BladeCluster Solution Manual

and 2, which increases the aggregate bandwidth between these zones. For more information,
refer to:
• “BladeCluster Connections for the Short-Haul Multi-Zone Topology (2 Zones)” (page 65)
• “BladeCluster Connections for the Short-Haul Multi-Zone Topology (3 Zones)” (page 66)
• “BladeCluster Connections for the Long-Haul Multi-Zone Topology (2 Zones)” (page 67)
• “BladeCluster Connections for the Long-Haul Multi-Zone Topology (3 Zones)” (page 68)
10. If you plan to use the removed zone as an independently functioning BladeCluster:
a. Restart the ServerNet Cluster Subsystem on the nodes you have removed. Refer to “Starting
the ServerNet Cluster Subsystem” (page 81).
b. Restart the Expand-over-ServerNet lines in the new BladeCluster. Refer to “Starting the
Expand-Over-ServerNet Line-Handler Processes and Lines” (page 82).
c. Restart applications.
Replacing ServerNet Switches in a BladeCluster Topology
Service providers, refer to the replacement instructions in the Replacing ServerNet Switch FRUs in
a NonStop BladeSystem service procedure.
Installing Quad MMF PICs in a Processor Switch for a BladeCluster
Topology
Service providers, refer to the Replacing P-switch online help for instructions for processor switches
that require installation of quad MMF PICs in slots 7 and 9 to join a BladeCluster topology.
Replacing ServerNet Switches in a BladeCluster Topology 79