A DEBUG OUTPUT
Friday, November 14, 2008
before that lets see a debug out put of rip
CODE
r1#debug ip rip events
RIP event debugging is on
r1#
*Mar 1 00:44:13.367: RIP: sending v2 update to 224.0.0.9 via Loopback50 (192.168.50.1)
*Mar 1 00:44:13.371: RIP: Update contains 9 routes ---------> *
*Mar 1 00:44:13.375: RIP: Update queued
*Mar 1 00:44:13.375: RIP: Update sent via Loopback50
*Mar 1 00:44:13.379: RIP: ignored v2 packet from 192.168.50.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:19.699: RIP: received v2 update from 172.16.12.2 on Serial2/0
*Mar 1 00:44:19.703: RIP: Update contains 2 routes
*Mar 1 00:44:20.151: RIP: sending v2 update to 224.0.0.9 via Loopback48 (192.168.48.1) -------->*
*Mar 1 00:44:20.155: RIP: Update contains 9 routes------>*
*Mar 1 00:44:20.159: RIP: Update queued
*Mar 1 00:44:20.159: RIP: Update sent via Loopback48----------->*
*Mar 1 00:44:20.163: RIP: ignored v2 packet from 192.168.48.1 (sourced from one of our addresses)
*Mar 1 00:44:20.527: RIP: sending v2 update to 224.0.0.9 via Loopback51 (192.168.51.1)
*Mar 1 00:44:20.531: RIP: Update contains 9 routes----------->*
*Mar 1 00:44:20.535: RIP: Update queued
r1#
*Mar 1 00:44:20.535: RIP: Update sent via Loopback51
*Mar 1 00:44:20.543: RIP: ignored v2 packet from 192.168.51.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:26.395: RIP: sending v2 update to 224.0.0.9 via Loopback49 (192.168.49.1)
*Mar 1 00:44:26.399: RIP: Update contains 9 routes
*Mar 1 00:44:26.403: RIP: Update queued
*Mar 1 00:44:26.403: RIP: Update sent via Loopback49
*Mar 1 00:44:26.411: RIP: ignored v2 packet from 192.168.49.1 (sourced from one of our addresses)
*Mar 1 00:44:27.175: RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.12.1)
*Mar 1 00:44:27.179: RIP: Update contains 7 routes
*Mar 1 00:44:27.183: RIP: Update queued
*Mar 1 00:44:27.183: RIP: Update sent via Serial2/0
*Mar 1 00:44:27.319: RIP: sending v2 update to 224.0.0.9 via Loopback70 (192.168.70.1)
r1#
*Mar 1 00:44:27.323: RIP: Update contains 9 routes
*Mar 1 00:44:27.327: RIP: Update queued
*Mar 1 00:44:27.327: RIP: Update sent via Loopback70
*Mar 1 00:44:27.335: RIP: ignored v2 packet from 192.168.70.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:34.667: RIP: sending v2 update to 224.0.0.9 via Loopback0 (172.16.1.1)
*Mar 1 00:44:34.671: RIP: Update contains 9 routes
*Mar 1 00:44:34.675: RIP: Update queued
*Mar 1 00:44:34.675: RIP: Update sent via Loopback0
*Mar 1 00:44:34.679: RIP: ignored v2 packet from 172.16.1.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:40.635: RIP: sending v2 update to 224.0.0.9 via Loopback50 (192.168.50.1)
*Mar 1 00:44:40.639: RIP: Update contains 9 routes
*Mar 1 00:44:40.643: RIP: Update queued
*Mar 1 00:44:40.643: RIP: Update sent via Loopback50
*Mar 1 00:44:40.651: RIP: ignored v2 packet from 192.168.50.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:46.279: RIP: received v2 update from 172.16.12.2 on Serial2/0
*Mar 1 00:44:46.283: RIP: Update contains 2 routes
*Mar 1 00:44:47.087: RIP: sending v2 update to 224.0.0.9 via Loopback51 (192.168.51.1)
*Mar 1 00:44:47.091: RIP: Update contains 9 routes
*Mar 1 00:44:47.095: RIP: Update queued
*Mar 1 00:44:47.095: RIP: Update sent via Loopback51
*Mar 1 00:44:47.099: RIP: ignored v2 packet from 192.168.51.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:50.135: RIP: sending v2 update to 224.0.0.9 via Loopback48 (192.168.48.1)
*Mar 1 00:44:50.139: RIP: Update contains 9 routes
*Mar 1 00:44:50.143: RIP: Update queued
*Mar 1 00:44:50.143: RIP: Update sent via Loopback48
*Mar 1 00:44:50.151: RIP: ignored v2 packet from 192.168.48.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:54.911: RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.12.1)
*Mar 1 00:44:54.915: RIP: Update contains 7 routes
*Mar 1 00:44:54.919: RIP: Update queued
*Mar 1 00:44:54.919: RIP: Update sent via Serial2/0
*Mar 1 00:44:55.431: RIP: sending v2 update to 224.0.0.9 via Loopback49 (192.168.49.1)
*Mar 1 00:44:55.435: RIP: Update contains 9 routes
*Mar 1 00:44:55.439: RIP: Update queued
*Mar 1 00:44:55.439: RIP: Update sent via Loopback49
*Mar 1 00:44:55.443: RIP: ignored v2 packet from 192.168.49.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:56.467: RIP: sending v2 update to 224.0.0.9 via Loopback70 (192.168.70.1)
*Mar 1 00:44:56.467: RIP: Update contains 9 routes
*Mar 1 00:44:56.467: RIP: Update queued
*Mar 1 00:44:56.467: RIP: Update sent via Loopback70
*Mar 1 00:44:56.467: RIP: ignored v2 packet from 192.168.70.1 (sourced from one of our addresses)
r1#u all
All possible debugging has been turned off
r1#
*Mar 1 00:45:03.159: RIP: sending v2 update to 224.0.0.9 via Loopback0 (172.16.1.1)
*Mar 1 00:45:03.163: RIP: Update contains 9 routes
*Mar 1 00:45:03.167: RIP: Update queued
*Mar 1 00:45:03.167: RIP: Update sent via Loopback0
*Mar 1 00:45:03.175: RIP: ignored v2 packet from 172.16.1.1 (sourced from one of our addresses)
r1#
RIP event debugging is on
r1#
*Mar 1 00:44:13.367: RIP: sending v2 update to 224.0.0.9 via Loopback50 (192.168.50.1)
*Mar 1 00:44:13.371: RIP: Update contains 9 routes ---------> *
*Mar 1 00:44:13.375: RIP: Update queued
*Mar 1 00:44:13.375: RIP: Update sent via Loopback50
*Mar 1 00:44:13.379: RIP: ignored v2 packet from 192.168.50.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:19.699: RIP: received v2 update from 172.16.12.2 on Serial2/0
*Mar 1 00:44:19.703: RIP: Update contains 2 routes
*Mar 1 00:44:20.151: RIP: sending v2 update to 224.0.0.9 via Loopback48 (192.168.48.1) -------->*
*Mar 1 00:44:20.155: RIP: Update contains 9 routes------>*
*Mar 1 00:44:20.159: RIP: Update queued
*Mar 1 00:44:20.159: RIP: Update sent via Loopback48----------->*
*Mar 1 00:44:20.163: RIP: ignored v2 packet from 192.168.48.1 (sourced from one of our addresses)
*Mar 1 00:44:20.527: RIP: sending v2 update to 224.0.0.9 via Loopback51 (192.168.51.1)
*Mar 1 00:44:20.531: RIP: Update contains 9 routes----------->*
*Mar 1 00:44:20.535: RIP: Update queued
r1#
*Mar 1 00:44:20.535: RIP: Update sent via Loopback51
*Mar 1 00:44:20.543: RIP: ignored v2 packet from 192.168.51.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:26.395: RIP: sending v2 update to 224.0.0.9 via Loopback49 (192.168.49.1)
*Mar 1 00:44:26.399: RIP: Update contains 9 routes
*Mar 1 00:44:26.403: RIP: Update queued
*Mar 1 00:44:26.403: RIP: Update sent via Loopback49
*Mar 1 00:44:26.411: RIP: ignored v2 packet from 192.168.49.1 (sourced from one of our addresses)
*Mar 1 00:44:27.175: RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.12.1)
*Mar 1 00:44:27.179: RIP: Update contains 7 routes
*Mar 1 00:44:27.183: RIP: Update queued
*Mar 1 00:44:27.183: RIP: Update sent via Serial2/0
*Mar 1 00:44:27.319: RIP: sending v2 update to 224.0.0.9 via Loopback70 (192.168.70.1)
r1#
*Mar 1 00:44:27.323: RIP: Update contains 9 routes
*Mar 1 00:44:27.327: RIP: Update queued
*Mar 1 00:44:27.327: RIP: Update sent via Loopback70
*Mar 1 00:44:27.335: RIP: ignored v2 packet from 192.168.70.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:34.667: RIP: sending v2 update to 224.0.0.9 via Loopback0 (172.16.1.1)
*Mar 1 00:44:34.671: RIP: Update contains 9 routes
*Mar 1 00:44:34.675: RIP: Update queued
*Mar 1 00:44:34.675: RIP: Update sent via Loopback0
*Mar 1 00:44:34.679: RIP: ignored v2 packet from 172.16.1.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:40.635: RIP: sending v2 update to 224.0.0.9 via Loopback50 (192.168.50.1)
*Mar 1 00:44:40.639: RIP: Update contains 9 routes
*Mar 1 00:44:40.643: RIP: Update queued
*Mar 1 00:44:40.643: RIP: Update sent via Loopback50
*Mar 1 00:44:40.651: RIP: ignored v2 packet from 192.168.50.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:46.279: RIP: received v2 update from 172.16.12.2 on Serial2/0
*Mar 1 00:44:46.283: RIP: Update contains 2 routes
*Mar 1 00:44:47.087: RIP: sending v2 update to 224.0.0.9 via Loopback51 (192.168.51.1)
*Mar 1 00:44:47.091: RIP: Update contains 9 routes
*Mar 1 00:44:47.095: RIP: Update queued
*Mar 1 00:44:47.095: RIP: Update sent via Loopback51
*Mar 1 00:44:47.099: RIP: ignored v2 packet from 192.168.51.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:50.135: RIP: sending v2 update to 224.0.0.9 via Loopback48 (192.168.48.1)
*Mar 1 00:44:50.139: RIP: Update contains 9 routes
*Mar 1 00:44:50.143: RIP: Update queued
*Mar 1 00:44:50.143: RIP: Update sent via Loopback48
*Mar 1 00:44:50.151: RIP: ignored v2 packet from 192.168.48.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:54.911: RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.12.1)
*Mar 1 00:44:54.915: RIP: Update contains 7 routes
*Mar 1 00:44:54.919: RIP: Update queued
*Mar 1 00:44:54.919: RIP: Update sent via Serial2/0
*Mar 1 00:44:55.431: RIP: sending v2 update to 224.0.0.9 via Loopback49 (192.168.49.1)
*Mar 1 00:44:55.435: RIP: Update contains 9 routes
*Mar 1 00:44:55.439: RIP: Update queued
*Mar 1 00:44:55.439: RIP: Update sent via Loopback49
*Mar 1 00:44:55.443: RIP: ignored v2 packet from 192.168.49.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:56.467: RIP: sending v2 update to 224.0.0.9 via Loopback70 (192.168.70.1)
*Mar 1 00:44:56.467: RIP: Update contains 9 routes
*Mar 1 00:44:56.467: RIP: Update queued
*Mar 1 00:44:56.467: RIP: Update sent via Loopback70
*Mar 1 00:44:56.467: RIP: ignored v2 packet from 192.168.70.1 (sourced from one of our addresses)
r1#u all
All possible debugging has been turned off
r1#
*Mar 1 00:45:03.159: RIP: sending v2 update to 224.0.0.9 via Loopback0 (172.16.1.1)
*Mar 1 00:45:03.163: RIP: Update contains 9 routes
*Mar 1 00:45:03.167: RIP: Update queued
*Mar 1 00:45:03.167: RIP: Update sent via Loopback0
*Mar 1 00:45:03.175: RIP: ignored v2 packet from 172.16.1.1 (sourced from one of our addresses)
r1#
so as we can see updates are being sent vigorously by rip . do we really need those updates ... we dont ..? so lets shut them ?