Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


traffic-engineering (OSPF)


Hierarchy Level


Enable the OSPF traffic engineering features.


Traffic engineering support is disabled.


advertise-unnumbered-interfaces—(Optional) (OSPFv2 only) Include the link-local identifier in the link-local traffic-engineering link-state advertisement. This statement must be included on both ends of an unnumbered link to allow an ingress LER to update the link in its traffic engineering database and use it for CSPF calculations. The link-local identifier is then used by RSVP to signal unnumbered interfaces as defined in RFC 3477.

credibility-protocol-preference—(Optional) (OSPFv2 only) Use the configured preference value for OSPF routes to calculate the traffic engineering database credibility value used to select IGP routes. Use this statement to override the default behavior, in which the traffic engineering database prefers IS-IS routes even if OSPF routes are configured with a lower, that is, preferred, preference value. For example, OSPF routes have a default preference value of 10, whereas IS-IS Level 1 routes have a default preference value of 15. When protocol preference is enabled, the credibility value is determined by deducting the protocol preference value from a base value of 512. Using default protocol preference values, OSPF has a credibility value of 502, whereas IS-IS has a credibility value of 497. Because the traffic engineering database prefers IGP routes with the highest credibility value, OSPF routes are now preferred.

ignore-lsp-metrics—(Optional) Ignore RSVP LSP metrics in OSPF traffic engineering shortcut calculations.

multicast-rpf-routes—(Optional) (OSPFv2 only) Install routes for multicast RPF checks into the inet.2 routing table. The inet.2 routing table consists of unicast routes used for multicast RPF lookup. RPF is an antispoofing mechanism used to check whether the packet is coming in on an interface that is also sending data back to the packet source.


You must enable OSPF traffic engineering shortcuts to use the multicast-rpf-routes statement. You must not allow LSP advertisements into OSPF when configuring the multicast-rpf-routes statement.

no-topology—(Optional) (OSPFv2 only) Disable the dissemination of the link-state topology information.

l3-unicast-topology—Download IGP topology information into the traffic engineering database (TED). In Junos OS, the IGPs install topology information into a database called the traffic engineering database. The traffic engineering database contains the aggregated topology information. The IGP routes are installed by the traffic engineering database on behalf of the corresponding IGP into a user-visible routing table called lsdist.0, subject to route policies.

The remaining statements are explained separately. See CLI Explorer.


When the OSPF traffic engineering configuration is considerably modified, the routing table entries are deleted and the routing table is recreated. Changes to configuration that can cause this behavior include enabling or disabling:

  • Traffic engineering shortcuts

  • IGP shortcuts

  • LDP tunneling

  • Multiprotocol LSP

  • Advertise summary metrics

  • Multicast RPF routes

Required Privilege Level

routing—To view this statement in the configuration.

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

Release Information

Statement introduced before Junos OS Release 7.4.

multicast-rpf-routes option introduced in Junos OS Release 7.5.

advertise-unnumbered-interfaces option introduced in Junos OS Release 8.5.

Support for OSPFv3 (ospf3) introduced in Junos OS Release 9.4.

Support for OSPFv3 (ospf3) introduced in Junos OS Release 9.4 for EX Series switches.

credibility-protocol-preference statement introduced in Junos OS Release 9.4.

credibility-protocol-preference statement introduced in Junos OS Release 9.4 for EX Series switches.

Support for l3-unicast-topology statement introduced in Junos OS Release 20.4R1.