SonicOS 7.1 High Availability Administration Guide
- SonicOS 7.1
- About SonicOS
- High Availability
- High Availability Status
- Configuring High Availability
- Configuring High Availability in the Cloud Platform
- Set up an Active/Standby High Availability Configuration Using Azure
- Install the Custom Template
- Enable Identity of Both Virtual Machines (HA1 and HA2)
- Role Assignment
- Check the Networking Tab
- Configuring Active NSv Firewall Using the Associated Public IP
- Configuring Standby NSv Firewall Using the Associated Public IP
- Enable the L3 Mode
- Configuring Active NSv Firewall Using the Floating Public IP
- Configuring HA to Active/Standby with L3 HA link
- Adding Additional Floating Public IP
- Set up an Active/Standby High Availability Configuration Using Azure
- Fine Tuning High Availability
- Monitoring High Availability
- Azure Use Cases
- SonicWall Support
Example of Stateful Synchronization
In case of a failover, the following sequence of events occurs:
- A PC user connects to the network, and the Active Security Appliance creates a session for the user.
- The Active Security Appliance synchronizes with the Standby Security Appliance. The Standby now has all of the user’s session information.
- The administrator restarts the Active unit.
- The Standby unit detects the restart of the Active unit and switches from Standby to Active.
- Now Active Security Appliance begins to send gratuitous ARP messages to the connected switches using the same Virtual MAC address and IP address as the Active Security Appliance. No routing updates are necessary for downstream or upstream network devices.
- When the PC user attempts to access a Web page, now Active Security Appliance has all of the user’s session information and is able to continue the user’s session without interruption.
Was This Article Helpful?
Help us to improve our support portal