Using debug can
be challenging for some students as they become overwhelmed by the wealth of
information that floods their screen and they are unable to decipher the
meaning. Instructors should take time here to ensure that students start to
interpret some of the debug output so that they are able to
efficiently troubleshoot errors. Capture some debug output
to a disk, enlarge it and display it up on a white background for discussion
and interpretation. Make sure the students become familiar with Figures
through
. Although the
lab is required, instructors are encouraged to adjust it to the lab environment
and the students.
The practical lab and e-Lab enable students to
troubleshoot using debug.
This page explains the use of the debug ip rip
command.
Use the debug ip rip command to display RIP
routing updates as they are sent and received.
The no
debug all or undebug all commands will turn off
all debugging.
The example shows that the router being debugged has
received updates from one router at source address 10.1.1.2.
The
router at source address 10.1.1.2 sent information about two destinations in
the routing table update. The router being debugged also sent updates, in both
cases to the multicast address 224.0.0.9 as the destination. The number in
parentheses is the source address encapsulated into the IP header.
Other
outputs sometimes seen from the debug ip rip command
includes entries such as the following:
RIP: broadcasting
general request on Ethernet0
RIP:
broadcasting general request on Ethernet1
These outputs
appear at startup or when an event occurs such as an interface transition or a
user manually clears the routing table.
An entry, such as the following,
is most likely caused by a malformed packet from the transmitter:
RIP: bad version 128 from 160.89.80.43
Examples of debug ip rip outputs and meanings are shown
in Figure
.
The Lab
Activities will help students become more familiar with
debug commands.