OID reference

tmnxOesDbInvalid

1.3.6.1.4.1.6527.3.1.3.98.0.5

Description

[CAUSE] The tmnxOesDbInvalid notification may be raised under the following conditions: 1) During initial installation, if the OES is not properly commissioned; 2) The serial number in the database does not match that of the OES either because the controller was replaced or the alarm card was replaced; 3) A downgrade …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6527.3.1.3.98.0 (tmnxOesNotifications)
Node code
5
Node name
tmnxOesDbInvalid
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.6527.3.1.3.98.0.5
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.3.98.0.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6527 3 1 3 98 0 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxOesMIBNotifyPrefix(98) tmnxOesNotifications(0) tmnxOesDbInvalid(5)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/3/1/3/98/0/5
  • /ISO/Identified-Organization/6/1/4/1/6527/3/1/3/98/0/5
  • /ISO/3/6/1/4/1/6527/3/1/3/98/0/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/org/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/org/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/org/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxOesMIBNotifyPrefix/tmnxOesNotifications/tmnxOesDbInvalid

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

Show 2 published definitions

tmnxOesDbInvalid · current

tmnxOesDbInvalid                 NOTIFICATION-TYPE
    OBJECTS {
        tmnxHwClass
    }
    STATUS      current
    DESCRIPTION
        "[CAUSE] The tmnxOesDbInvalid notification may be raised under the 
         following conditions:
           1) During initial installation, if the OES is not properly 
              commissioned;
           2) The serial number in the database does not match that of the OES 
              either because the controller was replaced or the alarm card was 
              replaced;
           3) A downgrade of OES software has occurred;
           4) Equipment Controller is removed/reseated during a system process, 
              causing file corruption;
           5) The database audit failed indicating some type of corruption of 
              the database.

         [EFFECT] The OES is not in a normal operating mode. It does not have 
         the correct configuration and the state of its cards is unpredictable.
         As a result, the OES will not boot normally and not all commands are 
         allowed.

         [RECOVERY] A database corruption on the OES requires that the OES be 
         re-commissioned. The correct database is held in the host system so 
         it will be restored to the shelf once the existing database is cleared 
         and the host re-establishes communication with the OES."
    ::= { tmnxOesNotifications 5 }

tmnxOesDbInvalid · current

tmnxOesDbInvalid                 NOTIFICATION-TYPE
    OBJECTS {
        tmnxHwClass
    }
    STATUS      current
    DESCRIPTION
        "[CAUSE] The tmnxOesDbInvalid notification may be raised under the 
         following conditions:
           1) During initial installation, if the OES is not properly 
              commissioned;
           2) The serial number in the database does not match that of the OES 
              either because the controller was replaced or the alarm card was 
              replaced;
           3) A downgrade of OES software has occurred;
           4) Equipment Controller is removed/reseated during a system process, 
              causing file corruption;
           5) The database audit failed indicating some type of corruption of 
              the database.

         [EFFECT] The OES is not in a normal operating mode. It does not have 
         the correct configuration and the state of its cards is unpredictable.
         As a result, the OES will not boot normally and not all commands are 
         allowed.

         [RECOVERY] A database corruption on the OES requires that the OES be 
         re-commissioned. The correct database is held in the host system so 
         it will be restored to the shelf once the existing database is cleared 
         and the host re-establishes communication with the OES."
    ::= { tmnxOesNotifications 5 }

Meaning

Descriptions

1 unique

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

[CAUSE] The tmnxOesDbInvalid notification may be raised under the following conditions: 1) During initial installation, if the OES is not properly commissioned; 2) The serial number in the database does not match that of the OES either because the controller was replaced or the alarm card was replaced; 3) A downgrade of OES software has occurred; 4) Equipment Controller is removed/reseated during a system process, causing file corruption; 5) The database audit failed indicating some type of corruption of the database. [EFFECT] The OES is not in a normal operating mode. It does not have the correct configuration and the state of its cards is unpredictable. As a result, the OES will not boot normally and not all commands are allowed. [RECOVERY] A database corruption on the OES requires that the OES be re-commissioned. The correct database is held in the host system so it will be restored to the shelf once the existing database is cleared and the host re-establishes communication with the OES.

