All MIBs › DOCS-QOS3-MIB › docsQosServiceFlowPkts
docsQosServiceFlowPkts
Module: DOCS-QOS3-MIB
OID (symbolic): DOCS-QOS3-MIB::docsQosServiceFlowPkts
OID (numeric): 1.3.6.1.4.1.4491.2.1.21.1.4.1.1
Node type: OBJECT-TYPE
Type: Counter64
Access: read-only
Description:
For outgoing Service Flows, this attribute counts the number of Packet Data PDUs forwarded to this Service Flow. For incoming upstream CMTS service flows, this attribute counts the number of Packet Data PDUs actually received on the Service Flow identified by the SID for which the packet was scheduled. CMs not classifying downstream packets may report this attribute's value as 0 for downstream Service Flows. This attribute does not count MAC-specific management messages.
Particularly for UGS flows, packets sent on the primary Service Flow in violation of the UGS grant size should be counted only by the instance of this attribute that is associated with the primary service flow.
Unclassified upstream user data packets (i.e., non- MAC-management) forwarded to the primary upstream Service Flow should be counted by the instance of this attribute that is associated with the primary service flow.
This attribute does include packets counted by ServiceFlowPolicedDelayPkts, but does not include packets counted by ServiceFlowPolicedDropPkts and ServiceFlowPHSUnknowns.
This counter's last discontinuity is the ifCounterDiscontinuityTime for of the associated MAC Domain interface index.
What is docsQosServiceFlowPkts?
This read-only counter tracks the total number of Packet Data Protocol Data Units (PDUs) that have been forwarded on a specific QoS service flow; for outgoing flows it counts PDUs sent to the service flow, and for incoming upstream CMTS flows it counts actual PDUs received on the SID-identified flow. Cable operators use this metric to monitor bandwidth usage and validate that traffic is flowing through the intended service flows with correct QoS treatment. This counter is essential for billing, performance verification, and troubleshooting data delivery in cable modem networks.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.21.1.4.1.1 snmpwalk -v2c -c public <target> DOCS-QOS3-MIB::docsQosServiceFlowPkts
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.21.1.4.1.1.1 snmpget -v2c -c public <target> DOCS-QOS3-MIB::docsQosServiceFlowPkts.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> docsQosServiceFlowPkts.1
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4 | private | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4.1 | enterprises | ANIROOT-MIB |
| 1.3.6.1.4.1.4491 | cableLabs | CLAB-DEF-MIB |
| 1.3.6.1.4.1.4491.2 | clabProject | CLAB-DEF-MIB |
| 1.3.6.1.4.1.4491.2.1 | clabProjDocsis | CLAB-DEF-MIB |
| 1.3.6.1.4.1.4491.2.1.21 | docsQos3Mib | CLAB-DEF-MIB |
| 1.3.6.1.4.1.4491.2.1.21.1 | docsQosMibObjects | DOCS-QOS3-MIB |
| 1.3.6.1.4.1.4491.2.1.21.1.4 | docsQosServiceFlowStatsTable | DOCS-QOS3-MIB |
| 1.3.6.1.4.1.4491.2.1.21.1.4.1 | docsQosServiceFlowStatsEntry | DOCS-QOS3-MIB |
| 1.3.6.1.4.1.4491.2.1.21.1.4.1.1 | docsQosServiceFlowPkts | DOCS-QOS3-MIB |