ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-47
Steps for Upgrading Software With System Loads to
Obtain G06.14 Functionality
k. Use the TSM Service Application to update the SP firmware. For the detailed
steps, refer to the online help.
l. Restart the MSGMON processes:
>SCF START PROCESS $ZZKRN.#MSGMON
m. Restart the SANMAN process:
>SCF START PROCESS $ZZKRN.#ZZSMN
n. Restart the SNETMON process:
>SCF START PROCESS $ZZKRN.#ZZSCL
o. Restart the ServerNet cluster subsystem:
>SCF START SUBSYS $ZZSCL
p. Restart all Expand-over-ServerNet lines:
>SCF START LINE $SCxxx
q. Use the TSM Service Application to check the ServerNet cluster status. For
information about using TSM, refer to Section 5, Managing a ServerNet
Cluster.
4. Use SCF to make sure direct ServerNet communication is possible on both fabrics
between all nodes connected to the cluster switches:
>SCF STATUS SUBNET $ZZSCL, PROBLEMS
5. Select a node whose system console can be used to download the ServerNet II
Switch firmware and configuration. This will be the downloader node.
If you are upgrading a cluster that uses a split-star topology, you must select two
downloader nodes: one for the X1/Y1 cluster switches and one for the X2/Y2
Note. In order to use the PROBLEMS option, T0294AAG (or a superseding SPR) must be
applied.
If the PROBLEMS option is not available, use the SCF STATUS SUBNET $ZZSCL
command on all nodes. SCF STATUS SUBNET $ZZSCL requires T0294AAA or a
superseding SPR. If remote passwords are configured, you can issue the SCF STATUS
SUBNET $ZZSCL command for a remote node (for example, \REMOTE) from the local
node as follows:
SCF STATUS SUBNET \REMOTE.$ZZSCL
This command eliminates the need to establish a logon window for each node.