BladeCluster Solution Manual

Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued)
Command or ActionMigration Only Tasks
SCF ABORT PROCESS $ZZKRN.#ZZSCLIf $ZZSCL is running, abort (but do not delete) the
process.
SCF STATUS PROCESS $ZZKRN.#MSGMONCheck if the $ZIMnn (MSGMON) processes are
running in each node that is being migrated from a
6700 series ServerNet Cluster to a BladeCluster
Solution topology.
SCF ABORT PROCESS $ZZKRN.#MSGMONIf the $ZIMnn processes are running, abort (but do
not delete) them.
Refer to:Complete Tasks 3, 4, and 6 for each node that is
being migrated from a 6700 series ServerNet
Cluster to a BladeCluster Solution topology.
• Task 3: Perform the Add Node to ServerNet Cluster
Procedure (page 31)
• Task 4: Connect the Node to the Advanced Cluster Hubs
(ACHs) and Verify the Automatic Line-Handler
Configuration (page 32)
• Task 6: Configure and Start Subsystem Processes and
Expand Lines and Verify ServerNet Cluster Connectivity
(page 33)
Task 8: Upgrading a 6700 Series ServerNet Cluster to a BladeCluster/6700 Series Solution Topology
NOTE: The NonStop NS14000 series only supports connections to a 6780 ServerNet cluster.
Upgrade Assumptions
This upgrade task assumes:
• An initial configuration comprised of either:
NonStop BladeSystem, NonStop NS16000 series, and NonStop S-series nodes that are connected to a 6770
series ServerNet Cluster.
◦
◦ NonStop BladeSystem, NonStop NS14000 series, NonStop NS16000 series, and NonStop S-series nodes that
are connected to a 6780 series ServerNet Cluster.
• A final BladeCluster topology comprised of either:
NonStop BladeSystems, NonStop NS16000 series, and NonStop S-series nodes connected to a BladeCluster/6770
Solution topology
◦
◦ NonStop BladeSystems, NonStop NS14000 series, NonStop NS16000 series, and NonStop S-series nodes
connected to a BladeCluster/6780 Solution topology. In this topology the S-Series and NS14000 nodes remain
connected to the 6780 topology only.
Upgrade Considerations
• You can upgrade from a 6700 series ServerNet Cluster to the BladeCluster over a period of several weeks or months
without installing the software or hardware in all of the nodes and without a system load as long as minimum RVU
requirements are met. For more information, refer to “Software Requirements for the Current Release of BladeCluster”
(page 22).
• Do not prepare the ServerNet switches or processor switches for connectivity to the BladeCluster Solution topology
via the OSM Service Connection until instructed to do so by this manual or the Add Node to ServerNet Cluster
guided procedure.
Command or Action...Upgrade Tasks
Task 1: Configure the Nodes for Installation or Migration to
the BladeCluster Solution (page 28)
Complete Task 1 and then return to this task.
Checklist for Required Installation and Migration Tasks 35