Behavior is different for outbound policies configured for peer groups for which you
have enabled Adj-RIBs-Out. If you change the outbound policy for such a peer group
and want to fill the Adj-RIBs-Out table for that peer group with the results of the new
policy, you must use the
clear ip bgp peer-group
command to perform a hard clear or
outbound soft clear of the peer group. You cannot merely perform a hard clear or
outbound soft clear for individual peer group members because that causes BGP to
resend only the contents of the Adj-RIBs-Out table.
•
Issuing this command automatically removes the
neighbor next-hop-unchanged
configuration (enabled or disabled) on the peer or peer group. Issuing the
no
or
default
version of this command has no effect on the
neighbor next-hop-unchanged
configuration.
•
Use the
no
version to disable this feature (and therefore enable next-hop processing
of BGP updates). Use the
default
version to remove the explicit configuration from
the peer or peer group and reestablish inheritance of the feature configuration.
•
See neighbor next-hop-self.
Assigning a Weight to a Route
You can assign a weight to a route when more than one route exists to the same
destination. A weight indicates a preference for that particular route over the other routes
to that destination. The higher the assigned weight, the more preferred the route. By
default, the route weight is 32768 for paths originated by the router, and 0 for other paths.
In the configuration shown in Figure 31 on page 109, routers Boston and NY both learn
about network 192.68.5.0/24 from AS 200. Routers Boston and NY both propagate the
route to router LA. Router LA now has two routes for reaching 192.68.5.0/24 and must
decide the appropriate route. If you prefer that router LA direct traffic through router
Boston, you can configure router LA so that the weight of routes coming from router
Boston are higher—more preferred—than the routes coming from router NY. Router LA
subsequently prefers routes received from router Boston and therefore uses router Boston
as the next hop to reach network 192.68.5.0/24.
Figure 31: Assigning a Weight to a Neighbor Connection
109
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...