3Com Switch 4800G 24-Port Configuration Manual page 373

Select the route originated by the local router
■
Select the route with the shortest AS-PATH
■
Select IGP, EGP, Incomplete routes in turn
■
Select the route with the lowest MED value
■
Select routes learned from EBGP, confederation, IBGP in turn
■
Select the route with the smallest next hop cost
■
Select the route with the shortest CLUSTER_LIST
■
Select the route with the smallest ORIGINATOR_ID
■
Select the route advertised by the router with the smallest Router ID
■
n
CLUSTER_IDs of route reflectors form a CLUSTER_LIST. If a route reflector
■
receives a route that contains its own CLUSTER ID in the CLUSTER_LIST, the
router discards the route to avoid routing loops.
If load balancing is configured, the system selects available routes to
■
implement load balancing.
Route selection with BGP load balancing
The next hop of a BGP route may not be a directly connected neighbor. One of the
reasons is next hops in routing information exchanged between IBGPs are not
modified. In this case, a router finds the direct route via IGP route entries to reach
the next hop. The direct route is called the reliable route. The process of finding a
reliable route to reach a next hop is route recursion.
Currently, the switch supports BGP load balancing based on route recursion,
namely if reliable routes are load balanced (suppose three next hop addresses),
BGP generates the same number of next hops to forward packets. Note that BGP
load balancing based on route recursion is always enabled on the switch rather
than configured using commands.
BGP differs from IGP in the implementation of load balancing in the following:
IGP routing protocols such as RIP, OSPF compute metrics of routes, and then
■
implement load balancing on routes with the same metric and to the same
destination. The route selection criterion is metric.
BGP has no route computation algorithm, so it cannot implement load
■
balancing according to metrics of routes. However, BGP has abundant route
selection rules, through which, it selects available routes for load balancing and
adds load balancing to route selection rules.
n
BGP implements load balancing only on routes that have the same AS_PATH,
■
ORIGIN, LOCAL_PREF and MED.
BGP load balancing is applicable between EBGPs, between IBGPs and between
■
confederations.
If multiple routes to the same destination are available, BGP selects routes for
■
load balancing according to the configured maximum number of load
balanced routes.
BGP Overview 373