Reference record for OID 1.3.6.1.4.1.253.8.53.17.2.1.7

Parent
1.3.6.1.4.1.253.8.53.17.2.1 (xcmHrDevAlertEntry)
Node code
7
Node name
xcmHrDevAlertDescription
Numeric OID
1.3.6.1.4.1.253.8.53.17.2.1.7
URN notation
urn:oid:1.3.6.1.4.1.253.8.53.17.2.1.7
ASN.1 notation

{1 3 6 1 4 1 253 8 53 17 2 1 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) xerox(253) xeroxCommonMIB(8) xcmHrMIB(53) xcmHrDevAlert(17) xcmHrDevAlertTable(2) xcmHrDevAlertEntry(1) xcmHrDevAlertDescription(7)}
OID-IRI notation
  • /1/3/6/1/4/1/253/8/53/17/2/1/7
  • /ISO/Identified-Organization/6/1/4/1/253/8/53/17/2/1/7
  • /ISO/3/6/1/4/1/253/8/53/17/2/1/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/identified-organization/dod/internet/private/enterprises/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/identified-organization/dod/internet/private/vendor-objects/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/org/dod/internet/private/enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/org/dod/internet/private/enterprises/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/org/dod/internet/private/ldap-enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/org/dod/internet/private/vendor-objects/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-identified-organization/dod/internet/private/enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-identified-organization/dod/internet/private/enterprises/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-organization/dod/internet/private/enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-organization/dod/internet/private/enterprises/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription
  • /iso/iso-organization/dod/internet/private/vendor-objects/xerox/xeroxCommonMIB/xcmHrMIB/xcmHrDevAlert/xcmHrDevAlertTable/xcmHrDevAlertEntry/xcmHrDevAlertDescription

Descriptions

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

Human-readable alert description for the device alert which is recorded in this conceptual row in the 'xcmHrDevAlertTable'. Usage: This is a human-readable string, not intended for machine parsing. Management stations SHOULD obtain the alert-specific fault code and severity level from the 'xcmHrDevAlertCodeString' and 'xcmHrDevAlertSeverityLevel' and the current status from 'hrDeviceStatus' objects rather than trying to interpret this string. Implementators are strongly encouraged to include in this description: - a description of the problem, - a description of the corrective action or a statement that no corrective action is required, - a description of the impact on device operations. Implementors SHOULD NOT include in this description a statement of the current operating state of the device, since the device state may be changed by some other event unrelated to this alert, making any such statement invalid. A statement such as 'Device operation may continue' or 'This problem must be corrected before the device can resume operation' is acceptable. Usage: Conforming implementations SHALL provide BOTH detailed 'xcmHrDevAlertDescription' AND terse 'xcmHrDevAlertTitle' descriptions for each critical alert and for each alert which requires human intervention. Implementations MAY provide the same text for both strings. Usage: Implementations SHALL provide localized translations of this string via the 'xcmGenMessageTextTable.' Usage: For devices of type 'hrDevicePrinter', this SHOULD be the same description provided in 'prtAlertDescription' in the IETF Printer MIB alert table. Implementations MAY choose to make these descriptions different in order to differentiate between IETF-only and XCMI-aware management applications.

Source records

xcmHrDevAlertDescription

Status in source: current.

