R3303-HP HSR6800 Routers Layer 3 - IP Routing Configuration Guide

223
*>i 10.0.0.0 2.2.2.2 50 0 300e
* i 3.3.3.3 50 0 200e
* i 1.1.1.1 60 0 200e
BGP load balancing cannot be implemented because load balanced routes must have the same AS-path
attribute.
To enable the comparison of MED of routes from each AS:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view or BGP-VPN
instance view.
• Enter BGP view:
bgp as-number
• Enter BGP-VPN instance view:
a. bgp as-number
b. ipv4-family vpn-instance
vpn-instance-name
Use either method.
3. Enable the comparison of
MEDs for routes on a per-AS
basis.
bestroute compare-med
Optional.
Not enabled by default.
Enabling the comparison of MED of routes from confederation peers
The MED attributes of routes from confederation peers are not compared if their AS-path attributes
contain AS numbers that do not belong to the confederation, such as these three routes: AS-path
attributes of them are 65006 65009, 65007 65009, and 65008 65009, and MED values of them are
2, 3, and 1. Because the third route contains an AS number that does not belong to the confederation,
the first route becomes the optimal route.
To enable the comparison of MED of routes from confederation peers:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view or BGP-VPN
instance view.
• Enter BGP view:
bgp as-number
• Enter BGP-VPN instance view:
a. bgp as-number
b. ipv4-family vpn-instance
vpn-instance-name
Use either method.
3. Enable the comparison of
MED of routes from
confederation peers.
bestroute med-confederation
Optional.
Not enabled by default.
Configuring the NEXT_HOP attribute
By default, when advertising routes to an IBGP peer or peer group, a BGP router does not set itself as the
next hop. However, to ensure a BGP peer can find the correct next hop in some cases, you need to
configure the router as the next hop for routes sent to the peer.