ServerNet Cluster Manual

Managing a ServerNet Cluster
ServerNet Cluster Manual—520575-003
5-29
Starting the External ServerNet SAN Manager
Process (SANMAN)
Starting the External ServerNet SAN Manager Process
(SANMAN)
Adding the external ServerNet SAN manager process (SANMAN) to the configuration
database is described in Section 3, Installing and Configuring a ServerNet Cluster.
When you add SANMAN, HP recommends that you set the STARTMODE attribute to
SYSTEM. If you do so, SANMAN starts automatically after a system load or a
processor reload.
To run SANMAN after adding it but before the next system load, or after stopping it with
the SCF ABORT PROCESS $ZZKRN.#ZZSMN command, use the SCF START
PROCESS command:
> START PROCESS $ZZKRN.#ZZSMN
Aborting the External ServerNet SAN Manager Process
(SANMAN)
To stop the ServerNet SAN manager process, use the SCF ABORT PROCESS
command:
> ABORT PROCESS $ZZKRN.#ZZSMN
There are two cases in which you might have to abort SANMAN:
•
During installation of a T0502 SPR that includes a new version of SANMAN. In this
case, follow the installation instructions in the SOFTDOC for the SPR.
•
Before you can alter one or more SANMAN process configuration attributes with
SCF ALTER PROCESS $ZZKRN.#ZZSMN. Normally, you should not need to alter
any of the SANMAN process configuration attributes, as long as you have
configured SANMAN with the TACL macro documented in Appendix E.
Note. In this section, the external ServerNet SAN manager process ($ZZSMN) is referred to
as SANMAN. The symbolic name for the SANMAN generic process is assumed to be ZZSMN,
which also is the recommended symbolic name.
Note. Although it has no effect on data traffic, aborting SANMAN causes the Cluster tab to
disappear in the TSM Service Application. Consequently, you cannot view or manage cluster
resources such as external fabrics and cluster switches. Normally, you should not need to
abort SANMAN—even if a system is no longer a member of a ServerNet cluster.