Snmp error 2003

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

What is this?

This knowledgebase contains questions and answers about PRTG Network
Monitor and network monitoring in general. You are invited to get involved by asking and
answering questions!

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

I´m a rookie with PRTG, after install and scan my network I face so many alerts showing something like:

»
(003)ixp0
Down
No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003
«

Does anyone idea how to fix or what it means?

alert
error
snmp

11 Replies

Accepted Answer

Hello,

first of all please check if the SNMP Settings (Version, Community String, port, eventual authentication, etc.) are correct. Then please also check if PRTG (or the PC on which PRTG is installed) is allowed to send SNMP Requests to the device in case.

Please check 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).

Best Regards.

I wanted to let everyone know what I discovered about this error. Also the «No Such Name» snmp error.

On my Linux box, in my snmpd.conf file there was a setting like this:

view systemview included .1.3.6.1.2.1

This limits the systemview to OID’s that fall under this section only. Apparently the OID’s that PRTG wants to look at are not under this. I change it to:

view systemview included .1

and re-started snmpd. Now it works.

hello i have similar problem when i try add custom sensor (oid 1.3.6.1.2.1.2.2.1.8.1) i have error: «No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003)»

when i test that oid in snmp tester i get right anserw in that case «1»

please help :)

Dear Piotr,

please double-check the settings made in the Tester and then in PRTG. If it works from the Tester and the Tester was used on the same machine as the PRTG Probe runs on, then the difference might be the user accounts under which both applications (respectively the PRTG Probe Service) run under.

best Regards.

I have faced this case often, is it failing to configure the PRTG or SNMP connection?

Hi there,

Basically the error message means that PRTG is unable to open a SNMP connection. Either the device is not answering to SNMP requests, the credentials/community is not correct or there is a firewall in between that blocks the connection.

Best regards.

Hello,

I am getting the same output as Piotr, I assume it has to do with credentials/community because I have turned off the firewall to make sure that isn’t the problem. The community string is correct but I’m not sure where to check on these so called credentials. I noticed the first comment mentioned something called eventual authentication, which i’m not entirely sure how to validate.

A quick background on what i am trying to achieve:

I have set up a Room Alert device for my server room which monitors the temperature, I have extracted the MIB file and have created a specific .oidlib using the MIB Importer but when i try creating a SNMP library sensor using the .oidlib file it fails and throws me the 2003 error. I have checked every all the basic troubleshooting steps provided in the following knowledge article:

https://kb.paessler.com/en/topic/46863-my-snmp-sensors-dont-work-what-can-i-do

Any help is appreciated!

Since the update to 20.3.61.1649+ we experience this problem on one device in our monitoring environment. And it’s not continuesly. It goes from green to red with the corresponding notification and after a while goes back to green again. When looking directly in the device there seems no problem to occur.
I will update now to version 20.3.62.1397 now to see if the problem disappears again.

Hi there,

In case the problem is still there after the update please create a dedicated Support Ticket. You can do this via the «Contact Support» button down in the right corner of your webclient or by sending a mail to [email protected]

Thank you!

Kind regards,
Andreas Günther
Tech Support, Paessler AG

[email protected]

You have to deactivate Control Panel-> System -> Security -> IP-Access
deactivate ssh telnet https

