请选择 进入手机版 | 继续访问电脑版

设为首页 收藏本站
思科社区 关注
思科社区

搜索
热搜: 邮件服务器
查看: 1134|回复: 6

WLC3504+AP1815I的诡异问题,手机连接不丢包,笔记本电脑就丢包

[复制链接]
发表于 2019-8-30 21:53:24 | 显示全部楼层 |阅读模式
6可用金钱
WLC3504+AP1815I的诡异问题,手机连接不丢包,笔记本电脑就丢包

版本是8.5.131,今天用笔记本电脑连接同个wifi,同个ap,手机长ping网关,不会丢包,延迟10ms左右,属于正常情况,但是笔记本电脑换了两台都是大量丢包,就算不丢包时候也有一两个600ms左右延迟,图片如下,哪位大佬有遇到类似情况,可以指点一下吗?不胜感激

wlc的日志如下:
(Cisco Controller) >show logging

Logging to Logger Queue :
- Logging of system messages to Logger Queue :
- Effective Logging Queue filter level.......... errors
- Number of Messages recieved for logging :
- Emergency severity............................ 0
- Alert Severity................................ 0
- Critical Severity............................. 0
- Error Severity................................ 248
- Warning Severity.............................. 2423
- Notice Severity............................... 363
- Information Severity.......................... 3153
- Debug Severity................................ 189
- Total messages recieved....................... 6376
- Total messages enqueued....................... 244
- Total messages dropped........................ 6132
Logging to buffer :
- Logging of system messages to buffer :
- Logging filter level.......................... errors
- Number of system messages logged.............. 247
- Number of system messages dropped.............
- Number of Messages dropped due to Facility .... 06308
- Logging of debug messages to buffer ........... Disabled

--More-- or (q)uit
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
- Cache of logging  ............................. Disabled
- Cache of logging time(mins) ................... 10080
- Number of over cache time log dropped  ........ 0
Logging to console :
- Logging of system messages to console :
- Logging filter level.......................... disabled
- Number of system messages logged.............. 0
- Number of system messages dropped............. 6555
- Number of system messages throttled........... 0
- Logging of debug messages to console .......... Enabled
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
- Number of debug messages throttled............ 0
Logging to syslog :
- Syslog facility................................ local0
- Logging of system messages to syslog :
- Logging filter level.......................... errors
- Number of system messages logged.............. 247
- Number of system messages dropped............. 6308
- Logging of debug messages to syslog ........... Disabled
- Number of debug messages logged............... 0

--More-- or (q)uit
- Number of debug messages dropped.............. 0
- Number of remote syslog hosts.................. 0
- syslog over tls................................ Disabled
- syslog over ipsec.............................. Disabled
- ipsec profile inuse for syslog................. none
  - Host 0.......................................
  - Host 1.......................................
  - Host 2.......................................
Logging of Debug messages to file :
- Logging of Debug messages to file.............. Disabled
- Number of debug messages logged................ 0
- Number of debug messages dropped............... 0
Logging of traceback............................. Enabled
- Traceback logging level........................ errors
Logging of source file informational............. Enabled
Timestamping of messages.........................
- Timestamping of system messages................ Enabled
- Timestamp format.............................. Date and Time
- Timestamping of debug messages................. Enabled
- Timestamp format.............................. Date and Time

Logging buffer (247 logged, 6308 dropped)


