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 RIP is enabled on the outbound interface.

    The network command is used to specify the interface network segment. Only an interface enabled with RIP protocol can receive and send RIP routes. Using the display current-configuration configuration rip command, check the information about the network segment where RIP is enabled. Check whether the outbound interface is enabled.

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

  2. Check whether the outbound interface works normally.

    Use the display interface command to check the running status of the outbound interface.

    If the physical state of the interface is down or Administratively Down or the state of the current protocol is Down, RIP cannot work normally on the interface.

    Therefore, the interface should be in UP state.

  3. Check whether the silent-interface command is configured on the outbound interface.

    The silent-interface command disables the interface from sending the RIP packet. Run the display current-configuration configuration rip command to check if the interface is disabled from sending the RIP packet. Enable the interface by running the undo silent-interface command.

  4. Check whether the undo rip output command is configured on the outbound interface.

    Run the display current-configuration command on the outbound interface to verify whether the rip output command is configured. The rip output command enables the interface to send the RIP packets. The undo rip output command disables the interface from sending the RIP packets. If the outbound interface is configured with the undo rip output command, the RIP packet cannot be sent on the interface.

  5. Check whether the summary has been configured.

    The rip summary-address command disables Classful summarization to perform routing between subnets. When Classful summarization is off, subnets are advertised. This feature is used to reduce the number of RIP packets on the network.

    If RIPv2 is configured on the interface, it always uses Classful summarization. In this case, you can run the undo rip summary-address command.

  6. Check whether the sum of the route and metric out value is greater than 16.

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

    While sending RIP routes, the RIP metricout value is added to the RIP packets. To correct this fault, decrease the metricout value for the interface through which the route is sent.

  7. Check whether routes exist in the RIP database.

    Run the display rip database command to check whether routes exist in the RIP database. If there is no route in the RIP database, routes fail to be sent.

  8. Check whether the policy that filters the imported RIP route is configured in RIP.

    Using the filter-policy export command, configure the filtering policy on the global interface. Only the route whose attributes match those specified in the filter policy are added to the advertised routing table of RIP and advertised through the updated packet.

  9. Check the status of the interface when the route is sent to the local interface address.

    Run the display interface command to check the running status of the interface. If the physical state of the interface is down or Administratively Down or the current state of the protocol on the outbound interface is down, the IP address of the interface cannot be added to the advertised routing table of RIP. Therefore, the routing information is not sent to the neighbor.

  10. Check whether the periodic timer value is too high and the age timer and garbage timer are too low.

    Run the display rip command to check the value of the RIP timers.

    If the update timer value is configured to a very high value, the updates are sent after a long period giving the impression that the router is not functioning properly. If the age timer and garbage timer are configured too less, then the route is removed from the database

    • Configure the periodic timer value to a smaller value, such as 30 seconds to get frequent updates.
    • Configure the age timer and garbage time to larger values, such as 120, 180 seconds respectively.
  11. Check whether other issues exist.

    If the outbound interface does not support the multicast or broadcast mode and the packet needs to be sent to the multicast or broadcast address, the fault occurs. Configure the peer command in RIP mode and send the packet to the unicast address. This action prevents the fault from occurring.

  12. Check whether the maximum packet length on the interface is less.

    Using the display current-configuration configuration command, check the information about the maximum packet length where RIP is enabled.

    Packets are not transmitted out if the maximum packet length is less than 32. Reconfigure the maximum packet length on the interface to at least 32.

    • The maximum packet length is 52 for an interface configured with simple authentication.

    • The maximum packet length is 56 for an interface configured with MD5 authentication in nonstandard mode.

    • The maximum packet length is 72 for an interface configured with MD5 authentication in usual mode.

  13. 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

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 616551

Downloads: 2965

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next