Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Intended Audience:HCX(OnPrem, Public/Private Cloud) Administrators or VMware Cloud on AWS AdministratorsBackground:Under certain circumstances, an HCX Administrator may want to decommission an HCX pairing between sites. This document will go over the end-to-end workflow to remove HCX services in both on-premises and cloud scenario. This is the best practice workflow to follow to ensure that a cleaned HCX decommission has been executed.Generally, the workflow is to clean-up from the HCX on-premises side first, then clean-up on the HCX cloud side afterwards.
HCX clean-up procedure:On-premises:1. Go to HCX standalone or vCenter plug-in UI and perform below: a. End, finish or remove any ongoing migrations (under "Migration" tab), or disaster recovery protections (under "Disaster Recovery" tab).b. Unstretch all networks through "Network Extension" tab.c. Go to Interconnect --> Multi-site Service Mesh --> Service Mesh and Select "Delete" button.d. Repeat the "Delete" button action in step 3 if you have more than 1 HCX Service Mesh deployed.e. Select the “Dashboard” tab, and click "Remove" button to remove the HCX cloud site pairing for the intended connector/cloud pair. 2. Unregister HCX plug-ins from the on-premises vCenter via vCenter mob Note A:- If any concerns in making MOB edits to vCenter appliance, you can take a snapshot of your current vCenter Server Appliance VM, before making these changes.Note B:- If your HCX Connector is registered to a production vCenter Server Appliance, then it is suggested that a designated change window can be aligned depending your needs as vsphere-client and vsphere-ui services will be required to be restarted (no longer than 30 minutes).Once precautionary notes A, and B have been acknowledged then proceed with the following mob unregistration steps a. Unregister via <https://vc.on.prem.ip:/mob> and login as administratorb. Go to ExtensionManagerc. Invoke "Unregister" and input strings to uninstall known HCX-plugin extensions com.vmware.hybriditycom.vmware.hybridity.drcom.vmware.hybridity.hcsp-dashboardcom.vmware.hybridity.publishercom.vmware.hybridity.troubleshootingcom.vmware.hybridity.hybrid-interconnect-uicom.vmware.hybridity.auditlog-uicom.vmware.vca.marketing.ngc.uicom.vmware.hybridity.mobility-appcom.vmware.hcsp.alarm d. If HCX plug-in still displays within the vCenter Server Appliance "Menu" button), itwill be necessary to restart vsphere-client and vsphere-ui services for your on-premises vCenter Server Appliance. i. Please execute these service commands to restart the vsphere-ui service (ssh root access to the on- premises vCenter appliance is required) service-control --stop vsphere-uiservice-control --start vsphere-ui Confirm you see the output of:"successfully started service vsphere-ui ii. Please execute these service commands to restart the vsphere-client services (ssh root access to the on-premises vCenter appliance is required) service-control --stop vsphere-clientservice-control --start vsphere-client Confirm you see the output of: successfully started service vsphere-client e. After a few minutes time, please confirm within the on-premises vCenter UI and ensure that the HCX plugin is removed, and proceed to step 3. 3. Power-Off HCX Connector VM and delete from disk along with vCenter Inventory.Public/Private Cloud:Post decommission of HCX connector, we can delete service mesh followed by site pairing removal from cloud(target) HCX UI. a. Go to Interconnect --> Multi-site Service Mesh --> Service Mesh --> Delete and select "Force Delete" option. Note:- Force delete option will try to delete service mesh even if connector site is not reachable. Once there is no response from connector, the cloud manager will proceed to remove all orphan objects related to that site pairing. b. Verify that HCX appliances are removed from vCenter inventory.c. Remove the appliance VMs manually if they haven't been removed successfully.d. Power-off HCX cloud VM and delete from disk. VMware Cloud on AWS(VMC):For the HCX Administrator to gracefully clean-up the cloud side: a. Ensure on-premises HCX components has been completely removed as described above.b. Follow the same process to delete service mesh followed by site pairing removal from VMC cloud HCX UI. Note:- In case of HCX deployment on VMC, the manual removal of HCX cloud manager VM is not allowed by administrator. The HCX admin need to “undeploy” within VMC Console/portal following this workflow: c. Log into VMC portal through https://vmc.vmware.com/d. Select your SDDC Name.e. Select “Integrated Services” and select “OPEN HYBRID CLOUD EXTENSION”.f. Select “Undeploy HCX” link and confirm to remove Cloud HCX Manager from the Cloud vCenter Mgmt-ResourcePool inventory (takes about 10 - 15 minutes for the undeploy to finish).