From: Pamela Forsyth (pforsyth@xxxxxxxxx)
Date: Mon Jul 12 1999 - 15:23:46 GMT-3
Bill,
A quirk of policy routing is that it doesn't apply to traffic sourced by
the router. If you had a PC on the ethernet and 10.10.161.2 was your
default gateway, you would probably have the desired result, but because
you're pinging from the router it won't work. To apply
policy to traffic sourced by the router, you need "ip local policy
route-map." Sorry, I didn't read carefully enough the first time.
It isn't clear from your description where 10.10.42.241 or 170.100.42.x
are configured in your lab network, so I really can't address your new
question on static routes and failed pings.
Pamela
On Mon, 12 Jul 1999, Bill Carter wrote:
> Thanks Pam, I caught that after I sent the question out. I applied the map t
o
> the ethernet interface of RouterC. After doing that I still get the same
> result, packets destined for 10.10.42.X (a.a.a.a) go out RouterC s0.
>
> As a test I removed 170.100.42.X from the OSPF configuration. I put a static
> route in routerB. RouterB could ping 10.10.42.241 no problem. A ping from
> routerC to 10.10.42.241 failed???
>
> Pamela Forsyth wrote:
>
> > Bill,
> >
> > I don't see where you have applied the route map in your configuration.
> > The route map is similar to an access list in that it doesn't have any
> > effect until you tell the router how to use it. You will need an "ip
> > policy route-map" statement.
> >
> > Pamela
> >
> > On Mon, 12 Jul 1999, Bill Carter wrote:
> >
> > > I am trying to set up route maps. Here is the scenario. 2 routers on
> > > the same ethernet segment (x.x.x.1 and x.x.x.2). Both routers have a
> > > frame connection to the 3rd router. Ospf is running between all routers
> > > and the 3 serial port are meshed
> > >
> > >
> > > |---10.10.161.1-RouterB-y.y.y.2---------------------------------
> > > |
> > > |
> > > y.y.y.1-RouterA---------|-a.a.a.1
> > > |---10.10.161.2-RouterC-y.y.y.3-----------------------------------
> > > |
> > >
> > > I want a packet that is sourced from 10.10.1612 and dest for a.a.a.1 to
> > > travel from RC to RB to RA
> > >
> > >
> > > Here is the RouterC config
> > >
> > > access-list 101 permit ip any 10.10.42.0 0.0.0.255
> > > access-list 101 deny ip any any
> > >
> > > route-map sleepy permit 10
> > > match ip address 101
> > > set ip next-hop 10.10.161.1
> > >
> > > An extended trace from RC ethernet port show the packet next hop is
> > > y.y.y.1 thu the packet did not got to routerB
> > >
> > > Will the route maps over rule the routing protocol?
> > >
> > > Is the route map configured correctly?
> > > !
> > >
> > >
> > >
> > > --
> > > ~~~~~~~~~~~~~~~~~~~~~~~~
> > > Bill Carter
> > > Senior Network Analyst
> > > Sentinel Technologies
> > > http://www.sentinel.com
> > > pg 800-612-6810
> > > wk 217-557-5011
> > > of 217-698-9200
> > >
> > > Favorite Quote
> > > "bodega stuck again... "
> > > -Cisco Bug CSCdk37204
> > > ~~~~~~~~~~~~~~~~~~~~~~~~
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:42 GMT-3