Table Of Contents

T Commands

template (BGP)

test forwarding distribution perf

test forwarding inconsistency

timers (GLBP)

timers active-time

timers basic

timers lsa-arrival (OSPF)

timers lsa-arrival (OSPFv3)

timers lsa-group-pacing (OSPF)

timers lsa-group-pacing (OSPFv3)

timers nsf converge

timers nsf route-hold

timers nsf signal

timers redirect

timers throttle lsa (OSPF)

timers throttle lsa (OSPFv3)

timers throttle spf (OSPF)

timers throttle spf (OSPFv3)

track (VRRP)

track interface

track ip route

transmit-delay (OSPF virtual link)

transmit-delay (OSPFv3 virtual link)

T Commands

---

This chapter describes the Cisco NX-OS unicast routing commands that begin with the letter T.

template (BGP)

To create a peer template and enter a peer template configuration mode, use the template command. To remove a peer template, use the no form of this command.

template {peer name | peer-policy name | peer-session name}

no template {peer name | peer-policy name | peer-session name}

Syntax Description

peer name	Specifies the name of the neighbor template.
peer-policy name	Specifies the name of the peer-policy template.
peer-session name	Specifies the name of the peer-session template.

Command Default

This command has no default settings.

Command Modes

Neighbor address-family configuration
Router bgp configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

The template command allows you to enable a set of predefined attributes that a neighbor inherits.

---

Note A BGP neighbor cannot be configured to work with both peer groups and peer templates. A BGP neighbor can be configured to belong to a peer group or to inherit policies from peer templates only.

---

Peer templates support only general policy commands. BGP policy configuration commands that are configured only for specific address families or NLRI configuration modes are configured with peer templates.

Peer Templates

The peer template combines the peer-session and peer-policy templates to form a basic neighbor definition. It is not mandatory to use a neighbor template but you can use it to simplify the BGP configuration.

Peer-policy Templates

Peer-policy templates are used to group and apply the configuration of commands that are applied within specific address-families and NLRI configuration mode. Peer-policy templates are created and configured in peer policy configuration mode. BGP policy commands that are configured for specific address-families or NLRI configuration modes are configured in a peer-policy template. When you enter the peer-policy template configuration mode, the following commands are available:

•suppress-inactive—Advertises the active routes to the peer only. See the suppress-inactive command for additional information.

•exit—Exits current configuration mode.

•filter-list name {in | out}—Creates the AS-PATH filter-list on the inbound and the outbound BGP routes. To remove the entry, use the no form of this command.

–in—Applies the access list to incoming routes.

–out—Applies the access list to outgoing routes.

•inherit peer-policy policy-name seq-num—Configures a peer-policy template to inherit the configuration from another peer-policy template. To remove an inherited statement from a peer-policy template, use the no form of this command. Range: 1 to 65535. Default: No inherit statements are configured.

The sequence number specifies the order in which the peer policy template is evaluated. Like a route-map sequence number, the lowest sequence number is evaluated first. Peer policy templates support inheritance and a peer can directly and indirectly inherit up to seven peer policy templates. Inherited peer policy templates are configured with sequence numbers like route maps. An inherited peer policy template, like a route map, is evaluated starting with the inherit statement with the lowest sequence number. However, peer policy templates do not fall through. Every sequence is evaluated. If a BGP policy command is reapplied with a different value, it will overwrite any previous value from a lower sequence number.

---

Note A Border Gateway Protocol (BGP) routing process cannot be configured to be a member of a peer group and to use peer templates for group configurations. You must use one method or the other. We recommend peer templates because they provide improved performance and scalability.

---

•maximum-prefix max—Specifies the maximum number of prefixes from this neighbor. Range: 1 to 300000. Default: This command is disabled by default. Peering sessions are disabled when the maximum number of prefixes is exceeded. See the maximum-prefix command for additional information.

•next-hop-self—Configures the router as the next hop for a Border Gateway Protocol (BGP) neighbor or peer group. To disable this feature, use the no form of this command. Default: Disabled.

•next-hop-third-party—Computes a third-party nexthop if possible.

•no—Negates a command or set its defaults.

•prefix-list name {in | out}—Specifies the route type to apply the prefix list. To remove the entry, use the no form of this command.

–in—Applies the prefix list to incoming routes.

–out—Applies the prefix list to outgoing routes.

•route-map name {in | out}—Specifies the route map name o apply the route type to apply to the neighbor.

–in—Applies the route map to incoming routes.

–out—Applies the route map to outgoing routes.

•route-reflector-client—Configures the router as a BGP route reflector and configures the specified neighbor as its client. To indicate that the neighbor is not a client, use the no form of this command. Default: There is no route reflector in the autonomous system.

By default, all internal BGP (iBGP) speakers in an autonomous system must be fully meshed, and neighbors do not readvertise iBGP learned routes to neighbors, thus preventing a routing information loop. When all the clients are disabled, the local router is no longer a route reflector.

If you use route reflectors, all iBGP speakers need not be fully meshed. In the route reflector model, an Interior BGP peer is configured to be a route reflector responsible for passing iBGP learned routes to iBGP neighbors. This scheme eliminates the need for each router to talk to every other router.

All the neighbors configured with this command will be members of the client group and the remaining iBGP peers will be members of the nonclient group for the local route reflector.

•send-community—Specifies that a community attribute be sent to a BGP neighbor. To remove the entry, use the no form of this command.

•soft-reconfiguration—Configures the Cisco NX-OS software to start storing updates. To not store received updates, use the no form of this command. Default: Disabled. Entering this command starts the storage of updates, which is required to do inbound soft reconfiguration. Outbound BGP soft reconfiguration does not require inbound soft reconfiguration to be enabled.

To use soft reconfiguration, or soft reset, without preconfiguration, both BGP peers must support the soft route refresh capability, which is advertised in the open message sent when the peers establish a TCP session. Clearing the BGP session using the soft-reconfiguration command has a negative effect on network operations and should only be used as a last resort.

To determine whether a BGP router supports this capability, use the show ip bgp neighbors command. If a router supports the route refresh capability, the following message is displayed:

Received route refresh capability from peer.

If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Similar to peer-session templates, peer-policy templates are configured once and applied to many neighbors through the direct application of a peer-policy template or through inheritance from peer-policy templates. The configuration of peer-policy templates simplifies the configuration of BGP policy commands that are applied to all neighbors within an autonomous system.

Peer-policy templates support direct and indirect inheritance from up to eight peer-policy templates. Inherited peer-policy templates are configured with sequence numbers like route-maps. An inherited peer-policy template, like a route-map, is evaluated starting with the inherit statement with the lowest sequence number and ending with the highest sequence number. However, there is a difference; a peer-policy template will not fall through like a route-map. Every sequence is evaluated, and if a BGP policy command is reapplied with different value, it will overwrite any previous value from a lower sequence number.

Peer-policy templates support only general policy commands. BGP policy configuration commands that are configured only for specific address families or NLRI configuration modes are configured with peer-policy templates.

---

Note A BGP neighbor cannot be configured to work with both peer groups and peer templates. A BGP neighbor can be configured to belong only to a peer group or to inherit policies from only peer templates.

---

Peer-session Templates

Peer-session templates are used to group and apply the configuration of general session commands to groups of neighbors that share common session configuration elements. General session commands that are common for neighbors that are configured in different address families can be configured within the same peer-session template. Peer-session templates are created and configured in peer session configuration mode. Only general session commands can be configured in a peer-session template.

When you enter the peer-session template configuration mode, the following commands are available:

•description description—Configures a description to be displayed by the local or a peer router. You can enter up to 80 characters including spaces.

•disable-connected-check—Disables connection verification for eBGP peers no more than one hop away when the eBGP peer is configured with a loopback interface.

•ebgp-multihop—Accepts and attempts BGP connections to external peers that reside on networks that are not directly connected.

---

Note You should enter this command under the guidance of Cisco technical support staff only.

---

•exit—Exits current configuration mode.

•inherit peer-session session-name—Configures a peer-session template to inherit the configuration from another peer-session template, use the peer-session keywords. To remove an inherit statement from a peer-session template, use the no form of this command.

•local-as—Allows you to customize the autonomous system number for eBGP peer groupings.

•neighbor inherit peer-session—Configures a router to send a peer session template to a neighbor so that the neighbor can inherit the configuration.

•neighbor translate-update—Upgrades a router running BGP in the NLRI format to support multiprotocol BGP.

