DOCS-QOS-MIB :: docsQosParamSetRequestPolicyOct

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsDOCS-QOS-MIBdocsQosParamSetRequestPolicyOct

docsQosParamSetRequestPolicyOct

Module: DOCS-QOS-MIB

OID (symbolic): DOCS-QOS-MIB::docsQosParamSetRequestPolicyOct

OID (numeric): 1.3.6.1.2.1.10.127.7.1.2.1.25

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: Specifies which transmit interval opportunities the CM omits for upstream transmission requests and packet transmissions. This object takes its default value for downstream service flows.

Unless otherwise indicated, a bit value of 1 means that a CM must *not* use that opportunity for upstream transmission.

Calling bit 0 the least significant bit of the least significant (4th) octet, and increasing bit number with significance, the bit definitions are as defined below:

broadcastReqOpp(0): all CMs broadcast request opportunities

priorityReqMulticastReq(1): priority request multicast request opportunities

reqDataForReq(2): request/data opportunities for requests

reqDataForData(3): request/data opportunities for data

piggybackReqWithData(4): piggyback requests with data

concatenateData(5): concatenate data

fragmentData(6): fragment data

suppresspayloadheaders(7): suppress payload headers

dropPktsExceedUGSize(8): A value of 1 mean that service flow must drop packet that do not fit in the Unsolicited Grant size

If the referenced parameter is not present in a QOS Parameter Set, the value of this object is reported as '00000000'H.

What is docsQosParamSetRequestPolicyOct?

4-byte bitmask indicating which upstream transmission-request opportunities (e.g. broadcast request slots, piggybacked requests, concatenation, fragmentation) a cable modem is forbidden from using for this service flow; downstream flows report the default value since the field doesn't apply to them. Admins use this to understand why a modem isn't using certain upstream request mechanisms, for example when concatenation has been deliberately disabled via this bitmap.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.127.7.1.2.1.25
snmpwalk -v2c -c public <target> DOCS-QOS-MIB::docsQosParamSetRequestPolicyOct

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.127.7.1.2.1.25.1
snmpget -v2c -c public <target> DOCS-QOS-MIB::docsQosParamSetRequestPolicyOct.1

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

OID Breakdown

Upper-level ancestors (8 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
1.3.6.1.2.1.10.127docsIfMibDOCS-IETF-RFI-MIB
Numeric OIDNameModule
1.3.6.1.2.1.10.127.7docsQosMIBDOCS-QOS-MIB
1.3.6.1.2.1.10.127.7.1docsQosMIBObjectsDOCS-QOS-MIB
1.3.6.1.2.1.10.127.7.1.2docsQosParamSetTableDOCS-QOS-MIB
1.3.6.1.2.1.10.127.7.1.2.1docsQosParamSetEntryDOCS-QOS-MIB
1.3.6.1.2.1.10.127.7.1.2.1.25docsQosParamSetRequestPolicyOctDOCS-QOS-MIB