Smarts MPLS: LSP Down on the Destination Router present when Source Router is Down
Article ID: 332035
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
Customer has source routers configured with hundreds of LSP Tunnels. When a router goes down, the NOC team is flood with hundreds of LSP Down events from the destination router.
When the source Router is down, the LSP Down events on the source router become impacts of the Router Down event, but the LSP Down events on the destination router do not become impacts of the Router Down event. They present as root cause when they should not become root cause. Instead they should appear as impacts of the Router Down event. When the issue occurs, not only LSP Destination notifications appearing, but also everything else such as Interface, NetworkConnection, AggregateInterface, AggregateLink and BGPSession.
Customer has source routers configured with hundreds of LSP Tunnels. When a router goes down, the NOC team is flood with hundreds of LSP Down events from the destination router.
When the source Router is down, the LSP Down events on the source router become impacts of the Router Down event, but the LSP Down events on the destination router do not become impacts of the Router Down event. They present as root cause when they should not become root cause. Instead they should appear as impacts of the Router Down event. When the issue occurs, not only LSP Destination notifications appearing, but also everything else such as Interface, NetworkConnection, AggregateInterface, AggregateLink and BGPSession.
Environment
VMware Smart Assurance - SMARTS
Cause
A Down router, would cause all LSP whose status are maintained by the down router to be alerted as Impacted. This is the current design of the Smarts MPLS. All other LSP that have destination to the down Router to be alerted as Down since these LSPs are monitored from other routers which are still up at the time.
Resolution
The application is working as design.
Additional Information
Please collect the following during the issue occurrence to help trouble shoot:
- Collect the MPLS topology log, Analysis log and Monitoring log files
- Collect the domain and audit log files from the SAM (aggregate) domain
- Out of the router from Splunk
- A recording of the LSP Outage
- Observation during the router down event
- Screen shots of the source router showing that all destination notifications are not part of the Router Down event
- Output of router snmp value of the follow 4 oids from the destination end:
mplsLspState = "1.3.6.1.4.1.2636.3.2.3.1.2",
mplsPathRecordRoute = "1.3.6.1.4.1.2636.3.2.3.1.19",
mplsLspInfoState = "1.3.6.1.4.1.2636.3.2.5.1.2",
mplsPathInfoRecordRoute = "1.3.6.1.4.1.2636.3.2.5.1.20"
- Video indicating he destination device it was ran on
- Collect the MPLS topology log, Analysis log and Monitoring log files
- Collect the domain and audit log files from the SAM (aggregate) domain
- Out of the router from Splunk
- A recording of the LSP Outage
- Observation during the router down event
- Screen shots of the source router showing that all destination notifications are not part of the Router Down event
- Output of router snmp value of the follow 4 oids from the destination end:
mplsLspState = "1.3.6.1.4.1.2636.3.2.3.1.2",
mplsPathRecordRoute = "1.3.6.1.4.1.2636.3.2.3.1.19",
mplsLspInfoState = "1.3.6.1.4.1.2636.3.2.5.1.2",
mplsPathInfoRecordRoute = "1.3.6.1.4.1.2636.3.2.5.1.20"
- Video indicating he destination device it was ran on
Feedback
Yes
No
Powered by
