Hello,
I couldn't find a proper way to report possible bugs into AirWave and Aruba products, so I'm opening it here for Aruba tries to reproduce this issue or help anyone that may find the same problem as me and I didn't want to open an Aruba TAC case because it would take so long and there's workaround solutions available for this issue.
Today I was setting up a IAP cluster managed by AMP (Management mode). When creating a new User Role and associating it to a SSID, the clients wasn't receiving this User Role and consequently the Captive Portal (ClearPass) wasn't splashing for them. Instead, they were receiving the "External CP" User Role.
When I turn off AMP so I could manage the IAP WebUI, I figure out the User Role haven't been created neither assigned. When I tried to create it manually, it reports for me that I couldn't created any more User Roles because I had exceeded the User Role number limit (it's 32 User Roles into AOS 8.7.0.0 and below and 64 User Roles for Aruba InstantOS 8.8.0.0+).
The workaround solution for me was removing an unused User Role locally at the IAP WebUI so the User Role was created as expected.
What I would like the Aruba TAC and engineer team figure out is why the AirWave didn't reported any error when applying the config (not even reported as "mismatched", it seems none config wasn't even applied at all) when the User Role limit was exceed. It would be great if AirWave checks the actual number of User Roles to check if it exceeded accordingly to Aruba InstantOS version instead of assuming it isn't exceeded.
Edit: I found the config sync log and figure out that in fact it shows that the config wasn't applied because the Max roles numbers was exceeded, but could be an error reported at the AirWave UI to state it more clearly instead of letting us trying to figure out what's going on.