The following table summarizes the resiliency options for OS 2200 partitions monitored by two Operations Sentinel servers, when the primary console fails. In this table, hot standby refers to the ability of the secondary server to receive messages and events from the backup console only when the primary console fails. Concurrent monitoring is the ability of two servers to receive the same console messages and events.
| Information Source | Configuration | Concurrent Monitoring | Hot Standby |
|---|---|---|---|
| OS 2200 console messages | One or multiple consoles per Operations Sentinel server | Partial3 | Yes1 |
| Event reports from CP-AMS | One or multiple consoles per Operations Sentinel server | Configurable2 | Configurable2 |
Notes:
This capability relies on the OS 2200 console handler automatically routing the primary copy of each console message to the backup console, when the primary console fails.
This capability relies on your CP-AMS database distinguishing the primary and echo copies of these messages. By sending the event report to Operations Sentinel for the primary and echo copies of the console message, you have concurrent monitoring. By sending the event report only for the primary copy of the message, you have hot standby.
This capability applies to read-only messages, but not read and reply messages.
The following table summarizes the resiliency options for OS 2200 partitions monitored by two Operations Sentinel servers, when the primary Operations Sentinel server fails. In this case only one Operations Sentinel server remains, so concurrent monitoring cannot continue and you have lost your resiliency.
| Information Source | Configuration | Hot Standby |
|---|---|---|
| OS 2200 console messages | One or multiple consoles per Operations Sentinel server | Yes |
| Event reports from CP-AMS | One or multiple consoles per Operations Sentinel server | Yes |