GEPARALLELUPS-MIB: View SNMP OID List / Download MIB

The MIB module to describe GE Digital Energy Uninterruptible Power Supplies.

Reading this variable returns bit mask indicating which UPSs in a parallel system are alive. Management software should poll only these UPSs on their snmp branches 11-18 as follows: 1 FirstUPS alive 2 SecondUPS alive 4 ThirdUPS alive 8 FourthUPS alive 16 FifthUPS alive 32 SixthUPS alive 64 SeventhUPS alive 128 EigthUPS alive Since the management software should always monitor the GenericUPS branch (10), this value has no meaning for single upses (which provide values on that snmp branch), and should be set to zero in that case.

Put the string, formatted as a IMV/CP4 packet, directly to internally RS485 bus. This OID could be used for accede directly to the internally RS485 bus from a remote place.

Contain the reply of the IMV/CP4 request packet sent using the OID geRequestPacket. Every time that a write command has be made at the OID ge RequestPacket, the value of this OID is erased.

The name of the UPS manufacturer.(*)

The UPS Model designation.(*)

The UPS firmware/software version(s). This variable may or may not have the same value as upsIdentAgentSoftwareVersion in some implementations.(*)

The UPS agent software version. This variable may or may not have the same value as upsIdentUPSSoftwareVersion in some implementations.(*)

A string identifying the UPS. This object should be set by the administrator.(*)

A string identifying the devices attached to the output(s) of the UPS. This object should be set by the administrator.(*)

The UPS serial number

The IMV communication protocol version

The present value of the operating time. total 'on' time since UPS manufactured

The indication of the capacity remaining in the UPS system's batteries. A value of batteryNormal indicates that the remaining run-time is greater than upsConfigLowBattTime. A value of batteryLow indicates that the remaining battery run-time is less than or equal to upsConfigLowBattTime. A value of batteryDepleted indicates that the UPS will be unable to sustain the present load when and if the utility power is lost (including the possibility that the utility power is currently absent and the UPS is unable to sustain the output).(*) Enumeration: 'unknown': 1, 'batteryNormal': 2, 'batteryDepleted': 4, 'batteryLow': 3.

If the unit is on battery power, the elapsed time since the UPS last switched to battery power, or the time since the network management subsystem was last restarted, whichever is less. Zero shall be returned if the unit is not on battery power.(*)

An estimate of the time to battery charge depletion under the present load conditions if the utility power is off and remains off, or if it were to be lost and remain off.(*)

An estimate of the battery charge remaining expressed as a percent of full charge.(*)

The magnitude of the present battery voltage.(*)

The present battery current.(*)

The ambient temperature at or near the UPS Battery casing.(*)

The present DC link RMS voltage ripple.(*)

A count of the number of times the input entered an out-of-tolerance condition as defined by the manufacturer. This count is incremented by one each time the input transitions from zero out-of-tolerance lines to one or more input lines out-of-tolerance.(*)

The number of input lines utilized in this device. This variable indicates the number of rows in the input table.(*)

A list of input table entries. The number of entries is given by the value of upsInputNumLines.(*)

An entry containing information applicable to a particular input line.(*)

The input line identifier.(*)

The present input frequency.(*)

The magnitude of the present input voltage.(*)

The magnitude of the present input current.(*)

The magnitude of the present input true power.(*)

The lowest magnitude of the input voltage since last read out.

The highest magnitude of the input voltage since last read out.

The present source of output power. The enumeration none(2) indicates that there is no source of output power (and therefore no output power), for example, the system has opened the output breaker.(*) Enumeration: 'none': 2, 'normal': 3, 'battery': 5, 'reducer': 7, 'other': 1, 'bypass': 4, 'booster': 6.

The present output frequency.(*)

The number of output lines utilized in this device. This variable indicates the number of rows in the output table.(*)

A list of output table entries. The number of entries is given by the value of upsOutputNumLines.(*)

An entry containing information applicable to a particular output line.(*)

The output line identifier.(*)

The present output voltage.(*)

The present output current.(*)

The present output true power.(*)

The percentage of the UPS power capacity presently being used on this output line, i.e., the greater of the percent load of true power capacity and the percent load of VA.(*)

The present output power factor. The returned value correspond to the cosf of the load. A positive value indicate an inductive load; a negative value indicate a capacitive load; value 1 indicate a resistive load. If the measure is not available due to a small load for a consistent calculation, the NA value is then returned.(*)

The present output peak current.(*)

In a parallel system ideally all the UPS are requested to contribute to the load with the same amount of current, i.e. with no current share. The current share occurs when an UPS exchanges some current with another UPS, so that this current component doesn't feed the load. The share part of the UPS current represents an undesired UPS loading, and therefore it should be minimized. If the share current is too high, the UPS results overloaded and in some conditions (i.e. very high load) the system could turn on bypass reducing dramatically the global system reliability. PMAD detects the amount of share currents in a parallel system, generating an alarm if this value is above a parameter-based threshold. Single UPS systems don't have this feature, NA will be provided.(*)

The present bypass frequency.(*)

The number of bypass lines utilized in this device. This entry indicates the number of rows in the bypass table.(*)

A list of bypass table entries. The number of entries is given by the value of upsBypassNumLines.(*)

An entry containing information applicable to a particular bypass input.(*)

The bypass line identifier.(*)

The present bypass voltage.(*)

The present bypass current.(*)

The present true power conveyed by the bypass.(*)

The present number of active alarm conditions.(*)

A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with upsAlarmId equal to 1, and increments the value of upsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of upsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because upsAlarmId might have wrapped. Alarms are named by an AutonomousType (OBJECT IDENTIFIER), upsAlarmDescr, to allow a single table to reflect well known alarms plus alarms defined by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. No two rows will have the same value of upsAlarmDescr, since alarms define conditions. In order to meet this requirement, care should be taken in the definition of alarm conditions to insure that a system cannot enter the same condition multiple times simultaneously. The number of rows in the table at any given time is reflected by the value of upsAlarmsPresent.(*)

An entry containing information applicable to a particular alarm.(*)

A unique identifier for an alarm condition. This value must remain constant.(*)

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.(*)

The value of sysUpTime when the alarm condition was detected. If the alarm condition was detected at the time of agent startup and presumably existed before agent startup, the value of upsAlarmTime shall equal 0.(*)

One or more batteries have been determined to require replacement.(*)

The UPS is drawing power from the batteries.(*)

The remaining battery run-time is less than or equal to upsConfigLowBattTime.(*)

The UPS will be unable to sustain the present load when and if the utility power is lost.(*)

A temperature is out of tolerance.(*)

An input condition is out of tolerance.(*)

An output condition (other than OutputOverload) is out of tolerance.(*)

The output load exceeds the UPS output capacity.(*)

The Bypass is presently engaged on the UPS.(*)

The Bypass is out of tolerance.(*)

The UPS has shutdown as requested, i.e., the output is off.(*)

The entire UPS has shutdown as commanded.(*)

An uncorrected problem has been detected within the UPS charger subsystem.(*)

The output of the UPS is in the off state.(*)

The UPS system is in the off state.(*)

The failure of one or more fans in the UPS has been detected.(*)

The failure of one or more fuses has been detected.(*)

A general fault in the UPS has been detected.(*)

The result of the last diagnostic test indicates a failure.(*)

A problem has been encountered in the communications between the agent and the UPS.(*)

The UPS output is off and the UPS is awaiting the return of input power.(*)

A upsShutdownAfterDelay countdown is underway.(*)

The UPS will turn off power to the load in less than 5 seconds; this may be either a timed shutdown or a low battery shutdown.(*)

A test is in progress, as initiated and indicated by the Test Group. Tests initiated via other implementation-specific mechanisms can indicate the presence of the testing in the alarm table, if desired, via a OBJECT-IDENTITY macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-IDENTITY.(*)

The receptacle are switch off

A problem on the High Speed Bus communication is detected

A CRC problem on the Highspeed Bus JA is detected.

A problem on the Connectivity Bus communication is detected

A CRC problem on the Highspeed Bus JB is detected.

The System detects an high current sharing on the parallel system

The System detects an high ripple voltage on one DC link

Specifies which alarm can be handled by the UPS. The 'Mask' parameter is a Long Integer32. The meaning of every bit is the same as for the 'upsAlarmGroupA' command. A bit having value=1 indicates that the corresponding alarm is handled by the UPS.

The test is named by an OBJECT IDENTIFIER which allows a standard mechanism for the initiation of tests, including the well known tests identified in this document as well as those introduced by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. Setting this variable initiates the named test. Sets to this variable require the presence of upsTestSpinLock in the same SNMP message. The set request will be rejected with an appropriate error message if the requested test cannot be performed, including attempts to start a test when another test is already in progress. The status of the current or last test is maintained in upsTestResultsSummary. Tests in progress may be aborted by setting the upsTestId variable to upsTestAbortTestInProgress. Read operations return the value of the name of the test in progress if a test is in progress or the name of the last test performed if no test is in progress, unless no test has been run, in which case the well known value upsTestNoTestsInitiated is returned.(*)

A spin lock on the test subsystem. The spinlock is used as follows. Before starting a test, a manager-station should make sure that a test is not in progress as follows: tryagain: get (upsTestSpinLock) while (upsTestResultsSummary == inProgress) { /* loop while a test is running for another manager */ short delay get (upsTestSpinLock) } lockvalue = upsTestSpinLock /* no test in progress, start the test */ set (upsTestSpinLock = lockvalue, upsTestId = requestedtest) if (errorindex == 1) { /* (upsTestSpinLock failed) */ /* if problem is not access control, then some other manager slipped in ahead of us */ goto tryagain } if (errorindex == 2) { /* (upsTestId) */ /* cannot perform the test */ give up } /* test started ok */ /* wait for test completion by polling upsTestResultsSummary */ get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) while (upsTestResultsSummary == inProgress) { short delay get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) } /* when test completes, retrieve any additional test results */ /* if upsTestSpinLock == lockvalue + 1, then these are our test */ /* results (as opposed to another manager's */ The initial value of upsTestSpinLock at agent initialization shall be 1.(*)

The results of the current or last UPS diagnostics test performed. The values for donePass(1), doneWarning(2), and doneError(3) indicate that the test completed either successfully, with a warning, or with an error, respectively. The value aborted(4) is returned for tests which are aborted by setting the value of upsTestId to upsTestAbortTestInProgress. Tests which have not yet concluded are indicated by inProgress(5). The value noTestsInitiated(6) indicates that no previous test results are available, such as is the case when no tests have been run since the last reinitialization of the network management subsystem and the system has no provision for non- volatile storage of test results.(*) Enumeration: 'doneError': 3, 'noTestsInitiated': 6, 'donePass': 1, 'doneWarning': 2, 'aborted': 4, 'inProgress': 5.

Additional information about upsTestResultsSummary. If no additional information available, a zero length string is returned.(*)

The value of sysUpTime at the time the test in progress was initiated, or, if no test is in progress, the time the previous test was initiated. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestStartTime has the value 0.(*)

The amount of time, in TimeTicks, since the test in progress was initiated, or, if no test is in progress, the previous test took to complete. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestElapsedTime has the value 0.(*)

No tests have been initiated and no test is in progress.(*)

The test in progress is to be aborted / the test in progress was aborted.(*)

The manufacturer's standard test of UPS device systems.(*)

A test that is sufficient to determine if the battery needs replacement.(*)

The system is placed on battery to a discharge level, set by the manufacturer, sufficient to determine battery replacement and battery run-time with a high degree of confidence. WARNING: this test will leave the battery in a low charge state and will require time for recharging to a level sufficient to provide normal battery duration for the protected load.(*)

This object determines the nature of the action to be taken at the time when the countdown of the upsShutdownAfterDelay and upsRebootWithDuration objects reaches zero. Setting this object to output(1) indicates that shutdown requests should cause only the output of the UPS to turn off. Setting this object to system(2) indicates that shutdown requests will cause the entire UPS system to turn off.(*) Enumeration: 'output': 1, 'system': 2.

Setting this object will shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) after the indicated number of seconds, or less if the UPS batteries become depleted. Setting this object to 0 will cause the shutdown to occur immediately. Setting this object to -1 will abort the countdown. If the system is already in the desired state at the time the countdown reaches 0, then nothing will happen. That is, there is no additional action at that time if upsShutdownType = system and the system is already off. Similarly, there is no additional action at that time if upsShutdownType = output and the output is already off. When read, upsShutdownAfterDelay will return the number of seconds remaining until shutdown, or -1 if no shutdown countdown is in effect. On some systems, if the agent is restarted while a shutdown countdown is in effect, the countdown may be aborted. Sets to this object override any upsShutdownAfterDelay already in effect.(*)

Setting this object will start the output after the indicated number of seconds, including starting the UPS, if necessary. Setting this object to 0 will cause the startup to occur immediately. Setting this object to -1 will abort the countdown. If the output is already on at the time the countdown reaches 0, then nothing will happen. Sets to this object override the effect of any upsStartupAfterDelay countdown or upsRebootWithDuration countdown in progress. When read, upsStartupAfterDelay will return the number of seconds until startup, or -1 if no startup countdown is in effect. If the countdown expires during a utility failure, the startup shall not occur until the utility power is restored. On some systems, if the agent is restarted while a startup countdown is in effect, the countdown is aborted.(*)

Setting this object will immediately shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) for a period equal to the indicated number of seconds, after which time the output will be started, including starting the UPS, if necessary. If the number of seconds required to perform the request is greater than the requested duration, then the requested shutdown and startup cycle shall be performed in the minimum time possible, but in no case shall this require more than the requested duration plus 60 seconds. When read, upsRebootWithDuration shall return the number of seconds remaining in the countdown, or -1 if no countdown is in progress. If the startup should occur during a utility failure, the startup shall not occur until the utility power is restored.(*)

Setting this object to 'on' will cause the UPS system to restart after a shutdown if the shutdown occurred during a power loss as a result of either a upsShutdownAfterDelay or an internal battery depleted condition. Setting this object to 'off' will prevent the UPS system from restarting after a shutdown until an operator manually or remotely explicitly restarts it. If the UPS is in a startup or reboot countdown, then the UPS will not restart until that delay has been satisfied.(*) Enumeration: 'on': 1, 'off': 2.

The number of receptacles utilized in this device. This entry indicates the number of rows in the receptacle table.

A list of receptacle table entries. The number of entries is given by the value of upsReceptacleNum.

An entry containing information applicable to a particular receptacle.

The receptacle line identifier.

The present state of the receptacle. Setting this object to 'on' will cause the receptacle to be turned on. Setting this object to 'off' will turn the receptacle off. If the receptacle is already in the desired state nothing will happen. After an autorestart (see upsAutoRestart) the receptacle will be on. Enumeration: 'on': 1, 'off': 2.

The operation mode off the UPS. Off-line indicates a mode in which the input power is transferred to the output directly or via a step-up or step-down transformer. On-line mode indicates a mode in which the output power is regenerated through some convertor. the operating mode of the UPS may be fixed, or may be selectable (e.g. an on-line UPS with ecomode) Enumeration: 'offLine': 1, 'iem': 4, 'ecomode': 3, 'onLine': 2.

The present state of the rectifier. Setting this object to 'on' will cause the rectifier to be turned on. Setting this object to 'off' will turn the rectifier off. If the rectifier is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present state of the charge method. Setting this object to 'Normal charge' will cause the battery to be charged using the normal method. Setting this object to 'Boost charge' will charge the battery in boost mode. If the charge method is already in the desired state nothing will happen. Enumeration: 'boostcharge': 2, 'normalcharge': 1.

The present state of the inverter. Setting this object to 'on' will cause the inverter to be turned on. Setting this object to 'off' will turn the inverter off. If the inverter is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present state of the bypass. Setting this object to 'on' will cause the bypass to be activated. Setting this object to 'off' will deactivate the bypass. If the UPS is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present source of the load. Setting this object to 'On bypass' will cause the load to be supplied by the bypass. Setting this object to 'On inverter' will cause the load to be supplied by the inverter. If the load is already supplied by the desired source nothing will happen. Enumeration: 'onInverter': 2, 'onDetour': 3, 'onbypass': 1, 'loadOff': 4, 'other': 5.

The magnitude of the nominal input voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The nominal input frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The magnitude of the nominal output voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The nominal output frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The magnitude of the nominal Volt-Amp rating.(*)

The magnitude of the nominal true power rating.(*)

The value of upsEstimatedMinutesRemaining at which a lowBattery condition is declared. For agents which support only discrete (discontinuous) values, then the agent shall round up to the next supported value. If the requested value is larger than the largest supported value, then the largest supported value shall be selected.(*)

The requested state of the audible alarm. When in the disabled state, the audible alarm should never sound. The enabled state is self-describing. Setting this object to muted(3) when the audible alarm is sounding shall temporarily silence the alarm. It will remain muted until it would normally stop sounding and the value returned for read operations during this period shall equal muted(3). At the end of this period, the value shall revert to enabled(2). Writes of the value muted(3) when the audible alarm is not sounding shall be accepted but otherwise shall have no effect.(*) Enumeration: 'disabled': 1, 'muted': 3, 'enabled': 2.

The minimum input line voltage allowed before the UPS system transfers to battery backup.(*)

The maximum line voltage allowed before the UPS system transfers to battery backup.(*)

The installed battery capacity. This value is the 'factory'-value, not the value after calibration.

The maximum battery charge current, including external chargers.

Dis- or enable 'no load' shutdown from the contact interface. Enumeration: 'disabled': 1, 'enabled': 2.

Minimum required autonomy time before the UPS may perform an autorestart.

The number of events to retreive from the UPS event buffer. When this object is set the EventTable will be filled with the requested number of entries. The value upsEventSetStartingTimeStamp will be used as the start value of the table with the lowest index number.

The number of events to retreive from the UPS event buffer. When this object is set the EventTable will be filled with the requested number of entries. The value upsEventLastTime will be used as the last value of the table with the highest index number. Returns SNMPNOSUCHNAME for UPSs that don't support this command.

The timestamp which is used as starting point for downloading events from the UPS event buffer

The current timestamp is retreived from the UPS

The number of entries in the event table. This object indicates the number of rows in the event table.

A list of event table entries. The number of entries is always 10, and the value of upsEventTableSize gives the number of valid entries from the begging of the table. Invalid entries return 0. To prevent problems with simultaneous queries from several agents, these values MUST be accessed using several PDUs in the same SNMP message ( is (1..10)): PDU-SET upsSetStartingTimeStamp PDU-SET upsEventGetNext PDU-GET upsEventTableSize PDU-GET upsEventCode,upsEventStatus,upsEventTime 1 PDU-GET upsEventCode,upsEventStatus,upsEventTime 2 .. PDU-GET upsEventCode,upsEventStatus,upsEventTime The table is read up to requested number of events and the management software afterwards decides which entries are valid, as indicated by the upsEventTableSize.

An entry containing information applicable to a particular event.

The event line identifier.

The event code in numerical format.

The status of the UPS at the moment that the event was generated. The format is specified at the 'upsStatus' command. If the UPS is not able to deliver status information, then SNMPNOSUCHNAME is returned.

The timestamp of the moment the event was generated.

The number of parameters to retreive from the UPS. When this object is set the ParameterTable will be filled with the requested number of entries. The value upsParametersStartAddress will be used as the start value of the table with the lowest index number.

The number of parameters to write to the UPS. When this object is set the ParameterTable will be send to the ups. The value upsParametersStartAddress will be used for the first value of the table with the lowest index number.

The address which is used as starting point for downloading parameters from the UPS

The number of entries in the parameter table. This object indicates the number of rows in the parameter table.

A list of parameter entries. The number of entries is always 16, and the value of upsParameterTableSize gives the number of valid entries from the begging of the table. Invalid entries return 0. To prevent problems with simultaneous queries from several agents, these values MUST be accessed using several PDUs in the same SNMP message ( is (1..16)): Read sequence: PDU-SET upsSetStartingAddress PDU-SET upsParametersRead PDU-GET upsParameterTableSize PDU-GET upsParameterValue 1 PDU-GET upsParameterValue 2 .. PDU-GET upsParameterValue The table is read up to requested number of events and the management software afterwards decides which entries are valid, as indicated by the upsParameterTableSize. Write sequence: PDU-SET upsSetStartingAddress PDU-SET upsParameterValue 1 PDU-SET upsParameterValue 2 .. PDU-SET upsParameterValue PDU-SET upsParametersWrite

An entry containing information applicable to a particular parameter.

The parameter line identifier.

The parameter value in numerical format.

The global UPS status is returned. Every bit reflects a specific status condition. Unused bits returns as 0. The status value can also be found on other commands. The value SNMPNOSUCHNAME means 'invalid status' or 'status value non available'. Status 1 0000 0001h upsStatusEcomodeIsOn 2 0000 0002h upsStatusBatteryIsCharging 4 0000 0004h upsStatusBatteryIsDischarging 8 0000 0008h upsStatusAlarmIsActive 16 0000 0010h upsStatusRectifierIsOn 32 0000 0020h upsStatusLowBattery 64 0000 0040h upsStatusOnBypass 128 0000 0080h upsStatusMainsBypassOK 256 0000 0100h upsStatusMainsRectifierOK 512 0000 0200h upsStatusDetourIsOn 1024 0000 0400h upsStatusAcousticAlarmIsOn 2048 0000 0800h upsStatusGlobalServiceCheck 4096 0000 1000h upsStatusInverterIsOn 8192 0000 2000h upsStatusNotInParallel (Q1 open) 16384 0000 4000h upsStatusResetLoadOff 32768 0000 8000h upsStatusLoadOff 65536 0001 0000h upsStatusBoostMode 131072 0002 0000h upsStatusBuckMode 262144 0004 0000h upsStatusIemModeIsOn 524288 0008 0000h upsStatus5thFilterIsOn 1048576 0010 0000h upsStatus11thFilterIsOn 2097152 0020 0000h upsStatus2ndRectifierBridgeIsOn 4194304 0040 0000h - reserved - 8388608 0080 0000h - reserved - 16777216 0100 0000h - reserved - 33554432 0200 0000h - reserved - 67108864 0400 0000h - reserved - 134217728 0800 0000h - reserved - 268435456 1000 0000h upsGlobalParallelValues

Count of main bypass failures (>200 ms), since UPS installation.

Count of mains rectifier failures (>200 ms), since UPS installation.

Count of transients on the mains bypass (0..2 ms), during the last 7 days.

Count of transients on the mains bypass (2..5 ms), during the last 7 days.

Count of transients on the mains bypass (5..10 ms), during the last 7 days.

Count of transients on the mains bypass (10..200 ms), during the last 7 days.

Bypass reliability degree [0..100%;255]. The value NOSUCHNAME means 'not available'.

The current timestamp (or real-time) of the UPS. For the format, see 'Timestamp' specifications. The write-command has to comply with the correct timestamp format expected by the UPS (counter value or real-time-clock value). Missing to doing so will result in a SNMPgenERROR, meaning 'command not supported'. It is possible to know which is the timestamp format supported by the UPS, by issuing a read-command or by reading events, which includes timestamps.

An encrypted code is send to enable use of restricted write objects during a limited period of time.

The code which is used as starting point to downloading the events from the UPS event buffer.

A spin lock on the event subsystem.

A spin lock on the parameters subsystem.

One or more batteries have been determined to require replacement.

The UPS is drawing power from the batteries.

The remaining battery run-time is less than or equal to upsConfigLowBattTime.

The UPS will be unable to sustain the present load when and if the utility power is lost)

A temperature is out of tolerance.

An input condition is out of tolerance.

An output condition (other than OutputOverload) is out of tolerance.

The output load exceeds the UPS output capacity.

The Bypass is presently engaged on the UPS.

The Bypass is out of tolerance.

The UPS has shutdown as requested, i.e., the output is off.

The entire UPS has shutdown as commanded.

An uncorrected problem has been detected within the UPS charger subsystem.

The output of the UPS is in the off state.

The UPS system is in the off state.

The failure of one or more fans in the UPS has been detected.

The failure of one or more fuses has been detected.

A general fault in the UPS has been detected.

The result of the last diagnostic test indicates a failure.

A problem has been encountered in the communication between the agent and the UPS.

The UPS output is off and the UPS is awaiting the return of the input power (*).

A upsShutdownAfterDelay countdown is underway.

The UPS will turn off power to the load in less than 5 seconds; this may be either a timed shutdown or a low battery shutdown.

A test is in progress, as initiated and indicated by the Test Group. Tests initiated via other implementation-specific mechanisms can indicate the presence of the testing in the alarm table, if desired, via a OBJECT-IDENTITY macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-IDENTITY.

A receptacle has been switched off.

A problem on the Highspeed Bus communication is detected.

A CRC failure on the Highspeed Bus JA is detected.

A problem on the Connectivity Bus is detected.

A CRC failure on the Highspeed Bus JB is detected.

An high current sharing on the parallel system is detected.

An high ripple voltage on his DC link is detected.

A Battery bad condition is restored.

The UPS is drawing power from mains again.

A Low Battery condition is restored.

A Depleted Battery condition is restored.

A bad temperature condition is restored.

An input bad condition is restored.

An output bad condition is restored.

An output overload condition is restored.

An On Bypass condition is restored.

A Bypass bad condition is restored.

A request shutdown has been restored.

A entire UPS command has been restored.

A Charger Failer condition is restored.

The output of the UPS switched in the on state.

The UPS system is switched in the on state.

A Fan failure condition is restored.

A Fuse failure condition is restored.

A general fault is restored.

A last diagnostic test indicates a failure is restored.

A problem in the communication between the agent and the UPS is restored.

A awaiting power condition is restored (*).

A upsShutdownAfterDelay countdown is restored.

A shutdown imminent condition is restored.

The test is in progress is terminated.

A receptacle has been switched on.

A problem on the Highspeed Bus communication is restored.

A CRC failure on the Highspeed Bus JA is restored.

A problem on the Connectivity Bus communication is restored.

A CRC failure on the Highspeed Bus JB is restored.

An high current sharing on the parallel system is restored.

An high ripple voltage on his DC link is restored.

A measurement value reached a value below its low-level threshold.

A measurement value reached a value higher than its high-level threshold.

A ValueLow alarm condition is restored.

A ValueHigh alarm condition is restored.

Bit oriented values associated to the ID of the UPS (bit0 = UPS1 ... bit7 = UPS8). The correspondent UPS is not present on the high speed bus communication JA if bit=0.(*)

Bit oriented values associated to the ID of the UPS (bit0 = UPS1 ... bit7 = UPS8). The correspondent UPS is not present on the high speed bus communication JA if bit=0.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The name of the UPS manufacturer.(*)

The UPS Model designation.(*)

The UPS firmware/software version(s). This variable may or may not have the same value as upsIdentAgentSoftwareVersion in some implementations.(*)

The UPS agent software version. This variable may or may not have the same value as upsIdentUPSSoftwareVersion in some implementations.(*)

A string identifying the UPS. This object should be set by the administrator.(*)

A string identifying the devices attached to the output(s) of the UPS. This object should be set by the administrator.(*)

The UPS serial number

The IMV communication protocol version

The present value of the operating time. total 'on' time since UPS manufactured

The indication of the capacity remaining in the UPS system's batteries. A value of batteryNormal indicates that the remaining run-time is greater than upsConfigLowBattTime. A value of batteryLow indicates that the remaining battery run-time is less than or equal to upsConfigLowBattTime. A value of batteryDepleted indicates that the UPS will be unable to sustain the present load when and if the utility power is lost (including the possibility that the utility power is currently absent and the UPS is unable to sustain the output).(*) Enumeration: 'unknown': 1, 'batteryNormal': 2, 'batteryDepleted': 4, 'batteryLow': 3.

If the unit is on battery power, the elapsed time since the UPS last switched to battery power, or the time since the network management subsystem was last restarted, whichever is less. Zero shall be returned if the unit is not on battery power.(*)

An estimate of the time to battery charge depletion under the present load conditions if the utility power is off and remains off, or if it were to be lost and remain off.(*)

An estimate of the battery charge remaining expressed as a percent of full charge.(*)

The magnitude of the present battery voltage.(*)

The present battery current.(*)

The ambient temperature at or near the UPS Battery casing.(*)

The present DC link RMS voltage ripple.(*)

A count of the number of times the input entered an out-of-tolerance condition as defined by the manufacturer. This count is incremented by one each time the input transitions from zero out-of-tolerance lines to one or more input lines out-of-tolerance.(*)

The number of input lines utilized in this device. This variable indicates the number of rows in the input table.(*)

A list of input table entries. The number of entries is given by the value of upsInputNumLines.(*)

An entry containing information applicable to a particular input line.(*)

The input line identifier.(*)

The present input frequency.(*)

The magnitude of the present input voltage.(*)

The magnitude of the present input current.(*)

The magnitude of the present input true power.(*)

The lowest magnitude of the input voltage since last read out.

The highest magnitude of the input voltage since last read out.

The present source of output power. The enumeration none(2) indicates that there is no source of output power (and therefore no output power), for example, the system has opened the output breaker.(*) Enumeration: 'none': 2, 'normal': 3, 'battery': 5, 'reducer': 7, 'other': 1, 'bypass': 4, 'booster': 6.

The present output frequency.(*)

The number of output lines utilized in this device. This variable indicates the number of rows in the output table.(*)

A list of output table entries. The number of entries is given by the value of upsOutputNumLines.(*)

An entry containing information applicable to a particular output line.(*)

The output line identifier.(*)

The present output voltage.(*)

The present output current.(*)

The present output true power.(*)

The percentage of the UPS power capacity presently being used on this output line, i.e., the greater of the percent load of true power capacity and the percent load of VA.(*)

The present output power factor. The returned value correspond to the cosf of the load. A positive value indicate an inductive load; a negative value indicate a capacitive load; value 1 indicate a resistive load. If the measure is not available due to a small load for a consistent calculation, the NA value is then returned.(*)

The present output peak current.(*)

In a parallel system ideally all the UPS are requested to contribute to the load with the same amount of current, i.e. with no current share. The current share occurs when an UPS exchanges some current with another UPS, so that this current component doesn't feed the load. The share part of the UPS current represents an undesired UPS loading, and therefore it should be minimized. If the share current is too high, the UPS results overloaded and in some conditions (i.e. very high load) the system could turn on bypass reducing dramatically the global system reliability. PMAD detects the amount of share currents in a parallel system, generating an alarm if this value is above a parameter-based threshold. Single UPS systems don't have this feature, NA will be provided.(*)

The present bypass frequency.(*)

The number of bypass lines utilized in this device. This entry indicates the number of rows in the bypass table.(*)

A list of bypass table entries. The number of entries is given by the value of upsBypassNumLines.(*)

An entry containing information applicable to a particular bypass input.(*)

The bypass line identifier.(*)

The present bypass voltage.(*)

The present bypass current.(*)

The present true power conveyed by the bypass.(*)

The present number of active alarm conditions.(*)

