{"id":437,"date":"2012-04-07T12:09:20","date_gmt":"2012-04-07T10:09:20","guid":{"rendered":"http:\/\/diablo.craem.net\/wordpress\/?p=437"},"modified":"2012-04-07T12:09:20","modified_gmt":"2012-04-07T10:09:20","slug":"backup-exec-nagios-monitorizar-las-copias-parte-1","status":"publish","type":"post","link":"https:\/\/diablo.craem.net\/?p=437","title":{"rendered":"Backup Exec + Nagios; monitorizar las copias. Parte 1"},"content":{"rendered":"

Esta entrada explicar\u00e1 c\u00f3mo tener monitorizadas las copias de backup exec desde nagios. En principio parece que no tenga mucha utilidad, pero si ten\u00e9is varios clientes a monitorizar (como es mi caso, m\u00e1s de 20), tener todo unificado en una sola consola \/ web es bastante \u00e1gil.
\nPara ello, necesitaremos:
\n1\u00ba) Nagios > 3.x
\n2\u00ba) NSClient++ instalado en el servidor a monitorizar.<\/a>
\n2\u00ba) nagios_be
\n Instalaremos este ejecutable<\/em> en el servidor a monitorizar, siendo los archivos:
\n – check_be.exe<\/a>
\n – La documentaci\u00f3n de c\u00f3mo hacerlo:Check_be<\/a>
\nHe seleccionado la versi\u00f3n 3.x del Nsclient; es la que he ido probando y funciona bastante bien. Descargamos y lo instalamos en c:nagios<\/strong> del servidor a monitorizar.
\nUna vez instalado (siguiente, siguiente), editaremos el fichero c:nagiosnsc.ini y modificaremos (en negrita):
\n
\n[modules]
\nNRPEListener.dll
\nNSClientListener.dll
\nFileLogger.dll
\nCheckSystem.dll
\nCheckDisk.dll
\nCheckEventLog.dll
\nCheckHelpers.dll
\n;# NSCLIENT++ MODULES
\n;# A list with DLLs to load at startup.
\n; You will need to enable some of these for NSClient++ to work.
\n; ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
\n; * *
\n; * N O T I C E ! ! ! - Y O U H A V E T O E D I T T H I S *
\n; * *
\n; ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
\n;FileLogger.dll
\n;CheckSystem.dll
\n;CheckDisk.dll
\n;NSClientListener.dll
\n;NRPEListener.dll
\n;SysTray.dll
\n;CheckEventLog.dll
\n;CheckHelpers.dll
\n;CheckWMI.dll
\n;
\n; Script to check external scripts and\/or internal aliases.
\n;CheckExternalScripts.dll
\n;
\n; NSCA Agent if you enable this NSClient++ will talk to NSCA hosts repeatedly (so dont enable unless you want to use NSCA)
\n;NSCAAgent.dll
\n;
\n; LUA script module used to write your own \"check deamon\".
\n;LUAScript.dll
\n;
\n; RemoteConfiguration IS AN EXTREM EARLY IDEA SO DONT USE FOR PRODUCTION ENVIROMNEMTS!
\n;RemoteConfiguration.dll
\n; Check other hosts through NRPE extreme beta and probably a bit dangerous! :)
\n;NRPEClient.dll
\n; Extreamly early beta of a task-schedule checker
\n;CheckTaskSched.dll
\n[Settings]
\nuse_file=1
\nallowed_hosts=ip.del.servidor.nagios
\npassword=password<\/strong>
\n[log]
\n[NSClient]
\n;# ALLOWED HOST ADDRESSES
\n; This is a comma-delimited list of IP address of hosts that are allowed to talk to NSClient deamon.
\n; If you leave this blank the global version will be used instead.
\nallowed_hosts=ip.del.servidor.nagios<\/strong>
\n;
\n;# NSCLIENT PORT NUMBER
\n; This is the port the NSClientListener.dll will listen to.
\nport=12489<\/strong>
\n;
\n[NRPE]
\n;# NRPE PORT NUMBER
\n; This is the port the NRPEListener.dll will listen to.
\nport=5666<\/strong>
\n;
\n;# COMMAND TIMEOUT
\n; This specifies the maximum number of seconds that the NRPE daemon will allow plug-ins to finish executing before killing them off.
\n;command_timeout=60
\n;
\n;# COMMAND ARGUMENT PROCESSING
\n; This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed.
\n;allow_arguments=0
\n;
\n;# COMMAND ALLOW NASTY META CHARS
\n; This option determines whether or not the NRPE daemon will allow clients to specify nasty (as in |`&><'\"[]{}) characters in arguments.\n;allow_nasty_meta_chars=0\n;\n;# USE SSL SOCKET\n; This option controls if SSL should be used on the socket.\n;use_ssl=1\n;\n;# BIND TO ADDRESS\n;# ALLOWED HOST ADDRESSES\n; This is a comma-delimited list of IP address of hosts that are allowed to talk to NRPE deamon.\n; If you leave this blank the global version will be used instead.\nallowed_hosts=ip.del.servidor.nagios<\/strong>
\n;
\n;# SCRIPT DIRECTORY
\n; All files in this directory will become check commands.
\n; *WARNING* This is undoubtedly dangerous so use with care!
\n;script_dir=scripts
\n;
\n;# SOCKET TIMEOUT
\n; Timeout when reading packets on incoming sockets. If the data has not arrived withint this time we will bail out.
\n;socket_timeout=30
\n[Check System]
\n;# CPU BUFFER SIZE
\n; so don't use a larger buffer then you need (ie. the longest check you do +1).
\n;CPUBufferSize=1h
\n;
\n;# CHECK RESOLUTION
\n; The resolution to check values (currently only CPU).
\n; The value is entered in 1\/10:th of a second and the default is 10 (which means ones every second)
\n;CheckResolution=10
\n;
\n;# CHECK ALL SERVICES
\n; Configure how to check services when a CheckAll is performed.
\n; ...=started means services in that class *has* to be running.
\n; ...=stopped means services in that class has to be stopped.
\n; ...=ignored means services in this class will be ignored.
\n;check_all_services[SERVICE_BOOT_START]=ignored
\n;check_all_services[SERVICE_SYSTEM_START]=ignored
\n;check_all_services[SERVICE_AUTO_START]=started
\n;check_all_services[SERVICE_DEMAND_START]=ignored
\n;check_all_services[SERVICE_DISABLED]=stopped
\n[External Script]
\n;# COMMAND TIMEOUT
\n; This specifies the maximum number of seconds that the NRPE daemon will allow plug-ins to finish executing before killing them off.
\n;command_timeout=60
\n;
\n;# COMMAND ARGUMENT PROCESSING
\n; This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed.
\n;allow_arguments=0
\n;
\n;# COMMAND ALLOW NASTY META CHARS
\n; This option determines whether or not the NRPE daemon will allow clients to specify nasty (as in |`&><'\"[]{}) characters in arguments.\n;allow_nasty_meta_chars=0\n;\n;# SCRIPT DIRECTORY\n; All files in this directory will become check commands.\n; *WARNING* This is undoubtedly dangerous so use with care!\n;script_dir=c:myscriptdir\n[Script Wrappings]\nvbs=cscript.exe \/\/T:30 \/\/NoLogo scriptslibwrapper.vbs %SCRIPT% %ARGS%\nps1=cmd \/c echo scripts%SCRIPT% %ARGS%; exit($lastexitcode) | powershell.exe -command -\nbat=scripts%SCRIPT% %ARGS%\n[External Scripts]\n;check_es_long=scriptslong.bat\n;check_es_ok=scriptsok.bat\n;check_es_nok=scriptsnok.bat\n;check_vbs_sample=cscript.exe \/\/T:30 \/\/NoLogo scriptscheck_vb.vbs\n;check_powershell_warn=cmd \/c echo scriptspowershell.ps1 | powershell.exe -command -\n[External Alias]\nalias_cpu=checkCPU warn=80 crit=90 time=5m time=1m time=30s\nalias_cpu_ex=checkCPU warn=$ARG1$ crit=$ARG2$ time=5m time=1m time=30s\nalias_disk=CheckDriveSize MinWarn=10% MinCrit=5% CheckAll FilterType=FIXED\nalias_service=checkServiceState CheckAll\nalias_process=checkProcState $ARG1$=started\nalias_mem=checkMem MaxWarn=80% MaxCrit=90% ShowAll type=physical\nalias_up=checkUpTime MinWarn=1d MinWarn=1h\nalias_file_age=checkFile2 filter=out \"file=$ARG1$\" filter-written=>1d MaxWarn=1 MaxCrit=1 \"syntax=%filename% %write%\"
\nalias_file_size=checkFile2 filter=out \"file=$ARG1$\" filter-size=>$ARG2$ MaxWarn=1 MaxCrit=1 \"syntax=%filename% %size%\"
\nalias_file_size_in_dir=checkFile2 filter=out pattern=*.txt \"file=$ARG1$\" filter-size=>$ARG2$ MaxWarn=1 MaxCrit=1 \"syntax=%filename% %size%\"
\nalias_event_log_old=CheckEventLog file=application file=system filter=new filter=out MaxWarn=1 MaxCrit=1 filter-generated=>2d filter-severity==success filter-severity==informational truncate=800 unique descriptions \"syntax=%severity%: %source%: %message% (%count%)\"
\nalias_event_log_new=CheckEventLog file=application file=system MaxWarn=1 MaxCrit=1 \"filter=generated gt -2d AND severity NOT IN ('success', 'informational')\" truncate=800 unique descriptions \"syntax=%severity%: %source%: %message% (%count%)\"
\nalias_event_log=alias_event_log_new
\ncheck_ok=CheckOK Everything is fine!
\n[Wrapped Scripts]
\n;check_test_vbs=check_test.vbs \/arg1:1 \/arg2:1 \/variable:1
\n;check_test_ps1=check_test.ps1 arg1 arg2
\n;check_test_bat=check_test.bat arg1 arg2
\n;check_battery=check_battery.vbs
\n;check_printer=check_printer.vbs
\n; [includes]
\n;# The order when used is \"reversed\" thus the last included file will be \"first\"
\n;# Included files can include other files (be carefull only do basic recursive checking)
\n;
\n; myotherfile.ini
\n; real.ini
\n[NSCA Agent]
\n;# CHECK INTERVALL (in seconds)
\n; How often we should run the checks and submit the results.
\n;interval=5
\n;
\n;# ENCRYPTION METHOD
\n; This option determines the method by which the send_nsca client will encrypt the packets it sends
\n; to the nsca daemon. The encryption method you choose will be a balance between security and
\n; performance, as strong encryption methods consume more processor resources.
\n; You should evaluate your security needs when choosing an encryption method.
\n;
\n; Note: The encryption method you specify here must match the decryption method the nsca daemon uses
\n; (as specified in the nsca.cfg file)!!
\n; Values:
\n;\t0 = None\t(Do NOT use this option)
\n;\t1 = Simple XOR (No security, just obfuscation, but very fast)
\n; 2 = DES
\n; 3 = 3DES (Triple DES)
\n;\t4 = CAST-128
\n;\t6 = xTEA
\n;\t8 = BLOWFISH
\n;\t9 = TWOFISH
\n;\t11 = RC2
\n;\t14 = RIJNDAEL-128 (AES)
\n;\t20 = SERPENT
\n;encryption_method=14
\n;
\n;# ENCRYPTION PASSWORD
\n; This is the password\/passphrase that should be used to encrypt the sent packets.
\n;password=
\n;
\n;# BIND TO ADDRESS
\n; Allows you to bind server to a specific local address. This has to be a dotted ip adress not a hostname.
\n; Leaving this blank will bind to \"one\" local interface.
\n; -- not supported as of now --
\n;bind_to_address=
\n;
\n;# LOCAL HOST NAME
\n; The name of this host (if empty \"computername\" will be used.
\n;hostname=
\n;
\n;# NAGIOS SERVER ADDRESS
\n; The address to the nagios server to submit results to.
\n;nsca_host=192.168.0.1
\n;
\n;# NAGIOS SERVER PORT
\n; The port to the nagios server to submit results to.
\n;nsca_port=5667
\n;
\n;# CHECK COMMAND LIST
\n; The checks to run everytime we submit results back to nagios
\n; Any command(alias\/key) starting with a host_ is sent as HOST_COMMAND others are sent as SERVICE_COMMANDS
\n; where the alias\/key is used as service name.
\n;
\n[NSCA Commands]
\n;my_cpu_check=checkCPU warn=80 crit=90 time=20m time=10s time=4
\n;my_mem_check=checkMem MaxWarn=80% MaxCrit=90% ShowAll type=page
\n;my_svc_check=checkServiceState CheckAll exclude=wampmysqld exclude=MpfService
\n;host_check=check_ok
\n[NRPE Handlers]
\n;# COMMAND DEFINITIONS
\n;# Command definitions that this daemon will run.
\n;# Can be either NRPE syntax:
\ncommand[check_users]=\/usr\/local\/nagios\/libexec\/check_users -w 5 -c 10
\n;# Or simplified syntax:
\n;check_other=-H 192.168.0.1 -p 5666 -c remote_command -a arguments
\ncheck_cpu=inject checkCPU warn=80 crit=90 5 10 15
\nnrpe_cpu=inject checkCPU warn=80 crit=90 5 10 15
\ncheck_be=c:nagioscheck_be.exe \"c:Program FilesSymantecBackup ExecData\" \"CopiaESXi\"<\/strong>
\n;# REMOTE NRPE PROXY COMMANDS
\n; A list of commands that check other hosts.
\n; Used by the NRPECLient module
\n[NRPE Client Handlers]
\n;check_other=-H 192.168.0.1 -p 5666 -c remote_command -a arguments
\ncheck_cpu=inject checkCPU warn=80 crit=90 5 10 15
\nnrpe_cpu=inject checkCPU warn=80 crit=90 5 10 15
\ncheck_be=c:nagioscheck_be.exe \"c:Program FilesSymantecBackup ExecData\" \"CopiaESXi\"<\/strong>
\n;# LUA SCRIPT SECTION
\n; A list of all Lua scripts to load.
\n;[LUA Scripts]
\n;scriptstest.lua
\n<\/code>
\nReiniciamos el servicio de windows. Ahora copiamos el fichero check_be.exe en la carpeta que nos ha creado el instalador (c:nagios)
\nUna vez copiado, desde el servidor windows, comprobamos si funciona, ejecutando desde el terminal:
\n
\nC:nagios>check_be \"c:Program FilesSymantecBackup ExecData\" \"CopiaESXi\" -w1 -c3
\nJob: CopiaESXi, Status: Completed with exceptions, Date:5\/4\/2012<\/strong>
\nC:nagios>
\n<\/code>
\nAhora explicamos…
\nc:nagioscheck_be –> el ejecutable
\n\u00abc:Program FilesSymantecBackup ExecData\u00bb –> la ubicaci\u00f3n de los cat\u00e1logos de veritas, en mi caso, en la versi\u00f3n 2010.
\n\u00abCopiaESXi\u00bb –> el nombre que le hemos dado a la tarea dentro del backup exec
\n\u00ab-w1 -c3\u00bb –> Seg\u00fan la ayuda
\n -c :
\n Return ‘critical’ state if the last occurrence of the job is older
\n than days. This can help to determine if a scheduled job is
\n disabled, locked, paused, or any other reason.
\n -w : Same, but for ‘warning’ state
\nSeguimos…. damos por hecho que la prueba de arriba ha salido bien… ahora vamos a la parte de los ficheros del nagios<\/p>\n","protected":false},"excerpt":{"rendered":"

Esta entrada explicar\u00e1 c\u00f3mo tener monitorizadas las copias de backup exec desde nagios. En principio parece que no tenga mucha utilidad, pero si ten\u00e9is varios clientes a monitorizar (como es mi caso, m\u00e1s de 20), tener todo unificado en una sola consola \/ web es bastante \u00e1gil. Para ello, necesitaremos: 1\u00ba) Nagios > 3.x 2\u00ba) […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[31,39,102,117,197],"class_list":["post-437","post","type-post","status-publish","format-standard","hentry","category-linux","tag-backupexec","tag-check_be","tag-linux-2","tag-nagios","tag-windows"],"_links":{"self":[{"href":"https:\/\/diablo.craem.net\/index.php?rest_route=\/wp\/v2\/posts\/437","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/diablo.craem.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/diablo.craem.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/diablo.craem.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/diablo.craem.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=437"}],"version-history":[{"count":0,"href":"https:\/\/diablo.craem.net\/index.php?rest_route=\/wp\/v2\/posts\/437\/revisions"}],"wp:attachment":[{"href":"https:\/\/diablo.craem.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/diablo.craem.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/diablo.craem.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}