Hi Team,

Could you please advise me the issue with this error. only one switch is giving this error while I'm trying to migrate to snmpv3.


Article Comments

Hello,

Please check if the SNMP Settings (Version, Community String, port, authentication) are correct. After that, please check if the corresponding PRTG Probe is allowed to send SNMP Requests to the device.

Please take a look at this article as well: My SNMP sensors don’t work. What can I do?

You can also use our SNMP Tester to test the SNMP-Functionality on the target device(s).


Kind regards,
Birk Guttmann, Tech Support Team


Mar, 2018 - Permalink

HI Team,

I have checked the necessary steps. Its just this particular switch that is giving the error. Is there any other guidance you could give?


Mar, 2018 - Permalink

Hello there,

Have you already tried to run a "Read Device Uptime" with our SNMP Tester against the correpsonding device?


Kind regards,
Birk Guttmann, Tech Support Team


Mar, 2018 - Permalink

Hi Birk,

I receive the below output:

Paessler SNMP Tester 5.2.3 Computername: 0153-KRISHNAS Interface: (10.129.32.152, 10.129.137.206)
3/7/2018 10:19:51 AM (3 ms) : Device: 10.128.64.9
3/7/2018 10:19:51 AM (4 ms) : SNMP V3
3/7/2018 10:19:51 AM (5 ms) : Uptime
3/7/2018 10:19:55 AM (4064 ms) : SNMP Datatype: ASN_PRIMITIVE
3/7/2018 10:19:55 AM (4068 ms) : -------
3/7/2018 10:19:55 AM (4073 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds )
3/7/2018 10:19:59 AM (8158 ms) : SNMP Datatype: ASN_PRIMITIVE
3/7/2018 10:19:59 AM (8160 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds )
3/7/2018 10:19:59 AM (8161 ms) : Done

Mar, 2018 - Permalink

Hi Birk,

For the one which already has the v3 running:

3/7/2018 10:17:27 AM (4 ms) : Device: 10.128.64.8
3/7/2018 10:17:27 AM (5 ms) : SNMP V3
3/7/2018 10:17:27 AM (7 ms) : Uptime
3/7/2018 10:17:31 AM (4126 ms) : SNMP Datatype: ASN_PRIMITIVE
3/7/2018 10:17:31 AM (4128 ms) : -------
3/7/2018 10:17:31 AM (4129 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds )
3/7/2018 10:17:35 AM (8232 ms) : SNMP Datatype: ASN_PRIMITIVE
3/7/2018 10:17:35 AM (8234 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds )
3/7/2018 10:17:35 AM (8236 ms) : Done

there is something wrong.


Mar, 2018 - Permalink

I have pushed in v3 on devices and updated same on prtg. It has accepted the credentials. I have included view iso and not have exluded anything. Now if I just test in tester. It gives 2003 error. Please advice. really urgent.


Mar, 2018 - Permalink

Hello there,

Please check SNMP configuration in the device. As long as you get this error, the device does not respond to SNMP requests. Some devices for example have a setting about which hosts are allowed to send them SNMP queries. You need to make sure that PRTG's IP (or from the remote probe that should run the sensor) is in this list.

Kind regards,

Erhard


Mar, 2018 - Permalink

Hi,

Could you guide me on the MIB part. I have the view internet and iso installed on of the AP and the uptime is successful. I want all the OID accessible. It would anyways be the readonly access.


Mar, 2018 - Permalink

Hi there,

This looks like what you might need.

Kind regards,

Erhard


Mar, 2018 - Permalink

Hi Team,

Is there a possibility to talk to one of the Engineers? We are using the corporate version of PRTG. I'm not able to proceed with this particular switch at all.


Mar, 2018 - Permalink

Hi there,

In this case I would recommend contacting the vendor's support. I'm afraid we cannot assist in setting up SNMP for a particular device.

Kind regards,

Erhard


Mar, 2018 - Permalink