This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
networking:monitoring:zabbix_host [2015/08/27 17:37] jcooper |
networking:monitoring:zabbix_host [2015/12/29 11:30] (current) gcooper |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Zabbix NMS Host ====== | ====== Zabbix NMS Host ====== | ||
+ | |||
+ | See also **[[networking: | ||
**Home**: http:// | **Home**: http:// | ||
Line 14: | Line 16: | ||
**HowTo - Agent**: http:// | **HowTo - Agent**: http:// | ||
- | |||
- | See also **[[networking: | ||
===== Add a Host to Monitor ===== | ===== Add a Host to Monitor ===== | ||
Line 25: | Line 25: | ||
===== Customize Trigger ===== | ===== Customize Trigger ===== | ||
- | Zabbix communications are all **TCP** based by default. They are configurable in the '' | + | https://www.zabbix.com/ |
- | :!: If you change the port in the '' | + | Use Case: You have a monitored device on a circuit that is having issues. |
- | ^ Port ^ Note ^ | + | * Clone the template with the problem alert. |
- | |162 |For Server, SNMP, Server Inbound | + | * Remove original template and attach new cloned template. |
- | |161 |For Server, SNMP, Server Outbound | + | |
- | |10050 | + | |
- | |10051 | + | |
- | :!: The server runs an agent too, so we allow both. | + | Clone Template |
- | + | ||
- | ==== IPtables Firewall ==== | + | |
- | + | ||
- | === Server === | + | |
- | + | ||
- | < | + | |
- | vim / | + | |
- | + | ||
- | -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 | + | |
- | </ | + | |
- | + | ||
- | === Agent === | + | |
- | + | ||
- | < | + | |
- | vim / | + | |
- | + | ||
- | -A INPUT -m state --state NEW -m tcp -p tcp --dport 10050 -j ACCEPT | + | |
- | </ | + | |
- | + | ||
- | < | + | |
- | service iptables restart | + | |
- | </ | + | |
- | + | ||
- | ==== CSF Firewall ==== | + | |
- | + | ||
- | === Zabbix Server === | + | |
- | + | ||
- | === Zabbix Agent === | + | |
- | + | ||
- | == csf.allow == | + | |
- | + | ||
- | < | + | |
- | tcp|in|d=10050|s=10.10.1.100 | + | |
- | tcp|out|d=10051|d=10.10.1.100 | + | |
- | </ | + | |
- | + | ||
- | ===== Agents ===== | + | |
- | + | ||
- | <note important> | + | |
- | + | ||
- | <note tip>If you have multiple monitored hosts behind a remote NAT firewall, you must use Active mode on the agent or (on the remote NAT firewall device) forward additional ports (10051, etc.) in to port 10050 of the additional monitored hosts and adjust the ports defined for the additional monitored hosts in the Zabbix web interface.</ | + | |
- | + | ||
- | ==== Active Agents ==== | + | |
- | + | ||
- | https:// | + | |
- | + | ||
- | * 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 '' | + | |
- | * All '' | + | |
- | * Generally by cloning templates | + | |
- | * See link above | + | |
- | * The configuration file is slightly different | + | |
- | * Set '' | + | |
- | + | ||
- | ==== Install Agents ==== | + | |
- | + | ||
- | :!: Install the '' | + | |
- | + | ||
- | <note important> | + | |
- | + | ||
- | Modify the agent configuration file: | + | |
- | + | ||
- | < | + | |
- | vim / | + | |
- | + | ||
- | Server=< | + | |
- | # | + | |
- | Hostname=< | + | |
- | </ | + | |
- | + | ||
- | 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 | + | |
- | </ | + | |
- | + | ||
- | === Windows === | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | Download and extract the Windows agent to '' | + | |
- | + | ||
- | :!: You can use '' | + | |
- | + | ||
- | Edit '' | + | |
- | + | ||
- | < | + | |
- | Server=< | + | |
- | # | + | |
- | Hostname=< | + | |
- | </ | + | |
- | + | ||
- | In an administrative (elevated) command prompt (not PowerShell): | + | |
- | + | ||
- | < | + | |
- | cd C: | + | |
- | .\zabbix_agentd.exe --config C: | + | |
- | net start " | + | |
- | sc config " | + | |
- | netsh advfirewall firewall add rule name=" | + | |
- | </ | + | |
- | + | ||
- | === Ubuntu === | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | === CentOS === | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | == CentOS 5 x86 == | + | |
- | + | ||
- | < | + | |
- | rpm -Uvh http:// | + | |
- | yum install zabbix zabbix-agent | + | |
- | </ | + | |
- | + | ||
- | == CentOS 6 x64 == | + | |
- | + | ||
- | < | + | |
- | rpm -Uvh http:// | + | |
- | yum install zabbix zabbix-agent | + | |
- | </ | + | |
- | + | ||
- | :!: Modify the firewall, edit the config file then start the agent service. | + | |
- | + | ||
- | === SME Server === | + | |
- | + | ||
- | == SME 9 x64 (CentOS 6 Base) == | + | |
- | + | ||
- | < | + | |
- | config set zabbix-agent service TCPPort 10050 access public status enabled | + | |
- | signal-event remoteaccess-update | + | |
- | + | ||
- | rpm -Uvh http:// | + | |
- | mv / | + | |
- | + | ||
- | yum install zabbix zabbix-agent | + | |
- | + | ||
- | chkconfig zabbix-agent on | + | |
- | + | ||
- | / | + | |
- | </ | + | |
- | + | ||
- | <note important> | + | |
- | + | ||
- | < | + | |
- | vim / | + | |
- | + | ||
- | / | + | |
- | </ | + | |
- | + | ||
- | == SME 8 x64 (CentOS 5 Base) == | + | |
- | + | ||
- | < | + | |
- | config set zabbix-agent service TCPPort 10050 access public status enabled | + | |
- | signal-event remoteaccess-update | + | |
- | + | ||
- | rpm -Uvh http:// | + | |
- | mv / | + | |
- | + | ||
- | yum install zabbix zabbix-agent | + | |
- | + | ||
- | chkconfig zabbix-agent on | + | |
- | ln -s / | + | |
- | + | ||
- | service zabbix-agent start | + | |
- | </ | + | |
- | + | ||
- | ===== Add a Host to Monitor ===== | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | https:// | + | |
- | ==== SNMP ==== | + | - Configuration -> Templates |
+ | - Click on Template with problem Trigger | ||
+ | - Click '' | ||
+ | - Append text to name to be descriptive and list next to original | ||
- | http:// | + | Remove Template and replace with clone |
- | | + | |
- | | + | |
- | * Will show more info | + | |
- | | + | |
- | | + | - Click '' |
- | * Like a password | + | |
- | * Defined with macro '' | + | |
- | === Test Access === | + | https:// |
- | :!: '' | + | Create/ |
- | < | + | :!: IE: Circuit is flaky, you know it and fix is down the road. " |
- | snmpwalk -v 2c -c < | + | |
- | </ | + | |
- | === Add Host === | + | - Configuration -> Host -> Triggers (on problem host) |
+ | - Disable " | ||
+ | - Rename Problem Trigger -> Edit expression and Description Click '' | ||
+ | - Enable new Trigger | ||
- | :!: Set the SNMP community string (like a password) for each host by adding a **macro** '' | ||
- | {{ :: | ||
- | ===== Troubleshooting ===== | + | ==== Trigger Dependencies |
- | This test should connect, then close when you hit < | + | https:// |
- | < | + | Sometimes the availability |
- | telnet < | + | |
- | </ | + | |
- | ===== Zimbra ===== | ||
- | https:// |