From: Howard C. Berkowitz (hcb@gettcomm.com)
Date: Fri Jan 03 2003 - 14:46:30 GMT-3
At 11:51 AM -0500 1/3/03, Jay Greenberg wrote:
>It looks like RIP is auto-summarizing 160.100.1.0/24 at the Class B
>boundary. 133.10.2.0/24 may not be summarized because of how it is
>assigned to any of the interfaces on that router. 192.190.102.0 would
>be summarized at the Class-C boundary anyway.
It might be informative to substitute IGRP for RIPv1. If the problem
continues, it pretty well proves it's an auto-summarization rather
than a RIP-specific problem.
>
>On Fri, 2003-01-03 at 06:28, Sage Vadi wrote:
>> Hi all,
>>
>> I have a seeming conundrum.
>>
>> R1 OSPF routes (redistributed on same router and sent
>> into RIP process) -
>>
>> 1. O E2 160.100.1.0/24
>>
>> 2. O IA 133.10.2.0/24
>>
>> 3. O E2 192.190.102.0/24
>>
>> Redistributed into RIP (debug ip rip) -
>>
>> 1. network 160.100.0.0 metric 2 ***???
>>
>> 2. subnet 133.10.2.0 metric 2
>>
>> 3. network 192.190.102.0 metric 2
>>
>> Q) Why does network 160.100.1.0/24 not get inserted
>> into the RIP process as 160.100.1.0 like points 2. and
>> 3. respectively. RIP version 1.
>>
>> Cheers,
>> Sage
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Everything you'll ever need on one web page
>> from News and Sport to Email and Music Charts
>> http://uk.my.yahoo.com
>> .
>.
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:40 GMT-3