Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco 4400 Series Wireless LAN Controllers

Release Notes for Cisco Wireless LAN Controllers and Mesh Access Points for Release 4.1.191.24M-Mesh

Downloads

Table Of Contents

Release Notes for Cisco Wireless LAN Controllers and Mesh Access Points for Release 4.1.191.24M-Mesh

Contents

Important Notes

Hardware Features

RAP vs. MAP Functionality

Software Features and Enhancements

Software Images

Operational Notes

System Requirements

Upgrade Compatibility Matrix

Upgrading to this Software Release

Upgrade Path to Release 4.1.191.24M

Mandatory Boot Variable Update for Networks with 1520s

Software Upgrade Procedure

Converting Indoor Access Points to Mesh Access Points (1130AG, 1240AG)

Changing MAP and RAP Roles for Indoor Mesh Access Points (1130AG, 1240AG)

Converting Indoor Mesh Access Points to Non-Mesh Lightweight Access Points (1130AG, 1240AG)

Caveats

Open Caveats

Resolved Caveats

Closed Caveats

If You Need More Information

Troubleshooting

Related Documentation

Obtaining Documentation, Support, and Security Guidelines

Copyright © 2008 Cisco Systems, Inc. All rights reserved.


Release Notes for Cisco Wireless LAN Controllers and Mesh Access Points for Release 4.1.191.24M-Mesh

Last Revised: February 19, 2008

These release notes describe features, enhancements, and caveats in Release 4.1.191.24M.

Release 4.1.191.24M is compatible with Release 4.2 of the Cisco Wireless Control System (WCS) and is supported on the following Cisco Wireless LAN controller platforms:

•2100 series, 4400 series and Wireless Service Module (WiSM) for the Catalyst 6500 and 7600.

Release 4.1.191.24M supports full interoperability between the following indoor and outdoor mesh access points:

•Cisco Aironet 1500 (1505 and 1510) series and 1520 (1522) series outdoor access points

•Cisco Aironet 1130AG and 1240 AG series indoor access points

Note Release 4.1.191.24M also supports the following indoor non-mesh Cisco access points:

1000 series, 1100 series, 1130 series, 1200 series, 1230 series, 1240 series and 1300 series.

–1250 series access points are not supported on this release.

•If some or all of your indoor access points will be operating in an indoor Enterprise Mesh deployment or an upgrade to a mesh deployment is planned, install mesh release 4.1.191.24M on your controller.

•If your indoor access points will not be operating in an indoor mesh deployment and no future upgrade to a mesh deployment is planned, install non-mesh release 4.2 or later on your controller.

Caution If your network is operating with 1520s or you plan to install 1520s in your network, you must set the boot variable on the 1520 before upgrading from release 4.1.190.5 to 4.1.191.24M (or greater mesh release). This ensures the 1520 joins correctly (CSCsl70218). Refer to the "Mandatory Boot Variable Update for Networks with 1520s" section for specific configuration details.
Caution A downgrade to mesh releases 4.1.190.5 and 4.1.191.24M from non-mesh release 4.2 is not supported. Please see the "System Requirements" section for important software upgrade and compatibility details prior to upgrading to this release.

Note Refer to the Cisco Aironet 1500 Series Outdoor Mesh Access Point Hardware Installation Guide for details on the physical installation and initial configuration of the mesh access points at http://www.cisco.com/en/US/products/ps8368/tsd_products_support_series_home.html

Note Refer to "Monitoring Wireless Devices" (Chapter 6) in the Cisco Wireless Control System Configuration Guide, Release 4.2 for details on monitoring the mesh network (access points, links, statistics, alarms) at the following link: http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsmon.html

Note Refer to "Running Reports" (Chapter 14) in the Cisco Wireless Control System Configuration Guide, Release 4.2 for more details on mesh reports at the following link: http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsreps.html

Contents

These release notes contain the following sections:

•Important Notes

•System Requirements

•Converting Indoor Access Points to Mesh Access Points (1130AG, 1240AG)

•Caveats

•Troubleshooting

•Related Documentation

•Obtaining Documentation, Support, and Security Guidelines

Important Notes

This section describes information about new hardware and software features, and operational notes for Release 4.1.191.24M.

Note Release 4.1.191.24M provides extended wireless mesh features beyond those offered in the main Cisco Unified Wireless Network (CUWN) release base. Mesh-specific features are currently only available in the mesh release series.

Hardware Features

Release 4.1.191.24M supports the following indoor and outdoor wireless access points:

•The 1130 which is equipped with two simultaneously operating radios: a 2.4-GHz radio used for client access and a 5-GHz radio used for data backhaul.

–The 5-Ghz radio on the 1130 supports the following bands:5.15GHz, 5.25GHz, and 5.47GHz.

•The 1240 which is equipped with two simultaneously operating radios: a 2.4-GHz radio used for client access and a 5-GHz radio used for data backhaul.

–The 5-Ghz radio on the 1240 supports the following bands: 5.15GHz, 5.25GHz, and 5.47GHz.

•The 1505 which is equipped with a single 2.4-GHz radio that provides client access and data backhaul.

•The 1510 which is equipped with two simultaneously operating radios: a 2.4-GHz radio used for client access and a 5-GHz radio used for data backhaul and client access.

–The 5Ghz radio on the 1510 supports the following bands: 4.9GHz, 5.47GHz, and 5.8GHz.

•The 1522 which is equipped with two simultaneously operating radios: a 2.4-GHz radio used for client access and a 5-GHz radio used for data backhaul.

–The 5Ghz radio on the 1522 supports the following bands: 4.9GHz, 5.25 GHz, 5.47 GHz, and 5.8 GHz.

•Non-mesh indoor access points: 1000 series, 1100 series, 1200 series (excluding 1250) and 1300 series.

T

Table 1 Hardware Feature and Band Support by Platform 

Feature/Platform
AP1505
AP1510
AP1522
AP1130
AP1240

2.4 GHz Band

X

X

X

X

X

4.9 GHz Band

-

X

X

   

5.15 GHz Band

     

X

X

5.25 GHz Band

   

X

X

X

5.47 GHz Band

-

X1

X2

X

X

5.8 GHz Band

-

X3

X4

   

DOCSIS 2.0 Cable Modem (Optional)

-

-

X

   

Fiber Module (Optional)

-

-

X

-

-

External Battery Status

X

X

-

   

Internal Battery Status

-

-

X

   

LEDs

X5

X5

X

X

X

1 The 5.47 GHz band is used by the -E and -K regulatory domains for the 1510.

2 The 5.47 GHz band is used by the -A, -E, -K and -T regulatory domains for the 1522.

3 The 5.8 GHz band is used by the -A, -C, -N and -S regulatory domains for the 1510.

4 The 5.8 GHz band is used by the -A, -C, -N, -S and -T regulatory domains for the 1522

5 A detachable, removable Cisco LED indicator is available to detect power for the 1505 and 1510.


.

RAP vs. MAP Functionality

Access points within a mesh network operate as either a root access point (RAP) or a mesh access point (MAP).

Outdoor mesh access points (1505, 1510 and 1522) and indoor mesh access points (1130 and 1240) can function as either RAPs or MAPs. By default, all outdoor mesh access points functions as MAPs and must be configured to function as a RAP.

Note Indoor access points by default are in local (non-mesh) mode. Specific configuration on the controller is required to convert indoor access points from local to mesh (bridge) access points and to assign the specific mesh role (RAP or MAP). Refer to the "Converting Indoor Access Points to Mesh Access Points (1130AG, 1240AG)" section for details.

At least one access point within a mesh network must be configured to function as a RAP.

RAPs within the network have a wired connection to the controller and MAPs communicate among themselves and back to the RAP using wireless connections over the backhaul. MAPs use the AWPP protocol to determine the best path through the other mesh access points to the controller.

All the possible paths between the MAPs and RAPs form the wireless mesh that is used to carry traffic from wireless LAN clients connected to MAPs and to carry traffic from devices connected to MAP Ethernet ports.

Software Features and Enhancements

The following new software features and enhancements are introduced in Release 4.1.191.24M:

•Dynamic Frequency Selection (DFS) support with seamless channel change for 1520 series access points.

•Indoor Mesh functionality for Cisco Aironet 1130AG and 1240AG series access points.

–Refer to Table 2 for detailed feature summary.

–Refer to "Converting Indoor Access Points to Mesh Access Points (1130AG, 1240AG)" section for details on how to upgrade these access points.

•Expanded Mesh Alarms, Events, Reports and Statistics in Cisco WCS release 4.2

–Three new general parameters are available for monitoring mesh access points from Cisco WCS: AP Uptime, LWAPP Uptime, LWAPP Join Taken Time and Hop count. (Monitor > Access Points > AP Name > Mesh Statistics).

–The software version for a mesh access point is now appended with the letter M: 4.1.191.24M.

–Mesh Statistics are summarized under a three-tabbed Mesh Statistics panel rather than on a single page. Statistics are summarized under the following sub-panel headings: Bridging, Queue and Security. (Monitor > Access Points > AP Name > Mesh Statistics).

Mesh Statistics are reported when a child mesh access point authenticates or associates with a parent mesh access point. Statistic entries are removed and no longer displayed when the child mesh access point disassociates from the controller.

Queue statistics are new to release 4.1.191.24M and summarize the average and peak number of packets waiting in management, platinum, gold, silver and bronze queues. Packets dropped and queue size are also summarized. This information was previously only available on the controller.

–Label and color coding of mesh links to reflect Signal-to-Noise Ratio (SNR) and Packet Error Rate (PER) values on maps (Monitor > Maps > Map Name).

–Traps for Poor Link SNR, excessive parent changes, console login and MAC authorization failure.

–Alarms for excessive hop count, excessive child count, default bridge group name (BGN), excessive association, no alternate path, and too high or too low SNR levels.

Note Refer to "Monitoring Wireless Devices" (Chapter 6) in the Cisco Wireless Control System Configuration Guide, Release 4.2 for details on monitoring the mesh network (access points, links, statistics, alarms) at the following link: http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsmon.html

–New reports for mesh access points: AP Uptime (Report > Access Point), Client count by RAP (Reports > Client Report); and Mesh Packet Statistics and Mesh Stranded APs (Report > Mesh).

Note Refer to "Running Reports" (Chapter 14) in the Cisco Wireless Control System Configuration Guide, Release 4.2 for more details on the mesh reports at the following link: http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsreps.html

•MAC Authorization by a RADIUS Server (NEW CLI Command)

To provide an additional level of security in authorizing an access point's MAC address, the following command is introduced.

config mesh security radius-mac-filter [enable | disable]

Enabling this feature, provides backup authorization for an access point on the RADIUS server in case the MAC address is not found in the controller's MAC filter. In addition to enabling the command on the controller, the user must enter the MAC address of the access point as the username and password in the RADIUS server.

This feature is disabled by default.

•Available Channels for a Mesh Access Point (NEW CLI command)

A new command, show ap channel AP_Name displays the available channels for a specified mesh access point. An example of the command and its display is shown below. 

>show ap channel AP_Name


	802.11b/g Current Channel ................. 1

      Allowed Channel List......................1,2,3,4,5,6,7,8,9,10,11

      802.11a Current Channel ..................161

      Allowed Channel List...................... 36,40,44,48,52,56,60,64,100,

        .........................................104,108,112,116,132,136,140,

        .........................................149,153,157,161

•DFS Mesh Sector Change (NEW CLI command)

–config mesh full-sector-dfs {enable | disable}

This command instructs the mesh sector to do a coordinated channel change on the detection of a radar signal. For example, if a MAP detects radar, the MAP will notify the RAP, and the RAP will initiate a sector change.

All MAPs and the RAP belonging to that sector go to a new channel. This lowers the probability of MAPs stranding when radar is detected on the current backhaul channel, and no other valid parent is available as backup.

Each sector change causes the network to be silent for 60 seconds (as dictated by the DFS standard).

It is expected that after a half hour, the RAP will go back to the previously configured channel. This means that if radar is frequently observed on a RAP's channel, it is important to configure a different channel for that RAP, and additionally to exclude the radar affected channel at the controller using the following commands:

–config 802.11a disable AP_name

where AP_name refers to the RAP name

config 802.11a channel AP_name channel number

where channel number refers to the new channel number

config advanced 802.11a channel delete channel number

where channel number refers to the radar-bearing channel number

config 802.11a enable AP_name

Note The show network command displays status of DFS.

•Expanded DFS events and history information (NEW CLI commands)

Two new commands are introduced to provide additional DFS event and history information for mesh access points. Command structure and example displays are shown below.

–show mesh dfs history 

ap1520#show mesh dfs history

Channel 100 detects radar and is unusable (Time Elapsed: 18 day(s), 22 hour(s), 10 
minute(s), 24 second(s)).

Channel is set to 136 (Time Elapsed: 18 day(s), 22 hour(s), 10 minute(s), 24 
second(s)).

Channel 136 detects radar and is unusable (Time Elapsed: 18 day(s), 22 hour(s), 9 
minute(s), 14 second(s)).

Channel is set to 161 (Time Elapsed: 18 day(s), 22 hour(s), 9 minute(s), 14 
second(s)).

Channel 100 becomes usable (Time Elapsed: 18 day(s), 21 hour(s), 40 minute(s), 24 
second(s)).

Channel 136 becomes usable (Time Elapsed: 18 day(s), 21 hour(s), 39 minute(s), 14 
second(s)).

Channel 64 detects radar and is unusable (Time Elapsed: 0 day(s), 1 hour(s), 20 
minute(s), 52 second(s)).

Channel 104 detects radar and is unusable (Time Elapsed: 0 day(s), 0 hour(s), 47 
minute(s), 6 second(s)).

Channel is set to 120 (Time Elapsed: 0 day(s), 0 hour(s), 47 minute(s), 6 
second(s)).

–show mesh dfs channel channel number 

ap1520#show mesh dfs channel 104

Channel 104 is available

Time elapsed since radar last detected: 0 day(s), 0 hour(s), 48 minute(s), 11 
second(s).

Note A mesh access point must be associated with a controller to display the correct time elapsed value in both commands given that MAPs are time synchronized with controllers.

A summary of previously released mesh software features supported by each mesh access point is provided in Table 2.

Table 2 Cisco AP 1500 Series Feature Support Matrix for 4.1.191.24M 

Feature/Platform
AP1505
AP1510
AP1522
AP1130
AP1240

Mesh Network Functionality

   

Passive scanning-Access point searches for an alternative parent on its current backhaul.

X

X

X

X

X

Background Scanning-Access point searches for an alternative parent on any possible backhaul channel.

X

X

-

-

-

Optimal Parent Selection-Access point joins the best available parent.

X

X

X

X

X

Exclusion Listing-Access point avoids selecting as parent those access points which have a pattern of failing.

X

X

X

X

X

Radar-free Coordinated Sector-Access point notifies parent when radar is detected on the channel so an alternative channel can be employed by the sector.

X

X

X

X

X

Dynamic Frequency Selection-Alternative channel is selected when radar is detected in regulated bands.

-

X

X

X

X

Synchronized Channel Change-Parent advises children of intended channel change.

X

X

X

X

X

Reliable Link Layer, Extended Retries-Transmissions that do not succeed will extend the number of retry attempts in an effort to improve reliability.

X

X

X

X

X

Reliable Link Layer, Secondary Backhaul Radio-A secondary backhaul radio is utilized as a temporary path for traffic that cannot be sent on the primary backhaul due to intermittent interference.

-

X

-

-

-

Passive Beaconing-Log messages from an access point that cannot connect are relayed through other access points to the controller.

X

X

X

X

X

Network Services Functionality

   

Ethernet Bridging-Traffic is bridged from hosts connected to a wired port.

X

X

X

X

X

Containment of Bridged Multicast Traffic- There are two types of multicast, Bridged and LWAPP, and each is governed by a different mechanism. LWAPP multicast is managed by the LWAPP methods at the controller, and bridged multicast is governed by the multicast network settings. Multicast flows (e.g. video camera broadcasts) originating in the network from a MAP Ethernet port terminate only at the RAP Ethernet (In mode Multicast). In this mode, multicast flows are not transmitted throughout the mesh network, thereby reducing bandwidth requirements.

X

X

-

-

-

Universal Access-Radio used for backhaul traffic provides access for client traffic

X

X

-

-

-

Support for Workgroup Bridges-Allows multiple wired hosts to connect to the wireless network through a workgroup bridge.

X

X

-

-

-

Multiple Queues for Backhaul Traffic-Extends client traffic prioritization to the backhaul traffic.

X

X

X

X

X

Static Call Admission Control (CAC)-Ensures sufficient bandwidth is available in a mesh sector before serving new T-SPEC client call requests.

-

X

-

-

-

Mesh Security

   

EAP Authentication-Restricts mesh node access to approved, authenticated access points. EAP-FAST authentication provides secure authentication and encryption key management.

X

X

X

X

X

Applications

   

High-speed Roaming-Roam speeds of up to 70 mph are supported for Cisco Compatible Extension v4 clients.

-

X

-

-

-


Software Images

Table 3 lists the names of the images associated with this release.

Table 3 Software Images Associated with Release 4.1.191.24M

Products
4.1.191.24M and Related Software Images
Access Point
 
Image
Boot Image
 

1130

c1130-k9w9-tar.124-3g.JMB (mesh, bridge mode)

c1130-k9w8-tar.124-3g.JMB (non-mesh, local mode)

c1130-boot.m.124-3g.JMB

 

1240

c1240-k9w9-tar.124-3g.JMB (mesh, bridge mode)

c1240-k9w8-tar.124-3g.JMB (non-mesh, local mode)

c1240-boot.m.124-3g.JMB

 

1505

VxWorks

VxWorks

 

1510

VxWorks

VxWorks

 

1520

c1520-k9w9-tar.124-3g.JMB

c1520-boot-m.124-3g.JMB

WLC-4400

AIR-WLC4400-K9-4-1-191-24M-MESH.aes

WLC-2100

AIR-WLC2100-K9-4-1-191-24M-MESH.aes

WiSM

SWISMK9-4-1-191-24-MESH.aes

WCS

WCS-STANDARD-K9-4.2.62.0.exe

Note For release 4.1.191.24M, Cisco WCS is only supported on Windows Server 2003.

WCS Navigator

NAVIGATOR-K9-1.1.62.exe

Note For release 4.1.191.24M, Cisco WCS Navigator is only supported on Windows Server 2003.


Operational Notes

This section describes information about important operational notes and changes to existing controller CLI and GUI for Release 4.1.191.24M.

New controller GUI windows and CLI commands are summarized under the"Software Features and Enhancements" section of this release note.

Configuration Database Setting of 2048 Recommended for Large Mesh Deployments

In large mesh deployments, increasing the configuration database setting to 2048 is highly recommended. The configuration database total includes MAC filter entries, access point MIC and SSC entries; dynamic interfaces, management users, and local net users. You can increase the configuration database to 2048 using the config database size 2048 command; and in the controller GUI, at the following Security > AAA > General window (CSCsg88704).

Bridge MAC Filter Config Status Shown in Error

The show network command mistakenly displays a status for the Bridge MAC Filter Config parameter. This parameter is not a configurable option in release 4.1.191.24M (CSCsk40572).

Limit Bridge Group Names to 11 Characters

Entering more than 11 characters into the bridge group name (BGN) field in the controller GUI mesh access point configuration window (Wireless > All APs > AP-Name > Mesh) generates an error message. This is also true when assigning bridge group names for mesh access points in Cisco WCS (Configure > Access Points > AP_name) and the config ap bridgegroupname set groupname Cisco_AP command (CSCsk64812).

External AAA is not Supported

The config mesh local-auth {enable | disable} command should not be used. Local authorization should never be disabled. Enter the show mesh config command to view local authorization status. 

(controller) >show mesh config 

Mesh Range....................................... 12000

Backhaul with client access status............... disabled

Background Scanning State........................ enabled

MAC Filter Config................................ enabled

Radius MAC Filter................................ disabled

Security Mode.................................... EAP

Local-Auth....................................... enabled

Four Gigabit Ethernet Ports Supported on 1520s

