Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Bridges STP issues

Hi,

I'm getting the bellow error:

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd68 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

We have  branches connected together with redundancy  using motorolla bridges and we have enabled portfast on the port were this motorolla bridges are connected to.

5 REPLIES
Cisco Employee

Bridges STP issues

Error Message    SW_MATM-4-MACFLAP_NOTIF: Host [enet] in [chars] [dec] is flapping

between port [chars] and port [chars]

Recommended Action    The switch found the traffic from the specified host flapping

between the specified ports. [enet] is the host MAC address, [chars] [dec] is the switch

ID, the first and second [chars] are the ports between which the host traffic is flapping.

Recommended Action    Check the network switches for misconfigurations that might cause a

data-forwarding loop.

Further more I would like to add:

I have checked the outputs and I can see that there is only I mac addressbthat is causing the problem, i.e

001a.a18f.bd68

, could you please trace this mac address and see if it is seen within the switch or it is being learnt

across the switch.

I can also see that the port channel is connected to the server, we could

get the error message if the NIC teaming is not done correctly.

NIC teaming allows users to group two or more physical NICs into a single

logical network device called a bond. Once a logical NIC is configured, the

virtual machine is notaware of the underlying physical NICs. Packets sent to

the logical NIC are dispatched toone of the physical NICs in the bond and

packets arriving at any of the physical NICs areautomatically directed to

the appropriate logical NIC.

If one of the underlying physical NICs is broken or its cable has been

unplugged, server  will detect the fault condition and automatically move

traffic to another NIC in the bond. This capability eliminates a single

point of failure for any one physical NIC and makes the overall network

connection fault-tolerant.

Hope this helps.

Regards

Inayath

*Plz rate all usefull posts.

Bridges STP issues

Thanks Inayath,

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd68 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.c1e8 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a233.d938 in vlan 2 is flapping between port Fa0/45 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.f6c8 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.f701.7d00 in vlan 2 is flapping between port Fa0/44 and port Gi0/1

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6ca2.0660 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6cfb.2d00 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd98 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd68 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.f6c8 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.c1e8 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6ca2.0660 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.f701.7d00 in vlan 2 is flapping between port Fa0/44 and port Gi0/1

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6cfb.2d00 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a233.d938 in vlan 2 is flapping between port Fa0/44 and port Fa0/45

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd98 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.f701.7d00 in vlan 2 is flapping between port Gi0/1 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.f6c8 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.c1e8 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6ca2.0660 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd98 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd68 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6cfb.2d00 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.f6c8 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.f701.7d00 in vlan 2 is flapping between port Fa0/44 and port Gi0/1

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6cfb.2d00 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.c1e8 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd68 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd98 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a233.d938 in vlan 2 is flapping between port Fa0/44 and port Fa0/45

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6ca2.0660 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.f6c8 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.6cfb.2d00 in vlan 2 is flapping between port Fa0/48 and port Fa0/44

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.f701.7d00 in vlan 2 is flapping between port Fa0/44 and port Gi0/1

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.bd68 in vlan 2 is flapping between port Fa0/44 and port Fa0/48

3w5d: %SW_MATM-4-MACFLAP_NOTIF: Host 001a.a18f.c1e8 in vlan 2 is fla

as you can see from logs there lot diffent mac address, our quick solution was to shutdown the redundancy link.

Cisco Employee

Bridges STP issues

Yup,

sorry forgot to mentioned you that this happens if you have STP issue in your network as well.

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 198797 last change occurred 00:01 ago <-time rec'd


         from gig1/2 <--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.

HTH

Regards

Inayath

Bridges STP issues

I have checked and TCN happen on the interfaces were bridges are connected to.


should I enable portfast on the interface were bridges are connected to?

Purple

Bridges STP issues

Hi,

Never configure PortFast on ports connecting to other switches, you can do it on trunk ports connecting to VMs or Router/ASA with the spanning-tree portfast trunk command under the interface but otherwise PortFast should only be configured on access ports linked to hosts.

Regards

Alain

Don't forget to rate helpful posts.

Don't forget to rate helpful posts.
670
Views
0
Helpful
5
Replies
CreatePlease to create content