mice-discuss

Download

By thread

mice-discuss@lists.micemn.net

1 participants
6649 messages

Re: Zayo to Omaha IX down

by Jay Hanke

Is there a master Zayo ticket open for the MICE ports that are down? On Wed, Oct 23, 2019 at 2:50 PM Jay Hanke <jayhanke(a)southfront.io> wrote: > > Looks like several of the Nebraska folks lost their MICE connections as well. > > On Wed, Oct 23, 2019 at 2:41 PM Jeff Dahna <jeff.dahna(a)windommn.com> wrote: > > > > We lost our route to Omaha IX via Zayo around 2:04 PM CST. Got a ticket in with Zayo. Anyone else down to Omaha via Zayo? > > > > Jeff Dahna > > Windomnet > > > > -- > 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

Oct. 23, 2019

Re: Zayo to Omaha IX down

by Gary Glissendorf

SDN Transport looks good both directions 😊 Gary Glissendorf | Network Architect gary.glissendorf(a)sdncommunications.com 2900 W. 10th St. | Sioux Falls, SD 57104 (w) 605.978.3558 | (c) 605.359-3737 | (tf) 800.247.1442 SDN NOC 877.287.8023 NOC Support email: sdnsupport(a)sdncommunications.com “Ausgezeichnet Zueinander Sein” -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Wednesday, October 23, 2019 2:50 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo to Omaha IX down <table style="border:1px; border-style:solid; border-color:#ac6337; background-color:#ffeb9c"><tr><td><font size=2 face=calibri>CAUTION: This email originated from outside of SDN Communications. Exercise caution when opening attachments or clicking links, especially from unknown senders.</font></td></tr></table><br> Looks like several of the Nebraska folks lost their MICE connections as well. On Wed, Oct 23, 2019 at 2:41 PM Jeff Dahna <jeff.dahna(a)windommn.com> wrote: > > We lost our route to Omaha IX via Zayo around 2:04 PM CST. Got a ticket in with Zayo. Anyone else down to Omaha via Zayo? > > Jeff Dahna > Windomnet -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 ***This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.***

Oct. 23, 2019

Re: Zayo to Omaha IX down

by Jay Hanke

Looks like several of the Nebraska folks lost their MICE connections as well. On Wed, Oct 23, 2019 at 2:41 PM Jeff Dahna <jeff.dahna(a)windommn.com> wrote: > > We lost our route to Omaha IX via Zayo around 2:04 PM CST. Got a ticket in with Zayo. Anyone else down to Omaha via Zayo? > > Jeff Dahna > Windomnet -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Oct. 23, 2019

Zayo to Omaha IX down

by Jeff Dahna

We lost our route to Omaha IX via Zayo around 2:04 PM CST. Got a ticket in with Zayo. Anyone else down to Omaha via Zayo? Jeff Dahna Windomnet

Oct. 23, 2019

Re: Problem with my connection to MICE

by Steve Savoy

Hi Keith, I was wondering if you could share that information with me as well? Thank you, Steve Savoy -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Keith Anderson Sent: Tuesday, October 22, 2019 11:15 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Problem with my connection to MICE Thanks everyone. Another MICE member reached out to me directly and said they had a similar problem with this Brocade "feature" and advised me how to filter this unwanted traffic. The port now appears to be online and I can re-enable my peering tonight. Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

Oct. 22, 2019

Re: Problem with my connection to MICE

by Keith Anderson

Thanks everyone. Another MICE member reached out to me directly and said they had a similar problem with this Brocade "feature" and advised me how to filter this unwanted traffic. The port now appears to be online and I can re-enable my peering tonight.

Oct. 22, 2019

Re: Problem with my connection to MICE

by Andrew Hoyos

You might also check with your carrier, if one involved, to make sure nothing is in the middle that may be errantly emitting frames (CDP/LLDP, STP, etc). > On Oct 22, 2019, at 9:01 AM, Keith Anderson <keith.anderson(a)MARCONET.COM> wrote: > > Thanks, Jeremy. I was hoping you could provide just that sort of detail. I'm just not sure how there would be multiple coming from my side when this is a P2P link and the switch port is in route-only mode; I may have to work with Brocade on that. I will look into it, but can you tell me if the MAC addresses appear to be all from the same vendor?

Oct. 22, 2019

Re: Problem with my connection to MICE

by Keith Anderson

Thanks, Jeremy. I was hoping you could provide just that sort of detail. I'm just not sure how there would be multiple coming from my side when this is a P2P link and the switch port is in route-only mode; I may have to work with Brocade on that. I will look into it, but can you tell me if the MAC addresses appear to be all from the same vendor?

Oct. 22, 2019

Re: Problem with my connection to MICE

by Jeremy Lumby

We are seeing Port security errors on your port for too many Mac addresses. The industry standard is one Mac address, however currently mice allows up to five. Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington MN 55425 Main 612-355-7740 Direct 612-392-6814 EFax 952-873-7425 jlumby(a)mnvoip.com -------- Original message -------- From: Keith Anderson <keith.anderson(a)MARCONET.COM> Date: 10/22/19 8:33 AM (GMT-06:00) To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Problem with my connection to MICE _____ >From : Keith Anderson [keith.anderson(a)MARCONET.COM] To : MICE-DISCUSS(a)LISTS.IPHOUSE.NET [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] Date : Tuesday, October 22 2019 08:23:08 Good morning all. I have a problem with my MICE connection and I'm wondering if anyone can give me some direction. On September 9th, my predecessor disabled our port facing MICE due to BGP flapping (his description). Since there was chatter on this board about a fiber cut that day, he thought it was related to that. Unfortunately, when I re-enabled the port, I saw similar behavior. BGP seems to flap about every three minutes, and my log indicates that link is actually dropping on that port. Even though light levels never seem to drop below -4.4db, I had Cologix check the cross connect, clean the ends of the fiber, and re-seat the sfp. None of that helped. On Wednesday I replaced the SFP, but when I enabled the port, I still saw the same behavior. Last night I disabled all of my BGP peers and brought the port back online for further layer2 testing, but I can't ping any of my peers and I'm not seeing any arp entries on this port. Anyone have any ideas what could be going on or what I should check next? I've included my port config below for reference. The log entries associated with this problem are: Oct 22 08:17:33:I:SYSTEM: port 2/4 link fault status is cleared(physical link goes down 24) Oct 22 08:17:33:I:SYSTEM: port 2/4 is down( local fault) Oct 22 08:17:33:I:System: Interface ethernet 2/4, state down - local fault Oct 22 08:17:09:I:System: Interface ethernet 2/4, state up Oct 22 08:16:45:W: Latched low RX Power warning, port 2/4 Oct 22 08:16:45:A: Latched low RX Power alarm, port 2/4 interface ethernet 2/4 port-name BGP peering with MICE Arista 5/19 XC23175 load-interval 30 no fdp enable no cdp enable route-only ip address xxx.xxx.xxx.xxx/24 no spanning-tree sflow forwarding !

Oct. 22, 2019

Problem with my connection to MICE

by Keith Anderson

Good morning all. I have a problem with my MICE connection and I'm wondering if anyone can give me some direction. On September 9th, my predecessor disabled our port facing MICE due to BGP flapping (his description). Since there was chatter on this board about a fiber cut that day, he thought it was related to that. Unfortunately, when I re-enabled the port, I saw similar behavior. BGP seems to flap about every three minutes, and my log indicates that link is actually dropping on that port. Even though light levels never seem to drop below -4.4db, I had Cologix check the cross connect, clean the ends of the fiber, and re-seat the sfp. None of that helped. On Wednesday I replaced the SFP, but when I enabled the port, I still saw the same behavior. Last night I disabled all of my BGP peers and brought the port back online for further layer2 testing, but I can't ping any of my peers and I'm not seeing any arp entries on this port. Anyone have any ideas what could be going on or what I should check next? I've included my port config below for reference. The log entries associated with this problem are: Oct 22 08:17:33:I:SYSTEM: port 2/4 link fault status is cleared(physical link goes down 24) Oct 22 08:17:33:I:SYSTEM: port 2/4 is down( local fault) Oct 22 08:17:33:I:System: Interface ethernet 2/4, state down - local fault Oct 22 08:17:09:I:System: Interface ethernet 2/4, state up Oct 22 08:16:45:W: Latched low RX Power warning, port 2/4 Oct 22 08:16:45:A: Latched low RX Power alarm, port 2/4 interface ethernet 2/4 port-name BGP peering with MICE Arista 5/19 XC23175 load-interval 30 no fdp enable no cdp enable route-only ip address xxx.xxx.xxx.xxx/24 no spanning-tree sflow forwarding !

Oct. 22, 2019

Jump to page: