08-19-2020 08:17 AM - edited 08-19-2020 08:18 AM
HI
On ASR1002-X using IOS 16.12.4 How can I get rid of following Log:
Aug 19 08:49:45.170: %SYS-5-CONFIG_P: Configured programmatically by process VTEMPLATE Background Mgr from console as console
Aug 19 08:51:35.364: %SYS-5-CONFIG_P: Configured programmatically by process VTEMPLATE Background Mgr from console as console
Aug 19 08:51:42.069: %SYS-5-CONFIG_P: Configured programmatically by process VTEMPLATE Background Mgr from console as console
Aug 19 08:55:41.531: %SYS-5-CONFIG_P: Configured programmatically by process VTEMPLATE Background Mgr from console as console
Thank you
Solved! Go to Solution.
08-19-2020 12:17 PM
Hello,
in addition to the other post, chances are you are hitting the bug below:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs94457/?rfs=iqvred
08-20-2020 01:52 AM
Hello Peyman,
It seems you're hitting a cosmetic issue that has been documented in here:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs94457
A suggested workaround is to apply a discriminator. Below is an example of a discriminator to suppress these log messages:
Router# logging discriminator TEST mnemonic drops .*CONFIG_P.* Router# logging buffered discriminator TEST
Thanks!
Marin
08-19-2020 10:13 AM
- You could use a logging discriminator , here is an example tutorial :
https://writemem.co.uk/logging-discriminator/
M,
08-19-2020 12:17 PM
Hello,
in addition to the other post, chances are you are hitting the bug below:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs94457/?rfs=iqvred
08-20-2020 01:52 AM
Hello Peyman,
It seems you're hitting a cosmetic issue that has been documented in here:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs94457
A suggested workaround is to apply a discriminator. Below is an example of a discriminator to suppress these log messages:
Router# logging discriminator TEST mnemonic drops .*CONFIG_P.* Router# logging buffered discriminator TEST
Thanks!
Marin
08-20-2020 07:48 AM
Thank you for the update...
07-06-2021 05:06 AM
This bug is showing as not viewable by the public now, so I can't confirm if this bug is relevant anymore. Any insight to whether this bug could be causing the same log message to spam our syslog in IOS-XE 17.3.3?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: