Error "Cannot create External Network. Existing network backings in use or is an uplink" when creating an external network in VMware Cloud Director
search cancel

Error "Cannot create External Network. Existing network backings in use or is an uplink" when creating an external network in VMware Cloud Director

book

Article ID: 383104

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • VLAN port group associated with the network was deleted and recreated in vCenter
  • Attempting to recreate the external network using same VLAN in VMware Cloud Director fails with the error

    Cannot create External Network. Existing network backings Network name (dvportgroup-xxxx) in use or is an uplink. Possible solution would be to configure overlapping networks (i.e. if you wish to use the same VLAN ID)".

  • Following entries are seen under/opt/vmware/vcloud-director/logs/networking.log 

    CREATE_EXTERNAL_REAL_NETWORK-> ActivityFutureTask [activityExecutionState=AbstractActivityExecutionState [activityName=com.vmware.vcloud.fabric.net.activities
    .network.externalrealnetwork.CreateExternalRealNetworkActivity, clientURI=urn:uuid:xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx, entityURI=xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx, currentPhase=com.vmware.vcloud.fabric.net.activities.network.externalrealnetwork.CreateExternalRealNetworkActivity$HandleClaimPortGroupCompleti
    onPhase, cancelRequested=false, parameters(size)=10], exception=java.util.concurrent.ExecutionException: com.vmware.vcloud.api.presentation.service.EntityIsInUseException: Existing network backings Network name (dvportgroup-xxxx) in use or is an uplink.  Possible solution would be to configure overlapping networks (i.e. if you wish to use the same VLAN ID)., partialFailure=false, partialFailureException=null, nullResult=false, result=null, canceled=false] - Handle: urn:uuid:xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx, Current Phase:CreateExternalVCDNetworkActivity$CreateExternalRealNetworkPhase 

  • API response from browser developer tools report following errors:
    {
        "minorErrorCode": "ENTITY_IS_IN_USE",
        "message": "[ xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx ] Existing network backings Network name (dvportgroup-xxxx) in use or is an uplink.  Possible solution would be to configure overlapping networks (i.e. if you wish to use the same VLAN ID).",
        "stackTrace": "com.vmware.vcloud.api.presentation.service.EntityIsInUseException: Existing network backings Network name (dvportgroup-xxxx) in use or is an uplink.  Possible solution would be to configure overlapping networks (i.e. if you wish to use the same VLAN ID).\n\tat com.vmware.vcloud.fabric.net.activities.network.externalrealnetwork.ClaimPortGroupForExternalRealNetworkActivity$VerifyReleasePortgroupsAndFailPhase.execute(ClaimPortGroupForExternalRealNetworkActivity.java:178)\n\tat com.vmware.vcloud.fabric.net.activities.AbstractNetworkFabricActivity$AbstractBaseNetworkingActivityPhase.invoke(AbstractNetworkFabricActivity.java:101)\n\tat

  • If we change the VLAN ID of the port group from vCenter, creation of external network using this port group is successful from VCD.

Environment

VMware Cloud Director

Cause

VLAN ID backed port group was deleted and recreated directly from vCenter leaving stale VLAN ID references in VCD database.

Resolution


Database modifications are required to remove VLAN ID references from Cloud Director. To resolve this issue, please open a Support Request with Broadcom Technical Support and note this Article ID (383104) in the problem description. For more information, see Creating and managing Broadcom support cases.