NOKIA-NTP-MIB

All MIBs › NOKIA-NTP-MIB

Organization: Nokia

Last Updated: 1999-08-05

Category: NTP

Description: Configures Nokia device NTP server associations and monitors clock synchronization accuracy.

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 NOKIA-NTP-MIB?

NOKIA-NTP-MIB models Nokia device clock synchronization, configuring NTP client behavior and reporting real-time-clock status, partially derived from the IETF draft MIB for Management of NTP with SNMP. It defines a server-association table for configuring one or more NTP time sources (address, port, preference, row status) plus objects reporting the device's current real-time-clock value, configured time zone, and an overall NTP-enabled flag. Its core monitoring purpose is software/system health: confirming NTP is enabled, verifying configured servers are in an active/valid status, and checking the device's clock value against expected time to catch drift or a failed synchronization source, which is critical for accurate log timestamps and certificate validation. It explicitly derives from the standard "Management of NTP with SNMP" MIB by Sethi, Gao, and Mills, showing a direct dependency on that IETF work. It is deployed on Nokia network devices such as routers and security appliances that need synchronized time for logging, authentication, and coordinated operations. Engineers can download the NOKIA-NTP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in NOKIA-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 router/security appliance

Monitoring Examples

An operator polls ntcNtpServerTable entries via ntcNtpServerIndex to check ntcNtpServerStatus and ntcNtpServerPreferred for each configured server, and reads ntcNtpRtcCurrentTime to confirm the device clock is current; a server whose ntcNtpServerStatus shows unreachable, combined with a stale ntcNtpRtcCurrentTime, indicates the device has lost time synchronization.

What Can Be Monitored

NTP enabled/disabled state
configured NTP server addresses and preference
NTP server association status
real-time clock current value
configured time zone

Imported Objects

From NOKIA-COMMON-MIB-OID-REGISTRATION-MIB

ntcCommonModules	OBJECT-IDENTITY
ntcNtpMibs	OBJECT-IDENTITY
ntcNtpReqs	OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
nokiaNtpMIB	1.3.6.1.4.1.94.1.16.5.2			This MIB module defines management objects that model the management aspects of real time clocks, including NTP client. This includes status and configuration information. This work is partially derived from the 'Management of the Network Time Protocol (NTP) with SNMP' MIB by Adarshpal S. Sethi, Hongxiang Gao, and David Mills.
nokiaNtpObjs	1.3.6.1.4.1.94.1.16.7.2.1
ntcNtpConf	1.3.6.1.4.1.94.1.16.7.2.1.1
ENA ntcNtpEnabled	1.3.6.1.4.1.94.1.16.7.2.1.1.1	EnabledDisabled	read-write	Used to determine if the NE is using NTP (Network Time Protocol) to update it's internal RTC. Possible values are 'enabled' (1) and 'disabled' (2), and the NTP is turned on or off according to this setting. If the variable is set to 'enabled' (1) while it is already 'enabled' (1), then program implementing NTP (e.g. xntpd) is restarted.
I32 ntcNtpServerTableNextIndex	1.3.6.1.4.1.94.1.16.7.2.1.1.2	Integer32	read-only	Reading this variable returns an available index for row creation in ntcNtpServerTable. Subsequent reads should not return same values to avoid conflicts in multiple manager cases. The value zero indicates that no unassigned entries are available.
ntcNtpServerTable	1.3.6.1.4.1.94.1.16.7.2.1.1.3		not-accessible	The list of NTP servers available for this network element.
ntcNtpServerEntry	1.3.6.1.4.1.94.1.16.7.2.1.1.3.1		not-accessible	The data for one NTP server.
I32 ntcNtpServerIndex	1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.1	Integer32	not-accessible	A unique value, greater than zero, for each NTP server. It is recommended that values are assigned continuously starting from 1.
STR ntcNtpServerAddress	1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.2	DisplayString	read-create	Address from which NTP based time is requested. This can be either absolute IP address eg. 131.228.32.41, or host name eg. ntpserver1.ntc.nokia.com.
I32 ntcNtpServerPort	1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.3	Integer32	read-create	Port number used in NTP communication with NTP server. The default value of this variable shall be 123.
TIM ntcNtpServerStatus	1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.4	TimeServerStatus	read-only	Current status of the corresponding NTP server or NE's capability to communicate with the NTP server.
T/F ntcNtpServerPreferred	1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.5	TruthValue	read-create	This boolean variable marks the server as preferred ('true' (1)) or non-preferred ('false' (2)).
ROW ntcNtpServerRowStatus	1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.6	RowStatus	read-create	This object is used to create new rows in this table, modify existing rows, and to delete existing rows. For further details see RowStatus defined in RFC1903
ntcNtpRtcConf	1.3.6.1.4.1.94.1.16.7.2.1.2
OCT ntcNtpRtcCurrentTime	1.3.6.1.4.1.94.1.16.7.2.1.2.1	OCTET STRING	read-write	Reading this variable gives the current local time of NEs RTC including the time zone information. NEs local time can be set by updating this variable. The time is always returned and must be always set in a format of full 11 octects as DateAndTime in RFC 1514, as follows: octets contents range 1-2 year 0..65536 (in network byte order) 3 month 1..12 4 day 1..31 5 hour 0..23 6 minutes 0..59 7 seconds 0..60 (use 60 for leap-second) 8 deci-seconds 0..9 9 direction from UTC + or - (in ascii notation) 10 hours from UTC 0..13 11 minutes from UTC 0..59
STR ntcNtpRtcTimeZone	1.3.6.1.4.1.94.1.16.7.2.1.2.2	DisplayString	read-write	Reading this variable gives the time zone where the NE is located. NEs time zone can be set by updating this variable. If the first character is + or - then the variable is interpreted as the direction from UTC (+ means east from UTC and - means west from UTC), and the next 4 characters are the hours and minutes values of the timezone (eg. +0300). Otherwise the string is an implementation specific name of the timezone (eg. EET, Europe/Helsinki or GMT+3).
ntcNtpGroups	1.3.6.1.4.1.94.1.16.8.2.1
ntcNtpMinimumRTCGroup	1.3.6.1.4.1.94.1.16.8.2.1.1			All of these objects are required to be implemented if Real Time Clock is implemented.
ntcNtpMandatoryNTPGroup	1.3.6.1.4.1.94.1.16.8.2.1.2			All of these objects are required to be implemented if NTP is supported.
ntcNtpCompliances	1.3.6.1.4.1.94.1.16.8.2.2
nokiaNtpCompliance	1.3.6.1.4.1.94.1.16.8.2.2.1			Describes the requirements for conformance to the Nokia NTP MIB

RFC description

Manages real-time clocks and NTP client configuration on Nokia devices including time synchronization status.

Start monitoring Nokia routers/security appliances 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 NOKIA-NTP-MIB

What Is NOKIA-NTP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description