NOKIA-NTP-MIB: View SNMP OID List / Download MIB

VENDOR: NOKIA


 Home MIB: NOKIA-NTP-MIB
Download as:   
NOKIA-COMMON-MIB-OID-REGISTRATION-MIB, SNMPv2-CONF, SNMPv2-TC, SNMPv2-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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
             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.
             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 no-access
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 no-access
The data for one NTP server.
                     ntcNtpServerIndex 1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.1 integer32 no-access
A unique value, greater than zero, for each NTP server. It is recommended that values are assigned continuously starting from 1.
                     ntcNtpServerAddress 1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.2 displaystring read-only
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.
                     ntcNtpServerPort 1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.3 integer32 read-only
Port number used in NTP communication with NTP server. The default value of this variable shall be 123.
                     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.
                     ntcNtpServerPreferred 1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.5 truthvalue read-only
This boolean variable marks the server as preferred ('true' (1)) or non-preferred ('false' (2)).
                     ntcNtpServerRowStatus 1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.6 rowstatus read-only
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
             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
             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