Courseiva
WirelessPrivileged EXEC

show controllers dot11Radio 0

Displays detailed hardware and firmware status of the 802.11 radio interface, used for troubleshooting wireless connectivity issues on Cisco access points and routers.

Definition: show controllers dot11Radio 0 is a Cisco IOS privileged exec command. Displays detailed hardware and firmware status of the 802.11 radio interface, used for troubleshooting wireless connectivity issues on Cisco access points and routers.

Overview

The 'show controllers dot11Radio 0' command is a powerful diagnostic tool used in Cisco wireless environments to inspect the low-level hardware and firmware status of an 802.11 radio interface. This command is essential for network engineers troubleshooting wireless connectivity issues on Cisco access points (APs) and integrated wireless routers. Unlike higher-level commands such as 'show interface dot11Radio 0' or 'show wireless client summary', which focus on logical interface statistics or client associations, 'show controllers' dives into the physical layer, revealing details about the radio transceiver, firmware version, temperature, voltage, and error counters.

This granularity is crucial when dealing with intermittent connectivity, poor signal quality, or hardware failures that are not apparent from interface counters alone. The command operates in privileged EXEC mode (enable), and its output is often extensive, requiring careful parsing. It does not modify the running configuration, making it safe for use in production environments.

In the broader troubleshooting workflow, this command is typically used after initial checks (e.g., 'show ip interface brief', 'show dot11 associations') have narrowed the issue to a specific radio. It helps confirm whether the radio is operational, whether the firmware is loaded correctly, and whether there are any hardware alarms. For CCNA and CCNP candidates, understanding this command is vital for mastering wireless troubleshooting, as it provides the deepest insight into radio health.

The command is available on Cisco IOS-based APs (e.g., 1130, 1240, 1600 series) and on routers with wireless interfaces (e.g., 800, 1900, 2900 series with HWIC-AP). On newer APs running IOS-XE (e.g., 3800, 4800 series), the equivalent command is 'show controllers dot11Radio 0' but with slightly different output formatting. The command's output is buffered, meaning it may be truncated if the terminal length is not set appropriately; using 'terminal length 0' before execution ensures full output.

Overall, this command is a cornerstone of wireless troubleshooting, providing the visibility needed to diagnose physical-layer problems that other commands miss.

Syntax·Privileged EXEC
show controllers dot11Radio 0

When to Use This Command

  • Verify radio state (up/down) and operational status after a reboot or configuration change.
  • Check for hardware errors, CRC failures, or excessive retries that indicate RF interference or faulty hardware.
  • Confirm firmware version and bootloader details to ensure compatibility with the IOS image.
  • Inspect antenna configuration and signal strength parameters when diagnosing coverage problems.

Parameters

ParameterSyntaxDescription
interfacedot11Radio <0-1>Specifies the 802.11 radio interface. On most Cisco APs, dot11Radio 0 is the 2.4 GHz radio (802.11b/g/n) and dot11Radio 1 is the 5 GHz radio (802.11a/n/ac). Valid values are 0 or 1. Common mistake: using 'dot11Radio 0/0' (subinterface notation) which is incorrect; the interface is a physical radio, not a subinterface.

Command Examples

Basic radio status check

show controllers dot11Radio 0
Radio0 - 802.11 Radio
State: UP
Firmware Version: 12.4(21a)JA1
Bootloader Version: 12.4(21a)JA1
MAC Address: 0011.2233.4455
IP Address: 192.168.1.100
Channel: 6 (2437 MHz)
Tx Power: 20 dBm
Antenna: Internal

Transmit Statistics:
  Total Packets: 1023456
  Total Bytes: 1234567890
  Retry Count: 12345
  CRC Errors: 67
  Deferred: 234

Receive Statistics:
  Total Packets: 987654
  Total Bytes: 987654321
  CRC Errors: 12
  Overruns: 0
  Lost Carrier: 0

Signal Statistics:
  Noise Floor: -95 dBm
  Signal Strength: -45 dBm
  SNR: 50 dB

State: UP indicates the radio is operational. Firmware/Bootloader versions show the code running on the radio. MAC and IP addresses identify the interface. Channel and Tx Power show current RF settings. Transmit/Receive statistics: Retry Count and CRC Errors indicate link quality; high values suggest interference or hardware issues. Signal Statistics: Noise Floor should be low (e.g., -95 dBm), Signal Strength strong (e.g., -45 dBm), and SNR high (e.g., 50 dB) for good performance.

Troubleshooting high error rates

show controllers dot11Radio 0
Radio0 - 802.11 Radio
State: UP
Firmware Version: 12.4(21a)JA1
Bootloader Version: 12.4(21a)JA1
MAC Address: 0011.2233.4455
IP Address: 192.168.1.100
Channel: 11 (2462 MHz)
Tx Power: 20 dBm
Antenna: Internal

Transmit Statistics:
  Total Packets: 500000
  Total Bytes: 600000000
  Retry Count: 50000
  CRC Errors: 1500
  Deferred: 5000

