You can do it at the point that one of them fails - we do this all the time where I work.
On both boxes, setup a sender group with a relay policy to accept mail from the other system.
On the box that no longer has internet connectivity: 1) export current smtproutes (if you have any - so you can return it to the orginal list easily) 2) clear the list 3) create the ALL smtproutes as your other gateway 4) delivernow (then pick all)
Now - if you don't like getting called in the middle of the night: While your normal routes are there: smtproutes export smtproutes.txt smtproutes clear smtproutes new ALL smtproutes export disaster_smtproutes.txt smtproutes import smtproutes.txt
Train your 24x7 personnel to login to the box when there is an issue and type: smtproutes import disaster_smtproutes.txt commit
delivernow all logout
And when the problem goes away: smtproutes import smtproutes.txt commit
Thanks Shannonh, I guess I should say I'm looking for a more automated solution to this within the devices themselves. None of us like getting woken up at 2am ;)
Seems to me there should be some method for doing this. For inbound mail there is althost, smtp routes and other means of directing deilivery, but I guess I'm a bit mystified that within AsynOS there is no options to shape/reroute the outbound traffic dynamically based off link state, destination host unreachable or non-response. Having this in place could give you an automatic second attempt at delivery from the partner device. Who knows, maybe there isn't much benefit to having a second delivery attmpt, but when it comes to the earlier situation of loosing your ISP/Circuit/Interface, having a setting for partner delivery if attempted delivery fails would be a elegant solution within the devices.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :