I'm going crazy trying to figure this out. Please refer to the pdf in the attachment below (it is small 55Kb).
Basically we have two networks subnet x and subnet y which are internally running OSPF each. We are not exchanging OSPF routes across the subnets for fear it might overwhelm the L3 switch in subnet Y and and have instead opted to configure a static route in the routers in subnet X going into subnet Y and default routes in subnet Y going into subnet X.
The below setup works, however, without going into specifics, there is a requirement in our setup to have the static ip routes going into subnet y configured on the L3 switch in subnet X in such a way that they are "removed" from the routing table if the next hop is unreachable.
Since this is not a straight up L3 P2P or a traditional P2P over serial, when the next hop goes down (in this case IPs 192.168.1.10 and .14), the L3 switch in subnet X is oblivious to the next hop going down since the vlan interface is kept alive due to active member ports in the L2 switch in the middle. Thus the route is never removed from the routing table.
I've tried using object interface tracking with the IP route reachability option but that again works off IP prefixes and as we have established, the route is never removed from the routing table, so the tracked object is always up.
So I guess, my question here is (deep breath), short of extending a direct L3 connetion between the two L3 devices in subnets X and Y thereby circumventing the L2 switch in between, is it possible to make stateful static routes in the given scenario ??
Appreciate any help with the above...