Wireless Access

Changing the min and max on EIRP for RF, from 18/21 to 6/15, does it take affect straight away or do you have to wait until the next airmatch database update?

I understand that its best to not change these values but we continue to experience wireless issues after upgrade from 6.5.4.9 to 8.3.0.3 (+ additional MM controller)

And as i understand it, RF power is taken into account, whereas ARM is ignored. Is it best practice to manually update the power because you read in a lot of places to leave everything as default with ArubaOS8 on MM...

- If you have an MM, you are using Airmatch and not ARM.

- Transmit power range is regulated by "Transmit EIRP" in the radio profiles (Min and Max EIRP), not the ARM profiles for each band.

- The Airmatch "solution" is run by default at 5am every morning to reflect the radio profile changes

- For Airmatch to run  before 5am you need to run the "airmatch runnow" command:

 https://www.arubanetworks.com/techdocs/ArubaOS_85_Web_Help/Content/arubaos-solutions/1cli-commands/airmatch-runnow.htm?Highlight=runnow

- It is perfectly normal and recommended to constrain the power on AP radios, just like you did with Min TX and Max TX power with ARM.

- It is also perfectly normal and recommended to constrain the Max channel bandwidth and Min channel bandwidth in the 5ghz Radio Profile to 20 or 40, so that you are not running 80mhz channels.

Thanks for the reply cjoseph.

Does chaging the power take affect immediatly or after the next airmatch database update?

At 5am.

Final question on this one, i promise :-)

Is that 5am local time on the MC or MM?

We have all our controllers set to UTC time, globally that is...

It will run based on the timezone on the MD (MC).  This can be overridden by configuring the Airmatch deploy-hour parameter https://www.arubanetworks.com/techdocs/ArubaOS_85_Web_Help/Content/arubaos-solutions/1cli-commands/airmatch-prof.htm?Highlight=deploy-hour