- mice-discuss - lists.micemn.net

Please welcome WIN LLC to MICE!

by Jeremy Lumby

Name: WIN LLC Switch: MICE 511 Core Port: E 6/32/1 ASN: 11796 IPv4: All IP info stays the same, this is a port upgrade to 2x100G in Po 7 IPv6: Peering Contact: peering(a)wintechnology.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

Sept. 7, 2023

Global Net (AS395466) - Circuit Restored

by Global Net NOC

MICEMN Members - Our carrier has resolved their power issue to restore our circuit and we have connectivity into Minneapolis again. I will begin to restore BGP sessions with our peers this morning. GLOBAL NET AS 395466 IPv4 206.108.255.97 IPv6 2001:504:27:0:6:8ca:0:1 Thanks, Scott Reed Global Net NOC noc(a)theglobal.net Global Net Peering Peering peering(a)theglobal.net

Aug. 30, 2023

Global Net (AS395466) - Carrier Outage / Carrier Maintenance

by Global Net NOC

MICEMN Members - Our carrier experienced a DC power plant failure on Saturday, August 26th @ 1356 MDT at which time our circuit between Bozeman, MT and Minneapolis, MN went down. This circuit was restored this morning at 0301 MDT, but via a temporary power supply. We are being told that the carrier will be replacing the failed DC power plant tomorrow around noon MDT with an expected impact of 90 minutes to our circuit. Our port to the MICE is currently down but I have all BGP sessions disabled for manual and graceful restart once service is fully restored. I would like to wait until the temporary power supply is replaced before bringing sessions back up. GLOBAL NET AS 395466 IPv4 206.108.255.97 IPv6 2001:504:27:0:6:8ca:0:1 Thanks, Scott Reed Global Net NOC noc(a)theglobal.net<mailto:noc@theglobal.net> Global Net Peering Peering peering(a)theglobal.net<mailto:peering@theglobal.net>

Aug. 28, 2023

Network Nerd Thoughts?

by Michael Horwath

ObOnTopic: Anyone have a contact there to see if they are willing to join MICE? ObOffTopic: everything else https://www.prnewswire.com/news-releases/gateway-fiber-bringing-100-fiber-o… I moved into CR July 2020 and .. connectivity options are not really options. Greenbutthole (you know, Centurylink, Lumen, some name that starts with Q) loves to say high speed, every address in a 4 block area around me is only capable of 10Mbps down. Comcast? I mean, it works, for a small value of works. Anyone dealt with these folks in the past in other areas? Will they come through? Are there any gotchas? I wish we had more choice. I mean, we had over 200 choices back in the late 90s and early-mid 2000s but they are all gone now. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Aug. 21, 2023

Re: OT: Blast from the past!

by Dean Bahls

That 10G spike on 8/15/13 probably got a few folks pretty excited back then. 😊 Dean From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Monday, August 14, 2023 2:26 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] OT: Blast from the past! [cid:image001.jpg@01D9CEBB.EA5C1610] -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io<mailto:jayhanke@southfront.io> Phone 612-204-0000 https://southfront.io/path.html ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 14, 2023

OT: Blast from the past!

by Jay Hanke

[image: 20180410_090819.jpg] -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 https://southfront.io/path.html

Aug. 14, 2023

Re: Ridgeview Traffic

by Jeremy Lumby

Yes, the second route server is at Ridgeview now. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Steve Howard Sent: Monday, August 7, 2023 4:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Ridgeview Traffic A great first weekend! I hope that others add/move to Ridgeview to increase the value of the redundant site. Is there going to be a route server at Ridgeview? On 8/7/23 14:21, Jay Hanke wrote: Looks like a successful weekend at the new Ridgeview. This is the uplink traffic measured at the 511 end. _____ 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 _____ 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

Aug. 7, 2023

Re: Ridgeview Traffic

by Steve Howard

Aug. 7, 2023

Ridgeview Traffic

by Jay Hanke

Looks like a successful weekend at the new Ridgeview. This is the uplink traffic measured at the 511 end. [image: image.png]

Aug. 7, 2023

Give Aways

by Justin Krejci

I have a few items to give away: first responding, first served. Must either pick up in Minnetonka, MN or possibly nearby area. 4x Fiber SMF duplex jumpers * SC to LC blue connectors (not green APC) * 5m fiber jumper with thicker outdoor jacket * The last 12 inches or so at each end are the standard yellow jacket. * Condition: New/unused 8x (could be 9 or 10) standard RJ45 patch panels * 48 ports * 2RU height * 19" width post * Model: unknown * Includes cable management clips that fasten onto the front side * Wire bars on the rear side for tying rear side cables * Condition: New/unused 2x 40G QSFPs * Model: Robofiber QSFP-4010-PLR4-A * Condition: Light or no use 2x 40G QSFPs * Model: Robofiber QSFP-4010-LR4-A * Condition: Light or no use 6x 40G QSFP AOCs * 1m length * Model: Robofiber QSFP-40G-01AOC-A * Condition: Light use, no damage, no visible wear and tear If anyone wants pictures of any of these let me know and I can send you some. -Justin

Aug. 4, 2023

Re: MICE Ridgeview Traffic

by Jay Hanke

There's a single switch at Ridgeview. The SFN switch is in Albert Lea. I added the core link between Ridgeview and 511 to ixp_mgr graphing yesterday. https://ixpmgr.micemn.net/statistics/core-bundle/3?category=bits&side=a I believe that remote switch traffic doesn't count in switch total traffic as they are classified as "core" links in ixp manager. SFN has an uplink to MN VoIP and an uplink to the new Ridgeview switch to our Albert Lea location. We're removing the link between the SFN Albert Lea remote and MN VoIP. We have one remaining member using the MN VoIP uplink (WCTA). That's scheduled to move on 8/8. On Wed, Aug 2, 2023 at 1:36 PM Steve Howard <showard(a)paulbunyan.net> wrote: > > Ahh! Thanks! I didn't realize there were multiple MICE switches at Ridgeview. > > > > On 8/2/23 13:09, Justin Krejci wrote: > > That is an SFN switch, look at the drop down list near the top of the page. > > > Try this URL instead: https://ixpmgr.micemn.net/statistics/switch/13/bits > > > > > ________________________________ > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Steve Howard <showard(a)PAULBUNYAN.NET> > Sent: Wednesday, August 2, 2023 1:01 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] MICE Ridgeview Traffic > > I wonder if the IXP Manager graphs are working correctly? Our records showed that we peaked around 30Gbps of traffic at Ridgeview last night. But, the graphs at https://ixpmgr.micemn.net/statistics/core-bundle/2 only show a peak of around 7-8Gbps at Ridgeview. > > > On 8/2/23 12:38, Jay Hanke wrote: > > It's not on the weather map yet. To see the graphs you need to go into ixpmgr.micemn.net > > On Wed, Aug 2, 2023, 12:02 PM Jonathan Stewart < jonathan(a)les.net> wrote: >> >> Is the Ridgeview switch visible on the weather map? I can't see it but maybe it's a problem with my eyes. >> >> http://micelg.usinternet.com/cacti/plugins/weathermap/weathermap-cacti-plug… >> >> Thanks, >> Jonathan >> >> On Tue, 2023-08-01 6:05 p.m., Justin Krejci wrote: >> >> I turned up a couple of BGP sessions across the Ridgeview MICE switch now. At this moment we are pushing close to 10gbps. >> >> >> I will continue tomorrow to get more BGP sessions going. >> >> >> >> ________________________________ >> From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Steve Howard <showard(a)PAULBUNYAN.NET> >> Sent: Tuesday, August 1, 2023 4:42 PM >> To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> Subject: Re: [MICE-DISCUSS] MICE Ridgeview Traffic >> >> Paul Bunyan Communications moved one of our MICE connections to Ridgeview today. We had a few minor issues that caused us to re-route traffic back to 511 temporarily. But, everything is looking good now. >> >> We hope that other MICE members will consider adding a connection (or moving one) to Ridgeview. This will help give everybody some protection against a failure at the main site! >> >> >> >> On 8/1/23 14:21, Jay Hanke wrote: >> >> Running about 18G of traffic on the new MICE Ridgeview switch! >> >> Jay >> >> >> >> ________________________________ >> >> 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 >> >> >> -- >> 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 >> >> >> ________________________________ >> >> 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 > > > > ________________________________ > > 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 > > > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 3, 2023

Re: MICE Ridgeview Traffic

by Steve Howard

Aug. 2, 2023

Re: MICE Ridgeview Traffic

by Justin Krejci

That is an SFN switch, look at the drop down list near the top of the page. Try this URL instead: https://ixpmgr.micemn.net/statistics/switch/13/bits ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Steve Howard <showard(a)PAULBUNYAN.NET> Sent: Wednesday, August 2, 2023 1:01 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE Ridgeview Traffic I wonder if the IXP Manager graphs are working correctly? Our records showed that we peaked around 30Gbps of traffic at Ridgeview last night. But, the graphs at https://ixpmgr.micemn.net/statistics/core-bundle/2<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169099…> only show a peak of around 7-8Gbps at Ridgeview. On 8/2/23 12:38, Jay Hanke wrote: It's not on the weather map yet. To see the graphs you need to go into ixpmgr.micemn.net<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169099…> On Wed, Aug 2, 2023, 12:02 PM Jonathan Stewart < jonathan(a)les.net<mailto:jonathan@les.net>> wrote: Is the Ridgeview switch visible on the weather map? I can't see it but maybe it's a problem with my eyes. http://micelg.usinternet.com/cacti/plugins/weathermap/weathermap-cacti-plug… Thanks, Jonathan On Tue, 2023-08-01 6:05 p.m., Justin Krejci wrote: I turned up a couple of BGP sessions across the Ridgeview MICE switch now. At this moment we are pushing close to 10gbps. I will continue tomorrow to get more BGP sessions going. ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET><mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> on behalf of Steve Howard <showard(a)PAULBUNYAN.NET><mailto:showard@PAULBUNYAN.NET> Sent: Tuesday, August 1, 2023 4:42 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE Ridgeview Traffic Paul Bunyan Communications moved one of our MICE connections to Ridgeview today. We had a few minor issues that caused us to re-route traffic back to 511 temporarily. But, everything is looking good now. We hope that other MICE members will consider adding a connection (or moving one) to Ridgeview. This will help give everybody some protection against a failure at the main site! On 8/1/23 14:21, Jay Hanke wrote: Running about 18G of traffic on the new MICE Ridgeview switch! Jay ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169092…> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169099…> -- 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 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169099…> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169099…> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169099…>