•password—Enables MD5 authentication on a TCP connection between two BGP peers. The following configuration tools are available:

–0 password—Specifies an unencrypted neighbor password.

–3 password—Specifies an 3DES encrypted neighbor password

–password—Specifies an unencrypted (cleartext) neighbor password

•remote-private-as—Removes the private AS number from outbound updates.

•show ip bgp template peer-policy—Displays the locally configured peer policy templates.

•show ip bgp template peer-session—Displays the locally configured peer session templates.

•shutdown—Disables a neighbor or peer group.

•timers keepalive-time—Configures keepalive and hold timers in seconds. Range: 0 to 3600. Default: 60.

•update-source {ethernet mod/port | loopback virtual-interface | port-channel number[.sub-interface]}—Specifies the source of the BGP session and updates. Range: virtual-interface is 0 to 1023; number is 0 to 4096; (optional) .sub-interface is 1 to 4093.

General session commands can be configured once in a peer-session template and then applied to many neighbors through the direct application of a peer-session template or through indirect inheritance from a peer-session template. The configuration of peer-session templates simplify the configuration of general session commands that are commonly applied to all neighbors within an autonomous system.

Peer-session templates support direct and indirect inheritance. A peer can be configured with only one peer-session template at a time, and that peer-session template can contain only one indirectly inherited peer-session template. However, each inherited session template can also contain one indirectly inherited peer-session template. So, only one directly applied peer-session template and up to seven additional indirectly inherited peer-session templates can be applied, allowing you to apply up to a maximum of eight peer session configurations to a neighbor: the configuration from the directly inherited peer-session template and the configurations from up to seven indirectly inherited peer-session templates. Inherited peer-session templates are evaluated first, and the directly applied template will be evaluated and applied last. So, if a general session command is reapplied with a different value, the subsequent value will have priority and overwrite the previous value that was configured in the indirectly inherited template.

Peer-session templates support only general session commands. BGP policy configuration commands that are configured only for specific address families or NLRI configuration modes are configured with peer-policy templates.

This command requires the Enterprise Services license.

Examples

The following example creates a peer-session template named CORE1. This example inherits the configuration of the peer-session template named INTERNAL-BGP.

switch(config-router)# template peer-session CORE1

switch(config-router-stmp)#

The following example shows how to create and configure a peer-policy template named CUSTOMER-A:

switch(config-router)# template peer-policy CUSTOMER-A

switch(config-router-ptmp)# exit

switch(config-router)# route-map SET-COMMUNITY in

switch(config-router)# filter-list 20 in 

switch(config-router)# inherit peer-policy PRIMARY-IN 20

switch(config-router)# inherit peer-policy GLOBAL 10

switch(config-router)# exit-peer-policy

switch(config-router)#

The following example shows that the maximum prefixes that will be accepted from the 192.168.1.1 neighbor is set to 1000:

switch(config)# router bgp 40000 

switch(config-router) network 192.168.0.0 

switch(config-router)# maximum-prefix 1000 

The following example shows that the maximum number of prefixes that will be accepted from the 192.168.2.2 neighbor is set to 5000. The router is also configured to display warning messages when 50 percent of the maximum-prefix limit (2500 prefixes) has been reached.

switch(config)# router bgp 40000 

switch(config-router) network 192.168.0.0 

switch(config-router)# maximum-prefix 5000 50 

The following example shows that the maximum number of prefixes that will be accepted from the 192.168.3.3 neighbor is set to 2000. The router is also configured to reestablish a disabled peering session after 30 minutes.

switch(config)# router bgp 40000 

switch(config-router) network 192.168.0.0 

switch(config-router)# neighbor 192.168.3.3 maximum-prefix 2000 restart 30 

The following example shows that the warning messages is displayed when the maximum-prefix limit (500) for the 192.168.4.4 neighbor is exceeded:

switch(config)# router bgp 40000 

switch(config-router)# network 192.168.0.0 

switch(config-router)# maximum-prefix 500 warning-only 

The following example forces all updates destined for 10.108.1.1 to advertise this router as the next hop:

switch(config)# router bgp 40000 

switch(config-router)# next-hop-self

The following router configuration mode example, the router belongs to autonomous system 109 and is configured to send the communities attribute to its neighbor at IP address 172.16.70.23:

