SonicOS 7.0 High Availability Administration Guide
- SonicOS 7.0
- 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
Physically Connecting Your Security Appliances
For complete procedures for connecting your Security Appliances, see the Quick Start Guide for your Security Appliance.
If you are connecting the Primary and Secondary Security Appliances to an Ethernet switch that uses the spanning tree protocol, be aware that it may be necessary to adjust the link activation time on the switch port to which the SonicWall interfaces connect.<![CDATA[ ]]>
High Availability requires additional physical connections among the affected SonicWall Security Appliances.
In any High Availability deployment, you must physically connect the interfaces of all units to the appropriate switches.
It is important that the X0 interfaces from all units be connected to the same broadcast domain. Otherwise, traffic failover does not work. Also, X0 is the default redundant HA port; if the normal HA Control link fails, X0 interfaces are used to communicate heartbeats between units. Without X0 in the same broadcast domain, both units would become active if the HA Control link fails.
If X0 interfaces are not used to communicate, the units should be connected directly to each other.
SonicOS Security Appliances now allow heartbeats to be exchanged between an HA pair across the MGMT interface in addition to the HA control interface.
A WAN connection to the Internet is useful for registering your Security Appliances on MySonicWall and for synchronizing licensing information. Unless live communication with SonicWall's licensing server is not permitted due to network policy, the WAN interface should be connected before registration and licensing are performed.
Was This Article Helpful?
Help us to improve our support portal