XUPS-MIB: View SNMP OID List / Download MIB

The UPS output power will turn off in a number of seconds equal to upsControlOutputOffTrapDelay.

The UPS output power will turn on in a number of seconds equal to upsControlOutputOnTrapDelay.

The UPS has no AC input power and is running on battery.

The UPS batteries are low. Tied to low battery alarm condition.

Input power has been restored after running on battery.

The battery has recovered from a low battery condition.

The ups has sensed an overload of greater than 106 percent. Tied to the 106% overload alarm.

Some component of the ups - rectifier, inverter, control panel has failed. Tied to alarms indicating failure.

The Battery Totally Discharged Alarm has occurred.

The ups inverter is unavailable due to an internal failure.

The ups has gone on bypass for some reason.

The ups bypass is unavailable

The ups output is switched off.

The ups input power is incorrect in voltage, frequency, or phase rotation.

One of the defined building alarms has occurred.

The ups shutdown imminent alarm has occurred.

The ups is returned to utility power running the inverter after either a transfer to bypass or a run on battery.

One of the UPS breakers or contactors has been opened.

An alarm not defined in the xups Well Known Alarms (eg, an alarm defined in RFC1628) has been added to the Alarm Table.

An alarm not defined in the xups Well Known Alarms has been removed from the Alarm Table.

The UPS Manufacturer Name (e.g. Powerware Corporation).

The UPS Model (e.g. Powerware Plus Model 18).

The firmware revision level(s) of the UPS microcontroller(s).

A binary code indicating who the UPS was manufactured or labeled for. 0 or 255 indicates Powerware itself.

Battery run time in seconds before UPS turns off due to low battery.

Battery voltage as reported by the UPS meters.

Battery Current as reported by the UPS metering. Current is positive when discharging, negative when recharging the battery.

Battery percent charge.

Gives the status of the Advanced Battery Management; batteryFloating(3) status means that the charger is temporarily charging the battery to its float voltage; batteryResting(4) is the state when the battery is fully charged and none of the other actions (charging/discharging/floating) is being done. Enumeration: 'batteryCharging': 1, 'batteryDischarging': 2, 'batteryResting': 4, 'batteryFloating': 3, 'unknown': 5.

The utility line frequency in tenths of Hz.

The number of times the Input was out of tolerance in voltage or frequency.

The Aggregate Object with number of entries equal to NumPhases and including the xupsInput group.

The input table entry containing the current, voltage, etc.

The number of the phase. Serves as index for input table.

The measured input voltage from the UPS meters in volts.

The measured input current from the UPS meters in amps.

The measured input real power in watts.

The present external source of input power. The enumeration none(2) indicates that there is no external source of power, for example, the UPS is On Battery (an internal source). The bypassFeed(4) can only be used when the Bypass source is known to be a separate utility feed than the primaryUtility(3). Enumeration: 'primaryUtility': 3, 'fuelcell': 8, 'none': 2, 'generator': 6, 'secondaryUtility': 5, 'flywheel': 7, 'other': 1, 'bypassFeed': 4.

The UPS output load in percent of rated capacity.

The measured UPS output frequency in tenths of Hz.

The number of metered output phases, serves as the table index.

The Aggregate Object with number of entries equal to NumPhases and including the xupsOutput group.

Output Table Entry containing voltage, current, etc.

The number {1..3} of the output phase.

The measured output voltage from the UPS metering in volts.

The measured UPS output current in amps.

The measured real output power in watts.

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, 'parallelCapacity': 8, 'reducer': 7, 'other': 1, 'highEfficiencyMode': 10, 'bypass': 4, 'parallelRedundant': 9, 'booster': 6.

The bypass frequency in tenths of Hz.

The number of lines in the UPS bypass table.

Entry in the XUPS bypass table.

The Bypass Phase, index for the table.

The measured UPS bypass voltage in volts.

The reading of the ambient temperature in the vicinity of the UPS or SNMP agent.

The Lower Limit of the ambient temperature; if xupsEnvAmbientTemp falls below this value, the xupsAmbientTempBad alarm will occur.

The Upper Limit of the ambient temperature; if xupsEnvAmbientTemp rises above this value, the xupsAmbientTempBad alarm will occur. This value should be greater than xupsEnvAmbientLowerLimit.

