06/02 Implantação de ferramenta de snmp para o setor de

Transcrição

UNIVERSIDADE FEDERAL DE MATO GROSSO
COORDENAÇÃO DE ENSINO DE GRADUAÇÃO EM
SISTEMAS DE INFORMAÇÃO
RELATÓRIO DE ESTÁGIO SUPERVISIONADO
IMPLANTAÇÃO DE FERRAMENTA DE SNMP PARA O
SETOR DE TECNOLOGIA DA INFORMAÇÃO DA
INFRAERO - AEROPORTO INTERNACIONAL
MARECHAL RONDON - SBCY
JULIAN FIGUERAS DORADO RODRIGUES
CUIABÁ – MT
2015
RELÁTORIO DE ESTÁGIO SUPERVISIONADO
IMPLANTAÇÃO DE FERRAMENTA DE SNMP PARA O
SETOR DE TECNOLOGIA DA INFORMAÇÃO DA
INFRAERO - AEROPORTO INTERNACIONAL
MARECHAL RONDON - SBCY
Relatório
apresentado
Instituto
de
Computação da Universidade Federal de
Mato Grosso, para obtenção do título de
Bacharel em Sistemas de Informação.
CUIABÁ – MT
2015
Relatório de Estágio Supervisionado apresentado à Coordenação do Curso de
Sistemas de Informação como uma das exigências para obtenção do título de
Bacharel em Sistemas de Informação da Universidade Federal de Mato Grosso
Aprovado por:
Prof. Nilton Hideki Takagi
Instituto de Computação
(Coordenador de Estágios)
Prof. Dr. Roberto Benedito de Oliveira Pereira
Instituto de Computação
(ORIENTADOR)
Mário Márcio de França
Tecnólogo em Redes de Computadores
(SUPERVISOR)
Prof. Dr. Luís Cézar Darienzo Alves
Intituto de Computação
(PROFESSOR CONVIDADO)
DEDICATÓRIA
A Deus graças pela possibilidade desse grande aprendizado.
À Antonielly e Letícia pelo apoio nessa etapa tão importante em minha vida.
AGRADECIMENTOS
Agradeço à Deus por tudo, em especial pela realização desse estágio
supervisionado, de suma importância dentro deste curso de Graduação em Sistemas
de Informação.
Agradeço à minha família, minhas amadas esposa Antonielly e minha filha
Letícia, por estarem sempre ao meu lado, sendo meu porto seguro. É por vocês que
estou aqui.
Agradeço à Empresa Brasileira de Infraestrutura Aeroportuária pela
oportunidade de realizar o estágio em suas dependências, nas pessoas do. Gerente
Comercial e de Logística de Carga Sr. Alexsander Leonardo Xavier: que permitiu o
estágio durante o horário de expediente; Encarregado de Atividades de Logística de
Carga Sr. Oéd Ferraz de Souza, meu chefe imediato, que me liberou para que
pudesse fazer o estágio, mesmo sabendo que isso desfalcaria a equipe, sem esse
esforço meu estágio não seria possível, meus mais profundos agradecimentos e
Encarregado de Atividades de Tecnologia da Informação Sr. Bruno Alvarenga
Teixeira, pela oportunidade desse aprendizado, principalmente pela liberdade
necessária para que eu pudesse acessar os equipamentos e realizar os procedimentos
intrínsecos ao estágio.
Agradeço também à Mario Márcio de Franca e Sandro Barros Siqueira pela
paciência e apoio nesse estágio supervisionado.
Agradeço também as pessoas de Weinne Willan Moreira Santos e Thais
Fernanda Bueno da Silva que me acompanharam nessa jornada, pela amizade e
companheirismo, que não me deixaram esmorecer diante das dificuldades.
Agradeço ao professor Roberto Benedito de Oliveira Pereira pela paciência e
incentivo, pela presteza em que me auxiliou nessa etapa.
A todos que me auxiliaram, os meus mais profundos agradecimentos.
SUMÁRIO
LISTA DE FIGURAS .......................................................................................................................... 7
LISTA DE SIGLAS E ABREVIATURAS ......................................................................................... 8
RESUMO ............................................................................................................................................ 10
1.
REVISÃO DE LITERATURA ................................................................................................ 14
1.1
REDES DE COMPUTADORES ............................................................................................. 14
1.2 MODELO OSI .............................................................................................................................. 15
1.2.1 CAMADA DE APLICAÇÃO ................................................................................................... 16
1.3 PROTOCOLOS............................................................................................................................ 17
1.3.1 PROTOCOLO SNMP............................................................................................................... 18
1.4 CABEAMENTO ESTRUTURADO ........................................................................................... 19
2.
MATERIAS, TÉCNICAS E MÉTODOS ............................................................................... 22
2.1 LOCAL DE ESTUDO .................................................................................................................. 22
2.1.1 INFRAESTRUTURA ................................................................................................................ 22
2.1.2 SERVIDOR ................................................................................................................................ 24
2.1.2.1 CONFIGURAÇÃO DE SERVIDOR .................................................................................... 25
2.1.2.2 REDES A SEREM MONITORADAS PELO SERVIDOR ................................................ 25
2.2 LEVANTAMENTO DE REQUISITOS ..................................................................................... 25
2.2.1 SOLUÇÕES ............................................................................................................................... 26
2.3 CONFIGURAÇÕES DOS HOSTS NO NAGIOS ..................................................................... 27
3.
RESULTADOS ......................................................................................................................... 31
3.1 “THE DUDE” ............................................................................................................................... 31
3.2 NAGIOS ........................................................................................................................................ 32
3.2.1 PREPARAÇÃO DO AMBIENTE ........................................................................................... 32
3.2.2 CONFIGURANDO O NAGIOS............................................................................................... 35
4.
DIFICULDADES ENCONTRADAS ...................................................................................... 48
4.1 DIFICULDADES NA CONFIGURAÇÃO DA MÁQUINA VIRTUAL ................................. 48
4.2 DIFICULDADES COM THE DUDE ......................................................................................... 49
4.3 DIFICULDADES COM NAGIOS .............................................................................................. 49
5.
CONCLUSÕES ......................................................................................................................... 50
6.
REFERÊNCIAS BIBLIOGRÁFICAS .................................................................................... 51
APÊNDICES E/OU ANEXOS .......................................................................................................... 52
7
LISTA DE FIGURAS
FIGURA 1 UMA REDE COM DOIS CLIENTES E UM SERVIDOR (TANENBAUM, 2003) ................................. 15
FIGURA 2: ILUSTRA AS CAMADAS DE REDES. (TANENBAUM, 2003)....................................................... 16
FIGURA 3: ILUSTRA COMPARAÇÃO ENTRE PROTOCOLOS HUMANOS E DE COMPUTADORES (KUROSE E
ROSS, 2006) ................................................................................................................................ 17
FIGURA 4: PORTA DA SALA DE TELECOMUNICAÇÕES ........................................................................... 23
FIGURA 5: ALGUNS PATCH PANELS DA SALA DE TELECOMUNICAÇÕES. ................................................. 23
FIGURA 6: OS TRÊS RACKS DA SALA DE TELECOMUNICAÇÕES............................................................... 23
FIGURA 7: AS SALAS DE SERVIDOR 1 E SERVIDOR 2.............................................................................. 24
FIGURA 8: IMAGEM DO SERVIDOR UTILIZADO PARA A EXECUÇÃO DO ESTÁGIO. .................................... 24
FIGURA 9: ILUSTRA DIFERENÇAS DAS VERSÕES DO NAGIOS. (NAGIOS ENTERPRISES, 2014) ................. 27
FIGURA 10: EXEMPLO DE IDENTIFICAÇÃO DAS CÂMERAS DO STVV NO SISTEMA DIGIFORT ................. 28
FIGURA 11: CONFIGURAÇÃO DOS HOSTS COMPARANDO COM A PLANILHA ............................................ 30
FIGURA 12: PLANILHA E ARQUIVO DE HOSTGROUP. .............................................................................. 30
FIGURA 13: EXIBIÇÃO DO THE DUDE. ................................................................................................... 31
FIGURA 14: GERENCIADOR DO SERVIDOR COM O RECURSO HYPER-V .................................................. 32
FIGURA 15: GERENCIADOR DO HYPER-V JÁ COM A MÁQUINA VIRTUAL INSTALADA ............................. 32
FIGURA 16: COMUTADORES DE REDE VIRTUAL .................................................................................... 33
FIGURA 17: PLACAS DE REDE VIRTUAIS ............................................................................................... 34
FIGURA 18: VERIFICAÇÃO DAS CONEXÕES DE REDE DO SERVIDOR........................................................ 34
FIGURA 19: LOGOTIPO DA INFRAERO NA INTERFACE WEB DO NAGIOS .................................................. 35
FIGURA 20: DIRETÓRIOS DOS ARQUIVOS DE HOSTGROUPS ..................................................................... 36
FIGURA 21: DIRETÓRIO SIMOVE E SEUS ARQUIVOS DE HOSTGROUPS ................................................... 36
FIGURA 22: STVV E SEUS ARQUIVOS DE HOSTGROUPS .......................................................................... 37
FIGURA 23: CONFIGURAÇÃO DE DIRETÓRIOS NO NAGIOS - SIMOVE ................................................... 37
FIGURA 24: CONFIGURAÇÃO DE DIRETÓRIOS NO NAGIOS - STVV ........................................................ 38
FIGURA 25: EXEMPLO DE CONFIGURAÇÃO DE HOSTGROUPS DO STVV DENTRO DO ARQUIVO
TEMPLATES.CFG .......................................................................................................................... 39
FIGURA 26: EXEMPLO DE CONFIGURAÇÃO DE HOSTGROUPS DO SIMOVE DENTRO DO ARQUIVO
TEMPLATES.CFG .......................................................................................................................... 40
FIGURA 27: CONFIGURAÇÃO DE HOST ................................................................................................... 41
FIGURA 28: DEFINIÇÃO DE HOSTGROUP ................................................................................................ 41
FIGURA 29: DEFINIÇÃO DE SERVIÇO...................................................................................................... 42
FIGURA 30: TELA DO PROGRAMA PUTTY COM O COMANDO DE VERIFICAÇÃO DE ERRO DO NAGIOS E
COMANDOS DE REINICIALIZAÇÃO DE SERVIÇOS. .......................................................................... 42
FIGURA 31: MONITORAMENTO DO NAGIOS ........................................................................................... 43
FIGURA 32: TELA INICIAL COM VISÃO GERAL DE MONITORAMENTO TÁTICO (TACTICAL MONITORING
OVERVIEW) .................................................................................................................................. 43
FIGURA 33: MENU DE VISUALIZAÇÃO DE MONITORAMENTO. ................................................................ 44
FIGURA 34: MENU: DETALHE DE HOST - HOST DETAIL.......................................................................... 44
FIGURA 35: INFORMAÇÃO DETALHADA DO HOST................................................................................... 45
FIGURA 36: EXIBINDO DETALHE DE SERVIÇO - SERVICE DETAIL ........................................................... 45
FIGURA 37: VISÃO GERAL DO HOSTGROUP OVERVIEW - ZOOM MÍNIMO PARA EXIBIR O MÁXIMO DE
HOSTGROUPS POSSÍVEIS. .............................................................................................................. 46
FIGURA 38: VISÃO MAIS DETALHADA DO HOSTGROUP OVERVIEW. ...................................................... 47
8
LISTA DE SIGLAS E ABREVIATURAS
ABNT
Associação Brasileira de Normas Técnicas
CPU
Central Processing Unit – Unidade Central de Processamento
Infraero
Empresa Brasileira de Infraestrutura Aeroportuária
RAM
Memória de Acesso Randômico
SBCY
Aeroporto Internacional Marechal Rondon
SICOA
Sistema de Identificação e Controle de Acesso
SIMOVE
Sistema de Monitoramento de Veículos, Equipamentos, Paletes e Cargas
SISO
Sistema Integrado de Soluções Operacionais
SISPONTO
Sistema de Ponto
SIV
Sistema de informação de Voos
SNMP
Protocolo Simples de Gerenciamento de Rede
STVV
Sistema de Televisão e Vigilância
TECA
Terminal de Carga Aérea
TECAPlus
Sistema de Gerenciamento de Cargas do TECA
ISO
Internacional Standards Organization
OSI
Open Systems Interconnection
9
10
RESUMO
O estágio supervisionado foi realizado na Empresa Brasileira de
Infraestrutura Aeroportuária - INFRAERO, localizada no Aeroporto Internacional
Marechal Rondon situado na Avenida Governador João Ponce de Arruda, Bairro
Jardim Aeroporto, Várzea Grande – MT.
Para execução desse estágio, fez-se necessário a criação de etapas para uma
melhor estruturação, etapas essas que são compostas por: Levantamento
Bibliográfico; Levantamento de Requisitos; Selecionar as ferramentas de acordo com
os requisitos; Configuração da Máquina a ser configurada para o SNMP;
Implantação das ferramentas SNMP e Testes de funcionalidades.
Dessa forma, o estágio foi realizado nas dependências do setor de
Tecnologia de Informação da Empresa Brasileira de Infraestrutura Aeroportuária,
acessando-se remotamente ou localmente (na sala de servidor) a máquina onde
propõe-se instalar e configurar o SNMP.
Como parte do embasamento teórico, foi realizada a revisão bibliográfica,
verificando conteúdo acadêmico para fundamentar a aplicação prática.
Para entender o problema foi realizado um levantamento de requisitos para
verificar as necessidades e atuação da ferramenta, e com isso ver qual sistema
atendia a problemática definida.
Configurou-se a máquina hospedeira para o SNMP, como instalação de
cabos nas interfaces ethernets e conexão nos switchs nas portas onde configurou-se
cada VLAN.
Foi instalado na máquina selecionada duas ferramentas de SNMP e
executamos testes, a primeira, o The Dude, mostrou-se inviável, escolheu-se então o
Nagios.
Testou-se tanto no The Dude, quanto no Nagios para verificação os
procedimentos de configuração, processo de instalação e recursos disponíveis.
Mediante as necessidades da INFRAERO entendo que o Nagios atende
melhor à necessidade de monitoramento das redes SIMOVE e STVV.
Finalizou-se o estágio com a exibição de resultados da instalação e testes da
ferramenta, alcançando assim, o objetivo proposto deste estágio.
11
12
INTRODUÇÃO
A Infraero, Empresa Brasileira de Infraestrutura Aeroportuária, é
responsável pela infraestrutura dos aeroportos estatais em todo o país. Essa é uma
grande responsabilidade pois inclui desde a manutenção da pista de pouso,
manutenção de equipamentos utilizados nas operações aeroportuárias (Viaturas de
apoio, ambulâncias, Ambulift, ente outros), até infraestrutura de rede, tecnologia da
informação, dispositivos conectados na rede.
Na área de tecnologia da informação divide-se em duas frentes de trabalho:
Interna e Externa. Na externa, atende aos concessionários e empresas terceirizadas
que atuam no aeroporto, sendo responsável pela infraestrutura de rede, provendo por
meio de cabeamento estruturado pontos de rede que podem ser utilizados para dados
e voz; na interna, atende a todos os dispositivos da Infraero, bem como a parte da
telefonia.
A rede da Infraero conta com diversos dispositivos para inúmeras funções,
relógios de registro de ponto, que são interligados ao Sistema de Ponto
(SISPONTO); também conta com equipamentos de Sistemas de Informações de Voo
SIV (monitores simples) e Vídeo-Wall, que são um computador com vários
monitores, formando um painel; conta com diversas câmeras que compõe o STVV,
bem como o servidor de armazenamento deste sistema; os diversos servidores;
impressoras do contrato outsourcing; dentre outros equipamentos críticos.
Tais equipamentos necessitam de um monitoramento em tempo real, para
que interrupções de funcionamento sejam detectadas e os problemas corrigidos com
maior rapidez.
O protocolo SNMP auxilia nesse monitoramento, pois com ferramentas
baseadas nele é possível monitorar dispositivos em rede em tempo real, inclusive
podendo adquirir informações sobre tempo ligado, uso de processador, memória,
armazenamento, entre outras informações em servidores. Por meio de ping, a
ferramenta desse protocolo pode verificar se o equipamento está ligado e
respondendo.
Logo, como esse protocolo pode ser utilizado para o monitoramento da rede
da INFRAERO a fim de prestar um serviço de melhor qualidade e tentar mantar ao
13
máximo a disponibilidade dos serviços providos por essa rede, o objetivo geral do
estágio foi realizar a instalação e configuração de um sistema para monitoramento de
ativos em redes, bem como controle de banda, evidenciando a aplicação de
conhecimentos adquiridos ao longo desta graduação em Sistema de Informação.
Para isso os objetivos específicos para a realização deste estágio são:

