150
Configuring LSP parameters
Configuring LSP timers
• 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:
Ste
Command
Remarks
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 maximum LSP
age.
timer lsp-max-age seconds
Optional.
1200 seconds by default.
• Specify the LSP refresh interval and generation interval.
Each router needs to refresh LSPs generated by itself at a configurable interval and send them to
other routers to prevent valid routes from being aged out. A smaller refresh interval speeds up
network convergence but consumes more bandwidth.
When the network topology changes, for example, a neighbor is down or up, or the interface
metric, system ID, or area ID is changed, 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.
To specify the LSP refresh interval and generation interval:
Ste
Command
Remarks
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
Optional.
900 seconds by
default.
4. Specify the LSP
generation interval.
timer lsp-generation maximum-interval
[ initial-interval [ second-wait-interval ] ] [ level-1 |
level-2 ]
Optional.
2 seconds by default.
• 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 such LSPs.
On a P2P link, IS-IS requires an advertised LSP be acknowledged. If no acknowledgement is
received within a configurable interval, IS-IS will retransmit the LSP.
To configure LSP sending intervals: