- mice-discuss - lists.micemn.net

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