Question 550
Following a supported configuration correction, the original issue was: 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. Which observation verifies success?
Explanation
Correct Answer
Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding. This confirms the approved response: Correct the VPN service label allocation and VRF binding on the egress PE. It is relevant because: MPLS VPN service labels identify the egress service context separately from outer backbone transport labels.
Incorrect Answers
A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes. This would validate ANOTHER scenario: 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. The specific correction here is: Correct the VPN service label allocation and VRF binding on the egress PE.
An approved Internet test flow completes both directions without exposing other tenants' internal networks. This would validate ANOTHER scenario: A remote customer site can send packets toward the Internet exit in a shared services VRF but the exit has no return route for the private customer prefix. The specific correction here is: Correct the VPN service label allocation and VRF binding on the egress PE.
The source stream arrives over the expected incoming interface and the RPF check passes. This would validate ANOTHER scenario: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. The specific correction here is: Correct the VPN service label allocation and VRF binding on the egress PE.