If you set the value of Monitor for a system to true, the Operations Sentinel server attempts to connect with the system. You can set the value on Monitor independently for different Operations Sentinel servers.
In networks with multiple Operations Sentinel servers, connections to managed systems are subjected to the following constraints. These constraints are true whether the multiple servers are on the same LAN, or on multiple LANs connected by LAN bridges or routers.
You must ensure that each system and console establishes a connection to the desired server.
[OS 2200]
An OS 2200 console in a ClearPath Dorado Enterprise System is hosted on one Operations Server at a time. However, other Operations Sentinel servers can request the Operations Server that hosts the console to forward the message traffic of the console. That way, many Operations Sentinel servers can manage an OS 2200 partition in a ClearPath Enterprise System, each with its own set of policies.
[MCP]
Each instance of the Operations Sentinel MCP agent running on an MCP system can communicate with one or two Operations Sentinel servers at a time. Therefore, you can simultaneously access an MCP system from two Operations Sentinel servers when you are running a single instance of the agent. By installing and running a second instance of the agent, you can access the MCP system from one or two additional Operations Sentinel servers.
[UNIX]
Each connection to a UNIX or Linux system can communicate with only one Operations Sentinel server at a time. The connection can be either a terminal/communications server to a serial port on the UNIX or Linux system, or a direct serial connection from the Operations Sentinel server to the UNIX or Linux system.
For a direct serial connection, only the Operations Sentinel server that is part of that connection can monitor the system. You can establish another direct serial connection from another monitoring port on the UNIX or Linux system to another Operations Sentinel server. That is a separate connection that processes different, although perhaps similar, information.
A physical connection through a terminal/communications server can move to another Operations Sentinel server, after it has been released by the first Operations Sentinel server, if the second server is waiting for the connection. Therefore, if a UNIX or Linux system connection with a terminal/communications server is being monitored by at least one Operations Sentinel server, you cannot simultaneously access that system using that connection from any other server. You can, however, configure multiple connections either through a terminal/communications server or a direct serial connection to the same UNIX or Linux system. These are treated as distinct systems by Operations Sentinel.
You can also configure one or more TELNET, SSH, or ping connections to a UNIX or Linux system from one or more Operations Sentinel servers. These function independently of each other, as each is configured and treated as a separate and unique UNIX or Linux system, even though they might actually connect to the same UNIX or Linux system.
[Windows]
Each Windows system can communicate with one or two Operations Sentinel servers at a time. Therefore, if a Windows system has a currently active connection with a server, then you can simultaneously access it from a second server.