Wireless Access

last person joined: 19 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Some devices aren't displaying the device type within the monitoring page

This thread has been viewed 4 times

  • 1.  Some devices aren't displaying the device type within the monitoring page

    Posted Feb 14, 2013 09:37 AM

    Some of the devices that are wirelessly connected to my 650 controller don't show the device type when I'm looking at the clients in the monitoring page.  Is there any reason why they wouldn't be displayed?

     

    I am running version 6.1

     

    Rory



  • 2.  RE: Some devices aren't displaying the device type within the monitoring page
    Best Answer

    Posted Feb 14, 2013 09:50 AM

    EDIT:   For a more accurate description/solution, please see cjoseph's post.

     

    Original Response:

    The device type listed in the client table can be determined by one of two things.   The first is the DHCP fingerprint.  The controller does not have to be the DHCP server, but needs to see the request.    If the client is running an odd OS type that is not in the database or has a static IP address or the AP is in bridgd mode this component would not reveal the device type.   The second is through HTTP header analysis.  Once the client attempts an HTTP request, additional information can be obtained about the device type (Windows XP vs Windows for example).

     

     

     

     



  • 3.  RE: Some devices aren't displaying the device type within the monitoring page

    Posted Feb 15, 2013 05:30 AM

    Thanks for the speedy reply!

     

    Thats just what im looking for :)

     

    Rory



  • 4.  RE: Some devices aren't displaying the device type within the monitoring page

    EMPLOYEE
    Posted Feb 22, 2013 10:37 AM
    @clembo wrote:

    The device type listed in the client table can be determined by one of two things.   The first is the DHCP fingerprint.  The controller does not have to be the DHCP server, but needs to see the request.    If the client is running an odd OS type that is not in the database or has a static IP address or the AP is in bridgd mode this component would not reveal the device type.   The second is through HTTP header analysis.  Once the client attempts an HTTP request, additional information can be obtained about the device type (Windows XP vs Windows for example).

     

     

    I hate to nitpick, but the OS Type displayed in the controller's user table is ONLY discovered through http requests and NOT dhcp fingerprints.  That is why devices like VOIP phones and others that do not open browsers will NOT have the OS displayed in the controller's user table.  

     

    The "show aaa device-id cache" command will show what devices have sent http and were identified in the user table.  You can still use the DHCP fingerprint to create a user derivation role for devices that do not use http change their role.  Their operating system will not be displayed in the user table of the controller if they do not use http, however:

     

     

    (host) #show aaa device-id-cache

Device ID Cache
---------------
MAC                Device ID                                                                                                                        Last Update
---                ---------                                                                                                                        -----------
c0:cb:38:39:63:5f  Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20100101 Firefox/6.0                                                                  Thu Mar 12 06:36:18 1970
c4:17:fe:00:57:21  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.1; .NET CLR 1.1.4322; .N  Mon Aug  8 13:28:37 2011
c4:46:19:6f:6b:05  Windows-RSS-Platform/2.0 (MSIE 8.0; Windows NT 5.1)                                                                              Sat Oct 15 14:59:43 2011
c0:f8:da:63:77:48  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB7.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .  Sun Nov 13 11:02:40 2011
78:e4:00:38:96:f2  Windows-RSS-Platform/2.0 (MSIE 9.0; Windows NT 6.1)                                                                              Sun Jul 10 20:17:30 2011
c4:46:19:30:7e:7c  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.0  Wed Sep 21 11:02:39 2011
c0:cb:38:80:8f:75  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Iron/10.0.650.0 Chrome/10.0.650.0 Safari  Thu Oct 27 22:10:09 2011
44:2a:60:f3:62:24  Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.24 Safari/535.1             Wed Jun 22 20:08:17 2011
c0:cb:38:80:9a:ee  Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.218 Safari/535.1                              Wed Aug 31 19:06:48 2011
f8:1e:df:0a:a2:e8  iTunes-iPhone/4.3.3 (3; 16GB)                                                                                                    Thu Jul 28 09:22:13 2011
38:59:f9:03:b4:8b  Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.307  Fri Oct 28 13:47:18 2011
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
c4:46:19:30:7f:59  Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20100101 Firefox/5.0                                                                  Mon Aug  8 13:28:58 2011
00:24:2c:3a:08:22  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.2; .NET4.0C; .NET4.0E; M  Sun Oct 30 18:03:10 2011
00:24:2c:1b:78:48  Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.109 Safari/535.1                              Mon Aug 29 06:18:32 2011
00:24:2b:39:67:e4  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET4.0C; .NET4.0E; InfoPath.2)    Thu Sep  8 17:40:33 2011
0c:ee:e6:9e:4b:46  Windows-RSS-Platform/1.0 (MSIE 7.0; Windows NT 5.1)                                                                              Mon Sep 12 08:53:08 2011
0c:60:76:78:9e:4c  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.307  Tue Oct 18 10:48:18 2011
c4:46:19:6f:a3:2c  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.0  Mon Sep 19 16:17:18 2011
c0:cb:38:80:8f:8d  Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101 Firefox/6.0                                                                 Wed Sep 21 15:01:59 2011
c4:17:fe:d4:a3:6c  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR   Wed Nov 16 10:00:43 2011
c4:17:fe:b7:60:cf  Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1                                                       Fri Oct 28 13:40:01 2011
c0:f8:da:63:68:bb  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.307  Fri Oct 28 13:51:39 2011
c0:cb:38:93:23:7c  Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.102 Safari/535.2                              Fri Oct 28 16:42:28 2011
c0:cb:38:22:b1:bf  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.307  Thu Nov  3 17:33:51 2011
08:11:96:1b:1b:e0  Windows-RSS-Platform/2.0 (MSIE 8.0; Windows NT 6.1)                                                                              Wed Nov  9 14:05:02 2011

     



  • 5.  RE: Some devices aren't displaying the device type within the monitoring page

    Posted Feb 22, 2013 10:49 AM
    @cjoseph wrote:
    I hate to nitpick......   

    Please do nitpick!  It helps us all in the long  run. 
    Thanks


  • 6.  RE: Some devices aren't displaying the device type within the monitoring page

    Posted Mar 31, 2016 01:36 PM

    Bringing up this one. We have wireless scanners connecting, not sending HTTP headers. Is it possible to add a custom device type based on the scanners MAC OUI? If not, can you create a rule which will set the Device Type to "SCANNER" when the MAC address starts-with xx:xx:xx....



  • 7.  RE: Some devices aren't displaying the device type within the monitoring page

    EMPLOYEE
    Posted Mar 31, 2016 01:43 PM

    That is not possible, no.