The purpose of this article is to show you how to check your HCX deployment via OVHcloud.
Topics
- Access the HCX user interface
- Review the site pairing
- Review VM workload replication
- Review fleet deployments (optional)
- Go further
Requirements
- Your admin username and password for vSphere (which will be used to log in to the HCX interface)
- Your source IP authorized for vCenter access via OVHcloud Control Panel (for instructions, please see our How to Authorize IP Addresses for vCenter Access guide)
Instructions
Access the HCX user interface
There are two ways to check for an HCX deployment: through the vSphere interface or the HCX landing page. In this guide, we will walk you through the workflow on how to check for the HCX deployment via the HCX Cloud landing page.
To access the HCX Cloud landing page, use this format https://hcx.pcc-xxx-xxx-xxx-xxx.ovh.us but substitute the URL for your Private Cloud.
NOTE: Only authorized IPs and users can get access to this page.
Review the site pairing
From the HCX interface, click Site Pairing under the Infrastructure heading in the left-hand navigation menu.
On this screen, you can see all pairings between your on-premises HCX and the cloud HCX. This page does not show the status of replications.
NOTE: You have access to the on-premises and cloud side HCX. OVHcloud can only access the cloud side.
Review VM workload replication
From the HCX interface, click Disaster Recovery under the Services heading in the left-hand navigation menu.
This page will show if your VM workload is being replicated from your vSphere Environment to the HCX Cloud. If this page shows 0 VMs protected, then you have no active replications to OVHcloud.
Review fleet deployments (optional)
NOTE: The Interconnect tab includes a lot of configuration options, which were covered during the HCX deployment in the initial setup of HCX to OVHcloud. Because of this, we are not covering them in detail in this guide.
You can explore this option to understand the Service Mesh topology of compute, networking, and storage. The Interconnect screen will show:
- how the fleets are deployed (Cloud Gateway Appliances on both sides used for replication traffic),
- the networking (Public IPs, Private IPs, VM Kernel Networking, and Management) used on both sides, and
- IP and storage configuration.
If you would like to review your fleet deployments (including Compute Profiles, Service Mesh, and Network Profiles), you can do so by clicking Interconnect under the Infrastructure heading in the left-hand navigation menu.
Go further
Support for HCX Disaster Recovery will end on January 15, 2024, along with NSX-V. OVHcloud has two other Disaster Recovery Plan options: Veeam and Zerto. You can use the resources below to determine which option you would like to use as a replacement for HCX.