- mice-discuss - lists.micemn.net

RE: MICE connectivity issues / elevated multicast traffic

by Sergii Polishchuk

We lost connection with both route-servers for a minute and direct peering with some members (but not all): Apr 30 14:02:18: %BGP-5-NBR_RESET: Neighbor 206.108.255.2 reset (BFD adjacency down) Apr 30 14:02:19: %BGP-5-ADJCHANGE: neighbor 206.108.255.2 Down BFD adjacency down Apr 30 14:02:19: %BGP_SESSION-5-ADJCHANGE: neighbor 206.108.255.2 IPv4 Unicast topology base removed from session BFD adjacency down Apr 30 14:02:35: %BGP-5-NBR_RESET: Neighbor 206.108.255.2 active reset (Peer closed the session) Apr 30 14:03:13: %BGP-5-ADJCHANGE: neighbor 206.108.255.2 Up Ping to AS42: Ping to AS6939: <https://www.facebook.com/InfotecManitoba> <https://twitter.com/InfotecManitoba> <https://www.linkedin.com/in/sergip/> Sergi Infotec Manitoba <tel:(844)%20777-3744> (844) 777-3744 <mailto:sergi@infotec.ca> sergi(a)infotec.ca <https://infotec.ca/> https://infotec.ca From: Ryan Nelson via mice-discuss <mice-discuss(a)lists.micemn.net> Sent: April 30, 2025 15:02 To: mice-discuss(a)lists.micemn.net Subject: MICE connectivity issues / elevated multicast traffic Anyone else seeing some connectivity issues over MICE coinciding with an uptick in multicast traffic coming from the core starting at around 2:10pm CDT? Ryan Nelson Architect, Platform Services Office: <tel:(218)%20336-2220> (218) 336-2220 <mailto:ryan.nelson@integrisit.com> ryan.nelson(a)integrisit.com <https://integrisit.com/> <https://integrisit.com/resources/> Integris Engage: Check out upcoming Education, Training & Networking

April 30, 2025

MICE connectivity issues / elevated multicast traffic

by Ryan Nelson

Anyone else seeing some connectivity issues over MICE coinciding with an uptick in multicast traffic coming from the core starting at around 2:10pm CDT? Ryan Nelson Architect, Platform Services Office: (218) 336-2220<tel:(218)%20336-2220> ryan.nelson(a)integrisit.com<mailto:ryan.nelson@integrisit.com> [cid:image854150.png]<https://integrisit.com/> Integris Engage<https://integrisit.com/resources/>: Check out upcoming Education, Training & Networking

April 30, 2025

Re: MICE at 2T

by Anthony Anderberg

The good news is that I’ve finally (!) had a block of time to work on this - and am confident that the Aggregate graph now reflects reality, both today and historically. The bad news is that I was correct that I’d been double counting a few hundred gig by including ports that Jeremy added to our backbone links during this spring’s changes, so we’re back under 2T - for now at least. Cheers, Anthony From: David Farmer <farmer(a)umn.edu> Date: Saturday, March 29, 2025 at 7:33 PM To: Anthony Anderberg <AnthonyAnderberg(a)nuvera.net> Cc: "mice-discuss(a)lists.micemn.net" <mice-discuss(a)lists.micemn.net> Subject: Re: MICE at 2T Have you been able to validate the graphs? Are we regularly gating to 2 Tb now? On Sun, Mar 23, 2025 at 10:39 PM Anthony Anderberg <AnthonyAnderberg(a)nuvera.net<mailto:AnthonyAnderberg@nuvera.net>> wrote: I think I might be double-counting the packets that transverse the 511 building 7504-7804 link… I’ll look at that tomorrow and verify if I excluded the members of that LAG properly. Cheers, Anthony Sent from my iPhone On Mar 22, 2025, at 7:35 PM, David Farmer via mice-discuss <mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net>> wrote: I think Mice broke 2T in the last few days. But I'm having a hard time getting to the cacti graphs to confirm. Thanks. =============================================== David Farmer Email:farmer@umn.edu<mailto:Email%3Afarmer@umn.edu> Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== _______________________________________________ mice-discuss mailing list -- mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net> To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net<mailto:mice-discuss-leave@lists.micemn.net> -- =============================================== David Farmer Email:farmer@umn.edu<mailto:Email%3Afarmer@umn.edu> Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

April 30, 2025

Re: Non-MICE/perhaps dumb question

by Mike Horwath

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

April 26, 2025

RE: Non-MICE/perhaps dumb question

by Jeremy Lumby

Correct, Waves are very transparent to errors and the carrier selling them cannot oversubscribe them, as well as the path is known and not easily changed. Most IXes are quite transparent, and require extension uplink upgrades at 66% as well as path diversity. You get a lot of stability/predictability since most of those things you do not get if you are just buying transit. From: Ben Wiechman via mice-discuss <mice-discuss(a)lists.micemn.net> Sent: Friday, April 25, 2025 4:51 PM To: Jeremy Lumby <jlumby(a)mnvoip.com> Cc: mice-discuss(a)lists.micemn.net Subject: Re: Non-MICE/perhaps dumb question So your solution is to provide transport to a location closer to the AWS region, and then the customer establishes a private connection to AWS from there? Megaport may provide a similar transport concept. They have transport to many different DC in the US, and also had a cloud router product designed to allow remote routing for public cloud traffic w/o installing hardware the remote DC. I haven't looked at their solution in a long time to give a better judgement call regarding its viability for this use case, or whether it would only be useful on a customer by customer basis where each customer would need to have their own instance of the cloud switching in relevant data centers. This may also only be useful if direct connectivity would provide a benefit or if the customer has a lot of E/W traffic that could route remotely between public cloud applications. Ben Wiechman Director of Network Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com <mailto:ben.wiechman@arvig.com> Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com <http://arvig.com> On Fri, Apr 25, 2025 at 4:23 PM Jeremy Lumby <jlumby(a)mnvoip.com <mailto:jlumby@mnvoip.com> > wrote: I do have customers that utilize my extension switches to other IXes so that they can connect to Amazon directly in other regions. Unfortunately I have a west coast option, and you are looking for an east coast option. From: Frank Bulk <fbulk(a)mypremieronline.com <mailto:fbulk@mypremieronline.com> > Sent: Friday, April 25, 2025 3:53 PM To: mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> Subject: Non-MICE/perhaps dumb question I’ve been reviewing some of AWS’s connectivity products, but it seems like none of them are designed to improve the AWS experience for all of an ISP’s customers across AWS’s various regions. The background here is that we have a business customer using a key application hosted in AWS’s East Coast region. The applications’ document upload performance has been less than ideal, and their external consultant is blaming their ISP — us. As you know, once traffic leaves our network and hits upstream providers, our influence on the experience is very limited. My initial thought was to explore whether we could bring AWS closer to all of our customers through some kind of direct peering or other arrangement with AWS. However, from what I’m seeing, AWS’s connectivity options are mostly targeted at connecting a single enterprise to AWS, not enhancing general public access to AWS services. 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? Frank Frank Bulk Chief Technology Officer / Chief Operating Officer 339 1st Ave NE | Sioux Center, IA 51250 | <https://www.facebook.com/PremierCommunicationsSiouxCenter> Find us on Facebook phone: 712.722.3451 web: mypremieronline.com <https://www.mypremieronline.com/> direct: (712) 722-7152 cell: (712) 441-6049 _______________________________________________ mice-discuss mailing list -- mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net <mailto:mice-discuss-leave@lists.micemn.net>

April 25, 2025

Re: Non-MICE/perhaps dumb question

by Ben Wiechman

So your solution is to provide transport to a location closer to the AWS region, and then the customer establishes a private connection to AWS from there? Megaport may provide a similar transport concept. They have transport to many different DC in the US, and also had a cloud router product designed to allow remote routing for public cloud traffic w/o installing hardware the remote DC. I haven't looked at their solution in a long time to give a better judgement call regarding its viability for this use case, or whether it would only be useful on a customer by customer basis where each customer would need to have their own instance of the cloud switching in relevant data centers. This may also only be useful if direct connectivity would provide a benefit or if the customer has a lot of E/W traffic that could route remotely between public cloud applications. Ben Wiechman Director of Network Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com On Fri, Apr 25, 2025 at 4:23 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > I do have customers that utilize my extension switches to other IXes so > that they can connect to Amazon directly in other regions. Unfortunately > I have a west coast option, and you are looking for an east coast option. > > > > *From:* Frank Bulk <fbulk(a)mypremieronline.com> > *Sent:* Friday, April 25, 2025 3:53 PM > *To:* mice-discuss(a)lists.micemn.net > *Subject:* Non-MICE/perhaps dumb question > > > > I’ve been reviewing some of AWS’s connectivity products, but it seems like > none of them are designed to improve the AWS experience for all of an ISP’s > customers across AWS’s various regions. > > > > The background here is that we have a business customer using a key > application hosted in AWS’s East Coast region. The applications’ document > upload performance has been less than ideal, and their external consultant > is blaming their ISP — us. As you know, once traffic leaves our network and > hits upstream providers, our influence on the experience is very limited. > My initial thought was to explore whether we could bring AWS closer to all > of our customers through some kind of direct peering or other arrangement > with AWS. > > > > However, from what I’m seeing, AWS’s connectivity options are mostly > targeted at connecting a single enterprise to AWS, not enhancing general > public access to AWS services. > > > > 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? > > > > Frank > > *Frank Bulk* > > *Chief Technology Officer / Chief Operating Officer* > > [image: PremierComm_logo_CMYK.png] > > 339 1st Ave NE *|* Sioux Center, IA 51250 *|* Find us on Facebook > <https://www.facebook.com/PremierCommunicationsSiouxCenter> > > *phone:* 712.722.3451 *web:* mypremieronline.com > <https://www.mypremieronline.com/> > *direct: *(712) 722-7152 *cell:* (712) 441-6049 > > > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net >

