Catalyst 3850 Denali, How to generate system report?

[Nick Chen]

I tried to generate system report follow the TechNotes. However, it looks like the commands were changed on Denali.  Is it possible to manually generate system report under Denali? Thanks.

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3850-series-switches/201070-Troubleshooting-3650-3850-reloads-by-sta.html

[flettster]

Hi Nick,

I found the below in this doc:
https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3850-series-switches/201070-Troubleshooting-3650-3850-reloads-by-sta.pdf

3. Generate System Reports Manually Manually creating system reports requires ‘service internal’ to be enabled. This will write a system report as a text file which can be done per switch basis.
3800-1#conf t Enter configuration commands, one per line. End with CNTL/Z.
3800-1(config)#service internal
3800-1(config)#exit

3800-1#resource create_system_report ?
WORD system report filename
3800-1#resource create_system_report sysreport.txt ?
switch Switch number
<cr>
3800-1#resource create_system_report sysreport.txt switch ?
<1-1> Switch number
3800-1#resource create_system_report sysreport.txt switch 1 ?
<cr>

Might be worth a go.

Cheers,

Flettster

[Nick Chen]

The doc is outdated for Denali 16.3.x.

[Mark Malone]

Hi Nick
there usually auto generated after crashes , is there a reason your trying to manually generate one ?

Denali Doc
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/16-1/configuration_guide/b_161_consolidated_3650_cg/b_161_consolidated_3650_cg_chapter_01101001.html#concept_55C49AEF142443A09D587DD1A9AA7822

System reports are generated in these situations:

In case of a switch failure—A system report is generated on the member that failed; reports are not generated on other members in the stack.

In case of a switchover—System reports are generated only on high availability (HA) member switches. reports are not generated for non-HA members.

The system does not generate reports in case of a reload.

During a process crash, the following is collected locally from the switch:

Full process core

Tracelogs

IOS syslogs (not guaranteed in case of non-active crashes)

System process information

Bootup logs

Reload logs

Certain types of /proc information

This information is stored in separate files which are then archived and compressed into one bundle. This makes it convenient to get a crash snapshot in one place, and can be then moved off the box for analysis. This report is generated before the switch goes down to rommon/bootloader.