Step 1 | enable
Example:
Router> enable
|
Enables
privileged EXEC mode. Enter your password if prompted.
|
Step 2 | configure
terminal
Example:
Router# configure terminal
|
Enters the
global configuration mode.
|
Step 3 |
cable
qos
enforce-rule
name
Example:
Router(config)# cable qos enforce-rule test
|
Creates an
enforce-rule with the specified
name and
enters the enforce-rule configuration mode.
The
name
parameter can be any arbitrary and unique string that is from 1 to 15
characters in length.
Note
| Each
enforce-rule can be created by giving it a name.
|
|
Step 4 | monitoring-basics{legacy |
peak-offpeak} {docsis10 |
docsis11}
Example:
Router(enforce-rule)# monitoring-basics peak-offpeak docsis11
|
Defines the
kind of monitoring desired and the type of modems to be monitored.
- legacy—Provides only one threshold and one
monitoring duration.
- peak-offpeak—Allows the selection of two peak
durations within a day.
- docsis10—Specifies application of the enforce-rule
to DOCSIS 1.0 cable modems.
- docsis11—Specifies application of the enforce-rule
to DOCSIS 1.1 cable modems.
The default
is legacy and DOCSIS 1.0.
|
Step 5 | qos-profile
registered
profile-id
Example:
Router(enforce-rule)# qos-profile registered 1
|
Specifies the
registered quality of service (QoS) profile that should be used for this
enforce-rule.
profile-id is a number from 0 to 16383.
Note
| If you
want to manage a cable modem that currently uses a modem-created QoS profile,
you must first manually create a new QoS profile on the CMTS with the same QoS
parameters as the modem-created profile. Then allow the modem to come online
using the manually created profile before using this command.
|
|
Step 6 | qos-profile
enforced
profile-id [no-persistence]
Example:
Router(enforce-rule)# qos-profile enforced 4
|
Specifies
the quality of service (QoS) profile that should be enforced when users violate
their registered QoS profiles.
-
profile-id
Number from 0 to 16383.
- no-persistence—(Optional) Configures the rule so
that the enforced QoS profile does not remain in effect when a cable modem
reboots.
|
Step 7 | service-class
{enforced
|
registered}
name
Example:
Router(enforce-rule)# service-class enforced test
|
Identifies
a particular service class with the specified
name for
cable modem monitoring in an enforce-rule.
- enforced—Specifies an enforced service class.
- registered—Specifies the service class using which
the cable modem registered.
Note
| This
command is applicable only for DOCSIS 1.1 (or later) cable modems.
|
|
Step 8 | duration
minutes
avg-rate
rate
sample-interval
minutes[penalty
minutes] {downstream
|
upstream}
[enforce]
Example:
Router(enforce-rule)# duration 10 avg-rate 500 sample-interval 10 penalty 120 downstream enforce
|
Specifies
the time period and sample rate used for monitoring subscribers when legacy
monitoring is configured (Step 4).
- minutes—Specifies the size of the sliding window
(in minutes) during which subscriber usage is monitored. The valid range is 10
to 44640, with a default of 360 (6 hours).
- avg-rate
rate—Specifies the average sampling rate in
kilobits per second for the specified duration. The valid range is 1 to 400000
with no default.
- sample-interval
minutes—Specifies how often (in minutes) the CMTS
router should sample a service flow to get an estimate o f subscriber usage.
The valid range is 1 to 30 minutes, with a default value of 15 minutes.
- penalty—(Optional) Specifies the period (in
minutes) during which a cable modem can be under penalty. This weekday penalty
duration, if configured, takes precedence over the duration specified using the
penalty-period command. The valid range is 1 to 10080.
- downstream—Specifies monitoring of traffic in the
downstream direction.
- upstream—Specifies monitoring of traffic in the
upstream direction.
- enforce—(Optional) Specifies that the enforce-rule
QoS profile should be applied automatically if a user violates their registered
QoS profile.
|
Step 9 | peak-time1
{hour
|
hour:minutes}
duration
minutes
avg-rate
rate
[peak-time2
{hour |
hour:minutes}
duration
minutes
avg-rate
rate][duration
offpeak-minutes
avg-rate
offpeak-rate
]
sample-interval
minutes[penalty
minutes] {downstream |
upstream}[enforce]
Example:
Router(enforce-rule)# peak-time1 6 duration 180 avg-rate 2 peak-time2 18 duration 180 avg-rate 2 duration 120 avg-rate 3 sample-interval 10 upstream enforce
Router(enforce-rule)# peak-time1 6:30 duration 180 avg-rate 2 peak-time2 18:40 duration 180 avg-rate 2 duration 120 avg-rate 3 sample-interval 10 penalty 120 upstream enforce
|
Specifies
peak monitoring periods when peak-offpeak monitoring is configured (Step 4).
- peak-time1
{hour
|
hour:minutes}—Specifies the time of day during
which monitoring occurs for the first peak time. This value can be specified in
hour (hh) or hour:minutes (hh:mm) format. The valid range for hour is 0 to 23
using a 24-hour clock. The valid range for minutes is 0 to 59.
- duration
minutes—Specifies the size of the sliding window
during which the subscriber usage is monitored for the first peak time, and
optionally for a second peak time when used with the
peak-time2
keyword. Valid range is 60 to 1440 minutes.
- avg-rate
rate—Specifies the average sampling rate in
kilobytes per second for the specified duration. The valid range is 1 to 400000
with no default.
- peak-time2
{hour
|
hour:minutes}—(Optional) Specifies the time of day
during which monitoring occurs for a second peak time. This value can be
specified in hour (hh) or hour:minutes (hh:mm) format. The valid range for
hours is 0 to 23 using a 24-hour clock. The valid range for minutes is 0 to 59.
- duration
offpeak-minutes—(Optional) Specifies the size of
the sliding window during which the subscriber usage is monitored for the
remaining offpeak time (time not specified for peak monitoring). The valid
range is 60 to 1440 minutes.
- avg-rate
offpeak-rate—(Optional) Specifies the average
sampling rate in kilobytes per second for the specified offpeak duration. The
valid range is 1 to 400000 with no default.
- sample-interval
minutes—Specifies how often (in minutes) the CMTS
router should sample a service flow to get an estimate of subscriber usage. The
valid range is 1 to 30 minutes, with a default value of 15 minutes.
- penalty—(Optional) Specifies the period (in
minutes) during which a CM can be under penalty. This weekday penalty duration,
if configured, takes precedence over the duration specified using the
penalty-period command. The valid range is 1 to 10080.
|
Step 10 |
|
- downstream—Specifies monitoring of traffic in the
downstream direction.
- upstream—Specifies monitoring of traffic in the
upstream direction.
- enforce—(Optional) Specifies that the enforce-rule
QoS profile should be applied automatically if a user violates the registered
QoS profile.
|
Step 11 | penalty-period
minutes [time-of-day {hour|hour:minutes}] [monitoring-on]
Example:
Router(enforce-rule)# penalty-period 10
|
(Optional)
Specifies the period for which an enforced QoS profile should be in effect for
subscribers who violate their registered QoS profiles.
- minutes—Number from 1 to 10080 minutes, with a
default value of 10080 minutes (7 days).
- time-of-day {hour
|hour:minutes}—(Optional) Specifies the time of day when
a penalized cable modem can be released from its enforced profile. The time can
be specified in the hh (hours) or hh:mm (hours:minutes) format. The valid range
for hours is 0 to 23 using a 24-hour clock. The valid range for minutes is 0 to
59.
-
monitoring-on—(Optional) Specifies that the monitoring should be turned on
after the cable modem is released from the penalty, that is, after time-of-day.
If this keyword is not specified, by default, monitoring is turned off after
the release time.
|
Step 12 | enabled
Example:
Router(enforce-rule)# enabled
|
(Optional)
Activates the enforce-rule and begins subscriber traffic management.
|
Step 13 | end
Example:
Router(enforce-rule)# end
|
Exits
enforce-rule configuration mode and returns to privileged EXEC mode.
|