On 8/15/07 4:45 PM, "Geoff Franks" <[EMAIL PROTECTED]> wrote:
> I just found these in zenhub.log:
>
> Traceback (most recent call last):
> File "/usr/local/zenoss/Products/ZenModel/PerformanceConf.py", line 188,
> in getDevices
> except:
> File "/usr/local/zenoss/Products/ZenModel/Device.py", line 498, in
> getSnmpOidTargets
> oids.extend(o.getSnmpOidTargets())
> File "/usr/local/zenoss/Products/ZenModel/RRDView.py", line 284, in
> getSnmpOidTargets
> for ds in templ.getRRDDataSources("SNMP"):
> File "/usr/local/zenoss/Products/ZenModel/RRDView.py", line 263, in
> getThresholds
> for thresh in templ.thresholds():
> AttributeError: thresholds
>
Well, I finally tracked it down. Apparently all my cisco devices are
advertising an interface called "Null0." On the device, it says hardware
unknown. Zenoss interprets this as "Other" and when it fails to find a
template for the interface of type "other," it crashes ALL performance
metrics for the device, rather than just for the one interface.
Additionally, no warnings, or info, or debug events are thrown for the
device. I remember having the propVirtual interface type throw errors when
zenoss didn't know about its metrics back in 1.x. Is this a new bug in 2.x?
Geoff Franks
Sr. Systems Administrator
Hauptman Woodward Institute
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
