No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CLI-based Configuration Guide - IP Unicast Routing

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Route Iteration

Route Iteration

Routes can be used to forward traffic only when they have directly connected next hops. However, this condition may not be met when routes are generated. The system then needs to search for directly connected next hops and corresponding outbound interfaces. This process is called route iteration. In most cases, BGP routes, static routes, and user network routes (UNRs) do not have directly connected next hops, and route iteration is required. The following examples demonstrate how route iteration generates an FIB entry.

A next-hop IP address of a BGP route is often the IP address of an indirectly connected peer's loopback interface, and therefore the BGP route needs to be iterated. The system searches the IP routing table for a direct route (an IGP route in most cases) that is destined for the next-hop IP address of the BGP route and then adds the next-hop IP address and outbound interface of the IGP route to the IP routing table. This generates a FIB entry.

A next-hop IP address of a BGP VPN route is often the IP address of an indirectly connected PE's loopback interface, and the BGP route needs to be iterated to a tunnel. The system searches the tunnel list for a tunnel that is destined for this loopback IP address and then adds the tunnel information to the routing table. This generates a FIB entry.

Updated: 2019-12-27

Document ID: EDOC1000174069

Views: 187593

Downloads: 316

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next