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

Please welcome T-Mobile USA, Inc to MICE!
by Jeremy Lumby Aug. 8, 2025

Aug. 8, 2025

Name: T-Mobile USA, Inc Switch: MICE Main Port: Ethernet 6/15/1 ASN: 21928 IPv4: This is a port addition to an existing LAG, all IP info remains the same. The new connection will be 3x100G IPv6: Peering Contact: peering(a)t-mobile.com Route Servers: Yes BFD: 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

2 7

Please welcome Qwilt Inc. to MICE!
by Jeremy Lumby May 15, 2025

May 15, 2025

Name: Qwilt Inc. Switch: MICE Main Ports: 6/29/1 ASN: 20253 IPv4: 206.108.255.202/24 IPv6: 2001:504:27:0:0:4F1D::1/64 Peering Contact: peering(a)qwilt.com Route Servers: YES BFD: NO 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

4 50

Please welcome Hiawatha Broadband Communications to MICE!
by Jeremy Lumby May 9, 2025

May 9, 2025

Name: Hiawatha Broadband Communications Switch: MICE Core Port: E5/41 ASN: 14828 IPv4: IPs remain the same. This is a port addition bringing capacity to 40G on portchannel 32 IPv6: Peering Contact: noc(a)hbci.com Route Servers: YES BFD: YES 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

3 21

MICE 400G Switch
by Richard Laager March 22, 2025

March 22, 2025

The 400G switch has arrived. Jeremy racked the switch. It's a big one! We don't have a firm go-live date at this point, but it will be soon. If you are interested in 400G ports, the Order Form has been updated: https://micemn.net/files/MICE%20Order%20Form.docx (I've just sent this to mice-discuss so far. I'm thinking we'll send something to mice-announce once the switch is live. But if people think I should be sending it there now, I'm open to the suggestion.) -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

5 8

UG 46 Meeting & Election
by Richard Laager Feb. 26, 2025

Feb. 26, 2025

The MICE UG 46 meeting will be held Wednesday, October 9, 3:00 pm at UMN and via Zoom. Parking, etc. details same as before: https://lists.iphouse.net/cgi-bin/wa?A2=MICE-DISCUSS;2c503e19.2209 * * *Zoom Details* https://umn.zoom.us/j/97601658469?pwd=C6JWkmoYfB9WjZsnRPr9S5u1l4Zkuz.1 ID: 94910223662, passcode: Jp74Et 651-372-8299, meeting ID 97601658469, passcode 864193 * * *Nominations* We will be holding an election for a board seat. The board consists of three seats with staggered terms, such that one seat comes up for re-election each year (at the fall meeting). This year, Reid's seat is up for election. As in the past, we will close nominations in advance of the meeting so people have a chance to instruct a proxy appropriately. *Nominations will be open for two weeks, September 23 - October 6. *I plan to send reminder emails approximately at the start of and just after the nomination period. In the event that the election is uncontested, our practice is to elect by acclimation at the meeting. Proxies are unnecessary in that situation, assuming that the meeting makes quorum. *Proxies * The bylaws state that you send proxies to the Chief Manager (me, Richard Laager), and electronic means are acceptable. So a simple email is sufficient: rlaager(a)wiktel.com or chiefmanager(a)micemn.net. If you send me a /vote/ by email (e.g. "We vote for <X>."), I will treat it as an a proxy appointment, appointing me to vote on your behalf, but restricted to /only/ the election item and to /only/ vote for the candidate you expressed. If you send me a proxy with different instructions (e.g. "We appoint <Y> to vote for us."), obviously that will be honored as written. -- Richard

4 7

MICE Switch-Cabinet Migration Round 1
by Jeremy Lumby Feb. 5, 2025

Feb. 5, 2025

On Wednesday February 5th at approximately 1PM CST I will be migrating the following networks off of the Arista 7504R (100Gig core switch) to the new 7804R3 (400Gig core switch) at 511. Prior to the migration BGP will be blocked on the specific participant's port to allow traffic to gracefully reroute. This will be the first 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. Ridgeview core switch uplink Old Ports: Port-channel10 Ethernet3/35/1 Ethernet3/36/1 Ethernet5/14/1 Ethernet5/15/1 Ethernet6/35/1 Ethernet6/36/1 New Ports: Port-channel3 Ethernet3/33/1 Ethernet3/34/1 Ethernet4/32/1 Ethernet4/33/1 Ethernet4/34/1 Ethernet4/36/1 MN VoIP extension switch uplink Old Ports: Port-channel15 Ethernet3/6/1 Ethernet6/6/1 Ethernet6/13/1 New Ports: Port-channel1 Ethernet3/1/1 (Native 400G port) Fiber Minnesota extension switch uplink Old Ports: Port-channel22 Ethernet3/7/1 Ethernet5/13/1 Ethernet5/16/1 Ethernet6/3/1 New Ports: Port-channel4 Ethernet3/2/1 (Native 400G port) Ethernet4/2/1 (Native 400G port) Akamai Old Ports: Port-channel19 Ethernet6/8/1 Ethernet6/10/1 Ethernet6/12/1 Ethernet6/31/1 Ethernet5/7/1 New Ports: Port-channel5 Ethernet3/3/1 Ethernet3/4/1 Ethernet3/5/1 Ethernet3/6/1 Ethernet3/7/1 Amazon Old Ports: Port-channel5 Ethernet3/12/1 Ethernet6/4/1 Ethernet5/3/1 Ethernet5/4/1 New Ports: Port-channel6 Ethernet3/8/1 Ethernet3/9/1 Ethernet3/10/1 Ethernet3/11/1 Apple Old Ports: Port-channel30 Ethernet 3/14/1 New Ports: Port-channel7 Ethernet 3/12/1 Arvig Old Ports: Port-channel42 Ethernet3/8/1 Ethernet6/11/1 Ethernet5/1/1 New Ports: Port-channel8 Ethernet3/13/1 Ethernet4/13/1 Ethernet4/14/1 Fastly Old Ports: Port-channel18 Ethernet4/50/1 New Ports: Port-channel9 Ethernet3/14/1 Meta Old Ports: Port-channel26 Ethernet3/10/1 New Ports: Port-channel10 Ethernet3/15/1 Microsoft Old Ports: Port-channel34 Ethernet3/18/1 New Ports: Port-channel11 Ethernet3/16/1 Netflix Old Ports: Port-channel2 Ethernet3/11/1 Ethernet3/27/1 New Ports: Port-channel12 Ethernet3/17/1 Ethernet3/18/1 Northern Lights GigaPOP Old Ports: Ethernet6/14/1 New Ports: Ethernet3/19/1 Qwilt Old Ports: Port-channel12 Ethernet6/29/1 Ethernet5/2/1 New Ports: Port-channel13 Ethernet3/20/1 Ethernet4/20/1 T-Mobile Old Ports: Port-channel41 Ethernet3/2/1 Ethernet6/9/1 Ethernet6/15/1 New Ports: Port-channel14 Ethernet3/21/1 Ethernet4/21/1 Ethernet4/22/1 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

1 2

1G Disconnections
by Richard Laager Jan. 23, 2025

Jan. 23, 2025

The following participants were disconnected yesterday, as they were still on 1G and the 1G switch is going away as part of the cabinet move and 400G switch upgrade. Coloplast [AS25111] Evolve IP (fka Advanced Integrated Tech / AI Tech) [AS13746] ipHouse [AS7753] ipHouse was going away in any event, due to acquisition activity as previously discussed. The other two did confirm they were aware of the disconnect. They elected not to connect at 10G or move to a remote. -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

1 0

2025-01-20 MICE Maintenance - Route Server 2
by Richard Laager Jan. 23, 2025

Jan. 23, 2025

MICE physical server 2 (and thus by extension route server 2) is again having errors on its peering interface. We will be performing maintenance tomorrow to address this. Since this only affects one of the two route servers, participants should not be impacted. Details: Sometime tomorrow (exact time depending on day job schedules), Jeremy and I will: 1. Apply the usual security updates to VMs and the host, since the host is going to be rebooted anyway. 2. Convert server 2's port to a LAG. This will make future changes easier, especially if this error problem continues. This will involve a reboot of the server. The reboot is "necessary" because Linux's netplan does not remove VLAN configuration when changes are made (only adds it). Without removing the old direct-on-the-physical-interface VLAN config, we could (would?) create a loop. You may recall that I created a loop that blew up the exchange in more-or-less that exact way when setting up the servers originally. While I could remove the VLAN configuration manually, in this case, it's easier and safer to simply reboot. That also ensures our running configuration is fully consistent with the configuration files. 3. Replace the optic, also moving to the other port on the NIC. The underlying failure manifests as a decrease in optical transmit power (i.e. power received at the switch) over time. We have replaced the optic previously, which fixes it, but then it fails again after a while. We are open to suggestions about why this might be occurring. One theory is that this is due to heat. We are going to try the second port in case that makes a difference. We are also considering switching to a direct attach cable, as perhaps that would produce less heat. -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

3 2