Azure VMware Solution
How To Series: Configuring NSX-T SNAT, No-SNAT & DNAT rules
Overview
Requirements
Lab Environment
NAT Rules
Kusto for NSX-T NAT Rule Logs
Overview
Many A...
Updated Sep 03, 2024
Version 4.0
Blog Post
6 MIN READ
Azure VMware Solution using a public IP down to the NSX-T Edge; configure SNAT, No-SNAT & DNAT
Excellent Guide, one question. Does it need to have any static routes either t0 or t1? or the dnat and snat does all on it's own?
You don't need to define static routes.
So it should work out of the box? if previous static routes were created should be removed? Is there any query i can apply to identify possible issues because neither DNAT and SNAT are working! Thank you!!
Did you see this:
Create a SNAT rule:
Source Network Address Translation (source-nat or SNAT) allows traffic from a private network to go out to the Internet. First let's make sure that the DNS service can reach the default DNS server 1.1.1.1. When first logging into the NSX-T interface, alarms will be present because the DNS service is unable to reach the upstream DNS servers at 1.1.1.1.
Figure 4: Alarms showing DNS service 1.1.1.1 is unreachable.
In this case you will have to add a SNAT rule to allow the Azure VMware Solution management segment access to the Internet. Follow the instructions below adding your management network (the /22 used when creating the SDDC) and one of the IP's created as part of configuration done when following the 'NSX-T public IP' procedure.
NOTE: PING WILL NOT WORK, ITS BLOCKED, USE TEST-NETCONNECTION X.X.X.X -port 443 to check for connectivity.
