What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

snmp Prtg error

Votes:

0

Hi everyone

I'm getting the below errors continuously

1. [PRTG Monitor] GCHOSW switch (#.#.#.#) (083) GCHOESX03_P6 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
2. [PRTG Monitor] GCHOSW switch (#.#.#.#) (082) GCHOESX02_P6 Traffic (SNMP Traffic) Down (SNMPERR_BAD_SENDTO (SNMP error # -12))
3. [PRTG Monitor] GCHOSW switch (#.#.#.#) (081) GCHOESX01_P6 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
4. [PRTG Monitor] GCHOSW switch (#.#.#.#) (008) GCHOSANSW1 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
5. [PRTG Monitor] NNSTSANSW1 (1073741830) FC port 0/6 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
6. [PRTG Monitor] NNSTSANSW1 (1073741829) FC port 0/5 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
7. [PRTG Monitor] NNSTSANSW1 (1073741828) FC port 0/4 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
8. [PRTG Monitor] NNSTSANSW1 (1073741826) FC port 0/2 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
9. [PRTG Monitor] GCSTSW switch (#.#.#.#) (068) GCSTESX02_P4 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
10. [PRTG Monitor] GCSTSW switch (#.#.#.#) (067) GCSTESX01_P4 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
11. [PRTG Monitor] GCSTSW switch (#.#.#.#) (066) GCSTPRTG1_P2 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
12. [PRTG Monitor] GCSTSW switch (#.#.#.#) (065) GigabitEthernet2/0/8 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
13. [PRTG Monitor] GCSTSW switch (#.#.#.#) (064) Backup_srv_1_P2 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
14. [PRTG Monitor] GCSTSW switch (#.#.#.#)  (063) GCSTSANSW2 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
15. [PRTG Monitor] GCSTSW switch (#.#.#.#) (062) GCSTWIZE1_CTRL2_P2 Traffic (SNMP Traffic) Down (SNMPERR_BAD_SENDTO (SNMP error # -12))
16. [PRTG Monitor] GCSTSW switch (#.#.#.#) (061) GCSTWIZE1_CTRL1_P2 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
17. [PRTG Monitor] GCSTSW switch (#.#.#.#) (060) GigabitEthernet2/0/3 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
18. [PRTG Monitor] GCSTSW switch (#.#.#.#) (059) GCSTSVC1_P5 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
19. [PRTG Monitor] GCSTSW switch (#.#.#.#)  (058) GCSTSVC1_P4 Traffic (SNMP Traffic) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)
20. [PRTG Monitor] GCSTSW switch(#.#.#.#) Uptime 255 (SNMP System Uptime) Down (No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP erro...)

can anyone help me I will be really appreciated

Thanks in advance

monitor server snmp-traffic switches

Created on Sep 24, 2018 11:44:30 AM

Last change on Sep 24, 2018 12:27:56 PM by Dariusz Gorka [Paessler Support]



7 Replies

Votes:

0

Did this ever work or did those issues start out of nowhere?

If new issues - what changed on the probe device? Did you uninstall e.g. AntiVirus that might interfere on the network level on the probe?

Seems a lot like SNMP traffic only - did you set the communities up right and is nothing else using the same community that would possibly interfere / block?

Are the community name(s) changed from "public" to something else?

Does the SNMP tester tool (see www.paessler.com for the free tool) work?

Regards

Florian Rossmark

www.it-admins.com

Created on Sep 24, 2018 2:03:56 PM



Votes:

0

Hi

Thanks for your reply

i didn't change anything and it happens every 6 hours or more

please check below link you can see community for each switch

https://postimg.cc/YG0hGsts

Created on Sep 25, 2018 6:34:37 AM



Votes:

0

Hi

lease find config for snmp 

1- ASA/act/pri# sh running-config snmp-server
snmp-server host outside 77.75.81.11 poll community ***** version 2c
snmp-server host outside 77.75.81.14 poll community ***** version 2c
snmp-server host outside Careitec_PRTG poll community ***** version 2c
snmp-server host grossist-net_inside #.#.#.#  community ***** version 2c
no snmp-server location
no snmp-server contact
snmp-server enable traps syslog

2-
 SW1#sh run | sec snmp-server
snmp-server community public RO
snmp-server host #.#.#.# public

3-
SW2#sh run | sec snmp-server
snmp-server community public RO
snmp-server host #.#.#.# public

Created on Sep 25, 2018 6:59:34 AM

Last change on Sep 25, 2018 10:21:48 AM by Luciano Lingnau [Paessler]



Votes:

1

Hi there,

Basically, the SNMP error 2003 means that the requests run into a timeout. This might be caused by any device on the route from PRTG to the host blocking / not forwarding the packets, or by the device not being able to answer to these requests. The first check would be to see if other protocols work at these times, like Pings or HTTP requests to the webinterface. If these also fail, it's likely that there is a general connection issue at these times.

If these scans work properly all over the time, it might also be caused by an overload of the target device. Some manufacturers put a low prioritisation on the SNMP daemon so that requests are getting dropped during load spikes. As Florian already mentioned, using the SNMP Tester at the time when the outage in PRTG is captured from the host where the PRTG probe is installed would help to see if SNMP works at all.

In PRTG, you can raise the scanning interval of these sensors to lower the total number of requests to see if the replies work more reliably afterwards.

Kind regards,
Felix Saure, Tech Support Team

Created on Sep 25, 2018 10:37:37 AM by Felix Saure [Paessler Support]



Votes:

0

Hi

Thanks for your reply

switches WS-C3650

ive checked the connection

1- from firewall--> i can ping prtg , switches

2- from switches --> i can't ping prtg, firewall

3- from prtg- virtual machine ---> i can ping all firewall, switches

and i'm receiving prtg alarms regarding to snmp errors i've checked the setting and nothing changed

Created on Sep 25, 2018 10:47:07 AM



Votes:

1

Hello,

Did you also used the SNMP Tester while the sensors are in a down status and did you already try to raise the scanning interval as suggested?

Kind regards,
Felix Saure, Tech Support Team

Created on Sep 26, 2018 9:28:36 AM by Felix Saure [Paessler Support]



Votes:

1

As for your PING from switches...

Unless all those switches involved have a proper IP set and are in the same VLAN and IP segment as PRTG and the FW you might not be able to PING them.

Even if, you might need to issue a PING IP 1.1.1.1 SOURCE VLAN 1 or PING IP 1.1.1.1 SOURCE 1.1.1.2 (source = switches own local IP in that VLAN).

In theory the default gateway or any other VLAN routing should solve it - but I saw it happening - not sure about your whole network - but I wanted to add it so you have a chance to look further in to that.

Felix already made good suggestions as well. Besides that I to suggest one more thing - change the public community to something own - something that is not default - this even helps that other systems might not try to abuse it and even try to attack those systems to easily. In theory there could be another system that is using SNMP against your FW and eventually causing this overload you seem to see - especially if it is kinda every 6 hours..

Regards

Florian Rossmark

www.it-admins.com

Created on Sep 26, 2018 1:54:38 PM




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.