switch(config)# router bgp 40000 

switch(config-router)# send-community

The following address family configuration mode example, the router belongs to autonomous system 109 and is configured to send the communities attribute to its neighbor at IP address 172.16.70.23:

switch(config)# router bgp 400 

switch(config-router)# address-family ipv4 multicast

switch(config-router-af)# send-community

The following example enables inbound soft reconfiguration for the neighbor 10.108.1.1. All the updates received from this neighbor will be stored unmodified, regardless of the inbound policy. When inbound soft reconfiguration is done later, the stored information will be used to generate a new set of inbound updates.

switch(config)# router bgp 100 

switch(config-router)# soft-reconfiguration inbound

Related Commands

Command	Description
router bgp	Enters the assign an autonomous system (AS) number to a router and enters the router BGP configuration mode
address-family	Enters the address family mode for the Border Gateway Protocol (BGP).

test forwarding distribution perf

To test the forwarding distribution performance of the Forwarding Information Base (FIB), use the test forwarding distribution perf command.

test forwarding distribution perf

Syntax Description

This command has no keywords or arguments.

Defaults

None

Command Modes

Any

Supported User Roles

Network Administrator
VDC Administrator

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

This command does not require a license.

Examples

This example shows how to test the forwarding distribution performance:

switch# test forwarding distribution perf

Related Commands

Command	Description
show forwarding distribution	Displays information about the FIB.

test forwarding inconsistency

To trigger the Layer 3 inconsistency checker for the Forwarding Information Base (FIB), use the test forwarding inconsistency command.

test forwarding inconsistency [ip | ipv4] [unicast] [vrf vrf-name] [module {slot| all}] [stop]

Syntax Description

ip	(Optional) Specifies the inconsistency check for IPv4 routes.
ipv4	(Optional) Specifies the inconsistency check for IPv4 routes.
unicast	(Optional) Specifies the inconsistency check for unicast routes.
module	(Optional) Specifies the inconsistency check for one or more modules.
slot	Module number. The range depends on the platform.
all	(Optional) Specifies the inconsistency check for all modules.
stop	(Optional) Stops the inconsistency check.

Defaults

None

Command Modes

Any

Supported User Roles

Network Administrator
VDC Administrator

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

This command does not require a license.

Examples

This example shows how to trigger the Layer 3 inconsistency checker for all modules:

switch# test forwarding inconsistency module all 

This example shows how to stop the Layer 3 inconsistency checker for all modules:

switch# test forwarding inconsistency module all stop

Related Commands

Command	Description
show forwarding distribution	Displays information about the FIB.

timers (GLBP)

To configure the time between hello packets sent by the Gateway Load Balancing Protocol (GLBP) gateway and the time that the virtual gateway and virtual forwarder information is considered valid, use the timers command. To return the timers to the default values, use the no form of this command.

timers [msec] hellotime [msec] holdtime

no timers

Syntax Description

msec	(Optional) Specifies that the following (hellotime or holdtime) argument value will be expressed in milliseconds.
hellotime	Hello interval. The range is from 1 to 60 seconds. The default is 3 seconds (3000 milliseconds).
holdtime	Time before the virtual gateway and virtual forwarder information contained in the hello packet is considered invalid. The range is from 2 to 180 seconds. The default is 10 seconds (10,000 milliseconds).

Defaults

hellotime: 3 seconds
holdtime: 10 seconds

Command Modes

GLBP configuration

Supported User Roles

Network Administrator
VDC Administrator

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

If you do not configure timers on a gateway, the gateway learns the timer values from the active virtual gateway (AVG). The timers configured on the AVG always override any other timer settings. All gateways in a GLBP group should use the same timer values. If a GLBP gateway sends a hello message, the information should be considered valid for one holdtime. Typically, the holdtime is greater than three times the value of the hello time, (holdtime > 3 * hellotime). The range of values for the holdtime force the holdtime to be greater than the hello time.

This command does not require a license.

Examples

This example shows how to configure the timers for GLBP group 10 on Ethernet interface 1/1:

switch(config)# interface ethernet 1/1

switch(config-if)# glbp 10 

switch(config-glbp)# timers 5 18 

Related Commands

Command	Description
glbp	Enters GLBP configuration mode and creates a GLBP group.
timers redirect	Configures the redirect and timeout values for the GLBP group.

