13
Collecting and reporting failure
information
If an exception has occurred, first record the following failure information immediately and then report
them to H3C Support:
•
Symptom, time of failure, and configuration.
•
Network topology information, including the network diagram, port connections, and points of
failure.
•
Log messages and diagnostic information.
•
Steps you have taken and the result.
Collecting basic failure information
shows the basic failure information to be collected if the device is faulty.
Table 13 Basic failure information
Item
Collection method
Time of failure
Record the time when the failure occurred down to the minute.
Symptom
Record detailed symptom of the failure.
Impact
Record the failure severity and affected services.
Networking
Draw a network diagram, including uplink and downlink devices and
connected interfaces.
Steps you have taken
Record the steps you have taken and the results, including output from the
commands executed during the troubleshooting process.
Collecting log information
Log information records daily information, user actions, system failures, system safety, and system
debugging. It includes diagnosis monitoring log messages, diagnostic log messages, system log
messages, and debug log messages.
To obtain the most recent log information, save the collected log messages to a log file.
To collect log information:
1.
The system automatically saves diagnosis monitoring log messages to a log file.
By default, diagnosis monitoring log files are saved in the
drvmon
folder under the root
directory of the storage device.
2.
The system automatically saves maintenance information to a file.
By default, maintenance information is saved in the
info
folder under the root directory of the
storage device.
3.
Save diagnostic log messages from the log buffer to a log file.
diagnostic-logfile save
By default, diagnostic log files are saved in the
diagfile
folder under the root directory of the
storage device.
4.
Save system log messages from the log buffer to a log file.
