• RFC 2918, which describes the dynamic route refresh capability
The dynamic route refresh capability is enabled by default and cannot be disabled. When the device sends a BGP4 OPEN message to a
neighbor, the device includes a Capability Advertisement to inform the neighbor that the device supports dynamic route refresh.
NOTE
The option for dynamically refreshing routes received from a neighbor requires the neighbor to support dynamic route refresh. If
the neighbor does not support this feature, the option does not take eect and the software displays an error message. The
option for dynamically re-advertising routes to a neighbor does not require the neighbor to support dynamic route refresh.
Dynamically refreshing routes
The following sections describe how to refresh BGP4 routes dynamically to put new or changed
lters into eect.
To request a dynamic refresh of all routes from a neighbor, enter a command such as the following.
device(config-bgp-router)# clear ip bgp neighbor 192.168.1.170 soft in
This command asks the neighbor to send its BGP4 table (Adj-RIB-Out) again. The device applies its lters to the incoming routes and
adds, modies, or removes BGP4 routes as necessary.
Syntax: clear ip bgp neighbor all | ip-addr | peer-group-name | as-num [ soft-outbound | soft [ in | out ] ]
The all , ip-addr , peer-group-name , and as-num parameters specify the neighbor. The ip-addr parameter species a neighbor by its IP
interface with the device. The peer-group-name species all neighbors in a specic peer group. The as-num parameter species all
neighbors within the specied AS. The all parameter species all neighbors.
The soft-outbound parameter updates all outbound routes by applying the new or changed lters, but sends only the existing routes
aected by the new or changed lters to the neighbor.
The soft in and soft out parameters specify whether you want to refresh the routes received from the neighbor or sent to the neighbor:
• soft in does one of the following:
– If you enabled soft reconguration for the neighbor or peer group, soft in updates the routes by comparing the route
policies against the route updates that the device has stored. Soft reconguration does not request additional updates from
the neighbor or otherwise aect the session with the neighbor.
– If you did not enable soft reconguration, soft in requests the entire BGP4 route table for the neighbor (Adj-RIB-Out), then
applies the lters to add, change, or exclude routes.
– If a neighbor does not support dynamic refresh, soft in resets the neighbor session.
• soft out updates all outbound routes, then sends the entire BGP4 router table for the device (Adj-RIB-Out) to the neighbor,
after changing or excluding the routes aected by the lters.
If you do not specify in or out , the device performs both options.
NOTE
The soft-outbound parameter updates all outbound routes by applying the new or changed lters, but sends only the existing
routes aected by the new or changed lters to the neighbor. The soft out parameter updates all outbound routes, then sends
the entire BGP4 route table for the device (Adj-RIB-Out) to the neighbor, after changing or excluding the routes aected by the
lters. Use soft-outbound if only the outbound policy is changed.
To dynamically resend all the device BGP4 routes to a neighbor, enter a command such as the following.
device(config-bgp)# clear ip bgp neighbor 192.168.1.170 soft out
This command applies lters for outgoing routes to the device BGP4 route table (Adj-RIB-Out), changes or excludes routes accordingly,
then sends the resulting Adj-RIB-Out to the neighbor.
Displaying BGP4 information
FastIron Ethernet Switch Layer 3 Routing
472 53-1003627-04