[[["易于理解","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-08-12。"],[],[],null,["# Move from Classic VPN to HA VPN\n\nThis page describes the strategy to move from Classic VPN to\nHA VPN.\n\nFor more information about Cloud VPN, see the\n[Cloud VPN overview](/network-connectivity/docs/vpn/concepts/overview).\n\nFor definitions of terms used on this page, see\n[Key terms](/network-connectivity/docs/vpn/concepts/key-terms).\n\nRequirements\n------------\n\n### General guidelines\n\nConsider the following as you plan a migration to HA VPN:\n\n- Your peer VPN device or service must support the Border Gateway Protocol\n (BGP). If it does not, you cannot use HA VPN.\n\n- The external IP address of your Cloud VPN gateway cannot be\n preserved. When you create an HA VPN gateway, two new\n external IP addresses are created. Google Cloud selects these IP\n addresses from two different pools as part of the high availability (HA)\n design.\n\n- You cannot migrate an existing Cloud VPN tunnel or tunnels on a\n Classic VPN gateway to an HA VPN gateway.\n Instead, you need to create new tunnels and delete the old ones.\n\n- Migrating to HA VPN means that you can only use features\n supported on HA VPN connections. For example, you\n cannot connect a Classic VPN gateway to an\n HA VPN gateway.\n\n### Create Cloud Routers\n\nWhen configuring a new HA VPN gateway, you can create a new\nCloud Router, or you can use an existing Cloud Router with\nexisting Cloud VPN tunnels or VLAN attachments. However, the\nCloud Router that you use must not already manage a BGP session for\na VLAN attachment associated with a Partner Interconnect\nconnection because of the attachment's\n[specific\nASN requirements.](/network-connectivity/docs/interconnect/how-to/partner/creating-vlan-attachments#creating_vlan_attachments)\n\nMigration steps\n---------------\n\nTo move from Classic VPN to HA VPN\ngateways and tunnels, perform the following steps:\n\n1. [Create a new HA VPN gateway, Cloud Router,\n and VPN tunnels](/network-connectivity/docs/vpn/how-to/creating-ha-vpn) to connect your Virtual Private Cloud network to your peer network. The new HA VPN gateway that you create has two new external IP addresses.\n2. [Verify that the new tunnels are working](/network-connectivity/docs/vpn/how-to/checking-vpn-status), and check the configuration of your HA VPN gateway for high availability.\n3. [Delete the tunnel or tunnels](/network-connectivity/docs/vpn/how-to/deleting-a-tunnel) connected to the Classic VPN gateway. If the previous VPN tunnel or tunnels were policy-based or route-based, [remove any leftover custom static routes](/vpc/docs/using-routes#deletingaroute).\n4. [Delete the Classic VPN\n gateway](/network-connectivity/docs/vpn/how-to/deleting-a-gateway#delete-classic-gw) and [release any static external IP addresses](/vpc/docs/reserve-static-external-ip-address#release_ip) that it used.\n\nWhat's next\n-----------\n\n- To use high-availability and high-throughput scenarios or multiple subnet scenarios, see [Advanced configurations](/network-connectivity/docs/vpn/concepts/advanced).\n- To help you solve common issues that you might encounter when using Cloud VPN, see [Troubleshooting](/network-connectivity/docs/vpn/support/troubleshooting)."]]
