DOCS-IETF-QOS-MIB :: docsIetfQosParamSetRequestPolicyOct

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

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

docsIetfQosParamSetRequestPolicyOct

Module: DOCS-IETF-QOS-MIB

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

OID (numeric): 1.3.6.1.2.1.127.1.2.1.21

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.

If bit 0 is the least significant bit of the least significant (4th) octet, and if bit number is increased with significance, the bit definitions are defined as follows:

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 means that the Service Flow must drop packets 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 docsIetfQosParamSetRequestPolicyOct?

A 32-bit flag field that tells the cable modem which upstream transmission opportunities it must avoid (e.g. broadcast request opportunities, piggybacking requests with data, concatenation, fragmentation, payload header suppression) for this service flow; reported as all-zeros ('00000000'H) when not configured, meaning no restrictions. Useful when troubleshooting why a modem isn't using a transmission technique you expected it to use.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.127.1.2.1.21
snmpwalk -v2c -c public <target> DOCS-IETF-QOS-MIB::docsIetfQosParamSetRequestPolicyOct

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.127.1.2.1.21.1
snmpget -v2c -c public <target> DOCS-IETF-QOS-MIB::docsIetfQosParamSetRequestPolicyOct.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::docsIetfQosParamSetRequestPolicyOct 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.2docsIetfQosParamSetTableDOCS-IETF-QOS-MIB
1.3.6.1.2.1.127.1.2.1docsIetfQosParamSetEntryDOCS-IETF-QOS-MIB
1.3.6.1.2.1.127.1.2.1.21docsIetfQosParamSetRequestPolicyOctDOCS-IETF-QOS-MIB