Alarm Hierarchy; Table 2-9 Path Alarm Hierarchy; Table 2-10 Facility Alarm Hierarchy - Cisco ONS 15600 SDH Troubleshooting Manual

2.5.4 Alarm Hierarchy

Severities can be customized for an entire network or for single nodes, from the network level down to
the port level by changing or downloading customized alarm profiles. These custom severities are
subject to the standard severity-demoting rules given in Telcordia GR-474-CORE and shown in the
2.5.4 Alarm Hierarchy
Alarms" chapter in the Cisco ONS 15600 SDH Procedure Guide.
2.5.4 Alarm Hierarchy
All alarm, condition, and unreported event severities listed in this manual are default profile settings.
However in situations when traffic is not lost, such as when the alarm occurs on protected ports or
circuits, alarms having Critical (CR) or Major (MJ) default severities can be demoted to lower severities
such as Minor (MN) or Non-Service-Affecting (NSA) as defined in Telcordia GR-474-CORE.
A path alarm can be demoted if a higher-ranking alarm is raised for the same object. For example, If an
high-order path trace identifier mismatch (HP-TIM) is raised on a circuit path and then an administrative
unit (AU) loss of pointer (LOP) is raised on it, the AU-LOP alarm stands and the HP-TIM closes. The
path alarm hierarchy used in the ONS 15600 SDH system is shown in
Table 2-9
Priority
Highest
—
—
Lowest
Facility (port) alarms also follow a hierarchy, which means that lower-ranking alarms are closed by
higher-ranking alarms. The facility alarm hierarchy used in the ONS 15600 SDH system is shown in
Table
Table 2-10
Priority
Highest
—
—
—
—
—
—
—
—
—
—
—
Cisco ONS 15600 SDH Troubleshooting Guide, R8.0
2-12
section. Procedures for customizing alarm severities are located in the "Manage
Path Alarm Hierarchy
2-10.
Facility Alarm Hierarchy
Condition Type
AU-AIS
AU-LOP
HP-UNEQ
HP-TIM
Condition Type
LOS
LOF
MS-AIS
1
MS-EXC
1
MS-DEG
1
MS-RDI
RS-TIM
AU-AIS
AU-LOP
1
HP-EXC
1
HP-DEG
HP-UNEQ
Chapter 2 Alarm Troubleshooting
Table 2-9.
July 2010