MPLS cross-domain
impact correlation analysis overview
MPLS failures, or apparent
failures, that are detected by
cannot be analyzed in isolation. Rather, those failures must be correlated with
the physical-transport failures that are detected by
IP Availability Manager
, or the BGP failures that are detected by
, in order to determine the root-cause problem that is
underlying all observed symptoms.
analyzes MPLS, physical-transport, and BGP failures to determine whether an
MPLS failure is indeed a root-cause problem, or simply a symptom (impact) of an
underlying physical-transport or BGP root-cause problem.
When
detects an MPLS alarm, it checks for any physical-transport or BGP problem that
might be causing the alarm. If it does not find such a problem,
focuses its analysis on just the MPLS domain and performs the root-cause
analysis described in
Chapter 3, “MPLS, VPN, and BGP
Objects and their Failures.”
If it does find such a problem,
diagnoses the MPLS alarm as an impact and exports the underlying
physical-transport or BGP problem and the MPLS impact to the
Global Manager
.
The
Global Manager
responds by adding the MPLS impact as an impact of the underlying
physical-transport or BGP root-cause problem.
MPLS and global impact
analysis shows the flow of information between the components in an
deployment to achieve MPLS and global impact analysis.
MPLS and global
impact analysis

Status updates
received from IP Availability Manager identifies the
IP Availability Manager
statuses to which
subscribes.
Object
| Problem-type status
| Event-type status
|
|---|---|---|
UnitaryComputerSystem Router
1 Switch and so on
| Unresponsive (event) 2
| |
Card
| Down (problem)
| |
NetworkAdapter Interface 1 Port
| Disabled (problem)
AdminStatus
(attribute)(to detect Down problem)
IsFlapping
(attribute)(to detect Unstable problem)
| |
NetworkConnection Cable
1 TrunkCable
| DownOrFlapping (event) 2
| |
1**Indentation
indicates class hierarchy.
2**Declared a
problem-type status by
.
| ||
Status updates
received from Network Protocol Manager for BGP identifies the
statuses to which
subscribes.
Object
| Problem-type status
| Event-type status
|
|---|---|---|
BGPService
| Down
| |
BGPProtocolEndpoint
| Disabled
| |
RemoteASMismatch
| ||
RemoteSystemNotRunning
| ||
RemoteSpeakerNotConfigured
| ||
IBGPPeerMissing
| ||
BGPSession
| Down
|
imports status information from
IP Availability Manager
and
through a remote repository (proxy) accessor, as shown in
Remote repository
accessor operation for MPLS Manager.
Remote repository
accessor operation for

Adding
IP Availability Manager
as a source to
causes
to
import topology and status from the
IP Availability Manager
. The
and the
provide instructions for
completing this task.
Adding
as a source to
causes
to
import status from the
. The
provides instructions for completing
this task.