Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Supported Platforms

 

Related Documentation

 

overload (Protocols OSPF)

Syntax

overload {timeout seconds;}

Hierarchy Level

[edit logical-systems logical-system-name protocols (oospf | ospf3)],[edit logical-systems logical-system-name protocols ospf topology (default | ipv4-multicast | name)],[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3)],[edit logical systems logical-system-name routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name)],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)],[edit protocols (ospf | ospf3)],[edit protocols ospf topology (default | ipv4-multicast | name)],[edit protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)],[edit routing-instances routing-instance-name protocols (ospf | ospf3)],[edit routing-instances routing-instance-name protocols ospf topology (default | ipv4-multicast | name],[edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)],

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Support for Multitopology Routing introduced in Junos OS Release 9.0.

Support for Multitopology Routing introduced in Junos OS Release 9.0 for EX Series switches.

Support for the realm statement introduced in Junos OS Release 9.2.

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

Statement introduced in Junos OS Release 11.3 for the QFX Series.

Description

Configure the local routing device so that it appears to be overloaded. You might do this when you want the routing device to participate in OSPF routing, but do not want it to be used for transit traffic.

Note: Traffic destined to directly attached interfaces continues to reach the routing device.

Options

timeout seconds—(Optional) Number of seconds at which the overloading is reset. If no timeout interval is specified, the routing device remains in overload state until the overload statement is deleted or a timeout is set.

Range: 60 through 1800 seconds

Default: 0 seconds

Note: Multitopology Routing does not support the timeout option.

Required Privilege Level

routing—To view this statement in the configuration.

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

 

Related Documentation

 

Published: 2014-05-08

Supported Platforms

 

Related Documentation

 

Published: 2014-05-08

Previous Page Next Page