*Jan 14 00:41:53.509: 00:13:02:43:f9:d3 mmAnchorExportRcv: WLAN QIB_GUEST policy mismatch between controllers, WLAN QIB_GUEST not found, or WLAN disabled. Ignore ExportAnchor mobility msg. Delete client.
I'm assuming this debug is for the client in question.
When I've had problems with my Guest anchoring, it has always come from the configurations on the two controllers not being IDENTICAL. As in, even the slightest mismatch in the two WLANs has caused my problem.
For example, I would make sure that the WLAN on your local controller is configured EXACTLY like the DMZ, from the dhcp options to the encryption options, even the session timeout to exclusion times.
The bottom line is that this debug says the policies don't match (since I am assuming the wlan is configured on both controllers, and that the wlans are no disabled).
As the other user suggested, the run-config from each controller would be nice to see, but the problem may be as simple as one overlooked value not being identical...
(I am speaking from my experience with 4.1 though.... but I bet the same behavior is in 5)
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...