We have all our APs and our WLCs configured to log to our syslog server. We have used the following command on each of our WLCs
config ap syslog host global x.x.x.x
This avoids the issues with the default of logging to the local broadcast address. This works great....too well infact as we are getting tons of logs that we are not really using or don't really want. We would like to stop it globally and to turn is on for specific APs as needed....
Is there a way to disable logging on the APs or send it to NULL? We has considered sending it to the local loopback address, but were concerned that this may affect the CPU on the APs. We had considered sending to to some blackhole network, etc, but would prefer not to have the logs from thousands of AP banging around....it would be cleaner to have them dropped on the AP or disable the logging.
I don't think it's possible to disable ap's from syslogging. This is likely an intended behavior.
As a test, you could set a couple of ap's syslog server to 127.0.0.1, then monitor the cpu. Unless there's some type of dramatic event going on, I wouldn't suspect that it would impact the ap's cpu that much...worth testing though before cutting it loose on all your ap's
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...