Wireless Access

We've seen drops in APs & users for the pass three weeks in our MRTG graphs (that we collect) and on Airwave between 3-6 am.

Looking at the logs for the primary controller on Airwave I found the following log message:Configuration verification: configuration on device does not match desired configuration. Coule this be the reason for the drop in APs and users during that time? Has anyone every ran across this problem?

Thanks. 

That only matters if you are Managing the Config on your controller with Airwave (your controllers are in managed mode).  If not, it is not directly related.  Even if your controllers are in manage mode, something else besides Airwave is causing your issue.

We have two 6000M3 controllers running 3.4.5.1 operating as Master/Local setup. We recently created a new ap-group and ap system-profile (& lms-ip), could there be a misconfiguration causing this problem?

Is this a false positive on the graphs showing drops in APs and users, even though we did not receive any alerts saying APs were down ?

Could this be a SNMP issue (i.e. wrong Community String)

Have you heard of this problem before?

Thanks.

It is quite possible that the controller did not return any SNMP tables during that last poll, so Airwave and anything else did not show all of the APs and users in the table.  3.4.5.1 is very old, so there is no telling what is going on, but that behavior has happened in the past.

You said that  behavior has happened in the past, do you know the root causes?

In our cause it happens every Wednesday between 3am-6am.

What happens in your network between 3 and 6 am?  What time does Airwave do its nightly backup?

From the controller perspective, there should not be anything that would happen between 3 and 6 am on Wednesdays.  If it only happens at that time, I would look at (1) your network or (2) airwave.

The SNMP polling issue is something that would only occur under load, presumably, so I would rule that out between 3 and 6 am.

Thanks, for the info, Airwave's nightly maintenance is 04:15, the issue may be on our network since this only occurs on Wednesdays.