Wrong Client OS

  • 2
  • Question
  • Updated 3 years ago
I'm seeing certain types of operating systems show up as unknown or the wrong type all together under the client OS column.  I have a windows 10 laptop that still shows up as Windows 8 and an iPhone 6 showing unknown.  The devices obtain the right ip addresses and are working correctly.  HM is currently 6.6r1 and the APs are currently running on 6.6r1b.2338.  Has anyone seen this problem?  Any reason why this is happening?

Photo of Josh Grzelakowski

Josh Grzelakowski

  • 11 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 2
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
See https://community.aerohive.com/aerohive/topics/ios-9-breaks-client-classification.

Those are most likely iOS devices that have been upgraded to iOS 9.
Photo of Josh Grzelakowski

Josh Grzelakowski

  • 11 Posts
  • 0 Reply Likes
I'm not doing client classification in my deployment.  Once I add the OS object, will it then show an apple device running iOS9 in the client OS column or does something else need to be done?  I just added the object and tried connecting my iPhone and it still shows up as unknown.

Can anything be done for Windows 10?
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
If you have a Management Option set (Network Policy -> Additional Settings -> Service Settings), you are most likely doing some DHCP snooping of clients.  This is (my understanding) how HiveManager detects the OS of the device.  To my knowledge, this uses the OS Objects (under Additional Configuration -> Common Objects -> OS Objects) to determine OS type.

I am not sure why you did not see the device type change from Unknown though.  With time, I'll try to reproduce this and see what is missing.
Photo of Josh Grzelakowski

Josh Grzelakowski

  • 11 Posts
  • 0 Reply Likes
After some trial and error, it seems that you can create an os object for iOS9 but HM won't tell the APs that the change needs to be applied.  Only way to add it to the APs is to add a client classification policy to the NP.  Also, if you remove it from the NP, when you go to update the AP, the command to remove the os object isn't in the list of commands to be ran.  I think it is a HM/HiveOS bug.
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
I see what you're saying.  But you can get around this with the Supplemental CLI.  Just add:

os-version iOS9 option55 1,121,3,6,15,119,252

as the command to run.  Put that on the gear and it should work.  I also assume this to be temporary until Aerohive builds detection into the gear natively via an upcoming HiveOS release...
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
I have engineers looking into this now. I am cautiously optimistic that we will fix this in time to include in our next upcoming HiveOS releases, around the end of this month...
Photo of Nick Brooker

Nick Brooker

  • 8 Posts
  • 2 Reply Likes
another one to add if you're wanting to get rid of all the unknowns..

os-version "Mac OS X El Capitan" option55 1,121,3,6,15,119,252,95,44,46

os-object MacOS os-version "Mac OS X El Capitan"