Configuring PCC Rule Activation in a Subscriber Management Dynamic Profile

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.

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.
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:
To activate all the PCC rules:
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.
(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).

Configuring PCC Rule Activation in a Subscriber Management Dynamic Profile

Related Documentation