Can't connect VMs to backend pool Load balancer

Question

_{Friday, October 19, 2018 9:47 AM}

As per my previous posting, I'm following the steps in https://docs.microsoft.com/en-us/azure/load-balancer/tutorial-load-balancer-port-forwarding-portal to add the created VMs to backend address pool.

When I land on the created Backend pool I don't find the 'Add a target network IP configuration' button. No network/subnetwork is listed (although I've created them), nor the VMs. All my resources are created in Western Europe.

I tried to change the VMs public IP address from Static to Dynamic but I've got the following message when saving:

Failed to save configuration changes to public IP address 'commManagerVM1-ip'. Error: Public IP address /subscriptions/0917f549-b373-4b4e-b5c4-98ef9cc56a17/resourceGroups/commManagerResourceGroupSLB/providers/Microsoft.Network/publicIPAddresses/commManagerVM1-ip is in use by ipconfig /subscriptions/0917f549-b373-4b4e-b5c4-98ef9cc56a17/resourceGroups/commManagerResourceGroupSLB/providers/Microsoft.Network/networkInterfaces/commmanagervm1453/ipConfigurations/ipconfig1 and cannot be updated from static to dynamic.

To note that I previoulsy needed to switch from public IP address from initial Dynamic to Static so that I can connect to the VMs (to install IIS) in RDP.

All replies (7)

_{Tuesday, October 23, 2018 12:18 PM ✅Answered | 1 vote}

Hello,

Assuming that you created a 'Standard_SKU' load balancer (which is proposed in the guides that you followed), you should also have 'Standard_SKU' IPs. You can determine that from the portal. Find the 'Public IP address' resource and check the SKU.

If you have 'Basic_SKU' IPs, you should create some 'Standard_SKU' IPs and attach them to your VMs.

After that, you should be able to add them to the Load Balancer pool.

As an alternative, delete the Load Balancer and re-create it using the 'Basic_SKU'. Then, you will be able to assign the VMs in the pool.

_{Friday, October 19, 2018 10:38 PM}

Is your scale set hosted in it's own resource group or is it located in a resource group with other VMs, Vnets, etc? 

Could you share some screenshots so I can better understand where you are seeing the problem? 

_{Saturday, October 20, 2018 8:20 AM}

Hi Micah,

I've been following this example https://docs.microsoft.com/en-us/azure/load-balancer/tutorial-load-balancer-port-forwarding-portal recommended by an MSFT engineer on Azure chat. FYI, I am in France, so all my resources are created in West Europe location:



and

I have implemented all the steps until adding the VMs to the backend address pool:

 When I click on commManager BackEndPool I get this:

with nothing in the drop-down lists, and no Add a target network IP configuration button, as mentioned in the tutorial.

Here are commManagerVM1 and commManagerVM2 (my two VMs) profiles:

In the example above that I implement there is no mention of Azure Scale Set, therefore I can't help you with that.

I provide you these screenshots for now, hoping they'd be meaningful to you. Anyway, please let me know what additional infos you need so that I can advance to my ultimate scope which is the port forwarding.

Thanks

_{Monday, October 22, 2018 9:26 PM}

Thanks for the extra details. 

It looks like you have created a load balancer using the Standard SKU rather than the basic sku. 

/en-us/azure/load-balancer/load-balancer-standard-overview

Did you have a reason for picking Standard vs Basic? 

Could you try adding a new load balancer and select the Basic sku and see if you get the same results? 

_{Tuesday, October 23, 2018 11:38 AM}

I am sorry but I am confused: the first step in the MSDN tutorial, that I literally follow, (https://docs.microsoft.com/en-us/azure/load-balancer/tutorial-load-balancer-port-forwarding-portal) says "Create a Standard Load Balancer". As my scope is to eventually make working a client-Cloud_server application requiring port fowarding, I completely rely on this forum (on you!) for how to right configure Azure as communication and hosting infrastructure.

Thus, to put it simple: I just followed the MSFT tutorial, no idea about using Standard vs Basic.

PS: Here is something that may be helpful to you. It is about the IP public address that was created by Azure with a new VM. Initially the address was of type 'Dynamic', but I had to change it to 'Static' because the connection via RDP was not working (RDP was needed to install IIS); the changed solved that problem. When I got the last problem - which is the object of this thread - I tried to change back the VM IP address from 'Static' to 'Dynamic' but trying to save the configuration gives the following error:

The 'Static' type doesn't bother me but it may tell you something related to the backend pool attachment to the LB.

_{Thursday, October 25, 2018 5:11 PM}

Thank you, that solved the problem.

I have delayed my reply because it took some time to create Standard type Public addresses. The tutorial should be updated by MSFT to account for this issue.

_{Thursday, October 25, 2018 5:24 PM}

Thanks for the update. I have forwarded this to our Networking lead to work in updating the doc.