October 2019 - mice-discuss - lists.micemn.net

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

Re: 2019 Election Results

by Mike Horwath

On Wed, Oct 16, 2019 at 09:53:02PM +0000, AnthonyAnderberg(a)nuvera.net wrote: > Richard was re-elected unanimously, thanks for your continued service! Congrats! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Oct. 17, 2019

2019 Election Results

by AnthonyAnderberg＠nuvera.net

Richard was re-elected unanimously, thanks for your continued service! [cid:60F64B08-B963-4E01-B287-F9A49C3DDDFD-L0-001] Sent from my iPhone

Oct. 16, 2019

MICE UG 33

by Richard Laager

Reminder: UG 33 is on Wednesday of this week (October 16) at 3:00pm Remote Conferencing: 952-562-5400 passcode MICE (6423) Location: 511 Building Cafeteria Agenda The agenda is attached. I'm behind on getting this out, so I didn't send a separate call for agenda. If you have something to add, let me know ASAP and I'll send an updated agenda. I'd like to try the modified ordering again. The idea here is to group business (official reports and things that could involve a motion/vote) before open discussion. This way, people who are not interested in the discussion can leave earlier if they wish, confident that they won't miss an official motion/vote. By shortening the "mandatory" part of the meeting, this may make the meetings more accessible. I'd like to give this a try for a couple meetings and see what people think. The UG 32 draft minutes are also attached. -- Richard

Oct. 15, 2019

Re: Zayo Maintenance??

by Frank Bulk

And the update, four days later: After investigating, it looks like your service was impacted by a planned maintenance tracked under ticket TTN-0003551872. This maintenance consisted of Zayo relocating paths due to an Iowa DOT highway 75 reconstruction. It began on 10/9/2019 11:29 PM Central and concluded on 10/10/2019 4:22 AM Central. Unfortunately, the span your circuit rides on was missed on the impact list and therefore you were not notified. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Thursday, October 10, 2019 9:19 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Maintenance?? I did get a confirmation of my trouble ticket being opened, but no update thereafter. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of James Urwiller Sent: Thursday, October 10, 2019 10:30 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Maintenance?? I still have no confirmation of maintenance activities or otherwise at this point. I also find it hard to believe that it was an actual outage due to another observation of how fast it was restored. 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 Frank Bulk Sent: Thursday, October 10, 2019 10:26 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Maintenance?? The timing suggested a maintenance window, just that it wasn't communicated. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Tim Fjeld Sent: Thursday, October 10, 2019 7:43 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Maintenance?? Zayo was in our DC Tuesday afternoon. They were working their way north from Omaha testing fibers and verifying connections in effort to finalize turn up of their new transport equipment. I would imagine the outage might be related to that project, but cannot say with certainty. Tim Fjeld City of Windom

Oct. 14, 2019

MN VoIP Remote Upgrade

by Jeremy Lumby

The maintenance is complete. Traffic is returning, and I am checking for any potential errors. -----Original Message----- From: Jeremy Lumby [mailto:jlumby@mnvoip.com] Sent: Friday, October 11, 2019 1:47 PM To: MICE Discuss Subject: MN VoIP Remote Upgrade The maintenance described below will begin in a few minutes. BGP will be blocked ahead of time to allow traffic to gracefully taper off. 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 -----Original Message----- From: Jeremy Lumby [mailto:jlumby@mnvoip.com] Sent: Monday, September 30, 2019 5:47 PM To: MICE Discuss Subject: MN VoIP Remote Upgrade In accordance with the MICE remote switch operator guidelines, MN VoIP will be upgrading their remote switch and uplink to the MICE core on the afternoon of October 11th at approx 2PM to keep uplink utilization under 66% of the link capacity. Prior to the maintenance, BGP will be blocked so traffic can gracefully reroute. During the maintenance connectivity will be down for approximately 15 minutes. A 100G switch will be added between the existing MN VoIP extension and the MICE core. This switch will not only increase the MN VoIP uplink from 40G to 100G, it will also make 32 100G ports available to anyone wishing to connect to MICE via MN VoIP @ 100G. I will send out a notification to the discuss list right before I commence with the maintenance. 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

Oct. 11, 2019

MN VoIP Remote Upgrade

by Jeremy Lumby

The maintenance described below will begin in a few minutes. BGP will be blocked ahead of time to allow traffic to gracefully taper off. 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 -----Original Message----- From: Jeremy Lumby [mailto:jlumby@mnvoip.com] Sent: Monday, September 30, 2019 5:47 PM To: MICE Discuss Subject: MN VoIP Remote Upgrade In accordance with the MICE remote switch operator guidelines, MN VoIP will be upgrading their remote switch and uplink to the MICE core on the afternoon of October 11th at approx 2PM to keep uplink utilization under 66% of the link capacity. Prior to the maintenance, BGP will be blocked so traffic can gracefully reroute. During the maintenance connectivity will be down for approximately 15 minutes. A 100G switch will be added between the existing MN VoIP extension and the MICE core. This switch will not only increase the MN VoIP uplink from 40G to 100G, it will also make 32 100G ports available to anyone wishing to connect to MICE via MN VoIP @ 100G. I will send out a notification to the discuss list right before I commence with the maintenance. 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

Oct. 11, 2019

Re: Zayo Maintenance??

by Frank Bulk

I did get a confirmation of my trouble ticket being opened, but no update thereafter. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of James Urwiller Sent: Thursday, October 10, 2019 10:30 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Maintenance?? I still have no confirmation of maintenance activities or otherwise at this point. I also find it hard to believe that it was an actual outage due to another observation of how fast it was restored. 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 Frank Bulk Sent: Thursday, October 10, 2019 10:26 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Maintenance?? The timing suggested a maintenance window, just that it wasn't communicated. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Tim Fjeld Sent: Thursday, October 10, 2019 7:43 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Maintenance?? Zayo was in our DC Tuesday afternoon. They were working their way north from Omaha testing fibers and verifying connections in effort to finalize turn up of their new transport equipment. I would imagine the outage might be related to that project, but cannot say with certainty. Tim Fjeld City of Windom

Oct. 11, 2019