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

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_1.3.6.1.4.1.2011.5.25.177.1.3.19 hwBgpPeerSessionThresholdExceed

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.19 hwBgpPeerSessionThresholdExceed

Description

BGP/3/PEERSESSIONTHRESHOLDEXCEED:OID [oid] The number of BGP peer sessions exceeded the threshold. (CurrentNumber=[INTEGER], Threshold=[INTEGER], MaximumNumber=[INTEGER])

The number of BGP peers reached a specified alarm prompt value.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.177.1.3.19 Minor

qualityOfServiceAlarm

Parameters

Name Meaning

CurrentNumber

Number of existing BGP peers

Threshold

Alarm threshold

MaximumNumber

Maximum number of existing BGP peers

Impact on the System

An alarm is generated to indicate that the number of BGP peers reaches a specified alarm prompt value.

Possible Causes

The number of BGP peers reached a specified alarm prompt value.

Procedure

  1. Check whether configurations and topology information contain an error to cause the device to generate such an alarm.

    • If the configuration or topology is incorrect, go to Step 2.

    • If the configuration and topology are correct, go to Step 3.

  2. Check the topology and user logs and correct the configuration and topology information, which prevents the device from creating excessive BGP peers.

  3. If more BGP peers need to be created, check that the device is to be expanded. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 70010

Downloads: 45

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