- mice-discuss - lists.micemn.net

Please Welcome Mid-Rivers Telephone to MICE

by Jay Hanke

Name: Mid-Rivers Telephone Port: Main Switch (New 20G LAG) Ethernet4/12, Ethernet5/21 ASN: 11961 IPv4: 206.108.255.173/24 IPv6: 2001:504:27::2eb9:0:1/64 Peering Contact: nse(a)midrivers.coop Route Servers- YES BFD: No Please note these may be reclaimed ports. MICE uses LACP by default on all LAG ports. Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Feb. 15, 2021

SFN MICE Remote Scheduled Maintenance

by Jay Hanke

The SFN Remote switch will be undergoing maintenance and will be power cycled during our transport provider doing software upgrades. The SFN remote switch will be hard down during the part of the maintenance and be isolated during part of the maintenance. Connectivity may be intermittent during the entire window as software updates are applied. This will also affect test filtering sessions to MICE-RS3. Primary Window: FROM: Tuesday, Feb 23, 2021 0030 hours (CST) TO: Tuesday, Feb 23, 2021 0230 hours (CST) Backup Window: FROM: Tuesday, Feb 24, 2021 0030 hours (CST) TO: Tuesday, Feb 24, 2021 0230 hours (CST) Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Feb. 14, 2021

Re: state.mn.us expired yesterday?

by Knutson, Lee R

Your guess that it's possible that such a kind of TLD means the expiration date doesn't matter is correct. (Neustar calls them .US locality domain names.) I just inquired about a different .us domain myself and got this response from Neustar support: = Although the whois record may show a system generated expiration date, .US locality domains do not expire and are automatically renewed. At this time, there is no charge for locality domains, so there is no action needed on your part to ensure the registration is active. Additionally, in the WHOIS record, the status autoRenewPeriod is listed to indicate that your domain has been auto renewed by the Registry. This status and the domain's expiration date will remain the same until 45 days after your expiration date which is when your domain's expiration date will extend by 1 year from the date and the autoRenewPeriod status is removed from WHOIS. = Note that this only applies to .US /locality/ domain names, not all .us domain names. You can read more about the difference under the ".US Locality Management" section at https://www.about.us/faqs -- Lee Knutson, CISSP Network Systems Specialist Minnesota State 30 East 7th Street, St. Paul, MN 55101 lee.knutson(a)minnstate.edu Desk: 651-201-1609 -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Sunday, February 7, 2021 8:31 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] state.mn.us expired yesterday? It appears that state.mn.us expired yesterday? It's possible with such kind of TLD that that doesn't matter? Frank Bulk Registry WHOIS Server : whois.nic.us Domain Name: state.mn.us Registry Domain ID: D3624286-US Registrar WHOIS Server: Registrar URL: https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.whois.… Updated Date: 2021-01-12T14:03:55Z Creation Date: 2003-02-06T20:25:14Z Registry Expiry Date: 2021-02-06T20:25:14Z Registrar: State of Minnesota Registrar IANA ID: Registrar Abuse Contact Email: Registrar Abuse Contact Phone: Domain Status: ok https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ficann.org… Domain Status: autoRenewPeriod https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ficann.org… Registry Registrant ID: C7705028-US Registrant Name: Network Operations Center Registrant Organization: State of Minnesota Registrant Street: Office of Enterprise Technology Registrant Street: 500 Centennial Office Building Registrant Street: 658 Cedar Street Registrant City: St. Paul Registrant State/Province: MN Registrant Postal Code: 55155 Registrant Country: US Registrant Phone: +1.6512971111 Registrant Phone Ext: Registrant Fax: +1.6512975368 Registrant Fax Ext: Registrant Email: nic<%>nic.state.mn.us Registrant Application Purpose: P5 Registrant Nexus Category: C21 Registry Admin ID: C7705028-US Admin Name: Network Operations Center Admin Organization: State of Minnesota Admin Street: Office of Enterprise Technology Admin Street: 500 Centennial Office Building Admin Street: 658 Cedar Street Admin City: St. Paul Admin State/Province: MN Admin Postal Code: 55155 Admin Country: US Admin Phone: +1.6512971111 Admin Phone Ext: Admin Fax: +1.6512975368 Admin Fax Ext: Admin Email: nic<%>nic.state.mn.us Admin Application Purpose: P5 Admin Nexus Category: C21 Registry Tech ID: C7705028-US Tech Name: Network Operations Center Tech Organization: State of Minnesota Tech Street: Office of Enterprise Technology Tech Street: 500 Centennial Office Building Tech Street: 658 Cedar Street Tech City: St. Paul Tech State/Province: MN Tech Postal Code: 55155 Tech Country: US Tech Phone: +1.6512971111 Tech Phone Ext: Tech Fax: +1.6512975368 Tech Fax Ext: Tech Email: nic<%>nic.state.mn.us Tech Application Purpose: P5 Tech Nexus Category: C21 Registry Domain Manager ID: C7704880-US Domain Manager Name: Network Operations Center Domain Manager Organization: State of Minnesota Domain Manager Street: Office of Enterprise Technology Domain Manager Street: 500 Centennial Office Building Domain Manager Street: 658 Cedar Street Domain Manager City: St. Paul Domain Manager State/Province: MN Domain Manager Postal Code: 55155 Domain Manager Country: US Domain Manager Phone: +1.6512971111 Domain Manager Phone Ext: Domain Manager Fax: +1.6512975368 Domain Manager Fax Ext: Domain Manager Email: nic<%>nic.state.mn.us Domain Manager Application Purpose: P5 Domain Manager Nexus Category: C21 Name Server: ns3.state.mn.us Name Server: ns2.state.mn.us Name Server: ns1.state.mn.us DNSSEC: signedDelegation URL of the ICANN Whois Inaccuracy Complaint Form: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann… >>> Last update of WHOIS database: 2021-02-07T14:25:40Z

