Cisco ONS 15310-MA Troubleshooting Manual page 16

Trouble Notifications
2.5.3 Severities
The ONS 15310-MA SDH use Telcordia-devised standard severities for alarms and conditions:
Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA) and Not Reported (NR). These are
described as follows:
•
•
•
•
•
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 ONS15310-MA 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 a
path trace identifier mismatch (HP-TIM) is raised on a circuit path and then a loss of pointer on the path
(AU-LOP) is raised on the path, the AU-LOP alarm stands and the HP-TIM closes. The path alarm
hierarchy used in the ONS 15310-MA SDH systems is shown in
Table 2-9
Priority
Highest
—
—
Lowest
Cisco ONS 15310-MA SDH Troubleshooting Guide, Release 9.0
2-16
A Critical (CR) alarm generally indicates severe, Service-Affecting (SA) trouble that needs
immediate correction. Loss of traffic on an VC3, which can hold 28 E1 circuits, would be a
Critical (CR), Service-Affecting (SA) alarm.
A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For example,
loss of traffic on more than five E1 circuits is Critical (CR), but loss of traffic on one to four E1
circuits is Major (MJ).
Minor (MN) alarms generally are those that do not affect service. For example, the automatic
protection switching (APS) byte failure (APSB) alarm indicates that line terminating equipment
(LTE) detects a byte failure on the signal that could prevent traffic from properly executing a traffic
switch.
Not Alarmed (NA) conditions are information indicators, such as for the free-run synchronization
state (FRNGSYNC) or a forced-switch to primary timing source event (FRCSWTOPRI). They could
or could not require troubleshooting, as indicated in the entries.
Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm
indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or
MJ) alarm occurs upstream. These conditions do not in themselves require troubleshooting, but
usually accompany primary alarms.
section. Procedures for customizing alarm severities are located in the "Manage
Path Alarm Hierarchy
Condition Type
AU-AIS
AU-LOP
HP-UNEQ
HP-TIM
Chapter 2 Alarm Troubleshooting
Table 2-9.
78-18663-01