Syslog and your wireless infrastructure

I found an *ancient* Cisco PDF that covers syslog in as much detail as I could ever require..

Cisco ISP Essentials from 06/06/2001! - the section covering detailed syslogging is on page 22.


Detailed Logging

Keeping logs is a common and accepted operation practice. Interface status, security alerts, environmental conditions, CPU process hog and many other events on the router can be captured and analysed via UNIX syslog. Cisco System's IOS has the capability to do UNIX logging to a UNIX syslog server. The router syslog format is compatible with BSD UNIX syslog (now found as part of most Unix and Linux systems deployed today). The follow is a typical logging configuration for ISPs:

no logging console <-- Don’t send logs to the router console
logging buffered 16384 <-- 16Kbyte history buffer on router
logging trap debugging <-- Catch debugging level traps (i.e. everything)
logging facility local7 <-- Syslog facility on syslog server
logging 169.223.32.1 <-- IP address of your first syslog server
logging 169.223.45.8 <-- IP address of your second syslog server

!---- logging [server ip address]
!---- logging trap [warning]

Setting the logging parameters on a 4402 WLC:

From ccie(w)