Network Management

Hi All,

Could anyone help point me in the right direction in regards to monitoring some legacy Cisco WLCs (4400's in this case) on Airwave please.

To give some context we have a number of sites running Cisco WLC 4400's with a mix of APs (predominantly 1420's), all of the sites are set up with 3 controllers for redundancy.

I've been able to add the WLCs to Airwave via SNMP and can see some information coming across (controller name, LAN MAC, IP etc) but I never see the actual APs appear, or appear in the New Devices tab as with Aruba WLCs.

We do have one site setup and working however this pre-dates my time of working with Airwave, as far as I can see the config on the WLC side is the same for both of these sites so hoping I've missed something obvious.

Thanks,

Matt.

Airwave have support for 4400 Series Wireless Controllers 7.0.235.0 (Bootloader: 7.0.235.0)

Have you added device as using Device type option cisco wlc?

Default when we add controller to Airwave automatically it will discover all APs associated to that controller in new device list. Can you cross check if Thin AP discover polling interval is enabled in Groups>Basic page and also make sure snmp porotocl which you are using is properly set in basic page.

Check any discovery is enabed in Devicsetup>Discovery section and also default folder set in AMPSetup>General>Authorization section.

If everything fine then check for ap_watcher log in system>status page for any errors and also time is in sync Airwave and controller.

Hi Pavan,

So I may have a couple of problems then - firstly I'm running 

Firmware: 7.0.235.3 (Bootloader: 6.0.199.4), althought this is also the case with the one that is working so is the bootloader version a hard limit or recommended?

I've checked all of the Thin AP stuff and that looks fine, my ap_watcher service doesn't look healthy though.

Device Monitor Down /var/log/ap_watcher

Log is filled with....

Thu May 30 18:21:04 2019: Started (PID: 41162)
Thu May 30 18:21:04 2019: Postgres PID: 41171
Thu May 30 18:21:19 2019: Started (PID: 41882)
Thu May 30 18:21:19 2019: Postgres PID: 41887
Thu May 30 18:21:34 2019: Started (PID: 42655)
Thu May 30 18:21:34 2019: Postgres PID: 42663
Thu May 30 18:21:49 2019: Started (PID: 43724)
Thu May 30 18:21:49 2019: Postgres PID: 43725
Thu May 30 18:22:04 2019: Started (PID: 44612)
Thu May 30 18:22:04 2019: Postgres PID: 44631
Thu May 30 18:22:19 2019: Started (PID: 45535)
Thu May 30 18:22:19 2019: Postgres PID: 45539
Thu May 30 18:22:34 2019: Started (PID: 46541)
Thu May 30 18:22:34 2019: Postgres PID: 46549
Thu May 30 18:22:49 2019: Started (PID: 47587)
Thu May 30 18:22:49 2019: Postgres PID: 47589
Thu May 30 18:23:04 2019: Started (PID: 48447)
Thu May 30 18:23:04 2019: Postgres PID: 48460
Thu May 30 18:23:19 2019: Started (PID: 562)
Thu May 30 18:23:19 2019: Postgres PID: 564

since ap_watcher service is down , APs are not discovering, are  you seeing anyother service down in system>status page other than ap_watcher?

Generally we see if server have performance issue, are you seeing any high RAM memory & swap usage and also CPU usage under system>performance page if YES then need to increase resources if they are not as per recommandation.

Try restart services once from system>status page and check if service is coming up.

Hi Pavan,

Restarted AMP services as directed and that's done the trick, after a little bit of time GUI came back up and APs appeared under New Devices!

Thanks for all your help, very much appreciated.

I can now monitor these terrible old Cisco WLCs, hopefully one day we'll be able to replace them ;)

Thanks,

Matt.