Client address space: The address space that is located on your on-premises site. In this case, replace the IP address values with your own if you want to create a working connection. Typically, when working with IP address values for Address space, you want to coordinate with your network administrator in order to avoid overlapping address spaces, which can affect routing. You can use these values to create a test environment, or refer to them to better understand the examples in this article. 
The examples in this article use the following values. Sample configuration values for this exercise For more information about Azure PowerShell in general, see the Azure PowerShell documentation. To install the SM cmdlets, see Install Service Management cmdlets. These cmdlets are different from the AzureRM or Az cmdlets. Instead, you must install the latest version of the Azure Service Management (SM) PowerShell cmdlets locally on your computer. When working with the classic deployment model, you can't use Azure Cloud Shell.
PowerShell is required in order to specify the shared key and create the VPN gateway connection. None of the subnets of your on-premises network can over lap with the virtual network subnets that you want to connect to. When you create this configuration, you must specify the IP address range prefixes that Azure will route to your on-premises location. If you are unfamiliar with the IP address ranges located in your on-premises network configuration, you need to coordinate with someone who can provide those details for you. Verify that you have an externally facing public IPv4 address for your VPN device. For more information about compatible VPN devices and device configuration, see About VPN Devices. Make sure you have a compatible VPN device and someone who is able to configure it. We recommend that you use the Resource Manager deployment model, as the classic model is legacy. If you want to work in the Resource Manager deployment model, see Create a Site-to-Site connection (Resource Manager). Verify that you want to work in the classic deployment model. Verify that you have met the following criteria before beginning configuration: 
For more information about VPN gateways, see About VPN gateway.
This type of connection requires a VPN device located on-premises that has an externally facing public IP address assigned to it. A Site-to-Site VPN gateway connection is used to connect your on-premises network to an Azure virtual network over an IPsec/IKE (IKEv1 or IKEv2) VPN tunnel.
0 kommentar(er)
