H3C S5800 Series Configuration Manual page 224

When advertising a self-originated route to an eBGP peer, a BGP speaker sets the NEXT_HOP
for the route to the address of its sending interface.
When sending a received route to an eBGP peer, a BGP speaker sets the NEXT_HOP for the
route to the address of the sending interface.
When sending a route received from an eBGP peer to an iBGP peer, a BGP speaker does not
modify the NEXT_HOP attribute. If load-balancing is configured, the NEXT_HOP attribute will be
modified. For load-balancing information, see
Figure 6-7 NEXT_HOP attribute
4) MED (MULTI_EXIT_DISC)
The MED attribute is exchanged between two neighboring ASs, each of which does not advertise the
attribute to any other AS.
Similar with metrics used by IGP, MED is used to determine the best route for traffic going into an AS.
When a BGP router obtains multiple routes to the same destination but with different next hops, it
considers the route with the smallest MED value the best route if other conditions are the same. As
shown below, traffic from AS10 to AS20 travels through Router B that is selected according to MED.
Figure 6-8 MED attribute
2.1.1.1
D = 9.0.0.0
Next_hop = 2.1.1.1
MED = 0
EBGP
Router A
EBGP
D = 9.0.0.0
Next_hop = 3.1.1.1
MED = 100
3.1.1.1
AS 10
MED = 100
In general, BGP compares MEDs of routes received from the same AS only.
MED = 0
Router B
IBGP
9.0.0.0
Router D
IBGP
IBGP
Router C
AS 20
BGP Route Selection.
6-7