logging history level

From: gladston@br.ibm.com
Date: Tue Nov 23 2004 - 17:41:21 GMT-3

• Next message: Brian Dennis: "RE: IPv6 books"
• Previous message: amilabs: "RE: Using IOS to generate a specific volume of traffic"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This page says that "logging history level" changes the level of syslog messages stored in the history and sent to the SNMP server.

=============================
quoted
Router(config)# logging trap level
 Limits the number of messages logged to the syslog servers
 

Router(config)# logging history level
 Changes the default level of syslog messages stored in the history file and sent to the SNMP server.
 
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_c/fcfprt3/fcf013.htm#wp1001168
===============================

Tests shows that logging history debugging does not change the logging trap level:

r4#sh logg
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns)
Console logging: level debugging, 28 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: disabled
Logging Exception size (4096 bytes)
Trap logging: level informational, 32 message lines logged

r4(config)#logging trap debugging
r4#sh logg
Trap logging: level debugging, 33 message lines logged

r4(config)#logging trap informational
r4#sh logg
Trap logging: level informational, 34 message lines logged

r4(config)#logging history debugging
r4#sh logg
Trap logging: level informational, 35 message lines logged

Any Thoughts?

• Next message: Brian Dennis: "RE: IPv6 books"
• Previous message: amilabs: "RE: Using IOS to generate a specific volume of traffic"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:49 GMT-3