AOS8 - config failure after changing regulatory domain settings

[SkiP]

Dear all!

On a newly installed system, I would like to set which channels the APs can use. At the appropriate level (MD group) on the Mobility Master, AP Group -> <groupname> -> Profiles -> AP -> Regulatory Domain displays the ap-group specific RD profile (<apgroupname> _rdp_ui), and I have blocked some 5GHz channels (like channel 165).

After I deployed the configuration, I received the following errors:

(MobilityMaster) [mynode] #show configuration failure all

All Configuration Failure
-------------------------
IP Address    MAC                Config ID  Process          Command                    Message
----------    ---                ---------  -------          -------                    -------
10.75.75.137  20:4c:03:2b:4d:3c  51         Profile Manager  no valid-11a-channel 165   Item not in list
10.75.75.138  20:4c:03:2b:4e:5c  51         Profile Manager  no valid-11a-channel 165   Item not in list

Total switches with config failures::2

I got same errors if I disabled channel 149, 153, 157 and 161 example.

How do I make the desired changes without getting errors?

Thanks!

[SkiP]

Does anyone have an idea about this?

Thanks!

[Craig Syme]

Whats the AP model (eg 305US or ROW) and the regulatory domain currently set to? Are you also using bonded channels within your environment?

[SkiP]

AP315 and AP345 RW models are used, and Regulatory Domain is set to HU.

Current channel settings:

2,4GHz: 20Mhz allowed only

5GHz: 20MHz and 40MHz allowed only

Current firmwares:

MM: 8.3.0.1

MDs: 8.3.0.1

I would like to disable UNII-III and ISM channels: 149-165

[SkiP]

Correct myself:

The config failure occurs when channel 165 is part of the deploy. If I skip it (remains enabled) and I disable 149-161 under regulatory domain settings, deployment runs properly, and everything is OK.

So it's seem to be the problem is only with the channel 165, if it is the part of the disabled channels.

If 149-161 was disabled earlier, and I disable 165 after that (in a separate deploy), it runs correctly.

Is this possible a bug in AOS?

[jhoward]

Sounds like an order of operations bug in AOS 8.3. You can open a TAC case to file it. For what it's worth, in 8.4.0.1 I don't see it (I can disabled 149-165 in one modification)