Note
|
Effective with
Cisco IOS Release 12.3(9a)BC, the
activate-rule
at-byte-count command is not available in Cisco
IOS software.
|
To specify the
number of bytes that a subscriber can transmit during the monitoring period on
a Cisco CMTS router, use the
activate-rule
at-byte-count
command in enforce-rule configuration mode. To reset the rule
to its default values, use the
no form of
this command.
activate-rule at-byte-count kbytes {downstream | upstream} [enforce]
no activate-rule at-byte-count kbytes {downstream | upstream} [enforce]
Syntax Description
|
kbytes
|
Maximum
number of kilobytes that the subscriber can transmit in the specified direction
during the monitoring period. The valid range is 1 to 4294967, with a default
of 0 (no limit).
|
Note
|
To
reset the kilobyte count to 0, use the
no
form of this command.
|
|
|
downstream
|
Specifies that the kilobyte count applies to traffic in the downstream
direction.
|
|
upstream
|
Specifies that the kilobyte count applies to traffic in the upstream direction.
The default value is
upstream .
|
|
enforce
|
(Optional) Specifies that the enforce-rule QoS profile should be applied
automatically if a user violates the registered QoS profile.
|
Note
|
You
must have previously configured a registered QoS profile, using the
qos-profile
registered command, before being able to use the
enforce
keyword.
|
|
Command Default
The
kbytes value
defaults to 0 (no limit), upstream direction, and enforce-rule QoS profiles are
not automatically applied (no
activate-rule
at-byte-count
enforce ).
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
|
Release
|
Modification
|
|
12.2(15)BC1
|
This
command was introduced.
|
|
12.3(9a)BC
|
This
command was removed.
|
|
IOS-XE 3.15.0S
|
This command is not supported on the Cisco cBR Series
Converged Broadband Routers.
|
Usage Guidelines
The
activate-rule
at-byte-count
command specifies the maximum number of bytes that a subscriber
can transmit during the monitor window period (see the
monitoring-duration
command). If a subscriber transmits traffic beyond this maximum
value, the CMTS router considers the subscriber to be overconsuming.
If the optional
enforce
keyword has been specified for an enforce-rule, the CMTS router automatically
switches overconsuming subscribers to the enforced QoS profile (see the
qos-profile
enforced command). The enforced QoS profile remains
in force during the penalty time period (see the
qos-profile
registered command).
An enforce-rule
can be created for only one direction, either upstream or downstream. To
activate subscriber traffic management for both the upstream and downstream
directions, create two different enforce-rules, with one rule’s
activate-rule-at-byte-count command specifying the
downstream direction and the other rule specifying the upstream direction.
When you change
the configuration of a currently active enforce-rule, that rule begins using
the new configuration immediately to manage the cable modems tracked by the
enforce-rule.
Note
|
You can
create an enforce-rule that is a duplicate of an existing enforce-rule, but the
duplicate rule is not activated and applied to service flows until at least one
of its parameters is changed so that it has a unique configuration.
|
Examples
The following
example shows a typical
activate-rule-at-byte-count command for the
downstream direction:
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# activate-rule at-byte-count 20 downstream
The following
example shows a typical
activate-rule-at-byte-count command for the
upstream direction. The
enforce
option is also added so that the enforce-rule QoS profile is
automatically applied to users who exceed their registered profile:
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# activate-rule at-byte-count 5 upstream enforce
The following
example shows the same command being given for a second enforce-rule. The
system rejects the command because it is a duplicate of an existing rule, using
the same QoS profile and direction. You must change at least one of the rule
parameters to make it unique before it is mapped and applied to service flows.
Router# configure terminal
Router(config)# cable qos enforce-rule test2
Router(enforce-rule)# activate-rule at-byte-count 5 upstream enforce
Enforce-rule test2 won't be mapped to service flows as it is duplicate of test1 with same registered qos-profile 5 and same direction
Feedback