Five Debugs You Must Know Cisco CCNA / CCNP Exam Tutorial
When it comes to RIP, "debug ip rip" is the primary debug to use. This debug will show you the contents of the routing update packets, & is vital in diagnosing RIP version mismatches & routing update authentication issues.
To pass the BSCI exam & move six step closer to CCNP certification success, you have got to know how & when to use debug commands to troubleshoot & verify network operations. While you should never practice debug commands on a production network, it is important to get some hands-on experience with them & not rely on "router simulators" & books to learn about them.
You know how to use the variance command to configure unequal-cost load-sharing with IGRP, but IGRP has no topology table that will give you the feasible successor metrics you need. With IGRP, you need to use the "debug ip igrp transactions" command to get these vital metrics.
Several factors are considered by OSPF-enabled routers when it comes to forming adjacencies, including hello & dead timer settings. If an adjacency doesn't form when you think it should, run "debug ip ospf adj". The reason the adjacency is not forming is usually seen quickly with this command's output.
When it comes to PPP, it can be frustrating to try to spot a problem with a password or username. Instead of staring at the configuration for 10 minutes, run "debug ppp negotiation" & send a ping over the link. This command will help you spot the router with the misconfigured username or password, not to mention saving you a lot of time!
Let's not ignore Layer one! If frame relay mappings are not forming according to your configuration, run "debug frame lmi". This debug will permit you to quickly diagnose & correct any LMI mismatches.
Effectively using debugs during your CCNA & CCNP exam study will help you truly understand what is going on "behind the command" - & it will come in handy on that day when your production network is not doing what you (think) you told it to do!
When it comes to RIP, "debug ip rip" is the primary debug to use. This debug will show you the contents of the routing update packets, & is vital in diagnosing RIP version mismatches & routing update authentication issues.
To pass the BSCI exam & move six step closer to CCNP certification success, you have got to know how & when to use debug commands to troubleshoot & verify network operations. While you should never practice debug commands on a production network, it is important to get some hands-on experience with them & not rely on "router simulators" & books to learn about them.
You know how to use the variance command to configure unequal-cost load-sharing with IGRP, but IGRP has no topology table that will give you the feasible successor metrics you need. With IGRP, you need to use the "debug ip igrp transactions" command to get these vital metrics.
Several factors are considered by OSPF-enabled routers when it comes to forming adjacencies, including hello & dead timer settings. If an adjacency doesn't form when you think it should, run "debug ip ospf adj". The reason the adjacency is not forming is usually seen quickly with this command's output.
When it comes to PPP, it can be frustrating to try to spot a problem with a password or username. Instead of staring at the configuration for 10 minutes, run "debug ppp negotiation" & send a ping over the link. This command will help you spot the router with the misconfigured username or password, not to mention saving you a lot of time!
Let's not ignore Layer one! If frame relay mappings are not forming according to your configuration, run "debug frame lmi". This debug will permit you to quickly diagnose & correct any LMI mismatches.
Effectively using debugs during your CCNA & CCNP exam study will help you truly understand what is going on "behind the command" - & it will come in handy on that day when your production network is not doing what you (think) you told it to do!
0 comments:
Post a Comment