Monitoring, Management & Location Tracking

Define Unknown Device Types on Airwave Reports

Aruba Employee

Environment : Unknown device types on Airwave reports

 

AirWave reports both the "AOS Device Type" and the "Device Type"
 
AOS Device Type
This is the device type as reported to AirWave by the controller or virtual controller.  The controllers get the device type by reading the User-Agent string in http requests. Those strings look like this:
 

 Mozilla/5.0 (iPad; U; CPU OS 3_2_1 like Mac OS X; en-us) AppleWebKit/531.21.10 (KHTML, like Gecko) Mobile/7B405


Tip: When AirWave reports the "AOS Device Type" as unknown, it means controller is not able to classify the device type and send to Airwave with the information.

 
Device Type: 

This is the device type calculated by AirWave.  It is determined based on different pieces of data from our controllers (including User-Agent string and OUI), as well as data from external MDM servers. AirWave gives the user some control over how this calculation is made.  We have a default set of rules that are almost always adequate, but in case somebody wanted to tinker with them, they could do it on the AMP Setup -> Device Type Setup page: 

 

rtaImage.jpg

 

For reporting purposes within AirWave, it's a recommended practice to use "Device Type" rather than "AOS Device Type" since it is based on more data points. 
 
What are the common reasons why AMP reports device type as "Unknown"? 
 
1. The controller doesn't know the type, probably because it hasn't seen the client do http. 
2. Monitoring of 3rd party wireless devices and the clients connected to them.

Version history
Revision #:
1 of 1
Last update:
‎04-08-2015 04:51 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.