-
Cisco CMTS Router Quality of Service Features Configuration Guide, Release 12.2SC
-
Default DOCSIS ToS Overwrite
-
DOCSIS 1.1 for the Cisco CMTS Routers
-
DOCSIS WFQ Scheduler on the Cisco CMTS Routers
-
Dynamic Bandwidth Sharing on the Cisco CMTS Router
-
Fairness Across DOCSIS Interfaces
-
MQC QoS on the Cisco CMTS Routers
-
Service Flow Admission Control for the Cisco CMTS Routers
-
Subscriber Traffic Management for the Cisco CMTS Routers
-
Feedback
Table Of Contents
DOCSIS WFQ Scheduler on the Cisco CMTS Routers
Prerequisites for DOCSIS WFQ Scheduler
Restrictions for DOCSIS WFQ Scheduler
Information About DOCSIS WFQ Scheduler
Maximum Sustained Traffic Rate
Enhanced Rate Bandwidth Allocation
DOCSIS 3.0 Downstream Bonding Support with Bonding Group Dynamic Bandwidth Sharing
How to Configure DOCSIS WFQ Scheduler
Mapping DOCSIS Priority to Excess Ratio
Verifying the Service Flows and Queues
Verifying the DOCSIS Priority to Excess Ratio Mapping
Verifying the HQF Queue Detail Information
Feature Information for DOCSIS WFQ Scheduler
DOCSIS WFQ Scheduler on the Cisco CMTS Routers
First Published: December 18, 2008
Last Updated: July 11, 2012
Cisco IOS Release 12.2(33)SCB introduces the Data-over-Cable Service Interface Specifications (DOCSIS) Weighted Fair Queuing (WFQ) Scheduler on the Cisco uBR10012 Universal Broadband Router. The DOCSIS WFQ Scheduler is an output packet scheduler that provides output scheduling services on both WAN uplink interfaces and DOCSIS downstream interfaces.
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 DOCSIS WFQ Scheduler" 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 DOCSIS WFQ Scheduler
•
•
•
•
Prerequisites for DOCSIS WFQ Scheduler
Table 1 shows the Cisco Cable Modem Termination System (CMTS) hardware compatibility prerequisites for this feature.
Table 1 DOCSIS 3.0 WFQ Scheduler QoS Support Hardware Compatibility Matrix
Cisco uBR10012 Universal Broadband Router
Cisco IOS Release 12.2(33)SCB and later releases
•
•
Cisco IOS Release 12.2(33)SCB and later releases
•
Cisco IOS Release 12.2(33)SCC and later
•
Cisco IOS Release 12.2(33)SCE and later
•
Cisco IOS Release 12.2(33)SCB and later releases
•
•
Cisco uBR7246VXR Universal Broadband Router
Cisco IOS Release 12.2(33)SCD and later releases
•
Cisco IOS Release 12.2(33)SCD and later releases
•
-
Cisco uBR7225VXR Universal Broadband Router
Cisco IOS Release 12.2(33)SCD and later releases
•
Cisco IOS Release 12.2(33)SCD and later releases
•
-
1 The Cisco UBR-MC20X20V cable interface line card has three variants: Cisco UBR-MC20X20V-0D, Cisco UBR-MC20X20V-5D, and Cisco UBR-MC20X20V-20D. The Cisco UBR-MC20X20V-0D line card supports 20 upstreams and 0 (no) downstreams. The Cisco UBR-MC20X20V-5D line card supports 20 upstreams and 5 downstreams, and the Cisco UBR-MC20X20V-20D line card supports 20 upstreams and 20 downstreams.
2 Cisco uBR3GX60V cable interface line card is not compatible with PRE2. You must use PRE4 with the Cisco uBR3GX60V cable interface line card.
3 The Cisco uBR-MC88V cable interface line card is not compatible with NPE-G1. You must use NPE-G2 with the Cisco uBR-MC88V cable interface line card.
Note
Restrictions for DOCSIS WFQ Scheduler
•
Information About DOCSIS WFQ Scheduler
The DOCSIS WFQ scheduling engine is used to provide output packet scheduling services, including absolute priority queueing, weighted fair queueing, minimum rate guarantee, traffic shaping, and DOCSIS bonding group dynamic bandwidth sharing on the Cisco uBR10012 universal broadband router. It replaces the existing Versatile Traffic Management System (VTMS) scheduler.
The DOCSIS WFQ Scheduler provides services on both WAN uplink interfaces and DOCSIS downstream interfaces. The scheduling parameters on WAN uplink interfaces are configured through the Modular QoS CLI (MQC). On cable downstream interfaces, queues are created for DOCSIS service flows with parameters configured by DOCSIS downstream QoS type, length, values (TLVs).
Starting with Cisco IOS Release 12.2(33)SCG, the default queue size for the DOCSIS service flows (with bandwidth greater than 150 Mbps) is increased from 255 to higher values based on the bandwidth on the cable downstream interfaces (see Table 2). Additionally, the queue limit for all service flows can also be adjusted using the cable queue-limit command. For more information, see the Cisco IOS CMTS Cable Command Reference.
Note
Table 2 is an example of the queue size based on Annex B 256 QAM channels.
For DOCSIS downstream interfaces, the DOCSIS WFQ Scheduler implements traffic shaping and physical link scheduling at two separate layers, which allows it to account for traffic overhead differently. This allows the scheduler to schedule accurately at the physical layer while conforming to DOCSIS specifications.
The DOCSIS WFQ Scheduler also allows significant enhancement to the queue scaling limits compared to the VTMS scheduler.
Table 3 shows the queue scaling number comparisons.
Table 3 Queue Scaling Limits
Cisco IOS Release 12.2(33)SCA or earlierTotal Number of Queues Per System1
384,000
384,000
65,534
64,000
Total Number of CIR Queues
120,000
120,000
65,534
64,000
Number of Queues Per GE Link
162
162
323
N/A
Maximum Number of Packets in PXF
Small 1,703,936
Large 245,760
Small 52,428
Large 32,768
Small 52,428
Large 32,768
Small 150,000
Large 50,000
Queue Size on WAN Uplink
16,00-32,00
16,00-32,00
32,000-16,000
N/A
Queue Size on DOCSIS Downstream4
255
255
64
128
1 Includes network-control and default queues.
2 14 user-configurable queues, 1 class-default queue, and 1 system queue.
3 30 user-configurable queues, 1 class-default queue, and 1 system queue.
4 Starting Cisco IOS Release 12.2(33)SCG, the Queue Size on the PRE4 and PRE2 modules varies from 255 to 1023 with bandwidth 150 Mbps to 600 Mbps. See Table 2.
The following sections explain the DOCSIS WFQ Scheduler features:
•
•
Queue Types
The DOCSIS WFQ Scheduler feature supports the following types of queues:
•
•
•
Priority Queues
Priority queues are serviced with absolute priority over all the other queues. On DOCSIS downstream interfaces, the priority queues are configured by DOCSIS applications that request a priority service flow, for example, a packet cable voice service flow. On WAN uplink interfaces, the priority queues are configured by the MQC policy maps.
The following restrictions apply to priority queues:
•
•
CIR Queues
A CIR queue is guaranteed to be serviced with at least the Committed Information Rate (CIR). CIR queues are used to service DOCSIS service flows with non-zero minimum reserved rates. If the offered load to a CIR queue exceeds its CIR value, the excess traffic is serviced as best effort traffic.
The following conditions apply to CIR queues:
•
•
Best Effort Queues
The Best Effort (BE) queues share the interface bandwidth not used by the priority queue and the CIR queues. The sharing is in proportion to each queue's quantum value.
The following conditions apply to BE queues:
•
•
DOCSIS QoS Support
DOCSIS defines a set of quality of service (QoS) parameters, including traffic priority, maximum sustained traffic rate, minimum reserved traffic rate, maximum traffic burst, maximum downstream latency, and peak traffic rate.
The downstream service flows use the QoS parameters to specify the desired QoS. The downstream policer and scheduler provides services such as traffic shaping, bandwidth provisioning, traffic prioritization, and bandwidth guarantee.
The DOCSIS service flow parameters are mapped to the packet queue parameters and provided with appropriate QoS support for the packet queues to support the DOCSIS parameters
The following DOCSIS QoS parameters are supported:
•
•
•
Note
Traffic Priority
The downstream channel bandwidth available to the best effort traffic, namely the channel bandwidth minus the amount consumed by the priority traffic and the CIR traffic, is allocated to the best effort service flows in proportion to their DOCSIS traffic priorities. For example, if there are three service flows sending packets at a particular moment over the same downstream channel, and their DOCSIS traffic priorities are 0, 1 and 3, respectively, their share of the channel bandwidth will be 1:2:4. To achieve this bandwidth allocation, each service flow is assigned a value known as its excess ratio which is derived from its DOCSIS priority. Table 4 shows the default mappings of DOCSIS priority to excess ratio.
Note
Table 4 DOCSIS Priority to Excess Ratio Mapping
0
4
1
8
2
12
3
16
4
20
5
24
6
28
7
32
Custom DOCSIS Priority to Excess Ratio Mappings
Cisco IOS Release 12.2(33)SCC introduces the option to configure custom priority to excess ratio mappings for downstream service flows that override the default mappings listed in Table 4.
Note
The option to configure priority to excess ratio mappings is available on a per downstream forwarding interface basis and is applicable to legacy cable, wideband and modular cable, and integrated cable interfaces.
Note
The cable downstream qos wfq weights command is used to configure the mappings. For more details on this command, refer to Cisco IOS CMTS Cable Command Reference Guide.
Maximum Sustained Traffic Rate
The maximum sustained traffic rate (MSR) specifies the peak information rate of a service flow. The MSR of a service flow is mapped to the shape rate of the packet queue. When the maximum sustained traffic rate is not specified or set to zero, its traffic rate becomes limited only by the physical channel capacity set by DOCSIS specifications.
Minimum Reserved Traffic Rate
The minimum reserved traffic rate (MRR) specifies the minimum rate reserved for a service flow. The MRR of a service flow is mapped to the CIR of the packet queue, which ensures the minimum amount of bandwidth a queue gets under congestion. When the MRR is not specified, the CIR is set to zero as per DOCSIS specifications.
High Priority Traffic
High priority traffic flows are mapped to a Low Latency Queue (LLQ) on the data forwarding interface. The packets in LLQ are serviced with absolute priority over other queues on the same interface.
The following service flows require high priority service:
•
•
•
Enhanced Rate Bandwidth Allocation
The DOCSIS WFQ Scheduler supports the Enhanced Rate Bandwidth Allocation (ERBA) feature for service flows. The ERBA feature allows cable modems (CMs) to burst their temporary transmission rates up to the full line rate for short durations of time. This capability provides higher bandwidth for instantaneous bandwidth requests without having to make changes to existing service levels in the QoS profile.
The DOCSIS WFQ Scheduler allows each service flow to have one dedicated queue. When ERBA is enabled for the service flow, the peak rate is implemented as the queue shape rate within the scheduler, while the maximum sustained rate is set as the token bucket refill rate. When ERBA is turned off, the burst size and the peak rate value are not used.
The maximum traffic burst parameter is used to control a service flow burst duration, to burst up to the channel line rate or a configured peak rate, when it is within its maximum burst size allowance. On the Cisco uBR10012 Universal Broadband Router, the cable ds-max-burst command is used to control this behavior explicitly.
For more details on this behavior and the CLI, refer to Cisco IOS CMTS Cable Command Reference Guide.
Note
Table 5 summarizes the ERBA support for the Cisco uBR10012 router.
In Cisco uBR7246VXR and Cisco uBR7225VXR routers, the dual token bucket-based shaper is used to support ERBA on the Cisco uBR-MC88V line card (the ERBA feature is always enabled on the Cisco uBR-MC88V line card). The dual token bucket shaper has two independent token buckets for each service flow. The maximum rate of one bucket is configured to MSR and the maximum tokens are set to maximum traffic burst. The other bucket is configured with the refilling rate of the peak-rate and the maximum tokens are set to the default level, of 4 milliseconds. Packets are shaped if any of the two buckets are exhausted.
Table 6 summarizes the ERBA dual token bucket configuration for the Cisco uBR7246VXR and Cisco uBR7225VXR routers.
For information about ERBA support on the Cisco CMTS routers, refer to Using Enhanced Bandwidth Rate Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems at the following location: http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_docsis11.html#wp1274325
Peak Traffic Rate
Note
The peak-rate option of the cable ds-max-burst command allows you to specify the peak rate an ERBA-enabled service flow can use. The peak-rate value is a global value and is applied to all service flows created after the configuration of the cable ds-max-burst command. The default value of the peak-rate is zero.
If the DOCSIS 3.0 TLV 25.27 is specified for a service flow, the peak-rate value is set as the TLV value. However, if ERBA is not turned on for a service flow, the peak-rate value is ignored.
The peak-rate value can also be configured through cable service class command which forms part of the service class template. During modem registration or Dynamic Service Addition (DSA) operation, the service class name TLV 25.4 is sent to create the static or dynamic downstream service flow that matches the service class template. These downstream service flows are created with a specific peak-rate. If the peak-rate is not specified, then the value specified by the cable ds-max-burst command is used.
If a service flow has both service class and TLV 25.27 defined peak-rate, then the peak-rate value specified in the TLV is used.
Some of the DOCSIS 1.x and DOCSIS 2.0 cable modems, which are not fully DOCSIS 1.x or DOCSIS 2.0 compliant, may fail to come online when they receive TLV 25.27 from the Cisco CMTS during registration. In order to overcome this you can configure the cable service attribute withhold-TLVs command with the peak-rate keyword to restrict sending of this TLV to non-DOCSIS 3.0 cable modems.
For more details on the cable service class and cable service attribute withhold-TLVs commands, see Cisco IOS CMTS Cable Command Reference Guide.
DOCSIS 3.0 Downstream Bonding Support with Bonding Group Dynamic Bandwidth Sharing
DOCSIS 3.0 introduces the concept of downstream channel bonding. Each Bonding Group (BG) is made up of a collection of downstream channels, which can be used by one or more bonding groups. Each downstream channel can also serve as a primary channel in a MAC domain and carry non-bonded traffic, while being part of a BG.
Prior to DOCSIS 3.0 standards, the downstream service flows were associated with a single downstream interface, which in turn corresponded to a physical downstream on an RF channel. In DOCSIS 3.0, the downstream service flows are associated with the downstream bonding groups. These bonding groups can use multiple downstream RF channels.
On the Cisco uBR10012 universal broadband router, the DOCSIS 3.0 downstream channel bonding is supported on the SPA RF channels. To efficiently utilize the underlying RF channel bandwidth and to provide QoS to the downstream service flows, dynamic bandwidth sharing (DBS) is supported on the interfaces using SPA RF channels.
DBS is the dynamic allocation of bandwidth for wideband (WB), integrated cable (IC), and modular-cable (MC) interfaces sharing the same downstream channel. Due to the channel sharing nature of the bonding groups, the bandwidth available to bonding groups or non-bonded channels is not fixed. The bandwidth depends on the configuration and the traffic load on the WB, IC, or MC.
Note
In the DBS mode, the bandwidth of the shared RF channels is dynamically allocated among the WB, IC, and MC interfaces. The DBS enables efficient use of the underlying RF channel bandwidth even in the presence of high burst traffic. The DBS is configured at the WB, IC, or MC interface level. By default, bandwidth for a WB, IC, or MC channel is statically allocated (non-DBS).
DBS does not prevent static bandwidth configuration. If a static portion of the bandwidth is configured on any RF channel that one or more DBS-enabled channel utilizes, that portion is subtracted from the RF channel bandwidth. This portion of bandwidth is dedicated to the non-DBS interface and becomes unavailable to the DBS WB, IC, or MC interfaces.
For information about DBS support on the Cisco CMTS routers, refer to the Dynamic Bandwidth Sharing on the Cisco CMTS Router feature.
How to Configure DOCSIS WFQ Scheduler
You cannot configure the DOCSIS WFQ Scheduler feature as it is automatically loaded into the Parallel Express Forwarding (PXF) engine. The parameters that the schedule uses include the interface bandwidth and queue parameters.
This section describes the following required and optional procedures:
•
•
•
•
Mapping DOCSIS Priority to Excess Ratio
This section describes how to map DOCSIS priorities to custom excess ratios for downstream service flows. These custom mappings will override the default mappings.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Verifying the Service Flows and Queues
Cisco uBR10012 Router
To verify the downstream (DS) service flows and parameters for a modem, use the show cable modem [mac-address | ip-address] qos command on the Cisco uBR10012 router as shown in the following example:
Router# show cable modem 0018.f826.3453 qosSfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate ThroughputState Type7 US act 1 BE 7 0 3044 0 08 DS act N/A BE 7 0 2000000 100000 742976929 DS act N/A BE 0 0 3044 0 0To verify the detailed service flow configuration, use the show interfaces cable-interface service-flow sfid qos command on the Cisco uBR10012 router as shown in the following example:
Router# show interfaces c7/0/0 service-flow 8 qosSfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate ThroughputState Type8 DS act N/A BE 7 0 2000000 100000 7430397To verify the detailed service flow statistics, use the show interfaces cable-interface service-flow sfid counters command on the Cisco uBR10012 router as shown in the following example:
Router# show interfaces c7/0/0 service-flow 8 countersSfid Packets Bytes PacketDrop Bits/Sec Packet/Sec8 100913 121095600 374337 7431599 773To verify the service flow ID to queue ID (queue index) association, use the show cr10k-rp cable-interface sfid queue command on the Cisco uBR10012 router as shown in the following example:
Router# show cr10k-rp mod 1/2/0:0 queueDocsis queues on the interface: 0Total DOCSIS Queues Allocated: 45Available/Maximal reservable rate(kbps): 3750/3750HQF BLT Info (LBLT Group 36):LBLT 36: wt/qntm 1/10000; PBLT 1236: BW 3750Kbps, flowbit prd/ofst 512/0, rsrc/flrsrc 3/3BE Queues:CIR Queues:LL Queues:To verify the service flow queue information, use the show pxf cpu queue interface-name command on the Cisco uBR10012 router as shown in the following example:
Router# show pxf cpu queue modular-cable 1/2/0:0Cable Interface Queues:QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)131147 0/255 190 0 0 1/240 0 58131148 0/255 33820 0 0 1/10000 0 32824Cable Service Flow Queues:* Best Effort QueuesQID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)131241 0/255 0 0 0 1/240 0 32881* CIR QueuesQID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)2049 254/255 131018 485751 99 1/1920 0 32880* Low Latency QueuesQID Len/Max Dequeues TailDropsCisco uBR7246VXR and Cisco uBR7225VXR Routers
To verify the downstream hierarchical queueing framework (HQF) queue information for a modem, use the show cable modem [mac-address | ip-address] queue command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show cable modem 41.3.190.2 queue* idx/gqid Len/Limit Deqs Drops CIR MIR/PR ForwInt SFIDpkts pkts pkts kbps kbpsBE Queues:3/43 0/128 103 0 0 0/0 In5/1:1 Ca5/1:22CIR Queues:Low Latency Queues:To verify the downstream HQF queue information for the interface, use the show interfaces cable-interface service-flow sfid queue command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show interfaces c3/0 service-flow 8 queue* idx/gqid Len/Limit Deqs Drops CIR MIR/PRpkts pkts pkts kbps kbps0/53 0/128 0 0 100 15000/0I: Cable Interface Queue$: Low Latency Queue~: Low Latency Policing QueueTo verify the detailed downstream HQF information for all queues under this interface, use the show interfaces cable-interface service-flow sfid queue verbose command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show interfaces c3/0 service-flow 8 queue verboseblt (0x19FA93C0, index 6, qid 53, fast_if_number 20) layer CLASS_HIER0scheduling policy: FIFO (110)classification policy: NONE (120)drop policy: TAIL (141)packet size fixup policy: NONE (0) no of global policers: 0D/Traffic Shaping enabledblt flags: 0x22A208C scheduler: 0x1A015D80total guarantee percent 0 total remaining perc 0 total bandwidth guarantee 9500 total active 1D/Traffic Shaping enabledtxcount 0 txqbytes 0 drops 0 qdrops 0 nobuffers 0 flowdrops 0qsize 0 aggregate limit/bytes 128/375000 availbuffers 128holdqueue_out 0 perc 0.00 remaining_ratio/perc 20visible_bw 100 max_rate 15000 allocated_bw 100 vc_encap 0 ecn_threshold NONEweight A 1 quantum A 1500 credit A 1500weight B 1 quantum B 1500 credit B 1500min-rate tokens: 1500, credit: 0, depth: 1500backpressure_policy 0 scheduler_flags C03Flast_sortq[A/B] 0/0, remaining pak/particles 0/0leaf_blt[P1] 0x1A015D80 burst packets/bytes[P1] 0/0leaf_blt[P2] 0x1A015D80 burst packets/bytes[P2] 0/0leaf_blt[NOTP] 0x1A015D80 burst packets/bytes[NOTP] 0/0OUTPUT ShapingBc internal 0 Be internal 0 Time interval 4increment 15000 increment_lower 0 increment_limit 15000last visit 0 credit 0 outstanding_tokens 0 maxtokens 32000000system timer delayed 0 restart timer 0timer set 0 hqf_shape_running 562nextexpire_system_time 0 nextexpire_time_qindex -1Verifying the DOCSIS Priority to Excess Ratio Mapping
Cisco uBR10012 Router
To verify the DOCSIS priority to excess ratio mapping configuration on the Cisco uBR10012 router, use the show running-config interface command as shown in the following example:
Router# show running-config interface cable 8/0/0 | i qoscable downstream qos wfq weights 10 20 30 40 50 60 70 80To verify the excess ratio for each queue on an interface, use the show cr10k-rp interface queue be command on the Cisco uBR10012 router as shown in the following example:
Router# show cr10k cable8/1/0 queue beForwarding Interface: Cable8/1/0Docsis queues on the interface: 8Total DOCSIS Queues Allocated: 25Available/Maximal reservable rate(kbps): 25232/26000HQF BLT Info (LBLT Group 86):LBLT 110: wt/qntm 1/10000; PBLT 1286: BW 26000Kbps, flowbit prd/ofst 32/3, rsrc/flrsrc 17/17BE Queues:Queue Index: 131268, GlobalQID 83, CBLT ID 131268MinRate(Kbps) 0, ExcessRatio 4, ShapeRate(bps) 10000000, QLimit 255 Service Flow(s): rp_sf_index 32880, lc_sfid 3, min_rate(bps) 0, max_rate(bps) 10000000 peak_rate(bps) 0Queue Index: 131376, GlobalQID 81, CBLT ID 131376MinRate(Kbps) 0, ExcessRatio 32, ShapeRate(bps) 0, QLimit 255 Service Flow(s): rp_sf_index 33115, lc_sfid 39, min_rate(bps) 0, max_rate(bps) 0 peak_rate(bps) 0Queue Index: 131377, GlobalQID 82, CBLT ID 131377MinRate(Kbps) 0, ExcessRatio 24, ShapeRate(bps) 5000000, QLimit 255 Service Flow(s): rp_sf_index 33116, lc_sfid 40, min_rate(bps) 0, max_rate(bps) 5000000 peak_rate(bps) 0Queue Index: 131378, GlobalQID 85, CBLT ID 131378MinRate(Kbps) 0, ExcessRatio 32, ShapeRate(bps) 0, QLimit 255 Service Flow(s): rp_sf_index 33120, lc_sfid 35, min_rate(bps) 0, max_rate(bps) 0 peak_rate(bps) 0Queue Index: 131379, GlobalQID 88, CBLT ID 131379MinRate(Kbps) 0, ExcessRatio 24, ShapeRate(bps) 5000000, QLimit 255 Service Flow(s): rp_sf_index 33121, lc_sfid 43, min_rate(bps) 0, max_rate(bps) 5000000 peak_rate(bps) 0Queue Index: 131398, GlobalQID 109, CBLT ID 131398MinRate(Kbps) 0, ExcessRatio 32, ShapeRate(bps) 0, QLimit 255 Service Flow(s): rp_sf_index 33170, lc_sfid 37, min_rate(bps) 0, max_rate(bps) 0 peak_rate(bps) 0Queue Index: 131399, GlobalQID 110, CBLT ID 131399MinRate(Kbps) 0, ExcessRatio 24, ShapeRate(bps) 5000000, QLimit 255 Service Flow(s): rp_sf_index 33171, lc_sfid 51, min_rate(bps) 0, max_rate(bps) 5000000 peak_rate(bps) 0Cisco uBR7246VXR and Cisco uBR7225VXR Routers
To verify the DOCSIS priority to excess ratio mapping configuration on the Cisco uBR7246VXR and Cisco uBR7225VXR routers, use the show interfaces cable-interface service-flow sfid queue verbose command as shown in the following example:
Router# show interfaces c3/0 service-flow 8 queue verboseblt (0x19FA93C0, index 6, qid 53, fast_if_number 20) layer CLASS_HIER0scheduling policy: FIFO (110)classification policy: NONE (120)drop policy: TAIL (141)packet size fixup policy: NONE (0) no of global policers: 0D/Traffic Shaping enabledblt flags: 0x22A208C scheduler: 0x1A015D80total guarantee percent 0 total remaining perc 0 total bandwidth guarantee 9500 total active 1D/Traffic Shaping enabledtxcount 0 txqbytes 0 drops 0 qdrops 0 nobuffers 0 flowdrops 0qsize 0 aggregate limit/bytes 128/375000 availbuffers 128holdqueue_out 0 perc 0.00 remaining_ratio/perc 20visible_bw 100 max_rate 15000 allocated_bw 100 vc_encap 0 ecn_threshold NONEweight A 1 quantum A 1500 credit A 1500weight B 1 quantum B 1500 credit B 1500min-rate tokens: 1500, credit: 0, depth: 1500backpressure_policy 0 scheduler_flags C03Flast_sortq[A/B] 0/0, remaining pak/particles 0/0leaf_blt[P1] 0x1A015D80 burst packets/bytes[P1] 0/0leaf_blt[P2] 0x1A015D80 burst packets/bytes[P2] 0/0leaf_blt[NOTP] 0x1A015D80 burst packets/bytes[NOTP] 0/0OUTPUT ShapingBc internal 0 Be internal 0 Time interval 4increment 15000 increment_lower 0 increment_limit 15000last visit 0 credit 0 outstanding_tokens 0 maxtokens 32000000system timer delayed 0 restart timer 0timer set 0 hqf_shape_running 562nextexpire_system_time 0 nextexpire_time_qindex -1Verifying the HQF Queue Detail Information
Cisco uBR7246VXR and Cisco uBR7225VXR Routers
To verify the downstream HQF queue information for all the queues under an interface, use the show interfaces {integrated-cable | wideband-cable} slot/port: sub-interface queue command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show interfaces integrated-cable 3/0:0 queue* idx/gqid Len/Limit Deqs Drops CIR MIR/PR SFIDpkts pkts pkts kbps kbpsBE Queues:I 0/1 0/128 0 0 0 0/0 -1/42 0/128 16 0 0 0/0 Ca4/0:1162/44 0/128 4 0 0 1000/0 Ca4/0:3890CIR Queues:Low Latency Queues:I: Cable Interface Queue$: Low Latency QueueTo verify the detailed downstream HQF queue information for all the queues under an interface, use the show interfaces {integrated-cable | wideband-cable} slot/port: sub-interface queue [verbose] command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show interfaces integrated-cable 4/0:0 queue verboseblt (0x20265E60, index 0, qid 0, fast_if_number 20) layer PHYSICALscheduling policy: WFQ (111)classification policy: CLASS_BASED (122)drop policy: TAIL (141)packet size fixup policy: NONE (0) no of global policers: 0D/Traffic Shaping enabledblt flags: 0x222000 scheduler: 0x202D2D80total guarantee percent 0 total remaining perc 0 total bandwidth guarantee 0total active 0D/Traffic Shaping enabledtxcount 13 txqbytes 746 drops 0 qdrops 0 nobuffers 0 flowdrops 0qsize 0 aggregate limit/bytes 8000/0 availbuffers 8000holdqueue_out 1000 perc 0.00 remaining_ratio/perc 0visible_bw 2600 max_rate 2600 allocated_bw 2080 vc_encap 0 ecn_threshold NONEweight A 1 quantum A 1500 credit A 0weight B 1 quantum B 1500 credit B 0min-rate tokens: 13000, credit: 0, depth: 13000backpressure_policy 1 scheduler_flags C03Flast_sortq[A/B] 0/0, remaining pak/particles 0/0leaf_blt[P1] 0x202D2D80 burst packets/bytes[P1] 0/0leaf_blt[P2] 0x202D2D80 burst packets/bytes[P2] 0/0leaf_blt[NOTP] 0x202D2D80 burst packets/bytes[NOTP] 0/0OUTPUT ShapingBc internal 0 Be internal 0 Time interval 4increment 2600 increment_lower 0 increment_limit 2600last visit 145532 credit 0 outstanding_tokens 20192 maxtokens 20800system timer delayed 0 restart timer 0timer set 0 hqf_shape_running 21nextexpire_system_time 0 nextexpire_time_qindex -1next layer HQFLAYER_CLASS (max entries 2000)BE Queues:blt (0x20265DA0, index 0, qid 1, fast_if_number 20) layer CLASS_HIER0scheduling policy: FIFO (110)classification policy: NONE (120)drop policy: TAIL (141)packet size fixup policy: NONE (0) no of global policers: 0blt flags: 0x220000 scheduler: 0x202D2CC0total guarantee percent 0 total remaining perc 0 total bandwidth guarantee 0total active 1txcount 13 txqbytes 746 drops 0 qdrops 0 nobuffers 0 flowdrops 0qsize 0 aggregate limit/bytes 128/0 availbuffers 128holdqueue_out 0 perc 0.00 remaining_ratio/perc 0visible_bw 0 max_rate 26000 allocated_bw 26000 vc_encap 0 ecn_threshold NONEweight A 1 quantum A 1600 credit A 0weight B 1 quantum B 1600 credit B 46min-rate tokens: 13000, credit: 0, depth: 13000backpressure_policy 0 scheduler_flags C03Flast_sortq[A/B] 0/0, remaining pak/particles 0/0leaf_blt[P1] 0x202D2CC0 burst packets/bytes[P1] 0/0leaf_blt[P2] 0x202D2CC0 burst packets/bytes[P2] 0/0leaf_blt[NOTP] 0x202D2CC0 burst packets/bytes[NOTP] 1/46CIR Queues:Low Latency Queues:To verify the normal downstream HQF queue information for all the class layer bandwidth limited traffic (CBLT) queues under an interface, use the show interfaces {integrated-cable | wideband-cable} slot/port: sub-interface queue cblt [index | priority ] command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show interfaces integrated-cable 3/0:0 queue cblt 1blt (0x65CE3EA0, index 1, qid 45, fast_if_number 19) layer CLASS_HIER0scheduling policy: FIFO (110)classification policy: NONE (120)drop policy: TAIL (141)packet size fixup policy: NONE (0) no of global policers: 0D/Traffic Shaping enabledblt flags: 0x22A208C scheduler: 0x65D504C0total guarantee percent 0 total remaining perc 0 total bandwidth guarantee 1000 total active 1D/Traffic Shaping enabledtxcount 890 txqbytes 63900 drops 0 qdrops 0 nobuffers 0 flowdrops 0qsize 0 aggregate limit/bytes 128/100000 availbuffers 128holdqueue_out 0 perc 0.00 remaining_ratio/perc 11visible_bw 0 max_rate 4000 allocated_bw 0 vc_encap 0 ecn_threshold NONEweight A 1 quantum A 1500 credit A 1500weight B 1 quantum B 1500 credit B 1500min-rate tokens: 1500, credit: 0, depth: 1500backpressure_policy 0 scheduler_flags C03Flast_sortq[A/B] 0/0, remaining pak/particles 0/0leaf_blt[P1] 0x65D504C0 burst packets/bytes[P1] 0/0leaf_blt[P2] 0x65D504C0 burst packets/bytes[P2] 0/0leaf_blt[NOTP] 0x65D504C0 burst packets/bytes[NOTP] 0/0OUTPUT ShapingBc internal 0 Be internal 0 Time interval 4increment 4000 increment_lower 0 increment_limit 4000last visit 87456736 credit 0 outstanding_tokens 23760 maxtokens 24352peak_rate_credit 0 peak_rate_tokens 0 peak_rate_increment 0system timer delayed 0 restart timer 0timer set 0 hqf_shape_running 17254nextexpire_system_time 0 nextexpire_time_qindex -1To verify the normal and priority downstream HQF queue information for all the CBLT queues under an interface, use the show interfaces {integrated-cable | wideband-cable} slot/port: sub-interface queue cblt [index | priority ] command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show interfaces integrated-cable 3/0:0 queue cblt priorityblt (0x19FA9300, index 0, qid 52, fast_if_number 20) layer CLASS_HIER0scheduling policy: FIFO (110)classification policy: NONE (120)drop policy: TAIL (141)packet size fixup policy: NONE (0) no of global policers: 0blt flags: 0x200800 scheduler: 0x1A015CC0total guarantee percent 0 total remaining perc 0 total bandwidth guarantee 9500 total active 1txcount 114 txqbytes 12864 drops 0 qdrops 0 nobuffers 0 flowdrops 0qsize 0 aggregate limit/bytes 128/0 availbuffers 128holdqueue_out 0 perc 0.00 remaining_ratio/perc 0visible_bw 0 max_rate 37500 allocated_bw 0 vc_encap 0 ecn_threshold NONEweight A 1 quantum A 1500 credit A 1500weight B 1 quantum B 1500 credit B 1500min-rate tokens: 1500, credit: 0, depth: 1500backpressure_policy 0 scheduler_flags C83Flast_sortq[A/B] 0/0, remaining pak/particles 0/0leaf_blt[P1] 0x1A015CC0 burst packets/bytes[P1] 0/0leaf_blt[P2] 0x1A015CC0 burst packets/bytes[P2] 0/0leaf_blt[NOTP] 0x1A015CC0 burst packets/bytes[NOTP] 0/0PRIORITY LEVEL 1: total bandwidth 500 kbps, total percent 0%To verify the downstream HQF queue information for all the physical layer bandwidth limited traffic (PBLT) queues under an interface, use the show interfaces {integrated-cable | wideband-cable} slot/port: sub-interface queue pblt command on the Cisco uBR7246VXR and Cisco uBR7225VXR routers as shown in the following example:
Router# show interfaces integrated-cable 3/0:0 queue pbltblt (0x19FB4700, index 0, qid 0, fast_if_number 20) layer PHYSICALscheduling policy: WFQ (111)classification policy: CLASS_BASED (122)drop policy: TAIL (141)packet size fixup policy: NONE (0) no of global policers: 0blt flags: 0x220000 scheduler: 0x1A0210C0total guarantee percent 0 total remaining perc 0 total bandwidth guarantee 0 total active 0txcount 67743 txqbytes 6281007 drops 2 qdrops 0 nobuffers 0 flowdrops 0qsize 0 aggregate limit/bytes 8000/0 availbuffers 8000holdqueue_out 1000 perc 0.00 remaining_ratio/perc 0visible_bw 37500 max_rate 37500 allocated_bw 18000 vc_encap 0 ecn_threshold NONEweight A 1 quantum A 1500 credit A 1500weight B 1 quantum B 1500 credit B 1500min-rate tokens: 13000, credit: 0, depth: 13000backpressure_policy 1 scheduler_flags C03Flast_sortq[A/B] 0/0, remaining pak/particles 0/0leaf_blt[P1] 0x1A0210C0 burst packets/bytes[P1] 0/0leaf_blt[P2] 0x1A0210C0 burst packets/bytes[P2] 0/0leaf_blt[NOTP] 0x1A0210C0 burst packets/bytes[NOTP] 0/0Additional References
The following sections provide references related to the DOCSIS WFQ Scheduler feature.
Related Documents
CMTS cable commands
Modular Quality of Service
Enhanced Bandwidth Rate Allocation
Dynamic Bandwidth Sharing
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for DOCSIS WFQ Scheduler
Table 7 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(33)SCB or a later release appear in the table.
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, Catalyst OS, and Cisco IOS XE 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
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.
© 2008-2010 Cisco Systems, Inc. All rights reserved.
