June 2023 - mice-discuss - lists.micemn.net

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