TIMETRA-NTP-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTIMETRA-NTP-MIB

Organization: Alcatel-Lucent

Last Updated: 2008-01-01

Description: TIMETRA-NTP-MIB module

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TIMETRA-NTP-MIB?

TIMETRA-NTP-MIB is a Nokia/Alcatel-Lucent proprietary SNMP module for SR OS devices that manages and monitors the Network Time Protocol client/server used for system clock synchronization. It exposes NTP system state (leap indicator, stratum, reference clock ID, reference and poll timing) as well as configured NTP server associations and their authentication key IDs. Its primary monitoring value is verifying that the device's clock is properly synchronized to a trusted time source, since stratum level and reference ID directly indicate sync health, and administrative/operational state shows whether NTP is running at all. Time synchronization is foundational infrastructure that other MIBs' timestamps (e.g. "last changed" objects across the TIMETRA MIB family) implicitly depend on for accuracy. It is deployed on Nokia SROS routers across service-provider networks, where TIMETRA-NTP-MIB SNMP monitoring ensures accurate time for logging, security, and protocol timers.

IPNetwork Monitor allows you to monitor SNMP objects defined in TIMETRA-NTP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Nokia/Alcatel-Lucent 7xxx SROS routers
  • vendor SROS network devices requiring synchronized clocks

Monitoring Examples

An admin polls tmnxNtpSysStratum and tmnxNtpSysRefId to confirm the router is synchronized to an expected upstream time source at a healthy stratum, and checks tmnxNtpAdminState/tmnxNtpOperState to ensure NTP is enabled and running. The tmnxNtpSysLeap object flags an impending leap-second event or an unsynchronized state, while tmnxNtpSysPoll shows the current polling interval to the peer. Configured servers in tmnxNtpServer, along with tmnxNtpServerKeyId, are checked when authentication failures prevent a server from being used as a time source.

What Can Be Monitored

  • NTP synchronization stratum
  • reference clock ID and time
  • NTP admin/operational state
  • configured NTP server associations
  • leap-second indicator
Imported Objects

From IF-MIB

InterfaceIndex

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TIMETRA-GLOBAL-MIB

timetraSRMIBModulesOBJECT-IDENTITY
tmnxSRConfsOBJECT-IDENTITY
tmnxSRNotifyPrefixOBJECT-IDENTITY
tmnxSRObjsOBJECT-IDENTITY

From TIMETRA-TC-MIB

TmnxAdminState
TmnxOperState

From TIMETRA-VRTR-MIB

vRtrIDOBJECT-TYPE

How to Use in IPNetwork Monitor

Example using tmnxNtpBroadcastAuthErrs OID:

Select a Nokia/Alcatel-Lucent 7xxx SROS router (NTP client/server sync-status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tmnxNtpBroadcastAuthErrs into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The value of tmnxNtpBroadcastAuthErrs indicates the number of times the tmnxNtpAuthMismatch notification has been generated because of an authentication check failure on this broadcast interface. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Alcatel-Lucent SROS private MIB for managing Network Time Protocol (NTP) client and server configuration on service routers.

Start monitoring Nokia/Alcatel-Lucent 7xxx SROS routers (NTP client/server sync-status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TIMETRA-NTP-MIB