您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

使用虚拟网络网关 SKU(旧式 SKU)Working with virtual network gateway SKUs (legacy SKUs)

本文包含有关旧式虚拟网络网关 SKU 的信息。This article contains information about the legacy (old) virtual network gateway SKUs. 旧式 SKU 仍可用于已创建的 VPN 网关的两种部署模型。The legacy SKUs still work in both deployment models for VPN gateways that have already been created. 经典 VPN 网关继续使用旧式 SKU,不管是对于现有网关还是对于新网关。Classic VPN gateways continue to use the legacy SKUs, both for existing gateways, and for new gateways. 新建资源管理器 VPN 网关时,使用新的网关 SKU。When creating new Resource Manager VPN gateways, use the new gateway SKUs. 有关新 SKU 的信息,请参阅关于 VPN 网关For information about the new SKUs, see About VPN Gateway.

网关 SKUGateway SKUs

旧版(老版)VPN 网关 SKU 为:The legacy (old) VPN gateway SKUs are:

  • 基本Basic
  • 标准Standard
  • HighPerformanceHighPerformance

VPN 网关不使用 UltraPerformance 网关 SKU。VPN Gateway does not use the UltraPerformance gateway SKU. 有关 UltraPerformance SKU 的信息,请参阅 ExpressRoute 文档。For information about the UltraPerformance SKU, see the ExpressRoute documentation.

使用旧版 SKU 时,请考虑以下方面:When working with the legacy SKUs, consider the following:

  • 如果想要使用 PolicyBased VPN 类型,必须使用基本 SKU。If you want to use a PolicyBased VPN type, you must use the Basic SKU. 任何其他 SKU 均不支持 PolicyBased VPN(之前称为静态路由)。PolicyBased VPNs (previously called Static Routing) are not supported on any other SKU.
  • 基本 SKU 不支持 BGP。BGP is not supported on the Basic SKU.
  • 基本 SKU 不支持 ExpressRoute-VPN 网关共存配置。ExpressRoute-VPN Gateway coexist configurations are not supported on the Basic SKU.
  • 只能在高性能 SKU 上配置主动-主动 S2S VPN 网关连接。Active-active S2S VPN Gateway connections can be configured on the HighPerformance SKU only.

可以在 "虚拟网络网关" 部分 (位于ExpressRoute 定价页上) 中查看旧版网关定价。You can view legacy gateway pricing in the Virtual Network Gateways section, which is located in on the ExpressRoute pricing page.

按 SKU 列出的估计聚合吞吐量Estimated aggregate throughput by SKU

下表按网关 SKU 显示了网关类型和估计的聚合吞吐量。The following table shows the gateway types and the estimated aggregate throughput by gateway SKU. 此表适用于 Resource Manager 和经典部署模型。This table applies to the Resource Manager and classic deployment models.

价格根据网关 SKU 的不同而异。Pricing differs between gateway SKUs. 有关详细信息,请参阅 VPN 网关定价For more information, see VPN Gateway Pricing.

请注意,此表中未显示 UltraPerformance 网关 SKU。Note that the UltraPerformance gateway SKU is not represented in this table. 有关 UltraPerformance SKU 的信息,请参阅 ExpressRoute 文档。For information about the UltraPerformance SKU, see the ExpressRoute documentation.

VPN 网关吞吐量 (1)VPN Gateway throughput (1) VPN 网关最大 IPsec 隧道数 (2)VPN Gateway max IPsec tunnels (2) ExpressRoute 网关吞吐量ExpressRoute Gateway throughput VPN 网关和 ExpressRoute 共存VPN Gateway and ExpressRoute coexist
基本 SKU (3)(5)(6)Basic SKU (3)(5)(6) 100 Mbps100 Mbps 1010 500 Mbps (6)500 Mbps (6) No
标准 SKU (4)(5)Standard SKU (4)(5) 100 Mbps100 Mbps 1010 1000 Mbps1000 Mbps Yes
高性能 SKU (4)High Performance SKU (4) 200 Mbps200 Mbps 3030 2000 Mbps2000 Mbps Yes

(1) VPN 吞吐量是根据同一 Azure 区域 VNet 之间的度量进行的粗略估计。(1) The VPN throughput is a rough estimate based on the measurements between VNets in the same Azure region. 不能保证该吞吐量通过 Internet 跨界连接。It is not a guaranteed throughput for cross-premises connections across the Internet. 它是可能的最大吞吐量。It is the maximum possible throughput measurement.

(2) 隧道数与 RouteBased VPN 相关。(2) The number of tunnels refer to RouteBased VPNs. PolicyBased VPN 只能支持一个站点到站点 VPN 隧道。A PolicyBased VPN can only support one Site-to-Site VPN tunnel.

(3) 基本 SKU 不支持 BGP。(3) BGP is not supported for the Basic SKU.

(4) 此 SKU 不支持 PolicyBased VPN。(4) PolicyBased VPNs are not supported for this SKU. 仅基本 SKU 支持它们。They are supported for the Basic SKU only.

(5) 此 SKU 不支持主动-主动 S2S VPN 网关连接。(5) Active-active S2S VPN Gateway connections are not supported for this SKU. 只有 HighPerformance SKU 才支持主动-主动连接。Active-active is supported on the HighPerformance SKU only.

(6) 用于 ExpressRoute 的基本 SKU 已弃用。(6) Basic SKU is deprecated for use with ExpressRoute.

按 SKU 和 VPN 类型划分的受支持配置Supported configurations by SKU and VPN type

下表列出了基于策略和基于路由的 VPN 网关的要求。The following table lists the requirements for PolicyBased and RouteBased VPN gateways. 此表适用于 Resource Manager 与经典部署模型。This table applies to both the Resource Manager and classic deployment models. 对于经典模型,基于策略的 VPN 网关与静态网关相同,基于路由的网关与动态网关相同。For the classic model, PolicyBased VPN gateways are the same as Static gateways, and Route-based gateways are the same as Dynamic gateways.

基于策略的基本 VPN 网关PolicyBased Basic VPN Gateway 基于路由的基本 VPN 网关RouteBased Basic VPN Gateway 基于路由的标准 VPN 网关RouteBased Standard VPN Gateway 基于路由的高性能 VPN 网关RouteBased High Performance VPN Gateway
站点到站点连接 (S2S)Site-to-Site connectivity (S2S) 基于策略的 VPN 配置PolicyBased VPN configuration 基于路由的 VPN 配置RouteBased VPN configuration 基于路由的 VPN 配置RouteBased VPN configuration 基于路由的 VPN 配置RouteBased VPN configuration
点到站点连接 (P2S)Point-to-Site connectivity (P2S) 不支持Not supported 支持(可与 S2S 共存)Supported (Can coexist with S2S) 支持(可与 S2S 共存)Supported (Can coexist with S2S) 支持(可与 S2S 共存)Supported (Can coexist with S2S)
身份验证方法Authentication method 预共享密钥Pre-shared key S2S 连接的预共享密钥,P2S 连接的证书Pre-shared key for S2S connectivity, Certificates for P2S connectivity S2S 连接的预共享密钥,P2S 连接的证书Pre-shared key for S2S connectivity, Certificates for P2S connectivity S2S 连接的预共享密钥,P2S 连接的证书Pre-shared key for S2S connectivity, Certificates for P2S connectivity
S2S 连接的最大数目Maximum number of S2S connections 1 1010 1010 3030
P2S 连接的最大数目Maximum number of P2S connections 不支持Not supported 128128 128128 128128
活动路由支持 (BGP)Active routing support (BGP) 不支持Not supported 不支持Not supported 支持Supported 支持Supported

重设网关大小Resize a gateway

可以在同一 SKU 系列内将网关大小重设到某个网关 SKU。You can resize your gateway to a gateway SKU within the same SKU family. 例如,如果具有标准 SKU,则可重设大小为高性能 SKU。For example, if you have a Standard SKU, you can resize to a HighPerformance SKU. 但不能在旧式 SKU 和新式 SKU 系列之间重设 VPN 网关大小。However, you can't resize your VPN gateway between the old SKUs and the new SKU families. 例如,不能从标准 SKU 调整为 VpnGw2 SKU 或从标准 SKU 调整为 VpnGw1。For example, you can't go from a Standard SKU to a VpnGw2 SKU, or a Basic SKU to VpnGw1.

资源管理器Resource Manager

若要使用 PowerShell 重设资源管理器部署模型的网关大小,请使用以下命令:To resize a gateway for the Resource Manager deployment model using PowerShell, use the following command:

$gw = Get-AzVirtualNetworkGateway -Name vnetgw1 -ResourceGroupName testrg
Resize-AzVirtualNetworkGateway -VirtualNetworkGateway $gw -GatewaySku HighPerformance

还可以在 Azure 门户中重设网关大小。You can also resize a gateway in the Azure portal.

传统型Classic

若要调整经典部署模型的网关大小, 必须使用服务管理 PowerShell cmdlet。To resize a gateway for the classic deployment model, you must use the Service Management PowerShell cmdlets. 请使用以下命令:Use the following command:

Resize-AzureVirtualNetworkGateway -GatewayId <Gateway ID> -GatewaySKU HighPerformance

更改到新式网关 SKUChange to the new gateway SKUs

如果使用的是资源管理器部署模型,则可更改到新式网关 SKU。If you are working with the Resource Manager deployment model, you can change to the new gateway SKUs. 当从旧式网关 SKU 更改到新式 SKU 时,需删除现有 VPN 网关并创建新的 VPN 网关。When you change from a legacy gateway SKU to a new SKU, you delete the existing VPN gateway and create a new VPN gateway.

工作流程:Workflow:

  1. 删除到虚拟网关的任何连接。Remove any connections to the virtual network gateway.
  2. 删除旧的 VPN 网关。Delete the old VPN gateway.
  3. 创建新的 VPN 网关。Create the new VPN gateway.
  4. 使用新的 VPN 网关 IP 地址更新本地 VPN 设备(适用于站点到站点连接)。Update your on-premises VPN devices with the new VPN gateway IP address (for Site-to-Site connections).
  5. 更新将连接到本网关的任何 VNet 到 VNet 本地网关的网关 IP 地址值。Update the gateway IP address value for any VNet-to-VNet local network gateways that will connect to this gateway.
  6. 下载适用于 P2S 客户端(通过此 VPN 网关连接到虚拟网络)的新客户端 VPN 配置包。Download new client VPN configuration packages for P2S clients connecting to the virtual network through this VPN gateway.
  7. 重新创建到虚拟网关的连接。Recreate the connections to the virtual network gateway.

注意事项:Considerations:

  • 若要更改到新式 SKU,VPN 网关必须处于资源管理器部署模型中。To move to the new SKUs, your VPN gateway must be in the Resource Manager deployment model.
  • 如果有经典的 VPN 网关,必须对该网关继续使用早期的旧式 SKU,但可以在旧式 SKU 之间重设网关大小。If you have a classic VPN gateway, you must continue using the older legacy SKUs for that gateway, however, you can resize between the legacy SKUs. 不能更改为新式 SKU。You cannot change to the new SKUs.
  • 当从旧式 SKU 更改到新式 SKU 时,连接将中断。You will have connectivity downtime when you change from a legacy SKU to a new SKU.
  • 更改为新网关 SKU 时,VPN 网关的公有 IP 地址将更改。When changing to a new gateway SKU, the public IP address for your VPN gateway will change. 即使指定以前使用的同一公共 IP 地址对象,也会出现这种情况。This happens even if you specify the same public IP address object that you used previously.

后续步骤Next steps

有关新式网关 SKU 的详细信息,请参阅网关 SKUFor more information about the new Gateway SKUs, see Gateway SKUs.

有关配置设置的详细信息,请参阅关于 VPN 网关配置设置For more information about configuration settings, see About VPN Gateway configuration settings.