Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

WiSM - Primary WLC APs are suddenly associating/deassociating between Pri and Sec

We have a WiSM with WLC running on ver. 7.0.116.0 with around 101 Aps and aroung 1600 users.

Out of a sudden all APs are deassociating from primary and associating to the secondary controller and after all AP's will start to swing back and forth between these 2 controllers. We rebooted the primary and it resolves the issue. It happen twice within a span of 1 week. All users connecting to the AP affected are getting connection issue.

From the show tech and logging there's nothing much I can decipher but noticed the trace back as below generated a number of times.

I cant decode this in Cisco interpreter since It does not recognize the system info of the WLC.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

Appreciate all feedback. Thank you.

apfOpenDtlSocket: Feb 03 13:28:23.503: %APF-1-PROC_CLIENT_ASS_RES_FAILED: apf_client.c:1387 Could not process client association response. Missing Information Elements in Association Response.

*apfReceiveTask: Feb 03 13:28:20.234: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile c4:2c:03:6b:bd:bf as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:28:12.988: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0b:fc:24 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:28:06.819: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile e0:b9:a5:27:d0:b7 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:59.334: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 90:84:0d:50:6f:94 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:27:58.760: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:26:AB:9D:D2:DC. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:27:57.472: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile e0:f8:47:1a:d2:d6 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:50.881: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0b:80:78 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfOpenDtlSocket: Feb 03 13:27:49.621: %APF-1-INVALID_AUTH_SEQ_NUM: apf_client.c:1677 Invalid authentication sequence number.

*apfOpenDtlSocket: Feb 03 13:27:49.601: %APF-1-INVALID_AUTH_SEQ_NUM: apf_client.c:1677 Invalid authentication sequence number.

*apfRogueTask: Feb 03 13:27:48.880: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 2A:E0:2C:AF:3D:E2. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:27:47.002: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0c:2a:f8 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:42.775: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile e0:f8:47:1b:06:34 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:31.854: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:96:b3:c8 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

--More-- or (q)uit

*apfReceiveTask: Feb 03 13:27:26.916: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 78:e4:00:aa:f0:72 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:26.881: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile d4:20:6d:72:e8:32 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:25.894: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile b4:74:9f:d0:76:00 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:13.868: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 90:84:0d:50:6f:94 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:27:12.890: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue E6:CE:8F:BC:A8:37. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:27:09.992: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue A4:D1:D2:0A:1A:D0. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:27:08.418: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 60:C5:47:94:AB:F8. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:27:07.802: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:03:ab:c0 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:27:06.008: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 7c:c5:37:79:8a:77 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:56.532: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile f0:7b:cb:11:48:56 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:55.729: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 64:a7:69:b2:2a:1d as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:55.159: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:02:94:38 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:55.126: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:08:35:f4 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

--More-- or (q)uit

*apfReceiveTask: Feb 03 13:26:45.522: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile f8:1e:df:de:a5:65 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:43.925: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:1d:e0:6c:46:fd as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:40.410: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0b:fc:24 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:39.821: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:99:d2:b0 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:38.293: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 7c:11:be:33:37:71 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:35.668: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile f0:cb:a1:7f:f4:12 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:33.620: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 68:a3:c4:34:db:54 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:32.041: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 60:33:4b:10:c3:a9 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:31.721: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:07:64:18 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:28.242: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 68:a3:c4:34:db:54 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:27.653: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:08:35:f4 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:27.218: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:9d:af:ac as anchor while in the wrong state.

--More-- or (q)uit

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:21.999: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 70:1a:04:4f:48:ba as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:18.338: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0b:c8:04 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:17.479: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 14:8f:c6:d2:73:ae as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:26:15.443: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 7A:1F:AA:B5:4A:5E. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:26:14.582: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:26:AB:0F:F9:FF. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:26:14.580: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:26:AB:0F:F8:0A. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:26:14.501: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:04:bd:b4 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:08.687: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0f:46:78 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:01.676: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0d:4f:bc as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:26:00.232: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:1e:64:46:34:8c as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:25:58.654: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:24:D7:02:96:90. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:25:57.043: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 14:5a:05:cb:79:c4 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:41.999: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile e0:f8:47:74:c7:f5 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

