HCX Service Mesh - IX appliance deployment failure with POST_CONFIG_VIX
search cancel

HCX Service Mesh - IX appliance deployment failure with POST_CONFIG_VIX

book

Article ID: 440603

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • The following error message is displayed in the HCX UI under Infrastructure > Interconnect > Service Mesh > MORE (View Tasks):

  • ApplianceLifecycleJob Failed. Reason: Interconnect Service Workflow GenerateAndPostConfig failed. Error: Operation timedout in state POST_CONFIG_VIX, Operation timedout in state POST_CONFIG_VIX

and/or

  • GenerateAndPostConfig Failed. Reason: Operation timedout in state POST_CONFIG_VIX

 

  • Login to the HCX manager as user admin and navigate to the log file /common/logs/admin/app.log, the following error is reported:

<Timestamp> [InterconnectService_SvcThread-6829, J:837d097d, , TxId: <TxID> ERROR c.v.v.h.s.i.InitiateServiceMeshOperation- Failure detected while verifying completion of InterconnectServiceJobs::processServiceMesh. Reason: Interconnect Service Workflow processServiceMesh failed. Error: Process Service Mesh failed. Interconnect Service Workflow GenerateAndPostConfig failed. Error: Operation timedout in state POST_CONFIG_VIX, Operation timedout in state POST_CONFIG_VIX java.lang.RuntimeException: Interconnect Service Workflow processServiceMesh failed. Error: Process Service Mesh failed. Interconnect Service Workflow GenerateAndPostConfig failed. Error: Operation timedout in state POST_CONFIG_VIX, Operation timedout in state POST_CONFIG_VIX

        at com.vmware.vchs.hybridity.service.interconnect.AbstractInterconnectJob.getSubflowJobDataArray(AbstractInterconnectJob.java:758)
        at com.vmware.vchs.hybridity.service.interconnect.AbstractInterconnectJob.checkComplete(AbstractInterconnectJob.java:2308)
        at com.vmware.vchs.hybridity.service.interconnect.InitiateServiceMeshOperation.handleState(InitiateServiceMeshOperation.java:170)
        at com.vmware.vchs.hybridity.service.interconnect.AbstractInterconnectJob.run(AbstractInterconnectJob.java:217)
        at com.vmware.vchs.hybridity.messaging.LoggingJobWrapper.run(LoggingJobWrapper.java:41)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)

Environment

VMware HCX

Cause

The Network Profiles used in the Compute Profile for the Service Mesh are configured to all use the same Network Subnet and same Default Gateway 

Resolution

  • Ensure the Network Profiles are configured to use unique non-overlapping IP address and Subnet.  
  • If logical separation of HCX traffic is not required, consolidate all necessary traffic types (Management, vMotion, Replication, Uplink) into a single Network Profile.
  • If network isolation is mandatory (e.g., separating Management traffic from vMotion or Uplink traffic), map those respective Network Profiles to distinct, non-overlapping subnets and VLANs to maintain strict routing boundaries on the deployed appliances.

Additional Information

Please reference Broadcom HCX Techdocs for reference on how Network Profiles are used:

Network Profile Considerations and Concepts

Powered by Wolken Software