RE: RIP v2 auto-summary

From: Athaide, Dwayne (DAthaide@eprod.com)
Date: Fri Dec 28 2007 - 23:33:25 ART


Hi
I did notice that that the update when auto-summary is disabled is the
/32 or the 192.168.2.2 address

The is with auto-summary turned on on both ends

R2
*Dec 28 21:23:44.885: RIP: sending v2 update to 224.0.0.9 via
Serial0/1/0.24 (172.29.24.2)
*Dec 28 21:23:44.885: RIP: build update entries
*Dec 28 21:23:44.885: 192.168.2.0/24 via 0.0.0.0, metric 2, tag 0
*Dec 28 21:24:03.869: RIP: received v2 update from 172.29.24.4 on
Serial0/1/0.24
*Dec 28 21:24:03.869: 172.29.24.0/24 via 0.0.0.0 in 1 hops
*Dec 28 21:24:03.869: 172.29.40.0/24 via 0.0.0.0 in 1 hops
*Dec 28 21:24:03.869: 192.168.2.0/24 via 0.0.0.0 in 3 hops
*Dec 28 21:24:03.869: 192.168.4.0/24 via 0.0.0.0 in 1 hops

R4
RIP protocol debugging is on
R4#
*Dec 28 21:26:04.249: RIP: sending v2 update to 224.0.0.9 via
Serial0/0/0 (172.29.24.4)
*Dec 28 21:26:04.249: RIP: build update entries
*Dec 28 21:26:04.249: 172.29.24.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 28 21:26:04.249: 172.29.40.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 28 21:26:04.249: 192.168.2.0/24 via 0.0.0.0, metric 3, tag 0
*Dec 28 21:26:04.249: 192.168.4.0/24 via 0.0.0.0, metric 1, tag 0
R4#
*Dec 28 21:26:20.725: RIP: received v2 update from 172.29.24.2 on
Serial0/0/0
*Dec 28 21:26:20.725: 192.168.2.0/24 via 0.0.0.0 in 2 hops
R4#

WITH NO-AUTOSUMMARY
*Dec 28 21:28:17.021: RIP: sending v2 update to 224.0.0.9 via
Serial0/1/0.24 (172.29.24.2)
*Dec 28 21:28:17.021: RIP: build update entries
*Dec 28 21:28:17.021: 192.168.2.2/32 via 0.0.0.0, metric 2, tag 100
*Dec 28 21:28:28.141: RIP: received v2 update from 172.29.24.4 on
Serial0/1/0.24
*Dec 28 21:28:28.141: 172.29.24.0/24 via 0.0.0.0 in 1 hops
*Dec 28 21:28:28.141: 172.29.40.0/24 via 0.0.0.0 in 1 hops
*Dec 28 21:28:28.141: 192.168.4.4/32 via 0.0.0.0 in 1 hops
*Dec 28 21:28:44.913: RIP: sending v2 update to 224.0.0.9 via
Serial0/1/0.24 (172.29.24.2)
*Dec 28 21:28:44.913: RIP: build update entries
*Dec 28 21:28:44.913: 192.168.2.2/32 via 0.0.0.0, metric 2, tag 100
*Dec 28 21:28:55.241: RIP: received v2 update from 172.29.24.4 on
Serial0/1/0.24
*Dec 28 21:28:55.241: 172.29.24.0/24 via 0.0.0.0 in 1 hops
*Dec 28 21:28:55.241: 172.29.40.0/24 via 0.0.0.0 in 1 hops
*Dec 28 21:28:55.241: 192.168.4.4/32 via 0.0.0.0 in 1 hops

R4
*Dec 28 21:31:46.677: RIP: received v2 update from 172.29.24.2 on
Serial0/0/0
*Dec 28 21:31:46.681: 192.168.2.2/32 via 0.0.0.0 in 2 hops
R4#sho ip
*Dec 28 21:31:54.657: RIP: sending v2 update to 224.0.0.9 via
Serial0/0/0 (172.29.24.4)
*Dec 28 21:31:54.657: RIP: build update entries
*Dec 28 21:31:54.657: 172.29.24.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 28 21:31:54.657: 172.29.40.0/24 via 0.0.0.0, metric 1, tag 0
*Dec 28 21:31:54.657: 192.168.2.2/32 via 172.29.24.2, metric 3, tag
100
*Dec 28 21:31:54.657: 192.168.4.4/32 via 0.0.0.0, metric 1, tag 0

From: Scott Morris [mailto:smorris@ipexpert.com]
Sent: Friday, December 28, 2007 6:46 PM
To: Athaide, Dwayne; 'groupstudy'
Subject: RE: RIP v2 auto-summary

When you did a "debug ip rip" what advertisement(s) did you see with
either
of those two configurations?

Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
JNCIE-M
#153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor

A Cisco Learning Partner - We Accept Learning Credits!

smorris@ipexpert.com

 

Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com

 

 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Athaide, Dwayne
Sent: Friday, December 28, 2007 3:45 PM
To: groupstudy
Subject: RIP v2 auto-summary

When I enable no-auto-summary under rip version 2 and do a show ip rip
database. Why is there an entry of 172.29.0.0/16 being summarized.

How does the no-auto and auto work for Rip Version 2. The database and
route table look the same for either command

Thanks

NO-AUTOSUMMARY

R2#sho ip rip database

172.29.0.0/16 auto-summary

172.29.12.0/26 directly connected, FastEthernet0/0

172.29.24.0/24 directly connected, Serial0/1/0.24

172.29.25.0/24 directly connected, Serial0/2/0

172.29.25.5/32 directly connected, Serial0/2/0

172.29.40.0/24

    [1] via 172.29.24.4, 00:00:25, Serial0/1/0.24

172.29.100.0/29 directly connected, Serial0/1/0.256

192.168.4.0/24 auto-summary

192.168.4.0/24

    [1] via 172.29.24.4, 00:00:25, Serial0/1/0.24

R2#sho ip route rip

     172.29.0.0/16 is variably subnetted, 7 subnets, 5 masks

R 172.29.40.0/24 [105/1] via 172.29.24.4, 00:00:19, Serial0/1/0.24

     192.168.4.0/32 is subnetted, 1 subnets

R 192.168.4.4 [105/1] via 172.29.24.4, 00:00:19, Serial0/1/0.24

R2#

AUTOSUMMARY

R2#sho ip rip database

172.29.0.0/16 auto-summary

172.29.12.0/26 directly connected, FastEthernet0/0

172.29.24.0/24 directly connected, Serial0/1/0.24

172.29.25.0/24 directly connected, Serial0/2/0

172.29.25.5/32 directly connected, Serial0/2/0

172.29.40.0/24

    [1] via 172.29.24.4, 00:00:00, Serial0/1/0.24

172.29.100.0/29 directly connected, Serial0/1/0.256

192.168.4.0/24 auto-summary

192.168.4.0/24

    [1] via 172.29.24.4, 00:00:00, Serial0/1/0.24

R2#

R2#sho ip route rip

     172.29.0.0/16 is variably subnetted, 7 subnets, 5 masks

R 172.29.40.0/24 [105/1] via 172.29.24.4, 00:00:16, Serial0/1/0.24

R 1



This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:32 ARST