Dear Community.
I have the following case with the central Aruba cloudauth integrated with the Active Directory in Azure.
In the authentication and access process, the rad-recj, eap-failure, and server failure messages are observed.
Auth Trace Buffer
-----------------
May 5 10:55:34 eap-failure <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 8 4 server rejected
May 5 10:55:35 station-up * e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 - - wpa2 aes
May 5 10:55:35 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 10 5
May 5 10:55:35 eap-start -> e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 - -
May 5 10:55:35 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 10 5
May 5 10:55:40 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 10 5
May 5 10:55:41 eap-id-resp -> e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 10 21 jampier.valdivia
May 5 10:55:41 rad-req -> e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 1 345 a9e560f3-537e-4206-8bda-0baa7ba5
May 5 10:55:41 rad-resp <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71/AS1_#guest#_ 1 -
May 5 10:55:41 eap-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 11 6
May 5 10:55:41 eap-nak -> e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 11 7
May 5 10:55:41 rad-req -> e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71/AS1_#guest#_ 1 349 a9e560f3-537e-4206-8bda-0baa7ba5
May 5 10:55:41 rad-reject <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71/AS1_#guest#_ 1 -
May 5 10:55:41 eap-failure <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 11 4 server rejected
May 5 10:56:12 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 12 5
May 5 10:56:17 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 13 5
May 5 10:56:22 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 13 5
May 5 10:56:27 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 13 5
May 5 10:56:32 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 14 5
May 5 10:56:37 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 14 5
May 5 10:56:42 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 14 5
May 5 10:56:47 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 15 5
May 5 10:56:52 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 15 5
May 5 10:56:57 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 15 5
May 5 10:57:03 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 16 5
May 5 10:57:08 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 16 5
May 5 10:57:13 eap-id-req <- e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 16 5
May 5 10:57:18 dot1x-timeout * e4:a4:71:e4:1b:a0 6c:c4:9f:25:6d:71 17 512 station timeout
6c:c4:9f:ca:56:d6#
In the configuration process, the guides and recommendations were followed step by step, not encountering problems, and observing the correct one.
operation in central Aruba with AD connection.
The problem occurs with users who try to access the wireless network, through the cloudauth method.
Please help me this case.
Thanks
Felipe H.V
------------------------------
Felipe Herrera
------------------------------