April 25, 2025

RE: Non-MICE/perhaps dumb question

by Jeremy Lumby

I do have customers that utilize my extension switches to other IXes so that they can connect to Amazon directly in other regions. Unfortunately I have a west coast option, and you are looking for an east coast option. From: Frank Bulk <fbulk(a)mypremieronline.com> Sent: Friday, April 25, 2025 3:53 PM To: mice-discuss(a)lists.micemn.net Subject: Non-MICE/perhaps dumb question I've been reviewing some of AWS's connectivity products, but it seems like none of them are designed to improve the AWS experience for all of an ISP's customers across AWS's various regions. The background here is that we have a business customer using a key application hosted in AWS's East Coast region. The applications' document upload performance has been less than ideal, and their external consultant is blaming their ISP - us. As you know, once traffic leaves our network and hits upstream providers, our influence on the experience is very limited. My initial thought was to explore whether we could bring AWS closer to all of our customers through some kind of direct peering or other arrangement with AWS. However, from what I'm seeing, AWS's connectivity options are mostly targeted at connecting a single enterprise to AWS, not enhancing general public access to AWS services. 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? Frank Frank Bulk Chief Technology Officer / Chief Operating Officer 339 1st Ave NE | Sioux Center, IA 51250 | <https://www.facebook.com/PremierCommunicationsSiouxCenter> Find us on Facebook phone: 712.722.3451 web: mypremieronline.com <https://www.mypremieronline.com/> direct: (712) 722-7152 cell: (712) 441-6049

April 25, 2025

Non-MICE/perhaps dumb question

by Frank Bulk

I've been reviewing some of AWS's connectivity products, but it seems like none of them are designed to improve the AWS experience for all of an ISP's customers across AWS's various regions. The background here is that we have a business customer using a key application hosted in AWS's East Coast region. The applications' document upload performance has been less than ideal, and their external consultant is blaming their ISP - us. As you know, once traffic leaves our network and hits upstream providers, our influence on the experience is very limited. My initial thought was to explore whether we could bring AWS closer to all of our customers through some kind of direct peering or other arrangement with AWS. However, from what I'm seeing, AWS's connectivity options are mostly targeted at connecting a single enterprise to AWS, not enhancing general public access to AWS services. 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? Frank [cid:a1ff5d57-4afc-4ec0-be61-51708bf94a4e.png] Frank Bulk Chief Technology Officer / Chief Operating Officer [cid:premiercomm_logo_cmyk_1388ffcb-8ec0-4842-9e40-a0e598482e7d.png] 339 1st Ave NE | Sioux Center, IA 51250 | Find us on Facebook<https://www.facebook.com/PremierCommunicationsSiouxCenter> phone: 712.722.3451 web: mypremieronline.com<https://www.mypremieronline.com/> direct: (712) 722-7152 cell: (712) 441-6049

April 25, 2025

Re: Qwilt question

by David Farmer

According to the MICE port graphing, Qwilt's traffic recovered somewhat in late February. However, since February, we haven't seen any local traffic for Qwilt. [image: image.png] Thanks On Fri, Feb 14, 2025 at 1:04 PM Richard Laager <rlaager(a)micemn.net> wrote: > On 2025-02-13 08:20, Steve Savoy wrote: > > Has anyone heard anymore information on Qwilt and when the peering might > be back up? > > > I think it is very unlikely they will be reconnecting soon. > > They haven't paid in a year and are being disconnected for non-payment. > > -- > Richard Laager > Chief Manager, Director > Midwest Internet Cooperative Exchange LLC > > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

April 23, 2025

Please welcome Cato Networks to MICE!

by Jeremy Lumby

Name: Cato Networks Inc Switch: MICE Core 511-100G 7504 Port: Ethernet 4/21 (10G) ASN: 13150 IPv4: 206.108.255.9/24 IPv6: 2001:504:27::335e:0:1/64 Peering Contact: peering(a)catonetworks.com 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

March 30, 2025