Juniper JUNOS OS 10.4 - RELEASE NOTES - Page 32

Interfaces Configuration Guide for details on how to configure output-vlan-map
statement options.
NOTE: You configure the output-vlan-map statement only when there
is a need to either pop or modify the outer tag found in a dual-tagged
packet meant for the subscriber.
•
Specify the unit family as vpls at the [edit dynamic-profiles profile-name interface
“$junos-interface-ifd-name” unit $junos-interface-unit family] hierarchy level.
•
Include the flexible-vlan-tagging statement for any interfaces you plan to use at the
[edit interfaces interface-name] hierarchy level.
•
Include the encapsulation statement for any interfaces you plan to use at the [edit
interfaces interface-name] hierarchy level and specify the encapsulation as follows:
flexible-ethernet-services.
•
Use the vlan-vpls or flexible-ethernet-services options if you specified the vlan-vpls
option for the encapsulation statement at the [edit dynamic-profiles profile-name
interface “$junos-interface-ifd-name” unit $junos-interface-unit] hierarchy level.
NOTE: Using the vlan-vpls encapsulation option in both the dynamic
profile and when configuring the physical interface limits the VLAN ID
value to a number greater than or equal to 512. Using the
flexible-ethernet-services encapsulation option does not result in a
limitation to the VLAN ID value.
•
Use the flexible-ethernet-services option if you plan to configure logical interfaces
with different encapsulations at the [edit dynamic-profiles profile-name interface
“$junos-interface-ifd-name” unit $junos-interface-unit] hierarchy level.
NOTE: This encapsulation type does not have a VLAN ID limitation.
•
Use the extended-vlan-vpls option if you chose not to specify an option for the
encapsulation statement at the [edit dynamic-profiles profile-name interface
“$junos-interface-ifd-name” unit $junos-interface-unit] hierarchy level.
NOTE: This encapsulation type can support multiple TPIDs and does
not have a VLAN ID limitation.
•
Specify the vpls option for the instance-type statement for any retailer routing
instances you plan to use at the [edit routing-instances instance-name] hierarchy
level.
Copyright © 2010, Juniper Networks, Inc.32
JUNOS OS 10.4 Release Notes