Any ideas what this means?
Nov 2 15:53:42 c1-145-ap 42: AP:000d.28f2.31ea: *Nov 2 22:53:40.582: %CAPWAP-3-CAPWAP_PAYLOAD_TOO_LARGE: Attempt to send capwap packet with payload exceeding max size. Payload Size: 2057, Maximum Allowed Payload: 1700Nov 2 15:53:42 c1-145-ap 43: AP:000d.28f2.31ea: -Traceback= 0x5E8E4 0x4B1410 0x43FA08 0x4417E4 0x4429E8 0x2A71ACNov 7 09:24:30 c3-143-ap 61: AP:000c.cea4.8b1a: *Nov 7 17:24:28.630: %CAPWAP-3-CAPWAP_PAYLOAD_TOO_LARGE: Attempt to send capwap packet with payload exceeding max size. Payload Size: 2044, Maximum Allowed Payload: 1700 Nov 7 09:24:30 c3-143-ap 62: AP:000c.cea4.8b1a: -Traceback= 0x5E8E4 0x4B1410 0x43FA08 0x4417E4 0x4429E8 0x2A71AC
These are 1100s in light-weight mode, managed by 5500WLC or WiSMs running 7.0.116 Message appears sporadically, every few weeks, sometimes once in a day, sometimes in bursts, typically from a single AP (out of a flock of ~200 campus-wide), the APs involved tend to live within a particular cluster of buildings.
You might as well open a TAC case on this unless one ot the Cisco guy's here can lookup that message. That message is not in the guide for that code you show:
Are the affected AP heavily loaded with voice and data clients.
Matching Bud ID - CSCtc82074
However the bug is fixed on 184.108.40.206 and it stops AP from crashing after this error message.
Printing error msg and traceback is ok but the AP shouldn't crash.