Virtual Machines showing "Waiting for IP" status for MON - VMware HCX

Products

• VMware HCX

Issue/Introduction

Virtual machines on an MON-enabled extended network are showing "Waiting for IP" status in the HCX Manager. 

Environment

VMware HCX
Mobility Optimized Networking (MON)

Cause

This status indicates that the HCX Manager cannot discover or verify the VM's IP address. This typically occurs due to one of the following:

1. Incorrect Gateway IP: 
   The Gateway IP provided during the network extension workflow does not match the actual gateway for that segment.
   
   
2. Missing Secondary IP:
   If a VM has multiple vNICs, HCX requires a valid IP to be configured and visible via VMware Tools for all connected interfaces on that segment.

Resolution

1. Verify VMware Tools: Ensure VMware Tools is running and correctly reporting IP addresses to vCenter.
   
   
2. Validate Network Extension: Confirm the correct Gateway IP was used during the initial Network Extension.
   
   
3. Configure Secondary IPs: If the VM uses multiple interfaces, work with the OS team to ensure all secondary vNICs have a valid IP address configured. This allows the enablement workflow to complete.
4. Simplify Network Design: If the "Waiting for IP" persists due to a dual vNIC setup, consider simplifying the VM to a single vNIC to enable full MON local egress functionality.

Additional Information

Note: Dual vNIC Architecture Restriction: A VM configured with two or more vNICs attached to the same extended segment triggers this state because the /32 host route cannot be automatically programmed.

Mobility Optimized Networking (MON) Troubleshooting Guide