Cisco Cisco 2000 Series Wireless LAN Controller
R E V I E W D R A F T — C I S C O C O N F I D E N T I A L
9
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.193.5
OL-xxxxx-xx
Important Notes
Important Notes
This section describes important information about the controllers and access points.
Resetting the Configuration on 2006 Controllers
If you wish to reset the configuration to factory defaults on a 2006 controller, perform one of the
following:
following:
•
From the controller GUI, cchoose Commands > Reset to Factory Default > Reset.
•
From the controller CLI (after system bootup and login), enter clear config. Then after the
configuration has been cleared, enter reset system without saving the current configuration.
configuration has been cleared, enter reset system without saving the current configuration.
•
From the controller console (after system bootup), enter Recover-Config at the User Name prompt.
Caution
Do not attempt to reset the controller’s configuration by choosing Option 5, Clear Config, from the boot
menu unless you have successfully upgraded to the _ER.aes image on Cisco.com. See CSCsg18356 in
the
menu unless you have successfully upgraded to the _ER.aes image on Cisco.com. See CSCsg18356 in
the
for more details.
Service Modules Supported in the Catalyst 6500 Series Switch
The Catalyst 6500 Series Switch chassis can support up to five Cisco WiSMs without any other service
module installed. If one or more service modules are installed, the chassis can support up to a maximum
of four service modules (WiSMs included).
module installed. If one or more service modules are installed, the chassis can support up to a maximum
of four service modules (WiSMs included).
Access Points Fail to Join Controllers If MTU Setting Is Less Than 1500
When the network path between access points and the controller is configured for an MTU size less than
1500, the controller does not receive join requests from access points in local mode. (MTU settings less
than 1500 are common when you use tunneling protocols such as IPsec VPN, GRE, and MPLS.) The
access point join request is larger than 1500 bytes, so the request is fragmented. The size of the first
fragment is 1500 bytes (including IP and UDP header) and the second fragment is 54 bytes (including
IP and UDP header).
1500, the controller does not receive join requests from access points in local mode. (MTU settings less
than 1500 are common when you use tunneling protocols such as IPsec VPN, GRE, and MPLS.) The
access point join request is larger than 1500 bytes, so the request is fragmented. The size of the first
fragment is 1500 bytes (including IP and UDP header) and the second fragment is 54 bytes (including
IP and UDP header).
Access points in REAP mode are not affected by this limitation, and the problem is resolved in the 4.0
release train because the LWAPP tunnel can reassemble up to 4 fragments. The problem occurs when all
four of these conditions exist on your network:
release train because the LWAPP tunnel can reassemble up to 4 fragments. The problem occurs when all
four of these conditions exist on your network:
•
Your controller runs release 3.2 or earlier
•
Your controller is configured for Layer 3 LWAPP
•
The network path MTU between the access point and the controller is less than 1500 bytes
•
The access point is in local access point (LAP) mode (not REAP mode)