Aug. 2, 2023

Re: MICE Ridgeview Traffic

by Steve Howard

Aug. 2, 2023

Re: MICE Ridgeview Traffic

by AnthonyAnderberg＠nuvera.net

The combination of a vacation and a platform migration have put me a little behind on the weathermap front - will try to give it some CPU cycles yet this week. Exciting times in any case! Cheers, anthony From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Jay Hanke <jayhanke(a)SOUTHFRONT.IO> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Date: Wednesday, August 2, 2023 at 12:38 PM To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE Ridgeview Traffic It's not on the weather map yet. To see the graphs you need to go into ixpmgr.micemn.net<http://ixpmgr.micemn.net> On Wed, Aug 2, 2023, 12:02 PM Jonathan Stewart <jonathan(a)les.net<mailto:jonathan@les.net>> wrote: Is the Ridgeview switch visible on the weather map? I can't see it but maybe it's a problem with my eyes. http://micelg.usinternet.com/cacti/plugins/weathermap/weathermap-cacti-plug… Thanks, Jonathan On Tue, 2023-08-01 6:05 p.m., Justin Krejci wrote: I turned up a couple of BGP sessions across the Ridgeview MICE switch now. At this moment we are pushing close to 10gbps. I will continue tomorrow to get more BGP sessions going. ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET><mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> on behalf of Steve Howard <showard(a)PAULBUNYAN.NET><mailto:showard@PAULBUNYAN.NET> Sent: Tuesday, August 1, 2023 4:42 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE Ridgeview Traffic Paul Bunyan Communications moved one of our MICE connections to Ridgeview today. We had a few minor issues that caused us to re-route traffic back to 511 temporarily. But, everything is looking good now. We hope that other MICE members will consider adding a connection (or moving one) to Ridgeview. This will help give everybody some protection against a failure at the main site! On 8/1/23 14:21, Jay Hanke wrote: Running about 18G of traffic on the new MICE Ridgeview switch! Jay ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169092…> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- 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 ________________________________ 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

Aug. 2, 2023

Re: MICE Ridgeview Traffic

by Jay Hanke

It's not on the weather map yet. To see the graphs you need to go into ixpmgr.micemn.net On Wed, Aug 2, 2023, 12:02 PM Jonathan Stewart <jonathan(a)les.net> wrote: > Is the Ridgeview switch visible on the weather map? I can't see it but > maybe it's a problem with my eyes. > > > http://micelg.usinternet.com/cacti/plugins/weathermap/weathermap-cacti-plug… > > Thanks, > Jonathan > > On Tue, 2023-08-01 6:05 p.m., Justin Krejci wrote: > > I turned up a couple of BGP sessions across the Ridgeview MICE switch now. At > this moment we are pushing close to 10gbps. > > > I will continue tomorrow to get more BGP sessions going. > > > > ------------------------------ > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Steve Howard > <showard(a)PAULBUNYAN.NET> <showard(a)PAULBUNYAN.NET> > *Sent:* Tuesday, August 1, 2023 4:42 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] MICE Ridgeview Traffic > > Paul Bunyan Communications moved one of our MICE connections to Ridgeview > today. We had a few minor issues that caused us to re-route traffic back > to 511 temporarily. But, everything is looking good now. > > We hope that other MICE members will consider adding a connection (or > moving one) to Ridgeview. This will help give everybody some protection > against a failure at the main site! > > > > On 8/1/23 14:21, Jay Hanke wrote: > > Running about 18G of traffic on the new MICE Ridgeview switch! > > Jay > > > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169092…> > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > -- > 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 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Aug. 2, 2023

Re: MICE Ridgeview Traffic

by Jonathan Stewart

Is the Ridgeview switch visible on the weather map? I can't see it but maybe it's a problem with my eyes. http://micelg.usinternet.com/cacti/plugins/weathermap/weathermap-cacti-plug… Thanks, Jonathan On Tue, 2023-08-01 6:05 p.m., Justin Krejci wrote: > > I turned up a couple of BGP sessions across the Ridgeview MICE switch > now. At this moment we are pushing close to 10gbps. > > > I will continue tomorrow to get more BGP sessions going. > > > > ------------------------------------------------------------------------ > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of > Steve Howard <showard(a)PAULBUNYAN.NET> > *Sent:* Tuesday, August 1, 2023 4:42 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] MICE Ridgeview Traffic > Paul Bunyan Communications moved one of our MICE connections to > Ridgeview today. We had a few minor issues that caused us to re-route > traffic back to 511 temporarily. But, everything is looking good now. > > We hope that other MICE members will consider adding a connection (or > moving one) to Ridgeview. This will help give everybody some > protection against a failure at the main site! > > > > On 8/1/23 14:21, Jay Hanke wrote: >> Running about 18G of traffic on the new MICE Ridgeview switch! >> >> Jay >> > > > ------------------------------------------------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169092…> > > > > ------------------------------------------------------------------------ > > 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> > -- 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

Aug. 2, 2023

Re: MICE Ridgeview Traffic

by Justin Krejci

