Alcatel-Lucent 5620 Troubleshooting Manual page 52

3 — Troubleshooting network alarms
2
3
4
5
6
7
8
9
10
11
12
3-14
Note — The list contains an Lsp Down alarm and an Lsp Path Down
alarm. Approximately one half hour later, a second Lsp Down alarm and
a second Lsp Path Down alarm were raised for a total of 18 alarms.
Click on the Object Type column to sort the alarms alphabetically according to
object type.
Scroll through the dynamic alarm list and find the object type that is lowest in the
network object hierarchy, as listed in Table 3-1.
In this example, the lowest-level object type in the alarm list is Lsp Path in the
Path/Routing Management domain. There are two Lsp Path Down alarms. One was
raised later than the other.
Choose the earlier Lsp Path alarm and acknowledge the alarm.
Note — Alarm reporting latency can vary depending on network
conditions. Therefore, the First Time Detected stamp is not a reliable
indication of the exact time an event occurred and should be used only
as an aid in troubleshooting.
Choose the alarms related to this affected object and acknowledge those alarms.
In this case, the only alarm listed under Related Problems is the dynamic Lsp Down
alarm.
View alarm information for the affected object. Double-click on the alarm in the
list to view the information in the Alarm Info form.
Review the information about the alarm.
Lsp Down is a path alarm on MPLS path 53 to 52.
•
The affected object name and site name indicate that the alarm arose on the
•
LSP path from device/site 53 to site 52.
The Site information identifies the site that raised the alarm. The root cause
•
is related to the device with Site Id 10.1.200.53.
Click on the View Alarmed Object button.
Click on the Faults tab button.
On the Alarm Info form, click on the Affected Object tab button and then click on
the View Object button to view state and other information about the object in
the alarm.
In this case, the Administrative State is Up and the Operational State is Down,
which results in an alarm. The Operational State cannot be modified manually.
Check alarm description Table
indicates that the root cause may be a lower object in the managed object
hierarchy.
View the details from the Related tab button on the Alarm Info form to display the
managed objects related to the object in alarm.
November 2008
3-32 for additional information, which in this case,
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Troubleshooting Guide 3HE 04244 AAAB Ed. 01