Cisco Cisco 2000 Series Wireless LAN Controller

Página de 32
 
14
Release Notes for Cisco Wireless LAN Controllers and Cisco Aironet Lightweight Access Points for Releases 3.2.78.4 and 3.2.78.0
OL-31336-01
  Important Notes
2006 Image Not Supported for 3504 Series Wireless LAN Controllers
The 2006 wireless LAN controller image is supported for use with only Cisco 2000 Series Wireless LAN 
Controllers. Do not install the 2006 image on a 3504 Series Wireless LAN Controller. Otherwise, errors 
may occur. Install only the 3504 image on a 3504 Series Wireless LAN Controller.
Running a 3504 Image on a Cisco 2000 Series Wireless LAN Controller
It is possible to run a 3504 wireless LAN controller image on a Cisco 2000 Series Wireless LAN 
Controller, but Cisco Aironet 1130 series lightweight access points, Cisco Aironet 1200 series 
lightweight access points, and Cisco Aironet 1240 series lightweight access points will not be able to 
connect with the wireless LAN controller.
Cisco Lightweight Access Points Fail to Join Cisco Wireless LAN Controllers
When a Cisco lightweight access point is connected to a terminal server port and reboots because of a 
join failure or timeout, this sequence repeats forever until the Cisco lightweight access point returns to 
the boot prompt and stays there. This condition occurs when there is no telnet session to the Cisco 
lightweight access point console port, and when the wireless LAN controller is not responding to the 
Cisco lightweight access point join response.
Workaround: Disconnect the Cisco lightweight access point console port from the terminal server. 
Reprogram the wireless LAN controller to have it respond to the Cisco lightweight access point join 
request. Power cycle the Cisco lightweight access point to force a restart.
Upgrading External Webauth
When upgrading wireless LAN controllers from operating system release 2.0 or 2.2.127.4 to release 3.0, 
update the external webauth configuration as follows:
Instead of using a preauth ACL, the network manager must configure the external web server IP 
address using the CLI command:
config custom-web ext-webserver add <IP address> 
(where <IP address> is the address of any web server that performs external web authentication.)
Then, the network manager must use the new login_template which is included below: 
<html>
<head>
<meta http-equiv="Pragma" content="no-cache"> <meta HTTP-EQUIV=”Content-Type” 
CONTENT="text/html; charset=iso-8859-1"> <title>Web Authentication</title> <script>
function submitAction(){
var link = document.location.href;
var searchString = "redirect=";
var equalIndex = link.indexOf(searchString);
var redirectUrl = "";
var urlStr = "";
if(equalIndex > 0) {
equalIndex += searchString.length;
urlStr = link.substring(equalIndex);
if(urlStr.length > 0){