I turned up a couple of BGP sessions across the Ridgeview MICE switch now. At this moment we are pushing close to 10gbps. I will continue tomorrow to get more BGP sessions going. ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Steve Howard <showard(a)PAULBUNYAN.NET> Sent: Tuesday, August 1, 2023 4:42 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE Ridgeview Traffic Paul Bunyan Communications moved one of our MICE connections to Ridgeview today. We had a few minor issues that caused us to re-route traffic back to 511 temporarily. But, everything is looking good now. We hope that other MICE members will consider adding a connection (or moving one) to Ridgeview. This will help give everybody some protection against a failure at the main site! On 8/1/23 14:21, Jay Hanke wrote: Running about 18G of traffic on the new MICE Ridgeview switch! Jay ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=169092…>

Aug. 1, 2023

Re: MICE Ridgeview Traffic

by Steve Howard

Aug. 1, 2023

MICE Ridgeview Traffic

by Jay Hanke

Running about 18G of traffic on the new MICE Ridgeview switch! Jay

Aug. 1, 2023

Please welcome Nebraksalink dba OPTK to MICE!

by Jeremy Lumby

Name: Nebraksalink dba OPTK Switch: MN VoIP Port: E 45 and 46 in Portchannel 7 ASN: 16851 IPv4: IPs remain the same. This is a switch move/port upgrade IPv6: Peering Contact: engineering(a)optk.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

July 31, 2023

Please welcome Akamai Technologies Inc. to MICE!

by Jeremy Lumby

Name: Akamai Technologies Inc. Switch: MICE Core Port: E6/31/1 (added to po19) ASN: 20940 IPv4: IPs remain the same. This is a port upgrade to 3x100G and 4x100G IPv6: Peering Contact: peering(a)akamai.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

July 31, 2023

Please welcome Paul Bunyan Communications to MICE!

by Jeremy Lumby

Name: Paul Bunyan Communications Switch: MICE Core - Ridgeview Port: E 3/5/1 Moving a second port from Fiber Minnesota for location diversity (Tie fibers 13-14) ASN: 14371 IPv4: 206.108.255.119 IPv6: 2001:504:27::3823:0:2 Peering Contact: peering(a)paulbunyan.net 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

July 31, 2023

Re: Fiber cut?

by Ben Wiechman

I don't show any issues in our log around that time. We observed some degradation roughly along the I-90 corridor across southern MN from Worthington to Owatonna around 10 AM yesterday, but nothing logged for the afternoon. 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 Tue, Jul 25, 2023 at 8:10 AM Larry Larsen < 000000186bf54e79-dmarc-request(a)lists.iphouse.net> wrote: > Good Morning; > > > > We use Arvig for our transport to Minneapolis, however Arvig is just using > Zayo fiber behind the scenes. I double checked all of my alerts and I do > not see any outages. > > > > Thanks! > > > > Larry L. > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Frank > Bulk > *Sent:* Monday, July 24, 2023 5:50 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] Fiber cut? > > > > WARNING!! This message originated from an *External Source*. Please use > proper judgment and caution when opening attachments, clicking links, or > responding to this email. > > Did anyone notice a fiber cut on Zayo’s network between Le Mars and Sioux > City around 2:45 pm? > > > > Our staff saw some damage south to their fiber of NIPCO, but it’s possible > that Zayo abandoned that stretch of fiber due to an earlier Hwy 75 road > project. > > > > Regards, > > > > Frank > > > ------------------------------ > > 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 >

July 25, 2023

Re: Fiber cut?

by Larry Larsen

Good Morning; We use Arvig for our transport to Minneapolis, however Arvig is just using Zayo fiber behind the scenes. I double checked all of my alerts and I do not see any outages. Thanks! Larry L. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Monday, July 24, 2023 5:50 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Fiber cut? WARNING!! This message originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Did anyone notice a fiber cut on Zayo's network between Le Mars and Sioux City around 2:45 pm? Our staff saw some damage south to their fiber of NIPCO, but it's possible that Zayo abandoned that stretch of fiber due to an earlier Hwy 75 road project. Regards, Frank ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

July 25, 2023

Fiber cut?

by Frank Bulk

Did anyone notice a fiber cut on Zayo's network between Le Mars and Sioux City around 2:45 pm? Our staff saw some damage south to their fiber of NIPCO, but it's possible that Zayo abandoned that stretch of fiber due to an earlier Hwy 75 road project. Regards, Frank

July 24, 2023

Please welcome the Society of Young Enterprise Engineers to MICE!

by Jeremy Lumby

Name: Society of Young Enterprise Engineers Switch: MN VoIP Ports: E 43 ASN: 25944 IPv4: 206.108.255.211/24 IPv6: 2001:504:27:0:0:6558::1/64 Peering Contact: peering(a)syee.org 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

July 20, 2023

Please welcome Albany Mutual Telephone to MICE!

by Jeremy Lumby

Name: Albany Mutual Telephone Switch: Fiber Minnesota Ports: Hu1/0/17 ASN: 27204 IPv4: 206.108.255.128/24 IPv6: 2001:504:27::6a44:0:1/64 Peering Contact: nate.scmitt(a)albanytel.net Route Servers: YES Please note that Albany Mutual Telephone is taking over AS27204 from New Core Wireless. 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

July 11, 2023

Please welcome AcenTek (MN) to MICE!

by Jeremy Lumby

Name: Ace Telephone Association, Inc dba AcenTek Switch: Fiber Minnesota Port: Hu1/0/18 ASN: 40328 IPv4: This is a port upgrade from 20G to 100G. All IP info remains the same. IPv6: Peering Contact: peering(a)acentek.net Route Servers: Yes BFD: No 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