timers active-time

To adjust the Enhanced Interior Gateway Routing Protocol (EIGRP) time limit for the active state, use the timers active-time command. To disable this function, use the no form of the command.

timers active-time [time-limit | disabled]

no timers active-time

Syntax Description

time-limit	(Optional) Active time limit (in minutes). The range is from 1 to 65535 minutes. The default value is 3.
disabled	(Optional) Disables the timers and permits the routing wait time to remain active indefinitely.

Defaults

Disabled

Command Modes

Address family configuration
Router configuration
Router VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers active-time command to control the time that the router waits (after a query is sent) before declaring the route to be in the stuck in active (SIA) state.

This command requires the Enterprise Services license.

Examples

The following example shows how to configure an indefinite routing wait time on the specified EIGRP route:

switch(config)# router eigrp 1

switch(config-router) address-family ipv4 unicast

switch(config-router-af)# timers active-time disabled

timers basic

To adjust the Routing Information Protocol (RIP) network timers, use the timers basic command in router address-family configuration mode. To restore the default timers, use the no form of this command.

timers basic update invalid holddown flush

no timers basic

Syntax Description

update	Rate (in seconds) at which updates are sent. The default is 30 seconds.
invalid	Interval of time (in seconds) after which a route is declared invalid; it should be at least three times the value of the update argument. A route becomes invalid when no updates refresh the route. The route then enters into a holddown state where it is marked as inaccessible and advertised as unreachable. However, the route is still used to forward packets. The default is 180 seconds.
holddown	Interval (in seconds) during which routing information regarding better paths is suppressed; it should be at least three times the value of the update argument. A route enters into a holddown state when an update packet is received that indicates that the route is unreachable. The route is marked as inaccessible and advertised as unreachable. However, the route is still used to forward packets. When holddown expires, routes advertised by other sources are accepted and the route is no longer inaccessible. The default is 180 seconds.
flush	Amount of time (in seconds) that must pass before the route is removed from the routing table; the interval specified should be greater than the sum of the invalid argument plus the holddown argument. If it is less than this sum, the proper holddown interval cannot elapse, which results in a new route being accepted before the holddown interval expires. The default is 240 seconds.

Defaults

update: 30 seconds
invalid: 180 seconds
holddown: 180 seconds
flush: 240 seconds

Command Modes

Router address-family configuration

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

You can modify the basic timing parameters for RIP. These timers must be the same for all routers and servers in the network.

---

Note You can view the current and default timer values by using the show ip protocols command.

---

This command does not require a license.

Examples

The following example shows how to set updates to broadcast every 5 seconds. If Cisco NX-OS does not hear from a router in 15 seconds (the invalid time), it declares the route as unusable. Cisco NX-OS suppresses further information for an additional 15 seconds (the holddown time). At the end of the suppression period, Cisco NX-OS flushes the route from the routing table.

switch(config)# router rip Enterprise

switch(config-router)# address-family ipv4 unicast

switch(config-router-af)# timers basic 5  15  15  30 

Related Commands\

Command	Description
address-family	Enters address-family configuration mode.

timers lsa-arrival (OSPF)

To set the minimum interval in which the software accepts the same link-state advertisement (LSA) from Open Shortest Path First (OSPF) neighbors, use the timers lsa-arrival command. To return to the default, use the no form of this command.

timers lsa-arrival milliseconds

no timers lsa-arrival

Syntax Description

milliseconds

Minimum delay (in milliseconds) that must pass between acceptance of the same LSA arriving from neighbors. The range is from 10 to 600,000 milliseconds. The default is 1000 milliseconds.

Defaults

1000 milliseconds

Command Modes

Router configuration
VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers lsa arrival command to configure the minimum interval for accepting the same LSA. The same LSA is an LSA instance that contains the same LSA ID number, LSA type, and advertising router ID. If an instance of the same LSA arrives sooner than the interval that is set, the software drops the LSA.

We recommend that you keep the milliseconds value of the timers lsa-arrival command less than or equal to the neighbors' hold-interval value of the timers throttle lsa command.

This command requires the Enterprise Services license.

Examples

The following example shows how to set the minimum interval for accepting the same LSA at 2000 milliseconds:

switch(config)# router ospf 1

switch(config-router)# timers lsa-arrival 2000

Related Commands

Command	Description
show ip ospf timers rate-limit	Displays all of the LSAs in the rate-limit queue.
timers throttle lsa	Sets rate-limiting values for LSAs being generated.

timers lsa-arrival (OSPFv3)

To set the minimum interval in which the software accepts the same link-state advertisement (LSA) from Open Shortest Path First version 3 (OSPFv3) neighbors, use the timers lsa-arrival command. To return to the default, use the no form of this command.

timers lsa-arrival milliseconds

no timers lsa-arrival

Syntax Description

milliseconds

Minimum delay (in milliseconds) that must pass between acceptance of the same LSA arriving from neighbors. The range is from 10 to 600,000 milliseconds. The default is 1000 milliseconds.

Defaults

1000 milliseconds

Command Modes

Router configuration
VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers lsa arrival command to configure the minimum interval for accepting the same LSA. The same LSA is an LSA instance that contains the same LSA ID number, LSA type, and advertising router ID. If an instance of the same LSA arrives sooner than the interval that is set, the software drops the LSA.

We recommend that you keep the milliseconds value of the timers lsa-arrival command less than or equal to the neighbors' hold-interval value of the timers throttle lsa command.

This command requires the Enterprise Services license.

Examples

This example shows how to set the minimum interval for accepting the same LSA at 2000 milliseconds:

switch(config)# router ospfv3 1

switch(config-router)# timers lsa-arrival 2000

Related Commands

Command	Description
show ospfv3 timers rate-limit	Displays all of the LSAs in the rate-limit queue.
timers throttle lsa	Sets rate-limiting values for LSAs being generated.

timers lsa-group-pacing (OSPF)

To change the interval at which Open Shortest Path First (OSPF) link-state advertisements (LSAs) are collected into a group and refreshed, checksummed, or aged, use the timers lsa-group-pacing command. To return to the default, use the no form of this command.

timers lsa-group-pacing seconds

no timers lsa-group-pacing

Syntax Description

seconds

Time (in seconds) in the interval in which LSAs are grouped and refreshed, checksummed, or aged. The range is from 1 to 1800 seconds. The default value is 240 seconds.

Defaults

The default interval for this command is 240 seconds. OSPF LSA group pacing is enabled by default.

Command Modes

Router configuration
VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers lsa-group-pacing command to control the rate at which LSA updates occur and reduce the high CPU or buffer utilization that can occur when an area is flooded with a very large number of LSAs. The default settings for OSPF packet pacing timers are suitable for the majority of OSPF deployments. Do not change the packet pacing timers unless you have tried all other options to meet OSPF packet flooding requirements. You should try summarization, stub area usage, queue tuning, and buffer tuning before changing the default flooding timers. There are no guidelines for changing timer values; each OSPF deployment is unique and should be considered on a case-by-case basis.

Cisco NX-OS groups the periodic refresh of LSAs to improve the LSA packing density for the refreshes in large topologies. The group timer controls the interval used for group refreshment of LSAs; however, this timer does not change the frequency that individual LSAs are refreshed (the default refresh rate is every 30 minutes).

The duration of the LSA group pacing is inversely proportional to the number of LSAs that the router is handling. For example, if you have about 10,000 LSAs, you should decrease the pacing interval. If you have a very small database (40 to 100 LSAs), you should increase the pacing interval to 10 to 20 minutes.

This command requires the Enterprise Services license.

Examples

The following example shows how to configure OSPF group packet-pacing updates between LSA groups to occur in 60-second intervals for OSPF routing process 1:

switch(config)# router ospf 1

switch(config-router)# timers lsa-group-pacing 60

Related Commands

Command	Description
show ip ospf	Displays general information about OSPF routing processes.

timers lsa-group-pacing (OSPFv3)

To change the interval at which Open Shortest Path First version 3 (OSPFv3) link-state advertisements (LSAs) are collected into a group and refreshed, checksummed, or aged, use the timers lsa-group-pacing command. To return to the default, use the no form of this command.

timers lsa-group-pacing seconds

no timers lsa-group-pacing

Syntax Description

seconds

Time (in seconds) in the interval in which LSAs are grouped and refreshed, checksummed, or aged. The range is from 1 to 1800 seconds. The default value is 240 seconds.

Defaults

The default interval for this command is 240 seconds. OSPFv3 LSA group pacing is enabled by default.

Command Modes

Router configuration
VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers lsa-group-pacing command to control the rate at which LSA updates occur and reduce the high CPU or buffer utilization that can occur when an area is flooded with a very large number of LSAs. The default settings for OSPFv3 packet pacing timers are suitable for the majority of OSPFv3 deployments. Do not change the packet pacing timers unless you have tried all other options to meet OSPFv3 packet flooding requirements. You should try summarization, stub area usage, queue tuning, and buffer tuning before changing the default flooding timers. There are no guidelines for changing timer values; each OSPFv3 deployment is unique and should be considered on a case-by-case basis.

Cisco NX-OS groups the periodic refresh of LSAs to improve the LSA packing density for the refreshes in large topologies. The group timer controls the interval used for group refreshment of LSAs; however, this timer does not change the frequency that individual LSAs are refreshed (the default refresh rate is every 30 minutes).

The duration of the LSA group pacing is inversely proportional to the number of LSAs that the router is handling. For example, if you have about 10,000 LSAs, you should decrease the pacing interval. If you have a very small database (40 to 100 LSAs), you should increase the pacing interval to 10 to 20 minutes.

This command requires the Enterprise Services license.

Examples

This example shows how to configure OSPFv3 group packet-pacing updates between LSA groups to occur in 60-second intervals for OSPFv3 routing process 1:

switch(config)# router ospfv3 1

switch(config-router)# timers lsa-group-pacing 60

Related Commands

Command	Description
show ospfv3	Displays general information about OSPFv3 routing processes.

timers nsf converge

To adjust the time limit for nonstop forwarding (NSF) convergence for the Enhanced Interior Gateway Routing Protocol (EIGRP), use the timers nsf converge command. To disable this function, use the no form of the command.

timers nsf converge seconds

no timers nsf converge

Syntax Description

seconds

Time limit for convergence after an NSF switchover (in seconds). The range is from 60 to 180 seconds. The default value is 120.

Defaults

120 seconds

Command Modes

Address family configuration
Router configuration
Router VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers nsf converge command to control the time that the router waits for convergence after a switchover.

This command requires the Enterprise Services license.

Examples

The following example shows how to configure the NSF convergence time for EIGRP:

switch(config)# router eigrp 1

switch(config-router) address-family ipv4 unicast

switch(config-router-af)# timers nsf converge 100

timers nsf route-hold

To set the timer that determines how long an NSF-aware Enhanced Interior Gateway Routing Protocol (EIGRP) router holds routes for an inactive peer, use the timers nsf route-hold command. To return the route hold timer to the default value, use the no form of this command.

timers nsf route-hold seconds

no timers nsf route-hold

Syntax Description

seconds

Time, in seconds, that EIGRP holds routes for an inactive peer. The range is from 20 to 300 seconds. The default is 240.

Defaults

EIGRP NSF awareness is enabled.
seconds: 240

Command Modes

Address family configuration
Router configuration
Router VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers nsf route-hold command to set the maximum period of time that the NSF-aware router holds known routes for an NSF-capable neighbor during a switchover operation or a well-known failure condition. The route hold timer is configurable so that you can tune network performance and avoid undesired effects, such as "black holing" routes (advertising invalid routes) if the switchover operation takes too much time. When this timer expires, the NSF-aware router scans the topology table and discards any stale routes, allowing EIGRP peers to find alternate routes instead of waiting during a long switchover operation.

This command requires the Enterprise Services license.

Examples

The following example shows how to set the route hold timer value for an NSF-aware router to 2 minutes (120 seconds):

switch(config)# router eigrp 1

switch(config-router) address-family ipv4 unicast

switch(config-router-af)# timers nsf route-hold 120

timers nsf signal

To set the time limit to signal a nonstop forwarding (NSF) restart for the Enhanced Interior Gateway Routing Protocol (EIGRP), use the timers nsf signal command. To return the route hold timer to the default, use the no form of this command.

timers nsf signal seconds

no timers nsf signal

Syntax Description

seconds

Time, in seconds, that EIGRP waits for a peer to signal an NSF restart. The range is from 10 to 30 seconds. The default is 20.

Defaults

EIGRP NSF awareness is enabled.
seconds: 20

