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

NE40E V800R010C10SPC500 Configuration Guide - IP Routing 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP Routing
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).
Configuring Basic RIP Functions

Configuring Basic RIP Functions

To use RIP features, start RIP and specify the network segment and RIP version first.

Usage Scenario

Configuring basic RIP functions is a prerequisite for building RIP networks.

Pre-configuration Tasks

Before configuring basic RIP functions, complete the following tasks:

  • Configure the link layer protocol.

  • Configure network layer addresses for interfaces to ensure that neighboring nodes are reachable at the network layer.

Configuration Procedures

Figure 7-1 Flowchart for configuring basic RIP functions

Creating a RIP process

The creation of a RIP process is a precondition of all RIP configurations.

Usage Scenario

Before running RIP on a device, you need to create a RIP process on the device.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

    RIP supports multi-instance. To bind a RIP process to a VPN instance, you can run the rip [ process-id ] vpn-instance vpn-instance-name command.

  3. (Optional) Run description

    A description is configured for the RIP process.

  4. Run commit

    The configuration is committed.

Follow-up Procedure

If you run RIP-related commands in the interface view before enabling RIP, the configurations take effect only after RIP is enabled.

Enabling RIP on Specified Network Segments

To enable a RIP process to receive and send RIP routes on specified network segments, enable RIP for the network segments first.

Context

You can perform either of the following operations to enable RIP on specified network segments:
  • Run the network command in the RIP process view to enable a RIP process to receive and send routes on a specified network segment.

  • Run the rip enable command in the interface view to enable a RIP process to receive and send routes on all the network segments where a specified interface is located.
    NOTE:

    The rip enable command takes precedence over the network command.

Procedure

  • Enable a RIP process to receive and send routes on a specified network segment.
    1. Run system-view

      The system view is displayed.

    2. Run rip [ process-id ]

      A RIP process is created, and the view of the RIP process is displayed.

    3. Run network network-address

      RIP is enabled on a specified network segment.

    4. Run commit

      The configuration is committed.

      RIP runs only on interfaces on the specified network segment.

  • Enable a RIP process to receive and send routes on all specified network segments where a specified interface is located.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run rip enable process-id

      RIP is enabled on all the network segments where the interface is located.

    4. Run commit

      The configuration is committed.

(Optional) Configuring the RIP Version Number

RIP include RIP-1 and RIP-2. The two versions have different functions.

Procedure

  • Configure the global RIP version number.
    1. Run system-view

      The system view is displayed.

    2. Run rip [ process-id ]

      A RIP process is created, and the RIP view is displayed.

    3. Run version version-num

      The global RIP version number is specified.

      NOTE:

      The RIP-1 protocol poses a security risk, and therefore the RIP-2 protocol is recommended.

    4. Run commit

      The configuration is committed.

  • Configure the RIP version number on an interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run rip version { 1 | 2 [ broadcast | multicast ] }

      The RIP version number is specified for the interface.

      NOTE:

      The RIP-1 protocol poses a security risk, and therefore the RIP-2 protocol is recommended.

    4. Run commit

      The configuration is committed.

Configuring the RIP Priority

When multiple routing protocols are running on the same device, you can adjust the priority of RIP for route selection.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Run preference { preference | { route-policy route-policy-name | route-filter route-filter-name } } *

    The RIP priority is set.

    The preference command can be used with a routing policy to set the priority for routes that match the routing policy.

    After RIP routes are delivered to the RM, if the RIP priority changes, the RM updates the routing table again.

  4. Run commit

    The configuration is committed.

(Optional) Disabling Check on the Source Address of RIP Packets on a P2P Network

On a P2P network, IP addresses of interfaces at the two ends of a link may belong to different networks. Therefore, the two ends can receive packets from each other only when the check on the source addresses of RIP packets is disabled.

Context

By default, RIP checks the source addresses of received packets, and the local RIP interface receives only the packets from the same network. On a P2P network, IP addresses of interfaces at the two ends of a link may belong to different networks. Therefore, the two ends can receive packets from each other only when the check on the source addresses of RIP packets is disabled.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Run undo verify-source

    The check on the source address of RIP packets is disabled.

  4. Run commit

    The configuration is committed.

