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 OSPFv3 Routing Information

Controlling OSPFv3 Routing Information

This section describes how to control OSPFv3 routing information.

Usage Scenario

Through the configuration in this section, you can control the advertising and receiving of OSPFv3 routing information and configure OSPFv3 to import external routes.

You can control the following types of routes:

  • Routes outside the local OSPFv3 area

    This function can be configured on any NE that runs OSPFv3. For example, you can enable the NE to filter received routes and set the maximum number of equal-cost routes.

  • Routes inside the local OSPFv3 area

    This function can be configured only on ABRs. For example, when an ABR has multiple routes to a destination in the local area, you can configure the ABR to summarize the routes and send only a summary LSA to the backbone area.

Pre-configuration Tasks

Before controlling OSPFv3 routing information, complete the following tasks:

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring OSPFv3 to Import External Routes

Importing the routes discovered by other routing protocols can enrich OSPFv3 routing information.

Context

OSPFv3 is a link state-based routing protocol and cannot filter LSAs to be advertised. Therefore, OSPFv3 must filter routes when importing them so that only the filtered routes can be advertised.

Perform the following steps on the NE that runs OSPFv3:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 view is displayed.

  3. Run default { cost cost | tag tag | type type } *

    The default cost is set for imported routes.

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

    External routes are imported.

    NOTE:

    The import-route command cannot be used to import the default route from another AS.

  5. Run import-route limit limit-number [ threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value ]

    A limit is configured on the number of LSAs generated when an OSPFv3 process imports external routes.

    If OSPFv3 imports a large number of external routes and advertises them to a device with a smaller routing table capacity, the device may restart unexpectedly. To address this problem, run the import-route limit command to configure a limit on the number of LSAs generated when an OSPFv3 process imports external routes.

    Ensure that upper-limit-value is greater than or equal to lower-limit-value.

  6. Run commit

    The configuration is committed.

Configuring OSPFv3 to Advertise the Default Route to the OSPFv3 Area

Configure OSPFv3 to advertise the default route to the OSPFv3 area, and only filtered routes can be advertised.

Context

Perform the following steps on the NE that runs OSPFv3:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 view is displayed.

  3. Run default-route-advertise [ always | cost cost | type type | tag tag | { route-policy route-policy-name | route-filter route-filter-name } ] *

    Default routes are advertised to the OSPFv3 route area.

  4. Run commit

    The configuration is committed.

Configuring OSPFv3 to Filter Received Routes

After receiving Link State Advertisements (LSAs), OSPFv3 determines whether to add the calculated routes to the local routing table based on a filtering policy.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 view is displayed.

  3. Run any of the following commands as required:

    • Configure a basic ACL:
      1. Run filter-policy { acl6-number | acl6-name acl6-name } import

        OSPFv3 is configured to filter received routes.

      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 filter-policy ipv6-prefix ipv6-prefix-name import

      OSPFv3 is configured to filter received routes.

    • Based on the Route-Policy:

      Run filter-policy route-policy route-policy-name import

      OSPFv3 is configured to filter received routes.

    The filter-policy import command is used to filter the routes calculated by OSPFv3. Only the routes that match the filtering rules are added to the routing table and can be advertised. Routes that do not match the filtering rules can be added to the OSPFv3 routing table but not to the routing information base (RIB) and cannot be advertised. Therefore, the LSDB is not affected regardless of whether the received routes match the filtering rules.

  4. Run commit

    The configuration is committed.

Configuring OSPFv3 to Filter the Routes to Be Advertised

After a filtering policy is configured for OSPFv3 routes to be imported, only the routes that match the policy will be advertised.

Context

When OSPFv3 receives LSAs, it can filter the received routes based on a filtering policy before advertising them to neighbors.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 process-id

    The OSPFv3 view is displayed.

  3. (Optional) Run default-route-advertise [ always | cost cost | type type | tag tag | route-policy route-policy-name | route-filter route-filter-name ] *

    Default routes are advertised in the OSPFv3 area.

  4. Run any of the following commands as required:

    • Configure a basic ACL:
      1. Run filter-policy { acl6-number | acl6-name acl6-name } export [ bgp | direct | static | { isis | ospfv3 | ripng } [ process-id ] ]

        The routes imported using the import-route command are filtered, and only the filtered routes can be advertised.

      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 filter-policy ipv6-prefix ipv6-prefix-name export [ bgp | direct | static | { isis | ospfv3 | ripng } [ process-id ] ]

      The routes imported using the import-route command are filtered, and only the filtered routes can be advertised.

    You can specify the parameter protocol [ process-id ] to filter the routes of a certain routing protocol or a certain OSPF process. If protocol [ process-id ] is not specified, OSPFv3 filters all imported routes.

  5. Run commit

    The configuration is committed.

Configuring OSPFv3 to Filter LSAs in an Area

Filtering LSAs in an area can prevent unnecessary LSA transmission. This reduces the size of the LSDB on the neighboring device and speeds up network convergence.

Context

After filtering conditions are set for the incoming or outgoing Type 3 LSAs (Inter-Area-Prefix LSAs) in an area, only the Type 3 LSAs that meet the filtering conditions can be received or advertised.

This function is applicable only to the ABR.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 process view is displayed.

  3. Run area area-id

    The OSPFv3 area view is displayed.

  4. Filter incoming or outgoing Type 3 LSAs in the area.

    • Filter incoming Type 3 LSAs in the area. Run any of the following commands as required:

      • Configure a basic ACL:
        1. Run filter { acl6-number | acl6-name acl6-name } import

          Filter incoming Type 3 LSAs in the area is configured.

        2. Run quit

          Return to the OSPFv3 view.

        3. Run quit

          Return to the system view.

        4. 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.

        5. 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 filter ipv6-prefix ipv6-prefix-name import

        Filter incoming Type 3 LSAs in the area is configured.

      • Based on the Route-Policy:

        Run filter route-policy route-policy-name import

        Filter incoming Type 3 LSAs in the area is configured.

    • Filter outgoing Type 3 LSAs in the area. Run any of the following commands as required:

      • Configure a basic ACL:
        1. Run filter { acl6-number | acl6-name acl6-name } export

          Filter outgoing Type 3 LSAs in the area is configured.

        2. Run quit

          Return to the OSPFv3 view.

        3. Run quit

          Return to the system view.

        4. 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.

        5. 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 filter ipv6-prefix ipv6-prefix-name export

        Filter outgoing Type 3 LSAs in the area is configured.

      • Based on the Route-Policy:

        Run filter route-policy route-policy-name export

        Filter outgoing Type 3 LSAs in the area is configured.

  5. Run commit

    The configuration is committed.

Configuring OSPFv3 Route Summarization

Routes with the same IPv6 prefix can be summarized into one route. On a large-scale OSPFv3 network, route lookup may slow down because of the large size of the routing table. To reduce the routing table size and simplify management, configure route summarization. With route summarization, if a link connected to a device within an IPv6 address range that has been summarized alternates between Up and Down, the link status change is not advertised to the devices beyond the IPv6 address range. This prevents route flapping and improves network stability.

Context

OSPFv3 route summarization is classified as follows:

  • Route summarization on an ABR, which is configured using the abr-summary command. When an ABR transmits routing information to other areas, it generates Type 3 LSAs for each network segment. If contiguous segments exist in this area, run the abr-summary command to summarize these segments into one segment so that the ABR sends only one summarized LSA.

  • Route summarization on an ASBR, which is configured using the asbr-summary command. The ASBR summarizes routes of imported Type 5 LSAs within the summarized address range. If a large number of routes with the same IPv6 prefix are imported, run the asbr-summary command to summarize them into one route.

