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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
Troubleshooting Procedure

Troubleshooting Procedure

After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the two-phase validation mode.

  • In immediate validation mode, the configuration takes effect immediately after you run a command and press Enter.
  • In two-phase validation mode, you must run the commit command after commands are configured to commit the configuration.

Save the results of each troubleshooting step, so you can provide related information to Huawei technical support if your troubleshooting fails.

Procedure

  1. Check whether the next hops of routes are reachable.

    Run the display bgp routing-table network { mask | mask-length } command on the local device that sends routes to check whether the target route is active and has been sent to the peer. network specifies the prefix of the target route.

    In the following example, the target route is a route to 10.0.0.0/8. The command output shows that this route is valid and has been selected and sent to the peer at 10.3.3.3. The original next hop and iterated next hop of this route are 10.1.1.1 and 172.16.1.1 respectively.

    <HUAWEI display bgp routing-table 10.0.0.0 8
    
     BGP local router ID : 10.1.1.2
     Local AS number : 100
     Paths:   1 available, 1 best, 1 select
     BGP routing table entry information of 10.0.0.0/8:
     From: 10.1.1.1 (121.1.1.1)
     Route Duration: 4d21h29m39s
     : 172.16.1.1
     Relay IP Out-Interface: Vlanif50
     : 10.1.1.1
     Qos information : 0x0
     AS-path Nil, origin incomplete, localpref 100, pref-val 0, , internal, , select, active, pre 255
     Aggregator: AS 100, Aggregator ID 121.1.1.1
     :
        10.3.3.3

    • If the target route is inactive, check whether there is a route to the original next hop in the IP routing table. If no route to the original next hop exists, the BGP route is not advertised because its next hop is unreachable. Determine why there is no route to the original next hop. Note that this fault is generally associated with IGP or static routes.

    • If the target route is active and has been selected but there is no information indicating that this route is sent to the peer, perform Step 2 to check the outbound policy applied to the local device.

    • Run the display bgp routing-table network { mask | mask-length } command on the peer to check whether it has received the target route.

      • If the peer has received the target route, perform Step 1 again to check whether the next hop of the route is reachable and whether this route has been selected.

      • If the peer has not received the target route, perform Step 2 to check the inbound policy applied to the peer.

    In BGP4+ networking, the display bgp routing-table ipv6-address prefix-length command is used to check whether the target route is received.

  2. Check whether the routing policies are configured correctly.

    Run the display current-configuration configuration bgp command on the local device and the peer to check whether the inbound and outbound policies are configured.

    <HUAWEI> display current-configuration configuration bgp
    #
    bgp 100
     peer 10.1.1.1 as-number 100
     #
     ipv4-family unicast
      
      
      peer 10.1.1.1 enable
      peer 10.1.1.1 
      peer 10.1.1.1 
      peer 10.1.1.1 
      peer 10.1.1.1 
      peer 10.1.1.1 
      peer 10.1.1.1 
      peer 10.1.1.1 
      peer 10.1.1.1 
     #
     ipv4-family vpnv4
      policy vpn-target
      peer 10.1.1.1 enable
    #
    return

    • If the inbound and outbound policies are configured on the two devices, you need to check whether the target route is filtered by these policies.

    • If the inbound and outbound policies are not configured on the two devices, go to Step 3.

  3. Check whether the number of routes is lower than the upper limit.

    Run the display current-configuration configuration bgp | include peer destination-address or display current-configuration configuration bgp | include peer group-name command on the peer to check whether an upper limit on the number of routes to be received is configured on the peer.

    For example, if the upper limit is set to 5, subsequent routes are dropped and a log is recorded after the peer receives five routes from the local device at 10.1.1.1.

    <HUAWEI> display current-configuration configuration bgp | include peer 10.1.1.1
     peer 10.1.1.1 as-number 100
     peer 10.1.1.1 
      peer 10.1.1.1 enable

    If a peer is added to a peer group, there may be no configurations of the upper limit in the command output.

    <HUAWEI> display current-configuration configuration bgp | include peer 10.1.1.1
     peer 10.1.1.1 as-number 100
     peer 10.1.1.1 
      peer 10.1.1.1 enable
      peer 10.1.1.1 

    In this case, run the display current-configuration configuration bgp | include peer group-name command to check the configurations of this peer group.

    <HUAWEI> display current-configuration configuration bgp | include peer IBGP
     peer 
      peer IBGP enable

    If the alarm BGP_1.3.6.1.4.1.2011.5.25.177.1.3.6 hwBgpPeerRouteExceed is generated when traffic is interrupted, the target route is dropped because the upper limit is exceeded. When this occurs, increase the upper limit.

    Changing the upper limit on the number of routes to be received from a peer interrupts the BGP peer relationship. Therefore, reduce the number of sent routes by configuring route summarization on the local device.

  4. Collect the following information and contact technical support personnel.

    • Results of this troubleshooting procedure.
    • Configuration files, log files, and alarm files of the devices.

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 613282

Downloads: 2962

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next