The reading of the ambient humidity in the vicinity of the UPS or SNMP agent.

The reading of a remote temperature sensor connected to the UPS or SNMP agent.

The reading of a remote humidity sensor connected to the UPS or SNMP agent.

The number of Contacts in the xupsContactSenseTable. This object indicates the number of rows in the xupsContactSenseTable.

A list of Contact Sensing table entries. The number of entries is given by the value of xupsEnvNumContacts.

An entry containing information applicable to a particular Contact input.

The Contact identifier; identical to the Contact Number.

The normal state for this contact. The 'other' state is the Active state for generating the xupstdContactActiveNotice trap. If anyChange(3) is selected, then this trap is sent any time the contact changes to either Open or Closed. No traps are sent if the Contact is set to notUsed(4). In many cases, the configuration for Contacts may be done by other means, so this object may be read-only. Enumeration: 'normallyOpen': 1, 'normallyClosed': 2, 'anyChange': 3, 'notUsed': 4.

The current state of the Contact input; the value is based on the open/closed input state and the setting for xupsContactType. When entering the openWithNotice(3) and closedWithNotice(4) states, no entries added to the xupsAlarmTable, but the xupstdContactActiveNotice trap is sent. Enumeration: 'closedWithNotice': 4, 'openWithNotice': 3, 'open': 1, 'closed': 2.

A label identifying the Contact. This object should be set by the administrator.

The Lower Limit of the remote temperature; if xupsEnvRemoteTemp falls below this value, the xupsRemoteTempBad alarm will occur.

The Upper Limit of the remote temperature; if xupsEnvRemoteTemp rises above this value, the xupsRemoteTempBad alarm will occur. This value should be greater than xupsEnvRemoteTempLowerLimit.

The Lower Limit of the remote humidity reading; if xupsEnvRemoteHumidity falls below this value, the xupsRemoteHumidityBad alarm will occur.

The Upper Limit of the remote humidity reading; if xupsEnvRemoteHumidity rises above this value, the xupsRemoteHumidityBad alarm will occur. This value should be greater than xupsEnvRemoteHumidityLowerLimit.

The current number of alarm conditions.

A unique identifier for an alarm condition.

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 the MIB-II variable sysUpTime when the alarm condition occurred.

The number of entries in the UPS event history queue.

A table of the UPS internal event history queue.

One of the entries in the UPS event history queue.

A unique number that reflects the order in which the event occurred. The oldest event in the queue will be number 1. Subsequent events will be numbered 2, 3, 4, etc.

The time and date that an event occurred as recorded in the UPS internal event queue. This string will reflect the time and date as set in the UPS itself and will not be referenced to sysUpTime. The format is MM/DD/YYYY:HH:MM:SS. Time is 24 hour standard.

Enumerated value that tells whether the event is an occurrence of an alarm condition or a clearing of an alarm condition. Enumeration: 'unknown': 3, 'cleared': 2, 'occurred': 1.

A description of the event stored in the UPS event queue. This description will be a sixteen bit integer value representing one of the defined alarms in the Powerware Binary Computer Mode communication specification; for example, a value of 0 represents the 'Inverter AC Over Voltage' alarm (byte 1, bit 0 in the BCM Alarm Map).

A text string describing each entry in the Event Log. The format of this text message is free (not fixed) for the operator to read; good contents would be a time & date stamp, the event type, and a description of the event.

Setting this variable to startTest initiates the battery test. All other set values are invalid. Enumeration: 'startTest': 1.

Reading this enumerated value gives an indication of the UPS Battery test status. Enumeration: 'scheduled': 7, 'unknown': 1, 'failed': 3, 'inhibited': 6, 'passed': 2, 'inProgress': 4, 'notSupported': 5.

Setting this value to other than zero will cause the UPS output to turn off after the number of seconds. Setting it to 0 will cause an attempt to abort a pending shutdown.

Setting this value to other than zero will cause the UPS output to turn on after the number of seconds. Setting it to 0 will cause an attempt to abort a pending startup.

When xupsControlOutputOffDelay reaches this value, a trap will be sent.

