From: NET HE (he_net@hotmail.com)
Date: Sun Feb 15 2009 - 19:48:47 ARST
I agree with Hobbs.
And it's simple to verify using "show logging". Before "logging trap" to
define logging syslog level, it's by default defined as informational.Best
Regards, Net (Xin) He > Date: Sun, 15 Feb 2009 14:38:24 -0700> Subject: Re:
question about logging trap command> From: deadheadblues@gmail.com> To:
slidersv@gmail.com> CC: o.neghina@gmail.com; ccielab@groupstudy.com> > Hold
on...That is "snmp-server enable traps syslog"> > According to the DocCD
logging trap specifies what messages get sent to the> server:> > "To limit how
many messages are sent to the syslog servers, use the logging> trap router
configuration command."> >
http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_09.html#wp10
15177> > Furthermore:> > "A trap is an unsolicited message sent to a remote
network management host.> Logging traps should not be confused with SNMP traps
(SNMP logging traps> require the use of the CISCO -SYSLOG-MIB, are enabled
using the *snmp-server> enable traps syslog* command, and are sent using the
Simple Network> Management Protocol.) "> > > On Sun, Feb 15, 2009 at 2:28 PM,
Pavel Bykov <slidersv@gmail.com> wrote:> > Ovidiu,> > These are separate
things.> > 1. logging x.x.x.x command sends SYSLOG messages using UDP/514> >
2. logging trap command is an auxiliary SNMP command (has to be used in> >
conjuction with other SNMP commands) that sends local SYSLOG messages into> >
SNMP traps and sends them using UDP/162> >> > On Sun, Feb 15, 2009 at 12:49
PM, Ovidiu Neghina <o.neghina@gmail.com> >wrote:> >> >> Hi> >> I have read the
command reference for logging trap and I need your> opinion.> >> If we type <
logging 223.1.9.100 > then the router will send by> >> default logs up to and
including informational level.> >> I have a lab that asks for all log messages
to be sent to server> >> 223.1.9.100. My understanding is that we should
type:> >> < logging 223.1.9.100 >> >> and> >> <logging trap debugging >> >> to
have all logs messages sent to the server.> >>> >> The solution however shows
only logging 223.1.9.100 which I believe> >> it is incomplete.> >>> >> What do
you think ?> >>> >> Br,> >> Ovidiu> >>> >>> >> Blogs and organic groups at
http://www.ccie.net> >>> >>
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:11 ARST