Question 660
A core network change board wants to avoid: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. Which ongoing safeguard fits best?
Explanation
Correct Answer
Test locator route advertisement whenever new SRv6 functions are provisioned. This helps prevent recurrence of the issue: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. Acceptance evidence should be: A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint.
Incorrect Answers
Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.
Monitor adjacency SID changes and invalidate stale policy segment lists. That is a sensible control for ANOTHER scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.
Inspect label-stack depth and disposition at each egress after LDP or BGP changes. That is a sensible control for ANOTHER scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.