BladeCluster Solution Manual

Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued)
Task 6: Configure and Start Subsystem Processes and Expand Lines and Verify ServerNet Cluster Connectivity
Action or CommandInstallation/Migration Tasks
Refer to Starting and Stopping ServerNet Cluster Processes
and Subsystems (page 80).
Run the ZSCCONF TACL macro (located in
$SYSTEM.ZSUPPORT) to configure and start the
$ZZSCL (SNETMON) and $ZIMnn (MSGMON)
processes processes in the node.
CAUTION:
You should neither configure nor start the $ZZSMN
(SANMAN) process unless the BladeCluster will be
connected to a 6700 series ServerNet cluster. The
SANMAN process supports 6770 or 6780
ServerNet cluster switches and is not needed unless
the BladeCluster will be configured in combination
with a 6700 series (as described later in this
checklist).
SCF START SUBSYS $ZZSCLIf necessary, start the ServerNet Cluster subsystem
in each node.
SCF STATUS SUBNET $ZZSCL, PROBLEMSIf one or more nodes were previously added to the
BladeCluster Solution topology, confirm ServerNet
Cluster connectivity between these nodes and the
nodes that were just added.
SCF START LINE $SC*If necessary, start any Expand-over-ServerNet lines
on the node that was just added and between other
nodes.
NOTE: If you are migrating from a previous release of BladeCluster, refer to “Migrating from Previous Releases of
the BladeCluster Solution” (page 23).
Task 7: Migrating a 6700 Series ServerNet Cluster to a BladeCluster Solution Topology
TIP: You can skip this task:
• If you are installing an initial BladeCluster topology without 6700 series ServerNet clusters, skip this task and Task
8. These tasks are “Migration Only” and do not apply to your topology.
• If your topology requires clustering of a BladeCluster with 6700 series ServerNet Clusters, skip this task and proceed
to Task 8: Upgrading a 6700 Series ServerNet Cluster to a BladeCluster/6700 Series Solution Topology (page 35).
Migration Assumptions
This migration task assumes:
• An initial configuration comprised of NonStop BladeSystem and NonStop NS16000 series nodes that are connected
to a 6700 series ServerNet Cluster.
• A final configuration comprised of these nodes connected to a BladeCluster Solution topology.
• That the 6700 series ServerNet Clusters are no longer needed and can be removed and disconnected once migration
is complete.
Migration Considerations
• The full and complete migration from a 6700 series ServerNet Cluster to a BladeCluster should not occur until the
required hardware and software has been installed in all nodes.
• The required hardware and software do not need to be installed in all nodes at once before the 6770/6780
ServerNet cluster topology is migrated to a BladeCluster Solution topology.
◦ The required hardware and software can be installed on one node at a time, potentially over a period of several
weeks or months.
◦ The required hardware and software can be installed without a system load as long as the minimum RVU
requirements are met. For more information, refer to “Software Requirements for the Current Release of
BladeCluster” (page 22).
Checklist for Required Installation and Migration Tasks 33