There is no generic solution for it. The error message shown «No response […] (SNMP error # -2003)» indicates a timeout and/or that PRTG is not able to receive the requested information via SNMP.

You need to verify that SNMP is properly configured on the monitored device and also configure the incoming SNMP communication from PRTG’s perspective properly.
To do so, please open the «Settings» tab of the device that has the affected sensor and configure the required SNMP settings under Credentials for SNMP Devices.

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.

Источник

  1. Поиск по форуму не дал результат. Помогите пожалуйста с настройкой SNMP.

    Есть: hAP ac^2 + 6.43

    [.@.] > snmp print
    enabled: yes
    contact:
    location:
    engine-id:
    trap-target:
    trap-community: public
    trap-version: 2
    trap-generators:

    [.@.] > snmp community print
    Flags: * — default
    # NAME ADDRESSES SECURITY READ-ACCESS
    0 * public 0.0.0.0/0 none yes

    [.@.] > ip firewall filter print
    1 ;;; SNMP OPEN FOR ZABBIX
    chain=input action=accept connection-state=new protocol=udp src-port=161,162
    log=no log-prefix=»»
    #остальные правила стандартные

    Zabbix в упор не видит Микротик по SNMP ни по внешнему IP ни из внутренней oVPN, также роутер не видится через SNMP Tester с разных пк разных сетей. При этом, соседний Windows Server по SNMP прекрасно мониторится, делаю вывод что проблема не на Заббиксе.

    Ошибка примерно одна:

    .@zabbix:~$ snmpwalk -v2c -c public x.x.x.x
    Timeout: No Response from x.x.x.x

    Paessler SNMP Tester 5.2.3 Computername: … Interface: (y.y.y.y)
    09.07.2019 14:03:42 (14 ms) : Device: x.x.x.x
    09.07.2019 14:03:42 (21 ms) : SNMP V2c
    09.07.2019 14:03:42 (27 ms) : Uptime
    09.07.2019 14:03:47 (5023 ms) : SNMP Datatype: ASN_PRIMITIVE
    09.07.2019 14:03:47 (5030 ms) : ——-
    09.07.2019 14:03:47 (5036 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 )
    09.07.2019 14:03:52 (10064 ms) : SNMP Datatype: ASN_PRIMITIVE
    09.07.2019 14:03:52 (10066 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 )
    09.07.2019 14:03:52 (10068 ms) : Done

    Пробовал:
    — Менять версию SNMP на v1 — ошибки аналогичные
    — Менять ADDRESS в Community — не помогло, оставил 0.0.0.0/0
    — Менять правило Firewall на Forward — безрезультатно
    — Увеличить таймаут SNMP Tester до 30 — проблема не решилась

    Подскажите, что сделал не так?

  2. А почему src-port, а не dst-port?

  3. Потому что невнимательный и суетливый. Поменял, взлетело. Спасибо вам и Плюс вам в карму.


Форум SPW

Источник

What is this?

This knowledgebase contains questions and answers about PRTG Network
Monitor and network monitoring in general. You are invited to get involved by asking and
answering questions!

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

I´m a rookie with PRTG, after install and scan my network I face so many alerts showing something like:

»
(003)ixp0
Down
No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003
«

Does anyone idea how to fix or what it means?

alert
error
snmp

11 Replies

Accepted Answer

Hello,

first of all please check if the SNMP Settings (Version, Community String, port, eventual authentication, etc.) are correct. Then please also check if PRTG (or the PC on which PRTG is installed) is allowed to send SNMP Requests to the device in case.

Please check 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).

Best Regards.

I wanted to let everyone know what I discovered about this error. Also the «No Such Name» snmp error.

On my Linux box, in my snmpd.conf file there was a setting like this:

view systemview included .1.3.6.1.2.1

This limits the systemview to OID’s that fall under this section only. Apparently the OID’s that PRTG wants to look at are not under this. I change it to:

view systemview included .1

and re-started snmpd. Now it works.

hello i have similar problem when i try add custom sensor (oid 1.3.6.1.2.1.2.2.1.8.1) i have error: «No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003)»

when i test that oid in snmp tester i get right anserw in that case «1»

please help :)

Dear Piotr,

please double-check the settings made in the Tester and then in PRTG. If it works from the Tester and the Tester was used on the same machine as the PRTG Probe runs on, then the difference might be the user accounts under which both applications (respectively the PRTG Probe Service) run under.

best Regards.

I have faced this case often, is it failing to configure the PRTG or SNMP connection?

Hi there,

Basically the error message means that PRTG is unable to open a SNMP connection. Either the device is not answering to SNMP requests, the credentials/community is not correct or there is a firewall in between that blocks the connection.

Best regards.

Hello,

I am getting the same output as Piotr, I assume it has to do with credentials/community because I have turned off the firewall to make sure that isn’t the problem. The community string is correct but I’m not sure where to check on these so called credentials. I noticed the first comment mentioned something called eventual authentication, which i’m not entirely sure how to validate.

A quick background on what i am trying to achieve:

I have set up a Room Alert device for my server room which monitors the temperature, I have extracted the MIB file and have created a specific .oidlib using the MIB Importer but when i try creating a SNMP library sensor using the .oidlib file it fails and throws me the 2003 error. I have checked every all the basic troubleshooting steps provided in the following knowledge article:

https://kb.paessler.com/en/topic/46863-my-snmp-sensors-dont-work-what-can-i-do

Any help is appreciated!

Since the update to 20.3.61.1649+ we experience this problem on one device in our monitoring environment. And it’s not continuesly. It goes from green to red with the corresponding notification and after a while goes back to green again. When looking directly in the device there seems no problem to occur.
I will update now to version 20.3.62.1397 now to see if the problem disappears again.

Hi there,

In case the problem is still there after the update please create a dedicated Support Ticket. You can do this via the «Contact Support» button down in the right corner of your webclient or by sending a mail to [email protected]

Thank you!

Kind regards,
Andreas Günther
Tech Support, Paessler AG

[email protected]

You have to deactivate Control Panel-> System -> Security -> IP-Access
deactivate ssh telnet https

