ServerNet Cluster Manual

ServerNet Cluster Description
ServerNet Cluster Manual—520575-003
1-38
NonStop Kernel Message System
MSGMON must be configured:
•
To be persistent.
•
To run in every processor of a system.
•
To have the process name $ZIMnn, where nn is the processor number. The CPU
ALL attribute ensures that the process names are created with the proper CPU
number suffix. The recommended symbolic name is MSGMON.
•
To run under the super ID (255,255).
NonStop Kernel Message System
The NonStop Kernel message system provides the set of privileged application
program interfaces (APIs) for interprocessor communication between processes
residing on the same or on different systems. The message system is changed for
G06.09 and later RVUs to allow interprocessor communication between distinct
systems over the ServerNet fabrics.
SANMAN Subsystem and SANMAN
The external system area network manager process (SANMAN) subsystem is the
software environment that enables control of the external ServerNet fabrics. The
following list summarizes naming and numbering for the SANMAN subsystem:
SANMAN
The External System Area Network Manager (SANMAN) is a process pair that runs in
every NonStop S-series server connected to a ServerNet cluster. SANMAN provides
the services needed to manage the external ServerNet fabrics and the system’s
access to the fabrics:
•
Manages the external ServerNet fabrics.
•
Initializes, monitors, configures, and controls the cluster switches.
•
Polls the cluster switches at regular intervals. For details, see Table 9-3 on
page 9-12.
•
Communicates with other processes or objects that require information from or
about the external fabrics. These processes or objects can include the OSM or
TSM client, SNETMON, SCF, the cluster switches, and the service processors
(SPs).
Full Name NonStop Kernel external SAN manager subsystem
Subsystem Name SMN
Subsystem Acronym ZSMN
Subsystem Number 237