Traditional load balancing and failover uses the IP addresses assigned by each ISP which means that the public IP address used changes depending on which WAN traffic is routed through. Ecessa software version 11.2.0 introduces features that allow for same IP failover. This is accomplished by routing traffic from a remote site through another Ecessa appliance, running in a data center or on a cloud provider such as Azure, which acts as the gateway to the Internet for traffic from other sites with Ecessa devices.
- An Ecessa device that will act as the gateway running software version 11.2.0 or greater
- One or more remote sites with Ecessa devices
- WAN Virtualization connecting each remote site to the gateway
1) Enable the SNAT Unmatched Traffic option by selecting the option on the WAN page of the web interface.
2) Configure and enable OSPF in the Dynamic Routing section of the web interface. The Export Default Route option will advertise to connected Ecessa devices that this Ecessa instance should be the default route for all outbound traffic. Both WAN Virtualization and the WAN(s) should be added in the Configure OSPF Interfaces section.
Remote site configuration
1) Configure and enable OSPF in the Dynamic Routing section of the web interface. Both WAN Virtualization and the LAN(s) should be added in the Configure OSPF Interfaces section.
- If there is outbound traffic from a remote site that should not go through the gateway Ecessa, and instead use the local WANs directly, then Medium Priority Static Routes will override OSPF
- For seamless failover the Duplicate option can be used within WAN Virtualization