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.

Configuration Guide - IP Unicast Routing
CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.

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).
Summary of RIP Configuration Tasks

Summary of RIP Configuration Tasks

Table 3-2 describes the RIP configuration tasks.

Table 3-2 RIP configuration tasks




Configuring basic RIP functions

Basic RIP functions include enabling RIP, specifying the network segment where RIP runs, and specifying the RIP version. The basic RIP functions must be configured before you use the RIP features.

Configuring Basic RIP Functions

Configuring RIP-2 features

RIP-2 is a classless routing protocol, and the RIP-2 packets contain subnet masks. Therefore, deploying a RIP-2 network can save IP addresses. Only RIP-2 can be deployed on a network where the IP addresses are discontinuous, and RIP-1 cannot be used.

RIP-2 supports authentication for protocol packets and provides multi-authentication modes to enhance security.

Configuring RIP-2

Preventing routing loops

RIP is a routing protocol based on the distance vector algorithm. RIP devices advertise their local routing tables to neighbors, so routing loops may occur.

RIP uses split horizon and poison reverse to prevent routing loops:
  • Split horizon: A route learnt by RIP from an interface is not sent to neighbors from the interface. This reduces bandwidth consumption and prevents routing loops.
  • Poison reverse: RIP sets the cost of a route learnt from an interface to 16 (an unreachable route), and sends the route to neighbors through the interface. In this way, RIP can delete useless routes from the neighbor routing table and prevent routing loops.

Preventing Routing Loops

Controlling RIP routing

To use RIP more flexibly on the existing network and meet various user requirements, you can configure different parameters to control RIP routing.

Controlling RIP Routing

Controlling the advertising and receiving of RIP routes

In practical applications, to meet network requirements, you can configure different parameters to accurately control the advertising and receiving of RIP routes.

Controlling RIP Route Advertisement

Controlling Receiving of RIP Routing Information

Improving RIP network performance

In practical applications, you can configure special RIP functions to improve RIP network performance.
  • Adjusting the value of the RIP timer to change the RIP network convergence rate.
  • Adjusting the number and interval of Update packets sent by the interface to reduce device resource and network bandwidth consumption.
  • Increasing the maximum length of RIP packets to add more routes to the packets, which improves bandwidth usage.
  • Enabling the replay-protect function to ensure normal communication between neighboring devices after the RIP process restarts.
  • Checking packet validity to meet network requirements for high security.

Improving RIP Network Performance

Configuring BFD for RIP

In general, RIP maintains neighbor relationships by periodically sending and receiving Update packets. If a device does not receive the Update packet from a neighbor in the aging time, it considers the neighbor Down. The default value of the aging timer is 180 seconds, so RIP can detect a link fault only after the fault lasts for 180 seconds. If high-speed data services are deployed on the network, a large amount of data will be lost during this period.

BFD provides the millisecond-level fault detection mechanism. It can detect faults on the protected links or nodes immediately, and report the faults to RIP. BFD improves the RIP process's response to network topology changes, which implements fast convergence of RIP routes.

Configuring BFD for RIP

Configuring the Network Management Function for RIP

By binding RIP to the MIB, you can view RIP information and configure RIP through the NMS.

Configuring the Network Management Function for RIP

Updated: 2019-03-21

Document ID: EDOC1000166601

Views: 291580

Downloads: 168

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next