I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues? ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On 02/19/2014 3:23 PM, Jeremy Lumby wrote:
I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues?
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Yes, spanning tree loop? 30 second input rate 766296000 bits/sec, 118912 packets/sec -James ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Is someone advertising v6 routes they should not be onto the Mice servers? 2001:504:27::D1AF:0:1 4 53679 7060055 721494 80179512 0 13 00:03:02 244 2001:504:27::D1AF:0:2 4 53679 7073987 724693 80179512 0 0 00:11:10 9020 I see a lot of HE routes coming from route server 02 ________________________________________ From: MICE Discuss [MICE-DISCUSS@LISTS.IPHOUSE.NET] on behalf of James Stahr [stahr@MAILBAG.COM] Sent: Wednesday, February 19, 2014 3:28 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Mice Issues On 02/19/2014 3:23 PM, Jeremy Lumby wrote:
I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues?
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Yes, spanning tree loop? 30 second input rate 766296000 bits/sec, 118912 packets/sec -James ######################################################################## 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
On Wed, Feb 19, 2014 at 09:34:40PM +0000, Justin Krejci wrote:
Is someone advertising v6 routes they should not be onto the Mice servers?
2001:504:27::D1AF:0:1 4 53679 7060055 721494 80179512 0 13 00:03:02 244 2001:504:27::D1AF:0:2 4 53679 7073987 724693 80179512 0 0 00:11:10 9020
I see a lot of HE routes coming from route server 02
That is normal, HE is peering their whole IPv6 table to the route servers. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On 02/19/2014 03:23 PM, Jeremy Lumby wrote:
I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues?
Yes, something is broken. Loop? The CNS switch has many log entries like the following: Feb 19 15:27:50.787 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 10f3.1134.e6de in vlan 847 is flapping between port Te0/10 and port Te0/8 Feb 19 15:28:04.578 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 001b.0de7.15c0 in vlan 847 is flapping between port Te0/10 and port Te0/11 Feb 19 15:28:04.779 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.9999.2345 in vlan 847 is flapping between port Te0/11 and port Te0/10 Feb 19 15:28:04.846 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 0021.a00a.a040 in vlan 847 is flapping between port Te0/10 and port Gi0/1 Feb 19 15:28:05.081 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a10e.9f05 in vlan 847 is flapping between port Te0/10 and port Te0/12 Feb 19 15:28:05.383 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 10f3.1134.e6de in vlan 847 is flapping between port Te0/10 and port Te0/8 Feb 19 15:28:19.862 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 001b.0de7.15c0 in vlan 847 is flapping between port Te0/10 and port Te0/11 Feb 19 15:28:19.963 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a10e.9f05 in vlan 847 is flapping between port Te0/10 and port Te0/12 Feb 19 15:28:20.030 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.9999.2345 in vlan 847 is flapping between port Te0/10 and port Te0/11 Feb 19 15:28:20.433 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 0021.a00a.a040 in vlan 847 is flapping between port Te0/10 and port Gi0/1 Feb 19 15:28:22.798 CST: %SW_MATM-4-MACFLAP_NOTIF: Host 10f3.1134.e6de in vlan 847 is flapping between port Te0/10 and port Te0/8 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On Wed, Feb 19, 2014 at 03:23:00PM -0600, Jeremy Lumby wrote:
I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues?
I have a weird error on my MICE facing port. Feb 19 15:11:44.976 CST: %ETHCNTR-3-LOOP_BACK_DETECTED: Keepalive packet loop-back detected on GigabitEthernet0/4. Feb 19 15:11:44.976 CST: %PM-4-ERR_DISABLE: loopback error detected on Gi0/4, putting Gi0/4 in err-disable state I cleared that, but still having big packet loss across MICE. Did somebody make a loop/packet storm? Going through the switch now, very slow to see if I can identify who/what/where. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On Wed, Feb 19, 2014 at 03:30:09PM -0600, Doug McIntyre wrote:
Did somebody make a loop/packet storm? Going through the switch now, very slow to see if I can identify who/what/where.
At the moment, it looks to be coming from Mankato, unless somebody can tell me I'm reading things wrong. The logs are filling up with Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 That MAC address is learned from Mankato's remote 10G link dmcintyre@MICE-SW1> show ethernet-switching mac-learning-log | match 00:04:96:37:14:c3 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was deleted on xe-0/0/37.0 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was learned on xe-0/0/37.0 But, I'm not getting an extraordinary level of input traffic from there. Juniper PR695200 says this error message can be harmless though, so I'm not convinced this is the root cause. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
I've shutdown my port as well until things are resolved. On Wed, Feb 19, 2014 at 3:48 PM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Wed, Feb 19, 2014 at 03:30:09PM -0600, Doug McIntyre wrote:
Did somebody make a loop/packet storm? Going through the switch now, very slow to see if I can identify who/what/where.
At the moment, it looks to be coming from Mankato, unless somebody can tell me I'm reading things wrong.
The logs are filling up with
Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105
That MAC address is learned from Mankato's remote 10G link
dmcintyre@MICE-SW1> show ethernet-switching mac-learning-log | match 00:04:96:37:14:c3 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was deleted on xe-0/0/37.0 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was learned on xe-0/0/37.0
But, I'm not getting an extraordinary level of input traffic from there.
Juniper PR695200 says this error message can be harmless though, so I'm not convinced this is the root cause.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
########################################################################
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
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started? -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On Wed, Feb 19, 2014 at 04:03:15PM -0600, Richard Laager wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
Nobody turned up recently. A better measure is who turned up on the switch rather than the route-server. This was a l2 flood, not anything in routing. No ports were up/down on the switch until the flood triggered my port and Implex's port offline (probably the same class of cisco switch protecting themselves from the l2 flood). Feb 19 15:11:45 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 604, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/3 Feb 19 15:11:48 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 606, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/5 So, it probably was from one of the existing remote switches. The MAC address I posted about before is an Extreme? switch. Also, the l2 flood seems abated. I've been pinging clear to the route servers for 5 minutes now. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
There are two Extreme networks on the Mankato Remote switch, Vaultas and Revnet. I don't have ssh right now, can someone check? On Wed, Feb 19, 2014 at 2:21 PM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Wed, Feb 19, 2014 at 04:03:15PM -0600, Richard Laager wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
Nobody turned up recently.
A better measure is who turned up on the switch rather than the route-server. This was a l2 flood, not anything in routing.
No ports were up/down on the switch until the flood triggered my port and Implex's port offline (probably the same class of cisco switch protecting themselves from the l2 flood).
Feb 19 15:11:45 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 604, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/3 Feb 19 15:11:48 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 606, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/5
So, it probably was from one of the existing remote switches.
The MAC address I posted about before is an Extreme? switch.
Also, the l2 flood seems abated.
I've been pinging clear to the route servers for 5 minutes now.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
########################################################################
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 CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Got ssh, that mac doug sent out belongs to Vaultas. On Wed, Feb 19, 2014 at 2:27 PM, Jay Hanke <jayhanke@mankatonetworks.net> wrote:
There are two Extreme networks on the Mankato Remote switch, Vaultas and Revnet. I don't have ssh right now, can someone check?
On Wed, Feb 19, 2014 at 2:21 PM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Wed, Feb 19, 2014 at 04:03:15PM -0600, Richard Laager wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
Nobody turned up recently.
A better measure is who turned up on the switch rather than the route-server. This was a l2 flood, not anything in routing.
No ports were up/down on the switch until the flood triggered my port and Implex's port offline (probably the same class of cisco switch protecting themselves from the l2 flood).
Feb 19 15:11:45 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 604, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/3 Feb 19 15:11:48 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 606, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/5
So, it probably was from one of the existing remote switches.
The MAC address I posted about before is an Extreme? switch.
Also, the l2 flood seems abated.
I've been pinging clear to the route servers for 5 minutes now.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
########################################################################
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 CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net
-- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
The Vaultas switch has been configured to participate in spanning-tree, so it won't blindly go along with loops any more. Sorry. The Vaultas switch didn't make the loop, it just made it worse. Any word on the origination of the loop? -- Dan Boehlke dboehlke@mac.com On Feb 19, 2014, at 4:47 PM, Jay Hanke <jayhanke@MANKATONETWORKS.NET> wrote:
Got ssh, that mac doug sent out belongs to Vaultas.
On Wed, Feb 19, 2014 at 2:27 PM, Jay Hanke <jayhanke@mankatonetworks.net> wrote:
There are two Extreme networks on the Mankato Remote switch, Vaultas and Revnet. I don't have ssh right now, can someone check?
On Wed, Feb 19, 2014 at 2:21 PM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Wed, Feb 19, 2014 at 04:03:15PM -0600, Richard Laager wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
Nobody turned up recently.
A better measure is who turned up on the switch rather than the route-server. This was a l2 flood, not anything in routing.
No ports were up/down on the switch until the flood triggered my port and Implex's port offline (probably the same class of cisco switch protecting themselves from the l2 flood).
Feb 19 15:11:45 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 604, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/3 Feb 19 15:11:48 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 606, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/5
So, it probably was from one of the existing remote switches.
The MAC address I posted about before is an Extreme? switch.
Also, the l2 flood seems abated.
I've been pinging clear to the route servers for 5 minutes now.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
########################################################################
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 CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net
-- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net
########################################################################
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
On Wed, 2014-02-19 at 17:40 -0600, Dan Boehlke wrote:
The Vaultas switch has been configured to participate in spanning-tree
Is that really what we want? -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
I was just thinking that, because generally exchange point best practice is to turn spanning tree off. So maybe I shouldn't be embarrassed for not having done it.... :-( -- Dan B. On Feb 19, 2014, at 5:43 PM, Richard Laager <rlaager@wiktel.com> wrote:
On Wed, 2014-02-19 at 17:40 -0600, Dan Boehlke wrote:
The Vaultas switch has been configured to participate in spanning-tree
Is that really what we want?
-- Richard
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
On 2/19/14, 17:43 , Richard Laager wrote:
On Wed, 2014-02-19 at 17:40 -0600, Dan Boehlke wrote:
The Vaultas switch has been configured to participate in spanning-tree
Is that really what we want?
There are philosophical arguments both ways on this one. Given our cooperative management there is an argument to having spanning tree there to catch us if/when we screw up. In a very tightly managed situation where there can be no loops then there is an argument to turn-off spanning tree, but god help you if there ever is a loop. -- ================================================ David Farmer Email: farmer@umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
So next question, which flavor of spanning tree is best. I configured PVST on a reflex, but remembered that the MICE switch is a Juniper, not a Cisco. Simple dot1d? -- Dan B. On Feb 19, 2014, at 5:50 PM, David Farmer <farmer@UMN.EDU> wrote:
On 2/19/14, 17:43 , Richard Laager wrote:
On Wed, 2014-02-19 at 17:40 -0600, Dan Boehlke wrote:
The Vaultas switch has been configured to participate in spanning-tree
Is that really what we want?
There are philosophical arguments both ways on this one. Given our cooperative management there is an argument to having spanning tree there to catch us if/when we screw up.
In a very tightly managed situation where there can be no loops then there is an argument to turn-off spanning tree, but god help you if there ever is a loop.
-- ================================================ David Farmer Email: farmer@umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================
########################################################################
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
On Wed, 2014-02-19 at 16:21 -0600, Doug McIntyre wrote:
On Wed, Feb 19, 2014 at 04:03:15PM -0600, Richard Laager wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
Nobody turned up recently.
A better measure is who turned up on the switch rather than the route-server. This was a l2 flood, not anything in routing.
Yes, I know it was at layer 2, but if you look at the graph, there was one new *peer* (not route) that showed up just before this happened. It seems worth investigating that a little, as it *might* be related. In the graph tree, click "MICE Route Server". The first graph, "MICE IP4 Peers" is the graph to which I'm referring. -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On 2/19/14, 16:21 , Doug McIntyre wrote:
Also, the l2 flood seems abated.
I've been pinging clear to the route servers for 5 minutes now.
From looking at my CPU history, the appears to started 85 minutes ago, peaked about 75 minutes ago, subsided about 25 minutes ago. We saw BGP flaps all over the place, all peerings are back now except our peering with Implex, which has been down for 80 minutes or so. -- ================================================ David Farmer Email: farmer@umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On 2/19/14, 16:33 , David Farmer wrote:
On 2/19/14, 16:21 , Doug McIntyre wrote:
Also, the l2 flood seems abated.
I've been pinging clear to the route servers for 5 minutes now.
From looking at my CPU history, the appears to started 85 minutes ago, peaked about 75 minutes ago, subsided about 25 minutes ago.
We saw BGP flaps all over the place, all peerings are back now except our peering with Implex, which has been down for 80 minutes or so.
Implex is back now too, so all our direct peerings are back up. -- ================================================ David Farmer Email: farmer@umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Our port flipped to err-dis due to a detected loop. Jeff Anderson jeffa@implex.net 612.799.7277 Cell 612.339.8255 x200 Office 612.339.3310 Fax -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer Sent: Wednesday, February 19, 2014 4:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Mice Issues On 2/19/14, 16:21 , Doug McIntyre wrote:
Also, the l2 flood seems abated.
I've been pinging clear to the route servers for 5 minutes now.
From looking at my CPU history, the appears to started 85 minutes ago, peaked about 75 minutes ago, subsided about 25 minutes ago. We saw BGP flaps all over the place, all peerings are back now except our peering with Implex, which has been down for 80 minutes or so. -- ================================================ David Farmer Email: farmer@umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## 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
HCMC turned up peering this afternoon, l2 has been up for several days. I think the timing was maybe 20 minutes prior to issue. On Wed, Feb 19, 2014 at 2:03 PM, Richard Laager <rlaager@wiktel.com> wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
-- Richard
########################################################################
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 CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Did they plug in a switch or a router? Was it a loop? Are there loop mitigation techniques in place to automatically shutdown offending ports? When would you suggest that it's safe to come back online? On 2/19/14 4:40 PM, "Jay Hanke" <jayhanke@MANKATONETWORKS.NET> wrote:
HCMC turned up peering this afternoon, l2 has been up for several days.
I think the timing was maybe 20 minutes prior to issue.
On Wed, Feb 19, 2014 at 2:03 PM, Richard Laager <rlaager@wiktel.com> wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
-- Richard
########################################################################
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 CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net
########################################################################
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
On 02/19/2014 03:48 PM, Doug McIntyre wrote:
On Wed, Feb 19, 2014 at 03:30:09PM -0600, Doug McIntyre wrote:
Did somebody make a loop/packet storm? Going through the switch now, very slow to see if I can identify who/what/where.
At the moment, it looks to be coming from Mankato, unless somebody can tell me I'm reading things wrong.
The logs are filling up with
Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105
That MAC address is learned from Mankato's remote 10G link
dmcintyre@MICE-SW1> show ethernet-switching mac-learning-log | match 00:04:96:37:14:c3 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was deleted on xe-0/0/37.0 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was learned on xe-0/0/37.0
But, I'm not getting an extraordinary level of input traffic from there.
Juniper PR695200 says this error message can be harmless though, so I'm not convinced this is the root cause.
Are you a bunch of broadcast/multicast traffic? The CNS switch is seeing ~5000pps of broadcast traffic from the MICE main switch. I don't know what the normal rate is, but it seems like it is a bit high. Especially given that the average broadcast cost over the uptime of the switch is about 20pps. If the Mankato switch has a high broadcast rate, I'd shut down the port and see if things stabilize. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
We were seeing strange traffic making it to our MICE port before we shut it down. Other MICE members' http traffic destined to addresses not on our network. As if unicast packets were getting flooded. -Danny Danny Meister Network Engineer, Level II Atomic Data 615 North 3rd Street Minneapolis, MN 55401 612.466.2000 Main Line 612.466.2071 Direct Dial Simple. Safe. Smart. www.atomicdata.com On 2/19/14, 4:04 PM, "Steve Howard" <showard@PAULBUNYAN.NET> wrote:
On 02/19/2014 03:48 PM, Doug McIntyre wrote:
On Wed, Feb 19, 2014 at 03:30:09PM -0600, Doug McIntyre wrote:
Did somebody make a loop/packet storm? Going through the switch now, very slow to see if I can identify who/what/where.
At the moment, it looks to be coming from Mankato, unless somebody can tell me I'm reading things wrong.
The logs are filling up with
Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105
That MAC address is learned from Mankato's remote 10G link
dmcintyre@MICE-SW1> show ethernet-switching mac-learning-log | match 00:04:96:37:14:c3 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was deleted on xe-0/0/37.0 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was learned on xe-0/0/37.0
But, I'm not getting an extraordinary level of input traffic from there.
Juniper PR695200 says this error message can be harmless though, so I'm not convinced this is the root cause.
Are you a bunch of broadcast/multicast traffic? The CNS switch is seeing ~5000pps of broadcast traffic from the MICE main switch. I don't know what the normal rate is, but it seems like it is a bit high. Especially given that the average broadcast cost over the uptime of the switch is about 20pps.
If the Mankato switch has a high broadcast rate, I'd shut down the port and see if things stabilize.
########################################################################
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
We were seeing elevated levels of multicast, but most of what we were receiving was unicast well in excess of what we normally see. If MACs were flapping between ports due to a bridging loop, the switch may have disabled MAC learning in the VLAN, leading to unicast flooding after learned MACs timed out. Steven Bertsch Engineer III OneNeck(r) IT Solutions, a TDS(r) Company Direct: 612.395.8966 Cell: 612.232.1181 Email: steven.bertsch@oneneck.com Website: www.oneneck.com -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Danny Meister Sent: Wednesday, February 19, 2014 4:08 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Mice Issues We were seeing strange traffic making it to our MICE port before we shut it down. Other MICE members' http traffic destined to addresses not on our network. As if unicast packets were getting flooded. -Danny Danny Meister Network Engineer, Level II Atomic Data 615 North 3rd Street Minneapolis, MN 55401 612.466.2000 Main Line 612.466.2071 Direct Dial Simple. Safe. Smart. www.atomicdata.com On 2/19/14, 4:04 PM, "Steve Howard" <showard@PAULBUNYAN.NET> wrote:
On 02/19/2014 03:48 PM, Doug McIntyre wrote:
On Wed, Feb 19, 2014 at 03:30:09PM -0600, Doug McIntyre wrote:
Did somebody make a loop/packet storm? Going through the switch now, very slow to see if I can identify who/what/where.
At the moment, it looks to be coming from Mankato, unless somebody can tell me I'm reading things wrong.
The logs are filling up with
Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 master MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105 Feb 19 15:34:18 MICE-SW1 backup MRVL-L2:mrvl_fdb_mac_entry_uc_set(),966:FDb SP HW-overwrite failed(3) for VLANIdx=3:00:04:96:37:14:c3/48:IFL=105
That MAC address is learned from Mankato's remote 10G link
dmcintyre@MICE-SW1> show ethernet-switching mac-learning-log | match 00:04:96:37:14:c3 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was deleted on xe-0/0/37.0 Wed Feb 19 15:11:44 2014 vlan_name default mac 00:04:96:37:14:c3 was learned on xe-0/0/37.0
But, I'm not getting an extraordinary level of input traffic from there.
Juniper PR695200 says this error message can be harmless though, so I'm not convinced this is the root cause.
Are you a bunch of broadcast/multicast traffic? The CNS switch is seeing ~5000pps of broadcast traffic from the MICE main switch. I don't know what the normal rate is, but it seems like it is a bit high. Especially given that the average broadcast cost over the uptime of the switch is about 20pps.
If the Mankato switch has a high broadcast rate, I'd shut down the port and see if things stabilize.
########################################################################
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
On 02/19/2014 03:23 PM, Jeremy Lumby wrote:
I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues?
The first log message in the CNS switch was at Feb 19 15:11:44.238 CST. Did anybody plug something in then? ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Atomic has proactively shutdown our port to MICE due to heavy traffic influx/reliability issues across the switch fabric. We will re-enable our peering after the issues have subsided. On 2/19/14 3:31 PM, "Steve Howard" <showard@PAULBUNYAN.NET> wrote:
On 02/19/2014 03:23 PM, Jeremy Lumby wrote:
I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues?
The first log message in the CNS switch was at Feb 19 15:11:44.238 CST. Did anybody plug something in then?
########################################################################
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
We're shut down as well until things calm down. Chase Rydberg *MDU Ethernet Solutions* On Wed, Feb 19, 2014 at 3:37 PM, Larry Patterson <larry@atomicdata.com>wrote:
Atomic has proactively shutdown our port to MICE due to heavy traffic influx/reliability issues across the switch fabric. We will re-enable our peering after the issues have subsided.
On 2/19/14 3:31 PM, "Steve Howard" <showard@PAULBUNYAN.NET> wrote:
On 02/19/2014 03:23 PM, Jeremy Lumby wrote:
I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues?
The first log message in the CNS switch was at Feb 19 15:11:44.238 CST. Did anybody plug something in then?
########################################################################
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
participants (15)
-
Bertsch, Steven -
Chase Rydberg -
Dan Boehlke -
Danny Meister -
David Farmer -
Doug McIntyre -
James Stahr -
Jay Hanke -
Jeff Anderson -
Jeremy Lumby -
Justin Krejci -
Larry Patterson -
Nathan Beard -
Richard Laager -
Steve Howard