Cross Cloud Mobility for VMware Cloud Foundation
Establishes business workload mobility and migrates workloads between a VMware Cloud Foundation instance and a VMware Cloud on AWS SDDC using the VMware HCX service. HCX extends on-premises networks to VMware Cloud on AWS, enabling live migration with no re-IP. Main objective is to provide the ability to move business workloads between an on-premises VCF platform and a VMware Cloud platform (hybrid cloud).
Key Components: VMware HCX (HCX Connector, HCX Cloud Manager, IX/NE Service Mesh appliances), VMware Cloud on AWS (mobility SDDC), vCenter Server, NSX Manager, ESXi
Logical Design: Two-site hybrid: VMware Cloud Foundation (on-premises private cloud) with vCenter Server, ESXi clusters, and HCX Connector appliance; VMware Cloud on AWS (public cloud) with vCenter Server, ESXi clusters, and HCX Manager (HCX Cloud). A unidirectional site pairing is created from the on-prem HCX Connector to HCX Cloud, and a Service Mesh deploys interconnect-dedicated HCX appliances at each site to provide network extension, vMotion, bulk migration, and replication services.
47 design decisions. The Quality column is the Academy's assessment for defence practice; the VVS documents do not classify decisions by design quality (D133).
| DD-ID | Decision | Quality (Academy view) |
|---|---|---|
| CCM-CDP-CFG-001 | Deploy the HCX Connector appliance in the default management vSphere cluster. | Availability |
Decision: Deploy the HCX Connector appliance in the default management vSphere cluster. Rationale: Required to establish secure communication between the VMware Cloud Foundation instance and VMware HCX. Implication: The HCX Connector must be able to connect to the internet through a firewall. Component: CDP | ||
| CCM-CDP-CFG-002 | Protect the HCX Connector appliance by using vSphere High Availability. | Availability |
Decision: Protect the HCX Connector appliance by using vSphere High Availability. Rationale: Supports the availability objective without requiring manual intervention during an ESXi host failure. Implication: None. Component: CDP | ||
| CCM-CDP-CFG-003 | Place the HCX Connector appliance in a designated virtual machine folder. | Manageability |
Decision: Place the HCX Connector appliance in a designated virtual machine folder. Rationale: Provides organization of the appliances in the management domain vSphere inventory. Implication: You must create the virtual machine folder before or during deployment. Component: CDP | ||
| CCM-CDP-CFG-004 | When using two availability zones, add the HCX Connector appliance to the VM group of the first… | Availability |
Decision: When using two availability zones, add the HCX Connector appliance to the VM group of the first availability zone. Rationale: Ensures that the HCX Connector appliance runs in the primary availability zone hosts group. Implication: After the implementation of the second availability zone for the management domain, you must update the VM group for the primary availability zone virtual machines to include the HCX Connector appliance. Component: CDP | ||
| CCM-CDP-NET-001 | Place the HCX Connector appliance on the management VLAN. | Manageability |
Decision: Place the HCX Connector appliance on the management VLAN. Rationale: • Places the HCX Connector on the same network as the VMware Cloud Foundation components that the appliance must communicate with. • Provides a consistent deployment model for VMware Cloud Services. Implication: None. Component: CDP | ||
| CCM-CDP-NET-002 | Allocate statically assigned IP addresses from the management VLAN to the HCX Connector appliance. | Manageability |
Decision: Allocate statically assigned IP addresses from the management VLAN to the HCX Connector appliance. Rationale: Using statically assigned IP addresses ensures stability of the deployment and simplifies maintenance and tracking. Implication: Requires precise IP address management. Component: CDP | ||
| CCM-CDP-NET-003 | Configure forward and reverse DNS records for the HCX Connector appliance IP address. | Manageability |
Decision: Configure forward and reverse DNS records for the HCX Connector appliance IP address. Rationale: Ensures the appliance is accessible by using a fully qualified domain name instead of using IP addresses only. Implication: • You must provide a DNS record for the appliance IP address. • Firewalls between the appliance and the DNS servers must allow DNS traffic. Component: CDP | ||
| CCM-CDP-NET-004 | Configure DNS servers on the HCX Connector appliance. | Manageability |
Decision: Configure DNS servers on the HCX Connector appliance. Rationale: Ensures the appliance has accurate name resolution. Implication: • DNS infrastructure services must be highly available in the environment. • Firewalls between the appliance and the DNS servers must allow DNS traffic. • You must provide two or more DNS servers unless a DNS geographic load balancing is active. Component: CDP | ||
| CCM-CDP-NET-005 | Configure NTP servers for the HCX Connector appliance. | Manageability |
Decision: Configure NTP servers for the HCX Connector appliance. Rationale: • Ensures that the appliance has accurate time synchronization. • Assists in the prevention of time mismatch between the appliance and dependencies. Implication: NTP infrastructure services must be highly available in the environment. Firewalls between the appliance and the NTP servers must allow NTP traffic. You must provide two or more NTP servers unless an NTP geographic load balancing is active. Component: CDP | ||
| CCM-AWS-CFG-001 | Deploy a VMware Cloud on AWS mobility SDDC with a minimum of two nodes. | Manageability |
Decision: Deploy a VMware Cloud on AWS mobility SDDC with a minimum of two nodes. Rationale: Ensures that the preprovisioned mobility SDDC remains available. A single node expires after 60 days. Implication: A pre-provisioned mobility SDDC consumes infrastructure that incurs a regular charge. Component: AWS | ||
| CCM-AWS-CFG-002 | Configure the management gateway to allow access to VMware Cloud on AWS mobility SDDC vCenter… | Manageability |
Decision: Configure the management gateway to allow access to VMware Cloud on AWS mobility SDDC vCenter Server over the internet. Rationale: Ensures users can access the vCenter Server UI of the mobility SDDC over the internet. Implication: You must manually manage access to the vCenter Server by using an NSX group. Component: AWS | ||
| CCM-HCX-CFG-001 | Register the HCX Connector with the VI workload domain vCenter Server. | Manageability |
Decision: Register the HCX Connector with the VI workload domain vCenter Server. Rationale: Registering the HCX Connector with vCenter Server installs the plug-ins to integrate HCX with vCenter Server. Implication: None. Component: HCX | ||
| CCM-HCX-CFG-002 | Register the HCX Connector with the VI workload domain NSX Manager. | Manageability |
Decision: Register the HCX Connector with the VI workload domain NSX Manager. Rationale: Registering the HCX Connector with NSX Manager is required to enable the networking configuration. Implication: None. Component: HCX | ||
| CCM-HCX-CFG-003 | Register the HCX Connector with the Single Sign-On Domain of the VI workload domain vCenter Server. | Security |
Decision: Register the HCX Connector with the Single Sign-On Domain of the VI workload domain vCenter Server. Rationale: By registering the HCX Connector with Single SignOn, you can create dedicated VMware HCX roles within vCenter Server. Implication: None. Component: HCX | ||
| CCM-HCX-CFG-004 | Pair the HCX Connector with the HCX Cloud service. | Manageability |
Decision: Pair the HCX Connector with the HCX Cloud service. Rationale: Required to establish unidirectional communication between the VMware Cloud Foundation instance and the HCX Cloud service to create a Service Mesh. Implication: • The HCX Connector must be able to connect to the internet through a firewall. • You can also establish connectivity through a proxy server which you would need to configure outside of this solution. Component: HCX | ||
| CCM-HCX-CFG-005 | Create a management network profile using the management network distributed switch port group and… | Manageability |
Decision: Create a management network profile using the management network distributed switch port group and assign Management and HCX Uplink traffic types. Rationale: Provides management network configuration details used when deploying VMware HCX service appliances. Implication: None. Component: HCX | ||
| CCM-HCX-CFG-006 | Assign the management network profile a pool of 5 IP address from the VI workload domain management… | Manageability |
Decision: Assign the management network profile a pool of 5 IP address from the VI workload domain management VLAN. Rationale: Provides a pool of IP addresses that can dynamically be assigned to the VMware HCX service appliances. Implication: Requires the allocation of a static pool of IP addresses from the VI workload domain management VLAN. Component: HCX | ||
| CCM-HCX-CFG-007 | Create a vMotion network profile using the vMotion network distributed switch port group and assign… | Manageability |
Decision: Create a vMotion network profile using the vMotion network distributed switch port group and assign vMotion traffic type. Rationale: Provides vMotion network configuration details used when deploying VMware HCX service appliances. Implication: None. Component: HCX | ||
| CCM-HCX-CFG-008 | Assign the vMotion network profile a pool of 5 IP addresses from the VI workload domain vMotion… | Manageability |
Decision: Assign the vMotion network profile a pool of 5 IP addresses from the VI workload domain vMotion VLAN. Rationale: Provides a pool of IP addresses that can dynamically be assigned to the VMware HCX service appliances. Implication: Requires the allocation of a static pool of IP addresses from the VI workload domain vMotion VLAN. Component: HCX | ||
| CCM-HCX-CFG-009 | Create a compute profile and activate all available VMware HCX services. | Manageability |
Decision: Create a compute profile and activate all available VMware HCX services. Rationale: Provides the compute, storage, and network settings that VMware HCX uses to deploy the interconnect-dedicated appliances when a Service Mesh is added. Implication: Services that can be activated are dependent on the VMware HCX license applied during the activation of the HCX Connector. Component: HCX | ||
| CCM-HCX-CFG-010 | Assign the VI workload domain cluster as a resource to the compute profile. | AvailabilityPerformance |
Decision: Assign the VI workload domain cluster as a resource to the compute profile. Rationale: Provides compute capacity for the interconnect-dedicated appliances when a Service Mesh is added. Implication: None. Component: HCX | ||
| CCM-HCX-CFG-011 | Assign a vSphere resource pool as a container to the compute profile. | Manageability |
Decision: Assign a vSphere resource pool as a container to the compute profile. Rationale: Provides a container to group the interconnectdedicated appliances and the ability to configure resource priorities. Implication: You must manually create a resource pool before configuring the compute profile. Component: HCX | ||
| CCM-HCX-CFG-012 | Assign a virtual machine folder as a container to the compute profile. | Manageability |
Decision: Assign a virtual machine folder as a container to the compute profile. Rationale: Provides organization of the appliances in the management domain vSphere inventory. Implication: You must manually create a virtual machine folder before configuring the compute profile. Component: HCX | ||
| CCM-HCX-CFG-013 | Assign the management and vMotion network profiles to the compute profile. | Manageability |
Decision: Assign the management and vMotion network profiles to the compute profile. Rationale: Provides network settings for the interconnect-dedicated appliances when a Service Mesh is added. Implication: None. Component: HCX | ||
| CCM-HCX-CFG-014 | Create a Service Mesh between the VMware Cloud Foundation instance and VMware Cloud on AWS SDDC. | Manageability |
Decision: Create a Service Mesh between the VMware Cloud Foundation instance and VMware Cloud on AWS SDDC. Rationale: Provides an interconnect between on-premises and the VMware Cloud on AWS environments to enable extending VMware Cloud Foundation networks to facilitate workload mobility without the need to re-IP application virtual machines. Implication: None. Component: HCX | ||
| CCM-CDP-LCM-001 | Manually upgrade the HCX Connector appliance using the built-in tools. | Manageability |
Decision: Manually upgrade the HCX Connector appliance using the built-in tools. Rationale: An upgrade package must be downloaded and applied to the HCX appliance to perform an upgrade. Implication: None. Component: CDP | ||
| CCM-CDP-LCM-002 | Use the VMware Cloud Services automatic over-the-air service to perform the upgrades to the HCX… | Manageability |
Decision: Use the VMware Cloud Services automatic over-the-air service to perform the upgrades to the HCX Connector appliance. Rationale: The VMware HCX service pushes upgrades automatically. Implication: None. Component: CDP | ||
| CCM-IAM-SEC-001 | Limit the use of local accounts for interactive or API access, and solution integration. | SecurityManageability |
Decision: Limit the use of local accounts for interactive or API access, and solution integration. Rationale: Local accounts are not specific to user identity and do not offer complete auditing from an endpoint back to the user identity. Implication: You must define and manage service accounts, security groups, group membership, and security controls in Active Directory. Component: IAM | ||
| CCM-IAM-SEC-002 | Limit the scope and privileges for accounts used for interactive or API access, and solution… | SecurityManageability |
Decision: Limit the scope and privileges for accounts used for interactive or API access, and solution integration. Rationale: The principle of least privilege is a critical aspect of access management and must be part of a comprehensive defense-in-depth security strategy. Implication: You must define and manage custom roles and security controls to limit the scope and privileges used for interactive access or solution integration. Component: IAM | ||
| CCM-IAM-SEC-003 | Assign VMware Cloud on AWS service roles to designated users. | Security |
Decision: Assign VMware Cloud on AWS service roles to designated users. Rationale: To provide access to the VMware Cloud on AWS service, you assign users to service roles. Implication: You must maintain the service roles required for users of your organization. Component: IAM | ||
| CCM-IAM-SEC-004 | Assign VMware HCX service roles to designated users. | Security |
Decision: Assign VMware HCX service roles to designated users. Rationale: To provide access to the VMware HCX service, you assign users to service roles. Implication: You must maintain the service roles required for users of your organization. Component: IAM | ||
| CCM-IAM-SEC-005 | Define a custom vCenter Server role for VMware HCX with minimum privileges required to support the… | Security |
Decision: Define a custom vCenter Server role for VMware HCX with minimum privileges required to support the registration of a vCenter Server. Rationale: VMware HCX integrates with each VI workload domain vCenter Server instance using a minimum set of privileges required to support registration and management. Implication: • You must maintain the privileges required by the custom vSphere role. • If additional VI workload domain vCenter Server instances are not in the same vCenter Single Sign-On domain, you must apply the custom role to each vCenter Single Sign-On domain. Component: IAM | ||
| CCM-IAM-SEC-006 | Assign the custom vCenter Server role to an Active Directory user account as a service account for… | AvailabilitySecurityManageability |
Decision: Assign the custom vCenter Server role to an Active Directory user account as a service account for each VI workload domain vCenter Server instance for application-to-application communication between VMware HCX and vCenter Server. Rationale: • Provides integration and data collection of objects managed by the vCenter Server for a given VI workload domain. • Limiting the use of a service account reduces the risk in the case of either a security or a password-related event. • Using a named Active Directory account provides for auditability unlike generic administrative accounts. Implication: You must maintain the life cycle, availability, and security controls for the account in Active Directory. Component: IAM | ||
| CCM-IAM-SEC-007 | Assign the default Enterprise Admin role in NSX Manager to a service account for each VI workload… | Security |
Decision: Assign the default Enterprise Admin role in NSX Manager to a service account for each VI workload domain NSX Manager instance for application-to-application communication between VMware HCX and NSX. Rationale: VMware HCX integrates with each VI workload domain NSX Manager instance using a minimum set of privileges required to support registration and management. Implication: None. Component: IAM | ||
| CCM-IAM-SEC-008 | Configure the local user password expiration policy for each HCX Connector appliance. | Security |
Decision: Configure the local user password expiration policy for each HCX Connector appliance. Rationale: • You configure the local user password expiration policy for each HCX Connector appliance to align with the requirements of your organization which might be based on industry compliance standards. • The local user password expiration policy is applicable to the root and admin accounts for the HCX Connector appliance. Implication: You must manage the local user password expiration settings on each HCX Connector appliance by using the appliance console. Component: IAM | ||
| CCM-IAM-SEC-009 | Configure the local user password complexity policy for each HCX Connector appliance. | Security |
Decision: Configure the local user password complexity policy for each HCX Connector appliance. Rationale: • You configure the local user password complexity policy for each HCX Connector appliance to align with the requirements of your organization which might be based on industry compliance standards. • The local user password complexity policy is applicable only to the local HCX Connector appliance users. Implication: You must manage the local user password complexity settings on each HCX Connector appliance by using the appliance console. Component: IAM | ||
| CCM-IAM-SEC-010 | Configure the local user account lockout policy for each HCX Connector appliance. | Security |
Decision: Configure the local user account lockout policy for each HCX Connector appliance. Rationale: • You configure the local user account lockout policy for each HCX Connector appliance to align with the requirements of your organization which might be based on industry compliance standards. • The local user account lockout policy is applicable only to the local HCX Connector appliance users. Implication: You must manage the local user account lockout settings on each HCX Connector appliance by using the appliance console. Component: IAM | ||
| CCM-IAM-SEC-011 | For each vCenter Server, change the VMware HCX service account password on a recurring or… | Security |
Decision: For each vCenter Server, change the VMware HCX service account password on a recurring or event-initiated schedule. Rationale: To maintain a secure platform, you must rotate the VMware HCX service account passwords on a regular basis Implication: Performing password rotation for a service account is a manual process. You update the associated credentials in the HCX Connector appliance. Component: IAM | ||
| CCM-IAM-SEC-012 | For each NSX Manager, change the VMware HCX service account password on a recurring or… | Security |
Decision: For each NSX Manager, change the VMware HCX service account password on a recurring or event-initiated schedule. Rationale: To maintain a secure platform, you must rotate the VMware HCX service account passwords on a regular basis. Implication: Performing password rotation for a service account is a manual process. You update the associated credentials in the HCX Connector appliance. Component: IAM | ||
| CCM-IAM-SEC-013 | Change the HCX Connector appliance root and admin passwords on a recurring or event-initiated… | Security |
Decision: Change the HCX Connector appliance root and admin passwords on a recurring or event-initiated schedule. Rationale: The password for the HCX Connector appliance root and admin accounts never expires based on the default password expiration policy. Implication: You must manage the password change for the root and the admin accounts. You must manage the password change on each HCX Connector appliance by using the virtual appliance console. Component: IAM | ||
| CCM-IAM-SEC-014 | Replace the default self-signed certificate with a CA-signed certificate during the deployment of… | SecurityPerformanceManageability |
Decision: Replace the default self-signed certificate with a CA-signed certificate during the deployment of the HCX Connector appliance. Rationale: Ensures that all communication to the user interface of the HCX Connector appliance is encrypted. Implication: • Replacing the default certificates with a trusted CA-signed certificate increases the deployment preparation time as certificates requests are generated and delivered. • You must manage the life cycle of the certificate replacement. • The SSL certificate key size must be 2048 or 4096 bits. Component: IAM | ||
| CCM-IAM-SEC-015 | Use an SHA-2 or higher algorithm when signing certificates. | Security |
Decision: Use an SHA-2 or higher algorithm when signing certificates. Rationale: The SHA-1 algorithm is considered less secure and is deprecated. Implication: Not all certificate authorities support SHA-2. Component: IAM | ||
| CCM-IAM-SEC-016 | Rotate the CA-signed certificate of the HCX Connector appliance on a recurring or event-initiated… | SecurityPerformanceManageability |
Decision: Rotate the CA-signed certificate of the HCX Connector appliance on a recurring or event-initiated schedule. Rationale: Ensures that all communication to the user interface of the HCX Connector appliance and between the components continues to be encrypted with a non-expired or noncompromised certificate. Implication: • Replacing the default certificates with a trusted CA-signed certificates might require preparation time as certificates requests are generated and delivered. • You must continue to manage the life cycle of the certificate replacement. • The SSL certificate key size must be 2048 or 4096 bits. Component: IAM | ||
| CCM-MON-IOM-001 | Add a Ping adapter for the HCX Connector appliance. | Availability |
Decision: Add a Ping adapter for the HCX Connector appliance. Rationale: Provides metrics on the availability of the HCX Connector appliance. Implication: You must add the adapter instances manually. Component: MON | ||
| CCM-MON-IOM-002 | Configure the Ping adapter for the HCX Connector appliance to use the local-instance collector… | Availability |
Decision: Configure the Ping adapter for the HCX Connector appliance to use the local-instance collector group. Rationale: Offloads data collection for local management components from the analytics cluster. Implication: None. Component: MON | ||
| CCM-BCK-HCX-001 | Configure an FTP server using the SFTP protocol as a target for the HCX Connector. | Recoverability |
Decision: Configure an FTP server using the SFTP protocol as a target for the HCX Connector. Rationale: Provides an external target for storing backup sets. Implication: An external FTP server supporting SFTP must be available in the environment. Component: BCK | ||
| CCM-BCK-HCX-002 | Configure a backup schedule for the HCX Connector. | Recoverability |
Decision: Configure a backup schedule for the HCX Connector. Rationale: Ensures regular backups, which facilitate recovery, are performed. Implication: None. Component: BCK | ||
Prerequisites
- VCF version listed in Support Matrix
- Environment configured per Before You Apply This Guidance
- Cross Cloud Mobility tab of Planning and Preparation Workbook completed
- Healthy VCF instance (see Operations Guide)
- Required DNS forward/reverse records in place
- Active Directory domain controllers available; service accounts created
- Microsoft CA available; CertGenVVS utility downloaded
- VMware Cloud on AWS account with Organization Owner/Administrator role
- HCX licensed and available for download from Customer Connect
- PowerShell module (automated implementation): PowerValidatedSolutions 2.12.0
- PowerShell module (automated implementation): VMware.PowerCLI 13.3.0
- PowerShell module (automated implementation): ImportExcel 7.8.9
- PowerShell module (automated implementation): PowerVCF 2.4.0
Implementation Procedure
Implementation
- Start PowerShell and create folder structure ($drive, $parentFolder, certificates, binaries, generatedJsons)
- Start-ValidatedSolutionMenu with protectedWorkbook path
- Enter 13. (CCM) Cross Cloud Mobility
- Menu 01: Generate JSON Specification File
- Menu 02: Verify Prerequisites
- Menu 05: End-to-End Deployment
- Menu 07: Configuration (solution interoperability)
UI Implementation Steps
- Define custom role in vSphere for HCX integration (least privilege)
- Configure service account permissions in vCenter Server
- Create VM & Template folder for HCX Connector on management domain vCenter
- Create VM & Template folder and resource pool on VI workload domain vCenter for auto-deployed HCX appliances
- Configure service account permissions in NSX Manager (HCX-to-NSX integration)
- Deploy HCX Connector appliance OVA to management domain
- Replace HCX Connector self-signed certificate with CA-signed cert
- (If multi-AZ) Add HCX Connector appliance to first AZ VM group
- Pair on-premises vSphere with HCX Cloud (unidirectional site pairing)
- Create Network Profiles (management and vMotion, with IP pools)
- Create Compute Profile in HCX (activate all services, VI WLD cluster as resource, resource pool, VM folder, both network profiles)
- Create Service Mesh between VCF instance and VMware Cloud on AWS HCX Cloud
High Level Stages
- Plan and prepare VCF environment (P&P Workbook)
- Prepare VCF instance (define custom vSphere role, configure service account permissions, create VM folder)
- Configure VMware Cloud on AWS (deploy mobility SDDC, configure vCenter Server access)
- Configure VMware HCX (deploy HCX to VMC on AWS, deploy HCX Connector appliance, replace self-signed certificate, site pairing, create network profiles, create compute profile, create Service Mesh)
External Services / Integration Points
- Active Directory (authentication/authorization)
- DNS
- NTP
Personas
| Persona | Responsibility | Component role or group |
|---|---|---|
| Cloud Admin | Admin access to the solution environment | Organization Owner; VMware Cloud on AWS Administrator; VMware Cloud on AWS NSX Cloud Admin; VMware HCX Administrator |
| VI Admin | Admin access to cloud and vSphere infrastructure environments | Organization member; VMware HCX Administrator |
Day-2 Operations Tasks
Operational verification — cloud services
After installation, upgrade or outageCheck the VMware Cloud Services status page for VMware Cloud on AWS and HCX; log in to the mobility SDDC vCenter through the management gateway rule (CCM-AWS-CFG-002).
Operational verification — HCX
After installation or upgradeIn the HCX Connector (registered with the VI workload domain vCenter and NSX, CCM-HCX-CFG-001/002) confirm the site pairing to HCX Cloud is Connected, the service mesh and its Interconnect and Network Extension appliances are Up, and a test vMotion or bulk migration completes; network profiles use the management and vMotion pools (CFG-005/008).
Mobility SDDC capacity
MonthlyKeep the VMware Cloud on AWS mobility SDDC at two or more nodes (CCM-AWS-CFG-001) — a one-node SDDC expires after 60 days; review the always-on charge against mobility demand.
HCX Connector upgrade
When HCX releases arriveThe VVS lists both CCM-CDP-LCM-001 (manual upgrade with the built-in tools: download and apply the package) and CCM-CDP-LCM-002 (VMware Cloud Services over-the-air service) for the Connector; each HCX Manager is upgraded from its own Administration > System Updates (HCX 4.8 User Guide, Upgrading the HCX Manager). Snapshot the Connector and verify the service mesh afterwards.
Backup
Daily scheduleConfigure the SFTP target on the HCX Connector and schedule backups (CCM-BCK-HCX-001/002); test a restore to a new appliance.
Certificate and password management
Per policyReplace the Connector certificate with a CA-signed one; rotate the Connector root/admin passwords from the appliance console (CCM-IAM-SEC-013) and the vCenter and NSX service accounts (custom vCenter role, CCM-IAM-SEC-005; NSX account CCM-IAM-SEC-012), updating the registrations afterwards.
Monitoring
ContinuousPing adapter for the HCX Connector in VCF Operations (CCM-MON-IOM-001); watch HCX dashboards for extension tunnel status.
Monitoring Points
- Verify VMware Cloud Services status page: HCX service and SDDC region operational
- Verify HCX Service Mesh via vSphere Client > HCX > Interconnect > Service Mesh tab; all hexagons green
- Verify operational state
- MonitoringConfigure monitoring/alerting via adjacent VVS (see VMware Cloud Foundation Validated Solutions).
Troubleshooting
Likely Panelist Questions
Q: Why a two-node mobility SDDC that is always on?
CCM-AWS-CFG-001: a single-node SDDC expires after 60 days; two nodes keep the mobility target persistent at a regular charge, which is the accepted cost of readiness.
Q: Where does the Connector sit and why?
CCM-CDP-CFG-001/002, CCM-CDP-NET-001: management cluster on the management VLAN, protected by vSphere HA, with controlled internet egress; registered with the VI workload domain vCenter and NSX (HCX-CFG-001/002).
Q: Network extension: overlay or VLAN?
Overlay NSX-backed extension is preferred for feature richness (MON/NET decisions); VLAN extension where the source network is not NSX-backed.
Q: How is the Connector life-cycled?
Manual upgrade with built-in tools (CCM-CDP-LCM-001) or the VMware Cloud Services over-the-air service (LCM-002) as the VVS lists both; SFTP backups (BCK-HCX-001).
Failure Scenarios
Trade-off Analysis
Two-node mobility SDDC vs one-node
Chosen: Two nodes (CCM-AWS-CFG-001)
Justification: Avoids the 60-day expiry of a one-node SDDC; always-on charge accepted.
Manual Connector upgrade vs over-the-air
Chosen: State your reading: VVS lists both LCM-001 and LCM-002 for the Connector
Justification: Manual gives change control; OTA reduces effort; HCX Cloud is service-managed either way.
Overlay NSX-backed extension vs VLAN extension
Chosen: Overlay where the source is NSX-backed
Justification: Richer features (MON, proximity routing); VLAN extension is the fallback.
Quiz — Cross Cloud Mobility
- Dedicated edge workload domain
- VMware Cloud on AWS SDDC
- Management domain default vSphere cluster
- VI workload domain default cluster
- 4 nodes
- 1 node
- 2 nodes
- 3 nodes
- vMotion only
- All four traffic types
- Management only
- Management and HCX Uplink
- 5
- 10
- 2
- 3
- Bidirectional
- Mesh
- Unidirectional from HCX Cloud to HCX Connector
- Unidirectional from HCX Connector to HCX Cloud
- Root password
- NTP configuration
- Self-signed certificate with CA-signed certificate
- SSH host keys
- No action needed
- Deploy a second HCX Connector in AZ2
- Add it to the first AZ VM group
- Clone it to AZ2
- Through Aria Suite Lifecycle
- Only manually, by downloading and applying an upgrade package
- Only by SDDC Manager as part of a VCF upgrade bundle
- The VVS lists both: a manual upgrade with the built-in tools (LCM-001) and the VMware Cloud Services automatic over-the-air service (LCM-002) — state your reading in the design
- 05
- 11
- 07
- 13
- Network profile
- Site pair
- Service Mesh
- Compute profile
- HCX Connector shuts down last
- HCX Connector is left running
- HCX Connector shuts down first
- Only HCX Cloud shuts down
- 90
- 0
- 99999
- -1 (never expires)
- vCenter snapshots and Veeam
- Azure Blob and AWS S3
- NFS and iSCSI
- FTP or SFTP servers
- Registration with the SSO domain of the VI WLD vCenter
- Registration with SDDC Manager
- Registration with NSX Manager
- Registration with vCenter only
- NSX VLAN transport zone
- NSX Federation
- NSX Logical Overlay
- NSX Edge uplink
Flashcards — Cross Cloud Mobility
Labs
Deploy HCX Connector and Site-Pair to HCX Cloud
Deploy HCX Connector in management domain, register with vCenter/NSX/SSO, apply CA-signed cert, and establish unidirectional site pair with HCX Cloud on a VMC on AWS mobility SDDC.
Starting State: Healthy VCF 5.2 instance with VI workload domain; mobility SDDC deployed on VMC on AWS (2+ nodes); CertGenVVS utility ready; AD service accounts created; DNS A/PTR records in place.
- Create HCX custom vSphere role with least privileges
- Assign custom role to HCX service account in VI WLD vCenter
- Create VM folder in management domain vCenter
- Deploy HCX Connector OVA from Content Library to management domain cluster
- Generate CA-signed certificate via CertGenVVS and apply via HCX Connector UI (port 9443)
- Register HCX Connector with VI WLD vCenter, NSX Manager, and SSO
- Log into HCX Cloud on VMC on AWS and note pairing URL
- From HCX Connector, create unidirectional site pair to HCX Cloud
- Verify site pair shows Healthy
Build a Service Mesh for Cross Cloud Mobility
Create management and vMotion network profiles, compute profile, and Service Mesh with all HCX services activated.
Starting State: Site pair established. VM folder and resource pool exist on VI WLD vCenter. Static IP pool of 5 addresses reserved from management VLAN and 5 from vMotion VLAN.
- In HCX UI, create network profile: management DVPG, Management + HCX Uplink traffic types, 5-IP pool
- Create network profile: vMotion DVPG, vMotion traffic type, 5-IP pool
- Create compute profile: activate all services, assign VI WLD cluster, resource pool, VM folder, both network profiles
- Create Service Mesh between VCF and HCX Cloud using the compute profiles on both sides
- Wait for IX and NE appliances to auto-deploy
- Verify Service Mesh tab: all HCX Services hexagons show green
Password Policy Hardening of HCX Connector
Configure password expiration, complexity, and lockout policies on the HCX Connector per organizational security standards.
Starting State: HCX Connector deployed and operational; SSH access as admin enabled.
- SSH as admin; elevate via 'su -'
- Run chage --maxdays 90 root and chage --warndays 14 root for root expiration
- Edit /etc/security/pwquality.conf with sed to set minlen=12, minclass=4, difok=5, retry=3, remember=10
- Enable enforce_for_root in /etc/security/pwhistory.conf
- Edit /etc/security/faillock.conf to set deny=5, unlock_time=900, root_unlock_time=60
- Validate settings with cat commands
- Document new values in runbook