Cisco IE-3000-8TC Administration Guide - Page 441
Cisco_Diagnostics_Report.html, Step 4
![]() |
View all Cisco IE-3000-8TC manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 441 highlights
Troubleshooting When You Cannot Access the Graphical User Interfaces WebServer FileSystem CollectLogs Configure the value to either Yes or No. The following system attributes are diagnosed: • Tomcat-Checks for the Tomcat process • Tomcat Deadlocks-Checks Tomcat for deadlocked threads • Tomcat Keystore-Checks Tomcat for keystore issues • Tomcat Connectors-Checks Tomcat for connector issues • Tomcat Threads-Checks Tomcat for thread issues • Tomcat Memory-Checks Tomcat for memory issues • Tomcat Sessions-Checks Tomcat for session issues Configure the value to either Yes or No. The following system attributes are diagnosed: • disk_files-Checks for usually large files in root • sdl_fragmentation-Checks the fragmentation of files in SDL directory • sdi_fragmentation-Checks the fragmentation of files in SDI directory Note The FileSystem attributes explained above are CPU intensive diagnostics and consume substantial time for completion. Configure the value to either none or min or max. • none-No logs are collected. • min-Minimum number of system logs are collected. • max-Maximum number of system logs are collected. Step 4 When the system diagnostics is completed, the following files are generated and stored on the Cisco Diagnostic USB flash drive. The following table describes the files that are generated after diagnostic completion. Table 104: Generated files after diagnostic completion Cisco_Diagnostics_Report.html A static HTML file that displays • System Configuration • Diagnostics Log and • Old Reports usbdiag.log.txt Log file generated after a USB Diagnostics OL-27022-01 Administration Guide for Cisco Business Edition 3000, Release 8.6(4) 421
![](/manual_guide/products/cisco-ie30008tc-administration-guide-dff24ae/441.png)