151
Configuring LSP parameters
Configuring LSP timers
1. Specify the maximum age of LSPs.
Each LSP has an age that decreases in the LSDB. Any LSP with an age of 0 is deleted from the
LSDB. You can adjust the age value based on the scale of a network.
To specify the maximum age of LSPs:
1. Enter system view.
N/A
2. Enter IS-IS view.
isis
[ process-id ]
[
vpn-instance
vpn-instance-name ]
N/A
3. Specify the maximum LSP
age.
timer lsp-max-age
seconds
The default setting is 1200
seconds.
2. Specify the LSP refresh interval and generation interval.
Each router needs to refresh its LSPs at a configurable interval and send them to other routers
to prevent valid routes from aging out. A smaller refresh interval speeds up network
convergence but consumes more bandwidth.
When network topology changes such as neighbor state, interface metric, system ID, or area ID
changes occur, the router generates an LSP after a configurable interval. If such a change
occurs frequently, excessive LSPs are generated, consuming a large amount of router
resources and bandwidth. To solve the problem, you can adjust the LSP generation interval.
When network changes are not frequent, the minimum-interval is adopted. If network changes
become frequent, the LSP generation interval increases by incremental-interval ×2
n-2
(n is the
number of calculation times) each time a generation occurs until the maximum-interval is
reached.
To specify the LSP refresh interval and generation interval:
1. Enter system view.
system-view
N/A
2. Enter IS-IS view.
isis
[ process-id ] [
vpn-instance
vpn-instance-name ]
N/A
3. Specify the LSP refresh
interval.
timer lsp-refresh
seconds
By default, the LSP refresh
interval is 900 seconds.
4. Specify the LSP
generation interval.
timer lsp-generation
maximum-interval
[ minimum-interval
[ incremental-interval ] ] [
level-1
|
level-2
]
By default:
• The maximum interval
is 5 seconds.
• The minimum interval
is 50 milliseconds.
• The incremental
interval is 200
milliseconds.
3. Specify LSP sending intervals.
If a change occurs in the LSDB, IS-IS advertises the changed LSP to neighbors. You can
specify the minimum interval for sending these LSPs to control the amount of LSPs on the
network.
On a P2P link, IS-IS requires an advertised LSP be acknowledged. If no acknowledgment is
received within a configurable interval, IS-IS will retransmit the LSP.