How To Add Remote Linux Host Into Icinga 2 Server PART1
How To Add Remote Linux Host Into Icinga 2 Server PART1
How To Add Remote Linux Host Into Icinga 2 Server PART1
2 Server
RAJ SEPTEMBER 13, 2016 0 COMMENTS CENTOS 6, CENTOS 7, DEBIAN 8, HOW TO UPDATE UBUNTU 13.04 TO
UBUNTU 14.04, ICINGA, MONITORING-TOOLS
In our previous article we have covered installing Icinga2 server on Ubuntu, Debian, and
Mint; also we have the installation Icinga Web 2 in Linux. In this guide, we will look at how to
add remote Linux host into the Icinga2 instance.
To enhance the security, Icinga2 uses SSL certificates for client and server communication.
Server and Client communications happen on TCP port 5665, make sure you have
configured the firewall to allow traffics in both ways.
Architecture:
The following diagram shows the illustration of distributed Icinga2 Server-Client
architecture.
Master Node This is the top most node in structure, where you usually install Icinga Web
2. It combines executed checks from child nodes into notifications.
Satellite Node This node can receive configurations for hosts or services, etc. from the
master node. It may execute the checks on its own or delegate the checks to client nodes,
and it can run even if the master node is unavailable.
Client Node This node either receives a remote command execution from the parent
node (master or satellite) or run its own configured checks.
Here, we will setup Master and Client node communication and be removing Satellite node.
Architecture diagram will look like below.
Environment:
Master Node:
Hostname: server.itzgeek.local
IP Address: 192.168.12.6
OS: Ubuntu 16.04
Client Node 1:
Hostname: client.itzgeek.local
IP Address: 192.168.12.7
OS: Debian 8
Client Node 2:
Hostname: centos.itzgeek.local
IP Address: 192.168.12.8
OS: CentOS 7
2.
3.
Generates the new certificate signing request (CSR), sign it with own CA and then
copy it into /etc/icinga2/pki/.
4.
Dumping configuration items (zones and endpoints) to /etc/icinga2/zones.conf
5.
Updating the /etc/icinga2/constants.conf file with NodeName and TicketSalt.
Verify the configurations files. Make sure your master node configurations should be like
below.
# cat /etc/icinga2/constants.conf | egrep -i "ZoneName|TicketSalt"
const ZoneName = "server.itzgeek.local"
const TicketSalt = "cbb245e46abb4761983de83a9acd7ecd"
PAGES: 1 2 3 4