- mice-discuss - lists.micemn.net

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

Re: MICE at 2T

by David Farmer

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> 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> 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 > 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 > 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 ===============================================

March 30, 2025

RE: Amazon bouncing

by Steve Savoy

I thought it might have been fixed as it stayed steady all night but I see it just flapped again 2 hrs ago. Steve Savoy WCTA From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Thursday, March 27, 2025 3:01 PM To: mice-discuss(a)lists.micemn.net Subject: RE: Amazon bouncing As some background information Amazon has been migrating from 2x4x100G to 2x2x400G. When they migrated their first link to 400G it worked fine until they linked their old 100G ports up again (the ones that they had appeared to have migrated away from), and then the loss started. I let Amazon know, but I did not react since they were still mid migration, and it only impacted Amazon. Last night they finished the migration, and I received an official completion notice. It was running fine until about an hour ago. Coincidentally at that exact time one of their old 4x100G LAGs came back online. Since I had received a completion notice, this time I went ahead and forcibly shutdown their old 100G ports, and things have seemed stable since then. Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com<mailto:jlumby@mnvoip.com> From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net>> Sent: Thursday, March 27, 2025 2:04 PM To: mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net> Subject: Amazon bouncing Has anyone else's Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 [cid:image001.gif@01DB9FB5.410EFD80]<https://youtu.be/A_tgcHZD6oA>[cid:image002.gif@01DB9FB5.410EFD80]<https://twitter.com/connectctc>[cid:image003.gif@01DB9FB5.410EFD80]<https://www.facebook.com/connectctc>goctc.com<http://www.goctc.com/> [cid:image004.gif@01DB9FB5.410EFD80]<https://www.goctc.com/> Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

March 28, 2025

RE: Amazon bouncing

by Jeremy Lumby

The MICE order form does encourage every member to signup for the mailing lists. MICE posts as many new member connections, as well as upgrades to the list as possible. Beyond that it would be up to the member to share their specific maintenance details on the list. From: nanog(a)jima.us <nanog(a)jima.us> Sent: Thursday, March 27, 2025 2:51 PM To: mice-discuss(a)lists.micemn.net Subject: RE: [EXTERNAL] Amazon bouncing Someone should come up with a way to preemptively give all potential peers at a given IX a heads-up as to maintenance events like that, so that all of the other participants didn’t have to individually troubleshoot the failure condition, work out amongst themselves what was going on, and possibly multiple of them reach out to inquire. I think something like that would really be popular. 👀 (Thanks for passing that along, Ryan!) - Jima From: Ryan Gunther via mice-discuss <mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> > Sent: Thursday, March 27, 2025 14:21 To: Shawn Rasmussen <shawnr(a)goctc.com <mailto:shawnr@goctc.com> >; mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> Subject: RE: [EXTERNAL] Amazon bouncing Hi Shawn – We have been seeing lots of the same over the past week or two. Bounces every minute for hours until we shut down our sessions. It took a few emails to Amazon to get a response – but I did receive the following back from them just the other day – Dear partner, Thank you for your inquiry. We're currently in the process of a significant infrastructure upgrade, which involves relocating this circuit to our new fabric. Our team has initiated the turndown process, which will be followed by a cable migration. While we don't have a specific ETA for the completion of this work, please be assured that our team is working diligently to restore capacity as quickly as possible. No action is required from your end at this time. We will keep you informed of any significant developments or if any action becomes necessary. We understand the inconvenience this may cause and sincerely appreciate your patience during this important upgrade process. If you have any questions or concerns, please don't hesitate to reach out. Regards, Ryan Gunther Network & Switching Engineer CCNA, MEF-CECP, A+ (406) 234-7458 105 N Montana Ave., Miles City, MT 59301 <https://www.midrivers.com/> www.midrivers.com <https://www.midrivers.com/> <https://facebook.com/midrivers> <https://www.instagram.com/midriverscommunications/> <https://www.linkedin.com/company/mid-rivers-communications/> <http://www.google.com/search?q=Mid-Rivers+Communications,1101%20Main%20St.,…> Review Us on Google From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> > Sent: Thursday, March 27, 2025 1:04 PM To: mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> Subject: [EXTERNAL] Amazon bouncing Notice: External Source: Confirm authenticity, stay secure. Has anyone else’s Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 <http://www.goctc.com/> goctc.com _____

March 27, 2025

RE: Amazon bouncing

by Jeremy Lumby

As some background information Amazon has been migrating from 2x4x100G to 2x2x400G. When they migrated their first link to 400G it worked fine until they linked their old 100G ports up again (the ones that they had appeared to have migrated away from), and then the loss started. I let Amazon know, but I did not react since they were still mid migration, and it only impacted Amazon. Last night they finished the migration, and I received an official completion notice. It was running fine until about an hour ago. Coincidentally at that exact time one of their old 4x100G LAGs came back online. Since I had received a completion notice, this time I went ahead and forcibly shutdown their old 100G ports, and things have seemed stable since then. Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net> Sent: Thursday, March 27, 2025 2:04 PM To: mice-discuss(a)lists.micemn.net Subject: Amazon bouncing Has anyone else's Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 <https://youtu.be/A_tgcHZD6oA> <https://twitter.com/connectctc> <https://www.facebook.com/connectctc> <http://www.goctc.com/> goctc.com- <https://www.goctc.com/> -

March 27, 2025

Re: [EXTERNAL] Amazon bouncing

by Andrew Hoyos

RFC9003 is a thing - https://www.rfc-editor.org/rfc/rfc9003.html Juniper example: https://www.juniper.net/documentation/us/en/software/junos/cli-reference/to… I know a lot of folks using this, and it is indeed very helpful to not waste resources chasing down BGP peers. Andrew Hoyos hoyosa(a)gmail.com > On Mar 27, 2025, at 14:51, nanog(a)jima.us wrote: > > Someone should come up with a way to preemptively give all potential peers at a given IX a heads-up as to maintenance events like that, so that all of the other participants didn’t have to individually troubleshoot the failure condition, work out amongst themselves what was going on, and possibly multiple of them reach out to inquire. > > I think something like that would really be popular. > > 👀 > > (Thanks for passing that along, Ryan!) > > - Jima > > From: Ryan Gunther via mice-discuss <mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net>> > Sent: Thursday, March 27, 2025 14:21 > To: Shawn Rasmussen <shawnr(a)goctc.com <mailto:shawnr@goctc.com>>; mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> > Subject: RE: [EXTERNAL] Amazon bouncing > > Hi Shawn – > We have been seeing lots of the same over the past week or two. Bounces every minute for hours until we shut down our sessions. It took a few emails to Amazon to get a response – but I did receive the following back from them just the other day – > > > Dear partner, > > Thank you for your inquiry. We're currently in the process of a significant infrastructure upgrade, which involves relocating this circuit to our new fabric. Our team has initiated the turndown process, which will be followed by a cable migration. > > While we don't have a specific ETA for the completion of this work, please be assured that our team is working diligently to restore capacity as quickly as possible. > > No action is required from your end at this time. We will keep you informed of any significant developments or if any action becomes necessary. > > We understand the inconvenience this may cause and sincerely appreciate your patience during this important upgrade process. If you have any questions or concerns, please don't hesitate to reach out. > > Regards, > > > <image001.png> > <image002.png> > Ryan Gunther > Network & Switching Engineer > CCNA, MEF-CECP, A+ > (406) 234-7458 > 105 N Montana Ave., Miles City, MT 59301 > www.midrivers.com <https://www.midrivers.com/> > <image003.png> <https://www.midrivers.com/> <image004.png> <image005.png> <https://facebook.com/midrivers> <image006.png> <https://www.instagram.com/midriverscommunications/> <image007.png> <https://www.linkedin.com/company/mid-rivers-communications/> > Review Us on Google <http://www.google.com/search?q=Mid-Rivers+Communications,1101%20Main%20St.,…> > > > From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net>> > Sent: Thursday, March 27, 2025 1:04 PM > To: mice-discuss(a)lists.micemn.net <mailto:mice-discuss@lists.micemn.net> > Subject: [EXTERNAL] Amazon bouncing > > Notice: External Source: Confirm authenticity, stay secure. > Has anyone else’s Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? > > Thanks, > > SHAWN > RASMUSSEN > Network Manager > D: (218) 454-1106 > <image008.gif> <https://youtu.be/A_tgcHZD6oA><image009.gif> <https://twitter.com/connectctc><image010.gif> <https://www.facebook.com/connectctc>goctc.com <http://www.goctc.com/> > <image011.gif> <https://www.goctc.com/> > > > > > > > > _______________________________________________ > 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>

March 27, 2025

RE: [EXTERNAL] Amazon bouncing

by nanog＠jima.us

Someone should come up with a way to preemptively give all potential peers at a given IX a heads-up as to maintenance events like that, so that all of the other participants didn’t have to individually troubleshoot the failure condition, work out amongst themselves what was going on, and possibly multiple of them reach out to inquire. I think something like that would really be popular. 👀 (Thanks for passing that along, Ryan!) - Jima From: Ryan Gunther via mice-discuss <mice-discuss(a)lists.micemn.net> Sent: Thursday, March 27, 2025 14:21 To: Shawn Rasmussen <shawnr(a)goctc.com>; mice-discuss(a)lists.micemn.net Subject: RE: [EXTERNAL] Amazon bouncing Hi Shawn – We have been seeing lots of the same over the past week or two. Bounces every minute for hours until we shut down our sessions. It took a few emails to Amazon to get a response – but I did receive the following back from them just the other day – Dear partner, Thank you for your inquiry. We're currently in the process of a significant infrastructure upgrade, which involves relocating this circuit to our new fabric. Our team has initiated the turndown process, which will be followed by a cable migration. While we don't have a specific ETA for the completion of this work, please be assured that our team is working diligently to restore capacity as quickly as possible. No action is required from your end at this time. We will keep you informed of any significant developments or if any action becomes necessary. We understand the inconvenience this may cause and sincerely appreciate your patience during this important upgrade process. If you have any questions or concerns, please don't hesitate to reach out. Regards, [signature] Ryan Gunther Network & Switching Engineer CCNA, MEF-CECP, A+ (406) 234-7458 105 N Montana Ave., Miles City, MT 59301 www.midrivers.com<https://www.midrivers.com/> [logo]<https://www.midrivers.com/> [facebook] <https://facebook.com/midrivers> [instagram] <https://www.instagram.com/midriverscommunications/> [linkedin] <https://www.linkedin.com/company/mid-rivers-communications/> Review Us on Google<http://www.google.com/search?q=Mid-Rivers+Communications,1101%20Main%20St.,…> From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net>> Sent: Thursday, March 27, 2025 1:04 PM To: mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net> Subject: [EXTERNAL] Amazon bouncing Notice: External Source: Confirm authenticity, stay secure. Has anyone else’s Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 [cid:image008.gif@01DB9F27.AEA7B910]<https://youtu.be/A_tgcHZD6oA>[cid:image009.gif@01DB9F27.AEA7B910]<https://twitter.com/connectctc>[cid:image010.gif@01DB9F27.AEA7B910]<https://www.facebook.com/connectctc>goctc.com<http://www.goctc.com/> [cid:image011.gif@01DB9F27.AEA7B910]<https://www.goctc.com/> ________________________________

March 27, 2025

RE: [EXTERNAL] Amazon bouncing

by Steve Savoy

We have witnessed this as well. .111 has been up for 22 minutes .112 has been up for 11 hours [A logo with blue and green textDescription automatically generated]<https://www.wctatel.net/> Steve Savoy Network Administrator Winnebago Cooperative Telecom Association 704 E Main St | Lake Mills, IA 50450 Phone: 641.592.6105 | Toll Free: 800.592.6105 | Fax: 641.592.6102 Email: stevesavoy(a)wctatel.com<mailto:stevesavoy@wctatel.com> [cid:image015.png@01DB9F25.F4053570]<https://www.facebook.com/WCTAtel> [cid:image017.png@01DB9F25.F4053570]<https://www.instagram.com/wctatel/> [cid:image019.png@01DB9F25.F4053570]<https://www.linkedin.com/company/wctatel/> [cid:image021.png@01DB9F25.F4053570]<https://www.youtube.com/@wcta4892> [cid:image022.jpg@01DB9F25.F4053570] From: Nathan Beard <nbeard(a)7sigma.com> Sent: Thursday, March 27, 2025 2:30 PM To: Ryan Gunther <Ryan.Gunther(a)midrivers.coop> Cc: Shawn Rasmussen <shawnr(a)goctc.com>; mice-discuss(a)lists.micemn.net Subject: Re: [EXTERNAL] Amazon bouncing You don't often get email from nbeard(a)7sigma.com<mailto:nbeard@7sigma.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Stellar Association has also seen this same behavior since the MICE port moves last week, and I've reached out to Amazon a couple times and have yet to get a response. Things seemed to stabilize around 3:10am this morning so I was hopeful it was fixed, but it looks like the .111 bi-lateral is flapping again as of 1:42pm. It's worth noting that the second bi-lateral sessions appears to be stable today. If anybody else gets any detailed updates from Amazon and could post those to the list it would be much appreciated. Nathan Beard 7Sigma Systems, Inc. Senior Network Engineer (218) 820-7636 www.7sigma.com<http://www.7sigma.com/> On Thu, Mar 27, 2025 at 2:23 PM Ryan Gunther via mice-discuss <mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net>> wrote: Hi Shawn – We have been seeing lots of the same over the past week or two. Bounces every minute for hours until we shut down our sessions. It took a few emails to Amazon to get a response – but I did receive the following back from them just the other day – Dear partner, Thank you for your inquiry. We're currently in the process of a significant infrastructure upgrade, which involves relocating this circuit to our new fabric. Our team has initiated the turndown process, which will be followed by a cable migration. While we don't have a specific ETA for the completion of this work, please be assured that our team is working diligently to restore capacity as quickly as possible. No action is required from your end at this time. We will keep you informed of any significant developments or if any action becomes necessary. We understand the inconvenience this may cause and sincerely appreciate your patience during this important upgrade process. If you have any questions or concerns, please don't hesitate to reach out. Regards, [signature] Ryan Gunther Network & Switching Engineer CCNA, MEF-CECP, A+ (406) 234-7458 105 N Montana Ave., Miles City, MT 59301 www.midrivers.com<https://www.midrivers.com/> [logo]<https://www.midrivers.com/> [facebook] <https://facebook.com/midrivers> [instagram] <https://www.instagram.com/midriverscommunications/> [linkedin] <https://www.linkedin.com/company/mid-rivers-communications/> Review Us on Google<http://www.google.com/search?q=Mid-Rivers+Communications,1101%20Main%20St.,…> From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net>> Sent: Thursday, March 27, 2025 1:04 PM To: mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net> Subject: [EXTERNAL] Amazon bouncing Notice: External Source: Confirm authenticity, stay secure. Has anyone else’s Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 [cid:image008.gif@01DB9F25.E3948790]<https://youtu.be/A_tgcHZD6oA>[cid:image009.gif@01DB9F25.E3948790]<https://twitter.com/connectctc>[cid:image010.gif@01DB9F25.E3948790]<https://www.facebook.com/connectctc>goctc.com<http://www.goctc.com/> [cid:image011.gif@01DB9F25.E3948790]<https://www.goctc.com/> ________________________________ _______________________________________________ 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> Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

March 27, 2025

Re: [EXTERNAL] Amazon bouncing

by Nathan Beard

Stellar Association has also seen this same behavior since the MICE port moves last week, and I've reached out to Amazon a couple times and have yet to get a response. Things seemed to stabilize around 3:10am this morning so I was hopeful it was fixed, but it looks like the .111 bi-lateral is flapping again as of 1:42pm. It's worth noting that the second bi-lateral sessions appears to be stable today. If anybody else gets any detailed updates from Amazon and could post those to the list it would be much appreciated. *Nathan Beard* *7Sigma Systems, Inc.* Senior Network Engineer (218) 820-7636 www.7sigma.com On Thu, Mar 27, 2025 at 2:23 PM Ryan Gunther via mice-discuss < mice-discuss(a)lists.micemn.net> wrote: > Hi Shawn – > > We have been seeing lots of the same over the past week or > two. Bounces every minute for hours until we shut down our sessions. It > took a few emails to Amazon to get a response – but I did receive the > following back from them just the other day – > > > > > > Dear partner, > > > > Thank you for your inquiry. We're currently in the process of a > significant infrastructure upgrade, which involves relocating this circuit > to our new fabric. Our team has initiated the turndown process, which will > be followed by a cable migration. > > > > While we don't have a specific ETA for the completion of this work, please > be assured that our team is working diligently to restore capacity as > quickly as possible. > > > > No action is required from your end at this time. We will keep you > informed of any significant developments or if any action becomes necessary. > > > > We understand the inconvenience this may cause and sincerely appreciate > your patience during this important upgrade process. If you have any > questions or concerns, please don't hesitate to reach out. > > > > Regards, > > > > > > [image: signature] > > [image: divider] > > Ryan Gunther > > Network & Switching Engineer > > CCNA, MEF-CECP, A+ > > (406) 234-7458 > > 105 N Montana Ave., Miles City, MT 59301 > > www.midrivers.com > > [image: logo] <https://www.midrivers.com/> [image: divider] [image: > facebook] <https://facebook.com/midrivers> [image: instagram] > <https://www.instagram.com/midriverscommunications/> [image: linkedin] > <https://www.linkedin.com/company/mid-rivers-communications/> > > Review Us on Google > <http://www.google.com/search?q=Mid-Rivers+Communications,1101%20Main%20St.,…> > > > > > > *From:* Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net> > *Sent:* Thursday, March 27, 2025 1:04 PM > *To:* mice-discuss(a)lists.micemn.net > *Subject:* [EXTERNAL] Amazon bouncing > > > > *Notice:* External Source: Confirm authenticity, stay secure. > > Has anyone else’s Amazon peering been bouncing a lot lately? They are > bouncing right now for us and have sporadic periods over the last week. Are > any of you seeing the same? Anyone know anything about it? > > > > Thanks, > > > > *SHAWN* > > *RASMUSSEN* > > Network Manager > > D: (218) 454-1106 > > <https://youtu.be/A_tgcHZD6oA> <https://twitter.com/connectctc> > <https://www.facebook.com/connectctc>*goctc.com* <http://www.goctc.com/> > ** > > <https://www.goctc.com/> > > > > > > > > > > > > ------------------------------ > > > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net >

March 27, 2025

RE: Amazon bouncing

by Randy Lehs - CarverLink

