Alerts and Alarms Overview

You can view alarms raised ond evices on the Alarms (Monitoring > Alarms and Alerts > Alarms) page. 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 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.

Note:

For Cisco IOS XR devices, you must set the default NETCONF port to 22, otherwise, you cannot view alarms.

You can view alarm statistics on the Paragon Automation dashboard. The 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.

You can view alerts that Paragon Automation generates on the Alerts (Monitoring > Alarms and Alerts > Alerts) page. Paragon Automation generates an alert for anomalies in a device group or a network group. You must deploy playbooks on device groups and network groups to monitor specific key performance indicators (KPIs) and detect anomalies. Anomalies incude system errors, protocol errors, interface errors, chassis errors, and other custom configurable KPIs. Paragon Automation also automatically combines several alerts under a main alert, called smart alarm, identifying the root cause of these combined errors and anomalies. These alerts are known as smart alerts. You can receive an alert notification for major events when you configure a notification profile and enable the notification profile in device group and network group settings. See Configure a Notification Profile for more information. You can view minor, major, and normal alerts on the Alerts page. You can also track the KPI associated with an alert from the timeline view, tile view, and table view on the Network Health page.

Table 1 describes the lifecycles of alarms and alerts.

Table 1: Alarm and Alert Lifecycle

Alarms	Alerts
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.	Raise—An alert is raised when an anomaly (for example, KPI exceeds a preset threshold) or a status change (for example, a link goes down) is detected on a device group or network group.
Assign—A user is assigned to check the issue raised by the alarm.	Acknowledge—A user views and acknowledges an alert. The user takes steps to remediate the conditions in the device that generated the alert. An acknowledgment indicates that work is in progress to rectify the error or anomaly.
Acknowledge—A user marks an alarm with the acknowledged status if they have viewed and/or troubleshooting the issue indicated by the alarm.	Shelve— You can set the status of an alert as shelve. Shelve lowers the priority of an alert and snoozes the alert for the time you configure. You can also re-open an alert that is closed or shelved. Or Close—After you resolve the issue raised by an alert, you can set the status of an alert as close. You can also re-open an alert that is closed.
Clear—Paragon Automation automatically clears alarms after the conditions that raised the alarm are normalized.	Delete—To remove an alert from the Alerts page, you can delete the alert.