0% found this document useful (0 votes)

143 views68 pages

01 Advanced IGP Features

Uploaded by

guido.martini

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

143 views68 pages

01 Advanced IGP Features

Uploaded by

guido.martini

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 68

Advanced IGP Features

Page 1 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Foreword
⚫ Both Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (IS-
IS) are link-state Interior Gateway Protocols (IGPs). Routers that run them synchronize link
state databases (LSDBs) and use the shortest path first (SPF) algorithm to calculate optimal
routes.
⚫ In response to network topology changes, OSPF and IS-IS support multiple fast convergence
and protection mechanisms, which minimize traffic loss caused by network faults.
⚫ To control the size of a routing table, OSPF and IS-IS support route selection and routing
information control.
⚫ This course describes the advanced features of OSPF and IS-IS, including fast convergence
and route control.

Page 2 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
⚫ On completion of this course, you will be able to:
 Describe various fast convergence techniques of OSPF and IS-IS.
 Configure OSPF and IS-IS equal-cost routes.
 Configure OSPF and IS-IS to advertise default routes.
 Describe the application scenarios of OSPF and IS-IS multi-process.
 Describe the application scenarios of OSPF forwarding address (FA).
 Describe the implementation of IS-IS LSP fragment extension.

Page 3 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Contents
1. OSPF Fast Convergence

2. OSPF Route Control

3. Other OSPF Features

4. Advanced IS-IS Features

Page 4 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Intelligent BFD
Overview PRC FRR
Timer Association

Overview of OSPF Fast Convergence

⚫ OSPF fast convergence is an extended feature of OSPF to speed up route convergence. It
features partial route calculation (PRC) and the intelligent timer.
⚫ In addition, OSPF supports fast convergence upon fault rectification. For example, OSPF IP
fast reroute (FRR) can be used to implement fast traffic switchover to a backup link, and
OSPF can also be associated with BFD to implement fast fault detection.

Page 5 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Intelligent BFD
Overview PRC FRR
Timer Association

PRC
⚫ PRC only calculates routes that have been changed on a network.
⚫ PRC does not calculate nodes. Instead, it updates routes based on the shortest path tree (SPT)
calculated using the SPF algorithm.
R1 (root) • Scenario description:
▫ OSPF runs on a network. The figure shows the SPT with R1 as the root after network
convergence. When R1 accesses R5, traffic is sent to the destination based on [outbound
interface of R1's downlink, IP address of R3's uplink interface].
R2 R3
▫ OSPF is enabled on Loopback0 of R5. This means that a new network segment is added to
the OSPF network.
• PRC:
R4 R5 ▫ R5 floods a new LSA on the entire network.
▫ After receiving the LSA, R1 creates a new route that inherits the original path and next
hop used when R1 accesses R5. In this case, the SPT remains unchanged, and only a leaf is
added to R5.
Loopback0: A directly connected ▫ Therefore, when R1 accesses Loopback0 of R5, traffic is sent to the destination based on
network segment is added. [outbound interface of R1's downlink, IP address of R3's uplink interface].
In route calculation, a node represents a • Benefits:
router, and a leaf represents a route. PRC
processes only the changed leaf information. ▫ PRC focuses only on routes that are changed due to the addition of network segments to
an OSPF network, thereby speeding up route calculation.

• Note: On Huawei devices, OSPF PRC is enabled by default.

Intelligent BFD
Overview PRC FRR
Timer Association

Intelligent Timer
⚫ The intelligent timer is used for SPF calculation and LSA generation.
⚫ It can quickly respond to a small number of external incidents and prevent excessive CPU
consumption.

Controlling LSA Generation and Reception Controlling Route Calculation

• To prevent network connections or frequent route flapping • When a network changes, the OSPF LSDB changes, and
from consuming excessive device resources, OSPF complies the shortest path needs to be recalculated. If a network
with the following rules: changes frequently, the shortest path is calculated
▫ After an LSA is generated, it cannot be generated accordingly, which results in excessive consumption of
again within 1s. The interval for updating LSAs is 5s. system resources and compromises device efficiency.

▫ The interval for receiving LSAs is 1s. • You can configure the intelligent timer to set a proper
interval for SPF calculation in order to prevent excessive
• On a stable network where routes need to be fast consumption of a router's memory and bandwidth
converged, the intelligent timer can be used to set the resources.
interval for updating LSAs to 0s in order to cancel this
interval. In this manner, topology or route changes can be
immediately advertised to the network through LSAs or be
immediately detected, thereby speeding up route
convergence on the network.

• If the interval for triggering route calculation is long, the network convergence speed is
affected.

• The first timeout period of the intelligent timer is fixed. Before the intelligent timer
expires, if an event that triggers the timer occurs, the next timeout period of the
intelligent timer becomes longer.
Intelligent BFD
Overview PRC FRR
Timer Association

Basic Intelligent Timer

Configuration Commands (1)
1. Set an interval for updating OSPF LSAs.

[Huawei-ospf-1] lsa-originate-interval { 0 | { intelligent-timer max-interval start-interval hold-

interval | other-type interval } * }

By default, the intelligent timer is enabled; the maximum interval, initial interval, and hold interval at which
LSAs are updated are 5000 ms, 500 ms, and 1000 ms, respectively.

After the intelligent timer is used:

1. The initial interval for updating LSAs is specified by start-interval.

2. The interval at which LSAs are updated for the nth (n ≥ 2) time equals hold-interval x 2(n – 2).

3. When the interval specified by hold-interval x 2(n – 2) reaches the maximum interval specified by max-interval, OSPF
updates LSAs at the maximum interval for three consecutive times. Then, OSPF returns to the first step and updates
LSAs at the initial interval specified by start-interval.

• Command: [Huawei-ospf] lsa-originate-interval { 0 | { intelligent-timer max-interval

start-interval hold-interval | other-type interval } }
▫ 0: sets the interval for updating LSAs to 0s, that is, cancels the interval of 5s for
updating LSAs.

▫ intelligent-timer: uses the intelligent timer to set the update interval for router-
LSAs and network-LSAs.

▫ max-interval: specifies the maximum interval for updating OSPF LSAs. The value
is an integer ranging from 1 to 120000, in milliseconds. The default value is 5000.

▫ start-interval: specifies the initial interval for updating OSPF LSAs. The value is an
integer ranging from 0 to 60000, in milliseconds. The default value is 500.

▫ hold-interval: specifies the hold interval for updating OSPF LSAs. The value is an
integer ranging from 1 to 60000, in milliseconds. The default value is 1000.

▫ other-type: sets an update interval for OSPF LSAs except router-LSAs and
network-LSAs.

▫ interval: specifies the interval for updating LSAs. The value is an integer ranging
from 0 to 10, in seconds. The default value is 5.
Intelligent BFD
Overview PRC FRR
Timer Association

Basic Intelligent Timer

Configuration Commands (2)
2. Set an interval for receiving OSPF LSAs.

[Huawei-ospf-1] lsa-arrival-interval { interval | intelligent-timer max-interval start-interval hold-interval }

By default, the intelligent timer is enabled; the maximum interval, initial interval, and hold interval at which
LSAs are received are 1000 ms, 500 ms, and 500 ms, respectively.

After the intelligent timer is used:

1. The initial interval for receiving LSAs is specified by start-interval.

2. The interval at which LSAs are received for the nth (n ≥ 2) time equals hold-interval x 2(n – 2).

3. When the interval specified by hold-interval x 2(n – 2) reaches the maximum interval specified by max-interval, OSPF
receives LSAs at the maximum interval for three consecutive times. Then, OSPF returns to the first step and receives
LSAs at the initial interval specified by start-interval.

• Command: [Huawei-ospf-1] lsa-arrival-interval { interval | intelligent-timer max-

interval start-interval hold-interval }
▫ interval: specifies the interval for receiving LSAs. The value is an integer ranging
from 0 to 10000, in milliseconds.

▫ intelligent-timer: uses the intelligent timer to set the receive interval for LSAs.

▫ max-interval: specifies the maximum interval for receiving OSPF LSAs. The value
is an integer ranging from 1 to 120000, in milliseconds. The default value is 1000.

▫ start-interval: specifies the initial interval for receiving OSPF LSAs. The value is an
integer ranging from 0 to 60000, in milliseconds. The default value is 500.

▫ hold-interval: specifies the hold interval for receiving OSPF LSAs. The value is an
integer ranging from 1 to 60000, in milliseconds. The default value is 500.
Intelligent BFD
Overview PRC FRR
Timer Association

Basic Intelligent Timer

Configuration Commands (3)
3. Set an interval for OSPF route calculation.
[Huawei-ospf-1] spf-schedule-interval { interval1 | intelligent-timer max-interval start-interval hold-
interval | millisecond interval2 }
By default, the intelligent timer is enabled; the maximum interval, initial interval, and hold interval for SPF
calculation are 10000 ms, 500 ms, and 1000 ms, respectively.

After the intelligent timer is used, the interval for SPF calculation is as follows:
1. The initial interval for SPF calculation is specified by start-interval.

2. The interval for SPF calculation for the nth (n ≥ 2) time equals hold-interval x 2(n – 2).

3. When the interval specified by hold-interval x 2(n – 2)

reaches the maximum interval specified by max-interval, OSPF
performs SPF calculation at the maximum interval for three consecutive times. Then, OSPF returns to the first step
and performs SPF calculation at the initial interval specified by start-interval.

• Command: [Huawei-ospf-1] spf-schedule-interval { interval1 | intelligent-timer max-

interval start-interval hold-interval | millisecond interval2 }
▫ interval1: specifies an interval for OSPF SPF calculation. The value is an integer
ranging from 1 to 10, in seconds.

▫ intelligent-timer: uses the intelligent timer to set the interval for OSPF SPF
calculation.

▫ max-interval: specifies the maximum interval for OSPF SPF calculation. The value
is an integer ranging from 1 to 120000, in milliseconds. The default value is
10000.

▫ start-interval: specifies the initial interval for OSPF SPF calculation. The value is
an integer ranging from 1 to 60000, in milliseconds. The default value is 500.

▫ hold-interval: specifies the hold interval for OSPF SPF calculation. The value is an
integer ranging from 1 to 60000, in milliseconds. The default value is 1000.

▫ millisecond interval2: specifies an interval for OSPF SPF calculation. The value is
an integer ranging from 1 to 10000, in milliseconds.
Intelligent BFD
Overview PRC FRR
Timer Association

OSPF IP FRR
⚫ OSPF IP fast reroute (FRR) is a dynamic IP FRR technology that uses the loop-free alternate (LFA)
algorithm to pre-calculate a backup path and saves it in the forwarding table. If the primary link fails,
traffic is rapidly switched to the backup link, ensuring traffic continuity and achieving traffic protection.
OSPF IP FRR can reduce the fault recovery time to less than 50 ms.
⚫ The LFA algorithm calculates a backup link based on the following principles:
 A device uses the SPF algorithm to calculate shortest paths to the destination, with each neighbor that provides
a backup link as a root node. The device then uses the inequality to calculate a loop-free backup link with the
minimum cost.

Page 11 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Intelligent BFD
Overview PRC FRR
Timer Association

Networking of OSPF IP FRR

Distance_opt (X, Y)
OSPF IP FRR protects traffic against either a link failure or a node-and-link failure. indicates the shortest path
from node X to node Y.

Link protection Node-and-link protection

Link protection inequality: Link protection inequality:
Distance_opt (N, D) < Distance_opt (N, S) + Distance_opt (S, D) Distance_opt (N, D) < Distance_opt (N, S) + Distance_opt (S, D)
This ensures that the traffic from node N to node D does not pass through node Node protection inequality:
S. That is, this ensures that no loop occurs.
Distance_opt (N, D) < Distance_opt (N, E) + Distance_opt (E, D)
S R1 D
Cost = 10 Cost = 5 This ensures that the traffic from node N to node D does not pass through nodes S
and E. That is, this ensures that no loop occurs.

S E D
Cost = 10 Cost = 5
S: source node
D: destination node
N: node along the
backup link
N S: source node
D: destination node
Traffic flows from node S to node D. The link cost satisfies the link N: node along the
protection inequality. If the primary link fails, node S switches the traffic backup link
N E: faulty node
to the backup link. This ensures that the traffic interruption time is less
than 50 ms. Node-and-link protection must meet the preceding two inequalities.

• Node-and-link protection:

▫ As shown in the right figure, traffic flows from node S to node D. The link cost
satisfies the node-and-link protection inequality. If the primary link fails, node S
switches the traffic to the backup link. This ensures that the traffic interruption
time is less than 50 ms.

• OSPF IP FRR protects traffic against either a link failure or a node-and-link failure.

▫ Link protection takes effect when the traffic to be protected flows along a
specified link.

▫ Node-and-link protection takes effect when the traffic to be protected flows

along a specified device. Node-and-link protection takes precedence over link
protection.
Intelligent BFD
Overview PRC FRR
Timer Association

Basic OSPF IP FRR Configuration Commands

1. Enable OSPF IP FRR.

[Huawei-ospf-1] frr
[Huawei-ospf-1-frr]

Create OSPF FRR and enter its view.

[Huawei-ospf-1-frr] loop-free-alternate

After OSPF IP FRR is enabled, the device uses the LFA algorithm to calculate the next hop and outbound
interface for a backup link.

2. (Optional) Disable OSPF IP FRR on an interface.

[Huawei-GigabitEthernet0/0/1] ospf frr block

OSPF IP FRR can be disabled on an interface of a specific device that is running important services and resides
on an FRR backup link. This setting prevents the device connected to this interface from being a part of a
backup link and being burdened after FRR switches traffic to the backup link.

Page 13 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Intelligent BFD
Overview PRC FRR
Timer Association

Example for Configuring OSPF IP FRR

If the link between R1 and R3 fails, traffic forwarded by R1 can be
R1 R3 R4 quickly switched to the backup link and forwarded by R2.
Cost = 10 Cost = 5
GE0/0/0 GE0/0/1 1. Assign an IP address to each interface and configure OSPF on
each device. (The configuration details are not provided here.)
2. Configure an OSPF cost for each device. The following example
uses the command output on R1.
OSPF
area 0 [R1] interface GigabitEthernet 0/0/0
R2 [R1-GigabitEthernet 0/0/0] ospf cost 10
[R1-GigabitEthernet 0/0/0] quit
Device Router ID Interface IP Address
[R1] interface GigabitEthernet 0/0/1
GE0/0/0 10.1.13.1/24 [R1-GigabitEthernet 0/0/1] ospf cost 10
R1 10.1.1.1 [R1-GigabitEthernet 0/0/1] quit
GE0/0/1 10.1.12.1/24
GE0/0/1 10.1.12.2/24 3. Enable OSPF IP FRR on R1.
R2 10.1.2.2
GE0/0/2 10.1.23.2/24 [R1] ospf
GE0/0/0 10.1.13.3/24 [R1-ospf-1] frr
[R1-ospf-1-frr] loop-free-alternate
R3 10.1.3.3 GE0/0/1 10.1.34.3/24 [R1-ospf-1-frr] quit
GE0/0/2 10.1.23.3/24 [R1-ospf-1] quit

R4 10.1.4.4 GE0/0/1 10.1.34.4/24

The cost configurations of R2, R3, and R4
are similar to the configuration of R1.

Page 14 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Intelligent BFD
Overview PRC FRR
Timer Association

Checking the OSPF IP FRR Configuration

R1 R3 R4 If the link between R1 and R3 fails, traffic forwarded by R1 can

Cost = 10 Cost = 5 be quickly switched to the backup link and forwarded by R2.
GE0/0/0 GE0/0/1

Check information about the route from R1 to GE0/0/1 of R4.

OSPF [R1]display ospf routing 10.1.34.4

area 0 OSPF Process 1 with Router ID 10.1.1.1
R2
Destination : 10.1.34.0/24
Device Router ID Interface IP Address AdverRouter : 10.1.4.4 Area : 0.0.0.0
Cost : 15 Type : Transit
GE0/0/0 10.1.13.1/24
R1 10.1.1.1 NextHop : 10.1.13.3 Interface : GigabitEthernet0/0/0
GE0/0/1 10.1.12.1/24 Priority : Low Age : 00h01m59s
GE0/0/1 10.1.12.2/24 Backup Nexthop : 10.1.12.2 Backup Interface:GigabitEthernet0/0/1
R2 10.1.2.2 Backup Type : LFA LINK
GE0/0/2 10.1.23.2/24
GE0/0/0 10.1.13.3/24
You can find that OSPF generates
R3 10.1.3.3 GE0/0/1 10.1.34.3/24
a backup link after OSPF IP FRR is
GE0/0/2 10.1.23.3/24 enabled on R1.
R4 10.1.4.4 GE0/0/1 10.1.34.4/24

Page 15 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Intelligent BFD
Overview PRC FRR
Timer Association

BFD for OSPF

⚫ A link fault or a topology change causes devices to recalculate routes. Fast and efficient routing
protocol convergence is necessary to improve network availability.
⚫ BFD for OSPF associates BFD with OSPF. If a fault occurs on the link between a device and its neighbor,
BFD can rapidly detect the link fault to speed up OSPF's response to network topology changes.

BFD The working principle of BFD for OSPF is as follows:

R1 S1 R2
▫ OSPF neighbor relationships are established between R1, R2, and R3.
When the neighbor relationships enter the Full state, BFD is
instructed to set up a BFD session.

▫ If a fault occurs on the link between R1 and R2, BFD detects the
fault and notifies R1. R1 processes the BFD session down event and
R3 recalculates the route. The new path is R1-R3-R2.
OSPF

• OSPF periodically sends Hello packets to neighbors to detect faults. It takes more than
1s to detect a fault. By default, when the OSPF Dead timer expires, the neighbor is
considered invalid. The default value of the OSPF Dead timer is 40s. With the
development of technologies, voice, video, and video on demand (VOD) services are
widely used. These services are sensitive to the packet loss rate and delay. When the
traffic rate reaches gigabit per second (Gbit/s), long-time fault detection causes a large
number of packets to be lost. This cannot meet high reliability requirements of the
carrier-class network.

• BFD for OSPF is introduced to resolve this problem. After BFD for OSPF is configured in
a specified process or on a specified interface, the link status can be rapidly detected
and fault detection can be completed in milliseconds. This speeds up OSPF convergence
when the link status changes.
Intelligent BFD
Overview PRC FRR
Timer Association

Basic BFD for OSPF Configuration Commands

1. Configure BFD for OSPF.

[Huawei-ospf-1] bfd all-interfaces enable

Enable BFD in an OSPF process.

[Huawei-ospf-1] bfd all-interfaces { min-rx-interval receive-interval | min-tx-interval transmit-interval |

detect-multiplier multiplier-value | frr-binding }

Configure BFD session parameters.

2. Configure BFD on a specified interface.

[Huawei-GigabitEthernet0/0/1] ospf bfd enable

Enable BFD on an OSPF interface.

[Huawei-GigabitEthernet0/0/1] ospf bfd { min-rx-interval receive-interval | min-tx-interval transmit-interval |

detect-multiplier multiplier-value | frr-binding }

Configure BFD session parameters on the OSPF interface.

• Prerequisites:
▫ Before using BFD to quickly detect link faults, run the bfd command in the
system view to enable BFD globally.
• The BFD configuration on an interface takes precedence over that in a process. If BFD
is enabled on an interface, the BFD parameters on the interface are used to establish
BFD sessions.
• OSPF IP FRR can be associated with BFD.
▫ During the OSPF IP FRR configuration, the underlying layer needs to fast respond
to a link status change so that traffic can be switched to the backup link
immediately.
▫ OSPF IP FRR and BFD can be bound to rapidly detect link faults. This ensures that
traffic is rapidly switched to the backup link in the case of link failures.
• Command: [Huawei-ospf-1] bfd all-interfaces { min-rx-interval receive-
interval | min-tx-interval transmit-interval | detect-multiplier multiplier-value | frr-
binding }
▫ min-rx-interval receive-interval: specifies an expected minimum interval for
receiving BFD packets from the peer. The value is an integer ranging from 10 to
2000, in milliseconds. The default value is 1000.
▫ min-tx-interval transmit-interval: specifies a minimum interval for sending BFD
packets to the peer. The value is an integer ranging from 10 to 2000, in
milliseconds. The default value is 1000.
▫ detect-multiplier multiplier-value: specifies a local detection multiplier. The
value is an integer ranging from 3 to 50. The default value is 3.
▫ frr-binding: binds the BFD session status to the link status of an interface. If a
BFD session goes down, the physical link of the bound interface also goes down,
triggering traffic to be switched to the backup link.
Contents
1. OSPF fast convergence

2. OSPF Route Control

3. Other OSPF Features

4. Advanced IS-IS Features

Page 18 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Overview of OSPF Route Control

OSPF route control includes:
 Adjusting the OSPF interface cost
 Setting the maximum number of equal-cost routes for load balancing
 Importing external routes
 Configuring route summarization
 Configuring default route advertisement
 Configuring filter-policies
 Configuring OSPF to filter outgoing LSAs
 Configuring an ABR to filter Type3 LSAs
 Setting the maximum number of External LSAs in the LSDB

• This course describes only equal-cost routes, default routes, and LSA filtering. For other
information, see HCIP-Datacom-Core Technology.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Equal-Cost Route
⚫ If the destinations and costs of the multiple routes discovered by one routing protocol are
the same, these routes are equal-cost routes and can participate in load balancing.
⚫ The device sends packets to the same destination address through multiple equal-cost routes
in load balancing mode.

Set the maximum number of equal-cost routes for load balancing.

[Huawei-ospf-1] maximum load-balancing number

• Command: [Huawei-ospf-1] maximum load-balancing number

▫ number: specifies the maximum number of equal-cost routes for load balancing.
The value range varies according to the device model. For details, see the product
documentation of the corresponding device.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Example for Configuring the Number of

Equal-Cost Routes for Load Balancing
R1 R3 It is required that R1 can access the loopback interface address of
Cost = 10
GE 0/0/0
R3 through the path R1 -> R3 or the path R1 -> R2 -> R3.
1. Assign an IP address to each interface and configure OSPF
on each device. (Details are not provided here.)
2. Configure the maximum number of OSPF equal-cost routes for
OSPF load balancing on R1.
Area 0 R2
[R1] ospf
[R1-ospf-1] maximum load-balancing 2
Device Interface IP Address
GE 0/0/0 10.1.13.1/24 3. Verify the configuration.
R1
GE 0/0/1 10.1.12.1/24
[R1]display ip routing-table
GE 0/0/1 10.1.12.2/24 Route Flags: R - relay, D - download to fib
R2 -------------------------------------------------------------------------------------------
GE 0/0/2 10.1.23.2/24
Loopback0 10.1.3.3/32 Destination/Mask Proto Pre Cost Flags NextHop Interface
R3 GE 0/0/0 10.1.13.3/24 10.1.3.3/32 OSPF 10 10 D 10.1.13.3 GigabitEthernet0/0/0
OSPF 10 10 D 10.1.12.2 GigabitEthernet0/0/1
GE 0/0/2 10.1.23.3/24

Page 21 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Default Route
⚫ On the area border and AS border of an OSPF network generally reside multiple routers for egress backup or traffic load balancing.
In this case, a default route can be configured to reduce the number of routing entries in the routing table and ensure high
availability of the network.

⚫ OSPF default routes are generally applied to the following scenarios:

 An ABR advertises Type 3 LSAs carrying the default route so that routers in an area forward inter-area packets accordingly.
 An ASBR advertises Type 5 or Type 7 LSAs carrying the default route so that routers in an AS forward AS-external packets.

Advertis Flooding
Area Type Trigger Condition LSA Type
ed by Scope
The default-route-advertise Common
Common area ASBR Type 5 LSA
command is run. area
Stub area and
totally stubby Automatically generated ABR Type 3 LSA Stub area
area
The nssa [ default-route-advertise ]
NSSA ASBR Type 7 LSA NSSA
command is run.
Totally NSSA Automatically generated ABR Type 3 LSA NSSA

• Default routes have all 0s as the destination address and mask. A device uses a default
route to forward packets when no matching route is available. Hierarchical
management of OSPF routes prioritizes the default route carried in Type 3 LSAs over
the default route carried in Type 5 or Type 7 LSAs.
• Common area:
▫ By default, routers in a common OSPF area do not generate default routes. To
enable a router in a common OSPF area to advertise a default route to OSPF, run
the default-route-advertise command on the router. After the command is run,
the router generates a default ASE LSA (Type 5 LSA) and advertises it to the
entire OSPF AS.
• Stub area:
▫ Type 5 LSAs cannot be advertised within a stub area. All routers within a stub
area can learn AS external routes only through an ABR.
▫ The ABR in a stub area automatically generates a default Type 3 LSA and
advertises it to the entire stub area. The ABR uses the default route to divert
traffic destined for a destination outside the AS to itself and then forwards the
traffic.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Configuring Default Route Advertisement to

OSPF Areas
1. Configure default route advertisement to common OSPF areas.

[Huawei-ospf-1] default-route-advertise [ [ always | permit-calculate-other ] | cost cost | type type | route-

policy route-policy-name [ match-any ] ]
By default, OSPF devices in a common OSPF area do not generate default routes.

2. Configure default route advertisement through a Type 3 summary LSA and set a cost for the route.

[Huawei-ospf-1] default-route-advertise summary cost cost

⚫ Note:
 The import-route (OSPF) command cannot import the default route of another routing protocol. To enable a router to
advertise the default route of another routing protocol, run the default-route-advertise command on an ASBR so that the
default route is advertised to all common OSPF areas.
 Before advertising a default route, OSPF compares the preferences of default routes in an OSPF area and then advertises a
default route with the highest preference. If a static default route is configured on an OSPF device, ensure that the preference of
the static default route is lower than that of the default route to be advertised by OSPF. This ensures that the default route
advertised by OSPF will be added to the routing table of the OSPF device.

• Command: [Huawei-ospf-1] default-route-advertise [[always | permit-calculate-

other] | cost cost | type type | route-policy route-policy-name [match-any]]
▫ always: An LSA that describes the default route is generated and advertised
regardless of whether the local device has an active default route that does not
belong to the current OSPF process.
▪ If always is configured, the device does not calculate the default routes
from other devices.
▪ If always is not configured, an LSA that describes the default route can be
generated only if an active default route that does not belong to the
current OSPF process exists in the routing table of the local device.
▫ permit-calculate-other: An LSA that describes the default route is generated
and advertised only if the device has an active default route that does not belong
to the current OSPF process, and the device still calculates the default routes
from other devices.
▫ type type: specifies the type of an external route. The value is 1 or 2. The default
value is 2.
▪ 1: Type 1 external route
▪ 2: Type 2 external route
▫ route-policy route-policy-name: specifies the name of a route-policy. The device
advertises default routes according to the configuration of the route-policy when
the routing table of the device contains a default route that matches the route-
policy but does not belong to the current OSPF process. The value is a string of 1
to 40 case-sensitive characters. If spaces are used, the string must start and end
with double quotation marks (").
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Configuring OSPF to Filter Outgoing LSAs

⚫ When multiple links exist between two routers, you can enable the function to filter outgoing LSAs,
preventing them from being sent to particular links. This function can help reduce unnecessary
retransmission of LSAs and reduce bandwidth consumption.
⚫ Filtering the outgoing LSAs on a specified OSPF interface can prevent unwanted LSAs from being sent
to neighbors, thus reducing the LSDB sizes of the neighbors and speeding up network convergence.

To filter outgoing LSAs on an OSPF interface, run the following command:

[Huawei-GigabitEthernet0/0/1] ospf filter-lsa-out { all | { summary [ acl { acl-number | acl-name } ]

| ase [ acl { acl-number | acl-name } ] | nssa [ acl { acl-number | acl-name } ] } }

The command configuration does not take effect for the LSAs that have been sent out before the command is
run. The aging time of such an LSA is still 3600 seconds.

• Command: [Huawei-GigabitEthernet0/0/1] ospf filter-lsa-out { all | { summary [ acl {

acl-number | acl-name } ] | ase [ acl { acl-number | acl-name } ] | nssa [ acl { acl-
number | acl-name } ] } }
▫ all: filters all outgoing LSAs, except grace LSAs.

▫ summary: filters outgoing network-summary-LSAs (Type 3).

▫ ase: filters outgoing AS-external-LSAs (Type 5).

▫ nssa: filters outgoing NSSA-LSAs (Type 7).

▫ acl acl-number: specifies the number of a basic ACL. The value is an integer
ranging from 2000 to 2999.

▫ acl acl-name: specifies the name of an ACL. The value is a string of 1 to 32 case-
sensitive characters. It cannot contain spaces and must start with a letter (a to z
or A to Z).
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Configuring OSPF to Filter ABR Type 3 LSAs

⚫ Configure filtering policies for incoming and outgoing ABR Type 3 LSAs (network-summary-LSAs) in an area,
allowing only those that pass the filtering to be sent and accepted.
⚫ Filtering Type 3 LSAs in a specified OSPF area can prevent unwanted LSAs from being sent to neighbors, thus
reducing the LSDB sizes and speeding up network convergence.

To filter outgoing Type3 LSAs in an OSPF area, run the following command:

[Huawei-ospf-1-area-0.0.0.1] filter { acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-

policy route-policy-name } export

To filter incoming Type3 LSAs in an OSPF area, run the following command:

[Huawei-ospf-1-area-0.0.0.1] filter { acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-

policy route-policy-name } import

• Command: [ Huawei-ospf-1-area-0.0.0.1 ] filter { acl-number | acl-name acl-name |

ip-prefix ip-prefix-name | route-policy route-policy-name } export

▫ acl-number: specifies the number of a basic ACL. The value is an integer ranging
from 2000 to 2999.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Overview of OSPF Database Overflow

⚫ The LSDBs of OSPF devices in the same area are synchronized after routes are converged. However,
achieving such a state can be difficult as the number of routes on a network continuously increases,
causing some devices to be unable to carry excess routing information due to limited system resources.
This is called an OSPF database overflow.
⚫ One way to solve such an issue is to configure stub areas or NSSAs, which reduces the amount of
routing information on devices. However, such an approach cannot prevent an OSPF database
overflow caused by a sharp increase in dynamic routes. To resolve this issue, set the maximum number
of non-default external LSAs allowed in the LSDB of a device to dynamically control the LSDB size.

Set the maximum number of non-default external LSAs allowed in the LSDB.
[Huawei-ospf-1] lsdb-overflow-limit number

• When the number of external LSAs (Type 5 and Type 7) imported by OSPF exceeds the
maximum number supported, excessive external LSAs cannot be processed properly
and are discarded. To address this issue, you can set a proper upper limit for the
number of non-default external LSAs in the LSDB, so as to adjust and optimize the
OSPF network.

• Command: [Huawei-ospf-1] lsdb-overflow-limit number

▫ number: specifies the maximum number of non-default external LSAs allowed in

the LSDB. The value is an integer ranging from 1 to 1000000.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Preventive Measures for OSPF

Database Overflows
⚫ Setting the maximum number of non-default external routes on a router can prevent OSPF database overflows.
⚫ Set the same maximum number for all routers on an OSPF network. When the number of non-default external
routes on a router reaches the maximum number, the router enters the Overflow state and starts the Overflow
state timer (default timeout period: 5s). After the timer expires, the router automatically exits the Overflow state.

Overflow Phase OSPF Processing

• Deletes all non-default external routes generated by the router
Enters the Overflow
Enters the Overflow itself.
state.
state. • Starts the Overflow state timer.
Enters the Overflow
the timer.
Restarts

• Does not generate non-default external routes.

state again.

• Discards newly received non-default external routes and does not

Stays in the Overflow reply with LSAck packets.
Stays in the
• Checks whether the number of external routes still exceeds the
state. Overflow state.
maximum number when the overflow state timer expires.
▪ If not, the router exits the Overflow state.
▪ If so, the router restarts the Overflow state timer.
Exits the Overflow • Deletes the Overflow state timer.
state. • Generates non-default external routes.
Exits the Overflow
• Accepts newly received non-default external routes and replies with
state.
LSAck packets.
• Gets ready to enter the Overflow state again.

Page 29 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Example for Configuring OSPF

Route Control (1)
1. Assign an IP address to each interface and
R1 R2 R3 configure OSPF on each device. (omitted).
Area0 Area1
2. Configure R2 to filter Type 3 LSAs.

[R2] acl 2000

OSPF
[R2-acl-basic-2000] rule deny
[R2-acl-basic-2000] quit
Type3 LSA
[R2] ospf
[R2-ospf-1] area 1
[R2-ospf-1-area-0.0.0.1] filter 2000 import

To reduce the number of LSAs on R3 and ensure that 3. Configure R2 to advertise default routes.
R3 can properly communicate with routers in other
[R2] ospf
areas, check that the following requirements are met: [R2-ospf-1] default-route-advertise always
 R2 does not inject Type 3 LSAs into Area 1.
 R2 advertises default routes.

Page 30 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Example for Configuring OSPF

Route Control (2)
1. Check the LSDB of R3.
R1 R2 R3 [R3]display ospf lsdb
Area0 Area1
OSPF Process 1 with Router ID 10.1.23.3
Link State Database
Area: 0.0.0.1
Type LinkState ID AdvRouter Age Len Sequence Metric
OSPF Router 10.1.23.3 10.1.23.3 731 48 80000004 1
Router 10.1.12.2 10.1.12.2 406 36 80000008 1
Type3 LSA Network 10.1.23.2 10.1.12.2 730 32 80000002 0

AS External Database
Type LinkState ID AdvRouter Age Len Sequence Metric
External 0.0.0.0 10.1.12.2 406 36 80000001 1
• The LSDB of R3 in Area1 does not contain
Type 3 LSAs but contains a default Type 5 LSA. 2. Check the routing table of R3.
• R3 can access devices in other areas through [R3]dis ip routing-table
the default route. Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 9 Routes : 9
Destination/Mask Proto Pre Cost Flags NextHop Interface
0.0.0.0/0 O_ASE 150 1 D 10.1.23.2 GigabitEthernet0/0/1
…

Page 31 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

OSPF Route Control Case Analysis

⚫ Network deployment:
Finance Marketing
 An enterprise network is divided into two networks, one for
department server department server the finance department and the other for the marketing
Static department.
routing  The enterprise network uses OSPF to allow internal
Border-1 Border-2 network connectivity. The backbone network is deployed in
area 0, clients of the finance department's network are
deployed in area 1, and clients of the marketing
OSPF department's network are deployed in area 2.
Area 0
Core-1 Core-2
 Border devices access department servers through static
routes, which are imported to the OSPF process.
⚫ Requirements:
 As long as the border-1 router and its uplink work properly,
AGG-1 AGG-2
the data flows of the finance department are forwarded
OSPF only through the border-1 router.
OSPF Area 2
Area 1  As long as the core-1 router and its uplink work properly,
the data flows of the finance department are forwarded
only through the core-1 router.

Finance Marketing
 For details about the data forwarding requirements of the
department client department client Data flow of the marketing department, see the comment of this slide.
finance department

• Data forwarding requirements of the marketing department:

▫ As long as the border-2 router and its uplink work properly, the data flows of the
marketing department are forwarded only through the border-2 router.

▫ As long as the core-2 router and its uplink work properly, the data flows of the
marketing department are forwarded only through the core-2 router.

• This case uses the data forwarding path of the finance department as an example. The
data forwarding path of the marketing department is not described here.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Requirement Analysis
1. Controlling the network egress for data forwarding:
Finance Marketing
 Data of the finance department is always forwarded
department server department server through border-1.
 Data of the marketing department is always forwarded
through border-2.
Border-1 Border-2

To ensure that fixed ASBRs are used to forward data, the

internal network changes must be ignored. That is, the
internal route cost is not calculated.
Core-1 Core-2 —Use Type 2 external routes of OSPF.

2. Controlling the precise internal path of data flows:

AGG-1 AGG-2 ▫ Load-balancing path should not exist.

Data needs to be sent to a specific ASBR along the planned

path on the network.
—Adjust the internal path cost.

Finance Marketing
department client department client Data flow of the
finance department

• Type 2 external route:

▫ Because a Type 2 external route offers low reliability, its cost is considered to be
much greater than the cost of any internal route to an ASBR.

▫ Cost of a Type 2 external route = Cost of the route from an ASBR to the
destination
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Traffic Egress Control

⚫ Implementation:
Imported finance Imported finance
Finance Marketing
department routes department server department server department routes  Import static routes destined for the finance department
Type: Type 2 Type: Type 2
Cost: 100 Cost: 200 server to the OSPF processes of R1 (border-1) and R2
(border-2) to implement egress backup through route-
Border-1 Border-2
R1 R2 policies.
 Set the type of the imported external route to Type 2.

Core-1 Core-2
 On R1, set the cost of the external route to 100; on R2, set
the cost of the external route to 200.

⚫ Configuration result:
AGG-1 AGG-2  When there are two Type 2 external routes with different
costs on the same network segment, the network device
prefers the route with a smaller cost. In this case, each
network device preferentially selects R1 as the egress.

Finance Marketing
department client department client

• The internal path cost to each ASBR is not considered during traffic egress control.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Controlling Internal Paths

⚫ Network requirement analysis:
Finance Marketing
department server department server  If the network is running properly, S3 (AGG-1)
selects path 1.
Border-1 Border-2
R1 R2
 If the link between S1 (core-1) and R1 fails, S3
selects path 2.
 If S1 fails, S3 selects path 3.
Core-1 Core-2
S1 S2
1 2 3
⚫ Implementation:
 Path 1-cost < Path 2-cost < Path 3-cost
AGG-1 AGG-2
S3 S4

Finance Marketing
department client department client Data flow of the
finance department

Page 35 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Controlling Internal Paths: Adjusting the Cost

Between Aggregation Devices and Core Devices
⚫ If the link between S1 and R1 fails, S3 preferentially selects path
Finance
department server
Marketing
department server
1 and then path 2 because S1 is working properly.
⚫ Implementation:
Border-1 Border-2  Path 1-cost < Path 2-cost, that is:
R1 R2
[Cost (S3 - S1) + Cost (S1 - S2) + Cost (S2 - R1)] < [Cost (S3 - S2) + Cost (S2 - R1)]
Cost=10
 Path 1 can be achieved by adjusting the path cost between
Core-1 Core-2
S1 Cost=10 S2 aggregation devices and core devices.
1 2
Cost=10

AGG-1 AGG-2
S3 Cost=50 S4

Finance Marketing
department client department client Data flow of the
finance department

Page 36 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Controlling the Internal Path: Adjusting the Cost

Between Core Devices and Boundary Devices
⚫ If the link between S3 and S1 fails, S3 preferentially selects path 1
Finance
department server
Marketing
department server
and then path 2 because S1 is working properly.
⚫ Implementation:
Border-1 Border-2  Path 1-cost < Path 2-cost, that is:
R1 R2
[Cost (S3 - S2) + Cost (S2 - S1) + Cost (S1 - R1)] < [Cost (S3 - S2) + Cost (S2 - R1)]
Cost=10
2
 Path 1 can be preferentially selected by adjusting the path cost
Core-1 1 Core-2
S1 Cost=10 S2 between core devices and boundary devices.

Cost=10

AGG-1 AGG-2
S3 Cost=50 S4

Finance Marketing
department client department client Data flow of the
finance department

Page 37 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Example for Configuring OSPF Route Control (1)

192.168.10.0/24 192.168.20.0/24 Configure a route-policy on R1 and set the cost to 100.
Imported finance Finance
department server
Marketing
department server
Imported finance [R1] acl 2000
department routes department routes [R1-acl-basic-2000] rule permit source 192.168.10.0 0.0.0.255
Type: Type 2 Static Type: Type 2
Cost: 100 Cost: 200 [R1-acl-basic-2000] quit
routing
Border-1 Border-2 [R1] route-policy static2ospf permit node 10
R1 R2
[R1-route-policy] if-match acl 2000
[R1-route-policy] apply cost 100
OSPF [R1-route-policy] quit
Core-1
Area 0
Core-2
[R1] route-policy static2ospf permit node 20
S1 S2 [R1-route-policy] quit

Import static routes to the OSPF process on R1.

AGG-1 AGG-2
S3 S4 [R1] ospf
OSPF OSPF [R1-ospf-1] import-route static route-policy static2ospf type 2
Area 1 Area 2

Finance Marketing
department client department client

Page 38 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Example for Configuring OSPF Route Control (2)

192.168.10.0/24 192.168.20.0/24 Configure a route-policy on R2 and set the cost to 200.
Imported finance Finance
department server
Marketing
department server
Imported finance [R2] acl 2000
department routes department routes [R2-acl-basic-2000] rule permit source 192.168.10.0 0.0.0.255
Type: Type 2 Static Type: Type 2
Cost: 100 Cost: 200 [R2-acl-basic-2000] quit
routing
Border-1 Border-2 [R2] route-policy static2ospf permit node 10
R1 R2
[R2-route-policy] if-match acl 2000
[R2-route-policy] apply cost 200
OSPF [R2-route-policy] quit
Core-1
Area 0
Core-2
[R2] route-policy static2ospf permit node 20
S1 S2 [R2-route-policy] quit

Import static routes to the OSPF process on R2.

AGG-1 AGG-2
S3 S4 [R2] ospf
OSPF OSPF [R2-ospf-1] import-route static route-policy static2ospf type 2
Area 1 Area 2

Finance Marketing
department client department client

Page 39 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Equal-Cost Default LSA Configuration
Overview
Route Route Filtering Case

Example for Configuring OSPF Route Control (3)

192.168.10.0/24 192.168.20.0/24 Set the OSPF cost of an interface (GE0/0/1 of R1 is used as an
Finance Marketing example).
department server department server

Static [R1] interface GigabitEthernet 0/0/1

routing
[R1-GigabitEthernet0/0/1] ospf cost 50
Border-1 Border-2
R1 R2

Cost=10
OSPF
Area 0
Core-1 Core-2
S1 Cost=10 S2

Cost=10

AGG-1 AGG-2
S3 Cost=50 S4
OSPF OSPF
Area 1 Area 2

Finance Marketing
department client department client

Page 40 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Contents
1. OSPF fast convergence

2. OSPF Route Control

3. Other OSPF Features

4. Advanced IS-IS Features

Page 41 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Multi- Association Forwarding
Process with BGP Address

OSPF Multi-Process
⚫ OSPF supports multiple processes that can separately run on the same device and do not affect each other. Route
exchange between different OSPF processes is similar to route exchange between different routing protocols.
⚫ An interface on a router can belong to only one OSPF process.

• Usage scenario: [PE] ospf 100 vpn-instance VPN1

[PE-ospf-100] quit
▫ A typical application of OSPF multi-process is in the VPN
CE1 [PE] ospf 200 vpn-instance VPN2
scenario. VPN1 [PE-ospf-200] quit
Site 1
▫ As shown in the figure, a PE connects to two different VPN
customers, and OSPF is deployed between the PE and CEs.
PE
Therefore, multiple processes can be deployed on the PE to
CE2
isolate the VPN customers. VPN2
Site 2

• VPN: virtual private network

• If a VPN instance is specified for an OSPF process that is to be created, the OSPF
process belongs to this instance. Otherwise, the OSPF process belongs to the global
instance.
Multi- Association Forwarding
Process with BGP Address

Association Between OSPF and BGP (1)

When a new device is added or a device is restarted, network traffic may be lost during BGP convergence. This is
because IGP route convergence is faster than BGP route convergence.

R2 1. If R2 fails, traffic is switched to the path R1 -> R3 -> R4 -> R5.

AS 100 AS 101
3
10.1.5.5/32 2. After R2 recovers, OSPF converges first because IGP route
2
convergence is faster than BGP route convergence. If R1 needs
1 to access 10.1.5.5/32, it searches for a BGP route with the next
R1 R4 EBGP R5 hop being R5. R2 then searches for the IGP route and sends
traffic to R2 over the route.
R3
IBGP
3. After receiving the traffic, R2 searches for the BGP route.
OSPF runs on R1, R2, R3, and R4 and full-mesh IBGP Because BGP route convergence is not complete, R2 does not
connections are established. R3 is the backup device of R2. find a route to 10.1.5.5/32 and therefore does not forward

When the network is stable, the traffic from R1 to 10.1.5.5/32 traffic. As a result, traffic is lost.

passes through the path R1 -> R2 -> R4 -> R5.

Page 43 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Multi- Association Forwarding
Process with BGP Address

Association Between OSPF and BGP (2)

⚫ OSPF-BGP synchronization can be enabled to prevent traffic loss.
⚫ After OSPF-BGP synchronization is enabled on a device, the device remains as a stub router within the set
synchronization period. That is, the link metric in the LSA advertised by the device is the maximum value 65535.
Therefore, the device instructs other OSPF devices not to use it for data forwarding.
Configure it as
Configure the stub router.
a stub router.
AS 100 R2 AS 101 [Huawei-ospf-1] stub-router [ on-startup [ interval ] ]
10.1.5.5/32 • Configuring a stub router is a special route selection
method. The path with a stub router configured is not
preferred.
R1 R4 EBGP R5
• The implementation is to set the metric to the maximum
R3 value (65535) to prevent data from being forwarded
IBGP
through the router. It is used to protect the link of the
Enable BGP association on R2. In this way, R1 continues to
router and is usually used in maintenance scenarios, such as
forward traffic through R3, but does not forward traffic to R2
upgrade.
until BGP route convergence on R2 is complete.

• Command: [Huawei-ospf-1] stub-router [ on-startup [ interval ] ]

▫ on-startup [ interval ]: specifies the interval for a device to remain as a stub

router when the device restarts or fails. The value is an integer ranging from 5 to
65535, in seconds. The default value is 500s.

▪ If on-startup is not configured, the device is always a stub router. That is,
the cost of all routes sent by this device is 65535.

▪ If on-startup is specified, the device remains as a stub router only when it

restarts or fails. The duration is determined by interval. If interval is not
specified, the default value of 500s is used.
Multi- Association Forwarding
Process with BGP Address

OSPF Forwarding Address

Forwarding address (FA):

 The FA is the address to which a data packet is forwarded before the packet reaches the advertised destination
address. If the forwarding address is 0.0.0.0, the packet is forwarded to the originating ASBR.
 Type 5 AS-External LSAs and Type 7 NSSA LSAs:

LS Age Options LS Type

Link State ID
Advertising Router
LS Sequence Number
LS Checksum Length
Network Mask OSPF Type 5 and Type 7 LSAs contain a special
E 0 Metric
FA field. The introduction of FA enables OSPF to
Forwarding Address
avoid the sub-optimal path problem in some
External Route Tag
special scenarios.
...

Page 45 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Multi- Association Forwarding
Process with BGP Address

Problem Occurring When No FA Is Used

⚫ OSPF runs on R2, R3, and R4 that are deployed in Area 0. OSPF is
10.1.1.1/32
enabled on GE0/0/1 of R2 and GE0/0/1 of R3, and OSPF
adjacencies are established between the two routers. However, no
R1
OSPF adjacencies are established between R1 and the two
GE0/0/1
routers.
10.1.123.1
1. Configure a static route destined for 10.1.1.1/32 on R2, with
1 Static route to 10.1.1.1/32
The next hop is 10.1.123.1. 10.1.123.1 as the next hop.

10.1.123.2 10.1.123.3 2. R2 imports the static route to OSPF and generates a Type 5
GE0/0/1 GE0/0/1 LSA to be flooded in the area.
R2 R3
2 Imports Type 5 LSA 3. After R3 receives the Type 5 LSA from R2, it calculates an
the route 10.1.1.1/32 3 external route to 10.1.1.1/32 and sets the next-hop address
to OSPF.
of the route to R2 (10.1.123.2).

⚫ The path from a router (for example, R4) in the OSPF domain to
OSPF R4 10.1.1.1/32 is R4 -> R3 -> R2 -> R1, which is the sub-optimal path.

Page 46 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Multi- Association Forwarding
Process with BGP Address

Using FA to Solve the Suboptimal

Path Problem
10.1.1.1/32
⚫ When advertising an external route destined for
R1
10.1.1.1/32 in the OSPF area, R2 sets the FA of the
GE0/0/1
10.1.123.1 corresponding Type 5 LSA to 10.1.123.1, which is
1 Static route to 10.1.1.1/32 Data packets sent the next hop of the external route.
The next hop is 10.1.123.1. to 10.1.1.1/32

10.1.123.2 10.1.123.3
⚫ When R3 receives the LSA, it calculates the route to
GE0/0/1 GE0/0/1 10.1.1.1/32 and finds that the FA is not 0.
R2 R3
2 Imports Type 5 LSA Therefore, R3 considers that the next hop to
the route 10.1.1.1/32 3
to OSPF. FA=10.1.123.1 10.1.1.1/32 is the address specified by the FA, that
is, 10.1.123.1.
OSPF R4

Page 47 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Multi- Association Forwarding
Process with BGP Address

FA Values
⚫ When an ASBR imports external routes, if the FA field in the Type 5 LSA is 0, the router considers that the data
packets destined for the destination network segment should be sent to the ASBR. If the FA field in a Type 5 LSA is
not 0, the router considers that the data packet destined for the destination network segment should be sent to the
device identified by the FA.
⚫ The FA field can be set to a non-zero value only when all the following conditions are met:
 The ASBR activates OSPF on the interface (outbound interface of the external route) connected to the external network.
 The preceding interface is not configured as a silent interface.
 The OSPF network type of such an interface is broadcast or NBMA.
 The IP address of the interface is within the network segment specified by the network command in the OSPF configuration.

• The route to the FA must be an OSPF intra-area route or an inter-area route. In this manner, the router that
receives the external LSA can add the LSA into the routing table. The next hop of the route generated using the
loaded external LSA is the same as the next hop to the FA.

• Type 7 LSAs in an NSSA are translated into Type 5 LSAs.

▫ To advertise external routes imported by an NSSA to other areas, Type 7 LSAs

must be translated into Type 5 LSAs. By default, the translator is the ABR with
the largest router ID in an NSSA.

▫ The propagate bit (P-bit) in the Options field of an LSA header is used to notify a
translator whether the Type 7 LSA needs to be translated into a Type 5 LSA. A
Type 7 LSA can be translated into a Type 5 LSA only when the P-bit is set to 1
and the FA is not 0.

▫ The P-bit is not set for Type 7 LSAs generated by an ABR.

• Note: All OSPF LSAs have the same LSA header, and the P-bit is in the Options field of
the LSA header.
Multi- Association Forwarding
Process with BGP Address

Case: Typical FA Application

in NSSA Scenarios
⚫ When multiple ABRs exist in an NSSA, the system automatically selects an ABR as a translator to translate Type 7 LSAs into Type 5
LSAs. Other ABRs do not perform LSA translation.

⚫ As shown in the figure, if the FA is not considered, R1 considers that the packet must pass through the ABR (R3) to reach the
destination because the router ID of R3 is greater than that of R2. In this way, traffic is diverted to the low-bandwidth link R1 -> R3 -
> R4 -> R5.
Router ID 10.1.3.3
R3

Area 0 NSSA Import direct

Type7 LSA external routes.
10.1.5.0/24
FA=10.1.45.5
R1 10.1.5.0/24
10.1.45.5
R4 R5

After the FA is introduced, traffic Data sent to 10.1.5.0/24 Route transfer

is transmitted to the destination
Path without the FA used
network segment through a R2
high-bandwidth link. Path with the FA used
Router ID 10.1.2.2
Page 49 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.

• As shown in the figure:

▫ Configure R5 to import direct external routes and set the IP address of the FA to
10.1.45.5, which is used by R5 to access the destination network segment
10.1.5.0/24.

▫ R3 translates Type 7 LSAs into Type 5 LSAs and the LSAs continue to carry the FA
10.1.45.5.

▫ Upon receipt, R1 searches its OSPF routing table for a route to the FA and uses
the next hop address of the route as the next hop address of the external route.

▫ Therefore, R1 will finally access the destination network segment 10.1.5.0/24

through the path R1 -> R2 -> R4 -> R5.
Contents
1. OSPF fast convergence

2. OSPF Route Control

3. Other OSPF Features

4. Advanced IS-IS Features

Page 50 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.
Fast Route Other
Convergence Control Features

Overview of IS-IS Fast Convergence

⚫ IS-IS fast convergence is an extended feature designed to speed up route convergence. It
provides a series of functions, covering incremental SPF (I-SPF), PRC, intelligent timer, and
LSP fast flooding.
⚫ IS-IS supports fast convergence after a fault is rectified. For example, IS-IS auto FRR can be
used to quickly switch traffic to a backup link, and IS-IS can be associated with BFD to
quickly detect faults.

• The functions, including PRC, intelligent timer, and FRR, of IS-IS are similar to those of
OSPF and therefore not detailed here.
Fast Route Other
Convergence Control Features

I-SPF
I-SPF implementation: When the network topology changes, I-SPF recalculates routes only for
affected nodes instead of all nodes, speeding up route calculation.
R1 (root) • Scenario description:
▫ On an IS-IS network, an SPT with R1 as the root is calculated after route
convergence, as shown in the left figure. When R1 accesses R5, the traffic of
R1 is forwarded to R5 based on [the outbound interface of R1's downlink and
R2 R3
the IP address of the inbound interface of R3's uplink].
▫ R6 is added as a downstream device of R5. IS-IS is enabled on R6, meaning
that there is a new network node on the IS-IS network.
R4 R5
• I-SPF calculation:
▫ R5 and R6 both flood LSPs carrying information about their neighbor
R6 (new) relationship on the entire network.
▫ After receiving such an LSP, R1 performs I-SPF calculation only for R5 and R6
to generate a new SPT.
▫ Therefore, when R1 accesses R5 and R6, the traffic of R1 is forwarded to R5
In route calculation, a node represents a router,
and R6 based on [the outbound interface of R1's downlink and the IP address
and a leaf represents a route. I-SPF processes
of the inbound interface of R3's uplink].
the information of only changed nodes.

• SPF for route calculation: If a node on a network changes, SPF recalculates routes for
all the nodes on the network, which takes a long time, consumes a large number of
CPU resources, and consequently reduces the network-wide convergence speed.

• I-SPF is an improvement of SPF. Unlike SPF that calculates all nodes, I-SPF calculates
only affected nodes. The SPT generated using I-SPF is the same as that generated
using SPF. This significantly decreases CPU usage and speeds up network convergence.

• I-SPF and PRC are used together on an IS-IS network.

▫ If the SPT calculated by I-SPF changes, PRC processes all the leaves (routes) of
only the changed node.

▫ If the SPT calculated by I-SPF does not change, PRC processes only the changed
leaves (routes). For example, if IS-IS is newly enabled on an interface of a node,
the SPT on the network remains unchanged. In this case, PRC updates only the
routes of this interface, which consumes less CPU resources.
Fast Route Other
Convergence Control Features

LSP Fast Flooding

LSP fast flooding: speeds up the flooding of LSPs.
 Generally, when an IS-IS router receives new or updated LSPs from other routers, it updates the
local LSDB and periodically floods the involved LSPs.
 LSP fast flooding speeds up LSDB synchronization because it allows a device to flood a number of
LSPs (not exceeding the upper limit) before route calculation when the device receives one or more
new or updated LSPs. This flooding mode significantly speeds up the network-wide convergence
speed.

Enable LSP fast flooding.

[Huawei-isis-1] flash-flood [ lsp-count | max-timer-interval interval | [ level-1 | level-2 ] ]
Note: You can specify the maximum number of LSPs to be flooded at a time. Once specified, the number takes
effect on all IS-IS interfaces. The actual number of LSPs that can be sent at a time is limited to the number
specified by lsp-count.

• Command: [Huawei-isis-1] flash-flood [ lsp-count | max-timer-interval interval | [

level-1 | level-2 ] ]

▫ lsp-count: specifies the maximum number of LSPs that can be flooded on each
interface at a time. The value is an integer ranging from 1 to 15. The default
value is 5.

▫ max-timer-interval interval: specifies the maximum interval at which LSPs are

flooded. The value is an integer ranging from 10 to 50000, in milliseconds. The
default value is 10.

▫ level-1: enables the LSP flash-flood function in the Level-1 area. If no level is
specified in the command, this function is enabled in both Level-1 and Level-2
areas.

▫ level-2: enables the LSP flash-flood function in the Level-2 area. If no level is
specified in the command, this function is enabled in both Level-1 and Level-2
areas.
Fast Route Other
Convergence Control Features

Overview of IS-IS Route Control

In real-world applications, IS-IS routes calculated using SPF sometimes cannot meet network planning and
traffic management requirements, which may lead to various problems, such as slow table lookup due to
a large number of routing entries in routing tables and unbalanced link usage on a network. To optimize
IS-IS networks and facilitate traffic management, more precise route control is required. You can use any
of the following methods to implement the control:
 Adjusting the IS-IS preference
 Adjusting the IS-IS interface cost
 Configuring equal-cost routes
 Configuring IS-IS route leaking
 Configuring default route advertisement
 Importing external routes
 Configuring filter-policies

• This course involves only equal-cost and default routes. For details about other control
methods, see HCIP-Datacom-Core Technology.
Fast Route Other
Convergence Control Features

Equal-Cost Route
If there are multiple redundant links on an IS-IS network, multiple equal-cost routes to the
same destination may exist. In this case, you can use either of the following methods to
configure equal-cost routes:
 Configure load balancing so that traffic is evenly distributed to relevant links.
◼ This method improves link utilization and reduces the possibility of congestion caused by overloaded links.
However, because traffic will be randomly forwarded, this method may make traffic management difficult.

 Configure a preference for each equal-cost route so that the route with the highest preference is
preferentially selected and the others function as backups.
◼ This method is used to specify the preferred route among multiple equal-cost routes, without the need to
modify original configurations. It facilitates traffic management and improves network reliability.
◼ Note: After preferences are configured for equal-cost routes, IS-IS devices forward traffic to the next hop
with the highest preference, instead of forwarding traffic in load balancing mode.

Configuration of Equal-Cost IS-IS Routes

1. Configure load balancing among equal-cost IS-IS routes.

[Huawei-isis-1] maximum load-balancing number

Configure the maximum number of equal-cost routes that participate in load balancing.
2. Configure preferences for equal-cost IS-IS routes.

[Huawei-isis-1] nexthop ip-address weight value

By default, no preferences are configured for equal-cost IS-IS routes. A smaller value indicates a higher
preference.
If the number of equal-cost routes is greater than the number specified using the maximum load-balancing
command, routes are selected for load balancing according to the following rules in sequence:
1. Route preference: Routes with smaller preference values (higher preferences) are selected for load balancing.
2. Next-hop system ID: If all equal-cost routes have the same preference, routes with smaller next-hop system IDs are selected for
load balancing.
3. Local outbound interface index: If all equal-cost routes have the same preference and next-hop system ID, routes with smaller
local outbound interface indexes are selected for load balancing.

• Command: [Huawei-isis-1] maximum load-balancing number

▫ number: specifies the maximum number of equal-cost routes that participate in

load balancing. The value varies according to the device model.

• Command: [Huawei-isis-1] nexthop ip-address weight value

▫ ip-address: specifies the IP address of the next hop. The value is in dotted decimal
notation.

▫ weight value: specifies the weight of the next hop. A smaller value indicates a
higher preference. The value is an integer ranging from 1 to 254.
Fast Route Other
Convergence Control Features

Example for Configuring Equal-Cost Routes (1)

On the network shown in the figure, IS-IS runs on R1, R2, and R3. It
R1 R3 is required that R1 be able to access the loopback interface address
Cost=10
GE0/0/0 of R3 through path R1 -> R3 or R1 -> R2 -> R3.

1. Assign IP addresses to device interfaces and configure IS-IS on

each device. (Omitted)
2. Configure the number of IS-IS equal-cost routes for load
R2 balancing on R1.
IS-IS
[R1] isis
Device Interface IP Address [R1-isis-1] maximum load-balancing 2

GE0/0/0 10.1.13.1/24
R1 3. Verify the configuration.
GE0/0/1 10.1.12.1/24
[R1]display ip routing-table
GE0/0/1 10.1.12.2/24 Route Flags: R - relay, D - download to fib
R2
GE0/0/2 10.1.23.2/24 -------------------------------------------------------------------------------------------
Loopback0 10.1.3.3/32
Destination/Mask Proto Pre Cost Flags NextHop Interface
R3 GE0/0/0 10.1.13.3/24 10.1.3.3/32 ISIS-L2 15 10 D 10.1.13.3 GigabitEthernet0/0/0
GE0/0/2 10.1.23.3/24 ISIS-L2 15 10 D 10.1.12.2 GigabitEthernet0/0/1

Example for Configuring Equal-Cost Routes (2)

On the network shown in the figure, IS-IS runs on R1, R2, and R3. It
R1 R3 is required that R1 access the loopback interface address of R3
Cost=10
GE0/0/0 preferentially through path R1 -> R3.

1. Assign IP addresses to device interfaces and configure

IS-IS on each device. (Omitted)

IS-IS R2 2. (Optional) Configure preference for equal-cost routes on R1.

[R1] isis
Device Interface IP Address [R1-isis-1] nexthop 10.1.13.3 weight 1
[R1-isis-1] nexthop 10.1.12.2 weight 2
GE0/0/0 10.1.13.1/24
R1
GE0/0/1 10.1.12.1/24 3. Verify the configuration.

GE0/0/1 10.1.12.2/24 [R1]display ip routing-table

R2 Route Flags: R - relay, D - download to fib
GE0/0/2 10.1.23.2/24
-------------------------------------------------------------------------------------------
Loopback0 10.1.3.3/32
R3 GE0/0/0 10.1.13.3/24 Destination/Mask Proto Pre Cost Flags NextHop Interface
10.1.3.3/32 ISIS-L2 15 10 D 10.1.13.3 GigabitEthernet0/0/0
GE0/0/2 10.1.23.3/24

Default Route
⚫ IS-IS allows you to control the generation and advertisement of default routes using the following
methods:
 On Level-1-2 devices, configure a rule for setting the attached (ATT) bit in Level-1 LSPs.
 Configure Level-1 devices not to automatically generate default routes even if they receive Level-1 LSPs with the
ATT bit set to 1.
 Configure devices to advertise default routes to the IS-IS routing domain.
⚫ LSP packet format:
 The ATT bit is generated by a Level-1-2 router to identify whether the originating router connects to other
areas. Note that the ATT field has four bits, and Huawei datacom products use only one of the four bits.

PDU Common Header PDU Length

PDU Specific Header Remaining Lifetime
Variable Length Fields (TLV) LSP ID
Sequence Number
Checksum
P ATT OL IS Type

Setting the ATT Bit to Control the

Generation of Default Routes
⚫ In IS-IS, if a Level-1-2 device determines based on LSDB information that it can reach more areas
through a Level-2 area than through a Level-1 area, the device sets the ATT bit to 1 in Level-1 LSPs
before advertising these LSPs. Upon receipt, Level-1 devices generate default routes destined for this
Level-1-2 device.
⚫ The preceding rules are applied by default. The ATT bit can be set as required on a live network.
1. (Level-1-2 device) Configure a rule for setting the ATT bit in LSPs.

[Huawei-isis-1] attached-bit advertise { always | never }

By default, the Level-1-2 device sets the ATT bit in LSPs following the default rules.

2. (Level-1 device) Configure the device not to generate a default route after it receives LSPs carrying ATT bit 1.

[Huawei-isis-1] attached-bit avoid-learning

By default, a Level-1 device generates a default route after it receives LSPs carrying ATT bit 1.

• Command: [Huawei-isis-1] attached-bit advertise { always | never }

▫ always: indicates that the ATT bit is set to 1. After receiving an LSP with ATT bit
1, a Level-1 device generates a default route.

▫ never: indicates that the ATT bit is set to 0. This prevents the Level-1 device from
generating default routes and reduces the size of the routing table.

• Although the ATT bit is defined in both Level-1 and Level-2 LSPs, it is set to 1 only in
Level-1 LSPs advertised by Level-1-2 devices. Therefore, this command takes effect only
on Level-1-2 devices.

• To prevent Level-1 devices from advertising default routes to their routing tables,
perform either of the following operations:

▫ Run the attached-bit advertise never command on Level-1-2 devices to disable

them from advertising LSPs with ATT bit 1.

▫ Run the attached-bit avoid-learning command on Level-1 devices that connect

to Level-1-2 devices.

• The difference between the preceding commands lies in that the attached-bit avoid-
learning command applies to specified Level-1 devices.
Fast Route Other
Convergence Control Features

Configuring Devices to Advertise

Default Routes to the IS-IS Routing Domain
⚫ After the default-route-advertise command is run on a boundary device in the IS-IS domain, the
device advertises default route 0.0.0.0/0 to the IS-IS routing domain. After that, all traffic destined for
other routing domains is forwarded to this boundary device first, and the device then forwards the
traffic outside the IS-IS routing domain.
⚫ Generally, if other routing protocols are configured in addition to IS-IS, use the following two methods
to forward traffic in the IS-IS routing domain to other routing domains:
 Configure boundary devices to advertise default routes to the IS-IS routing domain. This method is simple and
does not require external route learning.
 Configure boundary devices to import routes of other routing protocols into IS-IS.
Configure an IS-IS device to generate a default route.

[Huawei-isis-1] default-route-advertise [ always | match default | route-policy route-policy-name ]

[ cost cost | tag tag | [ level-1 | level-1-2 | level-2 ] ] [ avoid-learning ]

By default, an IS-IS device does not generate the default route.

• Command: [Huawei-isis-1] default-route-advertise [ always | match default | route-

policy route-policy-name ] [ cost cost | tag tag | [ level-1 | level-1-2 | level-2 ] ]
[ avoid-learning ]
▫ always: configures an IS-IS device to unconditionally advertise the default route
and set itself as the next hop in the route.
▫ match default: advertises the default route generated by another routing
protocol or IS-IS process through LSPs if such a route already exists in the routing
table.
▫ route-policy route-policy-name: specifies the name of the route-policy. A Level-
1-2 device advertises the default route to the IS-IS routing domain only when
external routes matching the route-policy exist in the routing table of the device.
This prevents routing blackholes caused by the advertisement of the default
route when link faults make some important external routes unavailable. This
route-policy does not affect the import of external routes into IS-IS. The value is
a string of 1 to 40 case-sensitive characters, spaces not supported. If spaces are
used, the string must start and end with double quotation marks (").
▫ cost cost: specifies the cost of the default route. The value is an integer. The
value range depends on cost-style. When cost-style is narrow, narrow-
compatible, or compatible, the value ranges from 0 to 63. When cost-style is
wide or wide-compatible, the value ranges from 0 to 4261412864.
Fast Route Other
Convergence Control Features

Example for Configuring Default Routes

1. Assign an IP address to each interface and configure
OSPF/IS-IS on each device.
R1 R2 L2 R3 L2
GE0/0/1 GE0/0/2 2. Configure R2 to advertise the default route to the IS-IS
Loopback0:
10.1.1.1/32
routing domain.
10.1.12.0/24 10.1.23.0/24
[R2] isis
OSPF IS-IS [R2-isis-1] default-route-advertise always

3. Configure R2 to advertise the default route to the OSPF

routing domain.
[R2] ospf
As shown in the figure, OSPF runs on GE0/0/1 and [R2-ospf-1] default-route-advertise always
Loopback0 of R1 and GE0/0/1 of R2, and IS-IS runs on
4. Check routing entries on R3.
GE0/0/2 of R2 and R3.
[R3]display ip routing-table
To enable R3 to access the OSPF network, configure R2 Route Flags: R - relay, D - download to fib
---------------------------------------------------------------------------------------
to advertise the default route to the IS-IS routing domain. Routing Tables: Public
Destinations : 8 Routes : 8
Destination/Mask Proto Pre Cost Flags NextHop Interface
Similarly, R2 also needs to advertise the default route to 0.0.0.0/0 ISIS-L2 15 10 D 10.1.23.2 GigabitEthernet0/0/2
…
the OSPF routing domain.

IS-IS Multi-Instance and Multi-Process

⚫ In IS-IS multi-instance, multiple IS-IS processes are created on the same router, with each process associated with
one VPN instance.
⚫ In IS-IS multi-process, multiple IS-IS processes are created in the same VPN instance (or in the same public network
instance). These IS-IS processes are independent of each other. IS-IS processes function similarly to different routing
protocols in route exchange.
⚫ A network may carry different services, which need to be isolated for security. You can bind each IS-IS process to a
different VPN instance.
[PE] isis 100 vpn-instance VPN1
[PE-isis-100] quit
⚫ Application scenarios:
CE1 [PE] isis 200 vpn-instance VPN2
▫ IS-IS multi-instance and multi-process are typically used in VPN1 [PE-isis-200] quit
VPN scenarios. Site1

▫ As the figure shown, a PE is connected to two VPNs, each

PE
belonging to a different customer, and IS-IS is deployed
CE2
between the PE and CEs. You can configure multiple IS-IS VPN2
processes on the PE to isolate the VPN customers. Site2

• IS-IS multi-process and multi-instance have the following characteristics:

▫ In IS-IS multi-process, processes share the same global routing table. IS-IS multi-
instance, however, uses the routing tables of VPNs, with each VPN having a
separate routing table.

▫ IS-IS multi-process allows a set of interfaces to be associated with a specified IS-

IS process. This ensures that the protocol operations in the specified IS-IS process
are confined only to this set of interfaces. In this way, multiple IS-IS processes can
work on a single router, with each process responsible for a unique set of
interfaces.

▫ When creating an IS-IS process, you can bind it to a VPN instance. The IS-IS
process then accepts and processes only the events related to the VPN instance.
When the bound VPN instance is deleted, the IS-IS process is also deleted.

• Command: [Huawei] isis [ process-id ] [ vpn-instance vpn-instance-name ]

▫ process-id: specifies the ID of an IS-IS process. If no IS-IS process is specified, IS-IS

process 1 is started. The value is an integer ranging from 1 to 65535. The default
value is 1.

▫ vpn-instance vpn-instance-name: specifies the name of a VPN instance. If this

parameter is not specified, no VPN instance is associated with the IS-IS process.
The value is a string of 1 to 31 case-sensitive characters. If spaces are used, the
string must start and end with double quotation marks (").
Fast Route Other
Convergence Control Features

LSP Fragment
⚫ When a PDU to be advertised by IS-IS contains too much information, an IS-IS router generates LSP
fragments to carry the information.
⚫ LSP packet format

PDU Common Header PDU Length System ID (6 bytes)

PDU Specific Header Remaining Lifetime Pseudonode ID (1 byte)
Variable Length Fields (TLV) LSP ID LSP Number (1 byte)
Sequence Number
Checksum
P ATT OL IS Type

⚫ An IS-IS LSP fragment is identified by the 1-byte LSP Number field in LSP ID. So, an IS-IS process can
generate a maximum of 256 LSP fragments, which means only limited information can be carried.

Basic Concepts of LSP Fragment Extension

⚫ You can configure a virtual system ID for IS-IS to generate virtual IS-IS LSPs to carry routing information.
 Originating system: a router that actually runs IS-IS. A single IS-IS process can advertise LSPs like multiple virtual routers, and
the originating system refers to the "actual" (not virtual) IS-IS process.
 Normal system ID: system ID of the originating system.
 Virtual system: system identified by an additional system ID to generate extended LSP fragments. These fragments carry
additional system IDs in their LSP IDs.
 Additional system ID: system ID of a virtual system. It is assigned by a network administrator to identify a virtual system. A
maximum of 256 extended LSP fragments can be generated for each additional system ID. Type=24
 TLV 24 (IS Alias ID TLV): carried in LSP fragments and describes the relationship Length
between the originating and virtual systems. Value:
Normal System-ID

⚫ After LSP fragment extension is configured, the system prompts you to restart the IS-IS process if information is lost because LSPs
overflow. After the IS-IS process is restarted, the originating system loads as much routing information as possible to its LSPs. The
information that cannot be loaded is placed in the LSPs of virtual systems for transmission. The originating system then notifies
other routers of its relationship with the virtual systems through TLV 24.
Page 66 Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.

• The additional and normal system IDs must be unique throughout a routing domain.
Fast Route Other
Convergence Control Features

Implementation of LSP Fragment Extension

⚫ In IS-IS, each normal system ID identifies a system, which can generate a maximum of 256 LSP fragments. With
additional system IDs, up to 50 virtual systems can be configured, and an IS-IS process can then generate a
maximum of 13,056 LSP fragments.
⚫ LSP fragment extension can work in two modes.

Mode-1 Mode-2
• Used when some routers on the network do not support LSP • Used when all the routers on the network support LSP fragment
fragment extension. extension.
Calculates routes R1-1 Considers received LSP-1 R1-1
separately for the received LSP R1 virtual and LSP-2 both the routing LSP R1 virtual
LSP-1 and LSP-2. system information of R1 and system
calculates routes uniformly.
R2 R1 R1-2 R2 R1 R1-2
Does not support LSP R1 virtual R1 virtual
fragment extension. system system

• As the figure shown, R1 loads some routing information to the LSPs • As the figure shown, R1 loads some routing information to the LSPs
of R1-1 and R1-2 for transmission. When R2 receives the LSPs from of R1-1 and R1-2 for transmission. When R2 receives LSPs from R1-1
R1, R1-1, and R1-2, it considers that there are three independent and R1-2, it knows that their originating system is R1 based on TLV
routers at the peer end and calculates routes as normal. The costs of 24. R2 then considers information advertised by R1-1 and R1-2 as
the routes from R1 to R1-1 and from R1 to R1-2 are both 0, meaning information of R1.
that the routes from R2 to R1 and from R2 to R1-1/R1-2 share the
same cost.

• Mode-1 implementation:
▫ Virtual systems participate in SPF calculation. The LSPs advertised by the
originating system contain information about links to each virtual system.
Similarly, the LSPs advertised by each virtual system contain information about
links to the originating system. In this way, virtual systems function like physical
routers that connect to the originating system.
▫ Mode-1 is a transitional mode used to support earlier versions that are incapable
of LSP fragment extension. In these earlier versions, IS-IS cannot identify TLV 24.
As a result, the LSPs sent by a virtual system must look like LSPs sent by an
originating system.
▫ Precautions:
▪ The LSPs sent by a virtual system must contain the same area address and
overload bit as those in LSPs sent by an originating system. Other TLVs
must also be the same.
▪ The neighbor of a virtual system must point to an originating system, and
the metric is the maximum value minus 1. The neighbor of the originating
system must point to the virtual system, and the metric must be 0. This
ensures that the virtual system is the downstream node of the originating
system when other routers calculate routes.
Fast Route Other
Convergence Control Features

Basic Configuration Commands of

LSP Fragment Extension
1. Enable LSP fragment extension for an IS-IS process.

[Huawei-isis-1] lsp-fragments-extend [ [ level-1 | level-2 | level-1-2 ] | [ mode-1 | mode-2 ] ]

By default, LSP fragment extension is disabled for IS-IS processes.
If no mode or level is specified during the configuration of LSP fragment extension, mode-1 and level-1-2 are
used by default.
2. Configure a virtual system.

[Huawei-isis-1] virtual-system virtual-system-id

By default, no virtual system is configured.

To enable a device to generate extended LSP fragments, you must configure at least one virtual system ID. This
ID must be unique throughout a routing domain.
An IS-IS process can be configured with up to 50 virtual system IDs.

Note: The preceding two commands must be used together. The configured virtual system ID takes effect only after
LSP fragment extension is enabled and the IS-IS process is restarted using the reset isis all command.

• Command: [Huawei-isis-1] lsp-fragments-extend [ [ level-1 | level-2 | level-1-2 ] | [

mode-1 | mode-2 ] ]

▫ level-1: enables LSP fragment extension in Level-1.

▫ level-2: enables LSP fragment extension in Level-2.

▫ level-1-2: enables LSP fragment extension in Level-1-2.

▫ mode-1: allows routers to be compatible with other routers running earlier

versions that are incapable of LSP fragment extension.

▫ mode-2: requires all routers to support LSP fragment extension.

• Command: [Huawei-isis-1] virtual-system virtual-system-id

▫ virtual-system-id: specifies a virtual system ID of an IS-IS process. The length is 6

bytes (48 bits), and the format is XXXX.XXXX.XXXX.
Quiz
1. (Multiple) Which of the following fast convergence mechanisms are supported by OSPF? ( )
A. I-SPF

B. LSP fast flooding

C. Intelligent timer

D. OSPF IP FRR

2. (TorF) The FA field in Type 5 LSAs of OSPF must be 0.0.0.0. ( )

A. True

B. False

3. (TorF) On an IS-IS network, if a device runs mode-2 LSP fragment extension, virtual systems do not participate in
SPF calculation. All routers on the network know that the LSPs generated by the virtual systems actually belong to
the originating system. ( )
A. True

B. False

1. CD

2. B

3. A
Summary
⚫ To better adapt to network topology changes, OSPF and IS-IS support multiple fast convergence
modes. I-SPF and PRC algorithm speed up route calculation; FRR enables fast traffic switching to the
backup link; and intelligent timers allow you to control the speeds at which link state information is
generated and routes are calculated.

⚫ To control the size of routing tables and improve network performance, OSPF and IS-IS support route
filtering, equal-cost routes, and default routes.

⚫ To isolate protocol routing tables, OSPF and IS-IS support multi-process deployment on the same
device. Protocol routing tables of different processes do not affect each other.

⚫ To prevent a sub-optimal route from being selected when external routes are imported, OSPF uses the
FA in Type 5 or Type 7 LSAs to guide data packet forwarding.

⚫ To carry more routing information, IS-IS provides LSP fragment extension.

HCIP-Datacom-Advanced Routing & Switching Technology V1.0 Training Material
No ratings yet
HCIP-Datacom-Advanced Routing & Switching Technology V1.0 Training Material
724 pages
HCIE-Datacom V1.0 Training Material
No ratings yet
HCIE-Datacom V1.0 Training Material
2,897 pages
01-05 OSPF Configuration
No ratings yet
01-05 OSPF Configuration
183 pages
HCIP-Datacom-Advanced Routing & Switching Technology V1.0 Training Material PDF
100% (1)
HCIP-Datacom-Advanced Routing & Switching Technology V1.0 Training Material PDF
654 pages
Huawei Certification HCNP-IERS Lab Guide V2.0
100% (1)
Huawei Certification HCNP-IERS Lab Guide V2.0
504 pages
01-05 OSPF Configuration
No ratings yet
01-05 OSPF Configuration
183 pages
01-05 OSPF Configuration
No ratings yet
01-05 OSPF Configuration
183 pages
Digital Communication - Introduction
100% (5)
Digital Communication - Introduction
111 pages
NE5000E80E40E OSPF Advanced Routing Features ISSUE 1.01
No ratings yet
NE5000E80E40E OSPF Advanced Routing Features ISSUE 1.01
58 pages
02 ODR103035 NE Series Routers OSPF Advanced Routing FeaturesV8
No ratings yet
02 ODR103035 NE Series Routers OSPF Advanced Routing FeaturesV8
60 pages
OSPF Questions
No ratings yet
OSPF Questions
31 pages
01-05 OSPF Configuration
No ratings yet
01-05 OSPF Configuration
171 pages
10.1.3.5 Lab - Configuring OSPFv2 Advanced Features ELEISER HEBER ZELAYA CONDORI
100% (2)
10.1.3.5 Lab - Configuring OSPFv2 Advanced Features ELEISER HEBER ZELAYA CONDORI
8 pages
4CAE000545 - RTU500 Rel. 12.2 Engineer - Webinar
No ratings yet
4CAE000545 - RTU500 Rel. 12.2 Engineer - Webinar
48 pages
HCIP Datacom - Core Technology D2D Activity
No ratings yet
HCIP Datacom - Core Technology D2D Activity
38 pages
6 SDN L3 Networking Principles ISSUE - 1.00
No ratings yet
6 SDN L3 Networking Principles ISSUE - 1.00
72 pages
06 OSPF Basics
No ratings yet
06 OSPF Basics
59 pages
Sg245204 - Subarea To APPN Migration - HPR and DLUR Implementation
No ratings yet
Sg245204 - Subarea To APPN Migration - HPR and DLUR Implementation
356 pages
OWD090922 (Slide) UGW9811 V900R009C01 Bandwidth Management-20120319-B-V1 1
100% (1)
OWD090922 (Slide) UGW9811 V900R009C01 Bandwidth Management-20120319-B-V1 1
44 pages
HC120115000 OSPF Protocol Basics
No ratings yet
HC120115000 OSPF Protocol Basics
38 pages
ODR002031 Configure OSPF On NE Series Routers (V8) ISSUE 1
No ratings yet
ODR002031 Configure OSPF On NE Series Routers (V8) ISSUE 1
94 pages
06 OSPF Basics
No ratings yet
06 OSPF Basics
49 pages
Santosh Final Thesis
No ratings yet
Santosh Final Thesis
83 pages
HC120115000 OSPF Protocol Basics
No ratings yet
HC120115000 OSPF Protocol Basics
38 pages
Intro Juniper-3
No ratings yet
Intro Juniper-3
70 pages
Sesión 2 OSPF Basics
No ratings yet
Sesión 2 OSPF Basics
49 pages
10 OSPF Basics
No ratings yet
10 OSPF Basics
27 pages
06 OSPF Basics
No ratings yet
06 OSPF Basics
50 pages
OSPF Config
No ratings yet
OSPF Config
264 pages
Lab 1-2 Multiple OSPF Areas
No ratings yet
Lab 1-2 Multiple OSPF Areas
37 pages
06 OSPF Basics
No ratings yet
06 OSPF Basics
49 pages
Ospf
No ratings yet
Ospf
22 pages
Chapter 7 OSPF
No ratings yet
Chapter 7 OSPF
35 pages
HC110110017 Link State Routing With OSPF
No ratings yet
HC110110017 Link State Routing With OSPF
29 pages
03 OSPF Basics
No ratings yet
03 OSPF Basics
47 pages
Chapter 1 SOLUTION
No ratings yet
Chapter 1 SOLUTION
12 pages
SDWAN Training
No ratings yet
SDWAN Training
12 pages
Clase 2 Fast Convergence&NQA
No ratings yet
Clase 2 Fast Convergence&NQA
49 pages
9237-9 Ospf Faq
No ratings yet
9237-9 Ospf Faq
12 pages
Ospf Faq
No ratings yet
Ospf Faq
12 pages
Lab 1-1 Single-Area OSPF
No ratings yet
Lab 1-1 Single-Area OSPF
30 pages
OSPF Principles and Configurations
No ratings yet
OSPF Principles and Configurations
15 pages
Sen361 L DCCN Lab 10 Ospf
No ratings yet
Sen361 L DCCN Lab 10 Ospf
12 pages
Cis185 ROUTE Lecture3 OSPF Part1
No ratings yet
Cis185 ROUTE Lecture3 OSPF Part1
139 pages
10.1.3.5 Lab Configuring OSPFv2 Advanced Features
No ratings yet
10.1.3.5 Lab Configuring OSPFv2 Advanced Features
7 pages
Multiple Choice Questions - Wireless Communication
No ratings yet
Multiple Choice Questions - Wireless Communication
3 pages
OSPF and The Internet: Lucent Technologies Remote Access Business Unit
No ratings yet
OSPF and The Internet: Lucent Technologies Remote Access Business Unit
11 pages
Ece3501-Internet of Things Fundamentals: Dr.B.Nagajayanthi
No ratings yet
Ece3501-Internet of Things Fundamentals: Dr.B.Nagajayanthi
441 pages
OSPF Update Packet-Pacing Configurable Timers PDF
No ratings yet
OSPF Update Packet-Pacing Configurable Timers PDF
8 pages
14 Ospf
No ratings yet
14 Ospf
6 pages
CISA Acronyms
No ratings yet
CISA Acronyms
8 pages
Comprehensive OSPF Guide - In-Depth Study of Open Shortest
No ratings yet
Comprehensive OSPF Guide - In-Depth Study of Open Shortest
5 pages
2.7.3 Packet Tracer Multiarea Ospf Exploration Physical Mode Part 1
No ratings yet
2.7.3 Packet Tracer Multiarea Ospf Exploration Physical Mode Part 1
4 pages
Top 90+ CCIE OSPF Interview Questions (UPDATED) 2018
No ratings yet
Top 90+ CCIE OSPF Interview Questions (UPDATED) 2018
8 pages
Configure Single-Area OSPFv2
No ratings yet
Configure Single-Area OSPFv2
6 pages
Practica7 - Configuring OSPFv2 Advanced Features
No ratings yet
Practica7 - Configuring OSPFv2 Advanced Features
9 pages
2.4.11 Packet Tracer - Modify Single-Area OSPFv2 - ILM
No ratings yet
2.4.11 Packet Tracer - Modify Single-Area OSPFv2 - ILM
3 pages
OSPF
No ratings yet
OSPF
4 pages
Fortinet Testking NSE4 v2016-16-20 by Andy 167q
No ratings yet
Fortinet Testking NSE4 v2016-16-20 by Andy 167q
87 pages
10.1.3.4 Packet Tracer - Configuring OSPF Advanced Features
No ratings yet
10.1.3.4 Packet Tracer - Configuring OSPF Advanced Features
3 pages
Xsmax
No ratings yet
Xsmax
28 pages
System Network Administration 2 Admin PDF
No ratings yet
System Network Administration 2 Admin PDF
213 pages
Journal of Data Communication and Networking
No ratings yet
Journal of Data Communication and Networking
29 pages
CCNP 300-715 Dumps Dec 2020
No ratings yet
CCNP 300-715 Dumps Dec 2020
36 pages
MN Unit 2 Notes
No ratings yet
MN Unit 2 Notes
12 pages
Chapter 2 - Architecture
No ratings yet
Chapter 2 - Architecture
15 pages
ECE 539 Lecture 1 - Comm Network Introduction
No ratings yet
ECE 539 Lecture 1 - Comm Network Introduction
23 pages
Interfaces
No ratings yet
Interfaces
20 pages
CS601 Updated Handout Lesson 1-70 by Farhan Ahmadani
No ratings yet
CS601 Updated Handout Lesson 1-70 by Farhan Ahmadani
92 pages
HP Procurve Advanced CLI Commands Reference
100% (1)
HP Procurve Advanced CLI Commands Reference
8 pages
11.6.6 Lab - Calculate IPv4 Subnets
No ratings yet
11.6.6 Lab - Calculate IPv4 Subnets
4 pages
Huawei CloudEngine 5800 Series Switches Data Sheet - Cleaned
No ratings yet
Huawei CloudEngine 5800 Series Switches Data Sheet - Cleaned
9 pages
C/C++ Based Test: 27 Question 35 Marks: Q1 Find The Output Assume Size of Int Is 4 Byte
100% (1)
C/C++ Based Test: 27 Question 35 Marks: Q1 Find The Output Assume Size of Int Is 4 Byte
21 pages
gs970m Ds Reva 0
No ratings yet
gs970m Ds Reva 0
4 pages
LTE-M Evolution Towards 5G Massive MTC: Rapeepat Ratasuk, Nitin Mangalvedhe, David Bhatoolaul, Amitava Ghosh
No ratings yet
LTE-M Evolution Towards 5G Massive MTC: Rapeepat Ratasuk, Nitin Mangalvedhe, David Bhatoolaul, Amitava Ghosh
6 pages
Project3
No ratings yet
Project3
14 pages
C2IU Modbus Communication Portfolio
No ratings yet
C2IU Modbus Communication Portfolio
6 pages
Assignemnt 1 (16DET19F2999)
No ratings yet
Assignemnt 1 (16DET19F2999)
7 pages
RUTX16 Datasheet
No ratings yet
RUTX16 Datasheet
14 pages
Preventing DDOS Attack in Cloud Using Machine Learning
No ratings yet
Preventing DDOS Attack in Cloud Using Machine Learning
6 pages
Nokia Siemens Networks Multicontroller Platform: Multicontroller BSC and Transcoder Multicontroller RNC
No ratings yet
Nokia Siemens Networks Multicontroller Platform: Multicontroller BSC and Transcoder Multicontroller RNC
2 pages
Study Guide for Implementing Cisco Service Provider Advanced Routing Solutions (300-510 SPRI) Exam
From Everand
Study Guide for Implementing Cisco Service Provider Advanced Routing Solutions (300-510 SPRI) Exam
Anand Vemula
No ratings yet
IP MULTICAST ROUTING Part -3: Use of multicast routing.
From Everand
IP MULTICAST ROUTING Part -3: Use of multicast routing.
Ummed Singh
No ratings yet
Versatile Routing and Services with BGP: Understanding and Implementing BGP in SR-OS
From Everand
Versatile Routing and Services with BGP: Understanding and Implementing BGP in SR-OS
Alcatel-Lucent
No ratings yet
IP Routing Protocols All-in-one: OSPF EIGRP IS-IS BGP Hands-on Labs
From Everand
IP Routing Protocols All-in-one: OSPF EIGRP IS-IS BGP Hands-on Labs
Redouane MEDDANE
No ratings yet
LEARN MPLS FROM SCRATCH PART-B: A Beginners guide to next level of networking
From Everand
LEARN MPLS FROM SCRATCH PART-B: A Beginners guide to next level of networking
POONAM DEVI
No ratings yet
First Hop Redundancy Protocol: Network Redundancy Protocol
From Everand
First Hop Redundancy Protocol: Network Redundancy Protocol
Mulayam Singh
No ratings yet
ROUTING INFORMATION PROTOCOL: RIP DYNAMIC ROUTING LAB CONFIGURATION
From Everand
ROUTING INFORMATION PROTOCOL: RIP DYNAMIC ROUTING LAB CONFIGURATION
Mulayam Singh
No ratings yet
In Depth Guide to IS-IS Routing: Learn Intermediate System to Intermediate System Routing from scratch
From Everand
In Depth Guide to IS-IS Routing: Learn Intermediate System to Intermediate System Routing from scratch
Mamta Devi
No ratings yet