Solved

[network::fortinet::fortigate::snmp::plugin] --mode=vpn UNKNOWN: SNMP Table Request: Timeout

  • 3 February 2023
  • 5 replies
  • 619 views

Userlevel 1
Badge +8

Hi there,

I am running centreon_fortinet_fortigate.pl to collect vpn data for multiples hosts. All of them respond as expected but one that returns timeout. This one has all the same configuration as the others, and its snmp queries are ok. I have no idea why the script for this host fails

normal host:

/usr/lib/centreon/plugins/centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --mode=vpn --hostname=2804:300:0:3fff::16 --snmp-version='2c' --snmp-community='public'
OK: Virtual domain 'root' Logged users: 0, Active web sessions: 0, Active tunnels: 0 - All vpn are ok | 'users'=0users;;;0; 'sessions'=0sessions;;;0; 'active_tunnels'=0tunnels;;;0; 'traffic_in_TU_1_INSS-ADM'=6785.95b/s;;;0; 'traffic_out_TU_1_INSS-ADM'=4931.87b/s;;;0; 'traffic_in_TU_1_INSS-DCDF'=78208.75b/s;;;0; 'traffic_out_TU_1_INSS-DCDF'=6166.38b/s;;;0; 'traffic_in_TU_1_INSS-DCRJ'=88907.79b/s;;;0; 'traffic_out_TU_1_INSS-DCRJ'=7361.37b/s;;;0; 'traffic_in_TU_1_INSS-DCSP'=14426.39b/s;;;0; 'traffic_out_TU_1_INSS-DCSP'=8742.48b/s;;;0; 'traffic_in_TU_2_INSS-ADM'=697.41b/s;;;0; 'traffic_out_TU_2_INSS-ADM'=697.33b/s;;;0; 'traffic_in_TU_2_INSS-DCDF'=739.46b/s;;;0; 'traffic_out_TU_2_INSS-DCDF'=714.07b/s;;;0; 'traffic_in_TU_2_INSS-DCRJ'=697.26b/s;;;0; 'traffic_out_TU_2_INSS-DCRJ'=695.79b/s;;;0; 'traffic_in_TU_2_INSS-DCSP'=697.53b/s;;;0; 'traffic_out_TU_2_INSS-DCSP'=699.51b/s;;;0;

this host:

 /usr/lib/centreon/plugins/centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --mode=vpn --hostname=2804:300:0:3fff::38 --snmp-version='2c' --snmp-community='public'
UNKNOWN: SNMP Table Request: Timeout

it returns all the snmpwalk tree requested from vpn.pm:

snmpwalk -v 2c -c public 2804:300:0:3fff::38 .1.3.6.1.4.1.12356.101.12.2
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.1.1 = STRING: "TU_1_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.2.1 = STRING: "TU_2_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.3.1 = STRING: "TU_1_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.4.1 = STRING: "TU_2_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.5.1 = STRING: "TU_1_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.6.1 = STRING: "TU_2_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.11.1 = STRING: "TU_1_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.12.1 = STRING: "TU_2_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.1.1 = STRING: "TU_1_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.2.1 = STRING: "TU_2_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.3.1 = STRING: "TU_1_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.4.1 = STRING: "TU_2_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.5.1 = STRING: "TU_1_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.6.1 = STRING: "TU_2_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.11.1 = STRING: "TU_1_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.12.1 = STRING: "TU_2_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.1.1 = IpAddress: 177.15.136.24
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.2.1 = IpAddress: 177.15.132.16
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.3.1 = IpAddress: 177.14.176.56
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.4.1 = IpAddress: 177.14.160.8
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.5.1 = IpAddress: 177.14.96.1
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.6.1 = IpAddress: 186.238.112.94
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.11.1 = IpAddress: 177.15.136.0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.12.1 = IpAddress: 177.15.132.24
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.1.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.2.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.3.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.4.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.5.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.6.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.11.1 = Gauge32: 0
...

it works ok for the other modes:

/usr/lib/centreon/plugins/centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --mode=hardware --hostname=2804:300:0:3fff::38 --snmp-version='2c' --snmp-community='public'
OK: All 3 components are ok [3/3 sensors]. | 'CPU ON-DIE Temperature#hardware.sensors.measure'=56;;;; 'MV1514 Temperature#hardware.sensors.measure'=37;;;; 'MV1515 Temperature#hardware.sensors.measure'=67;;;; 'hardware.sensors.count'=3;;;;

help me please

@sims24

icon

Best answer by gespada 4 February 2023, 16:47

View original

5 replies

Userlevel 4
Badge +14

Hi,

Could you try others options like :

--snmp-autoreduce

Or

--snmp-force-getnext

Or

--snmp-retries (with a value)

You could see others options here : https://github.com/centreon/centreon-plugins/blob/90b5de21b7b35267aece2cdb2ee1f04bb738ff6f/src/centreon/plugins/snmp.pm#L974

With a FortiADC with SNMPv3, i do add options : https://thewatch.centreon.com/data-collection-6/centreon-plugins-fortinet-fortiadc-250?postid=1646#post1646

Wasn't a timeout for me..

Userlevel 1
Badge +8

Hi @gespada , I’ve tried every single options, even all of them and I am still getting timeout for this host. Curiously it’s response is pretty fast using snmpwalk.

Userlevel 4
Badge +14

Hi @gespada , I’ve tried every single options, even all of them and I am still getting timeout for this host. Curiously it’s response is pretty fast using snmpwalk.

The perl module about vpn contains many OID, coud you test each OID , to investigate the timeout problem ?

https://github.com/centreon/centreon-plugins/blob/90b5de21b7b35267aece2cdb2ee1f04bb738ff6f/src/centreon/common/fortinet/fortigate/snmp/mode/vpn.pm#L146

To

https://github.com/centreon/centreon-plugins/blob/90b5de21b7b35267aece2cdb2ee1f04bb738ff6f/src/centreon/common/fortinet/fortigate/snmp/mode/vpn.pm#L162

This Fortigate have the same OS than the others ?

Userlevel 1
Badge +8

The perl module about vpn contains many OID, coud you test each OID , to investigate the timeout problem ?

The vpn.pm has all oid inside the .1.3.6.1.4.1.12356.101.12.2 tree. As I mentioned, it responds really well for this tree:

it returns all the snmpwalk tree requested from vpn.pm:

snmpwalk -v 2c -c public 2804:300:0:3fff::38 .1.3.6.1.4.1.12356.101.12.2
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.1.1 = STRING: "TU_1_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.2.1 = STRING: "TU_2_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.3.1 = STRING: "TU_1_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.4.1 = STRING: "TU_2_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.5.1 = STRING: "TU_1_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.6.1 = STRING: "TU_2_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.11.1 = STRING: "TU_1_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.2.12.1 = STRING: "TU_2_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.1.1 = STRING: "TU_1_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.2.1 = STRING: "TU_2_INSS-DCDF"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.3.1 = STRING: "TU_1_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.4.1 = STRING: "TU_2_INSS-DCRJ"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.5.1 = STRING: "TU_1_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.6.1 = STRING: "TU_2_INSS-DCSP"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.11.1 = STRING: "TU_1_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.3.12.1 = STRING: "TU_2_INSS-ADM"
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.1.1 = IpAddress: 177.15.136.24
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.2.1 = IpAddress: 177.15.132.16
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.3.1 = IpAddress: 177.14.176.56
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.4.1 = IpAddress: 177.14.160.8
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.5.1 = IpAddress: 177.14.96.1
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.6.1 = IpAddress: 186.238.112.94
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.11.1 = IpAddress: 177.15.136.0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.4.12.1 = IpAddress: 177.15.132.24
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.1.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.2.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.3.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.4.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.5.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.6.1 = Gauge32: 0
SNMPv2-SMI::enterprises.12356.101.12.2.2.1.5.11.1 = Gauge32: 0
...

 

I have also tested each single request just like the script does, I don’t know why the script times out.

I am almost sure all fortigates are indentical in OS and version but I will compare the running configuration and check the differences at monday.

Userlevel 1
Badge +8

This Fortigate have the same OS than the others ?

 

There was a lack of configuration missing on this one when we compared with the others.

Thanks for the attention

Reply