Soft Reconfiguration
Replay stored unmodified received routes after changing inbound policy.
Two routes and one inbound policy
R1 advertises two host routes to R2. Begin with no inbound policy; both appear in R2’s accepted BGP table. This lab changes MED locally to make policy reprocessing visible.
| Link | First endpoint | Second endpoint |
|---|---|---|
| R1–R2 | GigabitEthernet1 192.0.2.1/30 | GigabitEthernet1 192.0.2.2/30 |
Complete baseline configurations
R1
hostname R1
ip cef
interface Loopback0
ip address 10.255.0.1 255.255.255.255
exit
interface Loopback10
ip address 198.51.100.1 255.255.255.255
exit
interface Loopback11
ip address 198.51.100.2 255.255.255.255
exit
interface GigabitEthernet1
ip address 192.0.2.1 255.255.255.252
no shutdown
exit
router bgp 65001
bgp router-id 10.255.0.1
no bgp default ipv4-unicast
neighbor 192.0.2.2 remote-as 65002
address-family ipv4 unicast
no auto-summary
neighbor 192.0.2.2 activate
network 198.51.100.1 mask 255.255.255.255
network 198.51.100.2 mask 255.255.255.255
exit-address-family
endR2
hostname R2
ip cef
interface Loopback0
ip address 10.255.0.2 255.255.255.255
exit
interface GigabitEthernet1
ip address 192.0.2.2 255.255.255.252
no shutdown
exit
router bgp 65002
bgp router-id 10.255.0.2
no bgp default ipv4-unicast
neighbor 192.0.2.1 remote-as 65001
address-family ipv4 unicast
no auto-summary
neighbor 192.0.2.1 activate
exit-address-family
endR2# show ip bgp
Network Next Hop Metric LocPrf Weight Path
*> 198.51.100.1/32 192.0.2.1 0 0 65001 i
*> 198.51.100.2/32 192.0.2.1 0 0 65001 iPrepare the replay mechanism
router bgp 65002
address-family ipv4 unicast
neighbor 192.0.2.1 soft-reconfiguration inbound
exit-address-familyEnable storage before the advertisements that must be retained. If configured after the session is up, populate the copy through a supported refresh or a planned session restart; the command cannot recreate information already discarded.
Change inbound MED
route-map IN-MED permit 10
set metric 222
exitrouter bgp 65002
address-family ipv4 unicast
neighbor 192.0.2.1 route-map IN-MED in
exit-address-familyR2# clear ip bgp 192.0.2.1 soft inR2# show ip bgp 198.51.100.1/32
BGP routing table entry for 198.51.100.1/32
65001
192.0.2.1 from 192.0.2.1
Origin IGP, metric 222, localpref 100, valid, external, bestThe changed attribute is visible after replay. TCP need not restart, but the resulting routing-policy change can still alter or remove forwarding paths; soft does not promise zero traffic impact.
Compare before-policy and after-policy information
R2# show ip bgp neighbors 192.0.2.1 received-routes
Network Next Hop Metric Path
*> 198.51.100.1/32 192.0.2.1 0 65001 i
*> 198.51.100.2/32 192.0.2.1 0 65001 iThe retained received copy has MED 0; the accepted entry has MED 222. received-routes is not universally available without storage. Retaining unmodified paths costs memory per neighbor; the protocol’s conceptual Adj-RIB-In does not mandate this exact implementation.
Remove the experiment and re-evaluate
router bgp 65002
address-family ipv4 unicast
no neighbor 192.0.2.1 route-map IN-MED in
exit-address-familyR2# clear ip bgp 192.0.2.1 soft inR2# show ip bgp 198.51.100.1/32
BGP routing table entry for 198.51.100.1/32
65001
192.0.2.1 from 192.0.2.1
Origin IGP, metric 0, localpref 100, valid, external, bestIf storage was enabled only for this experiment, remove neighbor soft-reconfiguration inbound after verifying a suitable refresh method remains available.
Key Takeaways
- Inbound policy must be re-evaluated against route information.
- Stored replay and route refresh are different mechanisms.
- Pre-policy storage consumes extra memory.
- Soft outbound refresh regenerates local exports.
- A soft operation can still change forwarding through its new policy.
Protocol and command references
Route refresh · Enhanced refresh · BGP specification · Router-symbol attribution.