Question 140
At fictional Uplands Retail, a network engineer supporting customer edge routers is reviewing BGP routing, path attributes and EVPN exchange during an intersite service activation (HCIP-H12-821-BGP-035). The observed network issue is: A BGP router receives multiple paths and engineering assumes all alternate paths must be installed for forwarding regardless of BGP capability. Which routing, switching, or network principle best explains the appropriate solution?
Explanation
Correct Answer
The governing principle is: BGP can retain multiple paths while installing selected forwarding entries under platform rules. In this scenario, the appropriate action is: Differentiate retained alternatives, chosen best path and supported multipath forwarding configuration. Valid evidence would show: The RIB and FIB reflect only the authorized installed best or multipath routes.
Incorrect Answers
“BGP FSM states distinguish session formation failures from routing-update processing” responds to another technical or business failure: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. That source case depends on: BGP FSM states distinguish session formation failures from routing-update processing. The present issue is: A BGP router receives multiple paths and engineering assumes all alternate paths must be installed for forwarding regardless of BGP capability. The more direct action is “BGP can retain multiple paths while installing selected forwarding entries under platform rules” because BGP can retain multiple paths while installing selected forwarding entries under platform rules.
“eBGP multi-hop peers require explicit control of TTL and loopback reachability” responds to another technical or business failure: Two eBGP routers attempt to peer over loopback addresses separated by several transit hops using the default one-hop behavior. That source case depends on: EBGP multi-hop peers require explicit control of TTL and loopback reachability. The present issue is: A BGP router receives multiple paths and engineering assumes all alternate paths must be installed for forwarding regardless of BGP capability. The more direct action is “BGP can retain multiple paths while installing selected forwarding entries under platform rules” because BGP can retain multiple paths while installing selected forwarding entries under platform rules.
“BGP aggregation must be consistent with actual routed component reachability” responds to another technical or business failure: An operator creates a BGP aggregate but traffic is black-holed because no specific reachable next hop supports it. That source case depends on: BGP aggregation must be consistent with actual routed component reachability. The present issue is: A BGP router receives multiple paths and engineering assumes all alternate paths must be installed for forwarding regardless of BGP capability. The more direct action is “BGP can retain multiple paths while installing selected forwarding entries under platform rules” because BGP can retain multiple paths while installing selected forwarding entries under platform rules.