Hi,
Background - even though Azure web interface does not support assigning multiple public IPs, after reaching out to MS support while back, I was able to use the powershell scrips and actually assign multiple front end configs to a public facing LB. All of this worked out great as I could route the traffic from my sites to backend servers using NAT and remap ports etc.
Issue - Looks like there is a limit on the number of front end configurations that can be assigned to the same LB. I am getting the below error:
===========================================
Set-AzureRmLoadBalancer : A load balancer cannot have more than 5 FrontendIPConfigurations.
At line:1 char:180
+ ... ss $PublicIp | Set-AzureRmLoadBalancer
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [Set-AzureRmLoadBalancer], CloudException
+ FullyQualifiedErrorId : Microsoft.Azure.Commands.Network.SetAzureLoadBalancerCommand
===========================================
Attempt to fix - I have tried to create a second LB, and keep scaling out this way, but looks like it cannot use VMs from the same availability sets which are used from other/existing LBs. So, it comes down to me having to add more VMs, and create new availability set. So basically, for every 5 public IPs, I need a new LB, which needs new availability set, which in the end means more VMs...
Is there a way to increase the number of front end configs per load balancer?
Thanks a lot for your comments!
Ivan S / GalaxyLinq