Template:Menu content network

Revision as of 11:09, 17 November 2014 by WikiFreak (talk | contribs)


User management

Active directory Manage users and groups



DHCP and DNS

Network icon DHCP and DNS servers


Network
DHCP server DHCP server installation
DHCP dynamic IP assignation
DHCP static IP assignation
DNS DNS server installation
DNS server unique zone
DNS server split principle
DNS server split howto


File share

File share File share technologies


NetBoot

Netboot icon This section explains how to setup, boot and maintain a netboot image.


Requirements:


NetBoot and "Thin client" (diskless clinets) principle:


NetBoot services setup:


NFS image setup:


Register NFS image to TFTP:


Alternate Netboot scenario: 'Linux installation': network Linux installation



Mail

Mail icon Mail server (SMTP, POP3/IMAP)


Email relay

Email server setup



Monitoring

Monitoring Monitoring IT components, servers and applications using Zabbix


Monitoring
Zabbix server Zabbix server setup - requirements
Zabbix server setup - zabbix installation
Zabbix server configuration - first run
Zabbix server configuration - core setup
Zabbix server configuration - create hosts group
Zabbix server template management = create and manage template
Zabbix server create new application, items, triggers and actions
Zabbix server - add items to an application
Zabbix server hosts management
Zabbix server - play sound on alert
Zabbix server dashboard
Client side Zabbix agent setup - Recommended!
SNMP client - Old fashion monitoring, but still effective

You can also use 3rd parties dashboard on the server side using DASHING.

Dashboard icon Zabbix modern dashboard using DASHING


Note:

I'm using Zabbix v2.2. All the following information are just a practical summary of the Zabbix official documentation applied to my use-case.


Log aggregation

Log aggregation Monitor applications behavior using ELK.


Unlike Zabbix, this part is not about monitoring the environment but the actual applications behavior. To monitor applications results you can rely on logs files. ELK (Elastic search, Logstash, Kibana) is a wonderful stack to monitor that. See: http://www.elasticsearch.org/