Smarts MPLS: How does MPLS cross-domain correlation work
Article ID: 331781
Updated On:
Products
Environment
Resolution
When MPLS Manager 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, MPLS Manager focuses its analysis on just the MPLS domain and performs the root-cause analysis.
If it does find such a problem, MPLS Manager 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.
For example, consider device A is discovered in the IP domain. In turn, MPLS domain picks up the device A and performs discovery. At some point, device A in IP domain goes down. This causes the VRF discovered in the MPLS domain for device A to be down as well. This also means that device A discovered in MPLS domain is also down.
In this scenario, the following events appears:
- VRF down event sourced from MPLS domain
- device A down event sourced from MPLS domain
- device A down event sourced from IP domain
From the Global Manager perspective, the VRF down event would be an impact event of the device A down event from MPLS domain. Since the device A down event in IP domain is referencing the same device A down event from MPLS domain, the console would show one common event with two different sources, given that the event name is the same.
Additional Information
Feedback
