This document describes Radio Reset Codes for the Access Point (AP). The Radio Reset Code can be seen from the AP CLI with these commands: show controller dot11radio 0 or show controller dot11radio 1.
At the end of the output, you see the Radio Reset Code which helps you to identify the reason for the radio reset.
Here is an example:
AP#show controllers dot11Radio 0 | i reset Driver TX blocks: in use 0, high 0, at reset 0, fail 0 drop 0 Last radio reset code: 37 Radio resets - total:8 retries:0 failed:0
AP#show controllers dot11Radio 1 | i reset Driver TX blocks: in use 0, high 0, at reset 0, fail 0 drop 0 Last radio reset code: 37 Radio resets - total:8 retries:0 failed:0
Detailed Radio Reset History
In order to see the radio reset history, enter these privileged exec mode commands on the AP:
ap#show trace dot11_rst display time format local ap#show trace dot11_rst
You can then compare the radio reset history with the general AP log (show ap log command) in order to determine what went on around the time of the resets and how long the radios were unavailable.
Table of Radio Reset Codes
Reset Code #
Radio Reset Reason
The radio has failed to respond to the "dot11 flash" command. Not applicable for 802.11n radios.
The radio has failed to respond to a request to reset the interface.
The radio failed to start.
The radio or radio driver was unable to completely remove a client that is no longer serviced by the radio.
A completed packet transmission resulted in an unexpected status code from the hardware. This failure automatically results in a radio coredump written to the flash filesystem.
One or more packets have been submitted to the radio to be transmitted, but have not been reported as completed for 60 seconds.
A packet that has completed transmission is reported with an invalid internal memory address. Not applicable to 802.11n radios.
A transmit packet is attempted to be removed from an empty queue.
The driver attempts to free a packet that the radio still has in progress.
Memory for a completed transmission is attempted to be released twice.
The status of a transmitted Aggregation MAC Service Data Unit (AMSDU) packet is indeterminate.
An 802.11n Block Ack packet is assembled for a client that does not exist.
A command from the AP to the radio has taken 12 seconds without a response.
The radio reported that a command from the AP has failed to execute.
A command from the AP to the radio does not appear to complete. Not applicable to 802.11n radios.
A PCMCIA timeout occured when accessing a radio register. Does not apply to 802.11n radios.apply to 802.11n radios.A PCMCIA timeout occured when accessing a radio register. Does not apply to 802.11n radios.A PCMCIA timeout occured when accessing a radio register. Does not apply to 802.11n radios.A PCMCIA timeout occured when accessing a radio register. Does not apply to 802.11n radios.
The AP timed out when it attempted to load the radio's firmware.
The copy of radio firmware from the AP to the radio completed, but was not accepted by the radio.
A received packet points to an invalid area of memory.
An unexpected radio reset occurred in a four-radio system.
The AP was unable to find or load an appropriate radio firmware file to load into the radio. This could occur if the firmware image is missing or corrupted.
The radio hardware transmitter-watchdog detected a stuck packet and a reset of only the hardware transmitter was unsuccessful .
Client packets cannot be transmitted. Client packet stuck in radio for more than 60 seconds.
Spectrum Firmware, from Clean Air module, requires a radio reset.
There is a problem in the Radio packet receive buffer. Bad RX Ring Address.
The radio goes into or out of monitor mode, due to the CLI enabled the Radio Frequency (RF) monitor/store mode.
The radio goes into or out of promiscuous monitor mode, due to turn on/off RF monitor promiscous mode.
Radio debug tracing is turned on or off, due to start or stop all Dot11 driver tracing.
Hardware radio reset. PCI bus reset.
Start radio in special mode for directional antenna alignment.
Dynamic Frequency Selection reset for non-root radio.
Dynamic Frequency Selection reset due to no channels available.
Dynamic Frequency Selection channel change.
Dynamic Frequency Selection reset waiting for available channel.
Radio interface reset.
Radio reset prior to Cisco IOS? software reload.
Radio reset due to Cisco IOS IP address change.
Radio reset prior to reflashing the radio.
CCK transmit on dual antennas enable or disable.
Enable or disable World Mode IE.
Stop FCC compliance testing mode.
Start FCC compliance testing mode.
Carrier busy test via the CLI.
Reset if radio becomes disabled.
FCC test mode interface reset.
Radio reset due to configuration change.
Clear mesh backhaul.
Set as mesh listener. Radio reset due to enable/disable listening to broadcast on 802.11b (for mesh APs).
Reset on transmit completion.
Reset on completion of deferred multicast packets.
Radio interface has been enabled.
Radio interface has been shutdown.
Cisco IOS software interface goes down.
Cisco IOS ethernet link goes down.
Cisco IOS software interface comes up.
Uplink client goes away.
Uplink client comes up.
Radio configuration change.
Symbol phone extension support has been enabled or disabled.
Radio channel set. Reset while setting channel from Control and Provisioning of Wireless Access Points (CAPWAP).
Universal Access (Mesh) is disabled.
Rogue Location Discovery Protocol start.
Rogue Location Discovery Protocol stop.
Dynamic Frequency Selection debug mode. Reset due to test Dynamic Frequency Selection (DFS) command.
Hostname change after association.
Radio interface reset from command routines. Reset while configuring station_role/beamforming/Space-Time Block Coding (STBC) CLI commands
Radio exits inline Cisco Discovery Protocol (CDP) low power mode holddown.
Frequent command timeouts occur on the radio. Radio command timeouts are more than threshold [10 timeouts].
Indicates that while the radio state should be updated on controller, no reset should be reported.
Bad Tx done (or) bad off channel done.
Bad receive in progress pointer when you receive a packet from radio.
Reset while setting promiscous mode serving channel.
Bad Tx pointer.
Bad Rx ring index.
Radio interface bus down.
Wrong freeing of Tx completed packet.
Offchannel in prog is completed [zero] while radio waits to be stoppped.
Encryption engine stuck specific to 8864 radio chipset.
Beacons not transmitted for last 10 minutes.
Bad packet in transmit queue.
Debug code reset [Cisco bug ID CSCul63678]- infinite loop detected with Tx requeue client.
DMA engine locked [War for Cisco bug ID CSCui54586 / BZ868].