Can debug inter s0/0/0 bring the entire network down

amb1s1

Can debug inter s0/0/0 bring the entire network down? At my company we have like 200 branches and one of them had s0/0/0 down and I did debug inter s0/0/0. I don't concidence, but some of the branches went down. Can anybody tell me if I have to start writing my resume?

miller811

amb1s1 wrote: »

Can debug inter s0/0/0 bring the entire network down? At my company we have like 200 branches and one of them had s0/0/0 down and I did debug inter s0/0/0. I don't concidence, but some of the branches went down. Can anybody tell me if I have to start writing my resume?

did you run debug on the headend router?

Caution Debugging is assigned a high priority in your router CPU process, and it can render your router unusable. For this reason, use debug commands only to troubleshoot specific problems.The best time to use debug commands is during periods of low network traffic and few users to decrease
the likelihood that the debug command processing overhead affects network users.

amb1s1

I used on one of the branches. The branch was closed and there were no traffic. If I do debug inter s0/0/0 on the branch, it won't go to the core. Right?

gojericho0

No, the debugging process will stay local to that router. When you did the debug before did the branches go down immediatly and all at once or were you gradually losing sites.

You can also do a sh process cpu history to see if your processor was spiking during the debugging intervals.

mikearama

amb1s1 wrote: »

Can debug inter s0/0/0 bring the entire network down? At my company we have like 200 branches and one of them had s0/0/0 down and I did debug inter s0/0/0. I don't concidence, but some of the branches went down. Can anybody tell me if I have to start writing my resume?

Heck no. I've never seen using debug render an individual device unreachable, despite any cautions/warnings offered. So to think that it did that, AND THEN brought down other branches??? I wouldn't buy that for a second.

amb1s1

I mean I know that it would not bring the entire enteprise down, but when I saw like 50 percent of the company down, my confidence went right to the floor. My guess is that Verizon had plan outage. I saw that BGP went down and then came back up in about 10 minutes. The day shift is investigating this. Now, I can go to sleep because you guys confirmed it. By the way, the mobile version (iPhone) of techexams.net rockss!!!

APA

do any of the other branches connect to the core via this branch you issued the debug on????

The reason I ask is because if you did overload the router resources then you would have taken down those branches that are utilizing this branch to get to the core....

redwarrior

I have had individual devices become unrepsonsive during debugs...usually WLAN modules or something of that sort that already has a lot to handle CPU-wise. The only way I could see that bringing down other sites would be if you'd done it on the head-end router and it went down or if that particular router was essential for routing to the other sites in some way...even so, it really didn't look like the debug you were trying to do should have used up much resources.

Forsaken_GA

Even though it probably doesn't help after the fact,

Anytime I'm about to do something that I think has the remotest chance of crashing a router I won't be able to physically lay hands on, I issue the 'reload in 5' command. That way, if I crash it, at least it should be able to recover in a short amount of time, and if I don't crash it, I can always cancel the reload.

Since you said the interface was already down prior to issuing the debug command, the subsequent crashes were likely just symptoms of the same effect that brought that interface down in the first place.

amb1s1

No, there is no branches under the one that I was debugging.