Overload - Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual

Complete Software Guide for Junos

overload

Syntax
Hierarchy Level
Release Information
Description
Options
2134
®
OS for EX Series Ethernet Switches, Release 10.4
overload {
timeout seconds;
}
[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)],
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 statement introduced in Junos OS Release 9.2. for EX Series
realm
switches.
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 immediately attached interfaces continues to
reach the routing device.
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
statement is deleted or a timeout is set.
overload
Range: 60 through 1800 seconds
Default: 0 seconds
Copyright © 2010, Juniper Networks, Inc.