You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A cross-premises VPN connection consists of an Azure VPN gateway, an on-premises VPN device, and an IPsec S2S VPN tunnel connecting the two. The typical work flow includes the following steps:
21
+
A cross-premises VPN connection consists of an Azure VPN gateway, an on-premises VPN device, and an IPsec S2S VPN tunnel connecting the two.
22
+
23
+
The typical workflow includes the following steps:
22
24
23
25
1. Create and configure an Azure VPN gateway (virtual network gateway).
24
26
1. Create and configure an Azure local network gateway that represents your on-premises network and VPN device.
25
27
1. Create and configure an Azure VPN connection between the Azure VPN gateway and the local network gateway.
26
28
1. Configure the on-premises VPN device represented by the local network gateway to establish the actual S2S VPN tunnel with the Azure VPN gateway.
27
29
28
-
You can complete steps 1 through 3 using the Azure [portal](./tutorial-site-to-site-portal.md), [PowerShell](vpn-gateway-create-site-to-site-rm-powershell.md), or [CLI](vpn-gateway-howto-site-to-site-resource-manager-cli.md). The last step involves configuring the on-premises VPN devices outside of Azure. This feature allows you to download a configuration script for your VPN device with the corresponding values of your Azure VPN gateway, virtual network, and on-premises network address prefixes, and VPN connection properties, etc. already filled in. You can use the script as a starting point, or apply the script directly to your on-premises VPN devices via the configuration console.
30
+
You can complete steps 1 through 3 in the workflow using the Azure [portal](./tutorial-site-to-site-portal.md), [PowerShell](vpn-gateway-create-site-to-site-rm-powershell.md), or [CLI](vpn-gateway-howto-site-to-site-resource-manager-cli.md). Step 4 involves configuring the on-premises VPN devices outside of Azure. The steps in this article help you download a configuration script for your VPN device with the corresponding values of your Azure VPN gateway, virtual network, on-premises network address prefixes, and VPN connection properties already filled in. You can use the script as a starting point, or apply the script directly to your on-premises VPN devices via the configuration console.
29
31
30
32
The syntax for each VPN device configuration script is different and heavily dependent on the models and firmware versions. Pay special attention to your device model and version information against the available templates.
31
33
32
-
* Some parameter values must be unique on the device, and can't be determined without accessing the device. The Azure-generated configuration scripts prefill these values, but you need to ensure the provided values are valid on your device. For examples:
34
+
* Some parameter values must be unique on the device, and can't be determined without accessing the device. The Azure-generated configuration scripts prefill these values, but you need to ensure the provided values are valid on your device. For example:
33
35
34
36
* Interface numbers
35
37
* Access control list numbers
@@ -40,7 +42,7 @@ The syntax for each VPN device configuration script is different and heavily dep
40
42
41
43
## Download the configuration script - Azure portal
42
44
43
-
Create an Azure VPN gateway, local network gateway, and a connection resource connecting the two. The following page guides you through the steps:
45
+
Create an Azure VPN gateway, local network gateway, and a connection resource connecting the two. The following article guides you through the steps:
44
46
45
47
*[Create a Site-to-Site connection in the Azure portal](./tutorial-site-to-site-portal.md)
0 commit comments