NOKIA-NTP-MIB
File:
NOKIA-NTP-MIB.mib (10530 bytes)
Imported modules
Imported symbols
Defined Types
EnabledDisabled |
|
Tok_String |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
enabled(1), disabled(2) |
|
TimeServerStatus |
|
Current status of the corresponding NTP server or NE's capability to
communicate with the NTP server. Value ok(1) means that NE is able to
communicate with this NTP server, value notReachable(2) means that
this NTP server is not reachable, value clockNotInSynch(3) means that
this NTP server is currently unsynchronized (has just come up, has
been too long without external time source or its clock has been
reset), value diffTooBig(4)means that the NE cannot synchronize with
this NTP server because the difference between NTP server and NE's RTC
is too big (> 1000 seconds), and value otherError(5) is reserved for
any other errors. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
ok(1), notReachable(2), clockNotInSynch(3), diffTooBig(4), otherError(5) |
|
NtcNtpServerEntry |
|
SEQUENCE |
|
|
|
|
ntcNtpServerIndex |
Integer32 |
|
|
ntcNtpServerAddress |
DisplayString |
|
|
ntcNtpServerPort |
Integer32 |
|
|
ntcNtpServerStatus |
TimeServerStatus |
|
|
ntcNtpServerPreferred |
TruthValue |
|
|
ntcNtpServerRowStatus |
RowStatus |
|
Defined Values
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. |
MODULE-IDENTITY |
|
|
|
ntcNtpConf |
1.3.6.1.4.1.94.1.16.7.2.1.1 |
OBJECT IDENTIFIER |
|
|
|
ntcNtpEnabled |
1.3.6.1.4.1.94.1.16.7.2.1.1.1 |
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. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
EnabledDisabled |
|
|
ntcNtpServerTableNextIndex |
1.3.6.1.4.1.94.1.16.7.2.1.1.2 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
0..7fffffff |
|
ntcNtpServerTable |
1.3.6.1.4.1.94.1.16.7.2.1.1.3 |
The list of NTP servers available for this network element. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
NtcNtpServerEntry |
|
ntcNtpServerEntry |
1.3.6.1.4.1.94.1.16.7.2.1.1.3.1 |
The data for one NTP server. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
NtcNtpServerEntry |
|
|
ntcNtpServerIndex |
1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.1 |
A unique value, greater than zero, for each NTP server.
It is recommended that values are assigned continuously starting
from 1. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
Integer32 |
1..7fffffff |
|
ntcNtpServerAddress |
1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.2 |
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. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..255) |
|
ntcNtpServerPort |
1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.3 |
Port number used in NTP communication with NTP server.
The default value of this variable shall be 123. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
Integer32 |
1..ffff |
|
ntcNtpServerStatus |
1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.4 |
Current status of the corresponding NTP server or NE's capability to
communicate with the NTP server. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TimeServerStatus |
|
|
ntcNtpServerPreferred |
1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.5 |
This boolean variable marks the server as preferred ('true' (1)) or
non-preferred ('false' (2)). |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
ntcNtpServerRowStatus |
1.3.6.1.4.1.94.1.16.7.2.1.1.3.1.6 |
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 |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
RowStatus |
|
|
ntcNtpRtcCurrentTime |
1.3.6.1.4.1.94.1.16.7.2.1.2.1 |
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 |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
Size(11) |
|
ntcNtpRtcTimeZone |
1.3.6.1.4.1.94.1.16.7.2.1.2.2 |
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). |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..128) |
|
nokiaNtpCompliance |
1.3.6.1.4.1.94.1.16.8.2.2.1 |
Describes the requirements for conformance to the Nokia NTP MIB |
Status: current |
Access: read-write |
MODULE-COMPLIANCE |
|
|
|
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. |
Status: current |
Access: read-write |
OBJECT-GROUP |
|
|
|
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. |
Status: current |
Access: read-write |
OBJECT-GROUP |
|
|
|