--More-- or (q)uit
*emWeb: Aug 30 21:50:48.249: %CLI-3-LOGIN_FAILED: cliutil.c:708 Login failed. User:cisco, Service type:-8. Username/Password length must be between 3 and 128 characters.
*spamApTask7: Aug 30 18:32:32.773: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 d4:c9:3c:78:e8:20:  DTLS connection closed forAP  192:168:45:22 (5256), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*spamReceiveTask: Aug 30 18:05:34.173: %LWAPP-3-WLAN_ERR2: spam_lrad.c:37683 The system is unable to find WLAN 4 to be deleted; AP b0:8b:cf:55:a9:60
*spamReceiveTask: Aug 30 18:05:34.173: %LWAPP-3-WLAN_ERR2: spam_lrad.c:37683 The system is unable to find WLAN 4 to be deleted; AP b0:8b:cf:0e:a3:00
*spamReceiveTask: Aug 30 18:05:34.172: %LWAPP-3-WLAN_ERR2: spam_lrad.c:37683 The system is unable to find WLAN 4 to be deleted; AP a0:93:51:44:13:20
*Dot1x_NW_MsgTask_6: Aug 30 17:21:36.811: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 17:16:39.667: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*spamApTask7: Aug 30 17:00:54.841: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 d4:c9:3c:78:e8:20:  DTLS connection closed forAP  192:168:45:22 (5256), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*Dot1x_NW_MsgTask_4: Aug 30 16:46:17.532: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 16:42:41.914: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 16:40:42.699: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 16:36:58.155: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 16:34:13.914: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 16:30:28.776: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 16:27:39.774: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 16:25:38.576: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 16:21:04.443: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 16:20:38.457: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 16:16:59.666: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 16:14:48.749: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 16:12:37.633: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 16:07:47.427: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 16:06:00.312: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK

--More-- or (q)uit
*Dot1x_NW_MsgTask_6: Aug 30 16:00:48.690: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 15:58:31.027: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 15:52:36.559: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 15:50:36.551: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 15:46:59.347: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 30 15:38:38.091: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 30 15:16:03.094: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_2: Aug 30 15:05:30.954: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client dc:ef:ca:49:51:7a - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_6: Aug 30 15:03:50.751: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*spamApTask7: Aug 30 14:52:59.680: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 d4:c9:3c:78:e8:20:  DTLS connection closed forAP  192:168:45:22 (5256), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*Dot1x_NW_MsgTask_6: Aug 30 14:47:42.954: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 14:44:17.254: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 14:39:32.806: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 14:34:49.350: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 30 14:30:45.566: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 30 14:17:37.086: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 14:15:16.053: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 30 14:10:31.405: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 13:59:19.560: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 13:55:46.917: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 13:47:41.729: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 13:37:23.041: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 13:31:21.432: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK

--More-- or (q)uit
*apfMsConnTask_1: Aug 30 13:25:43.696: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for clientdc:08:0f:1c:f6:ff. Can't do preauth
*Dot1x_NW_MsgTask_5: Aug 30 12:46:59.639: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client f0:db:e2:9a:dd:cd - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Aug 30 12:34:55.030: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 12:22:11.741: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client a4:17:31:fa:3f:be may be using an incorrect PSK
*spamApTask7: Aug 30 11:29:06.961: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 d4:c9:3c:78:e8:20:  DTLS connection closed forAP  192:168:45:22 (5256), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*Dot1x_NW_MsgTask_1: Aug 30 11:28:27.792: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 1c:36:bb:bf:25:31 may be using an incorrect PSK
*apfMsConnTask_4: Aug 30 10:58:08.292: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for client68:ef:43:c3:43:0a. Can't do preauth
*Dot1x_NW_MsgTask_1: Aug 30 10:51:57.098: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 1c:36:bb:bf:25:31 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 30 10:47:00.302: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client b4:c0:f5:12:00:13 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_6: Aug 30 10:27:30.823: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 44:59:e3:61:ea:76 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 30 10:27:01.069: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 1c:36:bb:bf:25:31 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 10:20:01.142: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 44:59:e3:61:ea:76 may be using an incorrect PSK
*Dot1x_NW_MsgTask_6: Aug 30 10:06:52.461: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 44:59:e3:61:ea:76 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 09:47:48.519: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 30 09:27:03.215: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 30 09:16:10.211: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client bc:75:74:e0:d4:8b may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 09:09:52.932: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 30 09:05:48.552: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 09:04:28.018: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 08:55:22.131: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 30 08:44:53.528: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 30 07:53:31.872: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client b4:c0:f5:12:00:13 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_3: Aug 30 07:53:04.466: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client b4:c0:f5:12:00:13 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02

--More-- or (q)uit
*Dot1x_NW_MsgTask_3: Aug 30 07:53:04.439: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client b4:c0:f5:12:00:13 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_4: Aug 30 07:46:09.867: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 18:42:53.065: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 18:29:15.821: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 18:07:38.549: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 17:12:42.998: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 15:53:56.478: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 15:46:58.326: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 70:47:e9:b4:f7:db - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Aug 29 15:41:15.076: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 74:d2:1d:93:cd:89 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_3: Aug 29 15:34:32.105: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 15:31:03.429: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 15:30:00.549: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 15:27:41.102: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 15:25:29.590: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 15:21:53.574: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 15:21:36.713: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 15:14:27.264: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 15:11:27.748: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 15:09:06.318: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 15:05:36.057: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 14:46:41.086: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 70:47:e9:b4:f7:db - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_4: Aug 29 14:12:52.997: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 7c:50:49:6a:24:84 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 13:49:03.019: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK

--More-- or (q)uit
*dot1xMsgTask: Aug 29 13:46:48.928: %DOT1X-3-WPA_SEND_STATE_ERR: 1x_kxsm.c:1724 Unable to send EAPOL-key msg  - invalid WPA state (2) - client b8:c3:85:96:0e:47
*Dot1x_NW_MsgTask_7: Aug 29 13:12:04.164: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 12:48:18.873: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 70:47:e9:b4:f7:db - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Aug 29 12:23:28.470: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e0:33:8e:e6:34:c1 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 29 12:16:01.561: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e0:33:8e:e6:34:c1 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 29 12:08:00.537: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e0:33:8e:e6:34:c1 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 11:57:42.049: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 29 11:52:35.891: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client f0:db:e2:9a:dd:cd - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_7: Aug 29 11:49:28.727: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 29 11:42:55.577: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 29 11:36:02.790: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 11:29:48.682: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client b8:c3:85:96:0e:47 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 29 11:28:06.130: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 10:50:11.531: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 10:46:36.497: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 70:47:e9:b4:f7:db - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_3: Aug 29 10:44:30.152: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 10:40:27.161: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 10:33:59.962: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 10:27:13.523: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client e4:0e:ee:6b:71:5b may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 10:24:48.720: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 50:29:f5:1d:e7:6f may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 10:21:24.806: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 50:29:f5:1d:e7:6f may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 10:17:57.322: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 50:29:f5:1d:e7:6f may be using an incorrect PSK
*Dot1x_NW_MsgTask_7: Aug 29 10:14:30.631: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 50:29:f5:1d:e7:6f may be using an incorrect PSK

--More-- or (q)uit
*Dot1x_NW_MsgTask_7: Aug 29 10:11:07.309: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 50:29:f5:1d:e7:6f may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 29 09:09:49.117: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*apfMsConnTask_0: Aug 29 08:38:05.475: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for clientdc:08:0f:1c:f6:ff. Can't do preauth
*Dot1x_NW_MsgTask_5: Aug 29 06:45:45.771: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 29 00:01:10.248: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:57:09.042: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:57:03.541: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 3c:f5:91:99:56:15 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_5: Aug 28 23:53:43.537: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:42:27.327: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:37:45.386: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 3c:f5:91:99:56:15 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_5: Aug 28 23:37:42.481: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:37:33.652: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 3c:f5:91:99:56:15 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_5: Aug 28 23:37:24.696: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 3c:f5:91:99:56:15 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_5: Aug 28 23:34:07.459: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:08:56.145: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:04:36.888: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 23:01:09.206: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 19:20:16.586: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 19:14:04.065: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 19:07:46.586: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 19:01:43.983: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 18:55:35.629: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 18:45:24.675: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK

--More-- or (q)uit
*Dot1x_NW_MsgTask_3: Aug 28 18:32:36.230: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 18:20:36.382: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 28 18:10:32.574: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*sisfSwitcherTask: Aug 28 17:44:34.056: %LOG-3-Q_IND: 1x_eapkey.c:452 Invalid replay counter from client 3c:cd:5d:97:e9:33 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01[...It occurred 2 times.!]
                                             *Dot1x_NW_MsgTask_3: Aug 28 17:40:39.721: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 3c:cd:5d:97:e9:33 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_3: Aug 28 16:45:55.148: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*spamApTask0: Aug 28 16:37:21.590: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 d4:c9:3c:3d:a0:40:  DTLS connection closed forAP  192:168:45:33 (5272), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*spamApTask0: Aug 28 16:37:18.222: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 00:ea:bd:dd:79:00:  DTLS connection closed forAP  192:168:45:32 (5256), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*spamApTask0: Aug 28 16:37:18.222: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: 00:ea:bd:dd:79:00
*spamApTask7: Aug 28 16:37:17.826: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 70:ea:1a:0e:11:e0:  DTLS connection closed forAP  192:168:45:31 (5264), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*spamApTask7: Aug 28 16:37:17.825: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: 70:ea:1a:0e:11:e0
*spamApTask2: Aug 28 16:37:11.478: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 d4:c9:3c:d3:40:00:  DTLS connection closed forAP  192:168:45:34 (5256), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*spamApTask2: Aug 28 16:37:11.478: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: d4:c9:3c:d3:40:00
*apfMsConnTask_0: Aug 28 16:34:57.417: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for clientdc:08:0f:1c:f6:ff. Can't do preauth
*Dot1x_NW_MsgTask_3: Aug 28 16:18:18.244: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client ec:d0:9f:a3:8d:eb may be using an incorrect PSK
*spamApTask6: Aug 28 16:00:58.640: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 70:6d:15:3e:a0:e0:  DTLS connection closed forAP  192:168:45:38 (5256), Controller: 192:168:45:253 (5246) AP Message Timeout
*spamApTask6: Aug 28 16:00:58.640: %CAPWAP-3-MAX_RETRANSMISSIONS_REACHED: capwap_ac_sm.c:7623 Max retransmissions reached on AP(70:6d:15:3e:a0:e0),message (CAPWAP_CONFIGURATION_UPDATE_REQUEST
),number of pending messages(4)
*Dot1x_NW_MsgTask_2: Aug 28 13:19:34.374: %LOG-3-Q_IND: spam_lrad.c:13376 APs 70:6d:15:3e:a0:e0 country code changed from (UX) to (CN )
*spamApTask7: Aug 28 13:19:27.377: %LWAPP-3-RD_ERR9: spam_lrad.c:13376 APs 70:6d:15:3e:a0:e0 country code changed from (UX) to (CN )
*nim_t: Aug 28 13:04:10.011: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 12:57:21.545: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 12:57:13.304: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.

--More-- or (q)uit
*nim_t: Aug 28 12:55:56.138: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 12:55:47.897: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 12:54:30.731: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 12:54:23.519: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*RRM-DCLNT-2_4: Aug 28 11:53:20.172: %RRM-3-RRM_LOGMSG: rrmLrad.c:5108 RRM LOG: Client not found: 00B:70:94:88:0B
*apfMsConnTask_6: Aug 28 11:52:50.365: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for client00:db:70:94:88:0b. Can't do preauth
*spamApTask7: Aug 28 11:51:22.461: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 a8:b4:56:3c:86:20:  DTLS connection closed forAP  192:168:45:47 (5248), Controller: 192:168:45:253 (5246) AP Message Timeout
*spamApTask7: Aug 28 11:51:22.461: %CAPWAP-3-MAX_RETRANSMISSIONS_REACHED: capwap_ac_sm.c:7623 Max retransmissions reached on AP(a8:b4:56:3c:86:20),message (CAPWAP_CONFIGURATION_UPDATE_REQUEST
),number of pending messages(2)
*spamApTask7: Aug 28 11:41:48.805: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 a8:b4:56:3c:86:20:  DTLS connection closed forAP  192:168:45:47 (5248), Controller: 192:168:45:253 (5246) AP Message Timeout
*spamApTask7: Aug 28 11:41:48.805: %CAPWAP-3-MAX_RETRANSMISSIONS_REACHED: capwap_ac_sm.c:7623 Max retransmissions reached on AP(a8:b4:56:3c:86:20),message (CAPWAP_CONFIGURATION_UPDATE_REQUEST
),number of pending messages(2)
*spamApTask6: Aug 28 11:41:31.349: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 70:ea:1a:0e:03:80:  DTLS connection closed forAP  192:168:45:46 (5272), Controller: 192:168:45:253 (5246) Echo Timer Expiry
*spamApTask6: Aug 28 11:41:31.349: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: 70:ea:1a:0e:03:80
*nim_t: Aug 28 11:04:18.081: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 11:04:09.840: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 11:02:52.674: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 11:02:45.462: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 11:01:27.267: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 11:01:20.054: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 11:00:02.888: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 10:59:54.647: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 10:58:37.481: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.

