Understanding System Message Logging - Cisco Catalyst 3560-X Software Configuration Manual

Hide thumbs Also See for Catalyst 3560-X:

Table of Contents

Configuring System Message Logging and Smart

This chapter describes how to configure system message logging on the Catalyst 3750-X or 3560-X

switch. The switch also supports Smart Logging to capture packet flows based on configured triggers.

For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS

Configuration Fundamentals Command Reference, Release 12.4 and the command reference for this

Logging messages to the console at a high rate can cause high CPU utilization and adversely affect how

the switch operates.

Understanding System Message Logging

By default, a switch sends the output from system messages and debug privileged EXEC commands to

a logging process. Stack members can trigger system messages. A stack member that generates a system

message appends its hostname in the form of hostname-n, where n is a switch number from 1 to 9, and

redirects the output to the logging process on the stack master. Though the stack master is a stack

member, it does not append its hostname to system messages. The logging process controls the

distribution of logging messages to various destinations, such as the logging buffer, terminal lines, or a

UNIX syslog server, depending on your configuration. The process also sends messages to the console.

The syslog format is compatible with 4.3 BSD UNIX.

Understanding System Message Logging, page 1-1

Configuring System Message Logging, page 1-2

Configuring Smart Logging, page 1-14

Displaying the Logging Configuration, page 1-17

C H A P T E R

Catalyst 3750-X and 3560-X Switch Software Configuration Guide

Catalyst 3750-x