Essentially we'd configure the WLC's to send RADIUS accounting info to the NAC appliance, so that it knows the user had already been authenticated, and therefore, doesn't prompt him/her to login again.
We have centralized wireless & ACS solutions, but local NAC appliances at each remote location.
While it sounds good in theory, we think this solution has some serious scalability issues.
We have 150 AP's per WiSM logical unit, (300 total per WiSM blade); that number will be a lot higher when we migrate to WiSM2.
I just don't see how the NAC appliance will be able to handle all these RADIUS accounting messages when we have hundres of AP's & thousands of wireless users getting on the network.
Has anyone done something similar?
Could you please share how you made your solution scalable?
We are moving! Please use WLCCA Forum for updates and discussions
[toc:faq] Wireless LAN Controller (WLC) Config Analyzer Download Click
here to Download To request access, send an e-mail to
email@example.com. Please include your Cisco.com userna...
[toc:faq] IntroductionHere is the step by step process that we have to
take care of while converting LWAPP to IOS and then vice versa..LWAPP to
IOSThe hardware used = 1141 AP (make sure we are using the right
[toc:faq] Introduction AnyConnect Secure Mobility Client 3.0: Network
Access Manager & Profile Editor on Windows Summary Use the Cisco
AnyConnect Network Access Manager Profile Editor to build custom
profiles for the AnyConnect Secure Mobility Client. App...