[outages] BGP down and bouncing with L3 AS3356

[Tim Glen]

I am having a simillar problem in PHL with BGP Peering to L3 flapping  also.


 

>From L3: 

 

It has been confirmed that IP services are also being impacted. The IP NOC
has advised that that the issue is suspected to be the result of a Denial of
Service (DoS) attack on several links in the United States. Operations
Engineering are being engaged at this time to assist with investigations.

 

 

 

 

Regards,

Tim Glen
Sr. Network Engineer
Advertising Specialty Institute | Promoting SuccessT

Email: tglen at asicentral.com <mailto:youraddress at asicentral.com> 
Phone: (215) 953-3692
Fax: (215) 953-3759
Web: www.asicentral.com <http://www.asicentral.com/> 

 

From: Outages [mailto:outages-bounces at outages.org] On Behalf Of shaun coon
Sent: Tuesday, February 11, 2014 9:24 PM
To: alexzarris at yahoo.com
Cc: outages at outages.org
Subject: Re: [outages] BGP down and bouncing with L3 AS3356

 

Flapping in NYC since 8:07 PM EST.

 

On Tue, Feb 11, 2014 at 9:21 PM, <alexzarris at yahoo.com> wrote:

Down in Vancouver, BC area as well. We see drops out of Seattle.

 

From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Chris Stone
Sent: Tuesday, February 11, 2014 5:46 PM
To: outages at outages.org
Subject: [outages] BGP down and bouncing with L3 AS3356

 

Anyone else seeing L3 BGP sessions bouncing. Been up and down here in Denver
since 18:01:43 MST.

Feb 11 18:01:43 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Down
Peer closed the session
Feb 11 18:01:47 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Up
Feb 11 18:04:25 core01 bgpd[1977]: %ADJCHANGE: neighbor 208.69.76.46 Down
Peer closed the session
Feb 11 18:04:34 core01 bgpd[1977]: %ADJCHANGE: neighbor 208.69.76.46 Up
Feb 11 18:08:54 core01 bgpd[1977]: %NOTIFICATION: received from neighbor
4.28.16.137 4/0 (Hold Timer Expired) 0 bytes 
Feb 11 18:08:54 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Down BGP
Notification received
Feb 11 18:11:55 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Up
Feb 11 18:14:55 core01 bgpd[1977]: %NOTIFICATION: sent to neighbor
4.28.16.137 4/0 (Hold Timer Expired) 0 bytes 
Feb 11 18:14:55 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Down BGP
Notification send
Feb 11 18:15:59 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Up
Feb 11 18:19:18 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Down
Peer closed the session
Feb 11 18:23:06 core01 bgpd[1977]: %NOTIFICATION: sent to neighbor
4.28.16.137 4/0 (Hold Timer Expired) 0 bytes 
Feb 11 18:26:59 core01 bgpd[1977]: %NOTIFICATION: sent to neighbor
4.28.16.137 4/0 (Hold Timer Expired) 0 bytes 
Feb 11 18:27:50 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Up
Feb 11 18:39:56 core01 bgpd[1977]: %NOTIFICATION: received from neighbor
4.28.16.137 4/0 (Hold Timer Expired) 0 bytes 
Feb 11 18:39:56 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Down BGP
Notification received
Feb 11 18:43:27 core01 bgpd[1977]: %NOTIFICATION: received from neighbor
4.28.16.137 4/0 (Hold Timer Expired) 0 bytes 
Feb 11 18:43:53 core01 bgpd[1977]: %ADJCHANGE: neighbor 4.28.16.137 Up

Ticket opened, but not heard anything back yet.



Chris



-- 
Let's just say I was testing the bounds of society. I was just curious.
-- Jim Morrison


_______________________________________________
Outages mailing list
Outages at outages.org
https://puck.nether.net/mailman/listinfo/outages

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20140211/74406560/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3698 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/outages/attachments/20140211/74406560/attachment.bin>