UPSMAN
AI MIB Summary
Standard SNMP MIB module defining data structures for UPSMAN.
55
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
55 total| Object Name |
|---|
upsman OBJECT IDENTIFIER .1.3.6.1.4.1.1356 |
RFC1213-MIB Unknown .1.3.6.1.4.1.1356 |
communicationLostSEVERE: Communication to the UPS has been lost. Check cable or network
connections, steps to reestablish communication are in progress. TRAP-TYPE .1.3.6.1.4.1.1356.0.1 |
upsOverloadSEVERE: The UPS has sensed a load greater than 100 percent
of its rated capcity. TRAP-TYPE .1.3.6.1.4.1.1356.0.2 |
upsTurnedOffWARNING: The UPS has been turned 'off' by the management station. TRAP-TYPE .1.3.6.1.4.1.1356.0.3 |
communicationEstablishedINFORMATION: Communication with the UPS has been established. TRAP-TYPE .1.3.6.1.4.1.1356.0.4 |
powerRestoredINFORMATION: Utility power has been restored. TRAP-TYPE .1.3.6.1.4.1.1356.0.5 |
upsOnBatteryWARNING: The UPS has switched to battery backup power. TRAP-TYPE .1.3.6.1.4.1.1356.0.6 |
testStartedINFORMATION: A UPS test was started. TRAP-TYPE .1.3.6.1.4.1.1356.0.7 |
testCompletedINFORMATION: A UPS test is completed. Now a test result should be
available in upsTest.lastTestResult. TRAP-TYPE .1.3.6.1.4.1.1356.0.8 |
upsBatteryLowWARNING: Battery Low. TRAP-TYPE .1.3.6.1.4.1.1356.0.9 |
upsShutdownImminentINFORMATION: Server Shutdown imminent. TRAP-TYPE .1.3.6.1.4.1.1356.0.10 |
upsmanStartedINFORMATION: The UpsMan service has been started. TRAP-TYPE .1.3.6.1.4.1.1356.0.11 |
upsmanTrapInputBadAn abnormal condition of input UPS has been detected. TRAP-TYPE .1.3.6.1.4.1.1356.0.12 |
upsmanTrapOutputOverloadRemovedThe UPS has returned from an overload situation to normal operation. TRAP-TYPE .1.3.6.1.4.1.1356.0.13 |
upsmanTrapBatteryBadAn abnormal condition of the UPS batteries has been detected. TRAP-TYPE .1.3.6.1.4.1.1356.0.14 |
upsmanTrapTempBadAn abnormal UPS temperature has been detected. TRAP-TYPE .1.3.6.1.4.1.1356.0.15 |
upsmanTrapTempBadRemovedThe abnormal UPS temperature is back to normal level. TRAP-TYPE .1.3.6.1.4.1.1356.0.16 |
upsmanTrapFatalFaultA fatal fault in the UPS has been detected. The UPS can not backup, contact your UPS
service team. TRAP-TYPE .1.3.6.1.4.1.1356.0.17 |
ups OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1 |
upsIdent OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1.1 |
upsIdentModelNameThe UPS model name (e.g. 'O1000S').ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.1356.1.1.1 |
upsIdentUpsIDNameAn ID string identifying the UPS. This object
can be set by the administrator.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.1356.1.1.2 |
upsBattery OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1.2 |
upsBatteryStatusThe 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.ro Enumeration .1.3.6.1.4.1.1356.1.2.1 |
upsBatteryCapacityThe remaining battery capacity expressed in
percent of full capacity.ro INTEGER .1.3.6.1.4.1.1356.1.2.2 |
upsBatteryVoltageThe current battery voltage expressed in VDC.ro INTEGER .1.3.6.1.4.1.1356.1.2.3 |
upsBatteryTemperatureThe current internal UPS temperature expressed in
Celsius.ro INTEGER .1.3.6.1.4.1.1356.1.2.4 |
upsBatteryRunTimeRemainingThe UPS battery run time remaining before battery
exhaustion, in seconds.ro INTEGER .1.3.6.1.4.1.1356.1.2.5 |
upsBatteryLifeTimeRemainingForecast of the battery lifetime, replacement recommended in x month. Format: monthro INTEGER .1.3.6.1.4.1.1356.1.2.6 |
upsInput OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1.3 |
upsInputLineVoltageThe current utility line voltage in VAC.ro INTEGER .1.3.6.1.4.1.1356.1.3.1 |
upsInputLineFrequenceThe current utility line frequence in Hz.ro INTEGER .1.3.6.1.4.1.1356.1.3.2 |
upsOutput OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1.4 |
upsOutputStatusThe current state of the UPS. If the UPS is unable
to determine the state of the UPS this variable is set
to unknown(1).ro Enumeration .1.3.6.1.4.1.1356.1.4.1 |
upsOutputLoadThe current UPS load expressed in percent
of rated capacity.ro INTEGER .1.3.6.1.4.1.1356.1.4.2 |
upsOutputFrequencyThe present output frequency, format: 0.1 Hertz.ro INTEGER .1.3.6.1.4.1.1356.1.4.3 |
upsOutputVoltageThe present output voltage, format: RMS Volts.ro INTEGER .1.3.6.1.4.1.1356.1.4.4 |
upsTest OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1.5 |
upsRunTestSet this value to run a test. If this this variable is set
to NoTest(0) no test will be initiated.rw Enumeration .1.3.6.1.4.1.1356.1.5.1 |
upsLastTestPerformedThis value shows which last test was performed. If this value is
set to noTest(0) no test has been run since startup.ro Enumeration .1.3.6.1.4.1.1356.1.5.2 |
upsLastTestResultThe current UPS Test Result. If this value is undefined(0) no
test has been run since startup.ro Enumeration .1.3.6.1.4.1.1356.1.5.3 |
upsLastTestedBackupTimeThis value shows the last tested backup time in minutes.
To acquire a new value perform one of battery test's.ro INTEGER .1.3.6.1.4.1.1356.1.5.4 |
upsControl OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1.6 |
upsRunShutdownRestoreSet this value to run a shutdown procedure. If this this variable is set
to (0) nothing happens.rw Enumeration .1.3.6.1.4.1.1356.1.6.1 |
upsShutdownSecsThis value indicates the time in seconds after which a ups
shutdown will be performed. If this value is (0) shutdown
executes immediately.rw INTEGER .1.3.6.1.4.1.1356.1.6.2 |
upsRestoreSecsThis value indicates the time in seconds after which a ups
restore will be performed. If this value is (0) restore
executes immediately.rw INTEGER .1.3.6.1.4.1.1356.1.6.3 |
upsAlarms OBJECT IDENTIFIER .1.3.6.1.4.1.1356.1.7 |
upsAlarmFatalFaultStatusCRITICAL ALARM : A fatal fault in the UPS has been detected. Detailed information by referring to UpsAlarmFatalFaultDetail
Possible causes: Fatal Fault none (-1), Abnormal output (1), main circuit failure (2), fuse blown (3), fan fault (4), abnormal control (5),
abnormal battery (6), others (7).ro Enumeration .1.3.6.1.4.1.1356.1.7.1 |
upsAlarmWarningStatusWARNING : The UPS has detect a minor fault, warning level. Detailed information by referring to UpsAlarmWarningDetail.ro Enumeration .1.3.6.1.4.1.1356.1.7.2 |
upsAlarmInputBadStatusAn abnormal condition of the input in the UPS has been detected. Detailed information by referring to UpsAlarmInputBadDetail.ro Enumeration .1.3.6.1.4.1.1356.1.7.3 |
upsAlarmOutputOverloadStatusAn abnormal output overload in the UPS has been detected.ro Enumeration .1.3.6.1.4.1.1356.1.7.4 |
upsAlarmBatteryBadStatusAn abnormal condition of the battery in the UPS has been detected. Detailed information by referring to UpsAlarmBatteryBadDetail.ro Enumeration .1.3.6.1.4.1.1356.1.7.5 |
upsAlarmTempBadStatusAn abnormal condition of the temperature in the UPS has been detected. Detailed information by referring to UpsAlarmTempBadDetail.ro Enumeration .1.3.6.1.4.1.1356.1.7.6 |
mgmt OBJECT IDENTIFIER .1.3.6.1.4.1.1356.2 |
More MIBs from Upsman
Browse all UpsmanMIBs →OSPF-MIB
The OSPF-MIB module enables monitoring and management of OSPF Version 2 routing instances, providing access to critical metrics such as neighbor adjacency states, interface link costs, LSDB synchronization status, and SPF calculation statistics across Cisco, Juniper, and other vendor implementations.
160 objects→
SIP-MIB
The SIP-MIB module is intended for monitoring and managing Session Initiation Protocol (SIP) entities, specifically tracking call session states, registration status, and signaling traffic metrics. Although the provided description erroneously references SMDS interfaces, the standard SIP-MIB definition (RFC 3398) exclusively governs SIP-specific objects such as dialog counts, method invocations, and error counters for SIP proxies, user agents, and gateways.
71 objects→