Status in source: current.
Names: agentCosQueueDropPrecIndex
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"agentCosQueueDropPrecIndex",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The COS queue drop precedence level, numbered 1 to p, where p is the total number of drop precedences supported per queue, as indicated by agentCosQueueNumDropPrecedenceLevels. This is used as the minor index into the table. Each supported drop precedence level for a queue has its own set of configuration parameters. The actual number of drop precedence levels supported depends on the device characteristics. For example, some implementations may allow for three levels of drop precedence (1/2/3, sometimes referred to as green/yellow/red), some may support two levels (1/2, or high/low), while others only one. Some devices use the lowest (highest-numbered) drop precedence level to represent non-TCP traffic.\"",
"::=",
"{",
"agentCosQueueMgmtEntry",
"1",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The COS queue drop precedence level, numbered 1 to p, where p is the total number of drop precedences supported per queue, as indicated by agentCosQueueNumDropPrecedenceLevels. This is used as the minor index into the table. Each supported drop precedence level for a queue has its own set of configuration parameters. The actual number of drop precedence levels supported depends on the device characteristics. For example, some implementations may allow for three levels of drop precedence (1/2/3, sometimes referred to as green/yellow/red), some may support two levels (1/2, or high/low), while others only one. Some devices use the lowest (highest-numbered) drop precedence level to represent non-TCP traffic."
],
null,
null,
null,
null
]
}