Error "Cannot update network with new subnet because it does not overlap all allocated ips" in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

When attempting to edit a network specification, rename a network, or update a subnet range in the VMware Cloud Director (VCD) tenant or provider portal, the task fails with the following error message:

Cannot update network with new subnet because it does not overlap all allocated ips (<IP_ADDRESS>).

Environment

VMware Cloud Director 10.x

Cause

This issue occurs because VMware Cloud Director performs a validation check on every network in the proposed Network Specification to ensure that all currently allocated IP addresses, as recorded in the VCD database, are contained within the proposed CIDRs or Static IP Pools.

If an IP address, such as a Gateway IP, a NAT rule address, or a Load Balancer VIP, is already assigned but is missing from a defined Static IP Pool range, VCD blocks the update to prevent connectivity loss or configuration inconsistency. This is common after migrations (e.g., NSX-V to NSX-T) or when a subnet is being shrunk or shifted.

Resolution

To resolve this issue, ensure that the Static IP Pool includes the specific IP address mentioned in the error message.

1. Identify the Conflicting IP: Note the IP address(es) provided in the error message brackets.
2. Navigate to the Network Configuration:
   • Log in to the VMware Cloud Director Provider or Tenant portal.
   • Go to Networking > Networks (or Provider Gateways if editing a Tier-0/Tier-1 scope).
   • Select the affected network and click Edit.
3. Update Static IP Pools:
   • Navigate to the IP Management or Static IP Pools section.
   • Review the existing ranges.
   • Add a new range or expand an existing one to include the IP address mentioned in the error.
4. Save Changes: Click Save. VCD will re-validate the configuration. Since the allocated IP is now within the defined pool, the validation should pass.
5. Alternative: If the IP address mentioned is not currently in use by any service, identify and remove the service (NAT, Load Balancer, or VM NIC) configured to use that IP before updating the pool.