Bridge for V2T migration with DHCP within NSX-V and the client within NSX-T works with static addressing but not DHCP
Article ID: 341637
Updated On:
Products
VMware NSX
Issue/Introduction
To help configure and troubleshoot
Symptoms:
If static addressing is working between the client and the gateway that means the gateway is reachable which points to DHCP traffic not being received from the DHCP server back to the client.
This causes VMs on static addressing to be up but ones with DHCP in the NSX-T environment to not obtain an address from the DHCP server within the NSX-V environment
Symptoms:
If static addressing is working between the client and the gateway that means the gateway is reachable which points to DHCP traffic not being received from the DHCP server back to the client.
This causes VMs on static addressing to be up but ones with DHCP in the NSX-T environment to not obtain an address from the DHCP server within the NSX-V environment
Environment
VMware NSX-T Data Center 3.x
VMware NSX-T Data Center 4.x
VMware NSX-T Data Center
VMware NSX-T Data Center 4.x
VMware NSX-T Data Center
Cause
By default, the segment security profile is set to block DHCP servers on IPv4 and IPv6. If the default segment security profile is assigned within the NSX-T environment then the clients will not receive DHCP as expected
Resolution
Make a new segment profile and disable the DHCP server block as needed
Additional Information
Impact/Risks:
VMs within the NSX-T environment on the default security profile are unable to receive DHCP from an NSX-V or external environment
VMs within the NSX-T environment on the default security profile are unable to receive DHCP from an NSX-V or external environment
Feedback
Yes
No
Powered by
