FLAPPING ISSUE

Unanswered Question
Jul 22nd, 2013

In my network I got to much FLAPPING ISSUE

I have configured below mention command on all port

"

interface GigabitEthernet0/20

switchport mode access

switchport nonegotiate

spanning-tree portfast

spanning-tree bpdufilter enable    "

I thought   "  spanning-tree bpdufilter enable  "    may be this command flappiing is occure ... kindly suggest

Show a log of mention switches

is flapping between port Gi0/23 and port Gi0/20

Jul 23 04:40:09.083 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 04:42:08.134 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 04:44:07.940 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 04:56:02.164 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 04:57:00.926 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:00:59.272 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:03:04.010 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:13:10.331 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:18:11.499 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:20:11.406 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:25:07.289 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:33:07.788 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:35:59.386 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:40:01.087 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:44:08.652 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:49:02.580 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:53:15.715 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:57:03.625 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:58:06.414 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 05:59:10.344 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:04:09.356 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:07:06.053 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:11:00.607 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:17:05.227 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:25:41.034 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:27:02.253 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:28:09.756 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:28:35.358 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:32:05.333 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/20 and port Gi0/23

Jul 23 06:32:28.696 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:36:52.148 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:37:38.504 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:50:08.597 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 06:54:58.759 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:05:36.990 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:06:37.136 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:08:38.335 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:10:39.441 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:13:40.509 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:14:33.987 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:17:23.068 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:21:23.955 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:26:22.271 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:28:15.114 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:33:18.765 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:35:15.451 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:36:31.611 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:43:39.732 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:44:16.709 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 07:50:26.437 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:00:13.682 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:01:17.142 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:05:48.740 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:10:17.142 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:18:27.330 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:22:25.272 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:28:20.513 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:32:47.857 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:34:25.685 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:35:14.733 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:37:24.798 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:37:38.253 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 08:42:14.337 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
Peter Paluch Mon, 07/22/2013 - 20:37

Hi Naitik,

Definitely, the spanning-tree bpdufilter enable is inappropriate here. Using this command, you have effectively disabled STP on your ports. Now it is not able to protect your network against switching loops, as also evidenced by the MAC flapping message.

Remove the spanning-tree bpdufilter enable command from all your interfaces.

Is there any particular reason you wanted to use this command for? The BPDUFilter feature is used most often to separate two or more independent STP domains in a single switched network with no physical loops between the individual domains. I do not think this is what you wanted to achieve.

Best regards,

Peter

kevin.dorrell Tue, 07/23/2013 - 00:32

I agree with Peter ... I never use bpdufilter unless I have a real corner case that demands it.  bpdufilter removes all your protection against network meltdown (and flapping).

Some time ago there was a "best practice" document that recommended using bpdufilter on access ports.  IMHO, that recommendation was just plain wrong.  bpdufilter is dangerous.

OTOH, bdpuguard is an excellent idea on an access port, because it protects you against rogue switches or against users creating loops.  You can set bpduguard as a default for access ports with a global command.

Kevin Dorrell

Luxembourg

naitikpatel Tue, 07/23/2013 - 02:18

After configure  " spanning-tree bpduguard enable " on all access port still we got flapping on switch

find the below log of those switches

Jul 23 14:05:38.767 ist: %SYS-5-CONFIG_I: Configured from console by krunalb.tcs

on vty0 (172.25.56.127)

Jul 23 14:06:53.031 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:06:55.782 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f60a in vlan 1

is flapping between port Gi0/23 and port Gi0/12

Jul 23 14:07:16.074 ist: %SYS-5-CONFIG_I: Configured from console by krunalb.tcs

on vty0 (172.25.56.127)

Jul 23 14:07:58.420 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:13:58.935 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:15:49.077 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:18:01.978 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f60a in vlan 1

is flapping between port Gi0/23 and port Gi0/12

Jul 23 14:21:50.592 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:22:58.682 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:24:51.651 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:28:22.095 ist: %SYS-5-CONFIG_I: Configured from console by krunalb.tcs

on vty0 (172.25.56.127)

Jul 23 14:37:02.179 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:39:51.386 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20

Jul 23 14:47:31.524 ist: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.bc36.f618 in vlan 1

is flapping between port Gi0/23 and port Gi0/20


Leo Laohoo Tue, 07/23/2013 - 02:40

Both "0000.bc36.f618" and "0000.bc36.f60a" belong to Rockwell.

Are these clients configured with DUAL NICS?

naitikpatel Tue, 07/23/2013 - 19:56

IN Rockwell device they have a unmanaged 5 port switch

so how we identify...

insharie Tue, 07/23/2013 - 20:03

i would say tht the issue is STP, this might include many causes including L1 and L2, i will try to add the following statements i used to tshoot any STP related issues, as you know there is no procedureal way to tshoot STP, but we have to follow some best practises...

1) First, verify that currently the proper switch is STP root for all VLANs, as you have alredy done this. Then enable root guard on Root/Core switch on all uplink ports to the distribution layer switches.

Excellent doc that details root guard. See the section titled ” What Is the Difference Between STP BPDU Guard and STP Root Guard?” for clarification on the difference. You want root guard on the root and bpdu guard on the access layer. You do not want root guard on the port channel between core switches running HSRP. Only on the uplinks to other switches that you do NOT want to become spanning tree root.

