From: Janto Cin (jantocin@datacomm.co.id)
Date: Mon Jan 06 2003 - 04:32:49 GMT-3
Hi Carlos,
I tried to reload many times and R7 always did the same thing (first
from RIP, then prefer BGP, then delete the route).
Thanks for everyone replies.
Janto
-----Original Message-----
From: Carlos [mailto:cchorao@xtra.co.nz]
Sent: Sunday, January 05, 2003 6:04 PM
To: Janto Cin; ccielab@groupstudy.com
Subject: Re: BGP and RIP route
Janto ,
Did you get a satifacory explanation for this problem?
By examing the deb on my initial thoughts were as follows ( comments
follow each debug line)
>R 10.0.0.0/8 [80/1] via 192.168.10.2, 00:00:19, Serial0
route added to table via rip admin distance = 80;
Because rip is redistributed into ospf and becuase your acl fileters
out net 11.0.0.0 instead of 10.0.0.0 , this network appears in the
routing table of R5 at this stage.
> 00:04:04: %BGP-5-ADJCHANGE: neighbor 192.168.10.2 Up
>00:04:31: RT: closer admin distance for 10.0.0.0, flushing 1 routes
>00:04:31: RT: add 10.0.0.0/8 via 192.168.10.2, bgp metric [20/0]
the bgp adj comes up and the bgp route supercedes the RIP entry in the
routing table ( lower admin distance). The rip route is withdrawn, and
no longer reidtributed into ospf;
All is well for about 3 minutes when R7 does the folloing
00:07:32: RT: delete route to 10.0.0.0 via 192.168.10.2, rip metric
[20/0]
00:07:32: RT: no routes to 10.0.0.0, entering holddown
Initially I though that this final event was somehow caused by R5 (
timeout of some sort) . However when I reproduce the scenario, I do not
get the results you did ? Strange. Not happy.
Carlos
Telecom New Zealand - Advanced Solutions Group : Network Design and
Security
----- Original Message -----
From: "Janto Cin" <jantocin@datacomm.co.id>
To: <ccielab@groupstudy.com>
Sent: Tuesday, December 31, 2002 6:06 PM
Subject: BGP and RIP route
> Hi All,
>
> Need your help on below problem.
> Thanks in advance.
>
> (s0)R5(e0)-------(e0)R7(s0)--------(s0)R8(e0)
>
> R5 (s0): 150.50.100.5/24
> R5 (e0): 150.50.201.5/24
> R7 (e0): 150.50.201.7/24
> R7 (s0): 192.168.10.1/30
> R8 (s0): 192.168.10.2/30
> R8 (e0): 10.1.100.8/8
>
> R5
> -------
> router ospf 1
> router-id 150.50.5.5
> network 150.50.5.5 0.0.0.0 area 0
> network 150.50.100.0 0.0.0.255 area 1
> network 150.50.201.0 0.0.0.255 area 0
>
> router bgp 65522
> no synchronization
> bgp log-neighbor-changes
> bgp confederation identifier 8888
> bgp confederation peers 65511 65533
> neighbor 150.50.7.7 remote-as 65533
> neighbor 150.50.7.7 ebgp-multihop 255
> neighbor 150.50.7.7 update-source Loopback0
> neighbor 150.50.100.2 remote-as 65522
> no auto-summary
>
> R7
> --------
> router ospf 1
> router-id 150.50.7.7
> redistribute rip metric-type 1 subnets
> network 150.50.7.7 0.0.0.0 area 0
> network 150.50.201.0 0.0.0.255 area 0
> distribute-list 11 out rip
> !
> router rip
> redistribute ospf 1 metric 5
> passive-interface default
> no passive-interface Serial0
> network 192.168.10.0
> distance 80
> no auto-summary
> !
> router bgp 65533
> no synchronization
> bgp log-neighbor-changes
> bgp confederation identifier 8888
> bgp confederation peers 65511 65522
> neighbor 150.50.5.5 remote-as 65522
> neighbor 150.50.5.5 ebgp-multihop 255
> neighbor 150.50.5.5 update-source Loopback0
> neighbor 192.168.10.2 remote-as 800
> no auto-summary
>
> access-list 11 deny 11.0.0.0 0.0.0.255
> access-list 11 permit any
>
> R8
> -------
> router rip
> network 10.0.0.0
> network 11.0.0.0
> network 150.50.0.0
> network 192.168.10.0
> distance 80
> no auto-summary
> !
> router bgp 800
> no synchronization
> bgp log-neighbor-changes
> network 10.0.0.0
> neighbor 192.168.10.1 remote-as 8888
> neighbor 192.168.10.1 filter-list 1 in
> no auto-summary
>
> ip as-path access-list 1 deny _1000_
> ip as-path access-list 1 permit .*]
>
> Problem
> -------------
> I reload all router then turn on 'debug ip routing'.
>
> R7#sh ip ro
> R 10.0.0.0/8 [80/1] via 192.168.10.2, 00:00:19, Serial0
>
> 00:04:04: %BGP-5-ADJCHANGE: neighbor 192.168.10.2 Up
>
> R7#
> 00:04:31: RT: closer admin distance for 10.0.0.0, flushing 1 routes
> 00:04:31: RT: add 10.0.0.0/8 via 192.168.10.2, bgp metric [20/0]
>
> R7#sh ip ro
> B 10.0.0.0/8 [20/0] via 192.168.10.2, 00:00:12
>
> R7#
> 00:07:32: RT: delete route to 10.0.0.0 via 192.168.10.2, rip metric
> [20/0]
> 00:07:32: RT: no routes to 10.0.0.0, entering holddown
>
> R7#sh ip ro
> B 10.0.0.0/8 is possibly down, routing via 192.168.10.2
>
> R7#sh ip ro 10.0.0.0
> Routing entry for 10.0.0.0/8
> Known via "bgp 65533", distance 20, metric 4294967295 (inaccessible)
> Tag 800, type external
> Last update from 192.168.10.2 00:05:34 ago
> Hold down timer expires in 30 secs
>
> Why route 10.0.0.0/8 entering hold down?
> How to solve this problem?
> Thank you.
>
> Kind Regards,
> Janto
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:42 GMT-3