OID reference

issHealthChkErrorReason

1.3.6.1.4.1.2076.81.17.2

Description

When the MIB object 'issHealthChkStatus' indicates health as down, this object provides the reason for errors encountered. nonRecovTaskInitializationFailure(1), Indicates the occurence of non-recoverable failure during Task initialization. nonRecovInsufficientStartupMemory(2), Indicates that there is insufficient memo…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.81.17 (issHealthCheckGroup)
Node code
2
Node name
issHealthChkErrorReason
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.81.17.2
URN notation
urn:oid:1.3.6.1.4.1.2076.81.17.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 81 17 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 iss(81) issHealthCheckGroup(17) issHealthChkErrorReason(2)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/81/17/2
  • /ISO/Identified-Organization/6/1/4/1/2076/81/17/2
  • /ISO/3/6/1/4/1/2076/81/17/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/identified-organization/dod/internet/private/enterprises/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/org/dod/internet/private/enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/org/dod/internet/private/enterprises/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/org/dod/internet/private/ldap-enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/org/dod/internet/private/vendor-objects/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-organization/dod/internet/private/enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-organization/dod/internet/private/enterprises/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/iss/issHealthCheckGroup/issHealthChkErrorReason
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/iss/issHealthCheckGroup/issHealthChkErrorReason

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current

Enumerated values

ValueName
1nonRecovTaskInitializationFailure
2nonRecovInsufficientStartupMemory
3recovCruBuffExhausted
4recovConfigRestoreFailed
5recovProtocolMemPoolExhausted

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.2076.81.17.2.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

issHealthChkErrorReason · current

issHealthChkErrorReason    OBJECT-TYPE
    SYNTAX        INTEGER { nonRecovTaskInitializationFailure(1),
                            nonRecovInsufficientStartupMemory(2),
                            recovCruBuffExhausted(3),
                            recovConfigRestoreFailed(4),
                            recovProtocolMemPoolExhausted(5) }
    MAX-ACCESS    read-only
    STATUS        current
    DESCRIPTION
        "When the MIB object 'issHealthChkStatus' indicates health as down, this object provides the 
         reason for errors encountered.

         nonRecovTaskInitializationFailure(1), Indicates the occurence of non-recoverable failure during 
         Task initialization. 

         nonRecovInsufficientStartupMemory(2), Indicates that there is insufficient memory for successful
         startup. This error is non-recoverable and requires sufficient memory to be available in the system
         for successful ISS startup.

         recovCruBuffExhausted(3), Indicates that CRU Buffer Exhausted.

         recovConfigRestoreFailed(4), Indicates that config-restore failed for ISS. This is a recoverable error.

         recovProtocolMemPoolExhausted(5), Indicates that a mem-pool associated with a specific module in ISS has 
         drained out. This error may affect the functioning of the specific protocol alone and is treated as 
         a recoverable error.

         By default issHealthChkErrorReason is 0."
         

    ::= { issHealthCheckGroup 2 }

issHealthChkErrorReason · current

issHealthChkErrorReason    OBJECT-TYPE
    SYNTAX        INTEGER { nonRecovTaskInitializationFailure(1),
                            nonRecovInsufficientStartupMemory(2),
                            recovCruBuffExhausted(3),
                            recovConfigRestoreFailed(4),
                            recovProtocolMemPoolExhausted(5) }
    MAX-ACCESS    read-only
    STATUS        current
    DESCRIPTION
        "When the MIB object 'issHealthChkStatus' indicates health as down, this object provides the
         reason for errors encountered.

         nonRecovTaskInitializationFailure(1), Indicates the occurence of non-recoverable failure during
         Task initialization.

         nonRecovInsufficientStartupMemory(2), Indicates that there is insufficient memory for successful
         startup. This error is non-recoverable and requires sufficient memory to be available in the system
         for successful ISS startup.

         recovCruBuffExhausted(3), Indicates that CRU Buffer Exhausted.

         recovConfigRestoreFailed(4), Indicates that config-restore failed for ISS. This is a recoverable error.

         recovProtocolMemPoolExhausted(5), Indicates that a mem-pool associated with a specific module in ISS has
         drained out. This error may affect the functioning of the specific protocol alone and is treated as
         a recoverable error.

         By default issHealthChkErrorReason is 0."


    ::= { issHealthCheckGroup 2 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

When the MIB object 'issHealthChkStatus' indicates health as down, this object provides the reason for errors encountered. nonRecovTaskInitializationFailure(1), Indicates the occurence of non-recoverable failure during Task initialization. nonRecovInsufficientStartupMemory(2), Indicates that there is insufficient memory for successful startup. This error is non-recoverable and requires sufficient memory to be available in the system for successful ISS startup. recovCruBuffExhausted(3), Indicates that CRU Buffer Exhausted. recovConfigRestoreFailed(4), Indicates that config-restore failed for ISS. This is a recoverable error. recovProtocolMemPoolExhausted(5), Indicates that a mem-pool associated with a specific module in ISS has drained out. This error may affect the functioning of the specific protocol alone and is treated as a recoverable error. By default issHealthChkErrorReason is 0.

Sources for this description

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

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 3 sources

Description 1

issHealthChkErrorReason · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)3 sources

Status in source: current.

Names: issHealthChkErrorReason

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "issHealthChkErrorReason",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "nonRecovTaskInitializationFailure",
    "(",
    "1",
    ")",
    ",",
    "nonRecovInsufficientStartupMemory",
    "(",
    "2",
    ")",
    ",",
    "recovCruBuffExhausted",
    "(",
    "3",
    ")",
    ",",
    "recovConfigRestoreFailed",
    "(",
    "4",
    ")",
    ",",
    "recovProtocolMemPoolExhausted",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"When the MIB object 'issHealthChkStatus' indicates health as down, this object provides the reason for errors encountered. nonRecovTaskInitializationFailure(1), Indicates the occurence of non-recoverable failure during Task initialization. nonRecovInsufficientStartupMemory(2), Indicates that there is insufficient memory for successful startup. This error is non-recoverable and requires sufficient memory to be available in the system for successful ISS startup. recovCruBuffExhausted(3), Indicates that CRU Buffer Exhausted. recovConfigRestoreFailed(4), Indicates that config-restore failed for ISS. This is a recoverable error. recovProtocolMemPoolExhausted(5), Indicates that a mem-pool associated with a specific module in ISS has drained out. This error may affect the functioning of the specific protocol alone and is treated as a recoverable error. By default issHealthChkErrorReason is 0.\"",
    "::=",
    "{",
    "issHealthCheckGroup",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "nonRecovTaskInitializationFailure",
            1
          ],
          [
            "nonRecovInsufficientStartupMemory",
            2
          ],
          [
            "recovCruBuffExhausted",
            3
          ],
          [
            "recovConfigRestoreFailed",
            4
          ],
          [
            "recovProtocolMemPoolExhausted",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "When the MIB object 'issHealthChkStatus' indicates health as down, this object provides the reason for errors encountered. nonRecovTaskInitializationFailure(1), Indicates the occurence of non-recoverable failure during Task initialization. nonRecovInsufficientStartupMemory(2), Indicates that there is insufficient memory for successful startup. This error is non-recoverable and requires sufficient memory to be available in the system for successful ISS startup. recovCruBuffExhausted(3), Indicates that CRU Buffer Exhausted. recovConfigRestoreFailed(4), Indicates that config-restore failed for ISS. This is a recoverable error. recovProtocolMemPoolExhausted(5), Indicates that a mem-pool associated with a specific module in ISS has drained out. This error may affect the functioning of the specific protocol alone and is treated as a recoverable error. By default issHealthChkErrorReason is 0."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.81.17.1 issHealthChkStatus00
1.3.6.1.4.1.2076.81.17.3 issHealthChkMemAllocErrPoolId00
1.3.6.1.4.1.2076.81.17.4 issHealthChkConfigRestoreStatus00
1.3.6.1.4.1.2076.81.17.5 issHealthChkClearCtr00