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:
Topology Above is the simple topology based on which I have the scenario which I would like to resolve: Notes:1. BGP running between routers2. Networks behind each ISP can transit into each other using DC1 and DC2.3. Site 1 - has TPG IPVPN conne...
I have two switches, both with SFPs. When I connect them directly, with a fiber patch cable, they work fine and trunk well. When I put them over a fiber backbone, they both go to down/down. We flashlight tested three separate backbone co...
Hi there, please move if in wrong forumI have a single switch (Switch1 10.10.6.10) with three VLANS (VLAN200, VLAN300 and VLAN400)I want to add two switches for more ports (Switch2 10.10.6.20 and Switch3 10.10.6.30) so all three switches have all three VL...
I have a Cisco Catalyst 3560-CX switch and an RV320 router.I am trying to configure my router only for VPN and the switch in layer 3, I have 3 Vlan: Vlan 2 (wireless data), vlan 3 (VoIP server) and Vlan 4 (NAS and web server), but I still can't ping with ...