[AusNOG] Pipe NSW IX backup route server - outbound BGP updates

[Dylan Chidgey]

+1 on this.

 

Yet to receive notification from PIPE though. 

 

From: Patrick Mole [mailto:patrick.mole at gmail.com] 
Sent: Thursday, 24 April 2014 10:26 AM
To: dylan.chidgey at cirruscomms.com.au
Cc: Mark Tees; ausnog at lists.ausnog.net
Subject: Re: [AusNOG] Pipe NSW IX backup route server - outbound BGP updates

 

Looks like they fixed it at 04:15 this morning. My session dropped at this time and came back a minute later with a received count to match the .1 session. (previously having 0 received on the .62 session).

 

On Tue, Apr 22, 2014 at 6:20 PM, dylan.chidgey at cirruscomms.com.au <mailto:dylan.chidgey at cirruscomms.com.au>  <dylan.chidgey at cirruscomms.com.au <mailto:dylan.chidgey at cirruscomms.com.au> > wrote:

Pipe has advised they will be making a change on Thursday to rectify this fault.

Thanks
Dylan

sent from my Telstra NEXTG™ handset




----- Reply message -----
From: "Mark Tees" <mark.tees at digitalpacific.com.au <mailto:mark.tees at digitalpacific.com.au> >
To: "Matt Perkins" <matt at spectrum.com.au <mailto:matt at spectrum.com.au> >
Cc: <ausnog at lists.ausnog.net <mailto:ausnog at lists.ausnog.net> >
Subject: [AusNOG] Pipe NSW IX backup route server - outbound BGP updates
Date: Tue, Apr 22, 2014 5:47 PM


The issue appears after a reset I think. Have you reset your session with them recently?

On 22 Apr 2014, at 5:44 pm, Matt Perkins <matt at spectrum.com.au <mailto:matt at spectrum.com.au> > wrote:

> Just checked our pipe peer's back seem's fine. We peer at global switch.
> 
> Matt
> 
> 
> On 22/04/14 5:41 PM, Mark Tees wrote:
>>     Keepalives:           287        257
>>     Route Refresh:          0          0
>>     Total:                294        258
>> </snip>
>> 
>> Where as on the route server side when I look at the neighbour status output on their side it shows as them having sent updates and routes. I checked this via doing “show ip bgp neighbours 218.100.2.96” from their LG.
>> 
>> I spotted other peers connected to that route server with problems because in the BGP summary output from the LG, peers effected so far had been reset recently and their table version was 0. This has been confirmed by another peer.
>> 
>> Doesn’t look like any of this is related to policy. My question is from a config perspective is there anything outside of a bug that is likely to cause this behaviour with BGP UPDATE messages being dropped? Their side is Cisco too by the looks of it. Rumoured to be 7200 serie
> 
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net> 
> http://lists.ausnog.net/mailman/listinfo/ausnog

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net> 
http://lists.ausnog.net/mailman/listinfo/ausnog


_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net> 
http://lists.ausnog.net/mailman/listinfo/ausnog

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20140424/821f57c8/attachment.html>