NTAC Peering Working Group

[Hans Addleman <>]

Hi Bill,

Apologies for the late response. 

Internet2 routers during this time dropped many of our bgp sessions with 
international peers that were affected by the route leakage. All of our 
International peerings are safeguarded by prefix limits and we saw a number 
of them go down as they went over this limit.

As Dale stated we do not peer directly with NLR and we do not believe that we 
perpetuated this leakage. However, if you or anyone does find evidence that 
we did please share and I will investigate further.

Currently the NOC is pulling together a list of which peers we saw drop 
during this outage due to prefix limit exceeded.

Our current limit for all International peers is set at 4000.

Thanks!
Hans Addleman
IU Global NOC Engineer





On Jan 4, 2013, at 5:31 PM, Bill Owens wrote:

> On Fri, Jan 04, 2013 at 04:37:43PM -0500, Bill Owens wrote:
>> There was a short but very useful discussion of today's BGP problems 
>> taking place on the wg-multicast list, based on my initial (and incorrect) 
>> impression that the issue had something to do with multicast; Michael 
>> Lambert suggested that I bring the thread here instead.
> 
> Two things:
> 
> - I forgot to attach the graphs.
> 
> - Dale Finkelson pointed out that there's no peering connection between 
> Internet2 and NLR (which I should have remembered, duh) and no obvious way 
> that the routes leaking from NLR could get to I2 and then to NYSERNet. I 
> wasn't driving the router consoles during the actual problem, one of the 
> other engineers was; I remembered him seeing a high prefix count on our 
> Internet2 BGP session in NYC, but I don't have any direct evidence of 
> whether and how much the I2 peering jumped up. It's possible that we were 
> impacted purely by our NLR peering, and I2 wasn't involved at all. 
> Hopefully someone from the NOC can straighten that out.
> 
> Also, NLR has another maintenance scheduled for Sunday morning. . .
> 
> Bill.
> <NLR_BGP_count.png><NYSERNet_BGP_count.png>