Skip to content

Commit 1cfc042

Browse files
authored
Merge pull request #194076 from tanuballa/patch-206
add info for IPv6 Public Preview
2 parents e7f05d3 + 333b1d2 commit 1cfc042

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

articles/expressroute/expressroute-howto-set-global-reach.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,14 @@ Enable connectivity between your on-premises networks. There are separate sets o
6969
```azurepowershell-interactive
7070
Add-AzExpressRouteCircuitConnectionConfig -Name 'Your_connection_name' -ExpressRouteCircuit $ckt_1 -PeerExpressRouteCircuitPeering $ckt_2.Peerings[0].Id -AddressPrefix '__.__.__.__/29'
7171
```
72+
73+
> [!NOTE]
74+
> IPv6 support for ExpressRoute Global Reach is now in Public Preview. To add an IPv6 Global Reach connection, you must specify a /125 IPv6 subnet for *-AddressPrefix* and an *-AddressPrefixType* of *IPv6*.
75+
76+
```azurepowershell-interactive
77+
Add-AzExpressRouteCircuitConnectionConfig -Name 'Your_connection_name' -ExpressRouteCircuit $ckt_1 -PeerExpressRouteCircuitPeering $ckt_2.Peerings[0].Id -AddressPrefix '__.__.__.__/125' -AddressPrefixType IPv6
78+
```
79+
7280
3. Save the configuration on circuit 1 as follows:
7381
7482
```azurepowershell-interactive
@@ -95,6 +103,14 @@ If the two circuits are not in the same Azure subscription, you need authorizati
95103
```azurepowershell-interactive
96104
Add-AzExpressRouteCircuitConnectionConfig -Name 'Your_connection_name' -ExpressRouteCircuit $ckt_1 -PeerExpressRouteCircuitPeering "circuit_2_private_peering_id" -AddressPrefix '__.__.__.__/29' -AuthorizationKey '########-####-####-####-############'
97105
```
106+
107+
> [!NOTE]
108+
> IPv6 support for ExpressRoute Global Reach is now in Public Preview. To add an IPv6 Global Reach connection, you must specify a /125 IPv6 subnet for *-AddressPrefix* and an *-AddressPrefixType* of *IPv6*.
109+
110+
```azurepowershell-interactive
111+
Add-AzExpressRouteCircuitConnectionConfig -Name 'Your_connection_name' -ExpressRouteCircuit $ckt_1 -PeerExpressRouteCircuitPeering $ckt_2.Peerings[0].Id -AddressPrefix '__.__.__.__/125' -AddressPrefixType IPv6 -AuthorizationKey '########-####-####-####-############'
112+
```
113+
98114
3. Save the configuration on circuit 1.
99115

100116
```azurepowershell-interactive
@@ -122,6 +138,15 @@ Remove-AzExpressRouteCircuitConnectionConfig -Name "Your_connection_name" -Expre
122138
Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt_1
123139
```
124140

141+
> [!NOTE]
142+
> IPv6 support for ExpressRoute Global Reach is now in Public Preview. To delete an IPv6 Global Reach connection, you must specify an *-AddressPrefixType* of *IPv6* like in the following command.
143+
144+
```azurepowershell-interactive
145+
$ckt_1 = Get-AzExpressRouteCircuit -Name "Your_circuit_1_name" -ResourceGroupName "Your_resource_group"
146+
Remove-AzExpressRouteCircuitConnectionConfig -Name "Your_connection_name" -ExpressRouteCircuit $ckt_1 -AddressPrefixType IPv6
147+
Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt_1
148+
```
149+
125150
You can run the Get operation to verify the status.
126151

127152
After the previous operation is complete, you no longer have connectivity between your on-premises network through your ExpressRoute circuits.

0 commit comments

Comments
 (0)