From: Ivan Walker (ivan@itpro.co.nz)
Date: Sun Feb 15 2009 - 20:13:02 ARST
I believe to send syslog as an SNMP trap you use "snmp-server enable
traps syslog" (1) and that "logging trap <level>" sets the messages sent
to the configured syslog servers (2). I think the command logging trap
<level> is not so well named so leads to confusion. Something like
logging syslog-servers level <level> would be easier.
(1)
http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_19.html#wp1081885
(2)
http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_09.html#wp1015177
Ivan
Pavel Bykov 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
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
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