Disabling Console and Monitor Logging and Enabling Logging Buffered (Hybrid-Catalyst OS)

Disabling Console and Monitor Logging and Enabling Logging Buffered (Hybrid-Catalyst OS)

SW3> (enable) set logging console disable

System logging messages will not be sent to the console.

SW3> (enable) set logging buffer 500

System logging buffer size set to <500>

SW3> (enable)

The logging buffers in Examples 7-14 and 7-15 are specified in bytes and are circular, meaning the oldest log messages will be overwritten by the newest messages after the buffer is full. The maximum logging buffer size in Catalyst OS is 500 bytes. To view the contents of the logging buffer, use the show log command. One problem with relying only on the logging buffer is that it is wiped clean during a reload. A more effective solution for logging system messages is the addition of a syslog server. A syslog server is simply a machine running a syslog daemon conforming to the Berkley Standard Distribution (BSD) standard. A syslog server stores the messages in the order received for later viewing. Many network management tools such as CiscoWorks and HP Openview can operate as a syslog server. In larger environments, it is generally recommended to set up a dedicated syslog server because of the number of messages that can be generated each day by dozens or hundreds of Cisco devices. Example 7-16 shows the configuration of logging to a syslog server using native software.