Home: http://www.zabbix.com/

Downloads: http://www.zabbix.com/download.php

Documentation: https://www.zabbix.com/documentation/2.4/manual/installation/requirements

Wiki: http://www.zabbix.org/wiki

Forums: https://www.zabbix.com/forum/

HowTo - Server: http://tecadmin.net/install-zabbix-on-ubuntu/

HowTo - Agent: http://tecadmin.net/install-zabbix-agent-on-centos-rhel/

See also zabbix

http://tecadmin.net/add-host-zabbix-server-monitor/

https://www.zabbix.com/documentation/2.4/manual/config/hosts/host

https://www.zabbix.com/forum/showthread.php?t=19921

Use Case: You have a monitored device on a circuit that is having issues. Rather than have constant alerts due to packet loss etc. modify the alert to minimize the churning until the circuit can be stabilized then return to the stock template.

• Clone the template with the problem alert. Use “Full Clone” to take advantage of the previous configuration.

https://www.zabbix.com/documentation/2.4/manual/config/templates/template

• Clone the problem alert

https://www.zabbix.com/documentation/2.4/manual/config/triggers/dependencies

Sometimes the availability of one host depends on another. A server that is behind some router will become unreachable if the router goes down. With triggers configured for both, you might get notifications about two hosts down - while only the router was the guilty party.

vim /etc/sysconfig/iptables

-A INPUT -p udp -m udp --dport 162 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 10051 -j ACCEPT

vim /etc/sysconfig/iptables

-A INPUT -m state --state NEW -m tcp -p tcp --dport 10050 -j ACCEPT

service iptables restart

tcp|in|d=10050|s=10.10.1.100   # From Zabbix Server
tcp|out|d=10051|d=10.10.1.100  # To Zabbix Server

https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:os:zabbix

• Active agents initiate all communications to server
• No port forwarding required at client
• Multiple monitored hosts behind remote NAT firewall
• Lower resource utilization on server
• Modify the host on server
  • IP address must be set to 0.0.0.0
  • All Items must be configured as Zabbix Agent (active)
    • Generally by cloning templates
      • See link above
• The configuration file is slightly different
  • Set ServerActive to the IP address of the Zabbix server

Install the zabbix-agent on the Zabbix server as well.

Modify the agent configuration file:

vim /etc/zabbix/zabbix_agentd.conf

Server=<Zabbix Server IP>
#ServerActive=127.0.0.1
Hostname=<Monitored Host ID>

Configure the agent to auto-start, start the service and check the firewall:

chkconfig zabbix-agent on
service zabbix-agent start

ps ax|grep zabbix
netstat -tapn|grep 1005
iptables -nL |grep 1005

http://tecadmin.net/install-zabbix-agent-windows-system/

http://www.zabbix.com/downloads/2.4.4/zabbix_agents_2.4.4.win.zip

Download and extract the Windows agent to C:\Support.

You can use Wordpad as the editor, but turn word-wrap off. Use Notepad thereafter.

Edit C:\Support\zabbix_agents_2.4.4.win\conf\zabbix_agentd.win.conf:

Server=<Zabbix Server IP>
#ServerActive=127.0.0.1
Hostname=<exact-Zabbix-host-name>

In an administrative (elevated) command prompt (not PowerShell):

cd C:\Support\zabbix_agents_2.4.4.win\bin\win64
.\zabbix_agentd.exe --config C:\support\zabbix_agents_2.4.4.win\conf\zabbix_agentd.win.conf --install
net start "Zabbix Agent"
sc config "Zabbix Agent" start= auto
netsh advfirewall firewall add rule name="Zabbix Agent" dir=in action=allow protocol=TCP localport=10050

http://tecadmin.net/install-zabbix-agent-on-ubuntu-and-debian/

http://tecadmin.net/install-zabbix-agent-on-centos-rhel/

rpm -Uvh http://repo.zabbix.com/zabbix/2.4/rhel/5/i386/zabbix-release-2.4-1.el5.noarch.rpm
yum install zabbix zabbix-agent

rpm -Uvh http://repo.zabbix.com/zabbix/2.4/rhel/6/x86_64/zabbix-release-2.4-1.el6.noarch.rpm
yum install zabbix zabbix-agent

Modify the firewall, edit the config file then start the agent service.

config set zabbix-agent service TCPPort 10050 access public status enabled
signal-event remoteaccess-update

rpm -Uvh http://repo.zabbix.com/zabbix/2.4/rhel/6/x86_64/zabbix-release-2.4-1.el6.noarch.rpm
mv /etc/yum.repos.d/zabbix.repo /etc/yum.smerepos.d/

yum install zabbix zabbix-agent

chkconfig zabbix-agent on

/etc/init.d/zabbix-agent start

vim /etc/rc.local

/etc/rc4.d/S86zabbix-agent start

config set zabbix-agent service TCPPort 10050 access public status enabled
signal-event remoteaccess-update

rpm -Uvh http://repo.zabbix.com/zabbix/2.4/rhel/5/x86_64/zabbix-release-2.4-1.el5.noarch.rpm
mv /etc/yum.repos.d/zabbix.repo /etc/yum.smerepos.d/

yum install zabbix zabbix-agent

chkconfig zabbix-agent on
ln -s /etc/rc.d/init.d/zabbix-agent /etc/rc7.d/S87zabbix-agent

service zabbix-agent start

http://tecadmin.net/add-host-zabbix-server-monitor/

https://www.zabbix.com/documentation/2.4/manual/config/hosts/host

http://www.zabbix.org/wiki/Start_with_SNMP_traps_in_Zabbix

• Listening port is usually 161/UDP
• Use SNMP version 2c if possible
  • Will show more info
• Template SNMP Device will often suffice
• Set the community string per host
  • Like a password
  • Defined with macro {$SNMP_COMMUNITY}

2c is SNMP version.

snmpwalk -v 2c -c <community> <remoteIP> .

Set the SNMP community string (like a password) for each host by adding a macro {$SNMP_COMMUNITY} with the value being the community string for the host to be monitored.

This test should connect, then close when you hit <enter>:

telnet <IP of agent> 10050

https://github.com/YetOpen/zabbix-scripts/tree/master/zabbix-zimbra