Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

HCX - Site Pairing Connectivity Diagnostics (78340)

Last Updated: 6/14/2023Categories: TroubleshootingTotal Views: 15790Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

HCX Site Pairing not getting established after initial configuration or going down unexpectedly after being in service before.

Purpose

Provide troubleshooting steps to isolate common infrastructure issues that may impact HCX Site Pairing communication between HCX Connector and Cloud Manager.
The same steps are applicable for HCX Cloud to Cloud Site Pairings but access restrictions may apply from the Cloud Provider.

Cause

Site Pairing connectivity between HCX Managers will depend entirely on the underlying network infrastructure, so problems with basic routing, firewall configuration, or proxy settings can disrupt that communication.

Impact / Risks

If the Site Pairing is down, configuration workflows will fail and no migrations can be scheduled from HCX Connector or source Cloud Manager.
Existing Network Extension services will remain active indefinitely but no configuration changes can be made on those, except for "unstretch", which can be forced from the target HCX Cloud Manager's side.

Resolution

When Site Pairing is down or not getting established for the first time, check the following:

Date and Time should be the in sync on both HCX Managers, depending on the timezone for each system.

Verify NTP configuration on both HCX Managers.

Verify DNS resolution is working as expected.

Ensure the right vCenter credentials are used for the respective remote HCX Cloud Manager.

Site Pairing to an HCX Cloud Manager in a VMware Cloud on AWS SDDC must use "cloudadmin" credentials.

The HCX Cloud Manager local "admin" account can NOT be used for Site Pairing authentication.

SSH into the HCX Connector or Cloud Manager to test connectivity to the remote HCX Cloud Manager's URL over TCP 443. There will be a clear indication of a successful SSL/HTTP session:

curl -k -v https://<HCX_Manager_FQDN>

* Trying X.X.X.X...
* TCP_NODELAY set
* Connected to <HCX_Manager_FQDN> (X.X.X.X) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=California; L=Palo Alto; O=VMware, Inc; OU=Hybridity; CN=<HCX_Manager_FQDN>
* start date: Jun 18 05:42:30 2021 GMT
* expire date: Jun 18 05:42:27 2022 GMT
* issuer: C=US; O=Entrust, Inc.; OU=See www.entrust.net/legal-terms; OU=(c) 2012 Entrust, Inc. - for authorized use only; CN=Entrust Certification Authority - L1K
* SSL certificate verify ok.
> GET / HTTP/1.1
> Host: <HCX_Manager_FQDN>
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 302
< Date: Wed, 20 Apr 2022 18:13:26 GMT
< Server: Apache
< Location: https://<HCX_Manager_FQDN>/hybridity/ui/hcx-client/index.html
< Content-Length: 0
< Content-Security-Policy: style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data:
<
* Connection #0 to host <HCX_Manager_FQDN> left intact
* Closing connection 0

If above test fails, ensure TCP 443 communication is allowed between HCX Managers:

Check Firewall and/or DFW configuration.

Check Proxy settings on the source side.

If using a Proxy, only Basic Authentication is supported. Kerberos or any other type are not supported.

If there is an error message in the HCX UI about an untrusted connection, add the remote HCX Manager or the Proxy server certificate to the source HCX Connector or Cloud Manager via the HCX AUI. Refer to Managing CA and Self-Signed Certificates

IMPORTANT:  By default, when a Proxy server is configured, the Connector or Cloud Manager uses it for all HTTPS connections ( including communication to local vCenter Server, ESXi, NSX, and HCX IX and NE appliances over the Management Network ) therefore, required entries in the Exclusion list must be included to allow direct access to local network resources. Also, app and web engines restart is required for any changes in the Proxy configuration to take effect.

Ensure there is no asymmetric routing by running "traceroute" from the HCX Connector or Cloud Manager via SSH. This command requires "root" access for execution.

IMPORTANT: SSH access to the HCX Cloud Manager in an SDDC may be restricted by the Cloud Provider. This option may only be run from HCX Connector in those cases.

# su - root
# traceroute <HCX_Cloud_Manager_IP>

Try re-registering it using the HCX UI.

Try re-creating it using the HCX UI.

Refer to the HCX User Guide for Site Pairing configuration details.

Workaround

There is no workaround to have full HCX services availability without Site Pairing connectivity between Data Center sites.

Related Information

HCX site pairing fails with error "NumberFormatException" (80210)
HCX - Site pairing disconnected with "Error queuing Job: Workflow ReplicationTransferJob" (81978)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
在“vpxd 首次引导”期间，vCenter Server Appliance 从 6.5 升级到 6.7 失败 (76970)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware HCX

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant