- mice-discuss - lists.micemn.net

Re: Fwd: Google - Drain of routes for Route-Servers in your IX

by Anthony Anderberg

Yes, in last fall’s meeting we reminded everyone that they needed to create bilateral sessions with Google right away if they hadn’t already done so. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Jeremy Lumby <jlumby(a)MNVOIP.COM> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Date: Wednesday, April 3, 2024 at 2:38 PM To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Fwd: Google - Drain of routes for Route-Servers in your IX They did it to MICE back in December From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Wednesday, April 3, 2024 2:32 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Fwd: Google - Drain of routes for Route-Servers in your IX I haven't heard this for MICE, but presumably they will be doing the same thing here? -------- Forwarded Message -------- Subject: Google - Drain of routes for Route-Servers in your IX (fwd) Date: Wed, 3 Apr 2024 14:31:55 +0000 (UTC) From: Chris Caputo <ccaputo(a)seattleix.net><mailto:ccaputo@seattleix.net> To: members(a)seattleix.net<mailto:members@seattleix.net> FYI from Google... Chris ---------- Forwarded message ---------- Date: Wed, 03 Apr 2024 04:21:02 -0700 From: Google Peering Operations <peering-ops(a)google.com><mailto:peering-ops@google.com> To: info(a)seattleix.net<mailto:info@seattleix.net> Subject: Drain of routes for Route-Servers in your IX Dear Internet Exchange, As part of Google's effort to simplify peering operations and increase routing security we have decided to stop advertising and receiving prefix information from Route-Servers in Internet Exchanges. The BGP session with the route servers will remain established. We are planning to implement the change in your IX in the next few weeks. We won’t disconnect from the IX and we will keep current BGP bilateral sessions with individual peers on the IX. We invite other networks that rely on Route-Servers to request a bilateral session. Bilateral session request can be done at: https://isp.google.com/iwantpeering We kindly request you to inform peers in your Internet Exchange of these future changes so they can request bilateral sessions with us if they desire to do so. Sincerely, Google Network Operations ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

April 3, 2024

Re: Fwd: Google - Drain of routes for Route-Servers in your IX

by Jeremy Lumby

They did it to MICE back in December From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Wednesday, April 3, 2024 2:32 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Fwd: Google - Drain of routes for Route-Servers in your IX I haven't heard this for MICE, but presumably they will be doing the same thing here? -------- Forwarded Message -------- Subject: Google - Drain of routes for Route-Servers in your IX (fwd) Date: Wed, 3 Apr 2024 14:31:55 +0000 (UTC) From: Chris Caputo <mailto:ccaputo@seattleix.net> <ccaputo(a)seattleix.net> To: members(a)seattleix.net <mailto:members@seattleix.net> FYI from Google... Chris ---------- Forwarded message ---------- Date: Wed, 03 Apr 2024 04:21:02 -0700 From: Google Peering Operations <mailto:peering-ops@google.com> <peering-ops(a)google.com> To: info(a)seattleix.net <mailto:info@seattleix.net> Subject: Drain of routes for Route-Servers in your IX Dear Internet Exchange, As part of Google's effort to simplify peering operations and increase routing security we have decided to stop advertising and receiving prefix information from Route-Servers in Internet Exchanges. The BGP session with the route servers will remain established. We are planning to implement the change in your IX in the next few weeks. We won’t disconnect from the IX and we will keep current BGP bilateral sessions with individual peers on the IX. We invite other networks that rely on Route-Servers to request a bilateral session. Bilateral session request can be done at: https://isp.google.com/iwantpeering We kindly request you to inform peers in your Internet Exchange of these future changes so they can request bilateral sessions with us if they desire to do so. Sincerely, Google Network Operations _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1

April 3, 2024

Re: Fwd: Google - Drain of routes for Route-Servers in your IX

by Reid Fishler

I believe its internet-wide. Reid On Wed, Apr 3, 2024 at 3:32 PM Richard Laager <rlaager(a)wiktel.com> wrote: > I haven't heard this for MICE, but presumably they will be doing the same > thing here? > -------- Forwarded Message -------- > Subject: Google - Drain of routes for Route-Servers in your IX (fwd) > Date: Wed, 3 Apr 2024 14:31:55 +0000 (UTC) > From: Chris Caputo <ccaputo(a)seattleix.net> <ccaputo(a)seattleix.net> > To: members(a)seattleix.net > > FYI from Google... > > Chris > > ---------- Forwarded message ---------- > Date: Wed, 03 Apr 2024 04:21:02 -0700 > From: Google Peering Operations <peering-ops(a)google.com> > <peering-ops(a)google.com> > To: info(a)seattleix.net > Subject: Drain of routes for Route-Servers in your IX > > Dear Internet Exchange, > > As part of Google's effort to simplify peering operations and increase > routing security we have decided to stop advertising and receiving prefix > information from Route-Servers in Internet Exchanges. The BGP session with > the route servers will remain established. We are planning to implement the > change in your IX in the next few weeks. > > We won’t disconnect from the IX and we will keep current BGP bilateral > sessions with individual peers on the IX. We invite other networks that > rely on Route-Servers to request a bilateral session. Bilateral session > request can be done at: https://isp.google.com/iwantpeering > > We kindly request you to inform peers in your Internet Exchange of these > future changes so they can request bilateral sessions with us if they > desire to do so. > > Sincerely, > Google Network Operations > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- Reid Fishler Senior Director Hurricane Electric +1-510-580-4178

April 3, 2024

Fwd: Google - Drain of routes for Route-Servers in your IX

by Richard Laager