July 11, 2023

Re: FW: [EXTERNAL] - [MICE-DISCUSS] MICE Participants List

by Richard Laager

It turns out that I had the route server links wrong. There is a database ID that gets put into the BIRD protocol. I thought it was the customer (participant) ID. But it turns out it is the VLAN Interface ID. I corrected this, and now the links work correctly. On 2023-06-28 06:26, Miles McCredie wrote: > > FWIW, the looking glass links generate the following message > -- Richard

June 28, 2023

Re: MICE Participants List

by Jay Hanke

Michael- https://ixpmgr.micemn.net/api/v4/member-export/ixf/1.0 BTW if you're at other IXs many of them have this same format available listed as IX-F Member Export URL On Wed, Jun 28, 2023 at 10:09 AM Michael Hare <000000097dab80c5-dmarc-request(a)lists.iphouse.net> wrote: > > Not sure if this is a difficult ask, but any way to get a json/xml/yaml/api dump of this page? > > Why: annotation of data collected by mac address accounting. Mostly looking to tie name to IP. I've occasionally used tool assistance to parse the previous HTML page. Not sure if anyone else does [or would if easier] do this. Open to other suggestions. > > -Michael > > > -----Original Message----- > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of > > Richard Laager > > Sent: Wednesday, June 28, 2023 4:10 AM > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > Subject: [MICE-DISCUSS] MICE Participants List > > > > The MICE participants list is now built from IXP Manager: > > https://micemn.net/participants.html > > > > If there is something wrong about your entry, please let me or Jeremy > > know. See below about port discrepancies, first. > > > > I want to specifically thank Dustin Frandle of South Front Networks. He > > started this effort with JavaScript code to convert a standard IX-F JSON > > export into a participants table. While I ended up going a different > > direction (for reasons discussed below), he got the ball rolling. > > > > Jeremy and I wanted to retain the contact addresses, which IXP Manager > > only outputs in the IX-F export if you are logged in. (And, despite my > > request, they remain firm in that position and refuse to allow > > customization.) > > > > Additionally, I wanted to retain the ports, since our current process > > has Cologix using the website as the LOA/CFA. (We may want to move to a > > more standard approach on that, but I didn't want to put that change > > into the critical path of getting the participants list automated.) > > > > Unfortunately, despite a previous request and my re-request for it, the > > IXP Manager maintainer has taken a firm position that the IX-F JSON > > export should not be customizable. So I cannot easily tweak the template > > to output emails when unauthenticated or add additional information for > > ports. > > > > IXP Manager does support the idea of a custom member export, and INEX > > (the exchange primarily behind IXP Manager development) does use that > > for a custom JSON output. However, that requires building the desired > > output from scratch. I figured if I was going to do that, I might as > > well just output HTML directly. That way, I only have one thing in one > > language (PHP) to worry about, rather than two things (PHP + JavaScript). > > > > Granted, there are some cons too. I'm not 100% happy about any of this. > > But, ultimately I had to make some decision to get it done, and that's > > where I landed. > > > > I did the best I could with the responsive design. There are a couple of > > pre-existing bugs on edge cases (e.g. when your size falls at 991.xx so > > it's not <= 991 but also not >= 992, which is maybe only possible on > > HiDPI displays) that affect the whole site. This page in particular is > > not ideal on mobile, but I did what I could. If you've got better ideas, > > please let me know. > > > > ---- > > > > There are a couple port discrepancies that I've asked Jeremy to review: > > > > 702 Communications * > > Bluepeak > > Broadband Visions * > > G-Core Labs * > > HBC * > > LTD Broadband > > Omnitel * > > Paul Bunyan > > South Front > > Truestream * > > US Internet > > > > * I'm pretty sure these were wrong/outdated on the old list and correct > > in IXP Manager / on the new list. > > > > -- > > Richard

June 28, 2023

Re: MICE Participants List

by Michael Hare

