Basicamente o que tu tens que digitar em modo de configura��o �:
logging on
logging <ip_do_monitor>
Existem mais op��es configur�veis, que estou te enviando abaixo...
[]s
Rafael.
Fonte:
http://www.cisco.com/univercd/cc/td/doc/product/software/ssr83/rpc_r/48119.h
tm#xtocid2328451
<++++++++++++++++++++++++++++++++++++++++++>
<+++ Redirecting System Error Messages ++++>
<++++++++++++++++++++++++++++++++++++++++++>
By default, the network server sends the output from the EXEC command debug
and system error messages to the console terminal.
To redirect these messages, as well as output from asynchronous events such
as interface transition, to other destinations, use the logging
configuration command options.
These destinations include the console terminal, virtual terminals, and UNIX
hosts running a syslog server; the syslog format is compatible with 4.3 BSD
UNIX.
To configure the logging of messages, you need to be in the configuration
command collection mode. To enter this mode, use the EXEC command configure
at the EXEC prompt (see the section "Entering Configuration Mode" in the
chapter "First-Time Startup and Basic Configuration" for the procedure).
The following sections describe how to implement these redirection options.
Enabling Message Logging
To enable or disable message logging, use the following global configuration
commands:
logging on
no logging on
The logging on command enables message logging to all supported destinations
other than the console. This behavior is the default.
The no logging on command enables logging to the console terminal only.
Logging Messages to an Internal Buffer
The default logging device is the console; all messages are displayed on the
console unless otherwise specified.
To log messages to an internal buffer, use the logging buffered global
configuration command. The full command syntax follows.
logging buffered
no logging buffered
The logging buffered command copies logging messages to an internal buffer
instead of writing them to the console terminal. The buffer is circular in
nature, so newer messages overwrite older messages. To display the messages
that are logged in the buffer, use the EXEC command show logging. The first
message displayed is the oldest message in the buffer.
The no logging buffered command cancels the use of the buffer and writes
messages to the console terminal, which is the default.
Logging Messages to the Console
To limit how many messages are logged to the console, use the logging
console global configuration command. The full syntax of this command
follows:
logging console level
no logging console
The logging console command limits the logging messages displayed on the
console terminal to messages with a level at or above the specified
severity, which is specified by the level argument.
The argument level can be one of the following keywords, listed here in
order from the most severe to the least severe level.
emergencies--System unusable
alerts--Immediate action needed
critical--Critical conditions
errors--Error conditions
warnings--Warning conditions (output from debug commands are logged at this
level)
notifications--Normal but significant conditions
informational--Informational messages only
debug--Debugging messages
The default is to log messages at the warnings level to the console.
The no logging console command disables logging to the console terminal.
Example:
This command sets console logging of messages at the debug level:
logging console debug
Logging Messages to Another Monitor
To limit the level of messages to log to the terminal lines (monitors), use
logging monitor command. The full syntax of this command follows.
logging monitor level
no logging monitor
The logging monitor command limits the logging messages displayed on
terminal lines other than the console line to messages with a level at or
above level. The argument level is one of the keywords described for the
logging console command in the previous section,
"Logging Messages to the Console." To display logging messages on a
terminal, use the privileged EXEC command terminal monitor.
The no logging monitor command disables logging to terminal lines other than
the console line.
Example:
This command sets the level of messages displayed on monitors other than the
console to notifications:
logging monitor notifications
Logging Messages to a UNIX Syslog Server
To log messages to the syslog server host, use the logging global
configuration command. The full syntax is as follows:
logging internet-address
no logging internet-address
The logging command identifies a syslog server host to receive logging
messages. The argument internet-address is the Internet 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 command deletes the syslog server with the specified address
from the list of syslogs.
Limiting Messages to a Syslog Server
To limit how many messages are sent to the syslog servers, use the logging
trap global configuration command. Its full syntax follows:
logging trap level
no logging trap
The logging trap command limits the logging messages sent to syslog servers
to messages with a level at or above level. The argument level is one of the
keywords described for the logging console command in the earlier section,
"Logging Messages to the Console."
To send logging messages to a syslog server, specify its host address with
the logging command.
The no logging trap command disables logging to syslog servers.
The current software generates four categories of the syslog messages:
Error messages about software or hardware malfunctions, displayed at the
errors level.
Output from the debug commands, displayed at the warnings level.
Interface up/down transitions and system restart messages, displayed at the
notifications level.
Reload requests and low-process stack messages, displayed at the
informational level.
The EXEC command show logging displays the addresses and levels associated
with the current logging setup. The command output also includes ancillary
statistics.
Example:
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.debug /usr/adm/logs/tiplog
The local7 keyword specifies the logging facility to be used.
The debug argument specifies the syslog level. See the previous level
arguments list for other arguments that can be listed.
The UNIX system sends messages at or below this level to the file specified
in the next field. The file must already exist, and the syslog daemon must
have permission to write to it.
____________________________________________
Rafael L�ff
Backbone Team
[EMAIL PROTECTED]
Vant Communications
www.vant.com.br
-----Original Message-----
From: Carlos Pin Vinicius [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 23, 2000 1:47 PM
To: Lista de Discuss�o Rede Wan
Subject: [redewan] Logging
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
Como posso gerar logs nos roteadores 2500 e 4500 e direcionar os eventos
para um "servidor de log"?
Abra�os
Pin
______________________________________________________________________
|
