Reference record for OID 1.3.6.1.4.1.53973.1.1.1.3.1.3

Parent

1.3.6.1.4.1.53973.1.1.1.3.1 (upsCompliances)

Node code

Node name

upsFullCompliance

Numeric OID

1.3.6.1.4.1.53973.1.1.1.3.1.3

URN notation

urn:oid:1.3.6.1.4.1.53973.1.1.1.3.1.3

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) abb(53973) ups(1) upsModular(1) upsSystem(1) upsConformance(3) upsCompliances(1) upsFullCompliance(3)}

OID-IRI notation

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

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/identified-organization/dod/internet/private/enterprises/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/identified-organization/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/identified-organization/dod/internet/private/vendor-objects/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/org/dod/internet/private/enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/org/dod/internet/private/enterprises/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/org/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/org/dod/internet/private/vendor-objects/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-identified-organization/dod/internet/private/enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-identified-organization/dod/internet/private/enterprises/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-identified-organization/dod/internet/private/vendor-objects/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-organization/dod/internet/private/enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-organization/dod/internet/private/enterprises/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-organization/dod/internet/private/ldap-enterprise/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance
/iso/iso-organization/dod/internet/private/vendor-objects/abb/ups/upsModular/upsSystem/upsConformance/upsCompliances/upsFullCompliance

Descriptions

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

The compliance statement for UPSs that support advanced full-featured functions.

Source records

upsFullCompliance

Status in source: current.

Names: upsFullCompliance

Technical details

{
  "smi_kind": "MODULE-COMPLIANCE",
  "definition": [
    "upsFullCompliance",
    "MODULE-COMPLIANCE",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The compliance statement for UPSs that support advanced full-featured functions.\"",
    "MODULE",
    "MANDATORY-GROUPS",
    "{",
    "upsFullIdentGroup",
    ",",
    "upsFullBatteryGroup",
    ",",
    "upsFullInputGroup",
    ",",
    "upsFullOutputGroup",
    ",",
    "upsFullAlarmGroup",
    ",",
    "upsFullTestGroup",
    ",",
    "upsFullControlGroup",
    "}",
    "OBJECT",
    "upsAlarmDescr",
    "DESCRIPTION",
    "\"Support of all `well known' alarm types is not required. The well known alarm types which must be supported are: upsAlarmBatteryBad, upsAlarmOnBattery, upsAlarmLowBattery, upsAlarmDepletedBattery, upsAlarmTempBad, upsAlarmInputBad, upsAlarmOnBypass, upsAlarmBypassBad, upsAlarmOutputOffAsRequested, upsAlarmUpsOffAsRequested, upsAlarmUpsOutputOff, upsAlarmUpsSystemOff, upsAlarmGeneralFault, upsAlarmDiagnosticTestFailed, upsAlarmCommunicationsLost, upsAlarmShutdownPending, and upsAlarmTestInProgress.\"",
    "OBJECT",
    "upsTestId",
    "DESCRIPTION",
    "\"Support of all `well known' test types is not required. The well known test types which must be supported are: upsTestNoTestsInitiated, upsTestGeneralSystemsTest, and upsTestQuickBatteryTest.\"",
    "OBJECT",
    "upsOutputSource",
    "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",
    "upsFullBypassGroup",
    "DESCRIPTION",
    "\"The upsFullBypassGroup is only required for UPSs that have a Bypass present.\"",
    "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",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The compliance statement for UPSs that support advanced full-featured functions."
    ],
    null,
    [
      "ComplianceModules",
      [
        [
          null,
          [
            "upsFullIdentGroup",
            "upsFullBatteryGroup",
            "upsFullInputGroup",
            "upsFullOutputGroup",
            "upsFullAlarmGroup",
            "upsFullTestGroup",
            "upsFullControlGroup"
          ]
        ]
      ]
    ]
  ]
}

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

upsFullCompliance MODULE-COMPLIANCE
       STATUS     current
       DESCRIPTION
               "The compliance statement for UPSs that support
               advanced full-featured functions."
       MODULE -- this module
           MANDATORY-GROUPS { upsFullIdentGroup, upsFullBatteryGroup,
                     upsFullInputGroup, upsFullOutputGroup,
                     upsFullAlarmGroup, upsFullTestGroup,
                     upsFullControlGroup }

       OBJECT     upsAlarmDescr
       DESCRIPTION
               "Support of all `well known' alarm types is not
               required.  The well known alarm types which must be
               supported are: upsAlarmBatteryBad, upsAlarmOnBattery,
               upsAlarmLowBattery, upsAlarmDepletedBattery,
               upsAlarmTempBad, upsAlarmInputBad, upsAlarmOnBypass,
               upsAlarmBypassBad, upsAlarmOutputOffAsRequested,
               upsAlarmUpsOffAsRequested, upsAlarmUpsOutputOff,
               upsAlarmUpsSystemOff, upsAlarmGeneralFault,
               upsAlarmDiagnosticTestFailed,
               upsAlarmCommunicationsLost, upsAlarmShutdownPending,
               and upsAlarmTestInProgress."

       OBJECT     upsTestId
       DESCRIPTION
               "Support of all `well known' test types is not
               required.  The well known test types which must be
               supported are: upsTestNoTestsInitiated,
               upsTestGeneralSystemsTest, and
               upsTestQuickBatteryTest."

       OBJECT     upsOutputSource
       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 upsFullBypassGroup
           DESCRIPTION
               "The upsFullBypassGroup is only required for UPSs that
               have a Bypass present."

       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 3 }

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::upsFullCompliance.

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.1.3.1.1	upsSubsetCompliance	0	0
1.3.6.1.4.1.53973.1.1.1.3.1.2	upsBasicCompliance	0	0