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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical 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).
RIP Troubleshooting

RIP Troubleshooting

This chapter describes common causes of RIP faults and provides troubleshooting flowcharts and procedures, alarms, and logs to help identify and rectify these faults.

A Device Fails to Receive Some or All Routes

This section describes how to troubleshoot the failure of a device in receiving some or all routes.

Common Causes

Common causes are as follows:

  • RIP is not enabled on the interface.

  • The interface is not Up.

  • The authentication type and password in the packet from the other end are different from the local ones.

  • The RIP version in the packet from the other end is different from the local one.
    NOTE:

    A RIPv2–capable interface can receive both RIPv1 and RIPv2 packets.

  • The interface is disabled from receiving RIP packets using the undo rip input command.

  • A policy is configured, and the RIP routes are filtered out.

  • The metrics of the received routes are greater than 16.

  • The same route is learned from another protocol.

  • The number of received routes exceeds the upper limit.

Troubleshooting Flowchart
Figure 4-56 Flowchart for troubleshooting the RIP route reception fault

Troubleshooting Procedure

Context

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that RIP is enabled on the interface.

    The network command is used to enable RIP on interfaces in the specified network segment. An interface can receive and send RIP routing information only after RIP is enabled.

    Run the display current-configuration configuration rip command to check whether RIP is enabled on the interface.

    The network address specified in the network command must be a natural network segment.

  2. Check the status of the interface.

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

    • If the physical status of the interface is Down or Administratively Down, the interface cannot receive routes.
    • If the protocol status of the interface is Down, the costs of the RIP routes learned from the interface are changed to 16 and then the routes are cleared.

    Therefore, ensure that the interface is UP.

  3. Check that the RIP version in the packet from the other end is the same as the local one.

    If the RIP version in the packet from the other end is different from the local one, RIP routes may be discarded.

  4. Check that the undo rip input command is not run on the interface.

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

    The undo rip input command disables the specified interface from receiving RIP packets. If the undo rip input command is run on the interface, the interface does not process received RIP packets. As a result, the routing information cannot be received.

  5. Check whether a routing policy is configured and filters out received RIP routes.

    The filter-policy import command is used to filter received RIP routing information.

    • If an ACL is adopted, run the display acl command to check whether the learned RIP routing information is filtered out.

      Use the suffix list of the IP address to filter the route.

      If an IP prefix list is adopted, run the display ip ip-prefix command to check whether the learned RIP routing information is filtered out.

    • If the routing information is filtered out by the routing policy, re-configure the routing policy.
  6. Check whether the rip metricin command is run on the interface and increases the metric of the received route to a value greater than 16.

    The rip metricin command sets the metric to be added to received routes.

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

  7. Check whether load balancing is configured.

    Run the display this command in the RIP view to check the maximum number of RIP routes for load balancing.

    If the number of RIP routes in the routing table has reached the maximum value, no more routes are added to the routing table.

  8. Check whether the verify-source command is configured.

    The verify-source command enables a device to validate the source address of each received packet. The device discards the packets from a different network segment. By default, this function is enabled.

    If the device needs to receive packets from a different network segment, run the undo verify-source command in the RIP view.

  9. Check whether the same route learned by another protocol is available in the routing table.

    Run the display rip route command to check whether the same route learned by another protocol is available in the routing table.

    • The interface may have received the same route from RIP and another protocol, such as OSPF or IS-IS.
    • By default, the priority of OSPF or IS-IS is higher than that of RIP. If the same route is learned from OSPF or IS-IS, the RM module prefers the OSPF or IS-IS route to the RIP route. To change the priority of RIP to a larger value, run the preference command.
    • After the priority of RIP is changed to a value greater than that of OSPF or IS-IS, run the display ip routing-table protocol rip verbose command. The RIP route is displayed in the command output, and the state of the route is active.
  10. Check the RIPv2 authentication passwords.

    For RIPv2, if authentication is configured at both ends, the authentication passwords at both ends must be the same.

  11. contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure

    • Configuration, log, and alarm files

Relevant Alarms and Logs

Relevant Alarms

None

Relevant Logs

None

A Device Fails to Send Some or All Routes

This section describes how to troubleshoot the failure of a device in sending some or all routes.

