Question 650
At fictional Elmstone Transit, a network engineer supporting operations terminals is reviewing BGP routing, path attributes and EVPN exchange during a planned network scaling change (HCIP-H12-821-BGP-163). The observed network issue is: An operator creates a BGP aggregate but traffic is black-holed because no specific reachable next hop supports it. Which observation most directly verifies that the corrective change succeeded?
Explanation
Correct Answer
The best verification observation is: The aggregate is advertised with working forwarding paths to all intended destinations. It demonstrates the corrective action: Validate supporting component routes and safe aggregate generation or discard behavior. This fits the principle: BGP aggregation must be consistent with actual routed component reachability. Verify on the actual Huawei platform and network release.
Incorrect Answers
“The provider's confirmed accepted policy changes its inbound route choice as agreed” responds to another technical or business failure: An edge router tries to influence its upstream provider's path selection by assigning LOCAL_PREF on an eBGP announcement. That source case depends on: The best verification observation is: The provider's confirmed accepted policy changes its inbound route choice as agreed. The present issue is: An operator creates a BGP aggregate but traffic is black-holed because no specific reachable next hop supports it. The more direct action is “The aggregate is advertised with working forwarding paths to all intended destinations” because the best verification observation is: The aggregate is advertised with working forwarding paths to all intended destinations.
“Both routers reach Established using the planned loopback source and destination” responds to another technical or business failure: An iBGP adjacency to peer loopbacks fails because one side sends TCP from the physical interface address. That source case depends on: The best verification observation is: Both routers reach Established using the planned loopback source and destination. The present issue is: An operator creates a BGP aggregate but traffic is black-holed because no specific reachable next hop supports it. The more direct action is “The aggregate is advertised with working forwarding paths to all intended destinations” because the best verification observation is: The aggregate is advertised with working forwarding paths to all intended destinations.
“Reflected updates carry expected cluster-list information without false loop rejection” responds to another technical or business failure: Two route reflectors use an accidental identical cluster identifier across a design where distinct clusters are required. That source case depends on: The best verification observation is: Reflected updates carry expected cluster-list information without false loop rejection. The present issue is: An operator creates a BGP aggregate but traffic is black-holed because no specific reachable next hop supports it. The more direct action is “The aggregate is advertised with working forwarding paths to all intended destinations” because the best verification observation is: The aggregate is advertised with working forwarding paths to all intended destinations.