Loadbalancer multiple ports in one frontend rule
For NVA's (Network Virtual Appliances) in a HA setup, a load balancer is used to spread traffic across two active devices.
There are applications (i.e. AD) that uses a lot of ports for communication or even dynamic port-ranges.
Unfortunately at this moment the LB only allows up to 150 rules with a single port.
Ideally it should be possible to load balance all ports (*), especially when it is a security device and you want to perform zero trust even within the Azure environment.
This is merely a problem on the Internal Load Balancer.
Rob
shared this idea
This has been delivered as part of the Load Balancer Standard preview. Please take a look here for more details: https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-ha-ports-overview
4 comments
-
Itay
commented
what about Public LB? how can I make it pass all ports and traffic?
-
Mike
commented
This can be closed with HA Ports annoucned at ignite.
-
Jeremy Wilton
commented
Yes, this is needed for firewalls in Azure or otherwise more direct layer 2 access for VIPs so they can do native HA and not requiring load balancers on the public and private side.
HA firewalls that function fully are a must. They work in AWS.
-
Michel van Kessel
commented
This is exactly what we are waiting for!