Since I updated to version 17.2.32.2779, our Dell server hard disk show warning

Hi there and thank you for your KB-Post.

Please allow us to see how your device's SNMP Data Looks like. Please download our latest SNMP Tester, run it on the PRTG Host (or host of the Remote Probe), and perform a "Walk" against the target device providing the "1.3.6.1.4.1.674.10893.1.20.130.4" OID (without quotes) as parameter.

Which results do you get in the Tester? Please share the output from the tester here.

Best Regards,
Luciano Lingnau [Paessler Support]

Hello Luciano,

Here are the results:

I tried different SNMP versions ans used "walk" as well as "custom OID"

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: XXXXXXXXXX Interface: (10.86.36.23)
29.06.2017 14:41:26 (1 ms) : Device: a.b.c.d
29.06.2017 14:41:26 (1 ms) : SNMP V3
29.06.2017 14:41:26 (2 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4
29.06.2017 14:41:26 (37 ms) : Error: -33

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: VAN-SV-1984 Interface: (10.86.36.23)
29.06.2017 14:41:29 (2 ms) : Device: 10.86.36.5
29.06.2017 14:41:29 (3 ms) : SNMP V2c
29.06.2017 14:41:29 (4 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: VAN-SV-1984 Interface: (10.86.36.23)
29.06.2017 14:41:31 (3 ms) : Device: 10.86.36.5
29.06.2017 14:41:31 (4 ms) : SNMP V1
29.06.2017 14:41:31 (6 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: VAN-SV-1984 Interface: (10.86.36.23)
29.06.2017 14:41:40 (3 ms) : Device: 10.86.36.5
29.06.2017 14:41:40 (5 ms) : SNMP V1
29.06.2017 14:41:40 (7 ms) : Custom OID 1.3.6.1.4.1.674.10893.1.20.130.4
29.06.2017 14:41:40 (18 ms) : SNMP Datatype: ASN_NULL
29.06.2017 14:41:40 (20 ms) : -------
29.06.2017 14:41:40 (22 ms) : Value: NULL2
29.06.2017 14:41:40 (24 ms) : Done


----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: VAN-SV-1984 Interface: (10.86.36.23)
29.06.2017 14:42:05 (5 ms) : Device: 10.86.36.5
29.06.2017 14:42:05 (7 ms) : SNMP V2c
29.06.2017 14:42:05 (10 ms) : Custom OID 1.3.6.1.4.1.674.10893.1.20.130.4
29.06.2017 14:42:06 (28 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
29.06.2017 14:42:06 (32 ms) : -------
29.06.2017 14:42:06 (34 ms) : Value: No such object (SNMP error # 222)
29.06.2017 14:42:06 (37 ms) : Done


----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: VAN-SV-1984 Interface: (10.86.36.23)
29.06.2017 14:42:11 (11 ms) : Device: 10.86.36.5
29.06.2017 14:42:11 (16 ms) : SNMP V3
29.06.2017 14:42:11 (21 ms) : Custom OID 1.3.6.1.4.1.674.10893.1.20.130.4
29.06.2017 14:42:11 (111 ms) : SNMP Datatype: ASN_PRIMITIVE
29.06.2017 14:42:11 (116 ms) : -------
29.06.2017 14:42:11 (122 ms) : Value: Authentication failure (incorrect password, community or key) -35
29.06.2017 14:42:11 (127 ms) : Done

Hello and thank you for your reply.

While none of the queries succeeded, we've just received a walk from another customer reporting a very similar issue. We've just located the issue and will release a new version to address this issue, hopefully in the coming week.

Please keep an eye on updates to our release notes:

• Release Notes for the "Stable" Release Channel

Best Regards,
Luciano Lingnau [Paessler Support]

I have the exact same problem. Would it be okay to temporarily adjust the lookup file until a fix arrives to at least kill the warnings?

Hello pixel1138,
thank you for your KB-Post.

Yes, that should be possible:

• Create a new file called prtg.customlookups.yesno.statenook.ovl under "C:\Program Files (x86)\PRTG Network Monitor\lookups\custom"
• Paste the following definition in the file:

<?xml version="1.0" encoding="UTF-8"?>
  <ValueLookup id="prtg.customlookups.yesno.statenook" desiredValue="0" undefinedState="Warning" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
    <Lookups>
		<SingleInt state="Ok" value="0">No</SingleInt>
		<SingleInt state="Error" value="1">Yes</SingleInt>
    </Lookups>
  </ValueLookup>

• Head to Setup > Administrative Tools, issue a "Re-Load Lookups"
• Use Multi-Edit to modify the lookup used by the 'SMART Warning' channel of all affected sensors to the newly created prtg.customlookups.yesno.statenook

Best Regards,
Luciano Lingnau [Paessler Support]

I have the same problem.

I created a file prtg.customlookups.yesno.statenook.ovl, modified lookups for sensors 'Dell Poweredge Physical Disk Physical Disk' (channel 'S.M.A.R.T Warning').

But after few minutes the lookup value changed back for every sensor one by one.

I modified lookups again, but value resets again.

How can I resolve this issue?

Thank you.