with the given configuration if 10.51.14.0/24 network needs to go for 192.168.223.0/24 destination, ASA will NAT the source with RF interface IP , which means 192.168.223.0/24 will always see the traffic originating source as RF interface IP.
Kindly let me know if this is your requirement or you need something else.
There are two networks at this location; 10.51.14.0/24 which is routed via our MPLS and is behind the ASA.
And 192.168.223.0/24 which is standalone with no routing but we will set up intervlan routing within the site in the near future and it will also be behind that same ASA when we go live with this. It will not however be routed as I mentioned before because we are not allowed to route 192.168.x.x networks via the MPLS. So we were hopping to be able to do some kind of natting in order to manage and monitor it from 10.49.x.x.
The 10.49.x.x network is our HQ network from which we do all the monitoring of our world wide MPLS. It is behind an ASA as well.
I wanted to changed all 40 devices to a network that is routable but I am not permitted to do so. That would make this so much easier!
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...
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 :