[c-nsp] Static routes on frame relay interfaces pointing to interface and next hop

[FILYURIN, YAN]

Hello and thank you in advance for reading my email  I was wondering if
it is possible to do a static route and point that static route to
0.0.0.0 address and here is how I came to this question:  I have a set
up where I have an a remote site and two remote site routers each having
two frame relay connections and a PVC on each connection going to a
central site device.  The devices at the central site summarize a
0.0.0.0/0 route to the remote site.  The remote site runs OSPF and
another similar set up I have is BGP.  I can certainly advertise OSPF
into EIGRP and can originate a default in OSPF, but the OSPF AS in the
remote sites already has a default route which can't be touched (in
fact, I have a distributed list for OSPF that blocks it), so I need to
create a bunch of specific static routes on the remote site routers and
redistribute them into OSPF.  My other requirement is that I can't touch
the central site routers.  So my question is, how could I make it
perfectly dynamic to take advantage of all that redundancy?  Here is my
thought process so far (all routers are 12.2.15(T5) and CEF is enabled
with default settings)

1)I can create static routes on the remote site router pointing the
frame relay subinterface and redistribute them into OSPF.  I would
create 2 sets of static routes on each remote site router for each frame
relay subinterfance.  The problem is that in certain case when a frame
relay interface goes down like when the PVC goes bad, the interface will
not go down and the static routes will still stay blackholing the
traffic.

2)I can do the same as above and point the static routes to both of the
subinterfaces and the next hop IP address.  In theory it should work but
I am not 100 % sure if the route would withdraw if the something at the
frame relay level will go down (the interface will still stay up/up).
It would work great on regular HDLC or PPP,  I am sure.

3)Based on the above Cisco would remove static route if the next hop
address would not be available through the interface and at this time
all interfaces are learning the 0/0 through EIGRP and then I've heard
that you can point a static route to 0 address.  I've never seen it
documented or shown anywhere, so what better place to ask then this
list.  What I would get out of it that I would get special recursion
where first I would have something point to 0.0.0.0 and then this
0.0.0.0 would be inspected and found as EIGRP route and that in turn
would be sent to the next hop address on the right interfaces be it
either of the frame relay interfaces or a crossover cable between two
router FastE interfaces and I would get the redundancy.  I could even
avoid using the interface in my ip route command.

Does it sound reasonable, or am I just making this stuff up? 

Thank you and let me know if you need more details. 


Yan Filyurin
Electronic Data Systems, Bank of America Account Network Design and
Fleet WAN Transformation
Phone:  781-788-2207 
Cell:       617-875-4862 
Yan.Filyurin at bankofamerica.com
Yan.Filyurin at eds.com