Not sure if this is a difficult ask, but any way to get a json/xml/yaml/api dump of this page? Why: annotation of data collected by mac address accounting. Mostly looking to tie name to IP. I've occasionally used tool assistance to parse the previous HTML page. Not sure if anyone else does [or would if easier] do this. Open to other suggestions. -Michael > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of > Richard Laager > Sent: Wednesday, June 28, 2023 4:10 AM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] MICE Participants List > > The MICE participants list is now built from IXP Manager: > https://micemn.net/participants.html > > If there is something wrong about your entry, please let me or Jeremy > know. See below about port discrepancies, first. > > I want to specifically thank Dustin Frandle of South Front Networks. He > started this effort with JavaScript code to convert a standard IX-F JSON > export into a participants table. While I ended up going a different > direction (for reasons discussed below), he got the ball rolling. > > Jeremy and I wanted to retain the contact addresses, which IXP Manager > only outputs in the IX-F export if you are logged in. (And, despite my > request, they remain firm in that position and refuse to allow > customization.) > > Additionally, I wanted to retain the ports, since our current process > has Cologix using the website as the LOA/CFA. (We may want to move to a > more standard approach on that, but I didn't want to put that change > into the critical path of getting the participants list automated.) > > Unfortunately, despite a previous request and my re-request for it, the > IXP Manager maintainer has taken a firm position that the IX-F JSON > export should not be customizable. So I cannot easily tweak the template > to output emails when unauthenticated or add additional information for > ports. > > IXP Manager does support the idea of a custom member export, and INEX > (the exchange primarily behind IXP Manager development) does use that > for a custom JSON output. However, that requires building the desired > output from scratch. I figured if I was going to do that, I might as > well just output HTML directly. That way, I only have one thing in one > language (PHP) to worry about, rather than two things (PHP + JavaScript). > > Granted, there are some cons too. I'm not 100% happy about any of this. > But, ultimately I had to make some decision to get it done, and that's > where I landed. > > I did the best I could with the responsive design. There are a couple of > pre-existing bugs on edge cases (e.g. when your size falls at 991.xx so > it's not <= 991 but also not >= 992, which is maybe only possible on > HiDPI displays) that affect the whole site. This page in particular is > not ideal on mobile, but I did what I could. If you've got better ideas, > please let me know. > > ---- > > There are a couple port discrepancies that I've asked Jeremy to review: > > 702 Communications * > Bluepeak > Broadband Visions * > G-Core Labs * > HBC * > LTD Broadband > Omnitel * > Paul Bunyan > South Front > Truestream * > US Internet > > * I'm pretty sure these were wrong/outdated on the old list and correct > in IXP Manager / on the new list. > > -- > Richard

June 28, 2023

MICE Participants List

by Richard Laager

The MICE participants list is now built from IXP Manager: https://micemn.net/participants.html If there is something wrong about your entry, please let me or Jeremy know. See below about port discrepancies, first. I want to specifically thank Dustin Frandle of South Front Networks. He started this effort with JavaScript code to convert a standard IX-F JSON export into a participants table. While I ended up going a different direction (for reasons discussed below), he got the ball rolling. Jeremy and I wanted to retain the contact addresses, which IXP Manager only outputs in the IX-F export if you are logged in. (And, despite my request, they remain firm in that position and refuse to allow customization.) Additionally, I wanted to retain the ports, since our current process has Cologix using the website as the LOA/CFA. (We may want to move to a more standard approach on that, but I didn't want to put that change into the critical path of getting the participants list automated.) Unfortunately, despite a previous request and my re-request for it, the IXP Manager maintainer has taken a firm position that the IX-F JSON export should not be customizable. So I cannot easily tweak the template to output emails when unauthenticated or add additional information for ports. IXP Manager does support the idea of a custom member export, and INEX (the exchange primarily behind IXP Manager development) does use that for a custom JSON output. However, that requires building the desired output from scratch. I figured if I was going to do that, I might as well just output HTML directly. That way, I only have one thing in one language (PHP) to worry about, rather than two things (PHP + JavaScript). Granted, there are some cons too. I'm not 100% happy about any of this. But, ultimately I had to make some decision to get it done, and that's where I landed. I did the best I could with the responsive design. There are a couple of pre-existing bugs on edge cases (e.g. when your size falls at 991.xx so it's not <= 991 but also not >= 992, which is maybe only possible on HiDPI displays) that affect the whole site. This page in particular is not ideal on mobile, but I did what I could. If you've got better ideas, please let me know. ---- There are a couple port discrepancies that I've asked Jeremy to review: 702 Communications * Bluepeak Broadband Visions * G-Core Labs * HBC * LTD Broadband Omnitel * Paul Bunyan South Front Truestream * US Internet * I'm pretty sure these were wrong/outdated on the old list and correct in IXP Manager / on the new list. -- Richard

June 28, 2023

WiscNet router maintenance Thursday, June 29, 4pm

by Chris Wopat

WiscNet will be replacing a router this coming Thursday at 4pm local time. Our MICE connection will be down during this transition. Expect it down for 15mins or so, maintenance should be complete by 7pm. Cheers, -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

June 27, 2023

Re: Three BGP peers

by David Farmer

Verizon Media is back as of about 3:00 this afternoon. It looks like Google’s second port is back at the same time, but it only has minimal traffic currently. On Fri, Jun 23, 2023 at 15:20 Jay Hanke <jayhanke(a)southfront.io> wrote: > Both Yahoo MICE ports are still down. > > 1/2 Google ports are down. > > On Fri, Jun 23, 2023 at 3:18 PM Steve Savoy <stevesavoy(a)wctatel.com> > wrote: > > > > Has Yahoo been re-established for anyone? > > > > Thanks, > > Steve > > > > -----Original Message----- > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank > Bulk > > Sent: Thursday, June 22, 2023 4:42 PM > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > Subject: [MICE-DISCUSS] Three BGP peers > > > > Anyone else seeing both Yahoo peers and one Google peer down since early > am? I didn't see any log messages about exceeding prefix counts or the like. > > > > Frank > > > > SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary > information for VRF default Router identifier 207.32.15.21, local AS number > 18883 Neighbor Status Codes: m - Under maintenance > > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down > State PfxRcd PfxAcc > > 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 > Active > > 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 > Active > > 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 > Active > > SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary > information for VRF default Router identifier 207.32.15.21, local AS number > 18883 Neighbor Status Codes: m - Under maintenance > > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down > State PfxRcd PfxAcc > > 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 > 12:23:40 Active > > 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 > 12:23:47 Active > > 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 > 12:23:48 Active > > SiouxCity-Fibernet-Arista(s2)# > > 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. > -- =============================================== 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 ===============================================

June 24, 2023

Global Net (AS395466) - Circuit Down

by Global Net NOC

MICEMN Members - Our circuit to Cologix in Minneapolis is hard down due to a bridge collapse, train derailment and subsequent fiber cut in Columbus, MT. Our BGP sessions remain down. 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 Global Net Peering peering(a)theglobal.net

June 24, 2023

Re: [External] Re: [MICE-DISCUSS] Three BGP peers

by Tom Krenn

They did mention a transport issue they are working on when I talked to them earlier today. Sounds like they are hoping for a resolution before Monday. Tom Krenn Network Architect Enterprise Architecture - Information Technology -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Steve Savoy Sent: Friday, June 23, 2023 3:18 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [External] Re: [MICE-DISCUSS] Three BGP peers CAUTION: This email was sent from outside of Hennepin County. Unless you recognize the sender and know the content, do not click links or open attachments. Has Yahoo been re-established for anyone? Thanks, Steve -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Thursday, June 22, 2023 4:42 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Three BGP peers Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. Frank SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active SiouxCity-Fibernet-Arista(s2)# 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. Disclaimer: If you are not the intended recipient of this message, please immediately notify the sender of the transmission error and then promptly permanently delete this message from your computer system.

June 23, 2023

Re: Three BGP peers

by Steve Savoy

Thank you for the update Jay. Have a great weekend everyone. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Friday, June 23, 2023 3:20 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Three BGP peers Both Yahoo MICE ports are still down. 1/2 Google ports are down. On Fri, Jun 23, 2023 at 3:18 PM Steve Savoy <stevesavoy(a)wctatel.com> wrote: > > Has Yahoo been re-established for anyone? > > Thanks, > Steve > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk > Sent: Thursday, June 22, 2023 4:42 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] Three BGP peers > > Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. > > Frank > > SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active > 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active > 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active > SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active > 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active > 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active > SiouxCity-Fibernet-Arista(s2)# > 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.

