Question 400
An IPv6 packet exceeds an underlay path MTU and the operator expects intermediate IPv6 routers to fragment it. What should the operations engineer do first to address the stated fault?
Explanation
Correct Answer
Correct diagnosis: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. The appropriate action is: Review IPv6 path MTU discovery and endpoint fragmentation requirements. The follow-up evidence required is: The sender adapts to a validated path MTU and payload delivery succeeds.
Incorrect Answers
This answer would be more suitable when an engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context, where the corrective action is to apply and verify supported route policy at the intended routing import or export boundary. The failure here is different: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Required validation: The sender adapts to a validated path MTU and payload delivery succeeds.
More-specific routes can override an otherwise healthy IPv6 fallback describes a neighboring protocol concern. In this case the controlling fact is intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. A correct remediation would review IPv6 path MTU discovery and endpoint fragmentation requirements and demonstrate: The sender adapts to a validated path MTU and payload delivery succeeds.
The proposed principle concerns another network fault: BGP family negotiation and route policy control IPv6 NLRI exchange. Here, intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. The most direct correction is to review IPv6 path MTU discovery and endpoint fragmentation requirements, confirmed by the sender adapts to a validated path MTU and payload delivery succeeds.