---
oid: "1.3.6.1.2.1.33.3.1.1"
short-description: "upsSubsetCompliance MODULE-COMPLIANCE"
last-modified: "2020-03-04"
parent-oid: "1.3.6.1.2.1.33.3.1"
---

## OID: `1.3.6.1.2.1.33.3.1.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) upsMIB(33) upsConformance(3) upsCompliances(1) upsSubsetCompliance(1)}
```

### Description

```asn1
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, upsSubsetConfigGroup}
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."
OBJECT upsAutoRestart
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required, i.e., compliant systems need not support more than one restart type."
OBJECT upsConfigInputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigInputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputVoltage
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
OBJECT upsConfigOutputFreq
MIN-ACCESS read-only
DESCRIPTION
"Read-write access is not required."
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 1628](https://www.rfc-editor.org/rfc/rfc1628.html) with [Errata 4831](https://www.rfc-editor.org/errata_search.php?rfc=1628) applied.

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.