SOCOMECUPS-MIB: View SNMP OID List / Download MIB

The UPS Model designation.

The UPS firmware version.

The UPS Net Vision software version.

The UPS serial no.

The present battery status Enumeration: 'unknown': 1, 'upsOff': 7, 'batteryDepleted': 4, 'batteryFailure': 6, 'batteryNormal': 2, 'batteryLow': 3, 'batteryDischarging': 5.

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. -1 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 in 0.1 Volt DC.

The ambient temperature at or near the UPS Battery casing.

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

The current input frequency to the UPS system in 0.1 HZ.

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 utility line voltage in 0.1 volts.

The magnitude of the present input current in 0.1 A.

The maximum utility line voltage in 0.1 VAC for last 1 minute.

The minimum utility line voltage in 0.1 VAC for last 1 minute.

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: 'onBypass': 5, 'standby': 6, 'unknown': 1, 'upsOff': 8, 'ecoMode': 4, 'normalMode': 9, 'onMaintenanceBypass': 7, 'onMains': 3, 'onInverter': 2.

The current output frequency of the UPS system in 0.1 of HZ.

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 output voltage of the UPS system in 0.1 volts.

The output current of the UPS system in 0.1 Amps.

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.

Output KVA.

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 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 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.

Extra description.

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-TYPE macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-TYPE.

Digital power supply fault.

Auxiliary mains out of tolerance.

Manual By-pass closed

Short Circuit on UPS output.

Battery charger failure.

Inverter Over-current.

Excessive Inverter Distorsion.

Precharge voltage out of tolerance.

Boost output voltage too low.

Boost output voltage too high.

Battery voltage too high.

Improper condition of use

Overload timeout blocking Inverter.

Microprocessor control system failure

Configuration data map corrupted.

Pll fault.

Input mains general alarm.

Rectifier general alarm.

Boost general alarm.

Inverter general alarm.

Bettery charger general alarm.

Output voltage over limit.

Output voltage under limit.

Bypass charger general alarm.

Stop for overload.

UPS imminent stop

Module 1 in parallel general alarm.

Module 2 in parallel general alarm.

Module 3 in parallel general alarm.

Module 4 in parallel general alarm.

Module 5 in parallel general alarm.

Module 6 in parallel general alarm.

External Alarm 1.

External Alarm 2.

External Alarm 3.

External Alarm 4.

E-Service General Alarm

Redundancy lost

Periodic service check up.

Automatic and manual transfer disabled

Automatic transfer disabled

Battery room alarm

Manual bypass alarm

Battery Discharged

Insufficient resources

Optional boards general alarm

Rectifier fault

Boost fault

Inverter fault

Parallel module fault

Gen-set general alarm

Gen-set fault

Emergency stop active

Battery circuit open

Fans failure

Phase rotation fault

A62.

A63.

The test named by an OBJECT IDENTIFIER which allows a standard mechanism for the initiation of test, 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. Tests in progress may be aborted by setting this 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 bee 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: try_again: get (upsTestSpinLock) while (upsTestResultsSummary == inProgress) { /* loop while a test is running for another manager */ short delay get (upsTestSpinLock) } lock_value = upsTestSpinLock /* no test in progress, start the test */ set (upsTestSpinLock = lock_value, upsTestId = requested_test) if (error_index == 1) { /* (upsTestSpinLock failed) */ /* if problem is not access control, then some other manager slipped in ahead of us */ goto try_again } if (error_index == 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 == lock_value + 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: 'notActive': 1, 'failed': 4, 'inProgress': 2, 'byPass': 3.

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 Control UPS status Enumeration: 'upsStandbyOff': 2, 'upsEcoMode': 3, 'upsCommandReset': 6, 'upsStandbyOn': 1, 'upsBuzzerOff': 7, 'upsOnInverter': 9, 'upsOnBypass': 8, 'upsNormalMode': 4, 'upsAlarmReset': 5.

This object set the delay time (in seconds) to turn UPS off after Net Vision broadcast shutdown request to connected clients

This object enable/disable UPS turn off function after shutdown process complete Enumeration: 'enable': 1, 'disable': 2.

Table which describes the parametes for shutdown process when shutdown event occurs

The shutdown event identification

Status of the corresponding shutdown Event. When set to disable(), shutdown process will not start when corresponding event occured. Enumeration: 'enable': 1, 'disable': 2.

The Delay after the occurance of the curresponding shutdown event that Net Vision should issue shutdown request to connected clients. For WeeklyScheduledShutdown and SpecialScheduledShutdown, this is the time before the configured Shutdowntime when Net Vision will start sending the warning message to the connected clients. The value is in units of minutes.

The delay after the occurance of the curresponding shutdown event that the Net Vision will start sending the warning message to the connected clients. The value is in units of seconds

The frequency of sending warning messages to the connected clients when the curresponding shutdown event occurs. The value is in units of seconds.

Shutdown daemon severity.

The table to schedule shutting down the ups by weekly.

The entries for each day.

The index of scheduled events.

The weekday on which the UPS should shut down. Enumeration: 'none': 8, 'monday': 2, 'tuesday': 3, 'friday': 6, 'wednesday': 4, 'thursday': 5, 'sunday': 1, 'saturday': 7.

The time that the process of shutting down the UPS will be initiated in hh:mm:ss format.

The weekday on which the UPS should restart Enumeration: 'none': 8, 'monday': 2, 'tuesday': 3, 'friday': 6, 'wednesday': 4, 'thursday': 5, 'sunday': 1, 'saturday': 7.

The time the UPS will restart in hh:mm:ss format.

The table to schedule shutting down the ups.

The entries for each day.

The index of scheduled events.

The date on which the UPS should shut down in dd/mm/yyyy format.

The time that the process of shutting down the UPS will be initiated in hh:mm:ss format

The date on which the UPS should restart in dd/mm/yyyy format

The time the UPS will restart in hh:mm:ss format.

The table to schedule enable/disable ups eco/mode by weekly.

The entries for each day.

The index of scheduled events.

The weekday on which the UPS Eco/Mode should enable. Enumeration: 'none': 8, 'monday': 2, 'tuesday': 3, 'friday': 6, 'wednesday': 4, 'thursday': 5, 'sunday': 1, 'saturday': 7.

The time that the UPS Eco/Mode will be enabled, in hh:mm:ss format.

The weekday on which the UPS Eco/Mode should disable Enumeration: 'none': 8, 'monday': 2, 'tuesday': 3, 'friday': 6, 'wednesday': 4, 'thursday': 5, 'sunday': 1, 'saturday': 7.

The time the UPS Eco/Mode will disabled, in hh:mm:ss format.

The magnitude of the nominal input voltage.

The nominal input frequency.

The magnitude of the nominal output voltage.

The nominal output frequency.

The devices powered by UPS and registered to Net Vision

The devices protected by Net Vision

The index of the device that is plugged into the UPS.

The ip address of the device.

The name/description of the device plugged into the UPS.

The that device registered to Net Vision

status

severity

The ip address that NMS can identify the managed device

The default gateway that allow device managed through routers

Internet address subnet mask

The date in agent, format is (dd/mm/yyyy)

The time in agent, format is (hh:mm:ss)

Enumeration: 'gmt0500mumbai': 51, 'gmt0000monrovia': 27, 'gmt1000hobart': 72, 'gmt0900darwin': 68, 'gmt0100azores': 25, 'gmt0300nairobi': 43, 'gmt0200jerusalem': 39, 'gmt0600jayawardenepura': 55, 'gmt0500ekaterinburg': 48, 'gmt1000hawaii': 4, 'gmt0100paris': 31, 'gmt1200kwajalein': 2, 'gmt0400kabul': 47, 'gmt0800tijuana': 6, 'gmt0300greenland': 23, 'gmt0400yerevan': 46, 'gmt1200fiji': 76, 'gmt0900alaska': 5, 'gmt0600saskatchewan': 13, 'gmt0700mountain': 9, 'gmt0500quito': 14, 'gmt0600dhaka': 54, 'gmt0300georgetown': 22, 'gmt1300alofa': 77, 'gmt0300maghdad': 40, 'gmt0400atime': 17, 'gmt1100magadan': 74, 'gmt0600ctime': 11, 'gmt1000guam': 71, 'gmt0200minsk': 34, 'gmt0300newfoundland': 20, 'gmt0600rangoon': 56, 'gmt0000london': 28, 'gmt0600novosibirsk': 53, 'gmt0200vilnius': 38, 'gmt0800irkutsk': 60, 'gmt0500tashkent': 49, 'gmt0100prague': 30, 'gmt0200atlantic': 24, 'gmt0900tokyo': 64, 'gmt0500calcutta': 50, 'gmt0800beijing': 59, 'gmt0100wcafrica': 33, 'gmt1000brisbane': 69, 'gmt0800singapore': 61, 'gmt0300tehran': 44, 'gmt0100cvi': 26, 'gmt0300volgograd': 42, 'gmt0100zagreb': 32, 'gmt0700krasnoyarsk': 58, 'gmt0500indiana': 16, 'gmt0700bangkok': 57, 'gmt1200dateLineWest': 1, 'gmt1000vladivostok': 73, 'gmt0700arizona': 7, 'gmt0900adelaide': 67, 'gmt1100samoa': 3, 'gmt0600camerica': 10, 'gmt0500etime': 15, 'gmt0900yakutsk': 66, 'gmt0400caracas': 18, 'gmt1200auckland': 75, 'gmt0800taipei': 63, 'gmt0500kathmand': 52, 'gmt0700chihuahua': 8, 'gmt0600guadalajara': 12, 'gmt0100vienna': 29, 'gmt0800perth': 62, 'gmt1000canberra': 70, 'gmt0200bucharest': 35, 'gmt0400muscat': 45, 'gmt0200cairo': 36, 'gmt0300riyadh': 41, 'gmt0200pretoria': 37, 'gmt0900seoul': 65, 'gmt0400santiago': 19, 'gmt0300brasilia': 21.

The frequency of the updation of the history log. The value is in seconds

The ups parameters are sampled at the rate governed by the mconfigHistroyLogFrequency. These sampled values are further conslidated over period of time which is determined by this object.

The frequency that proxy agent polls the connected UPS in JBUS protocol. (unit : second)

The serial port communication speed (2400/9600 allowed). Enumeration: 'br2400': 1, 'br19200': 3, 'br9600': 2.

Enable or disable DHCP-BootP capability Enumeration: 'disabled': 2, 'enabled': 1.

Enable or disable telnet access Enumeration: 'disabled': 2, 'enabled': 1.

Enable or disable network upgrade capability Enumeration: 'disabled': 2, 'enabled': 1.

Reset all parameters of Net Vision to default value Enumeration: 'reset': 1, 'nothing': 2.

Restart Net Vision Enumeration: 'nothing': 2, 'restart': 1.

Clear agent log data Enumeration: 'nothing': 2, 'clear': 1.

Clear event log data Enumeration: 'nothing': 2, 'clear': 1.

Clear extented history log data Enumeration: 'nothing': 2, 'clear': 1.

Clear history log data Enumeration: 'nothing': 2, 'clear': 1.

A list of managers to send traps to. The number of entries is given by the value of upsAgentNumTrapReceivers

The managers to send traps to.

The index to a trap receiver entry.

The IP address of the manager to send a trap to.

The community name to use in the trap when sent to the manager.

Description of trap receivers

A list of managers which can access Net Vision with private community string.

The managers.

The index to a access control entry.

The IP address of the manager to access Net Vision

The community name to use in the manager when access Net Vision

Access type, only read-Write access type can change parameter of Net Vision Enumeration: 'readWrite': 2, 'readOnly': 1, 'notAccess': 3.

The version of MIB spec.

This OID allows traps to be sent with an octet string argument that my not be defined in the. A get of this OID will return error or NULL string.

The measurement of EMD temperature, in 0.1 degree

The measurement of EMD humidity, in 0.1 degree

The UPS is operating on battery power. This trap is persistent and is resent at one minute intervals until the UPS either turns off or is no longer running on battery.

This trap is sent upon completion of a UPS diagnostic test.

This trap is sent each time an alarm is inserted into to the alarm table. It is sent on the insertion of all alarms except for upsAlarmOnBattery and upsAlarmTestInProgress.

This trap is sent each time an alarm is removed from the alarm table. It is sent on the removal of all alarms except for upsAlarmTestInProgress.

INFORMATION: The UPS status is normal.

SEVERE: UPS failed the last test of battery.

WARNING: The UPS has switched to battery backup power.

SEVERE: Battery is near to be discharged.

INFORMATION: Input power has been restored.

SEVERE: The UPS is near to switch off the output power.

WARNING: The UPS has been turned off by the management station.

SEVERE: The UPS has sensed a temperature greater than its limit.

SEVERE: The UPS has sensed a load greater than 100 percent of its rated capacity.

SEVERE: The UPS output is on mains.

SEVERE: Redoundancy is lost.

SEVERE: EMD Sensor detected low temperature.

SEVERE: EMD Sensor detected high temperature.

SEVERE: EMD Sensor detected low humidity.

SEVERE: EMD Sensor detected high humidity.

SEVERE: The input is active.

INFORMATION: The input is restored.

SEVERE: The input is active.

INFORMATION: The input is restored.