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.