Failure to configure service mesh as IX appliance can not be deployed
search cancel

Failure to configure service mesh as IX appliance can not be deployed

book

Article ID: 425560

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

Failure to configure service mesh as IX appliance can not be deployed

The diagnostic show following error 

HCX-WAN-IX is unable to reach Deployment_HostSystem on the ports 8000. Please ensure firewall is not blockign the ports or routing is correctly configured.

Environment

VMware HCX

Cause

HCX appliance needs The error is received due to the issue of network configuration. 

The deployment of IX appliance requires access to vMotion network. This network is required to perform RAV based migration. To access vMotion network, IX appliance configure an interface for a vMotion network. This provides efficient, high-bandwidth VM movement, separate from the management network.
Through vMotion network, IX appliance creates connectivity with the ESX vMotion network. The connectivity requires port 8000 between ESX vMotion network and IX appliance vMotion network in both directions. 
The above error message requires investigation:
#1. Network connectivity between IX appliance (vMotion network) and ESX host vMotion network
#2. TCP Port  (on port 8000) connectivity between IX appliance vMotion network and ESX host vMotion network

 

Resolution

On vSphere ESX, each TCP/IP stack on a host can have only one default gateway. This default gateway is part of the routing table and all services that operate on the TCP/IP stack use it.


For example, the VMkernel adapters vmk0 and vmk1 can be configured on a host. 
vmk0 is used for management traffic on the ##.##.##.##/# subnet, with default gateway ##.##.##.##
vmk1 is used for vMotion traffic on the 1##.##.##.##/# subnet
If you set ##.##.##.## as the default gateway for vmk1,

vMotion uses vmk1 as its egress interface with the gateway ##.##.##.##. The ##.##.##.##gateway is a part of the vmk1 configuration and is not in the routing table. 

Only the services that specify vmk1 as an egress interface use this gateway. This provides additional Layer 3 connectivity options for services that need multiple gateways.

To configure a vMotion network with its own gateway, use the vSphere Client to override the default gateway settings for the specific VMkernel adapter: 
Select the Host: Navigate to ESXi host and select the Configure tab.
Open VMkernel Adapters: Go to Networking > VMkernel adapters.
Edit the Adapter: Click the ellipsis (...) next to the intended vMotion VMkernel adapter (e.g., vmk1) and select Edit.
Override Gateway: In the IPv4 settings section, check the box for Override default gateway for this adapter.

Additional Information

Override Kernel 

HCX Ports