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

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

   思科 CCO 登录 推荐
 找回密码
 立即注册

搜索
热搜: 邮件服务器
查看: 510|回复: 4

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: %DOT1