Cisco Cisco Packet Data Gateway (PDG)
Radio Congestion Policy Configuration Mode Commands
▀ data-loss threshold
▄ Command Line Interface Reference, StarOS Release 18
8212
data-loss threshold
Configures the acceptable data loss percentage in the network.
Product
All
Privilege
Security Administrator, Administrator, Operator, Inspector
Mode
Exec > ACS Configuration > Radio Congestion Policy Configuration
active-charging service service_name > radio-congestion policy policy_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-radio-congestion-policy)#
Syntax
data-loss threshold threshold_value weightage weightage_value
default data-loss
default
Configures this command with its default setting.
threshold threshold_value
Configures the percentage of packet loss considered as acceptable in the network. This is used to determine
the congestion level to be reported.
the congestion level to be reported.
threshold_value
must be a number from 1 to 99.
Default: 1%
weightage weightage_value
Configures the data loss weightage to be given to packet loss while calculating the congestion level for a
subscriber.
subscriber.
weightage_value
must be a number from 0 to 100.
Default: 50
Usage
Use this command to configure the acceptable percentage of packet-loss in the network, and the data loss
weightage to be given to packet loss while calculating the congestion level for a subscriber. Currently, the
minimum value allowed to be configured is 1%. This is required to offset the effects of parameters other than
the airlink congestion. The congestion primarily occurs at the airlink, but it is also possible at other places in
the flow path. The link monitor cannot distinguish between airlink and congestion at any other point. For
example, if 1% packet loss is considered normal in some network and if some flow of a subscriber
experiences a packet loss of 2%, then it will be considered as a sign of congestion. If some flow of a
subscriber has a packet loss of 1% or less, then it is not considered as congestion, as it is in the normal range
for that network.
weightage to be given to packet loss while calculating the congestion level for a subscriber. Currently, the
minimum value allowed to be configured is 1%. This is required to offset the effects of parameters other than
the airlink congestion. The congestion primarily occurs at the airlink, but it is also possible at other places in
the flow path. The link monitor cannot distinguish between airlink and congestion at any other point. For
example, if 1% packet loss is considered normal in some network and if some flow of a subscriber
experiences a packet loss of 2%, then it will be considered as a sign of congestion. If some flow of a
subscriber has a packet loss of 1% or less, then it is not considered as congestion, as it is in the normal range
for that network.