June 23, 2023

Re: Three BGP peers

by Jay Hanke

Both Yahoo MICE ports are still down. 1/2 Google ports are down. On Fri, Jun 23, 2023 at 3:18 PM Steve Savoy <stevesavoy(a)wctatel.com> wrote: > > Has Yahoo been re-established for anyone? > > Thanks, > Steve > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk > Sent: Thursday, June 22, 2023 4:42 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] Three BGP peers > > Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. > > Frank > > SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active > 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active > 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active > SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active > 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active > 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active > SiouxCity-Fibernet-Arista(s2)# > 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.

June 23, 2023

Re: Three BGP peers

by Steve Savoy

Has Yahoo been re-established for anyone? Thanks, Steve -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Thursday, June 22, 2023 4:42 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Three BGP peers Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. Frank SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active SiouxCity-Fibernet-Arista(s2)# 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.

June 23, 2023

Re: Route Server 1 - BFD not working

by Richard Laager

On 2023-06-23 10:46, Jonathan Stewart wrote: > Richard's debugging suggested it was BIRD not responding to valid BFD > packets transmitted from our Juniper router. Re: "valid". In looking at the packet capture again, I'm not sure how the discriminator values are supposed to look. So maybe that is related. > The problem for diagnosis is reproduceability. Since a session reset > fixed the problem, we can't reproduce the problem, and that makes > diagnosis impossible without additional data. > > To be clear, I don't expect any further action from MICE, as the > problem is resolved. I sent a write-up to the bird-users mailing list. We'll see if anyone there has any ideas. -- Richard

June 23, 2023

Re: Route Server 1 - BFD not working

by Jonathan Stewart

Richard's debugging suggested it was BIRD not responding to valid BFD packets transmitted from our Juniper router. But almost all BFD sessions are up, so what's wrong with this specific one--or pair in this case? There was a fibre cut which disconnected AS18451 from MICE for 1.5 days--maybe at service restoration there was packet loss for the first few seconds, so BFD handshaking failed? The problem for diagnosis is reproduceability. Since a session reset fixed the problem, we can't reproduce the problem, and that makes diagnosis impossible without additional data. To be clear, I don't expect any further action from MICE, as the problem is resolved. I'm just discussing troubleshooting and the limitations of our knowledge about this problem. Cheers, Jonathan Stewart AS18451 On Thu, 2023-06-22 3:53 p.m., Mike Horwath wrote: > On Thu, Jun 22, 2023 at 02:40:14PM -0500, Jonathan Stewart wrote: >> Disable the BGP (and thus also BFD) session, waited a minute, and >> re-enabled BGP & BFD. >> >> Came back as normal and looks fine now on both IPv4 and IPv6. >> >> Thanks for the assistance Richard. >> >> Though it's still not clear what the real cause of the problem was. > Bugs from the router vs the route-server perhaps? > > I hate magic like this. Magic sucks >

June 23, 2023

Re: [External] [MICE-DISCUSS] Three BGP peers

by Tom Krenn

