ServerNet Cluster 6780 Operations Guide (G06.24+, H06.03+)
Controlling ServerNet Cluster Processes
ServerNet Cluster 6780 Operations Guide—525606-002
2-4
Starting the External ServerNet SAN Manager
Process (SANMAN)
Starting the External ServerNet SAN Manager 
Process (SANMAN)
For details about adding the external ServerNet SAN manager process (SANMAN) to 
the configuration database, see the ServerNet Cluster 6780 Planning and Installation 
Guide. 
HP recommends that you set the STARTMODE attribute for SANMAN 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)
You might have to abort SANMAN in these two cases:
•
During installation of a T0502 software product revision (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 if you configured SANMAN 
with the TACL macro documented in the ServerNet Cluster 6780 Planning and 
Installation Guide.
To stop SANMAN, use the SCF ABORT PROCESS command:
> ABORT PROCESS $ZZKRN.#ZZSMN 
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 is the required symbolic name.
Note.  Although it has no effect on data traffic, aborting SANMAN causes the ServerNet 
Cluster resource to disappear from the OSM Service Connection. 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.










