How to troubleshoot communication issues between ePolicy Orchestrator and the vCenter

Articoli tecnici ID: KB86162
Ultima modifica: 10/13/2021

Ambiente

McAfee Cloud Workload Security (CWS) 5.x for vSphere

Riepilogo

This article explains how to troubleshoot communication issues between ePolicy Orchestrator (ePO) and the vCenter when the Cloud Workload Security for vSphere sync with vCenter fails.

Problema

When synchronization between the Cloud Workload and vCenter fails, you might see errors similar to the following in Orion.log:

ERROR [scheduler-InternalTask-thread-2] scheduler.FullSyncSchedulerCommand - com.mcafee.move.vcenter.discovery.exception.CommunicationException:
Problem in Communication to vCenter. URL = https://xx.xxx.xxx.xx:443/sdk

Causa

This random sync timeout issue occurs when the vCenter server and ePO server are unable to communicate.

This issue can occur when:

Using a domain account because of the additional time needed for connections to Active Directory (AD) server.
Using local accounts because the vCenter stops responding or because of network latency.
There are compatibility issues between the environments.

Soluzione

Do the following:

Make sure the ePO version and VMware vCenter version are compatible. For details, see KB74865.
Make sure that you can access the vSphere client and Web client from the ePO server:
1. Ping the vSphere client from the ePO server. If Ping works, other communication might fail, possibly because of firewall rules.
2. Open a browser and access the vSphere Web client or start the vSphere client from the ePO server. Authentication also works with the same credentials used to register the cloud account.
Access the following URL from a browser on the ePO server and make sure that authentication works with the same credentials used to register the cloud account with ePO:

https://vCenter_IP_Address/mob

NOTE: Replace vCenter_IP_Address with the actual IP address of the vCenter.
Make sure that you have RPC access to the AD server. For details, see VMware article 1032641, which covers SSPI Timeout when logging into vCenter Server using Windows session credentials:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1032641

If both of the above checks are successful and the authentication continues to fail, contact Technical Support.

To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.

If you are a registered user, type your User ID and Password, and then click Log In.
If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.

Prodotti interessati

Cloud Workload Security 5.3.x
Cloud Workload Security 5.2.x
Known Issue/Product Defect

Lingue:

Questo articolo è disponibile nelle seguenti lingue:

English United States
Spanish Spain
French
Italian
Portuguese Brasileiro

Glossario dei termini tecnici

Evidenzia termini glossario

Ti consigliamo di consultare il nostro Glossario dei termini tecnici.

Knowledge Center

How to troubleshoot communication issues between ePolicy Orchestrator and the vCenter

Ambiente

Riepilogo

Problema

Causa

Soluzione

Prodotti interessati

Lingue:

Glossario dei termini tecnici

Title

Title

Knowledge Center

How to troubleshoot communication issues between ePolicy Orchestrator and the vCenter

Ambiente

Riepilogo

Problema

Causa

Soluzione

Prodotti interessati

Lingue:

Glossario dei termini tecnici

Scegli la regione

Title

Title