Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Broadband Subscriber Services User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring PCC Rule Activation in a Subscriber Management Dynamic Profile

date_range 06-Dec-23
Note:

Starting in Junos OS Release 19.3R2, PCC rule activation in a dynamic profile is also supported if you have enabled Next Gen Services on the MX240, MX480 or MX960 router with the MX-SPC3 card.

To configure PCC rule activation by a dynamic profile, specify the PCEF profile to use, the PCC rules to activate, and the service set to use.

  1. Assign a PCEF profile to the dynamic profile. In the client dynamic profile, you can identify the PCEF profile with the variable $junos-pcef-profile. All of a subscriber’s dynamic profiles that include a PCEF profile must point to the same PCEF profile.
    content_copy zoom_out_map
    [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number service]
    user@host# set pcef pcef-profile-name
    
  2. Activate PCC rules in the dynamic profile. In the access profile, you can identify a rule name with the variable $junos-pcef-rule.
    Note:

    Do not activate both service data flow (Layer 3 or Layer 4) PCC rules that have a gating action and application-aware (Layer 7) PCC rules in the same dynamic profile. The gating action for the service data flow PCC rules is not applied in this situation.

    To activate one PCC rule:

    content_copy zoom_out_map
    [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number service pcef pcef-profile-name]
    user@host# set activate rule-name
    

    To activate all the PCC rules:

    content_copy zoom_out_map
    [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number service pcef pcef-profile-name]
    user@host# set activate-all
    
  3. Assign a service set to the dynamic profile. This must be a service set that you configured for application-aware policy control. In the client dynamic profile, you can identify the service set with a variable ($junos-input-service-set | $junos-output-service-set | $junos-input-ipv6-service-set | $junos-output-ipv6-service-set). You must use the same service set for both the input and output service.
    content_copy zoom_out_map
    [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family family service (input | output) service-set]
    user@host# set service-set service-set-name
    
  4. (Optional) Assign a service filter to the dynamic profile. The service filter can identify conditions for which you want to skip application-aware policy control. In the client dynamic profile, you can identify the service filter with a variable ($junos-input-service-filter | $junos-output-service-filter | $junos-input-ipv6-service-filter | $junos-output-ipv6-service-filter).
    content_copy zoom_out_map
    [edit dynamic-profile profile-name interfaces interface-name unit logical-unit-number family family service (input | output) service-set service-set-name]
    user@host# set service-filter filter-name
    
footer-navigation