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


To have a better experience, please upgrade your IE browser.


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.


  1. Check whether RIP is enabled on the inbound interface.

    The network command is used to specify the interface network segment. Only an interface enabled with RIP protocol can receive and send RIP routing information. You can run the display current-configuration configuration rip command to view information about the network segment where RIP is enabled and check whether the inbound interface is contained in the network segment.

    The network address enabled by the network command must be that of the natural network segment.

  2. Check whether the inbound interface works normally.

    Run the display interface command to check the running status of the inbound interface.

    • If the physical status of the interface is Down or Administratively Down, the interface cannot receive routes using RIP.

    • If the protocol status of the interface is Down, the cost of RIP routes learned from the interface is changed to 16 and then the routes are deleted.

    Therefore, the UP state of the interface must be ensured.

  3. Check whether the version number sent by the peer matches the version number received on the local interface.

    By default, an interface sends only RIPv1 packets, but it can receive both RIPv1 and RIPv2 packets. If the version numbers of the inbound interface and that of the RIP packet are different, the RIP routing information may not be received correctly.

  4. Check whether the undo rip input command is configured on the inbound interface.

    The rip input command enables the specified interface to receive the RIP packet. The undo rip input command disables the specified interface from receiving the RIP packets. If the undo rip input command is configured on the inbound interface, none of the RIP packets coming from the interface can be processed. Therefore, the routing information cannot be received.

  5. Check whether the policy that filters the received RIP route is configured in RIP.

    The filter-policy import command is used to filter the received RIP routing information. If the ACL is adopted, use the display current-configuration configuration acl-basic command to verify whether the RIP routing information learned from the neighbor is filtered out. Use the suffix list of the IP address to filter the route. Use the display ip ip-prefix command to check the configured policy. If the routing information is filtered out by the routing policy, configure the correct routing policy.

  6. Check whether the inbound interface is configured with the rip metricin command and the metric of received routes is greater than 16.

    The rip metricin command sets the metric added to the route when the interface receives the RIP packet. If the metric exceeds 16, the route is seen as unreachable. Therefore, the route is not added into the routing table.

  7. Check whether maximum load balancing is configured.

    Use the display this command in the RIP view to check the number of maximum balanced paths configured for RIP.

    If the maximum value is reached, then the incoming routes to the same destination are not added to the database.

  8. Check whether the verify-source is configured in the RIP process.

    If the verify-source command is configured in the RIP process, the device checks the source address of incoming RIP packets. The device discards the packets from a different network segment. By default, this feature is enabled.

    If the switch receives RIP packets from a different network, run the undo verify-source command in the RIP view.

  9. Check whether other protocols learning the same route exist.

    Run the display rip route command to check whether routes received from the neighbor exist. One possible case is that the RIP route is received correctly and the local device learns the same route from other protocols, such as OSPF and IS-IS. In general, the preference of OSPF or IS-IS protocol is greater than that of the RIP protocol. Therefore, if the same route is learned through OSPF or IS-IS, RM chooses either of those routes over RIP routes. You can change the preference of RIP to a larger value using the preference command. You can run the display ip routing-table protocol rip verbose to view the route information. The status of the route is active.

  10. Check for authentication keys (for RIPv2).

    For RIPv2, if authentication mode is configured on the sending and receiving interface, then the authentication keys on both the interfaces should be the same.

  11. If the fault persists, collect the following information and contact technical support personnel.

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

Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 613118

Downloads: 2960

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next