Cisco Cisco ASR 5000
ACS Rulebase Configuration Mode Commands
action priority ▀
Command Line Interface Reference, StarOS Release 18 ▄
651
Default: Disabled
mute
Disables application reporting to PCRF. This keyword is optional and visible only after configuring the
adc
keyword.
Default: Disabled
Default: Disabled
static-and-dynamic
The static-and-dynamic option causes the configuration to be defined and enabled, and allows a dynamic
protocol (such as the Gx interface) to disable or re-enable the configuration.
Default: Enabled
protocol (such as the Gx interface) to disable or re-enable the configuration.
Default: Enabled
Important:
When R7 Gx is enabled, “static-and-dynamic” rules behave exactly like “dynamic-only” rules. That
is, they must be activated explicitly by the Policy and Charging Rules Function (PCRF). When Gx is not enabled,
“static-and-dynamic” rules behave exactly like static rules.
“static-and-dynamic” rules behave exactly like static rules.
timedef timedef_name
Important:
This keyword is only available in StarOS 8.1 and StarOS 9.0 and later releases.
Associates the specified time definition with the ruledef / group-of-ruledefs. Timedefs activate or deactivate
ruledefs / groups-of-ruledefs, making them available for rule matching only when they are active.
ruledefs / groups-of-ruledefs, making them available for rule matching only when they are active.
timedef_name
must be the name of a timedef, and must be an alphanumeric string of 1 through 63
characters.
A timedef can be used with several ruledefs / group-of-ruledefs. When a packet is received, and a
ruledef / group-of-ruledefs is eligible for rule matching, if a timedef is associated with the ruledef / group-of-
ruledefs, before rule matching the packet-arrival time is compared with the timeslots configured in the
timedef. If the packet arrived in any of the timeslots configured in the associated timedef, rule matching is
undertaken, else the next ruledef / group-of-ruledefs is considered.
A timedef can be used with several ruledefs / group-of-ruledefs. When a packet is received, and a
ruledef / group-of-ruledefs is eligible for rule matching, if a timedef is associated with the ruledef / group-of-
ruledefs, before rule matching the packet-arrival time is compared with the timeslots configured in the
timedef. If the packet arrived in any of the timeslots configured in the associated timedef, rule matching is
undertaken, else the next ruledef / group-of-ruledefs is considered.
Important:
The time considered for timedef matching is the system’s local time.
ruledef ruledef_name
Adds the specified ruledef to the current rulebase.
ruledef_name
must be the name of a ruledef, and must be an alphanumeric string of 1 through 63
characters.
If the specified ruledef does not exist, there will be no ruledef triggers for this action priority within the
current rulebase.
If the specified ruledef does not exist, there will be no ruledef triggers for this action priority within the
current rulebase.
Important:
If the ruledef specified here is deleted or is not configured, the system accepts it without applying
any ruledef under current rulebase for this action priority.
group-of-ruledefs ruledefs_group_name
Adds the specified group-of-ruledefs to the current rulebase.
ruledefs_group_name
must be the name of a group-of-ruledefs, and must be an alphanumeric string of 1
through 63 characters.