04-21-2014 04:38 AM
Solved! Go to Solution.
04-21-2014 05:01 AM
04-21-2014 12:59 PM
As I remember controller clasiffies endpoints with DHCP fingerprint. You can enable debug log and follow the raw fingerprint from the client.
Something cool, helpful or interesting in my post - click the Kudos Star.
Helped to solve your problem - Click Accept as Solution
04-21-2014 01:36 PM - edited 04-21-2014 01:37 PM
In the user-table on the controller it uses the "Browser Agent" to show the operating system, NOT the DHCP fingerprint. To see what browser agent the incorrectly classified user is showing, Giovanni can type "show aaa device-id-cache | include <mac address>":
(192.168.1.3) #show aaa device-id-cache | include 00:24:2c:3a:08:37 00:24:2c:3a:08:37 Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 Wed Aug 3 19:55:32 2011
That will determine what application is causing the device to be misclassified.
Sometimes something as little as a weather APP causes the device to be misclassified.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base