Alcatel-Lucent 5620 - Sample Problems; Troubleshooting a Service Equipment Problem

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-13
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
If required, check the Administrative State of the supporting port objects. A port
with Administrative State Down does not generate alarms on the port, card, shelf,
LAG, protocols, or sessions, but generates network path and service alarms. If the
Administrative State is Down, change it to Up.
After the problem is fixed, the correlated alarms should automatically clear.
3.4 Sample problems
Figure 3-5 shows a two-node sample network configured with a VPLS that was used
to create problems and generate alarms. This configuration generates the maximum
number of alarms per problem type because alternate network paths are not available
for self-healing.
Figure 3-5 Sample network
The dynamic alarm list is used to troubleshoot the following types of problems that
are created.
• physical port problem that causes an Equipment Down alarm
• underlying port state problem that causes a number of related alarms at the LSP
level
• configuration problem that causes a Frame Size Problem alarm
Troubleshooting a service equipment problem
A problem in the sample network produces the list of alarms shown in Figure 3-6.
1/1/4 1/1/4
Customer
access
ports
Customer
access
ports
LAG 1/1/2, 1/1/3
10.10.11.1/24
LAG 1/1/2, 1/1/3
10.10.11.2/24
7750 SR
site ID
10.1.200.52/32
7750 SR
site ID
10.1.200.53/32
BGP, OSPF, and MPLS are on each network interface.
17558
Aug 2010
AAAD
8.0 R4