Cisco Cisco IOS Software Releases 12.2 B Mode D'Emploi

Page de 39
 
A-4
Cisco Packet Serving Data Node (PDSN) 1.2
OL-3236-02
Appendix A      Using Debug Commands for PDSN Release 1.2
Introduction
Logging to a Unix Syslog server
To log messages to a syslog server host, use the logging router configuration command:
logging ip-address
no logging ip-address
The logging command identifies the syslog server host that will receive the logging messages. The 
ip-address argument is the IP address of the host. Issuing this command more than once will build a list 
of syslog servers that receive the logging messages. The no logging command deletes the syslog server 
with the specified address from the list of syslogs.
The debugging destination (console, aux port, vty port, internal buffer) used affects the system overhead. 
Logging to a console produces the highest overhead. The virtual terminal (vty) produces less overhead, 
and a syslog server produces even less. Logging to an internal buffer produces the least overhead of any 
method.
Note
The no logging console and terminal no monitor commands only prevent the output from being output 
to the console, aux port, vty port. It does not stop the debugging, so router resources will continue to be 
used for debugging even though no debug messages will be displayed.
Enabling Message Logging
To enable message logging to all supported destinations other than console, use the logging on 
command. The no logging on command is used to direct logging to the console only and disable logging 
output to other destinations.
A sample of a router logging configuration is:
no logging console — don’t send logs to router console
logging buffered 16384- 16k byte history buffer on router
logging trap debugging- catch debugging level traps (i.e. everything)
logging facility local7— Syslog facility on syslog server
logging x.x.x.1- address of first syslog server
logging x.x.x.2- ip address of second syslog server
To setup the syslog daemon on a Unix system, include a line similar to the following into the 
/etc/syslog.conf:
local7.debugging/var/log/cisco.log
Setting Message Logging Levels
You can set logging levels when logging messages to the console, monitor or syslog server. The levels, 
keywords and descriptions are:
Level 0 - Emergencies - System is unusable
Level 1 - Alerts - Immediate action is needed
Level 2 - Critical - Critical conditions exist
Level 3 - Errors - Error conditions exist
Level 4 - Warnings - Warning conditions exist
Level 5 - Notifications - Normal, but significant conditions exist