I haven't heard this for MICE, but presumably they will be doing the same thing here? -------- Forwarded Message -------- Subject: Google - Drain of routes for Route-Servers in your IX (fwd) Date: Wed, 3 Apr 2024 14:31:55 +0000 (UTC) From: Chris Caputo <ccaputo(a)seattleix.net> To: members(a)seattleix.net FYI from Google... Chris ---------- Forwarded message ---------- Date: Wed, 03 Apr 2024 04:21:02 -0700 From: Google Peering Operations <peering-ops(a)google.com> To: info(a)seattleix.net Subject: Drain of routes for Route-Servers in your IX Dear Internet Exchange, As part of Google's effort to simplify peering operations and increase routing security we have decided to stop advertising and receiving prefix information from Route-Servers in Internet Exchanges. The BGP session with the route servers will remain established. We are planning to implement the change in your IX in the next few weeks. We won’t disconnect from the IX and we will keep current BGP bilateral sessions with individual peers on the IX. We invite other networks that rely on Route-Servers to request a bilateral session. Bilateral session request can be done at: https://isp.google.com/iwantpeering We kindly request you to inform peers in your Internet Exchange of these future changes so they can request bilateral sessions with us if they desire to do so. Sincerely, Google Network Operations

April 3, 2024

Please welcome MIDnet LLC Network to MICE!

by Jeremy Lumby

Name: MIDnet LLC Switch: NOCIX Ports: E 5/16 ASN: 16970 IPv4: 206.108.255.230/24 IPv6: 2001:504:27:0:0:424A::1/64 Peering Contact: noc(a)mid.net Route Servers: YES Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

March 29, 2024

Please welcome Qwilt Inc. to MICE!

by Jeremy Lumby

Name: Qwilt Inc. Switch: MICE Core 511 Ports: 5/2/1 in portchannel 12 for a total of 2x100G ASN: 20253 IPv4: All IP info remains the same, this is a 100G port addition IPv6: Peering Contact: peering(a)qwilt.com Route Servers: 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

March 27, 2024

Please welcome Mankato Networks to MICE!

by Jeremy Lumby

Name: Mankato Networks Switch: MICE Core - 511 Ports: E 4/38 in portchannel 32 for a total of 2x10G ASN: This is a remote switch uplink upgrade; all other info remains the same IPv4: IPv6: Peering Contact: peering(a)mankatonetworks.net Route Servers: 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 26, 2024

Please welcome Fort Dodge Fiber to MICE!

by Jeremy Lumby

Name: City of Fort Dodge dba Fort Dodge Fiber Switch: SouthFront Networks Ports: E 5/2 for a total of 1x10G ASN: 400405 IPv4: 206.108.255.229/24 IPv6: 2001:504:27:0:6:1C15::1/64 Peering Contact: noc(a)fortdodgefiber.net Route Servers: YES Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

March 26, 2024

Please welcome Starwire Technologies to MICE!

by Jeremy Lumby

Name: Starwire Technologies, LLC Switch: MICE Core - Ridgeview Ports: E 3/31/4 Strands 127-128 for a total of 1x10G ASN: 16614 IPv4: 206.108.255.227/24 IPv6: 2001:504:27:0:0:40E6::1/64 Peering Contact: info(a)starwire.net Route Servers: YES Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

March 26, 2024

Re: MICE interface flap

by Jeremy Lumby

I did get more information from Arista related to the bug that caused the other cards to restart/ports to flap a month ago. It is still in progress, so not everything is published in its final state yet. It comes down to swapping in a R2 card in a chassis that has mostly R1 cards in it. BUG 916990 Release Note: When Linecard of a SKU is swapped with Linecard of different SKU, SandFap agent corresponding to other Linecards on the chassis may restart 1 time. There is no workaround, recommendation is the perform the SKU swap during a maintenance window In our situation, this is the summary: Agent restarted when we replaced 7500-R with 7500-R2 because the SPPID binding was already present for a different VOQ. Agent restart happens to clear out this binding to allocate it properly with the 7500-R2 linecard. More information about the bug: The forwarding chip has a Traffic Manager that does destination lookup table that provides a destination based on a globally known ID called systemPhyPortID (SPPID). This SystemPhyPortID (SPPID) uniquely identifies the Virtual Output Queues (VOQ) that the packet will get inserted into and the final forwarding chip port the packet will be sent towards. The software binding of Traffic Manager's destination lookup table corresponding to SPPID of MeshDrop port wasn't cleaned up during removal of 7500-R card. When 7500-R2 card was inserted this SPPID got allocated to the front panel port. When programming on an existing slice agent (the cards which were already present on the switch) triggered for this Front panel port, the code asserted about binding already present for this SPPID with a different VOQ (MeshDrop port's VOQ), causing the slice agent to restart. Jeremy -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 21, 2024 4:54 PM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] MICE interface flap A quick update. I just heard from Arista support that the interface flap last week was the result of a new bug that they are currently working out the details of. At the moment I have no further information about the details. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Friday, February 16, 2024 9:44 AM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] MICE interface flap It will be interesting when Arista responds. It sounds very similar. The week before we upgraded to 4.30.5M to prepare for the new card (7500R2-36CQ-LC). -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Friday, February 16, 2024 9:03 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE interface flap Thanks for sharing, we definitely saw this, too. We had a *somewhat* similar issue last year that when we slotted a card into our 7504 and the other card rebooted. Turned out to be some kind of mesh bug. Bug ID 765840 resolved in 4.30.1. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Wednesday, February 14, 2024 4:57 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE interface flap I am still sorting out the details. But it was related to the card swap scheduled for today. The card was in up and running without an issue for several minutes, however when I programmed/moved the first link to it, all of the other cards in the core switch started rebooting themselves. I am opening a ticket with Arista since we seem to be stable at the moment. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Chris Wopat Sent: Wednesday, February 14, 2024 4:56 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE interface flap WiscNet's remote switch flapped twice within the last half hour: Feb 14 16:34:16.657 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Feb 14 16:39:29.456 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Aggregate traffic definitely shows a hit: https://link.edgepilot.com/s/5abcf6c9/_Ox0o9rFAUimx0FLu4zJ0g?u=http://micel… Curious if others experienced flaps or could reveal logs from the core Arista? -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965 Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.

March 19, 2024

UG 45 Meeting Reminder

by Anthony Anderberg

The MICE UG 45 meeting will be held Wednesday, March 20, 3:00 pm at the University of Minnesota IT Building. 2218 University Ave SE Minneapolis, MN 55414, Room 185 Across University Ave SE from Huntington (TCF) Bank Stadium 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/94910223662?pwd=RUluTERkODlsdU93eHlQejR4eFVRdz09 ID: 94910223662, passcode: XdrNr3 651-372-8299 (passcode: 988007) Thanks everyone, Anthony

March 18, 2024

Re: MWPS 2024 Transportion

by Joe Unger

Jay, John and I would be interested in the group bus ride. We are still trying to determine if we can make the NANOG plus the Peering Summit. You could put us down as a 'Maybe/Pending', and we will continue to firm things up as you firm things up on our end. On Thu, Mar 14, 2024 at 11:42 AM Jay Hanke < 0000001ddf7fafbb-dmarc-request(a)lists.iphouse.net> wrote: > If I had a coach bus going from MN to Kansas City Peering Summit, are > others interested? > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 507-327-2398 > https://southfront.io/ > -- Joe Unger 612.709.8699 joe(a)vaultas.com Vaultas | *Connecting you to the Ecosystem* vaultas.com

March 18, 2024

Re: MWPS 2024 Transportion

by Chris Wopat

I doubt i'm on the path but - is it going for NANOG 91 (Jun 10-12, https://www.nanog.org/events/future/) or just the summit? On Thu, Mar 14, 2024 at 11:42 AM Jay Hanke <0000001ddf7fafbb-dmarc-request(a)lists.iphouse.net> wrote: > > If I had a coach bus going from MN to Kansas City Peering Summit, are > others interested? > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 507-327-2398 > https://southfront.io/

March 14, 2024

MWPS 2024 Transportion

by Jay Hanke

If I had a coach bus going from MN to Kansas City Peering Summit, are others interested? -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 507-327-2398 https://southfront.io/

March 14, 2024

Re: MICE Usage Graphs

by Randy Lehs - CarverLink

Thank you! 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: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Anthony Anderberg Sent: Wednesday, March 6, 2024 10:56 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE Usage Graphs Yes, this had been on my todo list since Jeremy’s port changes - guess I just needed my friends to prod me a bit. :-) I think I’ve got everything cleaned up; I was able to preserve CarverLink’s data history but most of the others are new since the port changes. Cheers, Anthony From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> on behalf of Randy Lehs <rlehs(a)CARVERLINK.COM<mailto:rlehs@CARVERLINK.COM>> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Date: Tuesday, March 5, 2024 at 5:26 PM To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Subject: [MICE-DISCUSS] MICE Usage Graphs I noticed that several ports stopped graphing on the weathermap about a month ago, and just wanted to make sure someone was aware/working on it since I use the graphs all the time. 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 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 6, 2024

