Using Administration mode of Operations Sentinel Console, you can control which Operations Sentinel servers in a resilient environment connect with each system or console.
[MCP]
By setting the Monitor property to True for an MCP system on two Operations Sentinel servers, you can enable concurrent output to both servers from this MCP system. By running both a production instance and a test instance of the MCP agent, each of which can send concurrent output to two servers, you can enable concurrent monitoring by maximum of four Operations Sentinel servers.
[OS 2200, UNIX, Windows]
Assume that Figure 18–6 represents your Operations Sentinel network. Also, assume that OS 2200 consoles attached to system A initially connect to Operations Sentinel server A, and that systems B and C (Windows, UNIX, or Linux) initially connect to server B.
You can set up an environment so that if one Operations Sentinel server fails, all system consoles and systems currently connect to the failing server are automatically switched to and connected to the other server. The following steps are one way to do this:
Ensure that the configuration in both Operations Sentinel servers includes all systems and system consoles shown in Figure 18–6.
On server A, use Operations Sentinel Console to set the Monitor property to True for system consoles 1, 2, and 3 of system A. Set the Monitor property to False for systems B and C.
Now the consoles for system A are connected to server A and the Connection Status window indicates Active for each console.
On server B, use Operations Sentinel Console to set the Monitor property values to the opposite of those set for server A (False for system consoles 1, 2, and 3 of system A, and True for systems B and C).
Now systems B and C are connected to server B and the Connection Status window indicates Active for each system.
After each Operations Sentinel Console server is connected to the systems and consoles it is initially monitoring, set the Monitor property to True for each remaining system and console in each instance and save the changes. This allows each Operations Sentinel server to manage its portion of the data center, but each is prepared to manage the other portion of the data center, if necessary.
For example, for server A, the Connected Systems & Consoles view of Operations Sentinel Console shows that the systems managed by the server B are busy.
If one of the Operations Sentinel servers fails, the other Operations Sentinel server automatically establishes sessions with the system consoles and systems previously connected to the failing Operations Sentinel server.
Console traffic that is being logged by Operations Sentinel is also automatically switched to the remaining server.
[UNIX]
Only managed systems connected to the Operations Sentinel servers through a terminal/communications server have the resilient characteristics needed to recover a lost connection to the managed system from an alternate Operations Sentinel server.