将 ExpressRoute 线路从经典部署模型转移到 Resource Manager 部署模型Moving ExpressRoute circuits from the classic to the Resource Manager deployment model

本文概述了将 Azure ExpressRoute 线路从经典部署模型转移到 Azure 资源管理器部署模型时会发生什么。This article provides an overview of what happens when you move an Azure ExpressRoute circuit from the classic to the Azure Resource Manager deployment model.

可使用一条 ExpressRoute 线路连接到同时在经典部署模型和资源管理器部署模型中部署的虚拟网络。You can use a single ExpressRoute circuit to connect virtual networks that are deployed both in the classic and the Resource Manager deployment models.

跨两种部署模型链接到虚拟网络的 ExpressRoute 线路

在经典部署模型中创建的 ExpressRoute 线路ExpressRoute circuits that are created in the classic deployment model

在经典部署模型中创建的 ExpressRoute 线路需要首先迁移到资源管理器部署模型。ExpressRoute circuits created in the classic deployment model need to migrate to the Resource Manager deployment model first. 只有这样才能同时启用到经典部署模型和资源管理器部署模型的连接。Only then can enable connectivity to both the classic and the Resource Manager deployment models. 转移连接时,不会发生连接丢失或断开的情况。Connectivity isn't loss or disrupted when a connection is being moved. 经典部署模型中所有从线路到虚拟网络的链接都会保留,而无论这些链接是在同一订阅还是不同订阅中。All circuit-to-virtual network links in the classic deployment model within the same subscription and cross-subscription are preserved.

成功完成转移后,ExpressRoute 线路的行为将与在资源管理器部署模型中创建的 ExpressRoute 线路完全相同。After the move has successfully completed, the ExpressRoute circuit will behave exactly like an ExpressRoute circuit that was created in the Resource Manager deployment model. 现在,可以在 Resource Manager 部署模型中建立与虚拟网络的连接。You can now create connections to virtual networks in the Resource Manager deployment model.

将 ExpressRoute 线路转移到资源管理器部署模型后,只能在资源管理器部署模型中对其进行管理。Once you've moved the ExpressRoute circuit to the Resources Manager deployment model, you can only manage it in Resource Manager deployment model. 而且,将只能通过资源管理器部署模型执行管理对等互连、更新线路属性和删除线路的操作。Operations for managing peerings, updating circuit properties, and deleting circuits will only be available through the Resource Manager deployment model. 若要详细了解如何管理对这两个部署模型的访问,请参阅以下部分。Refer to the following section for further details on how you can manage access to both deployment models.

无需连接服务提供商操作,你就可将线路转移到资源管理器部署模型。You don't have to involve your connectivity provider to move your circuit to the Resource Manager deployment model.

在 Resource Manager 部署模型中创建的 ExpressRoute 线路ExpressRoute circuits that are created in the Resource Manager deployment model

可以允许从这两种部署模型访问在 Resource Manager 部署模型中创建的 ExpressRoute 线路。You can enable ExpressRoute circuits that are created in the Resource Manager deployment model to be accessible from both deployment models. 订阅中的任何 ExpressRoute 线路都可配置为从这两种部署模型访问。Any ExpressRoute circuit in your subscription can be configured to have access from both deployment models.

  • 默认情况下,在资源管理器部署模型中创建的 ExpressRoute 线路无法访问经典部署模型。ExpressRoute circuits that were created in the Resource Manager deployment model don't have access to the classic deployment model by default.
  • 默认情况下,可从这两种部署模型访问从经典部署模型转移到资源管理器部署模型的 ExpressRoute 线路。ExpressRoute circuits that have been moved from the classic deployment model to the Resource Manager deployment model are accessible from both deployment models by default.
  • 无论是在资源管理器部署模型还是经典部署模型中创建的,ExpressRoute 线路始终都可访问资源管理器部署模型。An ExpressRoute circuit always has access to the Resource Manager deployment model, whether it was created in the Resource Manager or classic deployment model. 可按照如何链接虚拟网络中的说明,创建到虚拟网络的连接。You can create connections to virtual networks by following instructions on how to link virtual networks.
  • 对经典部署模型的访问权限由 ExpressRoute 线路中的 allowClassicOperations 参数控制。Access to the classic deployment model is controlled by the allowClassicOperations parameter in the ExpressRoute circuit.

