Miguel,
Yes, you are correct. I've been caught with my pants down.
I will hang pity in my words only to revel in the fact that you can turn
static route propagation off with 3.7. You can actually set the propagation
rules from one routing protocol type to another. (see below...)
Also, here are few other words of wisdom:
Quoted from the ComOS Release Notes for 3.7:
Static routes are now properly injected into OSPF if RIP route injection
has been
disabled. The behavior of the "ospf accept-rip" command on Ethernet
interfaces
has been corrected. The intended behavior of this command has always been to
control whether RIP routes learned on this Ethernet interface were propagated
into the OSPF link state database so that OSPF could advertise these
RIP-learned
routes to its OSPF neighbors. However, before release 3.7, the command also
had
the undesirable effect of determining if static routes whose next hop
gateways
were reached via this Ethernet interface were propagated into the OSPF link
state database. This release ensures that static routes are always propagated
into OSPF independent of the setting of the "ospf accept-rip" command.
(below)...
Also look at pages 10-12 through 10-14 (especially) in the JUNE 97 Command
Line
Administrators Guide regarding the topic of 'propagation'. These rules are
part
of the BGP support we added. Also, notice the use of ROUTE FILTERS! More on
that later.
>From 10-14:
delete propagation <Protocol Source> <Protocol Destination>
***
One can extrapolate this command:
delete propagation static ospf
***
Metric is not a parameter for propagation deletion.
Please advise us of your success.
Regards,
Tom Fellenz
Your ~Humble~ Routing Conscience.
Livingston