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>

Reminder

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

upgrade

Whether NE40s/NE80s Support BGP Route Iteration Load Balancing?

Publication Date:  2013-01-07 Views:  51 Downloads:  0
Issue Description

Whether NE40s/NE80s support BGP route iteration load balancing?

 

Handling Process

NE40s and NE80s running versions of VRP3.10-0426sp01 support BGP route iteration load balancing.

This feature requires establishing multiple links between two routers to implement link backup. When all links function well, traffic can be load balanced.

Two routers establish a BGP peer relationship through each other's loopback interface. Each router's next hop is the BGP peer's loopback interface address. The BGP route destined for the final network segment becomes reachable after being iterated to the router destined for the loopback interface address. The BGP route destined for the loopback interface address has only one next hop. BGP route iteration enables the BGP route to have more next hops than its IGP route and therefore load balances traffic.

NE40s and NE80s support load balancing across the maximum of three links.

 

Root Cause

 

NE40s and NE80s running versions of VRP3.10-0426sp01 support BGP route iteration load balancing.

Solution

 

NE40s and NE80s running versions of VRP3.10-0426sp01 support BGP route iteration load balancing.

END