When migrating from a different firewall vendor I think it is best not to try to replace the NAT config 1 to 1 but instead try to figure out what the original requirement was and then try to figure out how to solve this on the MX. Very often it will just not work the same way as it was configured before.
@KarstenI Being that I am new to the Meraki NAT configuration. I want to make sure that I am setting it up correctly so that traffic that I flowing under the Sonicwall will under the Meraki.
Basically right now I have traffic that is flowing through a site to site VPN tunnel through a local IP to a server housed outside the organization. I want to be able to shut off the Sonicwall and have the Meraki take over.
The moment you have a lightly complex NAT-config on the other device, it will not always be possible to migrate that 1:1 to the MX. That's the reason it is important to describe to requirements as good as possible.
Remote server for radiology through Site to Site VPN to an EMR what has an internal IP address for the router. The traffic should flow both ways through that internal IP from the RA IP addresses and the EMR IP addresses. Is there an easy way to make that happen through the NAT rules in the Meraki?