Alarm History

Alarm history or the alarm persistence feature enables the maintenance of the history of the port and the path alarms of 48-Port T3/E3 CEM Interface Module.

The history of the port-level and path-level alarms are saved into a file and is retained for monitoring network events.

Alarm History Restrictions

The following restrictions apply for the alarm history feature:

  • Only port and path level alarm history or alarm persistency is supported.

  • Persistence of T1/E1 alarms on a Channelized T3/E3 port is not supported.

  • Two new files are created after each reboot.

  • The primary and secondary log file are created during feature initialization. The primary log file saves 10000 alarms. When the threshold of 10000 alarms in the primary log file is crossed, the subsequent 10000 alarms are saved in the secondary log file. After crossing the threshold of 10000 alarms in the secondary log file, the content of primary log file is cleared and is replaced with the subsequent alarms.

  • When a primary file switches to a secondary file and vice versa, the following happens:

    • An information level syslog message is displayed.
    • An informatory message is written in the file where subsequent alarms are stored.

  • When RSP switchover happens, the alarm history files are not copied to the new active RSP. Two new files are created in the new active RSP.

  • When you re-configure alarm history or alarm persistence feature, two new files are created.

Configuring Alarm History

The configuration of alarm history helps in defining the periodicity or the interval at which the alarm entries are saved in the designated file. To configure alarm history:

enable
configure terminal
service alarm persistency interval <20-600>
end

When alarm history is configured, two log files are created in bootflash:tracelogs in the following format:

<persistent_alarm[1/2][TIME_STAMP(DD_MMMM_YYYY_HH_MM_SSS)].log>

The syslog message is displayed as the following after configuration:

*Jun 15 10:16:51.270: %ALARM_PERSISTENCY-6-ALARM_INFO_PROCESS_CREATE: created
mcprp_spa_persistence_logger process:292
*Jun 15 10:16:51.270: %ALARM_PERSISTENCY-6-ALARM_CHUNK_INFO_CREATED: chunk pool creation
for alarm_info is successful
*Jun 15 10:16:51.270: %ALARM_PERSISTENCY-6-ALARM_CHUNK_QUEUE_CREATED: chunk pool for
alarm_queue is successful
*Jun 15 10:16:51.283: %ALARM_PERSISTENCY-6-ALARM_INFO_FILE_CREATED: Successfully created
/bootflash/tracelogs/persistent_alarm_1.15_June_2016_10_16__270.log file
Router#
*Jun 15 10:16:51.295: %ALARM_PERSISTENCY-6-ALARM_INFO_FILE_CREATED: Successfully created
/bootflash/tracelogs/persistent_alarm_2.15_June_2016_10_16__270.log file
*Jun 15 10:16:52.541: %SYS-5-CONFIG_I: Configured from console by console
Router#

Additional References for Alarm History

Related Documents

Related Topic

Document Title

Cisco IOS commands

Cisco IOS Master Commands List, All Releases

Standards

Standards

Title

There are no standards for this feature.

MIBs

MIB

MIBs Link

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFCs

Title

There are no RFCs for this feature.

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html