
Customizing OSPF Services
308627-14.20 Rev 00
6-15
Setting a Maximum Number of Refreshes for Summary and ASE LSAs
The router refreshes unchanged summary LSAs and AS external LSAs every 30
minutes and floods the refreshed LSAs to the other OSPF routers in the domain. If
the amount of LSA refresh traffic becomes excessive, you can configure the router
to impose a delay (from 1 through 5 seconds) on the flooding of refresh LSAs
after a specified number of consecutive LSA refreshes.
In general, multiple LSAs are packaged in one link state update packet: Sending
many LSAs in one update packet reduces system overhead (for example, the IP
header and OSPF header required for each update packet) and bandwidth usage.
To set the maximum number of consecutive refreshes of self-originated summary
and ASE LSAs that the router sends before enforcing a delay, go to the global
OSPF prompt (for example,
box; ip; ospf
) and enter:
lsa-refresh-max
<value>
value
is any integer. The default value is 0 (no delay between LSA refreshes).
To set a delay from 1 through 5 seconds after the maximum number of
consecutive refreshes has been reached, go to the global OSPF prompt (for
example,
box; ip; ospf
) and enter:
lsa-refresh-delay
<seconds>
seconds
is the number of seconds from 1 (the default) through 5.
For example, the following command sequence sets the maximum number of
refreshes of self-originated summary and ASE LSAs to 30 and sets a delay of
3 seconds after the maximum number has been reached:
ospf#
lsa-refresh-max 30
ospf#
lsa-refresh-delay 3
ospf#
Note:
To set the maximum number of LSAs, you should consider the
configured MTU value (see “Specifying the MTU Size” on page 6-35) to
calculate the number of LSAs that can fit into one link state update packet.
(Summary LSAs and ASE LSAs consume approximately 64 bytes.)
Commentaires sur ces manuels