Network Router User Manual

This command will replace the 1.1.1.1 virtual interface address, which shows up itself as the
DHCP server, with the actual DHCP server IP address that you defined on the interface or in
the override option of the WLAN.
Q. We have a couple of Access Control Servers (ACS) that authenticate
the wireless clients associated to wireless LAN controllers (WLCs). One
ACS acts as a primary authenticating server and the other as a failover
server. If the primary server fails, the controller falls back to secondary
for authenticating the wireless clients. Once the primary server comes
back up, the controller does not fallback to the primary server. Why?
A. This is an expected behavior. These steps occur when a client is authenticated through the
WLC in multiple ACS deployments:
Upon boot up, the WLC determines the active ACS.1.
When this active ACS does not respond to the RADIUS request from the WLC, the
WLC searches and makes a failover to the secondary ACS.
2.
Even when the primary ACS comes back up, the WLC does not fall back to it until
the ACS to which the controller is currently authenticating fails.
3.
In such cases, reboot the WLC in order for the WLC to identify the primary ACS again and
fallback to it. This fallback does not occur immediately after reboot. It might take some time.
Q. I am not able to Secure Shell (SSH) into the wireless LAN controller
(WLC) when I use SecureCRT SSH v2 SH client software. My controller
runs version 4.0.179.8.
A. This is because of Cisco bug ID CSCsc98897 (
registered customers only
) . SecureCRT works
only with controllers that run version 4.0.206.0. Upgrade your controller to this version.
Then, you can use SecureCRT SH client in order to SSH into the controller.
Q. How do I encrypt the configuration files on the WLC?
A. Encryption of configuration files is already available in controllers. If you choose from the
controller GUI, Commands > Upload File, you see the Configuration File Encryption
checkbox.
You can force the file to be encrypted through WCS in this way. From the WCS GUI, choose
Configure controller > commands > Upload/Download Commands> download config
from the controller. At this time, you see this message: Note: Configuration file encryption
key is not set. Downloading configuration file will fail if encryption key is needed. Please
click here to setup encryption. Basically, you can force the WCS to always set an
encryption key for controller configurations. Encryption is not enabled by default, but it can
be enabled both in WLC and WCS, as needed.
NetPro Discussion Forums − Featured Conversations
Networking Professionals Connection is a forum for networking professionals to share questions, suggestions,
and information about networking solutions, products, and technologies. The featured links are some of the
most recent conversations available in this technology.
NetPro Discussion Forums − Featured Conversations for Wireless