You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 18
Next »
Abiquo supports Standard SKU load balancers and Basic SKU load balancers.
Azure Element | Notes |
|
---|
Azure documentation | |
|
Load balancer name | The load balancer name can't have white spaces |
|
Algorithm | - DEFAULT
- SOURCEIP
- SOURCEIPPROTOCOL
|
|
Addresses and networks | - The load balancer must have one and only one public OR private address
- The load balancer can only be attached to one subnet. Mandatory for private addresses
|
|
Routing rules | - You must create at least one routing rule.
There must always be at least one routing rule in the load balancer - You can only create one routing rule per incoming port and one rule per outgoing port
(i.e. two rules cannot receive traffic on the same port or route it to the same port).
|
|
Routing rule protocol in | TCP and UDP |
|
Routing rule port in | |
|
SSL certificate | Not yet supported |
|
Health check | - One health check must be configured for the load balancer
- Protocols supported for health check
- Basic: TCP, HTTP
- Standard: TCP, HTTP, HTTPS
- Health check interval must be between 5 and 2147483646
- Health check port must be between 1 and 65535
|
|
Firewalls | - Basic: Azure NSGs are not supported for Basic load balancers
- Standard: You must add a firewall to your VMs to allow load balancer traffic
|
|
Nodes | - Azure does not allow you to attach a VM with a Basic hardware profile to a load balancer
- Basic: You must add VMs to an Availability set in order to use them with a load balancer
- Standard: The VMs must be in the same virtual network
|
|