[Contents] [Prev] [Next] [Index] [Report an Error]

traffic-engineering

Syntax



traffic-engineering (bgp | bgp-igp | bgp-igp-both-ribs
| mpls-forwarding);

Hierarchy Level



[edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls]

Release Information

Statement introduced before JUNOS Release 7.4.

Description

Select whether MPLS performs traffic engineering on BGP destinations only or on both BGP and IGP destinations. Affects only LSPs originating from this router, not transit or egress LSPs.

Default

bgp

Options

bgp—On BGP destinations only. Ingress routes are installed in the inet.3 routing table.
bgp-igp—On both BGP and IGP destinations. Ingress routes are installed in the inet.0 routing table. If IGP shortcuts are enabled, the shortcut routes are automatically installed in the inet.0 routing table.
bgp-igp-both-ribs—On both BGP and IGP destinations. Ingress routes are installed in the inet.0 and inet.3 routing tables. This option is used to support VPNs.
mpls-forwarding—On both BGP and IGP destinations. Use ingress routes for forwarding only, not for routing.

Usage Guidelines

See Configuring Traffic Engineering for LSPs.

Required Privilege Level

routing—To view this statement in the configuration.

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

[Contents] [Prev] [Next] [Index] [Report an Error]