I can understand you "x" ing iut your device that you are testing but showing is the OID would be very helpful.  The trick with getting your OID correct, and whether you have a .0 on the end or not, is to do with the structure of SNMP data.

Scalar data, like stuff from the system table of MIB-2, provides single values for each OID - like your sysUpTime example.  When you create templates to gather such variables, you must have the .0 on the end. 

Some SNMP data, by its nature, provides a table of values.  Interfaces is an obvious example.  For EACH interface, you will get ifInOctets, ifOutOctets, .... etc . In this case, a Zenoss template should not supply a .0 at the end of the oid and the Zenoss SNMP collector will automatically supply the table index and the table of values for each interface.

Not sure why you are maybe trying to setup an snmpwalk under $ZENHOME/libexec??  Just use the standard system snmpwalk.  If you are trying to use snmpwalk in a command template (which occasionally is useful but normally necessary) then use the full path to snmpwalk in your command path - otherwise the command path will default to $ZENHOME/libexec.

Hope that hekps some.  If not, publish yout snmpwalk command with the OIDs you are using and we can have another look.

Cheers,

Jane

Why are you creating a command data source for this rather than using an SNMP data source??? An SNMP template will automatically handle all the different instances and will create you your datapoint automatically - one datapoint for each OID.  The only reason that I use snmpwalk in a command template, rather than using a native SNMP data source, is if I want a polling interval faster than 5 minutes - but your command polling interval is 300 = 5 mins.

I would strongly suggest that you create a new Data SOURCE of type SNMP and use your OID, without the .0 if you are gathering a table of values.  This will automatically create a data point that you can add to your THresholds / Graphs.

Cheers,

Jane