Add IPv6 support for private peering using Azure PowerShell

This article describes how to add IPv6 support to connect via ExpressRoute to your resources in Azure using Azure PowerShell.

The steps and examples in this article use Azure PowerShell Az modules. To install the Az modules locally on your computer, see Install Azure PowerShell. To learn more about the new Az module, see Introducing the new Azure PowerShell Az module. PowerShell cmdlets are updated frequently. If you are not running the latest version, the values specified in the instructions may fail. To find the installed versions of PowerShell on your system, use the Get-Module -ListAvailable Az cmdlet.

1. Create an ExpressRoute circuit or use an existing circuit. Retrieve the circuit by running the Get-AzExpressRouteCircuit command:

   $ckt = Get-AzExpressRouteCircuit -Name "ExpressRouteARMCircuit" -ResourceGroupName "ExpressRouteResourceGroup"
   

2. Retrieve the private peering configuration for the circuit by running Get-AzExpressRouteCircuitPeeringConfig:

   Get-AzExpressRouteCircuitPeeringConfig -Name "AzurePrivatePeering" -ExpressRouteCircuit $ckt
   

3. Add an IPv6 Private Peering to your existing IPv4 Private Peering configuration. Provide a pair of /126 IPv6 subnets that you own for your primary link and secondary links. From each of these subnets, you assign the first usable IP address to your router as Azure uses the second usable IP for its router.

   Note

   The peer ASN and VlanId should match those in your IPv4 Private Peering configuration.

   Set-AzExpressRouteCircuitPeeringConfig -Name "AzurePrivatePeering" -ExpressRouteCircuit $ckt -PeeringType AzurePrivatePeering -PeerASN 100 -PrimaryPeerAddressPrefix "3FFE:FFFF:0:CD30::/126" -SecondaryPeerAddressPrefix "3FFE:FFFF:0:CD30::4/126" -VlanId 200 -PeerAddressType IPv6
   
   Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt
   

4. After the configuration is saved successfully, get the circuit again by running the Get-AzExpressRouteCircuit command. The response should look similar to the following example:

   Name                             : ExpressRouteARMCircuit
   ResourceGroupName                : ExpressRouteResourceGroup
   Location                         : chinaeast
   Id                               : /subscriptions/***************************/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit
   Etag                             : W/"################################"
   ProvisioningState                : Succeeded
   Sku                              : {
                                        "Name": "Standard_MeteredData",
                                        "Tier": "Standard",
                                        "Family": "MeteredData"
                                      }
   CircuitProvisioningState         : Enabled
   ServiceProviderProvisioningState : Provisioned
   ServiceProviderNotes             :
   ServiceProviderProperties        : {
                                        "ServiceProviderName": "Equinix",
                                        "PeeringLocation": "Washington DC",
                                        "BandwidthInMbps": 50
                                      }
   ExpressRoutePort                 : null
   BandwidthInGbps                  :
   Stag                             : 29
   ServiceKey                       : **************************************
   Peerings                         : [
                                        {
                                          "Name": "AzurePrivatePeering",
                                          "Etag": "W/\"facc8972-995c-4861-a18d-9a82aaa7167e\"",
                                          "Id": "/subscriptions/***************************/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit/peerings/AzurePrivatePeering",
                                          "PeeringType": "AzurePrivatePeering",
                                          "State": "Enabled",
                                          "AzureASN": 12076,
                                          "PeerASN": 100,
                                          "PrimaryPeerAddressPrefix": "192.168.15.16/30",
                                          "SecondaryPeerAddressPrefix": "192.168.15.20/30",
                                          "PrimaryAzurePort": "",
                                          "SecondaryAzurePort": "",
                                          "VlanId": 200,
                                          "ProvisioningState": "Succeeded",
                                          "GatewayManagerEtag": "",
                                          "LastModifiedBy": "Customer",
                                          "Ipv6PeeringConfig": {
                                            "State": "Enabled",
                                            "PrimaryPeerAddressPrefix": "3FFE:FFFF:0:CD30::/126",
                                            "SecondaryPeerAddressPrefix": "3FFE:FFFF:0:CD30::4/126"
                                          },
                                          "Connections": [],
                                          "PeeredConnections": []
                                        },
                                      ]
   Authorizations                   : []
   AllowClassicOperations           : False
   GatewayManagerEtag               :
   

To use IPv6 Private Peering with your existing Azure resources, follow these steps:

1. Retrieve the virtual network that your ExpressRoute circuit is connected to.

   $vnet = Get-AzVirtualNetwork -Name "VirtualNetwork" -ResourceGroupName "ExpressRouteResourceGroup"
   

2. Add an IPv6 address space to your virtual network.

   $vnet.AddressSpace.AddressPrefixes.add("ace:daa:daaa:deaa::/64")
   Set-AzVirtualNetwork -VirtualNetwork $vnet
   

3. Add IPv6 address space to your gateway subnet. The gateway IPv6 subnet should be /64 or larger.

   Set-AzVirtualNetworkSubnetConfig -Name GatewaySubnet -VirtualNetwork $vnet -AddressPrefix "10.0.0.0/26", "ace:daa:daaa:deaa::/64"
   Set-AzVirtualNetwork -VirtualNetwork $vnet
   

4. If you have an existing zone-redundant gateway, run the following to enable IPv6 connectivity (note that it can take up to 1 hour for changes to reflect). Otherwise, create the virtual network gateway using any SKU. If you plan to use FastPath, use UltraPerformance or ErGw3AZ (note that this feature is only available for circuits using ExpressRoute Direct).

   $gw = Get-AzVirtualNetworkGateway -Name "GatewayName" -ResourceGroupName "ExpressRouteResourceGroup"
   Set-AzVirtualNetworkGateway -VirtualNetworkGateway $gw
   

   Note

   If you have an existing gateway that is not zone-redundant (meaning it is Standard, High Performance, or Ultra Performance SKU), you will need to delete and recreate the gateway using any SKU and a Standard, Static public IP address.

To connect to a new set of Azure resources using your IPv6 Private Peering, apply the following steps:

1. Create a dual-stack virtual network with both IPv4 and IPv6 address space. For more information, see Create a virtual network.

2. Create the dual-stack gateway subnet.

3. Create the virtual network gateway using any SKU. If you plan to use FastPath, use UltraPerformance or ErGw3AZ (note that this feature is only available for circuits using ExpressRoute Direct).

4. Link your virtual network to your ExpressRoute circuit.

While IPv6 support is available for connections to deployments in global Azure regions, it doesn't support the following use cases:

• Connections to existing ExpressRoute gateways that aren't zone-redundant. Newly created ExpressRoute gateways of any SKU (both zone-redundant and not) using a Standard, Static IP address can be used for dual-stack ExpressRoute connections

• Use of ExpressRoute with virtual WAN

• Coexistence with VPN Gateway for IPv6 traffic. You can still configure coexistence with VPN Gateway in a dual-stack virtual network, but VPN Gateway only supports IPv4 traffic.

• It isn't possible to connect a dual-stack ExpressRoute Virtual Network Gateway to an ExpressRoute Circuit that only has IPv4 enabled on the Private Peering. IPv6 must also be enabled on the ExpressRoute Circuit. You must also configure IPv6 on your on-premises CPE device.

To troubleshoot ExpressRoute problems, see the following articles:

• Verifying ExpressRoute connectivity
• Troubleshooting network performance