Alcatel-Lucent 5620 Troubleshooting Manual page 54

Service aware manager
Hide thumbs Also See for 5620:
Table of Contents

Advertisement

Release 12.0 R4 | August 2014 | 3HE 08864 AAAD TQZZA Edition 01
2 — Troubleshooting using network alarms
3
Scroll through the dynamic alarm list and find the object type that is lowest in the
network object hierarchy, as listed in Table 2-1.
In the sample network in Figure 2-1, 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.
4
Choose the earlier Lsp Path alarm and acknowledge the alarm.
5
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
6
list to view the information in the Alarm Info form.
7
Review the information about the alarm.
8
Click on the View Alarmed Object button.
9
Click on the Properties button.
10
On the Alarm Info form, click on the Affected Object tab and then click on the
Properties button to view state and other information about the object in the
alarm.
In the sample network in Figure 2-1, the Administrative State is Up and the
Operational State is Down, which results in an alarm. The Operational State
cannot be modified manually.
11
Check the additional information for the alarm, which in this case indicates that
the root cause may be a lower object in the managed object hierarchy.
12
View the details from the Related tab on the Alarm Info form to display the
managed objects related to the object in alarm.
13
Find the object type that is lowest in the network object hierarchy, as listed in
Table 2-1. The lowest level object is a LAG.
14
Open the equipment view of the navigation tree. It indicates that there are alarms
related to both existing LAGs (Site Id 10.1.200.52 and Site Id 10.1.200.53).
However, there is no LAG alarm in the dynamic alarm list and the LAG State is Up.
2-14
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.
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.
Alcatel-Lucent 5620 Service Aware Manager
Troubleshooting Guide
5620 SAM

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents