Debug is your friend!
Plazma
Member Posts: 503
in CCNA & CCENT
To everyone who is pursuing the CCNA and it's subsidiaries:
If you have a real lab to practice on, learn how to use the debug command.. i know it sounds silly to make a post about this, but hear me out.
I would say a huge chunk of people are visual learners, and such even more so that work with networking (after all, diagrams are amazing, and say more than words ever could). With the debug command, you actually see what is happening at a visual level as well (not with pretty pictures, but accurate descriptions of what is going on). When i was doing my CCNA, i never really utilized the debug command much, but now I have expanded my horizons, the debug command for me is an invaluable asset. It allows me to see WHAT is happening and 95% of the time, tell me (in almost plain English) WHY something is broken.
Think of the traceroute command (or tracert in windows) - it shows you what your tracing, where it's trying to go, and the route it has to take to get there.. exact same type of scenario.
Anyway.. that was a bit of a rant, but it took me a while to realize how great the debug command is, and I wanted to stress it for all the CCNA hopefuls.
If you have a real lab to practice on, learn how to use the debug command.. i know it sounds silly to make a post about this, but hear me out.
I would say a huge chunk of people are visual learners, and such even more so that work with networking (after all, diagrams are amazing, and say more than words ever could). With the debug command, you actually see what is happening at a visual level as well (not with pretty pictures, but accurate descriptions of what is going on). When i was doing my CCNA, i never really utilized the debug command much, but now I have expanded my horizons, the debug command for me is an invaluable asset. It allows me to see WHAT is happening and 95% of the time, tell me (in almost plain English) WHY something is broken.
Think of the traceroute command (or tracert in windows) - it shows you what your tracing, where it's trying to go, and the route it has to take to get there.. exact same type of scenario.
Anyway.. that was a bit of a rant, but it took me a while to realize how great the debug command is, and I wanted to stress it for all the CCNA hopefuls.
CCIE - COMPLETED!
Comments
-
Paul Boz
Member Posts: 2,620 ■■■■■■■■□□
Great thread. Debug commands carried me through the CCNP BSCI. You have to see whats going on to understand it.CCNP | CCIP | CCDP | CCNA, CCDA
CCNA Security | GSEC |GCFW | GCIH | GCIA
pbosworth@gmail.com
http://twitter.com/paul_bosworth
Blog: http://www.infosiege.net/ -
dredlord
Member Posts: 172
Is it my opinion or is the CCNA more focused on the show commands, yes I haven't touched ICND2 but most of ICND1 at least was show commands. Are there any nice debug command labs as most of what I have are show command labs. I admit that im a bit worried on the debugs as compared to my show command knowledge im week in them ( other then debug ip rip)
-
Paul Boz
Member Posts: 2,620 ■■■■■■■■□□
The CCNA is indeed more concerned with show commands. The only difference between show commands and debug commands is that one is static and one is dynamic.CCNP | CCIP | CCDP | CCNA, CCDA
CCNA Security | GSEC |GCFW | GCIH | GCIA
pbosworth@gmail.com
http://twitter.com/paul_bosworth
Blog: http://www.infosiege.net/ -
Plazma
Member Posts: 503
there are many debug commands, check the IOS docs for the complete list. The beauty of the debug is it is dynamic and usually tells you what is wrong or mismatched (per say) then just taking a shot in the dark and doing various show commands and fixing it..CCIE - COMPLETED!
-
ITdude
Member Posts: 1,181 ■■■□□□□□□□
Paul Boz wrote:Great thread. Debug commands carried me through the CCNP BSCI. You have to see whats going on to understand it.
I second that motion!
I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci)