specify that a route with any MED value is always preferred to a route that is missing the
MED value.
bgp bestpath missing-as-worst
•
Use to set a missing MED value to infinity, the least preferred value.
•
After issuing this command, a route missing the MED is always preferred less than any
route that has a MED configured.
•
Example
host1(config-router)#
bgp bestpath missing-as-worst
•
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 restore the default condition, where a missing MED value is set
to 0, the most preferred value.
•
See bgp bestpath missing-as-worst.
Comparing MED Values Within a Confederation
A BGP speaker within a confederation of sub-ASs might need to compare routes to
determine the best path to a destination. By default, BGP does not use the MED value
when comparing routes originated in different sub-ASs within the confederation to which
the BGP speaker belongs. (Within the confederation, routes learned from different
sub-ASs are treated as having originated in different places.) You can use the
bgp
bestpath med confed
command to force MED values to be taken into account within a
confederation.
bgp bestpath med confed
•
Use to specify that BGP take into account the MED when comparing routes originated
in different sub-ASs within the confederation to which the BGP speaker belongs.
•
This command does not affect the comparison of routes that are originated in other
ASs and does not affect the comparison of routes that are originated in other
confederations.
•
Example
host1(config-router)#
bgp bestpath med confed
•
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.
Copyright © 2010, Juniper Networks, Inc.
122
JunosE 11.2.x BGP and MPLS Configuration Guide
Summary of Contents for JUNOSE 11.2.X BGP AND MPLS
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 38: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 192: ...Copyright 2010 Juniper Networks Inc 156 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 242: ...Copyright 2010 Juniper Networks Inc 206 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 244: ...Copyright 2010 Juniper Networks Inc 208 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 310: ...Copyright 2010 Juniper Networks Inc 274 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 356: ...Copyright 2010 Juniper Networks Inc 320 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 418: ...Copyright 2010 Juniper Networks Inc 382 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 524: ...Copyright 2010 Juniper Networks Inc 488 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 544: ...Copyright 2010 Juniper Networks Inc 508 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 608: ...Copyright 2010 Juniper Networks Inc 572 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 672: ...Copyright 2010 Juniper Networks Inc 636 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 674: ...Copyright 2010 Juniper Networks Inc 638 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 716: ...Copyright 2010 Juniper Networks Inc 680 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 717: ...PART 6 Index Index on page 683 681 Copyright 2010 Juniper Networks Inc...
Page 718: ...Copyright 2010 Juniper Networks Inc 682 JunosE 11 2 x BGP and MPLS Configuration Guide...