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

Configuring Static Subscriber Interfaces in Dynamic Profiles

In this release, you can use dynamic profiles to configure statically created logical interfaces. Dynamic profiles enable you to dynamically apply configured values (including CoS, IGMP, or filter configuration) to the static interfaces, making them easier to manage.

To configure static interfaces, you must first configure the interfaces on the router to which you expect subscribers to connect.

The subscriber access feature supports the following statically-created interface types in dynamic profiles:

  • GE—Gigabit Ethernet
  • XE—10 Gigabit Ethernet
  • AE—Aggregated Ethernet

This topic contains the following sections:

Configuring a Subscriber Interface with a Static VLAN Interface

This topic describes how to configure a subscriber interface with a static VLAN interface.

After you configure the static VLAN interface, you can reference it in a dynamic profile.

To configure a subscriber interface over a VLAN:

  1. Configure the static VLAN interface and enable VLAN tagging.
    [edit interfaces]ge-5/0/0 {vlan-tagging;}
  2. Configure the units and assign the VLAN IDs.
    unit 1 {proxy-arp;vlan-id 1;family inet {unnumbered-address lo0.0 preferred-source-address 192.1.1.1;}}unit 2 {proxy-arp;vlan-id 2;family inet {unnumbered-address lo0.0 preferred-source-address 192.1.1.1;}}
  3. Associate the static subscriber interface in a dynamic profile.

    See Associating Dynamic Profiles with Statically Created Interfaces.

Configuring Static Subscriber Interfaces Using IP Demux Interfaces

You can configure a subscriber interface using a statically created IP demux interface. This interface can be referenced in a dynamic profile.

To configure a static IP demux subscriber interface:

  1. Configure the IP demux interface on a physical device represented by a logical unit number. The logical interface resides on a physical device.

    See Configuring an IP Demultiplexing Interface.

  2. Configure the underlying interface on which the IP demux interface is running.

    See Configuring an IP Demux Underlying Interface

  3. Specify the underlying interface on which the IP demux interface is running.

    See Specifying the Demux Underlying Interface.

  4. Specify how ingress IPv4 traffic is to be demultiplexed based on packet destination or source addresses.

    See Configuring IP Demux Prefixes.

  5. Associate the static subscriber interface in a dynamic profile.

    See Associating Dynamic Profiles with Statically Created Interfaces.

Note: VLAN demux interfaces currently support the Internet Protocol version 4 (IPv4) suite (family inet) and the Internet Protocol version 6 (IPv6) suite (family inet6).

Configuring Static Subscriber Interfaces Using VLAN Demux Interfaces

You can configure a subscriber interface using a statically created VLAN demux interface. This interface can be referenced in a dynamic profile.

To configure a static VLAN demux subscriber interface:

  1. Configure the VLAN demux interface.

    See Configuring a VLAN Demultiplexing Interface.

  2. Configure the underlying interface on which the VLAN demux interface is running.

    See Configuring a VLAN Demux Underlying Interface

  3. Specify the underlying interface on which the VLAN demux interface is running.

    See Specifying the Demux Underlying Interface.

  4. Specify how ingress IP traffic is to be demultiplexed based on the VLAN ID.

    See Associating VLAN IDs to VLAN Demux Interfaces.

  5. Associate the static subscriber interface in a dynamic profile.

    See Associating Dynamic Profiles with Statically Created Interfaces.

Note: VLAN demux interfaces currently support the Internet Protocol version 4 (IPv4) suite (family inet) and the Internet Protocol version 6 (IPv6) suite (family inet6).

Associating Dynamic Profiles with Statically Created Interfaces

When configuring the interfaces stanza within a dynamic profile, you use variables to specify the interface name and the logical unit value. When a DHCP subscriber sends a DHCP request to the interface, the dynamic profile replaces the interface name variable and logical unit name variable with the actual interface name and logical unit number of the interface that received the DHCP request.

Note: Configuration of the interface name variable and logical interface name variable at the [edit dynamic-profiles profile-name interfaces] hierarchy level is required for a dynamic profile to function.

To configure the interface for a dynamic profile, specify the interface name variable and include the unit statement and associated logical interface name variable:

  1. Access the profile.
    [edit]user@host# edit dynamic-profiles basic-profile
  2. Specify the interface name variable.
    [edit dynamic-profiles basic-profile]user@host# set interfaces $junos-interface-ifd-name
  3. Specify the logical interface name variable with the unit statement.

    When referencing an existing interface, specify the $junos-underlying-interface-unit variable used by the router to match the unit value of the receiving interface:

    [edit dynamic-profiles basic-profile]user@host# set unit $junos-underlying-interface-unit

    When creating dynamic interfaces, specify the $junos-interface-unit variable used by the router to generate a unit value for the interface:

    [edit dynamic-profiles basic-profile]user@host# set unit $junos-interface-unit

Published: 2010-04-15

[an error occurred while processing this directive]