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).
Configuring an OSPFv3 NSSA

Configuring an OSPFv3 NSSA

Configuring a non-backbone area on a border of an autonomous system (AS) as a not-so-stubby area (NSSA) can reduce the routing table size and the amount of routing information to be transmitted.

Usage Scenario

An excessive number of entries in a routing table waste network resources and cause high CPU usage. To reduce the number of entries in a routing table, configure a non-backbone area on the border of an AS as a stub area or an NSSA to reduce the amount of routing information to be transmitted. For details on how to configure an OSPFv3 stub area, see Configuring an OSPFv3 Stub Area.

OSPFv3 stub areas cannot import or transmit external routes. If you need to import external routes to an area and prevent these routes from consuming resources, configure the area as an NSSA. NSSAs can import AS external routes and advertise them within the entire AS, without learning external routes from other areas in the AS, which reduces bandwidth and storage resource consumption on the ME device.

An NSSA requires NSSA attributes on all the ME devices in this area.

Pre-configuration Tasks

Before configuring an OSPFv3 NSSA, complete the following tasks:

  • Configure an IP address for each interface to ensure that neighboring routers can use the IP addresses to communicate with each other.
  • Configure basic OSPFv3 functions.

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. Run nssa [ default-route-advertise [ cost cost | type type | tag tag ] * | no-import-route | no-summary | translator-always | translator-interval translator-interval | set-n-bit ] *

    The specified area is configured as an NSSA.

    The usage scenarios of the nssa command are as follows:

    • If default-route-advertise is set, Type 7 LSAs carrying the default route will be generated, regardless of whether the route ::/0 exists in the routing table on an ABR; such LSAs are generated only when the route ::/0 exists in the routing table on an ASBR.

    • If an ASBR also functions as an ABR, setting no-import-route prevents external routes imported using the import-route command from being advertised to the NSSA.
    • To reduce the number of LSAs to be transmitted to the NSSA, set no-summary on an ABR to prevent the ABR from transmitting Summary LSAs (Type 3 LSAs) to the NSSA.
    • If set-n-bit is set, the DD packets sent by the ME device carry the N-bit being 1.

    • If multiple ABRs are deployed in the NSSA, the system automatically selects an ABR (generally the ME device with the largest router ID) as a translator to convert Type 7 LSAs into Type 5 LSAs. You can also set translator-always on an ABR to specify the ABR as an all-the-time translator. To specify two ABRs for load balancing, set translator-always on the two ABRs to specify them as all-the-time translators, which prevents LSA flooding caused by translator role changes.
    • The translator-interval parameter is used to ensure uninterrupted services when translator roles change. The value of interval-value must be greater than the flooding interval.

  5. Run commit

    The configuration is committed.

Checking the Configurations

After configuring an OSPFv3 NSSA, check the configurations.

  • Run the display ospfv3 [ process-id ] routing [ [ ipv6-address prefix-length ] | abr-routes | asbr-routes | ase-routes | inter-routes | intra-routes | nssa-routes ] [ verbose ] command to check the OSPFv3 routing table information.

  • Run the display ospfv3 [ process-id ] lsdb [ area area-id ] [ [ originate-router advertising-router-id | hostname hostname ] | self-originate ] [ { grace | inter-prefix | inter-router | intra-prefix | link | network | router | router-information | nssa } [link-state-id ] ] [ age { min-value min-age-value | max-value max-age-value } * ] command to check the OSPFv3 LSDB information.

# Run the display ospfv3 routing command to view OSPFv3 routing table information. Before an NSSA is configured:

<DeviceC> display ospfv3 routing
Codes : E2 - Type 2 External, E1 - Type 1 External, IA - Inter-Area,
        N - NSSA
Flags : A - Added to URT6

OSPFv3 Process (1)
     Destination                                                         Metric
       Next-hop
     2001:DB8:1::/64                                                          1
       directly connected, Vlanif18, Flags : A
IA   2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif18, Flags : A
IA   2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif14, Flags : A
     2001:DB8:3::/64                                                          1
       directly connected, Vlanif14, Flags : A
IA   2001:DB8:4::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif18, Flags : A
IA   2001:DB8:5::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif14, Flags : A
E2   2001:DB8:6::1/128                                                        1
       via FE80::3A6D:7CFF:FE21:1200, Vlanif18, Flags : A
E2   2001:DB8:6::1/128                                                        1
       via FE80::3A6D:7CFF:FE41:1200, Vlanif14, Flags : A
<DeviceD> display ospfv3 routing
Codes : E2 - Type 2 External, E1 - Type 1 External, IA - Inter-Area,
        N - NSSA
Flags : A - Added to URT6

OSPFv3 Process (1)
     Destination                                                         Metric
       Next-hop
IA   2001:DB8:1::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif13, Flags : A
     2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif13, Flags : A
     2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif11, Flags : A
IA   2001:DB8:3::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif11, Flags : A
     2001:DB8:4::/64                                                          1
       directly connected, Vlanif13, Flags : A
     2001:DB8:5::/64                                                          1
       directly connected, Vlanif11, Flags : A
E2   2001:DB8:7::1/128                                                        1
       via FE80::3A6D:7CFF:FE21:1200, Vlanif13, Flags : A
E2   2001:DB8:7::1/128                                                        1
       via FE80::3A6D:7CFF:FE41:1200, Vlanif11, Flags : A

After an NSSA is configured:

<DeviceC> display ospfv3 routing
Codes : E2 - Type 2 External, E1 - Type 1 External, IA - Inter-Area,
        N - NSSA
Flags : A - Added to URT6

OSPFv3 Process (1)
     Destination                                                         Metric
       Next-hop
     2001:DB8:1::/64                                                          1
       directly connected, Vlanif18, Flags : A
IA   2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif18, Flags : A
IA   2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif14, Flags : A
     2001:DB8:3::/64                                                          1
       directly connected, Vlanif14, Flags : A
IA   2001:DB8:4::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif18, Flags : A
IA   2001:DB8:5::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif14, Flags : A
E2   2001:DB8:6::1/128                                                        1
       via FE80::3A6D:7CFF:FE41:1200, Vlanif14, Flags : A
<DeviceD> display ospfv3 routing
Codes : E2 - Type 2 External, E1 - Type 1 External, IA - Inter-Area,
        N - NSSA
Flags : A - Added to URT6

OSPFv3 Process (1)
     Destination                                                         Metric
       Next-hop
E2   ::/0                                                                     1
N      via FE80::3A6D:7CFF:FE21:1200, Vlanif13, Flags : A
E2   ::/0                                                                     1
N      via FE80::3A6D:7CFF:FE41:1200, Vlanif11, Flags : A
IA   2001:DB8:1::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif13, Flags : A
     2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE21:1200, Vlanif13, Flags : A
     2001:DB8:2::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif11, Flags : A
IA   2001:DB8:3::/64                                                          2
       via FE80::3A6D:7CFF:FE41:1200, Vlanif11, Flags : A
     2001:DB8:4::/64                                                          1
       directly connected, Vlanif13, Flags : A
     2001:DB8:5::/64                                                          1
       directly connected, Vlanif11, Flags : A
By comparing the routing tables before and after an NSSA is configured, you can reach the following conclusions:
  • The NSSA imports AS external routes and advertises them to other OSPFv3 areas.
  • The NSSA does not learn external routes from other areas in the AS.

# Run the display ospfv3 lsdb nssa command to view NSSA LSA information.

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

               NSSA-external-LSA (Area 0.0.0.1)

  LS Age: 118
  LS Type: NSSA-external-LSA
  Link State ID: 0.0.0.1
  Originating Router: 1.1.1.1
  LS Seq Number: 0x80000008
  Retransmit Count: 0
  Checksum: 0x499
  Length: 48
  Flags: (E|-|T)
   Metric Type: 2 (Larger than any link state path)
      Metric: 1
   Prefix: 2001:DB8:6::1/128
    Prefix Options: 8 (-|P|-|-|-)
    Tag: 1

  LS Age: 1273
  LS Type: NSSA-external-LSA
  Link State ID: 0.0.0.0
  Originating Router: 2.2.2.2
  LS Seq Number: 0x8000000d
  Retransmit Count: 0
  Checksum: 0x38e4
  Length: 32    
  Flags: (E|-|T)
   Metric Type: 2 (Larger than any link state path)
      Metric: 1 
   Prefix: ::/0 
    Prefix Options: 0 (-|-|-|-|-)
    Tag: 0      
                
  LS Age: 1521  
  LS Type: NSSA-external-LSA
  Link State ID: 0.0.0.0
  Originating Router: 3.3.3.3
  LS Seq Number: 0x80000009
  Retransmit Count: 0
  Checksum: 0x22fa
  Length: 32    
  Flags: (E|-|T)
   Metric Type: 2 (Larger than any link state path)
      Metric: 1 
   Prefix: ::/0 
    Prefix Options: 0 (-|-|-|-|-)
    Tag: 0 
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20459

Downloads: 15

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