Logging Messages To A Unix Syslog Server; Limiting Messages To A Syslog Server - Cisco AJ732A - MDS 9134 Fabric Switch Command Reference Manual

Using Debug Commands
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
logging monitor notification

Logging Messages to a UNIX Syslog Server

To log messages to a syslog server host, use the logging host global configuration command. The full
syntax of this command follows:
The logging host command identifies a syslog server host that is to receive logging messages. The
ip-address argument is the IP address of the host. By issuing this command more than once, you build a
list of syslog servers that receive logging messages.
The no logging host command deletes the syslog server with the specified address from the list of
syslogs.

Limiting Messages to a Syslog Server

To limit the number of messages sent to syslog servers, use the logging trap router configuration
command. The full syntax of this command follows:
The logging trap command limits the logging messages sent to syslog servers to logging messages with
a level up to and including the specified level argument.
To send logging messages to a syslog server, specify its host address with the logging host command.
The default trap level is informational.
The no logging trap command returns the trap level to the default.
The current software generates the following categories of syslog messages:
•
•
•
•
•
•
•
The show logging privileged EXEC command displays the addresses and levels associated with the
current logging setup. The command output also includes ancillary statistics.
Example of Setting Up a UNIX Syslog Daemon
To set up the syslog daemon on a 4.3 BSD UNIX system, include a line such as the following in the file
/etc/syslog.conf:
local7.debugging /usr/adm/logs/tiplog
Cisco MDS 9000 Family Command Reference
1-44
logging host {ip-address | host-name} [xml]
no logging host {ip-address | host-name} [xml]
logging trap level
no logging trap
Error messages at the emergencies level.
Error messages at the alerts level.
Error messages at the critical level.
Error messages about software or hardware malfunctions, displayed at the errors level.
Interface up/down transitions and system restart messages, displayed at the notification level.
Reload requests and low-process stack messages, displayed at the informational level.
Output from the debug commands, displayed at the debugging level.
Chapter 1 CLI Overview
OL-18089-01, Cisco MDS NX-OS Release 4.x