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

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

本文概述将 Azure ExpressRoute 线路从经典部署模型转移到 Azure Resource Manager 部署模型的效果。This article provides an overview of what it means to move an Azure ExpressRoute circuit from the classic to the Azure Resource Manager deployment model.

可以使用一条 ExpressRoute 线路连接到在经典部署模型和 Resource Manager 部署模型中部署的虚拟网络。You can use a single ExpressRoute circuit to connect to virtual networks that are deployed both in the classic and the Resource Manager deployment models. 无论 ExpressRoute 线路的创建方式为何,现在都可以链接到这两种部署模型中的虚拟网络。An ExpressRoute circuit, regardless of how it is created, can now link to virtual networks across both deployment models.

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

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

在经典部署模型中创建的 ExpressRoute 线路需先转移到 Resource Manager 部署模型,才能连接到经典部署模型和 Resource Manager 部署模型。ExpressRoute circuits that are created in the classic deployment model need to be moved to the Resource Manager deployment model first to enable connectivity to both the classic and the Resource Manager deployment models. 转移连接时,不会发生连接断开的情况。There isn't connectivity loss or disruption 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 线路的感观和执行方式与在 Resource Manager 部署模型中创建的 ExpressRoute 线路完全相同。After the move is completed successfully, the ExpressRoute circuit looks, performs, and feels 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 线路转移到 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 和计费类型等线路属性,以及删除线路)只能在 Resource Manager 部署模型中执行。This means that you can perform 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. 请参阅下面关于在 Resource Manager 部署模型中创建的线路的部分,以便进一步详细了解如何管理对这两种部署模型的访问权限。Refer to the section below on circuits that are created in the Resource Manager deployment model for further details on how you can manage access to both deployment models.

不需要与连接服务提供商合作即可执行转移。You do not have to involve your connectivity provider to perform the move.

在 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 enabled to be accessed from both deployment models.

  • 默认情况下,在 Resource Manager 部署模型中创建的 ExpressRoute 线路无法访问经典部署模型。ExpressRoute circuits that were created in the Resource Manager deployment model do not have access to the classic deployment model by default.
  • 默认情况下,可以从这两种部署模型访问从经典部署模型转移到 Resource Manager 部署模型的 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.
  • 无论是在 Resource Manager 部署模型还是经典部署模型中创建的,ExpressRoute 线路始终都可以访问 Resource Manager 部署模型。An ExpressRoute circuit always has access to the Resource Manager deployment model, regardless of whether it was created in the Resource Manager or classic deployment model. 这意味着,可以根据 如何链接虚拟网络中的说明,与 Resource Manager 部署模型中创建的虚拟网络建立连接。This means that you can create connections to virtual networks created in the Resource Manager deployment model 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 线路的 allowClassicOperations 参数,即可让单个 ExpressRoute 线路链接到这两种部署模型中的虚拟网络。You can enable a single ExpressRoute circuit to link to virtual networks in both deployment models by setting the allowClassicOperations parameter of the ExpressRoute circuit.

allowClassicOperations 设置为 TRUE 即可从这两种部署模型中的虚拟网络链接到 ExpressRoute 线路。Setting allowClassicOperations to TRUE enables you to link virtual networks from both deployment models to the ExpressRoute circuit. 可以遵循有关 如何链接经典部署模型中的虚拟网络的指导,链接到经典部署模型中的虚拟网络。You can link to virtual networks in the classic deployment model by following guidance on how to link virtual networks in the classic deployment model. 可以遵循有关 如何链接 Resource Manager 部署模型中的虚拟网络的指导,链接到 Resource Manager 部署模型中的虚拟网络。You can link to virtual networks in the Resource Manager deployment model by following guidance on how to link virtual networks in the Resource Manager deployment model.

allowClassicOperations 设置为 FALSE 会阻止从经典部署模型访问线路。Setting allowClassicOperations to FALSE blocks access to the circuit from the classic deployment model. 但是,经典部署模型中的所有虚拟网络链接会保留。However, all virtual network links in the classic deployment model are preserved. 在此情况下,ExpressRoute 线路不显示在经典部署模型中。In this case, the ExpressRoute circuit is not 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 时,无法执行以下经典操作:You cannot perform the following classic operations when allowClassicOperations is set to TRUE:

  • 创建/更新/获取/删除 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. 经典部署模型的虚拟网络中的虚拟机与 Resource Manager 部署模型的虚拟网络中的虚拟机之间的流量将流经 ExpressRoute,前提是这两个虚拟网络链接到相同的 ExpressRoute 线路。Traffic between virtual machines in virtual networks in the classic deployment model and those in virtual networks in the Resource Manager deployment model flows through ExpressRoute if both virtual networks are linked to the same ExpressRoute circuit.

聚合吞吐量受限于虚拟网络网关的吞吐容量。Aggregate throughput is limited by the throughput capacity of the virtual network gateway. 在这种情况下,流量不进入连接服务提供商的网络或网络。Traffic does not 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 线路的感观和执行方式与在 Resource Manager 部署模型中创建的任何其他 ExpressRoute 线路相似。After it is moved, the ExpressRoute circuit looks, feels, and performs 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 和计费类型等线路属性,以及删除线路)只能在 Resource Manager 部署模型中执行。This means that you can perform 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. 经典部署模型的虚拟网络中的虚拟机与 Resource Manager 部署模型的虚拟网络中的虚拟机之间的流量将流经 ExpressRoute,前提是这两个虚拟网络链接到相同的 ExpressRoute 线路。Traffic between virtual machines in virtual networks in the classic deployment model and those in virtual networks in the Resource Manager deployment model flows 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 Resource Manager 模型后,即可迁移链接到 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.
  • 针对经典部署模型的基于角色的访问控制 (RBAC) 支持。Role-Based Access Control (RBAC) support for the classic deployment model. 无法对经典部署模型中的线路执行 RBAC 控制。You cannot perform 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