`show logging debug`

Displays the debug logs maintained in the log manager.

Syntax

show logging debug { boot number module sub-module severity | module sub-module severity [ unit-id ] [ date-time ] }

Parameters

boot: Displays logs from any previous backup file on your local unit.
number: Displays previous backup logs, starting with 1 for the most recent, 2 for the second most recent, and so on.
module: Displays the logs of a specified module or list of modules (separated by commas). Enter all to include all modules.
sub-module: Displays the logs of a specified sub-module or list of sub-modules (separated by commas). Enter all if multiple modules are specified. If only a single module is specified, then specify a single sub-module or list of sub-modules (separated by commas) belonging to the module.
severity: Specifies the severity level or list of severity levels (separated by commas) by which logs are displayed. Enter all to include all severity levels.
unit-id: Displays the logs of a unit or list of units (separated by commas). Enter all to aggregate the result from all units. If none of the units are specified, then logs of the local unit are displayed.
date-time: Displays the logs that are generated starting at the specified date and time. The format is month_date_hh:mm:ss:ms.

Modes

User EXEC mode

Usage Guidelines

If the logs are generated using the debug commands, you must use the exact module names and sub-module names as listed in the log manager hierarchy.

If the logs are generated using distributed logger (dlogger), the modules and sub-modules must be specified based on the mapping of distributed logger modules to log manager displayed in the show dlogger module filter lm-map command output.

If a fetch operation is not run or the fetched logs have been cleared, local logs are displayed. That is, to display the local logs, you must run the logmgr clear-fetched-logs command first.

Before retrieving logs, configure the logmgr fetch command to collect and display a concise summary of log analysis from the specified remote unit.

When retrieving previous logs using the boot keyword, specifying the unit-id is not required.

An active unit cannot access the previous boot logs of a member unit.

Examples

The following example displays the current boot logs and the immediately previous boot logs.

device# show logging debug infra logmgr_proc all

Jun 24 19:26:25:770533:info:infra:logmgr_proc:2:199386726402: **** logmgr_clam_request_callback, action = 3
Jun 24 17:52:01:923113:err:infra:logmgr_proc:2:182206857218: Error 1: Logs unavailable for the 10 previous bootOnly available upto 6 previous boot
Jun 24 17:52:01:880461:info:infra:logmgr_proc:2:182206857218: **** logmgr_clam_request_callback, action = 3
Jun 24 17:43:10:311603:info:infra:logmgr_proc:2:156437053442: File /logmgr/tmp/tmp_show_logs.log deleted successfully
Jun 24 17:43:10:111063:info:infra:logmgr_proc:2:156437053442: **** logmgr_clam_request_callback, action = 3
Jun 24 17:41:44:611386:info:infra:logmgr_proc:2:130667249666: File /logmgr/tmp/tmp_show_logs.log deleted successfully
Jun 24 17:39:41:420730:info:infra:logmgr_proc:2:130667249666: **** logmgr_clam_request_callback, action = 3
Jun 23 21:04:46:017484:info:infra:logmgr_proc:2:0: Unit ID [2], time taken [55.000000] sec
Jan 01 00:00:41:209570:info:infra:logmgr_proc:0:0: calling ITC process messages
Jan 01 00:00:41:209487:info:infra:logmgr_proc:0:0: slam API initialized
Jan 01 00:00:41:198165:info:infra:logmgr_proc:0:0: FileMgr API initialized
Jan 01 00:00:41:183523:info:infra:logmgr_proc:0:0: ITC app=122 initialized
Jan 01 00:00:41:102326:info:infra:logmgr_proc:0:0: ITC lib initialized
Jan 01 00:00:40:083364:debug:infra:logmgr_proc:0:0: total size: 322957
Jan 01 00:00:40:083291:debug:infra:logmgr_proc:0:0: Renaming /fast_iron/logs/backuplogs/PREV_BOOT_2025_06_23-21_02_37 -> /fast_iron/logs/backuplogs/logs_6_2025_06_23-21_02_37
Jan 01 00:00:40:065008:debug:infra:logmgr_proc:0:0: Zipping /fast_iron/logs/backuplogs/logs_5_2025_06_23-04_29_26 -> /fast_iron/logs/backuplogs/logs_5_2025_06_23-04_29_26.tgz
Jan 01 00:00:39:414310:info:infra:logmgr_proc:0:0: ============ LogMgr Lib Init Done; Will start logging with lm_log ===========
--------------------------------------------------------------------------------
                               PREVIOUS BOOT LOGS
