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

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

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

客户端无法连接

[复制链接]
发表于 2020-1-17 15:24:15 | 显示全部楼层 |阅读模式
0可用金钱
我2楼和23楼分别有一套无线设备ssid一样
我有一部分用户从2楼到了23楼后无法连接,控制器上有如下日志,请问这是什么问题


*Dot1x_NW_MsgTask_0: Jan 15 07:04:45.622: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 08, expected 00 00 00 00 00 00 00 09
*Dot1x_NW_MsgTask_0: Jan 15 07:04:45.621: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 07, expected 00 00 00 00 00 00 00 09
*Dot1x_NW_MsgTask_0: Jan 15 06:04:17.229: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 05, expected 00 00 00 00 00 00 00 06
*Dot1x_NW_MsgTask_0: Jan 15 05:03:58.839: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 15 01:03:27.948: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 13, expected 00 00 00 00 00 00 00 14
*Dot1x_NW_MsgTask_0: Jan 15 01:03:27.945: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 12, expected 00 00 00 00 00 00 00 14
*Dot1x_NW_MsgTask_0: Jan 15 00:03:17.802: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 10, expected 00 00 00 00 00 00 00 11
*Dot1x_NW_MsgTask_0: Jan 15 00:03:17.801: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 0f, expected 00 00 00 00 00 00 00 11
*Dot1x_NW_MsgTask_0: Jan 14 22:02:35.967: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 0c, expected 00 00 00 00 00 00 00 0d
*Dot1x_NW_MsgTask_0: Jan 14 22:02:35.966: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 0b, expected 00 00 00 00 00 00 00 0d
*Dot1x_NW_MsgTask_0: Jan 14 18:03:16.094: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 80:0c:67:de:d1:b2 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_0: Jan 14 18:03:15.685: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 06, expected 00 00 00 00 00 00 00 07
*Dot1x_NW_MsgTask_0: Jan 14 17:11:03.964: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 38:53:9c:79:b1:5c - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 14 17:11:03.963: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 38:53:9c:79:b1:5c - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 14 17:11:03.090: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client d8:1c:79:56:ca:9f - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Jan 14 16:45:43.296: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client c0:e8:62:58:d5:b8 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Jan 14 16:44:58.081: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 20:da:22:42:0f:73 - got 00 00 00 00 00 00 00 09, expected 00 00 00 00 00 00 00 0a
*Dot1x_NW_MsgTask_0: Jan 14 16:43:41.359: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client f0:a3:5a:59:76:83 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 14 16:02:36.739: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 14 16:02:36.738: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 34:42:62:5c:d0:55 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 14 15:43:07.896: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client fc:2a:9c:46:cd:51 - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 14 15:43:07.588: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client dc:08:0f:23:53:c9 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Jan 14 15:43:07.213: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:452 Invalid replay counter from client 0e:3b:29:6e:2f:ea - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04

  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
发表于 2020-1-18 15:39:38 | 显示全部楼层
如果是两套无线网络的话,可以看看配置有什么不同。使用的AP有什么不同?
如果可以的话,可以在WLC开启debug,观察客户端连接失败时的具体原因是什么。
命令:debug client <mac-add of client>
eg:debug client 00:11:22:33:44:55

关闭debug:debug disable-all
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
发表于 2020-1-19 11:20:30 | 显示全部楼层
Log的意思是说四次握手中M2/M4里的replay counter值错误。
可以升级一下客户端驱动看看是否能改善。

另外不同无线设备但相同SSID这个设计有可能会导致客户端漫游从而导致问题。
可以尝试用不同的SSID。
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
 楼主| 发表于 2020-6-29 09:14:17 | 显示全部楼层
这个问题是开启了802.1R引起的,只要关闭fasttransition就好了
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
 楼主| 发表于 2020-6-29 09:17:16 | 显示全部楼层
这个问题是开启了802.11R引起的,关闭fasttransition就好了
  • 1
  • 2
  • 3
  • 4
  • 5
  • 1
  • 2
  • 3
  • 4
  • 5
平均得分0 (0 评价)
您需要登录后才可以回帖 思科 CCO 登录 | 思科 CCO 注册   

本版积分规则

Archiver | 思科社区  

GMT+8, 2020-9-18 17:49 , Processed in 0.091061 second(s), 38 queries .

京ICP备11014401号-17

© 2020 思科系统.版权所有 重要声明 | 保密声明 | 隐私权政策 | 商标 |

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