This apparently is because these errors were always present but were only recently "revealed" to the user - they're reappearing after every remodeling. Use the search function and you'll find several similar threads - basically it comes down to having to setup new device templates that are named exactly the same as the "type" of interface you are monitoring that do not contain the bad oids zenoss is complaining about.
Basically, to do this: Under classes go to "devices" and then the templates tab Put a check next to ethernetcsmacd Choose "copy templates" and choose / as the location (or wherever appropriate) click on the "copy of" template and rename it *exactly* the type if interface you're getting the reports on and click save remove the oids you are getting "bad" reports on profit (ok, sorry, couldn't resist) That has worked for about half a dozen interface types I'm monitoring - to accelerate the reappearance of the errors, just remodel the device. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=18230#18230 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