--------------------------------------------------------------------------------
Jun 23 04:46:18:501822:info:infra:logmgr_proc:2:356298784770: **** logmgr_clam_request_callback, action = 10
Jun 23 04:46:08:275159:info:infra:logmgr_proc:2:343413882882: File /logmgr/tmp/tmp_show_logs.log deleted successfully
Jun 23 04:46:00:187428:info:infra:logmgr_proc:2:343413882882: **** logmgr_clam_request_callback, action = 3
Jun 23 04:44:20:858879:info:infra:logmgr_proc:2:313349111810: File /logmgr/tmp/tmp_show_logs.log deleted successfully
Jun 23 04:44:12:229537:info:infra:logmgr_proc:2:313349111810: **** logmgr_clam_request_callback, action = 3
Jun 23 04:43:47:415036:info:infra:logmgr_proc:2:287579308034: File /logmgr/tmp/tmp_show_logs.log deleted successfully
Jun 23 04:43:40:342640:info:infra:logmgr_proc:2:287579308034: **** logmgr_clam_request_callback, action = 3
Jun 23 04:31:47:585709:info:infra:logmgr_proc:2:0: Unit ID [2], time taken [55.000000] sec
Jan 01 00:00:48:418101:info:infra:logmgr_proc:0:0: calling ITC process messages
Jan 01 00:00:48:418027:info:infra:logmgr_proc:0:0: slam API initialized
Jan 01 00:00:48:408073:info:infra:logmgr_proc:0:0: FileMgr API initialized
Jan 01 00:00:48:379643:info:infra:logmgr_proc:0:0: ITC app=122 initialized
Jan 01 00:00:48:303500:info:infra:logmgr_proc:0:0: ITC lib initialized
Jan 01 00:00:47:285011:debug:infra:logmgr_proc:0:0: total size: 242673
Jan 01 00:00:47:284939:debug:infra:logmgr_proc:0:0: Renaming /fast_iron/logs/backuplogs/PREV_BOOT_2025_06_23-04_29_26 -> /fast_iron/logs/backuplogs/logs_5_2025_06_23-04_29_26
Jan 01 00:00:47:213821:debug:infra:logmgr_proc:0:0: Zipping /fast_iron/logs/backuplogs/logs_4_2025_06_17-21_46_11 -> /fast_iron/logs/backuplogs/logs_4_2025_06_17-21_46_11.tgz
Jan 01 00:00:46:693372:info:infra:logmgr_proc:0:0: ============ LogMgr Lib Init Done; Will start logging with lm_log ===========

The following example displays backup logs retrieved from a specific boot instance.

device# show logging debug boot 2 infra dnld all
Jun 23 04:29:07:649824:info:infra:dnld-mgr:2:492639879170: dnldmgr_get_status_func: Response status is 0
Jun 23 04:28:25:156489:info:infra:dnld-mgr:2:488344911874: Download thread exiting...
Jun 23 04:28:25:114668:info:infra:dnld-mgr:2:488344911874: Image Download Complete
Jun 23 04:28:25:013342:info:infra:dnld-mgr:2:488344911874: Current Download State set to Image download complete
Jun 23 04:28:25:012435:info:infra:dnld-mgr:2:488344911874: Download: COPY BUNDLE IMAGE COMPLETED
Jun 23 04:28:25:012350:debug:infra:dnld-mgr:2:488344911874: Suppressed 1 times: /usr/bin/img_flash_packages /tmp/TFTP/GZR10010hdevufi.bin secondary 0
Jun 23 04:28:24:327538:info:infra:dnld-mgr:2:362838528706478848: Received IPC response from unit 1 code 0
Jun 23 04:28:24:327446:info:infra:dnld-mgr:2:362838528706478848: Received IPC Message
Jun 23 04:28:24:324799:info:infra:dnld-mgr:2:360992710670156544: Received IPC response from unit 3 code 0
Jun 23 04:28:24:324704:info:infra:dnld-mgr:2:360992710670156544: Received IPC Message
Jun 23 04:28:06:005179:debug:infra:dnld-mgr:2:488344911874: /usr/bin/img_flash_packages /tmp/TFTP/GZR10010hdevufi.bin secondary 0
....
Jun 23 04:27:29:823474:info:infra:dnld-mgr:2:488344911874: Download: COPY BOOTROM IMAGE FROM BUNDLE START
Jun 23 04:27:29:822321:info:infra:dnld-mgr:2:488344911874: Download: COPY APPLICATION IMAGE FROM BUNDLE START

The following example displays an error message if you enter an unavailable boot number.

device# show logging debug boot 10 all all all all
Error: Logs unavailable for the 10 previous boot
Only available upto 6 previous boot (error code 1)

History

Release version	Command history
08.0.95	This command was introduced.
10.0.10h_cd1	This command was modified to include new boot keyword and to alter the format of the existing output.

Show Commands

show logging debug

`show logging debug`