Question 790
Following a supported configuration correction, the original issue was: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. Which observation verifies success?
Explanation
Correct Answer
A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table. This confirms the approved response: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF. It is relevant because: SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.
Incorrect Answers
A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state. This would validate ANOTHER scenario: A provider enables SR-MPLS forwarding but assumes each SR-TE path requires RSVP-TE state on every transit router, blocking deployment when RSVP is disabled. The specific correction here is: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.
An isolated service-prefix test traverses the gateway with the expected service context preserved. This would validate ANOTHER scenario: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. The specific correction here is: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.
FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path. This would validate ANOTHER scenario: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. The specific correction here is: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.