In our environment we have Juniper and Aruba WLCs that have been deployed and configured both types with their respective Device Profile Types. All the Junipers are placed in 1 Network Group Location where the policy set is configured to allow access to the Juniper Authorization Result and the Arubas with similar configuration to allow access with a different policy to the Aruba Authorization Result.
We have some Arubas that only work with the Juniper device profile and Juniper Authorization result, while the rest of them (roughly 50%) work using the Aruba device profile and Aruba Authorization result. In the detailed authentication report we see that for the Arubas that are not working properly the Authentication Method and Service Type are the same as for the Junipers but different from the Arubas that are working properly.
All the Junipers work as expected.
So the questions that I have are the following
1. Why are some the Arubas only working when we configure them as Junipers in ISE; is it because the Authentication Method and Service Type settings can only be properly handled with the Juniper Device Profile in combination with a Juniper Authorization Result (currently observed behavior) ?
2. If the above is the reason, where can those settings be modified/changed; is it the endpoints/devices (laptops, desktops etc) that determines them or the WLCs?