Yes, we have seen the same, with the bouncing starting late last week. Randy Lehs | CarverLink Fiber Manager CarverLink - A Department of Carver County Public Services 600 East Fourth Street Chaska, MN 55318-2102 www.carverlink.com<http://www.carverlink.com/> | rlehs(a)carverlink.com<mailto:rlehs@carverlink.com> Office: 952-361-1494 | Fax: 952-361-1582 | Cell: 612-719-1656 | Standard and Emergency Support 24/7/365: 952-361-1200 From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net> Sent: Thursday, March 27, 2025 2:04 PM To: mice-discuss(a)lists.micemn.net Subject: Amazon bouncing Has anyone else's Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 [cid:image005.gif@01DB9F24.442E84E0]<https://youtu.be/A_tgcHZD6oA>[cid:image006.gif@01DB9F24.442E84E0]<https://twitter.com/connectctc>[cid:image007.gif@01DB9F24.442E84E0]<https://www.facebook.com/connectctc>goctc.com<http://www.goctc.com/> [cid:image008.gif@01DB9F24.442E84E0]<https://www.goctc.com/>

March 27, 2025

RE: [EXTERNAL] Amazon bouncing

by Ryan Gunther

Hi Shawn - We have been seeing lots of the same over the past week or two. Bounces every minute for hours until we shut down our sessions. It took a few emails to Amazon to get a response - but I did receive the following back from them just the other day - Dear partner, Thank you for your inquiry. We're currently in the process of a significant infrastructure upgrade, which involves relocating this circuit to our new fabric. Our team has initiated the turndown process, which will be followed by a cable migration. While we don't have a specific ETA for the completion of this work, please be assured that our team is working diligently to restore capacity as quickly as possible. No action is required from your end at this time. We will keep you informed of any significant developments or if any action becomes necessary. We understand the inconvenience this may cause and sincerely appreciate your patience during this important upgrade process. If you have any questions or concerns, please don't hesitate to reach out. Regards, [signature] Ryan Gunther Network & Switching Engineer CCNA, MEF-CECP, A+ (406) 234-7458 105 N Montana Ave., Miles City, MT 59301 www.midrivers.com<https://www.midrivers.com/> [logo]<https://www.midrivers.com/> [facebook] <https://facebook.com/midrivers> [instagram] <https://www.instagram.com/midriverscommunications/> [linkedin] <https://www.linkedin.com/company/mid-rivers-communications/> Review Us on Google<http://www.google.com/search?q=Mid-Rivers+Communications,1101%20Main%20St.,…> From: Shawn Rasmussen via mice-discuss <mice-discuss(a)lists.micemn.net> Sent: Thursday, March 27, 2025 1:04 PM To: mice-discuss(a)lists.micemn.net Subject: [EXTERNAL] Amazon bouncing Notice: External Source: Confirm authenticity, stay secure. Has anyone else's Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 [cid:image012.gif@01DB9F1A.F436CDC0]<https://youtu.be/A_tgcHZD6oA>[cid:image013.gif@01DB9F1A.F436CDC0]<https://twitter.com/connectctc>[cid:image014.gif@01DB9F1A.F436CDC0]<https://www.facebook.com/connectctc>goctc.com<http://www.goctc.com/> [cid:image015.gif@01DB9F1A.F436CDC0]<https://www.goctc.com/> ________________________________ This email has been scanned for spam and viruses by Proofpoint Essentials. Click here<https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_opti…> to report this email as spam.

March 27, 2025

Amazon bouncing

by Shawn Rasmussen

Has anyone else's Amazon peering been bouncing a lot lately? They are bouncing right now for us and have sporadic periods over the last week. Are any of you seeing the same? Anyone know anything about it? Thanks, SHAWN RASMUSSEN Network Manager D: (218) 454-1106 [cid:image001.gif@01DB9F21.0F267F80]<https://youtu.be/A_tgcHZD6oA>[cid:image002.gif@01DB9F21.0F267F80]<https://twitter.com/connectctc>[cid:image003.gif@01DB9F21.0F267F80]<https://www.facebook.com/connectctc>goctc.com<http://www.goctc.com/> [cid:image004.gif@01DB9F21.0F267F80]<https://www.goctc.com/>

March 27, 2025

RE: [EXTERNAL] RE: HCMC (AS 40413) Lost Peering on 03-19-2025

by Huwe, Daniel

OK, I see it now, and I concur, this is a me problem. I'll need to swing out to the data center and figure this one out. Thanks! * Dan H. From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Tuesday, March 25, 2025 8:56 AM To: Huwe, Daniel <Daniel.Huwe(a)hcmed.org>; mice-discuss(a)lists.micemn.net Subject: [EXTERNAL] RE: HCMC (AS 40413) Lost Peering on 03-19-2025 CAUTION: This email originated from outside of HCMC. DO NOT CLICK links or open attachments unless you recognize the sender and know the content is safe. Daniel, I see the port is up, however we are not learning a MAC address from you: core-sw0(s1)#sh int e 4/35 Ethernet4/35 is up, line protocol is up (connected) Hardware is Ethernet, address is 444c.a8e6.5326 (bia 444c.a8e6.5326) Description: HCMC 40413 Ethernet MTU 10178 bytes, Ethernet MRU 10200 bytes, BW 10000000 kbit Full-duplex, 10Gb/s, auto negotiation: off, uni-link: disabled Up 4 days, 1 hour, 31 minutes, 8 seconds Loopback Mode : None 5 link status changes since last clear Last clearing of "show interface" counters never 5 minutes input rate 0 bps (0.0% with framing overhead), 0 packets/sec 5 minutes output rate 61.0 kbps (0.0% with framing overhead), 94 packets/sec 0 packets input, 0 bytes Received 0 broadcasts, 0 multicast 0 runts, 0 giants 0 input errors, 0 CRC, 0 alignment, 0 symbol, 0 input discards 0 PAUSE input 181316240 packets output, 44157130837 bytes Sent 18266385 broadcasts, 28825106 multicast 0 output errors, 0 collisions 0 late collision, 0 deferred, 3213 output discards 0 PAUSE output core-sw0(s1)#sh mac address-t e 4/35 % Invalid input core-sw0(s1)#sh mac address-t int e 4/35 Mac Address Table ------------------------------------------------------------------ Vlan Mac Address Type Ports Moves Last Move ---- ----------- ---- ----- ----- --------- Total Mac Addresses for this criterion: 0 Jeremy From: Huwe, Daniel <Daniel.Huwe(a)hcmed.org<mailto:Daniel.Huwe@hcmed.org>> Sent: Tuesday, March 25, 2025 8:52 AM To: mice-discuss(a)lists.micemn.net<mailto:mice-discuss@lists.micemn.net> Subject: HCMC (AS 40413) Lost Peering on 03-19-2025 Looks like our peering dropped and did not re-establish about 1:30p on the 19th with all our MICE peers. Did I miss a critical configuration change that we needed to adopt in our config as a result of the switch-port migrations that have recently concluded? I am also noticing BPDUs showing up on our interface where before the migration, there were none. Thanks in advance for helping point me in the right direction here! * Dan H. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message.

March 25, 2025

RE: HCMC (AS 40413) Lost Peering on 03-19-2025

by Jeremy Lumby

Daniel, I see the port is up, however we are not learning a MAC address from you: core-sw0(s1)#sh int e 4/35 Ethernet4/35 is up, line protocol is up (connected) Hardware is Ethernet, address is 444c.a8e6.5326 (bia 444c.a8e6.5326) Description: HCMC 40413 Ethernet MTU 10178 bytes, Ethernet MRU 10200 bytes, BW 10000000 kbit Full-duplex, 10Gb/s, auto negotiation: off, uni-link: disabled Up 4 days, 1 hour, 31 minutes, 8 seconds Loopback Mode : None 5 link status changes since last clear Last clearing of "show interface" counters never 5 minutes input rate 0 bps (0.0% with framing overhead), 0 packets/sec 5 minutes output rate 61.0 kbps (0.0% with framing overhead), 94 packets/sec 0 packets input, 0 bytes Received 0 broadcasts, 0 multicast 0 runts, 0 giants 0 input errors, 0 CRC, 0 alignment, 0 symbol, 0 input discards 0 PAUSE input 181316240 packets output, 44157130837 bytes Sent 18266385 broadcasts, 28825106 multicast 0 output errors, 0 collisions 0 late collision, 0 deferred, 3213 output discards 0 PAUSE output core-sw0(s1)#sh mac address-t e 4/35 % Invalid input core-sw0(s1)#sh mac address-t int e 4/35 Mac Address Table ------------------------------------------------------------------ Vlan Mac Address Type Ports Moves Last Move ---- ----------- ---- ----- ----- --------- Total Mac Addresses for this criterion: 0 Jeremy From: Huwe, Daniel <Daniel.Huwe(a)hcmed.org> Sent: Tuesday, March 25, 2025 8:52 AM To: mice-discuss(a)lists.micemn.net Subject: HCMC (AS 40413) Lost Peering on 03-19-2025 Looks like our peering dropped and did not re-establish about 1:30p on the 19th with all our MICE peers. Did I miss a critical configuration change that we needed to adopt in our config as a result of the switch-port migrations that have recently concluded? I am also noticing BPDUs showing up on our interface where before the migration, there were none. Thanks in advance for helping point me in the right direction here! * Dan H. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message.

March 25, 2025

HCMC (AS 40413) Lost Peering on 03-19-2025

by Huwe, Daniel

