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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document provides the explanations, causes, and recommended actions of alarms on the product.
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.6 hwBgpPeerRouteExceed

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.6 hwBgpPeerRouteExceed

Description

The number of routes received from the BGP peer exceeded the alarm number. (InstanceId=[InstanceId], Afi=[AddrFamilyAfi], Safi=[AddrFamilySafi], PeerRemoteAddrType=[PeerIPAddrType], PeerRemoteAddr=[PeerIPAddr], MaxRouteNum=[RouteLimitNum], AlarmThreshold=[RouteLimitThreshold])

The number of routes received from the BGP peer exceeded the upper limit allowed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

ROUTEEXCEED

Trap OID

1.3.6.1.4.1.2011.5.25.177.1.3.6

Alarm ID

0x08790002

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.7 hwBgpPeerRouteExceedClear

Parameters

Parameter Description

InstanceId

Instance ID

Afi

Address family

Safi

Sub-address family

PeerRemoteAddrType

Peer address type

PeerRemoteAddr

Peer address

MaxRouteNum

Maximum number of routes

AlarmThreshold

Alarm threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.1

hwBgpPeerConfigRouteLimitNum

None

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.2

hwBgpPeerConfigRouteLimitThreshold

None

Impact on the System

  • If the peer route-limit percentage command with percentage of 100% and without alert-only is run, the peer relationship is interrupted and the routes received from all peers are deleted.

  • If the peer route-limit percentage command with alert-only is run, services are not interrupted.

Possible Causes

Cause: The number of routes received from the BGP peer who configured with route-limit, exceeds the maximum value allowed.

Procedure

  • Cause: The number of routes received from the BGP peer who configured with route-limit, exceeds the maximum value allowed.
    1. Run the display bgp peer command to check whether the number of routes received from the peer exceeds the upper threshold.

      • If the number of routes received from the peer exceeds the upper threshold, go to Step 2.
      • If the number of routes received from a peer does not exceed the upper threshold, go to Step 9.

    2. Check whether the routes received from the peer are necessary ones.

      • If the routes received from the peer are necessary ones, go to Step 8.
      • If the routes received from the peer are not necessary ones, go to Step 3.

    3. View user log information to check whether a large number of unnecessary routes are received because the local import policy is modified using commands such as peer route-policy, peer ip-prefix, and peer filter-policy.

      • If a large number of unnecessary routes are received because the local import policy is modified, go to Step 4.
      • If a large number of unnecessary routes are received due to other reasons, go to Step 5.

    4. Update the local import policy by using the commands such as the peer route-policy command, the peer ip-prefix command, and the peer filter-policy command to deny the unnecessary routes. Then, check whether the problem is solved. If the fault persists, go to Step 9.
    5. Contact the maintenance engineer responsible for the remote device to check whether the routes sent by the remote device to the local device are necessary ones.

      • If the routes sent by the remote device to the local device are necessary ones, go to Step 7.
      • If the routes sent by the remote device to the local device are not necessary ones, go to Step 6.

    6. Request the maintenance engineer responsible for the remote device to modify the policy for importing routes or the policy for advertising routes to withdraw the unnecessary routes. Then, check whether the fault is rectified. If the fault persists, go to Step 9.
    7. Request the maintenance engineer responsible for the remote device to configure route aggregation to reduce the number of routes to be advertised. Then, check whether the fault is rectified. If the fault persists, go to Step 9.
    8. Increase the maximum number of routes that can be received from the peer. Then, check whether the fault is rectified. If the fault persists, go to Step 9.
    9. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17998

Downloads: 25

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