Supported Platforms
Related Documentation
- ACX, J, M, PTX, SRX, T Series
- Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding Engine
indirect-next-hop
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 8.2.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Description
Enable indirectly connected next hops for route convergence. This statement is implemented on the Packet Forward Engine to speed up forwarding information base (FIB) updates. Configuring this statement significantly speeds convergence times. The only downside of configuring this statement is that some additional FIB memory overhead is required. Unless routes have an extremely high number of next hops, this increased memory usage should not be noticeable.
 |
|
Default
Disabled.
Options
indirect-next-hop—Enable indirectly connected next hops.
no-indirect-next-hop—Explicitly disable indirect next hops.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, J, M, PTX, SRX, T Series
- Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding Engine
Published: 2013-01-17
Supported Platforms
Related Documentation
- ACX, J, M, PTX, SRX, T Series
- Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding Engine
