BladeCluster Solution Manual

Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued)
Command or Action...Upgrade Tasks
Notify end users before terminating applications.On each node that will be connected to the
BladeCluster Solution topology: stop all applications
that use Expand-over-ServerNet lines to communicate
with other nodes.
On all other nodes connected that will be connected
to the BladeCluster Solution topology: stop all
applications that use Expand-over-ServerNet lines
to communicate with the node that is being
migrated.
SCF ABORT LINE $SC*Stop all Expand-over-ServerNet lines on every node
that is about to be connected to the BladeCluster
Solution topology.
SCF ABORT LINE $SCnnnOn all other nodes: stop the Expand-over-ServerNet
line to the node that is about to be connected to the
BladeCluster Solution topology.
where nnn is the Expand node number of the node that will
be connected to the BladeCluster Solution topology.
SCF STOP SUBSYS $ZZSCLStop the ServerNet Cluster subsystem on each node
that will be connected to the BladeCluster Solution
topology.
SCF STATUS PROCESS $ZZKRN.#ZZSMNCheck if the $ZZSMN (SANMAN) process is
running on each node that will be connected to the
BladeCluster Solution topology.
SCF ABORT PROCESS $ZZKRN.#ZZSMNIf $ZZSMN is running, abort (but do not delete) the
process.
TIP: Do not delete the $ZZSMN process. This
process must run on all nodes connected to a
BladeCluster/6700 series Solution.
SCF STATUS PROCESS $ZZKRN.#ZZSCLCheck if the $ZZSCL (SNETMON) process is running
on each node that will be connected to the
BladeCluster Solution topology.
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 will be connected to the
BladeCluster Solution topology
SCF ABORT PROCESS $ZZKRN.#MSGMONIf the $ZIMnn processes are running, abort (but do
not delete) them.
CAUTION: Do not connect the fiber-optic cables until the
Add Node to ServerNet Cluster guided procedure instructs
you to do so.
Verify that the ServerNet node numbers of NonStop
BladeSystems and NonStop NS16000 series nodes
that will be connected to the BladeCluster Solution
topology are assigned the same ServerNet node
number on both the BladeCluster fabrics and the
6700 series ServerNet cluster fabrics.
NOTE: If the ServerNet node number of a
BladeSystem or a NonStop NS16000 series node
must be changed, then you must disconnect that
node from both 6700 ServerNet Cluster fabrics.
36 Installation and Migration Tasks