取消
显示结果 
搜索替代 
您的意思是: 
cancel
1502
查看次数
0
有帮助
4
回复

客户端无法连接

我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
4 条回复4

Rps-Cheers
VIP Collaborator VIP Collaborator
VIP Collaborator
如果是两套无线网络的话,可以看看配置有什么不同。使用的AP有什么不同?
如果可以的话,可以在WLC开启debug,观察客户端连接失败时的具体原因是什么。
命令:debug client
eg:debug client 00:11:22:33:44:55
关闭debug:debug disable-all
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rps-Cheers | If it solves your problem, please mark as answer. Thanks !

HaifengLi
Cisco Employee
Cisco Employee
Log的意思是说四次握手中M2/M4里的replay counter值错误。
可以升级一下客户端驱动看看是否能改善。
另外不同无线设备但相同SSID这个设计有可能会导致客户端漫游从而导致问题。
可以尝试用不同的SSID。

这个问题是开启了802.1R引起的,只要关闭fasttransition就好了

这个问题是开启了802.11R引起的,关闭fasttransition就好了
入门指南

使用上面的搜索栏输入关键字、短语或问题,搜索问题的答案。

我们希望您在这里的旅程尽可能顺利,因此这里有一些链接可以帮助您快速熟悉思科社区:





认可您的同行
快捷链接