0

I have a Juniper MIB in which this OID: 1.3.6.1.4.1.2636.3.1.13.1.24 corresponds to this value: 1.3.6.1.4.1.2636.3.1.13.1.2.

When I run an snmpwalk of 1.3.6.1.4.1.2636.3.1.13.1.24 I get this:

JUNIPER-MIB::jnxOperating5MinAvgCPU.1.1.0.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.2.1.1.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.2.1.2.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.4.1.1.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.4.1.2.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.4.1.3.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.4.1.4.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.4.1.5.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.7.1.0.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.8.1.1.0 = Gauge32: 0
JUNIPER-MIB::jnxOperating5MinAvgCPU.9.1.0.0 = Gauge32: 13

What's with all the extra stuff? Why isn't it just a single value? How would I be able to tell programatically which sub-value was relevant? Is there somewhere I can go read that would explain this result in detail?

Omnifarious
  • 400
  • 1
  • 3
  • 13

1 Answers1

1

If you read more about tables in SNMP books, you should realize that 1.3.6.1.4.1.2636.3.1.13 (aka jnxOperatingTable) is a table that contains data in tabular form.

Things like .1.1.0.0 are the actual indexes of each rows, if you read the INDEX part of 1.3.6.1.4.1.2636.3.1.13.1 (aka jnxOperatingEntry).

You can find the official documentation on this here

Lex Li
  • 1,235
  • 8
  • 10