The simplest way to install Zenoss Core 4.2 on a newly-deployed RHEL/CentOS 64-bit 5/6 system is to use our auto-deploy script, which downloads all required files for you. To use the script, first set up a new server running one of our supported operating systems. Then, as root, run the following commands:
# wget https://github.com/zenoss/core-autodeploy/tarball/4.2.5 -O auto.tar.gz
# tar xvf auto.tar.gz
# cd zenoss-core-autodeploy-*
Now, you have the option of editing zenpack_actions.txt, which defines all ZenPacks that will be installed by default (all Core ZenPacks). If you would like to avoid installing certain ZenPacks, then remove the corresponding lines from this file and save it.
Now you are ready to install Zenoss Core 4.2.5:
# ./core-autodeploy.sh #do not use ''tee'' or similar, /opt/zenoss/log/install.log will be created by the script.
Minimal Hardware Requirements:
Small Deployments (1 to 250 Monitored Devices)
- 4GB RAM
- 2 CPU Cores
- 1x 300GB, 10K RPM Drive
Medium Deployments (250 to 500 Monitored Devices)
- 8GB RAM
- 4 CPU Cores
- 1x 300GB, 10K RPM Drive
Large Deployments (500 to 1000 Monitored Devices)
- 16GB – 32GB RAM
- 8 CPU Cores
- 1x 300GB, 15K RPM Drive
Disable SELinux and IPtables
For this guide SELinux and IPtables were completely disabled and CentOS 6 was up-to-date!
Add DNS FQDN Entry and NTP Sync
To ensure proper resolving FQDN entries in DNS or /etc/hosts must exist and please configure NTP time synchronization for services to run properly. Continue reading “Install Zenoss on CentOS 6 64bit” »
Allow ICMP Through Firewall
Firstly you need to allow incoming ICMP ping request since this is the way Zenoss checks if the system is online.
Server Manager -> Configuration -> Windows Firewall with Advanced Security -> Inbound Rules
Do the following:
Enable rule “File and Printer Sharing (Echo Request – ICMPv4-In)”. Continue reading “Add windows client to zenoss monitoring” »
Good system administrator should know that they need to do these 3 most important things after delivering a server:
As part of monitoring task, in this tutorial, I am going to show on how to build a centralized monitoring system using Zenoss. Zenoss will need to use SNMP agent in every server that need to be monitored. If you have high number of servers, you should use Zenoss instead of Cacti or Nagios because it is easier to setup and maintain. The web-based management portal is really easy to understand and you can monitor a lot of things, not limited to SNMP MIB reporting only.
Zenoss has the community version which is free. The latest version of Zenoss at this date is version 4. Zenoss installer recommending user to use a clean server. But in my case, I will use a cPanel server which really not heavy in usage for this purpose. In order to run Zenoss in ‘not-so-clean’ server, I need to use Zenoss stack version 3. I will be using following variables:
OS: RHEL 5.3 64bit (Tikanga)
cPanel: 11.32.3 (build 23)
Zenoss server IP: 188.8.131.52
Server to be monitored: 184.108.40.206 and 220.127.116.11 Continue reading “Install and Configure Zenoss as Centralized Monitoring System” »