From: Volkov, Dmitry (IDS Canada) (dmitry_volkov@ca.ml.com)
Date: Fri Jul 18 2003 - 14:28:28 GMT-3
Mustafa,
The problem disappeared when I added "default-metric 2" under "router rip"
on R1
ibgp--(170.70.200.1)R1(170.70.10.1)---rip---(.16)R16 (IOS 12.1.5 T14)
See debug outputs below:
R1#
router rip
version 2
passive-interface Serial0/0
network 170.70.0.0
default-information originate
no auto-summary
!
router bgp 543
no synchronization
bgp log-neighbor-changes
neighbor 66.2.2.2 remote-as 543
neighbor 66.2.2.2 update-source Loopback0
neighbor 66.2.2.2 route-reflector-client
neighbor 66.3.3.3 remote-as 543
neighbor 66.3.3.3 shutdown
neighbor 66.3.3.3 update-source Loopback0
neighbor 66.3.3.3 route-reflector-client
r1#deb ip rou
IP routing debugging is on
r1#deb ip rip events
RIP event debugging is on
r1#deb ip rip database
RIP database events debugging is on
r1#deb ip rip
RIP protocol debugging is on
r1#
00:35:38: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (170.70.10.1)
00:35:38: RIP: build update entries
00:35:38: 0.0.0.0/0 via 0.0.0.0, metric 16, tag 0 <-------------
!!!!!!!!!!!!!!!!!!!
00:35:38: 10.1.4.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 66.1.1.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 66.2.2.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 66.3.3.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 66.4.4.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 170.70.20.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 170.70.23.0/30 via 0.0.0.0, metric 2, tag 0
00:35:38: 170.70.30.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 170.70.35.0/24 via 0.0.0.0, metric 2, tag 0
00:35:38: 170.70.200.0/24 via 0.0.0.0, metric 1, tag 0
00:35:38: RIP: Update contains 11 routes
00:35:38: RIP: Update queued
00:35:38: RIP: Update sent via Ethernet0/0
r16#deb ip rip
RIP protocol debugging is on
r16#
00:39:06: RIP: received packet with MD5 authentication
00:39:06: RIP: received v2 update from 170.70.10.1 on Ethernet0
00:39:06: 0.0.0.0/0 via 0.0.0.0 in 16 hops (inaccessible)
<------------- !!!!!!!!!!!!!!!!!!!
00:39:06: 10.1.4.0/24 via 0.0.0.0 in 2 hops
00:39:06: 66.1.1.0/24 via 0.0.0.0 in 2 hops
00:39:06: 66.2.2.0/24 via 0.0.0.0 in 2 hops
00:39:06: 66.3.3.0/24 via 0.0.0.0 in 2 hops
00:39:06: 66.4.4.0/24 via 0.0.0.0 in 2 hops
00:39:06: 170.70.20.0/24 via 0.0.0.0 in 2 hops
00:39:06: 170.70.23.0/30 via 0.0.0.0 in 2 hops
00:39:06: 170.70.30.0/24 via 0.0.0.0 in 2 hops
00:39:06: 170.70.35.0/24 via 0.0.0.0 in 2 hops
00:39:06: 170.70.200.0/24 via 0.0.0.0 in 1 hops
r16#
00:39:09: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (170.70.10.16)
00:39:09: RIP: build update entries - suppressing null update
===========================================================
BGP Shutdown:
r1(config)#router bgp 543
r1(config-router)#neighbor 66.3.3.3 shu
r1(config-router)#^Z
r1#
00:43:23: %BGP-5-ADJCHANGE: neighbor 66.3.3.3 Down Admin. shutdown
00:43:23: RT: del 0.0.0.0 via 170.70.200.4, bgp metric [200/0]
00:43:23: RT: delete network route to 0.0.0.0
00:43:23: %SYS-5-CONFIG_I: Configured from console by console
00:43:33: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (170.70.10.1)
00:43:33: RIP: build update entries
00:43:33: 0.0.0.0/0 via 0.0.0.0, metric 1, tag 0 <-------------
!!!!!!!!!!!!!!!!!!!
00:43:33: 10.1.4.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 66.1.1.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 66.2.2.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 66.3.3.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 66.4.4.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 170.70.20.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 170.70.23.0/30 via 0.0.0.0, metric 2, tag 0
00:43:33: 170.70.30.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 170.70.35.0/24 via 0.0.0.0, metric 2, tag 0
00:43:33: 170.70.200.0/24 via 0.0.0.0, metric 1, tag 0
00:43:33: RIP: Update contains 11 routes
00:43:33: RIP: Update queued
00:43:33: RIP: Update sent via Ethernet0/0
r16#
00:46:37: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (170.70.10.16)
00:46:37: RIP: build update entries - suppressing null update
r16#
00:46:38: RIP: received packet with MD5 authentication
00:46:38: RIP: received v2 update from 170.70.10.1 on Ethernet0
00:46:38: 0.0.0.0/0 via 0.0.0.0 in 1 hops <-------------
!!!!!!!!!!!!!!!!!!!
00:46:38: 10.1.4.0/24 via 0.0.0.0 in 2 hops
00:46:38: 66.1.1.0/24 via 0.0.0.0 in 2 hops
00:46:38: 66.2.2.0/24 via 0.0.0.0 in 2 hops
00:46:38: 66.3.3.0/24 via 0.0.0.0 in 2 hops
00:46:38: 66.4.4.0/24 via 0.0.0.0 in 2 hops
00:46:38: 170.70.20.0/24 via 0.0.0.0 in 2 hops
00:46:39: 170.70.23.0/30 via 0.0.0.0 in 2 hops
00:46:39: 170.70.30.0/24 via 0.0.0.0 in 2 hops
00:46:39: 170.70.35.0/24 via 0.0.0.0 in 2 hops
00:46:39: 170.70.200.0/24 via 0.0.0.0 in 1 hops
===========================================
add "default-metric 2" on R1
r1(config)#router rip
r1(config-router)#default-metric 2
r1(config-router)#
00:56:24: RIP-DB: Scan IP routing table and redistribute
00:56:24: RIP-DB: redist 170.70.200.0/24(metric 0, last interface Serial0/0)
to RIP
00:56:24: RIP-DB: Get redist for network 170.70.200.0
00:56:24: RIP-DB: adding 170.70.200.0/24 (metric 0) via 0.0.0.0 on Serial0/0
to RIP database
00:56:24: RIP-DB: redist 170.70.35.0/24(metric 75, last interface Serial0/0)
to RIP
00:56:24: RIP-DB: Get redist for network 170.70.35.0
00:56:24: RIP-DB: adding 170.70.35.0/24 (metric 2) via 66.3.3.3 on Serial0/0
to RIP database
00:56:24: RIP-DB: redist 170.70.10.0/24(metric 0, last interface
Ethernet0/0) to RIP
00:56:24: RIP-DB: Get redist for network 170.70.10.0
00:56:24: RIP-DB: adding 170.70.10.0/24 (metric 0) via 0.0.0.0 on
Ethernet0/0 to RIP database
00:56:24: RIP-DB: redist 170.70.30.0/24(metric 74, last interface Serial0/0)
to RIP
00:56:24: RIP-DB: Get redist for network 170.70.30.0
00:56:24: RIP-DB: adding 170.70.30.0/24 (metric 2) via 66.3.3.3 on Serial0/0
to RIP database
00:56:24: RIP-DB: re^Z
r1#dist 170.70.20.0/24(metric 74, last interface Serial0/0) to RIP
00:56:24: RIP-DB: Get redist for network 170.70.20.0
00:56:24: RIP-DB: adding 170.70.20.0/24 (metric 2) via 66.2.2.2 on Serial0/0
to RIP database
00:56:24: RIP-DB: redist 170.70.23.0/30(metric 1626, last interface
Serial0/0) to RIP
00:56:24: RIP-DB: Get redist for network 170.70.23.0
00:56:24: RIP-DB: adding 170.70.23.0/30 (metric 2) via 66.3.3.3 on Serial0/0
to RIP database
00:56:24: RIP-DB: adding 170.70.23.0/30 (metric 2) via 66.2.2.2 on Serial0/0
to RIP database
00:56:24: RIP-DB: redist 66.4.4.0/24(metric 65, last interface Serial0/0) to
RIP
00:56:24: RIP-DB: Get redist for network 66.4.4.0
00:56:24: RIP-DB: adding 66.4.4.0/24 (metric 2) via 66.4.4.4 on Serial0/0 to
RIP database
00:56:24: RIP-DB: redist 66.3.3.0/24(metric 65, last interface Serial0/0) to
RIP
00:56:24: RIP-DB: Get redist for network 66.3.3.0
00:56:24: RIP-DB: adding 66.3.3.0/24 (metric 2) via 66.3.3.3 on Serial0/0 to
RIP database
00:56:24: RIP-DB: redist 66.2.2.0/24(metric 65, last interface Serial0/0) to
RIP
00:56:24: RIP-DB: Get redist for network 66.2.2.0
00:56:24: RIP-DB: adding 66.2.2.0/24 (metric 2) via 66.2.2.2 on Serial0/0 to
RIP database
00:56:24: RIP-DB: redist 66.1.1.0/24(metric 0, last interface Loopback0) to
RIP
00:56:24: RIP-DB: Get redist for network 66.1.1.0
00:56:24: RIP-DB: adding 66.1.1.0/24 (metric 1) via 0.0.0.0 on Loopback0 to
RIP database
00:56:24: RIP-DB: redist 10.1.4.0/24(metric 10, last interface Serial0/0) to
RIP
00:56:24: RIP-DB: Get redist for network 10.1.4.0
00:56:24: RIP-DB: adding 10.1.4.0/24 (metric 2) via 66.4.4.4 on Serial0/0 to
RIP database
00:56:25: %SYS-5-CONFIG_I: Configured from console by console
00:56:33: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (170.70.10.1)
00:56:33: RIP: build update entries
00:56:33: 0.0.0.0/0 via 0.0.0.0, metric 2, tag 0 <-------------
!!!!!!!!!!!!!!!!!!!
00:56:33: 10.1.4.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 66.1.1.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 66.2.2.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 66.3.3.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 66.4.4.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 170.70.20.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 170.70.23.0/30 via 0.0.0.0, metric 2, tag 0
00:56:33: 170.70.30.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 170.70.35.0/24 via 0.0.0.0, metric 2, tag 0
00:56:33: 170.70.200.0/24 via 0.0.0.0, metric 1, tag 0
00:56:33: RIP: Update contains 11 routes
00:56:33: RIP: Update queued
00:56:33: RIP: Update sent via Ethernet0/0
> -----Original Message-----
> From: Mustafa Bayramov (ICT/IT) [mailto:mustafa@azercell.com]
> Sent: Monday, July 14, 2003 7:41 AM
> To: Volkov, Dmitry (IDS Canada); 'ccielab@groupstudy.com'
> Subject: RE: rip, bgp & default
>
>
> Dmitry
>
> Do debug ip routing on R1 and R6
> Also debug ip rip on R1.
>
> Then shutdown BGP neighbor to R16.
> Past debug output here.
>
>
> Regards
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> Behalf Of
> Volkov, Dmitry (IDS Canada)
> Sent: Sunday, July 13, 2003 5:51 PM
> To: 'ccielab@groupstudy.com'
> Subject: rip, bgp & default
>
> http://www.cisco.com/en/US/tech/tk365/tk554/technologies_tech_
> note09186a0080
> 094374.shtml
> <http://www.cisco.com/en/US/tech/tk365/tk554/technologies_tech
> _note09186a008
> 0094374.shtml>
> Note: In IOS release 12.0T and later, RIP does not advertise
> the default
> router if the route is not learned via RIP. Therefore, it may
> be necessary
> to redistribute the route into RIP, or use the
> default-information originate
> command.
>
> ibgp--(170.70.200.1)R1(170.70.10.1)---rip---(.16)R16 (IOS
> 12.1.5 T14)
>
>
> 1) R1 gets default via IBGP; R1 doesn't redistr BGP to RIP but has
> default-information originate command.
> R1 doesn't advertise 0.0.0.0 network to R16
>
> r1#
> Network Next Hop Metric LocPrf Weight Path
> *>i0.0.0.0 170.70.200.4 0 100 0 444 ?
> r1#sh ip ro 0.0.0.0
> Routing entry for 0.0.0.0/0, supernet
> Known via "bgp 543", distance 200, metric 0, candidate default path
> Tag 444, type internal
> Last update from 170.70.200.4 00:00:00 ago
> Routing Descriptor Blocks:
> * 170.70.200.4, from 66.3.3.3, 00:00:00 ago
> Route metric is 0, traffic share count is 1
> AS Hops 1
>
> r16#sh ip ro 0.0.0.0
> % Network not in table
>
> 2) R1 does BGP redistr to RIP - default goes to R16
>
> r16#sh ip ro 0.0.0.0
> Routing entry for 0.0.0.0/0, supernet
> Known via "rip", distance 120, metric 2, candidate default path
> Redistributing via rip
> Last update from 170.70.10.1 on Ethernet0, 00:00:00 ago
> Routing Descriptor Blocks:
> * 170.70.10.1, from 170.70.10.1, 00:00:00 ago, via Ethernet0
> Route metric is 2, traffic share count is 1
>
> 3) Shut BGP neighbor - default goes to R16 !!!
>
> r1(config)#router bgp 543
> r1(config-router)#neighbor 66.3.3.3 shu
>
> r16#sh ip ro 0.0.0.0
> Routing entry for 0.0.0.0/0, supernet
> Known via "rip", distance 120, metric 1, candidate default path
> Redistributing via rip
> Last update from 170.70.10.1 on Ethernet0, 00:00:00 ago
> Routing Descriptor Blocks:
> * 170.70.10.1, from 170.70.10.1, 00:00:00 ago, via Ethernet0
> Route metric is 1, traffic share count is 1
>
> Any explanations ??
>
>
> ______________________________________________________________
> _________
> You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:44 GMT-3