May 2025 - mice-discuss - lists.micemn.net

RE: Non-MICE/perhaps dumb question

by Frank Bulk

Thanks for everyone's input and feedback. I ended up having a call with Cologix to get a better understanding of AWS' product and how it works. I shared this with our customer and have not yet received a response. Frank Frank Bulk -----Original Message----- From: Mike Horwath <drechsau(a)geeks.org> Sent: Saturday, April 26, 2025 9:30 AM To: Frank Bulk <fbulk(a)mypremieronline.com> Cc: mice-discuss(a)lists.micemn.net Subject: Re: Non-MICE/perhaps dumb question On Fri, Apr 25, 2025 at 08:53:28PM +0000, Frank Bulk wrote: > Is that just the reality of it, or is there a broader product (other > than direct peering with Amazon) that would improve AWS performance > for all our customers? Is your customer willing to cover costs for direct connect? In my experience, this is very performant (depending on link speed you choose). Are they pushing into S3, some API endpoint, custom app, over SSH or FTP or another protocol? From home (over the comcastic networkz) I can saturate my upload (~350Mbps) without issue, and lab environment (~500Mbps, Atomic Data) can also hit the peak. This is over SSH (into instances) or S3 endpoints. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

May 29, 2025

Please welcome Microsoft to MICE!

by Jeremy Lumby

Name: Microsoft Location: MICE Core 511 Ports: adding E3/1/1 to portchannel 35 (Arista 7504R) and adding E 3/8/1 to portchannel 11 (Arista 7804 R3)for a total of 2x2x100G ASN: 8075 IPv4: All IP info remains the same, this is a 2x100G port addition IPv6: Peering Contact: peering(a)microsoft.com Route Servers: NO Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

May 15, 2025

Please welcome Accuris Technologies to MICE!

by Jeremy Lumby

Name: Accuris Technologies Ltd. Switch: NOCIX Port: Ethernet 5/19 (10G) ASN: 52210 IPv4: 206.108.255.12/24 IPv6: 2001:504:27:0:0:CBF2::1/64 Peering Contact: domainsupport(a)accur.is Route Servers: YES Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

May 9, 2025

Please welcome BIFIV Intrepid OpCo, LLC to MICE!

by Jeremy Lumby

Name: BIFIV Intrepid OpCo, LLC Switch: MN VoIP 100G Port: E 12/1 ASN: 394056 IPv4: This is a port upgrade to 100G all IP info stays the same. IPv6: Peering Contact: peering(a)intrepidfiber.com Route Servers: NO Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

May 9, 2025

Please welcome Fort Dodge Fiber to MICE!

by Jeremy Lumby

Name: City of Fort Dodge dba Fort Dodge Fiber Switch: SouthFront Networks 10G Ports: Adding E2 for a total of 2x10G ASN: 400405 IPv4: This is a port addition, all IP info stays the same IPv6: Peering Contact: noc(a)fortdodgefiber.net Route Servers: YES Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

May 9, 2025

RE: MICE connectivity issues / elevated multicast traffic

by Jeremy Lumby

Can I ask why port security did not trip on your MICE extension switch? From: Dean Bahls <dean.bahls(a)fiberminnesota.com> Sent: Thursday, May 1, 2025 7:18 AM To: Richard Laager <rlaager(a)micemn.net>; mice-discuss(a)lists.micemn.net Cc: Andrew Lambertson <andrew.lambertson(a)fiberminnesota.com> Subject: RE: MICE connectivity issues / elevated multicast traffic Oh man, we were definitely the cause of this. We were troubleshooting a transponder card and put it into loopback without thinking about MICE consequences. We will make sure that doesn’t happen in the future. Please accept our sincere apologies for causing havoc. Dean From: Richard Laager <rlaager(a)micemn.net <mailto:rlaager@micemn.net> > Sent: Wednesday, April 30, 2025 9:04 PM To: mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> Subject: Re: MICE connectivity issues / elevated multicast traffic It sounds like we had a loop of some kind on the Fiber Minnesota extension switch. It was almost certainly, in some way, related to work they were doing. They are going to investigate further in the morning to try to understand what, specifically, happened. -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

May 1, 2025

RE: MICE connectivity issues / elevated multicast traffic

by Dean Bahls

Oh man, we were definitely the cause of this. We were troubleshooting a transponder card and put it into loopback without thinking about MICE consequences. We will make sure that doesn’t happen in the future. Please accept our sincere apologies for causing havoc. Dean From: Richard Laager <rlaager(a)micemn.net> Sent: Wednesday, April 30, 2025 9:04 PM To: mice-discuss(a)lists.micemn.net Subject: Re: MICE connectivity issues / elevated multicast traffic It sounds like we had a loop of some kind on the Fiber Minnesota extension switch. It was almost certainly, in some way, related to work they were doing. They are going to investigate further in the morning to try to understand what, specifically, happened. -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

May 1, 2025

Re: MICE connectivity issues / elevated multicast traffic

by Richard Laager

It sounds like we had a loop of some kind on the Fiber Minnesota extension switch. It was almost certainly, in some way, related to work they were doing. They are going to investigate further in the morning to try to understand what, specifically, happened. -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

May 1, 2025