- Shared Load Balancers are now configurable in a self-service fashion.
- Customers can log in directly to their Dedicated Load Balancers.
- With the Shared Load Balancers the External IP sits directly on the Load Balancer.
- With a Dedicated Load Balancer, the VIP is an internal IP. In order to provide external access, a MIP/NAT must be added to the firewall, which will point to the internal VIP.
- If a customer wants to use a Load Balancer to access an internal VIP over their site to site VPN they must use a dedicated Load Balancer. It is not possible to access an internal VIP on the the Shared Load Balancer over a site to site VPN.
- All shared Load Balancers are in a High Availability pair. If either node goes down there will be no downtime. Dedicated Load Balancers can be put in a HA pair by request.
- MIP's are not accessible from within the datacenter. If you need to reach a public IP from both inside and outside the datacenter, you need to use the Shared Load Balancer.
- Dedicated Load balancer support is limited in that Customer Care engineers will confirm the infrastructure state and virtual machine state for the dedicated load balancer, though customers are responsible for all Day 1, 2 and N operational support.
- Tracking a Dedicated Load Balancer license expiration date is performed by the customer, please reference our License Management Article.
Definitions in regards to this article:
VIP - Virtual IP
MIP - Mapped IP
NAT - Network Address Translation
VIP - The IP used for the Virtual Server. A VIP includes both an IP and a port. Separate VIP's are required for multiple ports used with the same IP.
Internal VIP - A VIP on a dedicated Load Balancer. This will always be an internal IP
External VIP - A VIP on a shared Load Balancer. This will always be an external IP and is accessible from outside of the datacenter or within
MIP/NAT - A one to one IP translation. In regards to this article, it is a Public IP that points to an Internal IP. Example: 126.96.36.199 -> 10.90.250.250