topic Re: C9800 - wlc fails to show log after radioactive tracing. in Wireless

C9800 - wlc fails to show log after radioactive tracing.

Charlie Grey — Thu, 15 Aug 2024 08:22:21 GMT

hi,

on C9800 wlc, i did a debug w command. >

#debug platform condition feature wireless mac 1234.5678.aaaa

#debug platform condition start/stop command.

when i run show logging command to show log, instead it show this...

#show logging profile wireless start last 30 min filter mac 1234.5678.aaaa

c9800#show logging profile wireless start last 30 min filter mac 1234.5678.aaaa
Logging display requested on 202x/0x/xx 15:38:08 for Hostname: [xxxxxx], Model: [C9800-40-K9 ], Version: [17.09.05], SN: [xxxxxx], MD_SN: [xxxxxxxxx]

Displaying logs from the last 0 days, 0 hours, 30 minutes, 0 seconds
executing cmd on chassis 1 ...
Unified Decoder Library Init .. DONE
Found 1 UTF Streams

===========================================================
======= Unified Trace Decoder Information/Statistics ======
===========================================================
----------------- Decoder Input Information ---------------
===========================================================
Num of Unique Streams .. 1
Total UTF To Process ... 1
Total UTM To Process ... 37804
UTM Process Filter ..... cpp_cp,fman_fp,fman_rp,fman-rp,fman-fp,fed,mobilityd,nmspd,odm_proxy,rogued,rrm,repm,wncd,wncmgrd,wncd_x,IOSRP,smd,odm,wstatsd,linux-iosd-image
MRST Filter Rules ...... 22
===========================================================
----------------- Decoder Output Information --------------
===========================================================
First UTM TimeStamp ............... 2024/08/08 10:59:20.568771611
Last UTM TimeStamp ................ 2024/08/12 12:16:45.683714904
UTM [Skipped / Rendered / Total] .. 37804 / 0 / 37804
UTM [ENCODED] ..................... 6049
UTM [PLAIN TEXT] .................. 22
UTM [DYN LIB] ..................... 0
UTM [MODULE ID] ................... 0
UTM [TDL TAN] ..................... 0
UTM [APP CONTEXT] ................. 31733
UTM [MARKER] ...................... 0
UTM [PCAP] ........................ 0
UTM [LUID NOT FOUND] .............. 0
--More-- ===========================================================

what is happening or where i do wrong? other controller are working fine.

Re: C9800 - wlc fails to show log after radioactive tracing.

Mark Elsen — Thu, 15 Aug 2024 08:27:21 GMT

- I presume the mac address being tracked is effectively using the controller or trying to?
- Is the software version perhaps different compared to the other controllers ?

Re: C9800 - wlc fails to show log after radioactive tracing.

Charlie Grey — Thu, 15 Aug 2024 08:29:14 GMT

using same commands...

17.3.6 + 17.9.4a OK.

17.9.5 cannot.

Re: C9800 - wlc fails to show log after radioactive tracing.

Charlie Grey — Thu, 15 Aug 2024 08:35:52 GMT

found this which is similiar but no solution. 😞

C9600X Stackwise Virtual Active Failing to Show FED Traces CSCwj56654

Re: C9800 - wlc fails to show log after radioactive tracing.

Mark Elsen — Thu, 15 Aug 2024 08:39:20 GMT

>....17.9.5 cannot.
- Try with a few other mac addresses too , to make sure that there was no accidental mistake when typing the content
of a particular mac address and to make sure that the problem 'is steady'

Re: C9800 - wlc fails to show log after radioactive tracing.

Charlie Grey — Thu, 15 Aug 2024 11:46:43 GMT

no. i confirmed it's not typo error as i repeated the same command and double verified.

Re: C9800 - wlc fails to show log after radioactive tracing.

Haydn Andrews — Thu, 15 Aug 2024 22:37:25 GMT

Try the radio active trace via the GUI and ensure logging enabled in there. Find it easier anyway cause I can just download the tracefile post it running

Re: C9800 - wlc fails to show log after radioactive tracing.

JPavonM — Fri, 16 Aug 2024 07:13:45 GMT

Cisco has modified some logging behaviour in the last codes, something that it was working before is not working in 17.9.4 and 17.9.5 like "monitor logging profile wireless mac <MAC>" is not producing any output now, unless you enabled "service internal" in config mode before.

They are making this change to avoid resource starvation during logging, and they recommend to disable it after the debug.

Try if this fixes your RA tracking issue in the console as well.