ServerNet Cluster 6780 Operations Guide (G06.24+, H06.03+)

Controlling ServerNet Cluster Processes
ServerNet Cluster 6780 Operations Guide—525606-002
2-5
Restarting the External ServerNet SAN Manager
Process (SANMAN)
Restarting the External ServerNet SAN
Manager Process (SANMAN)
You might restart SANMAN for one of the following reasons:
•
Both processors in which the SANMAN 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.
•
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)
For details about adding SNETMON to the configuration database, see the ServerNet
Cluster 6780 Planning and Installation Guide.
HP recommends that you set the STARTMODE attribute for the ServerNet cluster
monitor process to SYSTEM. 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
You might have to abort SNETMON in these two cases:
•
During installation of a T0294 software product revision (SPR) that includes a new
product 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 using
SCF ALTER PROCESS $ZZKRN.#ZZSCL. Normally, you should not need to alter
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.