Command Modes

Address family configuration
Router configuration
Router VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers nsf signal command to set the maximum period of time that the NSF-aware router waits for an NSF-capable neighbor to signal a restart.

This command requires the Enterprise Services license.

Examples

The following example shows how to set the signal timer value for an NSF-aware router to the maximum (30 seconds):

switch(config)# router eigrp 1

switch(config-router) address-family ipv4 unicast

switch(config-router-af)# timers nsf signal 30

timers redirect

To configure the time interval in which the active virtual gateway (AVG) for a Gateway Load Balancing Protocol (GLBP) group continues to redirect clients to a secondary active virtual forwarder (AVF), use the timers redirect command. To return the redirect timers to the default values, use the no form of this command.

timers redirect redirect timeout

no timers redirect redirect timeout

Syntax Description

redirect	Redirect timer interval, in seconds. The range is from 0 to 3600 seconds. The default is 300 seconds (5 minutes).
timeout	Time, in seconds, before the secondary virtual forwarder becomes unavailable. The range is from 610 to 64800 seconds. The default is 14,400 seconds (4 hours).

Defaults

redirect: 300 seconds
timeout: 14,400 seconds

Command Modes

GLBP configuration

Supported User Roles

Network Administrator
VDC Administrator

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

A virtual forwarder that is assigned a virtual MAC address by the AVG is referred to as a primary virtual forwarder. If the virtual forwarder learned the virtual MAC address from hello messages, it is referred to as a secondary virtual forwarder.

You can use the redirect timer to set a time delay that starts when a forwarder fails on the network and the AVG assumes that the forwarder will not return. When you set a time delay, the virtual MAC address that the forwarder replies to is still in the Address Resolution Protocol (ARP) replies, but the actual forwarding task is handled by another group in the GLBP group.

The timeout interval is the time delay that begins when a forwarder fails on the network and the MAC address that the forwarder was responsible for becomes inactive on all of the routers in the GLBP group. After the timeout interval, packets sent to this virtual MAC address will be lost. You must configure a timeout interval that is long enough to allow all hosts to refresh the ARP cache entry that contained the virtual MAC address.

This command does not require a license.

Examples

This example shows how to configure the redirect and timeout values for GLBP group 1 on Ethernet interface 1/1:

switch(config)# interface ethernet 1/1

switch(config-if)# glbp 10 

switch(config-glbp)# timers redirect 600 7200 

switch(config-glbp)# ip 

Related Commands

Command	Description
glbp	Enters GLBP configuration mode and creates a GLBP group.
timers	Configures hello and hold timers for GLBP.

timers throttle lsa (OSPF)

To set rate-limiting values for Open Shortest Path First (OSPF) link-state advertisement (LSA) generation, use the timers throttle lsa command. To return to the default values, use the no form of this command.

timers throttle lsa {network | router} hold-interval

no timers throttle lsa {network | router}

Syntax Description

network	Specifies rate limiting network LSAs
router	Specifies rate limiting router LSAs
hold-interval	Incremental time (in milliseconds) that is used to calculate the subsequent rate limiting times for LSA generation. The range is from 1 to 600,000 milliseconds. The default value is 5000 milliseconds.

Defaults

hold-interval: 5000 milliseconds

Command Modes

Router configuration
VRF configuration

Supported User Roles

network-admin
vdc-admin

Command History

Release	Modification
4.0(1)	This command was introduced.

Usage Guidelines

Use the timers throttle lsa command to rate-limit LSA generation.

This command requires the Enterprise Services license.

Examples

This example shows how to customize OSPF network LSA throttling:

switch(config)# router ospf 1

switch(config-router)# timers throttle lsa network 10000

Related Commands

Command	Description
show ip ospf	Displays information about OSPF routing processes.
timers lsa arrival	Sets the minimum interval at which the software accepts the same LSA from OSPF neighbors.

timers throttle lsa (OSPFv3)

To set rate-limiting values for Open Shortest Path First version 3 (OSPFv3) link-state advertisement (LSA) generation, use the timers throttle lsa command. To return to the default values, use the no form of this command.

timers throttle lsa {intra-area-prefix | link | network | router} hold-interval

no timers throttle lsa {network | router}

Syntax Description

intra-area-prefix

Specifies rate limitin