There are several methods to speed up ISIS convergence. Using timers is one of the techniques. ISIS utilizes the SPF (Shortest Path First) algorithm as a way to create the topology view of the network. Changes in the topology trigger to run SPF or PRC (Partial Route Computation). Once a calculation is complete the router sends LSP update to other neighbours. The next device launch SPF or PRC. LSP is generated and sent to adjacent routers. And so on. The network is converged if the LSP database is the same on all routers. This process can be delayed significantly as there are two main holdups which is waiting for SPF or PRC run as well as an LSP generation. There are three timer based commands to improve this. The syntax of the first command linked with SPF is as follows:

spf-interval spf-max-wait spf-initial-wait spf-second-wait

spf-max-wait - It is the maximum time between SPF runs (in sec).
spf-initial-wait - Delay between the first event in the network which trigger SPF run and the actual start-up of SPF (in msec). The default value is 5500 milliseconds which should be definitely altered.
spf-second-wait - Time between first and second SPF calculation (in msec).

An example:
spf-interval 5 10 1000

The initial SPF run is after 10 milliseconds. Then wait 1 second before the next SPF. The next SPF is run after 2 seconds, then 4 sec, 5 sec, 5 sec .. as the maximum wait is set up to 5 seconds. Of course SPF is launched only if there is a trigger. The root cause to do so may be disconnecting/connecting a transit path or a node. When the network is stable and there are no triggers for two times of the maximum wait (10 sec in this example) the delay return to the beginning interval 10 msec.

The second command is reffering to PRC with the following syntax:

prc-interval prc-max-wait prc-initial-wait prc-second-wait

The meaning of timers is identical as previously but with the relation to PRC. Partial Route Computation is much quicker (even 10 times) than SPF and is usually run when leaf prefix is added or removed. It is advisible to use just 1 sec as prc-max-wait as PRC computation before that time. PRC processes about 20 prefixes per millisecond. Thus 1 second for 20000 prefixes is enough in most of the cases. The prc-initial-wait interval can be very low even 1 msec as the backoff mechanism (set prc-second-wait to a higher value) prevents PRC from a constant prefixes flapping.

An example:
prc-interval 1 1 20

SPF and PRC are responsible for calculation the network topology tree. The last command listed here is to improve the LSP generation time.

lsp-gen-interval lsp-max-wait lsp-initial-wait lsp-second-wait

Note that the default lsp-initial-wait is just 50 msec which is very low but still can be changed even to 1 msec. Simply no need to wait for LSP generation. Default settings of lsp-max-wait (5 sec) and lsp-second-wait (5 sec) can also be tuned to as low value as 1 sec and 1 msec respectively.

An example:
lsp-interval 1 1 50

Not only one recommended set of values can be found for timers listed above. Depending on sources it might be "5 1 20" for every of the commands. Some presentations suggest 1 sec max-wait for PRC and LSP generation and the higher than 1 msec value for the second-wait. It vary and depends on the network scale but the initial-wait is definitely not the main concern and can be tuned to the lowest 1 msec interval.

Managing routers requires logging the output of several show commands. It is much quicker to turn on logging, paste a list of commands and just to wait until the task is done.

On Juniper routers it is required to add no-more keyword after the pipe |.

What about Cisco? Are you irritated by stroking a space key to see the whole running-config? To avoid it use terminal length 0 to get the output in one block without showing --More-- on the screen. Zero in the command means no page limit. To go back to a former status type terminal no length 0 or terminal length 24. Similarly, ASA has the pager 0 instruction which also turns off pausing.