Sources for this description

Netdisco MIB archive copiesNokia networking 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 1Netdisco MIB archive copies, Nokia networking MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

tmnxOesDbInvalid · currentNetdisco MIB archive copies, Nokia networking MIB copies (LibreNMS/Observium Community)2 sources

Status in source: current.

Names: tmnxOesDbInvalid

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "tmnxOesDbInvalid",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "tmnxHwClass",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"[CAUSE] The tmnxOesDbInvalid notification may be raised under the following conditions: 1) During initial installation, if the OES is not properly commissioned; 2) The serial number in the database does not match that of the OES either because the controller was replaced or the alarm card was replaced; 3) A downgrade of OES software has occurred; 4) Equipment Controller is removed/reseated during a system process, causing file corruption; 5) The database audit failed indicating some type of corruption of the database. [EFFECT] The OES is not in a normal operating mode. It does not have the correct configuration and the state of its cards is unpredictable. As a result, the OES will not boot normally and not all commands are allowed. [RECOVERY] A database corruption on the OES requires that the OES be re-commissioned. The correct database is held in the host system so it will be restored to the shelf once the existing database is cleared and the host re-establishes communication with the OES.\"",
    "::=",
    "{",
    "tmnxOesNotifications",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "tmnxHwClass"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] The tmnxOesDbInvalid notification may be raised under the following conditions: 1) During initial installation, if the OES is not properly commissioned; 2) The serial number in the database does not match that of the OES either because the controller was replaced or the alarm card was replaced; 3) A downgrade of OES software has occurred; 4) Equipment Controller is removed/reseated during a system process, causing file corruption; 5) The database audit failed indicating some type of corruption of the database. [EFFECT] The OES is not in a normal operating mode. It does not have the correct configuration and the state of its cards is unpredictable. As a result, the OES will not boot normally and not all commands are allowed. [RECOVERY] A database corruption on the OES requires that the OES be re-commissioned. The correct database is held in the host system so it will be restored to the shelf once the existing database is cleared and the host re-establishes communication with the OES."
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Marcelo Mourier

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Jason Sterne

Siblings (15)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6527.3.1.3.98.0.1 tmnxOesCtlCommsDown00
1.3.6.1.4.1.6527.3.1.3.98.0.2 tmnxOesCtlCommsUp00
1.3.6.1.4.1.6527.3.1.3.98.0.3 tmnxOesDbSyncFailure00
1.3.6.1.4.1.6527.3.1.3.98.0.4 tmnxOesDbSyncFailureClear00
1.3.6.1.4.1.6527.3.1.3.98.0.6 tmnxOesDbInvalidClear00
1.3.6.1.4.1.6527.3.1.3.98.0.7 tmnxOesDbUnsync00
1.3.6.1.4.1.6527.3.1.3.98.0.8 tmnxOesDbUnsyncClear00
1.3.6.1.4.1.6527.3.1.3.98.0.9 tmnxOesSwUpgdFailed00
1.3.6.1.4.1.6527.3.1.3.98.0.10 tmnxOesNtpOutOfSync00
1.3.6.1.4.1.6527.3.1.3.98.0.11 tmnxOesNtpSync00
1.3.6.1.4.1.6527.3.1.3.98.0.12 tmnxOesSwBelowMinRev00
1.3.6.1.4.1.6527.3.1.3.98.0.13 tmnxOesFirmwareCondition00
1.3.6.1.4.1.6527.3.1.3.98.0.14 tmnxOesCfgFailNoMemory00
1.3.6.1.4.1.6527.3.1.3.98.0.15 tmnxOesCfgBlocked00
1.3.6.1.4.1.6527.3.1.3.98.0.16 tmnxOesSwUpgdCleanupFailed00