Realizar um levantamento Bibliográfico;

Fazer um levantamento de Requisitos;

Selecionar as ferramentas de acordo com os requisitos;

Configurar um servidor a ser configurada para o SNMP;

Implantar as ferramentas SNMP;

Realizar testes de funcionalidades.
A partir desta, este trabalho está organizado da seguinte forma: no Capítulo
1 é apresentada a revisão de literatura com as definições de conceitos de rede,
camadas e protocolos, aprofundando mais na Camada de Aplicação em que encontrase o Protocolo SNMP, tema deste estágio; no Capítulo 2 são apresentados os
materiais, técnicas e métodos utilizados na realização deste trabalho, tais como:
infraestrutura de rede, equipamentos utilizados e técnicas de implantação da
ferramenta utilizada, no Capítulo 3 são apresentados os resultados atingidos e no
Capítulo 4 são apresentadas as dificuldades encontras no decorrer deste trabalho. Por
fim, no Capítulo 5 é apresentada a conclusão obtida e no Capítulo 6 as referências
bibliográficas utilizadas como apoio a este trabalho.
14
1. REVISÃO DE LITERATURA
1.1
REDES DE COMPUTADORES
Com o avanço da tecnologia, Kurose e Ross (2006) relatam que a cada dia,
mais e mais dispositivos são conectados à rede mundial de computadores, conforme
pode ser visto por meio de sua transcrição abaixo.
“De browsers Web de telefones celulares a cafés que
oferecem acesso sem fio à Internet, de redes domésticas com
acesso de banda larga e infraestrutura tradicionais de TI em
ambientes de trabalho com PCs interligados em rede, carros em
rede, redes de sensores ambientais, Internet interplanetária –
quando achamos que as redes de computadores já estão
praticamente presentes em toda parte, novas aplicações começam a
ser desenvolvidas para ampliar ainda mais os alcances das redes
hoje! (...)” (Kurose e Ross, 2006)
Hoje a Internet, disponível na maioria dos lares, segundo Kurose e Ross
(2006) são classificadas como Internet Pública, contudo diferenciando das redes
privadas, mesmo que elas utilizem o mesmo protocolo. Essas redes, onde os diversos
dispositivos conectados comunicam-se entre si, criando assim, uma rede de maior,
chamado Internet, conforme será visto adiante.
“A Internet pública (...) é a rede a que normalmente nos
referimos como a Internet. Também há muitas redes privadas, tais
como redes corporativas e governamentais, cujos hospedeiros não
podem trocar mensagens com hospedeiros que estão fora da rede
privada (a menos que as mensagens passem por dispositivos
denominados firewalls, que restringem o fluxo de mensagens para
dentro e para fora da rede). Essas redes privadas são
frequentemente denominadas intranets, pois usam o mesmo tipo de
hospedeiros, roteadores, enlaces e protocolos da Internet pública.”
(Kurose e Ross, 2006)
Essa rede possibilita que vários recursos possam ser compartilhados, onde
uma máquina cliente pode acessar um banco de dados estando instalado em uma
máquina servidora remota, possibilitando assim que computadores em locais
15
diferentes, possam acessar uma mesma rede para transmissão de dados e troca de
informação, para diferentes fins.
“No mais simples dos termos, é possível imaginar que o
sistema de informações de uma empresa consiste em um ou mais
banco de dados e em algum número de funcionários que precisam
acessá-los remotamente. Nesse modelo, os dados são armazenados
em poderosos computadores chamados servidores. Com frequência
essas máquinas são instaladas e mantidas em um local central por
um administrador de sistemas. Em contraste os funcionários têm
em suas escrivaninhas máquinas mais simples chamadas clientes,
com as quais eles acessam dados remotos, por exemplo, para
incluir em planilhas eletrônicas que estão elaborando. (...) As
máquinas clientes e servidores são conectadas entre si por uma
rede, como ilustra a Figura 11.” (Tanenbaum, 2003)
Figura 1 Uma rede com dois clientes e um servidor (Tanenbaum, 2003)
Para isso, foi definido uma padronização por meio de um modelo de
referência para que todos os fabricantes e desenvolvedores pudessem seguir as
mesmas regras e conceitos, e esse modelo é o OSI, que será abordado no próximo
tópico.
1.2 Modelo OSI
Para que se tenha uma padronização nos protocolos nas camadas em uma
rede, fez-se necessário a criação do modelo OSI (Figura 2). Esse modelo, segundo
Tanenbaum (2003) baseia-se numa proposta desenvolvida pela organização ISO,
como uma tentativa de padronização internacional dos protocolos utilizados nas
1
No texto de Tanenbaum essa figura é apresentada como 1.1.
16
diversas camadas. O chamado Modelo de Referência ISO-OSI trata da interconexão
de sistemas abertos, que se comunicam com outros sistemas, por motivos de
praticidade é abreviado para Modelo OSI.
O modelo OSI tem sete camadas, identificadas na Figura 2:
Figura 2: Ilustra as camadas de redes. (Tanenbaum, 2003)
Este trabalho é focado no protocolo SNMP e por isso o enfoque dele será na
7 camada, que é a de aplicação, pois o mesmo está estruturado nessa camada, a qual
será vista adiante.
1.2.1 CAMADA DE APLICAÇÃO
O tema desse trabalho encontra-se na camada de Aplicação, que segundo
Kurose e Ross (2006) a razão de ser de uma rede de computadores são as aplicações
de rede, os protocolos de rede são projetados para suportarem as aplicações, nos
últimos 35 anos diversas aplicações de rede foram criadas, entre elas estão aplicações
de texto clássicas, que na década de 80 tornaram-se populares, tais como correio
eletrônico, acesso a computadores remotos e transferência de arquivos.
Entre elas estão as aplicações clássicas de texto, que se tornaram populares
na década de 1980: correio eletrônico, grupos de discussão, bate papo, acesso a
17
computadores remotos, transferência de arquivo, e também uma aplicação que
alcançou estrondoso sucesso em meados da década de 80: a Web.
Existem inúmeras aplicações multimídia, por exemplo o vídeo em tempo
real, videoconferência, telefonia por Internet e videoconferência. Outras duas
aplicações alcançaram grande fama, sendo elas, mensagem instantânea e
compartilhamento não hierárquico de arquivos (peer-to-peer – P2P).
Para que as diversas aplicações pudessem se comunicar, criou-se o
chamado protocolo, o qual será vista logo adiante.
1.3 PROTOCOLOS
Um protocolo é um conjunto de regras que definem como um dado pode ser
transmitido, Kurose e Ross (2006) explicam o conceito de protocolo por meio de
analogias, como em um diálogo, onde uma pessoa pergunta as horas a outrem
(Figura 3):
Figura 3: ilustra comparação entre protocolos humanos e de computadores (Kurose e Ross,
2006)
O protocolo de Camada de aplicação define como os processos de uma
aplicação em sistemas finais diferentes passam mensagem entre si, dessa forma um
protocolo de camada de aplicação define (Kurose e Ross ,2006):
 “Os tipos de mensagens trocadas, por exemplo, de requisição e
de resposta;
 A sintaxe dos vários tipos de mensagens, tais como os campos
da mensagem e como os campos são delineados;
18
 A semântica dos campos, isto é, o significado das informações
nos campos;
 Regras para determinar quando e como um processo envia
mensagens e reponde mensagens.”
1.3.1 PROTOCOLO SNMP
O protocolo em específico que se baseia o objetivo deste trabalho é o SNMP
conforme será vista abaixo.
Apesar do que o nome SNMP (protocolo simples de gerenciamento de rede)
sugere, o gerenciamento de rede na internet é mais do que apenas um protocolo para
transporte de dados de gerenciamento entre uma entidade gerenciadora e seus
agentes, dessa forma o SNMP é mais complexo que seu nome sugere. (Kurose e
Ross, 2006)
O SNMP foi herdado da (Internet Standart Managment Framework) e
remonta ao SGMP (Simple Gateway Monitoring Protocol – protocolo de
monitoramento de gateway simples). O protocolo SGMP permitiu que projetassem o
SNMP rapidamente. O SNMP está atualmente na sua versão SNMPv3, tendo
SNMPv1 e SNMPv2 como antecessores. (Kurose e Ross, 2006)
Quando se trata de gerenciamento de rede, deve-se questionar alguns
pontos, entre eles (Kurose e Ross, 2006):
 “O que está sendo monitorado (de um ponto de
semântico)? E que tipo de controle pode ser exercido
administrador de rede?
 Qual é o modelo específico das informações que
relatadas e/ou trocadas?
 Qual é o protocolo de comunicação para trocar
informações?”
vista
pelo
serão
essas
A estrutura de gerenciamento padrão da Internet é constituída de quatro
partes (Kurose e Ross, 2006):
 “Definições dos objetos de gerenciamento de rede,
conhecidos como objetos MIB. Na Estrutura de Gerenciamento de
Rede da Internet, as informações de gerenciamento são
representadas como uma coletânea de objetos gerenciados que,
juntos, formam um banco virtual de informações virtuais conhecido
como MIB. Um objeto MIB pode ser um contador, tal como um
número de datagramas IP descartados em um roteador devido a
19
erros em cabeçalhos de datagramas IP ou o número de erros de
detecção de portadora em uma placa de interface Ethernet; um
conjunto de informações descritivas, como a versão do software
que está sendo executado em um servidor DNS; informações de
estado, como se um determinado dispositivo está funcionando
corretamente; ou informações específicas sobre protocolos, como
um caminho de roteamento até um destino. Assim, os objetos MIB
definem as informações de gerenciamento mantidas por um
dispositivo gerenciado. Objetos MIB relacionados são reunidos em
módulos MIB. Em nossa analogia com uma organização humana,
a MIB define informação transportada entre a filial e a sede.
 Uma linguagem de definição de dados, conhecida como
SMI (Structure of Management Information – Estrutura de
Informação de Gerenciamento), que define os tipos de dados, um
modelo de objeto e regras para escrever e revisar informações de
gerenciamento. Objetos MIB são especificados nessa linguagem de
definição de dados. Em nossa analogia humana, a SMI é usada para
definir os detalhes do formato das informações que serão trocadas.
 Um protocolo, SNMP, para transmitir informações e
comandos entre uma entidade gerenciadora e um agente que os
executa em nome da entidade dentro de um dispositivo de rede
gerenciado.
 Capacidades de segurança e de administração. A
adição dessas capacidades representa o aprimoramento mais
importante do SNMPv3 em comparação com o SNMPv2.”
Auxiliando o gerenciamento de redes, sua arquitetura é modular, o que a
tornou melhor aplicável, com uma linguagem de definição de dados, assim como de
MIB independente de protocolo e um protocolo independente de MIB, essa
arquitetura modular foi inicialmente criada para facilitar a transição de um
gerenciamento de rede baseado no protocolo SNMP. A modularidade desse
protocolo permitiu que ele evoluísse diante das suas três revisões. (Kurose e Ross,
2006)
1.4 CABEAMENTO ESTRUTURADO
O Aeroporto de Cuiabá (SBCY) segue as normas propostas pelo método e
padrões definidos para Cabeamento Estruturado, conforme Marin (2010):
“Cabeamento estruturado é um sistema que envolve cabos
e hardware de conexão (conforme definidos em normas), capaz de
atender às necessidades de telecomunicações e TI dos usuários de
edifícios comerciais. Um sistema de cabeamento estruturado deve
20
ser projetado de modo que em cada área de trabalho qualquer
serviço de telecomunicações ou TI possa ser entregue a qualquer
usuário da rede em todo o edifício (ou edifícios). Em um sistema de
cabeamento estruturado, cada tomada instalada em uma área de
trabalho é uma tomada de telecomunicações e pode ser usada para
qualquer aplicação disponível na rede indistintamente. Em
cabeamento estruturado não há tomadas especificas para voz e para
dados. Dependendo das posições em que são conectados os patch
cords nos distribuidores de piso, uma tomada usada para voz pode
ser facilmente remanejada para um serviço de dados e vice-versa.”
Muitos profissionais confundem o conceito de cabeamento estruturado e
por isso vendem instalações ditas estruturadas, porém não passam de sistemas
independentes e isolados. (Marin, 2010)
Os cabos utilizados no cabeamento estruturado são distinguidos por Classe,
cada classe trabalha com uma frequência diferente. A classe utilizada em pequenas
redes corporativas e redes domésticas é a 5E, enquanto que no cabeamento
estruturado utiliza-se geralmente, a classe 6.
“Os parâmetros dos sistemas de cabeamento Categoria
6/Classe E (250MHz). Categoria 6 Aumentada/Classe E
Aumentada (500MHz). Categoria 7/Classe F (600MHz) e
Categoria
7
Aumentada/Classe
F
Aumentada
(em
desenvolvimento) existem para atender futuras aplicações que
requeiram larguras de banda superiores ou necessitem de sistemas
de cabeamento capazes de oferecer canais livres de ruídos e com
baixos níveis de interferência eletromagnética. Sistemas Cat. 6ª,
Cat. 7 e Cat. 7! São ótimas opções para ambientes com altos níveis
de ruídos. Se você precisa compartilhar serviços de natureza
distintas em um mesmo cabo de pares trançados dê preferência aos
sistemas Cat.7 e Cat. 7ª. Se o projeto é para cabear um data center,
prefira Cat. 6ª blindados.
O desenvolvimento recente do 10GBASE-T (10 Gigabit
Ethernet) obrigou os grupos de padronização de cabeamento a
formularem requisitos de largura de banda adicionais de cabos.
Como resultado, houve o desenvolvimento da Categoria 6ª para
cabos e hardware de conexão. A demanda por aplicações cada vez
mais rápidas é um processo contínuo e atualmente as aplicações
cada vez mais rápidas é um processo contínuo e atualmente as
aplicações a 40 Gigabits/s estão sendo testadas.” (Marin, 2010)
Conforme Marin (2010), o Cabeamento estruturado é dividido em
subsistemas, sendo eles:

Cabeamento horizontal
21

Cabeamento de backbone (dividido em backbone de campus e
backbone de edifício)

Área de Trabalho

Salas de Comunicações

Sala de Equipamentos

Infraestrutura de entrada
Ainda conforme Marin (2010) existem vários padrões (americano,
australiano, brasileiro, internacional, etc.) a terminologia pode não ser a mesma,
apesar de que em sua grande maioria os termos são coincidentes.
22
2. MATERIAS, TÉCNICAS E MÉTODOS
2.1 LOCAL DE ESTUDO
O estágio supervisionado foi realizado na Empresa Brasileira de
Infraestrutura Aeroportuária - INFRAERO, localizada no Aeroporto Internacional
Marechal Rondon situado na Avenida Governador João Ponce de Arruda, Bairro
Jardim Aeroporto, Várzea Grande – MT.
.
2.1.1 INFRAESTRUTURA
A Infraestrutura de rede é composta por cabeamento estruturado. A
topologia de rede utilizada é o formato de estrela estendida, onde o nó central fica no
prédio administrativo e nos prédios adjacentes ficam os distribuidores de edifício e
distribuidores de piso.
A sala de telecomunicações (Figura 4) é composta por três racks
apresentado nas Figura 5 e Figura 6, onde faz-se a distribuição da rede. Na Infraero
tal sala é chamada de Sala Técnica telemática.
23
Figura 4: Porta da Sala de Telecomunicações
Figura 5: Alguns Patch panels da sala de telecomunicações.
Figura 6: Os três racks da sala de telecomunicações
24
O servidor utilizado para configurar o SNMP encontra-se na sala de
equipamentos, aqui identificada como salas de Servidor 1 e Servidor 2. Conforme
vê-se na Figura 7 a sala é protegida por leitura biométrica e vigiada por STVV.
Figura 7: As salas de Servidor 1 e Servidor 2.
2.1.2 SERVIDOR
O Servidor encontra-se na sala Servidor 1, é um “HP ProLiant DL380p
Gen8” Com processador Intel® Xeon® CPU E5-2660, com 32 GB de Memória
RAM, com disco rígido com 320 GB de capacidade de armazenamento. O sistema
Operacional é o Windows Server 2012.
Figura 8: Imagem do servidor utilizado para a execução do estágio.2
2
http://www.storagereview.com/
25
2.1.2.1 CONFIGURAÇÃO DE SERVIDOR
Após a definição do sistema operacional Debian onde a ferramenta Nagios
será utilizada, fez-se necessário a configuração da máquina host para criação da
máquina virtual, para tanto habilitou-se o recurso HYPER-V do Windows Server e
criou-se uma máquina virtual, considerando a necessidade de processamento e
memória de acesso randômico (RAM), esta tem 6GB de memória RAM e um disco
virtual de 127 GB de armazenamento.
2.1.2.2 REDES A SEREM MONITORADAS PELO
SERVIDOR
O Servidor tem 4 interfaces ethernet de 1Gb, onde utiliza-se 3 delas para
monitoramento, sendo elas:

Porta 1: VLAN 10, Infraero – /20;

Porta 2: VLAN 100, SIMOVE – /24;

Porta 3: VLAN 1010, STVV – /22.
Cada VLAN compreende algumas sub-redes, VLAN Infraero, como:
Gateway; Servidores; Impressoras e Switchs; Workstation; SIV; Video-Wall e TI.
Na VLAN SIMOVE está uma Sub-rede e na VLAN STVV encontram-se
três sub-redes: Dessa forma, considerando que a rede INFRAERO já é monitorada
pelo Nagios, implementou-se um outro servidor Nagios para monitoramento das
VLANs SIMOVE e STVV. Ficando assim dois servidores Nagios.
Vale ressaltar que os switches tanto do SIMOVE quanto do STVV
encontram-se na VLAN INFRAERO, o que obrigou o servidor a também ter uma
interface de rede nessa VLAN.
2.2 LEVANTAMENTO DE REQUISITOS
26
O levantamento de requisitos foi realizado por meio de uma entrevista
informal com o Senhor Bruno Alvarenga Teixeira, Encarregado de Atividade de
Tecnologia da Informação, onde o mesmo explicitou as necessidades: É necessário
que se faça um monitoramento de ativos na rede, para que o atendimento seja
imediato. Esse levantamento é realizado em sistemas críticos (que não podem ser
interrompidos), como o SIMOVE e o STVV.
Foram apresentadas também algumas restrições: O servidor não poderia ser
formatado, perdendo a licença original, deveria seguir a política de rede da Infraero e
não poderia sobrecarrega-la, a empresa não adquirá nenhuma ferramenta para isso,
devendo-se utilizar software livres.
2.2.1 SOLUÇÕES
Após discutirmos as necessidades, foi realizado um levantamento de
ferramentas/ sistemas que potencialmente poderiam solucionar tais necessidades.
Dentre as ferramentas para o controle de ativos, encontramos The Dude e Nagios.
Nesse contexto o The Dude mostrou-se melhor aplicável, pois rodava em ambiente
Windows, então o mesmo foi instalado e começamos os testes, conforme explicado
no Resultados, o The Dude não se adequou, sendo então definido o Nagios.
O Nagios é uma ferramenta distribuída na versão paga e grátis. A versão
paga é completa, já sendo instalada em um disco virtual com sistema operacional
CentOS 6, disponibilizado no próprio site3.
O próprio sítio (Figura 9) oferece uma versão no Nagios grátis para Linux,
utilizamos esta versão rodando em uma máquina virtual.
3
http://www.nagios.org
27
Figura 9: Ilustra diferenças das versões do Nagios. (Nagios Enterprises, 2014)
Definido a ferramenta Nagios versão 4.0.8 para Linux, definiu-se que a
distribuição Debian 4encaixar-se-ia melhor para a configuração. A instalação foi feita
conforme Anexo 1.
2.3 CONFIGURAÇÕES DOS HOSTS NO NAGIOS
A configuração do Nagios é feita incluindo em arquivos com extensão
“.cfg”, dessa forma, utilizamos o programa “SSH Secure File Transfer Client 5” para
ter acesso remotamente aos arquivos de configuração do Nagios.
Para edição utilizei o aplicativo Notepad++6, que é um editor de texto com
notação voltada para programação, para auxiliar na indentação dos arquivos.
4
5
(Debian - Software in the Public Interest, 2014)
(SSH Communications Security Corp)
28
Para comandos dentro do Linux utilizei o programa PuTTY7 para emitir
comandos, tais como reiniciar serviços e compilar os arquivos de configuração.
Foi definido que os hosts que não fossem servidores (sub-rede 17) e switchs
(sub-rede 18) seriam monitorados, para tanto, foi disponibilizado pelo encarregado
duas planilhas (uma para o SIMOVE, outra para o STVV) contendo a identificação
dos equipamentos, como nome, ip, local, entre outros dados8.
Como as câmeras do STVV são separadas fisicamente por locais, na
documentação também foram separadas dessa forma.
Dito isso, o Nagios permite que se crie hostgroups, que são basicamente
agrupamentos de hosts, a identificação desde ficou na forma de sigla utilizada
anteriormente no sistema (Figura 10).
Figura 10: Exemplo de identificação das câmeras do STVV no sistema Digifort 9
Para um melhor monitoramento, o Nagios deve respeitar essa
documentação, então criou-se os 19 hostgroups com base na localização conforme:
6

Teca Nacional - TECANACIONAL

Seção Contra Incêndio - SCI

Terminal de Aviação Geral 1 - TAG1

Link ao Vivo - LAV
(Notepad++ team)
(Tathan)
8
Por motivos de segurança não pude incluir neste relatório as referidas planilhas.
9
Sistema Digifort é o sistema utilizado no STVV para exibição, gravação, gerenciamento de imagens
entre outros. Digifort Enterprise Surveillance Client - versão 6.7.1.
7
29

Manutenção - MNT

Teca Internacional - TIL

Via de Acesso aos Hangares - VAH

Terminal de Aviação Geral 2 - tag2

Hangaretes - HGS

Central de utilidades - CUT

Postes de Iluminação do Pátio - PIP

Postes Cerca Operacional - PCO

Terminal de Passageiros - TPS

Administração - ADM

Castelo Principal - CPL

Estação de Tratamento de Esgoto - ETE

Terminal de Passageiros - Térreo - TPS-TER

Terminal de Passageiros - Superior - TPS-SUP

Terminal de Passageiros - Cobertura - TPS-COB
Os equipamentos do SIMOVE também obedeciam esse critério sendo
separados em 8 hostgroups:

PÁTIO - SIMOVE-PATIO

ÁREA 2 - SIMOVE-AREA2

ÁREA 3 - SIMOVE-AREA3

CERCA OPERACIONAL - SIMOVE-CERC-OP ARQUIVO

LIMITE NORTE - SIMOVE-NORTE

PORTÃO A - SIMOVE-PORTAO-A

TECA NACIONAL - SIMOVE-TNL

