Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Wireless heat map does not show list of clients in Network Atlas

Wireless heat map does not show list of clients in Network Atlas

Table of contents

Updated January 30, 2017

Overview

This article provides information on the main requirement for deploying wireless heat maps. 

Environment

All NPM versions

Detail

Customer must have 3 APs on the map. Signal coverage from these APs must be good enough to be able to calculate the client position. The client has to be seen from at least 3 APs to be able to calculate its position.

 

When you check WLHM.BusinessLayer.log,you will see Warnings similar to the following:

WARN SolarWinds.Wireless.Heatmaps.BusinessLayer.ClientLocation.ClientLocationCalculator - Unable to calculate position for client '60672042D41E'. Exception: System.ArgumentOutOfRangeException: Not enough points at input, needs 3, has 2 Parameter name: 
 

 

 

 

Last modified

Tags

Classifications

Public