The 1520 series access point supports four Gigabit Ethernet interfaces.

•Port 0 (g0) is a Power over Ethernet input port-PoE (in)

•Port 1 (g1) is a Power over Ethernet output port-PoE (out)

•Port 2 (g2) is a cable connection

•Port 3 (g3) is a fiber connection

You can query the status of these four interfaces in the controller CLI and Cisco WCS.

In the Controller CLI, the show mesh env summary command is used to display the status of the ports.

•The Up or Down (Dn) status of the four ports is reported in the following format:

–port0(PoE-in):port1(PoE-out):port2(cable):port3(fiber)

•For example, rap1522.a380 in the display below shows a port status of UpDnDnDn. This indicates that:

–PoE-in port 0 (g0) is Up, PoE-out port 1 (g1) is Down (Dn), Cable port 2 (g2) is Down (Dn) and Fiber port 3 (g3) is Down (Dn). 

(controller)>show mesh env summary 

AP Name      Temperature(C/F) Heater Ethernet Battery 

--------     --------------- -------- ------- -------

rap1242.c9ef    N/A            N/A    UP       N/A 

rap1522.a380    29/84          OFF    UpDnDnDn N/A 

rap1522.4da8    31/87          OFF    UpDnDnDn N/A

In Cisco WCS, port status in found on the Interfaces tab of the access point page (Monitor > Access Points > AP Name).

Probing of Battery Charge Levels Requires Allowance for Cycles

After detaching and reattaching a probe to a backup battery on a 1510 the battery status remains at a 0% charge reading for up to 30 minutes. This is in keeping with the design of the battery. The battery estimates its charge on 30 minute cycles (CSCsi83272).

Monitoring Port LED Status on an Cisco Aironet 1520 Series Access Point

When physically disconnecting a cable from an 1520 series access point, the port LED associated with that connection might remain lit for up to 3 seconds.

Data Rate Considerations in Short Link Deployments of 1520s

For DFS bands, the Hammer 5 GHz radio does not meet the receiver saturation specification of -30 dBm for some of the higher data rate modes due to a transceiver chipset optimization made to lower the DFS false detect probability. The typical receiver saturation input level is -37 dBm at 24 and 36 Mbps. Future releases of the 1522 will contain an improvement to this parameter by way of further chipset register setting optimization. The receiver saturation performance impact can be mitigated by reducing transmit power and antenna gain where possible. For typical deployments where radios are separated by reasonable distances there is no impact to high data rate support.

System Requirements

You can install this software release on the following Cisco Wireless LAN controller platforms: 2100 series, 4400 series and Wireless Service Module (WiSM) for the Catalyst 6500 and 7600.

Note•You must install release 4.1.190.5 or 4.1.191.24M to operate Cisco Aironet 1520 series access points in your mesh network.

–Release 4.2.x and earlier 4.1.x releases will not support 1520 series mesh access points.

–A 1520 mesh access point operating with release 4.1.190.5 is only supported in the US and Canada.

Release 4.1.191.24M provides international support for 1520s, 1240s, and 1130s and support for the UNI-2 band in the US.

–If a 1520 mesh access point is operating in a network, and you downgrade the software release within your network to a non-mesh release, the 1520 will not reconnect and might become stranded.

•If 1520s are going to be installed in a mesh network that is also operating with 1510s, then note the following:

–The network must first be upgraded to a version of 4.1.190.5 or 4.1.191.24M.

–All 1510s must be upgraded to the new mesh release and associated with the controller (joined) before any 1520s can be added to the network.

–A 1520 should not be added to the network until release 4.1.190.5 or 4.1.191.24M is running on the network to ensure proper communication between 1510s and 1520s.

–Mobility groups functionality is supported when operating with 4.1.190.5 or 4.1.191.24M and all 4.1.x versions of non-mesh controller software.

–A 1510 can be a parent to a 1520 mesh access point in release 4.1.191.24M; however, in release 4.1.190.5 the 1510 can only be a child to a 1520.

Note Upgrading to 4.1.191.24M provides full interoperability between 1510s and 1520s. Release 4.1.190.5 does not provide full interoperability. Refer to the "Upgrade Compatibility Matrix" section for upgrade path specifics.

