規劃軟體定義的網路基礎結構Plan a Software Defined Network infrastructure

適用于: Azure Stack HCI、版本 20H2;Windows Server 2019、Windows Server (半年通道) 、Windows Server 2016Applies to: Azure Stack HCI, version 20H2; Windows Server 2019, Windows Server (Semi-Annual Channel), Windows Server 2016

深入瞭解軟體定義網路 (SDN) 基礎結構的部署規劃,包括硬體和軟體必要條件。Learn about deployment planning for a Software Defined Network (SDN) infrastructure, including hardware and software prerequisites. 本主題包含實體與邏輯網路設定、路由、閘道、網路硬體等的規劃需求。This topic includes planning requirements for physical and logical network configuration, routing, gateways, network hardware, and more. 它也包含擴充 SDN 基礎結構和使用階段式部署的考慮。It also includes considerations on extending a SDN infrastructure and using a phased deployment.

注意

延伸的 (多網站) 叢集不支援 SDN。SDN is not supported on stretched (multi-site) clusters.

PrerequisitesPrerequisites

SDN 基礎結構有幾個硬體和軟體必要條件,包括:There are several hardware and software prerequisites for a SDN infrastructure, including:

  • 安全性群組和動態 DNS 註冊Security groups and dynamic DNS registration . 您必須準備資料中心以進行網路控制站部署,這需要 (Vm) 的一組虛擬機器。You must prepare your datacenter for Network Controller deployment, which requires a set of virtual machines (VMs). 部署網路控制站之前,您必須先設定安全性群組和動態 DNS 註冊。Before you can deploy the Network Controller, you must configure security groups and dynamic DNS registration.

    若要深入瞭解資料中心的網路控制站部署,請參閱 部署網路控制站的需求。To learn more about Network Controller deployment for your datacenter, see Requirements for Deploying Network Controller.

  • 實體網路Physical network . 您需要存取您的實體網路裝置,以設定虛擬區域網路絡 (Vlan) 、路由和邊界閘道協定 (BGP) 。You need access to your physical network devices to configure virtual local area networks (VLANs), routing, and the Border Gateway Protocol (BGP). 本主題提供手動交換器設定的指示,以及在第3層交換器/路由器上使用 BGP 對等互連的選項,或 (RRAS) VM 的路由和遠端存取服務器的選項。This topic provides instructions for manual switch configuration, as well as options to use either BGP peering on Layer-3 switches / routers, or a Routing and Remote Access Server (RRAS) VM.

  • 實體計算主機Physical compute hosts . 這些主機會執行 Hyper-v,而且必須裝載 SDN 基礎結構和租使用者 Vm。These hosts run Hyper-V and are required to host a SDN infrastructure and tenant VMs. 這些主機需要特定的網路硬體,以獲得最佳效能,如 SDN 硬體需求中所述。Specific network hardware is required in these hosts for best performance, as described in SDN hardware requirements.

實體和邏輯網路設定Physical and logical network configuration

每個實體計算主機都需要透過一或多個連接到實體交換器埠的網路介面卡進行網路連線。Each physical compute host requires network connectivity through one or more network adapters attached to a physical switch port. 第2層 VLAN 支援分割成多個邏輯網路區段的網路。A Layer-2 VLAN supports networks divided into multiple logical network segments.

提示

在存取模式或未標記的情況下,使用 VLAN 0 進行邏輯網路。Use VLAN 0 for logical networks in either access mode or untagged.

重要

Windows Server 2016 軟體定義的網路功能支援基礎和覆迭的 IPv4 定址。Windows Server 2016 Software Defined Networking supports IPv4 addressing for the underlay and the overlay. 不支援 IPv6。IPv6 is not supported. Windows Server 2019 支援 IPv4 和 IPv6 定址。Windows Server 2019 supports both IPv4 and IPv6 addressing.

Logical networksLogical networks

本節涵蓋管理邏輯網路和 Hyper-v 網路虛擬化 (HNV) 提供者邏輯網路的 SDN 基礎結構規劃需求。This section covers SDN infrastructure planning requirements for the management logical network and the Hyper-V Network Virtualization (HNV) Provider logical network. 其中包含有關布建額外邏輯網路以使用閘道的詳細資料,以及 Load Balancer (SLB) 的軟體,以及範例網路拓撲的詳細資料。It includes details on provisioning additional logical networks to use gateways and the Software Load Balancer (SLB), and a sample network topology.

管理與 HNV 提供者Management and HNV Provider

所有實體計算主機都必須存取管理邏輯網路和 HNV 提供者邏輯網路。All physical compute hosts must access the management logical network and the HNV Provider logical network. 針對 IP 位址規劃目的,每個實體計算主機至少必須有一個從管理邏輯網路指派的 IP 位址。For IP address planning purposes, each physical compute host must have at least one IP address assigned from the management logical network. 網路控制站需要此網路的保留 IP 位址,才能作為具象狀態傳輸 (REST) IP 位址。The Network Controller requires a reserved IP address from this network to serve as the Representational State Transfer (REST) IP address.

HNV 提供者網路作為東部/西部的基礎實體網路, (內部內部) 租使用者流量、北/南部 (外部內部) 租使用者流量,以及與實體網路交換 BGP 對等互連資訊。The HNV Provider network serves as the underlying physical network for East/West (internal-internal) tenant traffic, North/South (external-internal) tenant traffic, and to exchange BGP peering information with the physical network.

DHCP 伺服器可以自動指派管理網路的 IP 位址,您也可以手動指派靜態 IP 位址。A DHCP server can automatically assign IP addresses for the management network, or you can manually assign static IP addresses. SDN 堆疊會針對來自 IP 位址池的個別 Hyper-v 主機,自動指派 HNV 提供者邏輯網路的 IP 位址。The SDN stack automatically assigns IP addresses for the HNV Provider logical network for the individual Hyper-V hosts from an IP address pool. 網路控制站會指定和管理 IP 位址池。The Network Controller specifies and manages the IP address pool.

注意

網路控制站只會在網路控制站主機代理程式收到特定租使用者 VM 的網路原則之後,將 HNV 提供者 IP 位址指派給實體計算主機。The Network Controller assigns an HNV Provider IP address to a physical compute host only after the Network Controller Host Agent receives network policy for a specific tenant VM.

如果...If... 則...Then...
邏輯網路使用 Vlan,The logical networks use VLANs, 實體計算主機必須連接到可存取 Vlan 的主幹交換器埠。the physical compute host must connect to a trunked switch port that has access to the VLANs. 請務必注意,電腦主機上的實體網路介面卡不能啟用任何 VLAN 篩選。It's important to note that the physical network adapters on the computer host must not have any VLAN filtering activated.
您使用 Switched-Embedded 小組 (設定) ,且有多個網路介面卡 (NIC) 小組成員,例如網路介面卡)You are using Switched-Embedded Teaming (SET) and have multiple Network Interface Card (NIC) team members, such as network adapters, 您必須將該特定主機的所有 NIC 小組成員連線至相同的第2層廣播網域。you must connect all NIC team members for that particular host to the same Layer-2 broadcast domain.
實體計算主機正在執行額外的基礎結構 Vm,例如網路控制站、SLB/多工器 (MUX) 或閘道The physical compute host is running additional infrastructure VMs, such as Network Controller, the SLB/Multiplexer (MUX), or Gateway, 確定管理邏輯網路有足夠的 IP 位址可供每個託管的 VM。ensure that the management logical network has sufficient IP addresses for each hosted VM. 此外,請確定 HNV 提供者邏輯網路有足夠的 IP 位址可配置給每個 SLB/MUX 和閘道基礎結構 VM。Also, ensure that the HNV Provider logical network has sufficient IP addresses to allocate to each SLB/MUX and gateway infrastructure VM. 雖然 IP 保留由網路控制站管理,但由於無法使用而無法保留新的 IP 位址,因此可能會導致您的網路上有重複的 IP 位址。Although IP reservation is managed by the Network Controller, failure to reserve a new IP address due to unavailability may result in duplicate IP addresses on your network.

如需 Hyper-v 網路虛擬化 (HNV) 的相關資訊,您可以用來將 Microsoft SDN 部署中的網路虛擬化,請參閱 Hyper-v 網路虛擬化For information about Hyper-V Network Virtualization (HNV) that you can use to virtualize networks in a Microsoft SDN deployment, see Hyper-V Network Virtualization.

閘道和軟體 Load Balancer (SLB) Gateways and the Software Load Balancer (SLB)

您需要建立並布建額外的邏輯網路,以使用閘道和 SLB。You need to create and provision additional logical networks to use gateways and the SLB. 請務必取得這些網路的正確 IP 首碼、VLAN Id 和閘道 IP 位址。Make sure to obtain the correct IP prefixes, VLAN IDs, and gateway IP addresses for these networks.

公用 VIP 邏輯網路Public VIP logical network 公用虛擬 IP (VIP) 邏輯網路必須使用可在雲端環境外路由傳送的 IP 子網首碼 (通常是可透過網際網路路由傳送的) 。The Public virtual IP (VIP) logical network must use IP subnet prefixes that are routable outside of the cloud environment (typically internet routable). 這些是外部用戶端用來存取虛擬網路中資源的前端 IP 位址,包括站對站閘道的前端 VIP。These are the front-end IP addresses that external clients use to access resources in the virtual networks, including the front-end VIP for the site-to-site gateway. 您不需要將 VLAN 指派至此網路。You don’t need to assign a VLAN to this network.
私人 VIP 邏輯網路Private VIP logical network 私人 VIP 邏輯網路不需要在雲端外部路由傳送。The Private VIP logical network is not required to be routable outside of the cloud. 這是因為只有可從內部雲端用戶端存取的 Vip 會使用它,例如私用服務。This is because only VIPs that can be accessed from internal cloud clients use it, such as private services. 您不需要將 VLAN 指派至此網路。You don’t need to assign a VLAN to this network.
GRE VIP 邏輯網路GRE VIP logical network 一般路由封裝 (GRE) VIP 網路是唯一用來定義 Vip 的子網。The Generic Routing Encapsulation (GRE) VIP network is a subnet that exists solely to define VIPs. Vip 會指派給在 SDN 網狀架構上執行的閘道 Vm,以用於站對站 (S2S) GRE 連線類型。The VIPs are assigned to gateway VMs running on your SDN fabric for a site-to-site (S2S) GRE connection type. 您不需要在實體交換器或路由器中預先設定此網路,或將 VLAN 指派給它。You don't need to preconfigure this network in your physical switches or router, or assign a VLAN to it.

網路拓撲範例Sample network topology

變更您環境的範例 IP 子網首碼和 VLAN 識別碼。Change the sample IP subnet prefixes and VLAN IDs for your environment.

網路名稱Network name 子網路Subnet MaskMask 主幹上的 VLAN 識別碼VLAN ID on trunk 閘道Gateway 保留 (範例) Reservation (examples)
管理性Management 10.184.108.010.184.108.0 2424 77 10.184.108.110.184.108.1 10.184.108.1-路由器10.184.108.1 - Router
10.184.108.4-網路控制站10.184.108.4 - Network Controller
10.184.108.10-計算主機110.184.108.10 - Compute host 1
10.184.108.11-計算主機210.184.108.11 - Compute host 2
10.184.108 x-計算主機 X10.184.108.X - Compute host X
HNV 提供者HNV Provider 10.10.56.010.10.56.0 2323 1111 10.10.56.110.10.56.1 10.10.56.1-路由器10.10.56.1 - Router
10.10.56.2-SLB/MUX110.10.56.2 - SLB/MUX1
10.10.56.5 - Gateway110.10.56.5 - Gateway1
公用 VIPPublic VIP 41.40.40.041.40.40.0 2727 NANA 41.40.40.141.40.40.1 41.40.40.1-路由器41.40.40.1 - Router
41.40.40.3-IPSec S2S VPN VIP41.40.40.3 - IPSec S2S VPN VIP
私密 VIPPrivate VIP 20.20.20.020.20.20.0 2727 NANA 20.20.20.120.20.20.1 20.20.20.1-預設 GW (路由器) 20.20.20.1 - Default GW (router)
GRE VIPGRE VIP 31.30.30.031.30.30.0 2424 NANA 31.30.30.131.30.30.1 31.30.30.1-預設 GW31.30.30.1 - Default GW

路由基礎結構Routing infrastructure

( ) SLB/MUX 和遠端存取) (伺服器會使用內部 BGP 對等互連,將路由資訊(例如 VIP 子網的下一個躍點)公告到實體網路。Routing information (such as next-hop) for the VIP subnets is advertised by the SLB/MUX and Remote Access Server (RAS) gateways into the physical network using internal BGP peering. VIP 邏輯網路沒有指派的 VLAN,也未在第2層交換器 (中預先設定,例如機架頂端交換器) 。The VIP logical networks do not have a VLAN assigned and they are not preconfigured in the Layer-2 switch (such as the Top-of-Rack switch).

您必須在路由器上建立 BGP 對等互連,讓 SDN 基礎結構用來接收 SLB/Mux 和 RAS 閘道所公告的 VIP 邏輯網路路由。You need to create a BGP peer on the router that your SDN infrastructure uses to receive routes for the VIP logical networks advertised by the SLB/MUXes and RAS Gateways. BGP 對等互連只需要從 SLB/MUX 或 RAS 閘道 (為外部 BGP 對等) 的一種方式。BGP peering only needs to occur one way (from the SLB/MUX or RAS Gateway to the external BGP peer). 在路由的第一層,您可以使用靜態路由或其他動態路由通訊協定,例如開放式最短路徑 First (OSPF) 。Above the first layer of routing, you can use static routes or another dynamic routing protocol, such as Open Shortest Path First (OSPF). 不過,如先前所述,VIP 邏輯網路的 IP 子網首碼必須可從實體網路路由傳送至外部 BGP 對等。However, as previously stated, the IP subnet prefix for the VIP logical networks do need to be routable from the physical network to the external BGP peer.

BGP 對等互連通常是在受管理交換器或路由器中設定為網路基礎結構的一部分。BGP peering is typically configured in a managed switch or router as part of the network infrastructure. BGP 對等也可以在已安裝「僅限路由」模式的「RAS」角色的 Windows 伺服器上進行設定。The BGP peer could also be configured on a Windows Server with the RAS role installed in a Routing Only mode. 網路基礎結構中的 BGP 路由器對等必須設定為使用自己的自發系統編號 (ASN) ,並允許從指派給 SDN 元件 ( SLB/MUX 和 RAS 閘道的 ASN 對等互連 ) 。The BGP router peer in the network infrastructure must be configured to use its own Autonomous System Numbers (ASN) and allow peering from an ASN that is assigned to the SDN components (SLB/MUX and RAS Gateways).

您必須從您的實體路由器或從該路由器控制的網路系統管理員取得下列資訊:You must obtain the following information from your physical router, or from the network administrator in control of that router:

  • 路由器 ASNRouter ASN
  • 路由器 IP 位址Router IP address

注意

SLB/MUX 不支援四個位元組的 Asn。Four-byte ASNs are not supported by the SLB/MUX. 您必須將兩個位元組的 Asn 配置給 SLB/MUX,以及它所連接的路由器。You must allocate two-byte ASNs to the SLB/MUX and the router to which it connects. 您可以在環境中的其他地方使用四個位元組的 Asn。You can use four-byte ASNs elsewhere in your environment.

您或您的網路系統管理員必須設定 BGP 路由器對等,以接受來自您 RAS 閘道和 SLB Mux 所使用的 HNV 提供者邏輯網路之 ASN 和 IP 位址或子網位址的連線。You or your network administrator must configure the BGP router peer to accept connections from the ASN and IP address or subnet address of the HNV Provider logical network that your RAS Gateway and SLB MUXes are using.

如需詳細資訊,請參閱 邊界閘道協定 (BGP) For more information, see Border Gateway Protocol (BGP).

預設閘道Default gateways

設定為連線至多個網路的機器(例如實體主機、SLB/MUX 和閘道 Vm)必須設定一個預設閘道。Machines configured to connect to multiple networks, such as the physical hosts, SLB/MUX, and gateway VMs must only have one default gateway configured. 針對主機和基礎結構 Vm 使用下列預設閘道:Use the following default gateways for the hosts and the infrastructure VMs:

  • 若為 Hyper-v 主機,請使用管理網路作為預設閘道。For Hyper-V hosts, use the management network as the default gateway.
  • 若為網路控制卡 Vm,請使用管理網路作為預設閘道。For Network Controller VMs, use the management network as the default gateway.
  • 針對 SLB/MUX Vm,請使用管理網路作為預設閘道。For SLB/MUX VMs, use the management network as the default gateway.
  • 針對閘道 Vm,請使用 HNV 提供者網路作為預設閘道。For the gateway VMs, use the HNV Provider network as the default gateway. 這應該設定在閘道 Vm 的前端 NIC 上。This should be set on the front-end NIC of the gateway VMs.

交換器和路由器Switches and routers

為協助設定您的實體交換器或路由器, MICROSOFT SDN GitHub 存放庫中有一組適用于各種交換器模型和廠商的範例設定檔。To help configure your physical switch or router, a set of sample configuration files for a variety of switch models and vendors is available at the Microsoft SDN GitHub repository. 提供的讀我檔案和測試的命令列介面 (CLI) 特定參數的命令。A readme file and tested command-line interface (CLI) commands for specific switches are provided.

如需詳細的交換器和路由器需求,請參閱 SDN 硬體需求For detailed switch and router requirements, see SDN hardware requirements.

計算Compute

所有 Hyper-v 主機都必須安裝適當的作業系統、針對 Hyper-v 啟用,並且使用外部 Hyper-v 虛擬交換器,並至少有一個連接到管理邏輯網路的實體介面卡。All Hyper-V hosts must have the appropriate operating system installed, be enabled for Hyper-V, and use an external Hyper-V virtual switch with at least one physical adapter connected to the management logical network. 主機必須可透過指派給管理主機 vNIC 的管理 IP 位址來連線。The host must be reachable via a management IP address assigned to the management host vNIC.

您可以使用與 Hyper-v、共用或本機相容的任何儲存體類型。You can use any storage type that is compatible with Hyper-V, shared, or local.

提示

您的所有虛擬交換器都使用相同的名稱是很方便的,但這不是必要的。It is convenient to use the same name for all your virtual switches, but it is not mandatory. 如果您打算使用腳本進行部署,請參閱 config.psd1 檔案中與變數相關聯的批註 vSwitchNameIf you plan to use scripts to deploy, see the comment associated with the vSwitchName variable in the config.psd1 file.

主機計算需求Host compute requirements

以下顯示範例部署中所使用之四個實體主機的最低硬體和軟體需求。The following shows the minimum hardware and software requirements for the four physical hosts used in the example deployment.

主機Host 硬體需求Hardware requirements 軟體需求Software requirements
實體 Hyper-v 主機Physical Hyper-V host 四核心 2.66 GHz CPU4-Core 2.66 GHz CPU
32 GB 的 RAM32 GB of RAM
300 GB 的磁碟空間300 GB of Disk Space
1 Gb/秒 (或更快的) 實體網路介面卡1 Gb/s (or faster) physical network adapter
作業系統:如中所定義Operating system: As defined in
本主題開頭的「適用于」。the “Applies to” at the start of this topic.
已安裝 hyper-v 角色Hyper-V Role installed

SDN 基礎結構 VM 角色需求SDN infrastructure VM role requirements

以下顯示 VM 角色的需求。The following shows the requirements for the VM roles.

角色Role vCPU 需求vCPU requirements 記憶體需求Memory requirements 磁碟需求Disk requirements
網路控制站 (三個節點) Network Controller (three nodes) 4個 vcpu4 vCPUs 最小 4 GB4 GB minimum
建議 (8 GB) (8 GB recommended)
適用于作業系統磁片磁碟機的 75 GB75 GB for operating system drive
SLB/MUX (三個節點) SLB/MUX (three nodes) 8 個 vCPU8 vCPUs 建議 8 GB8 GB recommended 適用于作業系統磁片磁碟機的 75 GB75 GB for operating system drive
RAS 閘道RAS Gateway
(三個節點的單一集區(single pool of three nodes
閘道,兩部主動,一個被動) gateways, two active, one passive)
8 個 vCPU8 vCPUs 建議 8 GB8 GB recommended 適用于作業系統磁片磁碟機的 75 GB75 GB for operating system drive
RAS 閘道 BGP 路由器RAS Gateway BGP router
針對 SLB/MUX 對等互連for SLB/MUX peering
(或者使用 ToR 參數(alternatively use ToR switch
作為 BGP 路由器) as BGP Router)
2個 vcpu2 vCPUs 2 GB2 GB 適用于作業系統磁片磁碟機的 75 GB75 GB for operating system drive

如果您使用 System Center-Virtual Machine Manager (VMM) 進行部署,則 VMM 和其他非 SDN 基礎結構需要額外的基礎結構 VM 資源。If you use System Center - Virtual Machine Manager (VMM) for deployment, additional infrastructure VM resources are required for VMM and other non-SDN infrastructure. 若要深入瞭解,請參閱 System Center Virtual Machine Manager 的系統需求To learn more, see System requirements for System Center Virtual Machine Manager.

擴充您的基礎結構Extending your infrastructure

基礎結構的大小和資源需求取決於您打算裝載的租使用者工作負載 Vm。The sizing and resource requirements for your infrastructure depend on the tenant workload VMs that you plan to host. 基礎結構 Vm 的 CPU、記憶體和磁片需求 (例如:網路控制站、SLB、閘道等) 是在上表中定義。The CPU, memory, and disk requirements for the infrastructure VMs (for example: Network Controller, SLB, gateway, and so on) are defined in the previous table. 您可以視需要新增更多基礎結構 Vm 以進行調整。You can add more infrastructure VMs to scale as needed. 不過,在 Hyper-v 主機上執行的任何租使用者 Vm 都有自己的 CPU、記憶體和磁片需求,您必須考慮這些 Vm。However, any tenant VMs running on the Hyper-V hosts have their own CPU, memory, and disk requirements that you must consider.

當租使用者工作負載 Vm 在實體 Hyper-v 主機上開始耗用太多資源時,您可以藉由新增額外的實體主機來擴充您的基礎結構。When the tenant workload VMs start to consume too many resources on the physical Hyper-V hosts, you can extend your infrastructure by adding additional physical hosts. 您可以使用 Windows Admin Center、VMM 或 PowerShell 腳本,透過網路控制站來建立新的伺服器資源。You can use either Windows Admin Center, VMM, or PowerShell scripts to create new server resources through the Network Controller. 要使用的方法取決於您最初部署基礎結構的方式。The method to use depends on how you initially deployed the infrastructure. 如果您需要為 HNV 提供者網路新增其他 IP 位址,您可以建立新的邏輯子網, (具有主機可使用的對應 IP 集區) 。If you need to add additional IP addresses for the HNV Provider network, you can create new logical subnets (with corresponding IP Pools) that the hosts can use.

階段式部署Phased deployment

根據您的需求,您可能需要部署 SDN 基礎結構的子集。Based on your requirements, you may need to deploy a subset of the SDN infrastructure. 例如,如果您只想要在資料中心裝載客戶工作負載,且不需要外部通訊,您可以部署網路控制站,並略過部署 SLB/MUX 和閘道 Vm。For example, if you want to only host customer workloads in your datacenter, and external communication is not required, you can deploy Network Controller and skip deploying SLB/MUX and gateway VMs. 以下說明 SDN 基礎結構的階段式部署的網路功能基礎結構需求。The following describes networking feature infrastructure requirements for a phased deployment of the SDN infrastructure.

功能Feature 部署需求Deployment requirements 網路需求Network requirements
邏輯網路管理Logical Network management
存取控制清單 (Acl) (的 VLAN 型網路) Access control lists (ACLs) (for VLAN-based network)
適用于 VLAN 型網路的服務品質 (QoS) () Quality of Service (QoS) (for VLAN-based networks)
網路控制站Network Controller NoneNone
虛擬網路Virtual Networking
使用者定義路由User Defined Routing
虛擬網路) 的 Acl (ACLs (for virtual network)
加密的子網Encrypted Subnets
虛擬網路) 的 QoS (QoS (for virtual networks)
虛擬網路對等互連Virtual network peering
網路控制站Network Controller HNV PA VLAN、Subnet、路由器HNV PA VLAN, Subnet, Router
輸入/輸出 NATInbound/Outbound NAT
負載平衡Load Balancing
網路控制站Network Controller
SLB/MUXSLB/MUX
HNV PA 網路上的 BGPBGP on HNV PA network
私用和公用 VIP 子網Private and Public VIP subnets
GRE 閘道連線GRE gateway connections 網路控制站Network Controller
閘道Gateway
HNV PA 網路上的 BGPBGP on HNV PA network
GRE VIP 子網GRE VIP subnet
IPSec 閘道連線IPSec gateway connections 網路控制站Network Controller
SLB/MUXSLB/MUX
閘道Gateway
HNV PA 網路上的 BGPBGP on HNV PA network
公用 VIP 子網Public VIP subnet
L3 閘道連線L3 gateway connections 網路控制站Network Controller
閘道Gateway
租使用者 VLAN、子網、路由器Tenant VLAN, Subnet, Router
租使用者 VLAN 上的 BGP 是選擇性的。BGP on tenant VLAN optional.

下一步Next steps

如需相關資訊,另請參閱:For related information, see also: