Adding to that,
be careful with soft reconfiguration inbound in newer kernels.
I've seen some new versions (15.2T) that actually seem to look inside 
the input buffer for bgp routes and end up having multiple copies of the 
same route, some w/o proper policy applied to it.
-Carlos
Yuri Bank @ 03/02/2013 06:35 -0300 dixit:
> Yup. soft-reconfiguration required you to store a copy of the
> Adj-RIB-IN, where as the route refresh capability tells the remote
> peer to re-send their Adj-RIB-OUT. But only if the neighbor supports
> it: show ip bgp neighbor <ip>, under "Neighbor capabilities"
>
> -Yuri
>
> On Sun, Feb 3, 2013 at 12:51 AM, Imran Ali <immrccie_at_gmail.com> wrote:
>> hi all
>>
>> i  just to confirm my  understanding of  " bgp route refresh capability "
>> feature
>>
>> previously  we need to issue  :  neighbor   1.1.1.1  soft-reconfiguration
>> inbound command  to apply any policy changes with  out  hard reseting the
>> connection at prot 179
>>
>> with   new route refresh capablity  we  no longer  needed  to issue   "
>> soft-reconfiguration  inbound " command and can   directly & dynamcically
>> issue " *clear ip bpg * in*   "  command
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
-- Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina Blogs and organic groups at http://www.ccie.netReceived on Sun Feb 03 2013 - 16:36:45 ART
This archive was generated by hypermail 2.2.0 : Fri Mar 01 2013 - 07:57:58 ART