Network Management

Hi

 

When I look at the usage in the controller gui dashboard, it reads 500M, but in airwave for the same controller it reads 202Mbps.

Why is there a difference between theese 2 readings ?

 

Screenshots please

Heres some screenshots.

The difference is not as big at the moment, but still 100M difference.

 

Do you only have the Aruba Controllers and APs attached to Airwave or do you also have other devices ?

I am not sure that I understand your question here.

 

I have 7210 controllers with APs attached, and are using airwave only as a monitoring platform.

In airwave I have the controllers attached, and can therefor monitor both APs and controllers.

 

Does that answer your question correct? :-)

The reason I ask is because you can also monitor wired activity from a switch for example and that would impact your overall usage vs what you see in the controller which is only monitoring wireless data.

The other thing is that the information presented in the controller usage is over the last 15 minutes (default) and in Airwave by default is over the last 2 hours .

You can change the airwave time range for the usage but not in the controller dashboard

Sent from Outlook for iPhone

No, I'm not monitoring any wired data, or anything else but the controllers.

 

And yes, there is a diffrence in the time span, but I find it strange that the traffic in the controller GUI is always higher than what is showing in the Airwave. And sometimes nearly by factor 2.

 

Anyway, thank you for your answer.

 

What version of AirWave and what version of AOS firmware?  Is data polling from AirWave via SNMP or AMON?  If SNMP, then the difference is probably due to latency from time of request/collection to time AirWave processes.  If on AMON, then this would be a defect and should be looked into with a support case.  Would expect the numbers to be very close (not realtime close, but within polling parameters).

I am running airwave 8.0.11 and AOS 6.4.3.5.

Datapolling is preferred to be AMON, but how can I see if that is actually the protocol beeing used?

 

While the AMP may have the setting for AMON, you also need to verify it from the controller end.

From controller CLI:

# show running-config | include mgmt

(looking for a command that looks like:
mgmt-server type amp primary-server 10.10.10.10 profile default-amp

where primary-server = AirWave IP

and profile = whatever you decided to use for the AMON profile - in this case it's default-amp)

# show mgmt-server profile default-amp

Mgmt Config profile "default-amp" (Predefined (changed))
--------------------------------------------------------
Parameter Value
--------- -----
Stats Enabled
Tag Enabled
Sessions Enabled
Monitored Info Enabled
Misc Enabled
Location Enabled
UCC Monitoring Disabled
AirGroup Info Disabled
Inline DHCP stats Enabled
Inline AP stats Enabled
Inline Auth stats Enabled
Inline DNS stats Enabled

 

A simplified breakdown of what these data points are:

1) general data collection = stats, monitored info, misc

2) VisualRF = location, tags (if you use wifi tags, example: ekahau)

3) UCC = UCC monitoring (Lync calls)

4) AppRF = sessions

5) AMP 8.2 upcoming feature: Clarity = the 4 'inline' stats

note that speed/goodput values for rf performance page are also transmitted via AMON