Docstoc

H4221_Administration_reseau_Dossier_architecture

Document Sample
H4221_Administration_reseau_Dossier_architecture Powered By Docstoc
					          Administration réseau : Dossier d’architecture   25 mars 2010




 A DMINISTRATION RESEAU
 Dossier d’architecture




Auteurs        H4221

               Clocher Brice

               Mao Chen

               Marechal Stanislas

               Perret Joris

               Pierrel Baptiste

               Jeatsa-Kengni Ronald

               El Gharbi Zakaria



                                                               
                                                                    COPEV
                                                               UE




H4221                                                                       1
                          Administration réseau : Dossier d’architecture                                               25 mars 2010




SOMMAIRE

Dossier d’architecture ..................................................................................................... 3
          Organisation de l'architecture ...................................................................................... 3
          Principe ......................................................................................................................... 3
          Description de la solution ............................................................................................. 4
          Mise en place de la solution d'administration ............................................................. 5
          Gestion de la politique de nommage............................................................................ 5
          Mise en place d'un système d'administration .............................................................. 8
Annexe 1 ...................................................................................................................... 12
Annexe 2 ...................................................................................................................... 14
       IPCONFIG sur la machine windows ................................................................................ 14
       IFCONFIG sur le serveur nagios ...................................................................................... 15
       NETSTAT ......................................................................................................................... 16
       Sniffer de paquet ICMP .................................................................................................. 17
       MIB du serveur nagios.................................................................................................... 19
       Traceroute sur iftpserv2 ................................................................................................. 20
Annexe 3 ...................................................................................................................... 22
       Installation de NAGIOS ................................................................................................... 22
       nagios.cfg........................................................................................................................ 24
       nsc.ini.............................................................................................................................. 57
       windows.cfg.................................................................................................................... 60
       Statut Nagios (if213-13) ................................................................................................. 64
       Critique de l'installation/utilisation de Nagios ............................................................... 64




    H4221                                                                                                                                 2
                           Administration réseau : Dossier d’architecture        25 mars 2010


DOSSIER D’ARCHITECTURE

  ORGANISATION DE L'ARCHITECTURE


  PRINCIPE




  H4221                                                                     3         3
                  Administration réseau : Dossier d’architecture                  25 mars 2010


   DESCRIPTION DE LA SOLUTION

Switch

       Des Switch sont utilises pour relier les cameras et les automates dans une sous
réseau.


Routeur

   Des routeurs sont utilises pour relier les différents sous réseaux.


Pare-feu

    Il y a un pare-feu mis en place pour contrôler l'échange entre le campus La Doua et le
réseau Renater. On va mettre également un pare-feu sur chaque entrée du site (site INSA,
site Roanne ...)


Serveur VPN

   Le VPN permet d'établir une liaison sécurisée a moindre cout (mais il ne permet pas
d'assurer une qualité de service comparable a une ligne louée dans la mesure où le réseau
physique est public, donc non garanti). Chaque site possède un serveur VPN pour que la
connexion VPN puisse être utilisée entre le site principal (site INSA) et les sites auxiliaires et
entre le client distant et les différents sites.


Serveur DNS

   Le serveur DNS permet d'établir la correspondance entre le nom de domaine et
l'adresse IP des machines d'un réseau. Un serveur DNS est mis en place sur chaque site et il
est déclaré dans un serveur de nom de domaine de niveau immédiatement supérieur (par
ex: le DNS du site INSA est déclaré dans le serveur DNS Rocad).



   Serveur DHCP

      Le serveur DHCP permet d'attribue des adresse IP automatiquement lors d'une
connexion sur le réseau. Un serveur DHCP est mis en place sur chaque site.




   H4221                                                                                       4
                 Administration réseau : Dossier d’architecture               25 mars 2010



Serveur Nagios

       Le serveur de monitoring/administration de réseau situé au site principal (site INSA)


Serveurs d'application

   Ce sont les serveurs ou on héberge les différentes applications de gestion de production
(par exemple ERP MES etc.) et le site web qui est déjà mis en place pour donner l'accès des
ressources au client distant et pour centraliser la gestion du portail de l'AIP.




  MISE EN PLACE DE LA SOLUTION D'ADMINISTRATION


  GESTION DE LA POLITIQUE DE NOMMAGE

  Définition de la politique

   //Corriger, p-e mettre le nom du site sur deux lettres. (cf. remarques de la prof)
Le nom de chaque dispositif pourra être composé du nom de département auquel il
appartient, suivi de son type et un nombre de trois chiffres. On utilise respectivement GE et
AIP pour le département Génie Electrique et le site AIP. On utilise respectivement CAM,
MU et AUT pour caméra, machine d’usinage et automate. Par exemple, pour une caméra
localisée au sein du site AIP, elle portera le nom suivant : AIPCAM001.




  H4221                                                                                   5
                                 Administration réseau : Dossier d’architecture   25 mars 2010



Organisation du service de DNS multi-domaines

Organisation globale et intégration dans les différents campus




H4221                                                                                   6
                 Administration réseau : Dossier d’architecture                25 mars 2010


   Processus de demande d'adresse / gestion des noms

   La gestion des adresses est effectuée par le serveur DHCP configuré au niveau du réseau
industriel de l'AIP. Des adresses IP fixes sont associées aux adresses MAC des périphériques
du réseau qui sont sur le réseau la majeure partie du temps. Lorsqu'une machine non
enregistrée est connectée sur le réseau le serveur va lui attribuer une adresse disponible
dans le sous réseau.



  Organisation des DNS / configuration avec les différents types d'enregistrement à
gérer

    Les machines du réseau industriel qui disposent d'une IP fixes sont enregistrées dans le
DNS avec un enregistrement double A et PTR. Les machines du réseau non industriel de
l'AIP sont enregistrées sur le DNS du campus auquel elles sont rattachées. On définit des
zones pour chaque autre campus. Ainsi les requêtes effectuées depuis le réseau industriel
qui ne sont pas résolues en local sont renvoyées vers le DNS des réseaux industriels des
autres sites.



   Mise en place de l'infrastructure DHCP

   Motivation

   Les platines n'étant pas forcément configurables aisément on utilise un serveur DHCP
pour gérer l'adressage même statique des machines. Il est aussi intéressant de permettre
une gestion dynamique de l'adressage notamment lorsque l'on déplace une plateforme de
TP d'un site à l'autre. Enfin la mise en place d'une infrastructure DHCP facilite la gestion du
DNS.



   Gestion des configurations

   Lorsqu'une machine est connectée au réseau le serveur DHCP lui attribue une adresse IP
de façon automatique. Pour chaque site on réserve une plage d'adresse pour les platines et
une plage d'adresse pour les webcams, c'est-à-dire une plage d'adresse pour chaque sous
réseau. C'est le serveur DHCP qui va ensuite effectuer les enregistrements A et PTR du
serveur DNS.




   H4221                                                                                    7
                Administration réseau : Dossier d’architecture                  25 mars 2010

  Gestion des adresses IP/MAC

  Les platines ont une adresse IP associée à leur adresse MAC.




  MISE EN PLACE D'UN SYSTEME D'ADMINISTRATION

  Principe de la solution

   Nous proposons une solution organisationnelle et technique d'administration et de
surveillance de tout le réseau industriel de l'AIP-RAO.

  La solution se décompose en deux grands axes :

      l'administration des systèmes, comprenant la surveillance du réseau, le monitoring
       des machines, et la gestion de la configuration réseau des machines ;
      l'administration des logiciels, comprenant la configuration des logiciels, serveurs ou
       clients, pour qu'ils puissent accéder aux différents dispositifs industriels, sur les
       sites de l'AIP.



   Le tableau ci-dessous récapitule, pour chaque exigence, et les solutions que nous
proposons.


  Besoin                                              Solution


  Surveillance et monitoring                          Nagios (cf. ci-dessous)


  Gestion de configuration réseau des
                                                      DHCP
machines


   Organisation de la configuration des
                                                      Tableur
logiciels




  H4221                                                                                    8
                  Administration réseau : Dossier d’architecture                 25 mars 2010

  Comparaison des différentes solutions logicielles

  Identification des critères de comparaison

        Auto-détection de la topologie (via LLDP ou autres?)
        Configuration par client ou par web
        Prix
        SNMP
        Ergonomie, simplicité d'utilisation
        Extensibilité (modules)
        Propriétaire ou open-source
        Qualité du reporting
        Qualité des alertes
        Accessibilité de la configuration et de l'évaluation des problèmes aux novices
        Résolution de problèmes
        Reconnaissance, support et évolution



  Tableau récapitulatif

    Nous n'avons consigné que les informations "crédibles" disponibles. Certains critères,
tels que la qualité du reporting, nécessiteraient des tests pour être correctement évalués.
N'ayant pas pu effectuer ces tests, nous ne pouvons fournir d'évaluation pertinente de ces
critères.


                            HiVision                    ConneXview           Nagios


  Licence                   Propriétaire                Propriétaire         Open-source


  Prix                     899.17$                -     N/C (Négociable)     Gratuit
                         2957.50$


  Ergonomie                 Bonne (Graphique)           N/C                   Moyenne
                                                                           (Terminal        et
                                                                           Graphique)


  Qualité reporting         N/C                         N/C                  Efficace


  Qualité alertes           N/C                         N/C                  Moyennement


  H4221                                                                                    9
                  Administration réseau : Dossier d’architecture                         25 mars 2010


                                                                              visibles


  Découverte réseau         Oui (LLDP)                  Oui (LLDP)               Non


   Résolution       de      Niveau 2                    Niveau 2                 Niveau 0
problèmes


    Equipements de          Oui                         N/C                      Oui
l'architecture
configurable par le
novice


   Surveillance             Oui                         N/C                      Oui
accessible au novice ?


  Protocoles               HiDiscovery, ICMP,   SNMP,                Modbus      25+ par plugins
                         SNMP v1-v3           TCP/IP


  Extensibilité             Non                        Modularité limitée    Modulaire             via
                                                    (bibliothèque      de Plugins
                                                    matériel)


   Plateforme client        Windows, Linux              Windows                  Tous (Web)
de surveillance


  Evolution                 N/C                        Propriétaire              Communauté
                                                    (patchs              et
                                                    bibliothèque)


  Reconnaissance            N/D                        Bénéficie de l'aura  Meilleur              outil
                                                    de Schneider Electric open-source


      A l'issue de ce comparatif, nous proposons de choisir la solution open-source
  Nagios, qui paraît adaptée aux besoins du client.



  H4221                                                                                           10
                 Administration réseau : Dossier d’architecture                25 mars 2010

   Organisation de la solution

   Besoins (matériels et logiciels)

   Le logiciel Nagios fonctionne sur un serveur web Linux. Sa configuration nécessite un
accès d'administrateur sur le système de fichiers. Cette raison, ajoutée à la nécessité de
pouvoir surveiller tous les serveurs du réseau, nous incite à placer Nagios sur un serveur à
part.

   Ainsi, nous aurons besoin d'une machine Debian faisant tourner la dernière version de
Nagios, ainsi qu'un accès root correctement configuré. Cette machine est dors et déjà
présente dans l'architecture générale en début de document, avec l'adresse IP
192.168.0.250.



   De plus, un serveur DHCP est nécessaire pour la configuration réseau des machines. On
préfère un serveur physique pour privilégier l'évolutivité du système.


Enfin, pour savoir comment configurer les logiciels, un logiciel de tableur sera nécessaire. Il
permettra d'établir la correspondance entre un dispositif et le site dans lequel il se trouve.
Ainsi l'administrateur (pas forcément expert en réseau) pourra déterminer comment
configurer les logiciels pour qu'ils puissent communiquer avec les dispositifs.



   Gestion des configurations

   La configuration automatique du réseau sur les machines est effectuée grâce à un
serveur DHCP.




   H4221                                                                                  11
                 Administration réseau : Dossier d’architecture              25 mars 2010

ANNEXE 1

  COMMANDE SET ALL

   Les éléments importants du paramétrage DNS sont port=53, type=A, class=IN,
timeout=2, retry=1, root=A.ROOT-SERVERS.NET., domain=insa-lyon.fr, IXFRversion=1,
srchlist=insa-lyon.fr




  RESOUDRE SERVIF-BAIE

   Pour résoudre servif-baie on n'a pas besoin du nom complet car on est sur le même sous
réseau : www.insa-lyon.fr. Son adresse est : 134.214.104.22. Pour retrouver l'IP à partir du
nom      de   la   machine       on    utilise   un    enregistrement     de     type     A.




  RESOUDRE MAIL

   Le nom de la machine qui héberge le serveur mail est dsi04.insa-lyon.fr son adresse IP
est : 134.214.182.66. L'adresse mail.univ-lyon1.fr n'existe pas. On peut en déduire que
l'université ne dispose pas d'un serveur de mail centralisé. La gestion des mails depuis
l'université        repose        sur         une          architecture       distribuée.




  TROUVER LE NOM DE 134.214.100.7

   La machine qui a pour IP : 134.214.100.7 a pour nom vieuxpop.univ-lyon1.fr. Pour
retrouver le nom de la machine à partir de son IP on utilise un enregistrement de type PTR.




  H4221                                                                                 12
                 Administration réseau : Dossier d’architecture                25 mars 2010


   RESOUDRE WWW.GOOGLE.FR

   Cette adresse est un alias pour le serveur www.l.google.com. Un autre alias pour ce
serveur est www.google.com.

   Plusieurs adresses IP correspondent au nom de domaine www.l.google.com :
209.85.227.106, 209.85.227.147, 209.85.227.99, 209.85.227.103, 209.85.227.104,
209.85.227.105. On a plusieurs adresses qui pointent chacune sur un serveur différent pour
répartir les utilisateurs en fonction de la charge sur les serveurs et pour gérer les pannes de
façon transparente pour l'utilisateur.

   La réponse ne fait pas autorité car la requête porte sur un serveur extérieur à notre
DNS. La réponse n'est pas nécessairement à jour car elle peut avoir été mise en cache.
Les types d'enregistrement mobilisés sont A et CNAME.




   ARCHITECTURE DU SERVICE D'ANNUAIRE

   Rappel sur la politique de nommage : Le nom de chaque dispositif pourra être composé
du nom de département auquel il appartient, suivi de son type et un nombre de trois
chiffres. On utilise respectivement GE et AIP pour le département Génie Electrique et le
site AIP. On utilise respectivement CAM, MU et AUT pour caméra, machine d’usinage et
automate. Par exemple, pour une caméra localisée au sein du site AIP, elle portera le nom
suivant : AIPCAM001.




   CONFIGURATION DNS

   On réserve une adresse IP publique pour chaque appareil connecté. Le DNS doit
posséder les enregistrements A et PTR pour les machines du réseau. On peut mettre en
place des alias avec des enregistrements CNAME pour certains appareils plus utilisés.




   H4221                                                                                  13
                 Administration réseau : Dossier d’architecture              25 mars 2010

ANNEXE 2

  IPCONFIG SUR LA MACHINE WINDOWS


Configuration IP de Windows

     Nom de l'hôte . . . . . . . . . . : if213-12
     Suffixe DNS principal . . . . . . : insa-lyon.fr
     Type de noud . . . . . . . . . . : Inconnu
     Routage IP activé . . . . . . . . : Oui
     Proxy WINS activé . . . . . . . . : Oui
     Liste de recherche du suffixe DNS : insa-lyon.fr
                                  insa-lyon.fr

Carte Ethernet VMware Network Adapter VMnet8:

     [...]

Carte Ethernet VMware Network Adapter VMnet1:

     [...]

Carte Ethernet Connexion au réseau local:

      Suffixe DNS propre à la connexion : insa-lyon.fr
      Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E G
igabit Ethernet NIC
      Adresse physique . . . . . . . . .: 00-24-1D-76-AD-5D
      DHCP activé. . . . . . . . . . . : Oui
      Configuration automatique activée . . . . : Oui
      Adresse IP. . . . . . . . . . . . : 134.214.105.171
      Masque de sous-réseau . . . . . . : 255.255.255.0
      Passerelle par défaut . . . . . . : 134.214.105.1
      Serveur DHCP. . . . . . . . . . . : 134.214.105.2
      Serveurs DNS . . . . . . . . . . : 134.214.182.134
                                     134.214.100.6
      Serveur WINS principal. . . . . . : 193.48.219.11
      Serveur WINS secondaire . . . . . : 193.48.219.12
      Bail obtenu . . . . . . . . . . . : lundi 15 mars 2010 06:29:54
      Bail expirant . . . . . . . . . . : lundi 15 mars 2010 14:29:54

Carte Ethernet Connexion au réseau local 2:

     [...]




  H4221                                                                               14
                   Administration réseau : Dossier d’architecture            25 mars 2010

Configuration de la machine :

         l'adresse MAC est 00-24-1D-76-AD-5D, l'adresse IP est 134.214.105.171, le
          nom est "if213-12"

         elle appartient au réseau 134.214.105.0, sa passerelle par défaut est
          134.214.105.1
         le DNS principal utilisé est "insa-lyon.fr" d'adresse 134.214.182.134 ; le DNS
          auxiliaire a pour adresse 134.214.100.6



NB : Les configurations des cartes virtuelles (VMWare) et de celle de Tornado (réseau local
2) ne sont pas détaillées car non pertinentes ici.




     IFCONFIG SUR LE SERVEUR NAGIOS

     eth0 Link encap:Ethernet HWaddr 00:50:56:98:18:7D
       inet adr:134.214.105.151 Bcast:134.214.105.255 Masque:255.255.255.0
       adr inet6: fe80::250:56ff:fe98:187d/64 Scope:Lien
       UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
       RX packets:680306 errors:0 dropped:0 overruns:0 frame:0
       TX packets:29575 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 lg file transmission:1000
       RX bytes:805883551 (768.5 MiB) TX bytes:2547870 (2.4 MiB)
       Interruption:177 Adresse de base:0x1424

lo       [...]

Configuration du serveur : l'adresse MAC est 00:50:56:98:18:7D, l'adresse IP est
134.214.105.151, le nom est "centos-nagios2". Elle appartient au même réseau que la
machine Windows.

NB : L'interface "lo" est une boucle locale non pertinente ici.




     H4221                                                                                 15
                Administration réseau : Dossier d’architecture             25 mars 2010


  NETSTAT

  NETSTAT -r
Voici la table de routage IP du noyau :
Destination Passerelle Genmask           Indic MSS Fenetre irtt Iface
134.214.105.0 *            255.255.255.0 U     00     0 eth0
169.254.0.0 *             255.255.0.0   U     00     0 eth0
default      134.214.105.1 0.0.0.0      UG     00     0 eth0

whois 169.254.0.0
OrgName: Internet Assigned Numbers Authority
OrgID: IANA
[...]

Nous passons par l'IANA (Internet Assigned Numbers Authority) autorité chargée de
l'attribution du nom de domaine et de l'adresse IP d'une source.

netstat
Connexions Internet actives (sans serveurs)
Proto Recv-Q Send-Q Local Address           Foreign Address     State
tcp     0 0 CENTOS-NAGIOS2.insa-l:47224 auth.insa-lyon.fr:ldap ESTABLISHED
[...]
tcp     0 0 CENTOS-NAGIOS2.insa-lyo:ssh if213-12.insa-lyon.f:mloadd ESTABLISHED
tcp     0 0 CENTOS-NAGIOS2.insa-lyo:ssh if213-13.ins:intuitive-edge ESTABLISHED

Nous avons 11 connexions TCP ldap activées, et deux connexions TCP ssh activées : à savoir
nous-mêmes (if213-12) et un autre groupe travaillant sur le même nagios (if213-13).




  H4221                                                                               16
                 Administration réseau : Dossier d’architecture              25 mars 2010




  SNIFFER DE PAQUET ICMP

  Analyse d'une requête ping sur IFSWITCH06 avec le logiciel Wireshark :




  Détail de la trame 897 (Echo (ping) request) :




La trame contenait 74 octets, ils sont tous parvenus à destination.
On retrouve notre adresse MAC (00-24-1D-76-AD-5D) dans le champ "Ethernet II".
Le détail du paquet IP nous donne bien notre adresse IP (134.214.105.171) comme source
et l'adresse IP du switch en destination (193.48.219.11). On retrouve le type de protocle :
ICMP.
Le détail du paquet ICMP nous donne le type du message : 8, c'est-à-dire une demande
d'ECHO (renvoi d'information). Le champ "Data", surligné en bleu dans la capture d'écran,
nous donne le contenu du paquet, à savoir une partie de l'alphabet sans signification
particulière.




  H4221                                                                                 17
                 Administration réseau : Dossier d’architecture             25 mars 2010

  Détail de la trame 902 (Echo (ping) reply) :




Cette trame est la réponse de IFSWITCH06 à notre machine.
Comme précédemment les 74 octets sont parvenus à destination (chez nous), ce que l'on a
pu observer dans la console où le ping a été tapé.
On retrouve encore les adresses IP et MAC dans les champs correspondants de
source/destination.
La différence principale se situe dans le type de paquet ICMP : 0, c'est-à-dire une réponse
d'ECHO. Le champ "Data" est le même.




  H4221                                                                                18
                Administration réseau : Dossier d’architecture   25 mars 2010


 MIB DU SERVEUR NAGIOS

 +--system(1)
|
+-- -R-- String sysDescr(1)
|     Textual Convention: DisplayString
|     Size: 0..255
+-- -R-- ObjID sysObjectID(2)
+-- -R-- TimeTicks sysUpTime(3)
| |
| +--sysUpTimeInstance(0)
|
+-- -RW- String sysContact(4)
|     Textual Convention: DisplayString
|     Size: 0..255
+-- -RW- String sysName(5)
|     Textual Convention: DisplayString
|     Size: 0..255
+-- -RW- String sysLocation(6)
|     Textual Convention: DisplayString
|     Size: 0..255
+-- -R-- INTEGER sysServices(7)
|     Range: 0..127
+-- -R-- TimeTicks sysORLastChange(8)
|     Textual Convention: TimeStamp
|
+--sysORTable(9)
  |
  +--sysOREntry(1)
    | Index: sysORIndex
    |
    +-- ---- INTEGER sysORIndex(1)
    |      Range: 1..2147483647
    +-- -R-- ObjID sysORID(2)
    +-- -R-- String sysORDescr(3)
    |      Textual Convention: DisplayString
    |      Size: 0..255
    +-- -R-- TimeTicks sysORUpTime(4)
          Textual Convention: TimeStamp




 H4221                                                                    19
                 Administration réseau : Dossier d’architecture              25 mars 2010



Le MIB est un ensemble d'informations structuré concernant le serveur nagios. La structure
est hiérarchique : les informations sont regroupées en arbre.
On a en première partie des informations de base sur le serveur : nom, location, temps
depuis la dernière mise en service (uptime). On a ensuite une table contenant une
description de différentes entrées.

Lancement du service snmp : service snmpd start

Uptime obtenu avec la commande snmpget -v 1 -c public localhost 1.3.6.1.2.1.1.3.0 :
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6257) 0:01:02.57
On obtient alors le temps écoulé depuis qu'on a lancé le service snmp, ici 1 minute et 3
secondes environ.

Contact système en cas de problème, obtenu avec la commande snmpget -v 1 -Cf -c public
localhost system.sysContact.0 :
SNMPv2-MIB::sysContact.0 = STRING: Root <root@localhost> (configure
/etc/snmp/snmp.local.conf)
On obtient l'adresse du contact système : root@localhost. Il s'agit du seul contact système,
en effet si on retape la commande avec system.sysContact.1, on obtient un message
d'erreur.



  TRACEROUTE SUR IFTPSERV2

   Commande traceroute iftpserv2 :
traceroute to iftpserv2 (134.214.104.18), 30 hops max, 40 byte packets
 1 134.214.105.1 (134.214.105.1) 3.198 ms 3.018 ms 3.021 ms
 2 iftpserv2.insa-lyon.fr (134.214.104.18) 0.407 ms 0.397 ms 0.343 ms




  H4221                                                                                    20
             Administration réseau : Dossier d’architecture   25 mars 2010

Topologie observée pour le réseau :




H4221                                                                  21
                   Administration réseau : Dossier d’architecture              25 mars 2010

ANNEXE 3

     INSTALLATION DE NAGIOS


1)
     a) ID de la machine : if213-13 / 134.214.105.172
     b) ID du serveur nagios : centos-nagios2 / 134.214.105.151


2)
  j) [root@centos-nagios2 libexec]# ./check_nt -H 134.214.105.172 -v CLIENTVERSION -p
12489
NSClient++ 0.2.5e 2006-02-08




3)
  e)
[root@centos-nagios2 etc]# ../bin/nagios -v nagios.cfg

Nagios Core 3.2.0
Copyright (c) 2009 Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-12-2009
License: GPL

Website: http://www.nagios.org
Reading configuration data...
 Read main config file okay...
Processing object config file '/usr/local/nagios/etc/objects/commands.cfg'...
Processing object config file '/usr/local/nagios/etc/objects/contacts.cfg'...
Processing object config file '/usr/local/nagios/etc/objects/timeperiods.cfg'...
Processing object config file '/usr/local/nagios/etc/objects/templates.cfg'...
Processing object config file '/usr/local/nagios/etc/objects/localhost.cfg'...
Processing object config file '/usr/local/nagios/etc/objects/windows.cfg'...
 Read object config files okay...

Running pre-flight check on configuration data...




     H4221                                                                              22
                Administration réseau : Dossier d’architecture             25 mars 2010

  Checking services...
    Checked 15 services.
Checking hosts...
    Checked 2 hosts.
Checking host groups...
    Checked 2 host groups.
Checking service groups...
    Checked 0 service groups.
Checking contacts...
    Checked 1 contacts.
Checking contact groups...
    Checked 1 contact groups.
Checking service escalations...
    Checked 0 service escalations.
Checking service dependencies...
    Checked 0 service dependencies.
Checking host escalations...
    Checked 0 host escalations.
Checking host dependencies...
    Checked 0 host dependencies.
Checking commands...
    Checked 25 commands.
Checking time periods...
    Checked 5 time periods.
Checking for circular paths between hosts...
Checking for circular host and service dependencies...
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check




  H4221                                                                             23
                 Administration réseau : Dossier d’architecture             25 mars 2010


   NAGIOS.CFG


##########################################################################
####
#
# NAGIOS.CFG - Sample Main Config File for Nagios 3.2.0
#
# Read the documentation for more information on this configuration
# file. I've provided some comments here, but things may not be so
# clear without further explanation.
#
# Last Modified: 12-14-2008
#
##########################################################################
####



# LOG FILE
# This is the main log file where service and host events are logged
# for historical purposes. This should be the first option specified
# in the config file!!!

log_file=/usr/local/nagios/var/nagios.log




# OBJECT CONFIGURATION FILE(S)
# These are the object configuration files in which you define hosts,
# host groups, contacts, contact groups, services, etc.
# You can split your object definitions across several config files
# if you wish (as shown below), or keep them all in a single config file.

# You can specify individual object config files as shown below:
cfg_file=/usr/local/nagios/etc/objects/commands.cfg
cfg_file=/usr/local/nagios/etc/objects/contacts.cfg
cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg
cfg_file=/usr/local/nagios/etc/objects/templates.cfg

# Definitions for monitoring the local (Linux) host
cfg_file=/usr/local/nagios/etc/objects/localhost.cfg

   H4221                                                                             24
                  Administration réseau : Dossier d’architecture             25 mars 2010



# Definitions for monitoring a Windows machine
cfg_file=/usr/local/nagios/etc/objects/windows.cfg

# Definitions for monitoring a router/switch
#cfg_file=/usr/local/nagios/etc/objects/switch.cfg

# Definitions for monitoring a network printer
#cfg_file=/usr/local/nagios/etc/objects/printer.cfg



# You can also tell Nagios to process all config files (with a .cfg
# extension) in a particular directory by using the cfg_dir
# directive as shown below:

#cfg_dir=/usr/local/nagios/etc/servers
#cfg_dir=/usr/local/nagios/etc/printers
#cfg_dir=/usr/local/nagios/etc/switches
#cfg_dir=/usr/local/nagios/etc/routers
#cfg_dir=/usr/local/nagios/etc/objects




# OBJECT CACHE FILE
# This option determines where object definitions are cached when
# Nagios starts/restarts. The CGIs read object definitions from
# this cache file (rather than looking at the object config files
# directly) in order to prevent inconsistencies that can occur
# when the config files are modified after Nagios starts.

object_cache_file=/usr/local/nagios/var/objects.cache




# PRE-CACHED OBJECT FILE
# This options determines the location of the precached object file.
# If you run Nagios with the -p command line option, it will preprocess
# your object configuration file(s) and write the cached config to this
# file. You can then start Nagios with the -u option to have it read
# object definitions from this precached file, rather than the standard
# object configuration files (see the cfg_file and cfg_dir options above).

   H4221                                                                              25
                 Administration réseau : Dossier d’architecture             25 mars 2010

# Using a precached object file can speed up the time needed to (re)start
# the Nagios process if you've got a large and/or complex configuration.
# Read the documentation section on optimizing Nagios to find our more
# about how this feature works.

precached_object_file=/usr/local/nagios/var/objects.precache




# RESOURCE FILE
# This is an optional resource file that contains $USERx$ macro
# definitions. Multiple resource files can be specified by using
# multiple resource_file definitions. The CGIs will not attempt to
# read the contents of resource files, so information that is
# considered to be sensitive (usernames, passwords, etc) can be
# defined as macros in this file and restrictive permissions (600)
# can be placed on this file.

resource_file=/usr/local/nagios/etc/resource.cfg




# STATUS FILE
# This is where the current status of all monitored services and
# hosts is stored. Its contents are read and processed by the CGIs.
# The contents of the status file are deleted every time Nagios
# restarts.

status_file=/usr/local/nagios/var/status.dat




# STATUS FILE UPDATE INTERVAL
# This option determines the frequency (in seconds) that
# Nagios will periodically dump program, host, and
# service status data.

status_update_interval=10




  H4221                                                                              26
                 Administration réseau : Dossier d’architecture              25 mars 2010

# NAGIOS USER
# This determines the effective user that Nagios should run as.
# You can either supply a username or a UID.

nagios_user=nagios




# NAGIOS GROUP
# This determines the effective group that Nagios should run as.
# You can either supply a group name or a GID.

nagios_group=nagios




# EXTERNAL COMMAND OPTION
# This option allows you to specify whether or not Nagios should check
# for external commands (in the command file defined below). By default
# Nagios will *not* check for external commands, just to be on the
# cautious side. If you want to be able to use the CGI command interface
# you will have to enable this.
# Values: 0 = disable commands, 1 = enable commands

check_external_commands=1




# EXTERNAL COMMAND CHECK INTERVAL
# This is the interval at which Nagios should check for external commands.
# This value works of the interval_length you specify later. If you leave
# that at its default value of 60 (seconds), a value of 1 here will cause
# Nagios to check for external commands every minute. If you specify a
# number followed by an "s" (i.e. 15s), this will be interpreted to mean
# actual seconds rather than a multiple of the interval_length variable.

# Note: In addition to reading the external command file at regularly
# scheduled intervals, Nagios will also check for external commands after
# event handlers are executed.
# NOTE: Setting this value to -1 causes Nagios to check the external
# command file as often as possible.

  H4221                                                                               27
                  Administration réseau : Dossier d’architecture            25 mars 2010



#command_check_interval=15s
command_check_interval=-1




# EXTERNAL COMMAND FILE
# This is the file that Nagios checks for external command requests.
# It is also where the command CGI will write commands that are submitted
# by users, so it must be writeable by the user that the web server
# is running as (usually 'nobody'). Permissions should be set at the
# directory level instead of on the file, as the file is deleted every
# time its contents are processed.

command_file=/usr/local/nagios/var/rw/nagios.cmd




# EXTERNAL COMMAND BUFFER SLOTS
# This settings is used to tweak the number of items or "slots" that
# the Nagios daemon should allocate to the buffer that holds incoming
# external commands before they are processed. As external commands
# are processed by the daemon, they are removed from the buffer.

external_command_buffer_slots=4096




# LOCK FILE
# This is the lockfile that Nagios will use to store its PID number
# in when it is running in daemon mode.

lock_file=/usr/local/nagios/var/nagios.lock




# TEMP FILE
# This is a temporary file that is used as scratch space when Nagios
# updates the status log, cleans the comment file, etc. This file
# is created, used, and deleted throughout the time that Nagios is
# running.

   H4221                                                                             28
                 Administration réseau : Dossier d’architecture             25 mars 2010



temp_file=/usr/local/nagios/var/nagios.tmp

# TEMP PATH
# This is path where Nagios can create temp files for service and
# host check results, etc.

temp_path=/tmp




# EVENT BROKER OPTIONS
# Controls what (if any) data gets sent to the event broker.
# Values: 0 = Broker nothing
#     -1 = Broker everything
#     <other> = See documentation

event_broker_options=-1




# EVENT BROKER MODULE(S)
# This directive is used to specify an event broker module that should
# by loaded by Nagios at startup. Use multiple directives if you want
# to load more than one module. Arguments that should be passed to
# the module at startup are seperated from the module path by a space.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# Do NOT overwrite modules while they are being used by Nagios or Nagios
# will crash in a fiery display of SEGFAULT glory. This is a bug/limitation
# either in dlopen(), the kernel, and/or the filesystem. And maybe Nagios...
#
# The correct/safe way of updating a module is by using one of these methods:
# 1. Shutdown Nagios, replace the module file, restart Nagios
# 2. Delete the original module file, move the new module file into place, restart Nagios
#
# Example:
#

  H4221                                                                                29
                  Administration réseau : Dossier d’architecture       25 mars 2010

# broker_module=<modulepath> [moduleargs]

#broker_module=/somewhere/module1.o
#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0




# LOG ROTATION METHOD
# This is the log rotation method that Nagios should use to rotate
# the main log file. Values are as follows..
#    n      = None - don't rotate the log
#    h      = Hourly rotation (top of the hour)
#    d      = Daily rotation (midnight every day)
#    w      = Weekly rotation (midnight on Saturday evening)
#    m       = Monthly rotation (midnight last day of month)

log_rotation_method=d




# LOG ARCHIVE PATH
# This is the directory where archived (rotated) log files should be
# placed (assuming you've chosen to do log rotation).

log_archive_path=/usr/local/nagios/var/archives




# LOGGING OPTIONS
# If you want messages logged to the syslog facility, as well as the
# Nagios log file set this option to 1. If not, set it to 0.

use_syslog=1




# NOTIFICATION LOGGING OPTION
# If you don't want notifications to be logged, set this value to 0.
# If notifications should be logged, set the value to 1.

log_notifications=1

   H4221                                                                        30
                 Administration réseau : Dossier d’architecture          25 mars 2010




# SERVICE RETRY LOGGING OPTION
# If you don't want service check retries to be logged, set this value
# to 0. If retries should be logged, set the value to 1.

log_service_retries=1




# HOST RETRY LOGGING OPTION
# If you don't want host check retries to be logged, set this value to
# 0. If retries should be logged, set the value to 1.

log_host_retries=1




# EVENT HANDLER LOGGING OPTION
# If you don't want host and service event handlers to be logged, set
# this value to 0. If event handlers should be logged, set the value
# to 1.

log_event_handlers=1




# INITIAL STATES LOGGING OPTION
# If you want Nagios to log all initial host and service states to
# the main log file (the first time the service or host is checked)
# you can enable this option by setting this value to 1. If you
# are not using an external application that does long term state
# statistics reporting, you do not need to enable this option. In
# this case, set the value to 0.

log_initial_states=0




# EXTERNAL COMMANDS LOGGING OPTION

   H4221                                                                          31
                 Administration réseau : Dossier d’architecture          25 mars 2010

# If you don't want Nagios to log external commands, set this value
# to 0. If external commands should be logged, set this value to 1.
# Note: This option does not include logging of passive service
# checks - see the option below for controlling whether or not
# passive checks are logged.

log_external_commands=1




# PASSIVE CHECKS LOGGING OPTION
# If you don't want Nagios to log passive host and service checks, set
# this value to 0. If passive checks should be logged, set
# this value to 1.

log_passive_checks=1




# GLOBAL HOST AND SERVICE EVENT HANDLERS
# These options allow you to specify a host and service event handler
# command that is to be run for every host or service state change.
# The global event handler is executed immediately prior to the event
# handler that you have optionally specified in each host or
# service definition. The command argument is the short name of a
# command definition that you define in your host configuration file.
# Read the HTML docs for more information.

#global_host_event_handler=somecommand
#global_service_event_handler=somecommand

# SERVICE INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" service checks when it starts monitoring. The
# default is to use smart delay calculation, which will try to
# space all service checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)! This is not a
# good thing for production, but is useful when testing the
# parallelization functionality.
#     n     = None - don't use any delay between checks

  H4221                                                                           32
                 Administration réseau : Dossier d’architecture     25 mars 2010

#    d    = Use a "dumb" delay of 1 second between checks
#    s   = Use "smart" inter-check delay calculation
#    x.xx = Use an inter-check delay of x.xx seconds

service_inter_check_delay_method=s




# MAXIMUM SERVICE CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all services should
# be completed. Default is 30 minutes.

max_service_check_spread=30




# SERVICE CHECK INTERLEAVE FACTOR
# This variable determines how service checks are interleaved.
# Interleaving the service checks allows for a more even
# distribution of service checks and reduced load on remote
# hosts. Setting this value to 1 is equivalent to how versions
# of Nagios previous to 0.0.5 did service checks. Set this
# value to s (smart) for automatic calculation of the interleave
# factor unless you have a specific reason to change it.
#     s    = Use "smart" interleave factor calculation
#     x    = Use an interleave factor of x, where x is a
#           number greater than or equal to 1.

service_interleave_factor=s




# HOST INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" host checks when it starts monitoring. The
# default is to use smart delay calculation, which will try to
# space all host checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)!
#     n     = None - don't use any delay between checks

    H4221                                                                    33
                  Administration réseau : Dossier d’architecture   25 mars 2010

#    d    = Use a "dumb" delay of 1 second between checks
#    s   = Use "smart" inter-check delay calculation
#    x.xx = Use an inter-check delay of x.xx seconds

host_inter_check_delay_method=s




# MAXIMUM HOST CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all hosts should
# be completed. Default is 30 minutes.

max_host_check_spread=30




# MAXIMUM CONCURRENT SERVICE CHECKS
# This option allows you to specify the maximum number of
# service checks that can be run in parallel at any given time.
# Specifying a value of 1 for this variable essentially prevents
# any service checks from being parallelized. A value of 0
# will not restrict the number of concurrent checks that are
# being executed.

max_concurrent_checks=0




# HOST AND SERVICE CHECK REAPER FREQUENCY
# This is the frequency (in seconds!) that Nagios will process
# the results of host and service checks.

check_result_reaper_frequency=10




# MAX CHECK RESULT REAPER TIME
# This is the max amount of time (in seconds) that a single
# check result reaper event will be allowed to run before

    H4221                                                                   34
                 Administration réseau : Dossier d’architecture        25 mars 2010

# returning control back to Nagios so it can perform other
# duties.

max_check_result_reaper_time=30




# CHECK RESULT PATH
# This is directory where Nagios stores the results of host and
# service checks that have not yet been processed.
#
# Note: Make sure that only one instance of Nagios has access
# to this directory!

check_result_path=/usr/local/nagios/var/spool/checkresults




# MAX CHECK RESULT FILE AGE
# This option determines the maximum age (in seconds) which check
# result files are considered to be valid. Files older than this
# threshold will be mercilessly deleted without further processing.

max_check_result_file_age=3600




# CACHED HOST CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous host check is considered current.
# Cached host states (from host checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to the host check logic.
# Too high of a value for this option may result in inaccurate host
# states being used by Nagios, while a lower value may result in a
# performance hit for host checks. Use a value of 0 to disable host
# check caching.


  H4221                                                                         35
                 Administration réseau : Dossier d’architecture          25 mars 2010

cached_host_check_horizon=15




# CACHED SERVICE CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous service check is considered current.
# Cached service states (from service checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to predictive dependency checks.
# Use a value of 0 to disable service check caching.

cached_service_check_horizon=15




# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of hosts when it predicts that future dependency logic test
# may be needed. These predictive checks can help ensure that your

# host dependency logic works well.
# Values:
# 0 = Disable predictive checks
# 1 = Enable predictive checks (default)

enable_predictive_host_dependency_checks=1




# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of service when it predicts that future dependency logic test
# may be needed. These predictive checks can help ensure that your
# service dependency logic works well.
# Values:
# 0 = Disable predictive checks
# 1 = Enable predictive checks (default)

enable_predictive_service_dependency_checks=1


  H4221                                                                           36
                 Administration réseau : Dossier d’architecture               25 mars 2010



# SOFT STATE DEPENDENCIES
# This option determines whether or not Nagios will use soft state
# information when checking host and service dependencies. Normally
# Nagios will only use the latest hard host or service state when
# checking dependencies. If you want it to use the latest state (regardless
# of whether its a soft or hard state type), enable this option.
# Values:
# 0 = Don't use soft state dependencies (default)
# 1 = Use soft state dependencies

soft_state_dependencies=0



# TIME CHANGE ADJUSTMENT THRESHOLDS
# These options determine when Nagios will react to detected changes
# in system time (either forward or backwards).

#time_change_threshold=900



# AUTO-RESCHEDULING OPTION
# This option determines whether or not Nagios will attempt to
# automatically reschedule active host and service checks to
# "smooth" them out over time. This can help balance the load on
# the monitoring server.
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_reschedule_checks=0



# AUTO-RESCHEDULING INTERVAL
# This option determines how often (in seconds) Nagios will
# attempt to automatically reschedule checks. This option only
# has an effect if the auto_reschedule_checks option is enabled.
# Default is 30 seconds.
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_interval=30

  H4221                                                                                37
                  Administration réseau : Dossier d’architecture       25 mars 2010



# AUTO-RESCHEDULING WINDOW
# This option determines the "window" of time (in seconds) that
# Nagios will look at when automatically rescheduling checks.
# Only host and service checks that occur in the next X seconds
# (determined by this variable) will be rescheduled. This option
# only has an effect if the auto_reschedule_checks option is
# enabled. Default is 180 seconds (3 minutes).
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_window=180




# SLEEP TIME
# This is the number of seconds to sleep between checking for system
# events and service checks that need to be run.

sleep_time=0.25




# TIMEOUT VALUES
# These options control how much time Nagios will allow various
# types of commands to execute before killing them off. Options
# are available for controlling maximum time allotted for
# service checks, host checks, event handlers, notifications, the
# ocsp command, and performance data commands. All values are in
# seconds.

service_check_timeout=60
host_check_timeout=30
event_handler_timeout=30
notification_timeout=30

ocsp_timeout=5
perfdata_timeout=5




  H4221                                                                         38
                 Administration réseau : Dossier d’architecture     25 mars 2010

# RETAIN STATE INFORMATION
# This setting determines whether or not Nagios will save state
# information for services and hosts before it shuts down. Upon
# startup Nagios will reload all saved service and host state
# information before starting to monitor. This is useful for
# maintaining long-term data on state statistics, etc, but will
# slow Nagios down a bit when it (re)starts. Since its only
# a one-time penalty, I think its well worth the additional
# startup delay.

retain_state_information=1




# STATE RETENTION FILE
# This is the file that Nagios should use to store host and
# service state information before it shuts down. The state
# information in this file is also read immediately prior to
# starting to monitor the network when Nagios is restarted.
# This file is used only if the preserve_state_information
# variable is set to 1.

state_retention_file=/usr/local/nagios/var/retention.dat




# RETENTION DATA UPDATE INTERVAL
# This setting determines how often (in minutes) that Nagios
# will automatically save retention data during normal operation.
# If you set this value to 0, Nagios will not save retention
# data at regular interval, but it will still save retention
# data before shutting down or restarting. If you have disabled
# state retention, this option has no effect.

retention_update_interval=60




  H4221                                                                      39
                 Administration réseau : Dossier d’architecture   25 mars 2010

# USE RETAINED PROGRAM STATE
# This setting determines whether or not Nagios will set
# program status variables based on the values saved in the
# retention file. If you want to use retained program status
# information, set this value to 1. If not, set this value
# to 0.

use_retained_program_state=1

