Debug IP RIP Command on CISCO Router/Switch

Command

Debug IP RIP

Use

This command enables RIP debugging messages. The debugging shows RIP updates that are being sent and received.

Syntax

Router#debug ip rip

Example

In the below example we enable RIP debugging on R2.

R2#debug ip rip
RIP protocol debugging is on
R2#
*Mar 1 00:59:36.891: RIP: received v2 update from 10.1.1.1 on FastEthernet0/0
*Mar 1 00:59:36.895: 1.1.1.1/32 via 0.0.0.0 in 1 hops
*Mar 1 00:59:36.899: 1.2.2.2/32 via 0.0.0.0 in 1 hops
*Mar 1 00:59:36.903: 1.3.3.3/32 via 0.0.0.0 in 1 hops
R2#
*Mar 1 00:59:43.907: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)
*Mar 1 00:59:43.907: RIP: build update entries
*Mar 1 00:59:43.907: 1.1.1.1/32 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:59:43.911: 1.2.2.2/32 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:59:43.911: 1.3.3.3/32 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:59:43.915: 10.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:59:43.915: 10.2.2.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:59:43.915: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)
R2#
*Mar 1 00:59:46.971: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.2.2.2)
*Mar 1 00:59:46.975: RIP: build update entries
*Mar 1 00:59:46.975: 1.1.1.1/32 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:59:46.979: 1.2.2.2/32 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:59:46.979: 1.3.3.3/32 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:59:46.983: 2.2.2.2/32 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:59:46.987: 10.1.1.0/24 via 0.0.0.0, metric 1, tag 0
R2#undebug all
*Mar 1 00:59:55.767: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.1.2)
*Mar 1 00:59:55.771: RIP: build update entries
*Mar 1 00:59:55.771: 2.2.2.2/32 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:59:55.775: 10.2.2.0/24 via 0.0.0.0, metric 1, tag 0
R2#undebug all
All possible debugging has been turned off
R2#

Related Articles

Leave a Reply

avatar