- mice-discuss - lists.micemn.net

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Richard Laager

> On May 18, 2016, at 11:34, Matthew Beckwell <matthewb(a)AITECH.NET> wrote: > > maybe we can convince Richard to throw up a section on the micemn.net technical page that lists the communities? :) Yes, will do. I have a few updates pending from the new members in the last couple days. I should have this all done in a few hours. -- Richard

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Matthew Beckwell

Doug & Chih, Thanks for your efforts on this. Mike H, can you post to MICE-ANNOUNCE? And maybe we can convince Richard to throw up a section on the micemn.net technical page that lists the communities? :) Thanks guys. ~Matthew On Wed, May 18, 2016 at 11:11 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > Thanks to Chih Chen's help at the U of Wisc, I have testing done for > phase1 of the BGP communities exporting that have been requested. > (Phase2 would be doing prepends, but I'll have to lab up that > functionality as I saw the export function grow 10 times or so before I > stopped). > Most of the delay was waiting for others to test with me. > > I plan on implementing this MICE site wide on Sunday, 5/22/2016, starting > at > around 10:00PM - 11:59PM. > > All the testing looked good to us during testing, the functions > behaved as expected. This function is an expansion of what was tested > before. > ipHouse has had this export function on it since the end of winter. > > It is written to properly handle 32-bit ASNs (I believe, that part was > provided > by the BIRD WIKI author). And of course IPv4 and IPv6 make no difference. > > The communities supported by this setup will include > > 0:peerAS -- Don't export route prefix to this peer. > 53679:peerAS -- Always export route prefix to this peer. > 0:53679 -- Don't export route prefix to all MICE peers. > > > The steps of actually implementing this would be non-eventful, but I know > some will want to drop for it. > > > > ALSO, we really should upgrade the OS that is running the route > servers too. So I'll be doing OS updates and other upgrades that will > upgrade BIRD as well in the same window. BIRD moves from > 1.4.5 -> 1.5.0. The release notes say it mostly is OSPF changes, > I expect no problems in this update, BIRD has been very stable, and the OS > has been stable in production use here. > > Thanks. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades >

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Chris Wopat

On 05/18/2016 11:11 AM, Doug McIntyre wrote: > Thanks to Chih Chen's help at the U of Wisc, I have testing done for > phase1 of the BGP communities exporting that have been requested. > (Phase2 would be doing prepends, but I'll have to lab up that > functionality as I saw the export function grow 10 times or so before I stopped). > Most of the delay was waiting for others to test with me. > > I plan on implementing this MICE site wide on Sunday, 5/22/2016, starting at > around 10:00PM - 11:59PM. > > All the testing looked good to us during testing, the functions > behaved as expected. This function is an expansion of what was tested before. > ipHouse has had this export function on it since the end of winter. > > It is written to properly handle 32-bit ASNs (I believe, that part was provided > by the BIRD WIKI author). And of course IPv4 and IPv6 make no difference. > > The communities supported by this setup will include > > 0:peerAS -- Don't export route prefix to this peer. > 53679:peerAS -- Always export route prefix to this peer. > 0:53679 -- Don't export route prefix to all MICE peers. > > > The steps of actually implementing this would be non-eventful, but I know > some will want to drop for it. > > > > ALSO, we really should upgrade the OS that is running the route > servers too. So I'll be doing OS updates and other upgrades that will > upgrade BIRD as well in the same window. BIRD moves from > 1.4.5 -> 1.5.0. The release notes say it mostly is OSPF changes, > I expect no problems in this update, BIRD has been very stable, and the OS > has been stable in production use here. Great work folks, glad to see this coming in to production. Is it possible to see examples of the config? Or at least verify that these communities are stripped out on the route server after the action is taken? Cheers, -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

May 18, 2016

Route Server BGP communities (& OS upgrades) - 5/22/2016

by Doug McIntyre

Thanks to Chih Chen's help at the U of Wisc, I have testing done for phase1 of the BGP communities exporting that have been requested. (Phase2 would be doing prepends, but I'll have to lab up that functionality as I saw the export function grow 10 times or so before I stopped). Most of the delay was waiting for others to test with me. I plan on implementing this MICE site wide on Sunday, 5/22/2016, starting at around 10:00PM - 11:59PM. All the testing looked good to us during testing, the functions behaved as expected. This function is an expansion of what was tested before. ipHouse has had this export function on it since the end of winter. It is written to properly handle 32-bit ASNs (I believe, that part was provided by the BIRD WIKI author). And of course IPv4 and IPv6 make no difference. The communities supported by this setup will include 0:peerAS -- Don't export route prefix to this peer. 53679:peerAS -- Always export route prefix to this peer. 0:53679 -- Don't export route prefix to all MICE peers. The steps of actually implementing this would be non-eventful, but I know some will want to drop for it. ALSO, we really should upgrade the OS that is running the route servers too. So I'll be doing OS updates and other upgrades that will upgrade BIRD as well in the same window. BIRD moves from 1.4.5 -> 1.5.0. The release notes say it mostly is OSPF changes, I expect no problems in this update, BIRD has been very stable, and the OS has been stable in production use here. Thanks. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 18, 2016

Re: Please welcome NebraskaLink to MICE

by Doug McIntyre

On Tue, May 17, 2016 at 05:57:42PM -0500, Jason Hanke wrote: > Name: NebraskaLink > ASN: 16851 > Port: NP MSP1 Remote xe-0/0/3 > IPv4: 206.108.255.70/24 > IPv6: 2001:504:27:0:0:41d3::1/64 > Contact: noc(a)nebraskalink.com > > Route Servers and website please! > > Welcome aboard! Sure thing, I have the route servers setup for this entry, ready to go. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 18, 2016

Re: Please welcome NebraskaLink to MICE

by Hannigan, Martin

Wow! Lots of MICEicles today!! Welcome everyone! > On May 17, 2016, at 18:57, Jason Hanke <jayhanke(a)NEUTRALPATH.NET> wrote: > > Name: NebraskaLink > ASN: 16851 > Port: NP MSP1 Remote xe-0/0/3 > IPv4: 206.108.255.70/24 > IPv6: 2001:504:27:0:0:41d3::1/64 > Contact: noc(a)nebraskalink.com > > Route Servers and website please! > > Welcome aboard! > > -- > Jay Hanke > CTO > Neutral Path Communications > 3 Civic Center Plaza, Suite 204 > Mankato, MN 56001 > (507) 327-2398 mobile > jayhanke(a)neutralpath.net > www.neutralpath.net

May 17, 2016

Please welcome NebraskaLink to MICE

by Jason Hanke

Name: NebraskaLink ASN: 16851 Port: NP MSP1 Remote xe-0/0/3 IPv4: 206.108.255.70/24 IPv6: 2001:504:27:0:0:41d3::1/64 Contact: noc(a)nebraskalink.com Route Servers and website please! Welcome aboard! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

May 17, 2016

Re: Please welcome Paragon Solutions Group to MICE

by Doug McIntyre

On Tue, May 17, 2016 at 09:36:33AM -0500, Jason Hanke wrote: > Name: Paragon Solutions Group > Port: ge-2/0/9 (main switch ex4550) > ASN: 55043 > IPv4: 206.108.255.57/24 > IPv6: 2001:504:27:0:0:d703::1/64 > Contact: chris.dye(a)paragon.net > > Route Server and website updates please. Sure, had to do some switch work too, as I'm assuming all fiber ports are all 10Gbps now, but we don't have any 1G only fiber ports left. Got them in the route servers too. All set to go. Welcome aboard! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 17, 2016

MICE Facebook Page

by Jason Hanke

We have a Facebook page! Like it! https://www.facebook.com/MNMICE/ We also have a Facebook event for MICE UG20 in Eau Claire! https://www.facebook.com/events/695794023896344/ -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

May 17, 2016

Please welcome Paragon Solutions Group to MICE

by Jason Hanke

Name: Paragon Solutions Group Port: ge-2/0/9 (main switch ex4550) ASN: 55043 IPv4: 206.108.255.57/24 IPv6: 2001:504:27:0:0:d703::1/64 Contact: chris.dye(a)paragon.net Route Server and website updates please. Paragon will provide an SFP to Cologix for installation. Welcome aboard! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

May 17, 2016

Please welcome Stealth Broadband to MICE!

by Jason Hanke

Name: Stealth Broadband ASN: TBD in Arin process now port: NP-MSP1 ge-0/0/2 IPv4: 206.108.255.69/24 IPv6: Pending ASN Contact: James.urwiller(a)stealthbroadband.com Please update the website at this time. They will be using the MICE connection to meet the multihoming requirements. We can update the other elements following the ASN assignment. Thanks! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

May 12, 2016

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

by Hannigan, Martin

All, I did look and we have received your requests. They will be taken care of shortly. Apologies for the delay. Best,, Marty > On May 9, 2016, at 21:38, Hannigan, Martin <marty(a)akamai.com> wrote: > > > Ill take a look in the queue. > > Thanks > > > > >> On May 9, 2016, at 21:09, Andrew Hoyos <hoyosa(a)GMAIL.COM> wrote: >> >> Likewise here, crickets…… >> >> >>> On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: >>> >>> Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. >>> >>> Jeremy >>> >>> 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

