Supported Platforms
Related Documentation
- EX, J, M, MX, PTX, QFX, T Series
- indirect-next-hop-change-acknowledgements
- J, M, PTX, SRX, T Series
- Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding Engine
krt-nexthop-ack-timeout
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 12.2.
Description
For indirect next-hop and multicast next-hop change acknowledgements, configure the time interval for which to wait for the next-hop acknowledgement. The routing protocol process (rpd) waits for the specified time period before changing the route to point to the new next hop.
If the acknowledgement is not received within the time period, it is assumed to have been received and the route is made to point to the new next hop.
Options
interval—Kernel next-hop acknowledgement timeout interval.
Range: 1 through 100 seconds
Default: 1 second
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- EX, J, M, MX, PTX, QFX, T Series
- indirect-next-hop-change-acknowledgements
- J, M, PTX, SRX, T Series
- Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding Engine
Published: 2013-07-23
Supported Platforms
Related Documentation
- EX, J, M, MX, PTX, QFX, T Series
- indirect-next-hop-change-acknowledgements
- J, M, PTX, SRX, T Series
- Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding Engine