When xupsControlOutputOnDelay reaches this value, a xupsOutputOff trap will be sent.

Setting this value to other than zero will cause the UPS output to go to Bypass after the number of seconds. If the Bypass is unavailable, this may cause the UPS to not supply power to the load. Setting it to 0 will cause an attempt to abort a pending shutdown.

Setting this value will cause the UPS output to turn off after the set number of seconds, then restart (after a UPS-defined 'down time') when the utility is again available. Unlike xupsControlOutputOffDelay, which might or might not, this object always maps to the XCP 0x8A Load Dump & Restart command, so the desired shutdown and restart behavior is guaranteed to happen. Once set, this command cannot be aborted. This is the preferred Control object to use when performing an On Battery OS Shutdown.

The nominal UPS Output voltage per phase in volts.

The nominal UPS Input voltage per phase in volts.

The nominal UPS available real power output in watts.

The nominal output frequency in tenths of Hz.

Date and time information for the UPS. Setting this variable will initiate a set UPS date and time to this value. Reading this variable will return the UPS time and date. This value is not referenced to sysUpTime. It is simply the clock value from the UPS real time clock. Format is as follows: MM/DD/YYYY:HH:MM:SS.

The Lower limit for acceptable Output Voltage, per the UPS specifications.

The Upper limit for acceptable Output Voltage, per the UPS specifications.

The level of severity of traps which will be sent to the requesting host; individual trap receivers will have individual values for this variable. Values are: (1) none: no traps will be sent to this host; (2) critical: only traps for Critical alarm conditions will be sent to this host; (3) major: Critical and Major traps will be sent; (4) allTraps: all Traps will be sent to this host (Critical, Major, Minor, Informational). Enumeration: 'none': 1, 'critical': 2, 'major': 3, 'allTraps': 4.

The type of traps which will be sent to the requesting host; individual trap receivers will have individual values for this variable. The additional variables in types (3) and (4) are useful for determining which UPS is the source on multi-port network adapters, and for getting additional descriptive information. Types (1) through (4) are all SNMP version 1 trap PDUs. Values are: (1) stnd: Traps as defined in the Standard UPS MIB (RFC1628) and Generic (MIB II) traps as defined in RFC 1215. (2) xups: xupsTrapDefined Traps as defined in the PowerMIB and Generic (MIB II) traps as defined in RFC 1215. (3) stndPlus: same as stnd plus variables from the interface group and, where appropriate, xupsTrapMessage. (4) xupsPlus: xupsTrapPortN Traps (same as xups plus variables from the interface group) and, for authFail, xupsTrapMessage. Enumeration: 'xups': 2, 'stnd': 1, 'xupsPlus': 4, 'stndPlus': 3.

A descriptive message which may be sent with traps to further explain the reason for the trap.

The UPS output power will turn off in a number of seconds equal to upsControlOutputOffTrapDelay.

The UPS output power will turn on in a number of seconds equal to upsControlOutputOnTrapDelay.

The UPS has no AC input power and is running on battery.

The UPS batteries are low. Tied to low battery alarm condition.

Input power has been restored after running on battery.

The battery has recovered from a low battery condition.

The ups has sensed an overload of greater than 106 percent. Tied to the 106% overload alarm.

Some component of the ups - rectifier, inverter, control panel has failed. Tied to alarms indi- cating failure.

The Battery Totally Discharged Alarm has occurred.

The ups inverter is unavailable due to an internal failure.

The ups has gone on bypass for some reason.

The ups bypass is unavailable

The ups output is switched off.

The ups input power is incorrect in voltage, frequency, or phase rotation.

One of the defined building alarms has occurred.

The ups shutdown imminent alarm has occurred.

The ups is returned to utility power running the inverter after either a transfer to bypass or a run on battery.

One of the UPS breakers or contactors has been opened.

An alarm not defined in the xups Well Known Alarms (eg, an alarm defined in RFC1628) has been added to the Alarm Table.

An alarm not defined in the xups Well Known Alarms has been removed from the Alarm Table.

One or more batteries have been determined to require replacement.

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

The result of the last diagnostic test indicates a failure.

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

An xupsControlOutputOffDelay countdown is underway.

