Table Of Contents
Subscriber Traffic Management for the Cisco CMTS Routers
Prerequisites for Subscriber Traffic Management on the Cisco CMTS Routers
Restrictions for Subscriber Traffic Management on the Cisco CMTS Routers
Information About Subscriber Traffic Management on the Cisco CMTS Routers
Sliding Window for Monitoring Service Flows
Restrictions for SNMP Trap Notifications
Cable Modem Interaction with the Subscriber Traffic Management Feature
How to Configure the Subscriber Traffic Management Feature on the Cisco CMTS Routers
Creating and Configuring an Enforce-Rule
Configuring Weekend Monitoring
Configuring Different Legacy Monitoring Conditions for Weekends
Configuring Different Peak-Offpeak Monitoring Conditions for Weekends
Removing Weekend Monitoring Conditions and Use the Same Monitoring Criteria Every Day
Changing a Cable Modem Service Class
Monitoring the Subscriber Traffic Management Feature on the Cisco CMTS Routers
Displaying the Currently Defined Enforce-Rules
Displaying the Current Subscriber Usage
Configuration Examples for Subscriber Traffic Management on the Cisco CMTS Routers
DOCSIS Configuration File and STM Service Classes: Example
Downstream Configuration: Example
Upstream Configuration: Example
Downstream and Upstream Configuration: Example
Weekend Monitoring Configuration: Example
Feature Information for Subscriber Traffic Management for the Cisco CMTS Routers
Subscriber Traffic Management for the Cisco CMTS Routers
Revised: May 21, 2009, Cisco IOS Release 12.2(33)SCBFirst Published: Cisco IOS Release 12.2(15)BC1
Note
Cisco IOS Release 12.2(33)SCA integrates support for this feature on the Cisco CMTS routers. This feature is also supported in Cisco IOS Release 12.3BC, and this document contains information that references many legacy documents related to Cisco IOS Release 12.3BC. In general, any references to Cisco IOS Release 12.3BC also apply to Cisco IOS Release 12.2SC. Most of the updates to this feature in Cisco IOS Release 12.3(23)BC2 are now supported in Cisco IOS Release 12.2(33)SCB.
For the latest information on Cisco CMTS router support in Cisco IOS Release 12.2SC, refer to the Cross-Platform Release Notes for Cisco Universal Broadband Routers in Cisco IOS Release 12.2SC.This document describes the Subscriber Traffic Management (STM) feature through version 1.2. STM version 1.2 supports DOCSIS 1.1-compliant cable modems (CMs).
The STM feature enables service providers to identify and control subscribers who exceed the maximum bandwidth allowed under their registered quality of service (QoS) profiles. STM works as a low CPU alternative to Network-Based Application Recognition (NBAR) and access control lists (ACLs), however, using STM does not mean that NBAR and ACLs have to be turned off; STM can be applied along with NBAR and ACLs. STM also works in conjunction with the Cisco Broadband Troubleshooter to support additional network management and troubleshooting functions in the Cisco CMTS.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Subscriber Traffic Management for the Cisco CMTS Routers" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
•
•
•
•
•
•
Prerequisites for Subscriber Traffic Management on the Cisco CMTS Routers
The Subscriber Traffic Management feature is supported on the Cisco CMTS routers in Cisco IOS Release 12.3BC and 12.2SC. Table 1 shows the hardware compatibility prerequisites for this feature.
Restrictions for Subscriber Traffic Management on the Cisco CMTS Routers
The Subscriber Traffic Management feature has the following restrictions and limitations:
•
•
•
The following is an example of a sampling rate calculation:
–
–
–
–
–
–
•
•
•
–
–
•
•
•
Information About Subscriber Traffic Management on the Cisco CMTS Routers
The following sections describe the Subscriber Traffic Management feature:
•
•
Feature Overview
The Subscriber Traffic Management feature allows service providers to identify and control subscribers who exceed the maximum bandwidth allowed under their registered quality of service (QoS) profiles. This feature supplements current techniques such as Network-Based Application Recognition (NBAR) and access control lists (ACLs), to ensure that a minority of users do not consume a majority of the cable network's bandwidth.
Current subscriber controls, such as NBAR and ACLs, examine all packets coming into the CMTS. These techniques can curb a large volume of problem traffic, but they are not as effective in dealing with the latest generation of peer-to-peer file-sharing applications that can place heavy demands on a network's available bandwidth. The Subscriber Traffic Management feature allows service providers to focus on a minority of potential problem users without impacting network performance or other users who are abiding by their service agreements.
The Subscriber Traffic Management feature supports two types of monitoring: legacy and peak-time. Legacy monitoring allows you to set up a single monitoring duration only, without the ability to choose a time of day when that monitoring is performed. Peak-time monitoring allows you to specify up to two high-traffic periods of the day for monitoring, in addition to the ability to continue monitoring during remaining (or, off-peak) time periods. Combining the peak-time option with weekend monitoring, you can identify and limit the bandwidth usage of certain subscribers for up to two peak network usage times during the weekdays, and during a different set of peak usage times on the weekends.
When a cable modem goes offline and remains offline for 24 hours, the Cisco CMTS router deletes its service flow IDs from its internal databases, and also deletes the modem's traffic counters. This can allow some users to exceed their bandwidth limits, go offline, and come back online with new counters. The Subscriber Traffic Management feature helps to thwart these types of theft-of-service attacks by implementing a penalty period for cable modems that violate their service level agreements (SLAs). Even if the cable modem goes offline, its counters are still reset, and the CMTS continues to enforce the penalty period.
The Subscriber Traffic Management feature allows users to set thresholds for downstream and upstream bandwidth utilization, as an additional level of control. The monitoring of modems will start only after exceeding these thresholds. However, the monitoring will not be immediately stopped if the interface bandwidth utilization falls below the upper threshold. The monitoring will still continue till it drops to another threshold, which is set at a further lower level.
Feature List
The Subscriber Traffic Management feature has the following operational features:
•
•
•
•
•
•
•
•
•
•
•
•
•
Sliding Window for Monitoring Service Flows
When an enforce-rule is activated, the CMTS periodically checks the bandwidth being used by subscribers to determine whether any subscribers are consuming more bandwidth than that specified by their registered QoS profiles. The CMTS keeps track of the subscribers using a sliding window that begins at each sample-rate interval and continues for the monitoring-duration period.
Each sample-rate interval begins a new sliding window period for which the CMTS keeps track of the total bytes transmitted. At the end of each sliding window period, the CMTS examines the byte counters to determine if any subscriber is currently overconsuming bandwidth on the network.
For example, with the default sample-rate interval of 15 minutes and the default monitoring-duration window of 360 minutes (6 hours), the CMTS samples the bandwidth usage every 15 minutes and determines the total bytes transmitted at the end of each 360-minute window. Therefore, every 15 minutes, the CMTS determines each subscriber's usage statistics for the preceding 6-hour period.
Figure 1 illustrates how this process works, with a new sliding window beginning at the beginning of each sample-rate interval period.
Figure 1 Monitoring-Duration Windows
Weekend Monitoring
With standard legacy and peak-offpeak monitoring configuration, monitoring continues to occur on the weekends, but in releases prior to Cisco IOS Release 12.3(23)BC2, there was not an ability to establish different monitoring criteria during the weekend days.
Beginning in Cisco IOS Release 12.3(23)BC2 for STM version 1.2, support for configuration of different monitoring conditions on weekends is introduced. Weekend monitoring options support the same parameters that are available in the existing monitoring options, but use a separate set of commands to configure alternate monitoring on weekend days. This includes configuration of peak and offpeak weekend monitoring windows.
In addition, the CLI supports the ability to turn off any monitoring on the weekend, or to use the same monitoring conditions for every day of the week.
SNMP Trap Notifications
Cisco IOS Release 12.2(15)BC1 (for the Cisco uBR10012 router) and Cisco IOS Release 12.3(9a)BC (for the Cisco uBR7246VXR router and the Cisco uBR7100 series routers) support a Simple Network Management Protocol (SNMP) trap notification that can be sent whenever a subscriber violates the enforce-rule. This trap is defined in the CISCO-CABLE-QOS-MONITOR-MIB and is enabled using the snmp-server enable traps cable command.
Each SNMP trap notification contains the following information:
•
•
•
•
The CISCO-CABLE-QOS-MONITOR-MIB also contains the following tables that provide information about the Subscriber Traffic Management configuration and about subscribers who violate their enforce-rules:
•
•
Beginning in Cisco IOS Release 12.3(23)BC2, the following new objects are introduced to support feature enhancements in STM version 1.2:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Restrictions for SNMP Trap Notifications
In Cisco IOS Release 12.3(23)BC2, the MIB objects for weekend monitoring only support SNMP GET and GETMANY operations.
Cable Modem Interaction with the Subscriber Traffic Management Feature
The Subscriber Traffic Management feature ensures that users cannot bypass the QoS restrictions by rebooting their cable modems or performing other configuration changes. The service provider, however, continues to be able to change the modems' profiles and other configuration parameters as desired.
When the Subscriber Traffic Management feature is enabled, the following behavior is in effect:
•
•
•
Note
•
–
–
–
•
How to Configure the Subscriber Traffic Management Feature on the Cisco CMTS Routers
This section describes the following required and optional procedures:
•
•
•
•
•
Creating and Configuring an Enforce-Rule
Every service class name that needs to be monitored, would be linked with an enforce-rule. The enforce-rule defines the monitoring-duration, the sample-rate, the penalty-period, and the registered service class name that the enforce-rule is linked to and the enforced service class name.
Use the following procedure to create and configure an enforce-rule. The enforce-rule does not become active until the enabled command is given.
Prerequisites
•
–
–
For additional information about these commands, refer to the Cisco IOS CMTS Cable Command Reference on Cisco.com:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
•
–
–
•
Restrictions
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
cable qos monitoring name
Example:Router(config)# cable qos monitoring test
Creates an enforce-rule with the specified name and enters enforce-rule configuration mode. The name parameter can be any arbitrary and unique string from 1 to 15 characters in length.
Note
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, where:
•
•
•
•
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, where profile-id is a number from 0 to 16383.
Note
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, where:
•
•
Step 7
service-class {enforced | registered} name
Example:Router(enforce-rule)# service-class enforced test
(Optional) Identifies a particular service class with the specified name for cable modem monitoring in an enforce-rule, where:
•
•
Step 8
duration minutes avg-rate rate sample-interval minutes {downstream | upstream} [enforce]
Example:Router(enforce-rule)# duration 10 avg-rate 500 sample-interval 10 downstream enforce
Specifies the time period and sample rate used for monitoring subscribers when legacy monitoring is configured in Step 4, where:
•
•
•
•
•
•
Step 9
peak-time1 hour duration minutes avg-rate rate [peak-time2 hour duration minutes avg-rate rate][duration offpeak-minutes avg-rate offpeak-rate] sample-interval 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 enforceSpecifies peak monitoring times when peak-offpeak monitoring is configured in Step 4, where:
•
•
•
•
•
•
•
•
•
•
Step 10
penalty-period minutes [time-of-day hour]
Example:Router(enforce-rule)# penalty-period 10(Optional) Specifies the time period that an enforced QoS profile should be in effect for subscribers who violate their registered QoS profiles, where:
•
•
Step 11
enabled
Example:Router(enforce-rule)# enabled
(Optional) Activates the enforce-rule and begins subscriber traffic management.
Step 12
end
Example:Router(enforce-rule)# end
Exits enforce-rule configuration mode and returns to privileged EXEC mode.
Examples
This section provides command-line interface (CLI) examples, including the help feature for some of the enforce-rule commands.
Legacy Monitoring Configuration Example
The following example shows a sample configuration of an enforce-rule for legacy monitoring:
Router(config)# cable qos enforce-rule testRouter(enforce-rule)# monitoring-basics ?legacy Enable legacy (same average rate for all day) monitoringpeak-offpeak Enable peak-offpeak monitoringRouter(enforce-rule)# monitoring-basics legacy ?docsis10 Enforce-rule will map to docsis 1.0 modemsdocsis11 Enforce-rule will map to docsis 1.1 modemsRouter(enforce-rule)# monitoring-basics legacy docsis11Router(enforce-rule)# service-class ?enforced Enforced service classregistered Registered service classRouter(enforce-rule)# service-class registered ?WORD Registered service class nameRouter(enforce-rule)# service-class registered BEUSRouter(enforce-rule)# service-class enforced testRouter(enforce-rule)# duration ?<10-10080> Duration in minutesRouter(enforce-rule)# duration 10 ?avg-rate Average rate for the duration in kbits/secRouter(enforce-rule)# duration 10 avg-rate ?<1-4294967> average rate in kbits/secRouter(enforce-rule)# duration 10 avg-rate 2 ?sample-interval Rate of sampling in MinutesRouter(enforce-rule)# duration 10 avg-rate 2 sample-interval ?<1-30> Sampling rate in MinutesRouter(enforce-rule)# duration 10 avg-rate 2 sample-interval 10 ?downstream downstreamupstream upstreamRouter(enforce-rule)# duration 10 avg-rate 2 sample-interval 10 upstream ?enforce enforce the qos-profile automatically<cr>Router(enforce-rule)# duration 10 avg-rate 2 sample-interval 10 upstream enfRouter(enforce-rule)# $ avg-rate 2 sample-interval 10 upstream enforceRouter(enforce-rule)# enabledRouter(enforce-rule)# endPeak-offpeak Monitoring Configuration Example
The following example shows a sample configuration of an enforce-rule for peak-offpeak monitoring:
Router(config)# cable qos enforce-rule testRouter(enforce-rule)# monitoring-basics peak-offpeakRouter(enforce-rule)# monitoring-basics peak-offpeak docsis10Router(enforce-rule)# qos-profile ?enforced Enforced qos profileregistered QoS profile indexRouter(enforce-rule)# qos-profile registered ?<1-255> Registered QoS profile indexRouter(enforce-rule)# qos-profile registered 5Router(enforce-rule)# qos-profile enforced 4Router(enforce-rule)# peak-time1 6 ?duration First peak durationRouter(enforce-rule)# peak-time1 6 duration ?<60-1440> Duration in minutesRouter(enforce-rule)# peak-time1 6 duration 180 ?avg-rate First peak average rate in kbits/secRouter(enforce-rule)# peak-time1 6 duration 180 avg-rate ?<1-4294967> Average rate in kbits/secRouter(enforce-rule)# peak-time1 6 duration 180 avg-rate 2 ?duration Off-peak durationpeak-time2 Second peak timesample-interval Rate of sampling in minutesRouter(enforce-rule)# peak-time1 6 duration 180 avg-rate 2 peak-time2 ?<10-1440> Start of second peak timeRouter(enforce-rule)# peak-time1 6 duration 180 avg-rate 2 peak-time2 18 ?duration Second peak durationRouter(enforce-rule)# $6 duration 180 avg-rate 2 peak-time2 18 duration ?<10-1440> Duration in minutesRouter(enforce-rule)# $6 duration 180 avg-rate 2 peak-time2 18 duration 240 ?avg-rate Second peak average rate in kbits/secRouter(enforce-rule)# $ 180 avg-rate 2 peak-time2 18 duration 240 avg-rate ?<1-4294967> Average rate in kbits/secRouter(enforce-rule)# $ 180 avg-rate 2 peak-time2 18 duration 240 avg-rate 3 ?duration Off-peak durationsample-interval Rate of sampling in minutesRouter(enforce-rule)# $ 180 avg-rate 2 peak-time2 18 duration 240 avg-rate 3 dRouter(enforce-rule)# $-time2 18 duration 240 avg-rate 3 duration 120 ?avg-rate Off-peak average rate in kbits/secRouter(enforce-rule)# $duration 240 avg-rate 3 duration 120 avg-rate 1 ?sample-interval Rate of sampling in minutesRouter(enforce-rule)# $40 avg-rate 3 duration 120 avg-rate 1 sample-interval ?<1-30> Sampling rate in MinutesRouter(enforce-rule)# $e 3 duration 120 avg-rate 1 sample-interval 10 ?downstream downstreamupstream upstreamRouter(enforce-rule)# $e 3 duration 120 avg-rate 1 sample-interval 10 upstream ?enforce enforce the qos-profile automatically<cr>Router(enforce-rule)# $on 120 avg-rate 1 sample-interval 10 upstream enforceRouter(enforce-rule)# enabledRouter(enforce-rule)# endCLI Help for peak-time Command Example
The following example shows output from the CLI help for the peak-time command:
Router(enforce-rule)# peak-time ?
<0-23> Start of first peak time, use 24 hour clock
Router(enforce-rule)# peak-time 1 ?
duration First peak duration
Router(enforce-rule)# peak-time 1 d ?
<60-1440> Duration in minutes
Router(enforce-rule)# peak-time 1 d 65 ?
First peak average rate in kbits/sec
Router(enforce-rule)# peak-time 1 d 65 a ?
<1-400000> Average rate in kbits/sec
Router(enforce-rule)# peak-time 1 d 65 a 1000 ?
duration Off-peak duration
peak-time2 Second peak time
sample-interval Rate of sampling in minutes
Router(enforce-rule)# peak-time 1 d 65 a 1000 d ?
<60-1440> Duration in minutes
Router(enforce-rule)# peak-time 1 d 65 a 1000 d 65 ?
avg-rate Off-peak average rate in kbits/sec
Router(enforce-rule)# peak-time 1 d 65 a 1000 d 65 a ?
<1-400000> Average rate in kbits/sec
Router(enforce-rule)# peak-time 1 d 65 a 1000 d 65 a 1000 ?
sample-interval Rate of sampling in minutes
Router(enforce-rule)# peak-time 1 d 65 a 1000 d 65 a 1000 s ?
<1-30> Sampling rate in Minutes
Router(enforce-rule)# peak-time 1 d 65 a 1000 d 65 a 1000 s 5 ?
downstream downstream
upstream upstream
Router(enforce-rule)# peak-time 1 d 65 a 1000 d 65 a 1000 s 5 d ?
enforce enforce the qos-profile automatically
<cr>
Router(enforce-rule)# peak-time 1 d 65 a 1000 d 65 a 1000 s 5 d
Configuring Weekend Monitoring
This section describes the tasks required to configure weekend monitoring for STM on a Cisco CMTS router.
Prerequisites
You must first configure the weekday monitoring parameters for an enforce-rule before configuring weekend monitoring. See the "Creating and Configuring an Enforce-Rule" section.
Restrictions
•
•
Configuring Different Legacy Monitoring Conditions for Weekends
Use the following procedure if you want to establish different legacy monitoring conditions for subscribers for either upstream or downstream traffic on weekend days.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Different Peak-Offpeak Monitoring Conditions for Weekends
Use the following procedure if you want to establish different peak and offpeak monitoring conditions for subscribers for either upstream or downstream traffic on weekend days.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Disabling Weekend Monitoring
Use the following procedure to turn off the weekend monitoring configuration and monitor on weekdays only.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Removing Weekend Monitoring Conditions and Use the Same Monitoring Criteria Every Day
Use the following procedure to remove the specified weekend monitoring conditions and use the same monitoring criteria all week (including weekends).
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Disabling an Enforce-Rule
Use the following procedure to disable an enforce-rule. The enforce-rule remains in the CMTS configuration file, but any subscriber traffic management that uses this enforce-rule ends.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Removing an Enforce-Rule
Use the following procedure to delete an enforce-rule and remove it from the CMTS configuration file. Any subscriber traffic management that uses this rule also ends.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Changing a Cable Modem Service Class
Use the following procedure to change a QoS service class for a particular DOCSIS 1.1 cable modem.
Restrictions
•
•
•
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Monitoring the Subscriber Traffic Management Feature on the Cisco CMTS Routers
This section describes the following tasks that can be used to monitor the Subscriber Traffic Management feature:
•
•
Displaying the Currently Defined Enforce-Rules
To display all enforce-rules that are currently defined on the Cisco CMTS router, or the definitions for a particular enforce-rule, use the show cable qos enforce-rule command in privileged EXEC mode.
For offpeak monitoring, use the show cable qos enforce-rule command to display the monitoring duration and average-rate values applicable for that time of day. If no monitoring is taking place, 0 is displayed.
The following example shows sample output from the show cable qos enforce-rule command for all configured enforce-rules:
Router# show cable qos enforce-ruleName Dur Dir byte-cnt Auto rate penalty Reg Enf Ena Persist(min) (kbytes) enf (min) (min) QoS QoSresidential 10 us 5 act 1 10080 5 10 Yes Yesef-q11d 30 ds 150 act 1 20 11 99 Yes Yesef-q11u 30 us 60 act 1 20 11 99 Yes Yesef-q21 720 us 60 act 1 10 21 81 Yes Yesef-q21d 300 ds 150 act 1 10 21 81 Yes Yesef-q22 720 us 60 act 1 10 22 82 Yes Yesef-q22d 300 ds 150 act 1 10 22 82 Yes Noef-q23 720 us 60 act 1 10 23 83 Yes Yesef-q23d 300 ds 150 act 1 10 23 83 Yes Yesef-q24 720 us 60 act 1 10 24 84 Yes Yesef-q24d 300 ds 150 act 1 10 24 84 Yes Yesef-q25 720 us 60 act 1 10 25 85 Yes Yesef-q25d 300 ds 150 act 1 10 25 85 Yes Yesef-q26 720 us 60 act 1 10 26 86 Yes Yesef-q26d 300 ds 150 act 1 10 26 86 Yes Yesef-q27 720 us 60 act 1 10 27 87 Yes Yesef-q27d 300 ds 150 act 1 10 27 87 Yes Yesef-q28 720 us 60 act 1 10 28 88 Yes Yesef-q28d 300 ds 150 act 1 10 28 88 Yes Noef-q5d 300 ds 150 act 1 10 5 99 Yes Yesef-q5u 720 us 600 act 1 10 5 99 Yes YesThe following example shows sample output from the show cable qos enforce-rule command for a particular enforce-rule named "test":
Router# show cable qos enforce-rule testName Type Dur Dir Avg-rate Auto rate Reg Enf En Per(min) kbits/s enf (min)test p-off 120 us 1 act 10 255 4 Y YThe following example shows sample output from the show cable qos enforce-rule verbose command for a particular enforce-rule named "test":
Router# show cable qos enforce-rule test verboseName : testVersion : docsis10Monitoring Type : peak-offpeakRegistered : 255Enforced : 4Monitoring duration : 120 (in minutes)Sample-rate : 10 (in minutes)Average-rate : 1 kbits/secDirection : upstreamAuto enforce : activePenalty time : 10080 (in minutes)Rule enabled : YesPersistence : YesFirst Peak time : 6Duration : 180 (in minutes)First Average-rate : 2 kbits/secSecond peak time : 18Duration : 240 (in minutes)Second Averate-rate : 3 kbits/secOff peak duration : 120 (in minutes)Offpeak Average-rate: 1 kbits/secrouter#sh clock*17:30:50.259 UTC Thu Feb 26 2004The following example shows sample output from the show cable qos enforce-rule verbose command for a particular enforce-rule named "test" that has specified peak-offpeak weekend monitoring options:
Router# show cable qos enforce-rule test verboseName : testVersion : docsis10Monitoring Type : peak-offpeakRegistered : 255Enforced : 4Monitoring Duration : 120 (in minutes)Sample-rate : 10 (in minutes)Average-rate : 1 kbits/secDirection : upstreamPenalty Time : 10080 (in minutes)Penalty End-time : 23 (time of day in hrs)Rule Enabled : YesPersistence : YesWeek-end : YesFirst Peak Time : 6Duration : 180 (in minutes)First Average-rate : 2 kbits/secSecond Peak Time : 18Duration : 240 (in minutes)Second Averate-rate : 3 kbits/secOffpeak Duration : 120 (in minutes)Offpeak Average-rate : 1 kbits/secAuto-enforce : activeWeekend First Peak Time : 8Weekend First Duration : 120 (in minutes)Weekend First Average-rate : 2 kbits/secWeekend Second Peak Time : 18Weekend Second Duration : 180 (in minutes)Weekend Second Average-rate : 5 kbits/secWeekend Offpeak Duration : 240 (in minutes)Weekend Offpeak Average-rate : 4 kbits/secWeekend Auto-enforce : activeDisplaying the Current Subscriber Usage
To display the usage for all subscribers on a cable interface, use the show cable subscriber-usage command in privileged EXEC mode without any options.
To display the usage for just those subscribers who are violating their registered quality of service (QoS) profiles, use the show cable subscriber-usage over-consume form of the command.
The following example shows sample output from the show cable subscriber-usage command for all users on the specified cable interface:
Router# show cable subscriber-usage cable 6/1/0Sfid Mac Address Enforce-rule Total-Kbyte Last-detect Last-penalty PenName Count time time Flag3 0007.0e03.110d efrule-q5 121944817 Jan1 03:44:08 Jan1 03:54:08 Act4 0007.0e03.110d efrule-q5d 1879076068 Jan1 03:35:05 Jan1 03:45:06 Act5 0007.0e03.1431 efrule-q5 120052387 Jan1 03:44:18 Jan1 03:54:18 Act6 0007.0e03.1431 efrule-q5d 1838493626 Jan1 03:34:55 Jan1 03:44:55 Act7 0007.0e03.1445 efrule-q5 120919427 Jan1 03:44:08 Jan1 03:54:08 Act8 0007.0e03.1445 efrule-q5d 1865955172 Jan1 03:35:06 Jan1 03:45:06 Act9 0007.0e03.1225 efrule-q5 120200155 Jan1 03:44:18 Jan1 03:54:18 Act10 0007.0e03.1225 efrule-q5d 1839681070 Jan1 03:34:55 Jan1 03:44:55 -11 0007.0e03.0cb1 efrule-q5 122941643 Jan1 03:43:58 Jan1 03:53:58 Act12 0007.0e03.0cb1 efrule-q5d 1889107176 Jan1 03:35:06 Jan1 03:45:06 Act13 0007.0e03.1435 efrule-q5 119504795 Jan1 03:44:18 Jan1 03:54:18 Act14 0007.0e03.1435 efrule-q5d 1835164034 Jan1 03:34:55 Jan1 03:44:55 -By default, the display is sorted by the service flow ID (SFID). To sort the display by the subscriber byte count, with the largest byte counts listed first, use the sort-byte-count option. The following example shows sample output for show cable subscriber-usage sort-byte-count form of the command:
Note
Router# show cable subscriber-usage sort-byte-countSfid Mac Address Enforce-rule Total-Kbyte Last-detect Last-penalty PenName Count time time Flag7 0007.0e03.2cad test1 65157114 Feb24 11:36:34 Mar3 11:36:34 Act9 0007.0e03.2c45 test1 16381014 -5 0007.0e03.2c25 test1 13440960 -Configuration Examples for Subscriber Traffic Management on the Cisco CMTS Routers
This section lists sample configurations for the Subscriber Traffic Management feature on a CMTS router:
•
•
•
•
•
DOCSIS Configuration File and STM Service Classes: Example
The following example shows a sample DOCSIS configuration file along with sample registered and enforced QoS service classes that you could define on a Cisco CMTS router to perform subscriber traffic management.
DOCSIS Configuration File Options
This is an example of a very basic set of options that you can configure for a cable modem in your DOCSIS configuration file that supports a successful configuration of new QoS service class options on the Cisco CMTS router.
Note
The following example shows the configuration of two service classes named "BE-STM-US-1" and "BE-STM-DS-1" in a DOCSIS configuration file to define a basic set of upstream and downstream parameters:
03 (Net Access Control) = Yes17 (Baseline Privacy Block)S01 (Authorize Wait Timeout) = 1018 (Maximum Number of CPE) = 1024 (Upstream Service Flow Block)S01 (Flow Reference) = 1S04 (Service Class Name) = BE-STM-US-1S06 (QoS Parameter Set Type) = 725 (Downstream Service Flow Block)S01 (Flow Reference) = 2S04 (Service Class Name) = BE-STM-DS-1S06 (QoS Parameter Set Type) = 729 (Privacy Enable) = YesThe following example shows sample cable service class commands on the Cisco CMTS router for configuration of subscriber traffic management that correspond to the service class names in the DOCSIS configuration file of "BE-STM-US-1" and "BE-STM-DS-1." These service classes correspond to the registered service classes configured by the service-class registered command for the QoS enforce-rules shown later in this example:cable service class 2 name BE-STM-US-1cable service class 2 upstreamcable service class 2 max-rate 2000000cable service class 2 max-burst 3044cable service class 3 name BE-STM-DS-1cable service class 3 downstreamcable service class 3 max-rate 30000000The following example shows sample cable service class commands on the Cisco CMTS router that configure new QoS parameters for identified subscribers to limit bandwidth using the max-rate parameter. These service classes correspond to the enforced service classes configured by the service-class enforced command for the QoS enforce rules shown later in this example:
cable service class 102 name BEUS-1cable service class 102 upstreamcable service class 102 max-rate 48888cable service class 102 max-burst 3044cable service class 103 name BEDS-1cable service class 103 downstreamcable service class 103 max-rate 988888The following example shows configuration of the corresponding enforce-rules for upstream and downstream monitoring, which identifies the registered and enforced service classes:
cable qos enforce-rule US-1monitoring-basics legacy docsis11penalty-period 10service-class registered BE-STM-US-1service-class enforced BEUS-1duration 10 avg-rate 1 sample-interval 10 up enfenabled!cable qos enforce-rule DS-1monitoring-basics legacy docsis11penalty-period 10service-class registered BE-STM-DS-1service-class enforced BEDS-1duration 10 avg-rate 1 sample-interval 10 do enfenabledDownstream Configuration: Example
The following example shows a typical enforce-rule configuration for traffic in the downstream direction:
!cable qos enforce-rule downstream-rulepenalty-period 10registered qos-profile 5enforced qos-profile 99monitoring-duration 30 sample-rate 10activate-rule at-byte-count 50000000 downstream enforceenabledUpstream Configuration: Example
The following example shows a typical enforce-rule configuration for traffic in the upstream direction:
!cable qos enforce-rule upstream-rulepenalty-period 10registered qos-profile 5enforced qos-profile 99monitoring-duration 30 sample-rate 10activate-rule at-byte-count 50000000 upstream enforceenabledDownstream and Upstream Configuration: Example
The following example shows a typical enforce-rule configuration for traffic in both the downstream and upstream directions. Two separate rules are created, using the identical configuration, except for the upstream and downstream keywords in the activate-rule command.
Note
!cable qos enforce-rule downstream-rulepenalty-period 10registered qos-profile 5enforced qos-profile 99monitoring-duration 30 sample-rate 10activate-rule at-byte-count 5 downstream enforceenabledcable qos enforce-rule upstream-rulepenalty-period 10registered qos-profile 5enforced qos-profile 99monitoring-duration 30 sample-rate 10activate-rule at-byte-count 5 upstream enforceenabledWeekend Monitoring Configuration: Example
The following example shows a sample configuration of peak-offpeak weekend monitoring for DOCSIS 1.0 cable modems:
cable qos enforce-rule monitoringmonitoring-basics peak-offpeak docsis10penalty-period 60qos-profile registered 6qos-profile enforced 100peak-time1 10 duration 120 avg-rate 10 peak-time2 23 duration 60 avg-rate 10 sample-interval 10 upstream enforceweekend peak-time1 8 duration 60 avg-rate 100 peak-time2 20 duration 60 avg-rate 10000 duration 90 avg-rate 20000 sample-interval 20 downstream enforceenabledAdditional References
For additional information related to the Subscriber Traffic Management feature, refer to the following references:
Related Documents
Standards
Data-over-Cable Service Interface Specifications Radio Frequency Interface Specification, version 1.1 (http://www.cablemodem.com)
Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 Compliant RF Interfaces
1 Not all supported standards are listed.
MIBs
•
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
1 Not all supported MIBs are listed.
RFCs
Technical Assistance
Feature Information for Subscriber Traffic Management for the Cisco CMTS Routers
Table 2 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
Guest
