VMware HCX [VMC on AWS] - Service Mesh Deployment Fails with Error "Service Insertion config not found"
search cancel

VMware HCX [VMC on AWS] - Service Mesh Deployment Fails with Error "Service Insertion config not found"

book

Article ID: 323348

calendar_today

Updated On:

Products

VMware

Issue/Introduction

In a VMware Cloud (VMC) on AWS environment, the following error may be seen while deploying an HCX Service Mesh from the on-premise site:

Service Insertion config not found, while configuring logical switches!

The error is displayed on the HCX Connector Manager UI located at the on-premise site under:

Interconnect - Service Mesh - Tasks

SI Error blur.jpg
 


Resolution

This error can be avoided by ensuring that the Uplink network selected in the HCX Compute Profile at the VMC site is either the directConnectNetwork1 Network Profile or the externalNetwork Network Profile depending on the type of deployment. This is done from the HCX Cloud Manager UI located at the VMC for AWS Cloud site. The Mgmt-app-network Network Profile should not be used for the Uplink network in the Compute Profile. This will ensure that when the Service Mesh is deployed the correct Uplink network is selected to avoid the error
 

Screen shots taken from the HCX Cloud Manager UI:

Interconnect - Network Profiles

lab NP blur.jpg

Interconnect - Compute Profiles

lab CP  blur.jpg

Interconnect - Service Mesh

lab SM blur.jpg
 

Additional Information

  
1) For Direct Connect (DX) Deployments:

 
Ensure the IP address range (CIDR) configured for the directConnectNetwork1 Network Profile does not overlap with the VMware Cloud (VMC) on AWS management subnet CIDR block or any other IP address range already in use for services in the VMC. Overlap can cause routing and network reachability issues for those other components. The CIDR used should be large enough so that each HCX Interconnect or Network Extension (IX/NE) appliance deployed at the VMC cloud site can be assigned an IP address. Also ensure the same CIDR is not used in the on-premise environment.
  

Existing Segment IP ranges used in the VMC can be checked from the VMware Cloud Console UI by selecting:

Network & Security - Segments - Segment List

Lab Segment Blur.jpg

The CIDR used should only be configured in the directConnectNetwork1 Network Profile. It must not be configured as a network segment within the VMC SDDC. After creation in the directConnectNetwork1 Network Profile this new network will be advertised via BGP over the Direct Connect (DX) to the on-premise site. This can be checked from the VMware Cloud Console UI by selecting:

Network & Security - Direct Connect

Lab DX Blur.png
   
2) For externalNetwork Deployments:

Ensure the IP addresses configured in the externalNetwork Network Profile are taken from the Public IPs list found in the VMware Cloud Console UI. The Public IPs can be found on the VMware Cloud Console UI by selecting: 

Network & Security - Public IPs

The REQUEST NEW IP button can be used to generate additional Public IPs if required. The IP address list configured in the externalNetwork Network Profile should be large enough so that each HCX Interconnect or Network Extension (IX/NE) appliance deployed at the VMC cloud site can be assigned an IP address.

lab Public IPs blur.jpg