•
This command takes effect immediately.
•
There is no
no
version.
•
See clear bgp ipv6.
•
See clear ip bgp.
Changing Policies Without Disruption
Changing policies can cause major network disruptions when you bring down sessions
to reapply the modified policies. You can use either of the methods in this section to
minimize network disruptions.
Soft Reconfiguration
You can use
soft reconfiguration
to enable the nondisruptive reapplication of inbound
policies. Issuing the command causes the router to store copies of the routes received
from the specified peer or from all members of the specified peer group. The route copies
are stored unmodified, before application of inbound policies.
If you then change your inbound policies, you can apply them to the stored routes without
clearing your BGP sessions—and causing network disruptions—by issuing the
clear ip
bgp soft in
command.
neighbor soft-reconfiguration inbound
•
Use to initiate the storage of copies of routes received from the specified IP address
or from all members of the specified peer group.
•
Use with the
clear ip bgp soft in
command to reapply inbound policies to stored routes
without clearing the BGP sessions.
•
Example
host1(config)#
router bgp 37
host1(config-router)#
neighbor 192.168.1.1 remote-as 42
host1(config-router)#
neighbor 192.168.1.1 soft-reconfiguration inbound
•
If you specify a BGP peer group by using the
peerGroupName
argument, all the members
of the peer group inherit the characteristic configured with this command unless it is
overridden for a specific peer.
•
If the route-refresh capability was negotiated with the peer, BGP immediately sends
a route-refresh message to the peer to populate the Adj-RIBs-In table.
If the route-refresh capability was not negotiated with the peer, BGP automatically
bounces the session. The Adj-RIBs-In table is repopulated when routes are received
from the peer after the session comes back up.
•
Use the
no
version to disable storage of the route copies. Use the
default
version to
remove the explicit configuration from the peer or peer group and reestablish inheritance
of the feature configuration.
•
See neighbor soft-reconfiguration inbound.
97
Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring BGP Routing
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...