TPLINK-QOS-MIB :: tpQosSchedulerConfig

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TPLINK-QOS-MIB › tpQosSchedulerConfig

tpQosSchedulerConfig

Module: TPLINK-QOS-MIB

OID (symbolic): TPLINK-QOS-MIB::tpQosSchedulerConfig

OID (numeric): 1.3.6.1.4.1.11863.6.22.1.2.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Here you can select the schedule mode for the switch. 0. SP-Mode: Strict-Priority Mode. In this mode, the queue with higher priority will occupy the whole bandwidth. Packets in the queue with lower priority are sent only when the queue with higher priority is empty. 1. WRR-Mode: Weight Round Robin Mode. In this mode, packets in all the queues are sent in order based on the weight value for each queue. You can also config the TC queues' weight with values 1-127. 2. SP+WRR-Mode: Strict-Priority + Weight Round Robin Mode. In this mode, this switch provides two scheduling groups, SP group and WRR group. Queues in SP group and WRR group are scheduled strictly based on strict-priority mode while the queues inside WRR group follow the WRR mode. In SP+WRR mode, the largest TC queue is in the SP group and the others belong to the WRR group and You can also config the TC queues' weight with values 0-127, value 0 means this TC queue is in SP group. In this way, when scheduling queues, the switch allows TC queues in SP group to occupy the whole bandwidth following the SP mode and the other TC queues in the WRR group will take up the bandwidth according to their ratio. 3. Equ-Mode: Equal-Mode. In this mode, all the queues occupy the bandwidth equally.

What is tpQosSchedulerConfig?

This selects the queue scheduling algorithm the switch uses across its egress traffic classes: strict priority, weighted round robin, a hybrid of both, or equal bandwidth sharing. An admin picks this to balance latency-sensitive traffic against fairness, since strict priority can starve lower-priority queues while WRR guarantees each queue some bandwidth. For example, setting it to sp-wrr-mode(2) lets the highest traffic-class queue always transmit first while the remaining queues share bandwidth by weight.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11863.6.22.1.2.1
snmpwalk -v2c -c public <target> TPLINK-QOS-MIB::tpQosSchedulerConfig

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11863.6.22.1.2.1.1
snmpget -v2c -c public <target> TPLINK-QOS-MIB::tpQosSchedulerConfig.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.11863.6.22.1.2.1.1 i <value>

Start monitoring TP-Link managed switch (QoS classification/queue-scheduling config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TPLINK-QOS-MIB::tpQosSchedulerConfig OID value, configure state conditions and alerts, and monitor any TP-Link managed switch (QoS classification/queue-scheduling config status) 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.11863tplinkTPLINK-MIB
1.3.6.1.4.1.11863.6tplinkMgmtTPLINK-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11863.6.22tplinkQosMIBTPLINK-QOS-MIB
1.3.6.1.4.1.11863.6.22.1tplinkQosMIBObjectsTPLINK-QOS-MIB
1.3.6.1.4.1.11863.6.22.1.2tplinkQosSchedulerTPLINK-QOS-MIB
1.3.6.1.4.1.11863.6.22.1.2.1tpQosSchedulerConfigTPLINK-QOS-MIB