I am pretty sure people has seen this issue , well yes i did encounter this one when establishing internal standard LN for one of my customer and back-end machines lost the internet connectivity.
Before we go ahead and fix this issue and talk about few interesting point lets understand Standard Load Balancer first -
Azure Load Balancer allows you to scale your applications and create high availability for your services. Load Balancer can be used for inbound as well as outbound scenarios and provides low latency, high throughput, and scales up to millions of flows for all TCP and UDP applications.
Standard Load Balancer is a new Load Balancer product for all TCP and UDP applications with an expanded and more granular feature set over Basic Load Balancer.
While Basic Load Balancer exists within the scope of an availability set, a Standard Load Balancer is fully integrated with the scope of a virtual network and all virtual network concepts apply.
Well will be discussing comparison in next post for now lets fix the issue as stated above.
To fix the backend VM's internet issue - you need to create one more standard Public LB and create the outbound rule which would allow the backend VM's talk to the internet via Public ip of LB.
When you configure backend pool if your VM has basic public Ip it wouldnt show to configure.
Backend VM's either should not have public IP or should have Standard Public IP.
you can create outbound rule via Azure CLI
Before we go ahead and fix this issue and talk about few interesting point lets understand Standard Load Balancer first -
Azure Load Balancer allows you to scale your applications and create high availability for your services. Load Balancer can be used for inbound as well as outbound scenarios and provides low latency, high throughput, and scales up to millions of flows for all TCP and UDP applications.
Standard Load Balancer is a new Load Balancer product for all TCP and UDP applications with an expanded and more granular feature set over Basic Load Balancer.
While Basic Load Balancer exists within the scope of an availability set, a Standard Load Balancer is fully integrated with the scope of a virtual network and all virtual network concepts apply.
Well will be discussing comparison in next post for now lets fix the issue as stated above.
To fix the backend VM's internet issue - you need to create one more standard Public LB and create the outbound rule which would allow the backend VM's talk to the internet via Public ip of LB.
When you configure backend pool if your VM has basic public Ip it wouldnt show to configure.
Backend VM's either should not have public IP or should have Standard Public IP.
you can create outbound rule via Azure CLI
az network lb outbound-rule create \
--resource-group yourRG \
--lb-name yourlb \
--name outboundrule \
--frontend-ip-configs yourfrontendip \
--protocol All \
--idle-timeout 15 \
--outbound-ports 10000 \
--address-pool your outboundpool
for details you can check the below link
https://docs.microsoft.com/en-us/azure/load-balancer/configure-load-balancer-outbound-cli
No comments:
Post a Comment