[c-nsp] Continous BGP session resets on SRD3

[Tima Maryin]

Rodney Dunn wrote:
> We are working to get some clarification on this.
> 
> In the interim...
> 
> Can anyone prove they saw this when either:
> 
> a) The upstream speaker did not have the AS Path limit configured to 
> something lower (say less than 200)?
> b) The upstream speaker was running with code *newer* than one of these:
> 
> 15.1(01.07.01)PIA14 15.1(01.05.01)PIA13 15.1(01)XB 15.0(01.01)SID 
> 15.0(01)M 12.4(24.06.06)PIL12 12.4(24.06.05)PIB12 12.4(24.06)PI11l 
> 12.2(33.01.21)MCP05 12.2(33)ZI 12.2(33)XNE 12.2(33)SXI02 
> 12.2(32.08.17)REC186 12.2(32.08.15)YCA273.10 12.2(32.08.11)XJC273.11 
> 12.2(32.08.11)SX277 12.2(32.08.06)YCA246.10 12.2(32.08.01)YCA273.15 
> 12.0(32)SY10


We observed problem only on 2 GSRs as upstream.
Both affected gsrs has  bgp maxas-limit 100 and runs 12.0(33)s4
We have several GSRs, which runs different versions - S5, S6, even couple with 
S2 and (32)SY6



> 
>  From what Shimol and I appear to have gleaned so far it's an issue 
> between a 4byte AS (new) speaker and and non 4 byte (old) speaker *and* 
> the 4byte AS (new) upstream speaker is on a version of code older than 
> one of the ones above.
> 
> Can folks confirm/deny if their deployment where they saw this either 
> did or did not match those conditions above?
> 
> Read it carefully as it can be tricky.
> 
> Thanks,
> Rodney
>