We often come accross the situations where the Router or the switch crashes after turning the Debug on. Some people would like to know why this happens.
When using debugging you want to have console logging turned off. Your console port is a very slow port and when you send the amount of messages that debugging sends, it over loads the console port and causes the processor to get backed up until it crashes.
Going forward you want to turn logging back on and specifically turn console logging off - no logging console. If you enter the terminal monitor command via telnet you will be able to see the same messages without the processor being affected as much.
Here is a link with the proper steps to do a debug capture:
Webcast video: Cisco SD-WAN Cloud onRamp for CoLocation
(Live Webcast Tuesday July 16, 2019 at 10 am Pacific/ 1 pm Eastern / 7 pm Paris)
This event had place on Tuesday 16th, July 2019 at 10hrs PDT
In this sessio...
Dear all, Currently I have been investigating the following limitation for example,Cat95K High Performance Model can configure FNF counter bytes/packets without long option butCat95K Normal and Cat93K do not support itself and long option is mandator...
Hi All, Bit confused with BGP graceful and restart procedures. Requirement is to shut bgp session to a bgp peer and then after the activity bring up the same session so that the BGP peering / route sharing gets back to normal. neighbor<ipv4-a...