BladeCluster Solution Manual

Performing an RVU Upgrade on a Node
This procedure describes the steps for an RVU upgrade in a node connected to any ServerNet
Cluster topology (such as a BladeCluster Solution, ServerNet Cluster 6770, ServerNet Cluster
6780, or a combination of these cluster topologies).
TIP: Besides the RVU upgrade itself, this procedure:
• Minimizes EMS error messages on other nodes connected to the same ServerNet Cluster.
• Minimizes error-handling software overhead in other nodes connected to the same ServerNet
Cluster, such as message retries to the node receiving the RVU upgrade.
• Allows for a graceful communication shut down to/from the node receiving the RVU upgrade.
To perform an RVU upgrade on a node:
1. Record the Expand-over-ServerNet lines to be stopped. Refer to “Expand Lines Form” (page 91)
.
2. Shut down any applications using Expand-over-ServerNet connections between the node and
the rest of the cluster.
3. Stop the Expand-over-ServerNet lines. Refer to “Stopping Expand-Over-ServerNet Lines”
(page 80).
4. On the node that is about to receive the RVU upgrade, stop the ServerNet cluster subsystem.
Refer to “Stopping the ServerNet Cluster Subsystem” (page 80).
5. Perform the RVU upgrade.
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 useful unless these switches are
present.
6. After the system load of the new RVU, issue these SCF commands to verify the $ZZSMN,
$ZZSCL, and $ZIMnn processes are started:
STATUS PROCESS $ZZKRN.#ZZSMN
STATUS PROCESS $ZZKRN.#ZZSCL
STATUS PROCESS $ZZKRN.#MSGMON
The above processes should start automatically after system load if they were configured
correctly as described in “Configuring MSGMON, SANMAN, and SNETMON” (page 87).
Otherwise, you can start these processes manually as described in “Starting SANMAN”
(page 81), “Starting MSGMON” (page 82), and “Starting SNETMON” (page 82).
7. To confirm the ServerNet cluster subsystem is started on the node that received the RVU
upgrade, issue the SCF command:
START SUBSYS $ZZSCL
8. The ServerNet cluster subsystem should start automatically after a system load, assuming the
STARTSTATE attribute is configured as STARTED. For details on the STARTSTATE attribute,
refer to the ServerNet Cluster Manual.
a. If necessary, display the STARTSTATE attribute by issuing the SCF command:
INFO SUBSYS $ZZSCL
b. If necessary, manually start the ServerNet cluster subsystem by issuing the SCF command:
START SUBSYS $ZZSCL
9. To confirm that ServerNet Cluster connectivity between the node that received the RVU upgrade
and all other nodes in the cluster has been restored, issue the SCF command:
STATUS SUBNET $ZZSCL
Performing an RVU Upgrade on a Node 77