Thanks Steve - I am aware of the 'next-table' functionality ... but what I want to achieve is a mechanism whereby a route (for example the 10.1.1.1/32 route) exists in the inet.0 table under normal conditions (and in this case is announced into the inet.0 table by eBGP) ... but if it disappears (i.e. the eBGP session/link fails) then an alternative route to 10.1.1.1/32 exists in a vrf-instance. This is why I wanted to use the resolution rib option.
I guess I could configure a static-route with a preference greater than 170 such that the eBGP route to 10.1.1.1/32 is always preferred until it disappears, then the static-route (preference 175 for example) to 10.1.1.1/32 with a next-hop next-table VRF.inet.0 takes over ...
↧