Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    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.

    policies group name list name rule name {type type;precedence precedence;accounting;}
    policies group name list name rule name dynamic-pcc-rule {charging-rule-name charging-rule-name;mute-notification;flow-status (ENABLED-UPLINK | ENABLED-DOWNLINK | ENABLED | DISABLED | REMOVED);forwarding-class-name forwarding-class-name;LRF-profile-name LRF-profile-name;HCM-profile-name HCM-profile-name;online;reporting-level (SERVICE-IDENTIFIER-LEVEL | RATING-GROUP-LEVEL | SPONSORED-CONNECTIVITY-LEVEL);description description;}
    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:
      [edit]user@host# edit policies group GXnew list gx-list rule dynpcc-rul1-name
    2. Set the type of policy rule to gx-dynamic-pcc-rule.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name]user@host# set type 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.

      [edit policies group GXnew list gx-list rule dynpcc-rul1-name]user@host# set precedence precedence
    4. (Optional) Enable the accounting flag so that the SRC software requests the usage monitoring information from the Services Control Gateway.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name]user@host# set accounting
    5. From configuration mode, access the configuration statement that configures the dynamic PCC rule.
      [edit]user@host# edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule
    6. Specify a dynamic PCC rule name.

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

      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set charging-rule-name charging-rule-name
    7. (Optional) Disable sending the PCEF application start or stop notification to the SRC software.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set mute-notification

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

    8. (Optional) Specify the traffic flow status.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set flow-status (ENABLED-UPLINK | ENABLED-DOWNLINK | ENABLED | DISABLED | REMOVED)
    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).
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set forwarding-class-name 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).
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set LRF-profile-name 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).
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set HCM-profile-name 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.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set online

      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.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set reporting-level (SERVICE-IDENTIFIER-LEVEL | RATING-GROUP-LEVEL | SPONSORED-CONNECTIVITY-LEVEL)
    14. (Optional) Specify a description for the dynamic PCC rule.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]user@host# set description description
    15. (Optional) Verify your configuration.
      [edit policies group GXnew list gx-list rule dynpcc-rul1-name dynamic-pcc-rule]
      user@host# show 
      LRF-profile-name LRF-profile-name;
      application-information { 
        TDF-application-id TDF-application-id;
        TDF-application-id-base TDF-application-id-base;
      }
      charging-rule-name Testnew;
      flow-status ENABLED;
      forwarding-class-name forwarding-class-name;
      gx-flows { 
        flow1 {
          flow-description flow-description;
          flow-direction BIDIRECTIONAL;
          flow-label flow-label;
          security-parameter-index security-parameter-index;
          tos-traffic-class tos-traffic-class;
        }
        flow2 {
          flow-description flow-description;
          flow-direction UPLINK;
          flow-label flow-label;
          security-parameter-index security-parameter-index;
          tos-traffic-class tos-traffic-class;
        }
      }
      mute-notification;
      online;
      qos-information { 
        max-requested-bw-DL max-requested-bw-DL;
        max-requested-bw-UL max-requested-bw-UL;
      }
      redirect-information { 
        redirect-address-type IPv4-Address;
        redirect-server-address redirect-server-address;
      }
      reporting-level RATING-GROUP-LEVEL;
      steering-information { 
        keep-existing-steering STEERING-ENABLED;
        service-chain-identifier service-chain-identifier;
        steering-downlink-VRF steering-downlink-VRF;
        steering-ip-address steering-ip-address;
        steering-uplink-VRF steering-uplink-VRF;
      }
      

    Modified: 2016-12-29