We have two sites: 192.168.100.x and 192.168.101.x currently connected via IPsec VPN. On each end we have a Cisco ASA 5505. However, each site also has an MPLS VPN with intentions to move all traffic to this link.
Site A: ASA inside interface is 192.168.101.1
Site B: ASA inside interface is 192.168.100.1
The ASA at site B is failing (keeps power cycling itself) so we want to move all traffic over to use the MPLS link as obviously the MPLS as better QoS control. The MPLS VPN is connected together via two Cisco 2800 routers.
Site A: Telco MPLS VPN (CPE) inside inter. 192.168.101.6
Site B: Telco MPLS VPN (CPE) inside inter: 192.168.100.6
We want to keep the ASA @ site - this site has remote access needs and we want to have control over the firewall at this site. We are going to remove the ASA at site B, have the telco change the IP from 192.168.100.6 to 192.168.100.1 (so to minimize issues with internal clients using the current default-gateway of the ASA.). At site A, again we want to keep the ASA in place and keep its inside IP address.
Here is the question: Do we simply need to add a static route on Site A’s ASA for any traffic needing to reach Site B. Like so -
route inside 192.168.101.0 255.255.255.0 192.168.101.6 1
Will this work on the ASA? We need to make sure traffic can hit the ASA @ site A on the inside interface and trafiic will forward to the MPLS VPN router which then handles the traffic. Too, will it cause any problems in bi-directional flow between the two sites?
Thank you for taking your time to review!
