3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-15
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
8 Review the information about the alarm. In this example,
• The Equipment Down alarm is a Physical Port alarm in the Equipment domain.
• The device at Site ID 10.1.200.52. raised the alarm on object Port 1/1/2.
• The alarm cause is inoperable equipment.
9 Check the port states. Click on the Affected Objects tab button, 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.
10 The root cause is indicated by the probable cause of alarm on the affected object:
physical Port 1/1/2 at site ID 10.1.200.52 is inoperable.
The dynamic alarm list also indicates that a second port on site 10.1.200.52, Port
1/1/3, is down. This port forms LAG 2 with port 1/1/2 and LAG 2 is down.
11 For equipment alarms, use the navigation tree view to identify the extent of the
problem. Locate ports 1/1/2 and 1/1/3 under the Shelf object that supports LAG
2 at Site 10.1.200.52. The state for each port is operationally down. The tree view
displays the aggregated alarms on objects up to the Router level.
A related LAG, LAG 1, is down but the alarms on LAG 2 ports were detected first.
Procedure 3-8 To clear alarms related to an equipment problem
This procedure describes how to clear the 22 alarms from the sample problem in this
section. The troubleshooting process determined that two physical ports in LAG 2 at
Site 10.1.200.52. are operationally down.
1 Check the physical connection to the port. The physical inspection shows that the
two port connections supporting LAG 2 at Site 10.1.200.52. are not properly
seated.
2 Seat the port connections. The 22 alarms, including the second two physical port
Equipment Down alarms on LAG 1, automatically clear.
Troubleshooting an underlying port state problem
An underlying port state problem in the sample network produces the list of alarms
shown in Figure 3-7.
To Next Page
Loading...
