No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical troubleshooting.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Guide to Collecting Fault Information

Guide to Collecting Fault Information

This section guides you how to collect and back up fault information as the reference for troubleshooting.

When an emergency occurs, you need collect and back up fault information on time for reference. When seeking Huawei technical support, you need provide the collected information to Huawei engineers for fault location and rectification.

When a fault occurs, collect the following information:

  • Basic fault information

  • Device fault information

Collecting Diagnostic Information

The display diagnostic-information command is used to obtain diagnostic information about a device in one-click mode. It incorporates multiple commonly used display commands, showing various information, such as the device startup configuration, current configuration, interface information, time information, and system version.

To output the current diagnostic information to a screen or a .txt file, run the display diagnostic-information [ level { high | medium | low } ] [ module-name ] &<1-8> [ slot slot-id ] [ key { slot | history } ] [ force ] [ file-name ] command. When using the command, note the following points:

  • If no parameter is specified, the system displays diagnostic information only on the screen. If there is a large amount of diagnostic information to be displayed, press Ctrl+C to stop the display as needed.

  • If the file-name parameter is specified, the system saves diagnostic information to a specified file.

    By default, the .txt file is saved to the cfcard:/ path. You can run the dir command in the user view to check whether the file is generated correctly. The file can also be transferred to a PC over FTP/SFTP. For details about how to transfer the file, see File System Management.

  • If the level parameter is specified, the system displays diagnostic information by level.
  • If the key parameter is specified, the system executes only the commands that carry the specified keyword exactly.
  • If the force parameter is specified, the system collects one-click diagnostic command information in forcible mode.
    NOTE:

    The display commands incorporated into the display diagnostic-information command vary with the device diagnosis focus.

    If the command does not carry the force parameter, diagnostic information is collected under the following CPU restrictions:
    • If the CPU usage is higher than 60% before the collection, an error is reported, preventing the collection.

    • If the CPU usage is higher than 80% during the collection, the collection is stopped for a period of 300 seconds. If the CPU usage falls below 70% within the period, the collection is continued. If the CPU usage does not fall below 70% when the period expires, an error is reported, and the system exits the collection.

The display diagnostic-information command is a level-3 (management level) command.

After a device fault occurs, deliver the diagnostic information file to the agent or Huawei for fast fault diagnosis and troubleshooting.

Example:

<HUAWEI> display diagnostic-information dia-info.txt
Now saving the diagnostic information of Admin-vs to the device                 
 100%                                                                           
Info: The diagnostic information was saved to the device successfully. 

This command is used to locate faults and collect diagnostic information. During the collection, system performance may be affected. For example, the CPU usage may increase. Therefore, do not run this command when the system is running properly. In addition, do not run this command concurrently on multiple terminals connected to the device. Otherwise, the CPU usage of the device may increase sharply, causing system performance to deteriorate.

Currently, commonly used terminal configuration software provides the function of outputting information to a file. Use Windows HyperTerminal as an example. To output information to a file, click Capture Text on the Transfer menu, specify a file name, and click Start. Then, run the display diagnostic-information command. In this way, the system displays all diagnostic information on the PC screen and saves the information as a file to a specified path on the PC.

Obtaining Logs and Alarms

When a device is faulty, collect log and alarm information about the device immediately. The information helps you know what happened during device operating and where the fault occurred.

By default, logs and alarms of all levels are recorded in log files in the logfile folder. The file format is *.log and the file size is 8 MB by default. When the log file size exceeds 8 MB, the system automatically compresses the log file into a .zip package in the format of log_ slot number _ time .log.zip. After the compression, the system generates a new log file.

To obtain the log and alarm information in the log file, perform the following steps:
  1. Run the save logfile command to manually save the information in the log file buffer to the log file.
  2. Transfer the file in the cfcard:/logfile/ path to the terminal through FTP/TFTP. If FTP/TFTP cannot be used for file transfer, run the more command, for example, run the more logfile/log.log command in the user view. For details about how to transfer the file over FTP/SFTP, see File System Management.
NOTE:
  • The logfile folder may contain a large number of log files. Generally, you need to collect only the log files generated at the time when the fault occurs.
  • If the fault involves the slave main control board, the log files saved on this board also need to be collected. These files are saved in the slave#cfcard:/logfile/ path.

Obtaining Collected KPI Data

The KPI system collects KPI data through the main control board and interface boards. You can quickly locate faults and determine service status based on the KPI data.

The KPI system records key device KPIs in real time, provides service impairment information (for example, the fault generation time, service impairment scope/type, relevant operation, and possible fault cause/location), and supports fast fault locating to reduce network maintenance costs.

The collected KPI data is saved to the cfcard:/KPISTAT path. The KPI system checks whether the receive buffer has data every 30 minutes. If the receive buffer has data, the data is written to the lpustat.dat file. Data is also written to the lpustat.dat file when the receive buffer is full. After the write operation is performed, the system checks whether the size of the data file is greater than or equal to 4 MB. If yes, the system compresses the data file in the year-month-day.hour-minute-second.dat.zip format and deletes the file after the compression is complete.

You can use FTP/SFTP to transfer the file in the cfcard:/KPISTAT path to a PC. For details about how to transfer the file over FTP/SFTP, see File System Management.

The file is saved in binary format and therefore cannot be directly viewed. In this case, ask Huawei engineers to parse the file using uFAD.

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13752

Downloads: 257

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next