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
•
Use the
no
version to delete the set clause from a route map.
•
See set metric.
Missing MED Values
By default, a route that arrives with no MED value is treated as if it had a MED of 0, the
most preferred value. You can use the
bgp bestpath missing-as-worst
command to
121
Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring BGP Routing
Содержание JUNOSE 11.2.X BGP AND MPLS
Страница 6: ...Copyright 2010 Juniper Networks Inc vi...
Страница 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 38: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 192: ...Copyright 2010 Juniper Networks Inc 156 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 242: ...Copyright 2010 Juniper Networks Inc 206 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 244: ...Copyright 2010 Juniper Networks Inc 208 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 310: ...Copyright 2010 Juniper Networks Inc 274 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 356: ...Copyright 2010 Juniper Networks Inc 320 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 418: ...Copyright 2010 Juniper Networks Inc 382 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 524: ...Copyright 2010 Juniper Networks Inc 488 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 544: ...Copyright 2010 Juniper Networks Inc 508 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 608: ...Copyright 2010 Juniper Networks Inc 572 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 672: ...Copyright 2010 Juniper Networks Inc 636 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 674: ...Copyright 2010 Juniper Networks Inc 638 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 716: ...Copyright 2010 Juniper Networks Inc 680 JunosE 11 2 x BGP and MPLS Configuration Guide...
Страница 717: ...PART 6 Index Index on page 683 681 Copyright 2010 Juniper Networks Inc...
Страница 718: ...Copyright 2010 Juniper Networks Inc 682 JunosE 11 2 x BGP and MPLS Configuration Guide...