Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"qosPolicy",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"weighteRoundRobin-8-4-2-1",
"(",
"1",
")",
",",
"strictPriority",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"(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.\"",
"::=",
"{",
"trafficPrioritization",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"weighteRoundRobin-8-4-2-1",
1
],
[
"strictPriority",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"(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."
],
null,
null,
null,
null
]
}