Feb. 7, 2021

Re: state.mn.us expired yesterday?

by Mike Johnston

Which reminds me of the Minnesota Legislature's use of the .mn TLD, which is for Mongolia. For example, their email addresses are listed as name(a)house.mn. See https://www.house.leg.state.mn.us/members/list for examples. I notice the Wikipedia article for .mn also mentions this (https://en.wikipedia.org/wiki/.mn) -Mike Johnston

Feb. 7, 2021

state.mn.us expired yesterday?

by Frank Bulk

It appears that state.mn.us expired yesterday? It's possible with such kind of TLD that that doesn't matter? Frank Bulk Registry WHOIS Server : whois.nic.us Domain Name: state.mn.us Registry Domain ID: D3624286-US Registrar WHOIS Server: Registrar URL: http://www.whois.us Updated Date: 2021-01-12T14:03:55Z Creation Date: 2003-02-06T20:25:14Z Registry Expiry Date: 2021-02-06T20:25:14Z Registrar: State of Minnesota Registrar IANA ID: Registrar Abuse Contact Email: Registrar Abuse Contact Phone: Domain Status: ok https://icann.org/epp#ok Domain Status: autoRenewPeriod https://icann.org/epp#autoRenewPeriod Registry Registrant ID: C7705028-US Registrant Name: Network Operations Center Registrant Organization: State of Minnesota Registrant Street: Office of Enterprise Technology Registrant Street: 500 Centennial Office Building Registrant Street: 658 Cedar Street Registrant City: St. Paul Registrant State/Province: MN Registrant Postal Code: 55155 Registrant Country: US Registrant Phone: +1.6512971111 Registrant Phone Ext: Registrant Fax: +1.6512975368 Registrant Fax Ext: Registrant Email: nic<%>nic.state.mn.us Registrant Application Purpose: P5 Registrant Nexus Category: C21 Registry Admin ID: C7705028-US Admin Name: Network Operations Center Admin Organization: State of Minnesota Admin Street: Office of Enterprise Technology Admin Street: 500 Centennial Office Building Admin Street: 658 Cedar Street Admin City: St. Paul Admin State/Province: MN Admin Postal Code: 55155 Admin Country: US Admin Phone: +1.6512971111 Admin Phone Ext: Admin Fax: +1.6512975368 Admin Fax Ext: Admin Email: nic<%>nic.state.mn.us Admin Application Purpose: P5 Admin Nexus Category: C21 Registry Tech ID: C7705028-US Tech Name: Network Operations Center Tech Organization: State of Minnesota Tech Street: Office of Enterprise Technology Tech Street: 500 Centennial Office Building Tech Street: 658 Cedar Street Tech City: St. Paul Tech State/Province: MN Tech Postal Code: 55155 Tech Country: US Tech Phone: +1.6512971111 Tech Phone Ext: Tech Fax: +1.6512975368 Tech Fax Ext: Tech Email: nic<%>nic.state.mn.us Tech Application Purpose: P5 Tech Nexus Category: C21 Registry Domain Manager ID: C7704880-US Domain Manager Name: Network Operations Center Domain Manager Organization: State of Minnesota Domain Manager Street: Office of Enterprise Technology Domain Manager Street: 500 Centennial Office Building Domain Manager Street: 658 Cedar Street Domain Manager City: St. Paul Domain Manager State/Province: MN Domain Manager Postal Code: 55155 Domain Manager Country: US Domain Manager Phone: +1.6512971111 Domain Manager Phone Ext: Domain Manager Fax: +1.6512975368 Domain Manager Fax Ext: Domain Manager Email: nic<%>nic.state.mn.us Domain Manager Application Purpose: P5 Domain Manager Nexus Category: C21 Name Server: ns3.state.mn.us Name Server: ns2.state.mn.us Name Server: ns1.state.mn.us DNSSEC: signedDelegation URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2021-02-07T14:25:40Z

Feb. 7, 2021

FW: [outages] [EXT]: CCI Southern Minnesota inbound connections from other providers failing

by Frank Bulk

FYI From: Outages <outages-bounces(a)outages.org> On Behalf Of Harris Kleyman via Outages Sent: Thursday, February 4, 2021 2:18 PM To: Nathan Engelhardt <NEngelhardt(a)yourcts.com> Cc: outages(a)outages.org Subject: Re: [outages] [EXT]: CCI Southern Minnesota inbound connections from other providers failing We are also seeing impacted clients. Harris Kleyman Manager of Data Centers & Facilities and NOC Supervisor ---- Atomic Data® // Safe. Simple. Smart.® 250 Marquette Avenue Minneapolis, MN 55401 Main // 612.466.2000 Direct // 612.466.2031 On Feb 4, 2021, at 2:15 PM, Nathan Engelhardt via Outages <outages(a)outages.org<mailto:outages@outages.org>> wrote: Outbound connections succeed, and inbound connections from other CCI sites succeed. Inbound connections from other providers fail. Charter/Spectrum to CCI: Tracing route to redacted [209.240.redacted] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms redacted.com [10.0.0.1] 2 * * * Request timed out. 3 17 ms 12 ms 10 ms 096-034-026-152.biz.spectrum.com [96.34.26.152] 4 14 ms 17 ms 13 ms cts01rhnlwi-tge-3-0-0.rhnl.wi.charter.com [96.34.16.147] 5 19 ms 15 ms 15 ms bbr02slidla-tge-0-1-0-6.slid.la.charter.com [96.34.1.188] 6 33 ms 21 ms 26 ms prr01mplsmn-bue-1.mpls.mn.charter.com [96.34.3.31] 7 25 ms 29 ms 21 ms AS12042.micemn.net [206.108.255.18] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. _______________________________________________ Outages mailing list Outages(a)outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages

Feb. 4, 2021

Traffic from Minneapolis to Seattle

by Jeremy Lumby

If anyone has large amounts of traffic that they are primarily moving from Minneapolis to Seattle please reach out to me off list. 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. 3, 2021

SFN 20G LAG Upgrade

by Jay Hanke

Please allocate Eth14 on the SFN Remote Switch to South Front Networks Eth14 and Eth2 will be LAGed to create a 20G port channel. The new port channel interface will be Po1 on the remote. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Feb. 2, 2021

US Internet Maintenance - February 22/23

by Justin Krejci

US Internet (AS10242) will be performing some network maintenance (primarily router reboots for updates) that will cause our IX connection and all router BGP sessions to drop. We intend to shift traffic away beforehand to be as graceful as possible. The event should be between FROM: Monday, February 22th at 11pm (CST) TO: Tuesday, February 23th at 6am (CST) We've reserved the following day (same times) as a backup date as well. FROM: Tuesday, February 23th at 11pm (CST) TO: Wednesday, February 24th at 6am (CST) Justin Krejci Network Engineer 952.253.3200 12450 Wayzata Blvd. Suite 320 | Minnetonka, MN 55305

Jan. 28, 2021

Re: eBGP- Google AS15169 v4+v6 peers

by Nick Twite

Thanks for the feedback I appreciate it. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Thursday, January 28, 2021 3:05 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] eBGP- Google AS15169 v4+v6 peers EXTERNAL: This email originated from a sender outside AcenTek. Do not click links or open attachments unless you recognize the sender and know the content is safe. Their link went down on their MICE port. It came back about 50 minutes ago. 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<mailto:jlumby@mnvoip.com> From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Timothy Peiffer Sent: Thursday, January 28, 2021 3:00 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] eBGP- Google AS15169 v4+v6 peers Northernlights GigaPOP had the same - a 20 minute outage for the peer. On Thu, Jan 28, 2021 at 2:55 PM Nick Twite <ntwite(a)acentek.net<mailto:ntwite@acentek.net>> wrote: Good afternoon, I am reaching out because we had a our Google peerings drop this afternoon approximately 1:45pm to 2:10 CST. They have since re-established and routes are again being shared. Just looking if anyone else experienced the same or has any details to share I would appreciate it. RP/0/RSP0/CPU0:Jan 28 13:43:59.242 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 1/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 13:44:11.705 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 2/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 14:10:39.427 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Up (VRF: default; AFI/SAFI: 1/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 14:10:48.019 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Up (VRF: default; AFI/SAFI: 2/1) (AS: 15169) Thanks Nick Twite Network Operations Specialist [cid:image001.png@01D6F58B.87E43EB0] 507-429-0135 Work Cell 507-896-6229 Desk ntwite(a)AcenTek.net<mailto:ntwite@AcenTek.net> www.AcenTek.net<http://www.AcenTek.net> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota ________________________________ 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

Jan. 28, 2021

Re: eBGP- Google AS15169 v4+v6 peers

by Jeremy Lumby

Their link went down on their MICE port. It came back about 50 minutes ago. 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 From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Timothy Peiffer Sent: Thursday, January 28, 2021 3:00 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] eBGP- Google AS15169 v4+v6 peers Northernlights GigaPOP had the same - a 20 minute outage for the peer. On Thu, Jan 28, 2021 at 2:55 PM Nick Twite <ntwite(a)acentek.net> wrote: Good afternoon, I am reaching out because we had a our Google peerings drop this afternoon approximately 1:45pm to 2:10 CST. They have since re-established and routes are again being shared. Just looking if anyone else experienced the same or has any details to share I would appreciate it. RP/0/RSP0/CPU0:Jan 28 13:43:59.242 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 1/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 13:44:11.705 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 2/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 14:10:39.427 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Up (VRF: default; AFI/SAFI: 1/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 14:10:48.019 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Up (VRF: default; AFI/SAFI: 2/1) (AS: 15169) Thanks Nick Twite Network Operations Specialist 507-429-0135 Work Cell 507-896-6229 Desk ntwite(a)AcenTek.net www.AcenTek.net To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 28, 2021

Re: eBGP- Google AS15169 v4+v6 peers

by Timothy Peiffer

Northernlights GigaPOP had the same - a 20 minute outage for the peer. On Thu, Jan 28, 2021 at 2:55 PM Nick Twite <ntwite(a)acentek.net> wrote: > Good afternoon, > > > > I am reaching out because we had a our Google peerings drop this afternoon > approximately 1:45pm to 2:10 CST. > > > > They have since re-established and routes are again being shared. > > > > Just looking if anyone else experienced the same or has any details to > share I would appreciate it. > > > > > > RP/0/RSP0/CPU0:Jan 28 13:43:59.242 CST: bgp[1020]: > %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Down - BGP > Notification sent, hold time expired (VRF: default; AFI/SAFI: 1/1) (AS: > 15169) > > RP/0/RSP0/CPU0:Jan 28 13:44:11.705 CST: bgp[1020]: > %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Down - BGP > Notification sent, hold time expired (VRF: default; AFI/SAFI: 2/1) (AS: > 15169) > > RP/0/RSP0/CPU0:Jan 28 14:10:39.427 CST: bgp[1020]: > %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Up (VRF: > default; AFI/SAFI: 1/1) (AS: 15169) > > RP/0/RSP0/CPU0:Jan 28 14:10:48.019 CST: bgp[1020]: > %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Up (VRF: > default; AFI/SAFI: 2/1) (AS: 15169) > > > > Thanks > > *Nick Twite* > > Network Operations Specialist > > 507-429-0135 Work Cell > > 507-896-6229 Desk > > *ntwite(a)AcenTek.net <ntwite(a)AcenTek.net>* > > *www.AcenTek.net* <http://www.AcenTek.net> > > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota

Jan. 28, 2021

eBGP- Google AS15169 v4+v6 peers

by Nick Twite

Good afternoon, I am reaching out because we had a our Google peerings drop this afternoon approximately 1:45pm to 2:10 CST. They have since re-established and routes are again being shared. Just looking if anyone else experienced the same or has any details to share I would appreciate it. RP/0/RSP0/CPU0:Jan 28 13:43:59.242 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 1/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 13:44:11.705 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 2/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 14:10:39.427 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 206.108.255.141 Up (VRF: default; AFI/SAFI: 1/1) (AS: 15169) RP/0/RSP0/CPU0:Jan 28 14:10:48.019 CST: bgp[1020]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor 2001:504:27::3b41:0:1 Up (VRF: default; AFI/SAFI: 2/1) (AS: 15169) Thanks Nick Twite Network Operations Specialist [cid:image001.png@01D6F584.3D31CB50] 507-429-0135 Work Cell 507-896-6229 Desk ntwite(a)AcenTek.net<mailto:ntwite@AcenTek.net> www.AcenTek.net

Jan. 28, 2021

Router12 MICE Port Move

by Jay Hanke

Router12 has moved to port Ethernet13 on the SFN remote. All IP address information remains the same. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 27, 2021

CS Tech Upgrade 1x10G to 2x10G

by Jay Hanke

CS Tech has completed an upgrade to 2x10G LAG on the SFN Albert Lea Remote Port Channel 3 members -Ethernet7 -Ethernet11 All IP information remains the same. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 19, 2021

Fibernet Port Augment

by Jay Hanke

Please add port Ethernet24 to the existing Fibernet LAG. Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 15, 2021

Re: Please welcome Key Cooperative to MICE!

by Doug McIntyre

On Tue, Jan 12, 2021 at 05:52:29PM -0600, Jay Hanke wrote: >Name: Key Cooperative >Port: MN VoIP 10G Ethernet25 >ASN: 40350 >IPv4: 206.108.255.172/24 >IPv6: 2001:504:27::9d9e:0:1/64 >Peering Contact: dl-peering(a)keycoop.com >Route Servers- YES >BFD: No They've been added to the RR's. Welcome!

Jan. 13, 2021

Please welcome Key Cooperative to MICE!

by Jay Hanke

Name: Key Cooperative Port: MN VoIP 10G Ethernet25 ASN: 40350 IPv4: 206.108.255.172/24 IPv6: 2001:504:27::9d9e:0:1/64 Peering Contact: dl-peering(a)keycoop.com Route Servers- YES BFD: No Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 12, 2021

Google MICE Issues

by Jay Hanke

Google is currently having issues with their circuit to MICE from Chicago and has disabled traffic during troubleshooting. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 12, 2021

Iowa Fiber Cut

by Jay Hanke

There is a third party fiber cut in Cedar Rapids, IA affecting several members MICE connections. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 11, 2021

Re: Google Ports to MICE

by Mike Horwath

On Mon, Jan 11, 2021 at 07:59:14AM -0800, Dave Schwartz wrote: > Hello MICE Members Hello! Thanks for the update! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Jan. 11, 2021

Google Ports to MICE

by Dave Schwartz

Hello MICE Members I hope this message finds you well. We have heard from a number of MICE members about congestion on Google's port to MICE so I wanted to provide a brief update to our peers on what our plans are. We are aware of the congestion on our current 100G port to MICE and started planning for a 2nd 100G port back in Q3 of 2020. For those of you not aware, the Google router that is connected to MICE is located in Chicago and we use a third party vendor to reach the MICE switch. We have been experiencing long delays with our vendor for our 2nd 100G wave and currently plan to have the 2nd 100G up at MICE in early February. This 2nd 100G link will be on a diverse Google router with a separate IP and plan to peer with the route server on this new link. While our port is congested you may see traffic inbound to your network on indirect paths. While we attempt to deliver all traffic directly, we can't offer any guarantee on where traffic will come from during congestion. If you happen to experience quality problems with any Google service over MICE during this congestion please do report these product specific issues to noc(a)google.com so we can investigate. Our CDN is normally able to handle congestion so we would like to be aware if any members are experiencing any degradation of Google services. Many Thanks, Dave -- Dave Schwartz Customer Engineering Manager Network Specialist Team Google Cloud Platform daveschwartz(a)google.com +1-424-625-9129

Jan. 11, 2021

FW: [outages] High packet loss on Spectrum in Southern Minnesota

by Frank Bulk

Cross-posting as this may interest some in this group. Frank From: Outages <outages-bounces(a)outages.org> On Behalf Of Abhi Devireddy via Outages Sent: Wednesday, January 6, 2021 3:46 PM To: Outages(a)outages.org; Goli, Matthew W. <Matthew.Goli(a)waupacafoundry.com> Subject: Re: [outages] High packet loss on Spectrum in Southern Minnesota Update: It's a backbone fiber between MN and WI that was impacted in Mazomanie, WI and Duluth, MN. Teams were dispatched and one's arrived on site. Still no confirmed ETR. Abhi ________________________________ From: Outages <outages-bounces(a)outages.org<mailto:outages-bounces@outages.org>> on behalf of Goli, Matthew W. via Outages <outages(a)outages.org<mailto:outages@outages.org>> Sent: Wednesday, January 6, 2021 2:36 PM To: Outages(a)outages.org<mailto:Outages@outages.org> <Outages(a)outages.org<mailto:Outages@outages.org>> Subject: Re: [outages] High packet loss on Spectrum in Southern Minnesota Hello, We're in central Wisconsin and we're impacted by this outage. Just received communication from Spectrum stating there is a confirmed fiber cut. Fiber recovery teams have been engaged but there is no ETR at this time. From: Outages <outages-bounces(a)outages.org<mailto:outages-bounces@outages.org>> On Behalf Of John Knutson via Outages Sent: Wednesday, January 6, 2021 2:29 PM To: Abhi Devireddy <abhi(a)devireddy.com<mailto:abhi@devireddy.com>> Cc: outages(a)outages.org<mailto:outages@outages.org> Subject: Re: [outages] High packet loss on Spectrum in Southern Minnesota CAUTION!! This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. I've got a coworker in Elk River, MN who has no connectivity. I am on Spectrum in Dayton, MN about 10 miles south of that and mine has been working fine so far. Both are residential cable connections. On Wed, Jan 6, 2021 at 1:36 PM Abhi Devireddy via Outages <outages(a)outages.org<mailto:outages@outages.org>> wrote: No v4/v6 connectivity in Northern MN. Looks like our peering traffic with them dropped to zero as well. Abhi ________________________________ From: Outages <outages-bounces(a)outages.org<mailto:outages-bounces@outages.org>> on behalf of Nathan Engelhardt via Outages <outages(a)outages.org<mailto:outages@outages.org>> Sent: Wednesday, January 6, 2021 12:56 PM To: outages(a)outages.org<mailto:outages@outages.org> <outages(a)outages.org<mailto:outages@outages.org>> Subject: Re: [outages] High packet loss on Spectrum in Southern Minnesota Update/additional info: Losses are only occurring over IPv4. IPv6 is performing normally, for what it's worth. From: Outages <outages-bounces(a)outages.org<mailto:outages-bounces@outages.org>> On Behalf Of Nathan Engelhardt via Outages Sent: Wednesday, January 6, 2021 12:45 PM To: outages(a)outages.org<mailto:outages@outages.org> Subject: [outages] High packet loss on Spectrum in Southern Minnesota A few of my coworkers and I, all WFH and on Spectrum, are seeing high packet loss. South-Central Minnesota. _______________________________________________ Outages mailing list Outages(a)outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages [puck.nether.net]<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…> CONFIDENTIALITY AND LEGAL NOTICE This electronic mail transmission is confidential, may be privileged and should be read or retained only by the intended recipient. If the reader of this transmission is not the intended recipient, you are hereby notified that any distribution or copying hereof is strictly prohibited. If you have received this transmission in error, please immediately notify the sender and remove it from your system. E-mail is not necessarily a secure communication method, therefore the sender shall not be responsible for any changes that occur during its transfer. All e-mails are scanned for viruses, however, files attached to this e-mail may contain viruses that could harm the systems of the recipient. Any opinions expressed in this email must be confirmed in writing and signed by the sender to have legal validity.

Jan. 6, 2021

Re: config assistance?

by James Urwiller

Thanks, ill give that a whirl! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Wednesday, December 30, 2020 14:23 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? James, Arista is very similar to Cisco where you need to issue no bgp enforce-first-as or a slight variation of it (if I do not have my Arista syntax exactly correct). Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Wednesday, December 30, 2020 2:14 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? Greetings all! I just realized that my peer sessions with the route servers are not receiving any prefix’s since the change. My direct peers through the exchange are working as intended. Is there another filter someplace that needs updated? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Tuesday, December 29, 2020 12:16 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? James, This is because Zayo is a non-compliant extension switch operator. There have been several things approved by the MICE board that Zayo has become non-responsive on implementing. As a result we needed to put a MAC filter in place on Zayo’s link to the MICE core. You can let me know your new MAC address, and I can update the filter. Also there are some other things related to route server security coming up shortly that will become an issue on the Zayo extension switch. If you have a good contact there, we would love to have them work with us. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Tuesday, December 29, 2020 12:04 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] config assistance? Greetings all, Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. Any ideas Arista/MICE guru’s? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com ________________________________________ 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