Re: MICE Usage Graphs

by Anthony Anderberg

Yes, this had been on my todo list since Jeremy’s port changes - guess I just needed my friends to prod me a bit. :-) I think I’ve got everything cleaned up; I was able to preserve CarverLink’s data history but most of the others are new since the port changes. Cheers, Anthony From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Randy Lehs <rlehs(a)CARVERLINK.COM> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Date: Tuesday, March 5, 2024 at 5:26 PM To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] MICE Usage Graphs I noticed that several ports stopped graphing on the weathermap about a month ago, and just wanted to make sure someone was aware/working on it since I use the graphs all the time. 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 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 6, 2024

MICE Usage Graphs

by Randy Lehs - CarverLink

I noticed that several ports stopped graphing on the weathermap about a month ago, and just wanted to make sure someone was aware/working on it since I use the graphs all the time. 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

March 5, 2024

Please welcome CarverLink to MICE!

by Jeremy Lumby

Name: CarverLink - Carver County Switch: MN VoIP Port: E 29 ASN: 55216 IPv4: IPs remain the same. This is a switch move IPv6: Peering Contact: rlehs(a)carverlink.com Route Servers: 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

Feb. 27, 2024

Re: IRR Mandatory at MICE / New Route Servers

by Richard Laager

Update: We are now down to 2 prefixes with exceptions. One fixed 13 of 14 prefixes but seemingly missed one, so hopefully that will get fixed now that I've prodded them. The other hasn't responded in a while. I emailed again and left a voicemail. If I don't hear back, I'll probably just drop that one if/when the other network fixes theirs. Then the exceptions will be gone. -- Richard

Feb. 27, 2024

Global Net - AS395466 Maintenance

by Global Net NOC

MICEMN Members - Our upstream provider, Zayo, will be undergoing a forced relocation at our datacenter in Montana. Expect our BGP sessions to drop during this time. 2/22 2200 – 2/23 0500 MST GLOBAL NET AS 395466 IPV4 206.108.255.97 IPV6 2001:504:27:0:6:8ca:0:1 Thanks, Global Net NOC noc(a)theglobal.net<mailto:noc@theglobal.net> Global Net Peering peering(a)theglobal.net<mailto:peering@theglobal.net>

Feb. 22, 2024

Re: UG 45 Meeting

by Richard Laager

This time with the right attachments. On 2024-02-21 22:42, Richard Laager wrote: > > The MICE UG 45 meeting will be held Wednesday, March 20, 3:00 pm at UMN. > > 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/94910223662?pwd=RUluTERkODlsdU93eHlQejR4eFVRdz09 > ID: 94910223662, passcode: XdrNr3 > 651-372-8299 (passcode: 988007) > -- Richard

Feb. 22, 2024

UG 45 Meeting

by Richard Laager

The MICE UG 45 meeting will be held Wednesday, March 20, 3:00 pm at UMN. 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/94910223662?pwd=RUluTERkODlsdU93eHlQejR4eFVRdz09 ID: 94910223662, passcode: XdrNr3 651-372-8299 (passcode: 988007) -- Richard

Feb. 22, 2024

Re: MICE interface flap

by Jeremy Lumby

A quick update. I just heard from Arista support that the interface flap last week was the result of a new bug that they are currently working out the details of. At the moment I have no further information about the details. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Friday, February 16, 2024 9:44 AM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] MICE interface flap It will be interesting when Arista responds. It sounds very similar. The week before we upgraded to 4.30.5M to prepare for the new card (7500R2-36CQ-LC). -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Friday, February 16, 2024 9:03 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE interface flap Thanks for sharing, we definitely saw this, too. We had a *somewhat* similar issue last year that when we slotted a card into our 7504 and the other card rebooted. Turned out to be some kind of mesh bug. Bug ID 765840 resolved in 4.30.1. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Wednesday, February 14, 2024 4:57 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE interface flap I am still sorting out the details. But it was related to the card swap scheduled for today. The card was in up and running without an issue for several minutes, however when I programmed/moved the first link to it, all of the other cards in the core switch started rebooting themselves. I am opening a ticket with Arista since we seem to be stable at the moment. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Chris Wopat Sent: Wednesday, February 14, 2024 4:56 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE interface flap WiscNet's remote switch flapped twice within the last half hour: Feb 14 16:34:16.657 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Feb 14 16:39:29.456 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Aggregate traffic definitely shows a hit: https://link.edgepilot.com/s/5abcf6c9/_Ox0o9rFAUimx0FLu4zJ0g?u=http://micel… Curious if others experienced flaps or could reveal logs from the core Arista? -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965 Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.

Feb. 21, 2024

Please welcome Arvig to MICE!

by Jeremy Lumby

Name: Arvig Switch: MICE 511 Core Port: E5/1/1 (added to po42) ASN: 16904 IPv4: IPs remain the same. This is a port upgrade to 3x100G IPv6: Peering Contact: peering(a)arvig.com Route Servers: 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

Feb. 21, 2024

Re: MICE interface flap

by Jeremy Lumby

It will be interesting when Arista responds. It sounds very similar. The week before we upgraded to 4.30.5M to prepare for the new card (7500R2-36CQ-LC). -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Friday, February 16, 2024 9:03 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE interface flap Thanks for sharing, we definitely saw this, too. We had a *somewhat* similar issue last year that when we slotted a card into our 7504 and the other card rebooted. Turned out to be some kind of mesh bug. Bug ID 765840 resolved in 4.30.1. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Wednesday, February 14, 2024 4:57 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE interface flap I am still sorting out the details. But it was related to the card swap scheduled for today. The card was in up and running without an issue for several minutes, however when I programmed/moved the first link to it, all of the other cards in the core switch started rebooting themselves. I am opening a ticket with Arista since we seem to be stable at the moment. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Chris Wopat Sent: Wednesday, February 14, 2024 4:56 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE interface flap WiscNet's remote switch flapped twice within the last half hour: Feb 14 16:34:16.657 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Feb 14 16:39:29.456 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Aggregate traffic definitely shows a hit: https://link.edgepilot.com/s/5abcf6c9/_Ox0o9rFAUimx0FLu4zJ0g?u=http://micel… Curious if others experienced flaps or could reveal logs from the core Arista? -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965 Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.

Feb. 16, 2024

Re: MICE interface flap

by Frank Bulk

Thanks for sharing, we definitely saw this, too. We had a *somewhat* similar issue last year that when we slotted a card into our 7504 and the other card rebooted. Turned out to be some kind of mesh bug. Bug ID 765840 resolved in 4.30.1. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Wednesday, February 14, 2024 4:57 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE interface flap I am still sorting out the details. But it was related to the card swap scheduled for today. The card was in up and running without an issue for several minutes, however when I programmed/moved the first link to it, all of the other cards in the core switch started rebooting themselves. I am opening a ticket with Arista since we seem to be stable at the moment. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Chris Wopat Sent: Wednesday, February 14, 2024 4:56 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE interface flap WiscNet's remote switch flapped twice within the last half hour: Feb 14 16:34:16.657 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Feb 14 16:39:29.456 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Aggregate traffic definitely shows a hit: https://link.edgepilot.com/s/5abcf6c9/_Ox0o9rFAUimx0FLu4zJ0g?u=http://micel… Curious if others experienced flaps or could reveal logs from the core Arista? -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965 Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.

Feb. 16, 2024

Re: MICE interface flap

by Jeremy Lumby

I just wanted to send over a quick update. I stayed at 511 for an hour after all of the line cards came back online. The core switch remained stable. I performed basic actions such as programming ports, inserting optics into the new card, and bringing links up on it. None of them triggered the cards to reboot again. At the moment I believe that the switch is stable. I will report back any findings from Arista as to the root cause when I have them, and so that this can be avoided in the future. -----Original Message----- From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 14, 2024 4:57 PM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] MICE interface flap I am still sorting out the details. But it was related to the card swap scheduled for today. The card was in up and running without an issue for several minutes, however when I programmed/moved the first link to it, all of the other cards in the core switch started rebooting themselves. I am opening a ticket with Arista since we seem to be stable at the moment. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Chris Wopat Sent: Wednesday, February 14, 2024 4:56 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE interface flap WiscNet's remote switch flapped twice within the last half hour: Feb 14 16:34:16.657 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Feb 14 16:39:29.456 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Aggregate traffic definitely shows a hit: http://micelg.usinternet.com/export/graph_2625.html Curious if others experienced flaps or could reveal logs from the core Arista? -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

Feb. 15, 2024

Re: MICE interface flap

by Jeremy Lumby

I am still sorting out the details. But it was related to the card swap scheduled for today. The card was in up and running without an issue for several minutes, however when I programmed/moved the first link to it, all of the other cards in the core switch started rebooting themselves. I am opening a ticket with Arista since we seem to be stable at the moment. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Chris Wopat Sent: Wednesday, February 14, 2024 4:56 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE interface flap WiscNet's remote switch flapped twice within the last half hour: Feb 14 16:34:16.657 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Feb 14 16:39:29.456 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Aggregate traffic definitely shows a hit: http://micelg.usinternet.com/export/graph_2625.html Curious if others experienced flaps or could reveal logs from the core Arista? -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

Feb. 14, 2024

MICE interface flap

by Chris Wopat

WiscNet's remote switch flapped twice within the last half hour: Feb 14 16:34:16.657 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Feb 14 16:39:29.456 2024 s-minneapolis-hub mib2d[8448]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 540, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/23 Aggregate traffic definitely shows a hit: http://micelg.usinternet.com/export/graph_2625.html Curious if others experienced flaps or could reveal logs from the core Arista? -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

Feb. 14, 2024

Please welcome Integris to MICE!

by Jeremy Lumby

Name: Integris LLC (fka Compudyne) Switch: MICE Core - 511 Ports: E 3/34 in po 9 (100G) ASN: This is a Remote Switch uplink upgrade from 20G to 100G IPv4: NA IPv6: NA Peering Contact: peering(a)integrisit.com Route Servers: NA 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. 14, 2024

Re: MICE Server Updates

by Cameron Skappel

This evening I applied server updates to the rest of the MICE servers including Route Server 1. Let me know if there are issues. -- Cameron

Feb. 9, 2024

Please welcome SpaceX to MICE!

by Jeremy Lumby

Name: Space Exploration Technologies Inc. Switch: MICE Core - Ridgeview Ports: E 3/7 and 3/8 in po 3 (200G) Strands 17-20 ASN: 14593 IPv4: 206.108.255.226/24 IPv6: 2001:504:27:0:0:3901::2/64 Peering Contact: starlink-peering(a)spacex.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

Feb. 8, 2024

Re: MICE BFD Errors

by Andrew Hoyos

Just from our POV for a data point (timestamps in GMT) Feb 8 04:52:48 er1.511.msp bfdd[31763]: BFDD_STATE_UP_TO_DOWN: BFD Session 2001:504:27::d1af:0:2 (IFL 360) state Up -> Down LD/RD(228/3270602753) Up time:16:39:29 Local diag: CtlExpire Remote diag: None Reason: Detect Timer Expiry. Feb 8 04:52:48 er1.511.msp bfdd[31763]: BFDD_TRAP_SHOP_STATE_DOWN: local discriminator: 228, new state: down, interface: et-0/0/1.0, peer addr: 2001:504:27::d1af:0:2 Feb 8 04:59:05 er1.511.msp bfdd[31763]: BFDD_TRAP_SHOP_STATE_UP: local discriminator: 228, new state: up, interface: et-0/0/1.0, peer addr: 2001:504:27::d1af:0:2 Feb 8 05:12:26 er1.511.msp bfdd[31763]: BFDD_STATE_UP_TO_DOWN: BFD Session 2001:504:27::d1af:0:2 (IFL 360) state Up -> Down LD/RD(228/1591314386) Up time:00:13:22 Local diag: NbrSignal Remote diag: CtlExpire Reason: Received DOWN from PEER. Feb 8 05:12:26 er1.511.msp bfdd[31763]: BFDD_TRAP_SHOP_STATE_DOWN: local discriminator: 228, new state: down, interface: et-0/0/1.0, peer addr: 2001:504:27::d1af:0:2 We saw BFD go down to rs2 when those updates took place an hour ago and hasn’t come back up, still down. Juniper here, but based on ARP/ND for the others, looks like a mix of Cisco/Juniper devices so perhaps not specific to any platform. Address State Interface Time Interval Multiplier 2001:504:27::d1af:0:2 Down et-0/0/1.0 3.000 2.000 3 Client BGP, TX interval 0.500, RX interval 0.500 Session down time 01:11:17, previous up time 00:13:22 Local diagnostic NbrSignal, remote diagnostic CtlExpire Remote state Down, version 1 Session type: Single hop BFD Min async interval 0.500, min slow interval 2.000 Adaptive async TX interval 2.000, RX interval 2.000 Local min TX interval 2.000, minimum RX interval 0.500, multiplier 3 Remote min TX interval 1.000, min RX interval 0.500, multiplier 3 Local discriminator 228, remote discriminator 1591314386 Echo TX interval 2.000, echo detection interval 6.000 Echo mode disabled/inactiveno-absorb, no-refresh Session ID: 0x0 > On Feb 8, 2024, at 00:01, Richard Laager <rlaager(a)WIKTEL.COM> wrote: > > BIRD is complaining that various peers are sending BFD packets with an unknown session id. > > Anyone have thoughts on this? > > > The logs look like this: > 2024-02-07 23:44:14 <RMT> bfd1: Bad packet from YOUR_IP - unknown session id (SOME_INTEGER) > > Those marked with an asterisk were doing this yesterday, so prior to the reboot of rs2. > > > rs1: > > Inteliquent (Neutral Tandem) > 206.108.255.137 * > > > rs2: > > les.net > 2001:504:27::4813:0:1 > > Savage Communications > 206.108.255.17 * > 2001:504:27::5adc:0:1 * > > Stellar Association > 206.108.255.53 > 2001:504:27::8e16:0:1 * > > Hoyos Consulting > 2001:504:27::d15d:0:1 > > Eastern Iowa Data Group > 206.108.255.168 * > 2001:504:27::f7a2:0:1 * > > Omnitel Communications > 206.108.255.148 > > > Here is for the entire month of January: > > rlaager@rs1:~$ rg "^2024-01-.*Bad packet from" /var/log/bird/rs1-ipv*.1 | awk '{print $8}' | sort | uniq -c > 9 2001:504:27::3823:0:2 > 2 2001:504:27::8252:0:1 > 1183836 2001:504:27::b7f8:0:1 > 4 2001:504:27::d15d:0:1 > 1183834 206.108.255.101 > 7498 206.108.255.119 > 380 206.108.255.121 > 1463099 206.108.255.137 > 3 206.108.255.176 > 3 206.108.255.185 > > root@rs2:~# rg "^2024-01-.*Bad packet from" /var/log/bird/rs2-ipv*.1 | awk '{print $8}' | sort | uniq -c > 12 2001:504:27::1e49:0:1 > 1 2001:504:27::3823:0:2 > 1 2001:504:27::39:0:1 > 1457433 2001:504:27::5adc:0:1 > 3 2001:504:27::6478:0:1 > 1457369 2001:504:27::8e16:0:1 > 1 2001:504:27::9dbe:0:1 > 5 2001:504:27::9dbe:0:2 > 1179733 2001:504:27::b7f8:0:1 > 1176975 2001:504:27::d15d:0:1 > 4 2001:504:27::e4f:0:1 > 1 2001:504:27::f756:0:1 > 1331747 2001:504:27::f7a2:0:1 > 1179735 206.108.255.101 > 7494 206.108.255.119 > 1954 206.108.255.120 > 3 206.108.255.137 > 3 206.108.255.161 > 1331745 206.108.255.168 > 1457437 206.108.255.17 > 2 206.108.255.176 > 8 206.108.255.185 > 11 206.108.255.3 > 6 206.108.255.46 > 1457345 206.108.255.53 > 4 206.108.255.92 > > > -- > Richard

Feb. 8, 2024

MICE BFD Errors

by Richard Laager

BIRD is complaining that various peers are sending BFD packets with an unknown session id. Anyone have thoughts on this? The logs look like this: 2024-02-07 23:44:14 <RMT> bfd1: Bad packet from YOUR_IP - unknown session id (SOME_INTEGER) Those marked with an asterisk were doing this yesterday, so prior to the reboot of rs2. rs1: Inteliquent (Neutral Tandem) 206.108.255.137 * rs2: les.net 2001:504:27::4813:0:1 Savage Communications 206.108.255.17 * 2001:504:27::5adc:0:1 * Stellar Association 206.108.255.53 2001:504:27::8e16:0:1 * Hoyos Consulting 2001:504:27::d15d:0:1 Eastern Iowa Data Group 206.108.255.168 * 2001:504:27::f7a2:0:1 * Omnitel Communications 206.108.255.148 Here is for the entire month of January: rlaager@rs1:~$ rg "^2024-01-.*Bad packet from" /var/log/bird/rs1-ipv*.1 | awk '{print $8}' | sort | uniq -c 9 2001:504:27::3823:0:2 2 2001:504:27::8252:0:1 1183836 2001:504:27::b7f8:0:1 4 2001:504:27::d15d:0:1 1183834 206.108.255.101 7498 206.108.255.119 380 206.108.255.121 1463099 206.108.255.137 3 206.108.255.176 3 206.108.255.185 root@rs2:~# rg "^2024-01-.*Bad packet from" /var/log/bird/rs2-ipv*.1 | awk '{print $8}' | sort | uniq -c 12 2001:504:27::1e49:0:1 1 2001:504:27::3823:0:2 1 2001:504:27::39:0:1 1457433 2001:504:27::5adc:0:1 3 2001:504:27::6478:0:1 1457369 2001:504:27::8e16:0:1 1 2001:504:27::9dbe:0:1 5 2001:504:27::9dbe:0:2 1179733 2001:504:27::b7f8:0:1 1176975 2001:504:27::d15d:0:1 4 2001:504:27::e4f:0:1 1 2001:504:27::f756:0:1 1331747 2001:504:27::f7a2:0:1 1179735 206.108.255.101 7494 206.108.255.119 1954 206.108.255.120 3 206.108.255.137 3 206.108.255.161 1331745 206.108.255.168 1457437 206.108.255.17 2 206.108.255.176 8 206.108.255.185 11 206.108.255.3 6 206.108.255.46 1457345 206.108.255.53 4 206.108.255.92 -- Richard

Feb. 8, 2024

MICE Server Updates

by Cameron Skappel

This evening I applied server updates to some of the MICE servers including Router Server 2. Let me know if there are issues. -- Cameron

Feb. 8, 2024

MICE Core Switch Card Upgrade

by Richard Laager

Date & Time Wednesday, February 14 at 15:00 US/Central Description Jeremy will swap a (now unused) 10G line card for a 100G line card in the Arista core switch at 511. There is no expected impact for most participants. In the (relatively unlikely) event that a fiber cable is physically in the way and he has to unplug it to remove/install the card, he will disable BGP for that participant first and wait (unless the port is part of a LAG with sufficient excess capacity at that time of day). The Fiber Minnesota and Minnesota VoIP remote switches are connected by 3x100G LAG. Jeremy will move one port from each LAG from card 6 to the new card. Rollback Plan If there is some problem, the new 100G card can be removed. The ports in the Fiber Minnesota and Minnesota VoIP remote switches can be moved back to card 6. -- Richard

Feb. 8, 2024

Please welcome Mark Twain Rural Telephone Company to MICE!

by Jeremy Lumby

Name: Mark Twain Rural Telephone Company Switch: MN VoIP 10G Switch Port: E 14 ASN: 10750 IPv4: 206.108.255.225/24 IPv6: 2001:504:27:0:0:29FE::1/64 Peering Contact: noc(a)marktwain.net Route Servers: Yes Welcome Aboard! 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

Feb. 7, 2024

Re: MICE Core Switch EOS Upgrade

by Jeremy Lumby

The maintenance is complete, and everything appears to be functioning normally. From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Wednesday, February 7, 2024 5:54 AM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] MICE Core Switch EOS Upgrade The maintenance will begin shortly. From: Jeremy Lumby <jlumby(a)mnvoip.com <mailto:jlumby@mnvoip.com> > Sent: Tuesday, January 30, 2024 2:07 PM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > Subject: RE: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Correct, 6AM central time. Assuming things go well and there are no complications, the outage should be short (less than 15 minutes) From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > On Behalf Of Gartley, Dakota S Sent: Tuesday, January 30, 2024 12:47 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Assuming this is 6AM Central on the 7th? How long do we anticipate the upgrade to take? I'll need to inform our teams that this upgrade is taking place so they can ignore any alerts from our MICE circuits during the window. ____________________________ Dakota Gartley Senior Manager, Network Engineering | Optum Technology T +1 763-732-6405 <mailto:Dakota.gartley@optum.com> dakota.gartley(a)optum.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > on behalf of Richard Laager <rlaager(a)WIKTEL.COM <mailto:rlaager@WIKTEL.COM> > Date: Tuesday, January 30, 2024 at 12:38 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > Subject: Re: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Caution: External email. Do not open attachments or click on links if you do not recognize the sender. Date & Time NEW: Wednesday, February 7 at 06:00 US/Central OLD: Wednesday, January 31 at 06:00 US/Central Description Jeremy will upgrade software on the Arista core switch at 511. This is necessary to be able to install the (newer) 100G card into the switch. Rollback Plan The previous software image will be available to revert. -- Richard _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or intended recipient's authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1

