Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


You must configure the fib-next-hop-split statement in conjunction with the egress-chaining and transit statements to enable route resolution over labeled IS-IS routes using flattened router next hops. Configuring the fib-next-hop-split statement alone does not have any effect.

When you configure the no-labeled-isis statement at the [edit routing-options forwarding-table chained-composite-next-hop transit] hierarchy level, the labeled IS-IS routes are flattened to ensure that the segment routing traffic-engineering (SPRING-TE) routes are not resolved any further over another composite next hop.



Create composite-chained next hops for labeled IS-IS routes.

In addition to enabling fib-next-hop-split, you can also configure egress-chaining to reduce the number of chained next hops present in a route that involves resolution over multiple routes with labels.

Required Privilege Level


Release Information

Statement introduced in Junos OS Release 20.4R1.