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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs 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/2/hwBgpPeerRouteExceed_active

BGP/2/hwBgpPeerRouteExceed_active

Message

BGP/2/hwBgpPeerRouteExceed_active: The number of routes received from the BGP peer exceeded the alarm number. (InstanceId=[InstanceId], Afi=[AddrFamilyAfi], Safi=[AddrFamilySafi], PeerRemoteAddrType=[PeerRemoteAddrType], PeerRemoteAddr=[PeerRemoteAddr], MaxRouteNum=[MaxRouteNum], AlarmThreshold=[AlarmThreshold])

Description

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

Parameters

Parameter Name Parameter Meaning

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

Possible Causes

Cause: The number of routes received by a BGP device configured with the peer route-limit limit command from its peer exceeded the upper threshold.

Procedure

  • Cause: The number of routes received by a BGP device configured with the peer route-limit limit command from its peer exceeded the upper threshold.
    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.
    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.
    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.
    9. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 119412

Downloads: 89

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