Technical Documentation

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

Consider the following configuration, which does 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 {vlan-id 20;}}ge-0/0/3 {unit 0 {vlan-id 30;}}

Note: This is not a complete router configuration.

With this configuration, broadcast packets inside frames arriving with VLAN identifier 10 on ge-0/0/1 are normalized to a dual-tagged frame with an outer VLAN value of 200 and an inner VLAN value of 100. The broadcast packet and frames egressing ge-0/0/2 or ge-0/0/3 have the outer VLAN value stripped and the inner VLAN value swapped to 20 and 30 respectively, according to the interface configuration. However, this stripping of the outer VLAN tag and the swapping is extra work, because the frames will still egress the VPLS pseudowire in routing instance green with an outer VLAN tag value of 200 and an inner VLAN tag value of 100, also according to the configuration.

The same configuration can be accomplished more effectively using dynamic profiles.

VPLS Pseudowire Interfaces and Dynamic Profiles

Consider the following configuration, which uses 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-id 100; # Desired inner VLAN tag on the VPLS pseudowireprotocols vpls {vpls-id 10; neighbor 10.1.1.20 {associate-profile green_vpls_pw_1; # The profile}}{...more...}}[edit interfaces]ge-0/0/1 {unit 0 {vlan-id 10;}}ge-0/0/2 {unit 0 {vlan-id 20;}}ge-0/0/3 {unit 0 {vlan-id 30;}}[edit dynamic-profiles]green_vpls_pw_1 interfaces $junos-interface-ifd-name {unit $junos-underlying-unit-number {vlan-tags outer 200 inner 100;}}

Note: This is not a complete router configuration.

With this configuration, broadcast packets inside frames arriving with VLAN identifier 10 on ge-0/0/1 are normalized to a frame with VLAN identifier 100. The broadcast packet and frames egressing ge-0/0/2 or ge-0/0/3 have this VLAN value swapped to 20 and 30 respectively, according to the interface configuration. Frames egress the VPLS pseudowire in routing instance green with an outer VLAN tag value of 200 pushed on top of the normalized value.

CE Routers Without Dynamic Profiles

You can apply a dynamic profile to an entire VPLS configuration, not just a neighbor.

Consider the following configuration, which does not use dynamic profiles to manipulate VLAN identifiers on a customer edge (CE) router with VLAN identifier 100:

[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 100;}}ge-0/0/2 {unit 0 {vlan-id 100;}}ge-0/0/3 {unit 0 {vlan-id 100;}}

Note: This is not a complete router configuration.

With this configuration, broadcast packets inside frames arriving on ge-0/0/1 are normalized to a dual-tagged frame with an outer VLAN value of 200 and an inner VLAN value of 100. The same configuration can be accomplished using dynamic profiles.

CE Routers and Dynamic Profiles

Consider the following configuration, which uses dynamic profiles at the protocols level:

[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-id 100; # Desired inner VLAN tag on the VPLS pseudowireprotocols vpls {associate-profile green_vpls_pw_2; # The profilevpls-id 10; neighbor 10.1.1.20;}{...more...}}[edit interfaces]ge-0/0/1 {unit 0 {vlan-id 100;}}ge-0/0/2 {unit 0 {vlan-id 100;}}ge-0/0/3 {unit 0 {vlan-id 100;}}[edit dynamic-profiles]green_vpls_pw_2 interfaces $junos-interface-ifd-name {unit $junos-underlying-unit-number {vlan-tags outer 200 inner 100;}}

Note: This is not a complete router configuration.

With this configuration, broadcast packets inside frames arriving with VLAN identifier 100 on ge-0/0/1 are normalized to a frame with VLAN identifier 100 (in this case, they are unchanged). The broadcast packet and frames egressing ge-0/0/2 or ge-0/0/3 are unchanged as well, according to the interface configuration. Frames egress the VPLS pseudowire in routing instance green with an outer VLAN tag value of 200 pushed on top of the normalized value.


Published: 2010-04-12