6GHz transmit power

Solved
DevOps_RC
Getting noticed

6GHz transmit power

Good Morning, We are about to enable a public access WPA3 SSID on our infrastructure, and as such the 6GHz radios will now be utilised on our C9162 & C9164 APs (internal antennas). I tend to leave the APs associated with the same Default Power profile and just tweak it slightly on 5Ghz, to disable 802.11b devices from connecting.

I noticed that by default the 2.4GHz has a transmit power range of 5-30, 5GHz has a transmit power range of 8-30, but the 6GHz has a transmit power range of 1-8. Apart from reducing the power requirements for the AP and the regulations regarding power levels on the 6GHz range (Diagram at the bottom), is there any reason not to increase the transmit power range too 1-24, while still allowing the APs to adjust power levels automatically? I appreciate that increasing the power will increase the coverage at the expense of data rates. Our 5Ghz APs tend to be using transmit power in the range of 15-18dBm, so I'd expect for the 6Ghz to get the same coverage, they would need to be in a similar power transmit range, maybe 16-19....Anyone have any experience?

DevOps_RC_0-1705920867534.png

 

1 Accepted Solution
cmr
Kind of a big deal
Kind of a big deal

On my network with CW916x APs the default settings for auto power are 8-30 as below:

 

cmr_0-1705922010769.png

 

The one AP that I have 6GHz enabled on has chosen 16dB, which is similar but slightly higher than the 5GHz radio as you'd expect:

 

cmr_1-1705922165640.png

 

If my answer solves your problem please click Accept as Solution so others can benefit from it.

View solution in original post

5 Replies 5
cmr
Kind of a big deal
Kind of a big deal

On my network with CW916x APs the default settings for auto power are 8-30 as below:

 

cmr_0-1705922010769.png

 

The one AP that I have 6GHz enabled on has chosen 16dB, which is similar but slightly higher than the 5GHz radio as you'd expect:

 

cmr_1-1705922165640.png

 

If my answer solves your problem please click Accept as Solution so others can benefit from it.
DevOps_RC
Getting noticed

Thanks for the quick reply. Maybe someone 'accidently adjusted' the power rating for 6Ghz for the network I checked earlier. I created a new network, associated an AP and  checked the power rating...and turns out someone did (Finger pointing to commence shortly).

Thanks for confirming the expected default power range.

GIdenJoe
Kind of a big deal
Kind of a big deal

I guess we need some end point manufacturer info about what the typical maximum Tx powers will be of laptops, smartphones etc...

 

If you know the FCC ID of a certain device you could lookup the documentation.  I have been looking at tests for apple products and I do find stuff like antenna gains and transmitpowers.  But you really need to look hard.

PhilipDAth
Kind of a big deal
Kind of a big deal

Interesting.  I use a custom RF profile rather than the defaults on my network - so the default RF profiles have never been changed.

 

On both my indoor and outdoor profile, the 6Ghz was set to use a minimum and maximum of 30.  I then used the "Reset to Meraki defaults" option in both profiles, and they are now show this:

 

PhilipDAth_0-1705951978399.pngPhilipDAth_1-1705952052000.png

 

Weird.

DevOps_RC
Getting noticed

Thats interesting. I checked the settings of the new network I created yesterday and they had the following settings:

DevOps_RC_0-1706002084582.png

I then clicked on 'Restore to Meraki Default' and ...the 6GHz was set too power range 0-8??:

DevOps_RC_1-1706002216554.png

 

Then went and checked that the country the network was assigned (automatically) was UK, didn't make a change, and then checked the power range values again, and they have changed in the background??..:

DevOps_RC_2-1706004294753.png

I can only guess there is a slight delay with the 'defaults' being applied, and then them being adjusted depending on country network is assigned to.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels