OPERATIONAL DEFECT DATABASE
...
...
Wireless clients experiencing unexpected disconnections with CO_CLIENT_DELETE_REASON_EXCLUDE_IP_THEFT reason in WLC always-on traces. Examples: {wncd_x_R0-4}{1}: [client-orch-sm] [18766]: (note): MAC: aaaa.aaaa.aaaa Client delete initiated. Reason: CO_CLIENT_DELETE_REASON_EXCLUDE_IP_THEFT, details: , fsm-state transition 13|14|15|13|14|15|13|14|15|13|14|15|13|14|15|13|14|15|13|17|18|28|33|42|44|46|48|4d|5c|5e|7f|a6| [client-iplearn] [18766]: (ERR): MAC: aaaa.aaaa.aaaa SISF theft event IP_THEFT_ATTEMPT IP y : y : y : y : y : y : y : y vlan X ifhdl: 0x90800204 owned by MAC: bbbb.bbbb.bbbb
IPv6 addressing used for client VLANs.
At this time, there is no workaround
Stale entries can be identified from the output of the following commands: sh wireless device-tracking database mac bbbb.bbbb.bbbb show wireless client summary | include bbbb.bbbb.bbbb Where bbbb.bbbb.bbbb is MAC address of the "original owner" of the conflicting IPv6 address. The first command shows the stale entry while the second command confirms client session is no longer active on the WLC.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
