ServerNet Cluster Web

How are the message system paths monitored? SNETMON maintains a matrix

of information about the status of processor-to-processor connections between

nodes. This information is made available to clients, such as the TSM package, for

use in incident analysis. You can view this information using the SCF STATUS

SUBNET command. For a local node, SNETMON stores the state of each internal

path within that node. For remote nodes, SNETMON maintains information about the

condition of the external ServerNet message system paths from the local node to all

remote nodes and from all remote nodes to the local nodes.

MSGMON

What does MSGMON do?

MSGMON is a new monitor process that resides in each processor of a server and

executes various functions required by the message system. MSGMON is a helper

for the ServerNet cluster subsystem monitor process (SNETMON). MSGMON handles

communications between SNETMON and individual processors. MSGMON also logs

events from and generates events on behalf of the IPC subsystem. MSGMON was

created to relieve the system monitor subsystem. MSGMON is a persistent process.

Once it is started, it terminates only in the event of an internal failure or a

termination message from the persistence monitor, $ZPM. Unlike SNETMON and

SANMAN, MSGMON is a single process—not a process pair.

Naming and Numbering

Do ServerNet clusters have logical names? No. The ServerNet cluster itself has

no logical name. There is no software function for naming a ServerNet cluster.

However, each node in a ServerNet cluster has a system name.

Do ServerNet clusters have cluster numbers? No. There is no number

associated with a ServerNet cluster as a whole. However, each node in a ServerNet

cluster has a ServerNet node number.

What is a ServerNet node number? A ServerNet node number is a number used

to identify a node within a ServerNet cluster. The node number is unique for each

member, or node, in a ServerNet cluster. You do not configure the ServerNet node

number. This number is assigned automatically, based on the port to which you

connect the node on the cluster switch and the position of the switch in the

topology.

How is a ServerNet node number different from an Expand node number?

The Expand node number, also known as the "system number," is a number in the

range 0 through 254 that identifies a node in an Expand network. You configure this

number when you install a new NonStop™ S-series server and set the system

number. Note that a ServerNet node has both an Expand node number and a

ServerNet node number.

NNA

What is an NNA? NNA stands for "node-numbering agent." An NNA is a

field-programmable gate array (FPGA) contained within some—but not