none
error configuring ipv6 load balancer RRS feed

  • Question

  • I'm trying to configure a load balancer to use ipv4 + ipv6.
    I'm roughly following the guide at:
        https://docs.microsoft.com/en-us/azure/virtual-network/scripts/virtual-network-cli-sample-ipv6-dual-stack

    I created a "standard" instead of "basic":
        az network lb create --name dd_portal_lb --resource-group dd1rg --sku standard \
            --frontend-ip-name dd_portal_lbfe4 \
            --public-ip-address ddvip_portal_ip4  \
            --backend-pool-name dd_portal_lbbe4

    this worked ok. I then try to add the IPv6. and do:

        az network lb frontend-ip  create --lb-name dd_portal_lb --resource-group dd1rg \
            --name dd_portal_lbfe6 --public-ip-address ddvip_portal_ip6

    I get the error:
        IPv6 frontendIpconfiguration is not permitted on Load balancer /subscriptions/0f2ff606-ecfb-4015-8fb8-8a079a60ba1a/resourceGroups/dd1rg/providers/Microsoft.Network/loadBalancers/dd_portal_lb since it was used or is being used in a configuration that required load balancing or public ip on secondary ipconfigs or secondary nics.

    Thursday, May 23, 2019 8:59 PM

Answers

  • Standard LB uses Standard IP. 

    Standard IP doesn't support IPv6. Here is the screenshot:

    It is a limitation as of now. Feature will be added in the future. 

    Regards, 

    Msrini

    • Marked as answer by jeffw000 Friday, May 24, 2019 3:39 PM
    Friday, May 24, 2019 3:20 PM
    Moderator

All replies

  • This sounds like one of your VMs has multiple NICs using IPv6 or one of your VMs has a public IPv6 address. Please see the Details and Limitations section for IPv6 support for Standard Load Balancers for more info. 

    If this is not the case, please let me know!

    Thursday, May 23, 2019 10:01 PM
    Moderator
  • nope.

    no VMs have been created yet in this resource-group.

    no VMs in any other resource-groups have IPv6 addresses.


    Thursday, May 23, 2019 10:38 PM
  • If you have any VMs in backend pools, please make sure that they have a IPv6 configuration, and if they have any public IP addresses, they are Standard SKU. 

    You can also try removing everything from backend pools. I assume you are following This Document on creating an IPv6 LB with the CLI

    If you delete and recreate the LB, use a different resource group and name. 

    Let me know if this helps, if not I will repro and see if I get the same error. 

    Thursday, May 23, 2019 11:19 PM
    Moderator
  • I have deleted the resource-group and started over using a new name.

    I still get the same error.

    I have cut the config down to a minimum example:

    az group create --name xxt4rg --location eastus
    az network public-ip create --name xxt4vip_data_ip4     --resource-group xxt4rg --sku standard --allocation-method static --version IPv4
    az network public-ip create --name xxt4vip_data_ip6     --resource-group xxt4rg --sku standard --allocation-method static --version IPv6
    az network lb create --name xxt4_data_lb --resource-group xxt4rg --sku standard --frontend-ip-name xxt4_data_lbfe4 --public-ip-address xxt4vip_data_ip4  --backend-pool-name xxt4_data_lbbe4
    az network lb frontend-ip  create --lb-name xxt4_data_lb --resource-group xxt4rg --name xxt4_data_lbfe6 --public-ip-address xxt4vip_data_ip6
    

    If I use the "basic" sku instead of "standard", the above completes successfully.

    Friday, May 24, 2019 1:04 AM
  • Hi, 

    Standard Load balancer uses Standard SKU IPs. 

    Standard SKU IPs doesn't support IPv6 and hence your deployment fails. 

    IPv6 for Load balancer only supports Basic SKU as of now. 

    Regards, 

    Msrini

    Friday, May 24, 2019 4:16 AM
    Moderator
  • for real? is this limitation documented anywhere?

    the documentation I find says:

        > Any scenario that's possible with Basic Load Balancer can also be created with Standard Load Balancer, although the approaches might differ slightly

    and also:

        > New designs should adopt Standard Load Balancer

    thanks


    Friday, May 24, 2019 2:31 PM
  • Standard LB uses Standard IP. 

    Standard IP doesn't support IPv6. Here is the screenshot:

    It is a limitation as of now. Feature will be added in the future. 

    Regards, 

    Msrini

    • Marked as answer by jeffw000 Friday, May 24, 2019 3:39 PM
    Friday, May 24, 2019 3:20 PM
    Moderator