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 a BGP peer relationship is set up.

    Run the display bgp peer command to check whether the BGP peer relationship is in the Established state.

  2. Check whether the BGP ORF function is enabled on BGP peers and the peers succeed in negotiating the BGP ORF capability.

    Run the display current-configuration configuration bgp command on the BGP peers to check whether peer ipv4-address capability-advertise orf ip-prefix is configured in the IPv4 unicast address family view.

    <HUAWEI> display current-configuration configuration bgp
    #
    bgp 100
    peer 7.1.1.1 as-number 100
    #
     ipv4-family unicast
      peer 7.1.1.1 ip-prefix in import
      
    #                              

    BGP ORF has three modes: send, receive, and both. In send mode, a device can send ORFs; in receive mode, a device can receive ORFs; in both mode, a device can both send and receive ORFs. To enable a device to receive ORF IP-prefix information, configure both or receive mode on the device and both or send mode on its peer.

    • If one peer is not configured with the BGP ORF function, enter the BGP IPv4 unicast address family view and run the peer ipv4-address capability-advertise orf ip-prefix command to enable BGP ORF. If both or receive is specified when you configure the local peer, both or send must be specified when you configure the remote peer.

      <HUAWEI> system-view
      [~HUAWEI] bgp 100
      [~HUAWEI-bgp] ipv4-family unicast
      [~HUAWEI-bgp-af-ipv4] peer 7.1.1.1 capability-advertise orf ip-prefix both

      If BGP ORF is enabled on both BGP peers, wait for the re-establishment of a BGP peer relationship, and run the display bgp peer ipv4-address verbose command to check whether the BGP ORF capability is successfully negotiated. The command output shows the ORF capabilities on both the local and remote peers.

      <HUAWEI> display bgp peer 7.1.1.1 verbose | include Address-Prefix
                           

      In this command output, the first part shows the ORF capability announced by the remote peer and the subsequent part shows the ORF capability configured on the local peer. The ORF capability supported by non-Huawei devices is different from that defined in the RFC standard. Therefore, to enable Huawei devices to communicate with non-Huawei devices, new commands for compatibility are added. Ensure that both BGP peers are configured with the same compatibility mode (either Cisco-compatible or RFC-compatible).

    • If both BGP peers are configured with the BGP ORF function and succeed in negotiating the BGP ORF capability, go to Step 3.

  3. Check whether an import IP-prefix policy is configured on the remote peer (route receiver).

    Run the display current-configuration configuration bgp command on the remote peer to check whether peer ipv4-address ip-prefix ip-prefix-name import is configured in the IPv4 unicast address family view.

    <HUAWEI> display current-configuration configuration bgp
    #
    bgp 100
    peer 7.1.1.1 as-number 100
    #
     ipv4-family unicast
      
      peer 7.1.1.1 capability-advertise orf ip-prefix both
    #      

    • If no import IP-prefix policy is configured on the remote peer, enter the BGP IPv4 unicast address family view, and run the peer ipv4-address ip-prefix ip-prefix-name import command to configure an import IP-prefix policy.

      <HUAWEI> system-view
      [~HUAWEI] bgp 100
      [~HUAWEI-bgp] ipv4-family unicast
      [~HUAWEI-bgp-af-ipv4] peer 7.1.1.1 ip-prefix in import
    • If an import IP-prefix policy is configured on the remote peer but the local peer still cannot receive ORF IP-prefix information from the remote peer, go to Step 4.

  4. Check whether the prefix list corresponding to the import IP-prefix policy is configured on the remote peer (route receiver).

    Run the display ip ip-prefix ip-prefix-name command on the remote peer to check whether the prefix list corresponding to the import IP-prefix policy is configured.

    <HUAWEI> display ip ip-prefix in
    
    

    This output shows that the prefix list in has not been successfully configured.

    Enter the system view, and run the ip ip-prefix ip-prefix-name index index-number permit ipv4-address mask-length command to configure a prefix list.

    <HUAWEI> system-view
    [~HUAWEI] ip ip-prefix in index 10 permit 10.1.1.0 24

    After completing this configuration, run the display ip ip-prefix ip-prefix-name command on the remote peer to check whether the prefix list corresponding to the import IP-prefix policy is configured.

    <HUAWEI> display ip ip-prefix in
    Prefix-list in
    Permitted 0
    Denied 0
            index: 10               permit  10.1.1.0/24
    

    This output shows that the prefix list in has been successfully configured. After completing these steps, if the local peer still cannot receive ORFs from the remote peer, go to Step 5.

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

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

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 610768

Downloads: 2956

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next