Feb. 7, 2024

Re: MICE Core Switch EOS Upgrade

by Jeremy Lumby

The maintenance will begin shortly. From: Jeremy Lumby <jlumby(a)mnvoip.com> Sent: Tuesday, January 30, 2024 2:07 PM To: 'MICE Discuss' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Correct, 6AM central time. Assuming things go well and there are no complications, the outage should be short (less than 15 minutes) From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > On Behalf Of Gartley, Dakota S Sent: Tuesday, January 30, 2024 12:47 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Assuming this is 6AM Central on the 7th? How long do we anticipate the upgrade to take? I'll need to inform our teams that this upgrade is taking place so they can ignore any alerts from our MICE circuits during the window. ____________________________ Dakota Gartley Senior Manager, Network Engineering | Optum Technology T +1 763-732-6405 <mailto:Dakota.gartley@optum.com> dakota.gartley(a)optum.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > on behalf of Richard Laager <rlaager(a)WIKTEL.COM <mailto:rlaager@WIKTEL.COM> > Date: Tuesday, January 30, 2024 at 12:38 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > Subject: Re: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Caution: External email. Do not open attachments or click on links if you do not recognize the sender. Date & Time NEW: Wednesday, February 7 at 06:00 US/Central OLD: Wednesday, January 31 at 06:00 US/Central Description Jeremy will upgrade software on the Arista core switch at 511. This is necessary to be able to install the (newer) 100G card into the switch. Rollback Plan The previous software image will be available to revert. -- Richard _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or intended recipient's authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1

Feb. 7, 2024

Please welcome SpaceX to MICE!

by Jeremy Lumby

Name: Space Exploration Technologies Inc. Switch: MICE Core - 511 Ports: E 3/15 and 6/34 in po 20 (200G) ASN: 14593 IPv4: 206.108.255.224/24 IPv6: 2001:504:27:0:0:3901::1/64 Peering Contact: starlink-peering(a)spacex.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

Feb. 2, 2024

Addresses on the list...

by Mike Horwath

Calling out: From: Tritan Internet LLC (AS393577) <noc(a)as393577.net> Subject: TD#937 - Acknowledgement from Tritan Internet NOC Please subscribe either a user to the list or update things so that autoresponses do not occur. LISTSERV picked it up and did the right thing, thankfully. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Jan. 31, 2024

Please welcome Hoyos Consulting to MICE!

by Jeremy Lumby

Name: Hoyos Consulting LLC Switch: Compudyne 511 Port: et-0/0/49 ASN: 53597 IPv4: This is a port upgrade to 100G. All IP info remains the same. IPv6: Peering Contact: noc(a)hoyosconsulting.com 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

Jan. 31, 2024

Re: MICE Core Switch EOS Upgrade

by Jeremy Lumby

Correct, 6AM central time. Assuming things go well and there are no complications, the outage should be short (less than 15 minutes) From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Gartley, Dakota S Sent: Tuesday, January 30, 2024 12:47 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Assuming this is 6AM Central on the 7th? How long do we anticipate the upgrade to take? I'll need to inform our teams that this upgrade is taking place so they can ignore any alerts from our MICE circuits during the window. ____________________________ Dakota Gartley Senior Manager, Network Engineering | Optum Technology T +1 763-732-6405 <mailto:Dakota.gartley@optum.com> dakota.gartley(a)optum.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > on behalf of Richard Laager <rlaager(a)WIKTEL.COM <mailto:rlaager@WIKTEL.COM> > Date: Tuesday, January 30, 2024 at 12:38 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > Subject: Re: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Caution: External email. Do not open attachments or click on links if you do not recognize the sender. Date & Time NEW: Wednesday, February 7 at 06:00 US/Central OLD: Wednesday, January 31 at 06:00 US/Central Description Jeremy will upgrade software on the Arista core switch at 511. This is necessary to be able to install the (newer) 100G card into the switch. Rollback Plan The previous software image will be available to revert. -- Richard _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or intended recipient's authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1

Jan. 30, 2024

Re: MICE Core Switch EOS Upgrade

by Gartley, Dakota S

Assuming this is 6AM Central on the 7th? How long do we anticipate the upgrade to take? I’ll need to inform our teams that this upgrade is taking place so they can ignore any alerts from our MICE circuits during the window. ____________________________ Dakota Gartley Senior Manager, Network Engineering | Optum Technology T +1 763-732-6405 dakota.gartley(a)optum.com<mailto:Dakota.gartley@optum.com> [A picture containing text, clipart Description automatically generated] From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Richard Laager <rlaager(a)WIKTEL.COM> Date: Tuesday, January 30, 2024 at 12:38 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE Core Switch EOS Upgrade Caution: External email. Do not open attachments or click on links if you do not recognize the sender. Date & Time NEW: Wednesday, February 7 at 06:00 US/Central OLD: Wednesday, January 31 at 06:00 US/Central Description Jeremy will upgrade software on the Arista core switch at 511. This is necessary to be able to install the (newer) 100G card into the switch. Rollback Plan The previous software image will be available to revert. -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or intended recipient’s authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.

Jan. 30, 2024

Re: MICE Core Switch EOS Upgrade

by Richard Laager

