• 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
  • Understanding High Availability
  • Understanding SonicWall High Availability Operation Modes
  • 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
    • Connecting the Active/Active DPI Interfaces for Active/Active DPI
  • 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
  • Configuration of HA Active/Standby
  • Configuring Active/Standby High Availability Settings
  • Configuring HA with Dynamic WAN Interfaces
  • Configuring Network DHCP and Interface Settings
    • Disabling the SonicOS DHCP Server
    • Configuring Virtual IP Addresses
    • Configuring Redundant Ports
• 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
• Failure Monitoring
• SonicWall Support
  • About This Document

Configuring Redundant Ports

You can assign an unused physical interface as a redundant port to a configured physical interface called the “primary interface”. If there is a physical link failure on the primary interface, the redundant interface can continue processing traffic without any interruption. One advantage of this feature is that in case of a physical link failure, there is no need to do a device failover.

You can configure a redundant port on Network | System > Interfaces > Edit Interface > Advanced dialog.

Because all Cluster Nodes share the same configuration, each node must have the same redundant ports configured and connected to the same switch(es).

To configure a redundant port for an interface:

1. Log in to the Primary unit of the Cluster Node.
2. Navigate to Network | System > Interfaces.
3. In the Interface Settings table, click the Edit icon for the primary interface for which you want to create a redundant port. For example, click the Edit icon for X2. The Edit Interface dialog displays.
4. Click Advanced.
5. From Redundant/Aggregate Ports, select Port Redundancy. The options on the dialog change.
6. From Redundant Port, select the redundant port. Only unused interfaces are available for selection. For example, select X4 for the redundant port.

7. Click OK.

   The selected interface is dimmed in the Interface Settings table. A note indicates that it is a redundant Port and lists the primary interface. The interface also appears in the Redundant Port field in the Edit Interface dialog of the primary port.

   The primary and redundant ports must be physically connected to the same switch, or preferably, to redundant switches in the network.

8. On each Cluster Node, replicate the redundant physical connections using the same interface numbers for primary and redundant ports. All Cluster Nodes share the same configuration as the Master node.