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 RIPng Route Selection

Adjusting RIPng Route Selection

You can adjust RIPng route selection on a complicated network.

Usage Scenario

To flexibly apply RIPng on a network and meet various requirements of users, you can change RIPng route selection by setting different parameters.

Pre-configuration Tasks

Before adjusting RIPng route selection, complete the following tasks:

Configuration Procedure

Perform one or more of the following configurations as required.

Configuring the Additional Metric on an Interface

The additional metric is the metric (hop count) to be added to the original metric of a RIPng route. You can set additional metrics for received RIPng 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. Run ripng metricin value

    The metric to be added to received routes is set.

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

    Run any of the following commands as required:

    • Configure a basic ACL:
      1. Run ripng metricout { value | { acl-number | acl-name acl-name } value1 } *

      2. Run quit

        Return to the system view.

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

        The basic ACL view is displayed.

      4. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment | source { source-ipv6-address { prefix-length | source-wildcard } | source-ipv6-address/prefix-length | any } | time-range time-name | [ vpn-instance vpn-instance-name | vpn-instance-any ] ] *

        A rule is configured for the basic ACL.

        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 ripng metricout { value | ipv6-prefix ipv6-prefix-name value1 } *

  5. Run commit

    The configuration is submitted.

Follow-up Procedure

Run the ripng metricin command to set an additional metric for received RIPng routes. This command affects the metric of each received route in the routing table.

Run the ripng metricout command to set an additional metric for advertised RIPng routes. However, the metric of the route in the routing table remains unchanged.

If the metric plus the additional metric exceeds 16, 16 is used as the metric.

Setting the Maximum Number of Equal-Cost Routes

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

Procedure

  1. Run interface

    The system view is displayed.

  2. Run ripng [ process-id ]

    The RIPng process is created, and the RIPng view is displayed.

  3. Run maximum load-balancing number

    The maximum number of equal-cost routes is set.

  4. Run commit

    The configuration is submitted.

Verifying the Configuration of RIPng Route Selection

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

Prerequisites

RIPng route selection has been adjusted.

Procedure

  • Run the display ripng [ process-id | vpn-instance vpn-instance-name ] command to check the current operating status and configuration of RIPng.
  • Run the display ripng process-id route [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number [ neighbor-address neighbor-address ] ] command to check RIPng routes.
  • Run the display ripng process-id interface command to check information about RIPng interfaces.

Example

Run the display ripng process-id command to view the operating status and configuration of the RIPng process.

<HUAWEI> display ripng
  Public vpn-instance name :
    RIPng process : 100
       Preference : 100
       Checkzero : Enabled
       Default Cost : 0
       Maximum number of balanced paths : 6
       Update time   : 30 sec   Age time  : 180 sec
       Suppress time : 0 sec    Garbage-Collect time : 120 sec
       Number of periodic updates sent : 0
       Number of trigger updates sent : 1
       Number of routes in database : 1
       Number of interfaces enabled : 1

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

<HUAWEI> display ripng 1 interface verbose
 GigabitEthernet1/0/0
    FE80::A0A:200:1
    State : UP, Protocol : RIPNG, MTU : 1440
    Metricin : 0 , Metricout : 1
    Default Route : Disabled
    Poison Reverse : Disabled
    Split Horizon : Enabled           

Run the display ripng process-id route command to check whether there are routes for load balancing. The following command output shows that there are two equal-cost routes with the same destination address (2001:DB8:C18:1::/64) but different next hops.

<HUAWEI> display ripng 100 route
   Route Flags: A - Aging, S - Suppressed, G - Garbage-collect
 ----------------------------------------------------------------

 Peer FE80::200:5EFF:FE04:B602  on GigabitEthernet6/0/0
 Dest 2001:DB8:C18:1::/64,
     via FE80::200:5EFF:FE04:B602, cost  2, tag 0, A, 34 Sec
 Dest 2001:DB8:C18:2::/64,
     via FE80::200:5EFF:FE04:B602, cost  2, tag 0, A, 34 Sec
 Peer FE80::200:5EFF:FE04:B601  on GigabitEthernet6/0/0
 Dest 2001:DB8:C18:1::/64,
     via FE80::200:5EFF:FE04:B601, cost  2, tag 0, A, 13 Sec
 Dest 2001:DB8:C18:3::/64,
     via FE80::200:5EFF:FE04:B601, cost  2, tag 0, A, 13 Sec
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20653

Downloads: 15

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