Date & Time NEW: Wednesday, February 7 at 06:00 US/Central OLD: Wednesday, January 31 at 06:00 US/Central Description Jeremy will upgrade software on the Arista core switch at 511. This is necessary to be able to install the (newer) 100G card into the switch. Rollback Plan The previous software image will be available to revert. -- Richard

Jan. 30, 2024

Re: BGP ADD-PATH capability

by Richard Laager

Sorry for the delay. I owe everyone an update. I did not make any changes. There was still some discussion (albeit not a lot) happening on the bird-users list. Today, I got a reply about this on the IXP Manager mailing list: https://www.inex.ie/pipermail/ixpmanager/2024-January/003739.html Honestly, I'm not sure if this is worth it. I'll just leave this off. Maybe we can revisit in the future if there is more interest and/or if this potential BIRD bug discussion goes somewhere. I reverted my testing changes. -- Richard

Jan. 24, 2024

Re: BGP ADD-PATH capability

by Michael Hare

Here is a juniper example set protocols bgp group iBGP-reflector-v4 family inet unicast add-path receive set protocols bgp group iBGP-reflector-v4 family inet unicast add-path send prefix-policy addPathiBGPPolicyASBR set protocols bgp group iBGP-reflector-v4 family inet unicast add-path send path-count 3 addPathiBGPPolicyASBR could be as simple as ‘accept all’ or something more granular. Richard I think addressed this a few weeks back; consider the potential growth of your RIB and recognize that the feature to preinstall the backup path in your FIB, if possible on your hardware, may be a different knob. -Michael From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of David Farmer Sent: Thursday, January 11, 2024 1:29 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] BGP ADD-PATH capability Here are a couple of Cisco Docs https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration… https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/2… Hope that helps; On Thu, Jan 11, 2024 at 11:04 AM Jonathan Stewart <jonathan(a)les.net<mailto:jonathan@les.net>> wrote: Does anyone--like another IX, possibly--have documentation that can be shared about how to enable, disable, or ignore the add-path configuration on the member router? Farmer mentions they didn't have it enabled suggesting each operator would need to enable add-path on their router before the functionality could be used by each member. Thanks, Jonathan Jonathan Stewart Network Engineer LES.NET<http://LES.NET> - AS18451 Desk: 1-204-666-6191 Mobile: 1-204-990-2120 130 Portage Avenue E Winnipeg, MB R3C 0A1 CANADA On Wed, 2024-01-10 11:08 p.m., David Farmer wrote: I'll add while we are receiving the Additional-Path BGP Capability from RS1, we don't have it enabled on our side, so it is not being negotiated. Thanks On Wed, Jan 10, 2024 at 8:33 PM Richard Laager <rlaager(a)wiktel.com<mailto:rlaager@wiktel.com>> wrote: Today, the University of Minnesota tested with me. I enabled "add paths tx" on one of their sessions and it worked. -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- =============================================== 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 =============================================== ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- =============================================== 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 =============================================== ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 12, 2024

Re: BGP ADD-PATH capability

by David Farmer

Here are a couple of Cisco Docs https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration… https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/2… Hope that helps; On Thu, Jan 11, 2024 at 11:04 AM Jonathan Stewart <jonathan(a)les.net> wrote: > Does anyone--like another IX, possibly--have documentation that can be > shared about how to enable, disable, or ignore the add-path configuration > on the member router? > > Farmer mentions they didn't have it enabled suggesting each operator would > need to enable add-path on their router before the functionality could be > used by each member. > > Thanks, > Jonathan > > Jonathan Stewart > Network EngineerLES.NET - AS18451 > Desk: 1-204-666-6191 > Mobile: 1-204-990-2120 > 130 Portage Avenue E > Winnipeg, MB R3C 0A1 > CANADA > > On Wed, 2024-01-10 11:08 p.m., David Farmer wrote: > > I'll add while we are receiving the Additional-Path BGP Capability from > RS1, we don't have it enabled on our side, so it is not being negotiated. > > Thanks > > On Wed, Jan 10, 2024 at 8:33 PM Richard Laager <rlaager(a)wiktel.com> wrote: > >> Today, the University of Minnesota tested with me. I enabled "add paths >> tx" on one of their sessions and it worked. >> >> -- >> Richard >> >> >> ------------------------------ >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> > > > -- > =============================================== > 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 > =============================================== > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- =============================================== 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 ===============================================

Jan. 11, 2024

Re: BGP ADD-PATH capability

by Jonathan Stewart

Does anyone--like another IX, possibly--have documentation that can be shared about how to enable, disable, or ignore the add-path configuration on the member router? Farmer mentions they didn't have it enabled suggesting each operator would need to enable add-path on their router before the functionality could be used by each member. Thanks, Jonathan Jonathan Stewart Network Engineer LES.NET - AS18451 Desk: 1-204-666-6191 Mobile: 1-204-990-2120 130 Portage Avenue E Winnipeg, MB R3C 0A1 CANADA On Wed, 2024-01-10 11:08 p.m., David Farmer wrote: > I'll add while we are receiving the Additional-Path BGP Capability > from RS1, we don't have it enabled on our side, so it is not being > negotiated. > > Thanks > > On Wed, Jan 10, 2024 at 8:33 PM Richard Laager <rlaager(a)wiktel.com> wrote: > > Today, the University of Minnesota tested with me. I enabled "add > paths tx" on one of their sessions and it worked. > > -- > Richard > > > ------------------------------------------------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> > > > > -- > =============================================== > 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 > =============================================== > > ------------------------------------------------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> >

Jan. 11, 2024

Re: BGP ADD-PATH capability

by David Farmer

I'll add while we are receiving the Additional-Path BGP Capability from RS1, we don't have it enabled on our side, so it is not being negotiated. Thanks On Wed, Jan 10, 2024 at 8:33 PM Richard Laager <rlaager(a)wiktel.com> wrote: > Today, the University of Minnesota tested with me. I enabled "add paths > tx" on one of their sessions and it worked. > > -- > Richard > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- =============================================== 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 ===============================================

Jan. 11, 2024