Cisco Cisco 2106 Wireless LAN Controller

Page de 50
 
36
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 6.0.202.0
OL-31336-01
  Editing Configuration Files
RADIUS Servers and the Management VLAN
If a RADIUS server is on a directly connected subnet (with respect to the controller), then that subnet 
must be the management VLAN subnet.
RADIUS Servers
This product has been tested with CiscoSecure ACS 4.2 and later releases and works with any 
RFC-compliant RADIUS server.
Management Usernames and Local Netuser Names
Management usernames and local netuser names must be unique because they are stored in the same 
database. That is, you cannot assign the same name to a management user and a local netuser.
Using the Backup Image
The controller bootloader stores a copy of the active primary image and the backup image. If the primary 
image becomes corrupted, you can use the bootloader to boot with the backup image. 
With the backup image stored before rebooting, be sure to choose Option 2: Run Backup Image from 
the boot menu to boot from the backup image. Then, upgrade with a known working image and reboot 
the controller.
Home Page Retains Web Authentication Login with IE 5.x
Because of a caching problem in the Internet Explorer 5.x browser, the home page retains the web 
authentication login. To correct this problem, clear the history or upgrade your workstation to Internet 
Explorer 6.x.
Ad-Hoc Rogue Containment
Client card implementations may mitigate the effectiveness of ad-hoc containment.
Changing the Default Values of SNMP Community Strings
The controller has commonly known default values of “public” and “private” for the read-only and 
read-write SNMP community strings. Using these standard values presents a security risk. Therefore, we 
strongly advise that you change these values. See the Cisco Wireless LAN Controller Configuration 
Guide, Release 6.0,
 for configuration instructions. In addition, restore of config backup could result with 
re-enabling default communities or snmp communities disabled with incorrect privileges. You should 
manually reconfigure these snmp communities in this situation. SNMP configuration should be reviewed 
after config restore on a new WLC (from defaults).