- mice-discuss - lists.micemn.net

Re: Update for Akamai (AS 20940) < > MICE

by Shaun Carlson

Posting to announce list now Shaun Carlson Director of Information Technology | Arvig ph: (218) 346.8673 | em: shaun.carlson(a)arvig.com On Wed, Apr 27, 2016 at 5:24 AM -0700, "Jason Hanke" <jayhanke(a)neutralpath.net> wrote: This is the right list. Not everyone follows it. On Apr 27, 2016 7:17 AM, "Hannigan, Martin" <marty(a)akamai.com> wrote: I haven't seen this approach to an administrative operational message before. Isnt this the right list? This is routine stuff. *shrug* Best, -M< On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby(a)MNVOIP.COM> wrote: Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

April 27, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Jason Hanke

This is the right list. Not everyone follows it. On Apr 27, 2016 7:17 AM, "Hannigan, Martin" <marty(a)akamai.com> wrote: > > I haven't seen this approach to an administrative operational message > before. Isnt this the right list? This is routine stuff. *shrug* > > Best, > > -M< > > On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby(a)MNVOIP.COM > <jlumby(a)mnvoip.com>> wrote: > > Thanks Marty, If someone with appropriate permissions could copy Marty's > email to the announce list, I feel it should reach more of the membership > since not everyone monitors the discuss list. > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET > <MICE-DISCUSS(a)LISTS.IPHOUSE.NET>] *On Behalf Of *Hannigan, Martin > *Sent:* Tuesday, April 26, 2016 9:34 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)lists.iphouse.net> > *Subject:* [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE > > > > > > Greetings everyone. And Reid. :-) > > > > Our implementation is proceeding and we’re projecting that we’ll be moving > bits back to the exchange in the next few weeks. > > > > Unfortunately, we’re dropping our route server sessions permanently. > Everyone who is now route server only will need to established bi lateral > peering. Send your peering request to peering(a)akamai.com with the > requisite details (ASN, peer addresses). If you had a direct session > previously, we have not forgotten it and there’s no need to restate. > Traffic will return slowly, first with our SSL bits and then full on edge a > few weeks after that. > > > > Thanks for your patience and for helping to build a better Internet in MSP. > > > > Best, > > > > Martin Hannigan // AS 20940 // AS 32787 > > > > > > > > > > > > > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2…> > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2…> > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

April 27, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Hannigan, Martin

I haven't seen this approach to an administrative operational message before. Isnt this the right list? This is routine stuff. *shrug* Best, -M< On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby(a)MNVOIP.COM<mailto:jlumby@mnvoip.com>> wrote: Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@lists.iphouse.net> Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we're projecting that we'll be moving bits back to the exchange in the next few weeks. Unfortunately, we're dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com<mailto:peering@akamai.com> with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there's no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2…> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2…>

April 27, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Jeremy Lumby

Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

April 27, 2016

Update for Akamai (AS 20940) < > MICE

by Hannigan, Martin

Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com<mailto:peering@akamai.com> with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787

April 27, 2016

Re: HE issue this afternoon

by Brady Kittel

I know they had something with their Chicago router today. We opened a ticket with them when we lost routes through our separate transit link with them for about 5 minutes earlier today. On Apr 26, 2016 3:30 PM, "Frank Bulk" <fbulk(a)mypremieronline.com> wrote: > During this afternoon’s HE hiccup ( > https://puck.nether.net/pipermail/outages/2016-April/008962.html) there > was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, > and 23. Here’s an example: > > > > > > Anyone know what that’s about? > > > > Frank > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

April 27, 2016

Re: HE issue this afternoon

by Justin Krejci

HE reported to me their issue was in Chicago. ________________________________________ From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Doug McIntyre [merlyn(a)IPHOUSE.NET] Sent: Tuesday, April 26, 2016 3:41 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] HE issue this afternoon On Tue, Apr 26, 2016 at 08:30:07PM +0000, Frank Bulk wrote: > During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: > > Anyone know what that's about? I'd think it is just a monitoring glitch. Monitoring of the devices happens to route through ipHouse (rather than direct across the exchange) due to old timing of onboarding. And we at ipHouse were definately impacted by HE's route engine failover event. We shut down HE pretty quickly, but I could see some packets going awry while that was happening. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

April 26, 2016

Re: HE issue this afternoon

by Doug McIntyre

On Tue, Apr 26, 2016 at 08:30:07PM +0000, Frank Bulk wrote: > During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: > > Anyone know what that's about? I'd think it is just a monitoring glitch. Monitoring of the devices happens to route through ipHouse (rather than direct across the exchange) due to old timing of onboarding. And we at ipHouse were definately impacted by HE's route engine failover event. We shut down HE pretty quickly, but I could see some packets going awry while that was happening. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

April 26, 2016

Re: HE issue this afternoon

by Dale W. Carder

Given the rate, it looks like a 10Mbit/sec storm-control policer. Dale Thus spake Frank Bulk (fbulk(a)MYPREMIERONLINE.COM) on Tue, Apr 26, 2016 at 08:30:07PM +0000: > During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: > > [cid:image001.png@01D19FD0.2A25A860] > > Anyone know what that's about? > > Frank

April 26, 2016

Re: HE issue this afternoon

by Shaun Carlson

And, of course, if I actually read your original email, I would know that you already mentioned the "hiccup" and wouldn't repeat the fact. During the event, were others trying to route through the cluster to get to HE? s *Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com On Tue, Apr 26, 2016 at 4:35 PM, Shaun Carlson <shaun.carlson(a)arvig.com> wrote: > According to our ticket, HE had a router failure at around that time. > > s > > > > *Shaun Carlson*Director of Information Technology | Arvig > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > On Tue, Apr 26, 2016 at 4:30 PM, Frank Bulk <fbulk(a)mypremieronline.com> > wrote: > >> During this afternoon’s HE hiccup ( >> https://puck.nether.net/pipermail/outages/2016-April/008962.html) there >> was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, >> and 23. Here’s an example: >> >> >> >> >> >> Anyone know what that’s about? >> >> >> >> Frank >> >> ------------------------------ >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> > >

April 26, 2016