Skip to content

Commit 894e884

Browse files
authored
PR review edit
1 parent 4c576c2 commit 894e884

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/expressroute/expressroute-howto-coexist-resource-manager.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -131,10 +131,10 @@ This procedure walks you through creating a VNet and Site-to-Site and ExpressRou
131131
```azurepowershell-interactive
132132
$azureVpn = New-AzVirtualNetworkGateway -Name "VPNGateway" -ResourceGroupName $resgrp.ResourceGroupName -Location $location -IpConfigurations $gwConfig -GatewayType "Vpn" -VpnType "RouteBased" -GatewaySku "VpnGw1" -Asn $VNetASN
133133
```
134-
> [!NOTE]
135-
> The default ASN of 65515 must be used for coexistance of gateways. See limits and limitations
136-
>
137134

135+
> [!NOTE]
136+
> For coexisting gateways, you must use the default ASN of 65515. See [limits and limitations](#limits-and-limitations).
137+
>
138138
139139
You can find the BGP peering IP and the AS number that Azure uses for the VPN gateway in $azureVpn.BgpSettings.BgpPeeringAddress and $azureVpn.BgpSettings.Asn. For more information, see [Configure BGP](../vpn-gateway/vpn-gateway-bgp-resource-manager-ps.md) for Azure VPN gateway.
140140
5. Create a local site VPN gateway entity. This command doesn’t configure your on-premises VPN gateway. Rather, it allows you to provide the local gateway settings, such as the public IP and the on-premises address space, so that the Azure VPN gateway can connect to it.

0 commit comments

Comments
 (0)