ups30BasicCompliance — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
The compliance statement for UPSs that support full-featured functions, such as control.
{1 3 6 1 4 1 53973 1 1 31 3 1 2}
The compliance statement for UPSs that support full-featured functions, such as control.
Status in source: current.
Names: ups30BasicCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"ups30BasicCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"The compliance statement for UPSs that support full-featured functions, such as control.\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"ups30BasicIdentGroup",
",",
"ups30BasicBatteryGroup",
",",
"ups30BasicInputGroup",
",",
"ups30BasicOutputGroup",
",",
"ups30BasicAlarmGroup",
",",
"ups30BasicTestGroup",
",",
"ups30BasicControlGroup",
"}",
"OBJECT",
"ups30AlarmDescr",
"DESCRIPTION",
"\"Support of all `well known' alarm types is not required. The well known alarm types which must be supported are: ups30AlarmOnBattery, ups30AlarmLowBattery, ups30AlarmDepletedBattery, ups30AlarmTempBad, ups30AlarmInputBad, ups30AlarmOutputOverload, ups30AlarmOnBypass, ups30AlarmBypassBad, ups30AlarmOutputOffAsRequested, ups30AlarmUpsOffAsRequested, ups30AlarmUpsOutputOff, ups30AlarmUpsSystemOff, ups30AlarmGeneralFault, ups30AlarmDiagnosticTestFailed, ups30AlarmCommunicationsLost, ups30AlarmShutdownPending, and ups30AlarmTestInProgress.\"",
"OBJECT",
"ups30TestId",
"DESCRIPTION",
"\"Support of all `well known' test types is not required. If no tests are supported, then the only well known test type which must be supported is ups30TestNoTestsInitiated.\"",
"OBJECT",
"ups30OutputSource",
"SYNTAX",
"INTEGER",
"{",
"normal",
"(",
"2",
")",
",",
"battery",
"(",
"4",
")",
"}",
"DESCRIPTION",
"\"Support of the values other(1), none(2), bypass(4), booster(6) and reducer(7) is not required.\"",
"GROUP",
"ups30BasicBypassGroup",
"DESCRIPTION",
"\"The ups30BasicBypassGroup is only required for UPSs that have a Bypass present.\"",
"OBJECT",
"ups30ShutdownType",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Read-write access is not required, i.e., compliant systems need not support more than one shutdown type.\"",
"::=",
"{",
"ups30Compliances",
"2",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The compliance statement for UPSs that support full-featured functions, such as control."
],
null,
[
"ComplianceModules",
[
[
null,
[
"ups30BasicIdentGroup",
"ups30BasicBatteryGroup",
"ups30BasicInputGroup",
"ups30BasicOutputGroup",
"ups30BasicAlarmGroup",
"ups30BasicTestGroup",
"ups30BasicControlGroup"
]
]
]
]
]
}Vendor MIB copy from the LibreNMS archive.
Module: ABBMODULARUPS-MIB
ups30BasicCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for UPSs that support
full-featured functions, such as control."
MODULE -- this module
MANDATORY-GROUPS { ups30BasicIdentGroup,
ups30BasicBatteryGroup, ups30BasicInputGroup,
ups30BasicOutputGroup, ups30BasicAlarmGroup,
ups30BasicTestGroup, ups30BasicControlGroup }
OBJECT ups30AlarmDescr
DESCRIPTION
"Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: ups30AlarmOnBattery, ups30AlarmLowBattery,
ups30AlarmDepletedBattery, ups30AlarmTempBad,
ups30AlarmInputBad, ups30AlarmOutputOverload,
ups30AlarmOnBypass, ups30AlarmBypassBad,
ups30AlarmOutputOffAsRequested,
ups30AlarmUpsOffAsRequested, ups30AlarmUpsOutputOff,
ups30AlarmUpsSystemOff, ups30AlarmGeneralFault,
ups30AlarmDiagnosticTestFailed,
ups30AlarmCommunicationsLost, ups30AlarmShutdownPending,
and ups30AlarmTestInProgress."
OBJECT ups30TestId
DESCRIPTION
"Support of all `well known' test types is not
required. If no tests are supported, then the only
well known test type which must be supported is
ups30TestNoTestsInitiated."
OBJECT ups30OutputSource
SYNTAX INTEGER {
normal(2),
battery(4)
}
DESCRIPTION
"Support of the values other(1), none(2), bypass(4),
booster(6) and reducer(7) is not required."
GROUP ups30BasicBypassGroup
DESCRIPTION
"The ups30BasicBypassGroup is only required for UPSs
that have a Bypass present."
OBJECT ups30ShutdownType
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
systems need not support more than one shutdown type."
::= { ups30Compliances 2 }{'SNMPv2-TC': ['DisplayString', 'TimeStamp', 'TimeInterval', 'TestAndIncr', 'AutonomousType', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'Counter32', 'Gauge32', 'Integer32', 'Unsigned32', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Downloaded: 2026-10-24T02:14:13.121331+00:00.
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.53973.1.1.31.3.1.1 | ups30SubsetCompliance | 0 | 0 | |
| 1.3.6.1.4.1.53973.1.1.31.3.1.3 | ups30FullCompliance | 0 | 0 |