[an error occurred while processing this directive][an error occurred while processing this directive]

Example: Configuring IPv4 Static VLAN Demux Interfaces Over a Gigabit Ethernet Underlying Interface with DHCP Local Server

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

To configure dynamic subscribers on VLAN demux interfaces:

  1. Enable VLAN tagging on the underlying interface that you plan to use for the VLAN demux interfaces.
    interfaces {ge-5/0/0 {vlan-tagging;}}
  2. Define the loopback interface.
    interfaces {lo0 {unit 0 {family inet {address 192.16.1.1/32;}}}}
  3. Define the demux interface.
    interfaces {demux0 {unit 102 {proxy-arp;vlan-id 103;demux-options {underlying-interface ge-5/0/0;}family inet {unnumbered-address lo0.0 preferred-source-address 173.16.1.1;}}}}
  4. Configure a dynamic profile for subscriber access.
    dynamic-profiles {user-profile {interfaces {"$junos-interface-ifd-name" {unit "$junos-underlying-interface-unit" {family inet;}}}}}
  5. Configure the access method used to dynamically create the subscriber interfaces.

    The following stanza specifies the gigabit Ethernet interface (ge-5/0/0.0) for use with the dynamically-created subscriber interfaces.

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

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

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

Published: 2010-04-15

[an error occurred while processing this directive]