Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE 26.x

PDF

Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE 26.x

Mesh convergence

Updated: September 14, 2026

Want to summarize with AI?

Log in

Explains mesh convergence, including failure detection, alternate path selection, fast network recovery mechanisms, and configuration and verification of parent loss detection and gateway reachability.

A mesh convergence event is a network recovery mechanism that

  • allows MAPs to re-establish connection with a controller after losing the backhaul link to the current parent

  • enables the use of a maintained subset of channels for future scanning and parent identification, and

  • supports multiple convergence methods to optimize reconnection time.

The table presents the supported convergence methods.

Table 1. Mesh convergence

Mesh convergence

Parent Loss Detection / Keepalive Timers

Standard

21 seconds / 3 seconds

Fast

7 seconds / 3 seconds

Very Fast

4 seconds / 2 seconds

Noise-tolerant-fast

21 seconds / 3 seconds

Noise-tolerant fast detection

A noise-tolerant fast detection is a detection method that

  • monitors the response to Adaptive Wireless Path Protocol (AWPP) neighbor requests at specified intervals

  • identifies parent connectivity loss through missed responses, and

  • initiates network recovery actions such as roaming or full scans when loss is detected.

Noise-tolerant fast detection occurs when there is no response to an AWPP neighbor request. In the standard method, the system evaluates the current parent every 21 seconds. Each neighbor receives a unicast request every three seconds, and the parent also receives a request. If the parent does not respond, the device either roams to an available neighbor on the same channel or performs a full scan to find a new parent.

Configure mesh convergence (CLI)

This section provides information about how to configure mesh convergence.

Procedure

  1. Enter global configuration mode.

    Example:

    Device# configure terminal

  2. Create a mesh profile.

    Example:

    Device(config)# wireless profile mesh profile-name

  3. Configure mesh convergence method in a mesh profile.

    Example:

    Device(config-wireless-mesh-profile)# convergence {fast | noise-tolerant-fast | standard | very-fast}

You have successfully configured mesh convergence for the specified mesh profile on the device.

Device# configure terminal
Device(config)# wireless profile mesh mesh1
Device(config-wireless-mesh-profile)# convergence fast

Mesh convergence verification

Verify mesh convergence configuration and view subset channels for bridge groups using command-line interface commands.

This example shows the output from the show wireless profile mesh detailed command, which displays the mesh convergence method.

Device# show wireless profile mesh detailed default-mesh-profile
 
Mesh Profile Name             : default-mesh-profile
-------------------------------------------------
Description                : default mesh profile
Convergence Method         : Fast

This example shows the output from show wireless mesh convergence subset-channels command, which displays the subset channels for the selected bridge group name.

Device# show wireless mesh convergence subset-channels 

Bridge group name                Channel
------------------------------------------
Default                          132

Mesh network recovery mechanisms

A mesh network recovery mechanism is a network self-healing feature that

  • rapidly detects uplink gateway reachability failures in mesh APs

  • automatically triggers alternate uplink selection to maintain connectivity, and

  • uses ICMP pings to default gateways to verify uplink status after failover events or controller disconnections.

In all 802.11ac Wave 2 and 802.11ax mesh APs, detecting uplink gateway failures quickly speeds up mesh network recovery. Mesh APs use ICMP ping to the default gateway, either IPv4 or IPv6, to check uplink gateway reachability.

Reachability checks for mesh APs work

A mesh AP triggers the reachability check in two scenarios:

  • After a new uplink is selected and before the mesh AP joins the controller

    After a new uplink is selected, the mesh AP has a 45-second window to reach the gateway (through static IP or DHCP) through the selected uplink. If the mesh AP does not reach the gateway within 45 seconds, the system blocks the current uplink and starts selecting a new uplink. If the AP joins the controller during this window, it stops the reachability check. The system does not perform gateway reachability checks during normal operations.

  • As soon as the mesh AP times out its connection with the controller

    When the mesh AP times out its connection with the controller and fails to reach the gateway within 5 seconds, the system marks the current uplink as blocked and starts the uplink selection process.