1
votes

I am having difficulties setting up my internal load balancer to process requests.

I have setup my vnet, vms, load balancer etc using this template

Azure Resource manager template

one of the differences between the template and my setup is that i am using a different backend port. I have setup the probe to also look at this port use this port aswell.

I have opened the port on each vm (windows 2012 R2 Datacenter). I can successfully call one vm to the other using the vip.

I'm aware I can't call the internal load balancer from a virtual machine that is being load balanced, so i setup a third test vm sitting in the same vnet and region etc, when i try to call the load balancer fromhere i simply get a page not found.

Thanks in advance for your help

2

2 Answers

1
votes

Hi Figured out what was happening. The setup was ok. The problem turned out to be related to the probe setup. I had changed the probe to http and prvided it a url, but i forgot the url returns 301. The ILB is looking for 200 only on these Probes otherwise it will throw the VM out of the pool. To fix the issue i just went back to TCP probe on the VM (backend) port.

0
votes

which port do you use? You may want to check your firewall on the VM and ensure your port is not blocked