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

Configuration Guide - IP Routing 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 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).
Controlling RIPng Routing Information

Controlling RIPng Routing Information

In most cases, multiple protocols run on the same network. Therefore, you need to control routing information of every protocol to meet different networking requirements.

Applicable Environment

To meet the requirements of complex networking, accurately control the sending and receiving of RIPng routing information.

Pre-configuration Tasks

Before configuring a NE to control RIPng routing information, complete the following tasks:

Configuration Procedure

Perform one or more of the following configurations as required.

Configuring RIPng to Import External Routes

RIPng can import routing information from other RIPng processes or routing protocols to enrich the RIPng routing table.

Context

On a large-scale network, multiple routing protocols may be configured for devices in different areas. In this situation, configure RIPng to import routes from other processes or routing protocols to implement inter-area communication.

If RIPng needs to advertise routing information of other RIPbg processes or other routing protocols (such as direct, static, RIPng, OSPFv3, IS-IS, or BGP), you can specify protocol to filter routing information. If protocol is not specified, routing information to be advertised can be filtered, including the imported routes and local RIPng routes (functioning as direct routes).

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ripng [ process-id ]

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

  3. (Optional) Run default-cost cost

    The default cost is set for the imported routes.

    If no cost is specified when external routes are imported, the default cost 0 is used.

  4. Run import-route { static | direct | bgp [ permit-ibgp ] | { isis | ospfv3 | ripng } [ process-id ] } [ [ cost cost | inherit-cost ] | { route-policy route-policy-name | route-filter route-filter-name } ] *

    External routes are imported.

  5. Run commit

    The configuration is submitted.

Configuring RIPng to Filter the Received Routes

You can configure a router to selectively receive routes.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ripng [ process-id ]

    The RIPng view is displayed.

  3. Run quitacl ipv6 { name basic-acl6-name { basic | [ basic ] number basic-acl6-number } | [ number ] basic-acl6-number } [ match-order { config | auto } ]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 ] ] *

    • filter-policy { acl6-number | acl6-name acl6-name } import

      The imported routes are filtered based on the ACL.

      1. Run

        Return to the system view.

      2. Run

        The basic ACL view is displayed.

      3. Run

        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.

    • filter-policy ipv6-prefix ipv6-prefix-name import

      The imported routes are filtered based on the prefix list.

    • filter-policy route-policy route-policy-name import

      The imported routes are filtered based on the route-policy.

    RIPng can filter the received routes based on an IPv6 ACL, route-policy or an IPv6 prefix list. Only the routes that meet the match conditions are added in the RIPng routing table.

  4. Run commit

    The configuration is submitted.

Configuring RIPng to Filter the Routes to be Sent

You can configure RIPng to filter the routes to be sent.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ripng [ process-id ]

    The RIPng view is displayed.

  3. (Optional) Run quitacl ipv6 { name basic-acl6-name { basic | [ basic ] number basic-acl6-number } | [ number ] basic-acl6-number } [ match-order { config | auto } ]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 ] ] *

    • filter-policy { acl6-number | acl6-name acl6-name } export [ protocol [ process-id ] ]

      RIPng is configured to filter the routes based on the ACL.

      1. Run

        Return to the system view.

      2. Run

        The basic ACL view is displayed.

      3. Run

        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.

    • filter-policy ipv6-prefix ipv6-prefix-name export [ protocol [ process-id ] ]

      RIPng is configured to filter the routes based on the prefix list.

    • filter-policy route-policy route-policy-name export [ protocol [ process-id ] ]

      RIPng is configured to filter the routes based on the route policy.

    RIPng can filter the routes to be sent based on an IPv6 ACL, route-policy or an IPv6 prefix list. Only the routes that meet the match conditions are advertised to neighbors. If protocol is not specified in the command, all the routing information to be advertised will be filtered, including the imported routes and local RIPng routes (directly connected routes).

  4. Run commit

    The configuration is submitted.

Configuring RIPng to Advertise the Default Routes

There are two methods of advertising RIPng default routes. You can configure a router to advertise RIPng default routes as required. Alternatively, you can specify the cost of the default routes to be advertised.

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 default-route { only | originate } [ cost cost-value | tag tag-value ] *

    RIPng is configured to advertise default routes.

    Specify either of the following parameters as required:

    • only: advertises only IPv6 default routes (::/0) and suppress the advertisement of other routes.

    • originate: advertises IPv6 default routes (::/0) without affecting the advertisement of other routes.

  4. Run commit

    The configuration is submitted.

Follow-up Procedure

RIPng default routes are advertised in Update packets through the specified interface, regardless of whether these routes exist in the IPv6 routing table.

Configuring RIPng Route Summarization

Configuring RIPng route summarization reduces the routing table size and prevents route flapping.

Context

The RIPng routing table of a device on a medium or large RIPng network contains a large number of routes. Storing the routes consumes a large number of memory resources, and transmitting and processing these routes consume lots of network resources. To address this issue, configure RIPng route summarization.

Route summarization is the process of summarizing routes that share the same next hop but are destined for different subnets of a network segment into one route. The system then advertises the summarized route to other network segments. Route summarization on a large-scale network reduces the number of routes in a routing table and minimizes system resource consumption. In addition, if a specific link frequently alternates between Up and Down, the link status changes will not be advertised to devices that are located beyond the summarized route network segment, which prevents route flapping and improves network stability.

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 summary-address ipv6-address prefix-length [ avoid-feedback ]

    RIPng route summarization is configured.

    NOTE:

    After RIPng route summarization is configured on a device, the local routing table still contains all specific routes before the summarization, while the routing tables of neighbors of the local device contain only the summarized route.

    The cost of the summarized route is the smallest cost of the routes that have been summarized.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of RIPng Routing Information Control

After controlling RIPng routing information, verify all activated routes in the RIPng database.

Prerequisites

Configurations have been performed to control RIPng routing information.

Procedure

  • Run the display ripng process-id database [ verbose ] [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number [ neighbor-address neighbor-address ] ] command to check routes in the RIPng database.

Example

Run the display ripng process-id database command to view the default routes and imported routes.

<HUAWEI> display ripng 100 database
   2001:DB8:8::8/128,
        cost 0, Imported
   2001:DB8:10::/64,
       via FE80::2E0:E6FF:FE1B:8242, cost 1
   2001:DB8:10::/64,
       via FE80::2E0:E6FF:FE1B:8242, cost 1
   2001:DB8:10::/64,
       via FE80::2E0:E6FF:FE1B:8142, cost 1
   2001:DB8:10::/64,
       via FE80::2E0:E6FF:FE1B:8142, cost 1
   2001:DB8:12::/64,
        cost 0, RIPng-interface
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 38282

Downloads: 57

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