A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with upsAlarmId equal to 1, and increments the value of upsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of upsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because upsAlarmId might have wrapped. Alarms are named by an AutonomousType (OBJECT IDENTIFIER), upsAlarmDescr, to allow a single table to reflect well known alarms plus alarms defined by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. No two rows will have the same value of upsAlarmDescr, since alarms define conditions. In order to meet this requirement, care should be taken in the definition of alarm conditions to insure that a system cannot enter the same condition multiple times simultaneously. The number of rows in the table at any given time is reflected by the value of upsAlarmsPresent.(*)

An entry containing information applicable to a particular alarm.(*)

A unique identifier for an alarm condition. This value must remain constant.(*)

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.(*)

The value of sysUpTime when the alarm condition was detected. If the alarm condition was detected at the time of agent startup and presumably existed before agent startup, the value of upsAlarmTime shall equal 0.(*)

One or more batteries have been determined to require replacement.(*)

The UPS is drawing power from the batteries.(*)

The remaining battery run-time is less than or equal to upsConfigLowBattTime.(*)

The UPS will be unable to sustain the present load when and if the utility power is lost.(*)

A temperature is out of tolerance.(*)

An input condition is out of tolerance.(*)

An output condition (other than OutputOverload) is out of tolerance.(*)

The output load exceeds the UPS output capacity.(*)

The Bypass is presently engaged on the UPS.(*)

The Bypass is out of tolerance.(*)

The UPS has shutdown as requested, i.e., the output is off.(*)

The entire UPS has shutdown as commanded.(*)

An uncorrected problem has been detected within the UPS charger subsystem.(*)

The output of the UPS is in the off state.(*)

The UPS system is in the off state.(*)

The failure of one or more fans in the UPS has been detected.(*)

The failure of one or more fuses has been detected.(*)

A general fault in the UPS has been detected.(*)

The result of the last diagnostic test indicates a failure.(*)

A problem has been encountered in the communications between the agent and the UPS.(*)

The UPS output is off and the UPS is awaiting the return of input power.(*)

A upsShutdownAfterDelay countdown is underway.(*)

The UPS will turn off power to the load in less than 5 seconds; this may be either a timed shutdown or a low battery shutdown.(*)

A test is in progress, as initiated and indicated by the Test Group. Tests initiated via other implementation-specific mechanisms can indicate the presence of the testing in the alarm table, if desired, via a OBJECT-IDENTITY macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-IDENTITY.(*)

The receptacle are switch off

A problem on the High Speed Bus communication is detected

A CRC failure on High Speed Bus JA is detected.

A problem on the Connectivity Bus communication is detected.

A CRC failure on High Speed Bus JB is detected.

The UPS detects an high current sharing on the parallel system.

The UPS detects an high ripple voltage on his DC link.

Specifies which alarm can be handled by the UPS. The 'Mask' parameter is a Long Integer32. The meaning of every bit is the same as for the 'upsAlarmGroupA' command. A bit having value=1 indicates that the corresponding alarm is handled by the UPS.

The test is named by an OBJECT IDENTIFIER which allows a standard mechanism for the initiation of tests, including the well known tests identified in this document as well as those introduced by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. Setting this variable initiates the named test. Sets to this variable require the presence of upsTestSpinLock in the same SNMP message. The set request will be rejected with an appropriate error message if the requested test cannot be performed, including attempts to start a test when another test is already in progress. The status of the current or last test is maintained in upsTestResultsSummary. Tests in progress may be aborted by setting the upsTestId variable to upsTestAbortTestInProgress. Read operations return the value of the name of the test in progress if a test is in progress or the name of the last test performed if no test is in progress, unless no test has been run, in which case the well known value upsTestNoTestsInitiated is returned.(*)

A spin lock on the test subsystem. The spinlock is used as follows. Before starting a test, a manager-station should make sure that a test is not in progress as follows: tryagain: get (upsTestSpinLock) while (upsTestResultsSummary == inProgress) { /* loop while a test is running for another manager */ short delay get (upsTestSpinLock) } lockvalue = upsTestSpinLock /* no test in progress, start the test */ set (upsTestSpinLock = lockvalue, upsTestId = requestedtest) if (errorindex == 1) { /* (upsTestSpinLock failed) */ /* if problem is not access control, then some other manager slipped in ahead of us */ goto tryagain } if (errorindex == 2) { /* (upsTestId) */ /* cannot perform the test */ give up } /* test started ok */ /* wait for test completion by polling upsTestResultsSummary */ get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) while (upsTestResultsSummary == inProgress) { short delay get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) } /* when test completes, retrieve any additional test results */ /* if upsTestSpinLock == lockvalue + 1, then these are our test */ /* results (as opposed to another manager's */ The initial value of upsTestSpinLock at agent initialization shall be 1.(*)

The results of the current or last UPS diagnostics test performed. The values for donePass(1), doneWarning(2), and doneError(3) indicate that the test completed either successfully, with a warning, or with an error, respectively. The value aborted(4) is returned for tests which are aborted by setting the value of upsTestId to upsTestAbortTestInProgress. Tests which have not yet concluded are indicated by inProgress(5). The value noTestsInitiated(6) indicates that no previous test results are available, such as is the case when no tests have been run since the last reinitialization of the network management subsystem and the system has no provision for non- volatile storage of test results.(*) Enumeration: 'doneError': 3, 'noTestsInitiated': 6, 'donePass': 1, 'doneWarning': 2, 'aborted': 4, 'inProgress': 5.

Additional information about upsTestResultsSummary. If no additional information available, a zero length string is returned.(*)

The value of sysUpTime at the time the test in progress was initiated, or, if no test is in progress, the time the previous test was initiated. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestStartTime has the value 0.(*)

The amount of time, in TimeTicks, since the test in progress was initiated, or, if no test is in progress, the previous test took to complete. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestElapsedTime has the value 0.(*)

No tests have been initiated and no test is in progress.(*)

The test in progress is to be aborted / the test in progress was aborted.(*)

The manufacturer's standard test of UPS device systems.(*)

A test that is sufficient to determine if the battery needs replacement.(*)

The system is placed on battery to a discharge level, set by the manufacturer, sufficient to determine battery replacement and battery run-time with a high degree of confidence. WARNING: this test will leave the battery in a low charge state and will require time for recharging to a level sufficient to provide normal battery duration for the protected load.(*)

This object determines the nature of the action to be taken at the time when the countdown of the upsShutdownAfterDelay and upsRebootWithDuration objects reaches zero. Setting this object to output(1) indicates that shutdown requests should cause only the output of the UPS to turn off. Setting this object to system(2) indicates that shutdown requests will cause the entire UPS system to turn off.(*) Enumeration: 'output': 1, 'system': 2.

Setting this object will shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) after the indicated number of seconds, or less if the UPS batteries become depleted. Setting this object to 0 will cause the shutdown to occur immediately. Setting this object to -1 will abort the countdown. If the system is already in the desired state at the time the countdown reaches 0, then nothing will happen. That is, there is no additional action at that time if upsShutdownType = system and the system is already off. Similarly, there is no additional action at that time if upsShutdownType = output and the output is already off. When read, upsShutdownAfterDelay will return the number of seconds remaining until shutdown, or -1 if no shutdown countdown is in effect. On some systems, if the agent is restarted while a shutdown countdown is in effect, the countdown may be aborted. Sets to this object override any upsShutdownAfterDelay already in effect.(*)

Setting this object will start the output after the indicated number of seconds, including starting the UPS, if necessary. Setting this object to 0 will cause the startup to occur immediately. Setting this object to -1 will abort the countdown. If the output is already on at the time the countdown reaches 0, then nothing will happen. Sets to this object override the effect of any upsStartupAfterDelay countdown or upsRebootWithDuration countdown in progress. When read, upsStartupAfterDelay will return the number of seconds until startup, or -1 if no startup countdown is in effect. If the countdown expires during a utility failure, the startup shall not occur until the utility power is restored. On some systems, if the agent is restarted while a startup countdown is in effect, the countdown is aborted.(*)

Setting this object will immediately shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) for a period equal to the indicated number of seconds, after which time the output will be started, including starting the UPS, if necessary. If the number of seconds required to perform the request is greater than the requested duration, then the requested shutdown and startup cycle shall be performed in the minimum time possible, but in no case shall this require more than the requested duration plus 60 seconds. When read, upsRebootWithDuration shall return the number of seconds remaining in the countdown, or -1 if no countdown is in progress. If the startup should occur during a utility failure, the startup shall not occur until the utility power is restored.(*)

Setting this object to 'on' will cause the UPS system to restart after a shutdown if the shutdown occurred during a power loss as a result of either a upsShutdownAfterDelay or an internal battery depleted condition. Setting this object to 'off' will prevent the UPS system from restarting after a shutdown until an operator manually or remotely explicitly restarts it. If the UPS is in a startup or reboot countdown, then the UPS will not restart until that delay has been satisfied.(*) Enumeration: 'on': 1, 'off': 2.

The number of receptacles utilized in this device. This entry indicates the number of rows in the receptacle table.

A list of receptacle table entries. The number of entries is given by the value of upsReceptacleNum.

An entry containing information applicable to a particular receptacle.

The receptacle line identifier.

The present state of the receptacle. Setting this object to 'on' will cause the receptacle to be turned on. Setting this object to 'off' will turn the receptacle off. If the receptacle is already in the desired state nothing will happen. After an autorestart (see upsAutoRestart) the receptacle will be on. Enumeration: 'on': 1, 'off': 2.

The operation mode off the UPS. Off-line indicates a mode in which the input power is transferred to the output directly or via a step-up or step-down transformer. On-line mode indicates a mode in which the output power is regenerated through some convertor. the operating mode of the UPS may be fixed, or may be selectable (e.g. an on-line UPS with ecomode) Enumeration: 'offLine': 1, 'iem': 4, 'ecomode': 3, 'onLine': 2.

The present state of the rectifier. Setting this object to 'on' will cause the rectifier to be turned on. Setting this object to 'off' will turn the rectifier off. If the rectifier is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present state of the charge method. Setting this object to 'Normal charge' will cause the battery to be charged using the normal method. Setting this object to 'Boost charge' will charge the battery in boost mode. If the charge method is already in the desired state nothing will happen. Enumeration: 'boostcharge': 2, 'normalcharge': 1.

The present state of the inverter. Setting this object to 'on' will cause the inverter to be turned on. Setting this object to 'off' will turn the inverter off. If the inverter is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present state of the bypass. Setting this object to 'on' will cause the bypass to be activated. Setting this object to 'off' will deactivate the bypass. If the UPS is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present source of the load. Setting this object to 'On bypass' will cause the load to be supplied by the bypass. Setting this object to 'On inverter' will cause the load to be supplied by the inverter. If the load is already supplied by the desired source nothing will happen. Enumeration: 'onInverter': 2, 'onDetour': 3, 'onbypass': 1, 'loadOff': 4, 'other': 5.

The magnitude of the nominal input voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The nominal input frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The magnitude of the nominal output voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The nominal output frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The magnitude of the nominal Volt-Amp rating.(*)

The magnitude of the nominal true power rating.(*)

The value of upsEstimatedMinutesRemaining at which a lowBattery condition is declared. For agents which support only discrete (discontinuous) values, then the agent shall round up to the next supported value. If the requested value is larger than the largest supported value, then the largest supported value shall be selected.(*)

The requested state of the audible alarm. When in the disabled state, the audible alarm should never sound. The enabled state is self-describing. Setting this object to muted(3) when the audible alarm is sounding shall temporarily silence the alarm. It will remain muted until it would normally stop sounding and the value returned for read operations during this period shall equal muted(3). At the end of this period, the value shall revert to enabled(2). Writes of the value muted(3) when the audible alarm is not sounding shall be accepted but otherwise shall have no effect.(*) Enumeration: 'disabled': 1, 'muted': 3, 'enabled': 2.

The minimum input line voltage allowed before the UPS system transfers to battery backup.(*)

The maximum line voltage allowed before the UPS system transfers to battery backup.(*)

The installed battery capacity. This value is the 'factory'-value, not the value after calibration.

The maximum battery charge current, including external chargers.

Dis- or enable 'no load' shutdown from the contact interface. Enumeration: 'disabled': 1, 'enabled': 2.

Minimum required autonomy time before the UPS may perform an autorestart.

The number of events to retreive from the UPS event buffer. When this object is set the EventTable will be filled with the requested number of entries. The value upsEventSetStartingTimeStamp will be used as the start value of the table with the lowest index number.

The number of events to retreive from the UPS event buffer. When this object is set the EventTable will be filled with the requested number of entries. The value upsEventLastTime will be used as the last value of the table with the highest index number. Returns SNMPNOSUCHNAME for UPSs that don't support this command.

The timestamp which is used as starting point for downloading events from the UPS event buffer

The current timestamp is retreived from the UPS

The number of entries in the event table. This object indicates the number of rows in the event table.

A list of event table entries. The number of entries is always 10, and the value of upsEventTableSize gives the number of valid entries from the begging of the table. Invalid entries return 0. To prevent problems with simultaneous queries from several agents, these values MUST be accessed using several PDUs in the same SNMP message ( is (1..10)): PDU-SET upsSetStartingTimeStamp PDU-SET upsEventGetNext PDU-GET upsEventTableSize PDU-GET upsEventCode,upsEventStatus,upsEventTime 1 PDU-GET upsEventCode,upsEventStatus,upsEventTime 2 .. PDU-GET upsEventCode,upsEventStatus,upsEventTime The table is read up to requested number of events and the management software afterwards decides which entries are valid, as indicated by the upsEventTableSize.

An entry containing information applicable to a particular event.

The event line identifier.

The event code in numerical format.

The status of the UPS at the moment that the event was generated. The format is specified at the 'upsStatus' command. If the UPS is not able to deliver status information, then SNMPNOSUCHNAME is returned.

The timestamp of the moment the event was generated.

The number of parameters to retreive from the UPS. When this object is set the ParameterTable will be filled with the requested number of entries. The value upsParametersStartAddress will be used as the start value of the table with the lowest index number.

The number of parameters to write to the UPS. When this object is set the ParameterTable will be send to the ups. The value upsParametersStartAddress will be used for the first value of the table with the lowest index number.

The address which is used as starting point for downloading parameters from the UPS

The number of entries in the parameter table. This object indicates the number of rows in the parameter table.

A list of parameter entries. The number of entries is always 16, and the value of upsParameterTableSize gives the number of valid entries from the begging of the table. Invalid entries return 0. To prevent problems with simultaneous queries from several agents, these values MUST be accessed using several PDUs in the same SNMP message ( is (1..16)): Read sequence: PDU-SET upsSetStartingAddress PDU-SET upsParametersRead PDU-GET upsParameterTableSize PDU-GET upsParameterValue 1 PDU-GET upsParameterValue 2 .. PDU-GET upsParameterValue The table is read up to requested number of events and the management software afterwards decides which entries are valid, as indicated by the upsParameterTableSize. Write sequence: PDU-SET upsSetStartingAddress PDU-SET upsParameterValue 1 PDU-SET upsParameterValue 2 .. PDU-SET upsParameterValue PDU-SET upsParametersWrite

An entry containing information applicable to a particular parameter.

The parameter line identifier.

The parameter value in numerical format.

The global UPS status is returned. Every bit reflects a specific status condition. Unused bits returns as 0. The status value can also be found on other commands. The value SNMPNOSUCHNAME means 'invalid status' or 'status value non available'. Status 1 0000 0001h upsStatusEcomodeIsOn 2 0000 0002h upsStatusBatteryIsCharging 4 0000 0004h upsStatusBatteryIsDischarging 8 0000 0008h upsStatusAlarmIsActive 16 0000 0010h upsStatusRectifierIsOn 32 0000 0020h upsStatusLowBattery 64 0000 0040h upsStatusOnBypass 128 0000 0080h upsStatusMainsBypassOK 256 0000 0100h upsStatusMainsRectifierOK 512 0000 0200h upsStatusDetourIsOn 1024 0000 0400h upsStatusAcousticAlarmIsOn 2048 0000 0800h upsStatusGlobalServiceCheck 4096 0000 1000h upsStatusInverterIsOn 8192 0000 2000h upsStatusNotInParallel (Q1 open) 16384 0000 4000h upsStatusResetLoadOff 32768 0000 8000h upsStatusLoadOff 65536 0001 0000h upsStatusBoostMode 131072 0002 0000h upsStatusBuckMode 262144 0004 0000h upsStatusIemModeIsOn 524288 0008 0000h upsStatus5thFilterIsOn 1048576 0010 0000h upsStatus11thFilterIsOn 2097152 0020 0000h upsStatus2ndRectifierBridgeIsOn 4194304 0040 0000h - reserved - 8388608 0080 0000h - reserved - 16777216 0100 0000h - reserved - 33554432 0200 0000h - reserved - 67108864 0400 0000h - reserved - 134217728 0800 0000h - reserved - 268435456 1000 0000h upsGlobalParallelValues

Count of main bypass failures (>200 ms), since UPS installation.

Count of mains rectifier failures (>200 ms), since UPS installation.

Count of transients on the mains bypass (0..2 ms), during the last 7 days.

Count of transients on the mains bypass (2..5 ms), during the last 7 days.

Count of transients on the mains bypass (5..10 ms), during the last 7 days.

Count of transients on the mains bypass (10..200 ms), during the last 7 days.

Bypass reliability degree [0..100%;255]. The value NOSUCHNAME means 'not available'.

The current timestamp (or real-time) of the UPS. For the format, see 'Timestamp' specifications. The write-command has to comply with the correct timestamp format expected by the UPS (counter value or real-time-clock value). Missing to doing so will result in a SNMPfirstERROR, meaning 'command not supported'. It is possible to know which is the timestamp format supported by the UPS, by issuing a read-command or by reading events, which includes timestamps.

An encrypted code is send to enable use of restricted write objects during a limited period of time.

The code which is used as starting point to downloading the events from the UPS event buffer.

A spin lock on the event subsystem.

A spin lock on the parameters subsystem.

One or more batteries have been determined to require replacement.

The UPS is drawing power from the batteries.

The remaining battery run-time is less than or equal to upsConfigLowBattTime.

The UPS will be unable to sustain the present load when and if the utility power is lost)

A temperature is out of tolerance.

An input condition is out of tolerance.

An output condition (other than OutputOverload) is out of tolerance.

The output load exceeds the UPS output capacity.

The Bypass is presently engaged on the UPS.

The Bypass is out of tolerance.

The UPS has shutdown as requested, i.e., the output is off.

The entire UPS has shutdown as commanded.

An uncorrected problem has been detected within the UPS charger subsystem.

The output of the UPS is in the off state.

The UPS system is in the off state.

The failure of one or more fans in the UPS has been detected.

The failure of one or more fuses has been detected.

A general fault in the UPS has been detected.

The result of the last diagnostic test indicates a failure.

A problem has been encountered in the communication between the agent and the UPS.

The UPS output is off and the UPS is awaiting the return of the input power (*).

A upsShutdownAfterDelay countdown is underway.

The UPS will turn off power to the load in less than 5 seconds; this may be either a timed shutdown or a low battery shutdown.

A test is in progress, as initiated and indicated by the Test Group. Tests initiated via other implementation-specific mechanisms can indicate the presence of the testing in the alarm table, if desired, via a OBJECT-IDENTITY macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-IDENTITY.

A receptacle has been switched off.

A problem on the Highspeed Bus communication is detected.

A CRC failure on the Highspeed Bus JB is detected.

A problem on the Connectivity Bus communication is detected

A CRC failure on the Highspeed Bus JB is detected.

An high current sharing on the parallel system is detected.

An high ripple voltage on his DC link is detected.

A Battery bad condition is restored.

The UPS is drawing power from mains again.

A Low Battery condition is restored.

A Depleted Battery condition is restored.

A bad temperature condition is restored.

An input bad condition is restored.

An output bad condition is restored.

An output overload condition is restored.

An On Bypass condition is restored.

A Bypass bad condition is restored.

A request shutdown has been restored.

A entire UPS command has been restored.

A Charger Failer condition is restored.

The output of the UPS switched in the on state.

The UPS system is switched in the on state.

A Fan failure condition is restored.

A Fuse failure condition is restored.

A general fault is restored.

A last diagnostic test indicates a failure is restored.

A problem in the communication between the agent and the UPS is restored.

A awaiting power condition is restored (*).

A upsShutdownAfterDelay countdown is restored.

A shutdown imminent condition is restored.

The test is in progress is terminated.

A receptacle has been switched on.

A problem on the Highspeed Bus communication is restored.

A CRC failure on the Highspeed Bus JA is restored.

A problem on the Connectivity Bus communication is restored.

A CRC failure on the Highspeed Bus JB is restored.

An high current sharing on the parallel system is restored.

An high ripple voltage on his DC link is restored.

A measurement value reached a value below its low-level threshold.

A measurement value reached a value higher than its high-level threshold.

A ValueLow alarm condition is restored.

A ValueHigh alarm condition is restored.

Bit oriented values associated to the ID of the UPS (bit0 = UPS1 ... bit7 = UPS8). The correspondent UPS is not present on the high speed bus communication JA if bit=0.(*)

Bit oriented values associated to the ID of the UPS (bit0 = UPS1 ... bit7 = UPS8). The correspondent UPS is not present on the high speed bus communication JA if bit=0.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The name of the UPS manufacturer.(*)

The UPS Model designation.(*)

The UPS firmware/software version(s). This variable may or may not have the same value as upsIdentAgentSoftwareVersion in some implementations.(*)

The UPS agent software version. This variable may or may not have the same value as upsIdentUPSSoftwareVersion in some implementations.(*)

A string identifying the UPS. This object should be set by the administrator.(*)

A string identifying the devices attached to the output(s) of the UPS. This object should be set by the administrator.(*)

The UPS serial number

The IMV communication protocol version

The present value of the operating time. total 'on' time since UPS manufactured

The indication of the capacity remaining in the UPS system's batteries. A value of batteryNormal indicates that the remaining run-time is greater than upsConfigLowBattTime. A value of batteryLow indicates that the remaining battery run-time is less than or equal to upsConfigLowBattTime. A value of batteryDepleted indicates that the UPS will be unable to sustain the present load when and if the utility power is lost (including the possibility that the utility power is currently absent and the UPS is unable to sustain the output).(*) Enumeration: 'unknown': 1, 'batteryNormal': 2, 'batteryDepleted': 4, 'batteryLow': 3.

If the unit is on battery power, the elapsed time since the UPS last switched to battery power, or the time since the network management subsystem was last restarted, whichever is less. Zero shall be returned if the unit is not on battery power.(*)

An estimate of the time to battery charge depletion under the present load conditions if the utility power is off and remains off, or if it were to be lost and remain off.(*)

An estimate of the battery charge remaining expressed as a percent of full charge.(*)

The magnitude of the present battery voltage.(*)

The present battery current.(*)

The ambient temperature at or near the UPS Battery casing.(*)

The present DC link RMS voltage ripple.(*)

A count of the number of times the input entered an out-of-tolerance condition as defined by the manufacturer. This count is incremented by one each time the input transitions from zero out-of-tolerance lines to one or more input lines out-of-tolerance.(*)

The number of input lines utilized in this device. This variable indicates the number of rows in the input table.(*)

A list of input table entries. The number of entries is given by the value of upsInputNumLines.(*)

An entry containing information applicable to a particular input line.(*)

The input line identifier.(*)

The present input frequency.(*)

The magnitude of the present input voltage.(*)

The magnitude of the present input current.(*)

The magnitude of the present input true power.(*)

The lowest magnitude of the input voltage since last read out.

The highest magnitude of the input voltage since last read out.

The present source of output power. The enumeration none(2) indicates that there is no source of output power (and therefore no output power), for example, the system has opened the output breaker.(*) Enumeration: 'none': 2, 'normal': 3, 'battery': 5, 'reducer': 7, 'other': 1, 'bypass': 4, 'booster': 6.

The present output frequency.(*)

The number of output lines utilized in this device. This variable indicates the number of rows in the output table.(*)

A list of output table entries. The number of entries is given by the value of upsOutputNumLines.(*)

An entry containing information applicable to a particular output line.(*)

The output line identifier.(*)

The present output voltage.(*)

The present output current.(*)

The present output true power.(*)

The percentage of the UPS power capacity presently being used on this output line, i.e., the greater of the percent load of true power capacity and the percent load of VA.(*)

The present output power factor. The returned value correspond to the cosf of the load. A positive value indicate an inductive load; a negative value indicate a capacitive load; value 1 indicate a resistive load. If the measure is not available due to a small load for a consistent calculation, the NA value is then returned.(*)

The present output peak current.(*)

In a parallel system ideally all the UPS are requested to contribute to the load with the same amount of current, i.e. with no current share. The current share occurs when an UPS exchanges some current with another UPS, so that this current component doesn't feed the load. The share part of the UPS current represents an undesired UPS loading, and therefore it should be minimized. If the share current is too high, the UPS results overloaded and in some conditions (i.e. very high load) the system could turn on bypass reducing dramatically the global system reliability. PMAD detects the amount of share currents in a parallel system, generating an alarm if this value is above a parameter-based threshold. Single UPS systems don't have this feature, NA will be provided.(*)

The present bypass frequency.(*)

The number of bypass lines utilized in this device. This entry indicates the number of rows in the bypass table.(*)

A list of bypass table entries. The number of entries is given by the value of upsBypassNumLines.(*)

An entry containing information applicable to a particular bypass input.(*)

The bypass line identifier.(*)

The present bypass voltage.(*)

The present bypass current.(*)

The present true power conveyed by the bypass.(*)

The present number of active alarm conditions.(*)

A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with upsAlarmId equal to 1, and increments the value of upsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of upsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because upsAlarmId might have wrapped. Alarms are named by an AutonomousType (OBJECT IDENTIFIER), upsAlarmDescr, to allow a single table to reflect well known alarms plus alarms defined by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. No two rows will have the same value of upsAlarmDescr, since alarms define conditions. In order to meet this requirement, care should be taken in the definition of alarm conditions to insure that a system cannot enter the same condition multiple times simultaneously. The number of rows in the table at any given time is reflected by the value of upsAlarmsPresent.(*)

An entry containing information applicable to a particular alarm.(*)

A unique identifier for an alarm condition. This value must remain constant.(*)

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.(*)

The value of sysUpTime when the alarm condition was detected. If the alarm condition was detected at the time of agent startup and presumably existed before agent startup, the value of upsAlarmTime shall equal 0.(*)

One or more batteries have been determined to require replacement.(*)

The UPS is drawing power from the batteries.(*)

The remaining battery run-time is less than or equal to upsConfigLowBattTime.(*)

The UPS will be unable to sustain the present load when and if the utility power is lost.(*)

A temperature is out of tolerance.(*)

An input condition is out of tolerance.(*)

An output condition (other than OutputOverload) is out of tolerance.(*)

The output load exceeds the UPS output capacity.(*)

The Bypass is presently engaged on the UPS.(*)

The Bypass is out of tolerance.(*)

The UPS has shutdown as requested, i.e., the output is off.(*)

The entire UPS has shutdown as commanded.(*)

An uncorrected problem has been detected within the UPS charger subsystem.(*)

The output of the UPS is in the off state.(*)

The UPS system is in the off state.(*)

The failure of one or more fans in the UPS has been detected.(*)

The failure of one or more fuses has been detected.(*)

A general fault in the UPS has been detected.(*)

The result of the last diagnostic test indicates a failure.(*)

A problem has been encountered in the communications between the agent and the UPS.(*)

The UPS output is off and the UPS is awaiting the return of input power.(*)

A upsShutdownAfterDelay countdown is underway.(*)

The UPS will turn off power to the load in less than 5 seconds; this may be either a timed shutdown or a low battery shutdown.(*)

A test is in progress, as initiated and indicated by the Test Group. Tests initiated via other implementation-specific mechanisms can indicate the presence of the testing in the alarm table, if desired, via a OBJECT-IDENTITY macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-IDENTITY.(*)

The receptacle are switch off

A problem on the High Speed Bus communication is detected

A High Speed Bus CRC failure on Bus JB is detected.

A problem on the Connectivity Bus communication is detected.

A High Speed Bus CRC failure on Bus JB is detected.

The UPS detects an high current sharing on the parallel system.

The UPS detects an high ripple voltage on his DC link.

Specifies which alarm can be handled by the UPS. The 'Mask' parameter is a Long Integer32. The meaning of every bit is the same as for the 'upsAlarmGroupA' command. A bit having value=1 indicates that the corresponding alarm is handled by the UPS.

The test is named by an OBJECT IDENTIFIER which allows a standard mechanism for the initiation of tests, including the well known tests identified in this document as well as those introduced by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. Setting this variable initiates the named test. Sets to this variable require the presence of upsTestSpinLock in the same SNMP message. The set request will be rejected with an appropriate error message if the requested test cannot be performed, including attempts to start a test when another test is already in progress. The status of the current or last test is maintained in upsTestResultsSummary. Tests in progress may be aborted by setting the upsTestId variable to upsTestAbortTestInProgress. Read operations return the value of the name of the test in progress if a test is in progress or the name of the last test performed if no test is in progress, unless no test has been run, in which case the well known value upsTestNoTestsInitiated is returned.(*)

A spin lock on the test subsystem. The spinlock is used as follows. Before starting a test, a manager-station should make sure that a test is not in progress as follows: tryagain: get (upsTestSpinLock) while (upsTestResultsSummary == inProgress) { /* loop while a test is running for another manager */ short delay get (upsTestSpinLock) } lockvalue = upsTestSpinLock /* no test in progress, start the test */ set (upsTestSpinLock = lockvalue, upsTestId = requestedtest) if (errorindex == 1) { /* (upsTestSpinLock failed) */ /* if problem is not access control, then some other manager slipped in ahead of us */ goto tryagain } if (errorindex == 2) { /* (upsTestId) */ /* cannot perform the test */ give up } /* test started ok */ /* wait for test completion by polling upsTestResultsSummary */ get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) while (upsTestResultsSummary == inProgress) { short delay get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) } /* when test completes, retrieve any additional test results */ /* if upsTestSpinLock == lockvalue + 1, then these are our test */ /* results (as opposed to another manager's */ The initial value of upsTestSpinLock at agent initialization shall be 1.(*)

The results of the current or last UPS diagnostics test performed. The values for donePass(1), doneWarning(2), and doneError(3) indicate that the test completed either successfully, with a warning, or with an error, respectively. The value aborted(4) is returned for tests which are aborted by setting the value of upsTestId to upsTestAbortTestInProgress. Tests which have not yet concluded are indicated by inProgress(5). The value noTestsInitiated(6) indicates that no previous test results are available, such as is the case when no tests have been run since the last reinitialization of the network management subsystem and the system has no provision for non- volatile storage of test results.(*) Enumeration: 'doneError': 3, 'noTestsInitiated': 6, 'donePass': 1, 'doneWarning': 2, 'aborted': 4, 'inProgress': 5.

Additional information about upsTestResultsSummary. If no additional information available, a zero length string is returned.(*)

The value of sysUpTime at the time the test in progress was initiated, or, if no test is in progress, the time the previous test was initiated. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestStartTime has the value 0.(*)

The amount of time, in TimeTicks, since the test in progress was initiated, or, if no test is in progress, the previous test took to complete. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestElapsedTime has the value 0.(*)

No tests have been initiated and no test is in progress.(*)

The test in progress is to be aborted / the test in progress was aborted.(*)

The manufacturer's standard test of UPS device systems.(*)

A test that is sufficient to determine if the battery needs replacement.(*)

The system is placed on battery to a discharge level, set by the manufacturer, sufficient to determine battery replacement and battery run-time with a high degree of confidence. WARNING: this test will leave the battery in a low charge state and will require time for recharging to a level sufficient to provide normal battery duration for the protected load.(*)

This object determines the nature of the action to be taken at the time when the countdown of the upsShutdownAfterDelay and upsRebootWithDuration objects reaches zero. Setting this object to output(1) indicates that shutdown requests should cause only the output of the UPS to turn off. Setting this object to system(2) indicates that shutdown requests will cause the entire UPS system to turn off.(*) Enumeration: 'output': 1, 'system': 2.

Setting this object will shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) after the indicated number of seconds, or less if the UPS batteries become depleted. Setting this object to 0 will cause the shutdown to occur immediately. Setting this object to -1 will abort the countdown. If the system is already in the desired state at the time the countdown reaches 0, then nothing will happen. That is, there is no additional action at that time if upsShutdownType = system and the system is already off. Similarly, there is no additional action at that time if upsShutdownType = output and the output is already off. When read, upsShutdownAfterDelay will return the number of seconds remaining until shutdown, or -1 if no shutdown countdown is in effect. On some systems, if the agent is restarted while a shutdown countdown is in effect, the countdown may be aborted. Sets to this object override any upsShutdownAfterDelay already in effect.(*)

Setting this object will start the output after the indicated number of seconds, including starting the UPS, if necessary. Setting this object to 0 will cause the startup to occur immediately. Setting this object to -1 will abort the countdown. If the output is already on at the time the countdown reaches 0, then nothing will happen. Sets to this object override the effect of any upsStartupAfterDelay countdown or upsRebootWithDuration countdown in progress. When read, upsStartupAfterDelay will return the number of seconds until startup, or -1 if no startup countdown is in effect. If the countdown expires during a utility failure, the startup shall not occur until the utility power is restored. On some systems, if the agent is restarted while a startup countdown is in effect, the countdown is aborted.(*)

Setting this object will immediately shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) for a period equal to the indicated number of seconds, after which time the output will be started, including starting the UPS, if necessary. If the number of seconds required to perform the request is greater than the requested duration, then the requested shutdown and startup cycle shall be performed in the minimum time possible, but in no case shall this require more than the requested duration plus 60 seconds. When read, upsRebootWithDuration shall return the number of seconds remaining in the countdown, or -1 if no countdown is in progress. If the startup should occur during a utility failure, the startup shall not occur until the utility power is restored.(*)

Setting this object to 'on' will cause the UPS system to restart after a shutdown if the shutdown occurred during a power loss as a result of either a upsShutdownAfterDelay or an internal battery depleted condition. Setting this object to 'off' will prevent the UPS system from restarting after a shutdown until an operator manually or remotely explicitly restarts it. If the UPS is in a startup or reboot countdown, then the UPS will not restart until that delay has been satisfied.(*) Enumeration: 'on': 1, 'off': 2.

The number of receptacles utilized in this device. This entry indicates the number of rows in the receptacle table.

A list of receptacle table entries. The number of entries is given by the value of upsReceptacleNum.

An entry containing information applicable to a particular receptacle.

The receptacle line identifier.

The present state of the receptacle. Setting this object to 'on' will cause the receptacle to be turned on. Setting this object to 'off' will turn the receptacle off. If the receptacle is already in the desired state nothing will happen. After an autorestart (see upsAutoRestart) the receptacle will be on. Enumeration: 'on': 1, 'off': 2.

The operation mode off the UPS. Off-line indicates a mode in which the input power is transferred to the output directly or via a step-up or step-down transformer. On-line mode indicates a mode in which the output power is regenerated through some convertor. the operating mode of the UPS may be fixed, or may be selectable (e.g. an on-line UPS with ecomode) Enumeration: 'offLine': 1, 'iem': 4, 'ecomode': 3, 'onLine': 2.

The present state of the rectifier. Setting this object to 'on' will cause the rectifier to be turned on. Setting this object to 'off' will turn the rectifier off. If the rectifier is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present state of the charge method. Setting this object to 'Normal charge' will cause the battery to be charged using the normal method. Setting this object to 'Boost charge' will charge the battery in boost mode. If the charge method is already in the desired state nothing will happen. Enumeration: 'boostcharge': 2, 'normalcharge': 1.

The present state of the inverter. Setting this object to 'on' will cause the inverter to be turned on. Setting this object to 'off' will turn the inverter off. If the inverter is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present state of the bypass. Setting this object to 'on' will cause the bypass to be activated. Setting this object to 'off' will deactivate the bypass. If the UPS is already in the desired state nothing will happen. Enumeration: 'on': 1, 'off': 2.

The present source of the load. Setting this object to 'On bypass' will cause the load to be supplied by the bypass. Setting this object to 'On inverter' will cause the load to be supplied by the inverter. If the load is already supplied by the desired source nothing will happen. Enumeration: 'onInverter': 2, 'onDetour': 3, 'onbypass': 1, 'loadOff': 4, 'other': 5.

The magnitude of the nominal input voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The nominal input frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The magnitude of the nominal output voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The nominal output frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.(*)

The magnitude of the nominal Volt-Amp rating.(*)

The magnitude of the nominal true power rating.(*)

The value of upsEstimatedMinutesRemaining at which a lowBattery condition is declared. For agents which support only discrete (discontinuous) values, then the agent shall round up to the next supported value. If the requested value is larger than the largest supported value, then the largest supported value shall be selected.(*)

The requested state of the audible alarm. When in the disabled state, the audible alarm should never sound. The enabled state is self-describing. Setting this object to muted(3) when the audible alarm is sounding shall temporarily silence the alarm. It will remain muted until it would normally stop sounding and the value returned for read operations during this period shall equal muted(3). At the end of this period, the value shall revert to enabled(2). Writes of the value muted(3) when the audible alarm is not sounding shall be accepted but otherwise shall have no effect.(*) Enumeration: 'disabled': 1, 'muted': 3, 'enabled': 2.

The minimum input line voltage allowed before the UPS system transfers to battery backup.(*)

The maximum line voltage allowed before the UPS system transfers to battery backup.(*)

The installed battery capacity. This value is the 'factory'-value, not the value after calibration.

The maximum battery charge current, including external chargers.

Dis- or enable 'no load' shutdown from the contact interface. Enumeration: 'disabled': 1, 'enabled': 2.

Minimum required autonomy time before the UPS may perform an autorestart.

The number of events to retreive from the UPS event buffer. When this object is set the EventTable will be filled with the requested number of entries. The value upsEventSetStartingTimeStamp will be used as the start value of the table with the lowest index number.

The number of events to retreive from the UPS event buffer. When this object is set the EventTable will be filled with the requested number of entries. The value upsEventLastTime will be used as the last value of the table with the highest index number. Returns SNMPNOSUCHNAME for UPSs that don't support this command.

The timestamp which is used as starting point for downloading events from the UPS event buffer

The current timestamp is retreived from the UPS

The number of entries in the event table. This object indicates the number of rows in the event table.

A list of event table entries. The number of entries is always 10, and the value of upsEventTableSize gives the number of valid entries from the begging of the table. Invalid entries return 0. To prevent problems with simultaneous queries from several agents, these values MUST be accessed using several PDUs in the same SNMP message ( is (1..10)): PDU-SET upsSetStartingTimeStamp PDU-SET upsEventGetNext PDU-GET upsEventTableSize PDU-GET upsEventCode,upsEventStatus,upsEventTime 1 PDU-GET upsEventCode,upsEventStatus,upsEventTime 2 .. PDU-GET upsEventCode,upsEventStatus,upsEventTime The table is read up to requested number of events and the management software afterwards decides which entries are valid, as indicated by the upsEventTableSize.

An entry containing information applicable to a particular event.

The event line identifier.

The event code in numerical format.

The status of the UPS at the moment that the event was generated. The format is specified at the 'upsStatus' command. If the UPS is not able to deliver status information, then SNMPNOSUCHNAME is returned.

The timestamp of the moment the event was generated.

The number of parameters to retreive from the UPS. When this object is set the ParameterTable will be filled with the requested number of entries. The value upsParametersStartAddress will be used as the start value of the table with the lowest index number.

The number of parameters to write to the UPS. When this object is set the ParameterTable will be send to the ups. The value upsParametersStartAddress will be used for the second value of the table with the lowest index number.

The address which is used as starting point for downloading parameters from the UPS

The number of entries in the parameter table. This object indicates the number of rows in the parameter table.

A list of parameter entries. The number of entries is always 16, and the value of upsParameterTableSize gives the number of valid entries from the begging of the table. Invalid entries return 0. To prevent problems with simultaneous queries from several agents, these values MUST be accessed using several PDUs in the same SNMP message ( is (1..16)): Read sequence: PDU-SET upsSetStartingAddress PDU-SET upsParametersRead PDU-GET upsParameterTableSize PDU-GET upsParameterValue 1 PDU-GET upsParameterValue 2 .. PDU-GET upsParameterValue The table is read up to requested number of events and the management software afterwards decides which entries are valid, as indicated by the upsParameterTableSize. Write sequence: PDU-SET upsSetStartingAddress PDU-SET upsParameterValue 1 PDU-SET upsParameterValue 2 .. PDU-SET upsParameterValue PDU-SET upsParametersWrite

An entry containing information applicable to a particular parameter.

The parameter line identifier.

The parameter value in numerical format.

