Well, rocommunity public just sets the community public to be read only
to anything. However, public is just a name, it could be anything. Read
only is fairly safe for the servers, it's the info "leak" possibility.
You could restrict it further, but that gets further into SNMP
configuration that I've gone. On Windows, it's easy to just list the IPs
that the server will accept SNMP packets from.
SSH tools is a package of scripts, I think, from ZenOSS. You need them
to monitor Daemons on Linux, you can do IP services (HTTP etc - exposed
ports as far as I can tell) out of the box, but if you want to know if
some process that doesn't expose a port is running I think you'll need
the scripts. Or more SNMP magic that I don't know.
SNMP gets you performance monitoring on Linux, Network use, and IP
services (HTTP, DSN, Etc) monitoring.
SNMP gets you the same minus performance (CPU/RAM use) on Windows.
Installing Informant on Windows gets you the CPU info, and WMI gets you
the service monitoring and event log monitoring.
I'm not really sure how you set up syslog on Linux to post the messages
to ZenOSS, but you can do that.
I'm just a user that's been messing about with ZenOSS 1.x and now 2.x
for a few months sharing what I've learned.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
prodjtech wrote:
jmp242 at mail.lepp.co... wrote:
Well, first, CENTOS5 for the ZenOSS server might be a pain as it
defaults IIRC to Python 2.5, which just doesn't work for the framework
ZenOSS uses.
Your best bet is to use CentOS4 if possible as then it will "just work".
This just for the ZenOSS server. The Important thing is Python 2.4.
Then you need the provided ZenOSS - deps rpms, ZenOSS rpm, and IME with
EL4, net-snmp + net-snmp utils from the base package.
ZenOSS installs ZOPE for it's own webserver @ port 8080.
Thanks for the tip w/ CentOS 4. :)
jmp242 at mail.lepp.co... wrote:
The Client servers will need SNMP configured properly. If you're firewalled off
SNMP from the internet, then rocommunity public is easiest.
For Linux servers, you may also want the SSH tools available (I don't
have any experience with those). For Windows, you'll want SNMP
Informant, and a Domain Admin account for WMI access.
I have no idea regarding Ensim Pro however.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
Ok, so if I understand correctly, if we run SNMP across a private network, we can use
"rocommunity public" in an SNMP config file to get things going (I presume
"rocommunity public" leaves things wide open.)?
As far as SSH tools for Linux, I know we have SSH installed on all the servers. Is this
what you're referring to, or is there a package called "SSH Tools"?
I don't know about ensim either at this point, but if all we need is to configure SNMP on
the web/email servers, (no additional packages/reconfiguration), I'd be willing to bet
that I'm in the clear here. Can you confirm that SNMP is the only change required to the
"client" servers?
Thanks again, James. You are really helping me out immensely. Are you
associated with the ZenOSS project or just an avid user?
------------------------
Dwight Porter
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9121#9121
-------------------- 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