Dec. 30, 2020

Re: config assistance?

by Jeremy Lumby

James, Arista is very similar to Cisco where you need to issue no bgp enforce-first-as or a slight variation of it (if I do not have my Arista syntax exactly correct). Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Wednesday, December 30, 2020 2:14 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? Greetings all! I just realized that my peer sessions with the route servers are not receiving any prefix’s since the change. My direct peers through the exchange are working as intended. Is there another filter someplace that needs updated? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Tuesday, December 29, 2020 12:16 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? James, This is because Zayo is a non-compliant extension switch operator. There have been several things approved by the MICE board that Zayo has become non-responsive on implementing. As a result we needed to put a MAC filter in place on Zayo’s link to the MICE core. You can let me know your new MAC address, and I can update the filter. Also there are some other things related to route server security coming up shortly that will become an issue on the Zayo extension switch. If you have a good contact there, we would love to have them work with us. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Tuesday, December 29, 2020 12:04 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] config assistance? Greetings all, Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. Any ideas Arista/MICE guru’s? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com ________________________________________ 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

Dec. 30, 2020

Re: config assistance?

by James Urwiller

Greetings all! I just realized that my peer sessions with the route servers are not receiving any prefix’s since the change. My direct peers through the exchange are working as intended. Is there another filter someplace that needs updated? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Jeremy Lumby *Sent:* Tuesday, December 29, 2020 12:16 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] config assistance? James, This is because Zayo is a non-compliant extension switch operator. There have been several things approved by the MICE board that Zayo has become non-responsive on implementing. As a result we needed to put a MAC filter in place on Zayo’s link to the MICE core. You can let me know your new MAC address, and I can update the filter. Also there are some other things related to route server security coming up shortly that will become an issue on the Zayo extension switch. If you have a good contact there, we would love to have them work with us. Jeremy *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET <MICE-DISCUSS(a)LISTS.IPHOUSE.NET>] *On Behalf Of *James Urwiller *Sent:* Tuesday, December 29, 2020 12:04 PM *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* [MICE-DISCUSS] config assistance? Greetings all, Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. Any ideas Arista/MICE guru’s? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com ------------------------------ 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

Dec. 30, 2020

Re: config assistance?

by James Urwiller

Thanks all for the help! We are back up and runnin. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Tuesday, December 29, 2020 14:09 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? On 12/29/20 1:44 PM, Andrew Hoyos wrote: > May be good to add to these pages as a note that explicit MAC address > filtering is in place for the Zayo switch: Done. Thanks for the suggestion! -- Richard

Dec. 29, 2020

Re: config assistance?

by Richard Laager

On 12/29/20 1:44 PM, Andrew Hoyos wrote: > May be good to add to these pages as a note that explicit MAC address > filtering is in place for the Zayo switch: Done. Thanks for the suggestion! -- Richard

Dec. 29, 2020

Re: config assistance?

by Andrew Hoyos

May be good to add to these pages as a note that explicit MAC address filtering is in place for the Zayo switch: http://micemn.net/technical.html <http://micemn.net/technical.html> and http://micemn.net/participants.html#zayo <http://micemn.net/participants.html#zayo> > On Dec 29, 2020, at 12:16 PM, Jeremy Lumby <jlumby(a)MNVOIP.COM> wrote: > > James, > > This is because Zayo is a non-compliant extension switch operator. There have been several things approved by the MICE board that Zayo has become non-responsive on implementing. As a result we needed to put a MAC filter in place on Zayo’s link to the MICE core. You can let me know your new MAC address, and I can update the filter. Also there are some other things related to route server security coming up shortly that will become an issue on the Zayo extension switch. If you have a good contact there, we would love to have them work with us. > > Jeremy > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>] On Behalf Of James Urwiller > Sent: Tuesday, December 29, 2020 12:04 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > Subject: [MICE-DISCUSS] config assistance? > > Greetings all, > Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. > > Any ideas Arista/MICE guru’s? > > James Urwiller > Network Architect > Stealth Broadband > james.urwiller(a)stealthbroadband.com <mailto:james.urwiller@stealthbroadband.com> > <image001.jpg> > > > 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> > 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>

