Static routing not working (in NSX Edge) towards physical environment
book
Article ID: 417777
calendar_today
Updated On:
Products
VMware NSX
Issue/Introduction
Manually configured static routes on NSX are not working, preventing external access to VM's, despite NAT being correctly allocated.
Packet captures from the Edge node confirmed ICMP requests were being sent to the physical infrastructure, but no replies were observed, indicating traffic drop in the physical network.
You have configured next hop on NSX as physical router VIP but the next hop added to physical router (towards NSX) is configured for Edge uplink interfaces instead of Edge HA VIP.
Environment
VMware NSX VMware NSX-T Datacenter
Cause
Incorrect next-hop configuration for static routes on the physical router, specifically, you have configured NSX uplink interfaces as next hops for static routes on the physical router, instead of using the NSX Edge HA VIP.
HA VIP is intended to work with static routing and the physical router interacts with the HA VIP only.
Resolution
Please make sure to have configured next hop on the physical router as Edge HA VIP instead of individual edge uplink interfaces