Friends,
This is a new, clean version of my older post "Frame Relay Cannot Receive Advertisement".
As we had a lot of replies, the chain was hard to deal with.
Three little adjustements were done, some debug data was produced and the question is more clear by now.
I think we can only focus core router.
I have a 3640 Frame-relay serial interface, with 7 point-to-point subinterfaces that is receiving branches advertisements,
regulary, but RIP engine is not taking in account these remote routes. Data from core is advertised and
processed correctly at each branch.
Listing below shows 2 ads from core and, after, branches routes arriving at each subinterface.
Rip data does not show these routes, only data from the 7 linking subnets appear.
I tried to explicit "no ip split-horizon" on that interface, but nothing changes.
Before the frame-relay migration, core router used 7 interafces to link HQ to branches. At this time, RIP v2
was running without any trouble.
I would still appreciate any help. Thanks, Paulo
------------------------debug ip rip listing ------------------------------------------------------------------------------------
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152320: 5w3d: RIP: sending v2 update to 224.0.0.9 via Serial0/0.7 (192.168.109.1)
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152321: 5w3d: RIP: build update entries
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152322: 5w3d: <009>192.168.0.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152323: 5w3d: <009>192.168.1.0/24 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152324: 5w3d: <009>192.168.102.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152325: 5w3d: <009>192.168.103.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152326: 5w3d: <009>192.168.104.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152327: 5w3d: <009>192.168.105.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152328: 5w3d: <009>192.168.107.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152329: 5w3d: <009>192.168.110.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152330: 5w3d: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (192.168.0.1)
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152331: 5w3d: RIP: build update entries
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152332: 5w3d: <009>192.168.1.0/24 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152333: 5w3d: <009>192.168.102.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152334: 5w3d: <009>192.168.103.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:34 Local7.Debug 192.168.1.1 152335: 5w3d: <009>192.168.104.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:38 Local7.Debug 192.168.1.1 152336: 5w3d: <009>192.168.105.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:38 Local7.Debug 192.168.1.1 152337: 5w3d: <009>192.168.107.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:38 Local7.Debug 192.168.1.1 152338: 5w3d: <009>192.168.109.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:38 Local7.Debug 192.168.1.1 152339: 5w3d: <009>192.168.110.0/30 via 0.0.0.0, metric 1, tag 0
2003-11-06 17:20:40 Local7.Debug 192.168.1.1 152340: 5w3d: RIP: received v2 update from 192.168.104.2 on Serial0/0.6
2003-11-06 17:20:40 Local7.Debug 192.168.1.1 152341: 5w3d: 192.168.4.0/24 via 0.0.0.0 in 1 hops
2003-11-06 17:20:44 Local7.Debug 192.168.1.1 152342: 5w3d: RIP: received v2 update from 192.168.110.2 on Serial0/0.3
2003-11-06 17:20:44 Local7.Debug 192.168.1.1 152343: 5w3d: 192.168.10.0/24 via 0.0.0.0 in 1 hops
2003-11-06 17:20:47 Local7.Debug 192.168.1.1 152344: 5w3d: RIP: received v2 update from 192.168.109.2 on Serial0/0.7
2003-11-06 17:20:47 Local7.Debug 192.168.1.1 152345: 5w3d: 192.168.9.0/24 via 0.0.0.0 in 1 hops
2003-11-06 17:20:51 Local7.Debug 192.168.1.1 152346: 5w3d: RIP: received v2 update from 192.168.103.2 on Serial0/0.2
2003-11-06 17:20:51 Local7.Debug 192.168.1.1 152347: 5w3d: 192.168.3.0/24 via 0.0.0.0 in 1 hops
2003-11-06 17:20:54 Local7.Debug 192.168.1.1 152348: 5w3d: RIP: received v2 update from 192.168.107.2 on Serial0/0.4
2003-11-06 17:20:54 Local7.Debug 192.168.1.1 152349: 5w3d: 192.168.7.0/24 via 0.0.0.0 in 1 hops
2003-11-06 17:20:57 Local7.Debug 192.168.1.1 152350: 5w3d: RIP: received v2 update from 192.168.105.2 on Serial0/0.5
2003-11-06 17:20:57 Local7.Debug 192.168.1.1 152351: 5w3d: 192.168.5.0/24 via 0.0.0.0 in 1 hops
2003-11-06 17:21:01 Local7.Debug 192.168.1.1 152352: 5w3d: RIP: received v2 update from 192.168.102.2 on Serial0/0.1
2003-11-06 17:21:01 Local7.Debug 192.168.1.1 152353: 5w3d: 192.168.2.0/24 via 0.0.0.0 in 1 hops
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------CORE DATA sh ip rip data --------------------------------------
CORE-ROT-001#sh ip rip data
192.168.0.0/24 auto-summary
192.168.0.0/30 directly connected, FastEthernet0/1
192.168.1.0/24 auto-summary
192.168.1.0/24 directly connected, FastEthernet0/0
192.168.102.0/24 auto-summary
192.168.102.0/30 directly connected, Serial0/0.1
192.168.103.0/24 auto-summary
192.168.103.0/30 directly connected, Serial0/0.2
192.168.104.0/24 auto-summary
192.168.104.0/30 directly connected, Serial0/0.6
192.168.105.0/24 auto-summary
192.168.105.0/30 directly connected, Serial0/0.5
192.168.107.0/24 auto-summary
192.168.107.0/30 directly connected, Serial0/0.4
192.168.109.0/24 auto-summary
192.168.109.0/30 directly connected, Serial0/0.7
192.168.110.0/24 auto-summary
192.168.110.0/30 directly connected, Serial0/0.3
CORE-ROT-001#
-------------------------------------------------------------------------CORE sh ip protocol ----------------------------------------------
CORE-ROT-001#sh ip protocol
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 20 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is
Incoming update filter list for all interfaces is
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
Serial0/0.1 2 2
Serial0/0.2 2 2
Serial0/0.3 2 2
Serial0/0.4 2 2
Serial0/0.5 2 2
Serial0/0.6 2 2
Serial0/0.7 2 2
FastEthernet0/1 2 2
Automatic network summarization is not in effect
Routing for Networks:
192.168.0.0
192.168.1.0
192.168.102.0
192.168.103.0
192.168.104.0
192.168.105.0
192.168.107.0
192.168.109.0
192.168.110.0
Routing Information Sources:
Gateway Distance Last Update
192.168.107.2 120 00:00:15
192.168.104.2 120 00:00:09
192.168.105.2 120 00:00:26
192.168.110.2 120 00:00:24
192.168.109.2 120 00:00:02
192.168.102.2 120 00:00:08
192.168.103.2 120 00:00:22
Distance: (default is 120)
CORE-ROT-001#
------------------------------------------------------------------------------------------------------------- Paulo
