Example: Configuring IPv4 Static VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server

This example shows how to configure a static IPv4 VLAN demux interface with aggregated Ethernet as the underlying interface. DHCP Local Server configuration enables the association of subscribers to the VLAN demux interface by listing the aggregated Ethernet interface in the DHCP local server configuration.

To configure dynamic subscribers on VLAN demux interfaces:

1. Enable hierarchical scheduling and VLAN tagging on the underlying interface that you plan to use for any VLAN demux interfaces.

   content_copy zoom_out_map

   interfaces {
       ae1 {
           hierarchical-scheduler;
           vlan-tagging;
           aggregated-ether-options {
               minimum-links 1;
               lacp {
                   active;
                   periodic slow;
                   link-protection {
                       non-revertive;
                   }
               }
           }
       }
   }
   

2. Define the gigabit Ethernet interfaces that are part of the aggregated Ethernet interface.

   content_copy zoom_out_map

   interfaces {
       ge-5/0/0 {
           gigether-options {
               802.3ad ae1;
           }
       }
       ge-5/2/0 {
           gigether-options {
               802.3ad ae1;
           }
       }
   }
   

3. Define the demux interface.

   content_copy zoom_out_map

   interfaces {
       demux0 {
           unit 102 {
               proxy-arp;
               vlan-id 103;
               demux-options {
                   underlying-interface ae1;
               }
               family inet {
                   unnumbered-address lo0.0 preferred-source-address 173.16.1.1;
               }
           }
       }
   }
   

4. Define the loopback interface.

   content_copy zoom_out_map

   interfaces {
       lo0 {
           unit 0 {
               family inet {
                   address 127.16.1.1/32;
               }
           }
       }
   }
   

5. Configure a dynamic profile for initial subscriber access.

   content_copy zoom_out_map

   dynamic-profiles {
       user-profile {
           interfaces {
               "$junos-interface-ifd-name" {
                   unit "$junos-underlying-interface-unit" {
                       family inet;
                   }
               }
           }
           protocols {
               igmp {
                   interface "$junos-interface-name" {
                       version 3;
                       immediate-leave;
                       promiscuous-mode;
                   }
               }
           }
       }
   }
   

6. Configure the access method used to dynamically create the subscriber interfaces.

   The following stanza specifies the aggregated Ethernet interface (ae1.0) for use with the dynamically created subscriber interfaces.

   content_copy zoom_out_map

   system {
       services {
           dhcp-local-server {
               group myDhcpGroup {
                   authentication {
                       password test;
                       username-include {
                           user-prefix igmp-user1;
                       }
                   }
                   dynamic-profile user-profile;
                   interface ae1.0;
               }
           }
       }
   }
   

   Instead of using the aggregated Ethernet interface, you can alternatively specify the specific demux interface (demux0.102) as the device to use with the subscriber interfaces as follows:

   content_copy zoom_out_map

   system {
       services {
           dhcp-local-server {
               group myDhcpGroup {
                   authentication {
                       password test;
                       username-include {
                           user-prefix igmp-user1;
                       }
                   }
                   dynamic-profile user-profile;
                   interface demux0.102;
               }
           }
       }
   }