--More-- or (q)uit
*nim_t: Aug 28 10:58:29.240: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 10:57:12.074: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 10:57:03.832: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 10:55:46.666: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 10:55:38.425: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 10:54:21.259: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 10:54:13.018: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 10:52:33.216: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 10:52:18.801: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 10:51:11.924: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*nim_t: Aug 28 10:51:03.683: %SIM-3-PORT_DOWN: sim.c:13911 Physical port 3 is down!.
*nim_t: Aug 28 10:48:44.774: %SIM-3-PORT_UP: sim.c:13902 Physical port 3 is up!.
*Dot1x_NW_MsgTask_5: Aug 28 10:41:46.578: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 10:37:00.147: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 10:18:24.368: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 28 10:03:52.971: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*apfMsConnTask_4: Aug 28 10:00:45.663: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for client00:db:70:94:88:0b. Can't do preauth
*Dot1x_NW_MsgTask_0: Aug 28 10:00:31.834: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 28 09:56:27.455: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*Dot1x_NW_MsgTask_0: Aug 28 09:52:57.590: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client d0:16:b4:2e:7f:a8 may be using an incorrect PSK
*apfMsConnTask_0: Aug 28 07:11:55.736: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for client00:db:70:94:88:0b. Can't do preauth
*Dot1x_NW_MsgTask_5: Aug 28 00:17:26.694: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 28 00:13:59.407: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK

--More-- or (q)uit
*Dot1x_NW_MsgTask_5: Aug 28 00:10:13.674: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 3c:f5:91:99:56:15 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 27 18:54:35.265: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 04:4f:4c:a2:5a:49 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 27 18:44:00.117: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 04:4f:4c:a2:5a:49 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 27 18:43:43.674: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 04:4f:4c:a2:5a:49 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_4: Aug 27 18:11:23.894: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 18:06:25.165: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 17:58:45.366: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 27 17:57:44.866: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 1c:36:bb:bf:25:31 may be using an incorrect PSK
*Dot1x_NW_MsgTask_1: Aug 27 17:56:08.067: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 04:4f:4c:a2:5a:49 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 17:55:11.733: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 0c:70:4a:df:7d:14 may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 27 17:53:10.733: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client c4:98:80:84:b9:0b may be using an incorrect PSK
*spamApTask6: Aug 27 17:53:06.568: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 70:6d:15:3e:a0:e0:  DTLS connection closed forAP  192:168:45:38 (5256), Controller: 192:168:45:253 (5246) AP Message Timeout
*spamApTask6: Aug 27 17:53:06.568: %CAPWAP-3-MAX_RETRANSMISSIONS_REACHED: capwap_ac_sm.c:7623 Max retransmissions reached on AP(70:6d:15:3e:a0:e0),message (CAPWAP_CONFIGURATION_UPDATE_REQUEST
),number of pending messages(2)
*Dot1x_NW_MsgTask_1: Aug 27 17:52:50.302: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 1c:36:bb:bf:25:31 may be using an incorrect PSK
*apfReceiveTask: Aug 27 17:50:22.933: %LOG-3-Q_IND: spam_lrad.c:13376 APs 70:6d:15:3e:a0:e0 country code changed from (UX) to (CN )
*spamApTask7: Aug 27 17:50:06.337: %LWAPP-3-RD_ERR9: spam_lrad.c:13376 APs 70:6d:15:3e:a0:e0 country code changed from (UX) to (CN )
*spamApTask6: Aug 27 17:38:02.838: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 70:6d:15:3e:a0:e0:  DTLS connection closed forAP  192:168:45:38 (5256), Controller: 192:168:45:253 (5246) AP Message Timeout
*spamApTask6: Aug 27 17:38:02.838: %CAPWAP-3-MAX_RETRANSMISSIONS_REACHED: capwap_ac_sm.c:7623 Max retransmissions reached on AP(70:6d:15:3e:a0:e0),message (CAPWAP_CONFIGURATION_UPDATE_REQUEST
),number of pending messages(4)
*Dot1x_NW_MsgTask_1: Aug 27 17:33:30.312: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 74:d2:1d:93:cd:89 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 00
*Dot1x_NW_MsgTask_3: Aug 27 17:16:43.418: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client c4:98:80:84:b9:0b may be using an incorrect PSK
*Dot1x_NW_MsgTask_3: Aug 27 17:08:45.172: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client c4:98:80:84:b9:0b may be using an incorrect PSK

--More-- or (q)uit
*Dot1x_NW_MsgTask_3: Aug 27 16:47:57.460: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 70:47:e9:b4:f7:db - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_4: Aug 27 16:46:01.050: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 16:35:16.183: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 7c:50:49:6a:24:84 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 16:33:16.372: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 16:28:49.777: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 7c:50:49:6a:24:84 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 16:28:10.502: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 14:57:49.127: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 14:45:19.720: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 14:23:37.884: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 14:07:40.800: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_4: Aug 27 14:00:57.535: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 90:b0:ed:5b:a3:94 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 27 13:48:26.426: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client f0:db:e2:9a:dd:cd - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_3: Aug 27 13:48:03.374: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 70:47:e9:b4:f7:db - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_5: Aug 27 13:46:03.328: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 30:52:cb:6f:06:dd may be using an incorrect PSK
*apfMsConnTask_0: Aug 27 12:01:32.034: %APF-3-PREAUTH_FAILURE: apf_80211.c:14698  There is no PMK cache entry for clientdc:08:0f:1c:f6:ff. Can't do preauth
*Dot1x_NW_MsgTask_5: Aug 27 11:59:58.418: %DOT1X-3-INVALID_WPA_KEY_STATE: 1x_eapkey.c:2905 Received EAPOL-key message while in invalid state (4) - version 1, type 3, descriptor 2, client 3c:cd:5d:32:c8:fd
*Dot1x_NW_MsgTask_1: Aug 27 11:34:01.234: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 1c:36:bb:bf:25:31 may be using an incorrect PSK
*Dot1x_NW_MsgTask_5: Aug 27 10:49:05.919: %DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:729 Client 20:a6:80:dc:b4:d5 may be using an incorrect PSK
*DHCP Client Task: Aug 27 10:47:50.394: %DHCP-3-BIND_SRPORT_ERR: dhcp_support.c:395 Binding service port for getting IP Address using DHCP failed.
*spamApTask1: Aug 27 10:47:45.397: %LWAPP-3-STATIC_IP_ERR: spam_lrad.c:55633 Configured static IP Address is not valid for AP d4:78:9b:61:42:e0


附件: 您需要 思科 CCO 登录 才可以下载或查看,没有帐号?思科 CCO 注册
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
 楼主| 发表于 2019-8-31 09:29:40 | 显示全部楼层
有大佬帮忙嘛
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
发表于 2019-9-2 18:06:53 | 显示全部楼层
1. 确认客户端是否有倾向性,看是否是客户端的问题
2. show ap auto-rf查看是否有干扰,问题是出在2.4Ghz还是5Ghz
3. 记录丢包的时间点,对比查看WLC和AP的该时间点的logging, 看是否有相同的log重复出现
4. debug client + 无线空间抓包和有线抓包(AP和WLC)进行分析
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
 楼主| 发表于 2019-9-2 21:38:48 | 显示全部楼层
haifeli 发表于 2019-9-2 18:06
1. 确认客户端是否有倾向性,看是否是客户端的问题
2. show ap auto-rf查看是否有干扰,问题是出在2.4Ghz ...

谢谢大佬,我测试一下,终于有人回复了
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
发表于 2019-9-9 08:18:06 | 显示全部楼层
升级到85140再观察看看是否有这个现象
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
发表于 2019-9-24 19:04:19 | 显示全部楼层
物理网线先去检查一下。。。
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
 楼主| 发表于 2019-10-31 13:02:34 | 显示全部楼层
sunbin03351 发表于 2019-9-9 08:18
升级到85140再观察看看是否有这个现象

升级到85.151解决了,谢谢各位
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
您需要登录后才可以回帖 思科 CCO 登录 | 思科 CCO 注册   

本版积分规则

Archiver | 思科社区  

GMT+8, 2020-2-23 04:06 , Processed in 0.107436 second(s), 45 queries .

京ICP备09041801号-187

版权所有 :copyright:1992-2019 思科系统  重要声明 | 保密声明 | 隐私权政策 | 商标 |

快速回复 返回顶部 返回列表