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. Run the ping command to check whether the BGP peers can ping each other.
    • If they can ping each other, there are available routes between the BGP peers and that link transmission is normal. In this case, go to Step 2.

      Run the ping -a source-ip-address -s packetsize host or ping ipv6 -a source-ipv6-address -s packetsize destination-ipv6-address command to detect the connectivity of the devices on both ends. Because the source address is specified in this command, you can check whether the two devices have available routes to each other. By specifying the size of a Ping packet, you can check whether large Ping packets can be normally transmitted over the link.

    • If the ping operation fails, rectify the ping operation failure.

  2. Check whether any ACL is configured to filter the packets whose destination port is TCP port 179.

    Run the display acl all command on the two devices to check whether an ACL is configured to filter the packets whose destination port is TCP port 179.

    <HUAWEI> display acl all
    Advanced ACL 3001, 2 rules
    ACL's step is 5
    ACL's match-order is config
      rule 5 deny 
      rule 10 deny 

    • If an ACL is configured to filter the packets whose destination port is TCP port 179, run the undo rule rule-id command to delete the ACL configuration.

    • If no such ACL is configured, go to Step 3.

  3. Check whether the peer router ID conflicts with the local router ID.

    View information about BGP peers to check whether their router IDs conflict. For example, if the IPv4 unicast peer relationship fails to be established, run the display bgp peer command to check whether the peer router ID conflicts with the local router ID. The following command output shows as an example:

    <HUAWEI> display bgp peer
      : 1.1.1.1
     Local AS number : 65001
     Total number of peers : 12                Peers in established state : 4
    
      Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
      10.9.0.8        4         100     1601     1443     0 23:21:56 Established   10000
      10.10.0.10      4         200     1565     1799     0 23:15:30 Established    9999
    Check information about peers in other address families.
    • Run the display bgp vpnv4 all peer command to check information about all VPNv4 peers.
    • Run the display bgp ipv6 peer command to check information about IPv6 peers.
    • Run the display bgp vpnv6 all peer command to check information about all VPNv6 peers.

    • If the peer router ID conflicts with the local router ID, run the router id command in the BGP view to change the two router IDs to different values. Generally, a loopback interface address is used as the local router ID.

    • If the peer router ID does not conflict with the local router ID, go to Step 4.

  4. Check whether the peer AS number is configured correctly.

    Run the display bgp peer command on each device to check whether the displayed peer AS number is the same as the remote AS number.

    <HUAWEI> display bgp peer
     BGP local router ID : 223.5.0.109
      : 41976
     Total number of peers : 12                Peers in established state : 4
    
      Peer            V            MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
      10.9.0.8        4         100     1601     1443     0 23:21:56 Established   10000
      10.10.0.10      4         200     1565     1799     0 23:15:30 Established    9999
    Check information about peers in other address families.
    • Run the display bgp vpnv4 all peer command to check information about all VPNv4 peers.
    • Run the display bgp ipv6 peer command to check information about IPv6 peers.
    • Run the display bgp vpnv6 all peer command to check information about all VPNv6 peers.

    • If the peer AS number is incorrectly configured, change it to be the same as the remote AS number.

    • If the peer AS number is configured correctly, go to Step 5.

  5. Check whether BGP configurations affect the establishment of the BGP peer relationship.

    Run the display current-configuration configuration bgp command to check the BGP configurations.

    Item

    Description

    peer connect-interface { interface-type interface-number | ipv4-source-address }

    If two devices use loopback interfaces to establish the BGP peer relationship, run the peer connect-interface command to specify the source interface through which the BGP packets are sent, and the source address with which the BGP connection is established.

    peer ebgp-max-hop hop-count

    When two directly connected devices use loopback interfaces to establish the EBGP peer relationship or two indirectly connected devices establish the EBGP peer relationship, run the peer ebgp-max-hop command and specify the maximum number of hops between the two devices.

    • When two directly connected devices use loopback interfaces to establish the EBGP peer relationship, the hop count can be any number greater than 1.

    • When two indirectly connected devices establish the EBGP peer relationship, specify the number of hops according to the actual situation.

    NOTE:

    The peer ebgp-max-hop command must be configured on the devices on both ends.

    peer valid-ttl-hops hops

    If the peer valid-ttl-hops hops command is configured, check whether the value of hops is correct. The valid TTL range of the detected packet is [255 - hops + 1, 255]. hops specifies the number of hops between the devices on both ends. The hop count between the two directly connected devices is 1.

    NOTE:

    The peer valid-ttl-hops command must be configured on the devices on both ends.

    peer route-limit limit

    If the peer route-limit limit command is configured, check whether the number of routes sent by the peer exceeds the upper limit specified by limit. If the upper limit is exceeded, reduce the number of routes to be sent by the peer, and run the reset bgp ip-address command to reset the BGP peer relationship to trigger the re-establishment of the BGP peer relationship.

    peer ignore

    If the peer ignore command is configured on the peer, the peer is not required to establish a temporary BGP peer relationship with the local device. To establish the BGP peer relationship between the peer and the local device, run the undo peer ignore command on the peer.

    Address family capability

    Check whether the address family capabilities of the devices on both ends match. For example, in order to establish the BGP VPNv4 peer relationship, the peer enable command must be configured in the BGP-VPNv4 address families of both devices. If the peer enable command is configured on one device only, the BGP peer relationship on the device is displayed as No neg, which means the address family is not enabled for the BGP peer.

  6. 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: 616415

Downloads: 2965

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next