Configuring High Availability across separate physical locations
12/20/2019 36 35224
DESCRIPTION: Configuring High Availability across separate physical locations
High Availability is supported across separate physical location using identical SonicWall Model. Here are some of the key factors to be considered when choosing this deployment:
High Availability link can only be established using Physical Interface on SonicWall.
High Availability link latency should be low and less than 500 msec.
High Availability link is recommended to be dedicated link between the HA interface on firewall located at separate physical locations however if using a shared LAN/WAN link for HA link using VLAN, L2 QOS (Cos) is required to prioritize the HA traffic.
High Availability Stateful Synchronization depends on Throughput and Bandwidth of the HA link/Dedicated HA Data link. Customer will require 1 Gig/10 Gig for HA Data depending on their deployment. It might be recommended to disable HA Stateful Synchronization depending on Throughput and Bandwidth of the Circuit.
High Availability link can be established using Dark Fiber, VPLS, L2 VPN ensuring low latency.
High Availability uses a Custom Ether Type hence it is recommended that any intermediate devices support it.
In High Availability setup with STP enabled on switches, it is required for all switch ports uplink to firewall interfaces should be configured for Spanning Tree Port Fast (Cisco) or similar configuration on other vendor devices.
All other pre-requisites for HA Deployment are also applicable here.
Note: Ensuring a low latency/high speed circuit for HA Control/Data link is critical part of this deployment and it is responsibility of customer and any 3rd party involved to provide the necessary assistance regarding circuit during troubleshooting. Support Team will be able to provide best effort to help narrow down any reported issue since we do not control the circuit.