•If you are operating with indoor and outdoor access points in your mesh network, then note the following:

–Series 1130 and 1240 indoor access points can operate as mesh access points in this release.

–All other indoor access points (excluding 1250) operate as standard, non-mesh access points.

Caution Indoor access points 1130 and1240 configured as mesh access points (bridge mode) should not be connected to a controller without mesh release 4.1.191.24M installed. The1130 and 1240 mesh access points must be converted back to LWAPP (local mode) access points before they are connected to a controller with a non-mesh release. See the "Converting Indoor Mesh Access Points to Non-Mesh Lightweight Access Points (1130AG, 1240AG)" section for details on the conversion.

Upgrade Compatibility Matrix

Table 4 outlines the upgrade compatibility of controller mesh and non-mesh releases and indicates the intermediate software releases required as part of the upgrade path. A summary of upgrade path requirements is noted in the "Upgrading to this Software Release" section.

Table 4 Upgrade Compatibility Matrix for Controller Mesh and Non-Mesh Releases

Upgrade to

4.1.191.24M

4.1.190.5

4.1.185.0
4.1.171.0
4.0.219.0

4.0.217.204

4.0.217.0

4.0.216.0

4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.5
4.0.155.0
3.2.195.10
3.2.193.5
3.2.171.6
3.2.171.5
3.2.150.10
3.2.150.6
3.2.116.21
3.2.78.0
3.1.111.0
3.1.105.0
3.1.59.24
Upgrade from

4.1.191.24M

-

                                             

4.1.190.5

Y

-

                                           

4.1.185.0

Y

Y1

-

                                         

4.1.181.0

 

Y1

Y1

                                         

4.1.171.0

 

Y1

Y1

-

                                       

4.0.219.0

   

Y1

Y1

-

                                     

4.0.217.204

Y1

 

Y1

Y1

Y1

-

                                   

4.0.217.0

   

Y1

Y1

Y1

Y2

-

                                 

4.0.216.0

   

Y1

Y1

Y1

Y2

Y

-

                               

4.0.206.0

   

Y1

Y1

Y1

Y2

Y

 

-

                             

4.0.179.11

           

Y

 

Y3

-

                           

4.0.179.8

           

Y

 

Y3

Y

-

                         

4.0.155.5

           

Y

 

Y3

Y

Y

-

                       

4.0.155.0

           

Y

 

Y3

Y

Y

Y

-

                     

3.2.195.10

           

Y

 

Y3

Y

Y

Y

 

-

                   

3.2.193.5

           

Y

 

Y3

Y

Y

Y

 

Y

-

                 

3.2.171.6

           

Y

 

Y3

Y

Y

Y

 

Y

 

-

               

3.2.171.5

           

Y

 

Y3

Y

Y

Y

 

Y

 

Y

-

             

3.2.150.10

           

Y

 

Y3

Y

Y

Y

 

Y

 

Y

 

-

           

3.2.150.6

           

Y

 

Y3

Y

Y

Y

 

Y

 

Y

 

Y

-

         

3.2.116.21

           

Y

 

Y3

Y

Y

Y

 

Y

 

Y

 

Y

 

-

       

3.2.78.0

           

Y

 

Y3

Y

Y

Y

 

Y

 

Y

 

Y

 

Y

-

     

3.1.111.0

                         

Y

 

Y

 

Y

 

Y

Y

-

   

3.1.105.0

                         

Y

 

Y

 

Y

 

Y

Y

Y

-

 

3.1.59.24

                         

Y

 

Y

 

Y

 

Y

Y

Y

Y

-

1 CUSTOMERS THAT REQUIRE DYNAMIC FREQUENCY SELECTION (DFS) FUNCTIONALITY SHOULD NOT USE THIS RELEASE. This release does not provide DFS functionality fixes found in release 4.0.217.204. Additionally, this release is not supported in ETSI compliant countries or Singapore.

2 Release 4.0.217.204 provides fixes for DFS on the AP1510. This functionality is only needed in countries where DFS rules apply.

3 An upgrade to 4.0.206.0 is not allowed in the following Country Codes when operating with the following access points: Australia (AP1505 and AP1510), Brazil (AP1505 and AP1510), Hong Kong (AP1505 and AP1510), India (AP1505 and AP1510), Japan (AP1510), Korea (AP1505 and AP1510), Mexico (AP1505 and AP1510), New Zealand (AP1505 and AP1510), and Russia (AP1505 and AP1510).


Upgrading to this Software Release

For instructions on downloading software to the controller using Cisco WCS, refer to the release 4.2 version of the Cisco Wireless Control System Configuration Guide at the following link:

http://www.cisco.com/en/US/products/ps6305/products_installation_and_configuration_guides_list.html

For instructions on downloading mesh release 4.1.191.24M software to the controller using the controller GUI or CLI, refer to Software Upgrade Procedure.

Upgrade Path to Release 4.1.191.24M

Details for upgrading your network to Release 4.1.191.24M from earlier releases of 3.1, 3.2, 4.0 and 4.1 are described below.

•If your controller is installed with release 4.0.2xx.x software, you must upgrade with two intermediate releases (or one if a DFS network) prior to installing 4.1.191.24M in your network.

–First upgrade to 4.1.185.0 (non-DFS network) or to 4.0.217.204 (DFS network)

–Secondly, upgrade to 4.1.190.5 (not required for networks that upgraded to 4.0.217.204)

–Thirdly, upgrade to 4.1.191.24M

•If your controller is installed with release 4.0.1xx.x or 3.2.xx, you must upgrade with three intermediate releases (or two if a DFS network) prior to installing Release 4.1.191.24M.

–First, upgrade to 4.0.217.0

–Secondly, upgrade to release 4.0.217.204 (DFS network) or 4.1.185.0 (non-DFS network)

–Thirdly, upgrade to Release 4.1.190.5 (not required for networks that upgraded to 4.0.217.204)

–Fourthly, upgrade to release 4.1.191.24M

•If your controller is installed with release 3.1.x, you must upgrade with four intermediate releases (or three if a DFS network) prior to installing Release 4.1.191.24M.

–First, upgrade to 3.2.195.10

–Secondly, upgrade to 4.0.217.0

–Thirdly, upgrade to 4.1.185.0 (non-DFS network) or 4.0.217.204 (DFS network)

–Fourthly, upgrade to Release 4.1.190.5 (not required for networks that upgraded to 4.0.217.204)

–Fifthly, upgrade to Release 4.1.191.24M.

Mandatory Boot Variable Update for Networks with 1520s

If your network is operating with 1520s or you plan to install 1520s in your network, you must set the boot variable on the 1520 BEFORE upgrading from release 4.1.190.5 to 4.1.191.24M or installing a 1520 in a 4.1.191.24M network. Updating the boot variable ensures the 1520 joins correctly.

Note You should check the boot variable setting before updating the boot.

•If the boot system image is visible, then no boot variable update is required.

–If upgrading from release 4.1.190.5, the system image should read: flash:/c1520-k9w9-mx.124-3g.JMA1/c1520-k9w9-mx.124-3g.JMA1

•If the boot system image is missing, then you must update the boot variable.

Checking the Boot Variable Setting

To check the setting of the boot variable, do the following:

Step 1 On the controller, enter the following commands for each mesh access point (MAP):

debug ap enable AP_Name

debug ap command "more flash:/env_vars" Cisco_AP

A display similar to the following appears: 

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: 5G_RADIO_CARRIER_SET=0020

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: 5G_RADIO_ENCRYPTION_CONFIG=02

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: 5G_RADIO_MAX_TX_POWER=65535

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: 
BOOT=flash:/c1520-k9w9-mx.124-3g.JMA1/c1520-k9w9-mx.124-3g.JMA1

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: DEFAULT_ROUTER=11.200.9.20

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: DEVIATION_NUM=0

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: DOT11G_RADIO_MODE=255

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: DOT11_DEVICE_TYPE=4C

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: DOT11_ENCRYPTION_CONFIG=02

Tue Jan 15 00:00:15 2008: SLT-HCAB-MAP-01-fe.bb.6f: DOT11_MAX_AS