Authenticate a supplicant on a Extreme 802.1x port with an ACS SE 4.2
Supplicant = IP Phone
Authenticator : Switch Extreme 450 E
Authentication Server : ACS SE 1113 22.214.171.124.9
1) We have done the tests with a Windows ACS 126.96.36.199 and everything runs correctly, the supplicant authenticates without any problem.
2)We have replicate the windows ACS with the ACS SE. The 802.1x authentication does not work with the ACS SE but works with the Windows ACS.
3) We have upload UDvs and VSA on the ACS SE and it still not work.
These are the .csv file uploaded :
accountactionsVsa.csv (used for the vendor)
accountAttributes.csv (used for the vendor attributes)
accountProfile.csv (used for the Attributes profile)
accountvalues.csv (used for the Attributes values). This one is not on the attachment files :
The message in ACS Failed Attemps logs is : "Bad Request from NAS".
We have verified the authenticator address and the secret key, everything is ok.
With Windows ACS we can see first an "access request" between authenticator and aurthentication server. Next an "access challenge" from authentication server to Authenticator. NExt an "access request" between authenticator and aurthentication server and then an "access Accept" from authentication server to Authenticator.
With ACS SE we can see first an "access request" between authenticator and aurthentication server. Next an "access Reject" from authentication server to Authenticator.
We have tried to understand the differences between the first "access request" in ACS windows architecture and the first "access request" in ACS SE architecture. The only difference is on the Message-authenticator(80).
Have you already had this kind of problem. How can i Solve it?
Thanks for your replies.