12-12-2013 11:27 AM - edited 12-12-2013 01:32 PM
This morning I upgraded from Aruba OS 18.104.22.168 to 22.214.171.124 on a 3200XM controller. I had 29 ap's before the reboot and 27 after. 2 of them mysteriously changed to Air monitors.
I made sure "Mode aware ARM" was unchecked and made sure the group they are provisioned to is set to ap-mode.
Does anyone have a clue what the issue could be?
12-12-2013 12:16 PM
From the output to "show ap debug received-config ap-name [AP Name]" do you see mode = ap-mode? If the mode = am-mode, I would check, if the RF Plan has the AP defined as an AM.
12-12-2013 12:37 PM
Hi Kevin, it shows up as a monitor. These two AP's are part of a group that use the same profile as 8 other AP's and the other AP's are fine and have not went into AM mode. RF is defined as ap-mode.
12-12-2013 12:44 PM - edited 12-12-2013 01:12 PM
Just noticed something else, when I go to my AP list both the AP's are flagged as E which means " E = Regulatory Domain Mismatch"
All Regulatory domains state "US" on the controller and on the profile.
Also, I switched back to my old boot partition, and everything came up just fine.
12-12-2013 01:52 PM
I have not seen an issue in this area.
Please open a case with TAC with the serial number of the AP and the "Regulatory Domain Mismatch" message. They should be able to verify, if there was a failed compliance check.
12-19-2013 08:19 AM
All of our AP's are 105's or 125's and all were purchased from the same vendor. Also when I run a debug on them they spit out US domain. The controller runs fine on the default software (ArubaOS 126.96.36.199) and throws up no flags, its only when we try and update the software(ArubaOS 188.8.131.52) that we have issues. This is using the same configuration.
06-18-2014 10:42 AM
Im thinking the newest OS isnt compatible with our 3200xm controller. I switched to the newest version of 6.1 which is 184.108.40.206 and everything was back to normal. I dont have a definite anwser on this being the case but it would seem so. I tried multiple different settings trying to make the new OS work but nothing seemed to take.
06-18-2014 06:56 PM
If you have an ap-specific profile for that AP, remove it.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base