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
Down in Vancouver, BC area as well. We see drops out of Seattle. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@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
Flapping in NYC since 8:07 PM EST. On Tue, Feb 11, 2014 at 9:21 PM, <alexzarris@yahoo.com> wrote:
Down in Vancouver, BC area as well. We see drops out of Seattle.
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Chris Stone *Sent:* Tuesday, February 11, 2014 5:46 PM *To:* outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
That time is right close to when it started here. Seems they have a real problem. Still heard nothing on my ticket. Chris -- Sent with MailDroid on my Samsung Galaxy 10.1 2014 tablet -----Original Message----- From: shaun coon <shauncoon2409@gmail.com> To: alexzarris@yahoo.com Cc: Chris Stone <cstone@axint.net>, outages@outages.org Sent: Tue, 11 Feb 2014 7:24 PM 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@yahoo.com> wrote:
Down in Vancouver, BC area as well. We see drops out of Seattle.
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Chris Stone *Sent:* Tuesday, February 11, 2014 5:46 PM *To:* outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
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@asicentral.com <mailto:youraddress@asicentral.com> Phone: (215) 953-3692 Fax: (215) 953-3759 Web: www.asicentral.com <http://www.asicentral.com/> From: Outages [mailto:outages-bounces@outages.org] On Behalf Of shaun coon Sent: Tuesday, February 11, 2014 9:24 PM To: alexzarris@yahoo.com Cc: outages@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@yahoo.com> wrote: Down in Vancouver, BC area as well. We see drops out of Seattle. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
Stable here in IND (fed from CVG). -- Jim Wininger jwininger@ifncom.net Desk/Cell - 317-777-7114 CONFIDENTIALITY NOTICE: The information contained in this electronic mail transmission (including any attachment) is intended for the exclusive use of the named recipient and may contain information that is privileged or otherwise confidential. It is not intended for transmission to, or receipt by, anyone other than the named recipient (or person authorized to deliver it to the named recipient). It should not be copied or forwarded to any unauthorized person. If you have received this electronic mail transmission in error, please delete it from your system including any attachment without copying or forwarding it, and notify the sender of the error by return e-mail. -----Original Message----- From: Tim Glen <tglen@asicentral.com> Date: Tuesday, February 11, 2014 at 9:31 PM To: 'shaun coon' <shauncoon2409@gmail.com>, "alexzarris@yahoo.com" <alexzarris@yahoo.com> Cc: "outages@outages.org" <outages@outages.org> Subject: Re: [outages] BGP down and bouncing with L3 AS3356 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 SpecialtyInstitute | Promoting Success Email: tglen@asicentral.com <mailto:youraddress@asicentral.com> Phone: (215) 953-3692 Fax: (215) 953-3759 Web: www.asicentral.com <http://www.asicentral.com/> From: Outages [mailto:outages-bounces@outages.org] On Behalf Of shaun coon Sent: Tuesday, February 11, 2014 9:24 PM To: alexzarris@yahoo.com Cc: outages@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@yahoo.com> wrote: Down in Vancouver, BC area as well. We see drops out of Seattle. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
Possibly related to this: http://www.pcworld.com/article/2096720/attackers-use-ntp-reflection-in-huge-... ------------------------------------------------------- Ala'alatoa Aloiamoa Anesi, Jr. Systems Engineer Blue Sky Communications 478 Laufou Shopping Ctr Pago Pago, American Samoa 96799 -- Ph: +1.684.699.2759 ext 1098 Cell: +1.684.258.1098 On Tue, Feb 11, 2014 at 3:53 PM, James Wininger <jwininger@ifncom.net>wrote:
Stable here in IND (fed from CVG). -- Jim Wininger
jwininger@ifncom.net Desk/Cell - 317-777-7114
CONFIDENTIALITY NOTICE: The information contained in this electronic mail transmission (including any attachment) is intended for the exclusive use of the named recipient and may contain information that is privileged or otherwise confidential. It is not intended for transmission to, or receipt by, anyone other than the named recipient (or person authorized to deliver it to the named recipient). It should not be copied or forwarded to any unauthorized person. If you have received this electronic mail transmission in error, please delete it from your system including any attachment without copying or forwarding it, and notify the sender of the error by return e-mail.
-----Original Message----- From: Tim Glen <tglen@asicentral.com> Date: Tuesday, February 11, 2014 at 9:31 PM To: 'shaun coon' <shauncoon2409@gmail.com>, "alexzarris@yahoo.com" <alexzarris@yahoo.com> Cc: "outages@outages.org" <outages@outages.org> Subject: Re: [outages] BGP down and bouncing with L3 AS3356
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 SpecialtyInstitute | Promoting Success
Email: tglen@asicentral.com <mailto:youraddress@asicentral.com> Phone: (215) 953-3692 Fax: (215) 953-3759 Web: www.asicentral.com <http://www.asicentral.com/>
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of shaun coon Sent: Tuesday, February 11, 2014 9:24 PM To: alexzarris@yahoo.com Cc: outages@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@yahoo.com> wrote: Down in Vancouver, BC area as well. We see drops out of Seattle.
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Stable in NYC throughout, normal traffic levels as well. On Feb 11, 2014, at 9:23 PM, shaun coon wrote:
Flapping in NYC since 8:07 PM EST.
On Tue, Feb 11, 2014 at 9:21 PM, <alexzarris@yahoo.com> wrote: Down in Vancouver, BC area as well. We see drops out of Seattle.
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
CASCADED EXTERNAL NOTES 12-Feb-2014 04:01:32 GMT From CASE: 7531588 - Event The IP NOC has advised that the issue is believed to have been mitigated. Operations Engineers are currently working to confirm that no further impact is being experienced at this time. Regards, Tim Glen Sr. Network Engineer Advertising Specialty Institute | Promoting SuccessT Email: tglen@asicentral.com <mailto:youraddress@asicentral.com> Phone: (215) 953-3692 Fax: (215) 953-3759 Web: www.asicentral.com <http://www.asicentral.com/> From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Charles Sprickman Sent: Tuesday, February 11, 2014 10:42 PM To: shaun coon Cc: outages@outages.org Subject: Re: [outages] BGP down and bouncing with L3 AS3356 Stable in NYC throughout, normal traffic levels as well. On Feb 11, 2014, at 9:23 PM, shaun coon wrote: Flapping in NYC since 8:07 PM EST. On Tue, Feb 11, 2014 at 9:21 PM, <alexzarris@yahoo.com> wrote: Down in Vancouver, BC area as well. We see drops out of Seattle. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
All returned to normal here now for the last 2 hours. Chris Sent with MailDroid on my Samsung Galaxy 10.1 2014 tablet -----Original Message----- From: Tim Glen <tglen@asicentral.com> To: 'Charles Sprickman' <spork@bway.net>, shaun coon <shauncoon2409@gmail.com> Cc: "outages@outages.org" <outages@outages.org> Sent: Tue, 11 Feb 2014 9:20 PM Subject: Re: [outages] BGP down and bouncing with L3 AS3356 CASCADED EXTERNAL NOTES 12-Feb-2014 04:01:32 GMT From CASE: 7531588 - Event The IP NOC has advised that the issue is believed to have been mitigated. Operations Engineers are currently working to confirm that no further impact is being experienced at this time. Regards, Tim Glen Sr. Network Engineer Advertising Specialty Institute | Promoting SuccessT Email: tglen@asicentral.com <mailto:youraddress@asicentral.com> Phone: (215) 953-3692 Fax: (215) 953-3759 Web: www.asicentral.com <http://www.asicentral.com/> From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Charles Sprickman Sent: Tuesday, February 11, 2014 10:42 PM To: shaun coon Cc: outages@outages.org Subject: Re: [outages] BGP down and bouncing with L3 AS3356 Stable in NYC throughout, normal traffic levels as well. On Feb 11, 2014, at 9:23 PM, shaun coon wrote: Flapping in NYC since 8:07 PM EST. On Tue, Feb 11, 2014 at 9:21 PM, <alexzarris@yahoo.com> wrote: Down in Vancouver, BC area as well. We see drops out of Seattle. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Been normal here for the last few hours, but we had the same BGP flapping issue with Level3 at Switch SuperNAP in Las Vegas. Petter Bruland | Network Engineer Allegiant Travel Company 8360 S. Durango Drive, Las Vegas, NV 89113 Phone: (702) 874-3332 | Cell: (702) 286-6549 petter.bruland@allegiantair.com http://www.allegiantair.com ________________________________ From: Outages [outages-bounces@outages.org] on behalf of Chris Stone [cstone@axint.net] Sent: Tuesday, February 11, 2014 9:17 PM Cc: outages@outages.org Subject: Re: [outages] BGP down and bouncing with L3 AS3356 All returned to normal here now for the last 2 hours. Chris Sent with MailDroid on my Samsung Galaxy 10.1 2014 tablet -----Original Message----- From: Tim Glen <tglen@asicentral.com> To: 'Charles Sprickman' <spork@bway.net>, shaun coon <shauncoon2409@gmail.com> Cc: "outages@outages.org" <outages@outages.org> Sent: Tue, 11 Feb 2014 9:20 PM Subject: Re: [outages] BGP down and bouncing with L3 AS3356 CASCADED EXTERNAL NOTES 12-Feb-2014 04:01:32 GMT From CASE: 7531588 - Event The IP NOC has advised that the issue is believed to have been mitigated. Operations Engineers are currently working to confirm that no further impact is being experienced at this time. Regards, Tim Glen Sr. Network Engineer Advertising Specialty Institute | Promoting Success™ Email: tglen@asicentral.com<mailto:youraddress@asicentral.com> Phone: (215) 953-3692 Fax: (215) 953-3759 Web: www.asicentral.com<http://www.asicentral.com/> From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Charles Sprickman Sent: Tuesday, February 11, 2014 10:42 PM To: shaun coon Cc: outages@outages.org Subject: Re: [outages] BGP down and bouncing with L3 AS3356 Stable in NYC throughout, normal traffic levels as well. On Feb 11, 2014, at 9:23 PM, shaun coon wrote: Flapping in NYC since 8:07 PM EST. On Tue, Feb 11, 2014 at 9:21 PM, <alexzarris@yahoo.com<mailto:alexzarris@yahoo.com>> wrote: Down in Vancouver, BC area as well. We see drops out of Seattle. From: Outages [mailto:outages-bounces@outages.org<mailto:outages-bounces@outages.org>] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@outages.org<mailto:outages@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@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
A lot of the issues I saw at customers seemed to be with older hardware/software combinations not handling the # of communities. Yesterday, it was a few prefixes (/22s from AS 50010) and today another from the same AS. The smaller gear choked and bounced sessions. I didn't see any of this with larger iron and newer software. Eric From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Petter Bruland Sent: Wednesday, February 12, 2014 1:14 AM To: Chris Stone Cc: outages@outages.org Subject: Re: [outages] BGP down and bouncing with L3 AS3356 Been normal here for the last few hours, but we had the same BGP flapping issue with Level3 at Switch SuperNAP in Las Vegas. Petter Bruland | Network Engineer Allegiant Travel Company 8360 S. Durango Drive, Las Vegas, NV 89113 Phone: (702) 874-3332 | Cell: (702) 286-6549 petter.bruland@allegiantair.com <mailto:petter.bruland@allegiantair.com> http://www.allegiantair.com _____ From: Outages [outages-bounces@outages.org] on behalf of Chris Stone [cstone@axint.net] Sent: Tuesday, February 11, 2014 9:17 PM Cc: outages@outages.org <mailto:outages@outages.org> Subject: Re: [outages] BGP down and bouncing with L3 AS3356 All returned to normal here now for the last 2 hours. Chris Sent with MailDroid on my Samsung Galaxy 10.1 2014 tablet -----Original Message----- From: Tim Glen <tglen@asicentral.com <mailto:tglen@asicentral.com> > To: 'Charles Sprickman' <spork@bway.net <mailto:spork@bway.net> >, shaun coon <shauncoon2409@gmail.com <mailto:shauncoon2409@gmail.com> > Cc: "outages@outages.org <mailto:outages@outages.org> " <outages@outages.org <mailto:outages@outages.org> > Sent: Tue, 11 Feb 2014 9:20 PM Subject: Re: [outages] BGP down and bouncing with L3 AS3356 CASCADED EXTERNAL NOTES 12-Feb-2014 04:01:32 GMT From CASE: 7531588 - Event The IP NOC has advised that the issue is believed to have been mitigated. Operations Engineers are currently working to confirm that no further impact is being experienced at this time. Regards, Tim Glen Sr. Network Engineer Advertising Specialty Institute | Promoting SuccessT Email: tglen@asicentral.com <mailto:youraddress@asicentral.com> Phone: (215) 953-3692 Fax: (215) 953-3759 Web: www.asicentral.com <http://www.asicentral.com/> From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Charles Sprickman Sent: Tuesday, February 11, 2014 10:42 PM To: shaun coon Cc: outages@outages.org <mailto:outages@outages.org> Subject: Re: [outages] BGP down and bouncing with L3 AS3356 Stable in NYC throughout, normal traffic levels as well. On Feb 11, 2014, at 9:23 PM, shaun coon wrote: Flapping in NYC since 8:07 PM EST. On Tue, Feb 11, 2014 at 9:21 PM, <alexzarris@yahoo.com <mailto:alexzarris@yahoo.com> > wrote: Down in Vancouver, BC area as well. We see drops out of Seattle. From: Outages [mailto:outages-bounces@outages.org <mailto:outages-bounces@outages.org> ] On Behalf Of Chris Stone Sent: Tuesday, February 11, 2014 5:46 PM To: outages@outages.org <mailto:outages@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@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
We have not seen any flapping on our transit links in NYC or Philadelphia George Carey
participants (10)
-
alexzarris＠yahoo.com -
Aloiamoa Anesi -
Charles Sprickman -
Chris Stone -
Eric Krichbaum -
George Carey -
James Wininger -
Petter Bruland -
shaun coon -
Tim Glen