SNMP with Remote Probe

remote-probe snmp timeouteffentia

I have a remote probe with 300 sensors (vmware, netapp, switch, printer....), all work except all the snmp sensors (no response error #2003)

Before moving to a remote probe, I tested with an local probe & core and all worked good...

I tried to increase snmp timeout to 60s but nothing :(

Sorry for my bad english best regard

Created on Jan 8, 2013 6:57:38 PM by mortimer (0) ●1

5 Replies

Votes:

0

Your Vote:

From the remote probe machine, please run our SNMP Tester and check if you can access the counters / OIDs in case.

Created on Jan 8, 2013 7:21:11 PM by Patrick Hutter [Paessler Support] (7,225) ●3 ●3

Votes:

0

Your Vote:

thank for reply

I test with your SNMP Tester the uptime of one device (SNMP v2c)

----------------------- New Test ----------------------- Paessler SNMP Tester 3.2 Device: 192.0.75.15

08/01/2013 21:01:56 (1 ms) : Start using SNMP V2c 08/01/2013 21:01:56 (3 ms) : ------- 08/01/2013 21:01:56 (4 ms) : Value: 1066428684 08/01/2013 21:01:56 (4 ms) : Done

Created on Jan 8, 2013 8:03:18 PM by mortimer (0) ●1

Votes:

0

Your Vote:

If you add a SNMP Uptime sensor in PRTG, does that yield a result?

Created on Jan 8, 2013 8:06:33 PM by Patrick Hutter [Paessler Support] (7,225) ●3 ●3

Votes:

0

Your Vote:

result : This sensor has not received any data since startup

Before moving to a remote probe, everything worked good with a local probe & server

Created on Jan 8, 2013 8:26:07 PM by mortimer (0) ●1

Votes:

0

Your Vote:

Please send us an email to [email protected] Please include screenshots of the SNMP Tester scans (including the device's configuration - please black out any non-disclosable information), the respective device's SNMP settings, as well as SNMP compatibility settings. Please mention this thread for reference.

Created on Jan 8, 2013 8:29:33 PM by Patrick Hutter [Paessler Support] (7,225) ●3 ●3