WLC and AP Power settings

AP Power settings made easy

To fully understand and sometimes troubleshoot our wireless networks, we need to know exactly what is going on with our AP s, especially what power they are outputting. So in this post we are going to look at AP Power settings made easy.

A man is drawing a diagram of an internet network

The Problem – Different AP models each have their own Power Levels

The problem we face is that different models of AP, each have their own set of power levels.

Cisco only tells us a number between 1 and X. 1 is full power, every number we add to it is a decrease of 3dB. Some APs go to 5, some go to 8. The same AP on 2.4GHz can have a different range on 5GHz.

This is further complicated by moving an AP from one UNII band in 5GHz to another, still in 5GHz, can completely change its power level range.

What we need is a simple easy way to know exactly what is going on with our power ranges, and what an AP’s power level is set to.

Well, never fear, Cisco has given us tools to help us with this.

The command ” show ap config 802.11a <ap_name> ” will show us lots of information about the power settings, see Table 1 below. We see the number of supported levels, how they map to dBm, the current power level, and whether the power has been set manually or by RRM.

Note: there is a lot of output from this command, the output shown is a snippet from several pages down – you need to press “spacebar” several times to get to this. It usually comes right after the speeds!

 

Table 1: “show ap config 802.11a <ap_name>” output (WLC 5508 8.5 code, 3602 AP)

Tx Power
Num Of Supported Power Levels … 8
Tx Power Level 1 ……………………….. 23 dBm
Tx Power Level 2 ………………………. 20 dBm
Tx Power Level 3 ………………………. 17 dBm
Tx Power Level 4 ………………………. 14 dBm
Tx Power Level 5 ………………………. 11 dBm
Tx Power Level 6 ……………………….. 8 dBm
Tx Power Level 7 ……………………….. 5 dBm
Tx Power Level 8 ………………………. 2 dBm
Tx Power Configuration …………….. CUSTOMIZED
Current Tx Power Level ……………… 3
Tx Power Assigned By ……………….. User

 

In fact, pressing spacebar again gives us more information about the AP channel, we can see this in table 2 below.

Table 2: further output of “show ap config 802.11a <ap_name>” command output (WLC 5508 8.5 code, 3602 AP)

Phy OFDM parameters
Configuration ……………………….. CUSTOMIZED
Current Channel …………………… 149
Channel Assigned By …………….. User
Extension Channel ……………. …. ABOVE
Channel Width………………….. …. 40 MHz
Allowed Channel List……………… 36,40,44,48,52,56,60,64,100,
…………………………………………….. 104,108,112,116,132,136,140,
…………………………………………….. 149,153,157,161,165

 

Here, we can see the current channel set, the channel width, is the extension above or below the current channel (in this case 802.11n +1 channel bonding). We can also see the allowed channels, and whether the channel selection has been set manually or by RRM.

Connecting to the AP (I consoled into the AP CLI, as I did with the WLC), we see it also has some commands we can use.

”show controllers dot11radio 1 freq” will show us the frequency and the channel we are on, as well as other channels supported, see Table 3 below. (In this case “controllers” refers to the hardware controller in the interface, not the WLC – controller).

 

Table 3: “show controllers dot11radio 1 freq” output (WLC 5508 8.5 code, 3602 AP)

Carrier Set: United states (US) (-A)
Uniform Spreading Required: Yes
Configured Frequency: 5745 MHz Channel 149 40MHz, extended above
Serving Frequency: 5745 MHz Channel 149 40MHz, extended above
Allowed Frequencies: * Dynamic Frequency Selection (DFS) only
5180( 36) 5200( 40) 5220( 44) 5240( 48) *5260( 52) *5280( 56) *5300( 60) *5320( 64) *5500(100) *5520(104) *5540(108) *5560(112) *5580(116) *5660(132) *5680(136) *5700(140) 5745(149) 5765(153) 5785(157) 5805(161) 5825(165)

Listen Frequencies:
5180( 36) 5200( 40) 5220( 44) 5240( 48) 5260( 52) 5280( 56) 5300( 60) 5320( 64) 5500(100) 5520(104) 5540(108) 5560(112) 5580(116) 5600(120) 5620(124) 5640(128) 5660(132) 5680(136) 5700(140) 5720(144) 5745(149) 5765(153) 5785(157) 5805(161) 5825(165)
Beacon Flags: 0, Interface Flags 2020105, Interface Events 0, Mode 9; Beacons are enabled; Probes are enabled

 

Note: The text has scrolled over the end-of-line, I left it like this, as this is how it appears on the screen.

Another command typed on the AP “ show controllers dot11radio powercfg ” will show us the number of power levels, the range of power levels allowed, and the current power level setting. (In this case “controllers” again refers to the hardware controller in the interface, not the WLC – controller).

 

