Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring a Retail Dynamic Profile for Use in the Layer 2 Wholesale Solution

To configure a dynamic profile for use with retailer access:


To support Layer 2 access profiles the RADIUS server must provide VLAN authentication.

  1. Create a retail dynamic profile.
  2. Define the dynamic routing instance variable in the dynamic profile.
  3. Set the dynamic interface variable for the dynamic routing instance.
  4. Define the dynamic interfaces variable for the dynamic profile.
  5. Define the dynamic interface unit variable for the dynamic profile.
  6. (Optional) Define VLAN encapsulation for the dynamic interfaces.

    If you choose not to specify an encapsulation for the logical interface, you must specify an encapsulation for the physical interface.

  7. Define the VLAN tag parameters for the dynamic profile:

    This solution example uses stacked VLAN tagging. However, you can also specify single-tag VLANs. For additional information about configuring dynamic VLANs, see the Broadband Subscriber VLANs and Interfaces User Guide.

  8. Define the input and output VLAN maps. See Stacking and Rewriting VLAN Tags for the Layer 2 Wholesale Solution for details. For our example, we use:
  9. Specify the unit family as vpls at the [edit dynamic-profiles profile-name interfaces “$junos-interface-ifd-name” unit “$junos-interface-unit” family] hierarchy level.

The result is a dynamic subscriber profile that uses RADIUS authentication to assign the outer VLAN ID dynamically.

The dynamic profile is displayed in curly brace format:

The need to authenticate the VLAN through RADIUS is specified by "$junos-vlan-map-id" and "$junos-vlan-id" parameters.

The outer VLAN ID is returned by the RADIUS server as part of the user name attribute, as shown: