From: Kim (support@isolvesystems.com)
Date: Thu May 03 2007 - 11:09:31 ART
Thanks Ivan. It works now after using your recommendation. It's weird...
On 5/3/07, ivan <ivan@iip.net> wrote:
>
> I remember such issue.
> Try to replace match int to match ip address under route-map
> configuration.
>
> On Thursday 03 May 2007 07:09, Kim wrote:
> > Here's the config. Please note that I removed the route-map and it's
> still
> > not working. It worked when I put the default info originate command on
> > another rip router....
> >
> > router rip
> > version 2
> > redistribute eigrp 10 metric 2
> > network 128.1.0.0
> > network 150.1.0.0
> > default-information originate route-map SW2-ONLY
> > no auto-summary
> >
> > route-map SW2-ONLY permit 10
> > match interface Ethernet0/1
> >
> > On 5/2/07, Gavin Lawson <GavinL@titan.net.au> wrote:
> > > Hi Kim
> > >
> > > Can you send your config and "sh ip route"
> > >
> > > GL
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > > Kim
> > > Sent: Thursday, 3 May 2007 10:47 AM
> > > To: WorkerBee; ccielab@groupstudy.com
> > > Subject: Re: RIP - Default Information Originate
> > >
> > > By the way, I added a static default route to the router with default
> > > information originate, it's not working....
> > >
> > > On 5/2/07, Kim <support@isolvesystems.com> wrote:
> > > > Below is the Router that's supposed to received the Default
> Route. I
> > > > did the debug ip rip, but I didn't see anything wrong, do you?
> > > >
> > > > Rack1SW2#debug ip rip
> > > > RIP protocol debugging is on
> > > > Rack1SW2#
> > > > *Mar 1 00:07: 06.539: RIP: sending v2 update to 224.0.0.9 via
> Vlan48
> > > > (
> > > > 128.1.48.8)
> > > > *Mar 1 00:07:06.543: RIP: build update entries - suppressing null
> > > > update Rack1SW2# *Mar 1 00:07:19.659: RIP: received v2 update from
> > > > 128.1.48.4 on Vlan48
> > > > *Mar 1 00:07:19.659: 51.51.51.51/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.663: 128.1.5.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.667: 128.1.10.0/24 via 0.0.0.0 in 4 hops
> > > > *Mar 1 00:07:19.671: 128.1.14.0/24 via 0.0.0.0 in 1 hops
> > > > *Mar 1 00:07:19.671: 128.1.27.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.675: 128.1.45.0/24 via 0.0.0.0 in 1 hops
> > > > *Mar 1 00:07:19.683 : 128.1.59.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.687: 128.1.63.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.687: 128.1.72.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.695: 128.1.109.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.699: 128.1.125.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.703: 128.1.125.1/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.707: 128.1.125.2/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.711 : 128.1.125.5/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.715:
> > > > Rack1SW2# 128.1.136.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.723: 150.1.1.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.723: 150.1.1.1/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.727: 150.1.2.2/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.735: 150.1.3.3/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.739: 150.1.4.0/24 via 0.0.0.0 in 1 hops
> > > > *Mar 1 00:07:19.739: 150.1.5.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.747: 150.1.5.5/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:19.751: 150.1.6.6/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.755: 150.1.7.7/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.759: 150.1.9.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:19.763: RIP: received v2 update from 128.1.48.4 on
> > >
> > > Vlan48
> > >
> > > > *Mar 1 00:07:19.767: 150.1.10.0/24 via 0.0.0.0 in 4 hops
> > > > *Mar 1 00:07:19.771: 192.10.1.0/24 via 0.0.0.0 in 3 hops
> > > > Rack1SW2#
> > > > *Mar 1 00:07:33.055: RIP: sending v2 update to 224.0.0.9 via Vlan48
> (
> > > > 128.1.48.8)
> > > > *Mar 1 00:07: 33.059: RIP: build update entries - suppressing null
> > > > update Rack1SW2# *Mar 1 00:07:46.819: RIP: received v2 update from
> > > > 128.1.48.4 on Vlan48
> > > > *Mar 1 00:07:46.823: 51.51.51.51/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.823: 128.1.5.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.827 : 128.1.10.0/24 via 0.0.0.0 in 4 hops
> > > > *Mar 1 00:07:46.831: 128.1.14.0/24 via 0.0.0.0 in 1 hops
> > > > *Mar 1 00:07:46.835: 128.1.27.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.835: 128.1.45.0/24 via 0.0.0.0 in 1 hops
> > > > *Mar 1 00:07:46.839: 128.1.59.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.843: 128.1.63.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.847: 128.1.72.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.847 : 128.1.109.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.851: 128.1.125.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.855: 128.1.125.1/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.859: 128.1.125.2/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.859: 128.1.125.5/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.863:
> > > > Rack1SW2# 128.1.136.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.867: 150.1.1.0/24 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.871: 150.1.1.1/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.871: 150.1.2.2/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.875: 150.1.3.3/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.879: 150.1.4.0/24 via 0.0.0.0 in 1 hops
> > > > *Mar 1 00:07:46.883: 150.1.5.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.887: 150.1.5.5/32 via 0.0.0.0 in 2 hops
> > > > *Mar 1 00:07:46.891: 150.1.6.6/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.895: 150.1.7.7/32 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.895: 150.1.9.0/24 via 0.0.0.0 in 3 hops
> > > > *Mar 1 00:07:46.895: RIP: received v2 update from 128.1.48.4 on
> > >
> > > Vlan48
> > >
> > > > *Mar 1 00:07:46.895: 150.1.10.0/24 via 0.0.0.0 in 4 hops
> > > > *Mar 1 00:07:46.895: 192.10.1.0/24 via 0.0.0.0 in 3 hops
> > > > Rack1SW2#u all
> > > > Port Statistics for unclassified packets is not turned on.
> > > >
> > > > All possible debugging has been turned off Rack1SW2#
> > > >
> > > > On 5/2/07, WorkerBee <ciscobee@gmail.com> wrote:
> > > > > do a debug ip rip and check for rip update, make sure no ACL is
> > > > > blocking.
> > > > >
> > > > > last resort, reload your router with the default-information
> > > > > originate command.
> > > > >
> > > > > On 5/3/07, Kim <support@isolvesystems.com> wrote:
> > > > > > Hello All,
> > > > > > Any idea why other RIP enabled routers are not receiving default
> > > > > > route
> > > > >
> > > > > from
> > > > >
> > > > > > a RIP router that has Default Information Originate configured?
> > > > > >
> > > > > > Thanks.
> > > > > > Kim
> > > > >
> > > > >
> ____________________________________________________________________
> > > > > ___
> > > > >
> > > > > > Subscription information may be found at:
> > > > > > http://www.groupstudy.com/list/CCIELab.html
> > >
> > >
> _______________________________________________________________________
> > > Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> --
> NOC umos.ru
> Ivan Kuchin (495) 137-31-04
This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:20 ART