05-20-2015 09:29 AM
I am having issues with the Heatmap not displaying. I have to turn it off and on again to fix it. Sometime, the heatmap appears as squared, at other times, it is very blocky and pixelated.
I really don't know how to trouble this issue. I have tried turning the heatmap on and off, and also changing grid size. Is this a bug?
05-21-2015 05:58 AM
If this is within Airwave, please upgrade to 188.8.131.52 and retest
Consulting Systems Engineer - ACCX, ACDX, ACMX
If you found my post helpful, please give kudos
05-21-2015 08:42 AM
Thank you for replying to my question. I am currently running Airwave v.184.108.40.206 Do you think upgrading to .8.1 help? I called support yesterday, and the engineer did something that I was not familiar with, he added boundaries to the site. I read the documentation, and it did not mention the need to add boundaries.
06-30-2015 11:30 PM
we are running 220.127.116.11 and the issue is not solved. There is no heatmap shown after you added a deployed device.
Please let us know when it will be fixed.
Or is it working in a previous version?
07-01-2015 01:08 AM - edited 07-01-2015 01:08 AM
Do you have the heatmap layer turned on, along with the devices you want displayed?
If not, please open a case, because you could have an issue specific to your deployment. It has worked for most people for awhile.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
08-06-2015 05:37 AM
Floors with recently deployed APs were not showing heatmaps for me. Toggling visualrf on/of did not help. Upgrading to 8.0.9 resolved my issue. Can you try this?
If a reply adequately addresses your issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users.
06-16-2016 12:40 PM - edited 06-16-2016 12:43 PM
It seems i am also facing a relatable issue. In my case however, the heatmap is not one would expect for a designed floor plan. Strangely, this occurs only on the Airwaves Visual RF which has had the plan imported but not on a local desktop standalone installation of Visual RF which shows a more tangible result for heatwave.
I have attached part of a floor plan for a building which shows significant difference in heatmap generated by the Airwaves Visual RF vs. Local(Standalone) Visual RF.
Airwave Visual RF:
Local(Standalone) Visual RF:
Can someone explain why this is as it seems rather a grave error and unreliability in Visual RF design software algorithm which is part of the Airwave Management System.
I am using the AirWave Management Platform version 18.104.22.168, which is the latest version to my understanding.
09-01-2016 09:32 AM
Just to lead weight to aramadur's reply we too are seeing the same results as shown in the image "Airwave Visual RF". Are VisualRF is server based and used to monitor remote locations all over the UK. We are using an older version and were planning on upgrading to see if it fixed the issue.
Extremely disappointed to read that version 22.214.171.124 is no better.
09-01-2016 10:13 AM
Thanks for adding the weight. Yes we are still facing this issue since I posted it. It seems to be a memory issue which Aruba Airwaves folks are supposedly acting blind to.
I got Aruba TAC on the line for this and all they did was change the memory and cores allocated to VRF in AMP. This started throwing off other alerts as our AMP is a VM. The TAC doubled the memory allocation to Visual RF in AMP and that seemed to satisfy VRF for a few hours..if not days. At the end, it still complained that it didnt have enough memory and 'Communication timed out' messages.
One quick workaround to try is to restart the Visual RF service on your AMP server. That generally gets the heatmaps right.
Aruba does state somewhere how much memory/cores to allocate based on # of buildings and despite having followed their reccomendation, we are still facing this issue! :(