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 V800R010C10SPC500 Feature Description - System Management 01

This is ME60 V800R010C10SPC500 Feature Description - System Management
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).
Information Classification

Information Classification

Table 3-1 describes information that can be classified as logs, traps, or debugging information based on contents, users, and usage scenarios.

Table 3-1 Information classification

Type

Description

Logs

Logs are records of events and unexpected activities of managed objects. Logging is an important method to maintain operations and identifying faults. Logs provide information for fault analysis and help an administrator trace user activities, manage system security, and maintain a system.

Some logs are used by technical support personnel for troubleshooting only. Because such logs have no practical instruction significance to users, users are not notified when the logs are generated. Logs are classified as user logs, diagnostic logs or maintain logs.
  • User logs: During device running, the log module in the host software records all running information in logs. The logs are saved in the log buffer, sent to the Syslog server, reported to the NMS, and displayed on the screen. Such logs are user logs. Users can view the compressed log files and content.
  • Diagnostic logs: The logs recorded after the device is started but before the logserver component starts are diagnostic logs. Such logs are recorded in the process-side black box, and they are not saved in the log buffer, sent to the Syslog server, reported to the NMS, or displayed on the screen. Users can view the compressed log files and content.
    NOTE:
    The information recorded in diagnostic logs is used for troubleshooting only and does not contain any sensitive information.
  • Maintenance logs: During the running of a device, the log module of the host software records the data generated during the running of each service, forming log information. Log information is not saved in the log buffer, sent to the Syslog server, reported to the NMS, or displayed on the screen. Users can view the compressed log files and content.
    NOTE:
    The information recorded in maintain logs is used for troubleshooting only and does not contain any sensitive information.

Traps

Traps are sent to a workstation to report urgent and important events, such as the restart of a managed device. In general, the system also generates a log with the same content after generating a trap, except that the trap contains an additional OID.

Debugging information

Debugging information shows the device's the running status, such as the sending or receiving of data packets. A device generates debugging information only after debugging services are enabled.

Information File Naming Mode

Information can be saved as files on a device. These files are called information files. Table 3-2 describes the naming modes for information files.

Table 3-2 Naming modes for information files

Naming Mode

Description

log.log

The current information files of the system are saved in log format.

diag.log

Logs recording exceptions that occur when the system is started or running are saved in diag.log format.

pads.pads

Logs generated during the running of each service after a device starts are saved in .pads format.

log_SlotID_time.log.zip

If the size of a current information file reaches the upper threshold, the system automatically compresses the file into a historical file and changes the file name to log_SlotID_time.log.zip.

In the file name, SlotID indicates the slot ID and time indicates the compression and saving time.

diag_SlotID_time.log.zip

When the diagnostic log file size reaches the specified upper limit, the system automatically converts the file to a compressed file and names the compressed file diag_SlotID_time.log.zip, where SlotID represents the board slot ID and time represents the file conversion time.

pads_SlotID_time.pads.zip

When the maintain log file size reaches the specified upper limit, the system automatically converts the file to a compressed file and names the compressed file pads_SlotID_time.pads.zip, where SlotID represents the board slot ID and time represents the file conversion time.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059466

Views: 10162

Downloads: 6

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