• SonicOS 8
• About SonicOS
  • Working with SonicOS
  • SonicOS Workflow
  • How to Use the SonicOS Administration Guides
  • Guide Conventions
• High Availability
  • About High Availability
    • High Availability Terminology
    • High Availability Modes
    • High Availability Encryption
    • Crash Detection
    • Virtual MAC Address
    • Dynamic WAN Interfaces with PPPoE HA
    • Stateful Synchronization with DHCP
    • Stateful Synchronization with DNS Proxy
    • About HA Monitoring
  • About Active/Standby HA
    • Benefits of Active/Standby HA
    • Working of Active/Standby HA
  • About Stateful Synchronization
    • Benefits of Stateful Synchronization
    • How Does Stateful Synchronization Work?
    • Example of Stateful Synchronization
  • Active/Standby Prerequisites
    • Supported Platforms and Licensing for HA
    • Physically Connecting Your Security Appliances
  • Maintenance
    • Removing an HA Association
    • Replacing a SonicWall Security Appliance
      • Replacing an HA Primary Unit
      • Replacing an HA Secondary Unit
• High Availability Status
  • Active/Standby High Availability Status
    • High Availability Status
    • High Availability Config
    • High Availability Licenses
• Configuring High Availability
  • Configuring Active/Standby High Availability Settings
  • Configuring HA with Dynamic WAN Interfaces
• 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
• Fine Tuning High Availability
  • Advanced Settings
  • Configuring Advanced High Availability Settings
• Monitoring High Availability
  • Configuring Active/Standby High Availability Monitoring
  • IPv6 High Availability Monitoring
  • IPv6 HA Monitoring Considerations
• Azure Use Cases
  • Use Case 1: Manage Azure HA Firewall
  • Use Case 2: Forward LAN traffic to the External Network through the Gateway after HA Failover
  • Use Case 3: Configure DNAT on Azure HA Firewall
  • Use Case 4: Configure DNAT on Azure HA Firewall (Need to move multiple floating IPs support)
• SonicWall Support
  • About This Document

Configuring Active/Standby High Availability Monitoring

To set the independent LAN management IP addresses and configure physical and/or logical interface monitoring

1. Log in as an administrator to the SonicOS Management Interface on the Active SonicWall Security Appliance.

2. Navigate to DEVICE | High Availability > Monitoring.

   

3. Click the Edit icon for an interface on the LAN, such as X0. The Interface Monitoring Settings dialog is displayed.

4. To enable link detection between the designated HA interfaces on the Primary and Secondary units, leave Physical/Link Monitoring selected. This option is selected by default.
5. In the Primary IPv4/v6 Address field, enter the unique LAN management IP address of the Primary unit and it should be same subnet as interface IP address. The default is 0.0.0.0.
6. In the Secondary IPv4/v6 Address field, enter the unique LAN management IP address of the Secondary unit it should be same subnet as interface IP address. The default is 0.0.0.0.

7. Select Allow Management on Primary/Secondary IP Address. When this option is enabled for an interface, a green icon appears in the interface’s Management column in the Monitoring Settings table. Management is only allowed on an interface when this option is enabled. This option is not selected by default.

8. In the Logical/ Probe IPv4/v6 Address field, enter the IP address of a downstream device on the network that should be monitored for connectivity. Typically, this should be a downstream router or server. (If probing is desired on the WAN side, an upstream device should be used.) This option is not selected by default.

   The Primary and Secondary Security Appliances regularly ping this probe IP address. If both successfully ping the target, no failover occurs. If neither successfully ping the target, no failover occurs, because it is assumed that the problem is with the target, and not the Security Appliances. But, if one Security Appliance can ping the target but the other cannot, failover occurs to the Security Appliance that can ping the target.

   The Primary IPv4/v6 Address and Secondary IPv4/v6 Address fields must be configured with independent IP addresses on a the interface, such as X0, (or a WAN interface, such as X1, for probing on the WAN) to allow logical probing to function correctly.

9. (Optional) To manually specify the virtual MAC address for the interface, select Override Virtual MAC and enter the MAC address in the field. The format for the MAC address is six pairs of hexadecimal numbers separated by colons, such as A1:B2:C3:d4:e5:f6. This option is not selected by default.

   Care must be taken when choosing the Virtual MAC address to prevent configuration errors.

   When Enable Virtual MAC is selected on DEVICE | High Availability > Settings, the SonicOS firmware automatically generates a Virtual MAC address for all interfaces. Allowing the SonicOS firmware to generate the Virtual MAC address eliminates the possibility of configuration errors and ensures the uniqueness of the Virtual MAC address, which prevents possible conflicts.

10. Click OK.
11. Click Close.