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 Stub Area

Configuring an OSPFv3 Stub Area

Configuring a non-backbone area as a stub area can reduce routing entries in the area in an AS does not transmit routes learned from other areas in the AS or AS external routes. This reduces bandwidth and storage resource consumption.

Applicable Environment

The number of LSAs can be reduced by partitioning an AS into different areas. To reduce the number of entries in the routing table and the number of LSAs to be transmitted in a non-backbone area, configure the non-backbone area on the border of the AS as a stub area.

Configuring a stub area is optional. A stub area generally resides on the border of an AS. For example, a non-backbone area with only one ABR can be configured as a stub area. In a stub area, the number of entries in the routing table and the amount of routing information to be transmitted greatly decrease.

Note the following points when configuring a stub area:

  • The backbone area (Area 0) cannot be configured as a stub area.
  • If an area needs to be configured as a stub area, all the ME devices in this area must be configured with stub attributes using the stub command.
  • An ASBR cannot exist in a stub area. External routes are not transmitted in the stub area.

Pre-configuration Tasks

Before configuring a stub area, complete the following tasks:

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 stub

    The specified area is configured as a stub area.

    NOTE:
    • All ME devices in a stub area must be configured with stub attributes using the stub command.
    • Configuring or deleting stub attributes will update routing information in the area. Stub attributes can be deleted or configured again only after the routing update is complete.

  5. (Optional) Run stub [ no-summary ]

    The ABR is prevented from sending Type 3 LSAs to the stub area.

  6. (Optional) Run default-cost cost

    The cost of the default route to the stub area is set.

    To ensure the reachability of AS external routes, the ABR in the stub area generates a default route and advertises the route to the non-ABR ME devices in the stub area.

  7. Run commit

    The configuration is committed.

Checking the Configurations

Run the display ospfv3 command, and you can view the OSPFv3 LSDB, including the types of LSA and link state IDs. For example:

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

               Link-LSA (Interface GigabitEthernet1/0/0)

Link State ID   Origin Router    Age   Seq#       CkSum      Prefix
0.0.0.4         1.1.1.1          1707  0x800000bd 0xd284          1
0.0.0.4         2.2.2.2          618   0x800000bd 0x4b20          1


               Router-Information-LSA (Interface GigabitEthernet1/0/0)

Link State ID   Origin Router    Age   Seq#       CkSum
0.0.0.0        1.1.1.1           103   0x80000001 0xa28c
0.0.0.0        2.2.2.2           733   0x80000001 0xbacb


               Router-LSA (Area 0.0.0.0)

Link State ID   Origin Router    Age   Seq#       CkSum    Link
0.0.0.1         1.1.1.1          1657  0x800000c3 0xe65d      1
0.0.0.1         2.2.2.2          1653  0x800000c1 0xcc75      1


               Network-LSA (Area 0.0.0.0)

Link State ID   Origin Router    Age   Seq#       CkSum 
0.0.0.4         2.2.2.2          1653  0x80000062 0x8f20


               Inter-Area-Prefix-LSA (Area 0.0.0.0)

Link State ID   Origin Router    Age   Seq#       CkSum 
0.0.0.2         1.1.1.1          1707  0x8000009b 0x8388
0.0.0.2         2.2.2.2          733   0x8000009b 0x65a2


               Inter-Area-Router-LSA (Area 0.0.0.0)

Link State ID   Origin Router    Age   Seq#       CkSum 
2.2.2.2         1.1.1.1          1614  0x80000062 0x456b
1.1.1.1         2.2.2.2          1614  0x80000062 0x2391


               Intra-Area-Prefix-LSA (Area 0.0.0.0)

Link State ID   Origin Router    Age   Seq#       CkSum   Prefix Reference
0.0.0.1         2.2.2.2          1653  0x80000062 0x7fce       1 Network-LSA


               Router-Information-LSA (Area 0.0.0.1)

Link State ID   Origin Router    Age   Seq#       CkSum
0.0.0.0         2.2.2.2          103   0x80000002 0x8bc0

               Router-LSA (Area 0.0.0.1)

Link State ID   Origin Router    Age   Seq#       CkSum    Link
0.0.0.1         1.1.1.1          1614  0x800000a1 0x741       1
0.0.0.1         2.2.2.2          1615  0x8000009f 0xec59      1

               AS-External-LSA

Link State ID   Origin Router    Age   Seq#       CkSum  Type
0.0.0.1         11.11.11.111     6     80000001   0x9943 E2

When Router is in a common area, there are AS external routes in the routing table. After the area where Router resides is configured as a stub area, AS external routes are invisible.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20758

Downloads: 15

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