RE: BGP and RIP route

From: ying c (bf5tgh1@yahoo.com)
Date: Thu Jan 02 2003 - 10:36:10 GMT-3


Hi,

Just took a quick look on your config. It looks like
you might accidentally deny 11.0.0.0/8 instead of
10.0.0.0/8 in R7. I think Tim's comment is for R8.

Chang
--- Janto Cin <jantocin@datacomm.co.id> wrote:
> Tim,
>
> I've tried with RIPv2 and it didn't work also.
> Any idea? Bgp backdoor or anything else?
> TIA.
>
> Janto
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> Ouellette, Tim
> Sent: Tuesday, December 31, 2002 5:58 PM
> To: 'Janto Cin'
> Cc: 'ccielab@groupstudy.com'
> Subject: RE: BGP and RIP route
>
>
> The problem is that R8 is advertising the 10.0.0.0/8
> with an AD of 80
> (due to you changing the AD of RIP) and it's being
> autosummarized to
> that because your running RIPv1 and advertisng a
> different classfull
> network over the 192.168.10.0/30 network. Also, your
> "no auto-summary"
> won't do too much for you with RIPv1.
>
> Your then advertising the 10.0.0.0/8 via BGP due to
> your "network
> 10.0.0.0" statement in BGP. BGP has an AD of 20,
> your RIP has a AD of
> 80 and therefor they're fighting for position in
> your routing table and
> therefor stepping on eachother (so to speak)
>
> Tim
>
> -----Original Message-----
> From: Janto Cin [mailto:jantocin@datacomm.co.id]
> Sent: Tuesday, December 31, 2002 12:06 AM
> To: ccielab@groupstudy.com
> 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:39 GMT-3