Looks like our peering dropped and did not re-establish about 1:30p on the 19th with all our MICE peers. Did I miss a critical configuration change that we needed to adopt in our config as a result of the switch-port migrations that have recently concluded? I am also noticing BPDUs showing up on our interface where before the migration, there were none. Thanks in advance for helping point me in the right direction here! * Dan H. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message.

March 25, 2025

Re: MICE at 2T

by Anthony Anderberg

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> 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 To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net

March 24, 2025

MICE at 2T

by David Farmer

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 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 ===============================================

March 23, 2025

2T

by David Farmer

=============================================== 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 ===============================================

March 23, 2025

Re: MICE 400G Switch

by Mike Horwath

On Sat, Mar 22, 2025 at 06:10:23PM +0000, Michael Hemphill wrote: > It has been a true joy to watch the growth from the small switch > donated by US Internet to the monster that serves MICE participants > today. I concur. Now if only OG Grumpy's were still around for a little party.. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

March 22, 2025

Re: MICE 400G Switch

by Nevin Lyne

Thank you for the pictures! It is amazing what MICE has grown into from those early Grumpy's meetings :) -Nevin -- -- Nevin Lyne -- Founder and Director of Technology -- Arcustech, LLC - https://www.arcustech.com/ On Sat, Mar 22, 2025, at 2:10 PM, Michael Hemphill wrote: > Jeremy, > The pictures represent many hours of work and planning. Thanks for all > that you do to support MICE!! > MICE has become a true force in the peering community. It has been a > true joy to watch the growth from the small switch donated by US > Internet to the monster that serves MICE participants today. 🤓🤓 > > Get Outlook for iOS <https://aka.ms/o0ukef> > *From:* Mike Horwath <drechsau(a)geeks.org> > *Sent:* Saturday, March 22, 2025 12:57:17 PM > *To:* Jeremy Lumby <jlumby(a)mnvoip.com> > *Cc:* 'MICE Discuss' <mice-discuss(a)lists.micemn.net> > *Subject:* Re: MICE 400G Switch > > On Sat, Mar 22, 2025 at 12:39:09PM -0500, Jeremy Lumby wrote: >> Now that the cabinet and switch migration is complete, I wanted to share >> some more pictures of the progress of moving everything into the new >> cabinet. > > Thanks for sharing the pics! > > I might hate boxes and wires but I do like pics of them :) > > -- > Mike Horwath, reachable via drechsau(a)Geeks.ORG > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net

March 22, 2025

Re: MICE 400G Switch

by Michael Hemphill

Jeremy, The pictures represent many hours of work and planning. Thanks for all that you do to support MICE!! MICE has become a true force in the peering community. It has been a true joy to watch the growth from the small switch donated by US Internet to the monster that serves MICE participants today. 🤓🤓 Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Mike Horwath <drechsau(a)geeks.org> Sent: Saturday, March 22, 2025 12:57:17 PM To: Jeremy Lumby <jlumby(a)mnvoip.com> Cc: 'MICE Discuss' <mice-discuss(a)lists.micemn.net> Subject: Re: MICE 400G Switch On Sat, Mar 22, 2025 at 12:39:09PM -0500, Jeremy Lumby wrote: > Now that the cabinet and switch migration is complete, I wanted to share > some more pictures of the progress of moving everything into the new > cabinet. Thanks for sharing the pics! I might hate boxes and wires but I do like pics of them :) -- Mike Horwath, reachable via drechsau(a)Geeks.ORG _______________________________________________ mice-discuss mailing list -- mice-discuss(a)lists.micemn.net To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net

March 22, 2025

Re: MICE 400G Switch

by Mike Horwath

On Sat, Mar 22, 2025 at 12:39:09PM -0500, Jeremy Lumby wrote: > Now that the cabinet and switch migration is complete, I wanted to share > some more pictures of the progress of moving everything into the new > cabinet. Thanks for sharing the pics! I might hate boxes and wires but I do like pics of them :) -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

March 22, 2025

MICE 400G Switch

by Jeremy Lumby

Now that the cabinet and switch migration is complete, I wanted to share some more pictures of the progress of moving everything into the new cabinet. I am very happy with how everything turned out. With everything complete, the new cabinet is consuming just under 6KWh to run everything. https://www.mnvoip.com/MICE400G/10.jpg https://www.mnvoip.com/MICE400G/11.jpg https://www.mnvoip.com/MICE400G/12.jpg https://www.mnvoip.com/MICE400G/13.jpg https://www.mnvoip.com/MICE400G/14.jpg https://www.mnvoip.com/MICE400G/15.jpg Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Thursday, January 23, 2025 9:27 AM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net> Subject: RE: MICE 400G Switch Here are some pics: https://www.mnvoip.com/MICE400G/1.jpg https://www.mnvoip.com/MICE400G/2.jpg https://www.mnvoip.com/MICE400G/3.jpg https://www.mnvoip.com/MICE400G/4.jpg https://www.mnvoip.com/MICE400G/5.jpg https://www.mnvoip.com/MICE400G/6.jpg https://www.mnvoip.com/MICE400G/7.jpg https://www.mnvoip.com/MICE400G/8.jpg https://www.mnvoip.com/MICE400G/9.jpg -----Original Message----- From: Mike Horwath <drechsau(a)geeks.org> Sent: Thursday, January 23, 2025 7:37 AM To: MICE Discuss <mice-discuss(a)lists.micemn.net> Subject: Re: MICE 400G Switch On Thu, Jan 23, 2025 at 12:02:13AM -0600, Richard Laager wrote: > The 400G switch has arrived. whoop! > Jeremy racked the switch. It's a big one! Pics!? -- Mike Horwath, reachable via drechsau(a)Geeks.ORG _______________________________________________ mice-discuss mailing list -- mice-discuss(a)lists.micemn.net To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net

March 22, 2025

RE: Round 6 (Final) - MICE Switch-Cabinet Migration

by Jeremy Lumby

This final round of maintenance is now complete. Let me know if you are experiencing any issues. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, March 19, 2025 1:06 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: RE: Round 6 (Final) - MICE Switch-Cabinet Migration The maintenance described below is starting now. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Monday, March 10, 2025 8:40 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: Round 6 (Final) - MICE Switch-Cabinet Migration On Wednesday March 19 at approximately 1PM central time I will perform the final steps of the MICE switch and cabinet migration project. Members that were moved to temporary switches/ports in the new cabinet during previous maintenance rounds will get moved onto the newly relocated original core switch. The full list of these port moves is below. BGP will be blocked for these members prior to moving them. The temporary switches are located directly above and below the original core switch so the link down period should be a matter of seconds per port. Participants not listed below should expect to see lower traffic levels, fewer prefixes from the route servers, and bilateral BGP sessions down to any network listed below during the maintenance. Netflix - 2906: Temporary Ports: Po3 E1/1 E2/1 New Ports: Po3 E6/1/1 E6/2/1 Meta - 32934: Temporary Ports: Po27 E3/1 New Ports: Po27 E6/3/1 Amazon - 16509: Temporary Ports: Po24 E4/1 E5/1 E6/1 E7/1 New Ports: Po24 E6/4/1 E6/5/1 E6/6/1 E6/7/1 CloudFlare - 13335: Temporary Ports: Po13 Et8/1 New Ports: Po13 Et6/8/1 G-Core Labs - 199524: Temporary Port: E9/1 New Port: E6/9/1 Apple - 714: Temporary Port: E10/1 New Port: E6/10/1 Inteliquent - 40160: Temporary Port: E33 New Port: E4/1 Inteliquent - 5715: Temporary Port: E34 New Port: E4/2 Hurricane Electric - 6939: Temporary Ports: Po6 E11/1 E12/1 E13/1 New Ports: Po6 E6/11/1 E6/12/1 E6/13/1 Metronet - 30600: Temporary Ports: Po40 E14/1 New Ports: Po40 E6/14/1 Cedar Falls Utilities - 13855: Temporary Port: E15/1 New Port: E6/15/1 Savage Communications - 23260: Temporary Port: E16/1 New Port: E6/16/1 Nuvera - 23465: Temporary Ports: Po29 E17/1 New Ports: Po29 E6/17/1 Long Lines - 32867: Temporary Port: E18/1 New Port: E6/18/1 Nsight - 3663: Temporary Port: E19/1 New Port: E6/19/1 Bluepeak - 20412: Temporary Port: E20/1 New Port: E6/20/1 UnitedHealth Group - 10879: Temporary Port: E21/1 New Port: E6/21/1 Hennepin County - 40382: Temporary Port: E22/1 New Port: E6/22/1 TDS - 4181: Temporary Port: E23/1 New Port: E6/23/1 Truestream - 398143: Temporary Port: E24/1 New Port: E6/24/1 HBC - 14828: Temporary Port: E25/1 New Port: E6/25/1 SRT Communications - 14543: Temporary Port: E26/1 New Port: E6/26/1 Akamai 20940: Temporary Ports: Po 1 E26/1 E25/1 E24/1 E23/1 New Ports: Po 1 E3/26/1 E3/25/1 E3/24/1 E3/23/1 Saskatchewan Telecommunications 803: Temporary Ports: Po 8 E22/1 New Ports: Po 8 E3/22/1 Integris Remote Switch: Temporary Ports: Po 9 E 21/1 New Ports: Po 9 E 3/21/1 Fastly 54113: Temporary Ports: Po 14 E 20/1 New Ports: Po 14 E 3/20/1 SpaceX 14593: Temporary Ports: Po 20 E 19/1 E 18/1 New Ports: Po 20 E 3/19/1 E 3/18/1 MidCo 11232: Temporary Ports: Po 23 E 17/1 New Ports: Po 23 E 3/17/1 Microsoft 8075: Temporary Ports: Po 35 E 16/1 New Ports: Po 35 E 3/16/1 Wisc.Net Remote Switch: Temporary Ports: Po 37 E 15/1 New Ports: Po 37 E 3/15/1 Hennepin County 40382 Temporary Port: E14/1 New Port: E3/14/1 UnitedHealth Group 10879 Temporary Port: E 13/1 New Port: E 3/13/1 SDN 13576: Temporary Port: E 12/1 New Port: E 3/12/1 DCN 26794: Temporary Port: E 11/1 New Port: E 3/11/1 Aureon 5056: Temporary Port: E 10/1 New Port: E 3/10/1 UofM GiGaPoP 57: Temporary Port: E 9/1 New Port: E 3/9/1 US Internet 10242: Temporary Port: E 8/1 New Port: E 3/8/1 Mankato Networks Remote Switch: Temporary Ports: Po 32 E 33 E 34 New Ports: Po32 E4/3 E4/4 Po39 Mid-Rivers 11961 Temporary Ports: Po 39 E 1/1 E 1/2 E 1/3 E 1/4 New Ports: Po39 E4/5 E4/6 E4/7 E4/8 WHCC 11852: Temporary Port: E2/1 New Port: E4/9 LOGIS 398846: Temporary Port: E2/2 New Port: E4/10 MN Teen Challenge 400316: Temporary Port: E2/3 New Port: E4/11 Charter 20115 New Ports: Po4 E2/4 E3/1 New Ports: Po4 E4/12 E4/13 Chia 400790 Temporary Port: E3/2 New Port: E4/14 Country Wireless 16616 Temporary Port: E3/3 New Port: E4/15 Zayo 6461 New Ports: Po17 E3/4 New Ports: Po17 E4/16 Marco 55043 Temporary Port: E4/1 New Port: E4/17 OneNeck 8015 Temporary Port: E4/2 New Port: E4/18 Radio Link 53301 Temporary Port: E4/3 New Port: E4/19 Cisco Umbrella 36692 Temporary Ports: Po16 E4/4 E5/1 New Ports: Po16 E4/20 E4/25 Code42 62715 Temporary Port: E5/2 New Port: E4/26 Velocity Telephone 15250 Temporary Port: E5/3 New Port: E4/27 Flexnetworks 19523 Temporary Port: E5/4 New Port: E4/28 Pavlov Media 23473 Temporary Port: E6/1 New Port: E4/29 Xcel Energy 215 Temporary Port: E6/2 New Port: E4/30 OneNet Global 46131 Temporary Port: E6/3 New Port: E4/31 Implex 21709 Temporary Port: E6/4 New Port: E4/32 Atomic Data 25694 Temporary Port: E7/1 New Port: E4/33 FDL Communications 396939 Temporary Port: E7/2 New Port: E4/34 HCMC 40413 Temporary Port: E7/3 New Port: E4/35 Nextera 22402 Temporary Port: E7/4 New Port: E4/36 Let me know if you have any questions. Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com

March 19, 2025

RE: Round 6 (Final) - MICE Switch-Cabinet Migration

by Jeremy Lumby

The maintenance described below is starting now. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Monday, March 10, 2025 8:40 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: Round 6 (Final) - MICE Switch-Cabinet Migration On Wednesday March 19 at approximately 1PM central time I will perform the final steps of the MICE switch and cabinet migration project. Members that were moved to temporary switches/ports in the new cabinet during previous maintenance rounds will get moved onto the newly relocated original core switch. The full list of these port moves is below. BGP will be blocked for these members prior to moving them. The temporary switches are located directly above and below the original core switch so the link down period should be a matter of seconds per port. Participants not listed below should expect to see lower traffic levels, fewer prefixes from the route servers, and bilateral BGP sessions down to any network listed below during the maintenance. Netflix - 2906: Temporary Ports: Po3 E1/1 E2/1 New Ports: Po3 E6/1/1 E6/2/1 Meta - 32934: Temporary Ports: Po27 E3/1 New Ports: Po27 E6/3/1 Amazon - 16509: Temporary Ports: Po24 E4/1 E5/1 E6/1 E7/1 New Ports: Po24 E6/4/1 E6/5/1 E6/6/1 E6/7/1 CloudFlare - 13335: Temporary Ports: Po13 Et8/1 New Ports: Po13 Et6/8/1 G-Core Labs - 199524: Temporary Port: E9/1 New Port: E6/9/1 Apple - 714: Temporary Port: E10/1 New Port: E6/10/1 Inteliquent - 40160: Temporary Port: E33 New Port: E4/1 Inteliquent - 5715: Temporary Port: E34 New Port: E4/2 Hurricane Electric - 6939: Temporary Ports: Po6 E11/1 E12/1 E13/1 New Ports: Po6 E6/11/1 E6/12/1 E6/13/1 Metronet - 30600: Temporary Ports: Po40 E14/1 New Ports: Po40 E6/14/1 Cedar Falls Utilities - 13855: Temporary Port: E15/1 New Port: E6/15/1 Savage Communications - 23260: Temporary Port: E16/1 New Port: E6/16/1 Nuvera - 23465: Temporary Ports: Po29 E17/1 New Ports: Po29 E6/17/1 Long Lines - 32867: Temporary Port: E18/1 New Port: E6/18/1 Nsight - 3663: Temporary Port: E19/1 New Port: E6/19/1 Bluepeak - 20412: Temporary Port: E20/1 New Port: E6/20/1 UnitedHealth Group - 10879: Temporary Port: E21/1 New Port: E6/21/1 Hennepin County - 40382: Temporary Port: E22/1 New Port: E6/22/1 TDS - 4181: Temporary Port: E23/1 New Port: E6/23/1 Truestream - 398143: Temporary Port: E24/1 New Port: E6/24/1 HBC - 14828: Temporary Port: E25/1 New Port: E6/25/1 SRT Communications - 14543: Temporary Port: E26/1 New Port: E6/26/1 Akamai 20940: Temporary Ports: Po 1 E26/1 E25/1 E24/1 E23/1 New Ports: Po 1 E3/26/1 E3/25/1 E3/24/1 E3/23/1 Saskatchewan Telecommunications 803: Temporary Ports: Po 8 E22/1 New Ports: Po 8 E3/22/1 Integris Remote Switch: Temporary Ports: Po 9 E 21/1 New Ports: Po 9 E 3/21/1 Fastly 54113: Temporary Ports: Po 14 E 20/1 New Ports: Po 14 E 3/20/1 SpaceX 14593: Temporary Ports: Po 20 E 19/1 E 18/1 New Ports: Po 20 E 3/19/1 E 3/18/1 MidCo 11232: Temporary Ports: Po 23 E 17/1 New Ports: Po 23 E 3/17/1 Microsoft 8075: Temporary Ports: Po 35 E 16/1 New Ports: Po 35 E 3/16/1 Wisc.Net Remote Switch: Temporary Ports: Po 37 E 15/1 New Ports: Po 37 E 3/15/1 Hennepin County 40382 Temporary Port: E14/1 New Port: E3/14/1 UnitedHealth Group 10879 Temporary Port: E 13/1 New Port: E 3/13/1 SDN 13576: Temporary Port: E 12/1 New Port: E 3/12/1 DCN 26794: Temporary Port: E 11/1 New Port: E 3/11/1 Aureon 5056: Temporary Port: E 10/1 New Port: E 3/10/1 UofM GiGaPoP 57: Temporary Port: E 9/1 New Port: E 3/9/1 US Internet 10242: Temporary Port: E 8/1 New Port: E 3/8/1 Mankato Networks Remote Switch: Temporary Ports: Po 32 E 33 E 34 New Ports: Po32 E4/3 E4/4 Po39 Mid-Rivers 11961 Temporary Ports: Po 39 E 1/1 E 1/2 E 1/3 E 1/4 New Ports: Po39 E4/5 E4/6 E4/7 E4/8 WHCC 11852: Temporary Port: E2/1 New Port: E4/9 LOGIS 398846: Temporary Port: E2/2 New Port: E4/10 MN Teen Challenge 400316: Temporary Port: E2/3 New Port: E4/11 Charter 20115 New Ports: Po4 E2/4 E3/1 New Ports: Po4 E4/12 E4/13 Chia 400790 Temporary Port: E3/2 New Port: E4/14 Country Wireless 16616 Temporary Port: E3/3 New Port: E4/15 Zayo 6461 New Ports: Po17 E3/4 New Ports: Po17 E4/16 Marco 55043 Temporary Port: E4/1 New Port: E4/17 OneNeck 8015 Temporary Port: E4/2 New Port: E4/18 Radio Link 53301 Temporary Port: E4/3 New Port: E4/19 Cisco Umbrella 36692 Temporary Ports: Po16 E4/4 E5/1 New Ports: Po16 E4/20 E4/25 Code42 62715 Temporary Port: E5/2 New Port: E4/26 Velocity Telephone 15250 Temporary Port: E5/3 New Port: E4/27 Flexnetworks 19523 Temporary Port: E5/4 New Port: E4/28 Pavlov Media 23473 Temporary Port: E6/1 New Port: E4/29 Xcel Energy 215 Temporary Port: E6/2 New Port: E4/30 OneNet Global 46131 Temporary Port: E6/3 New Port: E4/31 Implex 21709 Temporary Port: E6/4 New Port: E4/32 Atomic Data 25694 Temporary Port: E7/1 New Port: E4/33 FDL Communications 396939 Temporary Port: E7/2 New Port: E4/34 HCMC 40413 Temporary Port: E7/3 New Port: E4/35 Nextera 22402 Temporary Port: E7/4 New Port: E4/36 Let me know if you have any questions. Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com

