Wireless Access

Hello Community, 

I figure out a case which i need to disable te 5ghz without loosing the N.

I founded some ways :

One over the ARM :

http://www.arubanetworks.com/techdocs/ArubaOS_63_Web_Help/Content/ArubaFrameStyles/ARM/ARM_Profiles.htm

(See the screen 1)

Another ways on the VAP config by disabling the "all" to just "g"

What is the correct ways to disabled the 5ghz on a SSID without loosing the n features.

Many thanks in advance.Michael

For an SSID just set it at virtual-ap level.

Many for your reply, but where ?

See GUI virtual-ap for more information. Or CLI virtual-ap for the CLI config.

Parameter to change is "allowed-band".

thanks for your so useful answer !

Does i loose the 802.11n if i put the band on : g ?

802.11n exists ontop of  both 2.4 GHz (g) and 5 GHz (a) bands.

If you set the virtual-ap profile to <g> you will remain with 802.11n on the 2.4GHz band only. 

This means nomore ac or a or "n ontop of a" so hopefully you have a very good reason to do this because you basically just disabled the best WiFi band :)

the reason is that the building have some very heavy wall and the 5ghz works fine on the corridor for example but.... not as expected behind the wall...

For example, good coverage on the coridor which have the ap mounted and not really on rooms which doen't not have ap installed.

The 2.4ghz signal is better on the rooms... and we need wifi on the rooms...

that why i would like to use only the 2.4ghz channel...

Actually the Android (Xperia) phone doesn't not roams as expected... and we've got couples of second of network cut...

By just force the ssid on 2.4ghz, the phone will stay on the band and do not jump between the both band and cut the network..

(works fine and Iphone or Nexus)

If you have some tips and tricks to improve this behaviour do not hesitate to share

Well, if 5GHz doesn't reach the side rooms sufficiantly you realy should look into that. Check if your 5GHz radio is putting out max power. And if it is, you realy should look into deploying more APs if at all possible. 

Placing AP's in a straight corridor isn't best practise. APs will see other APs strongly and think their is high density overage and lower their output power. 

From CLI do a "show ap active". Post the output of that command here if you need some help interpreting it.

You can force APs to use more power by changing the Min Tx EIRP value from the arm profile. Keep in mind that both your 802.11g radio profiles as the 802.11a radoio profile might be using the same arm profile.

You REALY want to have your 5 GHz band for clients.

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
9c:1c:12:ca:b2:91 alone 172.18.10.143 1 AP:HT:11/9/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:28m:31s N/A
9c:1c:12:ca:ae:c3 alone 172.18.10.147 0 AP:HT:11/9/19 0 AP:HT:100+/22/22 105 aKr 148d:6h:4m:7s N/A
9c:1c:12:ca:ae:48 alone 172.18.10.163 0 AP:HT:6/9/19 0 AP:HT:100+/24/24 105 aKr 22d:13h:39m:50s N/A
9c:1c:12:ca:b5:d1 alone 172.18.10.52 0 AP:HT:1/15/19 0 AP:HT:116+/24/24 105 aKr 63d:0h:19m:20s N/A
9c:1c:12:ca:ac:ee alone 172.18.10.56 0 AP:HT:11/9/19 0 AP:HT:52+/22/22 105 aKr 149d:7h:50m:38s N/A
9c:1c:12:ca:be:12 alone 172.18.10.175 1 AP:HT:11/18/19 0 AP:HT:60+/22/22 105 aKr 30d:5h:38m:52s N/A
AP-Refectoire:ce:95:0a alone 172.18.10.191 0 AP:HT:11/9/19 0 AP:HT:100+/24/24 105 aKr 160d:3h:31m:1s N/A
9c:1c:12:ca:b1:4a alone 172.18.10.92 1 AP:HT:11/9/19 0 AP:HT:124+/24/24 105 aKr 160d:3h:27m:4s N/A
9c:1c:12:ca:b5:ed alone 172.18.10.80 0 AP:HT:11/15/19 0 AP:HT:52+/22/22 105 aKr 17h:28m:5s N/A
9c:1c:12:ca:ac:90 alone 172.18.10.76 0 AP:HT:1/9/19 0 AP:HT:100+/21/24 105 aKr 160d:3h:29m:17s N/A
9c:1c:12:ca:ad:05 alone 172.18.10.64 0 AP:HT:6/12/19 0 AP:HT:44+/22/22 105 aKr 160d:3h:28m:29s N/A
9c:1c:12:ca:ac:a7 alone 172.18.10.124 0 AP:HT:11/12/19 0 AP:HT:36+/22/22 105 aKr 160d:3h:32m:48s N/A
9c:1c:12:ca:ac:80 alone 172.18.10.112 1 AP:HT:11/12/19 0 AP:HT:48-/22/22 105 aKr 160d:3h:31m:19s N/A
9c:1c:12:ca:ab:f4 alone 172.18.10.108 0 AP:HT:11/19/19 0 AP:HT:100+/24/24 105 aKr 160d:3h:32m:22s N/A
9c:1c:12:ca:aa:5a alone 172.18.10.96 2 AP:HT:6/9/19 0 AP:HT:132+/24/24 105 aKr 160d:3h:34m:40s N/A
9c:1c:12:ca:aa:09 alone 172.18.10.136 2 AP:HT:6/19/19 0 AP:HT:124+/24/24 105 aKr 160d:3h:27m:53s N/A
9c:1c:12:ca:b0:55 alone 172.18.10.148 0 AP:HT:11/9/19 0 AP:HT:100+/24/24 105 aKr 160d:3h:32m:21s N/A
9c:1c:12:ca:b2:a8 alone 172.18.10.152 0 AP:HT:11/9/19 0 AP:HT:60+/24/24 105 aKr 160d:3h:33m:28s N/A
9c:1c:12:ca:ac:65 alone 172.18.10.164 0 AP:HT:6/9/19 0 AP:HT:60+/22/22 105 aKr 160d:3h:27m:46s N/A
9c:1c:12:ca:af:ab alone 172.18.10.51 0 AP:HT:11/19/19 0 AP:HT:40-/22/22 105 aKr 126d:23h:22m:1s N/A
9c:1c:12:ca:ac:4d alone 172.18.10.63 0 AP:HT:11/9/19 0 AP:HT:116+/24/24 105 aKr 160d:3h:28m:28s N/A
9c:1c:12:ca:ab:d5 alone 172.18.10.168 0 AP:HT:6/9/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:29m:27s N/A
9c:1c:12:ca:ae:55 alone 172.18.10.180 0 AP:HT:1/19/19 0 AP:HT:124+/24/24 105 aKr 160d:3h:32m:16s N/A
9c:1c:12:ca:ab:b4 alone 172.18.10.184 0 AP:HT:1/12/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:30m:40s N/A
9c:1c:12:ca:be:28 alone 172.18.10.91 1 AP:HT:11/9/19 0 AP:HT:116+/21/24 105 aKr 160d:3h:35m:12s N/A
9c:1c:12:ca:b5:e3 alone 172.18.10.87 0 AP:HT:11/9/19 0 AP:HT:116+/24/24 105 aKr 133d:0h:34m:37s N/A
9c:1c:12:ca:ab:68 alone 172.18.10.75 0 AP:HT:6/9/19 0 AP:HT:36+/22/22 105 aKr 160d:3h:29m:20s N/A
9c:1c:12:ca:bd:e1 alone 172.18.10.71 1 AP:HT:6/9/19 0 AP:HT:116+/21/22 105 aKr 160d:3h:29m:49s N/A
9c:1c:12:ca:b5:56 alone 172.18.10.123 0 AP:HT:6/9/19 1 AP:HT:48-/22/22 105 aKr 160d:3h:29m:59s N/A
9c:1c:12:ca:af:21 alone 172.18.10.119 0 AP:HT:6/9/19 0 AP:HT:44+/22/22 105 aKr 2d:9h:20m:11s N/A
9c:1c:12:ca:ab:92 alone 172.18.10.107 0 AP:HT:1/9/19 0 AP:HT:44+/22/22 105 aKr 160d:3h:31m:54s N/A
9c:1c:12:ca:b0:a3 alone 172.18.10.103 0 AP:HT:6/9/19 0 AP:HT:60+/22/22 105 aKr 160d:3h:33m:32s N/A
9c:1c:12:ca:bd:7a alone 172.18.10.133 0 AP:HT:6/12/19 0 AP:HT:60+/22/22 105 aKr 160d:3h:33m:15s N/A
9c:1c:12:ca:aa:75 alone 172.18.10.137 0 AP:HT:1/9/19 0 AP:HT:116+/24/24 105 aKr 160d:3h:33m:24s N/A
9c:1c:12:ca:ac:b9 alone 172.18.10.149 0 AP:HT:1/9/19 0 AP:HT:124+/24/24 105 aKr 160d:3h:28m:18s N/A
9c:1c:12:ca:b6:8c alone 172.18.10.153 0 AP:HT:1/9/19 0 AP:HT:100+/21/22 105 aKr 2d:16h:11m:49s N/A
9c:1c:12:ca:b6:2a alone 172.18.10.165 0 AP:HT:1/19/19 0 AP:HT:52+/22/22 105 aKr 160d:3h:31m:3s N/A
EXT-06:40:e8 Outdoor 172.18.10.50 0 AP:HT:11/9/19 0 AP:VHT:116E/24/28 275 AaKr 160d:3h:32m:35s N/A
9c:1c:12:ca:bd:86 alone 172.18.10.62 1 AP:HT:1/9/19 0 AP:HT:52+/22/22 105 aKr 160d:3h:28m:20s N/A
9c:1c:12:ca:be:b7 alone 172.18.10.169 4 AP:HT:6/9/19 1 AP:HT:48-/22/22 105 aKr 160d:3h:32m:2s N/A
EXT-01:7b:24 Outdoor 172.18.10.181 0 AP:HT:1/9/19 0 AP:HT:124+/24/24 114 oaKr 67d:12h:20m:27s N/A
9c:1c:12:ca:ac:8e alone 172.18.10.185 0 AP:HT:1/12/19 0 AP:HT:124+/24/24 105 aKr 126d:21h:47m:22s N/A
9c:1c:12:ca:b6:51 alone 172.18.10.86 0 AP:HT:11/19/19 0 AP:HT:60+/22/22 105 aKr 147d:1h:14m:25s N/A
9c:1c:12:ca:aa:c6 alone 172.18.10.74 1 AP:HT:6/9/19 0 AP:HT:108+/21/24 105 aKr 25d:10h:12m:22s N/A
9c:1c:12:ca:b0:08 alone 172.18.10.209 0 AP:HT:6/9/19 0 AP:HT:108+/24/24 105 aKr 133d:7h:38m:57s N/A
9c:1c:12:ca:b1:3d alone 172.18.10.70 0 AP:HT:11/9/19 0 AP:HT:44+/22/22 105 aKr 160d:3h:29m:16s N/A
9c:1c:12:ca:ab:ce alone 172.18.10.122 0 AP:HT:1/9/19 0 AP:HT:60+/22/22 105 aKr 160d:3h:31m:52s N/A
9c:1c:12:ca:be:b8 alone 172.18.10.118 1 AP:HT:1/9/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:32m:22s N/A
9c:1c:12:ca:aa:b6 alone 172.18.10.106 0 AP:HT:11/9/19 0 AP:HT:132+/24/24 105 aKr 160d:3h:32m:21s N/A
9c:1c:12:ca:c0:44 alone 172.18.10.102 1 AP:HT:6/19/19 0 AP:HT:36+/22/22 105 aKr 63d:23h:59m:58s N/A
9c:1c:12:ca:ac:d2 alone 172.18.10.130 0 AP:HT:1/12/19 1 AP:HT:36+/22/22 105 aKr 160d:3h:27m:34s N/A
9c:1c:12:ca:b0:d5 alone 172.18.10.142 1 AP:HT:11/9/19 0 AP:HT:124+/24/24 105 aKr 160d:3h:34m:42s N/A


Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
EXT-10:65:b8 Outdoor 172.18.10.109 0 AP:HT:11/9/19 0 AP:HT:132+/21/24 114 oaKr 160d:3h:31m:31s N/A
9c:1c:12:ca:aa:06 alone 172.18.10.97 0 AP:HT:6/12/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:30m:50s N/A
9c:1c:12:ca:aa:cb alone 172.18.10.135 0 AP:HT:6/9/19 0 AP:HT:116+/24/24 105 aKr 160d:3h:28m:52s N/A
9c:1c:12:ca:ac:8f alone 172.18.10.139 0 AP:HT:1/12/19 0 AP:HT:108+/21/24 105 aKr 160d:3h:34m:3s N/A
9c:1c:12:ca:bd:9b alone 172.18.10.151 1 AP:HT:1/9/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:31m:38s N/A
9c:1c:12:ca:b5:3d alone 172.18.10.155 3 AP:HT:6/9/19 7 AP:HT:40-/22/22 105 aKr 160d:3h:27m:5s N/A
9c:1c:12:ca:ac:4b alone 172.18.10.167 1 AP:HT:6/9/19 0 AP:HT:116+/24/24 105 aKr 160d:3h:32m:47s N/A
9c:1c:12:ca:b1:0c alone 172.18.10.60 0 AP:HT:6/9/19 0 AP:HT:132+/21/24 105 aKr 148d:6h:40m:12s N/A
9c:1c:12:ca:c1:bc alone 172.18.10.171 0 AP:HT:1/19/19 1 AP:HT:60+/22/22 105 aKr 150d:3h:24m:40s N/A
9c:1c:12:ca:ab:fe alone 172.18.10.183 0 AP:HT:6/9/19 0 AP:HT:52+/22/22 105 aKr 160d:3h:27m:5s N/A
9c:1c:12:ca:ad:06 alone 172.18.10.88 0 AP:HT:1/9/19 0 AP:HT:52+/21/22 105 aKr 160d:3h:35m:50s N/A
9c:1c:12:ca:aa:3e alone 172.18.10.72 0 AP:HT:11/9/19 0 AP:HT:116+/24/24 105 aKr 160d:3h:28m:47s N/A
9c:1c:12:ca:b6:18 alone 172.18.10.68 0 AP:HT:1/18/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:30m:14s N/A
9c:1c:12:ca:b6:0b alone 172.18.10.120 1 AP:HT:6/9/19 0 AP:HT:60+/21/22 105 aKr 160d:3h:29m:28s N/A
9c:1c:12:ca:ab:5e alone 172.18.10.104 0 AP:HT:11/9/19 0 AP:HT:108+/24/24 105 aKr 160d:3h:32m:8s N/A
9c:1c:12:ca:ab:dc alone 172.18.10.100 1 AP:HT:11/9/19 0 AP:HT:132+/24/24 105 aKr 160d:3h:33m:39s N/A
9c:1c:12:ca:b6:64 alone 172.18.10.128 2 AP:HT:11/18/19 0 AP:HT:124+/21/24 105 aKr 160d:3h:30m:20s N/A
9c:1c:12:ca:ac:10 alone 172.18.10.140 1 AP:HT:1/9/19 0 AP:HT:52+/22/22 105 aKr 160d:3h:31m:3s N/A
9c:1c:12:ca:b6:02 alone 172.18.10.144 0 AP:HT:11/9/19 0 AP:HT:108+/24/24 105 aKr 31d:1h:28m:53s N/A
9c:1c:12:ca:ab:cd alone 172.18.10.156 0 AP:HT:6/9/19 0 AP:HT:124+/21/24 105 aKr 160d:3h:28m:21s N/A
9c:1c:12:ca:b5:cf alone 172.18.10.55 0 AP:HT:6/9/19 0 AP:HT:132+/21/24 105 aKr 148d:7h:14m:34s N/A
EXT-03:7b:42 Outdoor 172.18.10.160 0 AP:HT:1/9/19 0 AP:HT:100+/24/24 114 oaKr 160d:3h:30m:40s N/A
9c:1c:12:ca:ab:77 alone 172.18.10.59 1 AP:HT:11/9/19 0 AP:HT:52+/22/22 105 aKr 160d:3h:33m:37s N/A
9c:1c:12:ca:ad:7d alone 172.18.10.172 0 AP:HT:1/12/19 0 AP:HT:124+/24/24 105 aKr 160d:3h:32m:46s N/A
9c:1c:12:ca:b1:57 alone 172.18.10.176 1 AP:HT:1/12/19 0 AP:HT:100+/24/24 105 aKr 160d:3h:31m:26s N/A
9c:1c:12:ca:ac:74 alone 172.18.10.95 1 AP:HT:11/9/19 0 AP:HT:60+/22/22 105 aKr 160d:3h:30m:38s N/A
9c:1c:12:ca:b1:2e alone 172.18.10.83 2 AP:HT:1/9/19 0 AP:HT:124+/21/24 105 aKr 147d:0h:15m:43s N/A
9c:1c:12:ca:b9:03 alone 172.18.10.127 0 AP:HT:11/9/19 0 AP:HT:44+/21/22 105 aKr 15d:23h:8m:22s N/A
9c:1c:12:ca:ab:a1 alone 172.18.10.115 1 AP:HT:11/19/19 0 AP:HT:132+/21/24 105 aKr 37d:1h:47m:10s N/A

9c:1c:12:ca:b9:16 alone 172.18.10.170 0 AP:HT:6/19/19 0 AP:HT:52+/22/22 105 aKr 160d:3h:32m:45s N/A
EXT-04:7b:2c Outdoor 172.18.10.182 0 AP:HT:1/9/19 0 AP:HT:100+/24/24 114 oaKr 160d:3h:25m:10s N/A
EXT-02:d9:58 Outdoor 172.18.10.186 1 AP:HT:11/19/19 0 AP:VHT:112E/24/28 275 AaKr 160d:3h:32m:27s N/A
9c:1c:12:ca:ab:ca alone 172.18.10.89 0 AP:HT:6/19/19 0 AP:HT:132+/24/24 105 aKr 160d:3h:34m:50s N/A
9c:1c:12:ca:b2:63 alone 172.18.10.73 0 AP:HT:11/9/19 0 AP:HT:60+/22/22 105 aKr 12d:0h:16m:35s N/A
9c:1c:12:ca:b6:69 alone 172.18.10.69 1 AP:HT:6/9/19 4 AP:HT:48-/22/22 105 aKr 160d:3h:34m:2s N/A
9c:1c:12:ca:ab:90 alone 172.18.10.121 0 AP:HT:6/9/19 0 AP:HT:124+/21/24 105 aKr 160d:3h:33m:18s N/A
9c:1c:12:ca:b7:c0 alone 172.18.10.117 0 AP:HT:11/9/19 1 AP:HT:44+/22/22 105 aKr 160d:3h:33m:1s N/A
9c:1c:12:ca:ab:29 alone 172.18.10.105 1 AP:HT:6/9/19 0 AP:HT:132+/21/24 105 aKr 16d:14h:41m:40s N/A
9c:1c:12:ca:ab:12 alone 172.18.10.101 2 AP:HT:1/19/19 0 AP:HT:100+/24/24 105 aKr 160d:3h:30m:19s N/A
Flags: 1 = 802.1x authenticated AP; 2 = Using IKE version 2;
A = Enet1 in active/standby mode; B = Battery Boost On; C = Cellular;
D = Disconn. Extra Calls On; E = Wired AP enabled; F = AP failed 802.1x authentication;
H = Hotspot Enabled; K = 802.11K Enabled; L = Client Balancing Enabled; M = Mesh;
N = 802.11b protection disabled; P = PPPOE; R = Remote AP;
S = AP connected as standby; X = Maintenance Mode;
a = Reduce ARP packets in the air; d = Drop Mcast/Bcast On; u = Custom-Cert RAP;
i = Provisioned as Indoor; o = Provisioned as Outdoor;
r = 802.11r Enabled
Channel followed by "*" indicates channel selected due to unsupported configured channel.
"Spectrum" followed by "^" indicates Local Spectrum Override in effect.
Num APs:127


ARM settings :

802.11a :Max TX EIRP : 24 / Min Tx EIRP : 21
802.11g:Max TX EIRP : 21 / Min Tx EIRP : 9

Well, most of your a-radios seem to be outputting max or near  max. 

Je might increas your min Tx in the arm profile for the a-radio to 24 and see if that makes a difference.. hopefully you are lucky.

Otherwise you're only real option is to place more APs to stay working with 5GHz.

Sorry for your feedback,  But you asked me to put the Min EIRP values for the ARM "a" profile to 24 ?

I don't really understand... the settings are : 802.11a :Max TX EIRP : 24 / Min Tx EIRP : 21

Which it's means that the Min and the Max will have the same settings ?

With 21 min - 24 max, APs can lower their outputpower to minimum 21 dBm.

By changing the min Tx to the same value as max Tx (24) you take away the choice from the AP, it will output 24dBm after setting this, increasing coverage a bit for APs that weren't already @ 24dBm.

And 24 is probably the max your regulatory domain will allow for ithose APs.

yes it's the max.

No chance to create some noise on the network ? 

Or overlapping between two AP on 5ghz ?

Sorry with my stupid question, i'm trying to well understand the matter

sure, there might be overlap in the corridor, but coverage with some overlap is better than no coverage (turned off)  right?

That said, you should have 10 channels in the 5GHz band so overlap shouldn't be horrible.

I just noticed most of your 2.4GHz radios are actually at quit low power. You are sure those 5GHz radios don't work properly because of low signal?  It's possible, but still sounds a bit weird to me. My experience is that I don't usualy see lower coverage from 5GHz when it has ~10dB more Tx power than the 2.4GHz radios.

global information, the network was made for the RTLS over the wifi.

We have a dense AP area, that could explain the lower signal for the 2.4ghz.

Do you have some advice ? of things to check ? 

Not realy.. 

Measure the 5GHz signal near an AP, move in the room where you think the low signal is and actually measure.

If you actualy verified this there isn't much more to do other than place more APs or give up 5GHz completely.