Correct configuration of logging history size

Unanswered Question
Nov 13th, 2007


instead of using a separate syslog server I want to configure our switches to send the syslog messages to our network management system via snmp traps:

logging history informational

snmp-server enable traps syslog


How can I garantuee that every syslog message is sent via snmp trap?

Is there any need to increase the logging history size from one to any higher number of messages to prevent messages from being dropped? Or is every message in the history table picked up by the snmp process fast enough?

Many thanks in advance,


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
mchin345 Mon, 11/19/2007 - 10:41

The snmp-server enable traps syslog command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command

To specify the severity level at which notifications should be generated, use the logging history global configuration command.

The following example enables the router to send system logging messages at severity levels 0 (emergencies) through 2 (critical) to the host at the address using the community string defined as public:

Router(config)# snmp-server enable traps syslog

Router(config)# logging history 2

Router(config)# snmp-server host traps version 2c public

thorsten.steffen Tue, 11/20/2007 - 00:09


what I was asking for is the recommended configuration of the logging history size which you can configure with the command

"logging history size".

Cisco Documentation about this command is:


logging history size

To change the number of syslog messages stored in the router's history table, use the logging history size command in global configuration mode. To return the number of messages to the default value, use the no form of this command.

Syntax Description


Number from 1 to 500 that indicates the maximum number of messages stored in the history table. The default is one message.


One message

Command Modes

Global configuration

Usage Guidelines

When the history table is full (that is, it contains the maximum number of message entries specified with the logging history size command), the oldest message entry is deleted from the table to allow the new message entry to be stored.


Best Regards,



This Discussion