[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Connecting from an on-premises network to VMware Engine standard or stretched private cloud\n\nConnecting from an on-premises network to VMware Engine\nstandard or stretched private cloud\n===========================================================================================\n\nGoogle Cloud VMware Engine enables key use cases such as data center lift and shift,\ndata center extension, and disaster recovery. These use cases require that you\nestablish connectivity from your on-premises network to Google Cloud and your\nVMware Engine network.\n\nConnecting from your on-premises network to VPC network\n-------------------------------------------------------\n\nGoogle Cloud offers multiple hybrid connectivity options such as\n[Cloud VPN](/network-connectivity/docs/vpn) and [Cloud Interconnect](/network-connectivity/docs/interconnect).\nFollow the links to learn how to set up Cloud VPN or\nCloud Interconnect (Dedicated and Partner Interconnect) connections\nwith your Virtual Private Cloud (VPC) network. If you have already connected\nyour on-premises network to a VPC network, you can use this\nconnection for this step.\n| **Warning:** Use of HCX requires either Cloud VPN or Cloud Interconnect-based connectivity between your on-premises network and your VMware Engine network.\n\nConnect from your VPC network to VMware Engine\n----------------------------------------------\n\nThe connection from your VPC network to a\nVMware Engine differs based on whether you use standard or legacy\nnetworks.\n\n### Standard VMware Engine networks\n\nThe connection from your VPC network to a Standard\nVMware Engine network uses\n[VPC Network Peering](/vmware-engine/docs/networking/peer-vpc-network).\n\n### Legacy VMware Engine networks\n\nThe connection from your VPC network to a\nLegacy VMware Engine network uses\n[private services access](/vpc/docs/configure-private-services-access).\nTo access your workload virtual machines (VMs) from an on-premises network or\nfrom your VPC network,\n[set up private services access from your\nVPC network to your VMware Engine network](/vmware-engine/docs/networking/howto-setup-private-service-access).\n\nEnd-to-end connectivity and routing considerations\n--------------------------------------------------\n\nTo allow a VMware Engine regional network to reach on-premises\nnetworks, you must enable **Import/export custom routes** on the\nVPC network peering connection associated with the private\nservices access. This enables routes that are advertised from on-premises to the\nVPC network to be propagated to the VMware Engine\nregion.\n\nWhen you use Cloud VPN for on-premises connection to the\nVPC network, you must add VMware Engine networks to\nthe [Cloud VPN tunnel](/network-connectivity/docs/vpn/concepts/choosing-networks-routing).\n\nWhen you use Cloud Interconnect for on-premises connection to the\nVPC network, you can [add custom routes](/network-connectivity/docs/router/how-to/advertising-custom-ip)\nto the Cloud Router that terminates the Cloud Interconnect\nattachment.\n\nMigrating VMs from on-premises to stretched private clouds\n----------------------------------------------------------\n\nYou can continue to use the same migration tools for on-premises to\nGoogle Cloud VMware Engine VM migrations for both standard private clouds and stretched\nprivate cloud destinations. VMware HCX is the default tool for VM migrations and\ncomes bundled with the service.\n\nHCX Cloud Manager is deployed automatically to the primary zone when a stretched\nprivate cloud is created. When an HCX service mesh is created, you can use\naffinity rules to ensure that the HCX service appliances are created in the\nprimary zone.\n\nAfter a site-level failover (in the case of a complete zone failure), the HCX\nManager and service appliances are started on the surviving zone."]]
