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 [2020/04/06 11:47]
yuriii [8 Naming, init and other scripts] updated to systemd
manual:appliance [2021/01/27 20:27] (current)
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_appliance|download]] a Zabbix appliance or Zabbix appliance installation CD image. ​+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 and installation CD versions are based upon the following OS:  Zabbix appliance and installation CD versions are based upon the following OS: 
 ^Zabbix appliance version^OS^ ^Zabbix appliance version^OS^
-|5.0.0|CentOS 8  |+|5.0.0|CentOS 8 (x86_64) ​ |
  
 Zabbix appliance installation CD can be used for instant deployment of Zabbix server (MySQL). 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|}}| |{{:​manual:​installation_cd_boot_menu1.png?​600|}}|
Line 19: Line 23:
 Zabbix virtual appliance is available in the following formats: Zabbix virtual appliance is available in the following formats:
  
-  * VMX (VMware+  * 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 a browser at the IP the appliance has received over DHCP.  To get started, boot the appliance and point a browser at the IP the appliance has received over DHCP. 
 +
 +<note important>​ DHCP must be enabled on the host. </​note>​
  
 To get the IP address from inside the virtual machine run: To get the IP address from inside the virtual machine run:
   ip addr show   ip addr show
  
-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). ​+To access Zabbix frontendgo to **<​nowiki>​http://<​host_ip></​nowiki>​** (for access from the host's browser bridged mode should be enabled in the VM network settings). ​
  
 <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>​ <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>​
Line 45: Line 49:
   [zabbix]   [zabbix]
   name=Zabbix Official Repository - $basearch   name=Zabbix Official Repository - $basearch
-  baseurl=http://​repo.zabbix.com/​zabbix/​4.5/​rhel/​8/​$basearch/​+  baseurl=http://​repo.zabbix.com/​zabbix/​5.2/​rhel/​8/​$basearch/​
   enabled=1   enabled=1
   gpgcheck=1   gpgcheck=1
Line 76: Line 80:
   * Run **systemctl restart network** command.   * Run **systemctl restart network** command.
  
-[[https://​access.redhat.com/​documentation/​en-us/​red_hat_enterprise_linux/​6/​html/​deployment_guide/​s1-networkscripts-interfaces|Cosult official Red Hat documentation if needed.]]+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 88: Line 92:
 === - 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) ==
Line 95: Line 99:
   * root: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 server and frontend respectively. </​note>​+<​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 ==
Line 125: Line 128:
 === - 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>//​.+The frontend can be accessed ​at //​http:​%%//​%%<​host>//​.
  
-This can be customised ​in **/​etc/​nginx/​conf.d/​zabbix.conf**. ​You have to restart nginx after modifying this file. To do so, log in using SSH as **root** user and execute:+This can be customized ​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:
  
   systemctl restart nginx   systemctl restart nginx
Line 135: Line 138:
 === - 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 
-  * 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. To enable authentication,​ open 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:
   dnf update zabbix*   dnf update zabbix*
  
Line 170: Line 153:
   systemctl list-units zabbix*   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 the 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), 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. To check the partition number use //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 an existing volume group with the newly created physical volume: 
-  vgextend zabbix-vg /dev/sdb1 
- 
-Check "​zabbix-vg"​ volume group: 
-  vgdisplay 
- 
-Now extend the logical volume with the free PE space: 
-  lvextend -l +100%FREE /​dev/​mapper/​zabbix--vg-root 
- 
-Resize the root volume (can be done on a live sysyem): 
-  resize2fs /​dev/​mapper/​zabbix--vg-root 
- 
-Reboot the virtual machine (as the modified partition is currently in use). The filesystem should be increased to the partition size. 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, the disk image has to be converted first. To do so: 
-  * Create a virtual disk, with at least the same size as the image 
-  * Find out the UUID of this disk 
- 
-  xe vdi-list params=all 
- 
-  * If there are a lot of disks, they can be filtered by the name parameter //​name-label//,​ 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 247: Line 161:
 == - HDD/flash image (raw) == == - HDD/flash image (raw) ==
  
-  dd if=./zabbix_appliance_4.0.0_x86_64.raw of=/dev/sdc bs=4k conv=fdatasync+  dd if=./zabbix_appliance_5.2.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.