Cisco Cisco Packet Data Interworking Function (PDIF)
ACS Rulebase Configuration Mode Commands
flow any-error ▀
Command Line Interface Reference, StarOS Release 18 ▄
729
flow any-error
This command allows you to specify the charging action to be used for packets dropped by Stateful Firewall due to any
error conditions.
error conditions.
Product
PSF
Privilege
Security Administrator, Administrator
Mode
Exec > ACS Configuration > Rulebase Configuration
active-charging service service_name > rulebase rulebase_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-rule-base)#
Syntax
flow any-error charging-action charging_action_name
default flow any-error
default
Configures the default action for packets dropped by Stateful Firewall due to any errors.
Default: Update the flow statistics if flow is available
Default: Update the flow statistics if flow is available
charging_action_name
Specifies the charging action based on which accounting action is taken on packets dropped by Stateful
Firewall due to any errors.
Firewall due to any errors.
charging_action_name
must be the name of a charging action, and must be an alphanumeric string of 1
through 63 characters.
Important:
The charging action specified here should preferably not be used for action on packets dropped due
to Stateful Firewall ruledef match or no-match (in the
firewall priority
and
firewall no-ruledef-matches
commands) and the content ID within the charging action must be unique so that dropped counts will not interfere with
other content IDs.
other content IDs.
Usage
Use this command to configure the charging action for packets dropped by Stateful Firewall due to any error
conditions, such as, a packet being inappropriate based on the state of the protocol of the packet's session, or
DoS protection causing the packet to be discarded, and so on.
For a packet dropped due to Stateful Firewall ruledef match or no match (first packet of a flow), the charging
action applied is the one configured in the
conditions, such as, a packet being inappropriate based on the state of the protocol of the packet's session, or
DoS protection causing the packet to be discarded, and so on.
For a packet dropped due to Stateful Firewall ruledef match or no match (first packet of a flow), the charging
action applied is the one configured in the
firewall priority
or the
firewall no-ruledef-matches
command respectively.
In StarOS 8.1, in the case of Policy-based Firewall, the charging action applied is the one configured in the
In StarOS 8.1, in the case of Policy-based Firewall, the charging action applied is the one configured in the
access-rule priority
or the
access-rule no-ruledef-matches
command respectively.