From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Mon Dec 19 2005 - 09:31:44 GMT-3
Thanks for the info, Gustavo. Yes, you are correct, I "typoed" that mask. On
the metric, changing it from an E1 to E2 would not change the matric at the
router, but would change the metric at the next router, since the E1 is
additive and increases per hop where the E2 stays the same.
Dave
-----Original Message-----
From: Gustavo Novais
To: Schulz, Dave; nobody@groupstudy.com; Josef A
Cc: Cisco certification
Sent: 12/18/2005 10:28 AM
Subject: RE: set metric on route-map applied to OSPF distribute-list
route-map XXXX in
Hello Dave,
Thank you for your reply.
I'm aware of the distance command and of its possibilities. What I had
in mind was setting a distance or metric based on a TAG previously given
to a route. For what I could see, distribute-list only allows you to
permit or deny a route into route table, according to whatever attribute
you specify on a route-map. Distance only allows you to do that if you
match the source and the access-list.
I solved things a bit differently... on the preferred source
redistribution points I redistributed tagged routes as E1 and all else
as E2... It did what expected, but there's always the doubt of "is
setting route-type considered changing metric?"
BTW, on the example you gave the source is matched by a wildcard mask
0.0.0.0, not a 255.255.255.255. If you try entering that you'll be
setting the distance for all sources the send you the route specified on
the ACL.
Thank everybody for your inputs
Gustavo Novais
From: Schulz, Dave [mailto:DSchulz@dpsciences.com]
Sent: sabado, 17 de Dezembro de 2005 23:50
To: Gustavo Novais; nobody@groupstudy.com; Josef A
Cc: Cisco certification
Subject: RE: set metric on route-map applied to OSPF distribute-list
route-map XXXX in
The Doyle tcp/ip book shows a number of examples that may help here
where you change the administrative distance on route or group of routes
based on where it is coming from. For example.....
interface Ethernet0
ip address 10.1.1.1 255.255.255.0
!
!
router ospf 1
log-adjacency-changes
network 10.1.1.0 0.0.0.255 area 0
distance 100 2.2.2.2 255.255.255.255 2
!
access-list 2 permit 120.1.2.2
The distance is set a specific route (access-list 2) from a specific
source (in ospf, this is the router-id of the remote router).
Hope this helps to think through your solution.
Dave
-----Original Message-----
From: nobody@groupstudy.com
To: Josef A
Cc: Cisco certification
Sent: 12/17/2005 2:56 PM
Subject: RE: set metric on route-map applied to OSPF distribute-list
route-map XXXX in
I just wanted to make a nice and versatile solution... not change costs
and
match specific routes... but...
If it is necessary...
Gustavo Novais
________________________________
From: Josef A [mailto:josefnet@gmail.com <mailto:josefnet@gmail.com> ]
Sent: sabado, 17 de Dezembro de 2005 19:53
To: Gustavo Novais
Cc: Cisco certification
Subject: Re: set metric on route-map applied to OSPF distribute-list
route-map
XXXX in
Hello,
Try matching on the input interface instead of the next-hop.
Remember also that the router still computes the routes from the LSAs
which
are not filtered, and cost is an LSA attribute.
So this might(?) not be possible using a distribute-list.
Just a thought.
Thanks
Josef.
On 12/17/05, Gustavo Novais <gustavo.novais@novabase.pt> wrote:
Hello
I'm trying to make OSPF decide between two paths without changing any
interface values.
The same routes are coming from both paths(two different interfaces),
but only the ones tagged with 10 are to be decided upon one interface or
the other. When one path is not available, the other path should kick
in.
To do this I'm trying to build a route-map like this.
router ospf 1
router-id 150.1.5.5
distribute-list route-map AS10-PREFER in
route-map AS10-PREFER permit 10
match ip next-hop R4
match tag 10
set metric 20
!
route-map AS10-PREFER permit 20
match ip next-hop R3
match tag 10
set metric 30
!
route-map AS10-PREFER permit 30
This, theoretically would allow me to enter on the RIB the routes with
smaller metric.
The problem is that OSPF keeps ignoring my set statements and keeps the
routes always with metric 20, thus allowing load sharing to the tagged
paths.
The target routes are E2, but shouldn't the route-map act upon their
metric nonetheless?
Or because I'm using the route-map on a distribute-list the set commands
are not valid?
TIA
Gustavo Novais
This archive was generated by hypermail 2.1.4 : Mon Jan 09 2006 - 07:07:51 GMT-3