Question 710
Following a supported configuration correction, the original issue was: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. Which observation verifies success?
Explanation
Correct Answer
A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes. This confirms the approved response: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation. It is relevant because: VPN routing can preserve stale more-specific or static routes that override newly learned paths.
Incorrect Answers
A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change. This would validate ANOTHER scenario: A CE-PE BGP session successfully exchanges routes but a newly provisioned customer VRF has no route targets and none of its routes propagate to distant PEs. The specific correction here is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.
Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding. This would validate ANOTHER scenario: An L3VPN PE advertises a VPNv4 route but the egress fails to associate the received VPN label with the correct customer VRF, causing the route to appear in the wrong context. The specific correction here is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.
An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree. This would validate ANOTHER scenario: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. The specific correction here is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.