Reference record for OID 1.3.6.1.4.1.53973.1.1.31.3.1.1

Parent

1.3.6.1.4.1.53973.1.1.31.3.1 (ups30Compliances)

Node code

Node name

ups30SubsetCompliance

Numeric OID

1.3.6.1.4.1.53973.1.1.31.3.1.1

URN notation

urn:oid:1.3.6.1.4.1.53973.1.1.31.3.1.1

ASN.1 notation

{1 3 6 1 4 1 53973 1 1 31 3 1 1}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsModule30(31) ups30Conformance(3) ups30Compliances(1) ups30SubsetCompliance(1)}

OID-IRI notation

/1/3/6/1/4/1/53973/1/1/31/3/1/1
/ISO/Identified-Organization/6/1/4/1/53973/1/1/31/3/1/1
/ISO/3/6/1/4/1/53973/1/1/31/3/1/1

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/identified-organization/dod/internet/private/enterprises/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/identified-organization/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/identified-organization/dod/internet/private/vendor-objects/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/org/dod/internet/private/enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/org/dod/internet/private/enterprises/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/org/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/org/dod/internet/private/vendor-objects/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-identified-organization/dod/internet/private/enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-identified-organization/dod/internet/private/enterprises/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-identified-organization/dod/internet/private/vendor-objects/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-organization/dod/internet/private/enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-organization/dod/internet/private/enterprises/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-organization/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance
/iso/iso-organization/dod/internet/private/vendor-objects/abb/ups/upsModular/upsModule30/ups30Conformance/ups30Compliances/ups30SubsetCompliance

Descriptions

ups30SubsetCompliance — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

The compliance statement for UPSs that only support the two-contact communication protocol.

Source records

ups30SubsetCompliance

Status in source: current.

Names: ups30SubsetCompliance

Technical details

{
  "smi_kind": "MODULE-COMPLIANCE",
  "definition": [
    "ups30SubsetCompliance",
    "MODULE-COMPLIANCE",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The compliance statement for UPSs that only support the two-contact communication protocol.\"",
    "MODULE",
    "MANDATORY-GROUPS",
    "{",
    "ups30SubsetIdentGroup",
    ",",
    "ups30SubsetBatteryGroup",
    ",",
    "ups30SubsetInputGroup",
    ",",
    "ups30SubsetOutputGroup",
    ",",
    "ups30SubsetAlarmGroup",
    ",",
    "ups30SubsetControlGroup",
    "}",
    "OBJECT",
    "ups30BatteryStatus",
    "SYNTAX",
    "INTEGER",
    "{",
    "batteryNormal",
    "(",
    "2",
    ")",
    ",",
    "batteryLow",
    "(",
    "3",
    ")",
    "}",
    "DESCRIPTION",
    "\"Support of the values unknown(1) and batteryDepleted(4) is not required.\"",
    "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, ups30AlarmInputBad, ups30AlarmUpsOutputOff, ups30AlarmUpsSystemOff, and ups30AlarmTestInProgress.\"",
    "OBJECT",
    "ups30OutputSource",
    "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",
    "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",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The compliance statement for UPSs that only support the two-contact communication protocol."
    ],
    null,
    [
      "ComplianceModules",
      [
        [
          null,
          [
            "ups30SubsetIdentGroup",
            "ups30SubsetBatteryGroup",
            "ups30SubsetInputGroup",
            "ups30SubsetOutputGroup",
            "ups30SubsetAlarmGroup",
            "ups30SubsetControlGroup"
          ]
        ]
      ]
    ]
  ]
}

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: ABBMODULARUPS-MIB

Vendor MIB copy from the LibreNMS archive.

Module: ABBMODULARUPS-MIB

Published definition

ups30SubsetCompliance MODULE-COMPLIANCE
       STATUS     current
       DESCRIPTION

               "The compliance statement for UPSs that only support
               the two-contact communication protocol."
       MODULE -- this module
           MANDATORY-GROUPS  { ups30SubsetIdentGroup,
                     ups30SubsetBatteryGroup, ups30SubsetInputGroup,
                     ups30SubsetOutputGroup, ups30SubsetAlarmGroup,
                     ups30SubsetControlGroup }

       OBJECT     ups30BatteryStatus
       SYNTAX     INTEGER {
           batteryNormal(2),
           batteryLow(3)
       }
       DESCRIPTION
               "Support of the values unknown(1) and
               batteryDepleted(4) is not required."

       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,
               ups30AlarmInputBad, ups30AlarmUpsOutputOff,
               ups30AlarmUpsSystemOff, and ups30AlarmTestInProgress."

       OBJECT     ups30OutputSource
       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     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 1 }

Module imports

{'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:

LibreNMS original distribution archiveFile: librenms/librenms/tar.gz/…; 80.2 MiB
Archive revision metadata: librenms/librenms (JSON)File: repos/librenms/librenms/commits/master; 36,945 bytes

Source location: ABBMODULARUPS-MIB::ups30SubsetCompliance.

Source version and references

Downloaded: 2026-10-24T02:14:13.121331+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.53973)

ABB Power Protection SA

Siblings (2)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.53973.1.1.31.3.1.2	ups30BasicCompliance	0	0
1.3.6.1.4.1.53973.1.1.31.3.1.3	ups30FullCompliance	0	0