--More-- or (q)uit

*apfReceiveTask: Feb 03 13:25:37.354: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:0c:2a:ac as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:29.760: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile f0:b4:79:46:32:54 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:24.219: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile cc:08:e0:ba:2a:24 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:24.134: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:08:3b:f8 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:19.030: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 78:e4:00:37:9d:47 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:16.901: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:08:35:f4 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:14.219: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile f0:cb:a1:81:c7:07 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:08.660: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 14:8f:c6:d2:73:ae as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:25:00.480: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:00:34:40 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:24:58.376: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:30:5B:02:3A:FF. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:24:57.525: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:97:0a:dc as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:55.078: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 60:33:4b:10:c3:a9 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

--More-- or (q)uit

*apfReceiveTask: Feb 03 13:24:52.280: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 64:a7:69:b2:2a:1d as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:24:49.995: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:30:5B:02:3B:01. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:24:47.004: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 18:f4:6a:22:ef:f2 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:38.858: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile a0:88:b4:05:8c:78 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:38.361: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile f8:1e:df:de:ac:ce as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:32.278: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 18:f4:6a:22:ef:f2 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:30.517: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 98:0c:82:5b:24:32 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:24:22.591: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 6A:60:BC:EB:DE:06. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:24:19.580: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:04:bd:b4 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:16.220: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 18:e7:f4:84:94:4f as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:01.571: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 4c:0f:6e:5f:3f:e5 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:24:01.341: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile e8:39:df:33:2e:97 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:23:50.342: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:26:c7:30:b9:ca as anchor while in the wrong state.

--More-- or (q)uit

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:23:42.035: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 14:5a:05:51:61:6f as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:23:41.637: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:16:cb:07:65:80 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:23:40.031: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:97:0a:dc as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:23:28.227: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile e0:f8:47:2b:ca:42 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:23:27.819: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:21:6a:1f:16:fc as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:23:05.388: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 7A:1F:AA:3D:31:84. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:22:53.641: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:24:D7:91:09:30. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:22:34.883: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:26:AB:0F:E4:FA. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:22:33.726: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile f8:1e:df:e0:ca:5f as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:22:21.994: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile d8:9e:3f:5c:af:ba as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:22:20.033: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile e4:ce:8f:17:01:d4 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:22:01.561: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:24:D7:12:89:7C. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:22:01.126: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 36:5A:05:A3:1B:62. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:22:00.500: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 6A:A8:6D:E5:19:14. multicast bit set in BSSID.

--More-- or (q)uit

*apfRogueTask: Feb 03 13:22:00.063: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 00:30:13:F8:37:4A. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:21:57.595: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 7E:59:48:65:2F:2D. multicast bit set in BSSID.

*apfOpenDtlSocket: Feb 03 13:21:53.740: %APF-1-INVALID_AUTH_SEQ_NUM: apf_client.c:1677 Invalid authentication sequence number.

*apfRogueTask: Feb 03 13:21:46.959: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 36:5A:05:1F:1A:E0. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:21:46.956: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 02:1A:11:FB:E1:69. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:21:14.439: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 72:EA:D6:31:29:28. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:21:10.082: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 2E:74:C2:4C:AB:1E. multicast bit set in BSSID.

*apfRogueTask: Feb 03 13:21:10.074: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 34:15:9E:7E:1C:46. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:21:05.075: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile 00:24:d7:a8:bd:f8 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfRogueTask: Feb 03 13:21:03.473: %APF-1-ROGUE_AP_CONTAIN_FAILED: apf_rogue.c:3920 Unable to contain rogue 3E:D0:F8:25:0C:EE. multicast bit set in BSSID.

