Internet Draft UPS MIB August 1993 UPS Management Information Base August, 1993 Jeffrey D. Case, Ph.D. (Editor) The University of Tennessee Department of Computer Science case@CS.UTK.EDU 1. Abstract This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet Drafts as reference material or to cite them other than as a "work in progress". Expires 2/1/94 [Page 1] Internet Draft UPS MIB August 1993 2. Introduction This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing uninterruptable power supply (UPS) systems. Expires 2/1/94 [Page 2] Internet Draft UPS MIB August 1993 3. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework consists of four major components. They are: o RFC 1441 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. o RFC 1213 defines MIB-II, the core set of managed objects for the Internet suite of protocols. o RFC 1445 which defines the administrative and other architectural aspects of the framework. o RFC 1448 which defines the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 3.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. 3.2. Format of Definitions Section 5 contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SMI, as amended by the extensions specified in [7,8]. In addition, there are Conformance Groups and Compliance levels defined per RFC 1444 [9]. They are commented out in Expires 2/1/94 [Page 3] Internet Draft UPS MIB August 1993 section 5 so that the MIB may work with SNMP Version 1 MIB compilers. However, any claim of conformance to a published version of this document must include a statement indicating the conformance level. For example, "This product is fully compliant with the UPS MIB, upsTwoContactCompliance" or "This product is fully compliant with the UPS MIB, upsBasicCompliance." It is impossible to be in conformance with this specification if the claim of conformance fails to include this required statement. These statements of compliance take precendence over the status clauses found in the OBJECT-TYPE definitions which are included for compatibility with existing SNMP Version 1 MIB compilers. 4. Overview This document defines the managed objects for Uninterruptable Power Supplies which are to be manageable via the Simple Network Management Protocol (SNMP). Expires 2/1/94 [Page 4] Internet Draft UPS MIB August 1993 5. Definitions UPS-MIB DEFINITIONS ::= BEGIN IMPORTS experimental, Counter, TimeTicks, Gauge FROM RFC1155-SMI DisplayString FROM RFC1213-MIB InstancePointer, DateAndTime FROM SNMPv2-TC OBJECT-TYPE FROM RFC-1212 TRAP-TYPE FROM RFC-1215; univPowerSupply OBJECT IDENTIFIER ::= { experimental 39 } -- Note: this should be unintPowerSupply upsMibDraft2 OBJECT IDENTIFIER ::= { univPowerSupply 12 } -- Note: univPowerSupply 1-12 were used in earlier drafts. -- From now on, drafts will use version and subversion numbers -- under the experimental tree to prevent OID name-space collision -- when implementing different versions of experimental MIBS. upsMibE22 OBJECT IDENTIFIER ::= { upsMibDraft2 2 } -- Experimenal Version 2 minor version 2 (Exp v2.2) of UPS MIB. -- -- The Device Identification group. -- All objects in this group are set at device initialization -- and remain static. -- upsIdent OBJECT IDENTIFIER ::= { upsMibE22 1 } upsIdentManufacturer OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The UPS manufacturer." ::= { upsIdent 1 } upsIdentModel OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory Expires 2/1/94 [Page 5] Internet Draft UPS MIB August 1993 DESCRIPTION "The UPS Model designation." ::= { upsIdent 2 } upsIdentSoftwareVersion OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The UPS Firmware software version." ::= { upsIdent 3 } upsIdentName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) ACCESS read-write STATUS mandatory DESCRIPTION "An 8 octet ID string identifying the UPS. This object should be set by the administrator." ::= { upsIdent 4 } upsIdentSpecific OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "A reference to MIB definitions specific to the particular UPS being managed. This object may be used to locate an enterprise-specific MIB for this device. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value." ::= { upsIdent 5 } Expires 2/1/94 [Page 6] Internet Draft UPS MIB August 1993 -- -- Battery Group -- upsBattery OBJECT IDENTIFIER ::= { upsMibE22 2 } upsBatteryStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), batteryNormal(2), batteryLow(3) } ACCESS read-only STATUS mandatory DESCRIPTION "The indication of the capacity remaining in the UPS system's batteries. A batteryLow value indicates the UPS will be unable to sustain the current load, and its services will be lost if power is not restored." ::= { upsBattery 1 } upsBatteryTimeOnBattery OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "If the unit is on battery power, the elapsed time since the UPS has switched to battery power, or since the network management subsystem rebooted, whichever is less. Zero shall be returned if the unit is not on battery power. (Unit of measure: Seconds)" ::= { upsBattery 2 } upsBatTimeRemaining OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The estimated time to battery charge depletion. (Unit of measure: Seconds)" ::= { upsBattery 3 } upsBatteryVoltage OBJECT-TYPE Expires 2/1/94 [Page 7] Internet Draft UPS MIB August 1993 SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The current battery voltage expressed in 1/10 of one VDC." ::= { upsBattery 4 } upsBatTemperature OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The temperature of the UPS Battery casing (Unit of measure: degrees Centigrade)" ::= { upsBattery 5 } Expires 2/1/94 [Page 8] Internet Draft UPS MIB August 1993 -- -- Input Group -- upsInput OBJECT IDENTIFIER ::= { upsMibE22 3 } upsInputFrequency OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The current input frequency. (Unit of measure: 1/10 Hertz)" ::= { upsInput 1 } upsInputLineBads OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of input out of tolerance conditions since the agent started." ::= { upsInput 2 } upsInputNumLines OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of input lines utilized in this device. This entry indicates the number of rows in the input table." ::= { upsInput 3 } upsInputTable OBJECT-TYPE SYNTAX SEQUENCE OF UpsInputEntry ACCESS not-accessible STATUS mandatory ::= { upsInput 4 } upsInputEntry OBJECT-TYPE SYNTAX UpsInputEntry ACCESS not-accessible STATUS mandatory Expires 2/1/94 [Page 9] Internet Draft UPS MIB August 1993 INDEX { upsInputLineIndex } ::= { upsInputTable 1 } UpsInputEntry ::= SEQUENCE { upsInputLineIndex INTEGER, upsInputVoltage INTEGER } upsInputLineIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The input line." ::= { upsInputEntry 1 } upsInputVoltage OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The input voltage. (Unit of measure: RMS Volt)" ::= { upsInputEntry 2 } Expires 2/1/94 [Page 10] Internet Draft UPS MIB August 1993 -- -- The Output group. -- upsOutput OBJECT IDENTIFIER ::= { upsMibE22 4 } upsOutputFrequency OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The current output frequency. (Unit of measure: 1/10 Hertz)" ::= { upsOutput 1 } upsOutputNumLines OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of output lines utilized in this device. This entry indicates the number of rows in the output table." ::= { upsOutput 3 } upsOutputTable OBJECT-TYPE SYNTAX SEQUENCE OF UpsOutputEntry ACCESS not-accessible STATUS mandatory ::= { upsOutput 4 } upsOutputEntry OBJECT-TYPE SYNTAX UpsOutputEntry ACCESS not-accessible STATUS mandatory INDEX { upsOutputLineIndex } ::= { upsOutputTable 1 } UpsOutputEntry ::= SEQUENCE { upsOutputLineIndex INTEGER, upsOutputVoltage INTEGER, upsOutputCurrent INTEGER, upsOutputWatts INTEGER } Expires 2/1/94 [Page 11] Internet Draft UPS MIB August 1993 upsOutputLineIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The output line index." ::= { upsOutputEntry 1 } upsOutputVoltage OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The output voltage. (Unit of measure: RMS Volts)" ::= { upsOutputEntry 2 } upsOutputCurrent OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The output current. (Unit of measure: 1/10 Amp)" ::= { upsOutputEntry 3 } upsOutputWatts OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The output power. (Unit of measure: Watt)" ::= { upsOutputEntry 5 } Expires 2/1/94 [Page 12] Internet Draft UPS MIB August 1993 -- -- The Bypass group. -- upsBypass OBJECT IDENTIFIER ::= { upsMibE22 5 } upsBypassFrequency OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The current bypass frequency. (Unit of measure: 1/10 Hertz)" ::= { upsBypass 1 } upsBypassNumLines OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of bypass lines utilized in this device. This entry indicates the number of rows in the bypass table." ::= { upsBypass 2 } upsBypassTable OBJECT-TYPE SYNTAX SEQUENCE OF UpsBypassEntry ACCESS not-accessible STATUS mandatory ::= { upsBypass 3 } upsBypassEntry OBJECT-TYPE SYNTAX UpsBypassEntry ACCESS not-accessible STATUS mandatory INDEX { upsBypassLineIndex } ::= { upsBypassTable 1 } UpsBypassEntry ::= SEQUENCE { upsBypassLineIndex INTEGER, upsBypassVoltage INTEGER, upsBypassCurrent INTEGER } upsBypassLineIndex OBJECT-TYPE Expires 2/1/94 [Page 13] Internet Draft UPS MIB August 1993 SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The bypass line index." ::= { upsBypassEntry 1 } upsBypassVoltage OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The bypass voltage. (Unit of measure: RMS Volt)" ::= { upsBypassEntry 2 } upsBypassCurrent OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The bypass current. (Unit of measure: 1/10 Amp)" ::= { upsBypassEntry 3 } Expires 2/1/94 [Page 14] Internet Draft UPS MIB August 1993 -- -- The Alarm group. -- This section needs more attention before we can be done upsAlarm OBJECT IDENTIFIER ::= { upsMibE22 6 } upsAlarms OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "The current number of active alarm conditions." ::= { upsAlarm 1 } upsAlarmTable OBJECT-TYPE SYNTAX SEQUENCE OF UpsAlarmEntry ACCESS not-accessible STATUS mandatory ::= { upsAlarm 2 } upsAlarmEntry OBJECT-TYPE SYNTAX UpsAlarmEntry ACCESS not-accessible STATUS mandatory INDEX { upsAlarmId } ::= { upsAlarmTable 1 } UpsAlarmEntry ::= SEQUENCE { upsAlarmId INTEGER, upsAlarmDescr OBJECT IDENTIFIER, upsAlarmTime TimeTicks } upsAlarmId OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION "A unique identifier for an alarm condition. This value must remain constant." ::= { upsAlarmEntry 1 } upsAlarmDescr OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only Expires 2/1/94 [Page 15] Internet Draft UPS MIB August 1993 STATUS mandatory DESCRIPTION "A reference to an alarm description object. The object referenced should not be accessible, but rather be used to provide a unique description of the alarm condition." ::= { upsAlarmEntry 2 } upsAlarmTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The value of sysUpTime when the alarm condition occurred." ::= { upsAlarmEntry 3 } -- -- Well Known alarm conditions. -- upsWellKnownAlarms OBJECT IDENTIFIER ::= { upsAlarm 3 } upsAlarmBatteryBad OBJECT IDENTIFIER ::= { upsWellKnownAlarms 1 } -- Battery needs replacing. upsAlarmOnBattery OBJECT IDENTIFIER ::= { upsWellKnownAlarms 2 } -- The UPS is drawing power from the battery. upsAlarmLowBattery OBJECT IDENTIFIER ::= { upsWellKnownAlarms 3 } -- The battery capacity is at a value considered low by -- the UPS manufacturer upsAlarmTempBad OBJECT IDENTIFIER ::= { upsWellKnownAlarms 4 } -- A temperature is out of tolerance. upsAlarmInputBad OBJECT IDENTIFIER ::= { upsWellKnownAlarms 5 } -- An input condition is out of tolerance. upsAlarmInputFreqError OBJECT IDENTIFIER ::= { upsWellKnownAlarms 6 } -- The input frequency is out of tolerance. upsAlarmOutputBad OBJECT IDENTIFIER ::= { upsWellKnownAlarms 7 } -- An output condition is out of tolerance. upsAlarmOutputOverload OBJECT IDENTIFIER ::= { upsWellKnownAlarms 8 } Expires 2/1/94 [Page 16] Internet Draft UPS MIB August 1993 -- The output is loaded over the UPSs capacity. upsAlarmOnBypass OBJECT IDENTIFIER ::= { upsWellKnownAlarms 9 } -- The Bypass is currently engaged on the UPS. upsAlarmBypassBad OBJECT IDENTIFIER ::= { upsWellKnownAlarms 10 } -- The Bypass is out of tolerance. upsAlarmStopNoticeIssued OBJECT IDENTIFIER ::= { upsWellKnownAlarms 11 } -- The UPS had been instructed to shutdown and has -- performed this shutdown. upsAlarmChargerFailed OBJECT IDENTIFIER ::= { upsWellKnownAlarms 12 } -- The UPS charger has failed. upsAlarmUpsOff OBJECT IDENTIFIER ::= { upsWellKnownAlarms 13 } -- The UPS is currently in an off state. upsAlarmInputBrkrOpen OBJECT IDENTIFIER ::= { upsWellKnownAlarms 14 } -- The input breaker is in an open state. upsAlarmBypassBrkrOpen OBJECT IDENTIFIER ::= { upsWellKnownAlarms 15 } -- The bypass breaker is in an open state. upsAlarmOutputBrkrOpen OBJECT IDENTIFIER ::= { upsWellKnownAlarms 16 } -- The output breaker is in an open state. upsAlarmBatteryBrkrOpen OBJECT IDENTIFIER ::= { upsWellKnownAlarms 17 } -- The battery breaker is in an open state. upsAlarmSysBypassBrkrOpen OBJECT IDENTIFIER ::= { upsWellKnownAlarms 18 } -- The system bypass breaker is in an open state. upsAlarmMaintenanceBypassBreakerClosed OBJECT IDENTIFIER ::= { upsWellKnownAlarms 19 } -- The maintenance bypass breaker is in a closed state. upsAlarmFanFailure OBJECT IDENTIFIER ::= { upsWellKnownAlarms 20 } -- A fan has failed in the UPS. upsAlarmOnGenerator OBJECT IDENTIFIER ::= { upsWellKnownAlarms 21 } -- The UPS is drawing power from an auxiliary generator. Expires 2/1/94 [Page 17] Internet Draft UPS MIB August 1993 -- -- The Test Group -- upsTest OBJECT IDENTIFIER ::= { upsMibE22 7 } upsTestDiagnosticSchedule OBJECT-TYPE SYNTAX INTEGER { unknown(1), biweekly(2), weekly(3), atTurnOn(4), never(5) } ACCESS read-write STATUS mandatory DESCRIPTION "The UPS system's automatic battery test schedule." ::= { upsTest 1 } upsTestDiagnostics OBJECT-TYPE SYNTAX INTEGER { noTest(1), test(2), abort(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Setting this variable to test(2) causes the UPS to perform a diagnostic self test. Setting this value to noTest(1) has no effect. The value noTest(1) will always be returned when the variable is read. Setting this variable to abort(3) will end a test in progress." ::= { upsTest 2 } upsTestDiagnosticsResults OBJECT-TYPE -- Editor's note: we need to state under what conditions each -- value is returned. SYNTAX INTEGER { passed(1), Expires 2/1/94 [Page 18] Internet Draft UPS MIB August 1993 failed(2), invalidTest(3), inProgress(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The results of the last UPS diagnostics test performed." ::= { upsTest 3 } upsTestLastDiagnosticsDate OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The date the last UPS diagnostics test was performed." ::= { upsTest 4 } upsTestIndicators OBJECT-TYPE SYNTAX INTEGER { noTest(1), test(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Setting this variable to test(2) causes the UPS to perform a front panel indicators (lights) test. Setting this value to noTest(1) has no effect. The value noTest(1) will always be returned when the variable is read." ::= { upsTest 5} Expires 2/1/94 [Page 19] Internet Draft UPS MIB August 1993 -- -- The Control group. -- upsControl OBJECT IDENTIFIER ::= { upsMibE22 8 } -- Editor's note: the interaction between upsControlOutputOffDelay and -- upsControlOutputOnDelay is ambiguous and needs to be fixed / clarified. -- What happens if upsControlOutputOnDelay is less than -- upsControlOutputOffDelay? upsControlOutputOffDelay OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-write STATUS mandatory DESCRIPTION "Setting this object will stop the output after the indicated number of seconds. Setting this object to 0 will cause the UPS to stop the output immediately. If the output is already off at the time the delay has counted down, nothing will happen. Output will remain off until either external controls or the execution of a upsControlOutputOnDelay or upsControlRebootUpsDelay that has run through its delay turns the power back on." ::= { upsControl 1 } upsControlOutputOnDelay OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-write STATUS mandatory DESCRIPTION "Setting this object will start the output after the indicated number of seconds. Setting this object to 0 will cause the UPS to start the output immediately. If the output is already on at the time the delay has counted down, nothing will happen." ::= { upsControl 2 } upsControlRebootUpsDelay OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-write STATUS mandatory Expires 2/1/94 [Page 20] Internet Draft UPS MIB August 1993 DESCRIPTION "Setting this object will cause the UPS to stop the output for the indicated after the indicated number of seconds. The UPS output will remain stopped for a brief period set by the UPS manufacturer, after which power will be restored." ::= { upsControl 3 } Expires 2/1/94 [Page 21] Internet Draft UPS MIB August 1993 -- -- The Configuration group. -- upsConfig OBJECT IDENTIFIER ::= { upsMibE22 9 } upsConfigOutputVoltage OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The nominal output voltage. (Unit of measure: RMS volt)" ::= { upsConfig 1 } upsConfigInputVoltage OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The nominal input voltage. (Unit of measure: RMS volt)" ::= { upsConfig 2 } upsConfigOutputVA OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The nominal Volt-Amp rating." ::= { upsConfig 3 } upsConfigOutputWatts OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The nominal power rating. (Unit of measure: watt)" ::= { upsConfig 4 } upsConfigOutputFreq OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory Expires 2/1/94 [Page 22] Internet Draft UPS MIB August 1993 DESCRIPTION "The nominal output frequency. (Unit of measure: 1/10 Hertz)" ::= { upsConfig 5 } upsConfigNominalBatTime OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The nominal battery time. (Unit of measure: seconds)" ::= { upsConfig 6 } upsConfigLowBatTime OBJECT-TYPE SYNTAX INTEGER (0..2147483648) ACCESS read-only STATUS mandatory DESCRIPTION "The available run time once the low battery condition is reached. (Unit of measure: seconds)" ::= { upsConfig 7 } upsConfigAutoRestart OBJECT-TYPE SYNTAX INTEGER { on(1), off(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Setting this object to 'on' will cause the device to restart after a shutdown if/when utility power is present" ::= { upsConfig 8 } Expires 2/1/94 [Page 23] Internet Draft UPS MIB August 1993 -- -- The Conformance Groups -- upsGroups OBJECT IDENTIFIER ::= { upsMibE22 10 } -- upsCommonGroup OBJECT-GROUP -- OBJECTS { upsIdentManufacturer, upsIdentModel, -- upsIdentSoftwareVersion, upsIdentName, -- upsIdentSpecific } -- STATUS current -- DESCRIPTION -- "The upsCommonGroup define the objects which are common -- across all managed UPSs." -- ::= { upsGroups 1 } -- upsTwoContactGroup OBJECT-GROUP -- OBJECTS { upsControlOutputOffDelay, upsTestDiagnostics, -- upsTestDiagnosticsResults } -- STATUS current -- DESCRIPTION -- "The upsTwoContactGroup defines the objects that are -- common to UPSs that only support the two-contact -- form of communication." -- ::= { upsGroups 2 } upsBasicGroups OBJECT IDENTIFIER ::= { upsGroups 3 } -- upsBasicBatteryGroup OBJECT-GROUP -- OBJECTS { upsBatteryStatus, upsBatteryTimeOnBattery, -- upsBatTimeRemaining, upsBatteryVoltage, upsBatTemperature } -- STATUS current -- DESCRIPTION -- "The upsBasicBatteryGroup defines the objects that are -- common to the battery groups of basic UPSs." -- ::= { upsBasicGroups 1 } -- upsBasicInputGroup OBJECT-GROUP -- OBJECTS { upsInputFrequency, upsInputLineBads, -- upsInputNumLines, upsInputLineIndex, -- upsInputVoltage } -- STATUS current -- DESCRIPTION -- "The upsBasicInputGroup defines the objects that are -- common to the Input groups of basic UPSs." Expires 2/1/94 [Page 24] Internet Draft UPS MIB August 1993 -- ::= { upsBasicGroups 2 } -- upsBasicOutputGroup OBJECT-GROUP -- OBJECTS { upsOutputFrequency, upsOutputNumLines, -- upsOutputLineIndex, upsOutputVoltage, -- upsOutputCurrent, upsOutputWatts } -- STATUS current -- DESCRIPTION -- "The upsBasicOutputGroup defines the objects that are -- common to the Output groups of basic UPSs." -- ::= { upsBasicGroups 3 } -- upsBasicBypassGroup OBJECT-GROUP -- OBJECTS { upsBypassFrequency, upsBypassNumLines, -- upsBypassLineIndex, upsBypassVoltage, -- upsBypassCurrent } -- STATUS current -- DESCRIPTION -- "The upsBasicBypassGroup defines the objects that are -- common to the Bypass groups of basic UPSs." -- ::= { upsBasicGroups 4 } -- upsBasicAlarmGroup OBJECT-GROUP -- OBJECTS { upsAlarms, upsAlarmId, upsAlarmDescr, -- upsAlarmTime } -- STATUS current -- DESCRIPTION -- "The upsBasicAlarmGroup defines the objects that are -- common to the Alarm groups of basic UPSs." -- ::= { upsBasicGroups 5 } -- upsBasicTestGroup OBJECT-GROUP -- OBJECTS { upsTestDiagnosticSchedule, upsTestDiagnostics, -- upsTestDiagnosticsResults, -- upsTestLastDiagnosticsDate, upsTestIndicators } -- STATUS current -- DESCRIPTION -- "The upsBasicTestGroup defines the objects that are -- common to the Test groups of basic UPSs." -- ::= { upsBasicGroups 6 } -- upsBasicControlGroup OBJECT-GROUP -- OBJECTS { upsControlOutputOffDelay, upsControlOutputOnDelay, -- upsControlRebootUpsDelay } -- STATUS current Expires 2/1/94 [Page 25] Internet Draft UPS MIB August 1993 -- DESCRIPTION -- "The upsBasicControlGroup defines the objects that are -- common to the Control groups of basic UPSs." -- ::= { upsBasicGroups 7 } -- upsBasicConfigGroup OBJECT-GROUP -- OBJECTS { upsConfigOutputVoltage, upsConfigInputVoltage, -- upsConfigOutputVA, upsConfigOutputWatts, -- upsConfigOutputFreq, upsConfigNominalBatTime, -- upsConfigLowBatTime, upsConfigAutoRestart } -- STATUS current -- DESCRIPTION -- "The upsBasicConfigGroup defines the objects that are -- common to the Config groups of basic UPSs." -- ::= { upsBasicGroups 8 } Expires 2/1/94 [Page 26] Internet Draft UPS MIB August 1993 -- -- Compliance Statements -- upsCompliances OBJECT IDENTIFIER ::= { upsMibE22 11 } -- upsTwoContactCompliance MODULE-COMPLIANCE -- STATUS current -- DESCRIPTION -- "The compliance statement for UPSs that only support -- the old two-contact communication protocol." -- MODULE -- MANDATORY-GROUPS { upsCommonGroup, upsTwoContactGroup } -- ::= { upsCompliances 1 } -- upsBasicComplaince MODULE-COMPLIANCE -- STATUS current -- DESCRIPTION -- "The compliance statement for UPSs that support -- basic functions." -- MODULE -- MANDATORY-GROUPS { upsCommonGroup, upsBasicBatteryGroup, -- upsBasicInputGroup, upsBasicOutputGroup, -- upsBasicAlarmGroup, upsBasicTestGroup, -- upsBasicControlGroup, upsBasicConfigGroup } -- GROUP {upsBasicBypassGroup } -- DESCRIPTION -- "The upsBasicBypassGroup is only required for -- UPSs that have a Bypass present." -- ::= { upsCompliances 2 } END Expires 2/1/94 [Page 27] Internet Draft UPS MIB August 1993 6. Acknowledgements The UPS MIB represents the combined work of the IETF UPS MIB Working Group, with particular, substantial authorship contributions from: Mike Davison Fibercom, Inc. Ray Wasson Consultant Roger Draper Liebert Corporation Jeff Case University of Tennessee Pete Yoest American Power Conversion Doug Rademacher American Power Conversion Ron Pitt Network Security Systems, Inc Terry Zumwalt International Power Machines Expires 2/1/94 [Page 28] Internet Draft UPS MIB August 1993 7. References [1] M.T. Rose and K. McCloghrie, Structure and Identification of Management Information for TCP/IP-based internets, Internet Working Group Request for Comments 1155. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [2] K. McCloghrie and M.T. Rose, Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1156. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [3] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, Simple Network Management Protocol, Internet Working Group Request for Comments 1157. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [4] K. McCloghrie and M.T. Rose (editors), Management Information Base for Network Management of TCP/IP-based internets: MIB-II, Internet Working Group Request for Comments 1213. Network Information Center, SRI International, Menlo Park, California, (March, 1991). [5] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December, 1987). [6] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization. International Standard 8825, (December, 1987). [7] M.T. Rose, K. McCloghrie (editors), Concise MIB Definitions, Internet Working Group Request for Comments 1212. Network Information Center, SRI International, Menlo Park, California, (March, 1991). [8] M.T. Rose (editor), A Convention for Defining Traps for use with the SNMP, Internet Working Group Request for Expires 2/1/94 [Page 29] Internet Draft UPS MIB August 1993 Comments 1215. Network Information Center, SRI International, Menlo Park, California, (March, 1991). [9] J.D. Case, K. McCloghrie, M.T. Rose, and S. Waldbusser, Conformance Statements for version 2 of the the Simple Network Management Protocol (SNMPv2), Request for Comments 1444, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, (April 1993). Expires 2/1/94 [Page 30] Internet Draft UPS MIB August 1993 8. Security Considerations Security issues are not discussed in this memo. 9. Author's Address Jeffrey D. Case, Ph.D. The University of Tennessee Department of Computer Science 107 Ayres Hall Knoxville, Tennessee 37996 Phone: (615) 573-1434 Email: case@CS.UTK.EDU Expires 2/1/94 [Page 31] Internet Draft UPS MIB August 1993 Table of Contents 1 Abstract .............................................. 1 2 Introduction .......................................... 2 3 The SNMPv2 Network Management Framework ............... 3 3.1 Object Definitions .................................. 3 3.2 Format of Definitions ............................... 3 4 Overview .............................................. 4 5 Definitions ........................................... 5 5.1 The Device Identification Group. ................... 5 5.2 The Battery Group ................................... 7 5.3 The Input Group ..................................... 9 5.4 The Output Group .................................... 11 5.5 The Bypass Group .................................... 13 5.6 The Alarm Group ..................................... 15 5.7 The Test Group ...................................... 18 5.8 The Control Group ................................... 20 5.9 The Configuration Group ............................. 22 5.10 The Conformance Groups ............................. 24 5.11 The Compliance Statements .......................... 27 6 Acknowledgements ...................................... 28 7 References ............................................ 29 8 Security Considerations ............................... 31 9 Author's Address ...................................... 31 Expires 2/1/94 [Page 32]