virtual-link
Syntax
virtual-link neighbor-id router-id transit-area area-id {
disable;
authentication key <key-id identifier>;
dead-interval seconds;
hello-interval seconds;
ipsec-sa name;
retransmit-interval seconds;
transit-delay seconds;
}
Hierarchy Level
[edit logical-systems
logical-system-name protocols (ospf | ospf3)
area area-id],
[edit logical-systems
logical-system-name routing-instances
routing-instance-name protocols
ospf
area area-id],
[edit protocols (ospf | ospf3)
area area-id],
[edit routing-instances
routing-instance-name protocols ospf
area area-id]
Release Information
Statement introduced before Junos OS Release 7.4.
Description
For backbone areas only, create a virtual link
to use in place of an actual physical link. All area border routers
and other routing devices on the backbone must be contiguous. If this
is not possible and there is a break in OSPF connectivity, use virtual
links to create connectivity to the OSPF backbone. When configuring
virtual links, you must configure links on the two routing devices
that form the end points of the link, and both of these routing devices
must be area border routers. You cannot configure links through stub
areas.
Options
neighbor-id router-id—IP address of the routing device at the remote end
of the virtual link.
transit-area area-id—Area identifier of the area through which the virtual
link transits. Virtual links are not allowed to transit the backbone
area.
ipsec-sa name—Apply the named IPsec authentication to the OSPF interface
or virtual link or to an OSPFv2 remote sham link.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing—To view this statement in the
configuration.
routing-control—To add this statement to the configuration.
