Workflow | WAN bonding service implementation

Plan the implementation.

Action	Considerations
Verify router model compatibility.	All Digi cellular extenders and routers can use the WAN bonding service except for the EX12, IX10, and IX15. If WAN bonding is not supported on your existing router, either utilize its native/primary backup or load-balancing connectivity options, or upgrade to routers that support this WAN bonding service.
Determine throughput and budget requirements.	Estimate total bandwidth needs for your applications (for example, video, SCADA, VPN). Match Digi WAN Bonding service tier (100 Mbps, 200 Mbps, 1 Gbps) to your performance goals. Select cellular plans that support the required data rate and usage levels. Plan license allocation: If deploying across multiple routers, decide which devices require bonding (for example, only high-bandwidth or mission-critical locations). Confirm number of devices needing a WAN bonding entitlement license. Review cost and renewals: Verify license renewal cycles and budget for ongoing service.
Confirm WAN bonding subscription and licenses in Digi Remote Manager.	Make sure there is a valid subscription for the WAN bonding service. Make sure there are enough licenses for the number of devices needing them. Plan renewal or expansion if deploying to multiple routers.
Check the DAL OS firmware version the devices are running.	Confirm the devices are running DAL OS 24.6 or newer. Back up the current configuration before upgrading. Schedule firmware upgrades during maintenance windows to minimize downtime.
Choose a WAN bonding server option.	Review the server options and decide whether to use a Digi-hosted, partner-hosted, or self-hosted server. Consider factors like control, security, latency, redundancy, and IT policy. Ensure sufficient compute capacity and bandwidth on the server side.
Identify all WAN interfaces to bond.	Determine which physical and logical interfaces should be included (Ethernet WAN, Cellular WWAN1/2, Wi-Fi as WAN). Note any data caps or costs that could influence bonding performance.
Plan network architecture and policies.	Define routing priorities, NAT behavior, and firewall/VPN rules. Confirm that bonded traffic integrates cleanly with your LAN, DMZ, or corporate VPN.
Decide deployment method for configuration.	Choose whether to deploy the bonding configuration via DRM templates or manual per-device setup.

Implement the WAN bonding server option.

This step focuses on implementing the WAN bonding server, which is what will terminate and reassemble bonded traffic from Digi routers.

Action	Considerations
Implement the WAN bonding server option you chose during the planning phase (Partner-hosted or self-hosted).	Whatever option you chose, note the following information you need to know about the WAN bonding server as you will need this information when configuring the WAN bonding settings on the device: Prerequisites Hostname or IPv4 address for each external server hosting the WAN bonding server. (Optional) Host port number the external server uses for the WAN bonding connection. (Optional) Channel UDP Listener Port number of the UDP port for the external hosting server. The username and password to authenticate with the hosting service. WAN interfaces that will be bonded. Password used to authenticate with the WAN bonding web interface. WAN bonding license key (if implementing a partner-hosted or self-hosted WAN bonding server). Additional items The firewall zone for the new bonded interface, if other than External.

Action

Considerations

Implement the WAN bonding server option you chose during the planning phase (Partner-hosted or self-hosted).

Whatever option you chose, note the following information you need to know about the WAN bonding server as you will need this information when configuring the WAN bonding settings on the device:

Prerequisites

Hostname or IPv4 address for each external server hosting the WAN bonding server.
(Optional) Host port number the external server uses for the WAN bonding connection.
(Optional) Channel UDP Listener Port number of the UDP port for the external hosting server.
The username and password to authenticate with the hosting service.
WAN interfaces that will be bonded.
Password used to authenticate with the WAN bonding web interface.
WAN bonding license key (if implementing a partner-hosted or self-hosted WAN bonding server).

Additional items

The firewall zone for the new bonded interface, if other than External.

Assign WAN bonding licenses to devices.

Action	Considerations
Assign WAN bonding licenses to devices.	Confirm activation: The license must show as active in Digi Remote Manager before WAN Bonding can be configured. See Confirm that a device has been assigned an active WAN bonding license. Ensure the license(s) are applied to the correct device(s) in the correct account.

Configure the WAN bonding settings.

