Troubleshooting The Network Management Domain - Alcatel-Lucent 5620 Troubleshooting Manual

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

Advertisement

Alarms for network objects
The 5620 SAM converts SNMP traps from NEs to events and alarms. You can then
use the 5620 SAM to correlate the events and alarms to the managed object,
configured services and policies. A correlated event or alarm can cause fault
conditions on multiple network objects and services. For example, an alarm raised
for a port failure causes alarms on all services that use that port. You can view the
alarm notification from the 5620 SAM topology maps, service configuration forms,
and customer information form that lists the affected objects.
See chapters
information to troubleshoot a network.
Service problems with no associated alarms
The proper delivery of services requires a number of operations that must occur
correctly at different levels within the service model. For example, an operation such
as the association of packets to a service, VC labels to a service, and each service to
a service tunnel must be performed successfully for the service to pass traffic
according to SLAs.
Even when tunnels are operating correctly and are correctly bound to services, for
example, incorrect FIB information can cause connectivity issues. You can use
configurable in-band or out-of-band packet-based OAM tools to verify that a service
is operational and that the FIB information is correct. Each OAM diagnostic can test
each of the individual packet operations. You must test the packet operation in both
directions.
For in-band, packet-based testing, the OAM packets closely resemble customer
packets to effectively test the forwarding path for the customer. However, you can
distinguish the OAM packets from customer packets, so they remain within the
managed network and are not forwarded to the customer. For out-of-band testing,
OAM packets are sent across some portion of the transport network. For example,
OAM packets are sent across LSPs to test reachability.
See chapter
to troubleshoot your network.

Troubleshooting the network management domain

Troubleshooting the network management domain is a reactive fault-management
process that requires comprehensive knowledge of the following:
5620 SAM database, 5620 SAM main and auxiliary servers, the 5620 SAM-O
interface, and the 5620 SAM client software
Windows and Solaris operating systems
Windows PC and Solaris workstations
TCP/IP networking
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723
AAAD
TQZZA Edition 01
3
and
5
for more information about using the 5620 SAM alarm
4
for more information about using the 5620 SAM service information
Note —
Unless specified otherwise, the term "server" in this
document refers to a 5620 SAM main server to which 5620 SAM
clients connect.
8.0 R4
Troubleshooting Guide
2 — 5620 SAM troubleshooting
Aug 2010
2-3

Advertisement

Table of Contents
loading

Table of Contents