Configuring Static Pseudowires For Vpls - Juniper EX9200 Features Manual

Related
Documentation

Configuring Static Pseudowires for VPLS

Copyright © 2016, Juniper Networks, Inc.
If this PE router does not select a best path after running the VPLS path selection
process, then the local PE router does not consider the remote site to exist.
When a VE device receives an advertisement for a Layer 2 NLRI that matches its own
site ID but the site is not multihomed, the pseudowire between the VE device and the
transmitting PE router transitions to a site collision state and is not considered to be up.
BGP Route Reflectors for VPLS on page 14
You can configure a VPLS domain using static pseudowires. A VPLS domain consists of
a set of PE routers that act as a single virtual Ethernet bridge for the customer sites
connected to these routers. By configuring static pseudowires for the VPLS domain, you
do not need to configure the LDP or BGP protocols that would normally be used for
signaling. However, if you configure static pseudowires, any changes to the VPLS network
topology have to be managed manually.
NOTE: In the VPLS documentation, the word router in terms such as PE router
is used to refer to any device that provides routing functions.
Static pseudowires require that you configure a set of in and out labels for each
pseudowire configured for the VPLS domain. You still need to configure a VPLS identifier
and neighbor identifiers for a static VPLS domain. You can configure both static and
dynamic neighbors within the same VPLS routing instance.
To configure a static pseudowire for a VPLS neighbor, include the
static (Protocols VPLS) {
incoming-label label;
outgoing-label label;
}
You must configure an incoming and outgoing label for the static pseudowire using the
and
incoming-label outgoing-label
pseudowire's incoming traffic and destination.
To configure a static pseudowire for a VPLS neighbor, include the
the
[edit routing-instances routing-instance-name protocols vpls neighbor address]
level.
You can also configure the
neighbor as static the backup must also be static) by including it at the
routing-instances routing-instance-name protocols vpls neighbor address backup-neighbor
address] hierarchy level and for a mesh group by including it at the
routing-instance-name protocols vpls mesh-group mesh-group-name neighbor address]
hierarchy level.
statements. These statements identify the static
static statement for a backup neighbor (if you configure the
Chapter 6: Configuring Pseudowires
statement:
static
static statement at
hierarchy
[edit
[edit routing-instances
59