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

PRTG and Fortigate 500E

Votes:

0

I am having problems getting PRTG talking to our new Fortigate firewalls PRTG is installed on a windows 2016 server - we already use PRTG to monitor our switches successfully. The fortigate is configured to use SNMPv3. When I run the SNMP tester on the PRTG server I get a no response error.

04/06/2018 10:47:48 (21 ms) : SNMP V3 04/06/2018 10:47:48 (30 ms) : Uptime 04/06/2018 10:47:52 (4086 ms) : SNMP Datatype: ASN_PRIMITIVE 04/06/2018 10:47:52 (4101 ms) : ------- 04/06/2018 10:47:52 (4109 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 ) 04/06/2018 10:47:56 (8179 ms) : SNMP Datatype: ASN_PRIMITIVE 04/06/2018 10:47:56 (8187 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 ) 04/06/2018 10:47:56 (8194 ms) : Done

Any ideas what I am doing wrong?

500e fortigate snmp

Created on Jun 4, 2018 9:55:15 AM



2 Replies

Accepted Answer

Votes:

0

Dear AlienCowboy,

the error "-2003" can be caused by

  • using the wrong device address, so the target device does not respondo
  • or wrong SNMP credentials (like encryption method, key, port number and so on)
  • or by a device which responds not in time, or not at all

In order to isolate the issue, you could check if the device also supports SNMP v2c and try to get a v2c connection first, before you go for the v3 connection.

Created on Jun 4, 2018 11:35:37 AM by Arne Seifert [Paessler Support]



Votes:

0

Ahh yep that fixed it. The fortigate was capable of vSNMP v3 but the windows 2016 server doesn't seem to be.

Created on Jun 4, 2018 12:10:01 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.