(Optional) Enabling Check on Zero Fields of RIP-1 Packets

Certain fields in RIP-1 packets must be 0, and these fields are called zero fields.

Context

Certain fields in RIP-1 packets must be 0, and RIP-2 packets contain no zero fields.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Run checkzero

    The check on zero fields of RIP-1 packets is configured.

  4. Run commit

    The configuration is committed.

Configuring an NBMA Network

RIP packets on a Non-Broadcast Multiple Access (NBMA) network are sent in a mode different from those on networks of other types, and therefore, special configurations are required.

Usage Scenario

RIP packets are sent in unicast mode only on an NBMA network. On networks of other types, RIP packets are sent in either broadcast or multicast mode.

Therefore, you need to perform the following configurations for an NBMA network:
  • Specify RIP neighbors.
  • Prevent interfaces from sending RIP packets in either broadcast or multicast mode.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Run peer ip-address

    RIP neighbors are configured on the NBMA network.

  4. Perform either of the following operations as required:

    • Run the silent-interface all command to prevent all interfaces from sending RIP packets in either broadcast or multicast mode.

    • Run the silent-interface interface-type interface-number command to prevent a specified interface from sending RIP packets in either broadcast or multicast mode.

    NOTE:

    If you want a small number of interfaces to send RIP packets in either broadcast or multicast mode, you can run the silent-interface all command first to prevent all interfaces from sending RIP packets in either broadcast or multicast mode and then run the silent-interface disable interface-type interface-number command to restore the capability to send RIP packets in either broadcast or multicast mode for the small number of interfaces.

  5. Run commit

    The configuration is committed.

Verifying the Basic RIP Configuration

After configuring basic RIP functions, verify the current running status of RIP and RIP routing information.

Prerequisites

Basic RIP functions have been configured.

Procedure

  • Run the display rip [ process-id | vpn-instance vpn-instance-name ] command to check the running status and RIP configurations.
  • Run the display rip process-id route command to check RIP routes.

Example

Run the display rip command to view the running status and RIP configurations, such as the RIP process, version number, and whether the check on the source address is enabled.

<HUAWEI> display rip
 Public VPN-instance
    RIP process : 1
       RIP version  : 1
       Preference    : 100
       Checkzero     : Enabled
       Default-cost  : 0
       Summary       : Enabled
       Host-route    : Enabled
       Maximum number of balanced paths : 32
       Update time   : 30 sec     Age time             : 180 sec
       Suppress time : 0 sec      Garbage-collect time : 120 sec
       Graceful restart  : Disabled
       BFD               : Disabled
       Silent-interfaces : None
       Default-route : Disabled
       Verify-source : Enabled
       Networks : 
       10.0.0.0       
       Configured peers             : None
       Number of routes in database : 2
       Number of interfaces enabled : 1
       Number of VRRP interfaces    : 0
       Triggered updates sent       : 1
       Number of route changes      : 0
       Number of replies to queries : 1
  Total count for 1 process :
       Number of routes in database : 2
       Number of interfaces enabled : 1
       Number of VRRP interfaces    : 0
       Number of routes sendable in a periodic update : 0
       Number of routes sent in last periodic update : 0

Run the display rip process-id route command to view all the active and inactive routes of the specified RIP process.

<HUAWEI> display rip 1 route
 Route Flags: R - RIP
              A - Aging, S - Suppressed, G - Garbage-collect 
 ----------------------------------------------------------------------------
 Peer 192.4.5.1  on GigabitEthernet4/0/1
      Destination/Mask        Nexthop     Cost   Tag     Flags   Sec
        172.4.0.0/16         192.4.5.1      1    0        RA      15
        192.13.14.0/24       192.4.5.1      2    0        RA      15
        192.4.5.0/24         192.4.5.1      1    0        RA      15
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 49177

Downloads: 201

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