I have a scenario of a production environment, where ASA uses a (hsrp virtual) IP as default gateway. Since a recent upgrade, there are now two routers and in order for these to manage the routes to the ASA dynamically I need to replace their static routes for the internal network to the ASA with that of a routing protocol.
What I want to solve is:
1) Have ASA still only communicating with the VIP of the routers HSRP.
2) Let the route for 220.127.116.11/20, which goes via ASA, be dynamically added with a routing protocol to ensure that if router01 loses physical connection to Cisco ASA, then router01 knows it can go via router02 (and vice versa)
router01 (active): 18.104.22.168
cisco asa: 22.214.171.124
Inner network, 126.96.36.199/20, for which the both routers now have a static route towards the ASA.
I easily find OSPF documentation, but Im unsure how to implement this in a production environment without losing connectivity. I guess my question can be reduced to: Is it safe to follow a typical Cisco ASA OSPF documentation to add the route dynamically, and when done remove the static routes to accomodate for a convering network in the event of a failure?
Solved! Go to Solution.
I realize I didn't think it through. I think either have rely on hsrp and using static routes, or scrap hsrp and use ospf. It becomes a case of layer 2 OR layer 3 redundancy - not both.