CTRON-TX-QUEUE-ARBITRATION-MIB.mib object view, vendor Enterasys-Networks-Inc
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CTRON-TX-QUEUE-ARBITRATION-MIB and use it to monitor vendor specific OID's.
CTRON-TX-QUEUE-ARBITRATION-MIB file content
Object view of CTRON-TX-QUEUE-ARBITRATION-MIB:
| Scalar Object |
| ctTxQPortGroupEntry |
.1.3.6.1.4.1.52.4.1.5.12.1.1.1 |
|
Defines a particular entry containing objects pertaining to
definition and control over interfaces supporting multiple transmit
queue arbitration.
|
| ctTxQArbEntry |
.1.3.6.1.4.1.52.4.1.5.12.1.2.1 |
|
Specifies the entries in the ctTxQArbTable.
|
| Tabular Object |
| ctTxQPortGroup |
.1.3.6.1.4.1.52.4.1.5.12.1.1.1.1 |
|
Indicates the transmit queue port group to which the interface
claims membership. The specific interface is indicated
by the instancing information.
|
| ctTxQArbNumQueues |
.1.3.6.1.4.1.52.4.1.5.12.1.2.1.2 |
|
The number of transmit queues for each port in this port group.
|
| ctTxQArbNumSlices |
.1.3.6.1.4.1.52.4.1.5.12.1.2.1.3 |
|
The number of 'slices' into which transmit resources are divided. This
determines the resolution with which transmit priority can be allocated
to each of the transmit queues. For example, if the number of slices
is 16, then transmit resources may be allocated to each transmit queue
in units of 1/16 (6.25% of the total). The numbers of slices allocated
to all queues must add up to the value of this object (i.e., 100%).
|
| ctTxQArbSetting |
.1.3.6.1.4.1.52.4.1.5.12.1.2.1.4 |
|
The approximate percentage of a port's transmit resources to
be allocated to each transmit queue. This allows for fine-tuning
of the 'strict priority' configuration.
Under strict priority, the highest queue (ctTxQArbNumQueues - 1)
has the highest priority, followed by (ctTxQArbNumQueues - 2), etc.
Queue 0 always has the lowest priority. All entries in a higher
priority queue will be transmitted before any entries from the lower
priority queues. This object allows the modification of the strict
priority scheme so that lower priority queues can be guaranteed some
access to the transmitter.
This object is an octet string in which the number of octets corresponds
to the number of transmit queues for each port in this port group,
as indicated by ctTxQArbNumQueues. The value of the first octet
represents the number of 'slices' of transmit resources to allocate to
Queue 0, the second octet represents the number for Queue 1, and so
forth. The sum of all the octets in the octet string must add up to
the total number of slices available for the port.
For example, on a port having 4 transmit queues and where transmit
resources are divided into 16 slices, writing an octet string of
{0x00, 0x04, 0x04, 0x08} would have the following effect:
At least 50% of the frames transmitted are from Queue 3
At least 25% of the frames transmitted are from Queue 2
At least 25% of the frames transmitted are from Queue 1
No frames will be transmitted from Queue 0 until Queues 1, 2 and 3
are empty.
|
| Table |
| ctTxQPortGroupMapTable |
.1.3.6.1.4.1.52.4.1.5.12.1.1 |
|
The ctTxQPortGroupMapTable defines the mapping of interfaces
to a specific port group.
|
| ctTxQArbTable |
.1.3.6.1.4.1.52.4.1.5.12.1.2 |
|
A table containing entries to specify the approximate priority
for servicing of each transmit queue for each port group on the
device.
|
| Object Identifier |
| ctTxQArbConfig |
.1.3.6.1.4.1.52.4.1.5.12.1 |
