Configuring Alarm History - Cisco ASR 900 Series Configuration Manual

Configuring Alarm History

• When RSP switchover happens, the alarm history files are not copied to the new active RSP. Two new
• 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#
Verification of Alarm History Configuration
Use the show process | include persis command to verify the validity of the process.
Router#show process | include persis
292 Msi 13F0D4AC
Router#
Verify the contents of the persistent alarm log files using the following commands:
Router#dir bootflash:tracelogs/*persistent*
Directory of bootflash:tracelogs/*persistent*
394172
persistent_alarm_1.15_June_2016_07_46__158.log
394173
persistent_alarm_2.15_June_2016_07_46__158.log
6185086976 bytes total (4867022848 bytes free)
Router#
Router#more bootflash:tracelogs/persistent_alarm_1.15_June_2016_07_46__158.log
At:15_June_2016_07_50__916 contents of persistent_alarm_2.15_June_2016_07_46__158.log are
full, so switched to this file
*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |6 |4
|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_UNEQUIPPED|CLEARED
*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |6 |4
|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_PATH_LOP|RAISED
1-Port OC-192 or 8-Port Low Rate CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.7.x
(Cisco ASR 900 Series)
130
• An information level syslog message is displayed.
• An informatory message is written in the file where subsequent alarms are stored.
files are created in the new active RSP.
-rw- 1606 Jun 15 2016 07:50:39 +00:00
-rw- 6299 Jun 15 2016 07:50:38 +00:00
0 49 010328/12000
Alarm History
0 mcprp_spa_persis