重要

将应用 服务限制 页中所述的所有配额。All quotas that are documented on the service limits page apply. 例如,标准线路最多可以有 10 个跨经典部署模型和 Resource Manager 部署模型的虚拟网络链接/连接。As an example, a standard circuit can have at most 10 virtual network links/connections across both the classic and the Resource Manager deployment models.

控制对经典部署模型的访问权限Controlling access to the classic deployment model

可在这两种部署模型中启用 ExpressRoute 线路,以链接到虚拟网络。You can enable an ExpressRoute circuit to link to virtual networks in both deployment models. 为此,请在 ExpressRoute 线路上设置 allowClassicOperations 参数。To do so, set the allowClassicOperations parameter on the ExpressRoute circuit.

allowClassicOperations 设置为 TRUE 即可从这两种部署模型中的虚拟网络链接到 ExpressRoute 线路。Setting allowClassicOperations to TRUE enables you to link virtual networks from both deployment models to the ExpressRoute circuit.

allowClassicOperations 设置为 FALSE 会阻止从经典部署模型访问线路。Setting allowClassicOperations to FALSE blocks access to the circuit from the classic deployment model. 不过,经典部署模型中链接的所有虚拟网络仍会保留。However, all virtual networks linked in the classic deployment model are still preserved. ExpressRoute 线路不会在经典部署模型中显示。The ExpressRoute circuit isn't visible in the classic deployment model.

经典部署模型中支持的操作Supported operations in the classic deployment model

allowClassicOperations 设置为 TRUE 时,ExpressRoute 线路支持以下经典操作。The following classic operations are supported on an ExpressRoute circuit when allowClassicOperations is set to TRUE:

  • 获取 ExpressRoute 线路信息Get ExpressRoute circuit information
  • 创建/更新/获取/删除到经典虚拟网络的虚拟网络链接Create/update/get/delete virtual network links to classic virtual networks
  • 创建/更新/获取/删除跨订阅连接的虚拟网络链接授权Create/update/get/delete virtual network link authorizations for cross-subscription connectivity

但是,将 allowClassicOperations 设置为 TRUE 时,无法执行以下经典操作:However, when allowClassicOperations is set to TRUE, you can't execute the following classic operations:

  • 创建/更新/获取/删除 Azure 专用对等互连、Azure 公共对等互连和 Microsoft 对等互连的边界网关协议 (BGP) 对等互连Create/update/get/delete Border Gateway Protocol (BGP) peerings for Azure private, Azure public, and Microsoft peerings
  • 删除 ExpressRoute 线路Delete ExpressRoute circuits

经典部署模型和 Resource Manager 部署模型之间的通信Communication between the classic and the Resource Manager deployment models

ExpressRoute 线路相当于经典部署模型与 Resource Manager 部署模型之间的桥梁。The ExpressRoute circuit acts like a bridge between the classic and the Resource Manager deployment models. 这两个部署模型的虚拟网络之间的流量可通过 ExpressRoute 线路,前提是这两种虚拟网络都链接到同一线路。Traffic between virtual networks for both deployment models can pass through the ExpressRoute circuit if both virtual networks are linked to the same circuit.

聚合吞吐量受限于虚拟网络网关的吞吐容量。Aggregate throughput is limited by the throughput capacity of the virtual network gateway. 在这种情况下,流量不会进入连接服务提供商的网络,也不进入你的网络。Traffic doesn't enter the connectivity provider's networks or your networks in such cases. 虚拟网络之间的流量完全包含在 Microsoft 网络中。Traffic flow between the virtual networks is fully contained within the Microsoft network.

对 Azure 公共对等互连资源和 Microsoft 对等互连资源的访问权限Access to Azure public and Microsoft peering resources

可以继续访问通常可通过 Azure 公共对等互连和 Microsoft 对等互连访问的资源,而不会出现任何中断。You can continue to access resources that are typically accessible through Azure public peering and Microsoft peering without any disruption.

支持的操作What's supported

本部分介绍可通过 ExpressRoute 线路执行的操作:This section describes what's supported for ExpressRoute circuits:

  • 可以使用一条 ExpressRoute 线路访问在经典部署模型和 Resource Manager 部署模型中部署的虚拟网络。You can use a single ExpressRoute circuit to access virtual networks that are deployed in the classic and the Resource Manager deployment models.
  • 可以将 ExpressRoute 线路从经典部署模型转移到 Resource Manager 部署模型。You can move an ExpressRoute circuit from the classic to the Resource Manager deployment model. 转移后,ExpressRoute 线路将继续像在资源管理器部署模型中创建的任何其他 ExpressRoute 线路一样运行。Once moved, the ExpressRoute circuit will continue to operate like any other ExpressRoute circuit that is created in the Resource Manager deployment model.
  • 只能转移 ExpressRoute 线路。You can move only the ExpressRoute circuit. 无法通过此操作转移线路链接、虚拟网络和 VPN 网关。Circuit links, virtual networks, and VPN gateways cannot be moved through this operation.
  • 将 ExpressRoute 线路转移到 Resource Manager 部署模型后,只能使用 Resource Manager 部署模型来管理 ExpressRoute 线路的生命周期。After an ExpressRoute circuit has been moved to the Resource Manager deployment model, you can manage the life cycle of the ExpressRoute circuit only by using the Resource Manager deployment model. 这意味着,某些操作只能在资源管理器部署模型中运行,例如添加/更新/删除对等互连、更新线路属性(例如带宽、SKU 和计费类型),以及删除线路。This means that you can run operations like adding/updating/deleting peerings, updating circuit properties (such as bandwidth, SKU, and billing type), and deleting circuits only in the Resource Manager deployment model.
  • ExpressRoute 线路相当于经典部署模型与 Resource Manager 部署模型之间的桥梁。The ExpressRoute circuit acts like a bridge between the classic and the Resource Manager deployment models. 经典虚拟网络中的虚拟机与资源管理器虚拟网络中的虚拟机之间的流量可通过 ExpressRoute 进行通信,前提是这两种虚拟网络都链接到同一 ExpressRoute 线路。Traffic between virtual machines in classic virtual networks and virtual machines in Resource Manager virtual networks can communicate through ExpressRoute if both virtual networks are linked to the same ExpressRoute circuit.
  • 经典部署模型和 Resource Manager 部署模型都支持跨订阅连接。Cross-subscription connectivity is supported in both the classic and the Resource Manager deployment models.
  • 将 ExpressRoute 线路从经典模型移到 Azure 资源管理器模型后,即可迁移链接到 ExpressRoute 线路的虚拟网络After you move an ExpressRoute circuit from the classic model to the Azure Resource Manager model, you can migrate the virtual networks linked to the ExpressRoute circuit.

不支持的功能What's not supported

本部分介绍不可通过 ExpressRoute 线路执行的操作:This section describes what's not supported for ExpressRoute circuits:

  • 从经典部署模型管理 ExpressRoute 线路的生命周期。Managing the life cycle of an ExpressRoute circuit from the classic deployment model.
  • 针对经典部署模型的 Azure 基于角色的访问控制 (Azure RBAC) 支持。Azure role-based access control (Azure RBAC) support for the classic deployment model. 无法对经典部署模型中的线路运行 Azure RBAC 控制。You can't run Azure RBAC controls to a circuit in the classic deployment model. 订阅的任何管理员/共同管理员都可以将虚拟网络链接到线路,也都可以取消此类链接。Any administrator/coadministrator of the subscription can link or unlink virtual networks to the circuit.

配置Configuration

遵循 将 ExpressRoute 线路从经典部署模型转移到 Resource Manager 部署模型中所述的说明。Follow the instructions that are described in Move an ExpressRoute circuit from the classic to the Resource Manager deployment model.

后续步骤Next steps