ServerNet Cluster Manual

Planning for Installation
ServerNet Cluster Manual—520575-003
2-33
Planning for the Dedicated OSM or TSM LAN
servers in a ServerNet cluster, provided the servers are located close enough for
the Ethernet cables to reach.
•
A public LAN connected to the E4SAs or FESAs in each NonStop S-series server
can be constructed to include all the nodes in a ServerNet cluster. There are no
restrictions to the types of servers or workstations that can participate in this LAN.
However, a system console connected to a public LAN can run only the OSM
Service Connection, TSM Service Application, or the Event Viewer applications.
These considerations are described in more detail in the following subsections:
•
Single-System Logon for OSM and TSM Applications on page 2-33
•
Using Multiple Copies of a OSM or TSM Application on page 2-35
•
Supported LAN Configurations for OSM and TSM on page 2-27
Single-System Logon for OSM and TSM Applications
OSM and TSM applications have an important operating restriction: you can log on to
and manage resources on only one system at a time. In addition, you can log on to a
system only if the system and the system console you are using belong to the same
Ethernet LAN.
In Figure 2-14, each node in the ServerNet cluster has a system console. And each
system console can display some generic ServerNet cluster information. For example,
OSM or TSM client applications communicate with SNETMON using SPI to obtain
information such as the identity of other nodes in the ServerNet cluster.
But because each LAN in this configuration services only a single system, its system
console can perform system management tasks (for example, viewing alarms on
components or loading processors) only on a single system. For example, the system
console connected to \A cannot perform management tasks on \D. The LAN
configurations prevent you from managing resources on systems not connected to the
same LAN as the system console you are using.