March 19, 2025

RE: Port down

by Jeremy Lumby

I just replied off list. -----Original Message----- From: todd(a)velocitytelephone.com <todd(a)velocitytelephone.com> Sent: Monday, March 17, 2025 4:48 PM To: mice-discuss(a)lists.micemn.net Subject: Port down Our (Velocity Telephone) MICE port physically went down around 4:25P CST today and is still down, anyone aware of any issues? Thanks, Todd _______________________________________________ mice-discuss mailing list -- mice-discuss(a)lists.micemn.net To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net

March 17, 2025

Port down

by todd＠velocitytelephone.com

Our (Velocity Telephone) MICE port physically went down around 4:25P CST today and is still down, anyone aware of any issues? Thanks, Todd

March 17, 2025

Re: RPKI deployment survey

by Richard Laager

On 2025-03-17 11:14, Ben Wiechman via mice-discuss wrote: > Did they indicate if or how they would present their findings? They did not and I didn't ask. > Are they aware of the MANRS project? > https://manrs.org/ Yes. -- Richard

March 17, 2025

Please welcome Stellar Association to MICE!

by Jeremy Lumby

Name: Stellar Association Switch: MN VoIP 100G Port: Ethernet 10/1 and 11/1 in po 6 (2x100G) ASN: 36374 IPv4: 206.108.255.3/24 IPv6: 2001:504:27:0:0:8E16::2/64 Peering Contact: peering(a)stellarllc.net Route Servers: YES Stellar is adding an additional redundant router/path to MICE 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

March 17, 2025

Re: RPKI deployment survey

by Ben Wiechman

Did they indicate if or how they would present their findings? Are they aware of the MANRS project? https://manrs.org/ 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 Sun, Mar 16, 2025 at 11:40 PM Richard Laager via mice-discuss < mice-discuss(a)lists.micemn.net> wrote: > Two professors, one from Tufts and one from Georgia Tech, are doing a > survey of RPKI deployments. They are "working on a research project looking > at barriers to RPKI adoption and the experience of different stakeholders > involved in RPKI to inform strategies to help promote further adoption." > > I spoke to them at length about my experience with MICE's IRR/RPKI > project, and some with my Wiktel hat too. > > If any of you are interested in speaking with them, please contact: > > Josephine Wolff <Josephine.Wolff(a)tufts.edu> <Josephine.Wolff(a)tufts.edu> > > Cecilia Testart <ctestart(a)gatech.edu> <ctestart(a)gatech.edu> > > -- > Richard > > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net >

March 17, 2025

RPKI deployment survey

by Richard Laager

Two professors, one from Tufts and one from Georgia Tech, are doing a survey of RPKI deployments. They are "working on a research project looking at barriers to RPKI adoption and the experience of different stakeholders involved in RPKI to inform strategies to help promote further adoption." I spoke to them at length about my experience with MICE's IRR/RPKI project, and some with my Wiktel hat too. If any of you are interested in speaking with them, please contact: Josephine Wolff <Josephine.Wolff(a)tufts.edu> Cecilia Testart <ctestart(a)gatech.edu> -- Richard

March 17, 2025

Round 6 (Final) - MICE Switch-Cabinet Migration

by Jeremy Lumby

On Wednesday March 19 at approximately 1PM central time I will perform the final steps of the MICE switch and cabinet migration project. Members that were moved to temporary switches/ports in the new cabinet during previous maintenance rounds will get moved onto the newly relocated original core switch. The full list of these port moves is below. BGP will be blocked for these members prior to moving them. The temporary switches are located directly above and below the original core switch so the link down period should be a matter of seconds per port. Participants not listed below should expect to see lower traffic levels, fewer prefixes from the route servers, and bilateral BGP sessions down to any network listed below during the maintenance. Netflix - 2906: Temporary Ports: Po3 E1/1 E2/1 New Ports: Po3 E6/1/1 E6/2/1 Meta - 32934: Temporary Ports: Po27 E3/1 New Ports: Po27 E6/3/1 Amazon - 16509: Temporary Ports: Po24 E4/1 E5/1 E6/1 E7/1 New Ports: Po24 E6/4/1 E6/5/1 E6/6/1 E6/7/1 CloudFlare - 13335: Temporary Ports: Po13 Et8/1 New Ports: Po13 Et6/8/1 G-Core Labs - 199524: Temporary Port: E9/1 New Port: E6/9/1 Apple - 714: Temporary Port: E10/1 New Port: E6/10/1 Inteliquent - 40160: Temporary Port: E33 New Port: E4/1 Inteliquent - 5715: Temporary Port: E34 New Port: E4/2 Hurricane Electric - 6939: Temporary Ports: Po6 E11/1 E12/1 E13/1 New Ports: Po6 E6/11/1 E6/12/1 E6/13/1 Metronet - 30600: Temporary Ports: Po40 E14/1 New Ports: Po40 E6/14/1 Cedar Falls Utilities - 13855: Temporary Port: E15/1 New Port: E6/15/1 Savage Communications - 23260: Temporary Port: E16/1 New Port: E6/16/1 Nuvera - 23465: Temporary Ports: Po29 E17/1 New Ports: Po29 E6/17/1 Long Lines - 32867: Temporary Port: E18/1 New Port: E6/18/1 Nsight - 3663: Temporary Port: E19/1 New Port: E6/19/1 Bluepeak - 20412: Temporary Port: E20/1 New Port: E6/20/1 UnitedHealth Group - 10879: Temporary Port: E21/1 New Port: E6/21/1 Hennepin County - 40382: Temporary Port: E22/1 New Port: E6/22/1 TDS - 4181: Temporary Port: E23/1 New Port: E6/23/1 Truestream - 398143: Temporary Port: E24/1 New Port: E6/24/1 HBC - 14828: Temporary Port: E25/1 New Port: E6/25/1 SRT Communications - 14543: Temporary Port: E26/1 New Port: E6/26/1 Akamai 20940: Temporary Ports: Po 1 E26/1 E25/1 E24/1 E23/1 New Ports: Po 1 E3/26/1 E3/25/1 E3/24/1 E3/23/1 Saskatchewan Telecommunications 803: Temporary Ports: Po 8 E22/1 New Ports: Po 8 E3/22/1 Integris Remote Switch: Temporary Ports: Po 9 E 21/1 New Ports: Po 9 E 3/21/1 Fastly 54113: Temporary Ports: Po 14 E 20/1 New Ports: Po 14 E 3/20/1 SpaceX 14593: Temporary Ports: Po 20 E 19/1 E 18/1 New Ports: Po 20 E 3/19/1 E 3/18/1 MidCo 11232: Temporary Ports: Po 23 E 17/1 New Ports: Po 23 E 3/17/1 Microsoft 8075: Temporary Ports: Po 35 E 16/1 New Ports: Po 35 E 3/16/1 Wisc.Net Remote Switch: Temporary Ports: Po 37 E 15/1 New Ports: Po 37 E 3/15/1 Hennepin County 40382 Temporary Port: E14/1 New Port: E3/14/1 UnitedHealth Group 10879 Temporary Port: E 13/1 New Port: E 3/13/1 SDN 13576: Temporary Port: E 12/1 New Port: E 3/12/1 DCN 26794: Temporary Port: E 11/1 New Port: E 3/11/1 Aureon 5056: Temporary Port: E 10/1 New Port: E 3/10/1 UofM GiGaPoP 57: Temporary Port: E 9/1 New Port: E 3/9/1 US Internet 10242: Temporary Port: E 8/1 New Port: E 3/8/1 Mankato Networks Remote Switch: Temporary Ports: Po 32 E 33 E 34 New Ports: Po32 E4/3 E4/4 Po39 Mid-Rivers 11961 Temporary Ports: Po 39 E 1/1 E 1/2 E 1/3 E 1/4 New Ports: Po39 E4/5 E4/6 E4/7 E4/8 WHCC 11852: Temporary Port: E2/1 New Port: E4/9 LOGIS 398846: Temporary Port: E2/2 New Port: E4/10 MN Teen Challenge 400316: Temporary Port: E2/3 New Port: E4/11 Charter 20115 New Ports: Po4 E2/4 E3/1 New Ports: Po4 E4/12 E4/13 Chia 400790 Temporary Port: E3/2 New Port: E4/14 Country Wireless 16616 Temporary Port: E3/3 New Port: E4/15 Zayo 6461 New Ports: Po17 E3/4 New Ports: Po17 E4/16 Marco 55043 Temporary Port: E4/1 New Port: E4/17 OneNeck 8015 Temporary Port: E4/2 New Port: E4/18 Radio Link 53301 Temporary Port: E4/3 New Port: E4/19 Cisco Umbrella 36692 Temporary Ports: Po16 E4/4 E5/1 New Ports: Po16 E4/20 E4/25 Code42 62715 Temporary Port: E5/2 New Port: E4/26 Velocity Telephone 15250 Temporary Port: E5/3 New Port: E4/27 Flexnetworks 19523 Temporary Port: E5/4 New Port: E4/28 Pavlov Media 23473 Temporary Port: E6/1 New Port: E4/29 Xcel Energy 215 Temporary Port: E6/2 New Port: E4/30 OneNet Global 46131 Temporary Port: E6/3 New Port: E4/31 Implex 21709 Temporary Port: E6/4 New Port: E4/32 Atomic Data 25694 Temporary Port: E7/1 New Port: E4/33 FDL Communications 396939 Temporary Port: E7/2 New Port: E4/34 HCMC 40413 Temporary Port: E7/3 New Port: E4/35 Nextera 22402 Temporary Port: E7/4 New Port: E4/36 Let me know if you have any questions. Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com

