Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring a Dynamic Profile for Client Access

1. Create a basic dynamic profile.

   See Configuring a Basic Dynamic Profile.

2. Configure the necessary router interfaces that you want accessing DHCP clients to use.

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

3. Ensure that the router is configured to enable communication between the client and the RADIUS server.

   See Specifying the Authentication and Accounting Methods for Subscriber Access.

4. 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

1. Access an IGMP access profile.
   user@host# edit dynamic-profiles access-profile[edit dynamic-profiles access-profile]user@host#
2. Define the IGMP interface with the interface variable.

   Note: The variable value is replaced by the name of the interface over which the router received the DHCP message.

   [edit dynamic-profiles access-profile]user@host# set protocols igmp interface $junos-interface-name
3. (Optional) Enable or disable accounting on the IGMP interface.
   [edit dynamic-profiles access-profile protocols igmp interface “$junos-interface-name”]user@host# set accounting

   or

   [edit dynamic-profiles access-profile protocols igmp interface “$junos-interface-name”]user@host# set no-accounting

   Note: This statement enables you to override the accounting setting at the IGMP protocol level. For example, if IGMP accounting is enabled at the [edit protocols igmp interface interface-name] hierarchy level, you can use the no-accounting statement to disable accounting for any IGMP interfaces that are dynamically created by the dynamic profile. If IGMP accounting is not enabled at the [edit protocols igmp interface interface-name] hierarchy level, you can use the accounting statement to enable accounting for any IGMP interfaces that are dynamically created by the dynamic profile.

4. Set the IGMP interface to remain enabled.
   [edit dynamic-profiles access-profile protocols igmp interface “$junos-interface-name”]user@host# set disable:$junos-igmp-enable

   Note: RADIUS is capable of disabling IGMP. By assigning the enable variable to the disable statement, you can ensure that IGMP remains enabled.

5. (Optional) Specify a group policy for the IGMP interface.
   [edit dynamic-profiles access-profile protocols igmp interface “$junos-interface-name”]user@host# set group-policy report-reject-policy
6. (Optional) Enable immediate leave on the IGMP interface.
   [edit dynamic-profiles access-profile protocols igmp interface “$junos-interface-name”]user@host# set immediate-leave:$junos-igmp-immediate-leave
7. (Optional) Set the IGMP interface to obtain the IGMP version from RADIUS.
   [edit dynamic-profiles access-profile protocols igmp interface “$junos-interface-name”]user@host# set version $junos-igmp-version