area
Syntax
area area-id {
interface interface-name {
no-eligible-remote-backup;
passive;
topology (ipv4-multicast | name) {
disable;
}
}
virtual-link neighbor-id router-id transit-area area-id {
topology (ipv4-multicast | name) {
disable;
}
}
}
Hierarchy Level
[edit logical-systems logical-system-name protocols (ospf | ospf3)], [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 ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)], [edit protocols (ospf | ospf3)], [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 ospf3 realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)]
Description
Specify the area identifier for this routing device to use when participating in OSPF routing. All routing devices in an area must use the same area identifier to establish adjacencies.
Specify multiple area statements to configure the
routing device as an area border router. An area border router does
not automatically summarize routes between areas. Use the area-range statement to configure route summarization. By definition, an area
border router must be connected to the backbone area either through
a physical link or through a virtual link. To create a virtual link,
include the virtual-link statement.
To specify that the routing device is directly connected to
the OSPF backbone, include the area 0.0.0.0 statement.
All routing devices on the backbone must be contiguous. If they
are not, use the virtual-link statement to create the appearance
of connectivity to the backbone.
You can also configure any interface that belongs to one or more topologies to advertise the direct interface addresses without actually running OSPF on that interface. By default, OSPF must be configured on an interface in order for direct interface addresses to be advertised as interior routes.
If you configure an interface with the passive statement, it applies to all the topologies to which the interface
belongs. You cannot configure an interface as passive for only one
specific topology and have it remain active for any other topologies
to which it belongs.
Options
area-id—Area identifier. The identifier can be up to 32 bits. It is common to specify the area number as a simple integer or an IP address. Area number 0.0.0.0 is reserved for the OSPF backbone area.
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.
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.
Support for the no-eligible-remote-backup statement
introduced in Junos OS Release 15.1.