Connectivity Guide

• hold-time — Sets the additional hold time between two SPF calculations in milliseconds, from 1 to 600000;
default 10000.
• max-wait — Sets the maximum wait time between two SPF calculations in milliseconds, from 1 to 600000;
default 10000.
Default
• start-time — 1000 milliseconds
• hold-time — 10000 milliseconds
• max-wait — 10000 milliseconds
Command Mode ROUTER-OSPFv3
Usage Information OSPFv2 and OSPFv3 support SPF throttling. By default, SPF timers are disabled in an OSPF instance.
Use SPF throttling to delay SPF calculations during periods of network instability. In an OSPF network, a topology
change event triggers an SPF calculation after a specied start time. When the start timer nishes, a hold time
may delay the next SPF calculation for an additional time. When the hold timer is running:
• Each time a topology change occurs, the SPF calculation delays for double the congured hold time up to
maximum wait time.
• If no topology change occur, an SPF calculation performs and the hold timer resets to its congured value.
If you do not specify a start-time, hold-time, or max-wait value, the default values are used. The no version of this
command removes the congured SPF timers and disables SPF throttling in an OSPF instance.
Example
OS10(config)# router ospfv3 100
OS10(config-router-ospfv3-100)# timers spf 1345 2324 9234
OS10(config-router-ospfv3-100)# do show ipv6 ospf
Routing Process ospfv3 100 with ID 129.240.244.107
SPF schedule delay 1345 msecs, Hold time between two SPFs 2324 msecs
Min LSA origination 5000 msec, Min LSA arrival 1000 msec
Min LSA hold time 0 msec, Max LSA wait time 0 msec
Number of area in this router is 1, normal 1 stub 0 nssa
Area (0.0.0.1)
Number of interface in this area is 1
SPF algorithm executed 2 times
Supported Releases 10.4.0E(R1) or later
Object tracking manager
OTM allows you to track the link status of Layer 2 (L2) interfaces, and the reachability of IPv4 and IPv6 hosts. You can increase the
availability of the network and shorten recovery time if an object state goes Down.
Object tracking monitors the status of tracked objects and communicates any changes made to interested client applications. OTM client
applications are virtual router redundancy protocol (VRRP) and policy-based routing (PBR). Each tracked object has a unique identifying
number that clients use to congure the action to take when a tracked object changes state. You can also optionally specify a time delay
before changes in a tracked object's state report to a client application.
VRRP subscribes to a track object which tracks the interface line protocol state. It uses the tracked object status to determine the priority
of the VRRP router in a VRRP group. If a tracked state or interface goes down, VRRP updates the priority based on how you congure the
new priority for the tracked state. When the tracked state comes up, VRRP restores the original priority for the virtual router group.
Layer 3
587