Zabbix Documentation 5.0

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:appliance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:appliance [2017/09/18 08:08]
martins-v updating version numbers
manual:appliance [2020/05/21 10:17] (current)
yuriii [1.1 Repositories] replaced 4.5 with 5.0 in zabbix repo url
Line 3: Line 3:
 === Overview === === Overview ===
  
-As an alternative to setting up manually or reusing an existing server for Zabbix, users may [[http://​www.zabbix.com/​download.php#​appliance|download]] a Zabbix appliance or Zabbix appliance installation CD image. Zabbix appliance installation CD could be used for instant deployment of Zabbix server (MySQL), Zabbix server (PostgreSQL),​ Zabbix proxy (MySQL) and Zabbix proxy (SQLite 3).+As an alternative to setting up manually or reusing an existing server for Zabbix, users may [[http://​www.zabbix.com/​download_appliance|download]] a Zabbix appliance or Zabbix appliance installation CD image. ​
  
-Zabbix Appliance virtual machines have prepared Zabbix server with MySQL support. It is built using Zabbix appliance installation CD.+Zabbix appliance ​and installation CD versions are based upon the following OS:  
 +^Zabbix appliance version^OS^ 
 +|5.0.0|CentOS 8 (x86_64) ​ |
  
-|{{:manual:installation_cd_boot_menu.png?​600|}}|+Zabbix appliance installation CD can be used for instant deployment of Zabbix server (MySQL). 
 + 
 +== System requirements:​ == 
 +  * //RAM//: 1.5 GB 
 +  * //Disk space//: at least 8 GB should be allocated for the virtual machine. 
 + 
 +|{{:manual:installation_cd_boot_menu1.png?​600|}}|
 |Zabbix installation CD/DVD boot menu| |Zabbix installation CD/DVD boot menu|
  
-|{{:​manual:​appliance_boot.png?​600|}}| 
-|Booting Zabbix appliance| 
  
-Zabbix appliance and installation CD versions are based upon the following Ubuntu versions:  +Zabbix appliance ​contains a Zabbix server (configured ​and running on MySQL) and a frontend.
-^Zabbix appliance version^Ubuntu version^ +
-|3.4.0|14.04.3  |+
  
-Zabbix appliance is available in the following formats:+Zabbix ​virtual ​appliance is available in the following formats:
  
-  * vmdk (VMware/​Virtualbox+  * VMWare ​(.vmx
-  * OVF (Open Virtualisation Format+  * Open virtualization format (.ovf
-  * KVM +  * Microsoft Hyper-V 2012 (.vhdx) 
-  * HDD/flash image, USB stick +  * Microsoft Hyper-V 2008 (.vhd) 
-  * Live CD/DVD +  * KVM, Parallels, QEMU, USB stick, VirtualBox, ​Xen (.raw
-  * Xen guest +  * KVM, QEMU (.qcow2)
-  * Microsoft VHD (Azure+
-  * Microsoft VHD (Hyper-V)+
  
-To get started, boot the appliance and point your browser at the IP it has received over DHCP<nowiki>http://<​host_ip>/​zabbix</nowiki>+To get started, boot the appliance and point browser at the IP the appliance ​has received over DHCP.  
 +<note importantDHCP must be enabled on the host. </note>
  
-It has Zabbix server configured and running on MySQL, as well as frontend available.+To get the IP address from inside the virtual machine run: 
 +  ip addr show
  
-The appliance has been built using standard Ubuntu/Debian feature called Preseed files.+To access Zabbix frontend, go to **<​nowiki>​http:​//<​host_ip></​nowiki>​** (for access from the host's browser bridged mode should be enabled in the VM network settings)
  
-=== - Changes to Ubuntu ​configuration ===+<note tip>If the appliance fails to start up in Hyper-V, you may want to press ''​Ctrl+Alt+F2''​ to switch tty sessions.</​note>​ 
 +=== - Changes to CentOS 8 configuration ===
  
-There are some changes applied to the base Ubuntu ​configuration.+The appliance is based on CentOS 8. There are some changes applied to the base CentOS ​configuration.
  
 == - Repositories == == - Repositories ==
  
-Official Zabbix [[manual:​installation:​install_from_packages#​debianubuntu|repository]] has been added to ///etc/apt/sources.list//: +Official Zabbix [[manual:​installation:​install_from_packages/​rhel_centos|repository]] has been added to ///etc/yum.repos.d//: 
-  ​## Zabbix ​repository +  ​[zabbix] 
-  ​deb http://​repo.zabbix.com/​zabbix/​3.4/ubuntu trusty main +  name=Zabbix ​Official Repository - $basearch 
-  ​deb-src http://repo.zabbix.com/zabbix/3.4/ubuntu trusty main +  ​baseurl=http://​repo.zabbix.com/​zabbix/​5.0/​rhel/​8/​$basearch
-  +  ​enabled=1 
 +  gpgcheck=1 
 +  gpgkey=file:///etc/pki/rpm-gpg/​RPM-GPG-KEY-ZABBIX-A14FE591 
 == - Firewall == == - Firewall ==
  
Line 53: Line 61:
   * Opened SNMP trap port (162 UDP);   * Opened SNMP trap port (162 UDP);
   * Opened outgoing connections to NTP port (53 UDP);   * Opened outgoing connections to NTP port (53 UDP);
-  * ICMP pakets ​limited to 5 packets per second;+  * ICMP packets ​limited to 5 packets per second;
   * All other incoming connections are dropped.   * All other incoming connections are dropped.
  
-== - Additional packages == 
- 
-Various basic utilities have been added that could make working with Zabbix and monitoring in general easier: 
-  * iptables-persistent 
-  * mc 
-  * htop 
-  * snmptrapfmt 
-  * snmp-mibs-downloader 
- 
-Some of these packages are used by Zabbix, some of them are installed to help users to configure/​manage appliance settings. 
  
 == - Using a static IP address == == - Using a static IP address ==
Line 72: Line 70:
  
   * Log in as root user;   * Log in as root user;
-  * Open file ///​etc/​network/​interfaces// in your favourite editor+  * Open ///etc/sysconfig/network-scripts/ifcfg-eth0// file
-  * //iface eth0 inet dhcp// ​-> //iface eth0 inet static// +  * Replace ​//BOOTPROTO=dhcp// ​with //BOOTPROTO=none// 
-  * Add the following lines after //iface eth0 inet static//+  * Add the following lines: 
-    * //address ​<IP address of the appliance>//​ +    * //IPADDR=<IP address of the appliance>//​ 
-    * //netmask ​<network mask>// +    * //PREFIX=<CIDR prefix>// 
-    * //gateway ​<your gateway address>//​ +    * //GATEWAY=<​gateway ​IP address>//​ 
-  Run the commands **sudo ifdown eth0 && sudo ifup eth0**. +    * //DNS1=<DNS server IP address>// 
- +  ​Run **systemctl restart network** command.
-<​note>​For more information about other possible options see the official Ubuntu [[https://help.ubuntu.com/​lts/​serverguide/​network-configuration.html|documentation]].</note> +
- +
-To configure DNS, add nameserver entries in ///​etc/​resolv.conf//,​ specifying each nameserver on its own line: **nameserver 192.168.1.2**.+
  
 +Consult the official Red Hat [[https://​access.redhat.com/​documentation/​en-us/​red_hat_enterprise_linux/​6/​html/​deployment_guide/​s1-networkscripts-interfaces|documentation]] if needed.
 == - Changing time zone == == - Changing time zone ==
  
Line 90: Line 86:
   cp /​usr/​share/​zoneinfo/​Europe/​Riga /​etc/​localtime   cp /​usr/​share/​zoneinfo/​Europe/​Riga /​etc/​localtime
  
-== - Locale changes == 
  
-The appliance contains a few locale changes: 
-  * Contains languages: //​en_US.UTF-8//,​ //​ru_RU.UTF-8//,​ //​ja_JP.UTF-8//,​ //​cs_CZ.UTF-8//,​ //​ko_KR.UTF-8//,​ //​it_IT.UTF-8//,​\\ //​pt_BR.UTF-8//,​ //​sk_SK.UTF-8//,​ //​uk_UA.UTF-8//,​ //​fr_FR.UTF-8//,​ //​pl.UTF-8//;​ 
-  * Default locale is //​en_US.UTF-8//​. 
  
-These changes are required to support a multilingual Zabbix web-interface. 
- 
-== - Other changes == 
- 
-  * Network is configured to use DHCP to obtain IP address; 
-  * Utility **fping** is set to have permissions 4710 and is owned by group **zabbix** - suid and only allowed to be used by zabbix group; 
-  * ntpd configured to synchronise to the public pool servers: //​ntp.ubuntu.com//;​ 
-  * LVM volume is used with ext4 filesystem. 
-  * "//​UseDNS no//" is added to SSH server configuration file ///​etc/​ssh/​sshd_config//​ to avoid long SSH connection waits; 
-  * Daemon snmpd is disabled using ///​etc/​default/​snmpd//​ configuration file. 
  
 === - Zabbix configuration === === - Zabbix configuration ===
  
-Appliance ​Zabbix setup has the following passwords and other configuration changes:+Zabbix ​appliance ​setup has the following passwords and configuration changes:
  
 == - Credentials (login:​password) == == - Credentials (login:​password) ==
  
 System: System:
-  * appliance:zabbix+  * root:zabbix
  
 +Zabbix frontend:
 +  * Admin:​zabbix
 Database: Database:
   * root:<​random>​   * root:<​random>​
   * zabbix:<​random>​   * zabbix:<​random>​
  
-<​note>​Database passwords are randomly generated during the installation process.\\ Root password is stored ​to /​root/​.my.cnf file, it is not required to input a password under the "​root"​ account.</​note>​ +<​note>​Database passwords are randomly generated during the installation process.\\ Root password is stored ​inside the /​root/​.my.cnf file. It is not required to input a password under the "​root"​ account.</​note>​
- +
-Zabbix frontend: +
-  * Admin:​zabbix+
  
-To change the database user password ​it has to be changed ​in the following locations:+To change the database user password, changes have to be made in the following locations:
   * MySQL;   * MySQL;
   * /​etc/​zabbix/​zabbix_server.conf;​   * /​etc/​zabbix/​zabbix_server.conf;​
   * /​etc/​zabbix/​web/​zabbix.conf.php.   * /​etc/​zabbix/​web/​zabbix.conf.php.
 +
 +<​note>​ Separate users ''​zabbix_srv''​ and ''​zabbix_web''​ are defined for the server and the frontend respectively. </​note>​
  
 == - File locations == == - File locations ==
  
-  * Configuration files are placed ​in **/​etc/​zabbix**. +  * Configuration files are located ​in **/​etc/​zabbix**. 
-  * Zabbix server, proxy and agent logfiles are placed ​in **/​var/​log/​zabbix**. +  * Zabbix server, proxy and agent logfiles are located ​in **/​var/​log/​zabbix**. 
-  * Zabbix frontend is placed ​in **/​usr/​share/​zabbix**. +  * Zabbix frontend is located ​in **/​usr/​share/​zabbix**. 
-  * Home directory for user **zabbix** is **/​var/​lib/​zabbix**.+  * Home directory for the user **zabbix** is **/​var/​lib/​zabbix**.
  
 == - Changes to Zabbix configuration == == - Changes to Zabbix configuration ==
  
-  ​* Server name for Zabbix frontend is set to "​Zabbix Appliance";​ +  * Frontend timezone is set to Europe/Riga (this can be modified in **/etc/php-fpm.d/​zabbix.conf**);​
-  ​* Frontend timezone is set to Europe/Riga (this can be modified in **/etc/apache2/​conf-available/​zabbix.conf**);​ +
- +
-== - Preserving configuration == +
- +
-If you are running a Live CD/DVD version of the appliance or for some other reason cannot have persistent storage, you can create a backup of the whole database, including all configuration and gathered data. +
- +
-To create the backup, run: +
- +
-  sudo mysqldump zabbix | bzip2 -9 > dbdump.bz2 +
- +
-Now you can transfer the **dbdump.bz2** file to another machine. +
- +
-To restore from the backup, transfer it to the appliance and execute: +
- +
-  bzcat dbdump.bz2 | sudo mysql zabbix+
  
-<note important>​Make sure that Zabbix server is stopped while performing the restore.</​note>​ 
  
 === - Frontend access === === - Frontend access ===
  
-Access ​to frontend ​by default ​is allowed from everywhere.+By default, access ​to the frontend is allowed from anywhere.
  
-The frontend can be accessed //​http:​%%//​%%<​host>​/zabbix//.+The frontend can be accessed ​at //​http:​%%//​%%<​host>//​.
  
-This can be customised in **/etc/apache2/conf-available/​zabbix.conf**. ​You have to restart the webserver ​after modifying this file. To do so, log in using SSH as **root** user and execute:+This can be customised in **/etc/nginx/conf.d/​zabbix.conf**. ​Nginx has to be restarted ​after modifying this file. To do so, log in using SSH as **root** user and execute:
  
-  ​service apache2 ​restart+  ​systemctl ​restart ​nginx
  
 === - Firewall === === - Firewall ===
  
-By default, only the ports listed in changes are open. To open additional ports just modify "///​etc/​iptables/​rules.v4//"​ or "///​etc/iptables/rules.v6//" ​files and reload firewall rules:+By default, only the ports listed in the [[#​firewall1configuration| configuration ​changes]] above are open. To open additional portsmodify "///​etc/​sysconfig/​iptables//" ​file and reload firewall rules:
  
-  ​service iptables-persistent ​reload +  ​systemctl ​reload ​iptables
-=== - Monitoring capabilities ===+
  
-Zabbix installation is provided with the support for the following: 
- 
-  * SNMP 
-  * IPMI 
-  * Web monitoring 
-  * VMware monitoring 
-  * Jabber notifications 
-  * EZ Texting notifications 
-  * ODBC 
-  * SSH2 
-  * IPv6 
-  * SNMP Traps 
-  * Zabbix Java Gateway 
- 
-=== - SNMP traps === 
- 
-Zabbix appliance uses //​snmptrapfmt//​ to handle SNMP traps. It is configured to receive all traps from everywhere. 
- 
-Authentication is not required. If you would like to enable authentication,​ you need to change the ///​etc/​snmp/​snmptrapd.conf//​ file and specify required auth settings. 
- 
-All traps are stored in the ///​var/​log/​zabbix/​snmptrapfmt.log//​ file. It is rotated by logrotate before reaching 2GB file size. 
  
 === - Upgrading === === - Upgrading ===
  
-The appliance ​Zabbix packages may be upgraded. To do so, run: +The Zabbix ​appliance ​packages may be upgraded. To do so, run: 
-  ​sudo apt-get --only-upgrade install ​zabbix* +  ​dnf update ​zabbix*
-=== - Naming, init and other scripts ===+
  
-Appropriate init scripts are provided. To control Zabbix server, use any of these: +=== System Services ===
-  service zabbix-server status+
  
-Replace ​**server** with **agent** for Zabbix agent daemon or with **proxy** for Zabbix proxy daemon.+Systemd services are available:​ 
 +  systemctl list-units zabbix*
  
-== - Increasing available diskspace == 
  
-<note warning>​Create a backup of all data before attempting any of the steps.</​note>​ 
- 
-Available diskspace on the appliance might not be sufficient. In that case it is possible to expand the disk. To do so, first expand the block device in your virtualization environment,​ then follow these steps. 
- 
-Start //fdisk// to change the partition size. As //root//, execute: 
- 
-  fdisk /dev/sda 
- 
-This will start //fdisk// on disk //sda//. Next, switch to sectors by issuing: 
- 
-  u 
- 
-<note important>​Don'​t disable DOS compatibility mode by entering **c**. Proceeding with it disabled will damage the partition.</​note>​ 
- 
-Then delete the existing partition and create a new one with the desired size. In the majority of cases you will accept the available maximum, which will expand the filesystem to whatever size you made available for the virtual disk. To do so, enter the following sequence in fdisk prompt: 
- 
-  d 
-  n 
-  p 
-  1 
-  (accept default 63) 
-  (accept default max) 
- 
-If you wish to leave some space for additional partitions (swap etc), you can enter another value for //last sector//. When done, save the changes by issuing: 
- 
-  w 
-  ​ 
-After partition creation (new disk or extended existing) create physical volume: 
-  pvcreate /dev/sdb1 
- 
-<note warning>​Partition name /dev/sdb1 is used in the example; in your case disk name and partition number could be different. You can check partition number using //fdisk -l /dev/sdb// command.</​note>​ 
- 
-Check newly created physical volume: 
- 
-  pvdisplay /dev/sdb1 
- 
-Check available physical volumes. There must be 2 volumes zabbix-vg and newly created: 
-  pvs 
- 
-Extend your existing volume group with the newly created physical volume: 
-  vgextend zabbix-vg /dev/sdb1 
- 
-Check "​zabbix-vg"​ volume group: 
-  vgdisplay 
- 
-Now extend your logical volume with the free PE space: 
-  lvextend -l +100%FREE /​dev/​mapper/​zabbix--vg-root 
- 
-Resize your root volume (can be done on a live sysyem): 
-  resize2fs /​dev/​mapper/​zabbix--vg-root 
- 
-Reboot the virtual machine (as the partition we modified is in use currently). That's it, filesystem should be grown to the partition size now. Check "/​dev/​mapper/​zabbix--vg-root"​ volume: 
-  df -h 
 === - Format-specific notes === === - Format-specific notes ===
-== - Xen == 
  
-**Converting image for XenServer** 
- 
-To use Xen images with Citrix Xenserver you have to convert the disk image. To do so: 
-  * Create a virtual disk, which is at least as large as the image 
-  * Find out the UUID for this disk 
- 
-  xe vdi-list params=all 
- 
-  * If there are lots of disks, they can be filtered by the name parameter //​name-label//,​ as assigned when creating the virtual disk 
-  * Import the image 
- 
-  xe vdi-import filename="​image.raw"​ uuid="<​UUID>"​ 
- 
-//​Instructions from Brian Radford blog//. 
 == - VMware == == - VMware ==
  
Line 285: Line 160:
 == - HDD/flash image (raw) == == - HDD/flash image (raw) ==
  
-  dd if=./zabbix_appliance_3.2.0_x86_64.raw of=/dev/sdc bs=4k conv=fdatasync+  dd if=./zabbix_appliance_5.0.0.raw of=/dev/sdc bs=4k conv=fdatasync
   ​   ​
 Replace ///​dev/​sdc//​ with your Flash/HDD disk device. Replace ///​dev/​sdc//​ with your Flash/HDD disk device.
-=== - Known issues ===+