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 #6: A Site Survey Is Optional

By Rie Morgan • July 17, 2026
Every Wi-Fi engineer has heard some version of it, "Can't we just install the access points where the old ones were?" Or perhaps, "The floorplan looks straightforward. Let's save some time and skip the survey." Occasionally, someone even says the dangerous words, "We've done hundreds of these buildings. They're all basically the same." That's usually the point where experienced wireless engineers quietly smile, knowing that the building is about to teach everyone a valuable lesson because: buildings don't read design guides, concrete doesn't care about your deployment schedule, metal doesn't respect your project budget, and radio waves have never once agreed to cooperate, simply because everyone wanted them to. Let's talk about why a site survey isn't an optional luxury... it's one of the most valuable engineering tools available. Every Building Is Different At first glance, two office buildings may appear identical: same square footage, same number of floors, similar room layouts, yet their wireless behavior can be dramatically different: one may have reinforced concrete walls, another may contain extensive glass partitions, the warehouse may be filled with moving inventory, a hospital may have elevators, imaging equipment, and countless reflective surfaces, a manufacturing facility may contain machinery that wasn't mentioned on any floorplan, and remember: even furniture changes RF behavior! Anyone who has performed enough surveys eventually develops a healthy respect for one simple fact: the building always gets a vote, too!

Wi-Fi Myth Series - Myth #5: Wider Channels Always Mean Better Performance

By Rie Morgan • July 13, 2026
There is something wonderfully satisfying about seeing a Wi-Fi channel get wider: twenty megahertz becomes forty. Forty becomes eighty. Eighty becomes one hundred and sixty. This begs the question: more bandwidth must mean more speed... right? Well... sometimes. Like many things in Wi-Fi engineering, the answer begins with, "It depends." The idea that wider channels always deliver better performance has become surprisingly common. It's an understandable conclusion because, in theory, wider channels can carry more data. More lanes on a highway should allow more traffic to flow. But Wi-Fi isn't driven by theory alone. The RF environment has an annoying habit of reminding us that physics always gets the final vote. Let's explore why bigger isn't always better... More Lanes... But Fewer Roads Imagine a city with only a handful of highways. If you combine four lanes into one giant superhighway, each individual vehicle might travel faster. Unfortunately, you've also eliminated several independent routes that other drivers could have used. That's exactly what happens with channel bonding: - An 80 MHz channel occupies the same spectrum as four adjacent 20 MHz channels. - A 160 MHz channel consumes eight. While you've increased the potential throughput available to one transmission, you've dramatically reduced the number of separate channels available for everyone else. In an empty environment, this is often perfectly acceptable. But, in a busy enterprise? Not so much.

Wi-Fi Myth Series – Myth #4: If Coverage is Good, Capacity Will Be Fine

By Rie Morgan • July 8, 2026
Walk into almost any office after a new Wi-Fi deployment and you'll hear a familiar sentence: "Coverage looks great. We should be good." It sounds logical. After all, if every corner of the building has a healthy signal, surely the network can handle whatever users throw at it. Except... that's not how Wi-Fi works. Coverage and capacity are close friends, but they're definitely not twins. One answers the question, "Can devices hear the network?" The other answers, "Can everyone actually use it at the same time?" Confusing the two is one of the most common mistakes in Wi-Fi design, and it often explains why a network that looks fantastic on a heatmap still leaves users frustrated.  Let's bust this myth once and for all.