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

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
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).
Device Does not Receive Partial or All the Routes

Device Does not Receive Partial or All the Routes

Common Causes

This fault is commonly caused by one of the following:

  • The incoming interface is not enabled with RIP.

  • The incoming interface is not in Up state.

  • The version number sent by the peer does not match with that received on the local interface.

  • The interface is disabled to receive the RIP packet.

  • The policy used to filter the received RIP routes is configured.

  • The metric of the received routes is larger than 16.

  • Other protocols have learned the same routes in the routing table.

  • The number of the received routes exceeds the upper limit.

  • The MTU value of the incoming interface is less than 532.

  • The authentication of sending and receiving interface is not matching.

Troubleshooting Flowchart

If a router receives partial or none routes or the display ip routing-table command dose not display routes learned by RIP, refer to the following troubleshooting flowchart, as shown in Figure 19-1.

Figure 19-1  RIP route receiving troubleshooting flowchart

Troubleshooting Procedure

Context

NOTE:

Saving the results of each troubleshooting step is recommended. If you are unable to correct the fault, you will have a record of your actions to provide technical support personnel.

Procedure

  1. Check that the incoming interface is enabled with RIP.

    The network command is used to specify the interface network segment. Only the interface enabled with RIP can receive and send the RIP routing information.

    Run the display current-configuration configuration rip command to check information about the network segment where RIP is enabled. Check whether the outgoing interface is enabled.

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

  2. Check that the incoming interface works normally.

    Run the display interface command to check the operating status of the incoming interface:

    • If the current physical status of the interface is Down or Administratively Down, RIP cannot receive any route from the interface.

    • If the current protocol status of the interface is Down, the cost of routes learnt by RIP from the interface changes to 16, and then is deleted.

    Therefore, ensure the normal status of the interface.

  3. Check that the version number sent by the peer matches with that received on the Local Interface.

    By default, the interface sends only RIP-1 packets, but can receive both RIP-1 and RIP-2 packets. If the version number of the incoming interface and that of the RIP packet are different, RIP routing information may not be received correctly.

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

    The rip input command enables a specified interface to receive RIP packets.

    The undo rip input command disables a specified interface from receiving RIP packets.

    If the undo rip input command is configured on the incoming interface, all the RIP packets from the interface cannot be processed. Therefore, the routing information cannot be received.

  5. Check whether a policy used to filter received RIP routes is configured.

    The filter-policy import command is used to filter the received RIP routes. If an ACL is used, run the display current-configuration configuration acl-basic command to view whether the RIP routes learned from the neighbor are filtered. If the IP-Prefix list is used to filter routes, the display ip ip-prefix command is used to check the configured policy.

    If a routing policy is set to filter routes, it must be configured correctly.

  6. Check whether the incoming interface is configured with the rip metricin command and if the metric is larger than 16.

    The rip metricin command is used to set the metric that is added to a route when the interface receives a RIP packet.

    If the metric exceeds 16, the route is regarded as unreachable and is not added to the routing table.

  7. Check whether the metric of the received routes is larger than 16.

    If the metric of a received route exceeds 16, the route is regarded as unreachable and is not added to the routing table.

  8. Check whether the authentication on the sending and receiving interface is matching.

    Run the display rip process-id statistics interface interface-type interface-number command to check whether packet authentication has failed on the interface.

    If the packet authentication was failed on the interface, it must be configured correctly.

  9. Check whether other protocols have learned the same routes in the routing table.

    Run the display rip process-id route command to check whether routes have been received from the neighbor.

    The possible cause 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.

    The weights of OSPF or IS-IS are generally greater than that of RIP. Routes learned through OSPF or IS-IS are preferred by routing management.

    Run the display ip routing-table protocol rip verbose command to view routes in the Inactive state.

  10. If the fault persists, contact technical support personnel and provide them with the following information.

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

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 446398

Downloads: 4301

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