From: Shibu Nair (shinair@cisco.com)
Date: Sat Jan 31 2004 - 18:21:19 GMT-3
I turned auto summ off on both R3 and R4.
Still no help.
Here is the debug ip rip information.
Regards
Shibu
R4:
01:50:52: RIP: received v2 update from 192.168.12.195 on Ethernet2/0
01:50:52: 172.17.1.0/24 via 0.0.0.0 in 1 hops
01:50:52: 172.17.2.0/24 via 0.0.0.0 in 1 hops
01:50:52: 172.17.4.0/24 via 0.0.0.0 in 2 hops
01:50:52: 192.168.12.64/27 via 0.0.0.0 in 1 hops
01:50:52: 192.168.200.0/24 via 0.0.0.0 in 2 hops
01:50:58: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (10.33.35.4)
01:50:58: RIP: build update entries
01:50:58: 10.33.48.0/20 via 0.0.0.0, metric 16, tag 0
01:50:58: 172.17.1.0/24 via 0.0.0.0, metric 2, tag 0
01:50:58: 172.17.2.0/24 via 0.0.0.0, metric 2, tag 0
01:50:58: 172.17.4.0/24 via 0.0.0.0, metric 3, tag 0
01:50:58: 192.168.0.0/19 via 0.0.0.0, metric 1, tag 0
01:50:58: 192.168.12.64/27 via 0.0.0.0, metric 2, tag 0
01:50:58: 192.168.200.0/24 via 0.0.0.0, metric 3, tag 0
01:51:19: RIP: received v2 update from 192.168.12.195 on Ethernet2/0
01:51:19: 172.17.1.0/24 via 0.0.0.0 in 1 hops
01:51:19: 172.17.2.0/24 via 0.0.0.0 in 1 hops
01:51:19: 172.17.4.0/24 via 0.0.0.0 in 2 hops
01:51:19: 192.168.12.64/27 via 0.0.0.0 in 1 hops
01:51:19: 192.168.200.0/24 via 0.0.0.0 in 2 hops
01:51:24: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (10.33.35.4)
01:51:24: RIP: build update entries
01:51:24: 10.33.48.0/20 via 0.0.0.0, metric 16, tag 0
01:51:24: 172.17.1.0/24 via 0.0.0.0, metric 2, tag 0
01:51:24: 172.17.2.0/24 via 0.0.0.0, metric 2, tag 0
01:51:24: 172.17.4.0/24 via 0.0.0.0, metric 3, tag 0
01:51:24: 192.168.0.0/19 via 0.0.0.0, metric 1, tag 0
01:51:24: 192.168.12.64/27 via 0.0.0.0, metric 2, tag 0
01:51:24: 192.168.200.0/24 via 0.0.0.0, metric 3, tag 0
R4#
R4#
R3:
R3#
R3#
R3#
01:51:07: RIP: received v1 update from 172.17.2.7 on Serial5/0
01:51:07: 172.17.4.0 in 1 hops
01:51:23: RIP: sending v2 update to 224.0.0.9 via Ethernet2/0 (192.168.12.195)
01:51:23: RIP: build update entries
01:51:23: 172.17.1.0/24 via 0.0.0.0, metric 1, tag 0
01:51:23: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:51:23: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:51:23: 192.168.12.64/27 via 0.0.0.0, metric 1, tag 0
01:51:23: 192.168.200.0/24 via 0.0.0.0, metric 2, tag 0
01:51:23: RIP: sending v2 update to 224.0.0.9 via Serial3/0 (172.17.1.3)
01:51:23: RIP: build update entries
01:51:23: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:51:23: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:51:23: 192.168.12.64/27 via 0.0.0.0, metric 1, tag 0
01:51:23: 192.168.12.192/27 via 0.0.0.0, metric 1, tag 0
01:51:23: 192.168.200.0/24 via 0.0.0.0, metric 2, tag 0
01:51:23: RIP: sending v1 update to 255.255.255.255 via Serial5/0 (172.17.2.3)
01:51:23: RIP: build update entries
01:51:23: subnet 172.17.1.0 metric 1
01:51:23: network 192.168.12.0 metric 1
01:51:23: network 192.168.200.0 metric 2
01:51:23: RIP: sending v2 update to 192.168.12.67 via Ethernet1/0
(192.168.12.65)
01:51:23: RIP: build update entries
01:51:23: 172.17.1.0/24 via 0.0.0.0, metric 1, tag 0
01:51:23: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:51:23: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:51:23: 192.168.12.192/27 via 0.0.0.0, metric 1, tag 0
01:51:27: RIP: ignored v1 packet from 172.17.1.6 (illegal version)
01:51:34: RIP: received v1 update from 172.17.2.7 on Serial5/0
01:51:34: 172.17.4.0 in 1 hops
01:51:50: RIP: sending v2 update to 224.0.0.9 via Ethernet2/0 (192.168.12.195)
01:51:50: RIP: build update entries
01:51:50: 172.17.1.0/24 via 0.0.0.0, metric 1, tag 0
01:51:50: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:51:50: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:51:50: 192.168.12.64/27 via 0.0.0.0, metric 1, tag 0
01:51:50: 192.168.200.0/24 via 0.0.0.0, metric 2, tag 0
01:51:50: RIP: sending v2 update to 224.0.0.9 via Serial3/0 (172.17.1.3)
01:51:50: RIP: build update entries
01:51:50: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:51:50: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:51:50: 192.168.12.64/27 via 0.0.0.0, metric 1, tag 0
01:51:50: 192.168.12.192/27 via 0.0.0.0, metric 1, tag 0
01:51:50: 192.168.200.0/24 via 0.0.0.0, metric 2, tag 0
01:51:50: RIP: sending v1 update to 255.255.255.255 via Serial5/0 (172.17.2.3)
01:51:50: RIP: build update entries
01:51:50: subnet 172.17.1.0 metric 1
01:51:50: network 192.168.12.0 metric 1
01:51:50: network 192.168.200.0 metric 2
01:51:50: RIP: sending v2 update to 192.168.12.67 via Ethernet1/0
(192.168.12.65)
01:51:50: RIP: build update entries
01:51:50: 172.17.1.0/24 via 0.0.0.0, metric 1, tag 0
01:51:50: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:51:50: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:51:50: 192.168.12.192/27 via 0.0.0.0, metric 1, tag 0
01:51:56: RIP: ignored v1 packet from 172.17.1.6 (illegal version)
01:52:02: RIP: received v1 update from 172.17.2.7 on Serial5/0
01:52:02: 172.17.4.0 in 1 hops
01:52:11: RIP: received v2 update from 192.168.12.67 on Ethernet1/0
01:52:11: 192.168.200.0/24 via 0.0.0.0 in 1 hops
01:52:18: RIP: sending v2 update to 224.0.0.9 via Ethernet2/0 (192.168.12.195)
01:52:18: RIP: build update entries
01:52:18: 172.17.1.0/24 via 0.0.0.0, metric 1, tag 0
01:52:18: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:52:18: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:52:18: 192.168.12.64/27 via 0.0.0.0, metric 1, tag 0
01:52:18: 192.168.200.0/24 via 0.0.0.0, metric 2, tag 0
01:52:18: RIP: sending v2 update to 224.0.0.9 via Serial3/0 (172.17.1.3)
01:52:18: RIP: build update entries
01:52:18: 172.17.2.0/24 via 0.0.0.0, metric 1, tag 0
01:52:18: 172.17.4.0/24 via 0.0.0.0, metric 2, tag 0
01:52:18: 192.168.12.64/27 via 0.0.0.0, metric 1, tag 0
01:52:18: 192.168.12.192/27 via 0.0.0.0, metric 1, tag 0
01:52:18: 192.168.200.0/24 via 0.0.0.0, metric 2, tag 0
01:52:18: RIP: sending v1 update to 255.255.255.255 via Serial5/0 (172.17.2.3)
01:52:18: RIP: build update entries
01:52:18: subnet 172.17.1.0 metric 1
01:52:18: network 192.168.12.0 metric 1
01:52:18: network 192.168.200.0 metric 2
01:52:18: RIP: sending v2 update to 192.168.12.67 via Ethernet1/0
(192.168.12.65)
At 03:20 PM 1/31/2004 -0500, Packet Man wrote:
>Shibu,
>
>Without knowing all the details of your set up, I can't be 100% sure of
>what the problem is, however...
>
>You may recall that the default behavior of a Classful routing protocol is
>to automatically summarize routes to their classful length on a boundary
>router. In your topology, R4 is a boundary router between 2 different
>major networks, 10.0.0.0/8 and 192.168.12.196/24.
>
>What I would do is turn on debug ip rip on both routers and see what
>routes are being advertised.
>
>I suspect that if you disable auto summarization, that may resolve the
>problem.
>
>HTH
>
>
>>From: Shibu Nair <shinair@cisco.com>
>>Reply-To: Shibu Nair <shinair@cisco.com>
>>To: <ccielab@groupstudy.com>
>>Subject: RIP v2 routes
>>Date: Sat, 31 Jan 2004 12:03:21 -0800
>>
>>Hi
>>Setup:
>>
>>R3 ------Ethernet----------R4---ethernet
>>
>>R3 and $ are connected using ethernet.
>>R3:
>>interface Ethernet1/0
>> ip address 192.168.12.65 255.255.255.224
>>
>>R4:
>>interface Ethernet2/0
>> ip address 192.168.12.196 255.255.224.0
>>
>>!
>>interface Ethernet0/0
>> ip address 10.33.35.4 255.255.240.0
>>
>>All links are up and RIP v2 is enabled on both routers.
>>Now i am supposed to see 10.33.35.4 /20 on R3 as part of the RIP routes.
>>I do not see that on R3.
>>
>>R4 is getting other routes through R3 ( R3 is connected to other RIP
>>routers).
>>But no way i can see R4 ethernet or loopback network on R3. Strange.
>>Pls advice
>>Regards
>>Shibu
>>
>>
>>R4#sh runn
>>Building configuration...
>>
>>Current configuration : 753 bytes
>>!
>>version 12.2
>>service timestamps debug uptime
>>service timestamps log uptime
>>no service password-encryption
>>!
>>hostname R4
>>!
>>!
>>clock timezone EST -5
>>ip subnet-zero
>>no ip domain-lookup
>>!
>>!
>>!
>>!
>>interface Loopback0
>> ip address 10.33.50.10 255.255.240.0
>>!
>>interface Ethernet0/0
>> ip address 10.33.35.4 255.255.240.0
>> no keepalive
>>!
>>interface Ethernet1/0
>> no ip address
>> shutdown
>>!
>>interface Ethernet2/0
>> ip address 192.168.12.196 255.255.224.0
>>!
>>interface Serial3/0
>> no ip address
>> shutdown
>>!
>>interface Serial4/0
>> no ip address
>> shutdown
>>!
>>interface Serial5/0
>> ip address 10.33.90.4 255.255.240.0
>> shutdown
>>!
>>router rip
>> version 2
>> network 10.0.0.0
>> network 192.168.12.0
>>!
>>ip classless
>>no ip http server
>>!
>>!
>>!
>>line con 0
>>line aux 0
>>line vty 0 4
>> login
>>!
>>end
>>
>>R4: routing table:
>>Gateway of last resort is not set
>>
>> 192.168.12.0/27 is subnetted, 1 subnets
>>R 192.168.12.64 [120/1] via 192.168.12.195, 00:00:10, Ethernet2/0
>>R 172.17.0.0/16 [120/1] via 192.168.12.195, 00:00:10, Ethernet2/0
>>R 192.168.200.0/24 [120/2] via 192.168.12.195, 00:00:10, Ethernet2/0
>> 10.0.0.0/20 is subnetted, 2 subnets
>>C 10.33.32.0 is directly connected, Ethernet0/0
>>C 10.33.48.0 is directly connected, Loopback0
>>C 192.168.0.0/19 is directly connected, Ethernet2/0
>>
>>
>>R3#sh runn
>>Building configuration...
>>
>>Current configuration : 882 bytes
>>!
>>version 12.2
>>service timestamps debug uptime
>>service timestamps log uptime
>>no service password-encryption
>>!
>>hostname R3
>>!
>>!
>>clock timezone EST -5
>>ip subnet-zero
>>!
>>!
>>!
>>!
>>interface Ethernet0/0
>> ip address 192.168.83.3 255.255.255.0
>> shutdown
>>!
>>interface Ethernet1/0
>> ip address 192.168.12.65 255.255.255.224
>>!
>>interface Ethernet2/0
>> ip address 192.168.12.195 255.255.255.224
>>!
>>interface Serial3/0
>> ip address 172.17.1.3 255.255.255.0
>> no fair-queue
>>!
>>interface Serial4/0
>> no ip address
>> shutdown
>>!
>>interface Serial5/0
>> ip address 172.17.2.3 255.255.255.0
>> ip rip send version 1
>> ip rip receive version 1
>>!
>>interface Serial6/0
>> no ip address
>> shutdown
>>!
>>router rip
>> version 2
>> passive-interface Ethernet1/0
>> network 172.17.0.0
>> network 192.168.12.0
>> network 192.168.83.0
>> neighbor 192.168.12.67
>>!
>>ip classless
>>no ip http server
>>!
>>!
>>!
>>line con 0
>>line aux 0
>>line vty 0 4
>> login
>>!
>>end
>>
>>R3 show ip route:
>>
>>Gateway of last resort is not set
>>
>> 192.168.12.0/27 is subnetted, 2 subnets
>>C 192.168.12.64 is directly connected, Ethernet1/0
>>C 192.168.12.192 is directly connected, Ethernet2/0
>> 172.17.0.0/24 is subnetted, 3 subnets
>>R 172.17.4.0 [120/1] via 172.17.2.7, 00:00:29, Serial5/0
>>C 172.17.1.0 is directly connected, Serial3/0
>>C 172.17.2.0 is directly connected, Serial5/0
>>R 192.168.200.0/24 [120/1] via 192.168.12.67, 00:00:47, Ethernet1/0
>>
>>_______________________________________________________________________
>>Please help support GroupStudy by purchasing your study materials from:
>>http://shop.groupstudy.com
>>
>>Subscription information may be found at:
>>http://www.groupstudy.com/list/CCIELab.html
>
>_________________________________________________________________
>Check out the new MSN 9 Dial-up fast & reliable Internet access with prime
>features! http://join.msn.com/?pgmarket=en-us&page=dialup/home&ST=1
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:52 GMT-3