# USE RETAINED SCHEDULING INFO
# This setting determines whether or not Nagios will retain
# the scheduling info (next check time) for hosts and services
# based on the values saved in the retention file. If you
# If you want to use retained scheduling info, set this
# value to 1. If not, set this value to 0.

use_retained_scheduling_info=1




# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
# The following variables are used to specify specific host and
# service attributes that should *not* be retained by Nagios during
# program restarts.
#
# The values of the masks are bitwise ANDs of values specified
# by the "MODATTR_" definitions found in include/common.h.
# For example, if you do not want the current enabled/disabled state
# of flap detection and event handlers for hosts to be retained, you
# would use a value of 24 for the host attribute mask...
# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16)
= 24

# This mask determines what host attributes are not retained
retained_host_attribute_mask=0

# This mask determines what service attributes are not retained
retained_service_attribute_mask=0




  H4221                                                                    40
                 Administration réseau : Dossier d’architecture              25 mars 2010

# These two masks determine what process attributes are not retained.
# There are two masks, because some process attributes have host and service
# options. For example, you can disable active host checks, but leave active
# service checks enabled.
retained_process_host_attribute_mask=0
retained_process_service_attribute_mask=0

# These two masks determine what contact attributes are not retained.
# There are two masks, because some contact attributes have host and
# service options. For example, you can disable host notifications for
# a contact, but leave service notifications enabled for them.
retained_contact_host_attribute_mask=0
retained_contact_service_attribute_mask=0




# INTERVAL LENGTH
# This is the seconds per unit interval as used in the
# host/contact/service configuration files. Setting this to 60 means

# that each interval is one minute long (60 seconds). Other settings
# have not been tested much, so your mileage is likely to vary...

interval_length=60




# CHECK FOR UPDATES
# This option determines whether Nagios will automatically check to
# see if new updates (releases) are available. It is recommend that you
# enable this option to ensure that you stay on top of the latest critical
# patches to Nagios. Nagios is critical to you - make sure you keep it in
# good shape. Nagios will check once a day for new updates. Data collected
# by Nagios Enterprises from the update check is processed in accordance
# with our privacy policy - see http://api.nagios.org for details.

check_for_updates=1




# BARE UPDATE CHECK

  H4221                                                                               41
                 Administration réseau : Dossier d’architecture                25 mars 2010

# This option deterines what data Nagios will send to api.nagios.org when
# it checks for updates. By default, Nagios will send information on the
# current version of Nagios you have installed, as well as an indicator as
# to whether this was a new installation or not. Nagios Enterprises uses
# this data to determine the number of users running specific version of
# Nagios. Enable this option if you do not want this information to be sent.

bare_update_check=0




# AGGRESSIVE HOST CHECKING OPTION
# If you don't want to turn on aggressive host checking features, set
# this value to 0 (the default). Otherwise set this value to 1 to
# enable the aggressive check option. Read the docs for more info
# on what aggressive host check is or check out the source code in
# base/checks.c

use_aggressive_host_checking=0




# SERVICE CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# service checks when it initially starts. If this option is
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in. Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of service checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks



execute_service_checks=1



# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# service checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_service_checks=1

  H4221                                                                                 42
                 Administration réseau : Dossier d’architecture     25 mars 2010



# HOST CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# host checks when it initially starts. If this option is
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in. Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of host checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks

execute_host_checks=1




# PASSIVE HOST CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# host checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_host_checks=1




# NOTIFICATIONS OPTION
# This determines whether or not Nagios will sent out any host or
# service notifications when it is initially (re)started.
# Values: 1 = enable notifications, 0 = disable notifications

enable_notifications=1




# EVENT HANDLER USE OPTION
# This determines whether or not Nagios will run any host or
# service event handlers when it is initially (re)started. Unless
# you're implementing redundant hosts, leave this option enabled.
# Values: 1 = enable event handlers, 0 = disable event handlers

enable_event_handlers=1




  H4221                                                                      43
                 Administration réseau : Dossier d’architecture           25 mars 2010



# PROCESS PERFORMANCE DATA OPTION
# This determines whether or not Nagios will process performance
# data returned from service and host checks. If this option is
# enabled, host performance data will be processed using the
# host_perfdata_command (defined below) and service performance
# data will be processed using the service_perfdata_command (also
# defined below). Read the HTML docs for more information on
# performance data.
# Values: 1 = process performance data, 0 = do not process performance data

process_performance_data=0




# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
# These commands are run after every host and service check is
# performed. These commands are executed only if the
# enable_performance_data option (above) is set to 1. The command
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on performance data.

#host_perfdata_command=process-host-perfdata
#service_perfdata_command=process-service-perfdata




# HOST AND SERVICE PERFORMANCE DATA FILES
# These files are used to store host and service performance data.
# Performance data is only written to these files if the
# enable_performance_data option (above) is set to 1.

#host_perfdata_file=/tmp/host-perfdata
#service_perfdata_file=/tmp/service-perfdata




  H4221                                                                            44
                 Administration réseau : Dossier d’architecture         25 mars 2010

# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
# These options determine what data is written (and how) to the
# performance data files. The templates may contain macros, special
# characters (\t for tab, \r for carriage return, \n for newline)
# and plain text. A newline is automatically added after each write
# to the performance data file. Some examples of what you can do are
# shown below.

#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECU
TIONTIME$\t$HOSTOUTPUT$\
t$HOSTPERFDATA$
#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVIC
EDESC$\t$SERVICEEXECUTIONTIME$\
t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$




# HOST AND SERVICE PERFORMANCE DATA FILE MODES
# This option determines whether or not the host and service
# performance data files are opened in write ("w") or append ("a")
# mode. If you want to use named pipes, you should use the special
# pipe ("p") mode which avoid blocking at startup, otherwise you will
# likely want the defult append ("a") mode.

#host_perfdata_file_mode=a
#service_perfdata_file_mode=a




# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
# These options determine how often (in seconds) the host and service
# performance data files are processed using the commands defined
# below. A value of 0 indicates the files should not be periodically
# processed.

#host_perfdata_file_processing_interval=0
#service_perfdata_file_processing_interval=0




  H4221                                                                          45
                 Administration réseau : Dossier d’architecture           25 mars 2010

# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
# These commands are used to periodically process the host and
# service performance data files. The interval at which the
# processing occurs is determined by the options above.

#host_perfdata_file_processing_command=process-host-perfdata-file
#service_perfdata_file_processing_command=process-service-perfdata-file



# OBSESS OVER SERVICE CHECKS OPTION
# This determines whether or not Nagios will obsess over service
# checks and run the ocsp_command defined below. Unless you're
# planning on implementing distributed monitoring, do not enable
# this option. Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over services, 0 = do not obsess (default)

obsess_over_services=0



# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
# This is the command that is run for every service check that is
# processed by Nagios. This command is executed only if the

# obsess_over_services option (above) is set to 1. The command
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ocsp_command=somecommand



# OBSESS OVER HOST CHECKS OPTION
# This determines whether or not Nagios will obsess over host
# checks and run the ochp_command defined below. Unless you're
# planning on implementing distributed monitoring, do not enable
# this option. Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over hosts, 0 = do not obsess (default)

obsess_over_hosts=0

  H4221                                                                            46
                 Administration réseau : Dossier d’architecture          25 mars 2010



# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
# This is the command that is run for every host check that is
# processed by Nagios. This command is executed only if the
# obsess_over_hosts option (above) is set to 1. The command
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ochp_command=somecommand




# TRANSLATE PASSIVE HOST CHECKS OPTION
# This determines whether or not Nagios will translate
# DOWN/UNREACHABLE passive host check results into their proper
# state for this instance of Nagios. This option is useful
# if you have distributed or failover monitoring setup. In
# these cases your other Nagios servers probably have a different
# "view" of the network, with regards to the parent/child relationship
# of hosts. If a distributed monitoring server thinks a host
# is DOWN, it may actually be UNREACHABLE from the point of
# this Nagios instance. Enabling this option will tell Nagios
# to translate any DOWN or UNREACHABLE host states it receives
# passively into the correct state from the view of this server.
# Values: 1 = perform translation, 0 = do not translate (default)

translate_passive_host_checks=0

# PASSIVE HOST CHECKS ARE SOFT OPTION
# This determines whether or not Nagios will treat passive host
# checks as being HARD or SOFT. By default, a passive host check
# result will put a host into a HARD state type. This can be changed
# by enabling this option.
# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT

passive_host_checks_are_soft=0




# ORPHANED HOST/SERVICE CHECK OPTIONS

  H4221                                                                           47
                 Administration réseau : Dossier d’architecture            25 mars 2010

# These options determine whether or not Nagios will periodically
# check for orphaned host service checks. Since service checks are
# not rescheduled until the results of their previous execution
# instance are processed, there exists a possibility that some
# checks may never get rescheduled. A similar situation exists for
# host checks, although the exact scheduling details differ a bit
# from service checks. Orphaned checks seem to be a rare
# problem and should not happen under normal circumstances.
# If you have problems with service checks never getting
# rescheduled, make sure you have orphaned service checks enabled.
# Values: 1 = enable checks, 0 = disable checks

check_for_orphaned_services=1
check_for_orphaned_hosts=1




# SERVICE FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of service results. Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_service_freshness=1




# SERVICE FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of service check results. If you have
# disabled service freshness checking, this option has no effect.

service_freshness_check_interval=60




  H4221                                                                             48
                 Administration réseau : Dossier d’architecture            25 mars 2010

# HOST FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically

# check the "freshness" of host results. Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_host_freshness=0




# HOST FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of host check results. If you have
# disabled host freshness checking, this option has no effect.

host_freshness_check_interval=60




# ADDITIONAL FRESHNESS THRESHOLD LATENCY
# This setting determines the number of seconds that Nagios
# will add to any host and service freshness thresholds that
# it calculates (those not explicitly specified by the user).

additional_freshness_latency=15




  H4221                                                                             49
                 Administration réseau : Dossier d’architecture         25 mars 2010

# FLAP DETECTION OPTION
# This option determines whether or not Nagios will try
# and detect hosts and services that are "flapping".
# Flapping occurs when a host or service changes between
# states too frequently. When Nagios detects that a
# host or service is flapping, it will temporarily suppress
# notifications for that host/service until it stops
# flapping. Flap detection is very experimental, so read
# the HTML documentation before enabling this feature!
# Values: 1 = enable flap detection
#      0 = disable flap detection (default)

enable_flap_detection=1




# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
# Read the HTML documentation on flap detection for
# an explanation of what this option does. This option
# has no effect if flap detection is disabled.

low_service_flap_threshold=5.0

high_service_flap_threshold=20.0
low_host_flap_threshold=5.0
high_host_flap_threshold=20.0




# DATE FORMAT OPTION
# This option determines how short dates are displayed. Valid options
# include:
#     us         (MM-DD-YYYY HH:MM:SS)
#     euro        (DD-MM-YYYY HH:MM:SS)
#     iso8601      (YYYY-MM-DD HH:MM:SS)
#     strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
#

date_format=us




  H4221                                                                          50
                 Administration réseau : Dossier d’architecture         25 mars 2010



# TIMEZONE OFFSET
# This option is used to override the default timezone that this
# instance of Nagios runs in. If not specified, Nagios will use
# the system configured timezone.
#
# NOTE: In order to display the correct timezone in the CGIs, you
# will also need to alter the Apache directives for the CGI path
# to include your timezone. Example:
#
# <Directory "/usr/local/nagios/sbin/">
# SetEnv TZ "Australia/Brisbane"
# ...
# </Directory>

#use_timezone=US/Mountain
#use_timezone=Australia/Brisbane




# P1.PL FILE LOCATION
# This value determines where the p1.pl perl script (used by the
# embedded Perl interpreter) is located. If you didn't compile
# Nagios with embedded Perl support, this option has no effect.

p1_file=/usr/local/nagios/bin/p1.pl




# EMBEDDED PERL INTERPRETER OPTION
# This option determines whether or not the embedded Perl interpreter

# will be enabled during runtime. This option has no effect if Nagios
# has not been compiled with support for embedded Perl.
# Values: 0 = disable interpreter, 1 = enable interpreter

enable_embedded_perl=1




  H4221                                                                          51
                 Administration réseau : Dossier d’architecture            25 mars 2010

# EMBEDDED PERL USAGE OPTION
# This option determines whether or not Nagios will process Perl plugins
# and scripts with the embedded Perl interpreter if the plugins/scripts
# do not explicitly indicate whether or not it is okay to do so. Read
# the HTML documentation on the embedded Perl interpreter for more
# information on how this option works.

use_embedded_perl_implicitly=1




# ILLEGAL OBJECT NAME CHARACTERS
# This option allows you to specify illegal characters that cannot
# be used in host names, service descriptions, or names of other
# object types.

illegal_object_name_chars=`~!$%^&*|'"<>?,()=




# ILLEGAL MACRO OUTPUT CHARACTERS
# This option allows you to specify illegal characters that are
# stripped from macros before being used in notifications, event
# handlers, etc. This DOES NOT affect macros used in service or
# host check commands.
# The following macros are stripped of the characters you specify:
#     $HOSTOUTPUT$
#     $HOSTPERFDATA$
#     $HOSTACKAUTHOR$
#     $HOSTACKCOMMENT$
#     $SERVICEOUTPUT$
#     $SERVICEPERFDATA$
#     $SERVICEACKAUTHOR$
#     $SERVICEACKCOMMENT$

illegal_macro_output_chars=`~$&|'"<>




  H4221                                                                             52
                 Administration réseau : Dossier d’architecture         25 mars 2010

# REGULAR EXPRESSION MATCHING
# This option controls whether or not regular expression matching
# takes place in the object config files. Regular expression
# matching is used to match host, hostgroup, service, and service

# group names/descriptions in some fields of various object types.
# Values: 1 = enable regexp matching, 0 = disable regexp matching

use_regexp_matching=0




# "TRUE" REGULAR EXPRESSION MATCHING
# This option controls whether or not "true" regular expression
# matching takes place in the object config files. This option
# only has an effect if regular expression matching is enabled
# (see above). If this option is DISABLED, regular expression
# matching only occurs if a string contains wildcard characters
# (* and ?). If the option is ENABLED, regexp matching occurs
# all the time (which can be annoying).
# Values: 1 = enable true matching, 0 = disable true matching

use_true_regexp_matching=0




# ADMINISTRATOR EMAIL/PAGER ADDRESSES
# The email and pager address of a global administrator (likely you).
# Nagios never uses these values itself, but you can access them by
# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
# commands.

admin_email=nagios@localhost
admin_pager=pagenagios@localhost




# DAEMON CORE DUMP OPTION
# This option determines whether or not Nagios is allowed to create
# a core dump when it runs as a daemon. Note that it is generally
# considered bad form to allow this, but it may be useful for

  H4221                                                                          53
                 Administration réseau : Dossier d’architecture           25 mars 2010

# debugging purposes. Enabling this option doesn't guarantee that
# a core file will be produced, but that's just life...
# Values: 1 - Allow core dumps
#     0 - Do not allow core dumps (default)

daemon_dumps_core=0




# LARGE INSTALLATION TWEAKS OPTION
# This option determines whether or not Nagios will take some shortcuts
# which can save on memory and CPU usage in large Nagios installations.
# Read the documentation for more information on the benefits/tradeoffs
# of enabling this option.
# Values: 1 - Enabled tweaks

#     0 - Disable tweaks (default)

use_large_installation_tweaks=0




# ENABLE ENVIRONMENT MACROS
# This option determines whether or not Nagios will make all standard
# macros available as environment variables when host/service checks
# and system commands (event handlers, notifications, etc.) are
# executed. Enabling this option can cause performance issues in
# large installations, as it will consume a bit more memory and (more
# importantly) consume more CPU.
# Values: 1 - Enable environment variable macros (default)
#      0 - Disable environment variable macros

enable_environment_macros=1




# CHILD PROCESS MEMORY OPTION
# This option determines whether or not Nagios will free memory in
# child processes (processed used to execute system commands and host/
# service checks). If you specify a value here, it will override
# program defaults.

    H4221                                                                          54
                Administration réseau : Dossier d’architecture             25 mars 2010

# Value: 1 - Free memory in child processes
#     0 - Do not free memory in child processes

#free_child_process_memory=1

# CHILD PROCESS FORKING BEHAVIOR
# This option determines how Nagios will fork child processes
# (used to execute system commands and host/service checks). Normally
# child processes are fork()ed twice, which provides a very high level
# of isolation from problems. Fork()ing once is probably enough and will
# save a great deal on CPU usage (in large installs), so you might
# want to consider using this. If you specify a value here, it will
# program defaults.
# Value: 1 - Child processes fork() twice
#      0 - Child processes fork() just once

#child_processes_fork_twice=1



# DEBUG LEVEL
# This option determines how much (if any) debugging information will
# be written to the debug file. OR values together to log multiple
# types of information.

# Values:
#     -1 = Everything
#     0 = Nothing
#     1 = Functions
#     2 = Configuration
#     4 = Process information
#     8 = Scheduled events
#     16 = Host/service checks
#     32 = Notifications
#     64 = Event broker
#     128 = External commands
#     256 = Commands
#     512 = Scheduled downtime
#     1024 = Comments
#     2048 = Macros

debug_level=0

  H4221                                                                             55
                Administration réseau : Dossier d’architecture                25 mars 2010

# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
# Values: 0 = Brief output
#      1 = More detailed
#      2 = Very detailed

debug_verbosity=1




# DEBUG FILE
# This option determines where Nagios should write debugging information.

debug_file=/usr/local/nagios/var/nagios.debug




# MAX DEBUG FILE SIZE
# This option determines the maximum size (in bytes) of the debug file. If
# the file grows larger than this size, it will be renamed with a .old
# extension. If a file already exists with a .old extension it will
# automatically be deleted. This helps ensure your disk space usage doesn't
# get out of control when debugging Nagios.

