Table of Contents
Advertisement
Command Reference Guide
BGP AF Neighbor Command Set
BGP updates are stored prior to filtering; thus, allowing the clear bgp soft command to be used in the
absence of route refresh (RFC 2918) capability. The unfiltered table is used when an inbound policy is
changed; allowing the router to immediately implement policy changes immediately based on the stored
table instead of having to wait on a new table to be built after a hard reset. A soft reset is beneficial over a
hard reset because it allows policy updates without disrupting network traffic flow. A hard reset terminates
the existing BGP session, effectively removing all routes learned from a neighbor. A new session is then
created and all of the routes must be relearned. Due to the fact that this process takes place with a hard
reset, a network outage can potentiality occur until the BGP database and route table have been rebuilt.
Refer to
clear bgp on page 91
for more information.
Usage Examples
The following example enables the unit to store BGP updates for the IPv4 BGP AF neighbor on the default
VRF instance:
(config)#router bgp 100
(config-bgp)#address-family ipv4
(config-bgp-ipv4)#neighbor 192.22.73.101
(config-bgp-ipv4-neighbor)#soft-reconfiguration inbound
The following example enables the unit to store BGP updates for the IPv4 BGP AF neighbor on the
nondefault VRF instance named RED1:
(config)#vrf RED1 route-distinguisher ip 192.17.250.24:33
(config)#router bgp 100
(config-bgp)#vrf RED1
(config-bgp-vrf)#address-family ipv4
(config-bgp-vrf-ipv4)#neighbor 10.20.1.1
(config-bgp-vrf-ipv4-neighbor)#soft-reconfiguration inbound
60000CRG0-35E
Copyright © 2012 ADTRAN, Inc.
2934
Advertisement
Table of Contents
