Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Alarm History Report

The Alarm History report is a standardized report generated in Network Director. It shows all active, acknowledged, and cleared alarms that occurred within a specified period of time for the indicated node. The report has two portions: a report header and the report body.

This topic describes:

Alarm History Header

The Alarm History report header provides file creation information about the report. The contents of the report header are described in Table 1.

Table 1: Alarm History Report Header




The type of report—in this case, the Alarm History report.

Generated On

The date and time the report ran. The date format is: [Day of the Month] [Month] [Year]. The time format follows the Coordinated Universal Time (UTC). For example: 07 December 2012 11:35 PM PST.

Generated By

The username of the user that generated the report.

Report Name

The name of the report assigned when the report was created.


The report is generated from this view and node in the network. Perspective can be Logical view, Location view, or Device view of the network. Node represents the selected object upon which the report is based.

Report Filters

The period of time specified for data collection.

Alarm History Tables

The body of the Alarm History report is a set of tables: one table for each alarm state (active, acknowledged, and cleared). In each table the alarms are listed by severity level. The fields of the tables have a common format, which is described in Table 2.

Table 2: Active Alarm History Fields



Alarm Name

The SNMP alarm name.


One of six levels that indicate the gravity of the alarm based on the impact on the system:

  • Critical

  • Major

  • Minor

  • Warning (customer defined)

  • Alert (customer defined)

  • Notice

  • Info


One of twenty-four functional areas:

  • BFD

  • BGP

  • Chassis

  • ClientAndUserSession

  • Configuration

  • CoS

  • DHCP

  • DOM

  • FlowCollection

  • General

  • GenericEvent

  • L2ALD

  • L2CP


  • Misc.

  • PassiveMonitoring

  • Ping

  • RFDetect

  • RMon


  • SonetAPS

  • VirtualChassis


An indication of what caused the alarm.


The Entity ID of the network device sending the trap.


Whether or not the alarm has been acknowledged.

Updated On

The date when the alarm was last updated (assigned, annotated, or acknowledged) otherwise, the date the alarm was created.