Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)
Meinberg Funkuhren Gmbh & Co. KG
Lange Wand 9
Bad Pyrmont
31812
Germany
+49 5281 9309 25
+49 5281 9309 30
heiko.gerstung@meinberg.de
Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park
27709
USA
+1 919-392-2146
none
chelliot@cisco.com
Internet
NTP
NTPv4
MIB
NTP
The Network Time Protocol (NTP) is used in networks of all types and
sizes for time synchronization of servers, workstations and other
networked equipment. As time synchronization is more and more a
mission critical service, standardized means for monitoring and
management of this subsystem of a networked host are required to
allow operators of such a service to setup a monitoring
system that is platform- and vendor-independant.
This Internet draft provides a standardized collection
of data objects for monitoring the NTP entity of such a network
participant and it is part of the NTP Version 4 standardization effort.
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC3410.
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in
RFC2578, RFC2579 and RFC2580.
The NTPv4 MIB Module is designed to allow SNMP to be used to monitor
and manage local NTP entities. It provides a collection of
data objects that can be queried using the SNMP protocol and
represent the current status of the NTP entity. This
includes general information about the NTP entity itself
(vendor, product, version) as well as connectivity to upstream NTP
servers used as sources of reference time and to hardware reference
clocks like radio clocks. The most important values are included in
order to be able to detect failures before they can have an impact on
the overall time synchronization status of the network. There are
also a collection of notification objects to inform about state
changes in the NTP entity. There are objects to control these
notifications as well.
The NTPv4 MIB Module is divided into sections for general server
information, current NTP entity status, status information of all
mobilized associations (e.g. unicast upstream time servers, multicast
or broadcast time references and hardware clocks), NTP entity
control objects, NTP objects used only for notifications, as well as
SNMP notification definitions for core events.
The general server information section contains static information
and can be queried to identify which NTP implementation is
running on a host. This includes the vendor and product name of the
running NTP software as well as version information, hardware/os
platform identity and the time resolution of the underlying OS.
Section 2 (current NTP status) includes data objects that represent
the current operational status of the NTP entity.
The third section contains data objects that represent the set of
time references ("associations") the NTP entity is currently
working with.
The fourth section contains objects that can be used to control the
NTP entity. The currently defined objects control how often the
heartbeat interval notification is sent out and which notifications
are enabled.
The fifth section contains objects that are only used as varbinds in
notifications. There is currently only one object in this section--a
message that adds a clear text event message to notifications.
Certain important events can occur while the NTP entity is running.
The sixth section defines SNMP notifications for a collection of the
most important ones ("core events") and additionally provides a
heartbeat notification as well as a test notification to allow
management systems to test the reception of NTP related notifications
as well as enable heartbeat-based monitoring systems to assure that
the NTP entity is still up and running.
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
RFC Ed. : the IANA is requested to assign a value for "XXX" under the
'mib-2' subtree and to record the assignment in the SMI Numbers
registry. When the assignment has been made, the RFC Editor is asked
to replace "XXX" (here and in the MIB module) with the assigned value
and to remove this note.
Most data objects in this MIB are read-only. The two read-write objects
control notifications. The security provided by the implementation of the
SNMP agent providing the data objects in this MIB will be sufficient,
although it is recommended that a security level of at least SNMPv3
AuthNoPriv be used. The general access management methods used for
SNMP agents apply.
Structure of Management Information Version 2 (SMIv2)
Cisco Systems, Inc.
170 West Tasman Drive
San Jose
CA
95134-1706
US
+1 408 526 5260
kzm@cisco.com
SNMPinfo
3763 Benton Street
Santa Clara
CA
95051
US
+1 408 221 8702
dperkins@snmpinfo.com
TU Braunschweig
Bueltenweg 74/75
38106 Braunschweig
DE
+49 531 3913283
schoenw@ibr.cs.tu-bs.de
Textual Conventions for SMIv2
Cisco Systems, Inc.
170 West Tasman Drive
San Jose
CA
95134-1706
US
+1 408 526 5260
kzm@cisco.com
SNMPinfo
3763 Benton Street
Santa Clara
CA
95051
US
+1 408 221 8702
dperkins@snmpinfo.com
TU Braunschweig
Bueltenweg 74/75
38106 Braunschweig
DE
+49 531 3913283
schoenw@ibr.cs.tu-bs.de
Conformance Statements for SMIv2
Cisco Systems, Inc.
170 West Tasman Drive
San Jose
CA
95134-1706
US
+1 408 526 5260
kzm@cisco.com
SNMPinfo
3763 Benton Street
Santa Clara
CA
95051
US
+1 408 221 8702
dperkins@snmpinfo.com
TU Braunschweig
Bueltenweg 74/75
Braunschweig
38106
DE
+49 531 3913283
schoenw@ibr.cs.tu-bs.de
Introduction and Applicability Statements for Internet-Standard Management Framework