Wireless Access

Hello,

I have a few of those guys ArubaOS (MODEL: 325), Version 6.5.4.3, like stand alone WAPs, without a controller.

Spend a lot of time to figure out how to set channels and power over the config file. According to this useful thread, it's an ap-env variables, and they can be set up over a cli as well as a web interface.

I found one solution - to create a config file in way like this (let's called it tftp config):

----env start----
name guest-wap3
wifi0_arm_channel 36
wifi0_arm_power 40
wifi1_arm_channel 1
wifi1_arm_power 40
standalone_mode 1
----env end----
----config start----
version 6.5.4.0-6.5.4
virtual-controller-country us
....

----config end----

and then upload it over tftp - it works fine, but if you'll try to upload it from the web page it raises an error. Anyway it's better then nothing, but I still have two question according to this:

1) when I try to set some channel/power over the web the result would be like this:

but in the cli  wifi*_arm_power changed to wifi*_arm_power_10x:

# show ap-env

wifi0_arm_channel:36
wifi0_arm_power_10x:40.0
wifi1_arm_channel:1
wifi1_arm_power_10x:40.0

what does that mean?

I've tried to apply those settings (ch. 36 power 40, ch.1 power 40) over a tftp config and the result was a little bit different:

wifi0_arm_channel:36
wifi0_arm_power:20
wifi1_arm_channel:1
wifi1_arm_power:20

there is no power_10x and power now 20 only...

2) can't apply over tftp config 80MHz channels for 5GHz radio. For example you can select E channels (like 36E, 52E, 100E and so on ) in the web as well as set them over the cli manually and the result would be:

wifi0_arm_channel:116E
wifi0_arm_power_10x:40.0

but if use tftp config it'll be:

wifi0_arm_channel:116
wifi0_arm_power:20.0

and now it's not a question in arm power, let it be even half, why it can't apply 116E and does 116? Maybe I have to use another notation?

Thanks for any thoughts.

You can't set the power to 40 dBm, it's always limited by your regulatory domain.

Do you have IAP-325s? Are they in a cluster (recommended) or deployed as single APs in different sites?

The supported methods of configuring Instant are:

- WebUI (local)

- CLI (local)

- Airwave (central, on-prem)

- Aruba Central (central, public-cloud management)

Also, it is deprecated to set power and channel manually in most situations. Instead, use Adaptive Radio Management (ARM) to get the optimal channel and power settings, and if you are not happy with that, tune ARM to get closer to what you prefer by setting more strict boundaries in the channel/power selection. For that reason, there is no broad support to do manual configuration of channel/power, and only few customers do so.

You may try to contact Aruba support to assist you with this tftp configuration, but they may tell you that it is not supported.