Hi,

We have a requirement to collect data on our network pertaining to QoS.
Ordinarily this would be quite a simple task, however we have hit the
problem that the data used to store it needs to be collected from
multiple tables.

The first table defines the QoS queues on the device:

dave@mercury:~$ snmpwalk -v2c -cpublic r1.man
.1.3.6.1.4.1.2636.3.15.3.1.2
SNMPv2-SMI::enterprises.2636.3.15.3.1.2.0 = STRING: "be"
SNMPv2-SMI::enterprises.2636.3.15.3.1.2.1 = STRING: "ef"
SNMPv2-SMI::enterprises.2636.3.15.3.1.2.2 = STRING: "af"
SNMPv2-SMI::enterprises.2636.3.15.3.1.2.3 = STRING: "nc"
SNMPv2-SMI::enterprises.2636.3.15.3.1.2.4 = STRING: "lbe"

The second table is the ifdescription table, which does the obvious:

dave@mercury:~$ snmpwalk -v2c -cpublic r1.man ifdescr
IF-MIB::ifDescr.1 = STRING: fxp0
IF-MIB::ifDescr.4 = STRING: lsi
IF-MIB::ifDescr.5 = STRING: dsc
IF-MIB::ifDescr.6 = STRING: lo0
IF-MIB::ifDescr.7 = STRING: tap
IF-MIB::ifDescr.8 = STRING: gre

...

IF-MIB::ifDescr.580 = STRING: ae3
IF-MIB::ifDescr.581 = STRING: ge-0/0/3.0
IF-MIB::ifDescr.583 = STRING: ae3.0
IF-MIB::ifDescr.584 = STRING: xe-1/2/0.0

The final piece of the puzzle is the parts of the tree that explains how
many packets and bytes were on each interface:

dave@mercury:~$ snmpwalk -v2c -cpublic r1.man
.1.3.6.1.4.1.2636.3.15.4.1.3
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.0 = Counter64: 6716541859572
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.1 = Counter64: 19367875396
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.2 = Counter64: 1203566194
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.3 = Counter64: 1190194586
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.4 = Counter64: 5938981960
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.5 = Counter64: 0
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.6 = Counter64: 0
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.506.7 = Counter64: 6
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.510.0 = Counter64: 140900599459
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.510.1 = Counter64: 294397738
SNMPv2-SMI::enterprises.2636.3.15.4.1.3.510.2 = Counter64: 124590652

As you can see, the penultimate section of the OID is a reference to the
interface we are interested in, and the very last part references the queue.

This MIB is similar to the Cisco QoS MIB, and likely various other MIBs

Regards,
Dave