Action	Considerations
Enable the WAN bonding service in Digi Remote Manager.	The WAN bonding server and interfaces may or may not already be configured, but without enabling the service there will be no activity between the device, Digi Remote Manager, and the server(s).
Add the WAN bonding server information.	Define the bonding parameters, so communication can occur between the device, server, and Digi Remote Manager.
Add the WAN bonding server credentials.	Make sure the credentials you use are securely managed.
Add the interfaces to the WAN bonding tunnel.	Select all WAN interfaces (Ethernet, Cellular, Wi-Fi) that should be included in the WAN bonding tunnel. Assign appropriate interface modes (Automatic, Cellular-Optimized for Latency, etc.) based on your network design.

Monitor, test, and validate the interfaces in the WAN bonding connection and the connection itself.

Action	Considerations
Add the password for the WAN bonding interface.	This password is what will authenticate Digi Remote Manager or an authorized administrator to connect to the bonding web UI to view or retrieve detailed performance statistics (through the bonded tunnel). Caution The WAN bonding interface exposes live network performance and routing data. Make sure this credential is securely managed.
To validate the connectivity of the interfaces in the WAN bonding connection, configure SureLink tests and recovery actions.	Understand the relationship between SureLink and WAN bonding. SureLink by default doesn’t monitor the bonded tunnel itself — it monitors the individual links that feed into it. If a link fails or goes “stale,” SureLink automatically resets or reconnects it, keeping the bonding tunnel healthy. So, configuring SureLink correctly ensures that WAN bonding always has good links available — otherwise, bonding may degrade or collapse. If you want to have Surelink monitor the WAN Bonding tunnel itself in addition to monitoring the individual interfaces linked to the tunnel, then enable and configure the Surelink settings for the WAN Bonding connection. Choose the right test method. Use Ping or TCP tests targeting a stable, reachable endpoint (e.g., 8.8.8.8 or your bonding server’s IP). Avoid relying solely on DNS or HTTP unless you specifically need to confirm application-layer connectivity. Select reliable test targets. If your SureLink test target is unreliable, it can cause false link resets — unnecessarily cycling interfaces that are actually fine. Set proper test intervals and retry limits. If SureLink is too aggressive, it can reboot interfaces mid-bonding, causing unnecessary tunnel re-establishments. If too lenient, it might delay failover or link recovery. Coordinate with WAN bonding link recover behavior. Enable SureLink on each WAN interface with moderate sensitivity — not too aggressive — so it complements, not conflicts with, bonding’s own monitoring.

Action

Considerations

Add the password for the WAN bonding interface.

This password is what will authenticate Digi Remote Manager or an authorized administrator to connect to the bonding web UI to view or retrieve detailed performance statistics (through the bonded tunnel).

Caution The WAN bonding interface exposes live network performance and routing data. Make sure this credential is securely managed.

To validate the connectivity of the interfaces in the WAN bonding connection, configure SureLink tests and recovery actions.

Understand the relationship between SureLink and WAN bonding. SureLink by default doesn’t monitor the bonded tunnel itself — it monitors the individual links that feed into it. If a link fails or goes “stale,” SureLink automatically resets or reconnects it, keeping the bonding tunnel healthy. So, configuring SureLink correctly ensures that WAN bonding always has good links available — otherwise, bonding may degrade or collapse.
If you want to have Surelink monitor the WAN Bonding tunnel itself in addition to monitoring the individual interfaces linked to the tunnel, then enable and configure the Surelink settings for the WAN Bonding connection.
Choose the right test method. Use Ping or TCP tests targeting a stable, reachable endpoint (e.g., 8.8.8.8 or your bonding server’s IP). Avoid relying solely on DNS or HTTP unless you specifically need to confirm application-layer connectivity.
Select reliable test targets. If your SureLink test target is unreliable, it can cause false link resets — unnecessarily cycling interfaces that are actually fine.
Set proper test intervals and retry limits. If SureLink is too aggressive, it can reboot interfaces mid-bonding, causing unnecessary tunnel re-establishments. If too lenient, it might delay failover or link recovery.
Coordinate with WAN bonding link recover behavior. Enable SureLink on each WAN interface with moderate sensitivity — not too aggressive — so it complements, not conflicts with, bonding’s own monitoring.