BGP soft in - any negative effects?

[PAUL TRIVINO]

I am familiar with inbound soft reconfiguration - but I do not know of any negative impacts this can have.  Can anyone say if there are any negatives about this?

Paul

[Peter Paluch · Accepted solution]

Hi Paul,

To my best knowledge, having inbound soft reconfiguration will increase your memory footprint and may increase the CPU utilization slightly as the BGP code will need to crawl through more entries in its table, skipping the ones-would-be-filtered-out. Otherwise, I am not aware of any outspokenly harmful effects.

Then again, if you do not know exactly you need it, you don't need it BGP implementations support the Route Refresh functionality for years now, and turning the soft reconfiguration on does not bring any additional functionality from the viewpoint of re-applying inbound policies.

Best regards,

Peter

[PAUL TRIVINO]

What I was trying to fix is getting:

ROUTER#sh ip bgp nei a.b.c.d received-routes

% Inbound soft reconfiguration not enabled on a.b.c.d

I have plenty of CPU and memory on the device in question.  Thanks for the reply!

Paul

[Pandu Ranga Rao Upadhyayula]

Route refresh capability consumes the bw by sending messages and the entire adj_rib_out table when ever there is a change in the inbound policy. Where as soft reconfig inbound , applies the modified policy on the routes which are stored separetly on adj_rib_in for that specific neighbor, there by saves bw.

Sent from Cisco Technical Support Android App