01-11-2009 03:01 AM - edited 03-06-2019 03:22 AM
I used the following entry on Cat6500
show memory debug leaks
and it took up 100% of the CPU. Can 'show' commands eat up so much of CPU. I believe they are only display commands.
01-11-2009 05:17 AM
Hello Cisco_lite,
debug commands can have such a disruptive effect on the network device even on a powerful one like a C6500 with Sup720.
For example by using a debug stp I caused a C4500 to become unusable and I needed someone to reload it !
Actually, displaying in a console has a great impact on the system you should
increase the local logging buffer size to 1000000 bytes or more
logging buffered
logging console 4
set logging console 4 to avoid to see debug messages on the fly then later you see the logging buffer by using
sh log
Think that usually is less heavy to export log messages to a syslog server then to have them displayed on the console or VTY connection.
We used this method of exporting to a syslog with logging disabled on the console, to get some debug outputs for Cisco TAC during some Service Request.
Hope to help
Giuseppe
01-11-2009 05:25 AM
Thanks. But I was assuming the entry tp be show command and not debug. I believed debug commands had to start with 'debug'.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide