Internet Draft UPS MIB July 1992 Expires 1/1/93 UPS Management Information Base July 2, 1992 Michael R. Davison SNMP Research, Incorporated 3001 Kimberlin Heights Road Knoxville, Tennessee 37920 (615) 573-1434 davison@CS.UTK.EDU Ray Wasson Emerson Computer Power Division, Liebert Corporation 9650 Jeronimo Road Irvine, California 92718 (714) 457-3600 Roger Draper Emerson Computer Power Division, Liebert Corporation 9650 Jeronimo Road Irvine, California 92718 (714) 457-3600 Jeffrey D. Case, Ph.D. The University of Tennessee Department of Computer Science 107 Ayres Hall Knoxville, Tennessee 37996 (615) 974-5067 case@CS.UTK.EDU Davison, Wasson, Draper, and Case [Page 1] Internet Draft UPS MIB July 1992 Expires 1/1/93 1. Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing uninterruptable power supply (UPS) systems. 2. Status of this Memo 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 draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. This document, when finalized, will be submitted to the RFC editor as an extension to the SNMP MIB. Distribution of this memo is unlimited. Please send comments to the authors. 3. Management Framework The Internet-standard Network Management Framework consists of three components. They are: RFC 1155 [1] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. RFC 1212 [7] defines a more concise description mechanism, which is wholly consistent with the SMI. RFC 1156 [2] which defines MIB-I, the core set of managed objects for the Internet suite of protocols. RFC 1213 Davison, Wasson, Draper, and Case [Page 2] Internet Draft UPS MIB July 1992 Expires 1/1/93 [4] defines MIB-II, an evolution of MIB-I based on implementation experience and new operational requirements. RFC 1157 [3] which defines the SNMP, the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Davison, Wasson, Draper, and Case [Page 3] Internet Draft UPS MIB July 1992 Expires 1/1/93 4. Objects 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) [5] defined in the SMI. In particular, each object has a name, a syntax, and an encoding. The name is an object identifier, an administratively assigned name, which specifies an object type. 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 OBJECT DESCRIPTOR, to also refer to the object type. The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 language is used for this purpose. However, the SMI [1] purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. The encoding of an object type is simply how that object type is represented using the object type's syntax. Implicitly tied to the notion of an object type's syntax and encoding is how the object type is represented when being transmitted on the network. The SMI specifies the use of the basic encoding rules of ASN.1 [6], subject to the additional requirements imposed by the SNMP. 4.1. Format of Definitions Section 6 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]. Davison, Wasson, Draper, and Case [Page 4] Internet Draft UPS MIB July 1992 Expires 1/1/93 5. Overview This document defines the managed objects for Uninterruptable Power Supplies which are to be manageable via the Simple Network Management Protocol (SNMP). Davison, Wasson, Draper, and Case [Page 5] Internet Draft UPS MIB July 1992 Expires 1/1/93 6. Definitions SNMP-UPS-MIB DEFINITIONS ::= BEGIN IMPORTS experimental, Counter, TimeTicks, Gauge FROM RFC1155-SMI OBJECT-TYPE FROM RFC-1212; univPowerSupply OBJECT IDENTIFIER ::= { experimental ??? } -- TBD -- groups in the UPS MIB module upsIdent OBJECT IDENTIFIER ::= { univPowerSupply 1 } upsBattery OBJECT IDENTIFIER ::= { univPowerSupply 2 } upsInput OBJECT IDENTIFIER ::= { univPowerSupply 3 } upsOutput OBJECT IDENTIFIER ::= { univPowerSupply 4 } upsBypass OBJECT IDENTIFIER ::= { univPowerSupply 5 } upsEnvironment OBJECT IDENTIFIER ::= { univPowerSupply 6 } upsAlarm OBJECT IDENTIFIER ::= { univPowerSupply 7 } upsTest OBJECT IDENTIFIER ::= { univPowerSupply 8 } upsControl OBJECT IDENTIFIER ::= { univPowerSupply 9 } upsConfig OBJECT IDENTIFIER ::= { univPowerSupply 10 } upsTruck OBJECT IDENTIFIER ::= { univPowerSupply 11 } Davison, Wasson, Draper, and Case [Page 6] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Device Identification group. -- All objects in this group are set at device initialization -- and remain static. Implementation of this group is mandatory -- for all systems. -- upsIdent OBJECT IDENTIFIER ::= { univPowerSupply 1 } upsIdentManufacturer OBJECT-TYPE SYNTAX OCTET STRING (SIZE (255)) ACCESS read-only STATUS mandatory DESCRIPTION "The UPS manufacturer." ::= { upsIdent 1 } upsIdentModel OBJECT-TYPE SYNTAX OCTET STRING (SIZE (255)) ACCESS read-only STATUS mandatory DESCRIPTION "The UPS Model designation." ::= { upsIdent 2 } upsIdentSoftwareVersion OBJECT-TYPE SYNTAX OCTET STRING (SIZE (255)) ACCESS read-only STATUS mandatory DESCRIPTION "The UPS software version." ::= { upsIdent 3 } 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 Davison, Wasson, Draper, and Case [Page 7] Internet Draft UPS MIB July 1992 Expires 1/1/93 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 4 } Davison, Wasson, Draper, and Case [Page 8] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Battery group. -- Implementation of this group is mandatory for all systems. -- upsBattery OBJECT IDENTIFIER ::= { univPowerSupply 2 } upsBatTimeRemaining OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The estimated time to battery charge depletion. (Unit of measure: Minute)" ::= { upsBattery 1 } upsBatTemperature OBJECT-TYPE SYNTAX INTEGER (-32768..32767) ACCESS read-only STATUS mandatory DESCRIPTION "The battery temperature. (Unit of measure: Degree, Centigrade)" ::= { upsBattery 2 } upsBatVoltage OBJECT-TYPE SYNTAX INTEGER (-32768..32767) ACCESS read-only STATUS mandatory DESCRIPTION "The current battery voltage. (Unit of measure: volt)" ::= { upsBattery 3 } upsBatCurrent OBJECT-TYPE SYNTAX INTEGER (-32768..32767) ACCESS read-only STATUS mandatory DESCRIPTION "The current battery charging/discharging current. (Unit of measure: Amp)" ::= { upsBattery 4 } upsBatCapacity OBJECT-TYPE Davison, Wasson, Draper, and Case [Page 9] Internet Draft UPS MIB July 1992 Expires 1/1/93 SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "The current battery capacity in percentage of total available." ::= { upsBattery 6 } Davison, Wasson, Draper, and Case [Page 10] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Input group. -- Implementation of this group is mandatory for all systems. -- upsInput OBJECT IDENTIFIER ::= { univPowerSupply 3 } upsInputFrequency OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The current input frequency. (Unit of measure: Hertz)" ::= { upsInput 1 } upsInputBrownOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of brown-out conditions since the agent started." ::= { upsInput 2 } upsInputBlackOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of black-out conditions since the agent started." ::= { upsInput 3 } upsInputTransients OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of transient (surge and spike) conditions since the agent started." ::= { upsInput 4 } upsInputNumPhases OBJECT-TYPE SYNTAX INTEGER (1..3) Davison, Wasson, Draper, and Case [Page 11] Internet Draft UPS MIB July 1992 Expires 1/1/93 ACCESS read-only STATUS mandatory DESCRIPTION "The number of input phases utilized in this device. This entry indicates the number of rows in the input table." ::= { upsInput 5 } upsInputTable OBJECT-TYPE SYNTAX SEQUENCE OF UpsInputEntry ACCESS not-accessible STATUS mandatory ::= { upsInput 6 } upsInputEntry OBJECT-TYPE SYNTAX UpsInputEntry ACCESS not-accessible STATUS mandatory INDEX { upsInputPhase } ::= { upsInputTable 1 } UpsInputEntry ::= SEQUENCE { upsInputPhase INTEGER, upsInputVoltage INTEGER, upsInputCurrent INTEGER, upsInputVA INTEGER, upsInputWatts INTEGER } upsInputPhase OBJECT-TYPE SYNTAX INTEGER (1..3) ACCESS read-only STATUS mandatory DESCRIPTION "The input phase." ::= { upsInputEntry 1 } upsInputVoltage OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The input voltage. (Unit of measure: Volt)" ::= { upsInputEntry 2 } Davison, Wasson, Draper, and Case [Page 12] Internet Draft UPS MIB July 1992 Expires 1/1/93 upsInputCurrent OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The input current. (Unit of measure: Amp/10)" ::= { upsInputEntry 3 } upsInputVA OBJECT-TYPE SYNTAX INTEGER (0..4294967296) ACCESS read-only STATUS mandatory DESCRIPTION "The input volt-amps." ::= { upsInputEntry 4 } upsInputWatts OBJECT-TYPE SYNTAX INTEGER (0..4294967296) ACCESS read-only STATUS mandatory DESCRIPTION "The input power. (Unit of measure: Watt)" ::= { upsInputEntry 5 } Davison, Wasson, Draper, and Case [Page 13] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Output group. -- Implementation of this group is mandatory for all systems. -- upsOutput OBJECT IDENTIFIER ::= { univPowerSupply 4 } upsOutputFrequency OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The current output frequency. (Unit of measure: Hertz)" ::= { upsOutput 1 } upsOutputLoad OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "The current output load percentage." ::= { upsOutput 2 } upsOutputNumPhases OBJECT-TYPE SYNTAX INTEGER (1..3) ACCESS read-only STATUS mandatory DESCRIPTION "The number of output phases 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 { outputPhase } Davison, Wasson, Draper, and Case [Page 14] Internet Draft UPS MIB July 1992 Expires 1/1/93 ::= { upsOutputTable 1 } UpsOutputEntry ::= SEQUENCE { upsOutputPhase INTEGER, upsOutputVoltage INTEGER, upsOutputCurrent INTEGER, upsOutputVA INTEGER, upsOutputWatts INTEGER } upsOutputPhase OBJECT-TYPE SYNTAX INTEGER (1..3) ACCESS read-only STATUS mandatory DESCRIPTION "The output phase." ::= { upsOutputEntry 1 } upsOutputVoltage OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The output voltage. (Unit of measure: Volt)" ::= { upsOutputEntry 2 } upsOutputCurrent OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The output current. (Unit of measure: Amp)" ::= { upsOutputEntry 3 } upsOutputVA OBJECT-TYPE SYNTAX INTEGER (0..4294967296) ACCESS read-only STATUS mandatory DESCRIPTION "The output volt-amps." ::= { upsOutputEntry 4 } upsOutputWatts OBJECT-TYPE SYNTAX INTEGER (0..4294967296) ACCESS read-only Davison, Wasson, Draper, and Case [Page 15] Internet Draft UPS MIB July 1992 Expires 1/1/93 STATUS mandatory DESCRIPTION "The output power. (Unit of measure: Watt)" ::= { upsOutputEntry 5 } Davison, Wasson, Draper, and Case [Page 16] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Bypass group. -- Implementation of this group is mandatory for all systems. -- upsBypass OBJECT IDENTIFIER ::= { univPowerSupply 5 } upsBypassFrequency OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The current bypass frequency. (Unit of measure: Hertz)" ::= { upsBypass 1 } upsBypassNumPhases OBJECT-TYPE SYNTAX INTEGER (1..3) ACCESS read-only STATUS mandatory DESCRIPTION "The number of bypass phases 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 { upsBypassPhase } ::= { upsBypassTable 1 } UpsBypassEntry ::= SEQUENCE { upsBypassPhase INTEGER, upsBypassVoltage INTEGER, upsBypassCurrent INTEGER } Davison, Wasson, Draper, and Case [Page 17] Internet Draft UPS MIB July 1992 Expires 1/1/93 upsBypassPhase OBJECT-TYPE SYNTAX INTEGER (1..3) ACCESS read-only STATUS mandatory DESCRIPTION "The bypass phase." ::= { upsBypassEntry 1 } upsBypassVoltage OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The bypass voltage. (Unit of measure: Volt)" ::= { upsBypassEntry 2 } upsBypassCurrent OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-only STATUS mandatory DESCRIPTION "The bypass current. (Unit of measure: Amp)" ::= { upsBypassEntry 3 } Davison, Wasson, Draper, and Case [Page 18] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Environment group. -- Implementation of this group is mandatory for all systems. -- upsEnvironment OBJECT IDENTIFIER ::= { univPowerSupply 6 } upsEnvControllerTemp OBJECT-TYPE SYNTAX INTEGER (-32768..32767) ACCESS read-only STATUS mandatory DESCRIPTION "The temperature of the controller. (Unit of measure: degree, Centigrade)" ::= { upsEnvironment 1 } upsEnvAmbientTemp OBJECT-TYPE SYNTAX INTEGER (-32768..32767) ACCESS read-only STATUS mandatory DESCRIPTION "The ambient temperature of the UPS. (Unit of measure: degree, Centigrade)" ::= { upsEnvironment 2 } Davison, Wasson, Draper, and Case [Page 19] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Alarm group. -- Implementation of this group is mandatory for all systems. -- upsAlarm OBJECT IDENTIFIER ::= { univPowerSupply 7 } upsAlarms OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "The current number of 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..4294967296) 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 Davison, Wasson, Draper, and Case [Page 20] Internet Draft UPS MIB July 1992 Expires 1/1/93 ACCESS read-only 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 occured." ::= { upsAlarmEntry 3 } -- -- Well known alarm condtions. -- upsAlarmBatteryBad OBJECT IDENTIFIER ::= { upsAlarm 3 } upsAlarmOnBattery OBJECT IDENTIFIER ::= { upsAlarm 4 } upsAlarmLowBattery OBJECT IDENTIFIER ::= { upsAlarm 5 } upsAlarmBatteryTempBad OBJECT IDENTIFIER ::= { upsAlarm 6 } upsAlarmInputBad OBJECT IDENTIFIER ::= { upsAlarm 7 } upsAlarmInputFreqError OBJECT IDENTIFIER ::= { upsAlarm 8 } upsAlarmOutputBad OBJECT IDENTIFIER ::= { upsAlarm 9 } upsAlarmOutputOverload OBJECT IDENTIFIER ::= { upsAlarm 10 } upsAlarmOnBypass OBJECT IDENTIFIER ::= { upsAlarm 11 } upsAlarmBypassBad OBJECT IDENTIFIER ::= { upsAlarm 12 } upsAlarmInverterTempBad OBJECT IDENTIFIER ::= { upsAlarm 13 } Davison, Wasson, Draper, and Case [Page 21] Internet Draft UPS MIB July 1992 Expires 1/1/93 upsAlarmControllerTempBad OBJECT IDENTIFIER ::= { upsAlarm 14 } upsAlarmStopNoticeIssued OBJECT IDENTIFIER ::= { upsAlarm 15 } upsAlarmChargerFailed OBJECT IDENTIFIER ::= { upsAlarm 16 } upsAlarmUpsOff OBJECT IDENTIFIER ::= { upsAlarm 17 } Davison, Wasson, Draper, and Case [Page 22] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Test group -- testXYZ - Initiates test of the XYZ function. -- testXYZStatus - An enumerated value indicating test results -- -- Implementation of this group is mandatory for all systems. -- upsTest OBJECT IDENTIFIER ::= { univPowerSupply 8 } upsTestBattery OBJECT-TYPE SYNTAX INTEGER { start(1), abort(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Setting this variable to 'start' will initiate the battery test. Setting this variable to 'abort' will stop the battery test if the test is in- progress, otherwise it has no effect. Reading this variable will return zero. If 'upsTestBatteryStatus' is 'failed' the test may not be performed again and the status will remain in the failure state." ::= { upsTest 1 } upsTestBatteryStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), passed(2), failed(3), inProgress(4), sysFailure(5), notSupported(6), inhibited(7) } ACCESS read-only STATUS mandatory DESCRIPTION "The status of the battery test." ::= { upsTest 2 } upsTestDiag OBJECT-TYPE SYNTAX INTEGER { start(1), abort(2) } ACCESS read-write Davison, Wasson, Draper, and Case [Page 23] Internet Draft UPS MIB July 1992 Expires 1/1/93 STATUS mandatory DESCRIPTION "Setting this variable to 'start' will initiate the diagnostics test. Setting this variable to 'abort' will stop the diagnostics test if the test is in-progress, otherwise it has no effect. Reading this variable will return zero." ::= { upsTest 3 } upsTestDiagStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), passed(2), failed(3), inProgress(4), sysFailure(5), notSupported(6), inhibited(7) } ACCESS read-only STATUS mandatory DESCRIPTION "The status of the diagnostics test." ::= { upsTest 4 } upsTestIndicators OBJECT-TYPE SYNTAX INTEGER { start(1), abort(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Setting this variable to 'start' will initiate the indicators test. Setting this variable to 'abort' will stop the indicators test if the test is in-progress, otherwise it has no effect. Reading this variable will return zero." ::= { upsTest 5 } upsTestIndicatorsStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), passed(2), failed(3), inProgress(4), sysFailure(5), Davison, Wasson, Draper, and Case [Page 24] Internet Draft UPS MIB July 1992 Expires 1/1/93 notSupported(6), inhibited(7) } ACCESS read-only STATUS mandatory DESCRIPTION "The status of the indicators test. If this test requires visual verification, 'upsTestIndicatorsStatus' should be set to the 'unknown(1)' value." ::= { upsTest 6 } Davison, Wasson, Draper, and Case [Page 25] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Control group. -- Implementation of this group is mandatory for all systems. -- upsControl OBJECT IDENTIFIER ::= { univPowerSupply 9 } upsControlOutputOffDelay OBJECT-TYPE SYNTAX INTEGER (0..4294967296) 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 abort any shutdown sequence. The output will restart in the number of TimeTicks indicated by 'upsControlOutputOnDelay' unless it is equal to 0. In the later case, the output will remain inactive. This object will be set to 0 when the device is initialized on power-up or restart." ::= { upsControl 1 } upsControlOutputOnDelay OBJECT-TYPE SYNTAX INTEGER (0..4294967296) ACCESS read-write STATUS mandatory DESCRIPTION "The number of seconds to delay before coming on- line. If this value is 0 the output will remain off. This object will be set to 0 when the device is initialized on power-up or restart." ::= { upsControl 2 } upsControlOutputOffTrapDelay OBJECT-TYPE SYNTAX INTEGER (0..4294967296) ACCESS read-write STATUS mandatory DESCRIPTION "When 'upsControlOutputOffDelay' reaches a value less than or equal to this object's value, a trap should be produced. The trap may be repeated at a system-dependant rate." ::= { upsControl 3 } upsControlOutputOnTrapDelay OBJECT-TYPE Davison, Wasson, Draper, and Case [Page 26] Internet Draft UPS MIB July 1992 Expires 1/1/93 SYNTAX INTEGER (0..4294967296) ACCESS read-write STATUS mandatory DESCRIPTION "When 'upsControlOutputOnDelay' reaches a value less than or equal to this object's value, a trap should be produced. The trap may be repeated at a system-dependant rate." ::= { upsControl 4 } Davison, Wasson, Draper, and Case [Page 27] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The Configuration group. -- Implementation of this group is mandatory for all systems. -- upsConfig OBJECT IDENTIFIER ::= { univPowerSupply 10 } upsConfigOutputVoltage OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-write STATUS mandatory DESCRIPTION "The nominal output voltage. (Unit of measure: volt)" ::= { upsConfig 1 } upsConfigInputVoltage OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-write STATUS mandatory DESCRIPTION "The nominal input voltage. (Unit of measure: volt)" ::= { upsConfig 2 } upsConfigOutputVA OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-write STATUS mandatory DESCRIPTION "The nominal Volt-Amp rating." ::= { upsConfig 3 } upsConfigOutputWatts OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-write STATUS mandatory DESCRIPTION "The nominal power rating. (Unit of measure: watt)" ::= { upsConfig 4 } upsConfigOutputFreq OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-write Davison, Wasson, Draper, and Case [Page 28] Internet Draft UPS MIB July 1992 Expires 1/1/93 STATUS mandatory DESCRIPTION "The nominal output frequency. (Unit of measure: Hertz)" ::= { upsConfig 5 } upsConfigInputFreq OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-write STATUS mandatory DESCRIPTION "The nominal input frequency. (Unit of measure: milli-Hertz)" ::= { upsConfig 6 } upsConfigNominalBatTime OBJECT-TYPE SYNTAX INTEGER (0..65536) ACCESS read-write STATUS mandatory DESCRIPTION "The nominal battery time. (Unit of measure: minute)" ::= { upsConfig 7 } upsConfigAudioStatus OBJECT-TYPE SYNTAX INTEGER { on(1),off(2), squelch(3) } ACCESS read-write STATUS mandatory DESCRIPTION "The status of the audio alarm. 'Off' indicates the alarm will not sound, while the 'squelch' value indicates the alarm has sounded and squelched. A squelched audio status will return to the previous state ('on' or 'off') when the alarm stops sounding." ::= { upsConfig 8 } 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." ::= { upsConfig 9 } Davison, Wasson, Draper, and Case [Page 29] Internet Draft UPS MIB July 1992 Expires 1/1/93 -- -- The UPS Truck group. -- Implementation of this group is optional. -- upsTruck OBJECT IDENTIFIER ::= { univPowerSupply 11 } upsTruckColor OBJECT-TYPE SYNTAX INTEGER { brown(1) } ACCESS read-only STATUS mandatory DESCRIPTION "The UPS truck color." ::= { upsTruck 1 } END Davison, Wasson, Draper, and Case [Page 30] Internet Draft UPS MIB July 1992 Expires 1/1/93 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 Davison, Wasson, Draper, and Case [Page 31] Internet Draft UPS MIB July 1992 Expires 1/1/93 Comments 1215. Network Information Center, SRI International, Menlo Park, California, (March, 1991). Davison, Wasson, Draper, and Case [Page 32] Internet Draft UPS MIB July 1992 Expires 1/1/93 Table of Contents 1 Abstract .............................................. 2 2 Status of this Memo ................................... 2 3 Management Framework .................................. 2 4 Objects ............................................... 4 4.1 Format of Definitions ............................... 4 5 Overview .............................................. 5 6 Definitions ........................................... 6 6.1 The Device Identification Group ..................... 7 6.2 The Battery Group ................................... 9 6.3 The Input Group ..................................... 11 6.4 The Output Group .................................... 14 6.5 The Bypass Group .................................... 17 6.6 The Environment Group ............................... 19 6.7 The Alarm Group ..................................... 20 6.8 The Test Group ...................................... 23 6.9 The Control Group ................................... 26 6.10 The Configuration Group ............................ 28 6.10 The UPS Truck Group ................................ 30 7 References ............................................ 31 Davison, Wasson, Draper, and Case [Page 33]