Error "Sub allocated IP pool specified for edge gateway Edge-Name is invalid. Ranges in the pool should belong to external network IP pool" when attempting to add external network to edge gateway in Cloud Director
search cancel

Error "Sub allocated IP pool specified for edge gateway Edge-Name is invalid. Ranges in the pool should belong to external network IP pool" when attempting to add external network to edge gateway in Cloud Director

book

Article ID: 417463

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • An external network is already associated with the edge gateway
  • Attempting to add another external network in different subnet following Add an External Network Connection to an NSX Edge Gateway to same edge gateway fails with error:

    [ #####-#####-#####-#####-#####] Sub allocated IP pool specified for edge gateway Edge-Name is invalid. Ranges in the pool should belong to external network IP pool. Sub allocated IP Ranges #.#.#.#-#.#.#.#. External network IP pool [].



  • In /opt/vmware/vcloud-director/logs/vcloud-container-debug.log of VMware Cloud Director (VCD) cell, you see errors similar to:

    {
        "minorErrorCode": "BAD_REQUEST",
        "message": "[ #####-#####-#####-#####-##### ] Cannot allocate multiple primary IP addresses for NSX-T Edge Gateway Edge-Name(com.vmware.vcloud.entity.gateway:f#####-#####-#####-#####-#####).",
        "stackTrace": "com.vmware.vcloud.api.presentation.service.BadRequestException: Cannot allocate multiple primary IP addresses for NSX-T Edge Gateway Edge-Name(com.vmware.vcloud.entity.gateway:f#####-#####-#####-#####-#####).\n\tat com.vmware.vcloud.networking.model.edge.nsxt.NsxTUplinkInterface.validatePrimaryIpAddress(NsxTUplinkInterface.java:189)\n\tat com.vmware.vcloud.networking.model.edge.nsxt.NsxTUplinkInterface.validate(NsxTUplinkInterface.java:83)\n\tat

Environment

VMware Cloud Director 10.6.x

Cause

This issue occurs when the external network does not have any IP ranges added to it's static IP pool.

Resolution

To resolve this issue,

  1. Edit the external network from VCD Provider portal and ensure they have IP ranges added under 'Static IP pools'. Refer External Networks in VCD .

  2. Once the IP ranges are added, add the external network to edge gateway following Add an External Network Connection to an NSX Edge Gateway