How alarms are triggered

Once every minute, Plixer Replicator scans all interfaces in either direction (Rx and Tx).

If packet drops are observed, the system will continue to monitor the exporter or collector associated with the drops and flag it as down if it remains inactive. This will trigger an alarm for the resource and any profile it has been assigned to.

Alarms are also triggered by high CPU usage or abnormal process termination.

Note

• Statistics reported in the Plixer Replicator web interface are a good reference for packet activity but not packet drops.

• The amount of time before an inactive exporter or collector is flagged is down is controlled by the Alarm Tolerance setting in the Settings tab of the UI.

• The CPU utilization percentage that will trigger an alarm is controlled by the CPU Threshold setting in the Settings tab of the UI.