> ACS Group-of-Ruledefs Configuration Mode Commands
> The ACS Group-of-Ruledefs Configuration Mode is used to configure groups of rule definitions (ruledefs).
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> add-ruledef
> This command allows you to add or remove ruledefs from a group-of-ruledefs.
> Important: A maximum of 128 ruledefs can be added to a group-of-ruledefs.
> Product
> ACS
> Privilege
> Security Administrator, Administrator
> Syntax
> add-ruledef priority ruledef_priority ruledef ruledef_name
> no add-ruledef priority ruledef_priority
> no
> If previously configured, specifies that the ruledef associated with the specified priority number be removed from the current group-of-ruledefs.
> priority ruledef_priority
> Specifies priority of the ruledef in the current group-of-ruledefs.
> ruledef_priority must be unique in the group-of-ruledefs, and must be an integer from 1 through 10000.
> ruledef ruledef_name
> Specifies name of the ruledef to add to the current group-of-ruledefs.
> ruledef_name must be the name of an ACS ruledef, and must be an alpha and/or numeric string of 1 through 63 characters.
> Usage
> Use this command to add/remove ruledefs from a group-of-ruledefs.
> A group-of-ruledefs can contain optimizable ruledefs. Whether a group is optimized or not is decided on whether all the ruledefs in the group-of-ruledefs can be optimized, and if the group is included in a rulebase that has optimization turned on, then the group will be optimized.
> When a new ruledef is added, it is checked if it is included in any group-of-ruledefs, and whether it needs to be optimized, etc.
> Example
> The following command adds the ruledef ruledef23 to the current group-of-ruledefs, and assigns it a priority of 3:
> add-ruledef priority 3 ruledef ruledef23
> dynamic-command
> This command allows you to add or remove dynamic commands from a group-of-ruledefs.
> Product
> ACS, CF
> Privilege
> Security Administrator, Administrator
> Syntax
> dynamic-command content-filtering category policy-id policy_id
> no dynamic-command content-filtering category policy-id
> no
> Specifies to remove dynamic command configuration from the current group-of-ruledefs.
> content-filtering category policy-id policy_id
> Specifies the dynamic command for Content Filtering Category Policy ID configuration.
> policy_id must be a Content Filtering Category Policy ID, and must be an integer from 1 through 4294967295.
> Usage
> Use this command to add a dynamic command to a group-of-ruledefs, which will be executed when a dynamic protocol specifies that group-of-ruledefs (via the Rulebase-Name AVP).
> Important: This release supports only one command option, which is dynamic-command content-filtering category policy-id policy_id
> Example
> The following command configures a dynamic command for Content Filtering Category Policy ID configuration using the policy ID 100:
> dynamic-command content-filtering category policy-id 100
> end
> Exits the current configuration mode and returns to the Exec mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Use this command to return to the Exec mode.
> exit
> Exits the current mode and returns to the parent configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Use this command to return to the parent configuration mode.
> group-of-ruledefs-application
> This command allows you to specify the purpose of setting up a group-of-ruledefs as either charging, post-processing, or for other purposes.
> Product
> ACS
> Privilege
> Security Administrator, Administrator
> Syntax
> group-of-ruledefs-application { charging | content-filtering | gx-alias | post-processing | tpo }
> no group-of-ruledefs-application
> no
> If previously configured, deletes the group-of-ruledefs-application configuration from the current group-of-ruledefs.
> charging
> Specifies that the current group-of-ruledefs is for charging purposes.
> content-filtering
> Specifies that the current group-of-ruledefs is for content-filtering purposes.
> gx-alias
> Specifies that the current group-of-ruledefs is for Gx-alias purposes.
> post-processing
> Specifies that the current group-of-ruledefs is for post-processing purposes, that is, for use by the post-processing CLI command or automatic name-matching to the Diameter Filter-Id AVPs.
> tpo
> Important: The tpo keyword is available only in 12.2 and later releases.
> Specifies that this group-of-ruledefs is for use in Traffic Performance Optimization (TPO) in-line service’s match-rule and match-advertisement configurations.
> TPO can use both “charging” and “tpo” rule-application types. Note that ruledef/group-of-ruledef statistics are computed only for the “tpo” rule-application type. In the case of charging ruledefs/group-of-ruledefs, statistics are not computed, and are allowed only for backward compatibility. To generate ruledef statistics use “tpo” ruledefs in the TPO policies.
> Default: Disabled
> Usage
> Use this command to specify the purpose of setting up a group-of-ruledefs. If not specified, by default the rule-application type will be charging.
> If the group-of-ruledefs-application is configured for content-filtering, no ruledef can be added to it. Similarly, if configured explicitly for charging or post-processing, a content-filtering policy cannot be configured in it.
> The group-of-ruledefs may be dynamically selected by Diameter, as described by the policy-control charging-rulebase-name command in the Active Charging Service Configuration Mode. If so selected, the priority field of the add-ruledef instances within the group-of-ruledefs are ignored, and all of the rules named by the ruledef keyword that are also configured with the same name in the action command are selected.
> Example
> The following command configures the current group-of-ruledefs as for post-processing purposes:
> group-of-ruledefs-application post-processing

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883