Announcement

Collapse
No announcement yet.

Nc_net

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Nc_net

    Bonjour, en vue de remplacer NSCLIENT++ j'ai installé NC_NET.

    Cependant, je n'arrive pas à recevoir d'information de celui-ci avec des requêtes check_nt (surveillance active donc?).

    Voici mes fichiers de configuration NC_NET :


    active_ip_accept_list.nc_net

    127.0.0.1
    192.168.0.134

    startup.cfg

    ## port - Default 1248
    ## This is the port for the active check TCP listener service.
    port 1248

    ## active_check - Enable or Disable active checks dynamically.
    ## 'false' to disable active checks
    ## If changed to false dynamically - NC_Net may wait for one last
    ## Active check before disabling.
    ## Once disabled can be re-enabled via passive configuration check:
    ## c[tab]active_check[tab]true
    active_check true

    ## passive_check
    ## 'false' to disable passive checks.
    ## This option is changeable dynamically once NC_Net has started.
    ## Restart passive checks via check_nt CONFIG command.
    ## (Only if lock_active_config was set to false)
    ## WARNING make sure to change this to true to use passive checks.
    passive_check false

    ## lock_passive_config
    ## When true NC_Net configuration cannot be changed through
    ## configuration command in passive.cfg .
    #lock_passive_config false

    ## lock_active_config
    ## When true NC_Net configuration cannot be changed
    ## through active check TCP listener port.
    lock_active_config false

    ## port_passive - Default port of the NSCA server for Nagios.
    ## Default is 5667
    ## Internal Development of NC_Net is using port 6024 so that the passive check
    ## results can be saved to a file by a second non-production NSCA server.
    #port_passive 5667

    ## host_passive
    ## Nagios Host ID for this local host. -This must match Nagios config files
    ## otherwise the check results may not be seen in Nagios.
    host_passive "NC_Net_host_ID"

    ## pass_passive
    ## Default passive check password NSCA default config does not have a password.
    #pass_passive ""

    ## pass - Default password "None". (Case sensitive)
    ## This is the password for check_nt. Check_nt default setting is "None".
    ## Change this if you explicitly changed the password of check_nt via -s.
    pass "nagios"

    ## ip_passive
    ## IP address of the NSCA daemon to send the passive checks.
    ## Default is loop back - should be set to your default NSCA/Nagios server.
    ip_passive "127.0.0.1"

    ## encrip_passive - Default is 1 for Xor.
    ## Encryption type - For Passive checks via NSCA.
    ## Only implemented encryption types are listed here.
    ## pass_passive is used with encryption in NSCA.
    ## Currently only implementing NONE and Xor -neither use pass_passive.
    ## Use External Send_NSCA (Configurable below) for a greater selection
    ## of encription types.
    ## 0 - none
    ## 1 - Xor (Default)
    ## X - not implemented yet
    #encrip_passive 1

    ## interval_passive - Default 5 minutes.
    ## Time interval in Minutes between passive checks runs.
    ## Dynamic changes to this will take place after next passive check run.
    #interval_passive 5

    ## interval_div_passive - Default is 1.
    ## Interval div passive is a divisor to the passive checks interval.
    ## The actual timer for the passive check interval is in milliseconds.
    ## This divisor is applied after the conversion of the interval to milliseconds.
    ## For example, if you wanted the interval to be 2.5 min,
    ## you can set the interval_passive to 5 and interval_div_passive to 2.
    ## Dynamic change of this will take place after next passive check run.
    #interval_div_passive 1

    ## cpu_max_interval - Default is 1 hour.
    ## Can only be changed in startup.cfg at this time.
    ## This number determins how many samples are taken for determining CPU LOAD.
    ## a sample is taken every 5 seconds for cpu_max_interval minutes.
    ## CPU Load may appear to process a time interval larger than this value,
    ## but the result will actually be calculated based on the number of samples.
    ## If CPULOAD is being check for a duration of more than one hour
    ## make sure to increase this value.
    #cpu_max_interval 60

    ## single_cpu - default is false
    ## on some single processor systems the CPULOAD is not properly collected.
    ## this may due to the performance counter not having a _total instance
    ## this variable was added for running CPULOAD bug fix on cpuload
    ## when true check counter: /Processor/% Processor Time"
    ## when false check counter: /Processor(_Total)/% Processor Time"
    #cpu_single false

    ## instead of having testrun=false in the passive config
    ## this variable will explicitly force the passive checks to
    ## try again each passive check interval despite failure of last iteration.
    ## WARNING: WHEN PASSIVE_ALWAYSON IS TRUE TESTRUN IS ALWAYS IMPLICITLY OFF.
    passive_alwayson false

    ##active timout is the port timout for TCP listener of active checks
    ##passive_timout is the timout for send_nsca
    #active_timeout 20
    #passive_timeout 10

    ## active_ip_accept_list
    ## This is to check that the IP address of the active check is located in the
    ## active_ip_accept_list.nc_net list. this list is in the config directory
    ## if the active check is comming from an IP that is not in the list when this
    ## argument is true, then the request will not be processed.
    #active_ip_accept_list false

    ## EXTERNAL SEND_NSCA
    ##
    ## Use the following variables to enable using an external send_nsca program.
    ## this was tested with the NSCA Win32Client found on NagiosExchange.
    ## make sure to set the full absolute path to the executables.
    ## path example: "C:\\send_nsca\\send_nsca.exe"
    ## set to true to enable. false to disable.
    ## if both are false then no passive checks will be sent.
    ## Keep embedded to true to use internal send_nsca
    ## set external to true to use external send_nsca
    ## functionally the data can be sent to two different NSCA servers.
    #embedded_send_nsca true
    #external_send_nsca false
    external_send_nsca_app "C:\\send_nsca\\send_nsca.exe"
    external_send_nsca_cfg "C:\\send_nsca\\send_nsca.cfg"
    external_send_nsca_ip 127.0.0.1
    #external_send_nsca_port 5667
    #external_send_nsca_timeout 10

    ## performance data format
    ## perfdata_format is a triger to allow for different performance data formats
    ## That have been preconfigured into NC_Net
    ## 0 - default - same as old check_nt
    ## 1 - internal - ShatterIT rrd format
    ## 2 - standard - per developer-guidelines - similar to UNIX equivalant plugin
    ## 3 - o.......... REquests welcom, but dependent on time constraints
    perfdata_format 2


    ## Mode is not actually a stored variable. --Causion using mode
    ## Mode should be near the last setting in this file.
    ## All settings following mode may overwrite a setting that mode set.
    ## Mode may have overwriten a setting previously set.
    ## Mode is a bitwise mask to apply several Boolean variables at once.
    ## Easy way to determine this value is to use the bellow chart - (2^n)
    ## The value you use for mode should equal the total sum of each
    ## options value that you want set to true.
    ## For example:
    ## Active check + passive check + lock_active_config all enabled:
    ## 1 + 2 + 8 = 11
    ##
    ## active_check 1
    ## passive_check 2
    ## lock_passive_config 4
    ## lock_active_config 8
    ## MYDEBUG 16
    ## testrun 32
    ##
    ## Best practices – for Passive checks using testrun.
    ## Testrun can be helpful in fine tuning the syntax and testing
    ## a new install with passive checks before putting NC_Net into production.
    ## If planning on using testrun in this way.
    ## Set mode to the desired level of the production server.
    ## set testrun to true
    ## When ready to change over to production: Change testrun to false.
    ##
    mode 9

    ## testrun when set to true will turn off send_nsca.
    ## Passive checks will process and write to passive.log.
    ## The sending over the network is disabled.
    ## Enables the debug log. (Caution: watch size of deb.log)
    ## This log is used during development and troubleshooting.
    ## interval_passive is set to 1.
    ## This sets up running passive check each minute.
    ## interval_div_passive is set to 1.
    ## No divisor to the passive interval.
    #testrun false

    ## MYDEBUG
    ## This is to turn on the debug log. (deb.log)
    ## deb.log lists the configuration applied during startup.
    ## (By default MYDEBUG is set to true at startup
    ## and then changed to false during startup via setting)
    ## MYDEBUG is primarily for developer use only.
    ## NC_Net does not publish standard DEBUG output for this debug log.
    ## The debug output is added for troubleshooting of issues as they arise.
    ## Usage of MYDEBUG and deb.log is subject to change without notice.
    ## MYDEBUG should never be left on during usage of NC_Net.
    ## It is ok to turn off MYDEBUG Dynamically.
    ## It is not ok to turn on MYDEBUG dynamically. it is inteded to be started
    ## during the startup.cfg
    MYDEBUG false


    Comme vous pouvez le voir le serveur oreon est 192.168.0.134
    NC_NET a été redémarrer aprés modification du fichier de configuration.
    Aucun firewall n'est mis en place.

    Merci de vos réponses.

  • #2
    Personne ?

    Comment


    • #3
      Désolé, pas installé NC_Net.
      J'ai installé NSClient++.

      Par contre, peux tu me dire pourquoi tu veux changer de client ?

      Comment


      • #4
        Et bien celui est parait plus pratique, il démarre en tant que service sur le PC dont pas besoin de le démarrer en ligne de commande.

        Comment


        • #5
          Originally posted by newdelirium View Post
          Et bien celui est parait plus pratique, il démarre en tant que service sur le PC dont pas besoin de le démarrer en ligne de commande.
          Ben NSClient++ aussi !?

          Faire : nsclient++ /install

          Et il s'installe en tant que service.
          Et tu as une commande du meme type pour le SysTray (je sais plus laquelle).
          J'aime bien NSClient car il est compatible NRPE...

          Comment


          • #6
            Alors la tu vien de m'apprendre un truc ops:

            Je savais pas, merci (en passant si tu à une solution pour envoyer une alerte quand un événement spécifique se produit sur windows, sa me serait utile également )

            Comment


            • #7
              Eh oui NSClient est compatible NRPE, mais NC_Net aussi ! Il a été conçu comme le successeur de NSClient et répond aux memes interrogations de check_nt, en plus de permettre la création de nouveaux checks par l'interrogation de compteurs de performance Windows. Mais sur ce point je galère pour trouver comment faire....
              J'ai testé les deux et honnêtement.... kifkif bourricot. NC_Net est ksute plus simple à installer. Clic clic clic et pas besoin de lignes de commande. Config par défaut en checks actifs, donc nickel. C'est du prêt à l'emploi ^^

              Comment


              • #8
                Existe t'il une version 64b ? Car du coté de NSClient++ ce n'est pas encore le cas...
                A surveiller, la reprise de dev de NSClient qui devient OPMonAgent :
                http://www.opservices.com.br/index.p...id=55&Itemid=0
                Il n'inclue pas encore NRPE, mais c'est prévu...

                Comment

                Working...
                X