
$gwPool = Get-NetworkControllerGatewayPool -ConnectionUri $uri # Retrieve the Gateway Pool configuration Verify that the gateway pool object exists in network controller.
#Virtual gateway how to#
The Windows PowerShell example scripts and commands in this topic demonstrate how to deploy a tenant virtual gateway on a RAS Gateway with each of these options.īefore you run any of the example Windows PowerShell commands and scripts provided, you must change all variable values so that the values are appropriate for your deployment.
IPSec site-to-site virtual private network (VPN). When you deploy a Tenant Virtual Gateway, you have the following configuration options: Network connection options When you provide site-to-site connectivity, your customers can connect their tenant virtual network to an external network, such as a tenant enterprise network, a service provider network, or the Internet. Network Controller automatically determines the best RAS Gateway to use when you deploy a new virtual gateway for your tenants.Įach virtual gateway corresponds to a particular tenant and consists of one or more network connections (site-to-site VPN tunnels) and, optionally, Border Gateway Protocol (BGP) connections. RAS gateway supports up to one hundred tenants, depending on the bandwidth used by each tenant. In this topic, you add tenant virtual gateways to instances of RAS gateway that are members of gateways pools, using Network Controller. Learn how to use Windows PowerShell cmdlets and scripts to provide site-to-site connectivity for your tenant's virtual networks.
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Azure Stack HCI, versions 21H2 and 20H2