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 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is ME60 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).
Adjusting RIP Route Selection

Adjusting RIP Route Selection

You can adjust RIP route selection on a complicated network.

Usage Scenario

The implementation of RIP is simple, and therefore, RIP is widely used in small and medium networks. To flexibly apply RIP on the live network to meet various requirements of users, you can change RIP route selection by setting different parameters.

Pre-configuration Tasks

Before adjusting RIP route selection, complete the following tasks:

Configuration Procedure

Perform one or more of the following configurations as required.

Disabling RIP-2 Classful Summarization

On the network where subnets are incontiguous, you can cancel the classful summarization of RIP-2 so that more accurate routing information can be obtained.

Context

Summarizing IP addresses can reduce the routing table size, but it shields routing information of subnets. As a result, incorrect routing information may be calculated.

On a non-contiguous subnet, you need to disable RIP-2 classful summarization. On the network shown in Figure 7-2, you need to disable split horizon from interfaces of Router A and Router C.

By default, RIP-2 classful summarization is enabled. Therefore, Router B and Router C send a route destined for 10.0.0.0/8 to Router A. Router A cannot differentiate 10.1.0.0/16, 10.2.0.0/16, 10.4.0.0/16, or 10.5.0.0/16. As a result, incorrect routes are calculated.

Figure 7-2 Disabling RIP-2 classful summarization

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 summary

    RIP-2 classful summarization is disabled.

  4. Run commit

    The configuration is committed.

Configuring the Additional Metric on an Interface

The additional metric is a metric (number of hops) that is added to the original metric of an RIP route. You set additional metrics for received RIP routes and those to be sent.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Set the metric to be added to received routes.

    Run any of the following commands as required:

    • Based on the basic ACL:
      1. Run rip metricin { value | { acl-number | acl-name acl-name } value1 }

      2. Run quit

        Return to the system view.

      3. Run acl { name basic-acl-name { basic | [ basic ] number basic-acl-number } | [ number ] basic-acl-number } [ match-order { config | auto } ]

        The basic ACL view is displayed.

      4. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | source { source-ip-address { source-wildcard | 0 | src-netmask } | any } | time-range time-name | vpn-instance vpn-instance-name ] *

        The rule for the basic ACL is configured.

        When the rule command is run to configure rules for a named ACL, only the source address range specified by source and the time period specified by time-range are valid as the rules.

        When a filtering policy of a routing protocol is used to filter routes:
        • If the action specified in an ACL rule is permit, a route that matches the rule will be received or advertised by the system.

        • If the action specified in an ACL rule is deny, a route that matches the rule will not be received or advertised by the system.

        • If a route has not matched any ACL rules, the route will not be received or advertised by the system.

        • If an ACL does not contain any rules, all routes matching the route-policy that references the ACL will not be received or advertised by the system.

        • If the ACL referenced by the route-policy does not exist, all routes matching the route-policy will be received or advertised by the system.

        • In the configuration order, the system first matches a route with a rule that has a smaller number and then matches the route with a rule with a larger number. Routes can be filtered using a blacklist or a whitelist:

          Route filtering using a blacklist: Configure a rule with a smaller number and specify the action deny in this rule to filter out the unwanted routes. Then, configure another rule with a larger number in the same ACL and specify the action permit in this rule to receive or advertise the other routes.

          Route filtering using a whitelist: Configure a rule with a smaller number and specify the action permit in this rule to permit the routes to be received or advertised by the system. Then, configure another rule with a larger number in the same ACL and specify the action deny in this rule to filter out unwanted routes.

    • Based on the IP prefix:

      Run rip metricin { value | ip-prefix ip-prefix-name value1 }

  4. Set the metric to be added to routes to be sent.

    Run any of the following commands as required:

    • Based on the basic ACL:
      1. Run rip metricout { value | { acl-number | acl-name acl-name } value1 } *

      2. Run quit

        Return to the system view.

      3. Run acl { name basic-acl-name { basic | [ basic ] number basic-acl-number } | [ number ] basic-acl-number } [ match-order { config | auto } ]

        The basic ACL view is displayed.

      4. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | source { source-ip-address { source-wildcard | 0 | src-netmask } | any } | time-range time-name | vpn-instance vpn-instance-name ] *

        The rule for the basic ACL is configured.

        When the rule command is run to configure rules for a named ACL, only the source address range specified by source and the time period specified by time-range are valid as the rules.

        When a filtering policy of a routing protocol is used to filter routes:
        • If the action specified in an ACL rule is permit, a route that matches the rule will be received or advertised by the system.

        • If the action specified in an ACL rule is deny, a route that matches the rule will not be received or advertised by the system.

        • If a route has not matched any ACL rules, the route will not be received or advertised by the system.

        • If an ACL does not contain any rules, all routes matching the route-policy that references the ACL will not be received or advertised by the system.

        • If the ACL referenced by the route-policy does not exist, all routes matching the route-policy will be received or advertised by the system.

        • In the configuration order, the system first matches a route with a rule that has a smaller number and then matches the route with a rule with a larger number. Routes can be filtered using a blacklist or a whitelist:

          Route filtering using a blacklist: Configure a rule with a smaller number and specify the action deny in this rule to filter out the unwanted routes. Then, configure another rule with a larger number in the same ACL and specify the action permit in this rule to receive or advertise the other routes.

          Route filtering using a whitelist: Configure a rule with a smaller number and specify the action permit in this rule to permit the routes to be received or advertised by the system. Then, configure another rule with a larger number in the same ACL and specify the action deny in this rule to filter out unwanted routes.

    • Based on the IP prefix:

      Run rip metricout { value | ip-prefix ip-prefix-name value1 } *

    NOTE:

    When using an ACL or an IP prefix list with the rip metricout command, you can specify the metric to be added to the RIP route that matches the ACL or the IP prefix list. If a RIP route does not match the ACL or the IP prefix list, its metric is increased by 1. When an ACL or an IP prefix list is used with the rip metricout command, the additional metric ranges from 2 to 15.

  5. Run commit

    The configuration is committed.

Setting the Maximum Number of Equal-Cost Routes

You can set the maximum number of equal-cost RIP routes to adjust the number of routes that load-balance traffic.

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 maximum load-balancing number

    The maximum number of equal-cost routes is set.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of RIP Route Selection

After adjusting RIP route selection, verify the running status of RIP, information about interfaces, and RIP routing information.

Prerequisites

RIP route selection has been adjusted.

Procedure

  • Run the display rip [ process-id | vpn-instance vpn-instance-name ] command to check the running status and configuration of RIP.
  • Run the display rip process-id route command to check RIP routes.
  • Run the display rip process-id interface command to check information about RIP interfaces.

Example

Run the display rip process-id command to view the running status and configuration of the RIP process.

<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 : 3
       Update time   : 30 sec  Age time  : 180 sec
       Suppress time : 0 sec   Garbage-collect time : 120 sec
       Silent-interfaces : None
       Default Route : Disabled
       Verify-source : Disabled
       Networks : 172.4.0.0
       Configured peers : None
       Number of routes in database : 4
       Number of interfaces enabled : 3
       Triggered updates sent : 3
       Number of route changes : 6
       Number of replies to queries : 1
       Description : RIP 
  Total count for 1 process:
     Number of routes in database : 1
     Number of interfaces enabled :  1
     Number of routes sendable in a periodic update : 1
     Number of routes sent in last periodic update : 1

Run the display rip process-id interface verbose command to view the metric to be added to received routes or routes to be sent on the interface.

<HUAWEI> display rip 1 interface verbose
GigabitEthernet1/0/0 (1.1.1.2)
  State    : UP              MTU: 0
  Metricin : 2
  Metricout: 3
  Input    : Disabled        Output: Disabled                  
  Protocol : RIPv2 Multicast                                   
  Send     : RIPv2 Multicast Packets                           
  Receive  : RIPv2 Multicast Packets                           
  Poison-reverse                : Enabled                      
  Split-Horizon                 : Enabled                      
  Authentication type           : None                         
  Max Packet Length             : 512                          

Run the display rip process-id route command to view whether there are routes for load balancing. The following command output shows that there are two equal-cost routes with the same destination address (10.10.10.10/32) and but different next hops.

<HUAWEI> display rip 1 route
 Route Flags: R - RIP
              A - Aging, S - Suppressed, G - Garbage-collect 
 ----------------------------------------------------------------------------
 Peer 1.1.1.1 on GigabitEthernet3/0/2
      Destination/Mask        Nexthop     Cost   Tag     Flags   Sec
        2.2.2.0/24            1.1.1.1        1     0      RA       7
        10.10.10.10/32        1.1.1.1        1     0      RA       7  
 Peer 2.2.2.2 on GigabitEthernet3/0/2
      Destination/Mask        Nexthop     Cost   Tag     Flags   Sec
        2.2.2.0/24            2.2.2.2        1     0      RA       7
        10.10.10.10/32        2.2.2.2        1     0      RA       7  
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20241

Downloads: 15

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