Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http:/​/​www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

The Conditional Debugging feature allows you to selectively enable debugging and logging for specific features based on the set of conditions you define. This feature is useful in systems where a large number of features are supported.

Note	In Cisco IOS XE Denali 16.1.1, only Control Plane Tracing is supported.

The Conditional debug allows granular debugging in a network that is operating at a large scale with a large number of features. It allows you to observe detailed debugs for granular instances within the system. This is very useful when we need to debug only a particular session among thousands of sessions. It is also possible to specify multiple conditions.

A condition refers to a feature or identity, where identity could be an interface, IP Address, or a MAC address and so on.

Note	In Cisco IOS XE Denali 16.1.1, MAC address is the only supported condition. The support for other features will be introduced in the releases that follow.

This is in contrast to the general debug command, that produces its output without discriminating on the feature objects that are being processed. General debug command consumes a lot of system resources and impacts the system performance.

Radioactive tracing provides the ability to stitch together a chain of execution for operations of interest across the system, at an increased verbosity level. This provides a way to conditionally print debug information (up to DEBUG Level or a specified level) across threads, processes and function calls.

Note	In Cisco IOS XE Denali 16.1.1 the default level is DEBUG. The users cannot change this to another level. The support for other levels will be introduced in the releases that follow.

Radioactive Tracing when coupled with Conditional Debugging, enable us to have a single debug CLI to debug all execution contexts related to the condition. This can be done without being aware of the various control flow processes of the feature within the box and without having to issue debugs at these processes individually.

By default the tracefile logs will be generated for each process and saved into either the /tmp/rp/trace or /tmp/fp/trace directory. In this temp directory, the trace logs are written to files, which are of 1 MB size each. The directory can hold up to a maximum of 25 such files for a given process. When a tracefile in the /tmp directory reaches its 1MB limit or whatever size was configured for it during the boot time, it is rotated out to an archive location in the /crashinfo partition under tracelogs directory.

The /tmp directory holds only a single tracefile for a given process. Once the file reaches its file size limit it is rotated out to /crashinfo/tracelogs. In the archive directory, up to 25 files are accumulated, after which the oldest one is replaced by the newly rotated file from /tmp.

The tracefiles in the crashinfo directory are located in the following formats:

1.    enable


2.    debug platform condition mac {mac-address}

3.    debug platform condition start


4.    show platform condition OR show debug

5.    debug platform condition stop


6.    request platform software trace archive [last {number} days] [target {crashinfo: | flashinfo:}]

7.    request platform software trace filter-binary {wire | wireless} [context {mac-address} | level | module]

8.    show platform software trace [filter-binary | level | message]

9.    clear platform condition all

Device> enable

Device# debug platform condition mac bc16.6509.3314

Device# debug platform condition start

Device# show platform condition
Device# show debug

Device# debug platform condition stop

Device# request platform software trace archive last 2 days

Device# request platform software trace filter-binary wireless context bc16.6509.3314

Device# show platform software trace message

Device# clear platform condition all

Note	The commands request platform software trace filter-binary and show platform software trace filter-binary work in a similar way. The only difference is:

• request platform software trace filter-binary - Sources the data from historical logs.

• show platform software trace filter-binary – Sources the data from the flash Temp directory.

Note	The command request platform software trace filter-binary wireless {mac-address} generates 3 flash files: collated_log_<.date..> mac_log <..date..> mac_database .. file

Of these, mac_log <..date..> is the most important file, as it gives the messages for the MAC we are debugging. The command show platform software trace filter-binary also generates the same flash files, and also prints the mac_log on the screen.

To identify a specific multicast receiver, specify the MAC address of the joiner or the receiver client, Group Multicast IP address and Snooping VLAN. Additionally, enable the trace level for the debug. The debug level will provide detailed traces and better visibility into the system.

The Recommended Workflow for Trace files is listed below:

1. To request the tracelogs for a specific time period.

   EXAMPLE 1 day.

   Use the command:

   Device#request platform software trace archive last 1 day

2. The system generates a tar ball (.gz file) of the tracelogs in the location /flash:

3. Copy the file off the switch. By copying the file, the tracelogs can be used to work offline. For more details on copying files, see section below.

4. Delete the tracelog file (.gz) file from /flash: location. This will ensure enough space on the switch for other operations.