Hello

I need to monitoring the Cisco Unity, the OID used is 1.3.6.1.4.1.9.9.385.1.2.1 - ciscoUnityServerState, with another monitoring tool it is possible.

Use get-Net: disabled

Aessler SNMP tester - 20.2.4 Device name: SOUMIMOPRO1 Interface: 10.255.110.5
03/15/2021 10:34:01 AM (9 ms): Device: 10.255.100.16
3/15/2021 10:34:01 AM (13 ms): SNMP v2c
03/15/2021 10:34:01 AM (17 ms): Custom OID 1.3.6.1.4.1.9.9.385.1.2.1
03/15/2021 10:34:01 AM (39 ms): SNMP data type: SNMP_EXCEPTION_NOSUCHINSTANCE
3/15/2021 10:34:01 AM (43 ms): -------
03/15/2021 10:34:01 AM (47 ms): Value: #N SNMP_EXCEPTION_NOSUCHINSTANCE223
03/15/2021 10:34:01 AM (50 ms): Done

Get-Netx User: Enabled

----------------------- New test -----------------------
Paessler SNMP Tester - 20.2.4 Computer Name: SOUMIMOPRO1 Interface: 10.255.110.5
03/15/2021 10:33:56 AM (9 ms): Device: 10.255.100.16
3/15/2021 10:33:56 AM (14 ms): SNMP v2c
03/15/2021 10:33:56 AM (18 ms): Custom OID 1.3.6.1.4.1.9.9.385.1.2.1
03/15/2021 10:33:56 AM (25 ms): SNMP data type: ASN_INTEGER
3/15/2021 10:33:56 AM (29 ms): -------
03/15/2021 10:33:56 AM (33 ms): Value: 3
03/15/2021 10:33:56 AM (37 ms): Done

How can I use get-next from snmp custom?

What alternatives does prtg offer me to achieve this?

Article Comments

Hi there,
You can adjust your SNMP settings in tab "Settings" of your parent device. You will find this options in section SNMP Compatibility Options.

Kind regards

Felix Wiesneth - Team Tech Support


Mar, 2021 - Permalink

Hi Felix,

Thanks for your insight on this, however this approach ......."you can adjust your SNMP settings in tab "Settings" of your parent device. You will find this options in section SNMP Compatibility Options.".... did not solve the problem I am having. Having made this change, I am still unable to get the sensor working.

The particular OID: 1.3.6.1.4.1.12356.101.4.9.2.1.9

Please help!

Thank you.


Mar, 2021 - Permalink

Hi Felix .

Thanks for your insight.

We have made this adjustment in SNMP settings for "SNMP Compatibility Options." the issues still persists.

The OID's

OID: 1.3.6.1.4.1.12356.101.4.9.2.1.9 OID: 1.3.6.1.4.1.12356.101.4.9.2.1.6 OID: 1.3.6.1.4.1.12356.101.4.9.2.1.5

Please help.


Mar, 2021 - Permalink

Hello Goziy,

Does the SNMP Tester shows a result for the OIDs? Please post the result of the SNMP Tester here.

Kind regards

Felix Wiesneth - Team Tech Support


Mar, 2021 - Permalink

Applied the configuration indicates but does not change the prtg error. Error 233. As stated in the SNMP test with get NEtx works, but the sensor in PRTG cannot receive the desired value.

I checked with the SNMP Custom and SNMP Custom String sensors but not working

Device:

SNMP Compatibility Options

Walk Mode
Use GETBULK requests (recommended)
Use GETNEXT requests. Selected


May, 2021 - Permalink

Hi,

I would recommend to run Wireshark on your Probe device to see if any packages are dropped. In some cases it is possible that the SNMP tester results are fine but Wireshark tells some more details and can display the error. Create a capture filter (not display filter) and analysed the pcap file after the sensor failed at least once. The filter can look like this:
host *Ip of target device

Kind regards

Felix Wiesneth - Team Tech Support


May, 2021 - Permalink