Well, the Admin Guide will help as will the Wikis. In general, you only
need read access to SNMP, and you could of course block that from the
net at your router. You could also use SNMP v3 with much stronger
security (though more complex to set up). I'm not actually aware of
Zenoss (currentyl) doing SNMP write even as an option.
You can, of course, in your snmpd.conf or whatever you're using to
configure SNMP limit access to read only, set a community (sort of a
password) *and* limit responses to a specific IP, that of your Zenoss
server. This would likely be "secure enough" on a LAN.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
Digitante wrote:
I had never previously attempted to set up network monitoring, so I was not
even aware of SNMP's existence before I attempted to install ZenOSS.
SNMP is of course, widely available, and it has its own set of configuration
utilities. Which raises some confusion, because ZenOSS apparently replaces some
of these, while requiring others to be already handled.
For example, it may be that I can configure SNMP servers remotely using ZenOSS,
but some minimal configuration must be done in order for those servers to
respond to ZenOSS.
Furthermore, SNMP obviously carries security risks, though I haven't enough
understanding of it to be certain I've considered them all.
So, just how much SNMP do I need to have installed and configured using my
distribution's tools (Debian in my case), before I can get full functionality
from ZenOSS?
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=22101#22101
-------------------- m2f --------------------
_______________________________________________
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