Common Causes

Common causes are as follows:

  • RIP is not enabled on the interface.

  • The interface is not Up.

  • The interface is prevented from sending RIP packets using the silent-interface command.

  • The interface is prevented from sending RIP packets using the undo rip output command.

  • A filtering policy is configured on the interface.

  • The physical status of the interface is Down or Administratively Down, or the status of the protocol on the interface is Down.

  • The interface does not support multicast or broadcast, and a packet needs to be sent to the multicast or broadcast address.

  • The number of received routes exceeds the upper limit.

  • The maximum packet length configured on the interface is less than the length of packets to be sent.

Troubleshooting Flowchart
Figure 4-57 Flowchart for troubleshooting the failure of a device in sending some or all routes

Troubleshooting Procedure

Context

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that RIP is enabled on the interface.

    The network command is used to enable RIP on interfaces in the specified network segment. An interface can receive and send RIP routing information only after RIP is enabled.

    • Run the display current-configuration configuration rip command to check whether RIP is enabled on the interface.

      Check whether RIP is enabled on the interface.

      The network address specified in the network command must be a natural network segment.

  2. Check the status of the interface.

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

    If the physical status of the interface is Down or Administratively Down, or the protocol status is Down, the interface cannot send routes. Therefore, ensure that the interface is UP.

  3. Check that the silent-interface command is not run on the interface.

    The silent-interface command disables the interface from sending RIP packets.

    • Run the display current-configuration configuration rip command to check if the interface is disabled from sending RIP packets.
    • Enable the interface by running the undo silent-interface command.
  4. Check that the undo rip output command is not run on the interface.

    Run the display current-configuration command on the interface to check whether the rip output command is run.

    The rip output command enables the interface to send RIP packets.

    The undo rip output command disables the interface from sending RIP packets.

  5. Check whether Classful route summarization has been configured.

    The rip summary-address command enables Classful route summarization. Classful route summarization reduces the number of RIP packets on the network, but subnet routes will not be advertised. If Classful summarization is enabled, run the undo rip summary-address command to disable it.

    If RIPv2 is configured on the interface, Classful summarization is enabled by default. In this situation, disable it.

  6. Check whether the metric value is greater than or equal to 16.

    Run the display rip database command to check the metric value of the route. If the metric value is greater than or equal to 16, it is considered unreachable.

    Before RIP packets are sent, a RIP metric value is added to the packets. You can decrease the metric value.

  7. Check whether a routing policy is configured and filters out imported routes.

    The filter-policy export command configures an export policy globally.

    If an export policy is configured, only the routes whose attributes match those specified in the policy are added to the RIP routing table and advertised through update packets.

  8. Check the status of the local interface if the routes to be advertised are destined for the interface.

    Run the display interface command to check the status of the interface. If the status of the interface is Down or Administratively Down or the status of the protocol on the interface is Down, the routes destined for the interface cannot be added to the RIP routing table nor sent to neighbors.

  9. Check whether the update timer value is too large and the age timer and garbage timer are too small.

    Run the display rip command to check the values of RIP timers. If the update timer is too large, routes may be suppressed. If the age timer and garbage timer are too small, routes are deleted from the database.

    • Decrease the update timer value, such as to 30s.
    • Increase the age timer and garbage timer, such as to 120s and 180s, respectively.
  10. Check whether other special issues exist.

    If the interface does not support multicast or broadcast and the packet needs to be sent to the multicast or broadcast address, the fault occurs; in this case, run the peer command in the RIP view so that packets are sent in unicast mode.

  11. Check whether the maximum packet length on the interface is too short.

    Run the display current-configuration configuration command to check the maximum packet length.

    Packets are not transmitted if the maximum packet length is less than 32. Therefore, the maximum packet length must be greater than or equal to 32.

    NOTE:
    • For the interfaces on which simple authentication is configured, the maximum packet length is 52.

    • For the interfaces on which MD5 authentication in nonstandard mode, the maximum packet length is 56.

    • For the interfaces on which MD5 authentication in usual mode, the maximum packet length is 72.

  12. contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure

    • Configuration, log, and alarm files

Relevant Alarms and Logs

Relevant Alarms

None

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13806

Downloads: 257

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