A test is in progress, as initiated and indicated by the Battery Test Group.

The ambient temperature, xupsEnvAmbientTemp, has fallen below the set lower limit, xupsEnvAmbientLowerLimit, or has risen above the set upper limit, xupsEnvAmbientUpperLimit.

The Contact indicated by xupsContactIndex is in its Active state. The following are the situations that generate this trap: For xupsContactType: and xupsContactState: normallyOpen(1) and closedWithNotice(4) normallyClosed(2) and openWithNotice(3) anyChange(3) and openWithNotice(3) or closedWithNotice(4)

The Contact indicated by xupsContactIndex has changed to its Inactive state.

A parallel UPS system is no longer operating in N+1 redundant mode; this may be due to module failure or removal, or due to overloading.

An internal temperature is out of tolerance.

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

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

The failure of one or more fuses has been detected.

A Relay, Contactor, or Breaker has failed.

One module in a parallel or composite system has failed.

The system is being powered by its Alternate Power Source, such as a Secondary utility feed (on a dual AC input UPS), generator, flywheel, or fuelcell.

On systems with a separate alternate power source (eg, dual AC inputs), that alternate power source is currently not available. This could be a problem if the primary power source (eg, utility) fails for a period of time longer than that for which the internal batteries can supply power.

Some Notice condition exists which is not covered by the other traps. This is like an xupstdInternalFailure, but at a lower severity level.

The remote temperature, xupsEnvRemoteTemp, has fallen below the set lower limit, xupsEnvRemoteTempLowerLimit, or has risen above the set upper limit, xupsEnvRemoteTempUpperLimit.

The remote temperature, xupsEnvRemoteHumidity, has fallen below the set lower limit, xupsEnvRemoteHumidityLowerLimit, or has risen above the set upper limit, xupsEnvRemoteHumidityUpperLimit.

The UPS output power will turn off in a number of seconds equal to upsControlOutputOffTrapDelay.

The UPS output power will turn on in a number of seconds equal to upsControlOutputOnTrapDelay.

The UPS has no AC input power and is running on battery.

The UPS batteries are low. Tied to low battery alarm condition.

Input power has been restored after running on battery.

The battery has recovered from a low battery condition.

The ups has sensed an overload of greater than 106 percent. Tied to the 106% overload alarm.

Some component of the ups - rectifier, inverter, control panel has failed. Tied to alarms indi- cating failure.

The Battery Totally Discharged Alarm has occurred.

The ups inverter is unavailable due to an internal failure.

The ups has gone on bypass for some reason.

The ups bypass is unavailable

The ups output is switched off.

The ups input power is incorrect in voltage, frequency, or phase rotation.

One of the defined building alarms has occurred.

The ups shutdown imminent alarm has occurred.

The ups is returned to utility power running the inverter after either a transfer to bypass or a run on battery.

One of the UPS breakers or contactors has been opened.

An alarm not defined in the xups Well Known Alarms (eg, an alarm defined in RFC1628) has been added to the Alarm Table.

An alarm not defined in the xups Well Known Alarms has been removed from the Alarm Table.

One or more batteries have been determined to require replacement.

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

The result of the last diagnostic test indicates a failure.

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

An xupsControlOutputOffDelay countdown is underway.

A test is in progress, as initiated and indicated by the Battery Test Group.

The ambient temperature, xupsEnvAmbientTemp, has fallen below the set lower limit, xupsEnvAmbientLowerLimit, or has risen above the set upper limit, xupsEnvAmbientUpperLimit.

A parallel UPS system is no longer operating in N+1 redundant mode; this may be due to module failure or removal, or due to overloading.

An internal temperature is out of tolerance.

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

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

The failure of one or more fuses has been detected.

A Relay, Contactor, or Breaker has failed.

One module in a parallel or composite system has failed.

The system is being powered by its Alternate Power Source, such as a Secondary utility feed (on a dual AC input UPS), generator, flywheel, or fuelcell.

On systems with a separate alternate power source (eg, dual AC inputs), that alternate power source is currently not available. This could be a problem if the primary power source (eg, utility) fails for a period of time longer than that for which the internal batteries can supply power.

Some Notice condition exists which is not covered by the other traps. This is like an xupstpInternalFailure, but at a lower severity level.

The remote temperature, xupsEnvRemoteTemp, has fallen below the set lower limit, xupsEnvRemoteTempLowerLimit, or has risen above the set upper limit, xupsEnvRemoteTempUpperLimit.

The remote temperature, xupsEnvRemoteHumidity, has fallen below the set lower limit, xupsEnvRemoteHumidityLowerLimit, or has risen above the set upper limit, xupsEnvRemoteHumidityUpperLimit.

The number of independently controllable Receptacles, as described in the xupsRecepTable.

The Aggregate Object with number of entries equal to NumReceptacles and including the xupsRecep group.

The Recep table entry, etc.

The number of the Receptacle. Serves as index for Receptacle table.

The Recep Status 1=On/Close, 2=Off/Open, 3=On w/Pending Off, 4=Off w/Pending ON, 5=Unknown. Enumeration: 'on': 1, 'pendingOff': 3, 'pendingOn': 4, 'off': 2, 'unknown': 5.

The Delay until the Receptacle is turned Off. Setting this value to other than -1 will cause the UPS output to turn off after the number of seconds (0 is immediately). Setting it to -1 will cause an attempt to abort a pending shutdown. When this object is set while the UPS is On Battery, it is not necessary to set xupsRecepOnDelaySecs, since the outlet will turn back on automatically when power is available again.

The Delay until the Receptacle is turned On. Setting this value to other than -1 will cause the UPS output to turn on after the number of seconds (0 is immediately). Setting it to -1 will cause an attempt to abort a pending restart.

The delay after going On Battery until the Receptacle is automatically turned Off. A value of -1 means that this Output should never be turned Off automatically, but must be turned Off only by command. Values from 0 to 30 are valid, but probably innappropriate. The AutoOffDelay can be used to prioritize loads in the event of a prolonged power outage; less critical loads will turn off earlier to extend battery time for the more critical loads. If the utility power is restored before the AutoOff delay counts down to 0 on an outlet, that outlet will not turn Off.

Seconds delay after the Outlet is signaled to turn On before the Output is Automatically turned ON. A value of -1 means that this Output should never be turned On automatically, but only when specifically commanded to do so. A value of 0 means that the Receptacle should come On immediately at power-up or for an On command.

Setting this value will cause the UPS output to turn off after the set number of seconds, then restart (after a UPS-defined 'down time') when the utility is again available. Unlike xupsRecepOffDelaySecs, which might or might not, this object always maps to the XCP 0x8A Load Dump & Restart command, so the desired shutdown and restart behavior is guaranteed to happen. Once set, this command cannot be aborted.

Value which denotes the type of UPS by its power topology. Values are the same as those described in the XCP Topology block's Overall Topology field.

ID Value which denotes the Powerware model of the UPS for software. Values are the same as those described in the XCP Configuration block's Machine Code field.

Identifies which unit and what type of data is being reported. A value of 0 means that this MIB information comes from the top-level system view (eg, manifold module or system bypass cabinet reporting total system output). Standalone units also use a value of 0, since they are the 'full system' view. A value of 1 or higher indicates the number of the module in the system which is reporting only its own data in the PowerMIB objects.

Value which denotes which Power Strategy is currently set for the UPS. The values are: highAlert(1) - The UPS shall optimize its operating state to maximize its power-protection levels. This mode will be held for at most 24 hours. standard(2) - Balanced, normal power protection strategy. UPS will not enter HE operating mode from this setting. enableHighEfficiency(3) - The UPS is enabled to enter HE operating mode to optimize its operating state to maximize its efficiency, when conditions change to permit it (as determined by the UPS). forceHighEfficiency(4) - If this value is permitted to be Set for this UPS, and if conditions permit, requires the UPS to enter High Efficiency mode now, without delay (for as long as utility conditions permit). After successfully set to forceHighEfficiency(4), xupsTopoPowerStrategy changes to value enableHighEfficiency(3). xupsOutputSource will indicate if the UPS status is actually operating in High Efficiency mode. Enumeration: 'enableHighEfficiency': 3, 'standard': 2, 'immediateHighEfficiency': 4, 'highAlert': 1.