Using BGP session resets destabilizing BGP and the BGP route refresh message.

We create a soft reconfiguration database and incoming prefixes are stored in the database.

So now , these(prefixes) are stored before our incoming policy is applied.

Policy changes can then be applied to the prefixes in the database without causing any disruptions.

To configure in use

neighbor x.x.x.x sot-reconfiguration inbound

This will create soft configuration of the neighbor's database and store prefixes in it.

To make changes

clear ip bgp soft in

To resend a prefix to neighbor without a session reset

clear ip bgp soft out

clear ip bgp soft (in both directions)

Route Refresh

Eliminates

need to store incoming prefixes

reset BGP sessions

BGP ROUTE refresh messsage

Any time we change our policy , we can send out a route refresh message to the neighbor and request them to resend their prefixes.

Route refresh capability is negotiated during session establishment.

The Outbound Route Filtering Capability defined in [BGP-ORF] provides a mechanism for a BGP speaker to send to its BGP peer a set of Outbound Route Filters (ORFs) that can be used by its peer to filter its outbound routing updates to the speaker