Hello,
I'd like to understand what would be the difference, if any at all, between using a Zabbix Internal and an SNMPv2/SNMPv3 item to check whether, or not, a certain/a group of SNMP equipment is no longer responding to our SNMP requests to check the health it. I read on the forum post linked below:
"{Host:sysUpTime.0.nodata(1200)}=1
This will set the trigger true if the parmater of sysUpTime gets no data changes for more than 1200 seconds. So far it has worked very well fo me."
But could that cause false positive or there is no such thing? Using that trigger and "{Template SonicWall Firewall:zabbix[host,snmp,available].nodata(10m)}=1" would give me the same end result (informing when the SNMP device stops responding)?
Edit: After reading the documentation it seems like the internal checks will only tell me if the SNMP is available on the device but not necessarily mean our Zabbix is able to obtain the health of our device due to, a possible, timeout?
I'd like to understand what would be the difference, if any at all, between using a Zabbix Internal and an SNMPv2/SNMPv3 item to check whether, or not, a certain/a group of SNMP equipment is no longer responding to our SNMP requests to check the health it. I read on the forum post linked below:
"{Host:sysUpTime.0.nodata(1200)}=1
This will set the trigger true if the parmater of sysUpTime gets no data changes for more than 1200 seconds. So far it has worked very well fo me."
But could that cause false positive or there is no such thing? Using that trigger and "{Template SonicWall Firewall:zabbix[host,snmp,available].nodata(10m)}=1" would give me the same end result (informing when the SNMP device stops responding)?
Edit: After reading the documentation it seems like the internal checks will only tell me if the SNMP is available on the device but not necessarily mean our Zabbix is able to obtain the health of our device due to, a possible, timeout?