Not peered with Yahoo but I do see that Google peer down. Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd 206.108.255.167 0 15169 605946 572995 0 0 0 13:06:45 Active Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd 2001:504:27::3b41:0:2 0 15169 598758 572903 0 0 0 13:07:55 Active Tom Krenn Network Architect Enterprise Architecture - Information Technology -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Thursday, June 22, 2023 4:42 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [External] [MICE-DISCUSS] Three BGP peers CAUTION: This email was sent from outside of Hennepin County. Unless you recognize the sender and know the content, do not click links or open attachments. Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. Frank SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active SiouxCity-Fibernet-Arista(s2)# Disclaimer: If you are not the intended recipient of this message, please immediately notify the sender of the transmission error and then promptly permanently delete this message from your computer system.

June 22, 2023

Re: Three BGP peers

by Frank Bulk

Thanks for confirming. Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Andrew Hoyos Sent: Thursday, June 22, 2023 5:03 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Three BGP peers Same, suspect fiber cut or maint. Weathermap doesn’t show any traffic on those links. [cid:image001.png@01D9A52B.A1A56C50] [cid:image002.png@01D9A52B.A1A56C50] > On Jun 22, 2023, at 4:42 PM, Frank Bulk <fbulk(a)MYPREMIERONLINE.COM<mailto:fbulk@MYPREMIERONLINE.COM>> wrote: > > Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. > > Frank > > SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab > BGP summary information for VRF default > Router identifier 207.32.15.21, local AS number 18883 > Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active > 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active > 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active > SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab > BGP summary information for VRF default > Router identifier 207.32.15.21, local AS number 18883 > Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active > 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active > 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active > SiouxCity-Fibernet-Arista(s2)#

June 22, 2023

Re: Three BGP peers

by Andrew Hoyos

Same, suspect fiber cut or maint. Weathermap doesn’t show any traffic on those links. > On Jun 22, 2023, at 4:42 PM, Frank Bulk <fbulk(a)MYPREMIERONLINE.COM> wrote: > > Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. > > Frank > > SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab > BGP summary information for VRF default > Router identifier 207.32.15.21, local AS number 18883 > Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active > 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active > 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active > SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab > BGP summary information for VRF default > Router identifier 207.32.15.21, local AS number 18883 > Neighbor Status Codes: m - Under maintenance > Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc > 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active > 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active > 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active > SiouxCity-Fibernet-Arista(s2)#

June 22, 2023

Three BGP peers

by Frank Bulk

Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. Frank SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active SiouxCity-Fibernet-Arista(s2)#

June 22, 2023

Re: Route Server 1 - BFD not working

by Mike Horwath

On Thu, Jun 22, 2023 at 02:40:14PM -0500, Jonathan Stewart wrote: > Disable the BGP (and thus also BFD) session, waited a minute, and > re-enabled BGP & BFD. > > Came back as normal and looks fine now on both IPv4 and IPv6. > > Thanks for the assistance Richard. > > Though it's still not clear what the real cause of the problem was. Bugs from the router vs the route-server perhaps? I hate magic like this. Magic sucks -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

June 22, 2023

Re: Route Server 1 - BFD not working

by Jonathan Stewart

On Wed, 2023-06-21 6:54 p.m., Richard Laager wrote: > Before I try that, have you tried flapping your BGP session? I had a chance to try this today. Disable the BGP (and thus also BFD) session, waited a minute, and re-enabled BGP & BFD. Came back as normal and looks fine now on both IPv4 and IPv6. Thanks for the assistance Richard. Though it's still not clear what the real cause of the problem was. Curious. Cheers, 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

June 22, 2023

Re: Route Server 1 - BFD not working

by Richard Laager

On 2023-06-22 08:39, Michael Hare wrote: > This March I reported to peering@ a similar problem to RR1 If this was happening in March, the "good" news is that this is not due to the new route servers (different OS, BIRD upgrade, new config, etc.). I looked at the BIRD release notes, and I'm not seeing anything about BFD specifically. There are plenty of mentions of generic bug fixes. I suppose I should take this to the BIRD mailing list. -- Richard

June 22, 2023

Re: Route Server 1 - BFD not working

by Michael Hare

Jonathan, This March I reported to peering@ a similar problem to RR1; I’m not sure when my problem started, I only noticed it while doing CLI jockey work on my router. I have had success removing and adding the BFD session on my Juniper. Over the last three months I saw one recurrence to RR1 but it was over v4 and v6; same solution for me. I didn’t spend time debugging JunOS further [myself or with jtac]. My side is a Juniper MX running 20.4. I have since added BFD session monitoring so I'm not reliant on syslogs. -Michael From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Wednesday, June 21, 2023 6:54 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Route Server 1 - BFD not working On 2023-06-21 14:06, Jonathan Stewart wrote: On our BGP session to Route Server 1 (206.108.225.1 & 2001:504:27::d1af:0:1) i have lost the BFD session. My Juniper router shows the state as "Down". Is this intentional? An accident of the upgrades? Is my configuration wrong? Anyone else noticing this? My configuration is an interval of 1000 ms, multiplier 3. MICE is configured as 500 * 3 tcpdump shows your BFD control packets coming in, but bird is not responding. I'm seeing the same issue with 206.108.255.137 (Inteliquent AS 40160) on IPv4 and 2001:504:27:0:0:B7F8::1 (Compudyne, AS47096) on IPv6. Everyone else is consistent between the two route servers. This thread from 2020 talks about someone having BFD issues after a reboot, which they fixed by restarting BFD in BIRD. That might be something to try if we run out of other ideas: https://www.mail-archive.com/bird-users@network.cz/msg05382.html Before I try that, have you tried flapping your BGP session? -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 22, 2023