[nsp] HELP! I need some ideas. OSPF + HSRP

Jim Devane jim at powerpulse.cc
Fri Oct 31 18:06:07 EST 2003


First of all, that you very much for replying and taking the time to
read/think about this... ( but ) 

Well, I thought of that. But I think the problem that I am having is that
when that static gets redistr it comes in as E2 110/20. Even if I route-map
and set metric the problem is that the route is still heard because the next
hop is reachable. I need the next hop to not be reachable yet have it
announced to the whole area... both of these routers are in area 0. bit of a
conundrum!

Here is the output I get when I use the poor metric

     172.16.0.0/30 is subnetted, 2 subnets
C       172.16.1.0 is directly connected, FastEthernet2/0
C       172.16.3.0 is directly connected, FastEthernet2/1
O E2 192.168.68.0/24 [110/20] via 172.16.1.1, 00:00:01, FastEthernet2/0
     192.168.87.0/29 is subnetted, 1 subnets
C       192.168.87.48 is directly connected, FastEthernet0/0

Rtr B is still redist it's static even though rtr B's link to the switch is
down....it can still reach the .50 from the OSPF advertisement of rtrA...so
it never withdraws it's atatic route...reagarless of the admin dist.

:(





-----Original Message-----
From: Ed Ravin [mailto:eravin at panix.com] 
Sent: Friday, October 31, 2003 2:55 PM
To: Jim Devane
Cc: cisco-nsp at puck.nether.net
Subject: Re: [nsp] HELP! I need some ideas. OSPF + HSRP

On Fri, Oct 31, 2003 at 01:51:08PM -0800, Jim Devane wrote:

> I cannot really do a static route on both of the routes since it will
create
> asymmetric traffic flows and I need for traffic to come in and out one
port
> to easily monitor and for billing.
...
> Ip route 192.168.68.1 255.255.255.0 172.16.87.50

How about a "poor metric" to the static route on the backup router B:

 ip route 192.168.68.1 255.255.255.0 172.16.87.XXX 250

With the "poor metric", the route should get overridden by the one
redistributed from A via OSPF.  When the route announced via OSPF
goes away, the static will be the only one left, and will be used.



More information about the cisco-nsp mailing list