Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Alerts and Alarms Overview

An alarm indicates conditions on a device that might prevent the device from operating normally. Alarm conditions for a device are predefined and are raised based on the fault monitoring and performance monitoring (FMPM) being performed on the device. For example, conditions such as hardware issues, drop in throughput and latency of data, temperature variations, and capacity optimization issues automatically trigger an alarm. You can view the alarms raised on the devices on the Alarms page.

You can view alarms raised on both Juniper Networks and Cisco IOS-XR devices. On Juniper Networks devices, you can view alarms for the following conditions:

  • Interface down

  • Chassis alarms

  • High output utilization

  • High input utilization

  • High CPU utilization

  • High memory utilization

  • High storage utilization

  • Fan failure

  • High temperature

For Cisco IOS XR devices running IOS XR Release 7.1.5 and later, you can view alarms defined in the OpenConfig alarm model.

The lifecycle of an alarm includes the following steps:

  • Raise—An alarm is raised when conditions defined in the telemetry manager are met. Paragon Automation stores the alarms and you can view them on the Alarms page.

  • Update—A user views and acknowledges the alarm, and takes the steps required to remediate the conditions in the device that raised the alarm.

  • Clear—The alarm is cleared after the conditions that raised the alarm are normalized.

Besides viewing the alarms details on the Alarms page, you can view alarm statistics on the Paragon Automation dashboard. Paragon Automation dashboard displays the severity of the different alarm types and the alarms history for the previous one hour, one day, one week, one month, and one year.