May 12, 2016

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

by Jeff Anderson

Same boat here as well. Jeff Anderson jeffa(a)implex.net 612.799.7277 Cell 612.339.8255 x200 Office 612.339.3310 Fax -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jeremy Lumby Sent: Monday, May 9, 2016 9:05 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. Jeremy 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

May 10, 2016

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

by Hannigan, Martin

Ill take a look in the queue. Thanks > On May 9, 2016, at 21:09, Andrew Hoyos <hoyosa(a)GMAIL.COM> wrote: > > Likewise here, crickets…… > > >> On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: >> >> Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. >> >> Jeremy >> >> 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

May 10, 2016

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

by Andrew Hoyos

Likewise here, crickets…… > On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > > Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. > > Jeremy > > 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

May 10, 2016

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

by Jeremy Lumby

Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. Jeremy 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

May 10, 2016

Technical Training Opportunity at TOC Conference in Fargo

by Shaun Carlson

All, CCI/Cisco are hosting a technical training, designed to be more of a deep dive, at the TOC conference in Fargo next week. There is no cost for the training except for registration for the conference itself. Attached is the flyer CCI created for this opportunity and the link to register for the session is right in there. If you're headed up for the conference, consider attending or sending someone to the session. This is my first run at bringing some deeper technical training to the region and I'm hoping to see it well attended. Thanks! s *Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

May 4, 2016

Re: Netflix addition/split

by Doug McIntyre

On Thu, Apr 28, 2016 at 09:17:50AM -0500, Jason Hanke wrote: > Netflix is converting their 7x10G to 2x4x10G and spreading the links over > switch 0 and 2 of the main fabric. > > The new port assignments for the second LAG are: > > xe-2/0/21 (Netflix side Et3/19/2) > xe-2/0/22 (Netflix side Et4/20/4) > xe-2/0/23 (Netflix side Et4/21/3) > xe-2/0/24 (TBD) Okay, I reactivated ae3, and made a 2nd LAG group with these ports in it. The switch configs should be ready for the physical work now. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

April 28, 2016

Netflix addition/split

by Jason Hanke

Netflix is converting their 7x10G to 2x4x10G and spreading the links over switch 0 and 2 of the main fabric. The new port assignments for the second LAG are: xe-2/0/21 (Netflix side Et3/19/2) xe-2/0/22 (Netflix side Et4/20/4) xe-2/0/23 (Netflix side Et4/21/3) xe-2/0/24 (TBD) Netflix will abandon 3 ports on the main switch as part of the transition: xe-0/2/0 xe-0/2/1 xe-0/2/3 We will move those optics to the new switch and Netflix will supply an additional optic for the forth port in the second LAG group. Thanks! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

April 28, 2016

Re: HE issue this afternoon

by Dale W. Carder

Are there packet counters / graphs to determine where the flood came in from? Also maybe not related, but on the naix-discuss list recently there was mention of an arp flooding issue w/ mikrotik that has been recently resolved. Dale Thus spake Frank Bulk (fbulk(a)MYPREMIERONLINE.COM) on Wed, Apr 27, 2016 at 01:40:50PM +0000: > Dale -- good point. But why did it kick in? Why would an issue with a peer cause/result in a flood of outbound traffic on other ports? > > Frank > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Dale W. Carder > Sent: Tuesday, April 26, 2016 3:40 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] HE issue this afternoon > > 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 27, 2016

Re: HE issue this afternoon

by Frank Bulk

There's no gaps in the graph, so no indication it was a polling issue. There's every reason to believe it really did happen -- I'm just trying to understand why. =) Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Tuesday, April 26, 2016 3:42 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 27, 2016

Re: HE issue this afternoon

by Frank Bulk

Dale -- good point. But why did it kick in? Why would an issue with a peer cause/result in a flood of outbound traffic on other ports? Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Dale W. Carder Sent: Tuesday, April 26, 2016 3:40 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] HE issue this afternoon 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 27, 2016

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

by Shaun Carlson

NM, beat to the punch by someone with faster Internet access (service sucks out here in Delaware). S Shaun Carlson Director of Information Technology | Arvig ph: (218) 346.8673 | em: shaun.carlson(a)arvig.com On Wed, Apr 27, 2016 at 5:29 AM -0700, "Mike Horwath" <drechsau(a)geeks.org> wrote: On Wed, Apr 27, 2016 at 12:29:25PM +0000, Shaun Carlson wrote: > Posting to announce list now Ha, I already did. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

April 27, 2016

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

by Mike Horwath

On Wed, Apr 27, 2016 at 12:29:25PM +0000, Shaun Carlson wrote: > Posting to announce list now Ha, I already did. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

April 27, 2016

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