Table 4: “show controller dot11radio 1 powercfg” output (WLC 5508 8.5 code, 3602 AP)

Configured TxPower: 17 dBm (Level Index 3)
Allowed Power Levels: 23 20 17 14 11 8 5 2 dBm
Allowed Client Power Levels: 23 20 17 14 11 8 5 2 dBm

So, there we have it. We now have an easy way to determine the power levels in use from the WLC’s and the AP’s perspectives.

See you next time!

 

If you are looking to make your mark in the IT Industry, then NC-Expert offers excellent training courses aimed at relevant IT industry certifications – contact us today to get started.

NC-Expert Blog

Wi-Fi Myth Series - Myth #11: Interference Is Always Someone Else’s Wi-Fi

By Rie Morgan • August 20, 2026
When Wi-Fi performance suddenly deteriorates, interference is often the first culprit to be suspected and, when this (interference) enters the conversation, attention tends to turn immediately toward neighboring Wi-Fi networks. “Someone must have installed another AP.” “The office next door is probably using our channel.” “There are too many SSIDs around here.” Sometimes, this diagnosis is exactly right, but RF interference has a much larger cast of characters than just neighboring APs. In fact, some of the most frustrating wireless problems occur when the interfering device isn’t speaking 802.11 at all! The spectrum doesn’t particularly care whether the energy occupying it came from an enterprise AP, a Bluetooth headset, a microwave oven, or something considerably stranger. To a Wi-Fi radio trying to communicate, unwanted RF energy is simply unwanted RF energy. Wi-Fi Has to Share the Neighborhood The 2.4 GHz band has always been something of an RF “community center”. Wi-Fi operates alongside Bluetooth, Zigbee and other technologies, while various consumer, industrial, medical, and electronic devices may also generate energy within or around the same spectrum. Microwave ovens are perhaps the most famous example. Their emissions can interfere with 2.4 GHz Wi-Fi, particularly when clients are operating nearby. Bluetooth devices, cordless equipment, wireless cameras, sensors, and other transmitters can also contribute RF energy. Some interferers transmit continuously. Others appear periodically. Some hop frequencies. Others produce wideband noise. That last category can be particularly entertaining to troubleshoot... in the very specific sense of “entertaining” that wireless engineers use when they have been staring at spectrum analysis for three hours! The important point is that interference doesn’t need to understand Wi-Fi to disrupt it.

Wi-Fi Myth Series - Myth #10: The AP Is Up, So the Wi-Fi Must Be Fine

By Rie Morgan • August 13, 2026
There is something wonderfully reassuring about seeing a row of green APs on a wireless dashboard: APs connected; radios operational; no obvious alarms; everything green. Excellent! The Wi-Fi must be fine... Except, of course, the users are complaining that Teams calls are breaking up, handheld scanners keep disconnecting, authentication takes forever, and someone in Accounting has discovered that turning Wi-Fi off and back on again temporarily fixes everything. Welcome to one of the more persistent myths in enterprise wireless: if the AP is up, the Wi-Fi must be working. An operational AP tells us something useful... but it tells us surprisingly little about the experience of the clients actually using the network. “Up” is an Infrastructure State When a monitoring platform reports that an AP is up, it usually means the infrastructure can communicate with it. It tells us: - the AP has power - its Ethernet connection is functioning - it may have established its management or CAPWAP connection - its radios are probably operational - it hasn't disappeared into the networking equivalent of a “black hole” ...all good things. But none of those things proves that a client can successfully use an application. Consider what still has to happen after the AP proudly announces its existence. A client must: discover the WLAN associate authenticate obtain the appropriate network configuration reach its default gateway resolve DNS access the required network resources, and maintain sufficient RF performance to exchange data reliably. Depending on the environment, that journey may involve: 802.1X RADIUS DHCP DNS VLANs ACLs firewalls roaming mechanisms upstream switching WAN connectivity cloud services ...and several other systems waiting for their opportunity to make your afternoon more “interesting”. ;-) The AP actually being operational is merely one part of that chain!

Wi-Fi Myth Series – Myth #9: More Bandwidth Always Means Better Performance

By Rie Morgan • August 6, 2026
If there's one thing network users love, it's bandwidth. Need faster Wi-Fi? More bandwidth. Application running slowly? More bandwidth. Video buffering? More bandwidth. Someone sneezed near the wireless network? Probably needs more bandwidth. :) As Wi-Fi engineers, we've all heard it. Somewhere along the way, bandwidth became synonymous with performance. But while bandwidth certainly matters, it's only one ingredient in a much larger recipe. In many deployments, increasing available bandwidth produces little improvement and, in some cases, it can actually make things worse! Like many Wi-Fi myths, this one contains just enough truth to be convincing. Let's bust it...