Question 720
To prevent recurrence of this provider network issue: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Which control should be retained?
Explanation
Correct Answer
Include transport and service-layer OAM in VPN fault playbooks. This helps prevent recurrence of the issue: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Acceptance evidence should be: The test isolates a healthy transport LSP from a missing inner VPN route or label binding.
Incorrect Answers
Measure end-to-end label-stack MTU at every new pseudowire deployment. That is a sensible control for ANOTHER scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.
Monitor protected-session status and route-to-transport-loopback reachability. That is a sensible control for ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.
Record reoptimization stability and path-change rate in monitoring. That is a sensible control for ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.