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

traffic-engineering

See the following sections:

traffic-engineering (OSPF)

Syntax

traffic-engineering {
advertise-unnumbered-interfaces;
ignore-lsp-metrics;
multicast-rpf-routes;
no-topology;
shortcuts {
lsp-metric-into-summary;
}
}

Hierarchy Level

[edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)],
[edit protocols (ospf | ospf3)],
[edit routing-instances routing-instance-name protocols (ospf | ospf3)]

Release Information

Statement introduced before JUNOS Release 7.4.

multicast-rpf-routes option introduced in JUNOS Release 7.5.

advertise-unnumbered-interfaces option introduced in JUNOS Release 8.5.

Support for OSPFv3 (ospf3) introduced in JUNOS Release 9.4.

Description

Enable the OSPF traffic engineering features.

Default

Traffic engineering support is disabled.

Options

advertise-unnumbered-interfaces—(Optional) (OSPFv2 only) Include the link-local identifier in the link-local TE link-state advertisement. You do not need to include this statement if the Resource Reservation Protocol (RSVP) is able to signal unnumbered interfaces as defined in RFC 3477.

multicast-rpf-routes—(Optional) (OSPFv2 only) Install routes for multicast RPF checks into the inet.2 routing table.

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

The remaining statements are explained separately.

Usage Guidelines

See Enabling OSPF Traffic Engineering Support.

Required Privilege Level

routing—To view this statement in the configuration.

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

traffic-engineering (Passive TE Mode)

Syntax

traffic-engineering {
remote-note-id address;
}

Hierarchy Level

[edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name passive],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name passive],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name passive],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name passive],
[edit protocols (ospf | ospf3) area area-id interface interface-name passive],
[edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name passive],
[edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name passive],
[edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name passive]

Release Information

Statement introduced in JUNOS Release 8.0.

Support for the realm statement introduced in JUNOS Release 9.2.

Description

Configure an interface in OSPF passive traffic engineering mode to enable dynamic discovery of OSPF AS boundary routers.

Default

OSPF passive TE mode is disabled.

Options

remote-node-id address—The IP address at the far end of the inter-AS link.

Usage Guidelines

See Configuring OSPF Passive Traffic Engineering Mode.

Required Privilege Level

routing—To view this statement in the configuration.

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

Related Topics

JUNOS MPLS Applications Configuration Guide

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

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.