RE: Confusing OSPF and Policy based Routing

From: rafael.valiente@bt.es
Date: Thu Dec 12 2002 - 04:56:02 GMT-3


Hello

Policy routing apply to incoming traffic from interface where is configured.

You are testing connectivity using ping, so is traffic generated locally for
the router, if you whish to apply policy-routing to this type of traffic you
need to remove the command from interface and add this global command:

ip local policy route-map pol

Note that standard acl match source address, you must change acl into
route-map:

access-list 101 permit ip any 10.34.0.0 0.0.255.255

Also you can use static route instead policy routing

ip route 10.10.1.2 255.255.255.255 10.10.1.1
ip route 10.10.1.3 255.255.255.255

I hope this help you

Regards

 Rafa
-----Mensaje original-----
De: KHAN, ITIKHAR A [mailto:IKHAN@scana.com]
Enviado el: miircoles 11 de diciembre de 2002 19:26
Para: 'ccielab@groupstudy.com'
Asunto: Confusing OSPF and Policy based Routing

Team,
 I working with OSPF scenario

10.1.1.1 10.10.1.1 10.10.1.2
------------R1-------------FR--------------R2---------------
                           |
                           | 10.10.1.3 10.34.1.1 10.34.1.2
10.44.1.1
 
|---------------R3------------------------------------R4--------------------

---
                           |
                           |   10.10.1.5
                           |---------------R5----------------------
                                                             11.1.1.5 

FR is Hub and Spoke with R1 as Hub FR is area 0 all routers see all networks. Problem is I can only use one Frame-relay map statement on R2,R3 and R5 pointing towards R1 it means all these three routers can ping R1 Frame-relay interface (10.10.1.1) but they can not ping Each other FR interfaces because pnly one FR map statement is allowed. Ospf runs well all router see all networks but R5 cannot ping 10.34.1.1 because it got next hop as R3 serial (10.10.1.3) but as it don't have layer 2 to layer three mapping for this IP 10.10.1.3 ( Due to lack for Frame-relay statement for this IP) it cannot ping it. What I know is that I need to know Policy routing to use 10.10.1.1 as next hop for 10.34.1.1 from R5 but where should I use configure it I configured at R5 serial interface for 10.34.1.1 network but its not working see my config

For interface

! interface Serial0 ip address 10.10.1.5 255.255.0.0 encapsulation frame-relay no ip route-cache no ip mroute-cache ip policy route-map pol frame-relay map ip 10.10.1.1 131 broadcast

For Access list

access-list 1 permit 10.34.0.0 0.0.255.255

For Route-map

route-map pol permit 10 match ip address 1 set ip next-hop 10.10.1.1

Still my router table shows

R5#sh ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route

Gateway of last resort is 10.10.1.2 to network 0.0.0.0

137.20.0.0/24 is subnetted, 1 subnets O IA 137.20.20.0 [110/65] via 10.10.1.2, 01:39:11, Serial0 10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks C 10.10.0.0/16 is directly connected, Serial0 O IA 10.1.0.0/16 [110/74] via 10.10.1.1, 01:39:11, Serial0 O IA 10.4.0.0/16 [110/138] via 10.10.1.3, 01:39:11, Serial0 O IA 10.44.0.0/22 [110/129] via 10.10.1.3, 01:39:11, Serial0 O IA 10.34.0.0/16 [110/128] via 10.10.1.3, 01:39:11, Serial0 <--------------- (it is suppose to use 10.10.1.1 as next hop) 11.0.0.0/16 is subnetted, 1 subnets C 11.1.0.0 is directly connected, Ethernet0 O*E1 0.0.0.0/0 [110/165] via 10.10.1.2, 01:39:11, Serial0

any idea,

Thanks Iftikhar . ********************************************** Noticia legal Este mensaje electrsnico contiene informacisn de BT Ignite Espaqa S.A.U. que es privada y confidencial, siendo para el uso exclusivo de la persona (s) o entidades arriba mencionadas. Si usted no es el destinatario seqalado, le informamos que cualquier divulgacisn, copia, distribucisn o uso de los contenidos esta prohibida. Si usted ha recibido este mensaje por error, por favor borre su contenido lo antes posible. Gracias. .



This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:44 GMT-3