exists in a single NE, only the top level condition in that hierarchy is
reported.
As a result, Metropolis
®
DMXplore reports alarm conditions that
either
•
are (or might be) directly actionable at the NE, OR
•
do (or might) affect service to a customer.
Metropolis
®
DMXplore does NOT report (in other words,
Metropolis
®
DMXplore masks) alarm conditions that are both
•
the direct consequence of another condition that is detected and
reported by the system, AND
•
not actionable; that is, cannot be repaired or corrected directly,
but can be repaired or corrected by clearing the other condition
of which this condition is a direct consequence.
Important! Service affecting (SA) inc. VT AIS and inc. STS1
AIS alarms are never masked.
Pre-existing lower-level alarms within a hierarchical group are
masked (cleared from the alarm list) when a higher level alarm is
detected and reported.
Example
Consider a DS1 service for which VT1.5 UPSR protection is
provided.
1.
An STS-1 AIS is detected on the associated STS-1 tributary on
one side of the ring and the condition is reported as a
non-service-affecting inc. STS-1 AIS.
2.
A VT AIS is generated in response to the STS-1 AIS. This
condition is masked (not reported) because it is internally
generated by a reported condition and it is not service affecting
(because the system automatically switches to the signal received
on the other side of the ring).
3.
The system then detects a VT1.5 AIS on the signal received on
the other side of the ring. Because the system is not able to
switch to the other side of the ring, this second VT1.5 AIS is
reported as a service-affecting inc. VT AIS.
Alarm and status conditions reporting
Maintenance overview
....................................................................................................................................................................................................................................
4 - 1 0
Lucent Technologies
365-372-333 R2.1
Issue 4, June 2005
