Error when trying to extend a network on HCX: "Unable to find backing dvpg id corresponding to logical switch"
search cancel

Error when trying to extend a network on HCX: "Unable to find backing dvpg id corresponding to logical switch"

book

Article ID: 410078

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • You are unable to extend any network.
  • From the HCX Cloud Manager (target), the Compute Profile applied to the Service Mesh is configured using the DVS switch for the "Network Container (Network Extension Appliance Limit)".
  • When reviewing the HCX Cloud logs in /common/logs/admin/app.log, the following error is observed:
    [NetworkStretchService_SvcThread-608, j: #########, s: #######, , TxId: #######-####-####-####=###########] WARN  c.v.v.h.networkstretch.AbstractJob- Failed to resolve vc opaque network moref for logical switch #######-####-####-####=###########: Failed to get opaque network moref with logical switch id #######-####-####-####=###########
    [NetworkStretchService_SvcThread-608, j: #########, s: #######, , TxId: #######-####-####-####=###########] WARN  c.v.v.h.n.i.PrepareOrgNetworkNsxTJobInt- Unable to find backing dvpg id corresponding to logical switch #######-####-####-####=###########. Retrying...
    [NetworkStretchService_SvcThread-608, j: #########, s: #######, , TxId: #######-####-####-####=###########] WARN  c.v.v.h.n.i.AbstractJobInt- Exception in NetworkStretchJobs:prepareCloudNetwork. Reason : Unable to find backing dvpg id corresponding to logical switch #######-####-####-####=###########. Retrying...
    NetworkStretchService_SvcThread-608, j: #########, s: #######, , TxId: #######-####-####-####=###########] WARN  c.v.v.h.n.i.AbstractJobInt- PrepareOrgNetworkNsxTJobInt failed in state GET_NETWORK_SEGMENT. Error: Unable to find backing dvpg id corresponding to logical switch #######-####-####-####=###########. Retrying.... Retry attempt: 0
    java.lang.RuntimeException: Unable to find backing dvpg id corresponding to logical switch #######-####-####-####=###########. Retrying...

Environment

VMware HCX

Cause

The Compute Profile applied to the Service Mesh on the HCX Cloud (target) must be configured to use the NSX overlay network, not the DVS switch.

Resolution

  1. Update the Compute Profile, and under the step "Select Network Containers Eligible for Network Extension" change from the DVS switch to use an overlay transport zone:
  2. Resync the Service Mesh from the HCX Connector (source):
    To perform a Resync operation, go to Interconnect > Service Mesh > Resync.
    Click Resync to confirm the operation.

    Note: HCX NE appliances will be redeployed during this operation.

Additional Information

Requirements for Network Extension

Networks with NSX-T Data Center at the destination:
NSX-T Overlay and NSX-T VLAN networks are always created as NSX Overlay networks at the destination. HCX Network Extension is always to NSX Overlay networks.