An MCP host can be monitored by more than two Operations Sentinel servers. To do this, you must run two or more instances of the interface software, configure different ports for each copy, and include the following command in the configuration file for the second and subsequent instances.

ALLOW_AUTOMATED_KEYINS NO

This command tells the interface software to ignore MCP commands (implemented using DCKEYIN) from both of the Operations Sentinel servers that connected to it. This ensures that only the Operations Sentinel server connected to the first instance of the interface software is allowed to send commands to the host.

By running a second instance of the interface software, you can have one or two Operations Sentinel servers connected to the host for testing purposes. If the ALLOW_AUTOMATED_KEYINS NO command is in the configuration file, the Operations Sentinel servers that connect to the instance of the interface software using this configuration file are regarded as test servers. All MCP commands issued by a test server are ignored

Using the COMS LOAD file and CONFIG files supplied with the release, you can connect with up to four Operations Sentinel servers. You must define a second port in the services file on the Operations Sentinel server unless you are using Operations Sentinel level 11.x or later and use the second port that is defined during the installation of Operations Sentinel.

For more information on resilient Operations Sentinel environments, see the Operations Sentinel Administration and Configuration Guide.