Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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 - Mobility Agent deployment fails with vCenter certificate management set to "custom" mode (79003)

Last Updated: 7/17/2023Categories: Known IssueTotal Views: 8736Language:
English

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

HCX Service Mesh configuration workflow fails deploy Mobility Agent (MA) virtual host with error message:

applianceLifecycyle job failed | intercocnnectConfigMA failed |error Adding Mobility Agent Host failed |SSL Exception.

From the vCenter Monitor Tasks, the HCX attempt to deploy MA host failing at ~80%

This issue will not impact the deployment of HCX Interconnect (IX) and Network Extension (NE) appliances.

vCenter vpxd logs will show the following error message:

ERROR c.v.v.h.s.i.InterconnectConfigureMA- Task task-124498 error out, error : A general system error occurred: SSL  Exception: Verification parameters:
PeerThumbprint: A3:04:3B:CC:3D:1B:18:5B:DB:9B:E9:B2:57:D6:E4:88:39:4E:C2:B1
ExpectedThumbprint:
ExpectedPeerName: 10.1.1.1
The remote host certificate has these problems:
* Host name does not match the subject name(s) in certificate.
* unable to get local issuer certificate
com.vmware.vim.binding.vmodl.fault.SystemError: A general system error occurred: SSL Exception: Verification parameters:
PeerThumbprint: A3:04:3B:CC:3D:1B:18:5B:DB:9B:E9:B2:57:D6:E4:88:39:4E:C2:B1
ExpectedThumbprint:
ExpectedPeerName: 10.1.1.1
The remote host certificate has these problems:
* Host name does not match the subject name(s) in certificate.

Purpose

Identify a known limitation and provide an alternative method for HCX deployment.

Cause

The issue will occur if vCenter is configured with Certificate Management policy set to "Custom" mode "vpxd.certmgmt.mode"

HCX MA virtual host must be added by HCX Manger into vCenter but since the IX appliance uses self-signed certificate, vCenter will reject the addition of the MA into the cluster.

Impact / Risks

The failure to deploy the MA will disable HCX Cold, vMotion, and RAV migration services.
VR Bulk migrations and DR Protections do not require MA.
There is no risk in implementing the recommended workaround as there is no impact to Network Extension services.

Resolution

HCX MA deployment in a vCenter environment with Certificate Management set to "Custom" mode is NOT supported.
Alternatively the recommended workaround can be implemented and that has been thoroughly verified, yet it has some restrictions for persistency.
Support for the the implementation of the workaround is provided as a best effort.

Workaround

The following procedure will replace the IX appliance certificate and key.
It will have to be performed for each Interconnect appliance that is deployed in a vCenter with 'custom' certificate management.

SSH into the HCX Manager as 'admin'

Enable CCLI mode

LIST the appliances and GO <appliance_ID> into the IX appliance

SSH to drop into the linux prompt

Change directory to /etc/vmware/ssl

Backup certificate files:

mv rui.crt rui.crt.bak
mv rui.key rui.key.bak

​​Replace the files with the custom CA cert and key

Reboot the IX appliance or restart the MA and authentication services

stc restart mobilityagent
stc restart authdlauncher

From the HCX Interconnect UI, re-sync the Service Mesh to trigger the MA deployment

IMPORTANT: This workaround will not be persistent if the Service Mesh is re-sync'ed or after service updates. The same procedure will have to be performed to re-deploy the MA again.

The following considerations should be taken into account:

As this is a custom CA cert to be trusted by vCenter, it must be generated in the same manner that the existing ESXi host certificates have been generated for this environment.

Ensure the 'CN' and 'SAN' fields of the certificate contain the IP address that is intended to be used for the management IP of the IX appliance.

If the certificate generated by the CA is provided as a cert.pem file, make sure the certificate chain (including target, intermediate, and root certificates) and private key aspects are separated into the rui.cert and rui.key files.

Related Information

Refer to the following VMware KB articles for more information on how to request and configure CA signed certificates for ESXi hosts

KB 2113926

KB 2015387

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Intelligence for Consumer Apps 2020/05/06 リリースのお知らせ (78963)

KB
•
VMware AirWatch Relay Service 4.3 for Android リリースのお知らせ (79016)

KB
•
VMware Workspace ONE Intelligent Hub 20.04 for Android リリースのお知らせ (78888)

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

Related Versions:

Take Our Survey

Support Assistant