[[["易于理解","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,["# Classic VPN dynamic routing deprecation\n\nDynamic routing or Border Gateway Protocol (BGP) for Classic VPN\ntunnels is deprecated on August 1, 2025. If your workloads require BGP\nfor VPN connectivity, you must use HA VPN.\n\nFor information about HA VPN, see the\n[Cloud VPN overview](/network-connectivity/docs/vpn/concepts/overview#ha-vpn).\n\nThe rest of this page helps you with planning and implementing your\nmigration.\n\nDeprecated configurations\n-------------------------\n\nYou cannot create new Classic VPN tunnels that use dynamic routing\n(BGP) that is managed by a Cloud Router.\n\nAs of August 1, 2025, the creation of Classic VPN tunnels\nusing dynamic routing (BGP) is no longer supported, regardless of the gateway\nthe tunnel connects to. This includes connections to VPN gateway software running\ninside a Compute Engine virtual machine (VM) instance or connections\noutside of Google Cloud.\n\nExisting Classic VPN tunnels that use dynamic routing (BGP)\nare not supported. While tunnels that are in use will continue to function,\nbut without an availability SLA.\n\n### What happens to deprecated configurations?\n\nIf you delete a Classic VPN tunnel that was configured with BGP, you won't be\nable to recreate it with BGP support. While existing, unmodified\nClassic VPN tunnels may continue to pass traffic (without SLA).\nYou must use HA VPN for any changes requiring recreation\nor modification of BGP settings configurations.\n\nSupported configurations\n------------------------\n\nYou can continue to create and receive support only for the following\nClassic VPN configurations:\n\n- Classic VPN tunnels using static routing from Classic VPN gateways to on-premises VPN gateways and from on-premises VPN gateways to Classic VPN gateways.\n- Classic VPN tunnels using static routing from a Classic VPN gateway to and from a Compute Engine VM that is acting as a VPN gateway.\n\nRecommendations\n---------------\n\nFor all production traffic requiring dynamic routing (BGP),\nuse HA VPN.\n\nWe recommend that you only retain Classic VPN if your\non-premises VPN devices don't support BGP, and therefore HA VPN\ncannot be used. However, we strongly recommend upgrading those devices to\nsupport BGP, as HA VPN provides a more flexible, reliable,\nand highly available solution compared to static routing, and is the only path\nfor BGP functionality within Cloud VPN.\n\nFor more information, see\n[HA VPN topologies](/network-connectivity/docs/vpn/concepts/topologies).\n\nBilling changes\n---------------\n\nAfter instantiating and using the additional, redundant tunnel for\nHA VPN, you will see billing changes as described on\nthe [Cloud VPN pricing page](/network-connectivity/docs/vpn/pricing).\n\nTo achieve high availability, HA VPN requires you to\ncreate VPN tunnels in pairs. Both tunnels are billed at the same hourly rate.\nIf you use one tunnel solely for failover, outbound data transfer charges apply\nonly to the active tunnel.\n\nAs of August 1, 2025, any traffic that has not been migrated to HA VPN\nand continues to flow through established Classic VPN gateways\nand tunnels will be charged at the standard Classic VPN rates.\n\nMove to HA VPN\n--------------\n\nTo move to HA VPN, you might need to make some routing or\ninfrastructure changes to support HA VPN. Your network\nadministrators or [site reliability engineers (SREs)](https://sre.google/)\nneed to schedule a [maintenance window](/network-connectivity/docs/vpn/how-to#maintaining-vpns)\nto perform the migration.\n\nTo plan and prepare, watch the following video,\n*Upgrade to Google's HA VPN*,\nfor guidance on key use cases.\n\nWhen your organization is ready to switch your production workflows from\nClassic VPN to HA VPN, use the checklists\nand instructions provided in [Move to HA VPN](/network-connectivity/docs/vpn/how-to/moving-to-ha-vpn). \n\nWhere to get help\n-----------------\n\nIf you have any questions or require assistance, [contact\nGoogle Cloud Support](/network-connectivity/docs/vpn/support/getting-support)."]]