http://www.cisco.com/en/US/tech/tk389/tk621/technologies_tech_note09186a00800ae96b.shtml

2) Enable loop guard on all distribution/access layer switches

3) Enable BPDU guard on all distribution/access layer switches

4) Enable UDLD aggressive on all fiber uplinksUnidirectional links can cause spanning tree loops. UDLD Aggressive will prevent this by shutting down a unidirectional link.

4.1) assure that all ten gig ports TX and RX connected correctly between peers...

5) Prune unnecessary VLANs off your trunks

6) assure that the customer doesnt make any tuning to the STP timers, as this could cause the loops as well...

6.1) assure that all Switches running RSTP, and check the trunks allowed Vlan list, using the command "show interface trunk", and makesure about the trunk allowed list on both ends of the trunk port... assure that both ends of the trunk allow the same list of vlans...

7) Enable mac-address move notification (if applicable) using >>> mac-address-table notification mac-move

Check the switch log for mac’s flapping between interfaces. These are the ports that are participating in the loop. Trace the MAC back to its source. Look for:

A link flapping on a upstream switch, causing spanning tree TCNs and Spanning Tree reconvergence. This should be used in conjunction with step 3 below.

A unidirectional link on an upstream switch causing the loop.

A hub or switch connected to a portfast enabled access port where this mac is learned. Shut this port down and see if this breaks the loop.

8)Check for TCNs

While the loop is occurring, if you see excessive TCNs you need to trace the TCNs (topology change notifications) to the source .

To do this, start from the core and run the following commands:

SW#show spanning-tree detail | inc ieee|occurr|from|is exec

The output from this command will show you the port the last TCN was received on and the time which it was received.

Look for the port that received a TCN in the last few seconds.

here is an example:

SW#sh spanning-tree detail | i ieee|occur|from|is exec

   VLAN0001 is executing the rstp compatible Spanning Tree protocol

     Number of topology changes 187927 last change occurred 00:01 ago <-time rec'd

         from Port-Channel12 <--interface that received the TCN

You will want to follow this port until the port that receives the TCN is an access port, or until the switch in question is generating TCNs but not receiving them. If you find an access port receiving TCNs, shut it down.

If you find a switch generating TCNs, you will want to look for two ports in a spanning tree forwarding state for the same VLAN. If you find two ports in a forwarding state, shut one port down and see if this breaks the loop. Check for a unidirectional link or excessive link flaps.

shanilkumar2003 Tue, 07/23/2013 - 20:26

This could be due to the unmanaged switch(hub) connected to that port. Try to remove it with a managed cisco switch and check.

Thanks
Shanil

Sent from Cisco Technical Support iPhone App

naitikpatel Wed, 07/24/2013 - 00:55

I follow all steps

When i reached Step 8

I apply command

SW#show spanning-tree detail | inc ieee|occurr|from|is exec

then i got

VLAN0001 is executing the ieee compatible Spanning Tree protocol

  Number of topology changes 16584 last change occurred 00:03:38 ago

          from GigabitEthernet1/0/4

VLAN0112 is executing the ieee compatible Spanning Tree protocol

  Number of topology changes 2 last change occurred 5d21h ago

VLAN0134 is executing the ieee compatible Spanning Tree protocol

  Number of topology changes 2 last change occurred 5d21h ago

VLAN0312 is executing the ieee compatible Spanning Tree protocol

  Number of topology changes 3 last change occurred 5d21h ago

Then i configured  on Interface GI 1/0/4

"

interface GigabitEthernet1/0/4

spanning-tree bpduguard enable

end  "

After configured  BPDUGUARD on TCn changed port

I also got flapping and same port also change TCN .

Which ccommand i used on that port ........That  port not changed TCN in future.

insharie Wed, 07/24/2013 - 03:40

Naitik,

Can you check what is connected to port GI 1/0/4 ? If possible can you shut down this port and check the situation?

Whats the cpu utilization?

Regards

Inayath

naitikpatel Wed, 07/24/2013 - 07:56

Ya i checked

on Interface Gi 1/0/4   Rockwell pannel's  AENT modual which is normaly a screen of Pannel

And CPU utilizatin is normal at that time.....When i got disconnect that pannel from GI 1/0/4......Flapping Stop for some switches.....But that pannel we cant unplung longer time.......So if that pannel plung and after what we do ..on that port to stop flapping ...

Leo Laohoo Wed, 07/24/2013 - 04:33
IN Rockwell device they have a unmanaged 5 port switch

So let me get this straight, you have TWO Rockwell devices plugged to a 5-port un-managed switch?  I presume this 5-port unmanaged switch is connected to your Cisco switch via TWO ports, right?

naitikpatel Sat, 07/27/2013 - 09:07

Its Rockwell devices  but in that one port is connected to AENT modual and other is a Versa-View which is nothing but a screen of Rockwell device...

Port number Gi1/0/4 is connected to AENT modual. I found that port is going up----down , down----up frequntly .  What is the reason behind that..

Actions

Login or Register to take actions

This Discussion

Posted July 22, 2013 at 8:31 PM
Stats:
Replies:13 Avg. Rating:
Views:486 Votes:0
Shares:0

Related Content

Discussions Leaderboard

Rank Username Points
1 14,997
2 8,150
3 7,720
4 7,078
5 6,718
Rank Username Points
180
80
59
55
55