TECA INTERNACIONAL - SIMOVE-TECAINTERNACIONAL
Para evitar problemas com endereçamento e identificação errados eu
utilizava a planilha aberta junto do Notepad++ para realizar a verificação enquanto
fazia a inclusão conforme Figura 11 e Figura 12.
30
Figura 11: Configuração dos hosts comparando com a planilha
Figura 12: Planilha e arquivo de hostgroup.
A inclusão dos arquivos no diretório do Nagios foi realizada por meio do
programa SSH File Transfer Client, conforme exibido nos resultados.
Com o Nagios configurado e os hosts inseridos, vamos agora ao resultado.
31
3. RESULTADOS
3.1 “THE DUDE”
O “The Dude” é uma ferramenta que permite o SNMP inclusive em
máquinas clientes, fazendo uma varredura de todos os equipamentos em rede. Porém
ao escolher uma determinada sub-rede para que ele fazer a varredura, o sistema
verificava todas as sub-redes, ao verificar em fóruns e sites, alguns afirmaram que a
varredura automática era imprecisa, e a melhor solução era inserir manualmente os
dispositivos da rede no sistema.
Considerando que o Nagios já estava sendo utilizado para gerenciar a rede
Infraero, e que o The Dude (Figura 13) não mostrou-se tão ágil quanto
imaginávamos, passamos então ao Nagios.
Figura 13: Exibição do The Dude.
32
3.2 NAGIOS
3.2.1 PREPARAÇÃO DO AMBIENTE
Para preparar o ambiente do servidor, foi configurado no Windows Server
2012 o recurso de Hyper-V (Figura 14).
Figura 14: Gerenciador do Servidor com o recurso Hyper-V
O próprio recurso acessou a imagem digital do disco de instalação do
Debian 7.7 e foi instalado na máquina virtual (Figura 15).
Figura 15: Gerenciador do Hyper-V já com a máquina virtual instalada
33
Após a instalação utilizou-se o comando “apt-get update” para atualização
dos repositórios do sistema, foi feito também a criação de comutadores de rede
(Figura 16), onde fez-se uma ponte entre as placas de rede virtuais e as placas de rede
física, após a criação dos comutadores, fez-se a inclusão de placas de redes virtuais
na máquina virtual onde rodará o Nagios. Dessa forma, primeiro cria-se os
comutadores e após isso na máquina virtual cria-se placas de redes virtuais que
utilizarão esses comutadores, para que o Nagios na máquina virtual possa acessar a
rede física e assim poder realizar o monitoramento (Figura 17).
Figura 16: Comutadores de Rede Virtual
34
Figura 17: Placas de Rede Virtuais
Acessando a máquina virtual via SSH, utilizou-se o comando route e
verificar as conexões do servidor (Figura 18):
Figura 18: Verificação das conexões de rede do servidor.
35
Após isso foi instalado o sistema Nagios nesta máquina virtual, conforme
Anexo 1.
3.2.2 CONFIGURANDO O NAGIOS
Após a instalação foi realizada a configuração das imagens no diretório
“shared” onde fica a interface gráfica do Nagios, por meio de web, para que na
interface web do Nagios exibisse o logo da Infraero, conforme Figura 19Figura 19:
Logotipo da Infraero na interface web do Nagios:
Figura 19: Logotipo da Infraero na interface web do Nagios
Realizei a configuração em todos os 27 arquivos de hostgroups, destes
sendo 451 hosts do STVV e 74 do SIMOVE.
Para se criar esses hostgroups era necessário criar um arquivo para cada
hostgroup com as configurações que será vista adiante. Por uma questão de
organização criei dois diretórios (Figura 20) para salvar os arquivos dos hostgroups,
um com o nome “simove” (Figura 21) e outro com nome “stvv” (Figura 22).
36
Figura 20: Diretórios dos arquivos de hostgroups
Figura 21: diretório SIMOVE e seus arquivos de hostgroups
37
Figura 22: STVV e seus arquivos de hostgroups
Após a criação dos diretórios inclui-se dentro do arquivo nagios.cfg os
endereços de cada hostgroup conforme Figura 23:
Figura 23: Configuração de diretórios no Nagios - SIMOVE
38
Figura 24: Configuração de diretórios no Nagios - STVV
39
Feito a inclusão dos diretórios dos hostgroups no nagios.cfg, agora há de se
incluir dentro do arquivo templates.cfg a configuração de cada hostgroup. Conforme
Figura 25:
Figura 25: Exemplo de configuração de hostgroups do STVV dentro do arquivo templates.cfg
40
Figura 26: Exemplo de configuração de hostgroups do SIMOVE dentro do arquivo templates.cfg
Tendo criado os diretórios, tendo incluído os endereços dos arquivos de
houstgroups no nagios.cfg e tendo definidos os hostgroups no arquivo templates.cfg,
deve-se agora realizar a inserção de cada host e serviço dentro do arquivo de
hostgroup. Basicamente cada arquivo tem a seguinte configuração:

Definição de host

Definição de hostgroup e

Definição de serviços.
Para definição de host é necessário definir hostgroup o qual pertence no
campo use, a identificação do host no campo host_name, o nome (alcunha) do host e
seu endereço ip conforme Erro! Fonte de referência não encontrada.:
41
Figura 27: Configuração de host
Para uma melhor compreensão da configuração inclui nos comentários
informações que achei pertinente, como a quantidade de hosts, a abrangência de ips,
em hostgroups com mais de 20 hosts, separei a cada 10 itens.
Na definição de hostgroup inclui-se a identificação e um nome conforme
Figura 28:
Figura 28: Definição de hostgroup
Na configuração de serviços inseriu-se os serviços que deverão ser
monitorados nos hosts (Figura 29). Como se quer somente verificar se o dispositivo
está operante, então habilitamos o ping, porém verificou-se a capacidade e uso disco
rígido, o uso de memória RAM ou a porcentagem de utilização do processador, por
exemplo. Estes últimos excelentes para gerenciamento de servidores. Para tanto fazse necessário a utilização do programa NSClient++10 nos hosts a serem gerenciados.
10
http://www.nsclient.org/
42
Figura 29: Definição de serviço
Após isso há de se utilizar o PuTTY para acessar remotamente o servidor
onde está o Nagios e realizar o teste de erro, para tanto faz-se necessário o comando
“/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg” que fará uma
verificação no arquivo nagios.cfg e suas dependências (Erick, 2011).
Figura 30: Tela do programa PuTTY com o comando de verificação de erro do Nagios e
comandos de reinicialização de serviços.
Conforme exibido na figura acima, ao realizar o comando de verificação de
erros do Nagios e o mesmo não encontrar erros e warnings deve-se reiniciar os
serviços do Nagios e Apache com os comandos “service nagios restart” e “service
apache2 restart”.
43
Nota-se no Nagios os hosts conectados, conforme Figura 31:
Figura 31: Monitoramento do Nagios
Figura 32: Tela inicial com Visão Geral de Monitoramento Tático (Tactical Monitoring
Overview)
Ao rodar o Nagios (Figura 32), agora exibe todos os dispositivos que
monitora-se. Podendo verificar com detalhes os hosts, os serviços, hostgroups entre
outros.
Conforme Figura 33Figura 32 agora há uma verificação detalhada de cada
dispositivo das redes do STVV e SIMOVE, podendo assim verificar sua
operacionalidade.
44
Figura 33: Menu de visualização de monitoramento.
Vê-se com detalhe o agrupamento por hosts, Figura 34:
Figura 34: Menu: Detalhe de Host - Host Detail
Nessa visualização organiza-se por:

View Service Status Detail For All Host Groups

View Status Overview For All Host Groups

View Status Summary For All Host Groups
45

View Status Grid For All Host Groups
Ao clicar em um host ele exibe informações mais detalhadas (Figura 35):
Figura 35: Informação detalhada do host.
Visualiza-se os serviços detalhadamente (Figura 36):
Figura 36: Exibindo Detalhe de Serviço - Service Detail
O detalhe de serviço pode ser visualizado também por:

View History For all hosts

View Notifications For All Hosts

