02-09-2010 07:12 AM - edited 03-06-2019 09:38 AM
I am having an issue at one of our remote agencies whereas we are getting numerous mac-flap notifications on our switches. This has become kind of a hinderance as we are getting tired of seeing these messages. The end users havent been complaining, but the log messages are annoying.
It's usually occurring with the same mac-addresses over and over. Upon further investigation, we found the mac-addresses are all on laptops which have both wireless and wired nic's. There are wireless AP's (cisco 1242's) in use which they can connect. We also found where the error is popping up as they move from wireless into docking into their docking station which has a lan cable attached. I was under the assumption that the wireless mac and wired mac were different numbers and therefore if the wired was up simultaneously with the wired, as it switched over, they shouldn't get a flap.
How can I correct this....or is it correctable?
I have attached a diagram to show my scenario, keep in mind those are just a few of the MANY msg's we have been receiving. If anyone
can explain this to me, I'd appreciate it.
02-09-2010 07:24 AM
jonesl1 wrote:
I am having an issue at one of our remote agencies whereas we are getting numerous mac-flap notifications on our switches. This has become kind of a hinderance as we are getting tired of seeing these messages. The end users havent been complaining, but the log messages are annoying.
It's usually occurring with the same mac-addresses over and over. Upon further investigation, we found the mac-addresses are all on laptops which have both wireless and wired nic's. There are wireless AP's (cisco 1242's) in use which they can connect. We also found where the error is popping up as they move from wireless into docking into their docking station which has a lan cable attached. I was under the assumption that the wireless mac and wired mac were different numbers and therefore if the wired was up simultaneously with the wired, as it switched over, they shouldn't get a flap.
How can I correct this....or is it correctable?
I have attached a diagram to show my scenario, keep in mind those are just a few of the MANY msg's we have been receiving. If anyone
can explain this to me, I'd appreciate it.
Are the users with these laptops roaming wirelessly across floors ie. could they be connected on bottom floor before then going back to floor 2, for example, where their wired connection is ?
Jon
02-09-2010 08:19 AM
yes, its very possible. I would say most generally, they would stay on their floor, but they could very easily move from floor to floor.
I also believe that they may be able to connect to the AP's on the other floors since they can probably pick up the AP signal.
Do you think that's what is causing my issue?
02-09-2010 08:41 AM
The wireless card and LAN card in the laptop will definitely have different MAC addresses.
We had the same thing with the wireless MAC addresses a while ago and I put it down to devices associating with different APs as they moved through the building (these were handheld wireless scanners in our case). However, there did also seem to be one or two laptops which I didn't think would move around so much.
I upgraded the IOS on the APs and the distribution switches (C3508s) but that didn't resolve the problem. The c3508s were later replaced by 3750-12S switches, but we still had MAC flap messages being reported. As all of the MAC addresses in question were wireless devices, I ended up ignoring the messages and putting it down to the devices roaming between APs.
The strange thing was that a couple of months after installing the 3750s, the problem went away!
I still think it was to do with wireless roaming though.
Not sure if all that is of much help to you or not.
It is worth checking if the MAC addresses that are flapping are the wireless card addresses.
Pete
02-09-2010 08:46 AM
That does help....thank you for your response. I will defnitely check that and see if they are the wireless nic's on all the devices.
04-08-2012 10:08 AM
MAC flapping will occur during a layer 2 roam for a clinet on 2 ap's or 2 wlc's ( salt and pepper deployment)
This can also happen during HREAP local switching roam
The reason for this is that the client MAC address is learnt on the local switch by 2 different ingress interfaces. Ona layer 2 roam the wlc will forward the client entry to the second wlc ( the ap where the client roams to, is on a different wlc)
04-08-2012 10:09 AM
This document has the information
http://www.cisco.com/en/US/products/hw/wireless/ps430/products_qanda_item09186a008009483e.shtml
12-10-2013 08:06 AM
was the issue resolved ??
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide