qosPolicy
Jetnet5010G ·
.1.3.6.1.4.1.24062.2.2.1.6.1
Object
scalar mandatory
r/w
Enumeration
(1)8,4,2,1 weight round robin scheme: the switch will follow
8:4:2:1 rate to process priority queue from Hi to lowest queue.
This approach prevents the lower priotiry packets from being
starved out with only a slight delay to the higher priority
packets.
(2)Use the strict priority scheme: Queue with higher priority
will always be process first, while queue with lower priority
will only be processed when the higher priority queue is empty.
This approach can cause the lower priorities the be startved
out preventing them from transmitting any packets, but it
ensures that all high priority packets serviced as soon as
possible.
Context
- MIB
- Jetnet5010G
- OID
.1.3.6.1.4.1.24062.2.2.1.6.1- Type
- scalar
- Access
- readwrite
- Status
- mandatory
- Parent
- trafficPrioritization
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'Jetnet5010G' -M '/opt/observium/mibs/korenix:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'Jetnet5010G::qosPolicy.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'Jetnet5010G' -M '/opt/observium/mibs/korenix:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'Jetnet5010G::qosPolicy'
Syntax
Enumeration
Values & Constraints
Enumerated Values
1 | weighteRoundRobin-8-4-2-1 |
2 | strictPriority |