Hello,

I have a problem adding custom oid sensor. I would like to add custom oid for RTT average (nqaResultsRttAvg OID ID - 1.3.6.1.4.1.2011.5.25.111.4.1.1.26) - this oid is huawei equipment.

(http://oidref.com/1.3.6.1.4.1.2011.5.25.111.4.1.1.26)

I am receiving error - Value: No such instance (SNMP error # 223).

When I run snmpwalk I am receiving values. example

snmpwalk -v2c -c {password} {IP} 1.3.6.1.4.1.2011.5.25.111.4.1.1.26

SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3078.1 = Gauge32: 6
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3079.1 = Gauge32: 21
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3080.1 = Gauge32: 8
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3081.1 = Gauge32: 6
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3082.1 = Gauge32: 5

I have tried snmp tester and tested OID by adding OID values one by one, but the result is the same.

1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103

Maybe someone has the same problems. Maybe you could advice how should I proceed with troubleshooting?

Kind regards, Egidijus

Article Comments

Hello Egidijus,

When trying to add the sensors to an SNMP Custom Advanced Sensor for example, make sure to enter each OID completely, they should look like this then (the sensor does no walk here by itself): 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3078.1 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3079.1 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3080.1 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3081.1 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3082.1

Alternatively use an SNMP Custom Table sensor on OID 1.3.6.1.4.1.2011.5.25.111.4.

See also What can I monitor with the SNMP Custom Table Sensor?

Kind regards,

Erhard


Feb, 2018 - Permalink

Hello Erhard,

I have already tried SNMP Custom and SNMP custom advanced sensor

  • 1.3.6.1.4.1.2011.5.25.111.4.1.1.26 and all other values example
  • 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011
  • 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5
  • 1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25 etc. But PRTG does not read the value. I used PRTG SNMP tester

this output is one NQA (like cisco IPSLA). It is configured to send one ping from source A to source B each 1 minute.

1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3078.1
1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3079.1
1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3080.1
1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3081.1
1.3.6.1.4.1.2011.5.25.111.4.1.1.26.2011.5.25.111.4.1.1.26.12.86.105.108.110.105.117.115.95.82.105.103.97.4.112.105.110.103.3082.1

Here is 5 values so I can not all OID numbers, because last number changes.

for example here are 2 NQA configured

SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.54.4.112.105.110.103.441752.1 = Gauge32: 4
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.54.4.112.105.110.103.441753.1 = Gauge32: 4
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.54.4.112.105.110.103.441754.1 = Gauge32: 3
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.54.4.112.105.110.103.441755.1 = Gauge32: 3
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.54.4.112.105.110.103.441756.1 = Gauge32: 3
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.55.4.112.105.110.103.441752.1 = Gauge32: 4
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.55.4.112.105.110.103.441753.1 = Gauge32: 4
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.55.4.112.105.110.103.441754.1 = Gauge32: 3
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.55.4.112.105.110.103.441755.1 = Gauge32: 4
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.55.4.112.105.110.103.441756.1 = Gauge32: 4

the difference is

SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.54
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.26.7.86.76.65.78.50.53.55

Tried to add these different NQA, but the same problem PRTG shows that Value:

No such instance (SNMP error # 223)

I have tried to do the same with Cisco and there was no problems.

Kind regards, Egidijus


Feb, 2018 - Permalink

Hello,

I have send you an email.

Kind regards, Egidijus


Feb, 2018 - Permalink

Just a heads up for anyone else that might be interested in this: What happens here is that the particular device changes the OIDs for IP SLA values all the time, meaning each new value will be put into a new OID. PRTG's sensors do not cover this particular scenario, it would basically require an SNMP walk with each scan to determine the current relevant OIDs that need to be queried.

The only way would be with a script as described here for example, where the issue is similar. The script performs a walk to determine the OIDs of interest and then retrieve the values to pass them along to PRTG.


Mar, 2018 - Permalink