If you have a remote-access configuration in which you are using two or more security appliances or VPN Concentrators connected on the same network to handle remote sessions, you can configure these devices to share their session load. This feature is called load balancing. To implement load balancing, group together logically two or more devices on the same private LAN-to-LAN network, private subnet, and public subnet into a virtual cluster.
The way how load balancing works is:
-The phase 1 negotiation is done on the virtual master. - An ike re-direct packet with the IP of a slave device was sent by the virtual master to the client. - The client will start a new phase 1 and 2 negotiation on the slave device just like a standalone vpn connection.
You can also have a configuration that combines both Load-Balancing and Failover. For illustration, the client connects to the IP address of the cluster and is redirected to the least-loaded ASA in the cluster. If that ASA goes down, the standby unit takes over immediately, and there is no impact to the client's tunnel.
Note:Only the Active units participate in Load Balancing. Should the Active unit of a FO-pair go down, then its Standby mate would become active and then join the Load Balancing cluster mechanism to distribute the VPN session load.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...