This started happening after

dhearin01 · ‎02-19-2015

This started happening after a tech worked on our APs. We have Cisco Aironets 1401s. User will be in their remote desktop session, then it will disconnect and keep trying to reconnect, the user retains and ip address while this is happening. I'm going to post the message log. There seems to be a lot of the invalid radio type 0 received, not sure if that might have something to do with--

*emWeb: Feb 19 13:11:59.268: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 13:11:40.195: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 19 13:01:48.452: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*dot1xMsgTask: Feb 19 12:59:13.444: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*emWeb: Feb 19 12:55:03.954: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:53:09.837: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 19 12:52:31.004: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*emWeb: Feb 19 12:48:26.733: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:secant. Service-Type is not present or it doesn't allow READ/WRITE permission..
*emWeb: Feb 19 12:48:02.401: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:secan. Service-Type is not present or it doesn't allow READ/WRITE permission..
*emWeb: Feb 19 12:45:30.002: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:45:12.061: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:43:33.303: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:25:58.931: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:22:16.635: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask5: Feb 19 12:14:13.201: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 8 for client 40:78:6a:15:90:0f is already in use by ac:b5:7d:54:21:9a for AP 00:08:30:8e:36:20 slot 0 vap 2
*emWeb: Feb 19 12:05:53.865: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:05:45.691: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:05:34.743: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:05:25.097: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 12:04:47.014: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_3: Feb 19 11:52:42.198: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 20:a2:e4:d9:36:eb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask7: Feb 19 11:28:13.677: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask7: Feb 19 11:28:09.275: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for 00:08:30:71:16:40 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask2: Feb 19 11:26:53.106: #LWAPP-3-RD_ERR9: spam_lrad.c:11182 APs 00:08:30:71:16:40 country code changed from () to (US )
*spamApTask2: Feb 19 11:26:53.106: #LWAPP-3-RD_ERR7: spam_lrad.c:10505 The system detects an invalid country code () for AP 00:08:30:71:16:40
*Dot1x_NW_MsgTask_0: Feb 19 10:52:37.387: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 19 10:31:59.280: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:admin. Service-Type is not present or it doesn't allow READ/WRITE permission..
*emWeb: Feb 19 10:04:46.797: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask3: Feb 19 09:52:54.244: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 1 for client bc:85:56:e4:aa:4f is already in use by 60:be:b5:0c:5b:52 for AP e8:ed:f3:1a:eb:70 slot 0 vap 2
*Dot1x_NW_MsgTask_0: Feb 19 09:52:01.142: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_7: Feb 19 09:52:00.827: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 19 09:39:47.986: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 09:39:26.748: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 09:38:53.982: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 19 09:05:02.987: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*emWeb: Feb 19 08:49:24.483: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 08:49:08.176: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 08:14:56.036: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 19 08:14:45.008: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 19 08:11:56.639: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*dot1xMsgTask: Feb 19 08:09:42.635: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_2: Feb 19 08:06:42.999: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 78:31:c1:06:2a:c2 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_0: Feb 18 16:44:10.649: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 18 15:44:58.192: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_4: Feb 18 15:43:19.042: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:f6:43:c0:16:b4 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 18 15:41:17.403: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 48:43:7c:bd:e0:20 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 18 15:01:40.965: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_3: Feb 18 14:43:43.583: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 20:a2:e4:d9:36:eb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 18 14:42:34.439: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 18 14:25:06.629: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 00:08:22:7c:13:0e - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 03
*spamApTask4: Feb 18 13:47:21.800: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask4: Feb 18 13:47:20.228: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for e8:ed:f3:1a:ee:f0 in the database. Prev.0x1045d800; Cur.0x1045d800
*dot1xMsgTask: Feb 18 13:45:19.963: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 20:10:7a:c1:7c:0e may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Feb 18 13:42:18.256: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Feb 18 13:42:18.252: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_3: Feb 18 13:42:17.000: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 64:9a:be:a0:de:8b - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask3: Feb 18 13:40:24.549: #LWAPP-3-INVALID_AID: spam_api.c:1433 The system has received invalid association identifier (0) for station 78:4b:87:c5:82:da on the Flex AP e8:ed:f3:1a:f2:80 slot 0 vap 2
*spamApTask3: Feb 18 13:40:21.534: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask3: Feb 18 13:40:18.356: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for e8:ed:f3:1a:f2:80 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask3: Feb 18 13:40:17.796: #LWAPP-3-STATIC_IP_ERR: spam_lrad.c:36639 Configured static IP Address is not valid for AP e8:ed:f3:1a:f2:80
*RRM-DCLNT-2_4: Feb 18 13:37:39.996: #RRM-3-RRM_LOGMSG: rrmLrad.c:3885 RRM LOG: Client not found: 20:10:7A:A7:77:49
*dot1xMsgTask: Feb 18 13:29:11.007: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 18:cf:5e:dc:3c:6b may be using an incorrect PSK
*spamApTask3: Feb 18 13:12:14.316: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 5 for client 0c:84:dc:9e:09:e6 is already in use by b8:ee:65:a6:d1:4c for AP e8:ed:f3:1a:eb:70 slot 1 vap 1
*Dot1x_NW_MsgTask_7: Feb 18 12:47:14.990: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client bc:85:56:e4:aa:4f - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 18 12:10:39.252: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 00:61:71:db:44:1e - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*spamApTask4: Feb 18 11:48:26.053: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 2 for client b4:18:d1:04:db:80 is already in use by d4:f4:6f:ed:f5:58 for AP e8:ed:f3:1a:f2:80 slot 0 vap 2
*Dot1x_NW_MsgTask_6: Feb 18 11:41:24.172: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 18 11:41:23.650: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Feb 18 10:47:04.347: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b8:ee:65:a2:24:39 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 18 10:40:29.336: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 18 10:38:52.054: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d8:d1:cb:9a:76:28 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask7: Feb 18 10:27:19.521: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 19 for client c8:85:50:f1:5c:3e is already in use by 18:f6:43:c0:16:b4 for AP 00:08:30:71:1b:00 slot 0 vap 2
*Dot1x_NW_MsgTask_6: Feb 18 10:12:57.230: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c8:85:50:f1:5c:3e - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_7: Feb 18 09:46:56.445: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 18 09:40:17.560: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 18 09:21:17.681: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_7: Feb 18 08:40:08.749: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 18 08:17:41.648: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 18 08:13:27.204: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*RRM-DCLNT-2_4: Feb 17 17:07:07.255: #RRM-3-RRM_LOGMSG: rrmLrad.c:3885 RRM LOG: Client not found: 20:10:7A:A7:77:49
*Dot1x_NW_MsgTask_2: Feb 17 16:36:56.685: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 84:7a:88:60:76:42 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 17 14:52:19.393: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 14:51:42.334: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 14:51:17.601: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 14:50:41.447: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 14:38:06.988: #EMWEB-1-BUFFER_TOO_MANY: ews_net.c:535 Received too many Http buffers from a session. BufCount(65) > Max (64), BufLen= 15913. Aborting session.
*emWeb: Feb 17 14:38:06.960: #EMWEB-1-BUFFER_TOO_MANY: ews_net.c:535 Received too many Http buffers from a session. BufCount(65) > Max (64), BufLen= 15814. Aborting session.
*emWeb: Feb 17 14:38:06.945: #EMWEB-1-BUFFER_TOO_MANY: ews_net.c:535 Received too many Http buffers from a session. BufCount(65) > Max (64), BufLen= 15793. Aborting session.
*emWeb: Feb 17 14:38:06.929: #EMWEB-1-BUFFER_TOO_MANY: ews_net.c:535 Received too many Http buffers from a session. BufCount(65) > Max (64), BufLen= 15809. Aborting session.
*emWeb: Feb 17 14:38:06.913: #EMWEB-1-BUFFER_TOO_MANY: ews_net.c:535 Received too many Http buffers from a session. BufCount(65) > Max (64), BufLen= 15815. Aborting session.
*RRM-DCLNT-2_4: Feb 17 14:33:31.673: #RRM-3-RRM_LOGMSG: rrmLrad.c:3885 RRM LOG: Client not found: 20:10:7A:A7:77:49
*Dot1x_NW_MsgTask_6: Feb 17 14:30:36.906: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask7: Feb 17 14:07:04.797: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 13 for client 60:be:b5:6d:f6:b0 is already in use by 68:ae:20:68:4a:32 for AP 00:08:30:71:1b:00 slot 0 vap 2
*Dot1x_NW_MsgTask_0: Feb 17 13:35:28.697: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d8:d1:cb:9a:76:28 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 17 13:35:13.119: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b4:3a:28:cf:c9:56 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 17 13:35:13.079: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 34:23:ba:e3:5c:40 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask3: Feb 17 13:26:40.302: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask3: Feb 17 13:26:39.080: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for e8:ed:f3:1a:ee:f0 in the database. Prev.0x1045d800; Cur.0x1045d800
*Dot1x_NW_MsgTask_0: Feb 17 12:29:54.855: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_7: Feb 17 11:59:35.112: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 00:21:00:c8:84:0f - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*dot1xMsgTask: Feb 17 11:39:57.038: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 0c:84:dc:9e:0a:b8 may be using an incorrect PSK
*emWeb: Feb 17 11:23:02.923: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 11:22:49.855: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:32:16.356: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:30:19.003: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_3: Feb 17 10:27:23.333: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 20:a2:e4:d9:36:eb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 17 10:13:22.716: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:12:52.250: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:12:05.088: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:11:20.662: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:11:01.466: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:10:01.787: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:09:44.479: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:09:30.138: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:08:20.286: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:05:40.126: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:05:19.147: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:04:48.906: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 10:03:06.674: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:58:01.691: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:57:49.297: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:57:48.034: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 17 09:57:43.906: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 0c:84:dc:9d:f0:57 may be using an incorrect PSK
*emWeb: Feb 17 09:57:43.303: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:57:37.604: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:57:29.278: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:57:12.535: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:49:14.845: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:47:21.494: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:43:51.774: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:22:59.291: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 17 09:22:30.087: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask2: Feb 17 09:10:09.293: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask2: Feb 17 09:10:08.453: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for e8:ed:f3:1a:ee:f0 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask4: Feb 17 09:08:12.217: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: e8:ed:f3:1a:ee:f0
*Dot1x_NW_MsgTask_6: Feb 17 08:27:31.909: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_6: Feb 17 08:27:31.908: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_4: Feb 17 08:27:30.967: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:f6:43:c0:16:b4 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_3: Feb 17 08:25:31.068: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:db:e2:8a:13:83 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask5: Feb 17 08:14:34.495: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 10 for client 00:26:82:d3:ca:c9 is already in use by 80:e6:50:58:2f:17 for AP 00:08:30:8e:36:20 slot 0 vap 1
*Dot1x_NW_MsgTask_1: Feb 16 16:47:29.848: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 00:26:82:d3:ca:c9 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_7: Feb 16 16:18:55.444: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 16 15:18:27.101: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d8:d1:cb:9a:76:28 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*RRM-DCLNT-2_4: Feb 16 14:45:12.894: #RRM-3-RRM_LOGMSG: rrmLrad.c:3885 RRM LOG: Client not found: AC:81:12:BE:E2:02
*spamApTask6: Feb 16 14:18:19.291: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 14 for client ac:81:12:02:e2:23 is already in use by 18:f6:43:c0:16:b4 for AP 00:08:30:71:16:40 slot 0 vap 1
*dot1xMsgTask: Feb 16 13:52:03.353: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 0c:84:dc:9d:fa:fb may be using an incorrect PSK
*dot1xMsgTask: Feb 16 13:34:40.269: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Feb 16 13:23:25.754: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 6c:94:f8:aa:ff:de - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask5: Feb 16 13:23:19.460: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 9 for client 78:4b:87:c5:82:da is already in use by 18:f6:43:c0:16:b4 for AP 00:08:30:8e:36:20 slot 0 vap 2
*Dot1x_NW_MsgTask_7: Feb 16 13:09:52.763: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 4c:b1:99:4a:b6:af - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*dot1xMsgTask: Feb 16 12:58:01.125: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*dot1xMsgTask: Feb 16 11:48:11.698: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*emWeb: Feb 16 11:16:39.646: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_2: Feb 16 11:16:01.301: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 78:4b:87:c5:82:da - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 16 11:16:00.908: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b4:3a:28:cf:c9:56 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_2: Feb 16 11:16:00.784: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 10:ae:60:1f:ee:4a - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*dot1xMsgTask: Feb 16 10:40:38.618: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Feb 16 10:15:52.632: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_6: Feb 16 10:15:52.631: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_7: Feb 16 10:15:51.375: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 00:26:82:e1:e5:cf - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 16 09:15:49.538: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_2: Feb 16 09:15:49.485: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 78:4b:87:c5:82:da - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_3: Feb 16 09:15:49.437: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 20:a2:e4:d9:36:eb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Feb 16 09:15:18.310: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 70:de:e2:38:73:81 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*dot1xMsgTask: Feb 16 09:00:32.666: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*spamApTask4: Feb 16 08:30:32.127: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 1 for client f8:27:93:09:09:76 is already in use by 64:9a:be:a0:de:8b for AP e8:ed:f3:1a:f2:80 slot 0 vap 1
*Dot1x_NW_MsgTask_1: Feb 16 08:14:55.545: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:cf:5e:f1:3d:69 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_1: Feb 16 08:14:55.545: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:cf:5e:f1:3d:69 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*dot1xMsgTask: Feb 16 08:05:42.187: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 0c:84:dc:9e:0a:b8 may be using an incorrect PSK
*spamApTask2: Feb 13 17:02:39.701: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 7 for client 98:f0:ab:38:a2:e7 is already in use by 14:1a:a3:c3:33:61 for AP 00:08:30:8e:69:50 slot 0 vap 2
*Dot1x_NW_MsgTask_1: Feb 13 15:46:01.273: #DOT1X-3-INVALID_WPA_KEY_STATE: 1x_eapkey.c:2113 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client b8:ee:65:a2:27:f9
*Dot1x_NW_MsgTask_3: Feb 13 15:45:18.561: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 20:a2:e4:d9:36:eb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Feb 13 14:45:54.283: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 70:de:e2:38:73:81 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_3: Feb 13 14:44:49.953: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 20:a2:e4:d9:36:eb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*dot1xMsgTask: Feb 13 13:54:24.607: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Feb 13 13:45:25.561: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 64:9a:be:a0:de:8b - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Feb 13 13:05:56.463: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client e8:99:c4:71:81:f1 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_1: Feb 13 12:45:29.792: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:cf:5e:73:60:f1 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*dot1xMsgTask: Feb 13 12:45:14.647: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Feb 13 12:43:43.002: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:f6:43:c0:16:b4 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask5: Feb 13 10:43:01.860: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 3 for client 84:7a:88:60:76:42 is already in use by 5c:96:9d:ef:7a:bd for AP 00:08:30:8e:36:20 slot 0 vap 2
*emWeb: Feb 13 10:29:15.160: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 09:20:41.031: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:50:48.137: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:49:08.577: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_3: Feb 13 08:47:34.168: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:db:e2:8a:13:83 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_3: Feb 13 08:47:34.167: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:db:e2:8a:13:83 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*emWeb: Feb 13 08:36:57.301: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:36:50.216: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:36:47.426: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*sisfSwitcherTask: Feb 13 08:36:33.089: #LOG-3-Q_IND: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:36:32.619: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:36:21.893: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:36:00.574: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:33:45.606: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:31:12.548: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:29:40.658: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*iappSocketTask: Feb 13 08:29:26.820: #LOG-3-Q_IND: spam_api.c:924 The system detects an invalid slot identifier (2) - ; AP 00:08:30:8e:36:20[...It occurred 11 times.!]
*emWeb: Feb 13 08:29:20.264: #LWAPP-3-INVALID_SLOT: spam_api.c:924 The system detects an invalid slot identifier (2) - ; AP 00:08:30:8e:36:20
*emWeb: Feb 13 08:29:20.200: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:29:12.067: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:28:48.095: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:28:23.339: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:secant . Service-Type is not present or it doesn't allow READ/WRITE permission..
*emWeb: Feb 13 08:26:32.416: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:26:23.144: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:26:11.066: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:25:50.091: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:22:35.652: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:22:12.132: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:21:52.845: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:21:25.888: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 13 08:20:10.817: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 0c:84:dc:9e:0a:b8 may be using an incorrect PSK
*emWeb: Feb 13 08:19:25.800: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 13 08:17:49.793: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 0c:84:dc:9e:0a:b8 may be using an incorrect PSK
*emWeb: Feb 13 08:10:51.460: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 13 08:10:35.743: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_3: Feb 12 17:40:00.827: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:db:e2:8a:13:83 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_3: Feb 12 17:40:00.826: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:db:e2:8a:13:83 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_7: Feb 12 17:03:54.647: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 98:f0:ab:38:a2:e7 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_7: Feb 12 17:03:54.644: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 98:f0:ab:38:a2:e7 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 02
*spamApTask4: Feb 12 17:03:29.805: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 1 for client 98:f0:ab:38:a2:e7 is already in use by 80:e6:50:58:2f:17 for AP e8:ed:f3:1a:f2:80 slot 0 vap 2
*Dot1x_NW_MsgTask_7: Feb 12 16:35:07.315: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 12 16:21:11.735: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_0: Feb 12 15:34:50.233: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_6: Feb 12 15:34:20.994: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 12 14:56:10.736: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_2: Feb 12 14:33:58.770: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 8c:3a:e3:7c:08:1a - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_7: Feb 12 14:33:45.624: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 12 14:22:12.571: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 14:07:35.240: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 14:01:12.732: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 14:00:56.378: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:59:17.282: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:52:06.631: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:51:45.685: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:49:28.176: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:46:30.981: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:45:18.657: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:43:33.640: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:42:42.828: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:41:50.695: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_4: Feb 12 13:34:27.828: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:f6:43:c0:16:b4 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 12 13:31:06.571: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:29:29.765: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:19:11.758: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:18:29.002: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:16:30.975: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 13:05:37.348: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_4: Feb 12 13:01:13.210: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:cf:5e:1b:7e:44 - got 00 00 00 00 00 00 00 05, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_4: Feb 12 13:01:12.211: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:cf:5e:1b:7e:44 - got 00 00 00 00 00 00 00 04, expected 00 00 00 00 00 00 00 00
*Dot1x_NW_MsgTask_4: Feb 12 13:01:11.211: #DOT1X-3-INVALID_WPA_KEY_STATE: 1x_eapkey.c:2113 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client 18:cf:5e:1b:7e:44
*dot1xMsgTask: Feb 12 13:01:10.833: #DOT1X-3-CLIENT_NOT_FOUND: dot1x_msg_task.c:1318 Unable to process 802.1X 8 msg - client b8:ee:65:6b:30:8d not found
*Dot1x_NW_MsgTask_5: Feb 12 13:01:09.704: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b8:ee:65:6b:30:8d - got 00 00 00 00 00 00 00 05, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_5: Feb 12 13:01:08.704: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b8:ee:65:6b:30:8d - got 00 00 00 00 00 00 00 04, expected 00 00 00 00 00 00 00 00
*Dot1x_NW_MsgTask_5: Feb 12 13:01:07.705: #DOT1X-3-INVALID_WPA_KEY_STATE: 1x_eapkey.c:2113 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client b8:ee:65:6b:30:8d
*emWeb: Feb 12 12:53:39.119: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 12:53:21.397: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 12:46:15.638: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 12:36:45.214: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 12:36:19.801: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_7: Feb 12 12:34:22.611: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask4: Feb 12 12:33:53.831: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask4: Feb 12 12:33:53.705: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for e8:ed:f3:1a:f2:80 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask4: Feb 12 12:33:53.146: #LWAPP-3-STATIC_IP_ERR: spam_lrad.c:36639 Configured static IP Address is not valid for AP e8:ed:f3:1a:f2:80
*Dot1x_NW_MsgTask_0: Feb 12 11:32:40.046: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b4:18:d1:04:db:80 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_7: Feb 12 11:32:39.734: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 12 11:27:57.248: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 11:20:52.207: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 11:18:10.164: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 11:15:24.501: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 11:11:24.784: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 11:09:14.056: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 11:08:55.458: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 11:02:32.016: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:59:21.458: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:59:08.177: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:56:35.584: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:48:16.443: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_3: Feb 12 10:47:09.143: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f8:a9:d0:28:06:4b - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*emWeb: Feb 12 10:47:00.814: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_7: Feb 12 10:43:36.483: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 40:78:6a:15:90:0f - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 12 10:40:57.820: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:37:26.400: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:32:40.853: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_0: Feb 12 10:32:19.322: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 48:43:7c:bd:e0:20 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Feb 12 10:32:19.321: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 48:43:7c:bd:e0:20 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*emWeb: Feb 12 10:31:03.547: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:30:40.894: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:30:24.458: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:28:58.672: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:26:49.882: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:26:37.255: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 10:25:58.367: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask0: Feb 12 10:24:00.764: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask0: Feb 12 10:23:54.628: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for e8:ed:f3:1a:f2:80 in the database. Prev.0x1045d800; Cur.0x1045d800
*emWeb: Feb 12 10:18:25.254: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask5: Feb 12 10:12:27.643: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 11 for client d4:f4:6f:3d:fc:be is already in use by 14:1a:a3:c3:33:61 for AP 00:08:30:8e:36:20 slot 0 vap 2
*spamApTask1: Feb 12 10:09:59.235: #LWAPP-3-RD_ERR9: spam_lrad.c:11182 APs e8:ed:f3:1a:f2:80 country code changed from () to (US )
*spamApTask1: Feb 12 10:09:59.235: #LWAPP-3-RD_ERR7: spam_lrad.c:10505 The system detects an invalid country code () for AP e8:ed:f3:1a:f2:80
*spamApTask1: Feb 12 10:09:59.235: #LWAPP-3-RD_ERR9: spam_lrad.c:11182 APs e8:ed:f3:1a:f2:80 country code changed from () to (US )
*spamApTask1: Feb 12 10:09:59.235: #LWAPP-3-RD_ERR7: spam_lrad.c:10505 The system detects an invalid country code () for AP e8:ed:f3:1a:f2:80
*spamApTask2: Feb 12 10:08:07.516: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: c0:67:af:2a:f7:60
*emWeb: Feb 12 09:34:32.016: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_7: Feb 12 09:33:24.880: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client bc:85:56:e4:aa:4f - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 12 09:32:58.662: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 00:61:71:db:44:1e - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_4: Feb 12 09:32:22.072: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b8:c7:5d:8b:46:1c - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 12 09:31:46.100: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_7: Feb 12 09:31:45.731: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*emWeb: Feb 12 08:41:38.976: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 08:39:45.096: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 12 08:35:16.113: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Feb 12 08:30:54.619: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 40:78:6a:15:90:0f - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 00
*emWeb: Feb 12 08:20:10.225: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 08:19:58.358: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 08:19:42.262: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 08:19:20.449: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 12 08:18:22.103: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:secant. Service-Type is not present or it doesn't allow READ/WRITE permission..
*emWeb: Feb 12 08:18:15.423: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:secant. Service-Type is not present or it doesn't allow READ/WRITE permission..
*Dot1x_NW_MsgTask_0: Feb 11 17:26:11.606: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Feb 11 17:06:52.844: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client a8:86:dd:5b:8d:d6 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 00
*Dot1x_NW_MsgTask_6: Feb 11 15:26:03.762: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_6: Feb 11 15:26:03.761: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client d4:f4:6f:3d:fc:be - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_7: Feb 11 15:26:02.819: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_4: Feb 11 15:25:25.506: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:f6:43:c0:16:b4 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_4: Feb 11 15:25:25.505: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:f6:43:c0:16:b4 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_7: Feb 11 15:24:11.463: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 98:f0:ab:38:a2:e7 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 11 14:29:41.797: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client bc:f5:ac:e8:47:e0 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_7: Feb 11 14:25:16.549: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Feb 11 14:25:16.396: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:cf:5e:dc:20:e8 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_2: Feb 11 14:25:16.306: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 18:cf:5e:dc:1a:5a - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_5: Feb 11 14:23:56.001: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 48:d7:05:3d:3d:c5 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_5: Feb 11 14:23:55.999: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 48:d7:05:3d:3d:c5 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*dot1xMsgTask: Feb 11 13:26:52.188: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Feb 11 13:24:10.308: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:db:e2:8a:13:83 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_3: Feb 11 13:24:10.307: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:db:e2:8a:13:83 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_7: Feb 11 12:24:34.667: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*dot1xMsgTask: Feb 11 10:41:38.074: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client e8:99:c4:71:81:f1 may be using an incorrect PSK
*spamApTask2: Feb 11 10:40:49.539: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 9 for client 64:9a:be:a0:de:8b is already in use by bc:85:56:e4:b5:75 for AP 00:08:30:8e:69:50 slot 0 vap 2
*Dot1x_NW_MsgTask_7: Feb 11 10:23:25.208: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 80:00:6e:9a:39:17 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_3: Feb 11 10:22:06.341: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 20:a2:e4:d9:36:eb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*spamApTask6: Feb 11 10:14:53.327: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 1 for client b8:ee:65:a2:27:f9 is already in use by 18:f6:43:c0:16:b4 for AP 00:08:30:71:16:40 slot 0 vap 1
*emWeb: Feb 11 10:13:58.864: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask2: Feb 11 09:52:08.872: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 14 for client 18:cf:5e:6e:cc:ad is already in use by 20:a2:e4:d9:36:eb for AP 00:08:30:8e:69:50 slot 0 vap 1
*dot1xMsgTask: Feb 11 09:50:16.790: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*emWeb: Feb 11 09:30:09.989: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 11 09:29:54.752: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 11 09:29:34.594: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 11 09:28:27.359: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 11 09:28:06.049: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 11 09:26:23.091: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*Dot1x_NW_MsgTask_0: Feb 11 09:23:16.904: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c0:63:94:5c:d2:58 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Feb 11 09:21:52.129: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client b8:ee:65:6b:30:91 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_1: Feb 10 17:14:53.675: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 0c:84:dc:9d:fa:89 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*dot1xMsgTask: Feb 10 16:00:18.298: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*dot1xMsgTask: Feb 10 15:35:00.298: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*dot1xMsgTask: Feb 10 15:29:54.898: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*dot1xMsgTask: Feb 10 15:22:08.498: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*dot1xMsgTask: Feb 10 14:53:13.098: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Feb 10 14:52:30.299: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 94:35:0a:6f:46:9d - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*spamApTask2: Feb 10 14:49:13.952: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 13 for client dc:86:d8:9d:3d:aa is already in use by 70:de:e2:38:73:81 for AP 00:08:30:8e:69:50 slot 0 vap 2
*emWeb: Feb 10 14:45:09.482: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*dot1xMsgTask: Feb 10 14:25:15.078: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client 78:31:c1:06:2a:c2 may be using an incorrect PSK
*emWeb: Feb 10 14:17:09.939: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 14:16:35.595: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 14:14:58.093: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask5: Feb 10 14:07:44.245: #LWAPP-3-INVALID_AID2: spam_api.c:1455 Association identifier 3 for client 98:f0:ab:38:a2:e7 is already in use by d8:d1:cb:9a:76:28 for AP 00:08:30:8e:36:20 slot 0 vap 2
*emWeb: Feb 10 14:01:58.847: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 14:01:21.789: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 14:01:12.125: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 14:00:48.897: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 13:59:30.591: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:secant. Service-Type is not present or it doesn't allow READ/WRITE permission..
*emWeb: Feb 10 13:59:16.182: #EMWEB-3-LOGIN_FAILED: ews_auth.c:2104 Login failed for the user:secant. Service-Type is not present or it doesn't allow READ/WRITE permission..
*emWeb: Feb 10 12:19:44.206: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 12:18:33.871: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*emWeb: Feb 10 12:13:35.323: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask7: Feb 10 12:12:44.469: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask7: Feb 10 12:12:44.209: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for 00:08:30:71:1b:00 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask6: Feb 10 12:12:44.162: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask6: Feb 10 12:12:43.903: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for 00:08:30:71:16:40 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask5: Feb 10 12:12:43.651: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask5: Feb 10 12:12:43.391: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for 00:08:30:8e:36:20 in the database. Prev.0x1045d800; Cur.0x1045d800
*emWeb: Feb 10 12:12:41.679: #APF-3-INVALID_RADIO_TYPE: apf_api.c:37043 Invalid radio type 0 received.
*spamApTask2: Feb 10 12:12:39.492: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask2: Feb 10 12:12:39.227: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for 00:08:30:8e:69:50 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask4: Feb 10 12:12:00.293: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask4: Feb 10 12:11:59.519: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for 50:17:ff:f4:f4:c0 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask3: Feb 10 12:11:56.512: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask3: Feb 10 12:11:55.648: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for e8:ed:f3:1a:eb:70 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask0: Feb 10 12:11:51.127: #LWAPP-3-VENDOR_SPEC_ERR: spam_lrad.c:12853 The system has failed decoding vendor specific payload
*spamApTask0: Feb 10 12:11:50.243: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:116 The system could not release exclusive access of AP entry for 50:17:ff:f4:f3:20 in the database. Prev.0x1045d800; Cur.0x1045d800
*spamApTask4: Feb 10 12:11:29.677: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: 00:08:30:8e:36:20
*spamApTask7: Feb 10 12:11:29.477: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: 00:08:30:71:16:40
*spamApTask6: Feb 10 12:11:29.077: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: 00:08:30:71:1b:00
*spamApTask7: Feb 10 12:11:28.477: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: 50:17:ff:f4:f4:c0
*spamApTask7: Feb 10 12:11:24.678: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: e8:ed:f3:1a:eb:70
*spamApTask3: Feb 10 12:11:20.877: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: 00:08:30:8e:69:50
*spamApTask7: Feb 10 12:11:19.677: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6101 Did not receive heartbeat reply; AP: 50:17:ff:f4:f3:20
*nim_t: Feb 10 12:09:37.520: #SIM-3-PORT_UP: sim.c:11289 Physical port 1 is up!.
*fp_main_task: Feb 10 12:09:37.272: #CNFGR-3-INV_COMP_ID: cnfgr.c:2945 Invalid Component Id : Unrecognized (94) in cfgConfiguratorInit.
*ipv6SocketTask: Feb 10 12:09:19.643: #LOG-3-Q_IND: sisf_shim_utils.c:316 Internal error, NULL entry in sisf_sw_policy_get_cfg_ptr[...It occurred 3 times.!]
*fp_main_task: Feb 10 12:09:19.638: #SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, NULL entry in sisf_sw_policy_get_cfg_ptr
*fp_main_task: Feb 10 12:09:08.570: #MM-3-MEMBER_ADD_FAILED: mm_dir.c:1197 Could not add Mobility Member. Reason: IP already assigned, Member-Count:1,MAC: 00:00:00:00:00:00, IP: 0.0.0.0
*mfpKeyRefreshTask: Feb 10 12:08:52.720: #SSHPM-3-NOT_INIT: bsnrandom.c:620 Random context not initialized
*fp_main_task: Feb 10 12:08:52.705: #CNFGR-3-INV_COMP_ID: cnfgr.c:2945 Invalid Component Id : Unrecognized (36) in cfgConfiguratorInit.

Rasika Nayanajith · ‎02-19-2015

What is the WLC software version you running ?

Rasika

dhearin01 · ‎02-19-2015

Software Version 7.4.130.0

Rasika Nayanajith · ‎02-19-2015

This started happening after a tech worked on our APs.

What type of work done on this ? any firmware upgrade of WLC ?

Have you tried with power cycle AP if this is happening in particular AP

HTH

Rasika

users continuously getting disconnected from session