TIMETRA-PTP-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-PTP-MIB

Organization: Alcatel-Lucent

Last Updated: 2011-02-01

Description: TIMETRA-PTP-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-PTP-MIB?

TIMETRA-PTP-MIB is Alcatel-Lucent's (now Nokia's) enterprise MIB for the SR OS operating system running on 7750/7450/7710-series service routers, providing management of Precision Time Protocol (PTP, IEEE 1588-2008) clock synchronization. It exposes configuration objects for PTP clock instances -- administrative state, clock type, profile, domain, announce interval, and Best Master Clock Algorithm priority values (priority1/priority2) -- as well as operational/status data such as clock identity and a wait-to-restore timer. Its primary monitoring value is software/protocol status: administrators can confirm whether a PTP clock is administratively enabled (tmnxPtpClockAdminState), what role it holds in the clock hierarchy, and query tmnxPtpClockOperTable for the operational clock identity to verify the timing system is synchronized correctly, which is critical for mobile backhaul and other timing-sensitive networks. As its name and description indicate, it is explicitly built on and dependent on the IEEE 1588-2008 Precision Time Protocol standard. This MIB is deployed on Alcatel-Lucent/Nokia SR OS routers used in mobile backhaul, financial, or other networks requiring precise clock synchronization over packet networks. Engineers can download the TIMETRA-PTP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TIMETRA-PTP-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

  • Alcatel-Lucent/Nokia SR OS service routers (7750/7450/7710 series)

Monitoring Examples

An administrator would poll tmnxPtpClockAdminState and tmnxPtpClockClockType to confirm a PTP clock instance is enabled and configured with the expected role (e.g., ordinary vs. boundary clock), then check tmnxPtpClockOperTable/tmnxPtpClockIdentity to verify which clock is currently acting as the synchronization source. Reviewing tmnxPtpClockPriority1 and tmnxPtpClockPriority2 helps confirm the Best Master Clock Algorithm will select the intended grandmaster, while tmnxPtpClockWaitToRestore shows how long the system waits before reverting to a preferred clock after a failover. An unexpected change in tmnxPtpClockIdentity in the operational table would indicate the router has failed over to a different PTP master, a signal worth investigating in a mobile backhaul timing chain.

What Can Be Monitored

  • PTP clock admin state
  • clock type and profile
  • clock domain and announce interval
  • BMCA priority1/priority2
  • operational clock identity
  • wait-to-restore timer
Imported Objects

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

DateAndTime
RowPointer
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TIMETRA-CHASSIS-MIB

tmnxChassisNotifyChassisIdOBJECT-TYPE
tmnxChassisNotifyHwIndexOBJECT-TYPE
tmnxCpmCardEntryOBJECT-TYPE
tmnxCpmCardOscillatorTypeOBJECT-TYPE

From TIMETRA-GLOBAL-MIB

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

From TIMETRA-PORT-MIB

TmnxPortEncapType

From TIMETRA-TC-MIB

TItemDescription
TmnxAdminState
TmnxEncapVal
TmnxOperState
TmnxPortID

From TIMETRA-VRTR-MIB

vRtrIDOBJECT-TYPE
vRtrIfEntryOBJECT-TYPE

How to Use in IPNetwork Monitor

Example using tmnxPtpClockRecStatsSyncPktLoss OID:

Select an Alcatel-Lucent/Nokia SR OS service router (7750/7450/7710 series) (PTP clock instance admin/oper 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 tmnxPtpClockRecStatsSyncPktLoss into the Find box to locate it in the OID tree, then select it and click OK. The value of tmnxPtpClockRecStatsSyncPktLoss indicates the number of times that the clock recovery process detected packet loss in the sync packet flow from the best master clock. 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 sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Precision Time Protocol (IEEE 1588-2008) management for Alcatel-Lucent SROS devices providing clock synchronization.

Start monitoring Alcatel-Lucent/Nokia SR OS service routers (7750/7450/7710 series) (PTP clock instance admin/oper 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-PTP-MIB