HCX vMotion IP change fails with "IPs from the pool are in use" on IX appliance
search cancel

HCX vMotion IP change fails with "IPs from the pool are in use" on IX appliance

book

Article ID: 442118

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

Changing the vMotion IP address on a deployed HCX IX (Interconnect) appliance is needed, and editing the existing vMotion Network Profile to remove the currently-leased IP fails with the following error in the HCX Manager UI:

Unable to update IPAM pool with range(s) ##.###.##.### - ##.###.##.###. Some of the affected IPs from the pool are in use.

Running a Service Mesh Resync after editing only the Network Profile pool returns the following result, with no change applied to the IX appliance:

No configuration changes found.

Attempting to create a second vMotion Network Profile pointing at the same vMotion port group is also blocked, because HCX enforces one Network Profile per backing network.

The underlying need to re-IP the IX is typically driven by a duplicate IP on the vMotion subnet. An intermittent vMotion test (failing, then passing) is the common first symptom. The duplicate IP is confirmed by disconnecting the IX vMotion vNIC at the VM hardware level (Edit Settings on the IX VM, uncheck Connected on the vMotion network adapter) and pinging the IX's vMotion IP. A successful ping with the vNIC disconnected proves another device on the subnet is using the same IP.

Environment

  • VMware HCX 4.x
  • HCX IX appliance deployed as part of a Service Mesh
  • vMotion Network Profile referenced by the Compute Profile in use

Cause

The HCX internal IPAM holds an active lease on the IX vMotion IP and blocks removal of that IP from the Network Profile pool while the lease is held. Service Mesh Resync compares the deployed appliance state against the Compute Profile / Network Profile binding rather than against pool membership, so a pool-only edit produces no delta for Resync to apply. The HCX one-profile-per-port-group enforcement prevents a parallel vMotion Network Profile from being created on the same port group as a workaround.

Resolution

Temporarily move the vMotion service in the Compute Profile to a different Network Profile (backed by a different port group, such as the Management or vSphere Replication profile). This releases the lease on the original vMotion IP and allows the original profile to be edited freely. Once the original profile is corrected, move the vMotion service back.

Pre-change checks

  1. Confirm no active migrations, replications, or DR protections are running on the Service Mesh.
  2. Confirm the Service Mesh is healthy (all tunnels Up, no appliance alarms).
  3. Identify a second Network Profile that can temporarily host the vMotion service. The Management or vSphere Replication profile is typical. The profile must be backed by a different port group than the vMotion profile.
  4. Plan a maintenance window. The IX appliance is reconfigured twice, and vMotion migrations must not run during the procedure.

Procedure

Step 1 - Add a free IP to the temporary Network Profile

  1. Navigate to Infrastructure > Interconnect > Multi-Site Service Mesh > Network Profiles.
  2. Select the temporary Network Profile and click Edit.
  3. Add at least one free IP to the IP Ranges so an IP is available for the IX to lease.
  4. Save the profile.

This step must happen before editing the Compute Profile. If the temporary profile has zero free IPs when the Compute Profile is edited and Resync runs, the Resync fails because no IP is available in the pool.

Step 2 - Edit the Compute Profile to move the vMotion service to the temporary profile

  1. Navigate to Infrastructure > Interconnect > Compute Profiles.
  2. Select the Compute Profile in use by the Service Mesh and click Edit.
  3. Step through the wizard to Configure Selected Services.
  4. Under Select vMotion Network Profile, change the selection from the original vMotion profile to the temporary profile.
  5. Complete the wizard and save the Compute Profile.

Step 3 - Resync the Service Mesh

  1. Navigate to Infrastructure > Interconnect > Multi-Site Service Mesh > Service Mesh.
  2. Select the Service Mesh and click Resync.
  3. Confirm and allow the operation to complete.
  4. The IX releases the original vMotion IP and leases an IP from the temporary profile.
  5. Verify in View Appliances that the IX vMotion interface shows an IP from the temporary profile.

Step 4 - Edit the original vMotion Network Profile

  1. Navigate to Network Profiles and select the original vMotion Network Profile.
  2. Click Edit.
  3. Remove the old IP (no longer leased) and add the new IP.
  4. Save the profile. The IPAM-in-use error does not appear, because the lease is released.

Step 5 - Edit the Compute Profile to move the vMotion service back

  1. Edit the Compute Profile again.
  2. Under Select vMotion Network Profile, change the selection back to the original vMotion Network Profile.
  3. Complete the wizard and save the Compute Profile.

Step 6 - Resync the Service Mesh again

  1. Run Resync on the Service Mesh.
  2. The IX releases the temporary IP and leases the new IP from the original vMotion Network Profile.
  3. Verify in View Appliances that the IX vMotion interface shows the new IP.

Step 7 - Clean up the temporary profile

  1. Edit the temporary Network Profile and remove the IP added in Step 1, if it is no longer needed.

Step 8 - Verify

  1. Confirm the Service Mesh status is Up and all tunnels are healthy.
  2. Run a test vMotion migration to validate end-to-end connectivity on the new IP.

Notes on Force Redeploy

Force Redeploy is not required for this procedure. Resync handles both Compute Profile transitions because changing which Network Profile a service binds to is a configuration delta Resync detects and applies. Force Redeploy is only appropriate as a fallback if a Resync hangs, the IX does not successfully transition between profiles, or the Service Mesh is in a degraded state at the start of the procedure.

If the error persists after following these steps, contact Broadcom Support for further assistance. Provide the following when opening a support request:

  • HCX Manager log bundle from both source and destination sites
  • Screenshot of the IPAM-in-use error from the Network Profile edit dialog
  • Screenshot of the Compute Profile vMotion network selection
  • Output of View Appliances showing the IX vMotion IP before and after
Powered by Wolken Software