If the diagnostic determines that a circuit pack has failed, the red
FAULT
LED on that circuit pack is turned on. If an incoming electrical
signal from the DSX fails, the red
FAULT
LED on the affected circuit
pack flashes on and off in one-second intervals. A failed incoming
optical signal has the same effect.
Metropolis
®
DMXplore provides alarm holdoff and clear delays. The
alarm holdoff delays prevent transient failures from causing
unnecessary maintenance activity. The office alarms are not activated,
and the operating systems (OSs) are not notified until a failure lasts at
least as long as the alarm holdoff delay. Alarm clear delays prevent
premature clearing of alarms. Alarm indications are not cleared until a
fault condition has been clear for at least as long as the alarm clear
delay.
Service affecting (SA) vs.
non-service affecting
(NSA)
Metropolis
®
DMXplore declares an alarm service affecting (SA) or
non-service affecting (NSA) based on protection switch status and
entity states. A condition is declared NSA (non-service affecting) if the
system is successfully providing protection switching in response to
the condition, or if the failed entity (circuit pack or signal) is in the
standby (not active) state. If protection switching is not successful, or
if the entity is unprotected, the condition is declared SA (service
affecting).
2waypr example
In 2waypr cross-connections, a single failure is protected by the
system. Under normal conditions, Metropolis
®
DMXplore performs a
UPSR protection switch. Since the failed path is then in the standby
state, the failure does not affect service and the alarm is identified as
NSA. If failure is present on both sides of a UPSR, the standby path
declares an NSA alarm as described above, but the active path
declares a SA alarm. Because the protection path is also failed, the
system cannot switch away from the failed signal.
Alarm masking
Metropolis
®
DMXplore automatically masks (suppresses the reporting
of) secondary or consequential conditions, allowing the operator to
quickly identify the root cause of a problem and the services that are
affected.
To minimize the number of alarm conditions reported by an NE,
related alarms/status conditions are arranged in hierarchical groups.
When more than one alarm or status condition in a hierarchical group
Alarm and status conditions reporting
Maintenance overview
....................................................................................................................................................................................................................................
365-372-333 R2.1
Issue 4, June 2005
Lucent Technologies
4 - 9
