OID reference

tmnxOesNtpOutOfSync

1.3.6.1.4.1.6527.3.1.3.98.0.10

Description

[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time on the OES is not synchronized to the host router. The host router must have NTP enabled and have recovered time from external time sources (NTP to PTP). If there is no NTP time source for the router, it will not serve time to the OES. In addition…

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

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

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

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

Show 2 published definitions

tmnxOesNtpOutOfSync · current

tmnxOesNtpOutOfSync              NOTIFICATION-TYPE
    OBJECTS {
        tmnxHwClass
    }
    STATUS      current
    DESCRIPTION
        "[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time 
         on the OES is not synchronized to the host router. The host router must 
         have NTP enabled and have recovered time from external time sources 
         (NTP to PTP). If there is no NTP time source for the router, it will 
         not serve time to the OES. In addition, once the NE is power cycled, 
         it takes approximately 20-30 minutes to initialize.  Thereafter, time 
         synchronization will be completed, with a maximum delay time of 2-3 
         minutes.
        
         [EFFECT] Timestamp of each event occurring on the OES may not be 
         exactly aligned with the host router.
        
         [RECOVERY] Ensure the host router has NTP configured and a reachable 
         time source.  Allow 40 minutes for the condition to clear."
    ::= { tmnxOesNotifications 10 }

tmnxOesNtpOutOfSync · current

tmnxOesNtpOutOfSync              NOTIFICATION-TYPE
    OBJECTS {
        tmnxHwClass
    }
    STATUS      current
    DESCRIPTION
        "[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time 
         on the OES is not synchronized to the host router. The host router must 
         have NTP enabled and have recovered time from external time sources 
         (NTP to PTP). If there is no NTP time source for the router, it will 
         not serve time to the OES. In addition, once the NE is power cycled, 
         it takes approximately 20-30 minutes to initialize.  Thereafter, time 
         synchronization will be completed, with a maximum delay time of 2-3 
         minutes.
        
         [EFFECT] Timestamp of each event occurring on the OES may not be 
         exactly aligned with the host router.
        
         [RECOVERY] Ensure the host router has NTP configured and a reachable 
         time source.  Allow 40 minutes for the condition to clear."
    ::= { tmnxOesNotifications 10 }

Meaning

Descriptions

1 unique

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

[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time on the OES is not synchronized to the host router. The host router must have NTP enabled and have recovered time from external time sources (NTP to PTP). If there is no NTP time source for the router, it will not serve time to the OES. In addition, once the NE is power cycled, it takes approximately 20-30 minutes to initialize. Thereafter, time synchronization will be completed, with a maximum delay time of 2-3 minutes. [EFFECT] Timestamp of each event occurring on the OES may not be exactly aligned with the host router. [RECOVERY] Ensure the host router has NTP configured and a reachable time source. Allow 40 minutes for the condition to clear.

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

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

Status in source: current.

Names: tmnxOesNtpOutOfSync

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "tmnxOesNtpOutOfSync",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "tmnxHwClass",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time on the OES is not synchronized to the host router. The host router must have NTP enabled and have recovered time from external time sources (NTP to PTP). If there is no NTP time source for the router, it will not serve time to the OES. In addition, once the NE is power cycled, it takes approximately 20-30 minutes to initialize. Thereafter, time synchronization will be completed, with a maximum delay time of 2-3 minutes. [EFFECT] Timestamp of each event occurring on the OES may not be exactly aligned with the host router. [RECOVERY] Ensure the host router has NTP configured and a reachable time source. Allow 40 minutes for the condition to clear.\"",
    "::=",
    "{",
    "tmnxOesNotifications",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "tmnxHwClass"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time on the OES is not synchronized to the host router. The host router must have NTP enabled and have recovered time from external time sources (NTP to PTP). If there is no NTP time source for the router, it will not serve time to the OES. In addition, once the NE is power cycled, it takes approximately 20-30 minutes to initialize. Thereafter, time synchronization will be completed, with a maximum delay time of 2-3 minutes. [EFFECT] Timestamp of each event occurring on the OES may not be exactly aligned with the host router. [RECOVERY] Ensure the host router has NTP configured and a reachable time source. Allow 40 minutes for the condition to clear."
    ],
    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.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.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