To prevent duplicate alert actions, you must either ensure that only one Operations Sentinel server at a time receives notification of alerts, or you must activate a different alert policy on each server.
To prevent the primary and secondary Operations Sentinel servers from performing duplicate external alert actions, note the following considerations:
If an external application generates an alert using an interface such as spo_pipe, you are responsible for coding the application so it sends the events to only one Operations Sentinel server at a time.
[UNIX, Windows]
For the Event Server API clients, this requirement is met automatically since only one Operations Sentinel server receives the events at a time.
[UNIX]
If SP-AMS generates alerts from UNIX and Linux console messages, only one Operations Sentinel server receives the triggering message traffic at a time.
[OS 2200]
If CP-AMS generates alerts for an OS 2200 system from a single console, and only the primary copy of the message is matched, this requirement is met automatically since only one Operations Sentinel server receives the triggering message traffic at a time.
[MCP]
The MCP agent can send concurrent output to two Operations Sentinel servers, which could lead to duplicate alert actions if you use the same alert policy on both Operations Sentinel servers.
[Windows]
The Windows Resource Monitor can send event reports concurrently to two Operations Sentinel servers, which could lead to duplicate alert actions, if you use the same alert policy on more than one Operations Sentinel server.