That is normal in an autonomous environment. The reason is because the MAC address is cached on the switch somewhen the device roams to a new Ap, the AP sends out the device MAC address and now you have multiple MAC address until the other MAC address is removed from the switch.
Wireless configuration is in all time Active/Active mode.
And about the Te1/6/3, this is the miserable part. Cause ASASM is the service module install at C6500 chassis, there's no physical interface can be found. I have no idea why only this logical interface having this error log,
Client MAC adrees is flapping between Po200 & Po201 indicating when client roam, those two APs controlled by two different controller. It is always good practice to put all the AP geographically close by on to one controller as primary. In that way most of the roaming would be intra controller roaming & would not have issues like you are facing.
What is vlan 120, does it need to go to Access switches ? Since you have layer 2 trunk link across access layer port channel, there is possiblity MAC learn via two path. Is it possble to block vlan 120 on P102 ?
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...