Łukasz Bromirski wrote on 27/08/2010 01:13:
On
2010-08-26 22:37, Jared Mauch wrote:
It's more about the culture at Cisco of "we
can introduce
> undocumented changes at our own whim and not give you knobs
> to disable them".
This feature was introduced as a feature request from a number of
accounts, it is documented in syslog messages reference guide.
With such widespread number of different customers, it's hard to
choose only features that are OK for 100% of them.
While I understand your frustration, new syslog messages are normally
not part of release notes information.
Now, there's syslog feature for filtering the messages, so for
example for buffered target, you may set something like this:
logging discriminator TEST facility drops SYS mnemonics drops
EXIT_CONFIG
logging buffered discriminator TEST
That would actually drop all SYS messages
http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/htnmsylg.html#wp1056331
After the first filtering criterion results in
a message being blocked, the filtering check stops.
We have already implemented the message discriminator (we use this or ESM for similar
annoying messages), until a better solution is found.
Imho, "logging userinfo" should be expanded to include this
functionality.
--
Tassos
Of
course for remote logging host it may be:
logging host 3.3.3.3 discriminator TEST
HTH although it's a workaround not a 'knob' to turn it on/off,
|
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
