%SYS-5-CONFIG_I: Configured from 192.x.x.x by snmp

Unanswered Question

Oh sorry about that. It's a 7206 VXR.


router(config)#no logging ?

Hostname or A.B.C.D IP address of the logging host

buffered Set buffered logging parameters

cns-events Set CNS Event logging level

console Set console logging parameters

count Count every log message and timestamp last occurrence

exception Limit size of exception flush output

facility Facility parameter for syslog messages

history Configure syslog history table

host Set syslog server IP address and parameters

monitor Set terminal line (monitor) logging parameters

on Enable logging to all enabled destinations

origin-id Add origin ID to syslog messages

rate-limit Set messages per second limit

reload Set reload logging level

server-arp Enable sending ARP requests for syslog servers when first configured

source-interface Specify interface for source address in logging transactions

trap Set syslog server logging level

router(config)#no logging


Farrukh Haroon Mon, 09/08/2008 - 18:13

I don't think this functionality is available on the 7206, but maybe others can suggest something better than this.



Joe Clarke Tue, 09/09/2008 - 08:19

If you don't want to see this message, you would have to lower your syslog trap severity to 4 or lower:

logging trap warning

Of course, this will prevent other useful severity 5 messages from being sent. An alternative to this approach is to use the Embedded Syslog Manager (ESM) which is available in 12.3(2)T and higher. Using ESM, you can build a Tcl filter which will drop this one message. See http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_esm_syslog.html for more details on ESM.

However, this class of message is quite important. It would be better to track down what on the 192.x.x.x host is trigger SNMP config changes, and stop it.


This Discussion