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


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


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

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.

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).
BGP Error Code

BGP Error Code

Error Code

Error Subcode

1: Message header error

  • 1: connection not synchronized

  • 2: error message length

  • 3: error message type

2: Open message error

  • 1: unsupported version number

  • 2: error peer AS

  • 3: error BGP identifier

  • 4: unsupported optional parameter

  • 5: authentication failed

  • 6: unacceptable hold-time

  • 7: unsupported capability

3: Update message error

  • 1: malformed attribute list

  • 2: unrecognized well-known attribute

  • 3: well-known attribute is missing

  • 4: attribute flags error

  • 5: attribute length error

  • 6: invalid origin attribute

  • 7: AS routing loop

  • 8: invalid Next-Hop attribute

  • 9: error optional attribute

  • 10: invalid network field

  • 11: abnormal AS-Path

4: Hold timer expired

0: no special definition of the error subcode

5: Finite state machine error

0: no special definition of the error subcode

6: Cease

  • 1: maximum number of prefixes reached

  • 2: administrative shutdown

  • 3: peer deleted

  • 4: administrative reset

  • 5: connection rejected

  • 6: other configuration change

  • 7: connection collision resolution

  • 8: out of resources

  • 9: BFD session Down

Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 107771

Downloads: 68

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next