Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring Dynamic PCC Rules for Routers Running Junos OS and Acting as PCEF (SRC CLI)

 

Use the following configuration statements to configure dynamic PCC rules, which enable the SRC software to provision dynamic policies to the routers (Services Control Gateways) acting as PCEF and running Junos OS through the Gx interface by using the Gx router driver.

Note

You can create multiple dynamic PCC rules. For creating a dynamic PCC rule, you must:

  • Set the role of the policy list to junos-gx

  • Set the policy list rule type to gx-dynamic-pcc-rule

  • Set the policy list applicability option to both

Note

If the mute notification, application information, and redirect information are configured, then the rule is called as ePCC rule.

  1. From configuration mode, create a dynamic PCC rule inside a policy list that has already been created and configured. For example, to create a dynamic PCC rule called dynpcc-rul1-name within a policy list called gx-list:
  2. Set the type of policy rule to gx-dynamic-pcc-rule.
  3. (Optional) Specify the order in which the service data flow templates are applied when service data flow is detected at the Services Control Gateway. The value ranges from 1 through 65,535.Note

    The precedence value should be unique for each IP CAN session.

  4. (Optional) Enable the accounting flag so that the SRC software requests the usage monitoring information from the Services Control Gateway.
  5. From configuration mode, access the configuration statement that configures the dynamic PCC rule.
  6. Specify a dynamic PCC rule name.Note

    The rule name should be unique for each IP CAN session.

  7. (Optional) Disable sending the PCEF application start or stop notification to the SRC software.

    By default, the PCEF application start or stop notification is sent to the SRC software.

  8. (Optional) Specify the traffic flow status.
  9. (Optional) Specify the name of the forwarding class. This value is transmitted between the Services Control Gateway and SRC software through the Juniper Networks VSA (Forwarding-Class-Name).
  10. (Optional) Specify the name of the LRF profile. This value is transmitted between the Services Control Gateway and SRC software through the Juniper Networks VSA (LRF-Profile-Name).
  11. (Optional) Specify the name of the HCM profile. This value is transmitted between the Services Control Gateway and SRC software through the Juniper Networks VSA (HCM-Profile-Name).
  12. (Optional) Specify whether the online charging interface provided by the Services Control Gateway can be used for the dynamic PCC rule.

    By default, the online charging interface configured at the Services Control Gateway is used.

  13. (Optional) Specify a level at which the Services Control Gateway should report the usage information.
  14. (Optional) Specify a description for the dynamic PCC rule.
  15. (Optional) Verify your configuration.