Controllerless Networks

Dear Community,

 

I recently installed an AP-505 and got it up and running using firmware version 8.6.0.2_73853. As part of the set up process, I have used " # show airgroup blocked-service-id" on the CLI to identify blocked services and manually add them to AirGroup as allowed services.

 

While doing so, I noticed that services I had manually allowed kept being blocked. After some experimentation I noticed the following system behaviors:

 

• I can add a maximum of only five groups (that quantity seems very low to me)
• Only the first two custom groups retain their service IDs despite saving.
• However, there appears to be a cutoff in those first two groups regarding the numbers of service IDs retained - once the list grows beyond that, the servide IDs are truncated.
• The other three groups appear to retain the service IDs but at some point the service IDs simply disappear and are not exported when exporting the configuration to a file either.

Am I doing something wrong or is this a bug in the current firmware?

 

Thanks for your help,

JP

is this still happening?

 

Thank you for getting back to me. As the error is reproducible, I have opened a support ticket (5344774479).

Would be nice, if you please would post in here again if your problem has been resolved

and what the solution was.

 

Aruba is still investigating the issue. They are having trouble replicating this issue in their lab. Are you experiencing the same problem?

I just disablet Airgroup, so that way the problem is fixed..

--
Venlig hilsen / Best regards

Anders Bramsen
Driftkonsulent
[image: mobile-icon] + 48 28 12 34 58
[image: email-icon] abramsen@gmail.com
[image: facebook icon] [image:
youtube icon][image: linkedin icon][image: twitter icon][image: instagram icon]

Aruba Support came back to me with the following answer:

 

"Engineering confirmed that’s it’s a limitation issue and the current limits for the maximum number of custom services supported is 5 and the maximum number of custom service ids is 32."

 

Hopefully, this limitation will be addressed/fixed in future firmware versions.