NOKIA-NTP-MIB
The NOKIA-NTP-MIB enables monitoring and configuration of Network Time Protocol (NTP) client operations and real-time clock synchronization status on Nokia network devices. It exposes specific metrics for NTP association states, stratum levels, reachability, and clock discipline parameters to ensure precise time alignment across the infrastructure.
Imported Objects
Objects
21 total| Object Name |
|---|
nokiaNtpMIBThis 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. MODULE-IDENTITY .1.3.6.1.4.1.94.1.16.5.2 |
nokiaNtpObjs OBJECT IDENTIFIER .1.3.6.1.4.1.94.1.16.7.2.1 |
ntcNtpConf OBJECT IDENTIFIER .1.3.6.1.4.1.94.1.16.7.2.1.1 |
ntcNtpEnabledUsed 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.rw EnabledDisabled .1.3.6.1.4.1.94.1.16.7.2.1.1.1 |
ntcNtpServerTableNextIndexReading 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.ro Integer32 (0..'7fffffff'h) .1.3.6.1.4.1.94.1.16.7.2.1.1.2 |
ntcNtpServerTableThe list of NTP servers available for this network element. SEQUENCE OF NtcNtpServerEntry .1.3.6.1.4.1.94.1.16.7.2.1.1.3 |
ntcNtpServerEntryThe data for one NTP server. NtcNtpServerEntry .1.3.6.1.4.1.94.1.16.7.2.1.1.3.1 |
ntcNtpServerIndexA unique value, greater than zero, for each NTP server. It is recommended that values are assigned continuously starting from 1. Integer32 (1..'7fffffff'h) .1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.1 |
ntcNtpServerAddressAddress 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.rw DisplayString .1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.2 |
ntcNtpServerPortPort number used in NTP communication with NTP server. The default value of this variable shall be 123.rw Integer32 (1..'ffff'h) .1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.3 |
ntcNtpServerStatusCurrent status of the corresponding NTP server or NE's capability to communicate with the NTP server.ro TimeServerStatus .1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.4 |
ntcNtpServerPreferredThis boolean variable marks the server as preferred ('true' (1)) or non-preferred ('false' (2)).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.5 |
ntcNtpServerRowStatusThis 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 RFC1903rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.6 |
ntcNtpRtcConf OBJECT IDENTIFIER .1.3.6.1.4.1.94.1.16.7.2.1.2 |
ntcNtpRtcCurrentTimeReading 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..59rw OCTET STRING .1.3.6.1.4.1.94.1.16.7.2.1.2.1 |
ntcNtpRtcTimeZoneReading 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).rw DisplayString .1.3.6.1.4.1.94.1.16.7.2.1.2.2 |
ntcNtpGroups OBJECT IDENTIFIER .1.3.6.1.4.1.94.1.16.8.2.1 |
ntcNtpMinimumRTCGroupAll of these objects are required to be implemented if Real Time Clock is implemented. Unknown .1.3.6.1.4.1.94.1.16.8.2.1.1 |
ntcNtpMandatoryNTPGroupAll of these objects are required to be implemented if NTP is supported. Unknown .1.3.6.1.4.1.94.1.16.8.2.1.2 |
ntcNtpCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.94.1.16.8.2.2 |
nokiaNtpComplianceDescribes the requirements for conformance to the Nokia NTP MIB Unknown .1.3.6.1.4.1.94.1.16.8.2.2.1 |
More MIBs from Nokia
Browse all NokiaMIBs →The TIMETRA-LDP-NG-MIB enables monitoring and configuration of Nokia SR OS (SROS) Label Distribution Protocol Next Generation features, specifically tracking LDP session states, neighbor adjacencies, and label distribution statistics for MPLS traffic engineering.
The TIMETRA-TC-MIB defines proprietary SNMP textual conventions required for the Nokia SROS (Service Router Operating System) to standardize data types for monitoring interface states, traffic counters, and system resource metrics. These definitions serve as the foundational data structures for all TIMETRA-based management applications, ensuring consistent interpretation of telemetry and configuration parameters across Nokia routing platforms.
The TIMETRA-LOG-MIB enables SNMP-based configuration and monitoring of logging utility parameters, event generation rules, and log buffer states on Nokia SR OS (SROS) routers. It facilitates the retrieval of system log severity levels, destination settings, and buffer utilization metrics for centralized network event management.
The TIMETRA-OAM-PM-MIB enables SNMP-based monitoring of Service OAM performance metrics, including packet loss, latency, and jitter counters, on Nokia SR OS (SROS) routers. This proprietary module provides granular visibility into the operational health and quality of service for Layer 2 and Layer 3 Ethernet services.
The TIMETRA-GMPLS-MIB enables SNMP-based provisioning and monitoring of Generalized Multi-Protocol Label Switching (GMPLS) control plane parameters, including label distribution, tunnel signaling states, and resource reservation objects, specifically on Nokia SR OS (formerly TiMOS) routers. This module facilitates the management of GMPLS-specific extensions such as wavelength, fiber, and time-division multiplexing (TDM) link attributes across Nokia's service router hardware.
ALU-MICROWAVE-MIB enables SNMP-based provisioning and monitoring of microwave radio components on Nokia 7xxx series transport devices, specifically tracking link status, signal quality metrics (such as SNR and BER), and interface operational states. This proprietary module facilitates the management of microwave-specific parameters including frequency allocation, modulation schemes, and alarm conditions for point-to-point and point-to-multipoint wireless backhaul links.