Since static routes are being discussed, I have a question on setup. I'm also running a lab environment. My physical world gateway/firewall/internet router is 10.20.8.1 (NAT example). My NSX-T lab transport nodes all have 4 nics. Two nics are left on vDS and two are dedicated for NSX-T.
My ESXi servers and vCenter hang off the vDS and use 10.20.8.1 as their default gateway for internet connectivity. I've successfully configured Tier-1 edge (for logical networks) and Tier-0 edge for N-S routing.
I also don't want to configure BGP and would prefer to just configure static routes between my Tier-0 and physical world gateway/firewall/internet router. I've configured a static route on the Tier-0 for both 0.0.0.0/0 (internet) and 10.20.8.0/22 (physical network). I configured a next hop address of 10.20.8.1 (is that correct?) using the uplink interface I configured (hanging off my vlan backed transport zone - IP: 10.20.8.253).
When I run a get-routes on the Tier-0 I can see all of the NSX-T logical networks I created (so I know Tier-1 is successfully advertising it's routes to Tier-0). From Tier-0 CLI I can ping 10.20.8.1 (although I'm not sure that's because Tier-0 mgmt interface is on 10.20.8.0/22?)
When I jump on a vm configured with a NSX-T logical network, I'd think I can ping physical network IP's now (i.e. IPs in 10.20.8.0/22) - but I can't. Is there anything missing from my static route setup? Do I have to also configure static routes on my physical world gateway/firewall/internet router for the NSX-T logical networks? In the end I'd like my vm's with logical networks to be able to communicate with my physical network and also get internet access - all via static routes.
Thanks