Cisco Ultra-Reliable Wireless Backhaul Standalone, Software Configuration Guide, Release 26.1.x

PDF

Configure and validate fast failover

Updated: April 10, 2026

Want to summarize with AI?

Log in

Outlines the pre-conditions for configuring and validating fast failover in both Fluidmax and Fluidity modes.

Before you configure the fast failover, use these pre-conditions:

  • Ensure that both the primary and the backup primary node should have same configuration. This includes the same channel's parameters: frequency, channel width, and mode. If Fluidmax is enabled, ensure that the Cluster ID is the same for both nodes.

  • Enable fast failover on all devices in the network.

    Note

    Fluidmax Fast failover is supported only on MP to MP or ME to ME with Ethernet backhaul.

The configure and validate fast failover procedure applies to both Fluidmax and Fluidity modes.

Configure fast failover from CLI

Configure fast failover functionality to provide automatic device failure detection and recovery in mesh network environments.

Fast failover configuration allows mesh point devices to quickly detect failures and switch to backup paths, minimizing network downtime and ensuring continuous connectivity.

Procedure

1.

Use the configure modeconfig mode meshpoint command to configure the operating mode of the device.

Example:

Device# configure modeconfig mode meshpoint

The available modes are mesh end (ME), mesh point (MP), and global gateway (L3).
2.

Use the configure mpls fastfail status {enable | disable} command to configure the fast failover status.

Example:

Device# configure mpls fastfail status enable

MPLS configures MPLS data frame packets for the specified device.

The fast failover feature status can be configured as enabled or disabled.
3.

Use the configure mpls fastfail timeout value command to set the fast failover timeout value.

Example:

Device# configure mpls fastfail timeout 100

The fast failover timeout determines the period for device failure detection. You can set any value from 0 to 65535.
4.

Use the configure mpls preempt-delay value command to set the preempt delay.

Example:

Device# configure mpls preempt-delay 100

By default, the preemption delay time is 70 seconds. During this period, the primary device actively gathers updates from the secondary device, allowing it to fully understand the network's current preemption delay status. You can configure a value from 0 to 65535.

Note

The radio interface setting must be the same on both ME and multi-point primaries.

Validate fast failover from CLI

Use this command to validate fast failover.

Device# show mpls config
Device# show dot11Radio <interface> fluidmax (check Fluidmax Primary ID and working state)

Example:

Device# show mpls config
layer 2
unicast-fllod
arp-unicast:
reduce-broadcast:
cluster ID
MPLS fast failover: enabled
Node failover timeout: 100 ms
……
MPLS tunnels:
Idp_id 381877266 debug 0 auto_pw 1
Local_gw 5.21.201.116 global_gw 0.0.0.0 pwlist {}