- mice-discuss - lists.micemn.net

Re: UG 28

by Richard Laager

Reminder: UG 28 is July 11, 3:00pm, at one of the 702 Communications facilities in the Fargo/Moorhead area (specific location TBA). If you have agenda items for the upcoming UG 28, please send them to me. -- Richard

June 12, 2018

Re: ADV: [MICE-DISCUSS] Please welcome Pavlov Media to MICE!

by Doug McIntyre

On Fri, Jun 08, 2018 at 09:29:16AM -0500, Jay Hanke wrote: >Name: Pavlov Media >Port: Ethernet4/24 (Main Switch) >ASN: 23473 >IPv4: 206.108.255.93 /24 >IPv6: 2001:504:27:0:0:5bb1::1 /64 >Route Server: Yes >BFD: NO >Peering Contact: peering(a)pavlovmedia.net > >Please provide you 10G Arista compatible SFP+ when you order your cross >connect. > >We will post the port assignment information to the MICE website. The >public posting (or this email) will serve as your LOA/CFA. I've added them to the route servers. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

June 8, 2018

Please welcome Pavlov Media to MICE!

by Jay Hanke

Name: Pavlov Media Port: Ethernet4/24 (Main Switch) ASN: 23473 IPv4: 206.108.255.93 /24 IPv6: 2001:504:27:0:0:5bb1::1 /64 Route Server: Yes BFD: NO Peering Contact: peering(a)pavlovmedia.net Please provide you 10G Arista compatible SFP+ when you order your cross connect. We will post the port assignment information to the MICE website. The public posting (or this email) will serve as your LOA/CFA. Welcome aboard -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io

June 8, 2018

Amazon Port Augment

by Jay Hanke

Amazon is adding additional ports and a redundant LAG. New Physical ports (LAG 23): Ethernet4/23 (10g) Ethernet5/23 (10g) New IP Addresses are: 206.108.255.112/24 2001:504:27:0:0:407d::2/64 Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io

June 7, 2018

Re: Changing hats

by Jay Hanke

You should be able to use the same ip address on any of the mice switches. We can allocate a test ip if needed. On Fri, Jun 1, 2018, 3:51 PM Frank Bulk <fbulk(a)mypremieronline.com> wrote: > My $DAYJOB employer, Premier Communications (AS53347) is planning to move > our interconnection with MICE to FiberNet (AS18883). I'm the technical > contact for both. > > Can we get another IX IP to accomplish this transition? > Organizationally, what, if anything, do I need to do with MICE? > > I know that I will need to make changes with all our direct peers, too. So > I would need both IPs for a while. > > Regards, > > Frank >

June 1, 2018

Changing hats

by Frank Bulk

My $DAYJOB employer, Premier Communications (AS53347) is planning to move our interconnection with MICE to FiberNet (AS18883). I'm the technical contact for both. Can we get another IX IP to accomplish this transition? Organizationally, what, if anything, do I need to do with MICE? I know that I will need to make changes with all our direct peers, too. So I would need both IPs for a while. Regards, Frank

June 1, 2018

Re: RFC: Remote Switch in Duluth

by Justin Krejci

This message is one-part "no opposition" to this request as long as standard expectations and policies are adhered to. This message is also one-part "pulse check" as the list has been rather silent the last few weeks. Hopefully that just means no problems and everyone is busy taking care of their respective business. ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Abhi Devireddy <abhi(a)DEVIREDDY.COM> Sent: Friday, May 11, 2018 5:30 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] RFC: Remote Switch in Duluth Good evening, I represent 2 different networks in different capacities, AS53740 (optbit, personal research and education) and AS3789 (Essentia Health, https://www.essentiahealth.org/about/) Both networks are based out of Duluth and neither of them are current members of MICE. A remote switch in Duluth would lower the barrier to entry for a number of organizations that provide regional content and resources. For AS3789, it would mean providing better access to telehealth resources in a traditionally underserved region where high latencies and low bandwidth have caused slow adoption. I would be in favor of a remote switch in Duluth. Thanks, Abhi -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Friday, May 11, 2018 2:52 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] RFC: Remote Switch in Duluth The following is from Ryan Goldberg of Compudyne: ---- Compudyne/AS47096 is interested in operating a MICE remote switch in Duluth. We have two 10G paths from 511 to Duluth (one on Charter, one on Enventis) in a ring of 5 Juniper MX boxes (2 at 511, 3 in Duluth - the 3 in Duluth are interconnected over dark fiber). We hit a little over 5G on 5min averages in total between the two 511<->Duluth legs. Latency is 4-5ms. We currently participate in MICE via MNVoip's extension, mainly because it makes more overall sense to pick up MICE + SIX + Denver + KC all on one interface (for now). We'd probable leave it like that for a while. For the proposed extension switch we'd do a two site VPLS config on the MXes, with on a fresh, dedicated 10gig port at 511 and corresponding 10gig port in Duluth. We'd start with an EX4200-24F in Duluth, and run the usual Juniper-y stuff (from http://micemn.net/technical.html) Initial participants would only be on 1gig ports on the 4200. As for location, we're currently leaning toward "the Missabe Building" at 227 W 1st St, Duluth, MN - this is our primary downtown Duluth POP, and aside from our fiber, and there's high-count fiber from at least 5 other carriers in the building. The space has dual AC and is backed by generator power. Upgrade path is 100G 511<->Duluth, at least on one leg. If business drives it, we'll just do it. Otherwise it's budgeted for next year. As for the switch, we'd move to a ex4550. ---- Without taking any position on this here yet, I'd like to highlight a couple of facts: The proposed transport is over a VPLS link (i.e. shared with other traffic, not a dedicated wave). In the past, and quite possibly still, we have had participants connected over shared links, but not entire remote switches. -- Richard

May 31, 2018

Re: RFC: Remote Switch in Duluth

by Abhi Devireddy

Good evening, I represent 2 different networks in different capacities, AS53740 (optbit, personal research and education) and AS3789 (Essentia Health, https://www.essentiahealth.org/about/) Both networks are based out of Duluth and neither of them are current members of MICE. A remote switch in Duluth would lower the barrier to entry for a number of organizations that provide regional content and resources. For AS3789, it would mean providing better access to telehealth resources in a traditionally underserved region where high latencies and low bandwidth have caused slow adoption. I would be in favor of a remote switch in Duluth. Thanks, Abhi -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Friday, May 11, 2018 2:52 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] RFC: Remote Switch in Duluth The following is from Ryan Goldberg of Compudyne: ---- Compudyne/AS47096 is interested in operating a MICE remote switch in Duluth. We have two 10G paths from 511 to Duluth (one on Charter, one on Enventis) in a ring of 5 Juniper MX boxes (2 at 511, 3 in Duluth – the 3 in Duluth are interconnected over dark fiber). We hit a little over 5G on 5min averages in total between the two 511<->Duluth legs. Latency is 4-5ms. We currently participate in MICE via MNVoip’s extension, mainly because it makes more overall sense to pick up MICE + SIX + Denver + KC all on one interface (for now). We’d probable leave it like that for a while. For the proposed extension switch we’d do a two site VPLS config on the MXes, with on a fresh, dedicated 10gig port at 511 and corresponding 10gig port in Duluth. We’d start with an EX4200-24F in Duluth, and run the usual Juniper-y stuff (from http://micemn.net/technical.html) Initial participants would only be on 1gig ports on the 4200. As for location, we’re currently leaning toward “the Missabe Building” at 227 W 1st St, Duluth, MN – this is our primary downtown Duluth POP, and aside from our fiber, and there’s high-count fiber from at least 5 other carriers in the building. The space has dual AC and is backed by generator power. Upgrade path is 100G 511<->Duluth, at least on one leg. If business drives it, we’ll just do it. Otherwise it’s budgeted for next year. As for the switch, we’d move to a ex4550. ---- Without taking any position on this here yet, I'd like to highlight a couple of facts: The proposed transport is over a VPLS link (i.e. shared with other traffic, not a dedicated wave). In the past, and quite possibly still, we have had participants connected over shared links, but not entire remote switches. -- Richard

May 11, 2018

RFC: Remote Switch in Duluth

by Richard Laager

The following is from Ryan Goldberg of Compudyne: ---- Compudyne/AS47096 is interested in operating a MICE remote switch in Duluth. We have two 10G paths from 511 to Duluth (one on Charter, one on Enventis) in a ring of 5 Juniper MX boxes (2 at 511, 3 in Duluth – the 3 in Duluth are interconnected over dark fiber). We hit a little over 5G on 5min averages in total between the two 511<->Duluth legs. Latency is 4-5ms. We currently participate in MICE via MNVoip’s extension, mainly because it makes more overall sense to pick up MICE + SIX + Denver + KC all on one interface (for now). We’d probable leave it like that for a while. For the proposed extension switch we’d do a two site VPLS config on the MXes, with on a fresh, dedicated 10gig port at 511 and corresponding 10gig port in Duluth. We’d start with an EX4200-24F in Duluth, and run the usual Juniper-y stuff (from http://micemn.net/technical.html) Initial participants would only be on 1gig ports on the 4200. As for location, we’re currently leaning toward “the Missabe Building” at 227 W 1st St, Duluth, MN – this is our primary downtown Duluth POP, and aside from our fiber, and there’s high-count fiber from at least 5 other carriers in the building. The space has dual AC and is backed by generator power. Upgrade path is 100G 511<->Duluth, at least on one leg. If business drives it, we’ll just do it. Otherwise it’s budgeted for next year. As for the switch, we’d move to a ex4550. ---- Without taking any position on this here yet, I'd like to highlight a couple of facts: The proposed transport is over a VPLS link (i.e. shared with other traffic, not a dedicated wave). In the past, and quite possibly still, we have had participants connected over shared links, but not entire remote switches. -- Richard

May 11, 2018

Re: Neutral Path link issue between Belle Plaine and MICE

by Jeremy Schmeichel

Splicing complete and NP is hands off for now, I’m sure a permanent repair will be done at a later date. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Saturday, May 05, 2018 5:35 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Neutral Path link issue between Belle Plaine and MICE I’m seeing BGP sessions restored and routes learned! Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Frank Bulk Sent: Saturday, May 5, 2018 6:27 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Neutral Path link issue between Belle Plaine and MICE Update received a few minutes ago: The splice crew is still in the process of installing the new cable. If everything goes according to plan, splicing will begin in about an hour. No ETR at this time, but we will continue to provide updates as they become available. Frank From: Frank Bulk Sent: Saturday, May 5, 2018 4:45 PM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Subject: RE: [MICE-DISCUSS] Neutral Path link issue between Belle Plaine and MICE Update received a few minutes ago: The splicing crew is now on site and are beginning to install the new cable. No ETR at this time. Frank From: Frank Bulk Sent: Saturday, May 5, 2018 2:59 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] Neutral Path link issue between Belle Plaine and MICE Last two updates from the NOC: 2:05 pm: Crews now have cable materials in-hand and should arrive at the site at approximately 3:30 pm central. It is estimated that the cable install will take at least 3.5 hours. Splicing will follow the install. Once splicing begins, an ETR might be available. 2:45 pm: Crews with the materials anticipate arriving at site in approximately 30 minutes. Is this the river crossing? https://www.google.com/maps/place/44%C2%B037'59.5%22N+93%C2%B045'56.7%22W/@44.6331841,-93.7745168,3083m/data=!3m2!1e3!4b1!4m14!1m7!3m6!1s0x87f5dfb93721879d:0x24b9fe962f7ae1fb!2sBelle+Plaine,+MN!3b1!8m2!3d44.6230409!4d-93.7684042!3m5!1s0x0:0x0!7e2!8m2!3d44.6331854!4d-93.7657624 Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of James Urwiller Sent: Saturday, May 5, 2018 1:05 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Neutral Path link issue between Belle Plaine and MICE ☹ indeed. I just got off the phone with them, about an hour ago they determined the fiber across the river is completely compromised and they are working to get a temporary drop across the river to restore services. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com<mailto:james.urwiller@stealthbroadband.com> [stealth300] From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Justin Krejci Sent: Saturday, May 5, 2018 13:01 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Neutral Path link issue between Belle Plaine and MICE Also, Neutral Path is now wholly owned by Zayo, FYI. :( -----Original Message----- From: anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> [anthonyanderberg(a)NU-TELECOM.NET<mailto:anthonyanderberg@NU-TELECOM.NET>] Received: Saturday, 05 May 2018, 11:42AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> [MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>] Subject: Re: [MICE-DISCUSS] Neutral Path link issue between Belle Plaine and MICE It looked like the river was quite high when I was through Belle Plaine yesterday, if that’s the location of the trouble I bet the crews are having to work around that huge mess. Sent from my iPhone On May 5, 2018, at 6:34 AM, Frank Bulk <fbulk(a)MYPREMIERONLINE.COM<mailto:fbulk@MYPREMIERONLINE.COM>> wrote: I woke up this morning to see emails about our BGP sessions with MICE to be down. Look at alarms and graphs I see that the link from Belle Plaine to MICE is down since about 12:39 am. According to the NeutralPath NOC (operated by WINS?), something about how a temporary fiber fix for emergency fiber work failed? I wasn’t even aware of any emergency fiber work. The NOC said that a tech was dispatched and he was hoping they would be able to fix it in the next few hours. Frank ________________________________ 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 ________________________________ 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

May 6, 2018