A community college district must adjust inbound BGP policy without flapping sessions. Which contrast should they recall between soft reconfiguration and route-refresh?
Select an answer to reveal the explanation.
Short Explanation
Soft-reconfig inbound is keeping a full carbon copy of everything the peer said so you can re-filter offline—handy but memory-hungry. Route-refresh is calling the peer and saying ‘send that again’ after a policy change, without dropping the session. Same goal, different storage bill.
Full Explanation
Soft reconfiguration inbound retains a pre-policy copy of received routes so new inbound filters can be applied without a session reset, at the cost of additional memory. Route-refresh (dynamic capability) asks the peer to resend Adj-RIB-In so policy can be re-evaluated without that permanent extra store. Neither should be confused with a hard clear that drops TCP. Prefer route-refresh when peers support it; use soft-reconfig when they do not and memory allows.