Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

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

date_range 06-Dec-23

To configure a dynamic profile for use with retailer access:

Note:

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

  1. Create a retail dynamic profile.
    content_copy zoom_out_map
    [edit] 
    user@host# edit dynamic-profiles Subscriber_Profile_Retail1
    
  2. Define the dynamic routing instance variable in the dynamic profile.
    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1]
    user@host# edit routing-instances $junos-routing-instance
    
  3. Set the dynamic interface variable for the dynamic routing instance.
    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1 routing-instances “$junos-routing-instance”]
    user@host# set interface $junos-interface-name
    
  4. Define the dynamic interfaces variable for the dynamic profile.
    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1]
    user@host# edit interfaces $junos-interface-ifd-name
    
  5. Define the dynamic interface unit variable for the dynamic profile.
    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1 interfaces “$junos-interface-ifd-name”]
    user@host# edit unit $junos-interface-unit
    
  6. (Optional) Define VLAN encapsulation for the dynamic interfaces.
    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1 interfaces “$junos-interface-ifd-name” unit “$junos-interface-unit”]
    user@host# set encapsulation vlan-vpls
    
    Note:

    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:
    Note:

    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.

    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1 interfaces “$junos-interface-ifd-name” unit “$junos-interface-unit”]
    user@host# set vlan-tags outer "$junos-stacked-vlan-id" inner "$junos-vlan-id" 
    
  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:
    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1 interfaces “$junos-interface-ifd-name” unit “$junos-interface-unit”]
    user@host# set input-vlan-map swap-push 
    user@host# set input-vlan-map vlan-id "$junos-vlan-map-id"
    user@host# set input-vlan-map inner-vlan-id "$junos-inner-vlan-map-id"
    user@host# set output-vlan-map pop-swap
    user@host# set output-vlan-map inner-tag-protocol-id 0x8100
  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.
    content_copy zoom_out_map
    [edit dynamic-profiles Subscriber_Profile_Retail1 interfaces “$junos-interface-ifd-name” unit “$junos-interface-unit”]
    user@host# set family vpls
    

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:

content_copy zoom_out_map
[edit]
user@host# show dynamic-profiles 
Subscriber_Profile_Retail1
    routing-instances {
        "$junos-routing-instance" {
            interface "$junos-interface-name";
        }
    }
    interfaces {
        "$junos-interface-ifd-name" {
            unit "$junos-interface-unit" {
                encapsulation vlan-vpls;
                vlan-tags outer "$junos-stacked-vlan-id" inner "$junos-vlan-id";
                input-vlan-map {
                    swap-push;
                    vlan-id "$junos-vlan-map-id";
                    inner-vlan-id "$junos-inner-vlan-map-id";
                }
                output-vlan-map {
                    pop-swap;
                    inner-tag-protocol-id 0x8100;
                }
                family vpls;
            }
        }
    }

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:

content_copy zoom_out_map
Type: VLAN
User Name: user1.xe-0/1/0:2015
Logical System: default
Routing Instance: ISP02-Test
Interface: xe-0/1/0.3221225509
Interface type: Dynamic
Underlying Interface: xe-0/1/0
Core IFL Name: xe-0/1/3.0
Dynamic Profile Name: Subscriber_Profile_Retail1
Dynamic Profile Version: 1
State: Active
Radius Accounting ID: 43
Session ID: 43
PFE Flow ID: 87
VLAN Id: 2015
VLAN Map Id: 100
Inner VLAN Map Id: 201
Login Time: 2021-07-07 06:42:33 PDT
Dynamic configuration: 
  junos-vlan-map-id: 100
footer-navigation