The global UPS status is returned. Every bit reflects a specific status condition. Unused bits returns as 0. The status value can also be found on other commands. The value SNMPNOSUCHNAME means 'invalid status' or 'status value non available'. Status 1 0000 0001h upsStatusEcomodeIsOn 2 0000 0002h upsStatusBatteryIsCharging 4 0000 0004h upsStatusBatteryIsDischarging 8 0000 0008h upsStatusAlarmIsActive 16 0000 0010h upsStatusRectifierIsOn 32 0000 0020h upsStatusLowBattery 64 0000 0040h upsStatusOnBypass 128 0000 0080h upsStatusMainsBypassOK 256 0000 0100h upsStatusMainsRectifierOK 512 0000 0200h upsStatusDetourIsOn 1024 0000 0400h upsStatusAcousticAlarmIsOn 2048 0000 0800h upsStatusGlobalServiceCheck 4096 0000 1000h upsStatusInverterIsOn 8192 0000 2000h upsStatusNotInParallel (Q1 open) 16384 0000 4000h upsStatusResetLoadOff 32768 0000 8000h upsStatusLoadOff 65536 0001 0000h upsStatusBoostMode 131072 0002 0000h upsStatusBuckMode 262144 0004 0000h upsStatusIemModeIsOn 524288 0008 0000h upsStatus5thFilterIsOn 1048576 0010 0000h upsStatus11thFilterIsOn 2097152 0020 0000h upsStatus2ndRectifierBridgeIsOn 4194304 0040 0000h - reserved - 8388608 0080 0000h - reserved - 16777216 0100 0000h - reserved - 33554432 0200 0000h - reserved - 67108864 0400 0000h - reserved - 134217728 0800 0000h - reserved - 268435456 1000 0000h upsGlobalParallelValues

Count of main bypass failures (>200 ms), since UPS installation.

Count of mains rectifier failures (>200 ms), since UPS installation.

Count of transients on the mains bypass (0..2 ms), during the last 7 days.

Count of transients on the mains bypass (2..5 ms), during the last 7 days.

Count of transients on the mains bypass (5..10 ms), during the last 7 days.

Count of transients on the mains bypass (10..200 ms), during the last 7 days.

Bypass reliability degree [0..100%;255]. The value NOSUCHNAME means 'not available'.

The current timestamp (or real-time) of the UPS. For the format, see 'Timestamp' specifications. The write-command has to comply with the correct timestamp format expected by the UPS (counter value or real-time-clock value). Missing to doing so will result in a SNMPsecondERROR, meaning 'command not supported'. It is possible to know which is the timestamp format supported by the UPS, by issuing a read-command or by reading events, which includes timestamps.

An encrypted code is send to enable use of restricted write objects during a limited period of time.

The code which is used as starting point to downloading the events from the UPS event buffer.

A spin lock on the event subsystem.

A spin lock on the parameters subsystem.

One or more batteries have been determined to require replacement.

The UPS is drawing power from the batteries.

The remaining battery run-time is less than or equal to upsConfigLowBattTime.

The UPS will be unable to sustain the present load when and if the utility power is lost)

A temperature is out of tolerance.

An input condition is out of tolerance.

An output condition (other than OutputOverload) is out of tolerance.

The output load exceeds the UPS output capacity.

The Bypass is presently engaged on the UPS.

The Bypass is out of tolerance.

The UPS has shutdown as requested, i.e., the output is off.

The entire UPS has shutdown as commanded.

An uncorrected problem has been detected within the UPS charger subsystem.

The output of the UPS is in the off state.

The UPS system is in the off state.

The failure of one or more fans in the UPS has been detected.

The failure of one or more fuses has been detected.

A general fault in the UPS has been detected.

The result of the last diagnostic test indicates a failure.

A problem has been encountered in the communication between the agent and the UPS.

The UPS output is off and the UPS is awaiting the return of the input power (*).

A upsShutdownAfterDelay countdown is underway.

The UPS will turn off power to the load in less than 5 seconds; this may be either a timed shutdown or a low battery shutdown.

A test is in progress, as initiated and indicated by the Test Group. Tests initiated via other implementation-specific mechanisms can indicate the presence of the testing in the alarm table, if desired, via a OBJECT-IDENTITY macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-IDENTITY.

A receptacle has been switched off.

A problem on the Highspeed Bus communication is detected.

A CRC failure on the Highspeed Bus JA is detected.

A problem on the Connectivity Bus communication is detected.

A CRC failure on the Highspeed Bus JB is detected.

An high current sharing on the parallel system is detected.

An high ripple voltage on his DC link is detected.

A Battery bad condition is restored.

The UPS is drawing power from mains again.

A Low Battery condition is restored.

A Depleted Battery condition is restored.

A bad temperature condition is restored.

An input bad condition is restored.

An output bad condition is restored.

An output overload condition is restored.

An On Bypass condition is restored.

A Bypass bad condition is restored.

A request shutdown has been restored.

A entire UPS command has been restored.

A Charger Failer condition is restored.

The output of the UPS switched in the on state.

The UPS system is switched in the on state.

A Fan failure condition is restored.

A Fuse failure condition is restored.

A general fault is restored.

A last diagnostic test indicates a failure is restored.

A problem in the communication between the agent and the UPS is restored.

A awaiting power condition is restored (*).

A upsShutdownAfterDelay countdown is restored.

A shutdown imminent condition is restored.

The test is in progress is terminated.

A receptacle has been switched on.

A problem on the Highspeed Bus communication is restored.

A CRC failure on the Highspeed Bus JA is restored.

A problem on the Connectivity Bus communication is restored.

A CRC failure on the Highspeed Bus JB is restored.

An high current sharing on the parallel system is restored.

An high ripple voltage on his DC link is restored.

A measurement value reached a value below its low-level threshold.

A measurement value reached a value higher than its high-level threshold.

A ValueLow alarm condition is restored.

A ValueHigh alarm condition is restored.

Bit oriented values associated to the ID of the UPS (bit0 = UPS1 ... bit7 = UPS8). The correspondent UPS is not present on the high speed bus communication JA if bit=0.(*)

Bit oriented values associated to the ID of the UPS (bit0 = UPS1 ... bit7 = UPS8). The correspondent UPS is not present on the high speed bus communication JA if bit=0.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The critical components are associated to Service parameters indicating the remaining lifetime. They are initially set to default values depending to the data given by the component supplier. The parameter values decrease over time and when one of them reaches zero (lifetime expiration) a service check warning is generated, indicating that a check or a replacement is suggested for that component. The service technician is then required to re-set the default value after the replacing of the component.(*)

The name of the UPS manufacturer.(*)

The UPS Model designation.(*)

The UPS firmware/software version(s). This variable may or may not have the same value as upsIdentAgentSoftwareVersion in some implementations.(*)

The UPS agent software version. This variable may or may not have the same value as upsIdentUPSSoftwareVersion in some implementations.(*)

A string identifying the UPS. This object should be set by the administrator.(*)

A string identifying the devices attached to the output(s) of the UPS. This object should be set by the administrator.(*)

The UPS serial number

The IMV communication protocol version

The present value of the operating time. total 'on' time since UPS manufactured

The indication of the capacity remaining in the UPS system's batteries. A value of batteryNormal indicates that the remaining run-time is greater than upsConfigLowBattTime. A value of batteryLow indicates that the remaining battery run-time is less than or equal to upsConfigLowBattTime. A value of batteryDepleted indicates that the UPS will be unable to sustain the present load when and if the utility power is lost (including the possibility that the utility power is currently absent and the UPS is unable to sustain the output).(*) Enumeration: 'unknown': 1, 'batteryNormal': 2, 'batteryDepleted': 4, 'batteryLow': 3.

If the unit is on battery power, the elapsed time since the UPS last switched to battery power, or the time since the network management subsystem was last restarted, whichever is less. Zero shall be returned if the unit is not on battery power.(*)

An estimate of the time to battery charge depletion under the present load conditions if the utility power is off and remains off, or if it were to be lost and remain off.(*)

An estimate of the battery charge remaining expressed as a percent of full charge.(*)

The magnitude of the present battery voltage.(*)

The present battery current.(*)

The ambient temperature at or near the UPS Battery casing.(*)

The present DC link RMS voltage ripple.(*)

A count of the number of times the input entered an out-of-tolerance condition as defined by the manufacturer. This count is incremented by one each time the input transitions from zero out-of-tolerance lines to one or more input lines out-of-tolerance.(*)

The number of input lines utilized in this device. This variable indicates the number of rows in the input table.(*)

A list of input table entries. The number of entries is given by the value of upsInputNumLines.(*)

An entry containing information applicable to a particular input line.(*)

The input line identifier.(*)

The present input frequency.(*)

The magnitude of the present input voltage.(*)

The magnitude of the present input current.(*)

The magnitude of the present input true power.(*)

The lowest magnitude of the input voltage since last read out.

The highest magnitude of the input voltage since last read out.

The present source of output power. The enumeration none(2) indicates that there is no source of output power (and therefore no output power), for example, the system has opened the output breaker.(*) Enumeration: 'none': 2, 'normal': 3, 'battery': 5, 'reducer': 7, 'other': 1, 'bypass': 4, 'booster': 6.

The present output frequency.(*)

The number of output lines utilized in this device. This variable indicates the number of rows in the output table.(*)

A list of output table entries. The number of entries is given by the value of upsOutputNumLines.(*)

An entry containing information applicable to a particular output line.(*)

The output line identifier.(*)

The present output voltage.(*)

The present output current.(*)

The present output true power.(*)

The percentage of the UPS power capacity presently being used on this output line, i.e., the greater of the percent load of true power capacity and the percent load of VA.(*)

The present output power factor. The returned value correspond to the cosf of the load. A positive value indicate an inductive load; a negative value indicate a capacitive load; value 1 indicate a resistive load. If the measure is not available due to a small load for a consistent calculation, the NA value is then returned.(*)

The present output peak current.(*)

In a parallel system ideally all the UPS are requested to contribute to the load with the same amount of current, i.e. with no current share. The current share occurs when an UPS exchanges some current with another UPS, so that this current component doesn't feed the load. The share part of the UPS current represents an undesired UPS loading, and therefore it should be minimized. If the share current is too high, the UPS results overloaded and in some conditions (i.e. very high load) the system could turn on bypass reducing dramatically the global system reliability. PMAD detects the amount of share currents in a parallel system, generating an alarm if this value is above a parameter-based threshold. Single UPS systems don't have this feature, NA will be provided.(*)

The present bypass frequency.(*)

The number of bypass lines utilized in this device. This entry indicates the number of rows in the bypass table.(*)

A list of bypass table entries. The number of entries is given by the value of upsBypassNumLines.(*)

An entry containing information applicable to a particular bypass input.(*)

The bypass line identifier.(*)

The present bypass voltage.(*)

The present bypass current.(*)

The present true power conveyed by the bypass.(*)