max_debug_file_size=1000000




  H4221                                                                                56
                 Administration réseau : Dossier d’architecture              25 mars 2010


  NSC.INI


[modules]
;# NSCLIENT++ MODULES
;# A list with DLLs to load at startup.
; You will need to enable some of these for NSClient++ to work.
;!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
;*                                      *
;*NOTICE!!!-YOU HAVE TO EDIT THIS*
;*                                      *
;!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
FileLogger.dll
CheckSystem.dll
CheckDisk.dll
NSClientListener.dll
NRPEListener.dll
SysTray.dll
CheckEventLog.dll
CheckHelpers.dll
;
; CheckWMI IS AN EXTREM EARLY IDEA SO DONT USE FOR PRODUCTION ENVIROMNEMTS!
;CheckWMI.dll

[Settings]
;# OBFUSCATED PASSWORD
; This is the same as the password option but here you can store the password in an
obfuscated manner.
; *NOTICE* obfuscation is *NOT* the same as encryption, someone with access to this file
can still figure out the
; password. Its just a bit harder to do it at first glance.
;obfuscated_password=Jw0KAUUdXlAAUwASDAAB
;
;# PASSWORD
; This is the password (-s) that is required to access NSClient remotely. If you leave this
blank everyone will be able to access the daemon remotly.
password=passe
;
;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to the all
daemons.

  H4221                                                                                 57
                  Administration réseau : Dossier d’architecture              25 mars 2010

; If leave this blank anyone can access the deamon remotly (NSClient still requires a valid
password).
allowed_hosts=127.0.0.1,134.214.105.172,134.214.105.151

[log]
;# LOG DEBUG
; Set to 1 if you want debug message printed in the log file (debug messages are always
printed to stdout when run with -test)
;debug=1
;
;# LOG FILE
; The file to print log statements to
;file=NSC.log
;
;# LOG DATE MASK
; The format to for the date/time part of the log entry written to file.
;date_mask=%Y-%m-%d %H:%M:%S



[NSClient]
;# NSCLIENT PORT NUMBER
; This is the port the NSClientListener.dll will listen to.
port=12489



[Check System]
;# CPU BUFFER SIZE
; Can be anything ranging from 1s (for 1 second) to 10w for 10 weeks. Notice that a larger
buffer will waste memory
; so don't use a larger buffer then you need (ie. the longest check you do +1).
;CPUBufferSize=1h
;
;# CHECK RESOLUTION
; The resolution to check values (currently only CPU).
; The value is entered in 1/10:th of a second and the default is 10 (which means ones every
second)
;CheckResolution=10




   H4221                                                                                  58
                Administration réseau : Dossier d’architecture           25 mars 2010

[NRPE]
;# NRPE PORT NUMBER
; This is the port the NRPEListener.dll will listen to.
;port=5666
;
;# COMMAND TIMEOUT
; This specifies the maximum number of seconds that the NRPE daemon will allow plug-ins
to finish executing before killing them off.
;command_timeout=60
;
;# COMMAND ARGUMENT PROCESSING
; This option determines whether or not the NRPE daemon will allow clients to specify
arguments to commands that are executed.
;allow_arguments=0
;
;# COMMAND ALLOW NASTY META CHARS
; This option determines whether or not the NRPE daemon will allow clients to specify
nasty (as in |`&><'"\[]{}) characters in arguments.
;allow_nasty_meta_chars=0
;
;# USE SSL SOCKET
; This option controls if SSL should be used on the socket.
;use_ssl=1

[NRPE Handlers]
;# COMMAND DEFINITIONS
;# Command definitions that this daemon will run.
;# Can be either NRPE syntax:
;command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
;# Or simplified syntax:
;test=c:\test.bat foo $ARG1$ bar
;check_disk1=/usr/local/nagios/libexec/check_disk -w 5 -c 10
;# Or even loopback (inject) syntax (to run internal commands)
;# This is a way to run "NSClient" commands and other internal module commands such as
check eventlog etc.
;check_cpu=inject checkCPU warn=80 crit=90 5 10 15
;check_eventlog=inject CheckEventLog Application warn.require.eventType=error
warn.require.eventType=warning critical.require.eventType=error
critical.exclude.eventType=info truncate=1024 descriptions
;check_disk_c=inject CheckFileSize ShowAll MaxWarn=1024M MaxCrit=4096M
File:WIN=c:\ATI\*.*

  H4221                                                                            59
                 Administration réseau : Dossier d’architecture          25 mars 2010

;# But be careful:
; dont_check=inject dont_check This will "loop forever" so be careful with the inject
command...
;# Check some escapings...
; check_escape=inject CheckFileSize ShowAll MaxWarn=1024M MaxCrit=4096M "File: foo
\" WIN=c:\\WINDOWS\\*.*"



  WINDOWS.CFG


##################################################################
# WINDOWS.CFG - SAMPLE CONFIG FILE FOR MONITORING A WINDOWS MACHINE
#
# Last Modified: 06-13-2007
#
# NOTES: This config file assumes that you are using the sample configuration
#     files that get installed with the Nagios quickstart guide.
#
##################################################################




###################################################################
##################################################################
#
# HOST DEFINITIONS
#
###################################################################
#################################################################

# Define a host for the Windows machine we'll be monitoring
# Change the host_name, alias, and address to fit your situation

define host{
    use      windows-server ; Inherit default values from a template
    host_name     if213-13      ; The name we're giving to this host
    alias    if213_13      ; A longer name associated with the host
    address     134.214.105.172        ; IP address of the host
    }

  H4221                                                                            60
                 Administration réseau : Dossier d’architecture                 25 mars 2010



##################################################################
##################################################################
#
# HOST GROUP DEFINITIONS
#
##################################################################
##################################################################



# Define a hostgroup for Windows machines
# All hosts that use the windows-server template will automatically be a member of this
group

define hostgroup{
    hostgroup_name windows-servers ; The name of the hostgroup
    alias     Windows Servers ; Long name of the group
    }




##################################################################
##################################################################
#
# SERVICE DEFINITIONS
#
##################################################################
##################################################################



# Create a service for monitoring the version of NSCLient++ that is installed
# Change the host_name to match the name of the host you defined above

define service{
    use            generic-service
    host_name          if213-13
    service_description NSClient++ Version
    check_command          check_nt!CLIENTVERSION
    }


  H4221                                                                                  61
                  Administration réseau : Dossier d’architecture         25 mars 2010



# Create a service for monitoring the uptime of the server
# Change the host_name to match the name of the host you defined above

define service{
    use            generic-service
    host_name          if213-13
    service_description Uptime
    check_command          check_nt!UPTIME
    }




# Create a service for monitoring CPU load
# Change the host_name to match the name of the host you defined above

define service{
    use            generic-service
    host_name          if213-13
    service_description CPU Load
    check_command          check_nt!CPULOAD!-l 5,80,90
    }




# Create a service for monitoring memory usage
# Change the host_name to match the name of the host you defined above

define service{
    use            generic-service
    host_name          if213-13
    service_description Memory Usage
    check_command          check_nt!MEMUSE!-w 80 -c 90
    }




# Create a service for monitoring C:\ disk usage
# Change the host_name to match the name of the host you defined above

define service{

  H4221                                                                           62
                Administration réseau : Dossier d’architecture           25 mars 2010

    use            generic-service
    host_name          if213-13
    service_description C:\ Drive Space
    check_command          check_nt!USEDDISKSPACE!-l c -w 80 -c 90
    }




# Create a service for monitoring the W3SVC service
# Change the host_name to match the name of the host you defined above

define service{
    use            generic-service
    host_name          if213-13
    service_description W3SVC
    check_command          check_nt!SERVICESTATE!-d SHOWALL -l W3SVC
    }




# Create a service for monitoring the Explorer.exe process
# Change the host_name to match the name of the host you defined above

define service{
    use            generic-service
    host_name          if213-13
    service_description Explorer
    check_command          check_nt!PROCSTATE!-d SHOWALL -l Explorer.exe
    }




  H4221                                                                           63
                 Administration réseau : Dossier d’architecture                25 mars 2010


  STATUT NAGIOS (IF213-13)




  CRITIQUE DE L'INSTALLATION/UTILISATION DE NAGIOS


La phase de configuration minimale de Nagios est assez facile s'il l'on est informés de la
marche à suivre. Le principe de dé-commenter des paramètres dans des fichiers de
configuration est assez habituel, mais on peut déplorer le manque d'interface HM. En
prenant un peu plus de recul, on s'aperçoit qu'une configuration non graphique,
uniquement avec des fichiers et des lignes de commandes, est cependant peu 'user-
friendly' pour des utilisateurs non informaticiens.

L'utilisation de Nagios, quant à elle, est relativement intuitive en ce qui concerne la
planification et l'exécution de tâches. Le reporting (tableaux de bord d'informations sur les
hôtes, les services ...) est aussi très facile à obtenir par le menu latéral.




  H4221                                                                                      64

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:57
posted:12/3/2011
language:French
pages:64