- mice-discuss - lists.micemn.net

Re: 2025-01-20 MICE Maintenance - Route Server 2

by Brady Kittel

As a server guy I'll mention two things. 1) If we're using SM fiber with LR optics I've seen issues with LR optics burning out on the receive side when used with short distances to servers. Depends on the optic it seems but it definitely happens. Fix for us was just to either use SR optics with mm fiber or use a DAC. Definitely avoid the use of active mode DACs too. I've seen all sorts of problems with compatibility and even causing OS crashes. Never had problems with hardware compatible passive mode DACs in my experience across our fleet of 350 servers. On Sun, Jan 19, 2025, 7:50 PM Richard Laager <rlaager(a)micemn.net> wrote: > 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 > > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net >

Jan. 23, 2025

Re: MICE 400G Switch

by Mike Horwath

On Thu, Jan 23, 2025 at 09:26:48AM -0600, Jeremy Lumby wrote: > Here are some pics: Thanks! That's some chonk! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Jan. 23, 2025

RE: MICE 400G Switch

by Jeremy Lumby

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

Jan. 23, 2025

Re: MICE 400G Switch

by Mike Horwath

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

Jan. 23, 2025

MICE 400G Switch

by Richard Laager

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

Jan. 23, 2025

2025-01-20 MICE Maintenance - Route Server 2

by Richard Laager

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

Jan. 20, 2025

RE: [MICE-DISCUSS] MICE Server Updates

by nanog＠jima.us

Cameron (or others), A cohort reached out to ask me... Does anyone know when the IPv6 address for micemn.net stopped responding? I foolishly didn't check after the migration; I see the v6 address is announced by the same ASN as the (working) v4 address, but attempts to trace die off after the penultimate hop (versus the v4 path). Happy Eyeballs would generally keep the site loading in browsers, assuming one has native IPv4/464XLAT, but it seems like a non-ideal state of affairs. Thank you! - Jima > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Cameron > Skappel > Sent: Monday, November 25, 2024 13:19 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] MICE Server Updates > > The first round of updates, which included Route Server 1, has been > completed. > > On 11/22/24 11:45, Cameron Skappel wrote: > > I plan to update the MICE servers and firewalls Monday November 25th > > at 13:00 Central and Tuesday November 26th at 14:30 Central. I will do > > one route server per day. > > > -- > Cameron Skappel > 218-436-5226 > Wikstrom Telephone Company

Dec. 18, 2024

Re: [MICE-DISCUSS] ipHouse MICE Disconnect

by John Unger

Thank you Doug and the IPhouse folks that helped, you will be missed!! Regards, John Unger Vaultas On Mon, Dec 2, 2024 at 2:41 PM Jay Hanke via mice-discuss < mice-discuss(a)lists.micemn.net> wrote: > ipHouse is disconnecting from MICE. > > ipHouse is an OG member of MICE and has been a huge supporter over the > years contributing to just about every aspect of the IX. They have > contributed everything from donating equipment, transit, mailing list > services and TONS of manual Bird config over the years. > > In particular, Doug McIntyre has contributed a huge amount of effort > when MICE was just a pinkie. It would have been much more difficult > without his help. > > Thanks! > > Jay > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net > -- John Unger President 612.325.2909 Vaultas | vaultas.com Connecting you to the Ecosystem

Dec. 18, 2024

Please welcome Mid-Rivers to MICE!

by Jeremy Lumby

Name: Mid-Rivers Telephone Cooperative Switch: 511 Core (7504R 10G/100G) Port: E 4/13 and E4/14 added to portchannel 39 ASN: 11961 IPv4: This is a port upgrade to a total of 4x10G. All IP info remains the same. IPv6: Peering Contact: nse(a)midrivers.coop Route Servers: Yes Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 M: 612-355-7740 D: 612-392-6814 F: 952-873-7425 jlumby(a)mnvoip.com

Dec. 13, 2024

[MICE-DISCUSS] Re: ipHouse MICE Disconnect

by Joe Unger

Thank you to ipHouse for all that you have done over the years. The MICE community truly appreciates your help and support. You guys will be missed. On Mon, Dec 2, 2024 at 3:56 PM Mike Horwath <drechsau(a)geeks.org> wrote: > On Mon, Dec 02, 2024 at 02:38:21PM -0600, Jay Hanke via mice-discuss wrote: > > In particular, Doug McIntyre has contributed a huge amount of effort > > when MICE was just a pinkie. It would have been much more difficult > > without his help. > > Doug deserves so much thanks. He rocks but I've known that since the > late 1980s.. :) > > -- > 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 > -- Joe Unger 612.709.8699 joe(a)vaultas.com Vaultas | *Connecting you to the Ecosystem* vaultas.com

Dec. 2, 2024