Question 70
Following a supported configuration correction, the original issue was: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. Which observation verifies success?
Explanation
Correct Answer
Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels. This confirms the approved response: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. It is relevant because: Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.
Incorrect Answers
A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments. This would validate ANOTHER scenario: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.
FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF. This would validate ANOTHER scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.
Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path. This would validate ANOTHER scenario: A router's MPLS TTL propagation policy differs from its neighboring core nodes, and traceroute unexpectedly exposes or hides provider hops relative to the service contract. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.