Names: xcmHrDevAlertDescription

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "xcmHrDevAlertDescription",
    "OBJECT-TYPE",
    "SYNTAX",
    "XcmFixedLocaleDisplayString",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Human-readable alert description for the device alert which is recorded in this conceptual row in the 'xcmHrDevAlertTable'. Usage: This is a human-readable string, not intended for machine parsing. Management stations SHOULD obtain the alert-specific fault code and severity level from the 'xcmHrDevAlertCodeString' and 'xcmHrDevAlertSeverityLevel' and the current status from 'hrDeviceStatus' objects rather than trying to interpret this string. Implementators are strongly encouraged to include in this description: - a description of the problem, - a description of the corrective action or a statement that no corrective action is required, - a description of the impact on device operations. Implementors SHOULD NOT include in this description a statement of the current operating state of the device, since the device state may be changed by some other event unrelated to this alert, making any such statement invalid. A statement such as 'Device operation may continue' or 'This problem must be corrected before the device can resume operation' is acceptable. Usage: Conforming implementations SHALL provide BOTH detailed 'xcmHrDevAlertDescription' AND terse 'xcmHrDevAlertTitle' descriptions for each critical alert and for each alert which requires human intervention. Implementations MAY provide the same text for both strings. Usage: Implementations SHALL provide localized translations of this string via the 'xcmGenMessageTextTable.' Usage: For devices of type 'hrDevicePrinter', this SHOULD be the same description provided in 'prtAlertDescription' in the IETF Printer MIB alert table. Implementations MAY choose to make these descriptions different in order to differentiate between IETF-only and XCMI-aware management applications.\"",
    "REFERENCE",
    "\"See: 'prtAlertDescription' in the Printer MIB.\"",
    "DEFVAL",
    "{",
    "'",
    "'",
    "H",
    "}",
    "::=",
    "{",
    "xcmHrDevAlertEntry",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "XcmFixedLocaleDisplayString",
      [
        "octetStringSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Human-readable alert description for the device alert which is recorded in this conceptual row in the 'xcmHrDevAlertTable'. Usage: This is a human-readable string, not intended for machine parsing. Management stations SHOULD obtain the alert-specific fault code and severity level from the 'xcmHrDevAlertCodeString' and 'xcmHrDevAlertSeverityLevel' and the current status from 'hrDeviceStatus' objects rather than trying to interpret this string. Implementators are strongly encouraged to include in this description: - a description of the problem, - a description of the corrective action or a statement that no corrective action is required, - a description of the impact on device operations. Implementors SHOULD NOT include in this description a statement of the current operating state of the device, since the device state may be changed by some other event unrelated to this alert, making any such statement invalid. A statement such as 'Device operation may continue' or 'This problem must be corrected before the device can resume operation' is acceptable. Usage: Conforming implementations SHALL provide BOTH detailed 'xcmHrDevAlertDescription' AND terse 'xcmHrDevAlertTitle' descriptions for each critical alert and for each alert which requires human intervention. Implementations MAY provide the same text for both strings. Usage: Implementations SHALL provide localized translations of this string via the 'xcmGenMessageTextTable.' Usage: For devices of type 'hrDevicePrinter', this SHOULD be the same description provided in 'prtAlertDescription' in the IETF Printer MIB alert table. Implementations MAY choose to make these descriptions different in order to differentiate between IETF-only and XCMI-aware management applications."
    ],
    [
      "REFERENCE",
      "See: 'prtAlertDescription' in the Printer MIB."
    ],
    null,
    null,
    [
      "DEFVAL",
      "''H"
    ]
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: XEROX-HOST-RESOURCES-EXT-MIB

    Published definition
    xcmHrDevAlertDescription OBJECT-TYPE
        SYNTAX      XcmFixedLocaleDisplayString (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
            "Human-readable alert description for the device alert which
            is recorded in this conceptual row in the 'xcmHrDevAlertTable'.
    
            Usage:  This is a human-readable string, not intended for
            machine parsing.  Management stations SHOULD obtain the
            alert-specific fault code and severity level from the
            'xcmHrDevAlertCodeString' and 'xcmHrDevAlertSeverityLevel' and 
    
    
            the current status from 'hrDeviceStatus' objects rather than 
            trying to interpret this string.
    
            Implementators are strongly encouraged to include in this       
            description:
                - a description of the problem,
                - a description of the corrective action or a statement
                  that no corrective action is required,
                - a description of the impact on device operations.
    
            Implementors SHOULD NOT include in this description a
            statement of the current operating state of the device,
            since the device state may be changed by some other event
            unrelated to this alert, making any such statement invalid.
            A statement such as 'Device operation may continue' or 'This
            problem must be corrected before the device can resume
            operation' is acceptable.
    
            Usage:  Conforming implementations SHALL provide BOTH
            detailed 'xcmHrDevAlertDescription' AND terse
            'xcmHrDevAlertTitle' descriptions for each critical
            alert and for each alert which requires human intervention.
            Implementations MAY provide the same text for both strings.
    
            Usage:  Implementations SHALL provide localized translations
            of this string via the 'xcmGenMessageTextTable.'
    
            Usage:  For devices of type 'hrDevicePrinter', this SHOULD
            be the same description provided in 'prtAlertDescription' in
            the IETF Printer MIB alert table.  Implementations MAY choose
            to make these descriptions different in order to differentiate
            between IETF-only and XCMI-aware management applications."
        REFERENCE
            "See:   'prtAlertDescription' in the Printer MIB."
        DEFVAL      { ''H }                 -- no alert description
        ::= { xcmHrDevAlertEntry 7 }
    Module imports
    {'SNMPv2-TC': ['DateAndTime', 'RowStatus', 'TruthValue', 'AutonomousType'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'Counter32', 'Integer32'], 'Printer-MIB': ['PresentOnOff'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'XEROX-COMMON-MIB': ['xeroxCommonMIB'], 'XEROX-GENERAL-TC': ['Ordinal32', 'Cardinal32', 'XcmFixedLocaleDisplayString', 'XcmGenNotifySeverityFilter', 'XcmGenNotifyTrainingFilter', 'XcmGenSNMPv2ErrorStatus', 'zeroDotZero'], 'HOST-RESOURCES-MIB': ['ProductID', 'hrDeviceIndex', 'hrDeviceStatus', 'hrSWRunIndex', 'hrSWInstalledIndex', 'hrStorageIndex'], 'XEROX-HOST-RESOURCES-EXT-TC': ['XcmHrDevCalendarDayOfWeek', 'XcmHrDevCalendarTimeOfDay', 'XcmHrDevDetailType', 'XcmHrDevDetailUnitClass', 'XcmHrDevInfoRealization', 'XcmHrDevInfoStatus', 'XcmHrDevInfoXStatus', 'XcmHrDevInfoConditions', 'XcmHrDevInfoXConditions', 'XcmHrDevMgmtCommandRequest', 'XcmHrDevMgmtCommandData', 'XcmHrDevPowerTimeUnit', 'XcmHrDevTrafficUnit', 'XcmHrGroupSupport', 'XcmHrSWRunXStatus', 'XcmHrStorageDetailType', 'XcmHrStorageRealization', 'XcmHrSuppliesClassTC', 'XcmHrDetailTableEnumTC', 'XcmHrConsoleDefaultService']}
    · Download XEROX-HOST-RESOURCES-EXT-MIB

    Related source files and packages:


    Source location: XEROX-HOST-RESOURCES-EXT-MIB::xcmHrDevAlertDescription.
    Source version and references

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

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.253)

Fonda Lix Pallone

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.253.8.53.17.2.1.1 xcmHrDevAlertIndex00
1.3.6.1.4.1.253.8.53.17.2.1.2 xcmHrDevAlertRowStatus00
1.3.6.1.4.1.253.8.53.17.2.1.3 xcmHrDevAlertSeverityLevel00
1.3.6.1.4.1.253.8.53.17.2.1.4 xcmHrDevAlertTrainingLevel00
1.3.6.1.4.1.253.8.53.17.2.1.5 xcmHrDevAlertCodeInteger00
1.3.6.1.4.1.253.8.53.17.2.1.6 xcmHrDevAlertCodeString00
1.3.6.1.4.1.253.8.53.17.2.1.8 xcmHrDevAlertReferenceOID00
1.3.6.1.4.1.253.8.53.17.2.1.9 xcmHrDevAlertDateAndTime00
1.3.6.1.4.1.253.8.53.17.2.1.10 xcmHrDevAlertTitle00
1.3.6.1.4.1.253.8.53.17.2.1.11 xcmHrDevAlertHelpReference00
1.3.6.1.4.1.253.8.53.17.2.1.12 xcmHrDevAlertReferenceIndex00
1.3.6.1.4.1.253.8.53.17.2.1.13 xcmHrDevAlertReferenceLocation00
1.3.6.1.4.1.253.8.53.17.2.1.14 xcmHrDevAlertDevAlertIndex00
1.3.6.1.4.1.253.8.53.17.2.1.15 xcmHrDevAlertPriority00