March 11, 2025

RE: Round 5 - MICE Switch-Cabinet Migration

by Jeremy Lumby

We are now hands off, let me know if you are still seeing any issues. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Thursday, March 6, 2025 1:04 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: RE: Round 5 - MICE Switch-Cabinet Migration This maintenance is now starting... -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, March 5, 2025 9:13 AM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: RE: Round 5 - MICE Switch-Cabinet Migration With the snowstorm that just came through, I have coordinated with Cologix to delay this maintenance listed below until tomorrow March 6th at 1 PM -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 26, 2025 3:33 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: Round 5 - MICE Switch-Cabinet Migration On Wednesday March 5th at approximately 1PM CST I will be moving the Arista 7504R (100Gig core switch) into the new cabinet, along with some remaining 10G connections on the switch, and all other equipment in cabinet 937. Prior to the migration BGP will be blocked on the specific participant's port to allow traffic to gracefully reroute. This is the fifth round of weekly moves and should complete migrating everything out of the existing cabinet. During this maintenance software on the 7504R switch, as well as route server 1 will be updated. There will be one final maintenance on the afternoon of Wednesday March 19 to move connections off of temp switches in the new cabinet. If you are interested in upgrading to 400Gig let us know ASAP so we can avoid double moves, and facilitate an easier transition for everyone. The full details of the move are: Virtual Host 1 (includes MICE Webserver, DNS server, IXP Manager, Route Server 1) Management Firewall Arista 7504R: Essentia - 3789 Old Ports: Et4/34 Et4/40 New Ports: E 4/42 E 4/41 30110 - Range Old Port: Et4/42 New Port: E 4/45 Management to Remote Switches Old Port: Et4/43 New Port: E 4/48 Yahoo 10310 Old Ports: Et4/44 Et4/48 New Ports: E 4/43 E 4/44 Virtual Host 1 Old Port: Et4/45 New Port: E 4/47 Xiber LLC 393950 Old Port: Et4/46 New Port: E 4/46 Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com

March 6, 2025

RE: Round 5 - MICE Switch-Cabinet Migration

by Jeremy Lumby

This maintenance is now starting... -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, March 5, 2025 9:13 AM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: RE: Round 5 - MICE Switch-Cabinet Migration With the snowstorm that just came through, I have coordinated with Cologix to delay this maintenance listed below until tomorrow March 6th at 1 PM -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 26, 2025 3:33 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: Round 5 - MICE Switch-Cabinet Migration On Wednesday March 5th at approximately 1PM CST I will be moving the Arista 7504R (100Gig core switch) into the new cabinet, along with some remaining 10G connections on the switch, and all other equipment in cabinet 937. Prior to the migration BGP will be blocked on the specific participant's port to allow traffic to gracefully reroute. This is the fifth round of weekly moves and should complete migrating everything out of the existing cabinet. During this maintenance software on the 7504R switch, as well as route server 1 will be updated. There will be one final maintenance on the afternoon of Wednesday March 19 to move connections off of temp switches in the new cabinet. If you are interested in upgrading to 400Gig let us know ASAP so we can avoid double moves, and facilitate an easier transition for everyone. The full details of the move are: Virtual Host 1 (includes MICE Webserver, DNS server, IXP Manager, Route Server 1) Management Firewall Arista 7504R: Essentia - 3789 Old Ports: Et4/34 Et4/40 New Ports: E 4/42 E 4/41 30110 - Range Old Port: Et4/42 New Port: E 4/45 Management to Remote Switches Old Port: Et4/43 New Port: E 4/48 Yahoo 10310 Old Ports: Et4/44 Et4/48 New Ports: E 4/43 E 4/44 Virtual Host 1 Old Port: Et4/45 New Port: E 4/47 Xiber LLC 393950 Old Port: Et4/46 New Port: E 4/46 Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com

March 6, 2025

RE: Round 5 - MICE Switch-Cabinet Migration

by Jeremy Lumby

With the snowstorm that just came through, I have coordinated with Cologix to delay this maintenance listed below until tomorrow March 6th at 1 PM -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 26, 2025 3:33 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: Round 5 - MICE Switch-Cabinet Migration On Wednesday March 5th at approximately 1PM CST I will be moving the Arista 7504R (100Gig core switch) into the new cabinet, along with some remaining 10G connections on the switch, and all other equipment in cabinet 937. Prior to the migration BGP will be blocked on the specific participant's port to allow traffic to gracefully reroute. This is the fifth round of weekly moves and should complete migrating everything out of the existing cabinet. During this maintenance software on the 7504R switch, as well as route server 1 will be updated. There will be one final maintenance on the afternoon of Wednesday March 19 to move connections off of temp switches in the new cabinet. If you are interested in upgrading to 400Gig let us know ASAP so we can avoid double moves, and facilitate an easier transition for everyone. The full details of the move are: Virtual Host 1 (includes MICE Webserver, DNS server, IXP Manager, Route Server 1) Management Firewall Arista 7504R: Essentia - 3789 Old Ports: Et4/34 Et4/40 New Ports: E 4/42 E 4/41 30110 - Range Old Port: Et4/42 New Port: E 4/45 Management to Remote Switches Old Port: Et4/43 New Port: E 4/48 Yahoo 10310 Old Ports: Et4/44 Et4/48 New Ports: E 4/43 E 4/44 Virtual Host 1 Old Port: Et4/45 New Port: E 4/47 Xiber LLC 393950 Old Port: Et4/46 New Port: E 4/46 Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com

March 5, 2025

Re: MICE Server Updates

by Cameron Skappel

The first round of updates has been completed. On 2/20/25 14:13, Cameron Skappel wrote: > I forgot Jeremy is doing some maintenance on Wednesday, I will do the > first set of updates Wednesday February 26th at 18:00 to avoid > conflicting with him. > > On 2/20/25 12:11, Cameron Skappel wrote: >> I plan to update the MICE servers and firewalls Wednesday February >> 26th at 13:00 Central and Thursday February 27th at 13:00 Central. I >> will do one route server per day. >> -- Cameron Skappel 218-436-5226 Wikstrom Telephone Company

Feb. 27, 2025

UG 47 Meeting

by Richard Laager

The MICE UG 47 meeting will be held Wednesday, March 12, 3:00 pm at UMN and via Zoom. *UMN Details* (from David Farmer) [The meeting] will be held at the University’s Information Technology Building, 2218 University Ave SE, Minneapolis, MN 55414, Room 185. It is across University Ave SE from Huntington Bank Stadium (Formerly TCF Bank Stadium). See the link to the Campus Map below. This room has a video room system, and remote access will be made available via Zoom video or phone audio, see Zoom details below. Please enter the building through the middle of three doors on the Ontario St SE side of the building. It will be open after 2:30 and will have a sign on it. If not, please knock hard, or call my cell phone (612-812-9952). This door is right outside the meeting room, this avoids everyone traipsing through the building. The Stadium Village Green Line Light Rail Station is less than a block east of the building, kitty-corner at the intersection of University Ave SE and Huron Blvd SE. See the link below for the station's info page. Limited Street Parking is available on Ontario St SE and Beacon St SE. Otherwise, public parking is available in the Oak St and University Ave Ramps, each a little over two blocks away. Also, the Maroon lot is a little further on the north side of the Stadium. See the link below for more parking details. DO NOT park in University Parking Lot 70 on the north of the building, by the front door, between University Ave SE and the building, or Parking Lot 71 near the loading dock to the east of the building, they are contract parking only, and you be ticketed. Also, DO NOT park in the private parking lot to the south of the building; you will likely be tagged, booted, and towed from that parking lot. https://campusmaps.umn.edu/information-technology https://www.metrotransit.org/stadium-village-station https://pts.umn.edu/Park/Basic-Parking-Information/Parking-Facilities * * *Zoom Details* https://umn.zoom.us/j/94150849014?pwd=KLBvs9gAlRyobV2T5oTKyHcWpnUpKq.1 ID: 94150849014, passcode: 39WgFG 312-626-6799, meeting ID 94150849014, passcode 332770 -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

Feb. 26, 2025

Round 5 - MICE Switch-Cabinet Migration

by Jeremy Lumby

