backup-neighbor
Syntax backup-neighbor address {
community name;
mtu number;
hot-standby;
psn-tunnel-endpoint address;
standby;
static;
virtual-circuit-id number;
}
Hierarchy Level [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls neighbor address],
[edit protocols l2circuit local-switching interface interface-name],
[edit protocols l2circuit neighbor address interface interface-name],
[edit routing-instances routing-instance-name protocols vpls neighbor address]
Release Information Statement introduced in Junos OS Release 9.2.
Statement introduced in Junos OS Release 12.2 for ACX Series routers.
Statement introduced in Junos OS Release 12.3 at the [edit protocols l2circuit
local-switching interface interface-name] hierarchy level.
Description Configure pseudowire redundancy for Layer 2 circuits and VPLS. A redundant pseudowire
can act as a backup connection and can be configured between a PE router and a CE
device or between PE routers, maintaining Layer 2 circuit and VPLS services after certain
types of failures. This feature can help improve the reliability of certain types of networks
where a single point of failure could interrupt service for customers.
NOTE: VPLS is not supported on ACX Series routers. The psn-tunnel-endpoint
statement is not supported at the [edit protocols l2circuit local-switching
interface interface-name end-interface interface interface-name] hierarchy level.
Options address—Specifies the address for the backup neighbor.
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.
Related
Documentation
Configuring Pseudowire Redundancy on the PE Router on page 606•
1447Copyright © 2017, Juniper Networks, Inc.
Chapter 41: Configuration Statements