Move to CCNP certification success and to pass the BSCI exam, you have got to understand how and when to use debug commands verify and to troubleshoot network operations. As you ought to not practice debug commands on a production network, it is important to find some hands-on experience together and not rely on”router simulators” and books to learn about them.
When it has to do with RIP,”debug ip rip” will be the primary debug to use. This debug it so is also vital in assessing RIP model mismatches and navigation upgrade authentication difficulties, also will show you the contents of the routing update packets.
You understand how to use the command to configure unequal-cost load-sharing using IGRP, however, IGRP has no topology table which will provide the possible successor metrics you need to one of. Together with IGRP, you will need to use this”debug ip igrp transactions” control to find these vital metrics.
When it comes to forming adjacencies, including dead and hello timer configurations OSPF-enabled routers consider several factors. If an adjacency does not sort when you think it should, operate”debug ip ospf adj”. The reason the adjacency is not forming is seen with the output of this command.
Let’s not dismiss Layer Two! If frame relay mappings aren’t forming depending on your configuration, run”debug frame lmi”. This debug will allow you to quickly diagnose and correct any LMI mismatches.
When it comes in PPP, it can be very frustrating to try to spot a problem with username or a password. Rather than staring at the setup for 10 minutes, run”debug ppp negotiation” and deliver a ping over the link. This control will allow you to spot the router using the username or password, and of course saving you plenty of time!
Effectively using debugs during your CCNA and CCNP assessment research will help you really understand what is going on”behind the control” – and it is going to really come in handy on that day as soon as your production network isn’t doing what you (think) you told it to do!