Collecting Log And Operating Information; Collecting Common Log Messages - H3C S6520X-HI Series Troubleshooting Manual

Collecting log and operating information

IMPORTANT:
To quickly locate faults, verify that the following features are enabled:
•
Information center—Enabled by default. To enable the information center, use the info-center
enable command.
•
Log file—Enabled by default. To enable the log file feature, use the info-center logfile enable
command.
•
Saving diagnostic log messages to the diagnostic log file—Enabled by default. To enable this feature,
use the info-center diagnostic-logfile enable command.
Table 1 shows the types of files that the system uses to store operating log and status information.
Common log files are stored in the flash:/logfile directory and diagnostic log files are stored in the
flash:/diagfile directory. You can export these files by using FTP, TFTP, or USB.
In an IRF system, these files are stored on the master device. If master/subordinate switchovers
have occurred, master devices before and after the switchovers have log files. You must collect log
files from all these devices. To more easily locate log information, save log files to a separate folder
for each member device and include their IRF member IDs in the folder names.
Table 1 Log and operating information
Category
Common log
Diagnostic log
Operating
statistics

Collecting common log messages

1. Save the common log messages from the log buffer to a log file.
By default, the log file is saved in the logfile directory of the Flash memory on each member
device.
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
2. Identify the log file on each member device:
# Display the log file on the master device.
File name format
logfile.log
diagfile.log
file-basename.tar.gz
Content
Command execution and operational log messages.
Diagnostic log messages about device operation, including
the following items:
•
Parameter settings used when an error occurs.
•
Information about a card startup error.
•
Handshaking information between member devices
when a communication error occurs.
IMPORTANT:
Current operation statistics for feature modules, including the
following items:
•
Device status.
•
CPU status.
•
Memory status.
•
Configuration status.
•
Software entries.
•
Hardware entries.
2