SonicOS 8 High Availability
- SonicOS 8
- 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
IPv6 HA Monitoring Considerations
Consider the following when configuring IPv6 HA Monitoring:
- In the Interface Settings dialog, enable Physical/Link Monitoring and Override Virtual MAC are dimmed because they are layer 2 properties. That is, the properties are used by both IPv4 and IPv6, so you configure them in the IPv4 monitoring page.
- The Primary/Secondary IPv6 address must be in the same subnet of the interface, and it can not be same as the global IP and Link-Local-IP of the Primary/Secondary Security Appliance.
- If the Primary/Secondary monitoring IP is set to (not ::), then they cannot be the same.
- If Allow Management on Primary/Secondary IPv6 Address is enabled, then Primary/Secondary monitoring IPv6 addresses cannot be unspecified (that is, ::).
- If Logical/Probe IPv6 Address is enabled, then the probe IP cannot be unspecified.
Was This Article Helpful?
Help us to improve our support portal