OID reference

tmnxOesDbSyncFailure

1.3.6.1.4.1.6527.3.1.3.98.0.3

Description

The active Equipment Controller is unable to synchronize its database with the inactive Equipment Controller. [CAUSE] The tmnxOesDbSyncFailure notification may be raised under the following conditions: 1) An incorrectly seated Equipment Controller; 2) The software versions on the active and inactive Equipment Controll…

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
3
Node name
tmnxOesDbSyncFailure
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.6527.3.1.3.98.0.3
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.3.98.0.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

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

Show 2 published definitions

tmnxOesDbSyncFailure · current

tmnxOesDbSyncFailure             NOTIFICATION-TYPE
    OBJECTS {
        tmnxHwClass
    }
    STATUS      current
    DESCRIPTION
        "The active Equipment Controller is unable to synchronize its database 
         with the inactive Equipment Controller. 

         [CAUSE] The tmnxOesDbSyncFailure notification may be raised under the 
         following conditions:
           1) An incorrectly seated Equipment Controller;
           2) The software versions on the active and inactive Equipment 
              Controllers are not compatible;
           3) A hardware problem with one or both controllers.

         [EFFECT] The OES does not have redundancy protection between the two 
         Equipment Controller cards.  

         [RECOVERY] Proceed as follows to clear the Database Synchronization 
         Failed alarm:
           1) Remove the Equipment Controller with the condition and examine 
              the connector on the back of the card for damage, including bent 
              or broken pins;
           2) Examine the connector on the backplane for damage. If there is 
              damage to the backplane of the shelf, contact your service 
              representative;
           3) Re-insert the Equipment Controller into its original slot and 
              allow the card to initialize;
           4) Repeat Step 2) through Step 4) for the second Equipment 
              Controller;
           5) Replace the Equipment Controller with the alarm condition with a 
              new unit. If the condition is not cleared, replace the second 
              Equipment Controller with a new unit.
         Follow the return and repair process to return the faulty card to 
         an authorized repair center for replacement."
    ::= { tmnxOesNotifications 3 }

tmnxOesDbSyncFailure · current

tmnxOesDbSyncFailure             NOTIFICATION-TYPE
    OBJECTS {
        tmnxHwClass
    }
    STATUS      current
    DESCRIPTION
        "The active Equipment Controller is unable to synchronize its database 
         with the inactive Equipment Controller. 

         [CAUSE] The tmnxOesDbSyncFailure notification may be raised under the 
         following conditions:
           1) An incorrectly seated Equipment Controller;
           2) The software versions on the active and inactive Equipment 
              Controllers are not compatible;
           3) A hardware problem with one or both controllers.

         [EFFECT] The OES does not have redundancy protection between the two 
         Equipment Controller cards.  

         [RECOVERY] Proceed as follows to clear the Database Synchronization 
         Failed alarm:
           1) Remove the Equipment Controller with the condition and examine 
              the connector on the back of the card for damage, including bent 
              or broken pins;
           2) Examine the connector on the backplane for damage. If there is 
              damage to the backplane of the shelf, contact your service 
              representative;
           3) Re-insert the Equipment Controller into its original slot and 
              allow the card to initialize;
           4) Repeat Step 2) through Step 4) for the second Equipment 
              Controller;
           5) Replace the Equipment Controller with the alarm condition with a 
              new unit. If the condition is not cleared, replace the second 
              Equipment Controller with a new unit.
         Follow the return and repair process to return the faulty card to 
         an authorized repair center for replacement."
    ::= { tmnxOesNotifications 3 }

Meaning

Descriptions

1 unique

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

The active Equipment Controller is unable to synchronize its database with the inactive Equipment Controller. [CAUSE] The tmnxOesDbSyncFailure notification may be raised under the following conditions: 1) An incorrectly seated Equipment Controller; 2) The software versions on the active and inactive Equipment Controllers are not compatible; 3) A hardware problem with one or both controllers. [EFFECT] The OES does not have redundancy protection between the two Equipment Controller cards. [RECOVERY] Proceed as follows to clear the Database Synchronization Failed alarm: 1) Remove the Equipment Controller with the condition and examine the connector on the back of the card for damage, including bent or broken pins; 2) Examine the connector on the backplane for damage. If there is damage to the backplane of the shelf, contact your service representative; 3) Re-insert the Equipment Controller into its original slot and allow the card to initialize; 4) Repeat Step 2) through Step 4) for the second Equipment Controller; 5) Replace the Equipment Controller with the alarm condition with a new unit. If the condition is not cleared, replace the second Equipment Controller with a new unit. Follow the return and repair process to return the faulty card to an authorized repair center for replacement.

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

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

Status in source: current.

Names: tmnxOesDbSyncFailure

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "tmnxOesDbSyncFailure",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "tmnxHwClass",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The active Equipment Controller is unable to synchronize its database with the inactive Equipment Controller. [CAUSE] The tmnxOesDbSyncFailure notification may be raised under the following conditions: 1) An incorrectly seated Equipment Controller; 2) The software versions on the active and inactive Equipment Controllers are not compatible; 3) A hardware problem with one or both controllers. [EFFECT] The OES does not have redundancy protection between the two Equipment Controller cards. [RECOVERY] Proceed as follows to clear the Database Synchronization Failed alarm: 1) Remove the Equipment Controller with the condition and examine the connector on the back of the card for damage, including bent or broken pins; 2) Examine the connector on the backplane for damage. If there is damage to the backplane of the shelf, contact your service representative; 3) Re-insert the Equipment Controller into its original slot and allow the card to initialize; 4) Repeat Step 2) through Step 4) for the second Equipment Controller; 5) Replace the Equipment Controller with the alarm condition with a new unit. If the condition is not cleared, replace the second Equipment Controller with a new unit. Follow the return and repair process to return the faulty card to an authorized repair center for replacement.\"",
    "::=",
    "{",
    "tmnxOesNotifications",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "tmnxHwClass"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The active Equipment Controller is unable to synchronize its database with the inactive Equipment Controller. [CAUSE] The tmnxOesDbSyncFailure notification may be raised under the following conditions: 1) An incorrectly seated Equipment Controller; 2) The software versions on the active and inactive Equipment Controllers are not compatible; 3) A hardware problem with one or both controllers. [EFFECT] The OES does not have redundancy protection between the two Equipment Controller cards. [RECOVERY] Proceed as follows to clear the Database Synchronization Failed alarm: 1) Remove the Equipment Controller with the condition and examine the connector on the back of the card for damage, including bent or broken pins; 2) Examine the connector on the backplane for damage. If there is damage to the backplane of the shelf, contact your service representative; 3) Re-insert the Equipment Controller into its original slot and allow the card to initialize; 4) Repeat Step 2) through Step 4) for the second Equipment Controller; 5) Replace the Equipment Controller with the alarm condition with a new unit. If the condition is not cleared, replace the second Equipment Controller with a new unit. Follow the return and repair process to return the faulty card to an authorized repair center for replacement."
    ],
    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.4 tmnxOesDbSyncFailureClear00
1.3.6.1.4.1.6527.3.1.3.98.0.5 tmnxOesDbInvalid00
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