This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references.
This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
The following table lists the product version related to this document.
Product Name |
Version |
---|---|
HUAWEI NetEngine 8000 F Series |
V800R021C00SPC100 |
iMaster NCE-IP |
V100R021C00SPC200 |
This document is intended for:
All the commands in these documents are intended for customers that deploy and maintain theHuawei devices on the live network. The commands, including but not limited to the commands that are used during production,assembly, and return for repair, are confidential and will not be provided in this document. Ifyou do need to use these commands, please apply to Huawei for them.
Encryption algorithm declaration
The encryption algorithms DES/3DES/RSA (with a key length of less than 2048 bits)/MD5 (in digital signature scenarios and password encryption)/SHA1 (in digital signature scenarios) have a low security, which may bring security risks. If protocols allowed, using more secure encryption algorithms, such as AES/RSA (with a key length of at least 2048 bits)/SHA2/HMAC-SHA2 is recommended.
Your purchased products, services, or features may use users' some personal data during service operation or fault locating. You must define user privacy policies in compliance with local laws and take proper measures to fully protect personal data.
When discarding, recycling, or reusing a device, back up or delete data on the device as required to prevent data leakage. If you need support, contact after-sales technical support personnel.
Reliability design declaration
Network planning and site design must comply with reliability design principles and provide device- and solution-level protection. Device-level protection includes planning principles of dual-network and inter-board dual-link to avoid single point or single link of failure. Solution-level protection refers to a fast convergence mechanism, such as FRR and VRRP. If solution-level protection is used, ensure that the primary and backup paths do not share links or transmission devices. Otherwise, solution-level protection may fail to take effect.
This document serves only as a guide. The content is written based on device information gathered under lab conditions. The content provided by this document is intended to be taken as general guidance, and does not cover all scenarios. The content provided by this document may be different from the information on user device interfaces due to factors such as version upgrades and differences in device models, board restrictions, and configuration files. The actual user device information takes precedence over the content provided by this document. The preceding differences are beyond the scope of this document.
The maximum values provided in this document are obtained in specific lab environments (for example, only a certain type of board or protocol is configured on a tested device). The actually obtained maximum values may be different from the maximum values provided in this document due to factors such as differences in hardware configurations and carried services.
Interface numbers used in this document are examples. Use the existing interface numbers on devices for configuration.
The pictures of hardware in this document are for reference only.
In this document, public IP addresses may be used in feature introduction and configuration examples and are for reference only unless otherwise specified.
The symbols that may be found in this document are defined as follows.
Symbol |
Description |
---|---|
Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury. |
|
Indicates a hazard with a medium level of risk which, if not avoided, could result in death or serious injury. |
|
Indicates a hazard with a low level of risk which, if not avoided, could result in minor or moderate injury. |
|
Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results. NOTICE is used to address practices not related to personal injury. |
|
Supplements the important information in the main text. NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration. |
The command conventions that may be found in this document are defined as follows.
Convention |
Description |
---|---|
Boldface |
The keywords of a command line are in boldface. |
Italic |
Command arguments are in italics. |
[ ] |
Items (keywords or arguments) in brackets [ ] are optional. |
{ x | y | ... } |
Optional items are grouped in braces and separated by vertical bars. One item is selected. |
[ x | y | ... ] |
Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. |
{ x | y | ... }* |
Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. |
[ x | y | ... ]* |
Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected. |
&<1-n> |
The parameter before the & sign can be repeated 1 to n times. |
# |
A line starting with the # sign is comments. |
Changes between document issues are cumulative. The latest document issue contains all the changes made in earlier issues.
This issue is the third official release. The software version of this issue is V800R021C00SPC100.
This issue is the second official release. The software version of this issue is V800R021C00SPC100.
This issue is the first official release. The software version of this issue is V800R021C00.