Table Of Contents
Release Notes for Cisco Aironet Access Points for Cisco IOS Release 12.3(8)JEB1
July 26, 2007
These release notes describe minor features and caveats for Cisco IOS Maintenance Release 12.3(8)JEB1. They also provide important information about Cisco Aironet 1100, 1200, and 1230 series autonomous access points. The Cisco Aironet 350 series is no longer supported in this release or any future release.
These release notes contain the following sections:
The Cisco Aironet Access Point is a wireless LAN transceiver that acts as the connection point between wireless and wired networks or as the center point of a standalone wireless network. In large installations, the roaming functionality provided by multiple access points enables wireless users to move freely throughout the facility while maintaining uninterrupted access to the network.
You can configure and monitor 1100, 1200, and 1230, series access points using the command-line interface (CLI), the web-browser interface, or Simple Network Management Protocol (SNMP).
Cisco IOS Release 12.3(8)JEB1 is a general maintenance release that concentrates on bug fixes and includes minor features. You can install Cisco IOS Release 12.3(8)JEB1 on any Cisco Aironet access 1100, 1210, or 1230 series access point.
Note Software upgrades fail when you use the web-browser interface to install Cisco IOS Release 12.3(8)JEB1 on 1200 series access points. The image size exceeds the access point's 4-MB restriction for software upgrades. Use TFTP to upgrade your access point to this release. For complete instructions on using TFTP to upgrade access point software, see the "Working with Software Images" section in the Cisco IOS Software Configuration Guide for Cisco Aironet Access Points. Click this link to browse to that document:
You can also install this release on 1200 series access points that have been converted to run Cisco IOS software. You can tell whether an access point runs VxWorks or Cisco IOS software by looking at the GUI: the GUI on an access point running VxWorks has a yellow and red color scheme, and the GUI on an access point running Cisco IOS software has a green, light-green, and black color scheme.
Your 1200 series access point must run one of these VxWorks versions before you can convert to Cisco IOS software: 12.03T, 12.02T1, 12.01T1, 12.00T, 11.56, or 11.54T. If your access point runs version 12.04, you must downgrade to a supported VxWorks version before upgrading to Cisco IOS software.
The conversion upgrade image for 1200 series access points installs Cisco IOS Release 12.2(13)JA2 on your 1200 series access point.
Note Do not attempt to load a Cisco IOS image on 1200 series access points that have not been converted.
Finding the Cisco IOS Software Version
To find the version of Cisco IOS software running on your access point, use a Telnet session to log into the access point, and enter the show version EXEC command. This example shows command output from an access point running Cisco IOS Release 12.3(8)JA:ap1200>show versionCisco Internetwork Operating System SoftwareIOS (tm) C1200 Software (C1200-K9W7-M), Version 12.3(8)JACopyright (c) 1986-2006 by Cisco Systems, Inc.
On access points running Cisco IOS software, you can also find the software version on the System Software Version page in the access point's web-browser interface. If your access point does not run Cisco IOS software, the software version appears at the top left of most pages in the web-browser interface.
Upgrading to a New Software Release
For instructions on installing access point software for your access point:
Step 1 Follow this link to the Cisco home page:
Step 2 Click Support. The Support page appears.
Step 3 Click See Documentation. The Documentation page appears.
Step 4 Click Wireless. The Wireless Support Resources page appears.
Step 5 Scroll down to the Access Points section.
Step 6 Select the access point model for which you need the information. The Introduction page for the model you selected appears.
Step 7 Under the Configure section, click Configuration Guides. A list of configuration documents appears.
Step 8 Click Cisco IOS Software Configuration Guide for Cisco Aironet Access Points, 12.4(3g)JA and 12.3(8)JEB1.
For information on Cisco IOS software, click this link to browse to the Cisco IOS Software Center on Cisco.com:
Disable Radios to Prevent Unexpected Reboot When Upgrading System Software
If your access point runs Cisco IOS Release 12.2(11)JA, 12.2(11)JA1, or 12.2(11)JA2, your access point might unexpectedly reboot after you upgrade to a later Cisco IOS Release. Because of a rare timing condition that affects the radios, the access point sometimes reboots immediately after the upgrade when the radios are enabled. However, after the access point reboots, the upgrade is complete, and the access point operates normally. To prevent the access point from rebooting unexpectedly, disable the radio interfaces before upgrading software.
Follow these steps to disable the radio interfaces using the web-browser interface:
Step 1 Browse to the Network Interfaces: Radio Settings page. Figure 1 shows the top portion of the Network Interfaces: Radio Settings page.
Figure 1 Network Interfaces: Radio Settings Page
Step 2 Select Disable to disable the radio.
Step 3 Click Apply at the bottom of the page.
Step 4 If your access point has two radios, repeat these steps for the second radio.
Beginning in privileged EXEC mode, follow these steps to disable the access point radios using the CLI:
If your access point has two radios, repeat these steps for the second radio. Use the no form of the shutdown command to enable the radio.
Converting to Cisco IOS Software
If your 1200 series access point does not run Cisco IOS software, you can use the conversion utility or the conversion upgrade image to convert the access point system to Cisco IOS software. Use the conversion utility to maintain the current configuration after the conversion, or load the upgrade image to convert to Cisco IOS software without saving the current configuration. Your 1200 series access point must be running one of these VxWorks firmware versions before you can convert to Cisco IOS software:
VxWorks version 12.03T, 12.02T1, 12.01T1, 12.00T, 11.56, or 11.54T
The conversion upgrade image for 1200 series access points installs Cisco IOS Release 12.2(13)JA2 on your 1200 series access point.
Note The upgrade image and the conversion tool do not support VxWorks version 12.04. Access points running version 12.04 must be downgraded to a supported operating system version before you can use the upgrade image or the conversion tool.
Note The upgrade to Cisco IOS software is permanent; you cannot revert to non-IOS software. Product warranties do not cover unintended upgrades.
For complete instructions on using the conversion utility, refer to the Cisco Aironet Conversion Tool for Cisco IOS Software, 2.1 Administrator Guide for Windows. Click this link to browse to the Administrator Guide:
To download the conversion utility or the upgrade image, click this link to browse to the Cisco IOS Software Center on Cisco.com:
On the Cisco IOS Software Center page, enter your Cisco.com username and password to use the Feature Navigator or the Cisco IOS Upgrade Planner, or click Wireless Software to go to the Wireless LAN Software page. Download the conversion utility or the upgrade image for 1200 series access points. You can also download instructions for using the utility and the image.
Some Fields Not Updated During Upgrade to Cisco IOS Software
When you upgrade an access point to run Cisco IOS software, some fields that are reported in the console messages during the upgrade are blank or are populated with zeros. However, blank or zero fields are normal after a successful upgrade, because 1200 series access points do not support that information. This example shows fields that might appear blank or populated with zeros:32K bytes of flash-simulated non-volatile configuration memory.Base Ethernet MAC Address: 00:05:9A:38:42:91Part Number: 0-0000-00PCA Assembly Number: 000-00000-00PCA Revision Number:PCB Serial Number:Top Assembly Part Number: 000-00000-00Top Assembly Serial Number:Top Revision Number:Product/Model Number: AIR-AP352-IOS-UPGRD
Cisco IOS Release 12.3(8)JEB1 is a maintenance release and contains no new features.
This section contains information that you should keep in mind when installing Cisco Aironet autonomous access points.
Installation in Environmental Air Space
This section provides information on installing 1100 and 1200 series access points in environmental air space, such as above suspended ceilings.
Cisco Aironet 1100, and 1200 series access points provide adequate fire resistance and low smoke-producing characteristics suitable for operation in a building's environmental air space, such as above suspended ceilings, in accordance with Section 300-22(C) of the National Electrical Code (NEC) and Sections 2-128, 12-010(3) and 12-100 of the Canadian Electrical Code, Part 1, C22.1.
Caution The power injector does not provide fire resistance and low smoke-producing characteristics and is not intended for use in extremely high or low temperatures or in environmental air spaces such as above suspended ceilings.
Note If you plan to mount a 1200 series access point with a 5-GHz radio in an area subject to environmental air space, we recommend that you mount the access point horizontally so that its antennas point down. Doing so ensures that the access point complies with regulatory requirements for environmental air space with the 5-GHz radio installed.
This section describes issues that you should consider before applying power to an access point.
Caution The operational voltage range for 1100 series access points is 35 to 57 VDC, and the nominal voltage is 48 VDC. Voltages higher than 60 VDC can damage the equipment.
Caution The nominal voltage for 1200 series access points is 48 VDC, and the access point is operational up to 60 VDC. Voltages higher than 60 VDC can damage the equipment.
Caution Cisco Aironet power injectors are only designed for use with Cisco Aironet access points and bridges. Do not use the power injector with any other Ethernet-ready device. Using the power injector with other Ethernet-ready devices can damage the equipment.
Use Only One Power Option
You cannot provide redundant power to 1100 and 1200 series access points with both DC power to its power port and inline power from a patch panel or powered switch to the access point Ethernet port. If you apply power to the access point from both sources, the switch or power patch panel might shut down the port to which the access point is connected. Figure 2 shows the power configuration that can shut down the port on the patch panel or powered switch.
Figure 2 Improper Power Configuration Using Two Power Sources
Using the AC Power Adapter
If you use the AC power adapter to provide power to the access point, you do not need to adjust the access point configuration.
Using a Switch Capable of IEEE 802.3af Power Negotiation
If you use a switch to provide Power over Ethernet (PoE) to the access point and the switch supports the IEEE 802.3af power negotiation standard, select Power Negotiation on the System Software: System Configuration page.
Using a Switch That Does Not Support IEEE 802.3af Power Negotiation
If you use a switch to provide Power over Ethernet (PoE) to the access point and the switch does not support the IEEE 802.3af power negotiation standard, select Pre-Standard Compatibility on the System Software: System Configuration page.
Using a Power Injector
If you use a power injector to provide power to the access point, select Power Injector on the System Software: System Configuration page, and enter the MAC address of the switch port to which the access point is connected.
Operating 5-GHz Radio Requires Power Injector, Power Module, or Catalyst 3550-24 PWR Switch
The 1200 series power injector and the 1200 series power module support operation of the 5-GHz radio in the access point. The Catalyst 3550-24 PWR switch supports power for both the 2.4-GHz radio and the 5-GHz radio. Other switches and power patch panels might not provide enough power for the 5-GHz radio.
Access Point Requires 1200 Series Universal Power Supply and Power Injector
If you use a power injector or a power module to provide power to a 1200 series access point, you must use a 1200 series universal power supply. If you need to use a power injector to inject power into the access point's Ethernet port, you must use a 1200 series power injector.
Unpowered 1100 Series Access Points Cause Loopback When Connected to Switches Without Loopback Detection
When you connect an unpowered 1100 series access point to a switch without loopback detection, the access point causes a loopback. To avoid this problem, make sure loopback detection is enabled on the switch to which the access point is connected. If your switch does not have loopback detection, disconnect the access point from the switch when the access point power is off.
For instructions on the proper installation and grounding of external antennas for 1200 series access points, refer to the National Fire Protection Association's NFPA 70, National Electrical Code, Article 810, and the Canadian Standards Association's Canadian Electrical Code, Section 54.
This section describes important information about the access point.
CCKM and Fast Roaming on Cisco 7921/7925 IP Phones
When a 7921 or 7925 wireless associates to an access point in a WDS with CCKM, it cannot fast roam because call admission control is not enabled. To work around this issue you must enable admission control by issuing the admit-traffic command in the access point SSID configuration as shown in the following example:dot11 ssid voice vlan 21 authentication open eap eap_methods authentication network-eap eap_methods authentication key-managemenet wpa cckm admit-traffic
Layer 3 Not supported with NAC for MBSSID
Layer 3 is not supported with NAC for MBSSID in this release.
DFS Enabled by Default on 5-GHz Radios in North America
In this release, Dynamic Frequency Selection (DFS) is automatically enabled on 5-GHz radios configured for use in North America. The 5-GHz radios use DFS to detect radar signals and avoid interfering with them. Radios configured for use in Europe and Singapore also use DFS. Other regulatory domains do not use DFS. Refer to the "DFS Enabled by Default on 5-GHz Radios in North America" section for detailed information.
Change to Default IP Address Behavior
Cisco IOS Releases 12.3(2)JA and later change the default behavior of access points requesting an IP address from a DHCP server:
•When you connect a 1200 or 1230 series access point with a default configuration to your LAN, the access point requests an IP address from your DHCP server and, if it does not receive an address, continues to send requests indefinitely.
•When you connect an 1100 series access point with a default configuration to your LAN, the 1100 series access point makes several attempts to get an IP address from the DHCP server. If it does not receive an address, it assigns itself the IP address 10.0.0.1 for 5 minutes. During this 5-minute window, you can browse to the default IP address and configure a static address. If after 5 minutes the access point is not reconfigured, it discards the 10.0.0.1 address and reverts to requesting an address from the DHCP server. If it does not receive an address, it sends requests indefinitely. If you miss the 5-minute window for browsing to the access point at 10.0.0.1, you can power-cycle the access point to repeat the process.
Save Interface Level Configuration Before Upgrading to Releases 12.3(8)JEB1
If the access points have SSIDs configured at the interface level (rather than at the global level), before upgrading to Cisco IOS Release 12.3(7)JA and above, upgrade to Cisco IOS Release 12.3(4)JA, save the configurations, and then upgrade to Release 12.3(8)JEB1. This procedure must be followed to make sure that the SSID configurations are converted from the interface level to global level.
Changes to the Default Configuration—Radios Disabled and No Default SSID
In this release, the radio or radios are disabled by default, and there is no default SSID. You must create an SSID and enable the radio or radios before the access point allows wireless associations from other devices. These changes to the default configuration improve the security of newly installed access points.
Clients Using WPA/WPA2 and Power Save Might Fail to Authenticate
Certain clients using WPA/WPA2 key management and power save might take many attempts to authenticate or, in some cases, fail to authenticate. Any SSID defined to use authentication key-management WPA, coupled with clients using power save mode and authenticating using WPA/WPA2 may experience this problem.
A hidden configure level command, dot11 wpa handshake timeout, can be used to increase the timeout between sending the WPA key packets from the default value (100 ms) to a value between 101 and 2000 ms. The command stores its value in the configuration across device reloads.
Default Username and Password Are Cisco
When you open the access point interface, you must enter a username and password. The default username for administrator login is Cisco, and the default password is Cisco. Both the username and password are case sensitive.
Some Client Devices Cannot Associate When QoS Is Configured
Some wireless client devices, including Dell Axim handhelds and Hewlett-Packard iPaq HX4700 handhelds, cannot associate to an access point when the access point is configured for quality of service (QoS). To allow these clients to associate, disable QoS on the access point. You can use the QoS Policies page on the access point GUI to disable QoS, or enter this command on the CLI:
ap(config-if) #no dot11 qos mode
Some Devices Disassociate When Multiple BSSIDs Are Added or Deleted
Devices on your wireless LAN that are configured to associate to a specific access point based on the access point MAC address (such as client devices, repeaters, hot standby units, or workgroup bridges) might lose their association when you add or delete a multiple BSSID. When you add or delete a multiple BSSID, check the association status of devices configured to associate to a specific access point. If necessary, reconfigure the disassociated device to use the BSSID new MAC address.
Enabling MBSSIDs Without VLANs Disables Radio Interface
If you use the mbssid configuration interface command to enable multiple BSSIDs on a specific radio interface but VLANs are not configured on the access point, the access point disables the radio interface. To re-enable the radio, you must shut down the radio, disable multiple BSSIDs, and re-enable the radio. This example shows the commands you use to re-enable the radio:AP1134(config)# interface d1AP1134(config-if)# shutAP1134(config-if)# no mbssidAP1134(config-if)# no shut
After you re-enable the radio, you can enable VLANs on the access point and enable multiple BSSIDs.
Cannot Set Channel on DFS-Enabled Radios in Some Regulatory Domains
Access points with 5-GHz radios configured at the factory for use in Europe, Singapore, Korea, Japan, Taiwan, and Israel now comply with regulations that require radio devices to use Dynamic Frequency Selection (DFS) to detect radar signals and avoid interfering with them. You cannot manually set the channel on DFS-enabled radios configured for these regulatory domains.
Cisco 7920 Phones Require Firmware Version 1.09 or Later When Multiple BSSIDs Are Enabled
When multiple BSSIDs are configured on the access point, Cisco 7920 wireless IP phones must run firmware version 1.09 or later.
AIR-RM21A/AIR-RM22A Radio Modules Usually Set to Max Transmit Power
AIR-RM21A and AIR-RM22A radio modules measure transmit power in decibels per milliwatt (dBm), but earlier versions of 802.11a radios in Cisco Aironet access points measure power in milliwatts (mW). Because power settings in mW do not translate directly to settings in dBm, the access point usually uses the default power setting of maximum when you install a new AIR-RM21A or AIR-RM22A radio module.
Table 1 lists 802.11a transmit power settings in mW and the power settings that the access point assigns to a new radio module.
Table 1 Transmit Power Settings Assigned to New Radio Modules
Power Settings in mW Power Setting Assigned to New Radio Module
5 dBm (approximately 3 mW)
maximum (17 dBm)
GRE Tunnelling Through WLSM Sometimes Requires MTU Setting Adjustments
If client devices on your wireless LAN cannot use certain network applications or cannot browse to Internet sites, you might need to adjust the MTU setting on the client devices or other network devices. For more information, refer to the Tech Note at this URL:
TACACS+ and DHCP IP Address Sometimes Locks Out Administrators
When you configure an access point for TACACS+ administration and to receive an IP address from the DHCP server, administrators might be locked out of the access point after it reboots if the administrator does not have a local username and password configured on the access point. This issue does not affect access points configured with a static IP address. Administrators who have been locked out must regain access by resetting the unit to default settings.
Access Points Do Not Support Loopback Interface
You must not configure a loopback interface on the access point.
Caution Configuring a loopback interface might generate an IAPP GENINFO storm on your network and disrupt network traffic.
Non-Cisco Aironet 802.11g Clients Might Require Firmware Upgrade
Some non-Cisco Aironet 802.11g client devices require a firmware upgrade before they can associate to the 802.11g radio in the access point. If your non-Cisco Aironet 802.11g client device does not associate to the access point, download and install the latest client firmware from the manufacturer's website.
Throughput Option for 802.11g Radio Blocks Association by 802.11b Clients
When you configure the 802.11g access point radio for best throughput, the access point sets all data rates to basic (required). This setting blocks association from 802.11b client devices. The best throughput option appears on the web-browser interface Express Setup and Radio Settings pages and in the speed CLI configuration interface command.
Transmit Power Set to Maximum When You Install 802.11g Radio
When you replace the 802.11b radio in a 1200 series access point with an 802.11g radio, the 802.11g radio is set to the maximum transmit power allowed in your regulatory domain, regardless of the power setting configured on the 802.11b radio. After you install the 802.11g radio and the access point reboots, configure the 802.11g radio to the preferred transmit power.
Use Auto for Ethernet Duplex and Speed Settings
Cisco recommends that you use auto, the default setting, for both the speed and duplex settings on the access point Ethernet port. When your access point receives inline power from a switch, any change in the speed or duplex settings that resets the Ethernet link reboots the access point. If the switch port to which the access point is connected is not set to auto, you can change the access point port to half or full to correct a duplex mismatch, and the Ethernet link is not reset. However, if you change from half or full back to auto, the link is reset, and, if your access point receives inline power from a switch, the access point reboots.
Note The speed and duplex settings on the access point Ethernet port must match the Ethernet settings on the port to which the access point is connected. If you change the settings on the port to which the access point is connected, change the settings on the access point Ethernet port to match.
Use force-reload Option with archive download-sw Command
When you upgrade access point or bridge system software by entering the archive download-sw command on the CLI, you must use the force-reload option. If the access point or bridge does not reload the flash memory after the upgrade, the pages in the web-browser interface might not reflect the upgrade. This example shows how to upgrade system software using the archive download-sw command:AP# archive download-sw /force-reload /overwrite tftp://10.0.0.1/image-name
Radio MAC Address Appears in ACU
When a Cisco Aironet client device associates to an access point running IOS software, the access point MAC address that appears on the Status page in the Aironet Client Utility (ACU) is the MAC address for the access point radio. The MAC address for the access point Ethernet port is on the label on the back of the access point.
Radio MAC Address Appears in Access Point Event Log
When a client device roams from an access point (such as access point alpha) to another access point (access point bravo), a message appears in the event log on access point alpha stating that the client roamed to access point bravo. The MAC address that appears in the event message is the MAC address for the radio in access point bravo. The MAC address for the access point Ethernet port is printed on the label on the back of the access point.
Mask Field on IP Filters Page Behaves the Same As in CLI
In Cisco IOS Release 12.2(8)JA and later, the mask that you enter in the Mask field on the IP Filters page in the access point GUI behaves the same way as a mask that you enter in the CLI. If you enter 255.255.255.255 as the mask, the access point accepts any IP address. If you enter 0.0.0.0, the access point looks for an exact match with the IP address that you entered in the IP Address field.
Repeater Access Points Running Cisco IOS Software Cannot Associate to Parent Access Points Running VxWorks
1200 series repeater access points running Cisco IOS software cannot associate to parent access points that do not run Cisco IOS software (1200 series access points that have not been converted to run Cisco IOS software).
Repeater Access Points Cannot Be Configured as WDS Access Points
Repeater access points can participate in WDS, but they cannot provide WDS. You cannot configure a repeater access point as a main WDS access point, and if a root access point becomes a repeater in fallback mode, it cannot provide WDS.
Crossover Cable Sometimes Needed When Ethernet Speed and Duplex Set to Fixed on 1100 Series Access Points
If you change the speed and duplex settings from auto to fixed on an 1100 series access point Ethernet port, the auto-MDIX feature on the port is disabled. When auto-MDIX is disabled, you must determine whether to use a straight-through or a crossover cable to connect the access point Ethernet port to another device. If the Ethernet link goes down after you set the speed and duplex to fixed, try changing the Ethernet cable from crossover to straight-through or from straight-through to crossover.
Cannot Perform Link Tests on Non-Cisco Aironet Client Devices and on Cisco Aironet 802.11g Client Devices
The link test feature on the web-browser interface does not support non-Cisco Aironet client devices nor Cisco Aironet 802.11g client devices.
1100 Series Access Points with Boot Loader Version 12.2(4)JA Boot into Monitor Mode
When the Ethernet port is disabled on an 1100 series access point running boot loader version 12.2(4)JA, the access point boots into monitor mode when it reboots. To avoid this problem, connect the access point Ethernet port to one of the following:
•a wired LAN
•the Ethernet port on a PC
Remove power from the access point, and reapply power to reboot the unit. When the access point senses an Ethernet connection, it boots normally.
Corrupt EAP Packet Sometimes Causes Error Message
During client authentication, the access point sometimes receives a corrupt EAP packet and displays this error message:Oct 1 09:00:51.642 R: %SYS-2-GETBUF: Bad getbuffer, bytes= 28165 -Process= "Dot11 Dot1x process", ipl= 0, pid= 32 -Traceback= A2F98 3C441C 3C7184 3C604C 3C5E14 3C5430 124DDC
You can ignore this message.
When Cipher Is TKIP Only, Key Management Must Be Enabled
When you configure TKIP-only cipher encryption (not TKIP + WEP 128 or TKIP + WEP 40) on any radio interface or VLAN, every SSID on that radio or VLAN must be set to use WPA or CCKM key management. If you configure TKIP on a radio or VLAN but you do not configure key management on the SSIDs, client authentication fails on the SSIDs.
Cisco CKM Supports Spectralink Phones
Cisco CKM (CCKM) key management is designed to support voice clients that require minimal roaming times. CCKM supports only Spectralink and Cisco 7920 Version 2.0 Wireless Phones.
Non-Cisco Aironet Clients Sometimes Fail 802.1x Authentication
Some non-Cisco Aironet client adapters do not perform 802.1x authentication to the access point unless you configure Open authentication with EAP. To allow both Cisco Aironet clients using LEAP and non-Cisco Aironet clients using LEAP to associate using the same SSID, you might need to configure the SSID for both Network EAP authentication and Open authentication with EAP.
Pings and Link Tests Sometimes Fail to Clients with Both Wired and Wireless Network Connections
When you ping or run a link test from an access point to a client device installed in a PC running Microsoft Windows 2000, the ping or link test sometimes fails when the client has both wired and wireless connections to the LAN. Microsoft does not recommend this configuration. For more information, refer to Microsoft Knowledge Base article 157025 at this URL:
Layer 3 Mobility Not Supported on Repeaters and Workgroup Bridges
Repeater access points and workgroup bridges cannot associate to an SSID configured for Layer 3 mobility. Layer 3 mobility is not supported on repeaters and workgroup bridges.
WLSM Required for Layer 3 Mobility
You must use a Wireless LAN Services Module (WLSM) as your WDS device to configure Layer 3 mobility. If you enable Layer 3 mobility for an SSID and your WDS device does not support Layer 3 mobility, client devices cannot associate using that SSID.
This section lists open and resolved caveats for access points.
These caveats are open in Cisco IOS Release 12.3(8)JEB1:
•CSCsc83206—A nested repeater access point fails to notify radar detection.
A nested repeater may lose connectivity to its parent for up to 30 minutes.
This may occur under the following conditions:
1. The nested repeater is operating on a DFS channel in the 5-GHz band (channels 52-140).
2. There is a radar operating in the vicinity of the nested repeater.
3. The nested repeater detects the radar.
4. Neither the nested repeater's parents nor the root AP detect the same radar.
Workaround—Re-design network to deploy root APs to avoid nested repeaters.
•CSCsc94510—GUI can set illegal combination of low latency rates.
The access point GUI is not setting Nominal, Non-nominal and disable for some data rates. The GUI can set an illegal combination of low latency rates on the access point. Rates of 48 and 54 Mbps set as both nominal and non-nominal can occur. Once the rates are set, you can not disable them, and they stay set as non-nominal.
•CSCse34644—Shared authentication with a non-native VLAN does not operate properly.
This situation occurred on flash:/c1130-k9w7-mx.v123_8_ja.20060520/c1130-k9w7-mx.v123_8_ja
Workaround—Save the configuration, and reload the access point. When the access point comes up and the clients get authenticated, edit the shared authentication SSID as follows:
1. Add open authentication.
2. Removed shared authentication.
3. Remove open and add shared authentication. The client should associate.
4. Reload the access point.
•CSCse34644—Shared authentication with non-native VLAN is not working.
Workaround—Save the configuration, and reload the access point. When the access point comes up, both clients authenticate. Edit the shared authentication SSID as follows:
Add open authentication; remove shared authentication. Then remove open and add shared authentication, and the client associates. Save the configuration and reload the access point.CSCsc94510—GE: GUI can set illegal combination of low latency rates
•CSCsj22047—Unable to modify or disable Key Management for configured SSID.
Key Management for a configured SSID cannot be disabled and in some instances attempts to modify from mandatory to optional fails.
Workaround—To disable key management, clear the WPA-PSK keys, select key-management as NONE, and click apply. The WPA-PSK keys are removed. Then select key-management as NONE, and click apply.
Configure an SSID with encryption AES-CCM and key management mandatory with WPA-PSK. Then attempt to disable the key management. After clicking apply and OK, select the SSID, and key management is still mandatory.
If the correct encryption is not selected for optional key management, an error message appears if the user selects optional and then clicks the WPA drop down list. If the user does not click the drop down and simply clicks apply at the bottom of the page, it appears as if the change is being made, but the key management remains mandatory.
•CSCsj17603—dot11ARP cache does not use client MAC address when sending ARP response
When the dot11 arp-cache feature is enabled and if a given ARP entry is cached, the access point responds to an ARP request with its own MAC address. However, the source MAC address in the ARP payload is correct.
Conditions—This caveat affects all autonomous access points in root access point mode.
•CSCsj25335—IP Redirect feature towards DNS packet is undocumented.
However, the IP Redirection Application Note mentions that BOOTP/DHCP, DNS, and broadcast data should not be redirected.
When the IP Redirect feature is configured under the dot11 radio interface, the destination MAC address of the DNS packet is rewritten with the host MAC Address specified under the ip redirect host <IP Address>.
•CSCsj13920—When saving config just within 32768 bytes, 1231G-J-K09 running Cisco IOS version 12.3(7)JA halts.
•CSCsj20308—SNMP object not available for RSSI.
A bridge running 12.3(8)JA2 or 12.3(11)JA1 code fails to return a value for Object cDot11ClientSignalStrength, OID 188.8.131.52.184.108.40.206.2220.127.116.11.1.3 while there is a value in the CLI for signal strength in the output of the show dot11 associations all-client command.
Workaround—None, except to use the CLI value.
•CSCsi40733—1242 access point randomly fails during CTK refresh.
Every 6 hours, a WLCCP link CTK refresh occurs, which should be a transparent action. However, it sometimes fails (on access point site) and the link needs to be re-established (new wlccp authentication).
•CSCsj08967—1242 access point rebooted with unknown reload cause - reason ptr 0xF, PC 0x135EF0, address 0x0.
•CSCsi98692—1230B-K9 access point reloads for unknown reason.
•CSCsd99067—AVVID priority map incorrectly maps CoS 5 to CoS 7 within same VLAN.
THE AVVID priority mapping in the CoS advanced parameters is incorrectly mapping the CoS value to 7 when making a call to a wired phone in same VLAN. This situation occurs in an 802.11g network running one 7921 and one access point.
These caveats are resolved in Cisco IOS Release 12.3(8)JEB1:
A device running Cisco IOS software that has Internet Protocol version 6 (IPv6) enabled may be subject to a denial of service (DoS) attack. For the device to be affected by this vulnerability the device also has to have certain Internet Protocol version 4 (IPv4) User Datagram Protocol (UDP) services enabled. To exploit this vulnerability an offending IPv6 packet must be targeted to the device. Packets that are routed throughout the router can not trigger this vulnerability. Successful exploitation will prevent the interface from receiving any additional traffic. The only exception is Resource Reservation Protocol (RSVP) service, which if exploited, will cause the device to crash. Only the interface on which the vulnerability was exploited will be affected.
Cisco is providing fixed software to address this issue. There are workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at
•CSCsi73614—CB21AG 5-GHz client now obtains IP address after roaming back to repeater.
•CSCsi04754—EAP-FAST now operates normally with local RADIUS server if LEAP is disabled.
•CSCsi35908—Workgroup bridge no longer fails while deleting CAC calls.
•CSCsi35911—Least Congested Channel Search feature is now available on the GUI.
•CSCsg30911—IEEE802dot11-MIB objects no longer show out of range values.
•CSCsi23996—Access point no longer fails when dot11_arp_cache_zero_remove command is issued.
•CSCsi80169—SSH can now be disabled through the GUI.
•CSCsi68728—Traceback is no longer observed while clearing WLCCP WDS statistics.
•CSCsi08181—Invalid interface no longer appears when reloading root bridge in point-to-multipoint configuration.
•CSCsi80249—CKIP SEQ replay no longer detected on root and repeater access points when mic-key-hash is enabled.
•CSCse02766—Repeater clients are now able to connect hosts on the DS.
•CSCsi90721—Access point no longer fails while printing the sh dot11 associations all command.
•CSCsi25620—Bridge timers now operate normally for a workgroup bridge.
•CSCsi82424—Control-plane config item no longer shows error on boot.
•CSCsg59063—Control Plane Policing is no longer available.
•CSCsi74487—wlccp wds mode wds-only command no longer tells customer to write-erase.
•CSCsj10551—WGB now sends IAPP message for static bridge entries in workgroup bridge mode.
•CSCsh43635—Frequent tracebacks on WDS process no longer occur.
•CSCsi35780—LRS-EAP-FAST now operates normally when a workgroup bridge is used as the supplicant.
•CSCek46661—VLAN assignment no longer fails when using local RADIUS server.
•CSCsg69625—IP GRE DSCP marking now operates normally.
•CSCsj44081—Cisco IOS Software has been enhanced with the introduction of additional software checks to signal improper use of data structures. This feature has been introduced in select Cisco IOS Software releases published after April 5, 2007.
Details: The %DATACORRUPTION-1-DATAINCONSISTENCY error message is preceded by a timestamp: May 17 10:01:27.815 UTC: %DATACORRUPTION-1-DATAINCONSISTENCY: copy error. The error message is then followed by a traceback.
If You Need More Information
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find select caveats of any severity. Click this URL to browse to the Bug Toolkit:
(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not yet have a customer-visible description, or the defect might be marked Cisco Confidential.)
For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at http://www.cisco.com/cisco/web/support/index.html. Click Technology Support, choose Wireless from the menu on the left, and click Wireless LAN.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Copyright © 2007 Cisco Systems, Inc. All rights reserved.