September 2020 - mice-discuss

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

Re: MICE port down

by Doug McIntyre

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

MICE port down

by Todd Mueller

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. Thanks! Todd

Sept. 21, 2020

Re: Please welcome Woofy.io to MICE!

by Doug McIntyre

On Fri, Sep 18, 2020 at 12:12:24PM -0500, Jay Hanke wrote: >Name: Woofy.io >Port: Ethernet19 (MN Voip 10G Remote Switch) >ASN: 396388 >IPv4: 206.108.255.171/24 >IPv6: 2001:504:27:0:6:c64:0:1/64 >Peering Contact: noc(a)woofy.io >Route Servers- YES >BFD: No >AS-SET: AS-WOOFY Added to the route servers.

Sept. 18, 2020