Procedimento SNMP Nobreak Maximus

Procedimento para integração e envio de e-mails
com Gerente SNMP

1- Objetivo...........................................................................................................................3
2- Requisitos para execução deste procedimento..............................................................3
3- Instalação do PRTG no Windows.....................................................................................3
4- Configuração para leitura SNMP do nobreak..................................................................8
5- Importando a MIB para o PRTG.....................................................................................14
6- Configurando o nobreak no PRTG e habilitando o envio de e-mail..............................20
7- Configuração do e-mail para notificações.....................................................................30
8- Configuração das notificações de eventos....................................................................34
Anexo A – MIB PPC................................................................................................................41
1- Objetivo
Este procedimento visa descrever a configuração para envio de e-mails, o monitoramento das
traps e integração do sistema em gerente SNMP padrão de mercado.
As configurações que serão abordadas neste procedimento são básicas, portanto, não sendo
responsabilidade da Maximus a intervenção ou suporte para instalação do software gerente
SNMP.
Este procedimento deve ser executado passo a passo, como descrito nos tópicos, para que seja
obtido a configuração correta e ocorra as notificações.
2- Requisitos para execução deste procedimento

Para configuração e testes foi necessário a utilização dos seguintes softwares e hardwares:
 Computador com o sistema operacional Windows 10 – home

 Software de gerenciamento SNMP PRTG
 Software para importar a MIB para o PRTG Paessler MIB IMPORTER
 Nobreak com adaptador SNMP
 MIB de gerenciamento do nobreak (disponível no link e anexo A deste procedimento)
 Acesso a rede de computadores
 Usuário administrador
 Servidor de e-mail SMTP
3- Instalação do PRTG no Windows.

O software PRTG é disponibilizado gratuitamente por 30 dias com todas as funções com 9990
sensores, porém, após este período o software limita em 90 sensores.
Para realizar o download basta acessar o link abaixo, que será redirecionado para o site da
Paessler.
https://www.br.paessler.com/PRTG
Ao clicar em realizar o download é apresentado uma chave de licença, recomendamos que

salve esta informação em algum bloco de notas, caso seja solicitado durante a instalação.
Após concluir o download do software, basta seguir o passo a passo abaixo:
 Clique duas vezes no instalador, após sua inicialização escolha o idioma a ser utilizado
pela instalação.
 Clique em ok
 Aceite o contrato do software e clique em avançar
 Insira um endereço de e-mail válido
 Aguarde a validação da chave de licença pelo software

 A instalação será iniciada automaticamente após validação das licenças.
 Aguarde o processo de instalação e inicialização do software
 Com a inicialização dos serviços do PRTG será aberto o seu navegador WEB padrão.
 Aguarde a liberação para acesso ao software;
 O login e senha padrão é prtgadmin e em seguida basta clicar em “Login”
 O PRTG ao ser iniciado, irá carregar algumas informações da rede de computadores e

apresentar alguns sensores que são padrões.
 Aguarde que a sonda Local esteja totalmente operacional, não tendo nenhum ícone
vermelho, para prosseguir com a instalação.
4- Configuração para leitura SNMP do nobreak

Após concluir a instalação do software PRTG deve ser feito a configuração do agente SNMP
que se encontra no nobreak.
Neste procedimento foi utilizado um nobreak de 3kVA, online dupla conversão, com nove (9)
baterias.
O procedimento para configuração do nobreak é:
 Desconecte o seu computador da internet e interligue o cabo de rede entre nobreak e

pc.
 Pressione as seguintes teclas “bandeira do Windows + R” e digite ncpa.cpl e clique em
ok.
 Será aberta a tela de configuração dos adaptadores de rede que o computador possui.
 Localize a conexão Ethernet

 Clique com o botão direito do seu mouse, em cima da conexão e em seguida na opção
propriedades
 Será aberta uma nova tela de configuração
 Pela barra de rolagem na vertical, localize o Protocolo IP Versão 4 (TCP/IPv4);

 Clique em Protocolo IP Versão 4 e em seguida será habilitador o campo Propriedades
 Clique em Propriedades será aberto a configuração para alterar o endereço ip do
computador.
 Clique na opção “usar o seguinte endereço IP” e preencha os campos com os seguintes
dados e clique em ok
Endereço IP: 192.168.0.110
Máscara de sub-rede: 255.255.255.0

 Basta fechar as outras telas em seguida.
 Para acessar o nobreak abra um navegador de internet e digite o seguinte endereço
http://192.168.0.100
 O usuário e senha padrão é admin e ao realizar o login a tela apresentada será do

status do produto.
 Na aba “Parameter Settings” localize a opção Network Settings

 Preencha os campos conforme sua configuração da rede de computadores e clique em
ok
Nota.: Recomendamos que seja utilizado um endereço de IP fixo para o nobreak.
 Acesse as configurações de SNMP, pelo campo “SNMP Settings”
 No campo SNMP Settings, ID e Ip user coloque o endereço ip do computador com o

software PRTG
 A comunidade de leitura padrão é public
 No campo “permision” selecione a opção Readable/Writeable
*Clique em ok, mas abaixo na página.

5- Importando a MIB para o PRTG
Com a configuração do endereço IP fixo no nobreak e definição do acesso as leituras e escritas
dos dados via protocolo SNMP é necessário importar a MIB para o PRTG.
Para esse processo é necessário o uso do software Paessler MIB IMPORTER, qual é gratuito e
disponibilizado no link abaixo e a MIB que está disponível no Anexo A.
https://www.paessler.com/tools/mibimporter
Após o download é necessário descompactar o software em uma pasta de fácil acesso e seguir
os passos abaixo.
 Execute o instalador e aceite os termos de licença do software e clique em next.

 Em seguida será aprestando algumas configurações que o software irá aplicar, clique
em next.
 Aguarde a instalação ser concluída e clique no botão Finish

 Excute o software
 Para importar a mib, basta clicar em File e em seguida Import Mib File.
 Na tela seguinte será necessário direcionar para onde a MIB foi salva.
 Selecione a MIB PPC e clique em abrir para que o software carregue para visualização e
aguarde a mensagem de confirmação e em seguida clique em close.
 Novamente clique em File e em seguida na opção Save for the PRTG Network
Monnitor.
 O software irá direcionar o local para salvar com o nome que deseja, já no formato
compatível com o PRTG e habilitando para o uso após clicar no botão salvar.
 Feche o software para finalizar.
6- Configurando o nobreak no PRTG e habilitando o envio de e-mail.

Abra em um navegador o PRTG e realize o login e siga os procedimentos abaixo:
 Clique na opção dispositivos e em seguida Adicionar dispositivo
 Na próxima tela será aprestando em qual sonda o dispositivo deverá ser alocado,
clique na Sonda Local em seguida OK
 Aguarde carregar e preencha os campos para o novo dispositivo
Nome do dispositivo – Nome do local ou potência do nobreak e etc.
Endereço IPV4/ Nome do DNS – Endereço ip que o nobreak está utilizando

Tag – Não é necessário o preenchimento
Ícone do dispositivo – Fica livre a escolha
Identificação de dispositivo(s) e descoberta automática – Manter a opção sem descoberta

automática.
Mantenha todas as credenciais ativas, porém, desativando a Credenciais para dispositivos
SNMP e preenchendo os campos com os seguintes dados:
Por fim cliquem em OK
 O dispositivo foi criado e sendo possível acessar pelo menu suspenso Dispositivos.
 Clique em adicionar Sensor

 Selecione na opção Tecnologia usada a opção SNMP
 Será alterado o campo Tipos de sensores mais usados, colocando todos os itens para
SNMP, localize a Opção Biblioteca SNMP e clique
 Será solicitado a escolha de um arquivo da biblioteca, neste pondo devemos localizar a

MIB que foi carregada pelo Paessler Mib Importer e clique em OK
 O PRTG vai realizar alguns testes enviando códigos OID’s da MIB selecionada para
validar.
 Após confirmação do software será liberado para selecionar quais códigos OIDS serão
monitorados.
Utilizando o campo pesquisa, procure pelos códigos OID’s e selecione com as seguintes
descrições:
Ups smart input line voltage (tensão de entrada do nobreak)

Ups smart output voltage (tensão de saída do nobreak
 Clique no botão criar e aguarde a criação dos sensores e atualização das leituras deles.
 Clique no primeiro sensor XPPC-MIB ups smart input para configurar os valores
 Clique nas engrenagens do ID 2 do sensor e será aberto a configuração das leituras.
Preencha os campos conforme informado abaixo e clique em OK
Unidade - com V
Divisão de escala – 10
 Repita o mesmo processo para configurar a leitura de ups smart output voltage
7- Configuração do e-mail para notificações.

Para que ocorra a notificação por e-mail, caso, ocorra algum evento crítico é necessário
configurar uma conta de e-mail no PRTG.
 Na tela inicial do PRTG, clique em configurações.

 Na opção Administração do sistema, clique em Entrega de notificação.
 Será aberta a tela para configuração do servidor, porta smtp e endereço de e-mail com
senha.
 Após preencher os campos clique no botão salvar.
 Para validar as configurações é disponibilizado um botão de teste das configurações
SMTP.
 Ao realizar o teste é solicitado um endereço de email

 Preencha os campos solicitados e clique em ok
 As configurações estando certas o e-mail de teste será entregue ao destinatário.

8- Configuração das notificações de eventos
Após a configuração da conta de e-mail no PRTG é necessário configurar nos sensores do
nobreak a notificação em caso de eventos críticos.
 Acesse os dispositivos do PRTG e localize e clique no nobreak
 Na tela dos sensores é necessário configurar individualmente, para cada sensor, os

acionadores de notificação.
 Clique no primeiro sensor XPPC-MIB ups smart imput

 Clique em Acionadores de Notificação
 Clique no mais e preencha como demostrado abaixo.
 Clique em adicionar modelo de notificação e preencha como demostrado abaixo

Por fim clique em salvar.
 Para que ocorra a notificação de retorno da rede elétrica é disponibilizado este campo
 Basta repetir a configuração aplicada para o envio do email no caso de falha da rede
elétrica, alterando o texto para Retorno da rede elétrica.
 Clique em salvar acionador para validar as configurações.

 Simulando uma falha da rede elétrica foi confirmado que as configurações de notificação
para envio de e-mails foram realizadas com sucesso.
Falha na rede elétrica:
Retorno da rede elétrica:

Anexo A – MIB PPC
A mib está transcrita neste documento, portanto, basta copiar e colar em um bloco de notas e
salvar como demostrado abaixo.
MIB PPC
--PPC-MIB { iso(1) org(3) dod(6) internet(1) private(4)
-- enterprises(1) ppc(935) }
-- Title: PPC TOP LEVEL MIB
-- Date: January 07, 1994 Version 1.00
--
-- Date: January 17, 1994 Version 1.01
--
-- Date: July 14, 1994 Version 1.02
--
-- Date: May 16, 2003 Version 2.00
XPPC-MIB DEFINITIONS ::= BEGIN
IMPORTS
TRAP-TYPE
FROM RFC-1215
DisplayString
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212
enterprises,
IpAddress
FROM RFC1155-SMI;
ppc OBJECT IDENTIFIER
::= { enterprises 935 }
products OBJECT IDENTIFIER
::= { ppc 1 }
ppcmgmt OBJECT IDENTIFIER
::= { ppc 2 }
hardware OBJECT IDENTIFIER
::= { products 1 }
mconfig OBJECT IDENTIFIER
::= { ppcmgmt 1 }
ups OBJECT IDENTIFIER
::= { hardware 1 }
upsIdentp OBJECT IDENTIFIER
::= { ups 1 }
upsBatteryp OBJECT IDENTIFIER
::= { ups 2 }
upsInputp OBJECT IDENTIFIER
::= { ups 3 }
upsOutputp OBJECT IDENTIFIER
::= { ups 4 }
upsConfigp OBJECT IDENTIFIER
::= { ups 5 }
upsControlp OBJECT IDENTIFIER
::= { ups 6 }
upsTestp OBJECT IDENTIFIER
::= { ups 7 }
upsThreePhase OBJECT IDENTIFIER
::= { ups 8 }
upsEnvironment OBJECT IDENTIFIER
::= { ups 9 }
upsBaseIdent OBJECT IDENTIFIER
::= { upsIdentp 1 }
upsSmartIdent OBJECT IDENTIFIER
::= { upsIdentp 2 }
upsBaseBattery OBJECT IDENTIFIER
::= { upsBatteryp 1 }
upsSmartBattery OBJECT IDENTIFIER
::= { upsBatteryp 2 }
upsBaseInput OBJECT IDENTIFIER
::= { upsInputp 1 }
upsSmartInput OBJECT IDENTIFIER
::= { upsInputp 2 }
upsBaseOutput OBJECT IDENTIFIER
::= { upsOutputp 1 }
upsSmartOutput OBJECT IDENTIFIER
::= { upsOutputp 2 }
upsBaseConfig OBJECT IDENTIFIER
::= { upsConfigp 1 }
upsSmartConfig OBJECT IDENTIFIER
::= { upsConfigp 2 }
upsBaseControl OBJECT IDENTIFIER
::= { upsControlp 1 }
upsSmartControl OBJECT IDENTIFIER
::= { upsControlp 2 }
upsBaseTest OBJECT IDENTIFIER

::= { upsTestp 1 }
upsSmartTest OBJECT IDENTIFIER
::= { upsTestp 2 }
upsThreePhaseBatteryGrp OBJECT IDENTIFIER
::= { upsThreePhase 1 }
upsThreePhaseInputGrp OBJECT IDENTIFIER
upsThreePhaseOutputGrp OBJECT IDENTIFIER
upsThreePhaseBypassGrp OBJECT IDENTIFIER
upsThreePhaseDCandRectifierStatusGrp OBJECT IDENTIFIER
upsThreePhaseUPSStatusGrp OBJECT IDENTIFIER
upsThreePhaseFaultStatusGrp OBJECT IDENTIFIER
upsThreePhaseRatingGrp OBJECT IDENTIFIER
-- object types
-- the ppcmgmt group

-- the mconfig group
mconfigTrapsReceiversNum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of managers to send traps to."
::= { mconfig 1 }
mconfigTrapsReceiversTable OBJECT-TYPE
SYNTAX SEQUENCE OF MconfigTrapsReceiversEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of managers to send traps to. The number of
entries is given by the value of mconfigNumTrapReceivers"
::= { mconfig 2 }
mconfigTrapsReceiversEntry OBJECT-TYPE
SYNTAX MconfigTrapsReceiversEntry
STATUS mandatory
DESCRIPTION
"The managers to send traps to."
INDEX {
trapsIndex }
::= { mconfigTrapsReceiversTable 1 }
MconfigTrapsReceiversEntry ::= SEQUENCE {
trapsIndex INTEGER,
trapsReceiverAddr IpAddress,
receiverCommunityString DisplayString,
severityLevel INTEGER,
receiverAccept INTEGER }
trapsIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The index to a trap receiver entry."
::= { mconfigTrapsReceiversEntry 1 }
trapsReceiverAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP address of the manager to send a trap to."
receiverCommunityString OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The community name to use in the trap when
sent to the manager."
severityLevel OBJECT-TYPE
SYNTAX INTEGER {
information(1),
warning(2),
severe(3) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The severity threshold of traps to send to the manager.
traps are labeled in severity as informational(1), warning(2),
severe(3). Only traps of equal or greater severity than
this value are sent to the manager."
receiverAccept OBJECT-TYPE
SYNTAX INTEGER {
yes(1),
no(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An entry will become active if yes, and will
be deleted if no."
-- the ups group
-- the upsBaseIdent group
upsBaseIdentModel OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The UPS model name (e.g. 'Intelligent 8000E 900VA')."
::= { upsBaseIdent 1 }
upsBaseIdentUpsName OBJECT-TYPE
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An 8 byte ID string identifying the UPS. This object
can be set by the administrator."
::= { upsBaseIdent 2 }
-- the upsSmartIdent group
upsSmartIdentFirmwareRevision OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The firmware revision of the UPS system."
::= { upsSmartIdent 1 }
upsSmartIdentDateOfManufacture OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The date when the UPS was manufactured in mm/dd/yy format."
upsSmartIdentUpsSerialNumber OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An 8-character string identifying the serial number of
the UPS internal microprocessor. This number is set at
the factory. NOTE: This number does NOT correspond to
the serial number on the rear of the UPS."
upsSmartIdentAgentFirmwareRevision OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The firmware revision of the UPS SNMP Proxy agent."

-- the upsBaseBattery group
upsBaseBatteryStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
batteryNormal(2),
batteryLow(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The status of the UPS batteries. A batteryLow(3)
value indicates the UPS will be unable to sustain the
current load, and its services will be lost if power is
not restored. The amount of run time in reserve at the
time of low battery can be configured by the
upsSmartConfigLowBatteryRunTime."
::= { upsBaseBattery 1 }
upsBaseBatteryTimeOnBattery OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The elapsed time in seconds since the UPS has switched
to battery power."
upsBaseBatteryLastReplaceDate OBJECT-TYPE
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The date when the UPS system's batteries were last replaced
in mm/dd/yy format. For UPS models, this value is originally
set in the factory. When the UPS batteries are replaced,
this value should be reset by the administrator."
-- the upsSmartBattery group
upsSmartBatteryCapacity OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The remaining battery capacity expressed in
percent of full capacity."
::= { upsSmartBattery 1 }
upsSmartBatteryVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current battery voltage expressed in 1/10 VDC."

upsSmartBatteryTemperature OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current internal UPS temperature expressed in tenths of
a Celsius degree."
upsSmartBatteryRunTimeRemaining OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The UPS battery run time remaining before battery
exhaustion, in seconds."
upsSmartBatteryReplaceIndicator OBJECT-TYPE
SYNTAX INTEGER {
noBatteryNeedsReplacing(1),
batteryNeedsReplacing(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether the UPS batteries need replacing."

upsSmartBatteryFullChargeVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The fully charged battery voltage of the battery system
used in the UPS, expressed in tenths of a volt."
upsSmartBatteryCurrent OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current battery current expressed in percent of
maximum current."
-- the upsBaseInput group
upsBaseInputPhase OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current AC input phase."

::= { upsBaseInput 1 }
-- the upsSmartInput group
upsSmartInputLineVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current utility line voltage in 1/10 VAC."
::= { upsSmartInput 1 }
upsSmartInputMaxLineVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The maximum utility line voltage in 1/10 VAC over the
previous 1 minute period."
upsSmartInputMinLineVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The minimum utility line voltage in 1/10 VAC over the
previous 1 minute period."

upsSmartInputFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current input frequency to the UPS system in 1/10 Hz."
upsSmartInputLineFailCause OBJECT-TYPE
SYNTAX INTEGER {
noTransfer(1),
highLineVoltage(2),
brownout(3),
blackout(4),
smallMomentarySag(5),
deepMomentarySag(6),
smallMomentarySpike(7),
largeMomentarySpike(8) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The reason for the occurrence of the last transfer
to UPS battery power. The variable is set to
noTransfer(1) if there is no transfer yet. The variable
is set to highLineVoltage(2) if the transfer to battery is
caused by an over voltage greater than the high transfer
voltage. The variable is set to brownout(3) if the duration

of the outage is greater than five seconds and the line
voltage is between 40 percent of the rated output voltage and
the low transfer voltage. The variable is set to blackout(4)
if the duration of the outage is greater than five seconds and
the line voltage is between 40 percent of the rated output voltage
and ground. The variable is set to smallMomentarySag(5)
if the duration of the outage is less than five seconds and
the line voltage is between 40 percent of the rated output voltage
and the low transfer voltage. The variable is set to
deepMomentarySag(6) if the duration of the outage is less
than five seconds and the line voltage is between 40 percent of the
rated output voltage and ground."
-- the upsBaseOutput group
upsBaseOutputStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
onLine(2),
onBattery(3),
onBoost(4),
sleeping(5),
onBypass(6),
rebooting(7),
standBy(8),
onBuck(9) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current state of the UPS. If the UPS is unable
to determine the state of the UPS this variable is set
to unknown(1)."
::= { upsBaseOutput 1 }
upsBaseOutputPhase OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current output phase."
::= { upsBaseOutput 2 }
-- the upsSmartOutput group
upsSmartOutputVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The output voltage of the UPS system in 1/10 VAC."
::= { upsSmartOutput 1 }
upsSmartOutputFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current output frequency of the UPS system in 1/10 Hz."
upsSmartOutputLoad OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current UPS load expressed in percent
of rated capacity."
-- the upsBaseConfig group
upsBaseConfigNumDevices OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of devices that are plugged into the UPS."
::= { upsBaseConfig 1 }
upsBaseConfigDeviceTable OBJECT-TYPE
SYNTAX SEQUENCE OF UpsBaseConfigDeviceEntry
STATUS mandatory
DESCRIPTION
"A list of devices that are plugged into the UPS. The
number of entries is given by the value of
upsBaseConfigNumDevices."
::= { upsBaseConfig 2 }
upsBaseConfigDeviceEntry OBJECT-TYPE
SYNTAX UpsBaseConfigDeviceEntry
STATUS mandatory
DESCRIPTION
"The devices plugged in to the UPS."
INDEX {
indexOfDevice }
::= { upsBaseConfigDeviceTable 1 }
UpsBaseConfigDeviceEntry ::= SEQUENCE {
indexOfDevice INTEGER,
nameOfDevice DisplayString,
vaRatingOfDevice INTEGER,
deviceAccept INTEGER }
indexOfDevice OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The index of the device that is plugged into the UPS."
::= { upsBaseConfigDeviceEntry 1 }
nameOfDevice OBJECT-TYPE
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The name/description of the device plugged into the UPS."
vaRatingOfDevice OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The volt-amp rating of the device plugged into the UPS."
deviceAccept OBJECT-TYPE
SYNTAX INTEGER {
yes(1),
no(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An entry is added if yes, the entry is deleted if no."
-- the upsSmartConfig group

upsSmartConfigRatedOutputVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The nominal output voltage from the UPS in 1/10 VAC.
Possible values are 1000, 1200, 2080, 2200, 2250, 2300
and 2400.
NOTE: Only units that are 2200, 2250, 2300 and 2400 can
be changed. Allowable values are 2200, 2250, 2300 and
2400.
For these adjustable units, if a value other than
a supported value is provided in a set request, the
UPS interprets it as the next lower acceptable value.
If the provided value is lower than the lowest acceptable
value, the lowest acceptable value is used."
::= { upsSmartConfig 1 }
upsSmartConfigHighTransferVolt OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum line voltage in 1/10 VAC allowed before the
UPS system transfers to battery backup.
Allowed value depend on the UPS used:

120 Volt units allow settings of 1290, 1320, 1350, 1380.
If a value other than a supported value is provided in a
set request, the UPS interprets it as the next lower
acceptable value. If the provided value is lower than
the lowest acceptable value, the lowest acceptable
value is used."
upsSmartConfigLowTransferVolt OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The minimum line voltage in 1/10 VAC allowed before the
UPS system transfers to battery backup.
Allowable values depend on the UPS used:
set request, the UPS interprets it as a the next higher
acceptable value. If the provided value is higher than
the highest acceptable value, the highest acceptable

value is used."
upsSmartConfigAlarm OBJECT-TYPE
SYNTAX INTEGER {
timed(1),
atLowBattery(2),
never(3) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A flag indicating how the UPS should handle audible line fail
alarms."
upsSmartConfigAlarmTimer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The time in seconds after initial line failure at which the
UPS begins emitting audible alarms (beeping). This timer is
observerd only if the value of extControlAlarm is timed(2).
Allowed values are 0 or 30 seconds.
set request, the UPS interprets it as a the next lower
acceptable value. If the provided value is lower than
the lowest acceptable value, the lowest acceptable

value is used."
upsSmartConfigMinReturnCapacity OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The minimum battery capacity as a percent of full capacity
required before the UPS will return from a low battery
shutdown condition. In other words, the UPS will not
re-energize the output until the battery capacity is equal
to this value. Allowed values are 0, 10, 25, or 90 percent.
value is used."
upsSmartConfigSensitivity OBJECT-TYPE
SYNTAX INTEGER {
auto(1),
low(2),
medium(3),
high(4) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The sensitivity of the UPS to utility line abnormalities
or noises."
upsSmartConfigLowBatteryRunTime OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The desired run time in seconds once the low battery
condition is reached. Allowed values are 120, 300, 420,
or 600 seconds. During this time the UPS will produce a
constant warning tone which can not be disabled.
value is used."
upsSmartConfigReturnDelay OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The delay in seconds after utility line power returns
before the UPS will turn on. This value is also used
when the UPS comes out of a reboot and before the UPS
wakes up from 'sleep' mode. Allowed values are 0, 60,
180 and 300 seconds.
value is used."
upsSmartConfigShutoffDelay OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The delay in seconds the UPS remains on after being told
to turn off. Allowed values are 12, 18, 24, 30, 36, 42,
48, 54, 60, 120, 180, 240, 300, 360, 420, 480, 540, and
600 seconds.
set request, the UPS interprets it as next higher acceptable
value. If the provided value is higher than the highest
acceptable value, the highest acceptable value is used."
upsSmartConfigUpsSleepTime OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The time in minutes for the UPS to go to 'sleep' when
instructed. When in sleep mode, the UPS will not provide
output power regardless of the input line state. Once the
specified time has elapsed, output power will be restored.
This is a configuration setting. The UPS will not go to
sleep until told to do so by the manager from a management
station.
Any input value is allowed, however the UPS only recognizes
0 - 9999 minutes in one minute increments.
If the provided value is higher than the highest acceptable
value, the highest acceptable value is used."
upsSmartConfigSetEEPROMDefaults OBJECT-TYPE
SYNTAX INTEGER {
noSetEEPROMDefaults(1),
setEEPROMDefaults(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"WRITE: Resets the UPS EEPROM variables to default values.
READ: returns 0"
-- the upsBaseControl group
upsBaseControlConserveBattery OBJECT-TYPE
SYNTAX INTEGER {
noTurnOffUps(1),
turnUpsOffToConserveBattery(2),
turnUpsOffToConserveBatteryDelay(3) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to turnUpsOffToConserveBattery(2)
causes a UPS on battery to be put into 'sleep' mode immediately.
The (10) means suspending time(10 minutes) before turn off UPS.
UPS will turn back on when utility power is restored.
Attempting to turn off a UPS that is not on battery will
result in a badValue error.
Setting this value to noTurnOffUps(1) has no
effect.
The value noTurnOffUps(1) will always be returned
when the variable is read."
::= { upsBaseControl 1 }
-- the upsSmartControl group
upsSmartControlUpsOff OBJECT-TYPE
SYNTAX INTEGER {
noTurnUpsOff(1),
turnUpsOff(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to turnUpsOff(2) causes
the UPS to shut off. When in this state, the UPS
will not provide output power regardless of the input
line state. The on/off switch on the UPS
must be toggled for the UPS to return to operation.
Setting this value to noTurnUpsOff(1) has no
effect.
The value noTurnUpsOff(1) will always be returned
::= { upsSmartControl 1 }
upsSmartControlRebootUps OBJECT-TYPE
SYNTAX INTEGER {
noRebootUps(1),
rebootUps(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to rebootUps(2) causes the
UPS to shut off and turn back on.
Setting this value to noRebootUps(1) has no effect.
The value noRebootUps(1) will always be returned

upsSmartControlUpsSleep OBJECT-TYPE
SYNTAX INTEGER {
noPutUpsToSleep(1),
putUpsToSleep(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to putUpsToSleep(2) causes
the UPS to go to sleep for the time specified by
upsSmartConfigUpsSleepTime.
When in sleep mode, the UPS will not provide output
power regardless of the input line state. Once the
specified time has elapsed, output power will be
restored.
Setting this value to noPutUpsToSleep(1) has no
effect.
The value noPutUpsToSleep(1) will always be returned
upsSmartControlSimulatePowerFail OBJECT-TYPE
SYNTAX INTEGER {
noSimulatePowerFailure(1),
simulatePowerFailure(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to simulatePowerFailure(2) causes
the UPS switch to battery power.
Setting this value to noSimulatePowerFailure(1) has no
effect.
The value noSimulatePowerFailure(1) will always be returned
upsSmartControlFlashAndBeep OBJECT-TYPE
SYNTAX INTEGER {
noFlashAndBeep(1),
flashAndBeep(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"UPS to identify itself by lighting all indicators
and beeping.
Setting this variable to FlashAndBeep(2) causes
the UPS lights all panel indicators and beeps.
Setting this value to noFlashAndBeep(1) has no
effect.
The value noFlashAndBeep(1) will always be returned
upsSmartControlTurnOnUpsLoad OBJECT-TYPE
SYNTAX INTEGER {
noUpsSmartControlTurnOnUpsLoad(1),
upsSmartControlTurnOnUpsLoad(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to upsSmartControlTurnOnUpsLoad(2)
causes the UPS switch back to utility power if utility
power is present.
Setting this value to noUpsSmartControlTurnOnUpsLoad(1)
has no effect.
The value noUpsSmartControlTurnOnUpsLoad(1) will always
be returned when the variable is read."
-- the upsBaseTest group
-- the upsSmartTest group
upsSmartTestDiagnosticSchedule OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
biweekly(2),
weekly(3),
never(4) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The UPS system's automatic battery test schedule."
::= { upsSmartTest 1 }
upsSmartTestDiagnostics OBJECT-TYPE
SYNTAX INTEGER {
noTestDiagnostics(1),
testDiagnostics(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to testDiagnostics(2) causes
the UPS to perform a diagnostic self test.
Setting this value to noTestDiagnostics(1) has no
effect.
The value noTestDiagnostics(1) will always be returned
upsSmartTestDiagnosticsResults OBJECT-TYPE
SYNTAX INTEGER {
ok(1),
failed(2),
invalidTest(3),
testInProgress(4) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The results of the last UPS diagnostics test performed."
upsSmartTestLastDiagnosticsDate OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The date the last UPS diagnostics test was performed in
mm/dd/yy format."
upsSmartTestIndicators OBJECT-TYPE
SYNTAX INTEGER {
noTestIndicators(1),
testIndicators(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to testIndicators(2) causes
the UPS to perform a front panel indicator (lights) test.
Setting this value to noTestIndicators(1) has no effect.

The value noTestIndicators(1) will always be returned
upsSmartTestRuntimeCalibration OBJECT-TYPE
SYNTAX INTEGER {
noPerformCalibration(1),
performCalibration(2),
cancelCurrentCalibration(3) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this variable to performCalibration(2) causes
the UPS to discharge to calibrate the UPS.
The test will only start if the battery capacity is 100 percent.
The test runs until capacity is less than 25 percent.
Setting this variable to cancelCurrentCalibration(3)
after setting performCalibration(2) will cancel the
current discharge.
Setting this variable to noPerformCalibration(1)
will have no effect.
The value noPerformCalibration(1) will always be returned
when the variable is read.
The result of the calibration will be saved in
upsSmartTestCalibrationResult."
upsSmartTestCalibrationResults OBJECT-TYPE
SYNTAX INTEGER {
ok(1),
invalidTest(2),
calibrationInProgress(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The results of the last runtime calibration.
Value ok(1) means a successful runtime calibration.
Value invalidTest(2) indicates last calibration did
not take place since the battery capacity was below
100 percent.
Value calibrationInProgress(3) means a calibration
is occurring now."
upsSmartTestCalibrationDate OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The date the last UPS runtime calibration was
performed in mm/dd/yy format."
-----------------------
--ups ThreePhase group-
-----------------------
upsThreePhaseBatteryVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Battery Voltage"
::= { upsThreePhaseBatteryGrp 1 }
upsThreePhaseBatteryCapacityPercentage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Battery Capacity Percentage"
upsThreePhaseBatteryTimeRemain OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Battery Time Remain (unit is Minute)"
upsThreePhaseBatteryCurrent OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Battery Electric Current"
upsThreePhaseBatteryTemperature OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Battery Temperature"
upsThreePhaseInputFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Input Frequency"
::= { upsThreePhaseInputGrp 1 }
upsThreePhaseInputVoltageR OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Input VoltageR"
upsThreePhaseInputVoltageS OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Input VoltageS"
upsThreePhaseInputVoltageT OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Input VoltageT"
upsThreePhaseOutputFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Output Frequency"
::= { upsThreePhaseOutputGrp 1 }
upsThreePhaseOutputVoltageR OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Output VoltageR"
upsThreePhaseOutputVoltageS OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Output VoltageS"
upsThreePhaseOutputVoltageT OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Output VoltageT"
upsThreePhaseOutputLoadPercentageR OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Load PercentageR"
upsThreePhaseOutputLoadPercentageS OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Load PercentageS"
upsThreePhaseOutputLoadPercentageT OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Load PercentageT"
upsThreePhaseBypassSourceFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass Frequency"
::= { upsThreePhaseBypassGrp 1 }
upsThreePhaseBypssSourceVoltageR OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass VoltageR"
upsThreePhaseBypssSourceVoltageS OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass VoltageS"
upsThreePhaseBypssSourceVoltageT OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass VoltageT"
upsThreePhaseDCandRectifierStatusRecRotError OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Rectifier Rotation Error"
::= { upsThreePhaseDCandRectifierStatusGrp 1 }
upsThreePhaseDCandRectifierStatusLowBatteryShutdown OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Low Battery Shutdown"
upsThreePhaseDCandRectifierStatusLowBattery OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Low Battery"
upsThreePhaseDCandRectifierStatusInAndOut OBJECT-TYPE
SYNTAX INTEGER {
threeInOneOut(2),
threeInThreeOut(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"In And Put"
upsThreePhaseDCandRectifierStatusBatteryStatus OBJECT-TYPE
SYNTAX INTEGER {
backup(4),
acnormal(5) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Back Status"
upsThreePhaseDCandRectifierStatusChargeStatus OBJECT-TYPE
SYNTAX INTEGER {
boost(6),
float(7),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Charge Status"
upsThreePhaseDCandRectifierStatusRecOperating OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Rectifier Operating"
upsThreePhaseUPSStatusBypassFreqFail OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass Status"
::= { upsThreePhaseUPSStatusGrp 1 }
upsThreePhaseUPSStatusManualBypassBreaker OBJECT-TYPE
SYNTAX INTEGER {
close(8),
open(9) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Breaker Status"
upsThreePhaseUPSStatusACStatus OBJECT-TYPE
SYNTAX INTEGER {
normal(10),
abnormal(11) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"AC Status"
upsThreePhaseUPSStaticSwitchMode OBJECT-TYPE
SYNTAX INTEGER {
invermode(12),
bypassmode(13) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Switch Mode"
upsThreePhaseUPSStatusInverterOperating OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Operating"
upsThreePhaseFaultStatusEmergencyStop OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Emergency Stop"
::= { upsThreePhaseFaultStatusGrp 1 }
upsThreePhaseFaultStatusHighDCShutdown OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"High DC Shutdown"
upsThreePhaseFaultStatusBypassBreaker OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass Breaker"
upsThreePhaseFaultStatusOverLoad OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Over Load"
upsThreePhaseFaultStatusInverterOutputFail OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Output Fail"
upsThreePhaseFaultStatusOverTemperature OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Over Temperature"
upsThreePhaseFaultStatusShortCircuit OBJECT-TYPE
SYNTAX INTEGER {
yes(14),
no(16) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Short Circuit"
upsThreePhaseRatingRectifierVoltage OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Rectifier Voltage"
::= { upsThreePhaseRatingGrp 1 }
upsThreePhaseRatingRectifierFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Rectifier Frequency"
upsThreePhaseRatingBypassVoltage OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass Voltage"
upsThreePhaseRatingBypassFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Bypass Frequency"
upsThreePhaseRatingOutputVoltage OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Output Voltage"
upsThreePhaseRatingOutputFrequency OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Output Frequency"
upsThreePhaseRatingBatteryVoltage OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Battery Voltage"
upsThreePhaseRatingPower OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Power Rating"
-----------------------
-----------------------
upsEnvStatus OBJECT IDENTIFIER ::= { upsEnvironment 1 }
upsEnvTemperature OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ambient environment temperature."
::= { upsEnvStatus 1 }
upsEnvHumidity OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The environment humidity."
upsEnvOverTemperature OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Alarm dupsAlarmOverTemperature on when the environment

temperature over the value."
::= { upsEnvSetting 1 }
upsEnvOverHumidity OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Alarm dupsAlarmOverHumidity on when the environment
humidity over the value."
upsEnvSecurity1 OBJECT-TYPE
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Security status"
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Security status"
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Security status"
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Security status"
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Security status"
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Security status"
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Security status"
upsEnvWater OBJECT-TYPE
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Water status"
upsEnvSmoke OBJECT-TYPE
SYNTAX INTEGER {
normal(1),
abnormal(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Smoke status"
upsEnvSetting OBJECT IDENTIFIER ::= { upsEnvironment 2 }
upsEnvUnderTemperature OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Alarm dupsAlarmUnderTemperature on when the environment
temperature below the value."
upsEnvUnderHumidity OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Alarm dupsAlarmUnderHumidity on when the environment
humidity below the value."
communicationLost TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"SEVERE: Communication to the UPS has been lost. Steps
to reestablish communication are in progress."
--#TYPE "PPC UPS: Communication failure"
--#SUMMARY "Communication to the UPS has been lost."
--#ARGUMENTS { }
--#SEVERITY CRITICAL
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE DEGRADED
::= 1
upsOverLoad TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"SEVERE: The UPS has sensed a load greater than 100 percent
of its rated capacity."
--#TYPE "PPC UPS: UPS overload"
--#SUMMARY "The UPS has sensed a load greater than 100 percent of its rated capacity."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE DEGRADED
::= 2
upsDiagnosticsFailed TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"SEVERE: The UPS failed its internal diagnostic self-test."
--#TYPE "PPC UPS: Failed self-test"
--#SUMMARY "The UPS has failed its internal diagnostic self-test."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE DEGRADED
::= 3
upsDischarged TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"SEVERE: The UPS just started a runtime calibration
discharge. The UPS batteries are being discharged."
--#TYPE "PPC UPS: Deep discharge"
--#SUMMARY "The UPS has just started a runtime calibration discharge."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE DEGRADED
::= 4
upsOnBattery TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The UPS has switched to battery backup power."
--#TYPE "PPC UPS: On battery"
--#SUMMARY "The UPS has switched to battery backup power."
--#ARGUMENTS { }
--#SEVERITY MAJOR
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE OPERATIONAL
::= 5
boostOn TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The UPS has enabled Boost."
--#TYPE "PPC UPS: SmartBoost"
--#SUMMARY "The UPS has enabled Boost."
--#ARGUMENTS { }
--#SEVERITY MINOR
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 6
lowBattery TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"SEVERE: The UPS batteries are low and will soon be exhausted.
If utility power is not restored the UPS will put itself
to 'sleep' and immediately cut power to the load."
--#TYPE "PPC UPS: Low battery"
--#SUMMARY "The UPS batteries are low and will soon be exhausted."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE DEGRADED
::= 7
communicationEstablished TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: Communication with the UPS has been
established."
--#TYPE "PPC UPS: Communication established"
--#SUMMARY "Communication with the UPS has been established."
--#ARGUMENTS { }
--#SEVERITY INFORMATIONAL
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 8
powerRestored TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: Utility power has been restored."
--#TYPE "PPC UPS: Utility restored"
--#SUMMARY "Normal power has been restored to the UPS."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 9
upsDiagnosticsPassed TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: The UPS passed its internal self-test."
--#TYPE "PPC UPS: Passed self-test"
--#SUMMARY "The UPS has passed its internal self-test."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 10
returnFromLowBattery TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: The UPS has returned from a low battery
condition."
--#TYPE "PPC UPS: Battery normal"
--#SUMMARY "The UPS has returned from a low battery condition."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 11
upsTurnedOff TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The UPS has been turned 'off' by the
management station."
--#TYPE "PPC UPS: Switching off"
--#SUMMARY "The UPS is being switched off by a management station."
--#ARGUMENTS { }
--#SEVERITY MAJOR
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE NONOPERATIONAL
::= 12
upsSleeping TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The UPS is entering 'sleep' mode. Power
to the load will be cut off."

--#TYPE "PPC UPS: Going to sleep"
--#SUMMARY "The UPS is going into sleep mode."
--#ARGUMENTS { }
--#SEVERITY MAJOR
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 13
upsWokeUp TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: The UPS woke up from 'sleep' mode. Power
to the load has been restored."
--#TYPE "PPC UPS: Wake up"
--#SUMMARY "The UPS has woke up from sleep mode."
--#ARGUMENTS { }
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 14
upsRebootStarted TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The UPS has started its reboot sequence. After
the specified delay the UPS will perform a reboot."
--#TYPE "PPC UPS: Starting reboot"
--#SUMMARY "The UPS has started its reboot sequence."
--#ARGUMENTS { }
--#SEVERITY MAJOR
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
::= 15
envOverTemperature TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The environment temperature exceed the normal value."
::= 16
envTemperatureNormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: The environment temperature is normal."
::= 17
envOverHumidity TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The environment humidity exceed the normal value."
::= 18
envHumidityNormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: The environment humidity is normal."
::= 19
envSmokeAbnormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Smoke is abnormal."
::= 20
envWaterAbnormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Water is abnormal."
::= 21
envSecurityAbnormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Security is abnormal."
::= 22
--envSmokeNormal TRAP-TYPE
-- ENTERPRISE ppc
-- DESCRIPTION
-- "INFORMATION: Smoke is normal."
-- ::= 23
envWaterNormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"INFORMATION: Water is normal."
::= 24
--envSecurityNormal TRAP-TYPE
-- ENTERPRISE ppc
-- DESCRIPTION
-- "INFORMATION: Security is normal."
-- ::= 25
envGasAbnormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Gas Alarm"
::= 26
upsTemp TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: UPS Temperature Overrun"
::= 27
upsLoadNormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: UPS Load Normal"
::= 28
upsTempNormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: UPS temperature Normal"
::= 29
envUnderTemperature TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The environment temperature below the normal value."
::= 30
envUnderHumidity TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The environment humidity below the normal value."
::= 31
upsBypass TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: The UPS is entering 'bypass' mode."
::= 32
envSecurity1 TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Security1 Alarm."
::= 33
ENTERPRISE ppc
DESCRIPTION
::= 34
ENTERPRISE ppc
DESCRIPTION
::= 35
ENTERPRISE ppc
DESCRIPTION
::= 36
ENTERPRISE ppc
DESCRIPTION
::= 37
ENTERPRISE ppc
DESCRIPTION
::= 38
ENTERPRISE ppc
DESCRIPTION
::= 39
--envSecurity1Return TRAP-TYPE
-- ENTERPRISE ppc
-- DESCRIPTION
-- "WARNING: Security1 Normal."

-- ::= 40
-- ENTERPRISE ppc
-- DESCRIPTION
-- "WARNING: Security2 Normal"
-- ::= 41
-- ENTERPRISE ppc
-- DESCRIPTION
-- ::= 42
-- ENTERPRISE ppc
-- DESCRIPTION
-- ::= 43
-- ENTERPRISE ppc
-- DESCRIPTION
-- ::= 44
-- ENTERPRISE ppc
-- DESCRIPTION
-- ::= 45
-- ENTERPRISE ppc
-- DESCRIPTION
-- ::= 46
upsRecroterror TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Rectifier Rotation Error"
::= 47
upsBypassFreFail TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Bypass Frequency Fail"
::= 48
upsBypassacnormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Bypass AC Normal"
::= 49
upsBypassacabnormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: Bypass AC Abnormal"
::= 50
upsTest TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: UPS Test"
::= 51
upsScheduleShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"WARNING: UPS Schedule Shutdown"
::= 52
upsBypassReturn TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS return from Bypass Mode"
::= 53
upsShortCircuitShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Short Circuit Shutdown"
::= 54
upsInverterOutputFailShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Inverter Output Fail Shutdown"
::= 55
upsBypassBreadkerOnShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Manual Bypass Breaker on Shutdown"
::= 56
upsHighDCShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS High DC Shutdown"
::= 57
upsEmergencyStop TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Emergency Stop"
::= 58
upsInverterMode TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Static Switch in Inverter Mode"
::= 59
upsBypassMode TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Static Switch in Bypass Mode"
::= 60
upsOverTemperatureShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Over Temperature Shutdown"
::= 61
upsOverLoadShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Overload Shutdown"
::= 62
upsCapacityUnderrun TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Capacity Underrun"
::= 63
upsCapacityNormal TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Capacity Normal"
::= 64
upsLowBatteryShutdown TRAP-TYPE
ENTERPRISE ppc
DESCRIPTION
"The UPS Low Battery Shutdown"
::= 67
END

Procedimento SNMP Nobreak Maximus

Enviado por

Direitos autorais:

Formatos disponíveis

Procedimento SNMP Nobreak Maximus

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Procedimento SNMP Nobreak Maximus

Enviado por

Direitos autorais:

Formatos disponíveis

Procedimento para integração e envio de e-mails

com Gerente SNMP

2- Requisitos para execução deste procedimento

 Computador com o sistema operacional Windows 10 – home

3- Instalação do PRTG no Windows.

Ao clicar em realizar o download é apresentado uma chave de licença, recomendamos que

Após concluir o download do software, basta seguir o passo a passo abaixo:

 Insira um endereço de e-mail válido

 Aguarde a validação da chave de licença pelo software

 O PRTG ao ser iniciado, irá carregar algumas informações da rede de computadores e

4- Configuração para leitura SNMP do nobreak

O procedimento para configuração do nobreak é:

 Desconecte o seu computador da internet e interligue o cabo de rede entre nobreak e

 Localize a conexão Ethernet

 Será aberta uma nova tela de configuração

 Pela barra de rolagem na vertical, localize o Protocolo IP Versão 4 (TCP/IPv4);

Endereço IP: 192.168.0.110

Máscara de sub-rede: 255.255.255.0

 O usuário e senha padrão é admin e ao realizar o login a tela apresentada será do

 Na aba “Parameter Settings” localize a opção Network Settings

Nota.: Recomendamos que seja utilizado um endereço de IP fixo para o nobreak.

 Acesse as configurações de SNMP, pelo campo “SNMP Settings”

 No campo SNMP Settings, ID e Ip user coloque o endereço ip do computador com o

*Clique em ok, mas abaixo na página.

 Execute o instalador e aceite os termos de licença do software e clique em next.

 Aguarde a instalação ser concluída e clique no botão Finish

6- Configurando o nobreak no PRTG e habilitando o envio de e-mail.

 Clique na opção dispositivos e em seguida Adicionar dispositivo

Nome do dispositivo – Nome do local ou potência do nobreak e etc.

Endereço IPV4/ Nome do DNS – Endereço ip que o nobreak está utilizando

Ícone do dispositivo – Fica livre a escolha

Identificação de dispositivo(s) e descoberta automática – Manter a opção sem descoberta

 Clique em adicionar Sensor

 Será solicitado a escolha de um arquivo da biblioteca, neste pondo devemos localizar a

Ups smart input line voltage (tensão de entrada do nobreak)

Preencha os campos conforme informado abaixo e clique em OK

7- Configuração do e-mail para notificações.

 Na tela inicial do PRTG, clique em configurações.

 Ao realizar o teste é solicitado um endereço de email

 As configurações estando certas o e-mail de teste será entregue ao destinatário.

 Acesse os dispositivos do PRTG e localize e clique no nobreak

 Na tela dos sensores é necessário configurar individualmente, para cada sensor, os

 Clique no primeiro sensor XPPC-MIB ups smart imput

 Clique no mais e preencha como demostrado abaixo.

 Clique em adicionar modelo de notificação e preencha como demostrado abaixo

 Clique em salvar acionador para validar as configurações.

Falha na rede elétrica:

Retorno da rede elétrica:

--PPC-MIB { iso(1) org(3) dod(6) internet(1) private(4)

-- Title: PPC TOP LEVEL MIB

-- Date: January 07, 1994 Version 1.00

-- Date: January 17, 1994 Version 1.01

-- Date: July 14, 1994 Version 1.02

-- Date: May 16, 2003 Version 2.00

XPPC-MIB DEFINITIONS ::= BEGIN

ppc OBJECT IDENTIFIER

::= { enterprises 935 }

products OBJECT IDENTIFIER

ppcmgmt OBJECT IDENTIFIER