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


Does PRTG provide native sensors for FortiGate firewalls?

Votes:

0

Your Vote:

Up

Down

In my network I have a firewall from FortiGate.

We're using the standard sensors in PRTG but this device's operation is very sensitive for my organization and we want to have additional monitoring so that we are alerted as soon as anything goes wrong.

What are my options?

device-template firewall fortigate paetemplate prtg snmp system-health

Created on Apr 3, 2017 7:15:12 AM by  Luciano Lingnau [Paessler Support]

Last change on Aug 10, 2017 8:23:11 AM by  Luciano Lingnau [Paessler Support]



8 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 16.3.25 or later

Additional Sensors for FortiGate Firewalls

While PRTG provides a couple of sensors that work with FortiGate firewalls by default, for example the SNMP Traffic sensor and the SNMP System Uptime sensor, you may still be interested in more detailed sensors.

FortiGate has a very extensive SNMP implementation which can lead to issues when you try to import or deploy a complete oidlib file and use the SNMP Library sensor. If you encounter this issue, please refer to PRTG hangs when adding SNMP library sensor.

In this article we describe a different approach that does not use the oidlib, but you could still use it for other sensors.

Adding FortiGate Sensors via Auto-Discovery

You can use the device template that we provide below to automatically create custom sensors with the PRTG auto-discovery.

The metrics that you can actually monitor vary depending on the size, management, and monitoring capabilities of your firewall model. The sensors can monitor the following if the data is available:

  • System Statistics
    • Total CPU Usage
    • Session Count
    • Memory Usage
  • Detailed CPU Metrics
    • Total Usage (per CPU)
    • User (time) Usage
    • System (time) Usage
  • Hardware Sensor
    • Value
    • Alarm (state)
  • HA Member (One Sensor per Member)
    • CPU Usage
    • Memory Usage
    • Session Count
    • Sync Status
  • VPN Tunnel
    • Status (state)
    • Traffic In/Out
  • Link Monitor
    • State (Alive/Dead)
    • Packets Sent/Received
    • Latency
    • Jitter

The device template creates the available and compatible sensors based on the data at hand. The sensors implement default alerts whenever possible, but you can still fine-tune most channels by defining additional limits in the sensor channels settings or modifying the lookups included by default.

Requirements

  • PRTG Network Monitor 16.3.25 or later
  • Because the device template relies on the auto-discovery process, the device you want to monitor needs to be reachable via PING.
  • SNMP must be enabled and the device must support the FORTINET-FORTIGATE-MIB from FortiGate.

Known Issues and Limitations

  • Because of the way that the vendor implemented the MIB, the Health sensors do not provide a unit for the readings, but provide alerts since the sensors also evaluate the status of the fgHwSensorEntAlarmStatus for the corresponding entry.
  • A non-clustered unit may cause alerts (Warning by lookup value 'Unsynchronized' in Sync Status) - You can either adjust the lookup or delete this sensor if you're not using a cluster.
  • A non-installed, redundant power supply may be recognized as an issue or alarm. If your device does not have an RPS, you can either acknowledge or delete the sensor to stop this alert.
  • PRTG shows the alerts as reported by the monitored device via SNMP using lookups. If the status is not reported correctly via SNMP, PRTG cannot detect any issues. For additional alerts, please set up limits for additional channels.
  • This device template was created based on data collected from other customers, so we cannot guarantee that the sensors described above will work on your systems. Use these components at your own risk. Please test and validate the sensors in your environment after deploying them.
  • VPN Tunnel: The template will produce one VPN Tunnel sensor per VPN x SA (Security Association). As a result you may see two or more entries for a single VPN. This happens because each VPN is listed as multiple entries in the fgVpnTunTable, distinguishable only by the fgVpnTunEntPhase2Name. To get an "Overall" status when there are multiple entries per VPN, please consider the Business Process Sensor. Here are a couple of examples: KB: How can I use the Business Process sensor?

Deployment and Usage

  1. Download the required zip archive here.
  2. Extract the archive to your PRTG program directory. By default, this is %Program Files (x86)%\PRTG Network Monitor\.
  3. In PRTG, restart the core server: open Setup | System Administration | Administrative Tools | Restart Core Server and click Go!. This ensures that the MIB and lookups are loaded before you run the auto-discovery.
  4. Create a new device in PRTG with the address (IP or FQDN) of the device that you want to monitor and configure the SNMP credentials accordingly.
  5. Right-click your new device, select Run Auto Discovery with Template, and select the Custom Fortigate Health v0.x from the list.
    Note: Using the auto-discovery with a dedicated device template is convenient here because it automates the creation of the custom sensors in an organized fashion.
  6. The sensors are deployed after a couple of seconds.
  7. You can adjust the channel limits or lookups to your needs later.

Result

The resulting sensors look like this:

Sensor's Overview

Sensor's Overview

Click for full-screen view

Device's Overview

Sensor's Overview

Click for full-screen view