Dec. 29, 2020

Re: config assistance?

by Jeremy Lumby

James, The MAC has been added. I can ping your interface. I will use your ticket to see if we can get some traction. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Tuesday, December 29, 2020 12:25 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? Jeremy, Thanks for the info! The MAC of my interface is now 98:5d:82:b7:07:87. I have a guy @ Zayo that seems to know what he is doing on my ticket, but admitted that this was all new to him and took all night for them to be able to access their MICE remote switch (they actually had to dispatch someone to belle plaine to bounce my port, but they now have remote access working) Joseph is the guys name, and my Zayo Ticket is 0004680143 if you need to reference that to get the right Joseph 😊 James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Tuesday, December 29, 2020 12:16 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] config assistance? James, This is because Zayo is a non-compliant extension switch operator. There have been several things approved by the MICE board that Zayo has become non-responsive on implementing. As a result we needed to put a MAC filter in place on Zayo’s link to the MICE core. You can let me know your new MAC address, and I can update the filter. Also there are some other things related to route server security coming up shortly that will become an issue on the Zayo extension switch. If you have a good contact there, we would love to have them work with us. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Tuesday, December 29, 2020 12:04 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] config assistance? Greetings all, Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. Any ideas Arista/MICE guru’s? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com 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

Dec. 29, 2020

Re: config assistance?

by James Urwiller

Jeremy, Thanks for the info! The MAC of my interface is now 98:5d:82:b7:07:87. I have a guy @ Zayo that seems to know what he is doing on my ticket, but admitted that this was all new to him and took all night for them to be able to access their MICE remote switch (they actually had to dispatch someone to belle plaine to bounce my port, but they now have remote access working) Joseph is the guys name, and my Zayo Ticket is 0004680143 if you need to reference that to get the right Joseph 😊 James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Jeremy Lumby *Sent:* Tuesday, December 29, 2020 12:16 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] config assistance? James, This is because Zayo is a non-compliant extension switch operator. There have been several things approved by the MICE board that Zayo has become non-responsive on implementing. As a result we needed to put a MAC filter in place on Zayo’s link to the MICE core. You can let me know your new MAC address, and I can update the filter. Also there are some other things related to route server security coming up shortly that will become an issue on the Zayo extension switch. If you have a good contact there, we would love to have them work with us. Jeremy *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET <MICE-DISCUSS(a)LISTS.IPHOUSE.NET>] *On Behalf Of *James Urwiller *Sent:* Tuesday, December 29, 2020 12:04 PM *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* [MICE-DISCUSS] config assistance? Greetings all, Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. Any ideas Arista/MICE guru’s? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com ------------------------------ 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

