Question 520
For a metro Ethernet service provider, the change record describes: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. What preventive validation should be standard?
Explanation
Correct Answer
Verify IPv4/IPv6 route consistency after partial protocol changes. This helps prevent recurrence of the issue: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. Acceptance evidence should be: The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.
Incorrect Answers
Trend prefix counts and alert before capacity thresholds are reached. That is a sensible control for ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. It is less targeted to this issue than: Verify IPv4/IPv6 route consistency after partial protocol changes.
Tune BFD to observed transport behavior and test at peak utilization. That is a sensible control for ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. It is less targeted to this issue than: Verify IPv4/IPv6 route consistency after partial protocol changes.
Review candidate redistribution tables under a default-deny policy. That is a sensible control for ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. It is less targeted to this issue than: Verify IPv4/IPv6 route consistency after partial protocol changes.