I am being asked to create a duplicate network that will service VM clones of production VMs for testing and development purposes (without changing their IP or anything else). We have something similar at a different site using "transit" zones and individual NAT rules (that I did not configure), but this task is a bit different from that.
I need a L3 interface to represent this duplicate network, to eventually communicate to the internet.
I am trying this small test first.
Is there a way to NAT the IP of devices (and maybe gateway IP) to communicate to a unique L3 interface on the firewall?
I assume separate zones and virtual routers will keep the traffic separate, looking for suggestions for the NAT rules to accomplish.
Solved! Go to Solution.
This may be possible by creating multiple VSYS and then a transit zone, but I would be really careful with having the same IP subnets on the same firewall in the same VSYS. We ran into an issue where we had the same public facing network on outside multiple interfaces and ran into an issue where bi-directional NAT feature did not work as it would randomly chose to start advertising the MAC address on an interface that did not have rules for that particular NATed IP. We had to then create both inbound and outbound NAT rules. Not even sure how this would look or what potential issues you could run into.
In our case we have a separate firewall for sandbox testing.
I would say that the only way to properly do this is by having multiple VSYS as already mentioned by @mlinsemier. That would allow you to keep the traffic fully seperated and only allow inter-VSYS communications exactly where needed. This also ensures that you can build out security policies for your test/dev enviroment that will never apply to your production traffic until you actually role out to production.
Thank you guys for the feedback. I just created my first transit network (without a new vsys).
But still need to configure it in a more specific way.
I am in process of that and researching creating a new vsys. Will report back, update, and close this week.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!