Dec. 29, 2020

Re: config assistance?

by Jeremy Lumby

James, This is because Zayo is a non-compliant extension switch operator. There have been several things approved by the MICE board that Zayo has become non-responsive on implementing. As a result we needed to put a MAC filter in place on Zayo’s link to the MICE core. You can let me know your new MAC address, and I can update the filter. Also there are some other things related to route server security coming up shortly that will become an issue on the Zayo extension switch. If you have a good contact there, we would love to have them work with us. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Tuesday, December 29, 2020 12:04 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] config assistance? Greetings all, Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. Any ideas Arista/MICE guru’s? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 29, 2020

config assistance?

by James Urwiller

Greetings all, Last night I cutover to a new Arista for BGP services facing MICE and a few other peers. All my other peers are up and functioning properly, but I cannot reach any of the MICE peers. Since I am connected to the Zayo remote switch in Belle Plaine, I had Zayo bounce my port thinking it was a mac-limit issue. Even before they did this, I can see MICE peers in ARP and in the MAC-Table, but I cant ping any of them, like the traffic is filtered in one direction. Zayo’s port bouncing had no effect. Any ideas Arista/MICE guru’s? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com

Dec. 29, 2020

Global Net (AS395466) - Upcoming Maintenance 12/28/20

by Global Net NOC

MICEMN Members - We have a maintenance window scheduled for Monday, December 28th to replace our MICE facing router. BGP sessions will be gracefully shutdown prior to the work. In the event of a failed swap we will be reverting to our current hardware. Start: 12/28/20 1115 GMT End: 12/28/20 1300 GMT ASN: 395466 Speed: 10G IPv4: 206.108.255.97 IPv6: 2001:504:27:0:6:08ca::1 Thanks, Global Net NOC noc(a)theglobal.net Global Net Peering peering(a)theglobal.net

Dec. 22, 2020

SFN MICE Remote Switch work

by Jay Hanke

We will be upgrading the backhaul of the SFN remote switch to 100G at Midnight. There may be some brief packet loss when we disable the existing LAG group. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 5, 2020

OmniTech (AS54821) MICE Port Move

by Jay Hanke

OmniTech has been moved from the Zayo Remote switch to SFN Remote switch port Ethernet10. All IP/ASN information remains the same. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 4, 2020

Re: AS34962 AS Change

by Austin Gillmann

Hi Richard, We are actually gonna be changing AS'es completely from 34962 to 58110. 34962 will no longer be at this location and were moving all our clients over to the new AS (Essentially turning from Epik to IP Volume clients. On Wed, Dec 2, 2020 at 1:38 PM Richard Laager <rlaager(a)wiktel.com> wrote: > On 12/2/20 1:33 PM, Austin Gillmann wrote: > > We recently decided to split our hosting into a subsidiary known as IP > > Volume to better market our hosting services. > > > > All sessions including the IX route server have been updated to the new > > AS and we are awaiting your connection. If you have any questions feel > > free to contact me. > > I'm confused. AS34962 is currently listed on the participants page [1] > as Epik. Are you saying you are adding a second AS (for "IP Volume") on > the same port? If so, what is that AS number? You will presumably need a > second IP allocated for the new AS, and the route server configured > accordingly. > > [1] http://micemn.net/participants.html > > -- > Richard >

Dec. 2, 2020

Re: AS34962 AS Change

by Richard Laager

On 12/2/20 1:33 PM, Austin Gillmann wrote: > We recently decided to split our hosting into a subsidiary known as IP > Volume to better market our hosting services. > > All sessions including the IX route server have been updated to the new > AS and we are awaiting your connection. If you have any questions feel > free to contact me. I'm confused. AS34962 is currently listed on the participants page [1] as Epik. Are you saying you are adding a second AS (for "IP Volume") on the same port? If so, what is that AS number? You will presumably need a second IP allocated for the new AS, and the route server configured accordingly. [1] http://micemn.net/participants.html -- Richard

Dec. 2, 2020

AS34962 AS Change

by Austin Gillmann

Hi all, We recently decided to split our hosting into a subsidiary known as IP Volume to better market our hosting services. All sessions including the IX route server have been updated to the new AS and we are awaiting your connection. If you have any questions feel free to contact me. We appreciate your continued support and wish you all the best!

Dec. 2, 2020

RS3 Route server

by Jay Hanke

Connectivity to the MICE test route server (RS3) took a 5 minute hit about 2110 hrs. Connectivity has been restored. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 1, 2020

Re: MICE Blackhole IP Allocation

by Richard Laager

On 11/22/20 8:11 AM, Jay Hanke wrote: > SIX has a /23 for the peering subnet and the blackhole address sits on > the middle .0 which is old school cidr legal. Good point. > The mice 0 is also the network address which could cause issues arping > with some gear. Fair enough. -- Richard

Nov. 22, 2020

Re: MICE Blackhole IP Allocation

by Jay Hanke

> > Why not .0, as SIX does? > SIX has a /23 for the peering subnet and the blackhole address sits on the middle .0 which is old school cidr legal. The mice 0 is also the network address which could cause issues arping with some gear.

Nov. 22, 2020

