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 Dynamic Underlying VLAN Interfaces to Use Access-Line Identifiers

date_range 06-Dec-23

After you define the access-line-identifier (ALI) interface set, you must configure the underlying VLAN interface to enable creation of dynamic VLAN subscriber interfaces based on the ALI. You can configure the underlying VLAN interface statically or dynamically.

This topic describes how to configure the underlying VLAN interface dynamically.

Before you begin:

To configure a dynamic underlying VLAN interface to use the ALI:

  1. In the dynamic profile for the underlying VLAN interface, associate the underlying VLAN interface with the line identity dynamic profile that defines the ALI interface set.
    content_copy zoom_out_map
    [edit dynamic-profiles profile-name]
    user@host# set interfaces interface-name unit logical-unit-number auto-configure line-identity dynamic-profile ali-interface-set-profile-name
    

    For example, the following statement in a dynamic profile named ali-vlan-underlying-profile-demux associates the dynamic underlying VLAN interface with the dynamic profile ali-vlan-set-profile2 that defines the ALI interface set. You must use the predefined dynamic variable $junos-interface-ifd-name to represent the interface name, and $junos-interface-unit to represent the logical unit number.

    content_copy zoom_out_map
    [edit dynamic-profiles ali-vlan-underlying-profile-demux]
    user@host# set interfaces “$junos-interface-ifd-name” unit “$junos-interface-unit” auto-configure line-identity dynamic-profile ali-vlan-set-profile2
    
  2. Configure one or more trusted options—the access-line-identifier information—that are accepted to trigger the creation of the dynamic VLAN.
    content_copy zoom_out_map
    [edit dynamic-profiles profile-name]
    user@host# set interfaces interface-name unit logical-unit-number auto-configure line-identity include trusted-option
    

    For example, the following statement specifies that only the ARI is accepted to trigger creation of the VLAN. When the ARI is not received, no VLAN is created.

    content_copy zoom_out_map
    [edit dynamic-profiles ali-vlan-underlying-profile-demux]
    user@host# set interfaces “$junos-interface-ifd-name” unit “$junos-interface-unit” auto-configure line-identity include remote-id
    

The following example shows the dynamic configuration that uses these statements. This configuration enables the underlying dynamic IP demultiplexing (IP demux) VLAN interface to create dynamic subscriber interfaces based on the ARI by applying a single default ALI interface set dynamic profile (ali-vlan-set-profile2) to all households on the VLAN interface.

content_copy zoom_out_map
[edit dynamic-profiles ali-vlan-underlying-profile-demux]
interfaces {
    “$junos-interface-ifd-name” {
        unit "$junos-interface-unit" {
            auto-configure {
                line-identity {
                    dynamic-profile ali-vlan-set-profile2;
                    include {
                        remote-id;
                    }
                }
            }
            vlan-id "$junos-vlan-id";
            demux-options {
                underlying-interface “$junos-interface-ifd-name”;
            }
            family inet {
                unnumbered-address lo0.0 preferred-source-address 198.51.100.20;
            }
        }
    }
}
footer-navigation