*apfReceiveTask: Feb 03 13:20:49.511: %APF-1-RCV_MOBILITY_RES: apf_mm.c:181 Received Mobility response for mobile cc:08:e0:ba:2a:24 as anchor while in the wrong state.

-Traceback:  1010d088 1010f5e0 10110500 101242f8 1060b06c 10cc7978 112774ec

*apfReceiveTask: Feb 03 13:20:39.229: %APF-1-RCV_MOBIL*apfMsConnTask_0: Feb 03 13:10:53.466: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:17:c4:ca:02:6b to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 13:10:53.466: %PEM-1-ADDNPURULE1: pem_api.c:2787 Unable to push temporary Fast Path rule for mobile 00:17:c4:ca:02:6b on AP 00:27:0d:07:6b:a0

*apfMsConnTask_0: Feb 03 13:10:53.438: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:17:c4:ca:02:6b to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 13:10:53.386: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:17:c4:ca:02:6b to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 13:10:53.386: %PEM-1-ADDNPURULE1: pem_api.c:2787 Unable to push temporary Fast Path rule for mobile 00:17:c4:ca:02:6b on AP 00:27:0d:8b:a7:30

*apfMsConnTask_0: Feb 03 13:10:53.270: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:17:c4:ca:02:6b to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 13:10:53.269: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:24:d7:0c:2a:f8 to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 13:1

*apfMsConnTask_0: Feb 03 12:53:45.185: %PEM-1-ADDNPURULE1: pem_api.c:2748 Unable to push temporary Fast Path rule for mobile 00:21:6a:34:51:78 on AP 00:27:0d:e3:0e:a0

*apfMsConnTask_0: Feb 03 12:53:45.145: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:1d:e0:8b:92:7d to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 12:53:43.469: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:1d:e0:8b:92:7d to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 12:53:43.469: %PEM-1-ADDNPURULE1: pem_api.c:2748 Unable to push temporary Fast Path rule for mobile 00:1d:e0:8b:92:7d on AP 00:27:0d:e3:2a:b0

*apfMsConnTask_0: Feb 03 12:53:43.351: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 00:1d:e0:8b:92:7d to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

*apfMsConnTask_0: Feb 03 12:53:43.351: %PEM-1-ADDNPURULE1: pem_api.c:2748 Unable to push temporary Fast Path rule for mobile 00:1d:e0:8b:92:7d on AP 00:27:0d:e3:2a:b0

*apfMsConnTask_0: Feb 03 12:53:42.891: %APF-1-MOBILE_ADD_FAILED: apf_policy.c:285 Unable to add mobile 80:60:07:96:a7:f1 to PEM module.

-Traceback:  1012f1d4 1079b490 107a40c8 1060b06c 10cc7978 112774ec

4 REPLIES
Hall of Fame Super Gold

WiSM - Primary WLC APs are suddenly associating/deassociating be

Did you try to configure the primary/secondary controllers on a per-WAP basis?

New Member

Re: WiSM - Primary WLC APs are suddenly associating/deassociatin

Hi Leo,

Current loading is primary 101 AP secondary 22 AP. This is a campus environment with around 8 WiSM. This controller as a max 1600 users out of 8000+ users base on the positioning of the 101 APs..

Cisco Employee

WiSM - Primary WLC APs are suddenly associating/deassociating be

#configure both ip and WLC name for primary and secondary, if not already.

#disable 'AP fallback' on WLCs to stop AP bouncing between WLCs.

#check spanning tree.

New Member

WiSM - Primary WLC APs are suddenly associating/deassociating be

Hello to all,

Did you find at the end what was the cause which generate the problem and the messages???

The WLC or something on the network and hte messages were the consequence???

Many Thanks for a feedback

Omar

3532
Views
0
Helpful
4
Replies
CreatePlease to create content