DOCS-IETF-QOS-MIB :: docsIetfQosServiceFlowPkts

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DOCS-IETF-QOS-MIB › docsIetfQosServiceFlowPkts

docsIetfQosServiceFlowPkts

Module: DOCS-IETF-QOS-MIB

OID (symbolic): DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPkts

OID (numeric): 1.3.6.1.2.1.127.1.4.1.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: For outgoing Service Flows, this object counts the number of Packet Data PDUs forwarded to this Service Flow. For incoming upstream CMTS service flows, this object 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 object's value as 0 for downstream Service Flows. This object 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 object 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 object that is associated with the primary service flow.

This object does include packets counted by docsIetfQosServiceFlowPolicedDelayPkts, but does not include packets counted by docsIetfQosServiceFlowPolicedDropPkts and docsIetfQosServiceFlowPHSUnknowns.

This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.

What is docsIetfQosServiceFlowPkts?

A running Counter64 of Packet Data PDUs forwarded on this outgoing flow, or actually received on this incoming upstream flow (CMs that don't classify downstream traffic may just report 0 for downstream flows); MAC management messages aren't counted. A flat counter on a flow you expect to be busy is a strong sign traffic isn't reaching that service flow.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.127.1.4.1.1
snmpwalk -v2c -c public <target> DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.127.1.4.1.1.1
snmpget -v2c -c public <target> DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPkts.1

Start monitoring DOCSIS 1.1/2.0 cable modem/CMTS (QoS, vendor-neutral IETF standard RFC 4323) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPkts OID value, configure state conditions and alerts, and monitor any DOCSIS 1.1/2.0 cable modem/CMTS (QoS, vendor-neutral IETF standard RFC 4323) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.127docsIetfQosMIBDOCS-IETF-QOS-MIB
1.3.6.1.2.1.127.1docsIetfQosMIBObjectsDOCS-IETF-QOS-MIB
1.3.6.1.2.1.127.1.4docsIetfQosServiceFlowStatsTableDOCS-IETF-QOS-MIB
1.3.6.1.2.1.127.1.4.1docsIetfQosServiceFlowStatsEntryDOCS-IETF-QOS-MIB
1.3.6.1.2.1.127.1.4.1.1docsIetfQosServiceFlowPktsDOCS-IETF-QOS-MIB