Wireless Access

I have a mobility controller 3200.

I have four ap 125s. This installation is in my home (home office) and I totally do not need four aps. I'd like to setup two of them to be air monitors.

I've created a new AP group called 'spect', and configured it so that all radios go into AM mode.

However, whenever I try to select two of the APs and put them in the 'spect' ap group, nothing changes. They all stay in the 'default' group. I've tried by hand and using the wizards - same result. I even bought rfprotect licenses hoping that would do the trick. Still no love. 

Am I doing something wrong, or this a bug? or does this controller not support using multiple AP groups?

What version of ArubaOS is this?

Type "show log system 50" and see if you are getting an error while provisioning those access points.

ArubaOS (MODEL: Aruba3200-US), Version 6.4.4.9

And the resulting system log is a bit troubling.

the AP I'm trying to put into the other AP group is the "office" AP.  All APs in the system are exhibiting this error though.

Jul 27 07:18:03 :311002:  <WARN> |AP office@10.0.0.57 sapd|  Rebooting: Rebooting after provisioning
Jul 27 07:18:03 :311002:  <WARN> |AP office@10.0.0.57 sapd|  Rebooting: SAPD: Rebooting after provisioning
Jul 27 07:18:04 :303086:  <ERRS> |AP office@10.0.0.57 nanny| Process Manager (nanny) shutting down - AP will reboot!
Jul 27 07:18:25 :311020:  <ERRS> |AP livingroom@10.0.0.25 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1005 arg 0x64933c.
Jul 27 07:18:29 :311020:  <ERRS> |AP livingroom@10.0.0.25 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1003 arg 0x649324.
Jul 27 07:18:42 :311020:  <ERRS> |AP garage@10.0.0.33 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1003 arg 0x649324.
Jul 27 07:18:42 :311020:  <ERRS> |AP garage@10.0.0.33 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1005 arg 0x64933c.
Jul 27 07:18:50 :303022:  <WARN> |AP office@10.0.0.57 nanny|  Reboot Reason: AP rebooted Thu Jul 27 07:18:10 PST 2017; SAPD: Rebooting after provisioning 
Jul 27 07:19:19 :311020:  <ERRS> |AP livingroom@10.0.0.25 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1005 arg 0x64933c.
Jul 27 07:19:24 :311020:  <ERRS> |AP livingroom@10.0.0.25 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1003 arg 0x649324.
Jul 27 07:19:36 :311020:  <ERRS> |AP garage@10.0.0.33 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1003 arg 0x649324.
Jul 27 07:19:36 :311020:  <ERRS> |AP garage@10.0.0.33 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1005 arg 0x64933c.

It looks like a bug.  Try to change ap-groups of those APs using the ap-regroup commandline in the interim:  http://www.arubanetworks.com/techdocs/ArubaOS_65x_WebHelp/Web_Help_Index.htm#ArubaFrameStyles/1CommandList/ap-regroup.htm?Highlight=ap-regroup

The message you are seeing seems to be fixed by 6.4.4.11:

Attachment(s)

ArubaOS 6.4.4.11 Release Notes (3).pdf   394 KB 1 version

Still no luck.

Even after issuing the command in the cli to reclassify the AP it refuses to leave the "Default" group.