Technical Documentation

passive

Syntax

passive {traffic-engineering {remote-node-id address;}}

Hierarchy Level

[edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name],[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name],[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],[edit protocols (ospf | ospf3) area area-id interface interface-name],[edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name],[edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name],[edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast) area area-id interface interface-name]

Release Information

Statement introduced before JUNOS Release 7.4.

traffic-engineering and remote-node-id address statements introduced in JUNOS Release 8.0.

traffic-engineering and remote-node-id address statements introduced in JUNOS Release 8.0 for EX Series switches.

Statement introduced in JUNOS Release 9.0 for EX Series switches.

Support for the realm statement introduced in JUNOS Release 9.2.

Support for the realm statement introduced in JUNOS Release 9.2 for EX Series switches.

Description

Advertise the direct interface addresses on an interface without actually running OSPF on that interface. A passive interface is one for which the address information is advertised as an internal route in OSPF, but on which the protocol does not run.

To configure an interface in OSPF passive traffic engineering mode, include the traffic-engineering statement. Configuring OSPF passive traffic engineering mode enables the dynamic discovery of OSPF AS boundary routers.

Enable OSPF on an interface by including the interface statement at the [edit protocols (ospf | ospf3) area area-id] or the [edit routing-instances routing-instance-name protocols ospf area area-id] hierarchy levels. Disable it by including the disable statement, To prevent OSPF from running on an interface, include the passive statement. These three states are mutually exclusive.

Required Privilege Level

routing—To view this statement in the configuration.

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


Published: 2010-04-14