Информационное Руководство для Cisco Cisco 2000 Series Wireless LAN Controller
Q. My 2006 WLC shows that different channels have been assigned to
the registered access points (APs). However, when I scan with Aironet
Desktop Utility (ADU) or Netstumbler, all the APs are in the same
channel (1). What is the reason?
the registered access points (APs). However, when I scan with Aironet
Desktop Utility (ADU) or Netstumbler, all the APs are in the same
channel (1). What is the reason?
A. This problem occurs when these registered APs are in close proximity with each other.
You might be hitting Cisco bug ID CSCsg03420 (
You might be hitting Cisco bug ID CSCsg03420 (
registered customers only
) .
Q. When I issue the ipconfig/all command at the command prompt of my
PC, a different DHCP server address shows. It shows 1.1.1.1 as the
DHCP server IP address. This is the virtual interface IP address of the
WLC and not the DHCP server address. Why is this shown as the DHCP
server?
PC, a different DHCP server address shows. It shows 1.1.1.1 as the
DHCP server IP address. This is the virtual interface IP address of the
WLC and not the DHCP server address. Why is this shown as the DHCP
server?
A. This is because the 1.1.1.1 virtual interface address acts as a DHCP proxy for the original
DHCP server. If you want to see the original DHCP server address at the output of the
ipconfig/all command, then disable the DHCP proxy feature in the WLC to which the client
is associated. This can be disabled with the config dhcp proxy disable command.
DHCP server. If you want to see the original DHCP server address at the output of the
ipconfig/all command, then disable the DHCP proxy feature in the WLC to which the client
is associated. This can be disabled with the config dhcp proxy disable command.
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.
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 WLC falls back to secondary for
authenticating the wireless clients. Once the primary server comes back
up, the WLC does not fallback to the primary server. Why?
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 WLC falls back to secondary for
authenticating the wireless clients. Once the primary server comes back
up, the WLC 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:
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.
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 WLC is currently authenticating fails.
the ACS to which the WLC 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.
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 WLC runs
version 4.0.179.8.
(WLC) when I use SecureCRT SSH v2 SH client software. My WLC runs
version 4.0.179.8.
A. SecureCRT works only with WLCs that run version 4.0.206.0 or later. Upgrade your WLC
to this version. Then, you can use SecureCRT SH client in order to SSH into the WLC.
to this version. Then, you can use SecureCRT SH client in order to SSH into the WLC.