EyesOfNetwork Using Using of solution EoN Fernandez Sébastien Original reference: EoN 3.1 Installation Actual reference: EoN 4.0 Installation State: Completed Last modification: July 21 2013 This file is distributed to you under Creative Commons Paternité version 2.5. To summarize: you are free to distribute and modify the file as long as you credit its author(s). The mention of the license is optional for derivative works. Official text of the license: http://creativecommons.org/licenses/by/2.5/deed.fr 1
-- History of modifications - Version Date Responsable Modifications 2.1.5 12/07/2010 Fernandez Sébastien Creation of document 2.2 02/01/2011 Fernandez Sébastien Modification for version 2.2 3.1 28/06/2012 Fernandez Sébastien Modification for version 3.1 4.0 18/07/3013 Texeire Emmanuelle Modification for version 4.0 + translation 2
Sommaire 1. PREAMBLE... 5 1.1. WHY THIS DOCUMENTATION?... 5 1.2. THANKS... 5 1.3. AXIS OF ADVANCE... 5 1.4. NOMENCLATURE... 6 2. WHAT IS EON?... 7 3. LOGINS AND PASSWORDS... 8 4. PROJECT TAB... 9 5. DISPONIBILITIES TAB... 10 5.1. GLOBAL VIEWS... 10 5.1.1. Dashboard... 10 5.2. TACTICAL OVERVIEW... 11 5.2.1. Panorama... 12 5.2.2. Performances... 13 5.2.3. Problems... 14 5.3. MAPS... 15 5.3.1. Thruk (Ex visu Nagios)... 15 5.3.2. Nagvis... 16 5.3.3. Wheatermap... 16 5.4. EVENTS... 17 5.4.1. Active events... 17 5.4.2. Resolved events... 17 5.4.3. Equipments... 18 5.4.4. Services... 18 5.4.5. Equipments/services groups... 18 5.4.6. Business view = Nagiosbp... 19 5.4.7. Business impact = Nagiosbp... 19 5.5. PROBLEMS... 20 5.5.1. Equipments ou services... 20 5.5.2. Downtimes and recurring downtimes... 20 6. CAPACITY TABS... 21 6.1. PERFORMANCE... 21 6.1.1. Graph view/cacti... 21 6.1.2. Graph view/pnp4nagios... 21 6.1.3. Performances/per Host... 21 6.1.4. Performances/per label... 21 7. PRODUCTION TAB... 22 7.1. TOOLS... 22 7.1.1. Hosts... 22 7.1.2. Externals... 23 7.2. LOGS... 24 7.2.1. Nagios... 24 7.2.2. Systems... 25 7.3. CONFIGURATIONS... 26 7.3.1. Asset management : glpi... 26 7.3.2. Inventory : ocs... 26 8. REPORTS TAB... 27 8.1. EVENTS... 27 8.1.1. Number of incidents... 27 8.1.2. Technical SLA... 28 3
8.2. DISPONIBILITY... 29 8.2.1. Availability... 29 8.2.2. Trends... 30 8.2.3. Alert summary reports... 31 8.2.4. Generation of reports/nagios... 33 8.3. CAPACITY... 34 8.3.1. Performance... 34 8.3.2. Networks... 34 9. ADMINISTRATION... 35 9.1. LOCAL ACCESS... 35 9.1.1. SSH access... 35 9.1.2. Snmpwalk... 36 9.2. MAIN SETTINGS... 37 9.2.1. Authentification... 37 9.2.2. Groups... 38 9.2.3. Users... 38 9.2.4. Process... 39 9.2.5. SNMP... 40 9.2.6. SNMPTrapd... 40 9.2.7. Backup... 41 9.2.8. Logs... 45 9.3. NAGIOS... 46 9.3.1. Configuration... 46 9.3.2. Hosts... 70 9.3.3. Templates... 70 9.3.4. Business processes = Nagiosbp configuration... 71 9.3.5. Downtime scheduling... 72 9.3.6. Advanced notifications... 73 9.3.7. CSV Import... 75 9.3.8. Cacti Synchronisation... 76 9.3.9. Apply configuration... 76 9.4. GED... 77 9.5. MAPS... 78 9.5.1. Nagvis... 78 9.5.2. Weathermap... 86 9.6. EXTERN LINKS... 93 9.6.1. Thruk... 93 9.6.2. Cacti... 93 10. INTRODUCTION FOR EON UPDATE... 99 10.1. TAKE BACKUPS... 99 10.2. NEW VERSION INSTALLATION... 99 10.3. RESTORATION... 99 10.3.1. Postfix update... 99 10.3.2. Nagios update... 100 10.3.3. Nagvis update... 101 10.3.4. Cacti Update... 102 10.3.5. Eonweb interface update... 102 11. AXIS OF ADVANCE... 104 4
1. Preamble 1.1. Why this documentation? This documentation aims to provide users with a better understanding of the capabilities of EyesOfNetwork solution. However some basic knowledge of Linux/nagios/cacti will be necessary for a full understanding of the documentation. 1.2. Thanks Before digging into the heart of the matter, I wish to thank the active members of the community of "www.eyesofnetwork.com" for having been able to develop a complete, accessible and relevant tool. 1.3. Axis of advance This documentation will cover most of functionalities of EoN solution. At first it can seem to be too technical because the documentation is for people who already have knowledge in supervision field. It is up to you to complete this documentation to match the needs of the greatest number. Contributors are gracefully invited to complete the part history 5
1.4. Nomenclature A command line to enter in the console is represented in this form: /etc/init.d/xxx Important information requiring your attention is represented like this: Think to start the service Useful information is represented like this: Do «/ect/init.d/service restart» 6
2. What is EON? EyesOfNetwork ( EON ) is the OpenSource solution combining a pragmatic usage of ITIL processes and a technological interface allowing their workaday application. EyesOfNetwork Supervision is the first brick of a range of products targeting to assist IT management and governance. EyesOfNetwork Supervision provides event management, availability, problems and capacity. The Release 4 reinforces always this positioning, by providing: Business Processes configuration tool PDF reporting templates (monitoring+performances) New design of web interface Automatic generation of performance graphs using performance data from Nagios (Pnp4nagios) Calculation of owning time of events in the active queue (RSS Feed) Generation of popups when events happened in the active queue New plugins: Oracle, Network Easier hosts and services definition EyesOfNetwork is accessible via a single Web interface that aims to bring together the various actors of an information system (Governance, Administrators, Technicians, Operators, ). Each of these actors has a view corresponding to his position. 7
3. Logins and passwords An IP address is attached to your monitoring server during installation. To connect to the interface web "http:// IP server" of monitoring server login / password: admin / admin For Glpi, login / password: admin / admin, coupled with EoN To Ocs, login / password: admin / admin For Ntop, login / password: admin/root66 Password root mysql : root66 8
4. Project tab Presentation of the solution 9
5. Disponibilities tab 5.1. Global views 5.1.1. Dashboard View that appears by default when you open the web page (see previous picture). There is a summary of the statements of hosts/nagios services and active events. 10
5.2. Tactical overview Synthesis of nagios checks, used interface is thruk: 11
5.2.1. Panorama This view allows creating a specific dashboard, customizing your view of hosts/services nagios and events. 12
5.2.2. Performances Summary of tests in a period of time. 13
5.2.3. Problems Summary of failures (nagios point of view): 14
5.3. Maps 5.3.1. Thruk (Ex visu Nagios) Base Mapping thruk, robust but too limited. Note that you can change the display section at the top right! 15
5.3.2. Nagvis More sophisticated mapping, flexible and adaptable, takes into account the recursive maps. Note that these cards are DEMO! 5.3.3. Wheatermap Display of cacti/weathermap by default no map created. The creation will see in chapter Administration. 16
5.4. Events 5.4.1. Active events Displays events when information feedback of a "non-ok" state. By right clicking on it, you can own the failure or acknowledge it. Allows checking of incidents. 5.4.2. Resolved events Same display but on the events resolved... i.e. when an event is either up or was acquitted in the active events view. 17
5.4.3. Equipments Summary of nagios hosts state only. 5.4.4. Services Same display but on nagios tested services. 5.4.5. Equipments/services groups Display the nagios view of desired groups. 18
5.4.6. Business view = Nagiosbp Vision of the services state provided to customers. Generated by Nagiosbp. 5.4.7. Business impact Opportunity to display services state provided to customers by simulating a failure of a host or service. 19
5.5. Problems 5.5.1. Equipments ou services Display Hosts or Services in failure with Nagios point of view. 5.5.2. Downtimes and recurring downtimes Force Nagios not to test a host or service for a specified period and therefore do not consider it down. 20
6. Capacity tabs 6.1. Performance 6.1.1. Graph view/cacti Display all graphs created by cacti. At the moment there is no graph. This page open a link to cacti. 6.1.2. Graph view/pnp4nagios Display all graphs created using data collected by nagios. At the moment you can see the graphs for localhost. 6.1.3. Performances/per Host Display all graphs created by cacti for a particular host. A host must be created under cacti and graphs must be associated to it! 6.1.4. Performances/per label Display all same graphs created by cacti for different hosts. Same remark that for equipment view. 21
7. Production tab 7.1. Tools 7.1.1. Hosts With this view you can: - Access a host by ssh or telnet - Scan opened ports on equipment - Display the state of network interfaces of equipment if it is declared in cacti (with SNMP community) Host must be declared in cacti! 22
7.1.2. Externals Same possibility but entering IP address of host manually. No need to register host in cacti In the case of show interface, enter IP, select show interface (it should be highlighted), enter Snmp Community, select appropriate version of SNMP and the click on Run it. 23
7.2. Logs 7.2.1. Nagios Display Nagios logs. 24
7.2.2. Systems Display the view of syslog portal (here cacti plugin id used). You can set rules to automatically delete by clicking on the icon marked with a cross, it allows you going to the removal rule cacti section! At this step, rsyslog configuration only supports the local logs! To enable reception of logs via other servers see documentation configuration. 25
7.3. Configurations 7.3.1. Assets management : glpi Possibility of access to glpi: IT asset management (login / pwd coupled with eonweb). Whereas this is an option, we will not talk about it, excellent tutorials circulating on the web. Note that to facilitate the management glpi, ocs can be installed on EyesOfNetwork. 7.3.2. Inventory : ocs Possibility of access OCS: Inventory / software deployment. Whereas this is an option, we will not talk about it, excellent tutorials circulating on the web. Not to duplicate it is possible to import the OCS data in glpi... 26
8. Reports tab 8.1. Events 8.1.1. Number of incidents Let summarize the number of failure encountered in a given period (host or service failure). In this example it is the view for the equipment webdev on a week. 27
8.1.2. Technical SLA Allows synthesizing the average resolution time of failures for a given period, the same example as above. 28
8.2. Disponibility 8.2.1. Availability Allow having availability of host/service or hosts/services group over a given period To display a coherent result enter at the top, First assumed host state to «up» and First assumed host service to «up». Always the same example used, select host webdev. Click on button create report to generate the report. 29
8.2.2. Trends Allow having availability of host/service or hosts/services group over a given period To display a coherent result enter at the top, First assumed host state to «up». Always the same example used, select host webdev. Click on button create report to generate the report. 30
8.2.3. Alert summary reports This view allows giving statistics about events with filter on hosts, group hosts Most recent alerts: 31
Top alerting: 32
8.2.4. Generation of thruk reports Generate a report with thruk. For this feature, to be useful, it is necessary to have previously configured a mail relay, see documentaion configuration". 33
8.3. Capacity 8.3.1. Performance Displays all available graphs cacti in a given period to have a summary of the load in the period. 8.3.2. Networks Results seen by ntop probe. First do not forget to have run the ntop process in the Admin. 34
9. Administration 9.1. Local access 9.1.1. SSH access Allows accessing to supervision server console if the client have the Java platform installed. SSH tool also allows you to upload or download files between the client and the server. 35
9.1.2. Snmpwalk Starts an SNMP request to a remote host to verify the response of the SNMP agent. 36
9.2. Main settings 9.2.1. Authentification Indicates whether you want to use the sql server database monitoring for users management suite. By default only admin account is present. You can use, for example, authentication based on a 2003 server Active Directory or LDAP standard. Example configuration for a connection with Active Directory 2003: FOR a classic Ldap: 37
9.2.2. Groups Select add group and click on Submit button. This view allow the segregation of user access by definition of groups. Indeed for each group you can specify which tabs of the solution will be available... one or more... 9.2.3. Users This view allows creating users and assigning them to groups. 38
It is possible to use an LDAP or AD basis for selecting EXISTING users in order to place them in access groups of the solution. 9.2.4. Process Displays a list of useful process for solution... Ability to stop / start the process without having to connect to the server in console mode... 39
9.2.5. SNMP Allow changing snmp community of solution without having to connect to the server in console mode. Do your change, click on update button then restart snmp service via Main setting/process. 9.2.6. SNMPTrapd Identical function to SNMP but for file snmptrapd. Differentiate snmp and snmptrap! When you configure SNMP service that involves an external application (in our case a nagios script) will access this service to read information, it is active supervision. Snmptrap sends information directly to your server after an event, we speak in this case of passive supervision. 40
9.2.7. Backup Identical function to SNMP but for file allowing to configure backup of the solution. By default the solution backups /etc, /srv, sql databases.in files.tar.gz or bzip locate in directory /var/archive. EON uses a configuration file to perform the backups. This file is based on backup software backupmanager configuration file. Every night at 4:00 am a backup of databases, various software and their configuration files are stored in the /var/archive directory. The script, which is used for backup is available by clicking on the Administration tab and backup section. Once stripped of all his comments, the script looks like this: 41
export BM_REPOSITORY_ROOT="/var/archives" export BM_TEMP_DIR="/tmp" export BM_REPOSITORY_SECURE="true" export BM_REPOSITORY_USER="root" export BM_REPOSITORY_GROUP="root" export BM_REPOSITORY_CHMOD="770" export BM_ARCHIVE_CHMOD="660" export BM_ARCHIVE_TTL="5" export BM_REPOSITORY_RECURSIVEPURGE="false" export BM_ARCHIVE_PURGEDUPS="true" export BM_ARCHIVE_PREFIX="$HOSTNAME" export BM_ARCHIVE_STRICTPURGE="true" export BM_ARCHIVE_NICE_LEVEL="10" export BM_ARCHIVE_METHOD="tarball mysql" export BM_TARBALL_NAMEFORMAT="long" export BM_TARBALL_FILETYPE="tar.gz" export BM_TARBALL_OVER_SSH="false" export BM_TARBALL_DUMPSYMLINKS="false" declare -a BM_TARBALL_TARGETS BM_TARBALL_TARGETS[0]="/etc" BM_TARBALL_TARGETS[1]="/home" BM_TARBALL_TARGETS[2]="/srv" Explanation: We will explain some guidelines that are used so that you can adapt the script to suit your needs. Sources: http://doc.ubuntu-fr.org/backup-manager BM_REPOSITORY_ROOT Directory where are all archives. 42
BM_TEMP_DIR Temporary directory use during the backup. BM_REPOSITORY_SECURE For security reasons the backup directory can access only by some users/group defined in variables BM_REPOSITORY_USER, BM_REPOSITORY_USER and BM_REPOSITORY_CHMOD BM_ARCHIVE_CHMOD Rights of backup files. (660 = rw-rw---- soit read, write for owner, rw for group and nothing for other) BM_ARCHIVE_TTL Time To Live in days of archive. BM_REPOSITORY_RECURSIVEPURGE Recursive purge of the backup directory. BM_ARCHIVE_PURGEDUPS If two successive archives (backups) are identical backup-manager can create a link instead of recreating an archive. BM_ARCHIVE_PREFIX Give prefix at the name of archive BM_ARCHIVE_STRICTPURGE This directive is useful if you stored all your backups from different backup-manager in the same directory. Passing the value to "yes", BM will not delete the files generated by other BM and have more than 5 days. BM_ARCHIVE_NICE_LEVEL When BM generates a backup, it stresses the CPU. To avoid excessive CPU load, the directive assigns a priority level in the process. Plus the nice level is high better is. By default, BM uses a nice level of 19 for Desktop environment. BM_ARCHIVE_METHOD The method for creating the archive BM_TARBALL_NAMEFORMAT How to appear in the file list: long: list all sub-directories and the file name (eg /home/foo/doc.odt) short: give only the file name (eg doc.odt) BM_TARBALL_FILETYPE This is the type of compression desired. BM_TARBALL_DUMPSYMLINKS Is backup-manager backup directories pointed on links (shortcuts)? BM_TARBALL_TARGETS Directories to backup. 43
BM_TARBALL_BLACKLIST Give a blacklist that has some folders and files not save. BM_TARBALL_SLICESIZE Determines the maximum size of archives BM_TARBALL_EXTRA_OPTIONS To add more options to "tar". For example, to active the verbose mode: BM_TARBALL_EXTRA_OPTIONS="-v" BM_TARBALLINC_MASTERDATETYPE Determines the frequency of full backups: weekly or monthly BM_TARBALLINC_MASTERDATEVALUE The day of full backups: if weekly: put a number from 0 6 (Sunday Saturday) if monthly: a number from 1 31 BM_MYSQL_DATABASES Databases to backup BM_MYSQL_SAFEDUMPS Means used to save the db. Currently the safest method because it allows inject the sql file generated in another db without modification. BM_MYSQL_ADMINLOGIN User mysql BM_MYSQL_ADMINPASS Password of mysql user BM_MYSQL_HOST Mysql server BM_MYSQL_PORT Port of Mysql server BM_MYSQL_FILETYPE Compression format for BDD. You must use "bunzip2" to decompress. BM_UPLOAD_SSH / Rsync etc.... These directives allow you to save your data on a remote directory other than locally. BM_PRE_BACKUP_COMMAND Here you enter the command to perform before a backup BM_POST_BACKUP_COMMAND Here you enter the following command to perform after a backup. Changing the configuration file to save by FTP 44
Change directives like this: BM_UPLOAD_METHOD="" by BM_UPLOAD_METHOD="ftp" BM_UPLOAD_FTP_USER="" by BM_UPLOAD_FTP_USER="your login" BM_UPLOAD_FTP_HOSTS="" by BM_UPLOAD_FTP_HOSTS="IP address of server ftp" BM_UPLOAD_FTP_DESTINATION="" by BM_UPLOAD_FTP_DESTINATION="path to directory" Then login in ssh then start the script in /usr/sbin /usr/sbin/backup-manager -v The principle is the same as rsync, S3, ssh. 9.2.8. Logs Display interesting logs of solution. 45
9.3. Nagios 9.3.1. Configuration Display web portal of nagios Administration. Operating principle: The changes here are in SQL database. To apply in nagios you must export the database to Nagios files. 9.3.1.1. General Menu This menu is displayed by default when you open, giving access to a home page. You can modify: - Nagios Daemon Configuration : the configuration of nagios (path, broker ) - Nagios Resources : Basic variables used $USER1$ is the absolute path to the directory containing the nagios scripts. $USER2$ is snmp community used for check. To remain consistent the various equipment supervised, the monitoring server and this variable must contain the same SNMP community name. - Time Periods : allow creating new schedules check ranges. By default only 7j/7 24h/24 is present. - Contact Group : At this point it is possible to create groups of contacts, they will combine several contacts who need to receive the same Nagios alerts - Service Group : Possibility of creation of groups services Example: A group of service web gathering all the tests of web services for different devices. - Nagios Web Interface Configuration : Configuration of available options for Nagios web portal. - Nagios Commands : Manages the association between scripts and equipment checks The scripts are located in the directory /srv/eyesofnetwork/nagios/plugins. We can therefore add new commands to check service. - Contact : Possibility to modify contact created with eonweb interface particularly notification method - Host Group : Possibility of create groups of equipment. 46
47
9.3.1.2. Template Menu 48
The templates are used to preset options common to multiple hosts or services. This is to avoid having to configure all options for each guest or services such as commands, notices... Some default host templates are already created, for example for windows 2000/2003/XP platform with related services. It may be necessary to modify the associated services to better meet the need. Similarly, a generic-service basis is created, taking a common service configuration. Notifications already in place, contact admin by default, the time period defined... Since v2.2 a navigation bar is added with the possibility of multiple selection, the ability to clone or delete. An example is given to modify hosts template. 49
9.3.1.3. Example to modify a host template - Click on a template (ex: AIX5): -Go in part Services - List of all services tested and associated with template is displayed. Opening each service we can find the command used for testing of each service. It will then be possible to return to the General section of lilac nagios command section to make the necessary adjustments. 50
9.3.1.4. Example to modify a check command Example with systime service: - Click on Edit if you want modify for example display name. - Click on Checks 51
-The command used is systime. - To see the exact test command return to the General tab at the top in Nagios Commands - Down and then select systime. 52
You can modify the command in Command line section. After the command changed click on modify command to apply change. Proceed in the same way for all service commands to change. Note that special characters and accents are ignored characters, it must be replaced by. the character called joker. It is also possible to use variables... in the case of this command $ARG1$. Use variables to define a common services but using two different checks. Be careful not to make such a replacement in a template. Indeed the principle of service template is to be common to all so if the command is changed it will change for all hosts associated with template and therefore service. The principle of variable is applied to services associated with hosts instead of templates. We will expand on this in the next chapter. 9.3.1.5. Example of creation of new nagios command Consider the case where you found on the web a new Nagios plugin (script) to test your specific hardware. -Download this file -Via a kind utility winscp copy this script on eon in /srv/eyesofnetwork/nagios/plugins/ -Set the right permissions on this file doing: - Change to the appropriate directory: cd /srv/eyesofnetwork/plugins/ 53
-Set the good rights: chown nagios:eyesofnetwork FileName chmod 755 nomdufichier - Now test the syntax of the command by running:./filename In general, you must enter parameters such an address of device, snmp community, SNMP Version, threshold values warning and critical in % or other... read help of the command! When you have the desired result it remains only to you built this command in nagios configuration by doing the parallel between your parameters and variables used in the portal. In the web portal eonweb Administration tab nagios configuration section go to nagios commands -Choose add command -Enter a name for minimum control and check its syntax Here is some help for syntax: All commands will be preceded by the variable $USER1$ (which corresponds to the path /srv/eyeofnetwork/nagios/plugins), the variable $HOSTADDRESS$ replaces the address of the host, $USER2$ is the snmp community, etc... See on existing command! After it you just have to assign this command to a service... 54
9.3.1.6. Network Menu -In this menu it is possible to add equipment. -Here is an example of creating, click on Add a new child host 9.3.1.7. Example of host creation -Enter the host name, a description, an IP address. The Display Name is an option that is not mandatory. Select a template and click on Add Template. Then click on Add Host. In this view you assign a Template to your Host, in order to avoid typing all the options manually. For this demonstration linux selected. 55
This screen has the same architecture for all hosts, it includes the following tabs: - General : Basic information on the host, click on Edit to change the information. - Parents : The notion of Parents / Childs determines the relationships between the devices. Your host was connected to a switch which could be in parent add. This is important because if a host is detected down, Nagios will not test the children and place them in unreachable status and will not do required checks. You must be logic in the organization of parent/child. 56
- Inheritance : - Checks : As a template is associated to the host, there are default values. By default, on this template, the check command of host is check-host-alive i.e. ping. - Flapping : This menu allows you to set options for flapping. The Flapping refers to hosts or services changing state often. 57
- Logging : Little useful concept, not used. - Notifications : This menu sets, if in case of problem, notifications will be sent or not and in what cases. In this example, the notifications are enabled for down or unreachable states... - Services : In this menu you can see the services of template attached to the host. It is possible to create other services, the point that we will detail. 58
9.3.1.8. Example of service creation for a host Click on Create a new service for this host Enter a description and name of service. At the same way as the host templates, it is possible to inherit template for a service. A generic_service is integrated and allows predefined checks and notifications. To inherit of the generic_service, select generic_service in the list and click on add template. Most options are pre-filled, it remains to define the command of check itself. Click on Provide Value and select your command by example check_http. You can now add parameter if necessary. For example check_http, enter 80 for $ARG1$ then click on Add service 59
-Flapping and logging sections: little used -Notifications sections: Prefilled via the template Service -Group Membership section: It is possible to combine different services from different hosts in the same group, on condition that you specify... -Contact section: Allows you to specify one or more contacts, one or more contact group to receive notifications when problems arise, on condition you have specified previously... -Extend information section: Optional information that can add to this service like an icon, a URL containing more information on this service... -Dependency section: Opportunity to highlight the dependencies between services and other hosts, little or no use. -Escalation: little used - Check command parameter section: 60
If you return in check part, we will see the variable appears This service is configured, click on back to host to return to the configuration of the host: - Group Membership - Contacts - Extended information - Dependencies - Escalations - Check Command Parameter All the menus have the same role as those addressed in the creation of a service, but with a host point of view... In fact, the host groups, contacts, settings are not necessarily identical for the host and services. Once the host is created and it has associated services (not required, the check-host-alive of host may suffice if there is anything relevant to be tested again). The configuration section is ended. 61
However, these data are present in administration nagios interface, but not in Nagios itself. For this, we need to export the configuration to Nagios. This point is treated later. 62
9.3.1.9. Example of host creation by duplication Go to the Network menu: The right side of the hosts allows doing multiple selection while the top section Actions allows selecting action remove, duplicate or export. The section Object to allows you to add/delete Hostgroup, Parent and Template. Duplicating host is interesting to avoid to create device manually. Suppose we have several EON Server in our network, one is natively present in the network section, the original localhost. However all that EON have the same services, same design, only the name and IP @ machines differ. We will create an EON 2. First, duplicate the original EON as follows: Click on submit, a clone of original EON is created: 63
It remains only to edit the new host to just change its name and its IP to obtain, for example: And the host was created in a few click with the same hostgroup, contact Service... than the original! This possibility of duplication / multi selection is also valid in the template section. 64
9.3.1.10. Tools Menu - Import : Import data from a database system fruity or flat files nagios. However the nagios configuration is specific to the solution, importing files from outside nagios system does not work, especially because of the path and templates. - Export : To export the configuration of from lilac to flat files nagios just click on "Restart" job nagios (top right). In case of error export, look down the page for the job. Until the error is resolved, no data will be exported to nagios. - AutoDiscovery : This tool, based on nmap can scan ports on network ranges to autodetect equipment. To automate the combination of a host with a template, it is possible to set up filters on the templates to make the connection Scan port = Template. 65
9.3.1.11. Example of automtic attribution of template This basic example will assign template Windows and Linux automatically. Go to Templates tab, select WINDOWS. In this template click on Auto-discovery filters : To achieve this it just click edit select provide value on the Operating System line and enter Windows. Before click add filter service, choose TCP Port protocol: 135... this port is a Port microsoft rpc... Now, filter for windows is in place. 66
For template Linux : Here are the settings used. Then return to the Tools menu Autodiscovery section. 9.3.1.12. Creation of autodiscovery job Here an example of creation of autodiscover job name in this case scan1 67
Necessary information: -name of job -Target specification: IP address or range of IP at nmap format! Example: 192.1.1,2.1-100 = 192.1.1.1 to100 and192.1.2.1 to 100 Click then on add target then begin auto-discovery job 68
Click on the green background area to open the result Select the required equipment and choose import and click on process button. 69
9.3.2. Hosts Network view. 9.3.3. Templates Template view. 70
9.3.4. Business processes = Nagiosbp configuration This section describes how create business processes display like this: Go to Administration tab Business processes section Click on eon to see business processes eon : Here are some things to configure: - Eon -> name of Nagios Business Process - Process name -> Name display in disponibilities view - Display 1 = priority of business processes - URL: Displays the blue icon I in disponibilities view, in case of BP EON / 71
- Command: Result command displays in status information in disponibilities view For EON uptime. Click on modify to view service details. - Localhost ;Process_ged : check ged service of localhost So NagiosBP Eon is up if services ged of localhost AND port ssh localhost AND port mysql localhost are up. 9.3.5. Downtime scheduling This view allows setting easily recurrent downtime. 72
9.3.6. Advanced notifications The advanced notification uses the same description of contacts and groups that sending conventional mail by applying a filter on each notification. Only the notification command is changed to use advanced notifications. Example: Secondly, we must define the rules of notification via eonweb interface in Administration -> advanced notifications. 73
The following lines describe the syntax of this configuration file. Tags rules delimit the configuration. All statements that are out of these tags will not be taken into account by notify. Tags debug_rules allow to define a level of log to notify. 0 no log, 1 log all notifier actions, 2 log notify actions corresponding to sends the notification. Tags logrules_file allows to define the localization of log file for chosen debug mode. Tags host allows to define specific rules of advanced notifications which will be applied to the equipment. Notifications rules are defined on the following format: contact ; host ; service ; state ; dayofweek ; timeperiod ; notificationnumber ; method Contact : Person or group will match the rules. It is possible to assign multiple contacts on the same rule. These must be separated by a comma. Host : Equipment or group of equipment will match the rules. Service : Service or service group will match the rules. State : Particular state of the equipment (UP, DOWN, UNREACHABLE) or service (OK, WARNING, CRITICAL, UNKNOWN) will match the rules. Dayofweek : Day of the week will match the rules. (mon, tue, wed, thu, fri, sat, sun). Timeperiod : Time range in which the notification rule will work. (hhmm-hhmm) Notificationnumber : Number of notifications for which the rule is valid. Unique (4) or from the Xth notification (4-). Method : Notification method when the rule matchs. (email, sms,...) Corresponds to the methods of notifications defined in the notifier.cfg file. 74
Jokers are available. They are defined as follows: - * : Is anything. If this joker is used, it will match all entries. - - : Corresponds to nothing. If this joker is used, it will match a blank entry. Typically, in the rules of notification for the equipment, must be the service field filled with this joker. Examples: For equipment: Admin:localhost:-:*:mon,tue,wed,thu,fri:0800-1800:1:email It notifies admin contact for localhost equipment, for all states, between Monday and Friday from 8:00 to 18:00 only to the first notification by sending an email. For service: Admin:localhost:ssh:*:mon,tue,wed,thu,fri:0800-1800:4- :email It notifies admin contact for ssh service of localhost equipment, for all states, between Monday and Friday from 8:00 to 18:00, from the 4th notification by sending an email. 9.3.7. CSV Import This section allows you to import hosts via a Csv file... To do this: - Create previously under lilac the hosts templates" suiting your needs. - Fill the csv file like this: Hostnames, @ ip, description, names of the selected template In the web-portal click on browse, retrieve your file then click on upload button. -Your hosts should be in lilac (9.3.1.4), you have to export to nagios. 75
9.3.8. Cacti Synchronisation This menu allows you to import a host from lilac to cacti. Simply select one or more hosts to the same kind (switch, linux,...) on the left, choose the Host template (cacti not nagios) that best fits, enter the SNMP community version and then click on import. In contrast to remove choose hosts on the right and click on remove. 9.3.9. Apply configuration This section corresponds to the view Nagios Configuration / Tools / Exporter As in lilac to launch an lilac export database to Nagios, click on restart job. 76
9.4. Ged GED Part not details!!! 77
9.5. Maps 9.5.1. Nagvis Nagvis replaces mapping Nagios, it is not quite readable and too rigid. Nagvis will help to make connections between maps, insert background images, icons and pictures... To assimilate the different possibilities we will create a map. 9.5.1.1. Nagvis map creation The Open section displays the active maps without the possibility of change. The Options section allows creating or remove maps, inject or remove backgrounds, shapes (icons...) or define backend. A backend is a module to trace the changes of states of nagios which in a sql database (using ndo2db) or buffer flat files (ndo2fs / mklive status). 78
Nagvis can t interact directly with Nagios, it only reads the remounted of a backend. EyesOfNetwork provides to administrators three different backend. In view of the performance the best of the three is mklive status selected by default. To inject an object (forms) click on Options then Manage shape. By clicking browse it will be possible to upload a picture of your client station to Nagvis to use in maps, Choose Upload. It is also possible through this part to find a picture of nagvis and remove it. To inject a background that is the same way, once returned to Options menu select Manage Background. Through this interface you can: -create a single manual wallpaper (upper part) by entering a name, color and size in pixels. -inject an image that will serve as a wallpaper on the same principle as the forms. -remove a background picture of nagvis. To create a map in the same way, once returned to the Options menu select Manage maps. 79
- Enter name of map - Choose Map Iconset. - Select background for example your background previously imported. - Click on create, your blank map is ready! It is also possible to rename the map, delete or export / import the configuration file of a map. The map will open and it will be possible to add hosts, services, images... 80
To do it, make a click on Edit map in the banner at the top part (A note on an existing map, you must first unlock the map clicking on lock / unlock all ), select Add Icon -> Host 81
The section add icon Host / Service section /... will help to add a icon will change color according to the Nagios state of this host / Service... Note that there is also in icon Map. This icon map will help other maps remounted their state via the icon in the main map. The Add Special" section contains a TextBox section to add text and shapes part (to use images already inserted as shapes ). The Add line" section finally allows to draw lines! 9.5.1.2. Add icons to Nagvis map Example: Select Add special -> shapes Then left-click with the mouse to the place where the object will be placed then: Description : -icon : select an objet -x and y coordinates prefilled -z coordinate depth = useful when the object / icon overlay. The object or icon with a higher than another will appear above value. -Other options will not be discussed. Then click on Save button. 82
To associate a Nagios state icon, via a right-click on edit map -> add icon, choose host Using the cross click on where you want the icon... a window appears 83
-Hostname : Select wanted host, here localhost. -X,Y : coordinates prefilled -Z : depth -Iconset : icon style -label_show display or not a text window with the name of the host, permit access parts LabelText... to select this section click on yes -LabelText: the [name] default will be used to display the name of the host as it was entered in nagios, the value can be changed to customize the title. -label x, y, z coordinates of the text box -label_width: length of the text frame, auto default. -label_background: background color of text box transparent by default. The color values are in hexadecimal. Ex: # aff = blue, # FFF = white. -label_border: colors from the edge of the text box. -only_hard_states: This icon should or should not display the hard status -recognize_services: This icon should or should not show. - 84
-Click on save. -Ability remaining clicked on the icon to move it after the creation of map. Map ended, to display see menu 5.2.2 85
9.5.2. Weathermap Before using weathermap it is necessary to have previously configured a device in cacti, part 9.6.2 To create map click on Weathermap editor : It is possible to use an existing template or from a blank file. For this test, create a map named test1.conf based on simple.conf because using other possibilities the legend has a display problem. The file must be ended by.conf extension. 86
At the opening of the map, click on the nodes and arrows and choose delete for each time. In this interface, only this items are useful: 9.5.2.1. Add node A node is a node to which we can associate an icon, a name,... To do this, click on Add node, the mouse pointer will be changed. Then click on the background map to add the node. Click on Node to open a configuration menu. 87
-Position: coordinates of node -Internal Name: name used in configuration file -Label : name displayed on the map -Info url : url link for information - Hove graph url: possibility to associate with the icon a link, for example cacti(pick from cacti) if you want to associate a graph has an icon. Weathermap is often used to see network load, so we won't Association at this level... -Icon Filename: Choose an icon You can add extra icons to weathermap. The fastest is to use winscp and then to transfer icons from the client workstation to the directory /srv/eyesofnetwork/cacti/plugins/weathermap/images / on Eon server. Then set on new files the rights 774 and user:group = cacti :eyesofnetwork Click a second time, on Add node and edit it to have new node name server 1 like this: 88
- Go back to first node by clicking on node and : -Change label and Icon filename and click on Submit -You obtain: -With Add Link create a link between the two nodes. 9.5.2.2. Add Link Click Add Link then on serveur1 and Lan. 89
-A left-click on the arrow will open a menu: -Maximum bandwidth Into: max value of bandwidth by bits/sec unit: K, M, G -Maximum bandwith Out : Possibility select the Same As or define a value manually -Data source: Set the source of statistics to display. In our case, and always if the host was previously integrated into cacti with associated graphs, click on pick from cacti. Selected the wanted graph. 90
-Info url and Hover Graph url: These fields will be filled automatically -IN Comment : Comment in the case of reach the mini threshold -Out Comment : Comment in the case of reach the maxi threshold Click on submit button. It is possible to add a legend color via position legend tab. The map is created, a delay will be necessary to weathermap to initialize it (5 min). We must now declare it in the active maps. Go back to : 9.5.2.3. Map Activation -Click on Add at the right corner, - Click on Add on the line where your map is -Then click on admin at accessible by flag -Choose Anyone then click on update, access restrictions are handled by the web portal. 91
After the time of calculation, the map will be displayed in the view 5.2.3 The complete documentation of weathermap is accessible via a link at the bottom of the map: local documentation. 92
9.6. Extern Links 9.6.1. Thruk Link on web page thruk 9.6.2. Cacti Link redirecting to the Cacti portal. Not having been mentioned before, these are elements to facilitate the configuration of hosts. After item 9.3.4 a host has already been imported into cacti. Here's how does it manually: 9.6.2.1. Add equipment with a cacti graph -To go in the view present hosts click on devices in the left menu. -To add a host, click on Add at the right of device bar. 93
-Description: description of equipment -Hostname: dns name or IP address -Host Template: possibility like for nagios to select a template -Disable host: in case problem, possibility to desactivate tests. -Downed Device Detection: Method used by cacti to check a host : Snmp,Ping, -In SNMP options define snmp version, community -Click on Create button. -Open again the Device created to create one or more graphs 94
-In this case, it is an equipment using the "ucd/net SNMP host" template that was used, so you see already Associated Graph Templates. Note that those are graph templates but in no case graphs have been created. -However for weathermap for example (previous chapter) it would be interesting to add in the section associated data query a query on network interfaces. For that, For this, click on the drop down menu to the right of add data query (bottom) and choose SNMP Interface statistics. At the end do add to the right of this line. -At the top click now on Create graph for this host. 95
-This screen displays the available requests to create graphs. The section which interests us for weathermap is "SNMP Interface statistics. -Click on the checkbox to select the wanted interface. -Then click bottom on create button. -In this screen click at the upper left on edit this host to return to the window or you set the equipment and then down to save. 9.6.2.2. Put a graph in tree -In left menu click on Graph Management 96
-Select the graph and choose Place on a tree in the menu Choose an action then click on go button. - There is only the branch root by default, click on yes. - Your graph is created and available in the graph tab. To check click on the tab on top name graph 97
You can also view the graph in realtime: 9.6.2.3. Modify graph tree It is possible to create its own tree of graphs...for this, return to the main page by clicking on the tab console, and then on the left side on graph Via this screen it is possible to rename the default tree by clicking on it but also to create subtrees... The complete documentation of cacti is available on the internet, www.cacti.net. 98
10. Introduction for EON update EON does not provide tool, at the moment, to do automatic update. The restoration of your databases and configuration files must be done manually. The procedure to update that you will follow is largely inspired by the documentation «tutoriel migration eon v2» written by Sébastien Fernandez. 10.1. Take backups EON generates a backup every night at 4:00 in the morning in the directory / var/archive. The syntax of the file name is year - month day. Get the last backup on your local disk with Filezilla or winscp or other.. You must have the files: EON4-cacti EON4-eonweb EON4-etc EON4-glpi if installed EON4-home EON4-lilac EON4-mysql EON4-nagiosbp EON4-ndoutils EON4-ocsweb if installed EON4-srv 10.2. New version installation Make a new installation of EON according to documentation installation. 10.3. Restoration 1. Connect on new release of EON with Filezilla or winscp or other. 2. Create directory save in directory srv 3. Upload backup files of old version 4. Connect with putty or Mobaxterm to decompress archives. 10.3.1. Postfix update 1. Uncompressing file EON4-etc.xxxx.master.tar.gz tar xvfz EON-etc.xxxx.master.tar.gz 99
2. A directory etc is created. Replace the file main.cf in /etc by the file extract of the backup. mv etc/postfix/main.cf /etc/postfix/main.cf 3. Reload postfix service to apply modification /etc/init.d/postfix reload If you have other configurations files, the process remains the same. 10.3.2. Nagios update 1. Uncompressing file EON4-srv.xxx.master.tar.gz. A directory srv is created 2. Stop nagios service /etc/init.d/nagios stop 3. Update files If you added plug-ins in your older version, then copy them into the new version cp Rup /srv/save/srv/eyesofnetwork/nagios-xxx/plugins/* /srv/eyesofnetwork/nagios/plugins/ Explications : -R : Recursive mode: It will treat subfolders in the "plug-ins" directory -u : Update mode: Add only new files -p : Keep rights If you want to copy your images of your old release of nagios. 100
cp -up /srv/save/srv/eyesofnetwork/nagios-3.0.6/share/images/logos/* /srv/eyesofnetwork/nagios/share/images/logos/ Normally rights are preserved but in case: chmod 755 R /srv/eyesofnetwork/nagios/* chown R nagios:eyesofnetwork /srv/eyesofnetwork/nagios/* We now import the mysql lilac database of the old nagios version in this version. 4. Uncompressing file sql EON4-lilac.xxxx.sql.bz2 bunzip2 EON4-lilac.xxxx.sql.bz2!!! Edit the SQL file to keep only relevant parts as hosts, services... 5. Import file in lilac BDD mysql lilac -u root --password=root66 < /srv/save/lilac.sql 6. Connect to eonweb interface (admin/admin) to launch an export in lilac. 7. Click on link Restart of job by default. 8. Verify that all equipments are in Nagios This ended the Nagios update 10.3.3. Nagvis update In EON V4.0, nagvis interface no longer allows to copy maps directly on the console. So in General, it is better use the menus to import data nagvis to re-inject its icons, forms, maps. 101
10.3.4. Cacti Update 1. First copy files images, map and/or icon of cacti/weathermap if needed cp up /srv/save/srv/eyesofnetwork/cacti/plug-ins/weathermap/images/ /srv/eyesofnetwork/cacti/plug-ins/weathermap/images/ cp up /save/srv/eyesofnetwork/cacti/plug-ins/weathermap/configs/* /srv/eyesofnetwork/cacti/plug-ins/weathermap/configs/ Copy rra files of cacti. These are the data files generated by cacti for your devices. cp up /srv/save/srv/eyesofnetwork/cacti/rra/* /srv/eyesofnetwork/cacti/rra/ 2. Uncompressing EON4-cacti bunzip2 EON4-cacti xxxx.sql.bz2!!! Edit the SQL file to keep only relevant parts as hosts, services... 3. Import file sql in cacti database mysql cacti -u root --password=root66 < /srv/save/eon4-cacti.xxx..sql 4. Connect to interface web in cacti and verify all is OK. 10.3.5. Eonweb interface update This step is necessary if you have customized the web interface (adding users, groups, or customizing the LDAP connector). 1. Uncompressing sql EON4-eonweb bunzip2 srveon-eonweb xxxx.sql.bz2!!! Edit the SQL file to keep only relevant parts as hosts, services... 102
2. Imprt sql file mysql eonweb -u root --password=root66 < /srv/save/eon4-eonweb.xxx..sql 103
11. Axis of advance To enrich this documentation it would be good that the community goes back any corrections or improvements via the forum.eyesofnetwork.com forum. Document written by: FERNANDEZ Sébastien, Translated by Emmanuelle Texeire, for EyesOfNetwork community 104