You can enable AP syslog via WLC CLI only. AP needs to be register for a WLC prior to apply this commands. If you connect new APs, they will send syslog for the configured host, but level & facility will be default(not what you configured). So to make sure it is correct you have to configuer these when all APs register (or every time you add new APs)
You can use for "all" keyword if you want to apply settings to all APs, or else specific AP name if you want to configure this for a given AP
config ap logging syslog facilityall>
config ap logging syslog levelall>
config ap syslog host global x.x.x.x
If you want to configuere syslog host for specific AP
config ap syslog host specific x.x.x.x
Following commands can be used to verify.
show ap config global
show ap config general
In case if you want to configure similar thing for WLC you can use the followings
Message logging is enabled by default. It must be enabled to send messages to any destination other than the console. When enabled, log messages are sent to a logging process, which logs messages to designated locations asynchronously to the processes that generated the messages.
Beginning in privileged EXEC mode, follow these steps to disable message logging:
Step 1 -configure terminal Enter global configuration mode.
Step 2 -no logging on Disable message logging.
Step 3 -end Return to privileged EXEC mode.
Step 4 -show running-config
show logging Verify your entries.
Step 5 -copy running-config startup-config (Optional) Save your entries in the configuration file.
In unified wireless (ie CAPWAP) you cannot save any configuration like you said & ovewritten by WLC. Therefore you have to configure them through WLC if you want to persist the config even during a AP reboot.
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...