Is there a way to view a clients location on the maps section of HiveManager?

  • 2
  • Question
  • Updated 5 years ago
  • Answered
I have tried adding a client's MAC address to the client watch list and then I have selected the "Clients" check box once I'm on a map under the Maps tab, and that doesn't seem to do anything.
Photo of Luke Nikunen

Luke Nikunen

  • 15 Posts
  • 1 Reply Like

Posted 5 years ago

  • 2
Photo of Roberto Casula

Roberto Casula, Champ

  • 231 Posts
  • 111 Reply Likes
Hi,

In order to view clients' locations, HiveManager needs to receive and co-ordinate client RSSI measurements from multiple locations. It can do this using a separate location tracking solution (Aeroscout or Ekahau for example) or by using the Aerohive APs themselves to return the necessary data.

Note that in a large and busy network, there is some overhead for the APs in collecting this information and sending it to HiveManager - you can minimise this if you limit the collection of RSSI information to a subset of devices.

To use the Aerohive APs as location servers, go into the Network Policy -> Additional Settings and add a new Location Server object under Management Server Settings of type "Aerohive Location Server". You then need to specify which clients you want to monitor - there is a default "All Clients" object, but you could create your own filter based on MAC addresses if you only want to monitor a small number of devices.

When you push the policy to your APs, they will start gathering RSSI information and client locations will be displayed on the map when requested. Note that a minimum of three APs (by default) need to provide RSSI measurements before a client's location can be determined. The more APs provide the RSSI measurements, the more accurate the location will be - it is very important that your APs are accurately located on your maps and the location tracking will be significantly improved if you add walls to your maps so that the algorithm can take into account the expected attenuation by obstacles between the measuring AP and the client.

Regards,
Roberto
Photo of Luke Nikunen

Luke Nikunen

  • 15 Posts
  • 1 Reply Like
I believe I have followed your instructions correctly, but I'm still not seeing anything on the map when I click on the clients check box.

I will attach a couple screen shots.







Photo of Andrew MacTaggart

Andrew MacTaggart, Champ

  • 483 Posts
  • 86 Reply Likes
http://www.aerohive.com/330000/docs/h...

I assume you pushed config to APs

but maybe the help file will help

When devices are configured to track client locations, it is possible to see the estimated locations of active clients on a map. Certain conditions are required for HiveManager to be able to estimate client locations and show icons representing those estimations on a map:

Devices must be configured to perform client tracking (see "Location Server Assignments").
HiveManager must have the minimum number of RSSI measurements (the default is three) and the measurements must be higher than the location threshold (-75 dBm by default).
The estimated position of the client must not be outside the borders of a map.

To see the estimated location of a client, select its check box, and then click Operation > Show Client Location. If all the above conditions are met, HiveManager shows an icon for the selected client on a map.
Photo of Andrew MacTaggart

Andrew MacTaggart, Champ

  • 483 Posts
  • 86 Reply Likes
with HM on Prem version 6.1.r2

I just enabled this

and seems to work for me

maybe remove your tags and see if you can get it working with just Mac Address first.

3 APs will need to hear the client though.

design for location services must be in place - meaning your AP deployment was designed for location services.

Photo of Andrew MacTaggart

Andrew MacTaggart, Champ

  • 483 Posts
  • 86 Reply Likes
I am in a multistory building, so location service may not work in certain environments.

from active clients click the operation and click show client location

The result is ambiguous. Client is reported by 4 devices (AP1, AP2, AP3, AP4) at -75 dBm or stronger, but they are on different topology maps (4Floor, 5Floor, 6Floor).
Photo of Roberto Casula

Roberto Casula, Champ

  • 231 Posts
  • 111 Reply Likes
The most likely reason is, as Andrew says, that the deployment has not been designed with location tracking in mind. As with all AP-based location systems, accuracy relies on multiple access points (by default a minimum of three, but the more the better) located on the same floor being able to gather sufficiently reliable RSSI information from clients. If there is insufficient data, location will not be available. While it is possible to lower the thresholds (e.g. number of reporting APs, how recent the RSSI data needs to be and what the RSSI threshold is), this will very quickly result in wildly inaccurate location as the "fingerprint" becomes ambiguous (there are multiple possible locations which would produce the same fingerprint) and the "error bars" in the location become bigger and bigger due to the logarithmic nature of the RSSI data.