---

Subject:	ZENOSS 4.2
Author:	John Boyle
Posted:	2017-01-31 15:09

Kingston,

Zach will be helping you with your questions shortly. Thanks for posting!

JB

John Boyle

Zenoss Community Engineer/Manager

jboyle@zenoss.com

Twitter: @BrandFlair

---

Subject:	Installing Zenoss per-se does
Author:	Jane Curry
Posted:	2017-01-31 15:46

Installing Zenoss per-se does not actually configure the snmp agent although the net-snmp package should have been installed. You don't say what platform you are working on Certainly some RedHat / CentOS builds tend to ship a very restricted default agent configuration in the snmpd.conf file which ONLY responds to queries to the SNMP MIb-2 system table - which, frankly, doesn't get you anything much very useful.

You need to configure both the Zenoss manager and each of your SNMP agents to use the "correct" community name. The default for prettty-well every type of SNMP agent is public and this is also the default that Zenoss will use.

Have you had a look at the Zenoss Admin Guide It does seem to have a temporary problem on the website but if you send me a direct email, I can send you a copy of the 4.2.5 Admin Guide - there are some helpful sections in there about SNMP monitoring.

I would start by checking / modifying the snmpd.conf agent config file on your Zenoss server (often in /etc/snmp - but it depends on your OS architecture); make sure it responds to a community of public from all devices initially. Then make sure that your Zenoss server is discovered as a device under the /Server/Linux device class; if it already exists in a different class, simply drag it on the GUI list of devices to the /Server/Linux class. That will ensure that it uses suitable SNMP modeler plugins to discover configuration details (like interfaces and filesystems) and will also ensure that regular SNMP performance data is collected. Make sure you remodel your device - from the Action icon (the "gear" symbol at the bottom left when you are looking at details of a device) choose "ReModel device" - that forces Zenoss to go and rediscover configuration details for that device. Once you have a successful model, performance data is typically gathered every 5 minutes - it can take 2 cycle times before you start to see data in the graphs.

When you have that working, then you can start tightening up your SNMP agent config, using a better community name and more restrictive access rights, if you want to. You can also expand to other devices.

Use the command-line snmpwalk utility from the Zenoss server, to do basic SNMP connectivity tests.

Cheers,

Jane

Email: jane.curry@skills-1st.co.uk    Web: https://www.skills-1st.co.uk

---

Subject:	The links to "recent" Zenoss
Author:	Jane Curry
Posted:	2017-02-01 15:02

The links to "recent" Zenoss documentation has now been fixed. Look here b for all 4.2.5 documentation.

Cheers,

Jane

Email: jane.curry@skills-1st.co.uk    Web: https://www.skills-1st.co.uk