No sensors deployed? :(
Please read ahead for troubleshooting.


Troubleshooting

Have any issues? Please don't hesitate to contact us by replying to this post or via a support ticket. Please make sure to mention this KB post. Please read ahead for troubleshooting steps that you can take in advance.

Auto-Discovery Log

Your auto-discovery log tells you a lot about what went wrong during the sensor's deployment. You can troubleshoot the auto-discovery by inspecting the auto-discovery log. If you get entries like the one below (NOT FOUND), it means that the required protocol or Object Identifier (OID) is not available.

[...]
23.02.2017 14:37:58: Device ID: 19294 Name: somename EMULATOR@163 Host: somehost.somedomain.sometld
23.02.2017 14:37:58: Device Templates; Device ID: 21890; Selected: 1
23.02.2017 14:37:58: Template Loaded; Device ID: 21890; Name: Custom Fortigate Health v0.1
23.02.2017 14:38:01: Template Check; Device ID: 21890; Check ID: ping; FOUND
23.02.2017 14:38:01: Template Assigned; Device ID: 21890; Name: Custom Fortigate Health v0.1
23.02.2017 14:38:06: Template Check; Device ID: 21890; Check ID: snmp_fgProcessorTable; FOUND
23.02.2017 14:38:16: Template Check; Device ID: 21890; Check ID: snmp_fgHwSensorTable; NOT FOUND
[...]

In the example above, some sensors were skipped because the device did not respond to the snmp_fgHwSensorTable check. This means that this data is probably not available on your device. You can track this data by looking for the name after snmp_. In this case, a search for fgHwSensorTable will tell you which OID from the MIB is missing.

You can also use this log to identify if the discovery was interrupted because the device did not respond to PING or to a basic SNMP check.

SNMP Data

If the discovery log is not sufficient, you can review the SNMP data directly from your device. To do so, save the text below (in the white box) as .txt and use it with the Scan Script option in our SNMP Tester. This will allow you to review which SNMP queries succeed and which do not deliver any data. Please have this information at hand when contacting our support team.

--------
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
----
fgLinkMonitor
walk=1.3.6.1.4.1.12356.101.4.8
----

Version History

VersionDescription
0.1Initial Release
0.2Added HA Member sensor(s)
0.3Fixed issue in HA Status Lookup (thanks JohnG)
0.4Added VPN Tunnel Status/Traffic (thanks Mark G.)
0.5Added support for Fortigate Link Monitors
0.6Modified the way the "VPN Tunnel" works to make them more reliable (in Detail: The sensor now uses the fgVpnTunEntPhase2Name for tracking within the Table. This means one working sensor per VPNxSA



Best Regards,
Luciano Lingnau [Paessler Support]

Created on Apr 3, 2017 7:15:37 AM by  Luciano Lingnau [Paessler Support]

Last change on Jan 9, 2019 8:22:21 AM by  Luciano Lingnau [Paessler Support]



Votes:

1

Your Vote:

Up

Down

Very useful, thanks for this.

There's an error in the HA value lookup table, causing it to report an error when HA units are in sync. The corrected file is as below:

    <SingleInt state="Error" value="0">Unsynchronized</SingleInt>
    <SingleInt state="OK" value="1">Synchronized</SingleInt>

the original file had

    <SingleInt state="Warning" value="0">Unsynchronized</SingleInt>
    <SingleInt state="Error" value="1">Synchronized</SingleInt>

Created on May 8, 2017 6:53:26 PM by  JohnG (10)

Last change on Jan 7, 2019 10:02:55 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thank you for the feedback and input. Well spotted, I've adjusted the included lookup in the zip file for download. Any other tips/suggestions are also welcome. :)

Best Regards,
Luciano Lingnau [Paessler Support]

Created on May 9, 2017 5:30:00 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Do you happen to have a template that works for Fortiweb device ?

Created on Nov 13, 2018 2:08:56 PM by  silavric (0) 1



Votes:

0

Your Vote:

Up

Down

Hello silavric,
thank you for your reply.

At the present time there is no Fortiweb specific template. However, depending on how Fortigate did this (If they've implemented the same FORTINET-FORTIGATE-MIB) the template above might work just as well. The template won't refuse to work if the device isn't a Fortigate. As long as the relevant metrics are present, sensors will be deployed (I assume that for instance the CPU and Hardware implementation might be common to the two devices).

Just remember to enable SNMP before trying to use the template. You can also perform the test suggested in the Troubleshooting\SNMP Data section of the article to check if any data is available for the relevant OID's on your particular device (Fortiweb).

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Nov 14, 2018 6:27:23 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello,

Will you edit it to have the Performance SLAs instead of the link monitors? It's new with FortiOS 6.0.*. The oid walk is 1.3.6.1.4.1.12356.101.4.9.

Created on Jan 30, 2019 8:07:41 PM by  mike_dp (10)



Votes:

0

Your Vote:

Up

Down

Hi Mike,

Thanks for letting us know! Could you provide what you specifically changed so we can adjust the guide above?

Best regards.

Created on Jan 31, 2019 8:02:11 PM by  Dariusz Gorka [Paessler Support]



Votes:

1

Your Vote:

Up

Down

It's pretty much like the link monitors but the name is different and the OID used is different too. I tried to edit it by myself but something doesn't work and I'm not sure how to troubleshoot it. Performances SLAs are like advanced link monitors and are used with SD-WAN. It's continuous checks to make sure the connection related to it is still reliable. I'm using a custom snmp table for now in PRTG but maybe with this it would be easier to configure in PRTG.

The table oid used is 1.3.6.1.4.1.12356.101.4.9.1 for health checks (performance SLAs) instead of 1.3.6.1.4.1.12356.101.4.8.1 for the link monitors and the table name is fgvwlhealth check link.

Fortinet has a new mib with it with their OS 6.0.*

Created on Feb 1, 2019 7:49:02 PM by  mike_dp (10)

Last change on Feb 4, 2019 11:14:18 AM by  Dariusz Gorka [Paessler Support]



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.