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

PDF

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

Wireless client debug bundle

Updated: April 10, 2026

Want to summarize with AI?

Log in

Introduces the wireless client debug bundle feature, detailing how it streamlines troubleshooting by collating debug logs, packet captures, show command outputs, and AP logs into a single file, and highlighting its release history and usage considerations.

A wireless client debug bundle is a troubleshooting feature that

  • collates client-specific debug logs, packet captures, and relevant show command outputs

  • packages them into a single compressed tar file for easier analysis, and

  • streamlines client issue investigation by reducing the need to run multiple commands.

In earlier releases, logs were collected through various individual steps and commands. Now, the output of show commands related to clients is collected in a tar file through a single debug command. From Cisco IOS XE Cupertino 17.11.1, client debug bundle collates AP logs along with the existing controller bundle.

Note

The client debug bundle is not supported on HA with Stateful Switch Over (SSO).

Note

When you enable the all command option on the AP console, the command activates debug logging for all clients. This action can result in an excessive amount of logs being printed to the console.

Feature history for wireless client debug bundle

This table provides release and related information about the feature explained in this section.

This feature is also available in all the releases subsequent to the one in which they are introduced in, unless noted otherwise.

Table 1. Feature History for client debug bundle

Feature Name

Release Information

Feature Description

Wireless client debug bundle

Cisco IOS XE 17.11.1

Client debug bundle includes AP logs along with the existing controller bundle, collected in a tar file through a single debug command.

Types of logs collected

A log type is a diagnostic data category that

  • groups related log files generated during client device troubleshooting

  • distinguishes between control plane packet captures, AP logs, and client-specific traces, and

  • determines the format and file structure used to collect and organize system diagnostics.

The client debug bundle logs are collected in tar file format on bootflash by using a single debug command.

This example displays the file formats of logs collected from a client device with MAC address 8cXX.90XX.fdXX:

Example :

The final tar file that is generated is wireless_bundle_123456_UTC_Oct_20_2022.tar.

These files are extracted from the wireless_bundle_123456_UTC_Oct_20_2022.tar file:

  • wireless_bundle_8cXX.90XX.fdXX.tar (client radioactive trace debug log)

  • epc_135790_UTC_Oct_20_2022.pcap (packet capture in a control plane)

  • ap_3802_cisco_client_bundle.17.11.0.61.20221020.135154.tgz (AP logs)

These files are extracted from wireless_bundle_8cXX.90XX.fdXX.tar client radioactive trace debug log file:

  • show_tech_support_wireless_client_before_RA_start_8cXX.90XX.fdXX_134941_UTC_Oct_20_2022.txt

  • ra_trace_8cXX.90XX.fdXX_135055_UTC_Oct_20_2022.log

  • ra_trace_internal_8cXX.90XX.fdXX_135057_UTC_Oct_20_2022.log

  • show_tech_support_wireless_client_after_RA_stop_8cXX.90XX.fdXX_135055_UTC_Oct_20_2022.txt

These files are extracted from ap_3802_cisco_client_bundle.17.11.0.61.20221020.135154.tgz AP log file:

  • ap_3802_cisco_client_bundle.17.11.0.61.20221020.135154.messages

  • ap_3802_cisco_client_bundle.17.11.0.61.20221020.135154.syslogs

  • ap_3802_cisco_client_bundle.17.11.0.61.20221020.135154.tech_cdb_0

  • ap_3802_cisco_client_bundle.17.11.0.61.20221020.135154.tech_cdb_1

Collect wireless client debug bundle (CLI)

Collect wireless client debug information for specified clients for troubleshooting using commands.

Procedure

1.

Add client MAC addresses for which debug logs are required.

Example:

Device# debug wireless bundle client mac aaaa.bbbb.cccc

You can add up to 32 client MAC addresses to the command. To delete the MAC addresses, run the no form of this command.
2.

Start the collection of the client debug bundle for wireless clients.

Example:

Device# debug wireless bundle client start
3.

(Optional) Enable the AP archive collection on a site tag.

Example:

Device# debug wireless bundle client start ap-archive site-tag default-site-tag level { critical | debug | error | verbose}

This specifies the AP archive levels as well.
4.

(Optional) Enable embedded packet capture (EPC) in a control plane.

Example:

Device# debug wireless bundle client start epc
Note

If EPC is already enabled and active from a different source, you cannot start the debug bundle with EPC. To use EPC with the debug bundle, stop EPC if it is enabled from a different source, and then restart it with the debug bundle.
5.

(Optional) Configure the maximum time, in minutes, to trace the condition.

Example:

Device# debug wireless bundle client start monitor-time 30
The default time is 30 minutes.
6.

(Optional) Stop the collection of the debug bundle for wireless clients.

Example:

Device# debug wireless bundle client stop-all collect {all | mac H.H.H}
7.

(Optional) Cancel the collection of the debug bundle for wireless clients.

Example:

Device# debug wireless bundle client abort