[VMC on AWS] Following SDDC upgrade from 1.18v9 to 1.20v5 Horizon VMs using DHCP are not releasing IPs
Article ID: 323253
Updated On:
Products
VMware Cloud on AWS
Issue/Introduction
Symptoms:
Following an upgrade from 1.18v9 to 1.20v5 Horizon VMs using NSX as the DHCP server are not releasing or getting new IP address assignments.
Following an upgrade from 1.18v9 to 1.20v5 Horizon VMs using NSX as the DHCP server are not releasing or getting new IP address assignments.
Cause
During phase 3 of the upgrade process the DHCP IP address changed, resulting in lost DHCP Request and DHCP Offer traffic
Resolution
Please file a Support Request with VMware
Workaround:
Change the NSX config from DHCP server to DHCP relay. This means that instead of the NSX acting as the DHCP server locally it will instead relay that traffic to an external DHCP server. Another work around is to manually assign the IPs to VMs.
Workaround:
Change the NSX config from DHCP server to DHCP relay. This means that instead of the NSX acting as the DHCP server locally it will instead relay that traffic to an external DHCP server. Another work around is to manually assign the IPs to VMs.
Additional Information
Impact/Risks:
This causes networking to fail for VMs as they are unable to renew their IP addresses.
This causes networking to fail for VMs as they are unable to renew their IP addresses.
Feedback
Yes
No
Powered by
