Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


Enable egress peer engineering to direct core service traffic such as MPLS RSVP to a specific single-hop egress BGP peer. The ingress BGP peer can traffic-engineer the core inet unicast and inet6 unicast service traffic using BGP labeled unicast towards a specific egress BGP peer, which is also the AS boundary router.

You can enable MPLS fast reroute (FRR) on the egress BGP peer, which has traffic engineering enabled. The AS boundary router switches to the backup path when the primary link fails. Specify a predefined template with one or more backup paths. You can define a template using the egress-te-backup-paths configuration statement and configure one or more backup path for MPLS FRR. The backup paths specified in the template must belong to the same address family as the BGP peer.



Enable traffic engineering on the egress peer.

backup-path backup-path

(Optional) Specify a predefined template that has the configured backup path for MPLS fast reroute.


Import policy to set attributes on the egress-te created route.


Host (/32 or /128) address to install egress-te route in inet[6].3 table.


Avoid installation to FIB or resolving over egress-te route.

rib (inet.0 | inet6.0)

Install egress-te route in inet[6].0 instead of inet[6].3

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 14.2R4.