There is no generic solution for it. The error message shown «No response […] (SNMP error # -2003)» indicates a timeout and/or that PRTG is not able to receive the requested information via SNMP.

You need to verify that SNMP is properly configured on the monitored device and also configure the incoming SNMP communication from PRTG’s perspective properly.
To do so, please open the «Settings» tab of the device that has the affected sensor and configure the required SNMP settings under Credentials for SNMP Devices.

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.

If you receive a prtg error, this article was written to help you.

Updated

  • 1. Download ASR Pro
  • 2. Run the program
  • 3. Click «Scan Now» to find and remove any viruses on your computer

    • Speed up your computer today with this simple download.

    g.

    g.

    Make Life Easier For All Sysadmins

    prtg error

    Since we want to keep it as easy as possible for you as a sysadmin, here’s a little glossary onand more common error codes, problems, and messages that you may encounter on your system. time.

    We hope tracking (in addition to PRTG, Connected Course)
    makes your day a little better.

    Sometimes clients use the problems reported by PRTG Network Monitor when setting up monitoring of their systems using Simple Network Management Protocol (SNMP). Most

    In some cases, these problems are the result of incorrect settings or SNMP settings.

    This article provides an overview of the most common causes of SNMP monitoring problems.

    First Steps

    How do I reset PRTG?

    In the Probe Management Tools section, you can either restart all probes (continue! In the Restart All Probes section), if desired, restart a specific probe (click Restart Probe in the Probe [number] [name] section). Windows Trial Service will restart your computer even after updating the critical PRTG server.

    Important! Before diving into troubleshooting, you should have a good understanding of SNMP principles and performance!

    • For an overview of SNMP technology, see Paessler IT Explained: SNMP.
    • You can find an overview of SNMP and MIBs, OIDs in How do SNMPs, MIBs and OIDs work?
    • Suitable SNMP sensors can be found under Which SNMP sensors does PRTG offer?

    Basic SNMP Troubleshooting

    1. Basic SNMP Requirements For SNMP Ambition Device

    • Enable SNMP on the device. For more information, see How do I install SNMP on Windows service systems?
    • Allow SNMP access for the computer running PRTG Network Monitor in the device settings.
    • Allow User Data Protocol (UDP) packets to be sent from the machine running PRTG to the device you want to monitor and vice versa. If the device and PRTG are on opposite sides of the firewall software, make sure UDP access to Connector 161 (SNMP) is allowed. Moreover, the way back must be open. See the following articles for more information:
      • Microsoft: open ports in firewall
      • How do I usually change the SNMP port number in Windows?
    • Make sure the device under test has the latest firmware! If an SNMP sensor (for example, a regular SNMP traffic sensor) receives very little packets from the monitored device, a firmware update for that device will likely help.
    • Look, SNMP doesn’t work either! Could you help me ?! on our Paessler website.

    2. PRTG Settings For SNMP

    SNMP partnership error

    • SNMP version 1
    • SNMP version 2c (recommended)
    • SNMP 3

    It is important to know which SNMP service to choose because if the product is not supported by the server or monitored device, you may receive an error message. Unfortunately, only this minimal information, for example, does not allow a connection to be established.

    Check or change the SNMP version previously used by PRTG in settings | Identifiers for SNMP devices in an engine or group.

    SNMP Authentication Error

    • Community Strings: A community string is similar to a user ID or password in the sense that it allows you to connect to statistics for a device. PRTG sends one with all SNMP requests. If the community string is often incorrect, the device denies requests and takes no action. This value is case sensitive!
    • Username
    • Passwords

    Error messages indicating something is wrong. Often these terms are:

    • Failed to establish connection
    • Error # 10060
    • Error number 2003

    SNMP Performance Limits

    SNMP v3 recently had software dependent performance limitations due to SSL encryption.If anyone is having trouble overloading SNMP with v3, try these options:

    • Increase the monitoring interval for SNMP v3 sensors. PRTG can currently typically handle about 40 requests from the second and primary computer, depending on the user’s system. This means that on a typical 1.x GHz computer with cores, two people can monitor approximately 5000 SNMP v3 alarm systems with a scan interval of 60 seconds.
    • Spread SNMP v3 sensors across two or more probes if specific SNMP channel values ​​increase with probe interval delay or open core health / probe health probe probe requests.
    • Switch to SNMP v1 or if v2 works without encryption, as these types do not have these restrictions.

    Target SNMP Monitoring Software

    Updated

    Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don’t wait any longer, download ASR Pro today!

    Expected data from a probe via SNMP may not work (polling localhost, 127.0.0.1, or :: 1). This isIt will appear if you add this device to PRTG under the IP address it has as part of your network and create an SNMP probe on this device.

    Advanced SNMP Troubleshooting

    When users need to troubleshoot their SNMP sensors and verify all basic SNMP requirements, they can debug SNMP activity to find notifications and / or data problems in SNMP monitoring configurations.

    What does it mean when PRTG puts a sensor into unusual state?

    “Unusual” PRTG detection An unusual state is a state built into the autopilot that is intended to represent when an absolute gauge exceeds standard average usage limits based on a particular programming structure.

    For Paessler, this is a Paessler SNMP Tester that performs simple SNMP queries on a device on your network. If the connection works with this tool, you understand that it also works with PRTG.

    Troubleshooting SNMP Actions – Steps

    1. Access to SNMP Paessler tester.
    2. Download the zip file and follow the instructions on the page.
    3. Find on the target device the system running your PRTG probe. Analyze only after working hours, and then for other values.
    4. Check to see if reviews are coming back.
    • How can I test my SNMP device for Awesome?
    • How to Handle Subkey Unablefail “or” Error 10060 “when using SNMP?

    Import MIB

    prtg error

    Many network devices and programs come with Management Basic Information (MIB) files that describe settings and read documents available for monitoring via SNMP. With the MIB importer along with Paessler, you can import most of these MIB files and convert them to OIDs for PRTG. This makes it easy to configure SNMP library sensors.For more information see Paessler MIB Importer in addition to Converter.

    Note. PRTG creates a log file mibparser.log for debugging MIB imports. This file contains all warnings and errors that may occur while reading the MIB file. You can view the file in the MIB subfolder of the PRTG program directory.

    Tips & Tricks

    How do I disable PRTG?

    Run the Uninstall PRTG Network Monitor command from the Windows Start menu or open the Windows Control Panel and select the required entry in the Programs and Features section.If necessary, confirm the question in the “Windows User Account Control” section by clicking “Yes” so that you can undoubtedly uninstall the program.

    SNMP, Windows And PRTG

    • How do I install the SNMP service on Windows systems?
    • What security aspects should I consider when working with SNMP versus Windows?
    • I want to use SNMP sensors that use WMI sensors. What can I do?
    • What SNMP sensors does PRTG Mac offer?

    SNMP Operating System Home And PRTG

    • How do I enable SNMP for Mac OS so that it can also be monitored with PRTG?

    SNMP, Linux And PRTG

    • Checklist: Configuring SNMP on Linux

    SNMP And PRTG Traps

    • Can the application send SNMP traps using PRTG?
    • How to use an interrupt receiver like PRTG and what are its limitations?
    • How to check the SNMP trap receiver sensor?

    SNMP Sensors And Devices

    • How can I see all interfaces when adding an SNMP sensor to find my Cisco device?
    • My Cisco switch monitoring may not work properly with SNMP. What can I do?
    • No similar name (SNMP error # 2) for NetApp sensors
    • NetApp SNMP System Status: Error 137
    • SNMP Error # 223 on HP C3000 Server Blade
    • My Juniper switches are showing false 0, almost no value. What can I do?
    • What can I check if SNMP and SSH sensors are giving timeout and authentication errors?

    Other Problems May Arise

    • How to read OID in DateAndTime format?
    • How to convert the default values ​​of automatically generated names for newSNMP sensors?
    • Some of my SNMP alerts don’t work after upgrading PRTG 8 to PRTG 9 or higher (may also work after upgrading other versions)

    Further Reading

    For general information about SNMP, see the following Microsoft TechNet content pages:

    • What is SNMP?
    • How SNMP Works
    • Quo Vadis, SNMP? SNMP Implementation and SNMP Implementation

    Note. SNMP v1 does not support 64-bit counters, which can lead to incorrect data when monitoring website views over SNMP. We recommend that you try SNMP v2c (the most common) or SNMP v3.

    Speed up your computer today with this simple download.

    Советы по устранению неполадок при ошибках Prtg
    Wskazówki Dotyczące Rozwiązywania Problemów Z Błędami Prtg
    Suggerimenti Per La Risoluzione Dei Problemi Per Errori Di Stampa
    Consejos Para La Resolución De Problemas De Errores Prtg
    Tipps Zur Fehlerbehebung Bei Prtg-Fehlern
    Dicas De Solução De Problemas Para Erros Prtg
    Prtg 오류에 대한 문제 해결 팁
    Tips Voor Het Oplossen Van Problemen Bij Prtg-fouten
    Felsökningstips För Prtg-fel
    Conseils De Dépannage Pour Les Erreurs De Prtg

    Taj Chirnside

    • Remove From My Forums

    • Вопрос

    • В сети из 18 серверов и нескольких Cisco 2960 и 3750 у всех серверов одинаковое железо и (за исключением специализированного для назначения  сервера) программное обеспечение (операционная система
      на всех серверах стоит «Windows 7 Профессиональная»). Один из серверов предназначен для сбора информации от датчиков железа всех серверов сети и о состоянии программного обеспечения (запущено/не запущено) по протоколам SNMP
      и WMI; для отображения информации используется программное обеспечение PRTG Network Monitor.

      Периодически (неделя через неделю, день через день, час через час — вообщем всегда по разному) перестают поступать параметры о состоянии почти ото всех серверов.

      Вот ошибки, которые пишет PRTG:

      1) Ошибка при передачи данных по WMI:

      Connection could not be established (Port Error 135: RPC Server not accessible. — Host: 172.19.206.3, User: Иванов, Password: ******, Domain: ntlmdomain:servmon-z2) (code: PE015)

      2) Ошибка при передачи данных по SNMP:

      No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community,
      passwords etc) (SNMP error # -2003)

      Перепробывали многое, из того что написано на форумах, — не помогает…

      Подскажите пожалуйста решение проблемы?!

    Источник

    Понравилась статья? Поделить с друзьями:
  • Smtp error from remote mail server after pipelined end of data
  • Smbios 0x16 error supermicro
  • Smbios 0x01 error supermicro
  • Slime rancher ошибка unity
  • Sl4a error clip db not found