I'm pretty sure you can only have one threshold per class, but you can
write a script that snmp gets or snmp walks the OID of choice, and then
have it write a file with the value, check if it changes and then if it
does return bad...
Just a really quick rough non tested example:
command line in zenoss:
yourscriptname {dev/manageip}
script:
oldvalue = `cat $1`
newvalue=`snmpwalk -v 1 -c public $1 OID | awk '{ print $4}'`
echo $newvalue > $1
if [ $oldvalue = $newvalue ]
then
echo "OK|Value="$newvalue
else
echo "Warning|Value="$newvalue
fi
Note - here I'm doing string compare because it's simpler, if you do
want to do math, you need to do it differently. You'd stuff this in a
command datasource, and you could graph this if you wanted by naming the
datapoint Value...
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
breto wrote, On 12/18/2008 3:37 PM:
> Can you explain or have some code examples... I'm still pretty new to Zenoss.
>
> I didn't know if it would be possible to do with with a threshold but had one
> threshold applied to the primary and a different threshold to the backup.
>
> Bret
>
>
>
>
> -------------------- m2f --------------------
>
> Read this topic online here:
> http://forums.zenoss.com/viewtopic.php?p=29330#29330
>
> -------------------- m2f --------------------
>
>
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users