![](http://pdfasset.owneriq.net/8/48/8487ffbe-39e2-4a92-9bcd-73b9dbfe021c/8487ffbe-39e2-4a92-9bcd-73b9dbfe021c-bg58.png)
• Example: Configuring VPLS Pseudowires with Dynamic Profiles—Basic Solutions on
page 64
• Example: Configuring VPLS Pseudowires with Dynamic Profiles—Complex Solutions
on page 68
Example: Configuring VPLS Pseudowires with Dynamic Profiles—Basic Solutions
The following limitations apply to dynamic profiles for VPLS on MX Series routers:
•
The native-vlan-id statement is not supported.
•
The native-inner-vlan-id statement is not supported.
•
The interface-mode access statement option is not supported.
•
The vlan-id-range statement is not supported.
In many cases, a configuration using dynamic profiles is more efficient than a static
configuration, as shown by the examples in this topic.
•
VPLS Pseudowire Interfaces Without Dynamic Profiles on page 64
•
VPLS Pseudowire Interfaces and Dynamic Profiles on page 65
•
CE Routers Without Dynamic Profiles on page 66
•
CE Routers and Dynamic Profiles on page 67
VPLS Pseudowire Interfaces Without Dynamic Profiles
Consider the followingconfiguration, whichdoes not use dynamic profiles to manipulate
VLAN identifiers:
[edit routing-instances]
green {
instance-type vpls;
interface ge-0/0/1.1;
interface ge-0/0/2.1;
interface ge-0/0/3.1;
vlan-tags outer 200 inner 100;
protocols vpls {
vpls-id 10;
neighbor 10.1.1.20;
}
{...more...}
}
[edit interfaces]
ge-0/0/1 {
unit 0 {
vlan-id 10;
}
}
ge-0/0/2 {
unit 0 {
Copyright © 2010, Juniper Networks, Inc.64
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide