Richard,
You can overload the template (ie put a super set of values in it)
zenperfsnmp will prune out any missing OIDs. This is not the most
efficient mode for zenperfsnmp but it will save you some
configuration effort. We need to think about other ways solve this
issue possibly by allowing multiple templates to be bound to an object.
-EAD
On Sep 7, 2006, at 9:47 AM, rpalmer wrote:
Hi Erik,
On Thu, Sep 07, 2006 at 09:15:49AM -0400, Erik A. Dahl wrote:
Richard,
Just the closest Device template is bound to the device. I'm
guessing the template is currently attached to /Device/Server/Linux.
You can add them to that template or create a new sub class for the
changes. You can also make a local template on any given device.
Will this not start leading to some complex /Device trees though ?.
E.g
if we have all dell boxes, some with temp probes and some with raid
cards
I would need to create this device tree for correct monitoring:
/Device/Server/Linux/Dell/
/Device/Server/Linux/Dell/Temp
/Device/Server/Linux/Dell/Raid/
/Device/Server/Linux/Dell/Raid/Temp
and so on for all permutations of our hardware. Or is the idea that
this will be handled in plugins in the future so their will be
little need
for device subclassing ?.
regards,
Richard.
--
Richard Palmer
Systems Administration Officer / Centre for Computing in the
Humanities
King's College London / Arts & Humanities Data Service
Tel: 0207 848 1973 / 1936
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
