upsSubsetCompliance — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
The compliance statement for UPSs that only support the two-contact communication protocol.
{1 3 6 1 4 1 53973 1 1 1 3 1 1}
The compliance statement for UPSs that only support the two-contact communication protocol.
Status in source: current.
Names: upsSubsetCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"upsSubsetCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"The compliance statement for UPSs that only support the two-contact communication protocol.\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"upsSubsetIdentGroup",
",",
"upsSubsetBatteryGroup",
",",
"upsSubsetInputGroup",
",",
"upsSubsetOutputGroup",
",",
"upsSubsetAlarmGroup",
",",
"upsSubsetControlGroup",
"}",
"OBJECT",
"upsBatteryStatus",
"SYNTAX",
"INTEGER",
"{",
"batteryNormal",
"(",
"2",
")",
",",
"batteryLow",
"(",
"3",
")",
"}",
"DESCRIPTION",
"\"Support of the values unknown(1) and batteryDepleted(4) is not required.\"",
"OBJECT",
"upsAlarmDescr",
"DESCRIPTION",
"\"Support of all `well known' alarm types is not required. The well known alarm types which must be supported are: upsAlarmOnBattery, upsAlarmLowBattery, upsAlarmInputBad, upsAlarmUpsOutputOff, upsAlarmUpsSystemOff, and upsAlarmTestInProgress.\"",
"OBJECT",
"upsOutputSource",
"SYNTAX",
"INTEGER",
"{",
"normal",
"(",
"3",
")",
",",
"battery",
"(",
"5",
")",
"}",
"DESCRIPTION",
"\"Support of the values other(1), none(2), bypass(4), booster(6) and reducer(7) is not required.\"",
"OBJECT",
"upsShutdownType",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Read-write access is not required, i.e., compliant systems need not support more than one shutdown type.\"",
"::=",
"{",
"upsCompliances",
"1",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The compliance statement for UPSs that only support the two-contact communication protocol."
],
null,
[
"ComplianceModules",
[
[
null,
[
"upsSubsetIdentGroup",
"upsSubsetBatteryGroup",
"upsSubsetInputGroup",
"upsSubsetOutputGroup",
"upsSubsetAlarmGroup",
"upsSubsetControlGroup"
]
]
]
]
]
}Vendor MIB copy from the LibreNMS archive.
Module: ABBMODULARUPS-MIB
upsSubsetCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for UPSs that only support
the two-contact communication protocol."
MODULE -- this module
MANDATORY-GROUPS { upsSubsetIdentGroup,
upsSubsetBatteryGroup, upsSubsetInputGroup,
upsSubsetOutputGroup, upsSubsetAlarmGroup,
upsSubsetControlGroup }
OBJECT upsBatteryStatus
SYNTAX INTEGER {
batteryNormal(2),
batteryLow(3)
}
DESCRIPTION
"Support of the values unknown(1) and
batteryDepleted(4) is not required."
OBJECT upsAlarmDescr
DESCRIPTION
"Support of all `well known' alarm types is not
required. The well known alarm types which must be
supported are: upsAlarmOnBattery, upsAlarmLowBattery,
upsAlarmInputBad, upsAlarmUpsOutputOff,
upsAlarmUpsSystemOff, and upsAlarmTestInProgress."
OBJECT upsOutputSource
SYNTAX INTEGER {
normal(3),
battery(5)
}
DESCRIPTION
"Support of the values other(1), none(2), bypass(4),
booster(6) and reducer(7) is not required."
OBJECT upsShutdownType
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant
systems need not support more than one shutdown type."
::= { upsCompliances 1 }{'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.1.3.1.2 | upsBasicCompliance | 0 | 0 | |
| 1.3.6.1.4.1.53973.1.1.1.3.1.3 | upsFullCompliance | 0 | 0 |