qubit wrote:
> The Method 'Test Against Device' is running fine but when the template is
> bound against a device we receive the following message ;(
>
>
> Code:
>
> 2009-03-02 16:20:44 ERROR zen.zenperfsnmp: invalid literal for int():
> NET-SNMP-EXTEND-MIB::nsExtendOutputFull
> Traceback (most recent call last):
> File "/usr/local/zenoss/zenoss/Products/ZenRRD/zenperfsnmp.py", line 134,
> in checkException
> return function(*args, **kw)
> File
> "/usr/local/zenoss/python/lib/python2.4/site-packages/pynetsnmp/twistedsnmp.py",
> line 235, in get
> oids = [asOid(oidStr) for oidStr in oidStrs]
> File
> "/usr/local/zenoss/python/lib/python2.4/site-packages/pynetsnmp/twistedsnmp.py",
> line 103, in asOid
> return tuple([int(x) for x in oidStr.strip('.').split('.')])
> ValueError: invalid literal for int(): NET-SNMP-EXTEND-MIB::nsExtendOutputFull
> 2009-03-02 16:20:44 WARNING zen.zenperfsnmp: Failed to collect on HOSTNAME
> (exceptions.ValueError: invalid literal for int():
> NET-SNMP-EXTEND-MIB::nsExtendOutputFull)
>
>
>
>
> Regards Daniel
Daniel, there is a simpler solution to accomplish what you want. You simply
need the numeric OID for your custom parameter.
You can find this using snmpwalk. Add the " -On" switch to snmpwalk to see the
numeric OID and you can use this OID with Zenoss.
Code:
snmpwalk -On -v1 -cpublic localhost
'NET-SNMP-EXTEND-MIB__::nsExtendOutput1Line__."datecheck"'
something like that should produce:
Code:
.1.3.6.1.4.1.8072.1.3.2.3.1.1.17.104.102.97.120.109.111.100.101.109.115.115.101
= STRING: <blah>
but at least you'll have an OID that's compatible with Zenoss.
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=32124#32124
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