Receive Statistics:
  Total Packets: 400000
  Total Bytes: 480000000
  CRC Errors: 2000
  Overruns: 100
  Lost Carrier: 50

Signal Statistics:
  Noise Floor: -80 dBm
  Signal Strength: -60 dBm
  SNR: 20 dB

High Retry Count (10% of total packets) and CRC Errors (1500 TX, 2000 RX) indicate poor link quality. High Noise Floor (-80 dBm) and low SNR (20 dB) suggest interference. Overruns and Lost Carrier point to possible hardware issues or congestion. This output suggests checking for channel overlap, adjusting power, or inspecting antennas.

Understanding the Output

The output is divided into sections: Radio identity and state, firmware details, MAC/IP, RF configuration, and statistics. The 'State' field is critical; if not UP, the radio is disabled or faulty. Firmware version should match expected release.

Channel and Tx Power show current RF settings; ensure channel is not overlapping with nearby APs. Transmit/Receive statistics: Retry Count and CRC Errors are key indicators of link quality—high values (e.g., >5% of total packets) suggest interference, distance, or hardware problems. Deferred packets indicate medium contention.

Receive overruns and lost carrier indicate hardware buffer issues or signal loss. Signal Statistics: Noise Floor should be below -90 dBm; higher values indicate interference. Signal Strength should be above -70 dBm for good connectivity.

SNR (Signal-to-Noise Ratio) should be above 25 dB; lower values cause retransmissions. Use this command to baseline normal operation and identify degradation over time.

Configuration Scenarios

Verify Radio Hardware Health on an Autonomous Access Point

An autonomous AP (e.g., AIR-AP1242AG) is experiencing intermittent client disconnects. The network engineer needs to check if the radio hardware is functioning correctly, including temperature, voltage, and firmware state.

Topology

AP1242 (dot11Radio0) --- Wireless Clients | Switch (Gi0/1)

Steps

  1. 1.Step 1: Connect to the AP via console or SSH and enter privileged EXEC mode: AP> enable
  2. 2.Step 2: Disable terminal paging to see full output: AP# terminal length 0
  3. 3.Step 3: Execute the command: AP# show controllers dot11Radio 0
  4. 4.Step 4: Examine the output for 'Radio0 - 802.11b/g/n' status, check 'Firmware Version', 'Temperature', 'Voltage', and 'Hardware Status' fields.
  5. 5.Step 5: Look for any 'Alarm' or 'Error' indicators, such as 'Temperature out of range' or 'Voltage fault'.
Configuration
! No configuration changes are made; this is a show command.
AP# show controllers dot11Radio 0

Verify: Expected healthy output includes: 'Radio0 - 802.11b/g/n', 'Firmware Version: 12.4(21a)JA1', 'Temperature: 35 C', 'Voltage: 3.3 V', 'Hardware Status: OK'. Problem indicators: 'Temperature: 85 C' (overheating), 'Voltage: 2.5 V' (undervoltage), 'Hardware Status: FAIL'.

Watch out: The command output can be very long; always use 'terminal length 0' to avoid missing critical fields. Also, the 'Hardware Status' field may show 'OK' even if there are minor errors; check 'Rx Error Counters' for CRC errors.

Troubleshoot Radio Not Initializing on a Router with Wireless Interface

A Cisco 891 router with an integrated 802.11n radio is not broadcasting SSIDs. The 'show ip interface brief' shows the dot11Radio0 interface is up, but clients cannot see the WLAN. The engineer suspects a firmware loading issue.

Topology

Router891 (dot11Radio0) --- Wireless Clients | Internet (Gi0/0)

Steps

  1. 1.Step 1: Access the router in privileged EXEC mode: Router> enable
  2. 2.Step 2: Check interface status: Router# show ip interface brief | include dot11Radio
  3. 3.Step 3: If the interface is up, proceed to check radio controllers: Router# show controllers dot11Radio 0
  4. 4.Step 4: Look for 'Firmware Loaded: NO' or 'Firmware Version: Unknown' which indicates the radio firmware did not load.
  5. 5.Step 5: If firmware is not loaded, reload the router or reinsert the wireless module: Router# reload
  6. 6.Step 6: After reload, recheck: Router# show controllers dot11Radio 0
Configuration
! No configuration changes; diagnostic only.
Router# show controllers dot11Radio 0

Verify: Expected output after successful firmware load: 'Firmware Loaded: YES', 'Firmware Version: 15.1(4)M4', 'Radio State: ENABLED'. Problem output: 'Firmware Loaded: NO', 'Radio State: DISABLED'.

Watch out: Sometimes the radio firmware may not load due to a corrupt image; in that case, upgrading the IOS or firmware bundle may be necessary. Also, ensure the router has the correct 'dot11' feature set; some IOS images lack wireless support.

Troubleshooting with This Command

When using 'show controllers dot11Radio 0' for troubleshooting, the first step is to ensure you have the full output by disabling terminal paging. Healthy output typically begins with a line indicating the radio type (e.g., 'Radio0 - 802.11b/g/n') and shows 'Hardware Status: OK'. Key fields to focus on include 'Firmware Version' – if it shows 'Unknown' or 'Not Loaded', the radio is not operational.

The 'Temperature' field should be within the normal range (typically 0-60°C for most APs); values above 80°C indicate overheating and may cause the radio to shut down. 'Voltage' should be stable (e.g., 3.3V); deviations suggest power supply issues. The 'Rx Error Counters' section is critical: look for 'CRC Errors', 'Frame Errors', or 'Overruns'.

A high number of CRC errors indicates RF interference or faulty cabling. If the 'Radio State' is 'DISABLED', the radio may be administratively down or in a reset loop. The 'Alarm' section will list any hardware alarms, such as 'Temperature Alarm' or 'Voltage Alarm'.

A step-by-step diagnostic flow: 1) Check 'Hardware Status' – if FAIL, the radio may need replacement. 2) Check 'Firmware Loaded' – if NO, reload the device or upgrade firmware. 3) Check 'Temperature' and 'Voltage' – if out of range, inspect environmental conditions or power source. 4) Check 'Rx Error Counters' – if high, investigate RF interference, antenna issues, or cable problems. 5) Correlate with 'show interface dot11Radio 0' for input/output errors and 'show logging' for any radio-related messages. Also use 'debug dot11 events' to see real-time radio events. Common symptoms this command helps diagnose include: radio not transmitting (firmware not loaded), intermittent disconnects (high CRC errors), poor performance (low signal-to-noise ratio indicated in other fields), and complete radio failure (hardware status FAIL).

By systematically examining these fields, a network engineer can isolate the root cause of wireless issues that are not visible at the logical interface level.

CCNA Exam Tips

1.

CCNA 200-301 may ask which command to verify radio hardware status; 'show controllers dot11Radio 0' is the answer.

2.

Know that 'State: UP' means the radio is operational; any other state indicates a problem.

3.

High CRC errors or retries often point to RF interference or faulty cables/antennas.

4.

The exam might present output with high noise floor and ask for the likely cause (e.g., co-channel interference).

Common Mistakes

Confusing 'show controllers dot11Radio' with 'show interface dot11Radio'—the former shows hardware details, the latter shows Layer 2 stats.

Assuming 'State: UP' guarantees good performance; high error rates can still exist with an UP state.

Ignoring firmware version mismatches which can cause feature incompatibility or bugs.

show controllers dot11Radio 0 vs show ap summary

These commands are often confused because both relate to wireless interface status, but show controllers dot11Radio 0 is executed on an autonomous access point or router to inspect a specific radio card, while show ap summary is run on a wireless LAN controller to view a list of all associated lightweight access points.

Aspectshow controllers dot11Radio 0show ap summary
ScopeSingle radio interface (e.g., slot 0)All APs managed by the controller
Detail LevelLow-level hardware/firmware details, bitmaps, registersHigh-level summary: name, IP, status, model
Use CaseTroubleshoot RF issues, signal, noise, hardware errorsVerify AP connectivity, registration, operational state
Output FormatTechnical, verbose, often hexadecimalTabular, human-readable summary
EnvironmentAutonomous AP or router with radio interfaceWireless LAN controller (AireOS or IOS-XE)

Use show controllers dot11Radio 0 when you need to diagnose physical layer issues like signal levels, noise, or hardware errors on a specific radio interface.

Use show ap summary when you need to quickly check the registration status, IP addresses, and model of all access points managed by a WLC.

Platform Notes

On Cisco IOS-XE platforms (e.g., Catalyst 9800 WLC, embedded wireless on ISR 4000 series), the command 'show controllers dot11Radio 0' is still available but the output format differs. For example, on a 9800 WLC, the output is more structured and includes additional fields like 'Radio Profile' and 'Channel Width'. On IOS-XE, the command may also be 'show controllers dot11Radio 0 | begin Radio' to filter.

On NX-OS (Cisco Nexus switches), there is no direct equivalent because NX-OS does not support wireless interfaces. For ASA firewalls, wireless interfaces are not supported, so this command does not exist. On IOS-XR, wireless interfaces are not supported either.

Between IOS versions, the output has evolved: in IOS 12.x, the output is more verbose with raw register dumps; in 15.x, it is cleaner with more human-readable fields; in 16.x (IOS-XE), it is even more structured. Some older IOS versions (12.4) may show 'Radio0 - 802.11g' instead of '802.11b/g/n'. Also, on autonomous APs running IOS 15.2(2)JB, the command includes 'DFS Status' fields.

Always check the specific platform documentation for exact field names. For lightweight APs (LAPs) that are controller-based, this command is not available on the AP itself; instead, use the controller's 'show ap dot11 5ghz' or 'show ap dot11 24ghz' commands. In summary, while the command exists across many Cisco wireless platforms, the output varies; engineers should familiarize themselves with the specific syntax and fields for their platform.

Practice for the CCNA 200-301

Test your knowledge with practice questions covering all CCNA 200-301 exam domains.

Practice CCNA 200-301 Questions