search

riskersen / Monitoring

Monitoring plugins wich are Nagios/icinga compatible
65 stars 113 forks source link

[check_fortigate.pl]: unkown mem-sys #75

Open sgruber94 opened 3 years ago

sgruber94 commented 3 years ago

Hi, sorry for the delay. i have try the new script but i have a mistake

./check_fortigate.pl -H A.B.C.D -C [COMUNITY] -p [FORTISERIAL_PATH] -T mem-sys UNKNOWN: OID .1.3.6.1.4.1.12356.101.4.1.4.0.1 does not exist

The script add the .1 for the master and .2 for the slave, but this OID doesn't exist

Originally posted by @VincentROLLAND in https://github.com/riskersen/Monitoring/issues/59#issuecomment-943207835

sgruber94 commented 3 years ago

I opened a new issue for tracking this issue down.

I discovered the problem of that. It's the handling about the health check. Sadly I haven't any FGT 201 or FGT 60 Cluster, so I can't verify Cluster State

The Issue is, that the Value adds an .1 and .2 instead of nothing.

We can replace the HC with another function (internal change) or adding a Mode to the health check and try to call a "mode" for particular checks)

https://github.com/riskersen/Monitoring/blob/0e9b80225e0ee95a45bc53f3fc86c1f01a76475a/fortigate/check_fortigate.pl#L553-L564

sgruber94 commented 3 years ago

@VincentROLLAND take a look and test it please.

VincentROLLAND commented 3 years ago

Hi,

Sorry i was out of office, i have try the scrypt with 0e9b802, but it add again the .1 for master and .2 for slave:

./check_fortigate.pl -H A.B.C.D -C [COMMUNITY] -p [FORTISERIAL_PATH] -T cpu-sys UNKNOWN: OID .1.3.6.1.4.1.12356.101.4.1.3.0.1 does not exist

./check_fortigate.pl -H A.B.C.D -C [COMMUNITY] -p [FORTISERIAL_PATH] -T mem-sys UNKNOWN: OID .1.3.6.1.4.1.12356.101.4.1.4.0.1 does not exist

./check_fortigate.pl -H A.B.C.D -C [COMMUNITY] -p [FORTISERIAL_PATH] -T cpu-sys -s UNKNOWN: OID .1.3.6.1.4.1.12356.101.4.1.3.0.2 does not exist

./check_fortigate.pl -H A.B.C.D -C [COMMUNITY] -p [FORTISERIAL_PATH] -T mem-sys -s UNKNOWN: OID .1.3.6.1.4.1.12356.101.4.1.4.0.2 does not exist

VincentROLLAND commented 3 years ago

in fact i have try the same script than 1.8.10 with this link https://github.com/riskersen/Monitoring/blob/0e9b80225e0ee95a45bc53f3fc86c1f01a76475a/fortigate/check_fortigate.pl#L553-L564 i'm not used to with github... Could you provide me the link?

sgruber94 commented 3 years ago

Hi Vincent, thats the link: https://github.com/sgruber94/Monitoring-riskersen/blob/check_fortigate_unkownmem/fortigate/check_fortigate.pl

VincentROLLAND commented 3 years ago

Hi, it's OK and reflect the memory form fortigate GUI: ./check_fortigate.pl.1 -H A.B.C.D -C [COMMUNITY] -p [FORTISERIAL_PATH] -T mem-sys OK: A.B.C.D (Current device: [FORTISERIAL]) Memory is okay: 60%|'memory'=60%;80;90