View Host Status Detail For All Hosts
Também visualiza-se os
dispositivos
separados
por seus
visualizando o Hostgroup Overview conforme Figura 37 Figura 38:
locais,
46
Figura 37: Visão geral do Hostgroup Overview - zoom mínimo para exibir o máximo de
hostgroups possíveis.
47
Figura 38: Visão mais detalhada do Hostgroup Overview.
Essas são as funcionalidades mais básicas do Nagios. Dos 525 hosts
conectados na rede, verificamos problemas em 242, onde será vista mais a fundo na
conclusão.
48
4. DIFICULDADES ENCONTRADAS
4.1 DIFICULDADES NA CONFIGURAÇÃO DA MÁQUINA
VIRTUAL
Primeira dificuldade foi a instalação da máquina virtual, pois o antivírus
corporativo utilizado pela Infraero, “Trend Micro OfficeScan” não permite a
gravação de dados da máquina virtual, sendo assim, a solução encontrada foi
desabilitá-lo pelo tempo necessário à instalação, voltando assim a rodar logo após a
configuração, esse problema persiste em qualquer configuração da máquina virtual
que resulte em gravação em disco (salvar alterações).
Ao configurar a Máquina virtual, quando incluiu-se a primeira vez os
comutadores, ocorreu um conflito com a placa de rede física, ocasionando o erro
“NMI HARDWARE FAILURE”, toda vez que eu conectava algum cabo de rede,
ocorria esse erro. Ao consultar o site da Microsoft 11, foram encontradas duas
possíveis soluções: reinstalar alguns drivers e realizar um “chkdsk /f /r”. Deixei mais
de 24 horas rodando o chkdsk sendo que o mesmo parou em 27%. Ao reiniciar o
computador ele sempre voltava novamente no chkdsk, até que cancelei o mesmo para
que o computador reiniciasse normalmente. Atualizei os drivers da placa de rede,
conforme orientado, também sem sucesso.
Após muitas tentativas, decidi desinstalar todos os comutadores do
HYPER-V, e ao fazer isso, conectando o cabo de rede não apresentou mais
problemas, então percebi o conflito, reconfigurei as placas de redes físicas,
configurei os comutadores, conforme as placas de rede, e após isso a máquina virtual
ficou com a placa virtual conforme configurado, e o sistema host não apresentou
mais problemas.
11
http://support.microsoft.com/kb/2750146
http://answers.microsoft.com/en-us/windows/forum/windows_8-system/computer-encountered-annmihardwarefailure-error/f736016b-e8f4-48c3-af48-9019bd0b9892
http://support.microsoft.com/kb/315223
49
4.2 DIFICULDADES COM THE DUDE
Após diversas tentativas, essa ferramenta foi descartada, pois não se adequa
à necessidade de separação de sub-redes.
Apesar dos gráficos serem bons, com possibilidade de alterar ícones, porém
em termos de relatórios não atendeu à necessidade.
4.3 DIFICULDADES COM NAGIOS
Uma grande dificuldade foi a criação de dezenas de arquivos para cada
grupo de hosts, tendo que a cada um definir cada host, ter que definir o serviço de
maneira manual.
O maior problema ao meu ver é que ao realizar a verificação por meio do
comando no SSH, o Nagios não informa se todos os serviços estão atrelados aos
hosts. Por exemplo, em um dos hostgroups eu defini em duplicidade o cerc-op08,
não definindo o host cerc-op-10, porém no serviço estada definido para o item 10, o
verificador somente identificou como warning a duplicidade de hosts, mas não
detectou se todos os serviços estavam atrelados a hosts definidos.
Dessa forma ao corrigir a duplicidade, excluí a definição de host. E o
Nagios exibia 525 serviços e 524 hosts. Tive que verificar os serviços para ver os
dispositivos, e percebi que pulava do cerc-op-09 ao cerc-op-11, então o que eu tinha
excluído era na verdade, o host que copiei para alterar depois o número, porém não o
fiz.
Para evitar problemas com endereçamento e identificação errados eu
utilizava a planilha aberta junto do Notepad++ para realizar a verificação enquanto
fazia a inclusão. Conforme Figura 11 e Figura 12.
50
5. CONCLUSÕES
O levantamento de requisito foi realizado via entrevista onde o encarregado
informou suas necessidades. Esse levantamento serviu como base para identificação
de problemas e a partir deste procurarmos a melhor solução, a qual foi identificada o
Nagios, o que atendeu melhor tais necessidades.
A Configuração da Máquina onde foi configurado o SNMP aconteceu a
contento, o Nagios pôde alcançar seu objetivo.
Para implantar a ferramenta SNMP foi realizado a implantação do recurso
Hyper-V, que é bem intuitivo, não tendo problemas na instalação. Mas as placas de
redes da máquina virtual montada para instalação do Nagios conflitaram com a placa
real, porém após a detecção e correção do problema o Nagios pôde ser instalado e
configurado, onde foram inseridos 525 hosts e um serviço para cada host nos
arquivos de configuração
Conforme proposto, o Nagios foi instalado e agora monitora as redes STVV
e SIMOVE.
Foram detectados 242 hosts com problemas, quase 50% dos dispositivos,
porém, conforme informado pelo encarregado sr. Bruno, muitos desses dispositivos
ainda não foram instalados.
Como os switchs que distribuem as redes SIMOVE e STVV estão
instalados em caixas externas, muitas vezes durante uma chuva de vento infiltra água
na caixa, danificando o switch, deixando assim vários dispositivos inoperante.
O objetivo primordial do Nagios que é o monitoramento de redes e seus
dispositivos foi alcançado com êxito, pois agora há em tempo real a visualização da
operação dos dispositivos.
51
6. REFERÊNCIAS BIBLIOGRÁFICAS
Debian - Software in the Public Interest, I. (2014). Debian. Fonte: Debian:
https://www.debian.org/index.pt.html
Erick. (23 de 03 de 2011). Encontrando erros no Nagios. Fonte: Viva O Linux:
http://www.vivaolinux.com.br/dica/Encontrando-erros-no-Nagios
Kurose e Ross. (2006). Redes de Computadores e a Internet: Uma abordagem topdown. São Paulo: Pearson Addison Wesley.
Marin, P. S. (2010). Cabeamento Estruturado - Desvendando cada passo: do projeto
à instalação. São Paulo: Editora Érica Ltda.
Nagios Enterprises, L. (2014). Nagios. Fonte: Nagios The Industry Standard In IT
Infrastructure Monitoring: http://www.nagios.org/
Notepad++ team. (s.d.). Notepad++ v6.7.1. Fonte: Notepad++ v6.7.1: http://notepadplus-plus.org
SSH Communications Security Corp. (s.d.). SSH Secure File Transfer - Versão 3.2.9
(Build 283). Fonte: http://www/ssh.com
Tanenbaum, A. S. (2003). Redes de Computadores - Quarta Edição. Amsterdan:
Campus.
Tathan, S. (s.d.). Fonte: PuTTY Release 0.63:
http://www.chiark.greenend.org.uk/~sgtatham/putty/
52
APÊNDICES E/OU ANEXOS12
ANEXO 1 - Instalação Nagios - Debian 7 Wheezy - Sandro Barros Siqueira, 2014.
12
Para não delongar demasiadamente, nos arquivos dos hostgroups inclui apenas os 10 primeiros
hosts para exemplificar.
53
54
55
ANEXO 2 – Arquivo de configuração do Nagios: “nagios.cfg”.
##############################################################################
#
# NAGIOS.CFG - Sample Main Config File for Nagios 4.0.8
#
# 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.
#
#
##############################################################################
# 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
###################################################################################
###################################################################################
########
STVV
###########
###################################################################################
###################################################################################
# Definitions for monitoring a TECANACIONAL machine
cfg_file=/usr/local/nagios/etc/objects/stvv/tecanacional.cfg
# Definitions for monitoring a SEÇÃO CONTRA INCÊNDIO - SCI machine
cfg_file=/usr/local/nagios/etc/objects/stvv/sci.cfg
# Definitions for monitoring a TERMINAL DE AVIAÇÃO GERAL 1 - TAG1 machine
cfg_file=/usr/local/nagios/etc/objects/stvv/tag1.cfg
# Definitions for monitoring a LINK AO VIVO - LAV machine
cfg_file=/usr/local/nagios/etc/objects/stvv/lav.cfg
# Definitions for monitoring a MANUTENÇÃO - MNT machine
cfg_file=/usr/local/nagios/etc/objects/stvv/mnt.cfg
# Definitions for monitoring a TECA INTERNACIONAL - TIL machine
cfg_file=/usr/local/nagios/etc/objects/stvv/til.cfg
# Definitions for monitoring a VIA DE ACESSO AOS HANGARES - VAH machine
cfg_file=/usr/local/nagios/etc/objects/stvv/vah.cfg
# Definitions for monitoring a TERMINAL DE AVIAÇÃO GERAL 2 - TAG2 machine
cfg_file=/usr/local/nagios/etc/objects/stvv/tag2.cfg
# Definitions for monitoring a HANGARETES - HGS machine
cfg_file=/usr/local/nagios/etc/objects/stvv/hgs.cfg
# Definitions for monitoring a CENTRAL DE UTILIDADES - CUT machine
cfg_file=/usr/local/nagios/etc/objects/stvv/cut.cfg
# Definitions for monitoring a POSTES DE ILUMINAÇÃO DO PÁTIO - PIP machine
56
cfg_file=/usr/local/nagios/etc/objects/stvv/pip.cfg
# Definitions for monitoring a POSTES CERCA OPERACIONAL - PCO machine
cfg_file=/usr/local/nagios/etc/objects/stvv/pco.cfg
# Definitions for monitoring a TERMINAL DE PASSAGEIROS - TPS machine
cfg_file=/usr/local/nagios/etc/objects/stvv/tps.cfg
# Definitions for monitoring a ADMINISTRAÇÃO - ADM machine
cfg_file=/usr/local/nagios/etc/objects/stvv/adm.cfg
# Definitions for monitoring a CASTELO PRINCIPAL - CPL machine
cfg_file=/usr/local/nagios/etc/objects/stvv/cpl.cfg
# Definitions for monitoring a ESTAÇÃO DE TRATAMENTO DE ESGOTO - ETE machine
cfg_file=/usr/local/nagios/etc/objects/stvv/ete.cfg
# Definitions for monitoring a TERMINAL DE PASSAGEIROS - TÉRREO - TPS-TER machine
cfg_file=/usr/local/nagios/etc/objects/stvv/tps-ter.cfg
# Definitions for monitoring a TERMINAL DE PASSAGEIROS - SUPERIOR - TPS-SUP machine
cfg_file=/usr/local/nagios/etc/objects/stvv/tps-sup.cfg
# Definitions for monitoring a TERMINAL DE PASSAGEIROS - COBERTURA - TPS-COB machine
cfg_file=/usr/local/nagios/etc/objects/stvv/tps-cob.cfg
###################################################################################
###################################################################################
#################
SIMOVE
###################
###################################################################################
###################################################################################
# Definitions for monitoring a SIMOVE-PATIO machine
cfg_file=/usr/local/nagios/etc/objects/simove/patio.cfg
# Definitions for monitoring a SIMOVE-AREA2 machine
cfg_file=/usr/local/nagios/etc/objects/simove/area2.cfg
# Definitions for monitoring a SIMOVE-AREA3 machine
cfg_file=/usr/local/nagios/etc/objects/simove/area3.cfg
# Definitions for monitoring a SIMOVE-SIMOVE-CERC-OP machine
cfg_file=/usr/local/nagios/etc/objects/simove/cercop.cfg
# Definitions for monitoring a SIMOVE-NORTE machine
cfg_file=/usr/local/nagios/etc/objects/simove/norte.cfg
# Definitions for monitoring a SIMOVE-PORTAO-A machine
cfg_file=/usr/local/nagios/etc/objects/simove/portaoa.cfg
# Definitions for monitoring a SIMOVE-TNL machine
cfg_file=/usr/local/nagios/etc/objects/simove/tecanacional.cfg
# Definitions for monitoring a SIMOVE-TIL machine
cfg_file=/usr/local/nagios/etc/objects/simove/tecainternacional.cfg
#####################################################################################
#
OUTROS HOSTSGROUPS QUE FICARAM COMO DEFAULT
#####################################################################################
# Definitions for monitoring a router/switch
#cfg_file=/usr/local/nagios/etc/objects/switch.cfg
# Definitions for monitoring a network printer
57
#cfg_file=/usr/local/nagios/etc/objects/printer.cfg
# Definitions for monitoring the local (Linux) host
# cfg_file=/usr/local/nagios/etc/objects/localhost.cfg
# Definitions for monitoring a Windows machine
# cfg_file=/usr/local/nagios/etc/objects/windows.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
# 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).
# 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
58
# Nagios will periodically dump program, host, and
# service status data.
status_update_interval=10
# 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 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
# QUERY HANDLER INTERFACE
# This is the socket that is created for the Query Handler interface
#query_socket=/usr/local/nagios/var/rw/nagios.qh
# 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.
temp_file=/usr/local/nagios/var/nagios.tmp
# TEMP PATH
59
# 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:
#
# 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
60
# 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
# 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
# CURRENT STATES LOGGING OPTION
# If you don't want Nagios to log all current host and service states
# after log has been rotated to the main log file, you can disable this
# option by setting this value to 0. Default value is 1.
log_current_states=1
# EXTERNAL COMMANDS LOGGING OPTION
# 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
61
# 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
#
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
#
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
62
# 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
# 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
63
# check caching.
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
# 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
64
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.
auto_rescheduling_interval=30
# 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).
auto_rescheduling_window=180
# 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
# 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 retain_state_information
# variable is set to 1.
state_retention_file=/usr/local/nagios/var/retention.dat
65
# 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
# 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
# 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
66
# 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
# 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
# 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!
67
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
# 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=/usr/local/nagios/var/host-perfdata
#service_perfdata_file=/usr/local/nagios/var/service-perfdata
# 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)
68
# 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$HOSTEXECUTIONTIME$\t$HOSTOUTP
UT$\t$HOSTPERFDATA$
#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXEC
UTIONTIME$\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
# 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
# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
# These options determine wether the core will process empty perfdata
# results or not. This is needed for distributed monitoring, and intentionally
# turned on by default.
# If you don't require empty perfdata - saving some cpu cycles
# on unwanted macro calculation - you can turn that off. Be careful!
# Values: 1 = enable, 0 = disable
#host_perfdata_process_empty_results=1
#service_perfdata_process_empty_results=1
# 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
69
# 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
# 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
# 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
# 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.
70
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
# SERVICE CHECK TIMEOUT STATE
# This setting determines the state Nagios will report when a
# service check times out - that is does not respond within
# service_check_timeout seconds. This can be useful if a
# machine is running at too high a load and you do not want
# to consider a failed service check to be critical (the default).
# Valid settings are:
# c - Critical (default)
# u - Unknown
# w - Warning
# o - OK
service_check_timeout_state=c
# 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
# FLAP DETECTION OPTION
71
# 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
# 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
# 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
72
# 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=`~$&|'"<>
# 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
# 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
73
# 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 is a very bad idea for anything but very small setups,
# as it means plugins, notification scripts and eventhandlers may run
# out of environment space. It will also cause a significant increase
# in CPU- and memory usage and drastically reduce the number of checks
# you can run.
# Values: 1 - Enable environment variable macros
#
0 - Disable environment variable macros (default)
enable_environment_macros=0
# 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.
# 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
# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
74
# 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
# Should we allow hostgroups to have no hosts, we default this to off since
# that was the old behavior
allow_empty_hostgroup_assignment=0
# Normally worker count is dynamically allocated based on 1.5 * number of cpu's
# with a minimum of 4 workers. This value will override the defaults
#check_workers=3
# EXPERIMENTAL load controlling options
# To get current defaults based on your system issue a command to
# the query handler. Please note that this is an experimental feature
# and not meant for production use. Used incorrectly it can induce
# enormous latency.
# #core loadctl
# jobs_max - The maximum amount of jobs to run at one time
# jobs_min - The minimum amount of jobs to run at one time
# jobs_limit - The maximum amount of jobs the current load lets us run
# backoff_limit - The minimum backoff_change
# backoff_change - # of jobs to remove from jobs_limit when backing off
# rampup_limit - Minimum rampup_change
# rampup_change - # of jobs to add to jobs_limit when ramping up
# NOTE: The backoff_limit and rampup_limit are NOT used by anything currently,
#
so if your system is under load nothing will actively modify the jobs
#
even if you have these options enabled, they are for external
#
connector information only. However, if you change the jobs_max or
#
jobs_min manually here or through the query handler interface that
#
WILL affect your system
#loadctl_options=jobs_max=100;backoff_limit=10;rampup_change=5
75
ANEXO 3 – Arquivo de configuração do Nagios: “templates.cfg”.
###############################################################################
# TEMPLATES.CFG - SAMPLE OBJECT TEMPLATES
#
#
# NOTES: This config file provides you with some example object definition
#
templates that are refered by other host, service, contact, etc.
#
definitions in other config files.
#
#
You don't need to keep these definitions in a separate file from your
#
other object definitions. This has been done just to make things
#
easier to understand.
#
###############################################################################
###############################################################################
###############################################################################
#
# CONTACT TEMPLATES
#
###############################################################################
###############################################################################
# Generic contact definition template - This is NOT a real contact, just a template!
define contact{
name
generic-contact
; The name of this contact template
service_notification_period 24x7
; service notifications can be sent anytime
host_notification_period
24x7
; host notifications can be sent anytime
service_notification_options w,u,c,r,f,s
; send notifications for all service states, flapping events, and
scheduled downtime events
host_notification_options
d,u,r,f,s
; send notifications for all host states, flapping events, and scheduled
downtime events
service_notification_commands notify-service-by-email
; send service notifications via email
host_notification_commands notify-host-by-email
; send host notifications via email
register
0
; DONT REGISTER THIS DEFINITION - ITS NOT A REAL CONTACT, JUST
A TEMPLATE!
}
###############################################################################
###############################################################################
#
# HOST TEMPLATES
#
###############################################################################
###############################################################################
# Generic host definition template - This is NOT a real host, just a template!
define host{
name
generic-host ; The name of this host template
notifications_enabled
1
; Host notifications are enabled
event_handler_enabled
1
; Host event handler is enabled
flap_detection_enabled
1
; Flap detection is enabled
process_perf_data
1
; Process performance data
retain_status_information
1
; Retain status information across program restarts
retain_nonstatus_information 1
; Retain non-status information across program restarts
notification_period
24x7
; Send host notifications at any time
register
0
; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
}
# Linux host definition template - This is NOT a real host, just a template!
define host{
name
linux-server
; The name of this host template
76
use
generic-host
; This template inherits other values from the
generic-host template
check_period
24x7
; By default, Linux hosts are checked round the
clock
check_interval
5
; Actively check the host every 5 minutes
retry_interval
1
; Schedule host check retries at 1 minute intervals
max_check_attempts
10
; Check each Linux host 10 times (max)
check_command
check-host-alive ; Default command to check Linux hosts
notification_period
workhours ; Linux admins hate to be woken up, so we only notify during the day
; Note that the notification_period variable is
being overridden from
; the value that is inherited from the generic-host
template!
notification_interval
120
; Resend notifications every 2 hours
notification_options
d,u,r
; Only send notifications for specific host states
contact_groups
admins
; Notifications get sent to the admins by default
register
0
; DONT REGISTER THIS DEFINITION - ITS NOT A
REAL HOST, JUST A TEMPLATE!
}
# Windows host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
windows-server
generic-host
; Inherit default values from the generic-host template
24x7
; By default, Windows servers are monitored round the clock
5
; Actively check the server every 5 minutes
1
10
; Check each server 10 times (max)
check-host-alive
; Default command to check if servers are "alive"
24x7
; Send notification out at any time - day or night
30
; Resend notifications every 30 minutes
d,r
admins
windows-servers ; Host groups that Windows servers should be a member of
0
; DONT REGISTER THIS - ITS JUST A TEMPLATE
#####################################################################################################
#####################################################################################################
#
HOSTS UTILIZADOS PELO STVV, DIVIDIDOS POR LOCAIS
#####################################################################################################
#####################################################################################################
# TECA NACIONAL host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
TECANACIONAL ; The name of this host template
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
TECANACIONAL ; Host groups that Windows servers should be a member of
0
# SECAO CONTRA INCENDIO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts 10
SCI
generic-host
24x7
5
1
77
check_command
notification_period
contact_groups
hostgroups
register
}
check-host-alive
admins
SCI ; Host groups that Windows servers should be a member of
0
24x7
30
d,r
# TERMINAL DE AVIACAO GERAL 1 host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
TAG1
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
TAG1 ; Host groups that Windows servers should be a member of
0
# LINK AO VIVO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
LAV
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
LAV ; Host groups that Windows servers should be a member of
0
# MANUTENCAO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
MNT
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
MNT ; Host groups that Windows servers should be a member of
0
# TECA INTERNACIONAL host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
TIL
generic-host
24x7
5
1
78
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
10
check-host-alive
24x7
30
d,r
admins
TIL ; Host groups that Windows servers should be a member of
0
# VIA DE ACESSO AOS HANGARES host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
VAH
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
VAH ; Host groups that Windows servers should be a member of
0
# TERMINAL DE AVIAÇÃO GERAL 2 host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
TAG2
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
TAG2 ; Host groups that Windows servers should be a member of
0
# HANGARETES host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
HGS
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
HGS ; Host groups that Windows servers should be a member of
0
# CENTRAL DE UTILIDADES host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
CUT
generic-host
24x7
79
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
5
1
10
check-host-alive
24x7
30
d,r
admins
CUT ; Host groups that Windows servers should be a member of
0
# POSTES DE ILUMINAÇÃO DO PÁTIO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
PIP
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
PIP ; Host groups that Windows servers should be a member of
0
# POSTES CERCA OPERACIONAL host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
PCO
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
PCO ; Host groups that Windows servers should be a member of
0
# TERMINAL DE PASSAGEIROS host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
TPS
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
TPS ; Host groups that Windows servers should be a member of
0
# ADMINISTRAÇÃO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
ADM
generic-host
24x7
5
80
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
1
check-host-alive
24x7
30
d,r
admins
ADM ; Host groups that Windows servers should be a member of
0
10
# CASTELO PRINCIPAL host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
CPL
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
CPL ; Host groups that Windows servers should be a member of
0
# ESTAÇÃO DE TRATAMENTO DE ESGOTO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
ETE
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
ETE ; Host groups that Windows servers should be a member of
0
# TERMINAL DE PASSAGEIROS - TÉRREO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
TPS-TER ; The name of this host template
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
TPS-TER ; Host groups that Windows servers should be a member of
0
# TERMINAL DE PASSAGEIROS - SUPERIOR host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
TPS-SUP ; The name of this host template
generic-host
24x7
5
81
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
1
check-host-alive
24x7
30
d,r
admins
TPS-SUP ; Host groups that Windows servers should be a member of
0
10
# TERMINAL DE PASSAGEIROS - COBERTURA host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
TPS-COB ; The name of this host template
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
TPS-COB ; Host groups that Windows servers should be a member of
0
##################################################################################################
##################################################################################################
###
HOSTS DO SIMOVE DIVIDIDOS POR LOCAIS
##################################################################################################
##################################################################################################
# PATIO host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
SIMOVE-PATIO
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
SIMOVE-PATIO ; Host groups that Windows servers should be a member of
0
# AREA 2 host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
SIMOVE-AREA2 ; The name of this host template
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
SIMOVE-AREA2 ; Host groups that Windows servers should be a member of
0
82
# AREA 3 host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
SIMOVE-AREA3 ; The name of this host template
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
SIMOVE-AREA3 ; Host groups that Windows servers should be a member of
0
# CERCA OPERACIONAL host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
SIMOVE-CERC-OP ; The name of this host template
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
SIMOVE-CERC-OP ; Host groups that Windows servers should be a member of
0
# LIMITE NORTE host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
SIMOVE-NORTE ; The name of this host template
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
SIMOVE-NORTE ; Host groups that Windows servers should be a member of
0
# PORTAO A host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
SIMOVE-PORTAO-A
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
SIMOVE-PORTAO-A ; Host groups that Windows servers should be a member of
0
83
# TECA NACIONAL host definition template - This is NOT a real host, just a template!
define host{
name
SIMOVE-TNL
use
generic-host
check_period
24x7
check_interval
5
retry_interval
1
check_command
check-host-alive
notification_period 24x7
notification_interval 30
notification_options d,r
contact_groups
admins
hostgroups
SIMOVE-TNL ; Host groups that Windows servers should be a member of
register
0
}
# TECA INTERNACIONAL host definition template - This is NOT a real host, just a template!
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
hostgroups
register
}
SIMOVE-TIL
generic-host
24x7
5
1
10
check-host-alive
24x7
30
d,r
admins
SIMOVE-TIL ; Host groups that Windows servers should be a member of
0
# We define a generic printer template that can be used for most printers we monitor
define host{
name
use
check_period
check_interval
retry_interval
max_check_attempts
check_command
notification_period
contact_groups
register
}
generic-printer
generic-host
24x7
; By default, printers are monitored round the clock
5
; Actively check the printer every 5 minutes
1
10
; Check each printer 10 times (max)
check-host-alive
; Default command to check if printers are "alive"
workhours
; Printers are only used during the workday
30
d,r
admins
0
# Define a template for switches that we can reuse
define host{
name
generic-switch
use
generic-host
check_period
24x7
; By default, switches are monitored round the clock
check_interval
5
; Switches are checked every 5 minutes
retry_interval
1
; Check each switch 10 times (max)
check_command
check-host-alive
; Default command to check if routers are "alive"
notification_period 24x7
; Send notifications at any time
notification_interval 30
notification_options d,r
contact_groups
admins
register
0
}
84
###############################################################################
###############################################################################
#
# SERVICE TEMPLATES
#
###############################################################################
###############################################################################
# Generic service definition template - This is NOT a real service, just a template!
define service{
name
generic-service
active_checks_enabled
1
passive_checks_enabled
1
parallelize_check
1
major performance problems)
obsess_over_service
1
check_freshness
0
notifications_enabled
1
event_handler_enabled
1
flap_detection_enabled
1
process_perf_data
1
retain_status_information
1
retain_nonstatus_information 1
is_volatile
0
check_period
24x7
max_check_attempts
3
normal_check_interval
10
retry_check_interval
2
contact_groups
admins
notification_options w,u,c,r
60
notification_period
24x7
register
0
SERVICE, JUST A TEMPLATE!
}
; The 'name' of this service template
; Active service checks are enabled
; Passive service checks are enabled/accepted
; Active service checks should be parallelized (disabling this can lead to
; We should obsess over this service (if necessary)
; Default is to NOT check service 'freshness'
; Service notifications are enabled
; Service event handler is enabled
; Flap detection is enabled
; Process performance data
; Retain status information across program restarts
; Retain non-status information across program restarts
; The service is not volatile
; The service can be checked at any time of the day
; Re-check the service up to 3 times in order to determine its final (hard) state
; Check the service every 10 minutes under normal conditions
; Re-check the service every two minutes until a hard state can be determined
; Notifications get sent out to everyone in the 'admins' group
; Send notifications about warning, unknown, critical, and recovery events
; Re-notify about service problems every hour
; Notifications can be sent out at any time
; DONT REGISTER THIS DEFINITION - ITS NOT A REAL
# Local service definition template - This is NOT a real service, just a template!
define service{
name
use
max_check_attempts
normal_check_interval
retry_check_interval
register
0
TEMPLATE!
}
local-service
; The name of this service template
generic-service
; Inherit default values from the generic-service definition
4
; Re-check the service up to 4 times in order to determine its final (hard) state
5
; Check the service every 5 minutes under normal conditions
1
; Re-check the service every minute until a hard state can be determined
; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A
85
ARQUIVOS DE CONFIGURAÇÃO DO STVV:
ANEXO 4 – Arquivo de configuração do Nagios: “adm.cfg”
###############################################################################
# adm.CFG - SAMPLE CONFIG FILE FOR MONITORING A ADMINISTRAÇÃO - ADM MACHINE
#
#
# NOTES: This config file assumes that you are using the sample configuration
#
files that get installed with the Nagios quickstart guide.
#
#
CRIADO POR: JULIAN FIGUERAS DORADO RODRIGUES
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
# Define a host for the Windows machine we'll be monitoring Change the host_name, alias, and address to fit your situation
#
#
#==============================================================================
#
STVV ADMINISTRAÇÃO
#==============================================================================
#
#
ABRANGENCIA DE IPS: .33.101-132
#
ADM-01 A ADM-32 - 32 HOSTS
#
#01-10
define host{
use ADM ; Inherit default values from a template
host_name ADM-01 ; The name we're giving to this host
alias ADMINISTRACAO 01 ; A longer name associated with the host
address xxx.xxx.34.101 ; IP address of the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
86
}
define host{
}
define host{
}
define host{
}
#
FIM ADMINISTRACAO
###############################################################################
###############################################################################
#
# 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
#
DEFININDO HOSTGROUPS POR SETORES DOS DISPOSITIVOS
#define hostgroup{
#
hostgroup_name
windows-servers
; The name of the hostgroup
#
alias Windows Servers ; Long name of the group
#
}
define hostgroup{
hostgroup_name
ADM
alias ADMINISTRACAO ; 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
#
#==============================================================================
#
SERVICOS ADMINISTRACAO
#==============================================================================
#
#
ADM-01 A ADM-32
#
#01-10
define service{
use generic-service ; Inherit values from a template
host_name ADM-01 ; The name of the host the service is associated with
service_description PING ; The service description
check_command check_ping!200.0,20%!600.0,60% ; The command used to monitor the service
normal_check_interval 5 ; Check the service every 5 minutes under normal conditions
retry_check_interval 1 ; Re-check the service every minute until its final/hard state is determined
}
define service{
87
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM ADMINISTRACAO
88
ANEXO 5 – Arquivo de configuração do Nagios: “cpl.cfg”.
###############################################################################
# cpl.CFG - SAMPLE CONFIG FILE FOR MONITORING A CASTELO PRINCIPAL - CPL MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#==========================================================================================
================
#
STVV - CASTELO PRINCIPAL
#==========================================================================================
================
#
# ABRANGENCIA DE IPS: .33.24-28
#
# CPL-01 A CPL-04
#
define host{
use CPL ; Inherit default values from a template
host_name CPL-01 ; The name we're giving to this host
alias CASTELO PRINCIPAL 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
#
#
FIM DE CASTELO PRINCIPAL
#
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#
#
89
#
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
CPL
alias CASTELO PRINCIPAL ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==========================================================================================
================
#
SERVICOS TERMINAL AVIACAO GERAL 1
#==========================================================================================
================
#
#
CPL-01 A CPL-04
#
define service{
host_name CPL-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
#
#
FIM DE SERVICOS DE CASTELO PRINCIPAL
90
ANEXO 6 – Arquivo de configuração do Nagios: “cut.cfg”.
###############################################################################
# cut.CFG - SAMPLE CONFIG FILE FOR MONITORING A CENTRAL DE UTILIDADES - CUT MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
STVV CENTRAL DE UTILIDADES
#==============================================================================
#
#
#
CUT-01 A CUT-03
#
define host{
use CUT ; Inherit default values from a template
host_name CUT-01 ; The name we're giving to this host
alias CENTRAL DE UTILIDADES 01 ; A longer name associated with the host
}
define host{
}
define host{
}
#
FIM CENTRAL DE UTILIDADES
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
CUT
alias CENTRAL DE UTILIDADES ; Long name of the group
}
###############################################################################
###############################################################################
91
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS CENTRAL DE UTILIDADES
#==============================================================================
#
#
CUT-01 A CUT-03
#
define service{
host_name CUT-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
#
FIM SERVICOS CENTRAL DE UTILIDADES
92
ANEXO 7 – Arquivo de configuração do Nagios: “ete.cfg”.
###############################################################################
# ete.CFG - SAMPLE CONFIG FILE FOR MONITORING A ESTACAO DE TRATAMENTO DE ESGOTO - ETE
MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
STVV ESTACAO DE TRATAMENTO DE ESGOTO - ETE
#==============================================================================
#
#
#
ETE-01 A ETE-08
#
define host{
use ETE ; Inherit default values from a template
host_name ETE-01 ; The name we're giving to this host
alias ESTACAO DE TRATAMENTO DE ESGOTO 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
93
}
define host{
}
#
FIM ESTACAO DE TRATAMENTO DE ESGOTO
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
ETE
alias ESTACAO DE TRATAMENTO DE ESGOTO ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVI?S ESTACAO DE TRATAMENTO DE ESGOTO
#==========================================================================================
========================
#
#
# ETE-01 a ETE-08
#
define service{
host_name ETE-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
94
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM DE ESTACAO DE TRATAMENTO DE ESGOTO
95
ANEXO 8 – Arquivo de configuração do Nagios: “hgs.cfg”.
###############################################################################
# hgs.CFG - SAMPLE CONFIG FILE FOR MONITORING A HANGARETES - HGS MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#==============================================================================
#
HANGARETES
#==============================================================================
#
#
#
HGS-01 A HGS-05
#
define host{
use HGS ; Inherit default values from a template
host_name HGS-01 ; The name we're giving to this host
alias HANGARETES 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
#
FIM HANGARETES
#
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
96
#
#
#
hostgroup_name
windows-servers
}
define hostgroup{
hostgroup_name
HGS
alias HANGARETES ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS HANGARETES
#==============================================================================
#
#
HGS-01 A HGS-05
#
define service{
host_name HGS-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM SERVICOS HANGARETES
97
ANEXO 9 – Arquivo de configuração do Nagios: “lav.cfg”
###############################################################################
# lav.CFG - SAMPLE CONFIG FILE FOR MONITORING A LINK AO VIVO - LAV MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
LINK AO VIVO
#==============================================================================
#
#
#
LAV-01 A LAV-05
#
define host{
use LAV ; Inherit default values from a template
host_name LAV-01 ; The name we're giving to this host
alias LINK AO VIVO 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
#
FIM DE LINK AO VIVO
#
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
98
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
LAV
alias LINK AO VIVO ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SERVICOS LINK AO VIVO
#==============================================================================
#
#
LAV-01 A LAV-05
#
define service{
host_name LAV-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
define service{
}
#
#
FIM DE SERVICO LINK AO VIVO
#
99
ANEXO 10 – Arquivo de configuração do Nagios: “mnt.cfg”.
###############################################################################
# mnt.CFG - SAMPLE CONFIG FILE FOR MONITORING A MANUTENÇÃO - MNT MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
MANUTENCAO
#==============================================================================
#
#
#
MNT-01 A MNT-06
#
define host{
use MNT ; Inherit default values from a template
host_name MNT-01 ; The name we're giving to this host
alias MANUTENCAO 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
#
FIM DE MANUTENCAO
###############################################################################
###############################################################################
#
#
100
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
MNT
alias MANUTENCAO ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVIÇOS MANUTENCAO
#==============================================================================
#
#
MNT-01 A MNT-06
#
define service{
host_name MNT-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
101
#
}
FIM DE SERVICO MANUTENCAO
102
ANEXO 11 – Arquivo de configuração do Nagios: “pco.cfg”.
###############################################################################
# pco.CFG - SAMPLE CONFIG FILE FOR MONITORING A POSTES CERCA OPERACIONAL - PCO MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#
#==============================================================================
#
STVV POSTES CERCA OPERACIONAL
#==============================================================================
#
#
ABRANGENCIA DE IPS: .32.204 - .31.254 /// .33.01 - .33.18
#
OBS: HÁ MUDANÇA NA SUB-REDE DE 31 PARA 32 DEVIDO A QUANTIDADE DE HOSTS
#
SÃO 23 POSTES, CADA UM COM 3 CÂMERAS
#
PCO01-01 A PCO23-69
#
##
#
POSTE 01 - PCO01-01 A PCO01-03
define host{
use PCO ; Inherit default values from a template
host_name PCO01-01 ; The name we're giving to this host
alias POSTES CERCA OPERACIONAL 01 01 ; A longer name associated with the host
}
define host{
}
define host{
}
##
#
define host{
}
define host{
}
define host{
103
}
#
##
define host{
}
define host{
}
define host{
}
#
##
define host{
}
# FIM POSTES CERCA OPERACIONAL
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
PCO
alias POSTES CERCA OPERACIONAL ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS POSTES CERCA OPERACIONAL
#==============================================================================
#
#
PCO01-01 A PCO23-69
#
#
PCO01-01 A PCO04-10
define service{
104
host_name PCO01-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
105
}
#
FIM POSTES CERCA OPERACIONAL
106
ANEXO 12 – Arquivo de configuração do Nagios: “pip.cfg”.
###############################################################################
# pip.CFG - SAMPLE CONFIG FILE FOR MONITORING A POSTES DE ILUMINAÇÃO DO PÁTIO - PIP MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
POSTES DE ILUMINACAO DO PATIO
#==============================================================================
#
#
#
OBS.: SAO 8 POSTES
#
PIP01-01 A PIP16-31
#
#
POSTE 01 - PIP01-01 A PIP01-03
define host{
use PIP ; Inherit default values from a template
host_name PIP01-01 ; The name we're giving to this host
alias POSTE DE ILUMINACAO DO PATIO 01 01 ; A longer name associated with the host
}
define host{
}
define host{
}
#
POSTE 03 - PIP03-04 A PIP03define host{
}
define host{
}
define host{
host_name PIP03-06; The name we're giving to this host
}
define host{
107
}
#
POSTE 07 - PIP07-08 A PIP07-11
define host{
}
define host{
}
define host{
}
#
FIM POSTES DE ILUMINACAO DO PATIO
#
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
PIP
alias POSTES DE ILUMINACAO DO PATIO ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
POSTES DE ILUMINACAO DO PATIO
#==============================================================================
#
#
OBS.: SAO 8 POSTES
#
PIP01-01 A PIP16-31
#
#
PIP01-01 A PIP01-03
define service{
host_name PIP01-01 ; The name of the host the service is associated with
}
define service{
108
}
define service{
}
#
PIP03-04 A PIP03-07
define service{
}
define service{
}
define service{
}
define service{
}
#
PIP07-08 A PIP07-11
define service{
}
define service{
}
define service{
}
#
FIM POSTES DE ILUMINACAO DO PATIO
109
110
ANEXO 13 – Arquivo de configuração do Nagios: “sci.cfg”.
###############################################################################
# sci.CFG - SAMPLE CONFIG FILE FOR MONITORING A SEÇÃO CONTRA INCÊNDIO - SCI MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#=============================================================================
#
SEÇÃO CONTRA INCENDIO
#==============================================================================
#
# Abrangencia de ips: .31.108-114
# SCI-01 a SCI-07
#
define host{
use SCI ; Inherit default values from a template
host_name SCI-01
; The name we're giving to this host
alias SECAO CONTRA INCENDIO 01 ; A longer name associated with the host
}
define host{
host_name SCI-02
}
define host{
host_name SCI-03
}
define host{
host_name SCI-04
}
define host{
host_name SCI-05
}
define host{
host_name SCI-06
}
define host{
host_name SCI-07
}
#
# FIM SECAO CONTRA INCENDIO
111
#
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
# Define a hostgroup for Windows machines All hosts that use the SCI template will automatically be a member of this group
#
define hostgroup{
hostgroup_name
SCI
alias SECAO CONTRA INCENDIO ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#
#==========================================================================================
================
#
SERVICOS SECAO CONTRA INCENDIO
#==========================================================================================
================
# SCI-01 a SCI-07
define service{
host_name SCI-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
define service{
112
}
define service{
}
define service{
}
#
#
FIM SECAO CONTRA INCENDIO
#
113
ANEXO 14 – Arquivo de configuração do Nagios: “tag1.cfg”.
###############################################################################
# tag1.CFG - SAMPLE CONFIG FILE FOR MONITORING A TERMINAL DE AVIAÇÃO GERAL 1 - TAG1 MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#==========================================================================================
================
#
STVV - TERMINAL DE AVIACAO GERAL 1
#==========================================================================================
================
#
# ABRANGENCIA DE IPS: .32.115-123 E .33.28
#
# TAG1-01 A TAG1-10
#
define host{
use TAG1 ; Inherit default values from a template
host_name TAG1-01 ; The name we're giving to this host
alias TERMINAL DE AVIACAO GERAL 1 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
114
}
define host{
}
define host{
}
define host{
}
#
#
FIM DE TERMINAL DE AVIACAO GERAL 1
#
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#
#
#
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
TAG1
alias TERMINAL AVIACAO GERAL 1 ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==========================================================================================
================
#
SERVICOS TERMINAL AVIACAO GERAL 1
#==========================================================================================
================
#
#
TAG1-01 A TAG1-09
#
define service{
host_name TAG1-01 ; The name of the host the service is associated with
115
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
116
}
#
#
FIM DE SERVICOS DE TERMINAL DE AVIACAO GERAL 1
117
ANEXO 15 – Arquivo de configuração do Nagios: “tag2.cfg”.
###############################################################################
# tag2.CFG - SAMPLE CONFIG FILE FOR MONITORING A TERMINAL DE AVIAÇÃO GERAL 2 - TAG2 MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
TERMINAL DE AVIACAO GERAL 2
#==============================================================================
#
#
#
TAG2-01 A TAG2-06
#
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
#
FIM TERMINAL DE AVIACAO GERAL 2
#
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
118
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
TAG2
alias TERMINAL DE AVIACAO GERAL 2 ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS TERMINAL DE AVIACAO GERAL 2
#==============================================================================
#
#
TAG2-01 A TAG2-06
#
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
119
#
}
FIM DE SERVICO TERMINAL DE AVIACAO GERAL 2
120
ANEXO 16 – Arquivo de configuração do Nagios: “tecanacional.cfg”.
###############################################################################
# tecanacional.CFG - SAMPLE CONFIG FILE FOR MONITORING A TECA NACIONAL - TECANACIONAL MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#============================================================================
#
STVV TECA NACIONAL
#============================================================================
#
#
#
# ips abrangidos .32.51-107
# TNL-01 a TNL-57
#
#
#01-10
define host{
use TECANACIONAL ; Inherit default values from a template
host_name TNL-01 ; The name we're giving to this host
alias TECA NACIONAL 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
121
}
define host{
}
define host{
}
define host{
}
#
FIM TECA NACIONAL
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
define hostgroup{
hostgroup_name
windows-servers
}
define hostgroup{
hostgroup_name
TECANACIONAL ; The name of the hostgroup
alias TECA NACIONAL ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVIÇOS TECA NACIONAL
#==========================================================================================
========================
#
#
# TNL-01 a TNL-57
#
#01-10
define service{
host_name TNL-01 ; The name of the host the service is associated with
}
define service{
122
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
#
FIM TECA NACIONAL
123
ANEXO 17 – Arquivo de configuração do Nagios: “til.cfg”.
###############################################################################
# WINDOWS.CFG - SAMPLE CONFIG FILE FOR MONITORING A WINDOWS MACHINE
#
#
#
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
STVV TECA INTERNACIONAL
#==============================================================================
#
#
ABRANGENCIA DE IPS: 135-152
#
TIL-01 A TIL-18
#
define host{
use TIL ; Inherit default values from a template
host_name TIL-01
alias TECA INTERNACIONAL 01 ; A longer name associated with the host
}
define host{
host_name TIL-02
}
define host{
host_name TIL-03
}
define host{
host_name TIL-04
}
define host{
host_name TIL-05
}
define host{
host_name TIL-06
}
define host{
host_name TIL-07
}
define host{
host_name TIL-08
124
}
define host{
host_name TIL-09
}
define host{
host_name TIL-10
}
# FIM TECA INTERNACIONAL
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
TIL
alias TECA INTERNACIONAL ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==============================================================================
#
SERVICO TECA INTERNACIONAL
#==============================================================================
#
#
TIL-01 A TIL-18
#
define service{
host_name TIL-01 ; The name of the host the service is associated with
}
define service{
}
define service{
125
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
# FIM DE SERVICO TECA INTERNACIONAL
126
ANEXO 18 – Arquivo de configuração do Nagios: “tps.cfg”.
###############################################################################
# tps.CFG - SAMPLE CONFIG FILE FOR MONITORING A TERMINAL DE PASSAGEIROS - TPS MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
STVV TERMINAL DE PASSAGEIROS - TPS
#==============================================================================
#
#
ABRANGENCIA DE IPS: .33.19-21 // .33.133-143
#
TPS-01 A TPS-14
#
define host{
use TPS ; Inherit default values from a template
host_name TPS-01 ; The name we're giving to this host
alias TERMINAL DE PASSAGEIROS 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
127
}
define host{
}
define host{
}
#
FIM TERMINAL DE PASSAGEIROS
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
TPS
alias TERMINAL DE PASSAGEIROS ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVIÇOS TERMINAL DE PASSAGEIROS
#==========================================================================================
========================
#
#
# TPS-01 a TPS-03
#
define service{
host_name TPS-01 ; The name of the host the service is associated with
}
define service{
128
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM DE TERMINAL DE PASSAGEIROS
129
ANEXO 19 – Arquivo de configuração do Nagios: “tps-cob.cfg”.
###############################################################################
# tps-cop.CFG - SAMPLE CONFIG FILE FOR MONITORING A TERMINAL DE PASSAGEIROS - COBERTURA - TPSCOB MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
STVV TERMINAL DE PASSAGEIROS - COBERTURA
#==============================================================================
#
#
#
TPS-COB-01 A TPS-COB-12
#
define host{
use TPS-COB ; Inherit default values from a template
host_name TPS-COB-01
alias TERMINAL DE PASSAGEIROS - COBERTURA 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
130
}
define host{
}
define host{
}
define host{
}
#
FIM TERMINAL DE PASSAGEIROS - COBERTURA
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
TPS-COB ; The name of the hostgroup
alias TERMINAL DE PASSAGEIROS - COBERTURA ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS TERMINAL DE PASSAGEIROS - COBERTURA
#==============================================================================
#
#
TPS-COB-01 A TPS-COB-12
#
define service{
host_name TPS-COB-01 ; The name of the host the service is associated with
}
define service{
131
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM SERVICOS TERMINAL DE PASSAGEIROS - COBERTURA
132
ANEXO 20 – Arquivo de configuração do Nagios: “tps-sup.cfg”.
###############################################################################
# tps-sup.CFG - SAMPLE CONFIG FILE FOR MONITORING A TERMINAL DE PASSAGEIROS - SUPERIOR - TPS-SUP
MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
STVV TERMINAL DE PASSAGEIROS - SUPERIOR
#==============================================================================
#
#
ABRANGENCIA DE IPS: .34.101-112 E .34.125-171
#
TPS-SUP-01 A TPS-SUP-59
#
#
TPS-SUP-01 - TPS-SUP-10
define host{
use TPS-SUP ; Inherit default values from a template
host_name TPS-SUP-01
alias TERMINAL DE PASSAGEIROS - SUPERIOR 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
133
}
define host{
}
define host{
}
define host{
}
#
FIM TERMINAL DE PASSAGEIROS - SUPERIOR
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
TPS-SUP ; The name of the hostgroup
alias TERMINAL DE PASSAGEIROS - SUPERIOR ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS TERMINAL DE PASSAGEIROS - SUPERIOR
#==============================================================================
#
#
#
#
define service{
host_name TPS-SUP-01 ; The name of the host the service is associated with
}
define service{
134
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM SERVICOS TERMINAL DE PASSAGEIROS - SUPERIOR
135
ANEXO 21 – Arquivo de configuração do Nagios: “tps-ter.cfg”.
###############################################################################
# tps-ter.CFG - SAMPLE CONFIG FILE FOR MONITORING A TERMINAL DE PASSAGEIROS - TERREO - TPS-TER
MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
STVV TERMINAL DE PASSAGEIROS - TERREO
#==============================================================================
#
#
#
TPS-TER-01 A TPS-TER-99
#
#
TPS-TER-01 - TPS-TER-10
define host{
use TPS-TER ; Inherit default values from a template
host_name TPS-TER-01
alias TERMINAL DE PASSAGEIROS - TERREO 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
136
}
define host{
}
define host{
}
define host{
}
#
FIM TERMINAL DE PASSAGEIROS - TERREO
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
TPS-TER ; The name of the hostgroup
alias TERMINAL DE PASSAGEIROS - TERREO ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS TERMINAL DE PASSAGEIROS - TERREO
#==============================================================================
#
#
#
#
define service{
host_name TPS-TER-01 ; The name of the host the service is associated with
}
define service{
137
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM SERVICOS TERMINAL DE PASSAGEIROS - TERREO
138
ANEXO 22 – Arquivo de configuração do Nagios: “vah.cfg”.
###############################################################################
# vah.CFG - SAMPLE CONFIG FILE FOR MONITORING A VIA DE ACESSO AOS HANGARES - VAH MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#
#==============================================================================
#
STVV VIA DE ACESSO AOS HANGARES
#==============================================================================
#
#
#
VAH-01 A VAH-06
#
define host{
use VAH ; Inherit default values from a template
host_name VAH-01 ; The name we're giving to this host
alias VIA DE ACESSO AOS HANGARES 01 ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
}
define host{
}
# FIM VIA DE ACESSO AOS HANGARES
###############################################################################
###############################################################################
#
139
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
VAH
alias VIA DE ACESSO AOS HANGARES ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#
#==============================================================================
#
SERVICOS VIA DE ACESSO AOS HANGARES
#==============================================================================
#
#
VAH-01 A VAH-06
#
define service{
host_name VAH-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
define service{
140
}
define service{
}
#
FIM VIA DE ACESSO AOS HANGARES
141
ARQUIVOS DE CONFIGURAÇÃO DO SIMOVE:
ANEXO 23 – Arquivo de configuração do Nagios: “area2.cfg:.
###############################################################################
# area2.CFG - SAMPLE CONFIG FILE FOR MONITORING A AREA2 MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE AREA2
#==============================================================================
#
#
#
AREA2-01 A AREA2-10
#
define host{
use SIMOVE-AREA2 ; Inherit default values from a template
host_name AREA2-01
alias P044 - Entre hangares da Sol e Policia Militar ; A longer name associated with the host
}
define host{
host_name AREA2-02
alias P045 - poste proximo a entrada dos hangares ; A longer name associated with the host
}
define host{
host_name AREA2-03
alias P046 - poste proximo ao portao hangares (fundo) ; A longer name associated with the host
}
define host{
host_name AREA2-04
alias P049 - Curva da Fibra (Ponto 02 no AutoCad) ; A longer name associated with the host
}
define host{
host_name AREA2-05
alias P050 - Poste adicional ; A longer name associated with the host
}
define host{
host_name AREA2-06
alias P077 - Poste adicional (externo) - P116 ; A longer name associated with the host
}
define host{
host_name AREA2-07
142
alias P116 - Poste adicional - P050 ; A longer name associated with the host
}
define host{
host_name AREA2-08
alias P122 - [Portao A] - P021 ; A longer name associated with the host
}
define host{
host_name AREA2-09
alias P126 - Entre hangares da Sol e Policia Militar - P044 ; A longer name associated with the host
}
define host{
host_name AREA2-10
alias P127 - poste proximo a entrada dos hangares - P045 ; A longer name associated with the host
}
#
FIM AREA 2
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
SIMOVE-AREA2 ; The name of the hostgroup
alias SIMOVE - AREA 2 ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO AREA 2
#==========================================================================================
========================
#
#
# AREA2-01 a AREA2-10
#
define service{
host_name AREA2-01 ; The name of the host the service is associated with
}
define service{
143
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM DE AREA 2
144
ANEXO 24 – Arquivo de configuração do Nagios: “area3.cfg”.
###############################################################################
# area3.CFG - SAMPLE CONFIG FILE FOR MONITORING A AREA 3 MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE AREA3
#==============================================================================
#
#
#
AREA3-01 A AREA3-04
#
define host{
host_name AREA3-01
alias P056 - Entre P057 e P059 ; A longer name associated with the host
}
define host{
host_name AREA3-02
alias P057 - Poste novo proximo Hangar Abelha ; A longer name associated with the host
}
define host{
host_name AREA3-03
alias P081 - Hangar Abelha - P057 ; A longer name associated with the host
}
define host{
host_name AREA3-04
alias P130 - Entre P057 e P059 - P056 ; A longer name associated with the host
}
#
FIM AREA 3
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
145
hostgroup_name
SIMOVE-AREA3 ; The name of the hostgroup
alias SIMOVE - AREA 3 ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO AREA3
#==========================================================================================
========================
#
#
# AREA3-01 a AREA3-04
#
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM AREA 3
146
ANEXO 25 – Arquivo de configuração do Nagios: “cercop.cfg”.
###############################################################################
# cercop.CFG - SAMPLE CONFIG FILE FOR MONITORING A CERCA OPERACIONAL MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE CERCA OPERACIONAL
#==============================================================================
#
#
#
CERC-OP-01 A CERC-OP-08
#
define host{
use SIMOVE-CERC-OP ; Inherit default values from a template
host_name CERC-OP-01
alias P059 - poste do canto da cerca na cabeceira 35 ; A longer name associated with the host
}
define host{
alias P060 - poste adicional da cabeceira 35 ; A longer name associated with the host
}
define host{
alias P061 - portao proximo ao VOR ; A longer name associated with the host
}
define host{
alias P062 - poste proximo a biruta ; A longer name associated with the host
}
define host{
alias P063 - poste proximo ao radar ; A longer name associated with the host
}
define host{
alias P064 - poste adicional proximo a fazendinha ; A longer name associated with the host
}
define host{
alias P117 - poste adicional proximo a fazendinha - P064 ; A longer name associated with the host
}
147
define host{
alias P128 - poste adicional da cabeceira 35 - P060 ; A longer name associated with the host
}
define host{
alias P131 - poste do canto da cerca na cabeceira 35 - P059 ; A longer name associated with the host
}
define host{
alias P132 - portao proximo do VOR - P061 ; A longer name associated with the host
}
#
FIM CERCA OPERACIONAL
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
SIMOVE-CERC-OP ; The name of the hostgroup
alias SIMOVE - CERCA OPERACIONAL ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO CERCA OPERACIONAL
#==========================================================================================
========================
#
#
# CERC-OP-01 a CERC-OP-08
#
define service{
host_name CERC-OP-01 ; The name of the host the service is associated with
}
define service{
148
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM DE CERCA OPERACIONAL
149
ANEXO 26 – Arquivo de configuração do Nagios: “norte.cfg”.
###############################################################################
# norte.CFG - SAMPLE CONFIG FILE FOR MONITORING A LIMITE NORTE MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE LIMITE NORTE
#==============================================================================
#
#
#
NORTE-01 A NORTE-03
#
define host{
use SIMOVE-NORTE ; Inherit default values from a template
host_name NORTE-01
alias P001 - Cerca externa proximo cabeceira 17 ; A longer name associated with the host
}
define host{
host_name NORTE-02
alias P114 - Cerca externa proximo cabeceira 17 ; A longer name associated with the host
}
define host{
host_name NORTE-03
alias P115 - poste em frente ao SCI - P019 ; A longer name associated with the host
}
#
FIM LIMITE NORTE
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
SIMOVE-NORTE ; The name of the hostgroup
alias SIMOVE - LIMITE NORTE ; Long name of the group
}
150
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO LIMITE NORTE
#==========================================================================================
========================
#
#
# NORTE-01 a NORTE-08
#
define service{
host_name NORTE-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
#
FIM DE LIMITE NORTE
151
ANEXO 27 – Arquivo de configuração do Nagios: “patio.cfg”.
###############################################################################
# patio.CFG - SAMPLE CONFIG FILE FOR MONITORING A PATIO MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE PATIO
#==============================================================================
#
#
ABRANGENCIA DE IPS: .224.X A SEQUENCIA DO IP NAO ESTA POR LOCAL
#
#
define host{
use SIMOVE-PATIO ; Inherit default values from a template
host_name PATIO-01 ; The name we're giving to this host
alias P019 - Poste em frente ao SCI ; A longer name associated with the host
}
define host{
alias P021 - Poste em frente ao portao A ; A longer name associated with the host
}
define host{
alias P027 - Posto abastecimento BR ; A longer name associated with the host
}
define host{
alias P029 - MOP direito - portao de embarque ; A longer name associated with the host
}
define host{
alias P031 - TPS meio. Carrinhos de bagagem ; A longer name associated with the host
}
define host{
alias P037 - Entre os hangares da TAM e Trip ; A longer name associated with the host
}
define host{
alias P038 - entre os hangares da Trip e Fenix ; A longer name associated with the host
}
152
define host{
alias P039 - Entre os hangares da CHC e Quality ; A longer name associated with the host
}
define host{
alias P040 - Predio ao lado do BR Aviation (Fiscais) ; A longer name associated with the host
}
define host{
alias P043 - Entre os hangares da Alianca e Asta ; A longer name associated with the host
}
#
FIM PATIO
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
SIMOVE-PATIO
alias SIMOVE - PATIO ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO PATIO
#==========================================================================================
========================
#
#
# PATIO-01 a PATIO-08
#
define service{
host_name PATIO-01 ; The name of the host the service is associated with
retry_check_interval 1 ; Re-check the service every minute until its final/hard state is dPATIOrmined
}
define service{
153
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM DE PATIO
154
ANEXO 28 – Arquivo de configuração do Nagios: “portaoa.cfg”.
###############################################################################
# portaoa.CFG - SAMPLE CONFIG FILE FOR MONITORING A PORTAO A MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE PORTAO A
#==============================================================================
#
#
#
PORTAO-A-01 A PORTAO-A-05
#
define host{
use SIMOVE-PORTAO-A ; Inherit default values from a template
host_name PORTAO-A-01
alias P024 - Portão externo do do SCI ; A longer name associated with the host
}
define host{
alias P087 - Acesso ao SCI ; A longer name associated with the host
}
define host{
alias P088 - Acesso ao SCI ; A longer name associated with the host
}
define host{
alias P093 - Portão A - Interno pátio ; A longer name associated with the host
}
define host{
alias P094 - Portão A - Interno pátio ; A longer name associated with the host
}
#
FIM DE PORTAO A
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
155
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
SIMOVE-PORTAO-A
alias SIMOVE - PORTAO A ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO PORTAO A
#==========================================================================================
========================
#
#
# PORTAO-A-01 a PORTAO-A-05
#
define service{
host_name PORTAO-A-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM DE PORTAO A
156
ANEXO 29 – Arquivo de configuração do Nagios: “tecainternacional.cfg”.
###############################################################################
# tecainternacional.CFG - SAMPLE CONFIG FILE FOR MONITORING A TECA INTERNACIONAL MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE TECA INTERNACIONAL
#==============================================================================
#
#
#
TECA-INTERNACIONAL-01 A TECA-INTERNACIONAL--08
#
define host{
use SIMOVE-TIL ; Inherit default values from a template
host_name TECA-INTERNACIONAL-01 ; The name we're giving to this host
alias P033 - TECA Internacional ; A longer name associated with the host
}
define host{
}
define host{
}
define host{
}
define host{
alias P075 - Teca Internacional - portão externo ; A longer name associated with the host
}
define host{
alias P077 - Teca Internacional - P074 ; A longer name associated with the host
}
define host{
alias P079 - Teca Internacional - P074 ; A longer name associated with the host
}
157
#
FIM DE TECA INTERNACIONAL
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
SIMOVE-TIL
alias SIMOVE - TECA INTERNACIONAL ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO TECA INTERNACIONAL
#==========================================================================================
========================
#
#
# TECA-INTERNACIONAL-01 a TECA-INTERNACIONAL-07
#
define service{
host_name TECA-INTERNACIONAL-01 ; The name of the host the service is associated with
}
define service{
}
define service{
}
define service{
158
}
define service{
}
define service{
}
define service{
}
#
FIM DE TECA INTERNACIONAL
159
ANEXO 30 – Arquivo de configuração do Nagios: “tecanacional.cfg”.
###############################################################################
# tecanacional.CFG - SAMPLE CONFIG FILE FOR MONITORING A TECA NACIONAL MACHINE
#
#
#
#
#
#
MAT.: 147432-7
#
###############################################################################
###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################
#
#
#==============================================================================
#
SIMOVE TECA NACIONAL
#==============================================================================
#
#
#
TECANACIONAL-01 A TECANACIONAL-15
#
define host{
use SIMOVE-TNL ; Inherit default values from a template
host_name TECA-NACIONAL-01
alias P002 - Teca Nacional - Pequenos Volumes ; A longer name associated with the host
}
define host{
alias P003 - Teca Nacional - Gate 1 ; A longer name associated with the host
}
define host{
alias P004 - Teca Nacional - Gate 2 ; A longer name associated with the host
}
define host{
alias P005 - Teca Nacional - Gate 3
; A longer name associated with the host
}
define host{
alias P013 - Teca Nacional - Central do galpão ; A longer name associated with the host
}
define host{
alias P016 - Teca Nacional - via de circulação ; A longer name associated with the host
}
define host{
alias P076 - Teca Nacional - P016 ; A longer name associated with the host
}
160
define host{
alias P084 - Teca Nacional - portão de acesso interno ; A longer name associated with the host
}
define host{
alias P085 - Teca Nacional - portão de acesso interno ; A longer name associated with the host
}
define host{
alias P096 - Desktop Videowall 3/4 - Sala Teca Nacional ; A longer name associated with the host
}
#
FIM DE TECA NACIONAL
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
this group
#
#define hostgroup{
#
hostgroup_name
windows-servers
#
#
}
define hostgroup{
hostgroup_name
SIMOVE-TNL
alias SIMOVE - TECA NACIONAL ; Long name of the group
}
###############################################################################
###############################################################################
#
#
###############################################################################
###############################################################################
#==========================================================================================
========================
#
SERVICO TECA NACIONAL
#==========================================================================================
========================
#
#
# TECANACIONAL-01 a TECANACIONAL-15
#
define service{
host_name TECA-NACIONAL-01 ; The name of the host the service is associated with
}
define service{
161
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
define service{
}
#
FIM DE TECA NACIONAL

06/02 Implantação de ferramenta de snmp para o setor de

Transcrição

Documentos relacionados

.Serviços

Interreg Europe - Second call letter of support template

Not waiting to live, not living to wait.

Magento Computer theme Installation Guide

2-5 E2 Series - Self lubrication Kit for Linear Guideways

Using Interval Graphs in an Order Processing Optimization

1 Swedish Phonetic Text - Acapela Group

Language Manual

User Guide - SP Upgrade - Os melhores cursos online do Brasil

Minutes of the Board of Directors´ Meeting BR PROPERTIES S.A