Actually, this isn't working for some reason - I've created new templates for the types that were an issue, and they have been applied (automatically in most cases), but for some reason when zenoss is restarted, I get a huge pile of blue alerts listing bad oids that aren't even included in the profile any longer.
For example .1q-vlans - I've created a new profile for these, removed both .1.3.6.1.2.1.2.2.1.20 and .1.3.6.1.2.1.2.2.1.14 from the data sources and have removed the errors graph from that interface type. I have verified that this template is applied to all my ethernet vlans. Now, whenever zenoss is restarted, I get the old familiar > Error reading value for "FastEthernet0/0.299-802.1Q vLAN subif" on ar1 (oid > .1.3.6.1.2.1.2.2.1.14.979 is bad) and > Error reading value for "FastEthernet0/0.299-802.1Q vLAN subif" on ar1 (oid > .1.3.6.1.2.1.2.2.1.20.979 is bad) event alerts. As far as I understand it, these OIDs simply should not be queried for these interfaces. Something changed in 2.1.3 that shouldn't have. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17590#17590 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
