Skip to main content

Hi,

I have installed centreon_fortinet_fortigate.pl fro the Monitoring connector manager.

In the available mode I have uptime listed.

/centreon_fortinet_fortigate.pl  --plugin=network::fortinet::fortigate::snmp::plugin --list-mode
Plugin Description:
Check Fortinet Fortigate in SNMP.

...

Modes Available:
ap-usage
cluster-status
cpu
disk
hardware
interfaces
ips-stats
link-monitor
list-interfaces
list-link-monitors
list-switches
list-virtualdomains
memory
sdwan
sessions
signatures
switch-usage
uptime
vdom-usage
virus
vpn

However when I try it:

> /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl  --plugin=network::fortinet::fortigate::snmp::plugin --mode=uptime --hostname=X.Y.Z.A --snmp-version='2c' --snmp-community='dummy'

UNKNOWN: Cannot load module --mode.
Can't locate snmp_standard/mode/uptime.pm in @INC (you may need to install the snmp_standard::mode::uptime module) (@INC contains: /usr/lib/centreon/plugins FatPacked::94775752674704=HASH(0x5632b3124d90) /usr/local/lib64/perl5/5.32 /usr/local/share/perl5/5.32 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 6069.

At first I thought I was missing a plugin in the Monitoring connector manager but generic snmp module is installed. Then by looking at similar error message on the web it seems to be an issue in the plugin istself.

I am not an expert on centreon so is it me doing something very stupid or is there an bug in the plugin?

hello

the “fatpack” plugins are compiled by centreon and they should include all the neccessary perl files, this looks like they missed a dependency 

the fatpack should have been installed with a package (rpm or deb), could you retrieve which package version was installed, so centreon can pinpoint which version is not woking

(for centos/rhel based you can “rpm -qa | grep -i forti” in the shell of the poller)

 

as an alternative : add the connector for “linux snmp” host

edit the fortigate host template and add the “uptime” for linux snmp OS, it the same base snmp OID and work fine

 

edit for clarity, in the host template config page, search the fortigate snmp custom template, go to relation and add the service template “OS-Linux-Uptime-SNMP-Custom” as show here : 

 

(or do not modify the template and simply add the service manually on the host, using the service template OS-Linux-Uptime-SNMP-Custom directly)


Thanks, again, for your quick answer. Using the linux snmp uptime for the host as a workaround did the trick.

Is there a specific way to inform centreon of the missing dependency or mentioning it here is enought?

As per the package installed on my server this is the installed version:

>root@tlsvsl0008:~]$ rpm -qa | grep -i forti

centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp-20250400-1.el9.noarch

>root@tlsvsl0008:~]$ dnf info centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp-20250400-1.el9.noarch
Last metadata expiration check: 2:32:27 ago on Thu May 22 09:18:56 2025.
Installed Packages
Name         : centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp
Version      : 20250400
Release      : 1.el9
Architecture : noarch
Size         : 683 k
Source       : centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp-20250400-1.el9.src.rpm
Repository   : @System
From repo    : centreon-plugins-24.04-stable-noarch
Summary      : centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp
URL          : https://centreon.com
License      : Apache-2.0
Description  : centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp
             : Commit: a45b479b7c0c3698c250b8640bf4a254d9293a74

 


here

github

support website (I think this is for non free customers, don’t know if IT-100 have access as I’m a entrepise edition user)

 

Centreonian are here all the time and will see that post


Hello :) 

I've studied your issue and I'm reproducing it in my test env, it turns out that the uptime resource is missing in the fatpack packaging (also we need to add commands and service template in the monitoring connector for uptime) so we'll fix that for the next release. Thanks for your feedback.

Kind regards.

 


Reply