Router Dublin advertises a MED of 25 for route 192.168.33.0/24, which is
lower—more preferred—than the MED advertised by router Paris or router Nice.
However, the AS path for the route through router Dublin is longer than that through
router Paris. The AS path is the same length for router Paris and router Nice, but the
MED advertised by router Paris is lower than that advertised by router Nice.
Consequently, router London prefers the path through router Paris.
Suppose, however that router Dublin was not configured to set the MED for route
192.168.33.0/24 in its outbound route map 10. Would router London receive a MED
of 50 passed along by router Paris through router Dublin? No, because the MED
attribute is nontransitive. Router Dublin does not transmit any MED that it receives.
A MED is only of value to a direct peer.
bgp always-compare-med
■
Use to enable the comparison of the MED for paths from neighbors in different
ASs.
■
Unless you specify the
bgp always-compare-med
command, the router compares
MED attributes only for paths from external neighbors that are in the same AS.
■
The BGP path decision algorithm selects a lower MED value over a higher one.
■
Unlike local preferences, the MED attribute is exchanged between ASs, but does
not leave the AS.
■
The value is used for decision making within the AS only.
■
When BGP propagates a route received from outside the AS to another AS, it
removes the MED.
■
Example
host1(config-router)#
bgp always-compare-med
■
Changes apply automatically whenever BGP subsequently runs the best-path
decision process for a destination prefix; that is, whenever a best route is picked
for a given prefix.
To force BGP to run the decision process on routes already received, you must
use the
clear ip bgp
command to perform an inbound soft clear or hard clear
of the current BGP session.
■
Use the
no
version to disable the feature.
■
See bgp always-compare-med.
set metric
■
Use to set the metric value—for BGP, the MED—for a route.
■
Sets an absolute metric. You cannot use both an absolute metric and a relative
metric within the same route map sequence. Setting either metric overrides any
previously configured value.
■
Example
host1(config)#
route-map nyc1 permit 10
host1(config-route-map)#
set metric 10
124
■
Selecting the Best Path
JUNOSe 11.0.x BGP and MPLS Configuration Guide
Summary of Contents for JUNOSE
Page 6: ...vi...
Page 8: ...viii JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 24: ...xxiv Table of Contents JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 37: ...Part 1 Border Gateway Protocol Configuring BGP Routing on page 3 Border Gateway Protocol 1...
Page 38: ...2 Border Gateway Protocol JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 234: ...198 Monitoring BGP JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 236: ...200 Multiprotocol Layer Switching JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 298: ...262 Point to Multipoint LSPs Configuration JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 536: ...500 Monitoring BGP MPLS VPNs JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 538: ...502 Layer 2 Services Over MPLS JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 604: ...568 Virtual Private LAN Service JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 618: ...582 VPLS References JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 674: ...638 Virtual Private Wire Service JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 718: ...682 Monitoring MPLS Forwarding Table for VPWS JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 719: ...Part 6 Index Index on page 685 Index 683...
Page 720: ...684 Index JUNOSe 11 0 x BGP and MPLS Configuration Guide...