From: ccie2be (ccie2be@nyc.rr.com)
Date: Thu May 26 2005 - 21:46:17 GMT-3
From my study notes:
-Gotcha: Unlike when sending log messages to other destinations such as the
internal buffer, or syslog server, to send log messages to an snmp-server,
you don't use a command that begins with logging, you use the command
snmp-server enable trap syslog along with whatever other commands are needed
to for snmp.
-Gotcha: Although you might think that the logging trap <severity level> is
related to snmp traps, actually, this command is used to specify which
severity levels messages are sent to the syslog server and has nothing to do
with snmp.
HTH, Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
simon hart
Sent: Wednesday, March 16, 2005 3:23 PM
To: gladston@br.ibm.com; ccielab@groupstudy.com
Subject: RE: SNMP Syslog
Not entirely sure, but I think you should have
logging traps debugging
or
logging traps 7
Simon
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
gladston@br.ibm.com
Sent: 16 March 2005 18:42
To: ccielab@groupstudy.com
Subject: SNMP Syslog
Reading Doyle vol II and Deal's Cisco Router Firewall Security I thought it
would be possible to send any syslog messages to the SNMP station
management, but it seems to work differently.
Only some messages are sent via SNMP, even though "logging history
debugging" is configured.
Any feedback appreciated.
r1#sh logg
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0
flushes, 0 overruns)
Console logging: level emergencies, 1439 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 4713 messages logged
Logging Exception size (4096 bytes)
Trap logging: level debugging, 1851 message lines logged
r1#sh snmp
Chassis: 26411040
0 SNMP packets input
0 Bad SNMP version errors
0 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
0 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
0 Get-next PDUs
0 Set-request PDUs
107 SNMP packets output
0 Too big errors (Maximum packet size 1500)
0 No such name errors
0 Bad values errors
0 General errors
0 Response PDUs
107 Trap PDUs
SNMP logging: enabled
Logging to 172.16.100.100.162, 0/10, 12 sent, 0 dropped.
r1#
r1#sh snmp
Chassis: 26411040
0 SNMP packets input
0 Bad SNMP version errors
0 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
0 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
0 Get-next PDUs
0 Set-request PDUs
107 SNMP packets output
0 Too big errors (Maximum packet size 1500)
0 No such name errors
0 Bad values errors
0 General errors
0 Response PDUs
107 Trap PDUs
SNMP logging: enabled
Logging to 172.16.100.100.162, 0/10, 12 sent, 0 dropped.
r1#
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:12:02 GMT-3