You are welcome, it is such a great program I hope someday they continue to develop it.
First just right click on the device in question and SNMPwalk the device. (You will see how awesome this tool is)
In the new window check to see if values are returned.
If values are returned click on subtree and put part of the oid that you are interested in.
SnmpWalkoid.png
If you do not get any values, make sure the community string is the same in the dude and on the device. Change to SNMP v1 if v2 doesn't work.
Then you can simplify steps to help figure out what is not working. Place a known working OID on the appearance of the device label. If it is blank the dude is having trouble using SNMP to read the device.
[oid("1.3.6.1.4.1.12356.101.1.630.1.3")]
maybe you need .0
[oid("1.3.6.1.4.1.12356.101.1.630.1.3.0")]
Expand your label to prove your function is correct...
[if(string_size(oid("1.3.6.1.4.1.12356.101.1.630.1.3")), oid("1.3.6.1.4.1.12356.101.1.630.1.3")+1 ,"False")]
Place the label directly into a function.
Function
Fortigate_90D_CPU_a
if(string_size(oid("1.3.6.1.4.1.12356.101.1.630.1.3")), oid("1.3.6.1.4.1.12356.101.1.630.1.3")+1 ,"False")
Try the function on a label...
[Fortigate_90D_CPU_a()]
Later in the value of the probe you can subtract 1.
Fortigate_90D_CPU_a() -1
since the added 1 keeps the probe from failing when CPU=0% utilization.
Finally if you can't determine the trouble...
Run wireshark add a filter "host 192.168.1.1" then start a capture, see the exact packets being sent and received, does it look like a conversation?
Lebowski
You do not have the required permissions to view the files attached to this post.