New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

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

 

Top Tags


View all Tags


Can't receive tunnel status fortinet 100D

Votes:

0

Your Vote:

Up

Down

Dear team

Please help me to check my issue , I've followed this link to create custom sensors with the PRTG auto-discovery:

I've succeed to discovered the Ipsec tunnel status on my fortinet 200D , but i don't know why it can not get the tunnel status on another fortinet device (forinet 100D) , after query snmp status it just show all information exclude status of IPsec tunnel , i don't know why ? Can you please guide me how to fix it

Thanks and Regards

Ryan

fortinet vpn-snmp vpn-tunnel

Created on Aug 17, 2018 10:29:09 AM by  ryantrung (0) 1

Last change on Aug 17, 2018 11:22:56 AM by  Luciano Lingnau [Paessler Support]



6 Replies

Votes:

0

Your Vote:

Up

Down

Hello Ryan,
thank you for your KB-Post.

Please refer to the Troubleshooting section of the mentioned topic and provide us with the output from the SNMP Tester test (described under SNMP Data). This will allow us to confirm what data is or isn't available. The sensor can only work with available data, if the data is missing in the walk, you'll have to check with the vendor what the cause could be.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Aug 17, 2018 11:48:23 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Luciano

Thanks for your reply , after follow Troubleshooting , this is error in my auto discovery debug log :

Template Create Meta Request; Device ID: 3651; Create ID: _snmp_fgVpnTunTable; ERROR: 106

please advise

Thanks and Regards
Ryan

Created on Aug 17, 2018 2:15:07 PM by  ryantrung (0) 1

Last change on Aug 20, 2018 6:33:53 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Ryan,
thank you for your reply.

Sounds like the data is not available. To confirm this, I need you to perform the following:


SNMP Data

Save the text below (in the white box) as .txt and use it with the Scan Script option in our SNMP Tester. Share the output from the SNMP Tester this. This will allow us to confirm which SNMP queries succeed and which do not deliver any data.

--------
Walk Default
--------
hrSystemUptime
walk=1.3.6.1.2.1.25.1.1
--------
MIB-2 System
walk=1.3.6.1.2.1.1
--------
Sensor Specific Queries
----
fgha
walk=1.3.6.1.4.1.12356.101.13.1
----
fgSystem
walk=1.3.6.1.4.1.12356.101.4
----
fgAppWebCache
walk=1.3.6.1.4.1.12356.101.10.113
----
fgVpn
walk=1.3.6.1.4.1.12356.101.12
----

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Aug 20, 2018 6:35:53 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Luciano

Please review my log file below ,

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: 
8/21/2018 3:58:00 PM (2 ms) : 
8/21/2018 3:58:00 PM (3 ms) : SNMP V2c
8/21/2018 3:58:00 PM (4 ms) : Scan Script: test.txt
8/21/2018 3:58:00 PM (5 ms) : --------
8/21/2018 3:58:00 PM (6 ms) : Walk Default
8/21/2018 3:58:00 PM (7 ms) : --------
8/21/2018 3:58:00 PM (8 ms) : hrSystemUptime
8/21/2018 3:58:00 PM (10 ms) : walk 1.3.6.1.2.1.25.1.1
[...]
8/21/2018 3:58:15 PM (15182 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.475 = "475" [ASN_INTEGER]
8/21/2018 3:58:15 PM (15212 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.476 = "476" [ASN_INTEGER]
8/21/2018 3:58:15 PM (15241 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.477 = "477" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15266 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.478 = "478" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15290 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.479 = "479" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15316 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.480 = "480" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15341 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.481 = "481" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15366 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.482 = "482" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15391 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.483 = "483" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15416 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.484 = "484" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15440 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.485 = "485" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15465 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.486 = "486" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15489 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.487 = "487" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15513 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.488 = "488" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15537 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.489 = "489" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15563 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.490 = "490" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15587 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.491 = "491" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15611 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.492 = "492" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15635 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.493 = "493" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15660 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.494 = "494" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15685 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.495 = "495" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15709 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.496 = "496" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15733 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.497 = "497" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15757 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.498 = "498" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15781 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.499 = "499" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15806 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.500 = "500" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15833 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.501 = "501" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15914 ms) : 1.3.6.1.4.1.12356.101.12.2.2.1.1.502 = "502" [ASN_INTEGER]
8/21/2018 3:58:16 PM (15939 ms) : 1.3.6.1.4.1.12356

Created on Aug 21, 2018 9:04:15 AM by  ryantrung (0) 1

Last change on Aug 21, 2018 9:21:54 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello ryantrung,
thank you for your reply and output of the test.

I've omitted part of the test, to focus on what is relevant.

The test appears to have stopped (or the output is incomplete) but shows that there are more than 500 VPN's in the VPN's Table. This is probably too much for PRTG to handle.

How many VPN's are there actually, on this Fortigate device?

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Aug 21, 2018 9:23:27 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Luciano

No , I just have about 77 VPNs connection , after using custom sensor to check ( using OID : 1.3.6.1.4.1.12356.101.12.1.1.0 )

Thanks and Regards Ryan

Created on Aug 21, 2018 9:30:02 AM by  ryantrung (0) 1



Please log in or register to enter your reply.


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.