Procedure

  • Configure route summarization on an ABR.
    1. Run system-view

      The system view is displayed.

    2. Run ospfv3 [ process-id ]

      The OSPFv3 view is displayed.

    3. Run area area-id

      The OSPFv3 area view is displayed.

    4. Run abr-summary ipv6-address prefix-length [ not-advertise | cost cost | hold-max-cost interval ] *

      Route summarization is configured on an ABR.

      • The not-advertise parameter prevents the summarized route in the specified network segment from being advertised.

      • The cost cost parameter sets a cost for a summarized route. By default, the largest cost of the specific routes for summarization is used as the cost of the summarized route.

    5. Run commit

      The configuration is committed.

  • Configure route summarization on an ASBR.
    1. Run system-view

      The system view is displayed.

    2. Run ospfv3 [ process-id ]

      The OSPFv3 view is displayed.

    3. Run asbr-summary prefix-length [ not-advertise | tag tag | cost cost | distribute-delay interval ] *

      Route summarization is configured on an ASBR.

      • The cost cost parameter sets a cost for a summarized route. By default, the largest cost of the specific routes for summarization is used as the cost of the summarized route.

      • The tag tag parameter sets a tag to control summarized route advertisement.

      • The not-advertise parameter prevents the summarized route with the specified IPv6 prefix or prefix length from being advertised.

      • The distribute-delay interval parameter sets a delay in advertising summarized routes, which ensures that the summarized routes advertised each time contain more valid routes and prevents incorrect routing information in case of network flapping.

    4. Run commit

      The configuration is committed.

Verifying the Configuration of OSPFv3 Routing Information Control

After controlling OSPFv3 routing information, verify the OSPFv3 LSDB.

Prerequisites

OSPFv3 routing information has been controlled.

Procedure

  • Run the display ospfv3 [ process-id ] lsdb command to view the OSPFv3 LSDB.
  • Run either of the following commands to check OSPFv3 route information:

    • Run the display ospfv3 [ process-id ] abr-summary-list [ ipv6-address prefix-length ] command to check information about the summarized routes on an ABR.

    • Run the display ospfv3 [ process-id ] asbr-summary [ ipv6-address prefix-length ] [ verbose ] command to check information about the summarized routes on an ASBR.

Example

Run the display ospfv3 lsdb command to view the Link State ID in the header of each LSA and information about the NEs that generate or advertise the LSAs.

<HUAWEI> display ospfv3 lsdb
               OSPFv3 Router with ID (2.2.2.2) (Process 1)

               Inter-Area-Prefix-LSA (Area 0.0.0.0)

Link State ID   Origin Router    Age   Seq#       CkSum
0.0.0.1         1.1.1.1          0238  0x80000003 0xbfb1
0.0.0.2         1.1.1.1          0238  0x80000003 0xcfe8
0.0.0.3         1.1.1.1          0238  0x80000003 0xff6b
0.0.0.4         1.1.1.1          0025  0x80000001 0x445e
0.0.0.1         2.2.2.2          0121  0x80000003 0xef7a
0.0.0.2         2.2.2.2          0121  0x80000003 0xb103
0.0.0.3         2.2.2.2          0121  0x80000003 0x93d6


               Inter-Area-Router-LSA (Area 0.0.0.0)

Link State ID   Origin Router    Age   Seq#       CkSum 
1.1.1.1         2.2.2.2          0028  0x80000001 0xe530


                       AS-External-LSA

Link State ID   Origin Router    Age   Seq#       CkSum  Type
0.0.0.1         1.1.1.1          0005  0x80000001 0xac60 E2
Run the display ospfv3 abr-summary-list command to view information about the summarized routes on an ABR.
<HUAWEI> display ospfv3 abr-summary-list

OSPFv3 Process (1)
Area ID  :  0.0.0.1
 Prefix                                 Prefix-Len   Matched          Status        
 2001:DB8::                             32           1 [Active]       Advertised 
Run the display ospfv3 asbr-summary command to view information about the summarized routes on an ASBR.
<HUAWEI> display ospfv3 asbr-summary verbose

 OSPFv3 Process (1)
 Total summary address count: 1

                 Summary Address

 Prefix         : 2001::
 Prefix length  : 16
 Tag            : 1 (Not Configured)
 Status         : Advertised
 Cost           : 2 (Not Configured)
 Delay          : 0 (Not Configured)
 Type           : 2 (Larger than any link state path)

 The Count of Route is: 3

 Destination                             Mask       Protocol   Proc       Type       Metric    
 2001:DB8:2::1                           128        Static     0          2          1         
 2001:DB8:3::1                           128        Static     0          2          1         
 2001:DB8:4::1                           128        Static     0          2          1        
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 34182

Downloads: 49

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