Juniper JUNOS OS 10.4 - RELEASE NOTES REV 6 Release Note page 38

JUNOS OS 10.4 Release Notes
38
Include the
encapsulation
interfaces interface-name]
flexible-ethernet-services
Use the or
vlan-vpls flexible-ethernet-services
option for the encapsulation
interface "$junos-interface-ifd-name" unit $junos-interface-unit]
NOTE: Using the
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
limitation to the VLAN ID value.
Use the
flexible-ethernet-services
with different encapsulations at the
"$junos-interface-ifd-name" unit $junos-interface-unit]
NOTE: This encapsulation type does not have a VLAN ID limitation.
Use the
extended-vlan-vpls
encapsulation statement at the
"$junos-interface-ifd-name" unit $junos-interface-unit]
NOTE: This encapsulation type can support multiple TPIDs and does
not have a VLAN ID limitation.
Specify the vpls option for the
instances you plan to use at the
level.
Include the qualified-bum-pruning-mode
you plan to use at the
[edit routing-instances instance-name]
Specify the option for the
permanent
routing-instances instance-nameprotocols vpls]
routing instance (pseudo-wire) remains operational.
Configure the VLAN Interfaces to use the dynamic profile. See the Subscriber Access
Configuration Guide for details.
Define access to your RADIUS server and specify the access profile at the
hierarchy level.
access]
To view the logical system and routing instance for each subscriber, use the
operational command.
subscriber
statement for any interfaces you plan to use at the
hierarchy level and specify the encapsulation as follows:
.
options if you specified the
statement at the [edit dynamic-profiles profile-name
vlan-vpls encapsulation option in both the dynamic
encapsulation option does not result in a
option if you plan to configure logical interfaces
[edit dynamic-profiles profile-name interface
option if you chose not to specify an option for the
[edit dynamic-profiles profile-name interface
instance-type statement for any retailer routing
[edit routing-instances instance-name]
statement in any retailer routing instances
connectivity-type
hierarchy level to ensure that the
Copyright © 2011, Juniper Networks, Inc.
[edit
vlan-vpls
hierarchy level.
hierarchy level.
hierarchy level.
hierarchy
hierarchy level.
statement at the
[edit
[edit
show