If you have two or more Operations Sentinel servers, you must first decide on the particular LAN topology that will satisfy your needs.

Operations Sentinel servers A and B can be on the same LAN as in Figure 3–2. In this case, either of the Operations Sentinel servers is capable of controlling any one or all of the connected systems. Whether you choose zones that are exactly alike, totally dissimilar, or a combination depends on how you distribute operations responsibility. Also, you must decide whether or not you require resilient operations.

In Figure 3–3, the systems are separated by a LAN bridge. In addition to local control, LAN bridges and routers enable an operator at one data center to control the systems at another data center, perhaps thousands of miles away.

Although the systems, consoles, Operations Sentinel servers, and Operations Sentinel workstations are physically separated, Operations Sentinel provides the same capabilities as if the hardware were on the same physical LAN.

All Operations Sentinel LAN-based monitoring connections can function across bridges and routers. This means Operations Sentinel Console can access TELNET and Secure Shell (SSH) sessions, OS 2200 systems, MCP systems, Windows systems, and terminal/communications servers on LANs that are connected by a bridge or router.

[OS 2200]

Which Operations Sentinel servers can host an OS 2200 console in a ClearPath Dorado Enterprise System is dictated by a priority list that is defined for each OS 2200 console in Site Configuration and Management System (SCMS) or using the Server Control Client. If the Operations Sentinel server that hosts the OS 2200 console fails, the next Operations Server in the list is requested to rehost the OS 2200 console.

[MCP]

When the Operations Sentinel MCP agent on an MCP system is activated, it opens a service port and waits for a connection request. If the value of Monitor specified for the system in Operations Sentinel Console is true, it attempts to connect with the MCP system.

An agent using the Event Server API opens a connection with the Operations Sentinel server that is identified in its environment. This occurs whether or not Operations Sentinel Console is running.

[UNIX]

UNIX and Linux systems that are connected using a terminal/communications server and the LAN establish connections with an Operations Sentinel server by opening a service port and waiting for a connection request. If the value of Monitor specified for the system in Operations Sentinel Console is true, it attempts to connect with the UNIX or Linux system.

The UNIX/Linux Resource Monitor on each UNIX or Linux system opens a session with the Operations Sentinel server identified in its environment. This occurs whether or not Operations Sentinel Console is running.

An agent using the Event Server API opens a connection with the Operations Sentinel server that is identified in its environment. This occurs whether or not Operations Sentinel Console is running.

[Windows]

The Windows Resource Monitor on each Windows system opens a session with the Operations Sentinel server identified in its environment. This occurs whether or not Operations Sentinel Console is running.

An agent using the Event Server API opens a connection with the Operations Sentinel server that is identified in its environment. This occurs whether or not Operations Sentinel Console is running.