Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Configuring a Basic Dynamic Profile

This topic describes how to create a basic dynamic profile. A basic profile must contain a profile name and have both an interface variable name (such as $junos-interface-ifd-name) included at the [edit dynamic-profiles profile-name interfaces hierarchy level and logical interface variable name (such as $junos-underlying-interface-unit or $junos-interface-unit) at the [edit dynamic-profiles profile-name interfaces variable-interface-name unit] hierarchy level.

Before you configure dynamic profiles for initial client access:

  1. Configure the necessary router interfaces that you want DHCP clients to use when accessing the network.

    See Subscriber Interface Overview for information about the types of interfaces you can use with dynamic profiles and how to configure them.

  2. Configure all RADIUS values that you want the profiles to use when validating DHCP clients for access to the multicast network.

    See Configuring RADIUS Server Parameters for Subscriber Access

To configure a basic dynamic profile:

  1. Name the profile.
    [edit]user@host# edit dynamic-profiles basic-profile
  2. Define the interface-name statement with the internal $junos-interface-ifd-name variable used by the router to match the interface name of the receiving interface.
    [edit dynamic-profiles basic-profile]user@host# edit interfaces $junos-interface-ifd-name
  3. Define the unit statement with the internal variable:
    • 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.
    • 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 interfaces "$junos-interface-ifd-name"]user@host# set unit $junos-underlying-interface-unit

    or

    [edit dynamic-profiles basic-profile interfaces "$junos-interface-ifd-name"]user@host# set unit $junos-interface-unit
  4. If you are using interface sets, you must apply the traffic-control profile to the interface set in the static [edit class-of-service] hierarchy. The interface set name must be explicitly referenced in the CoS configuration as part of the static configuration outside of the dynamic profile. The CoS configuration is static and the interface set name must be statically referenced.

    This rule applies to all interface sets except ACI sets.

 

Related Documentation

 

Published: 2013-02-11

Previous Page Next Page