R2#debug ip rip ?
database
RIP database events
events
RIP protocol events
trigger
RIP trigger extension
<cr>
R2#debug ip rip
RIP protocol debugging is on
R2#
*Mar 1 00:13:10.147: RIP:
received v2 update from 10.1.12.1 on FastEthernet0/0
*Mar 1 00:13:10.151: 1.1.1.0/24
via 0.0.0.0 in 1 hops
R2#
*Mar 1 00:13:13.891: RIP:
sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)
*Mar 1 00:13:13.891: RIP:
build update entries
*Mar 1 00:13:13.891: 1.1.1.0/24 via
0.0.0.0, metric 2, tag 0
*Mar 1 00:13:13.891: 3.3.3.0/24 via
0.0.0.0, metric 2, tag 0
*Mar 1 00:13:13.891: 10.1.12.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:13:13.891: 10.1.13.0/24 via
0.0.0.0, metric 1, tag 0
*Mar 1 00:13:13.899: RIP: ignored v2 packet from
2.2.2.2 (sourced from one of our addresses)
R2#
*Mar 1 00:13:15.191: RIP: sending v2 update to
224.0.0.9 via FastEthernet1/0 (10.1.13.2)
*Mar 1 00:13:15.195: RIP: build update entries
*Mar 1 00:13:15.195: 1.1.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:13:15.199: 2.2.2.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:13:15.199: 10.1.12.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:13:15.331: RIP: received v2 update from
10.1.13.3 on FastEthernet1/0
*Mar 1 00:13:15.331: 3.3.3.0/24 via 0.0.0.0 in 1 hops
R2#
*Mar 1 00:13:25.999: RIP: sending v2 update to
224.0.0.9 via FastEthernet0/0 (10.1.12.2)
*Mar 1 00:13:26.003: RIP: build update entries
*Mar 1 00:13:26.003: 2.2.2.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 00:13:26.007: 3.3.3.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:13:26.007: 10.1.13.0/24 via 0.0.0.0, metric 1, tag 0
R2#debug ip rip database
RIP
database events debugging is on
R2#
*Mar 1 00:19:09.203: RIP-DB: network_update with
1.1.1.0/24 succeeds
*Mar 1 00:19:09.207: RIP-DB: adding 1.1.1.0/24
(metric 1) via 10.1.12.1 on FastEthernet0/0 to RIP database
R2#
*Mar 1 00:19:19.207: RIP-DB: network_update with
3.3.3.0/24 succeeds
*Mar 1 00:19:19.211: RIP-DB: adding 3.3.3.0/24
(metric 1) via 10.1.13.3 on FastEthernet1/0 to RIP database
R2#debug ip rip events
RIP event debugging is on
R2#
*Mar 1 00:21:06.799:
RIP: received v2 update from 10.1.13.3 on FastEthernet1/0
*Mar 1 00:21:06.799: RIP: Update contains 1 routes
R2#
*Mar 1 00:21:10.047: RIP: sending v2 update to
224.0.0.9 via Loopback0 (2.2.2.2)
*Mar 1 00:21:10.051: RIP: Update contains 4 routes
*Mar 1 00:21:10.051: RIP: Update queued
*Mar 1 00:21:10.055: RIP: Update sent via
Loopback0
*Mar 1 00:21:10.063: RIP: ignored v2 packet from
2.2.2.2 (sourced from one of our addresses)
R2#
*Mar 1 00:21:12.275: RIP: sending v2 update to
224.0.0.9 via FastEthernet0/0 (10.1.12.2)
*Mar 1 00:21:12.279: RIP: Update contains 3 routes
*Mar 1 00:21:12.279: RIP: Update queued
*Mar 1 00:21:12.283: RIP: Update sent via
FastEthernet0/0
R2#
*Mar 1 00:21:16.343: RIP: sending v2 update to
224.0.0.9 via FastEthernet1/0 (10.1.13.2)
*Mar 1 00:21:16.343: RIP: Update contains 3 routes
*Mar 1 00:21:16.343: RIP: Update queued
*Mar 1 00:21:16.343: RIP: Update sent via
FastEthernet1/0
R2#
*Mar 1 00:21:28.731: RIP: received v2 update from
10.1.12.1 on FastEthernet0/0
*Mar 1 00:21:28.735: RIP: Update contains 1 routes
R2#
*Mar 1 00:21:35.191:
RIP: received v2 update from 10.1.13.3 on FastEthernet1/0