Cisco Cisco Aironet 1400 Wireless Bridge Notas de publicación
14
Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(10b)JDA and 12.4(10b)JDA2
OL-17693-02
Important Notes
Enabling a Crash File for 1250 Series Access Points
A 1250 series access point that is running a Cisco IOS Release prior to 12.4(10b)JDA and greater do not
generate a crash log when it crashes. The crash log is disabled so that a crash does not corrupt the flash
file system.
generate a crash log when it crashes. The crash log is disabled so that a crash does not corrupt the flash
file system.
New 1250 series access points shipped from the factory contain the new bootloader image. Previous
versions do not support that fixes the flash file system after it is corrupted during a crash (without losing
files). This new bootloader automatically sets a new CRASH_LOG environment variable to “yes,” which
enables a crash log to be generated following a crash. Therefore, no user configuration is needed to
enable a crash log on new 1250 series access points shipped from the factory.
versions do not support that fixes the flash file system after it is corrupted during a crash (without losing
files). This new bootloader automatically sets a new CRASH_LOG environment variable to “yes,” which
enables a crash log to be generated following a crash. Therefore, no user configuration is needed to
enable a crash log on new 1250 series access points shipped from the factory.
To enable 1250 series access points in the field to generate a crash log following a crash, install Cisco
IOS Release (insert Krypton release number here) or later and enter this case-sensitive bootloader CLI
command on the access point: set CRASH_LOG yes. When you set this CLI, the access point does not
immediately generate a crash log. The log is generated after a crash occurs. After the crash log is
generated, enter this command to disable the CRASH_LOG environment variable to minimize the risk
of corrupting the flash file system: set CRASH_LOG no.
IOS Release (insert Krypton release number here) or later and enter this case-sensitive bootloader CLI
command on the access point: set CRASH_LOG yes. When you set this CLI, the access point does not
immediately generate a crash log. The log is generated after a crash occurs. After the crash log is
generated, enter this command to disable the CRASH_LOG environment variable to minimize the risk
of corrupting the flash file system: set CRASH_LOG no.
Low Throughput Seen on 1250 Series Access Points with 16 BSSIDs Configured
If your network uses 16 BSSIDs with 1- and 2-Mbps data rates, 1250 series access points might
experience very low throughput due to high management traffic.
experience very low throughput due to high management traffic.
802.11n HT Rates Apply Only to No Encryption or WPA2/AES Encryption
The 802.11n HT rates apply only to no encryption or WPA2/AES encryption. They do not apply to WEP
or WPA encryption. If WEP or TKIP encryption is used, the 1250 series access points and any 802.11n
Draft 2.0 clients will not transmit at the HT rates. Legacy rates (802.11a/b/g) will be used for any clients
using WEP or TKIP encryption.
or WPA encryption. If WEP or TKIP encryption is used, the 1250 series access points and any 802.11n
Draft 2.0 clients will not transmit at the HT rates. Legacy rates (802.11a/b/g) will be used for any clients
using WEP or TKIP encryption.
Layer 3 Not Supported with NAC for MBSSID
Layer 3 is not supported with NAC for MBSSID in this release.
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:
address from a DHCP server:
When you connect a 1130 or 1240 series access point or a 1300 series outdoor access point/bridge 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.
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.