无线认证请求过多造成WLC-Radius拥堵崩溃现象就及解决方法

简介:

Logging现象:

RADIUS server 10.200.1.X:1812 deactivated on WLAN 1

RADIUS auth-server 10.200.1.X:1812 unavailable

RADIUS auth-server 10.200.1.X:1812 available

RADIUS server 10.200.1.X:1812 activated on WLAN 1

……

RADIUS server 10.200.1.X:1812 activated on WLAN 1

RADIUS server 10.200.1.X:1812 deactivated on WLAN 1

RADIUS auth-server 10.200.1.X:1812 unavailable

RADIUS server 10.200.1.X:1812 failed to respond to request

RADIUS auth-server 10.200.1.X:1812 available

RADIUS server 10.200.1.X:1812 activated on WLAN 1

RADIUS server 10.200.1.X:1812 deactivated on WLAN 1

RADIUS auth-server 10.200.1.X:1812 unavailable

RADIUS server 10.200.1.103:1812 failed to respond to request

RADIUS auth-server 10.200.1.103:1812 available

RADIUS server 10.200.1.X:1812 activated on WLAN 1

RADIUS server 10.200.1.X:1812 deactivated on WLAN 1

RADIUS auth-server 10.200.1.X:1812 unavailable

RADIUS server 10.200.1.X:1812 failed to respond to request

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

AAA Authentication Failure for UserName:xxxxxx\sap_pm User Type: WLAN USER

……<<<<大量重复出现traps logs;

*Dot1x_NW_MsgTask_2:  18:15:30.003: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:861 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 28:b2:bd:b7:01:42  <<<<大量重复出现Message Logs;

235934jg85wgk4llpr7nk7.png

Look for:

  • High Retry: First Request ratio (should be no more than 10%)

  • High Reject: Accept ratio

  • High Timeout: First Request ratio (should be no more than 5%)

解决方法:

·      "Excessive 802.1X Authentication Failures" is selected in the WLC's global Client Exclusion Policies.

·         Client exclusion is enabled in the WLAN's advanced settings.

·         Client exclusion timeout is set to at least 120 seconds.60 to 300 seconds

235755hcfr9wzfu77w7bga.png

235807s88ufa1iuf58e38l.png

000507pl5xfjfy74hyy5yc.png

000644f11f3c8mr8w2088w.png

 Disable Aggressive Failover, which does not allow a single misbehaving supplicant to cause the WLC to fail between the RADIUS servers.

  Use the CLI command:  “config radius aggressive-failover disable”

To see the current state, use:  show radius summary

and look for the line "Aggressive Failover" near the top of the output. There is no GUI option for this setting.

Configure Fast Secure Roaming for your clients.


·         Make sure that Microsoft Windows EAP clients use Wi-Fi Protected Access 2 (WPA2)/Advanced Encryption Standard (AES) so they can use Opportunistic Key Caching (OKC).

·         If you can segregate Apple iOS clients to their own WLAN, then you can enable 802.11r on that WLAN.

·         Enable Cisco Centralized Key Management (CCKM) for any WLAN that supports 792x phones (but do not enable CCKM on any Service Set Identifier (SSID) that supports Microsoft Windows or Android clients, because they tend to have problematic CCKM implementations).

·         Enable Sticky Key Caching (SKC) for any EAP WLAN that supports the Macintosh Operating System (MAC OS) X and/or Android clients.
Refer to 
802.11 WLAN Roaming and Fast-Secure Roaming on CUWN for more information.                  http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/116493-technote-technology-00.html

Note:  Monitor your WLC Pairwise Master Key (PMK) cache usage at peak times with the show pmk-cache all command. If you reach your maximum PMK-cache size, or get close to it, then you will probably have to disable SKC.

 

参考链接:

https://supportforums.cisco.com/discussion/11702421/getting-disconnected-randomly-5508-controller-3300-series-laps

http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/118703-technote-wlc-00.html

https://supportforums.cisco.com/discussion/11827081/radius-server-failed-respond-request 


转载自小伙伴鱼排饭的博客











本文转自Grodd51CTO博客,原文链接:http://blog.51cto.com/juispan/2066738,如需转载请自行联系原作者

相关文章
|
5月前
|
缓存 网络协议 Linux
网络的救命稻草:重传机制如何确保数据顺利传输?
在网络传输中,数据的可靠性和稳定性一直是一个重要的挑战。幸运的是,重传机制应运而生,为我们解决了这个问题。本文将深入探讨重传机制在网络中的应用和工作原理。我们将介绍TCP中最常见的超时重传和快速重传,以及SACK和D-SACK这两种高级重传机制。了解这些机制如何工作可以帮助我们更好地理解数据传输的可靠性和稳定性的保障。
123 1
网络的救命稻草:重传机制如何确保数据顺利传输?
|
9月前
|
存储 缓存 API
案例23-服务出现频繁掉线情况
服务出现频繁掉线情况
171 0
|
10月前
|
数据采集 监控 前端开发
网络抖动对重复提交的影响与解决方案
网络抖动对重复提交的影响与解决方案
245 0
|
安全 关系型数据库 MySQL
网站被攻击导致服务器CPU百分之百 无法访问的终极解决办法
公司的官方网站从春节前无缘无故就出现连接数据库异常的现象,由于以前也出现过,再加上没多久逢年过节,也就没有太在乎这个情况,仅仅试着重新启动了网站数据库。逢年过节的时候我发现了有一些不太对,网站数据库只有一打开没多久就宕掉。检查服务器里的资源,发现服务器的内存被占满,CPU达到百分之100就连远程连接都越来越巨慢至极,因此开展对该网站被攻击的问题解决。
417 0
网站被攻击导致服务器CPU百分之百 无法访问的终极解决办法
|
小程序 安全 专有云
排查指南 | mPaaS 小程序提示“网络不给力”时该如何排查?
从此,Android 应用打开 mPaaS 小程序,告别“网络不给力”
3153 0
排查指南 | mPaaS 小程序提示“网络不给力”时该如何排查?
|
网络安全 网络架构 开发者
网络稳定的第二道屏障: 带外网络DHCP异常排查方案
网络管理通常可分为带外管理(out-of-band)和带内管理(in-band)两种管理模式,带外网络是通过独立于数据网络之外的专用管理通道对机房网络设备(路由器、交换机、防火墙等)、服务器设备(小型机、服务器、工作站)以及机房电源系统进行集中化整合管理的网络集中管理系统。当企业网络建成后,网络上会传输各种企业的业务数据,如果业务网络出现问题,就需要通过带外网络来进行故障的排查,保障系统的稳定。
网络稳定的第二道屏障: 带外网络DHCP异常排查方案
|
数据采集 安全 网络安全
由大量爬虫请求引起的带宽占满事件分析和解决方案
2018年2月24日晚,卓见云某客户网站公网出流量突然爆发性增长,导致带宽被占满,事故发现后紧急提升了SLB的带宽,但提升后的带宽仍然被流量占满(原带宽15M,提升至35M)。由于事故发生在非黄金访问时段,正常流量不会这么大,加上其他现象,怀疑是遭到了网络攻击。
6049 0