Reference Guide
• If no topology change occurs, an SPF calculation is performed and the hold timer is reset to its congured
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 congured 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
Object tracking manager (OTM) allows you to track the link status of Layer 2 interfaces, and the reachability of IP 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 VRRP and PBR. Each tracked object has a unique identifying number that clients use to congure 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 are reported to a
client application.
VRRP can subscribe to a track object which tracks the interface line protocol state. It can use 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 what you
congure the new priority to be for the tracked state. When the tracked state comes up, VRRP restores the original priority for the virtual
router group.
398
Layer 3