| upsIdentManufacturer |
.1.3.6.1.2.1.33.1.1.1 |
|
The name of the UPS manufacturer.
|
| upsIdentModel |
.1.3.6.1.2.1.33.1.1.2 |
|
The UPS Model designation.
|
| upsIdentUPSSoftwareVersion |
.1.3.6.1.2.1.33.1.1.3 |
|
The UPS firmware/software version(s). This variable
may or may not have the same value as
upsIdentAgentSoftwareVersion in some implementations.
|
| upsIdentAgentSoftwareVersion |
.1.3.6.1.2.1.33.1.1.4 |
|
The UPS agent software version. This variable may or
may not have the same value as
upsIdentUPSSoftwareVersion in some implementations.
|
| upsIdentName |
.1.3.6.1.2.1.33.1.1.5 |
|
A string identifying the UPS. This object should be
set by the administrator.
|
| upsIdentAttachedDevices |
.1.3.6.1.2.1.33.1.1.6 |
|
A string identifying the devices attached to the
output(s) of the UPS. This object should be set by
the administrator.
|
| upsBatteryStatus |
.1.3.6.1.2.1.33.1.2.1 |
|
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).
|
| upsSecondsOnBattery |
.1.3.6.1.2.1.33.1.2.2 |
|
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.
|
| upsEstimatedMinutesRemaining |
.1.3.6.1.2.1.33.1.2.3 |
|
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.
|
| upsEstimatedChargeRemaining |
.1.3.6.1.2.1.33.1.2.4 |
|
An estimate of the battery charge remaining expressed
as a percent of full charge.
|
| upsBatteryVoltage |
.1.3.6.1.2.1.33.1.2.5 |
|
The magnitude of the present battery voltage.
|
| upsBatteryCurrent |
.1.3.6.1.2.1.33.1.2.6 |
|
The present battery current.
|
| upsBatteryTemperature |
.1.3.6.1.2.1.33.1.2.7 |
|
The ambient temperature at or near the UPS Battery
casing.
|
| upsInputLineBads |
.1.3.6.1.2.1.33.1.3.1 |
|
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.
|
| upsInputNumLines |
.1.3.6.1.2.1.33.1.3.2 |
|
The number of input lines utilized in this device.
This variable indicates the number of rows in the
input table.
|
| upsInputEntry |
.1.3.6.1.2.1.33.1.3.3.1 |
|
An entry containing information applicable to a
particular input line.
|
| upsOutputSource |
.1.3.6.1.2.1.33.1.4.1 |
|
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.
|
| upsOutputFrequency |
.1.3.6.1.2.1.33.1.4.2 |
|
The present output frequency.
|
| upsOutputNumLines |
.1.3.6.1.2.1.33.1.4.3 |
|
The number of output lines utilized in this device.
This variable indicates the number of rows in the
output table.
|
| upsOutputEntry |
.1.3.6.1.2.1.33.1.4.4.1 |
|
An entry containing information applicable to a
particular output line.
|
| upsBypassFrequency |
.1.3.6.1.2.1.33.1.5.1 |
|
The present bypass frequency.
|
| upsBypassNumLines |
.1.3.6.1.2.1.33.1.5.2 |
|
The number of bypass lines utilized in this device.
This entry indicates the number of rows in the bypass
table.
|
| upsBypassEntry |
.1.3.6.1.2.1.33.1.5.3.1 |
|
An entry containing information applicable to a
particular bypass input.
|
| upsAlarmsPresent |
.1.3.6.1.2.1.33.1.6.1 |
|
The present number of active alarm conditions.
|
| upsAlarmEntry |
.1.3.6.1.2.1.33.1.6.2.1 |
|
An entry containing information applicable to a
particular alarm.
|
| upsTestId |
.1.3.6.1.2.1.33.1.7.1 |
|
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.
|
| upsTestSpinLock |
.1.3.6.1.2.1.33.1.7.2 |
|
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.
|
| upsTestResultsSummary |
.1.3.6.1.2.1.33.1.7.3 |
|
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.
|
| upsTestResultsDetail |
.1.3.6.1.2.1.33.1.7.4 |
|
Additional information about upsTestResultsSummary.
If no additional information available, a zero length
string is returned.
|
| upsTestStartTime |
.1.3.6.1.2.1.33.1.7.5 |
|
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.
|
| upsTestElapsedTime |
.1.3.6.1.2.1.33.1.7.6 |
|
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.
|
| upsShutdownType |
.1.3.6.1.2.1.33.1.8.1 |
|
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.
|
| upsShutdownAfterDelay |
.1.3.6.1.2.1.33.1.8.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.
|
| upsStartupAfterDelay |
.1.3.6.1.2.1.33.1.8.3 |
|
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.
|
| upsRebootWithDuration |
.1.3.6.1.2.1.33.1.8.4 |
|
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.
|
| upsAutoRestart |
.1.3.6.1.2.1.33.1.8.5 |
|
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.
|
| upsConfigInputVoltage |
.1.3.6.1.2.1.33.1.9.1 |
|
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.
|
| upsConfigInputFreq |
.1.3.6.1.2.1.33.1.9.2 |
|
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.
|
| upsConfigOutputVoltage |
.1.3.6.1.2.1.33.1.9.3 |
|
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.
|
| upsConfigOutputFreq |
.1.3.6.1.2.1.33.1.9.4 |
|
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.
|
| upsConfigOutputVA |
.1.3.6.1.2.1.33.1.9.5 |
|
The magnitude of the nominal Volt-Amp rating.
|
| upsConfigOutputPower |
.1.3.6.1.2.1.33.1.9.6 |
|
The magnitude of the nominal true power rating.
|
| upsConfigLowBattTime |
.1.3.6.1.2.1.33.1.9.7 |
|
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.
|
| upsConfigAudibleStatus |
.1.3.6.1.2.1.33.1.9.8 |
|
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.
|
| upsConfigLowVoltageTransferPoint |
.1.3.6.1.2.1.33.1.9.9 |
|
The minimum input line voltage allowed before the UPS
system transfers to battery backup.
|
| upsConfigHighVoltageTransferPoint |
.1.3.6.1.2.1.33.1.9.10 |
|
The maximum line voltage allowed before the UPS
system transfers to battery backup.
|
| upsMIB |
.1.3.6.1.2.1.33 |
|
The MIB module to describe Uninterruptible Power
Supplies.
|
| upsObjects |
.1.3.6.1.2.1.33.1 |
| upsIdent |
.1.3.6.1.2.1.33.1.1 |
| upsBattery |
.1.3.6.1.2.1.33.1.2 |
| upsInput |
.1.3.6.1.2.1.33.1.3 |
| upsOutput |
.1.3.6.1.2.1.33.1.4 |
| upsBypass |
.1.3.6.1.2.1.33.1.5 |
| upsAlarm |
.1.3.6.1.2.1.33.1.6 |
| upsWellKnownAlarms |
.1.3.6.1.2.1.33.1.6.3 |
| upsAlarmBatteryBad |
.1.3.6.1.2.1.33.1.6.3.1 |
|
One or more batteries have been determined to require
replacement.
|
| upsAlarmOnBattery |
.1.3.6.1.2.1.33.1.6.3.2 |
|
The UPS is drawing power from the batteries.
|
| upsAlarmLowBattery |
.1.3.6.1.2.1.33.1.6.3.3 |
|
The remaining battery run-time is less than or equal
to upsConfigLowBattTime.
|
| upsAlarmDepletedBattery |
.1.3.6.1.2.1.33.1.6.3.4 |
|
The UPS will be unable to sustain the present load
when and if the utility power is lost.
|
| upsAlarmTempBad |
.1.3.6.1.2.1.33.1.6.3.5 |
|
A temperature is out of tolerance.
|
| upsAlarmInputBad |
.1.3.6.1.2.1.33.1.6.3.6 |
|
An input condition is out of tolerance.
|
| upsAlarmOutputBad |
.1.3.6.1.2.1.33.1.6.3.7 |
|
An output condition (other than OutputOverload) is
out of tolerance.
|
| upsAlarmOutputOverload |
.1.3.6.1.2.1.33.1.6.3.8 |
|
The output load exceeds the UPS output capacity.
|
| upsAlarmOnBypass |
.1.3.6.1.2.1.33.1.6.3.9 |
|
The Bypass is presently engaged on the UPS.
|
| upsAlarmBypassBad |
.1.3.6.1.2.1.33.1.6.3.10 |
|
The Bypass is out of tolerance.
|
| upsAlarmOutputOffAsRequested |
.1.3.6.1.2.1.33.1.6.3.11 |
|
The UPS has shutdown as requested, i.e., the output
is off.
|
| upsAlarmUpsOffAsRequested |
.1.3.6.1.2.1.33.1.6.3.12 |
|
The entire UPS has shutdown as commanded.
|
| upsAlarmChargerFailed |
.1.3.6.1.2.1.33.1.6.3.13 |
|
An uncorrected problem has been detected within the
UPS charger subsystem.
|
| upsAlarmUpsOutputOff |
.1.3.6.1.2.1.33.1.6.3.14 |
|
The output of the UPS is in the off state.
|
| upsAlarmUpsSystemOff |
.1.3.6.1.2.1.33.1.6.3.15 |
|
The UPS system is in the off state.
|
| upsAlarmFanFailure |
.1.3.6.1.2.1.33.1.6.3.16 |
|
The failure of one or more fans in the UPS has been
detected.
|
| upsAlarmFuseFailure |
.1.3.6.1.2.1.33.1.6.3.17 |
|
The failure of one or more fuses has been detected.
|
| upsAlarmGeneralFault |
.1.3.6.1.2.1.33.1.6.3.18 |
|
A general fault in the UPS has been detected.
|
| upsAlarmDiagnosticTestFailed |
.1.3.6.1.2.1.33.1.6.3.19 |
|
The result of the last diagnostic test indicates a
failure.
|
| upsAlarmCommunicationsLost |
.1.3.6.1.2.1.33.1.6.3.20 |
|
A problem has been encountered in the communications
between the agent and the UPS.
|
| upsAlarmAwaitingPower |
.1.3.6.1.2.1.33.1.6.3.21 |
|
The UPS output is off and the UPS is awaiting the
return of input power.
|
| upsAlarmShutdownPending |
.1.3.6.1.2.1.33.1.6.3.22 |
|
A upsShutdownAfterDelay countdown is underway.
|
| upsAlarmShutdownImminent |
.1.3.6.1.2.1.33.1.6.3.23 |
|
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.
|
| upsAlarmTestInProgress |
.1.3.6.1.2.1.33.1.6.3.24 |
|
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.
|
| upsTest |
.1.3.6.1.2.1.33.1.7 |
| upsWellKnownTests |
.1.3.6.1.2.1.33.1.7.7 |
| upsTestNoTestsInitiated |
.1.3.6.1.2.1.33.1.7.7.1 |
|
No tests have been initiated and no test is in
progress.
|
| upsTestAbortTestInProgress |
.1.3.6.1.2.1.33.1.7.7.2 |
|
The test in progress is to be aborted / the test in
progress was aborted.
|
| upsTestGeneralSystemsTest |
.1.3.6.1.2.1.33.1.7.7.3 |
|
The manufacturer's standard test of UPS device
systems.
|
| upsTestQuickBatteryTest |
.1.3.6.1.2.1.33.1.7.7.4 |
|
A test that is sufficient to determine if the battery
needs replacement.
|
| upsTestDeepBatteryCalibration |
.1.3.6.1.2.1.33.1.7.7.5 |
|
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.
|
| upsControl |
.1.3.6.1.2.1.33.1.8 |
| upsConfig |
.1.3.6.1.2.1.33.1.9 |
| upsTraps |
.1.3.6.1.2.1.33.2 |
| upsConformance |
.1.3.6.1.2.1.33.3 |
| upsCompliances |
.1.3.6.1.2.1.33.3.1 |
| upsGroups |
.1.3.6.1.2.1.33.3.2 |
| upsSubsetGroups |
.1.3.6.1.2.1.33.3.2.1 |
| upsBasicGroups |
.1.3.6.1.2.1.33.3.2.2 |
| upsFullGroups |
.1.3.6.1.2.1.33.3.2.3 |
| upsSubsetIdentGroup |
.1.3.6.1.2.1.33.3.2.1.1 |
|
The upsSubsetIdentGroup defines objects which are
common across all UPSs which meet subset compliance.
Most devices which conform to the upsSubsetIdentGroup
will provide access to these objects via a proxy
agent. If the proxy agent is compatible with multiple
UPS types, configuration of the proxy agent will
require specifying some of these values, either
individually, or as a group (perhaps through a table
lookup mechanism based on the UPS model number).
|
| upsSubsetBatteryGroup |
.1.3.6.1.2.1.33.3.2.1.2 |
|
The upsSubsetBatteryGroup defines the objects that
are common to battery groups of two-contact UPSs.
|
| upsSubsetInputGroup |
.1.3.6.1.2.1.33.3.2.1.3 |
|
The upsSubsetInputGroup defines the objects that are
common to the Input groups of two-contact UPSs.
|
| upsSubsetOutputGroup |
.1.3.6.1.2.1.33.3.2.1.4 |
|
The upsSubsetOutputGroup defines the objects that are
common to the Output groups of two-contact UPSs.
|
| upsSubsetAlarmGroup |
.1.3.6.1.2.1.33.3.2.1.6 |
|
The upsSubsetAlarmGroup defines the objects that are
common to the Alarm groups of two-contact UPSs.
|
| upsSubsetControlGroup |
.1.3.6.1.2.1.33.3.2.1.8 |
|
The upsSubsetControlGroup defines the objects that
are common to the Control groups of two-contact UPSs.
|
| upsSubsetConfigGroup |
.1.3.6.1.2.1.33.3.2.1.9 |
|
The upsSubsetConfigGroup defines the objects that are
common to the Config groups of two-contact UPSs.
|
| upsBasicIdentGroup |
.1.3.6.1.2.1.33.3.2.2.1 |
|
The upsBasicIdentGroup defines objects which are
common to the Ident group of compliant UPSs which
support basic functions.
|
| upsBasicBatteryGroup |
.1.3.6.1.2.1.33.3.2.2.2 |
|
The upsBasicBatteryGroup defines the objects that are
common to the battery groups of compliant UPSs which
support basic functions.
|
| upsBasicInputGroup |
.1.3.6.1.2.1.33.3.2.2.3 |
|
The upsBasicInputGroup defines the objects that are
common to the Input groups of compliant UPSs which
support basic functions.
|
| upsBasicOutputGroup |
.1.3.6.1.2.1.33.3.2.2.4 |
|
The upsBasicOutputGroup defines the objects that are
common to the Output groups of compliant UPSs which
support basic functions.
|
| upsBasicAlarmGroup |
.1.3.6.1.2.1.33.3.2.2.6 |
|
The upsBasicAlarmGroup defines the objects that are
common to the Alarm groups of compliant UPSs which
support basic functions.
|
| upsBasicTestGroup |
.1.3.6.1.2.1.33.3.2.2.7 |
|
The upsBasicTestGroup defines the objects that are
common to the Test groups of compliant UPSs which
support basic functions.
|
| upsBasicControlGroup |
.1.3.6.1.2.1.33.3.2.2.8 |
|
The upsBasicControlGroup defines the objects that are
common to the Control groups of compliant UPSs which
support basic functions.
|
| upsBasicConfigGroup |
.1.3.6.1.2.1.33.3.2.2.9 |
|
The upsBasicConfigGroup defines the objects that are
common to the Config groups of UPSs which support
basic functions.
|
| upsBasicBypassGroup |
.1.3.6.1.2.1.33.3.2.2.5 |
|
The upsBasicBypassGroup defines the objects that are
common to the Bypass groups of compliant UPSs which
support basic functions.
|
| upsFullIdentGroup |
.1.3.6.1.2.1.33.3.2.3.1 |
|
The upsFullIdentGroup defines objects which are
common to the Ident group of fully compliant UPSs.
|
| upsFullBatteryGroup |
.1.3.6.1.2.1.33.3.2.3.2 |
|
The upsFullBatteryGroup defines the objects that are
common to the battery groups of fully compliant UPSs.
|
| upsFullInputGroup |
.1.3.6.1.2.1.33.3.2.3.3 |
|
The upsFullInputGroup defines the objects that are
common to the Input groups of fully compliant UPSs.
|
| upsFullOutputGroup |
.1.3.6.1.2.1.33.3.2.3.4 |
|
The upsFullOutputGroup defines the objects that are
common to the Output groups of fully compliant UPSs.
|
| upsFullAlarmGroup |
.1.3.6.1.2.1.33.3.2.3.6 |
|
The upsFullAlarmGroup defines the objects that are
common to the Alarm groups of fully compliant UPSs.
|
| upsFullTestGroup |
.1.3.6.1.2.1.33.3.2.3.7 |
|
The upsFullTestGroup defines the objects that are
common to the Test groups of fully compliant UPSs.
|
| upsFullControlGroup |
.1.3.6.1.2.1.33.3.2.3.8 |
|
The upsFullControlGroup defines the objects that are
common to the Control groups of fully compliant UPSs.
|
| upsFullConfigGroup |
.1.3.6.1.2.1.33.3.2.3.9 |
|
The upsFullConfigGroup defines the objects that are
common to the Config groups of fully compliant UPSs.
|
| upsFullBypassGroup |
.1.3.6.1.2.1.33.3.2.3.5 |
|
The upsFullBypassGroup defines the objects that are
common to the Bypass groups of fully compliant UPSs.
|
