- mice-discuss - lists.micemn.net

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

PeeringDB Audit Emails

by Jay Hanke

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

IPv6 BGP Peering to Netflix bouncing 60+ days

by Jesse Reed

All: We have been tracking our IPv6 peering via our MICE path to Netflix and noticed it bouncing consistently since at least September (probably longer). All other peerings on this path (both v4 and v6) have been stable and are not experiencing these drops. Is anyone else in the group experiencing similar drops to their IPv6 only peerings w/Netflix? The peer that we see this occurring w/is: 2001:504:27::b5a:0:1 Thanks so much ahead of time, Jesse

Nov. 18, 2020

SFN Remote Switch Backhaul Upgrade

by Jay Hanke

Please allocate Ethernet1/1 on the MN VoIP 100G remote switch for a new SFN remote uplink. When completed the link from the SFN Remote switch will increase from 40G to 100G. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 13, 2020

Re: Nuvera Upgrade to 1x4x10G

by Doug McIntyre

On Thu, Nov 12, 2020 at 12:00:18PM -0600, Jay Hanke wrote: >Please allocate and add the following ports to the existing Nuvera LAG group. > >Ethernet4/14 >Ethernet5/14 > >The new group will be 4x10G I added the two ether interfaces to the existing LAG on PC33. This is complete and waiting for their circuits to be installed.

Nov. 12, 2020

Nuvera Upgrade to 1x4x10G

by Jay Hanke

Please allocate and add the following ports to the existing Nuvera LAG group. Ethernet4/14 Ethernet5/14 The new group will be 4x10G -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 12, 2020

MN VoIP Remote Switch Upgrade

by Jay Hanke

Port Ethernet6/6/1 on the main switch has been allocated to MN VoIP. The port will be in a LAG configuration with their existing 100G port for a total of 2x100G IP addresses will remain the same. Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Oct. 27, 2020

Fwd: [arin-announce] Vote Now in the 2020 ARIN Elections

by David Farmer

It's that time of year, again. Voting has opened for the ARIN election and will remain open to 5:00 PM ET, Friday, October 30th. Please take the time to vote if you are a designated voting contact for ARIN for your organization. Thank you, and Please VOTE!! ---------- Forwarded message --------- From: ARIN <info(a)arin.net> Date: Fri, Oct 23, 2020 at 2:00 PM Subject: [arin-announce] Vote Now in the 2020 ARIN Elections To: arin-announce(a)arin.net <arin-announce(a)arin.net> Eligible Voting Contacts from General Members in Good Standing may now cast online ballots in the 2020 ARIN Elections to fill two seats on the ARIN Board of Trustees and five seats on the ARIN Advisory Council. Ballots may be cast now through 5:00 PM ET, Friday, 30 October. To vote, simply log in to ARIN Online with a user account associated with a voting contact for an eligible Member in Good Standing and look for the “Vote Now” link on your dashboard. Additional instructions are available at https://www.arin.net/voting/ For information about the candidates, there are several options: * You may view video of candidate speeches and review statements of support and candidate questionnaire responses at https://www.bigpulse.com/p60984/ * Read the collected candidate biographies in the ARIN Elections 2020 Voter Guide at https://www.arin.net/participate/oversight/elections/candidate_bios.pdf * Starting Monday, 26 October, you can view the Board and Advisory Council Candidate Forums that took place during the virtual ARIN 46 Members Meeting at https://www.arin.net/elections/ Statements of Support are still open for submissions through 30 October. To view or submit a Statement of Support, please visit the link above. Anyone, regardless of voter status, is eligible to submit a Statement of Support for a candidate. During the week of 26 – 30 October, all eligible Voting Contacts will receive regular email reminders and may receive a personal call from an ARIN representative reminding them to please vote. Those who have already voted should not receive any further reminders. As the voting contact for an eligible member organization, participation in ARIN Elections requires only minutes of your time and is not only a key member responsibility, but is an opportunity to shape the future of ARIN, our community, and the Internet. For questions about voting, or if you encounter an issue with the election system, please contact us immediately at members(a)arin.net. You may also submit a question via ARIN Online and direct it to Meetings/Elections. Thank you for your participation in the 2020 ARIN Elections! Regards, Jason Byrne Senior Customer Success Analyst American Registry for Internet Numbers (ARIN) _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce(a)arin.net) Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-announce Please contact info(a)arin.net if you experience any issues. -- =============================================== 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 ===============================================

Oct. 23, 2020

UG 36 Meeting (1 Hour Reminder)

by Richard Laager

On 9/14/20 3:55 PM, Richard Laager wrote: > The MICE UG 36 meeting will be held Wednesday, October 7, 3:00 pm, > online at: https://meet.google.com/zgg-eeyu-dxz > > The agenda and draft UG 35 minutes are attached. > > If something goes wrong with the Google Meet, we can fall back to the > phone conference: 952-562-5400 passcode MICE (6423). Note that the > phone conference will /not/ connect you to the Google Meet meeting; > this is purely a backup plan. > > *Election* > > At this meeting, we will be holding an election for a board seat. The > board consists of three seats with staggered terms, such that one seat > comes up for re-election each year (at the fall meeting). This year, > Anthony's seat is up for election. > > As in the past, we will close nominations in advance of the meeting so > people have a chance to instruct a proxy appropriately. *Nominations > will be open for two weeks (so until the end of September 28).* > > If we end up with only one person running (like last time), then > voting is a formality. But if we end up with a contested election, we > will need to vote. I don't know of a good way to do secret balloting > by Google Meet, nor am I particularly familiar with separate services > to do the same. Suggestions are welcome if you don't like the > following plan: > > My current plan is to roll call for (public) votes at the meeting to > give people that option, but in practice, I'm guessing people will > want to vote by email for convenience. > > The bylaws state that you send proxies to the Chief Manager (me, > Richard Laager), and electronic means are acceptable. So a simple > email is sufficient: rlaager(a)wiktel.com <mailto:rlaager@wiktel.com> > or, if you prefer, chiefmanager(a)micemn.net > <mailto:chiefmanager@micemn.net> works too. > > If you send me a /vote/ by email (e.g. "We vote for <X>."), I will > treat it as an a proxy appointment, appointing me to vote on your > behalf, but restricted to /only/ the election item and to /only/ vote > for the candidate you expressed. So then at the meeting, I will say > something like, "On behalf of members X, Y, and Z, I cast 1 vote for A > and 2 votes for B." This will provide /some/ anonymization (obviously, > /I/ will know how you voted). > > If you send me a proxy with different instructions (e.g. "We appoint > <Y> to vote for us."), obviously that will be honored as written. > > -- > Richard > -- Richard

Oct. 7, 2020

Re: TDS Peer Down

by Deprez, Rich

I can confirm there was a transport disruption to both 10G's into MICE for us. 1 of the 2 restored shortly after and we're investigating why the second did not restore. Rich Deprez TDS Telecom – IP Network Operations -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Dean Bahls Sent: Saturday, September 26, 2020 5:03 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] TDS Peer Down AT&T had a scheduled maintenance along I94 today.... Yes, during the day on a Saturday. Seems a bit arrogant when they demand maintenance windows during the week IMHO. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Saturday, September 26, 2020 3:11 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] TDS Peer Down It looks like there was a transport hiccup on one of the routes coming into Minneapolis from the NW (several members connections bounced). TDS appears to be coming back online with other peers. If you're bilateral, make sure to hit their peering contact directly with issues. On Sat, Sep 26, 2020 at 3:04 PM Keith Wirch <kwirch(a)atomicdata.com> wrote: > > Lost Peering with TDS @ 14:45. For now we have the neighbor shutdown incase flapping happens. > > > > atomic-router#ping 206.108.255.4 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 206.108.255.4, timeout is 2 seconds: > > ..... > > Success rate is 0 percent (0/5) > > > > > > > Keith Wirch > Infrastructure Engineer > ---- > Atomic Data® // Safe. Simple. Smart.® > 250 Marquette Avenue > Minneapolis, MN 55401 > Main // 612.466.2000 > Direct // 612.466.2106 > > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Sept. 28, 2020

Re: TDS Peer Down

by Dean Bahls

AT&T had a scheduled maintenance along I94 today.... Yes, during the day on a Saturday. Seems a bit arrogant when they demand maintenance windows during the week IMHO. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Saturday, September 26, 2020 3:11 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] TDS Peer Down It looks like there was a transport hiccup on one of the routes coming into Minneapolis from the NW (several members connections bounced). TDS appears to be coming back online with other peers. If you're bilateral, make sure to hit their peering contact directly with issues. On Sat, Sep 26, 2020 at 3:04 PM Keith Wirch <kwirch(a)atomicdata.com> wrote: > > Lost Peering with TDS @ 14:45. For now we have the neighbor shutdown incase flapping happens. > > > > atomic-router#ping 206.108.255.4 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 206.108.255.4, timeout is 2 seconds: > > ..... > > Success rate is 0 percent (0/5) > > > > > > > Keith Wirch > Infrastructure Engineer > ---- > Atomic Data® // Safe. Simple. Smart.® > 250 Marquette Avenue > Minneapolis, MN 55401 > Main // 612.466.2000 > Direct // 612.466.2106 > > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Sept. 26, 2020

Re: TDS Peer Down

by Jay Hanke

It looks like there was a transport hiccup on one of the routes coming into Minneapolis from the NW (several members connections bounced). TDS appears to be coming back online with other peers. If you're bilateral, make sure to hit their peering contact directly with issues. On Sat, Sep 26, 2020 at 3:04 PM Keith Wirch <kwirch(a)atomicdata.com> wrote: > > Lost Peering with TDS @ 14:45. For now we have the neighbor shutdown incase flapping happens. > > > > atomic-router#ping 206.108.255.4 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 206.108.255.4, timeout is 2 seconds: > > ..... > > Success rate is 0 percent (0/5) > > > > > > > Keith Wirch > Infrastructure Engineer > ---- > Atomic Data® // Safe. Simple. Smart.® > 250 Marquette Avenue > Minneapolis, MN 55401 > Main // 612.466.2000 > Direct // 612.466.2106 > > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Sept. 26, 2020

TDS Peer Down

by Keith Wirch

Sept. 26, 2020

Re: MICE port down

by Todd Mueller

Gotcha, thanks. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Monday, September 21, 2020 12:27 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE port down If it happens again, you should be able to disable the port on your side and then re-enable it after a minute and the error state should clear. On Mon, Sep 21, 2020 at 12:24 PM Doug McIntyre <merlyn(a)iphouse.net> wrote: > > On Mon, Sep 21, 2020 at 12:21:35PM -0500, Todd Mueller wrote: > >Could someone please check the MICE port for Velocity Telephone, I > >saw it go down about 15 minutes ago. > > > >I suspect it shut down because there was more than 1 MAC address coming in. > >I noticed the MAC address for a layer 2 interface from one of our > >switches showing up in the corresponding VLAN momentarily for some > >reason, but it is gone now. > > Yes, it was a MAC address security violation. I assume it'll be fine > to post it, so you can find what one is causing you grief. > > Sep 21 12:02:46 core-sw0 PortSec: %PORTSECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address 64:9e:f3:ec:b9:73 on vlan 1 interface Ethernet4/21. > Sep 21 12:02:46 core-sw0 Ebra: %ETH-4-ERRDISABLE: portsec error detected on Ethernet4/21. > Sep 21 12:02:46 core-sw0 Ebra: %LINEPROTO-5-UPDOWN: Line protocol on > Interface Ethernet4/21 (15250 - Velocity Telephone), changed state to > down Sep 21 12:02:46 core-sw0 Stp: %SPANTREE-6-INTERFACE_DEL: > Interface Ethernet4/21 has been removed from instance Vl1 > > I cleared the error from the port. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Sept. 21, 2020

Re: MICE port down

by Todd Mueller

Thanks Doug, I will try to track down what the deal is. -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre Sent: Monday, September 21, 2020 12:25 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE port down On Mon, Sep 21, 2020 at 12:21:35PM -0500, Todd Mueller wrote: >Could someone please check the MICE port for Velocity Telephone, I saw >it go down about 15 minutes ago. > >I suspect it shut down because there was more than 1 MAC address coming in. >I noticed the MAC address for a layer 2 interface from one of our >switches showing up in the corresponding VLAN momentarily for some >reason, but it is gone now. Yes, it was a MAC address security violation. I assume it'll be fine to post it, so you can find what one is causing you grief. Sep 21 12:02:46 core-sw0 PortSec: %PORTSECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address 64:9e:f3:ec:b9:73 on vlan 1 interface Ethernet4/21. Sep 21 12:02:46 core-sw0 Ebra: %ETH-4-ERRDISABLE: portsec error detected on Ethernet4/21. Sep 21 12:02:46 core-sw0 Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet4/21 (15250 - Velocity Telephone), changed state to down Sep 21 12:02:46 core-sw0 Stp: %SPANTREE-6-INTERFACE_DEL: Interface Ethernet4/21 has been removed from instance Vl1 I cleared the error from the port.

Sept. 21, 2020

Re: MICE port down

by Jay Hanke

If it happens again, you should be able to disable the port on your side and then re-enable it after a minute and the error state should clear. On Mon, Sep 21, 2020 at 12:24 PM Doug McIntyre <merlyn(a)iphouse.net> wrote: > > On Mon, Sep 21, 2020 at 12:21:35PM -0500, Todd Mueller wrote: > >Could someone please check the MICE port for Velocity Telephone, I saw it go > >down about 15 minutes ago. > > > >I suspect it shut down because there was more than 1 MAC address coming in. > >I noticed the MAC address for a layer 2 interface from one of our switches > >showing up in the corresponding VLAN momentarily for some reason, but it is > >gone now. > > Yes, it was a MAC address security violation. I assume it'll be fine > to post it, so you can find what one is causing you grief. > > Sep 21 12:02:46 core-sw0 PortSec: %PORTSECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address 64:9e:f3:ec:b9:73 on vlan 1 interface Ethernet4/21. > Sep 21 12:02:46 core-sw0 Ebra: %ETH-4-ERRDISABLE: portsec error detected on Ethernet4/21. > Sep 21 12:02:46 core-sw0 Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet4/21 (15250 - Velocity Telephone), changed state to down > Sep 21 12:02:46 core-sw0 Stp: %SPANTREE-6-INTERFACE_DEL: Interface Ethernet4/21 has been removed from instance Vl1 > > I cleared the error from the port. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Sept. 21, 2020