you could write a local check and just echo the output of the OID:
#!/bin/bash
hostname="[SET HOSTNAME OF FIREWALL HERE]"
ip="[SET IP OF THE FIREWALL HERE]"
community="[SET CNMP COMMUNITY STRING HERE"
forti_fw_version=`snmpget -v2c $ip -c $community -On .1.3.6.1.2.1.47.1.2.1.1.2.1 | cut -d"," -f3
echo "<<<<${HOSTNAME}>>>>"
echo "<<<local>>>"
echo "0 \"FortiGate Version\" - ${forti_fw_version}"
echo "<<<<>>>>"
Place this as a shell script under /usr/lib/check_mk_agent/local/ and your good to go. (I hope I do not have any typo in the script )
and just to mention: with this script it should be displayed on the firewall itself, you only have to enter the host name of the firewall or the name used in checkmk for the firewall and the piggyback processing must be active.
yes, we have approximately 40-50 fortigate devices already in our monitoring.
Is this snmp info check part of the check mk installation? We are using the cme version: 2.0.0p20
I found an external article which should bring me closer to a solution via the snmp info check. Check_MK: SNMP based Check – LANbugs
Lets see what i can do.
Yes, every SNMP based device should discover it. It contains the sysContact, sysLocation and oftentimes some sort of version information. It is plainly called ‘SNMP Info’.