ServerNet Cluster Manual

Managing a ServerNet Cluster
ServerNet Cluster Manual—520575-003
5-30
Restarting the External ServerNet SAN Manager
Process (SANMAN)
Restarting the External ServerNet SAN Manager Process
(SANMAN)
The external ServerNet SAN manager process may be restarted for the following
reasons:
•
Both processors in which the ServerNet SAN manager process pair is running are
stopped. The $ZPM persistence manager automatically restarts the process pair
as soon as any processor in its processor list becomes available.
•
The ServerNet SAN manager process abends. The $ZPM persistence manager
restarts it immediately.
•
An operator issues an SCF ABORT PROCESS $ZZKRN.#ZZSMN command,
followed by an SCF START PROCESS $ZZKRN.#ZZSMN command.
Starting the ServerNet Cluster Monitor Process (SNETMON)
Adding the ServerNet cluster monitor process (SNETMON) to the configuration
database is described in Section 3, Installing and Configuring a ServerNet Cluster.
HP recommends that you set the STARTMODE attribute to SYSTEM for the ServerNet
cluster monitor process. If you do so, SNETMON starts automatically after a system
load or a processor reload.
To start SNETMON after configuring it but before the next system load, or after
stopping it by using the SCF ABORT PROCESS $ZZKRN.#ZZSCL command, use the
SCF START command:
> START PROCESS $ZZKRN.#ZZSCL
Aborting the ServerNet Cluster Monitor Process (SNETMON)
To stop the ServerNet cluster monitor process, use the SCF ABORT PROCESS
command:
> ABORT PROCESS $ZZKRN.#ZZSCL
There are two cases in which you might have to abort SNETMON:
•
During installation of a T0294 SPR that includes a new version of SNETMON. In
this case, follow the installation instructions in the SOFTDOC for the SPR.
•
Before you can alter one or more SNETMON process configuration attributes via
SCF ALTER PROCESS $ZZKRN.#ZZSCL. Normally, you should not need to alter
any of the SNETMON process configuration attributes, if you configured
SNETMON with the TACL macro documented in Appendix E.
Note. Normally, you should not need to abort SNETMON—even if a system is no longer a
member of a ServerNet cluster. The ServerNet statistics provided by the Node Statistics (1200)
event are not available when SNETMON is aborted.