Re: MICE Blackhole IP Allocation

by Richard Laager

On 11/21/20 2:20 PM, Jay Hanke wrote: > The following IP addresses have been allocated for the upcoming > blackhole project on the MICE Internet Exchange. > > MICE-BH > IPv4: 206.108.255.228/24 Why not .0, as SIX does? > IPv6: 2001:504:27::6666:dead:beef/64 > > We will be using 66:66:de:ad:be:ef as the mac-address and inject the > arp entry from a virtual machine on the SFN-Remote until a permanent > solution on the main switch is worked out. A VM on the same setup as the route server is a reasonable permanent plan (and I believe was the plan). -- Richard

Nov. 22, 2020

MICE Blackhole IP Allocation

by Jay Hanke

The following IP addresses have been allocated for the upcoming blackhole project on the MICE Internet Exchange. MICE-BH IPv4: 206.108.255.228/24 IPv6: 2001:504:27::6666:dead:beef/64 We will be using 66:66:de:ad:be:ef as the mac-address and inject the arp entry from a virtual machine on the SFN-Remote until a permanent solution on the main switch is worked out. Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 21, 2020

Re: Update PTR

by Frank Bulk

Great, thank you. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre Sent: Wednesday, November 18, 2020 5:00 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Update PTR On Wed, Nov 18, 2020 at 10:02:16PM +0000, Frank Bulk wrote: >Premier is no longer a part of MICE. > >Can the PTR for 206.108.255.67 be updated so that it doesn't list AS53347.micemn.net? Okay, that is done. I also removed the IPv6 reverse that was setup as well.

Nov. 20, 2020

Re: Update PTR

by Doug McIntyre

On Wed, Nov 18, 2020 at 10:02:16PM +0000, Frank Bulk wrote: >Premier is no longer a part of MICE. > >Can the PTR for 206.108.255.67 be updated so that it doesn't list AS53347.micemn.net? Okay, that is done. I also removed the IPv6 reverse that was setup as well.

Nov. 18, 2020

Update PTR

by Frank Bulk

Premier is no longer a part of MICE. Can the PTR for 206.108.255.67 be updated so that it doesn't list AS53347.micemn.net? Thanks, Frank

Nov. 18, 2020

Re: PeeringDB Audit Emails

by Jay Hanke

Yes, we have been through this process without progress. :( On Wed, Nov 18, 2020 at 2:56 PM James Urwiller <james.urwiller(a)turnkey-telecom.com> wrote: > > After talking to a few people at Zayo through normal support channels. They > said that an email has to be sent to peering(a)zayo.com to get this the > visibility it needs. Sorry I couldn’t get any further with this! > > James Urwiller > Network Architect > Stealth Broadband > james.urwiller(a)stealthbroadband.com > > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke > Sent: Wednesday, November 18, 2020 11:52 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] PeeringDB Audit Emails > > I've gotten several emails from MICE members about IX-F export issues on > PeeringDB. > > MICE provides a list of port/peering information to PeeringDB in JSON format > and they started auditing against what users have entered into the site. The > export is generated from our IXP Manager platform we deployed a couple > months ago. > > The most common mismatch is the user not having the IPv6 address loaded in > PeeringDB. MICE allocates an IPv6 address with every IPv4 allocation. > [insert ipv6 pitch here] > > Members on the Zayo Remote switch in Belle Plaine are currently not > currently included in the export. There is an issue with loading the ports > into IXP manager and we need an admin at Zayo to make a couple of > routing/snmp changes. All of the other switches were completed and loaded > several months ago. > > If someone has a good contact at Zayo for this please let me know. > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 18, 2020

Re: PeeringDB Audit Emails

by James Urwiller

After talking to a few people at Zayo through normal support channels. They said that an email has to be sent to peering(a)zayo.com to get this the visibility it needs. Sorry I couldn’t get any further with this! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Wednesday, November 18, 2020 11:52 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] PeeringDB Audit Emails I've gotten several emails from MICE members about IX-F export issues on PeeringDB. MICE provides a list of port/peering information to PeeringDB in JSON format and they started auditing against what users have entered into the site. The export is generated from our IXP Manager platform we deployed a couple months ago. The most common mismatch is the user not having the IPv6 address loaded in PeeringDB. MICE allocates an IPv6 address with every IPv4 allocation. [insert ipv6 pitch here] Members on the Zayo Remote switch in Belle Plaine are currently not currently included in the export. There is an issue with loading the ports into IXP manager and we need an admin at Zayo to make a couple of routing/snmp changes. All of the other switches were completed and loaded several months ago. If someone has a good contact at Zayo for this please let me know. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 18, 2020

Re: PeeringDB Audit Emails

by James Urwiller

I have zero good contacts there.. I will just create a service ticket and see where it gets me James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Wednesday, November 18, 2020 11:52 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] PeeringDB Audit Emails I've gotten several emails from MICE members about IX-F export issues on PeeringDB. MICE provides a list of port/peering information to PeeringDB in JSON format and they started auditing against what users have entered into the site. The export is generated from our IXP Manager platform we deployed a couple months ago. The most common mismatch is the user not having the IPv6 address loaded in PeeringDB. MICE allocates an IPv6 address with every IPv4 allocation. [insert ipv6 pitch here] Members on the Zayo Remote switch in Belle Plaine are currently not currently included in the export. There is an issue with loading the ports into IXP manager and we need an admin at Zayo to make a couple of routing/snmp changes. All of the other switches were completed and loaded several months ago. If someone has a good contact at Zayo for this please let me know. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 18, 2020