On Wednesday March 5th at approximately 1PM CST I will be moving the Arista 7504R (100Gig core switch) into the new cabinet, along with some remaining 10G connections on the switch, and all other equipment in cabinet 937. Prior to the migration BGP will be blocked on the specific participant's port to allow traffic to gracefully reroute. This is the fifth round of weekly moves and should complete migrating everything out of the existing cabinet. During this maintenance software on the 7504R switch, as well as route server 1 will be updated. There will be one final maintenance on the afternoon of Wednesday March 19 to move connections off of temp switches in the new cabinet. If you are interested in upgrading to 400Gig let us know ASAP so we can avoid double moves, and facilitate an easier transition for everyone. The full details of the move are: Virtual Host 1 (includes MICE Webserver, DNS server, IXP Manager, Route Server 1) Management Firewall Arista 7504R: Essentia - 3789 Old Ports: Et4/34 Et4/40 New Ports: E 4/42 E 4/41 30110 - Range Old Port: Et4/42 New Port: E 4/45 Management to Remote Switches Old Port: Et4/43 New Port: E 4/48 Yahoo 10310 Old Ports: Et4/44 Et4/48 New Ports: E 4/43 E 4/44 Virtual Host 1 Old Port: Et4/45 New Port: E 4/47 Xiber LLC 393950 Old Port: Et4/46 New Port: E 4/46 Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 Fax 952-873-7425 jlumby(a)mnvoip.com

Feb. 26, 2025

RE: Round 4 - MICE Switch-Cabinet Migration

by Jeremy Lumby

The maintenance is complete. Let me know if you are seeing any issues. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 19, 2025 4:16 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: Round 4 - MICE Switch-Cabinet Migration On Wednesday February 26th at approximately 1PM CST I will be migrating the following networks off of the Arista 7504R (100Gig core switch) to a temporary switch in the new cabinet/space that the 100G chassis will eventually be moved to at 511. Prior to the migration BGP will be blocked on the specific participant's port to allow traffic to gracefully reroute. This is the fourth round of weekly moves as everything is migrated out of the existing cabinet. If you are interested in upgrading to 400Gig let us know ASAP so we can avoid double moves, and facilitate an easier transition for everyone. WHCC 11852: Old Port: Et4/1 New Temporary Port: E2/1 LOGIS 398846: Old Port: Et4/2 New Temporary Port: E2/2 MN Teen Challenge 400316: Old Port: Et4/4 New Temporary Port: E2/3 Charter 20115 Old Ports: Po4 Et4/3 Et4/3 New Ports: Po4 E2/4 E3/1 Chia 400790 Old Port: Et4/6 New Temporary Port: E3/2 Country Wireless 16616 Old Port: Et4/7 New Temporary Port: E3/3 Zayo 6461 Old Ports: Po17 Et4/9 New Ports: Po17 E3/4 Marco 55043 Old Port: Et4/11 New Temporary Port: E4/1 OneNeck 8015 Old Port: Et4/15 New Temporary Port: E4/2 Radio Link 53301 Old Port: Et4/17 New Temporary Port: E4/3 Cisco Umbrella 36692 Old Ports: Po16 Et4/10 Et4/30 New Ports: Po16 E4/4 E5/1 Code42 62715 Old Port: Et4/19 New Temporary Port: E5/2 Velocity Telephone 15250 Old Port: Et4/21 New Temporary Port: E5/3 Flexnetworks 19523 Old Port: Et4/23 New Temporary Port: E5/4 Pavlov Media 23473 Old Port: Et4/24 New Temporary Port: E6/1 Xcel Energy 215 Old Port: Et4/25 New Temporary Port: E6/2 OneNet Global 46131 Old Port: Et4/27 New Temporary Port: E6/3 Implex 21709 Old Port: Et4/29 New Temporary Port: E6/4 Atomic Data 25694 Old Port: Et4/31 New Temporary Port: E7/1 FDL Communications 396939 Old Port: Et4/33 New Temporary Port: E7/2 HCMC 40413 Old Port: Et4/36 New Temporary Port: E7/3 Nextera 22402 Old Port: Et4/39 New Temporary Port: E7/4 Let me know if you have any questions Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 eFax 952-873-7425 jlumby(a)mnvoip.com

Feb. 26, 2025

RE: Round 4 - MICE Switch-Cabinet Migration

by Jeremy Lumby

Just a reminder the maintenance below is starting now. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 19, 2025 4:16 PM To: 'MICE Discuss' <mice-discuss(a)lists.micemn.net>; mice-announce(a)lists.micemn.net Subject: Round 4 - MICE Switch-Cabinet Migration On Wednesday February 26th at approximately 1PM CST I will be migrating the following networks off of the Arista 7504R (100Gig core switch) to a temporary switch in the new cabinet/space that the 100G chassis will eventually be moved to at 511. Prior to the migration BGP will be blocked on the specific participant's port to allow traffic to gracefully reroute. This is the fourth round of weekly moves as everything is migrated out of the existing cabinet. If you are interested in upgrading to 400Gig let us know ASAP so we can avoid double moves, and facilitate an easier transition for everyone. WHCC 11852: Old Port: Et4/1 New Temporary Port: E2/1 LOGIS 398846: Old Port: Et4/2 New Temporary Port: E2/2 MN Teen Challenge 400316: Old Port: Et4/4 New Temporary Port: E2/3 Charter 20115 Old Ports: Po4 Et4/3 Et4/3 New Ports: Po4 E2/4 E3/1 Chia 400790 Old Port: Et4/6 New Temporary Port: E3/2 Country Wireless 16616 Old Port: Et4/7 New Temporary Port: E3/3 Zayo 6461 Old Ports: Po17 Et4/9 New Ports: Po17 E3/4 Marco 55043 Old Port: Et4/11 New Temporary Port: E4/1 OneNeck 8015 Old Port: Et4/15 New Temporary Port: E4/2 Radio Link 53301 Old Port: Et4/17 New Temporary Port: E4/3 Cisco Umbrella 36692 Old Ports: Po16 Et4/10 Et4/30 New Ports: Po16 E4/4 E5/1 Code42 62715 Old Port: Et4/19 New Temporary Port: E5/2 Velocity Telephone 15250 Old Port: Et4/21 New Temporary Port: E5/3 Flexnetworks 19523 Old Port: Et4/23 New Temporary Port: E5/4 Pavlov Media 23473 Old Port: Et4/24 New Temporary Port: E6/1 Xcel Energy 215 Old Port: Et4/25 New Temporary Port: E6/2 OneNet Global 46131 Old Port: Et4/27 New Temporary Port: E6/3 Implex 21709 Old Port: Et4/29 New Temporary Port: E6/4 Atomic Data 25694 Old Port: Et4/31 New Temporary Port: E7/1 FDL Communications 396939 Old Port: Et4/33 New Temporary Port: E7/2 HCMC 40413 Old Port: Et4/36 New Temporary Port: E7/3 Nextera 22402 Old Port: Et4/39 New Temporary Port: E7/4 Let me know if you have any questions Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington MN 55425 Main 612-355-7740 x211 Direct 612-392-6814 eFax 952-873-7425 jlumby(a)mnvoip.com

Feb. 26, 2025

Please welcome Gateway Infrastructure to MICE!

by Jeremy Lumby

Name: Gateway Infrastructure Switch: MICE Core 511-400G 7804 Port: Ethernet 3/24/1 in po 18 (1x100G) ASN: 398113 IPv4: 206.108.255.244/24 IPv6: 2001:504:27:0:6:1321::1/64 Peering Contact: netops(a)gatewayfiber.com Route Servers: Partial 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

Feb. 24, 2025

Please welcome T-Mobile USA, Inc to MICE!

by Jeremy Lumby

Name: T-Mobile USA, Inc Switch: MICE Core 511-400G 7804 Port: Ethernet 3/22/1 (1x400G) ASN: 21928 IPv4: 206.108.255.243/24 IPv6: 2001:504:27:0:0:55a8::2/64 Peering Contact: peering(a)t-mobile.com Route Servers: Partial This second connection will gradually be migrated over to, and the original 3x100G disconnected 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

Feb. 24, 2025

Please welcome Amazon to MICE!

by Jeremy Lumby

Name: Amazon Switch: MICE Core 511-400G 7804 Ports: 3/14/1 & 3/26/1 in portchannel 16 and 4/14/1 & 4/26/1 to portchannel 17 for a total of 2x2x400G ASN: IPv4: All IP info remains the same, this is an upgrade to 4x400G IPv6: Peering Contact: peering-amer(a)amazon.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

Feb. 24, 2025

Please welcome Amazon to MICE!

by Jeremy Lumby

Name: Amazon Switch: MICE Core 511-400G 7804 Ports: 3/14/1 & 3/26/1 in portchannel 16 and 4/14/1 & 4/26/1 to portchannel 17 for a total of 2x2x400G ASN: IPv4: All IP info remains the same, this is an upgrade to 4x400G IPv6: Peering Contact: peering-amer(a)amazon.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

Feb. 24, 2025

Re: MICE Server Updates

by Cameron Skappel

I forgot Jeremy is doing some maintenance on Wednesday, I will do the first set of updates Wednesday February 26th at 18:00 to avoid conflicting with him. On 2/20/25 12:11, Cameron Skappel wrote: > I plan to update the MICE servers and firewalls Wednesday February > 26th at 13:00 Central and Thursday February 27th at 13:00 Central. I > will do one route server per day. > -- Cameron Skappel 218-436-5226 Wikstrom Telephone Company

Feb. 20, 2025

MICE Server Updates

by Cameron Skappel

I plan to update the MICE servers and firewalls Wednesday February 26th at 13:00 Central and Thursday February 27th at 13:00 Central. I will do one route server per day. -- Cameron Skappel 218-436-5226 Wikstrom Telephone Company

Feb. 20, 2025