draft-ietf-ntp-ntpv4-mib-07.txt   rfc5907.txt 
NTP H. Gerstung Internet Engineering Task Force (IETF) H. Gerstung
Internet-Draft Meinberg Request for Comments: 5907 Meinberg
Intended status: Standards Track C. Elliott Category: Standards Track C. Elliott
Expires: September 6, 2010 ISSN: 2070-1721
B. Haberman, Ed. B. Haberman, Ed.
JHU APL JHU APL
March 5, 2010 June 2010
Definitions of Managed Objects for Network Time Protocol Version 4 Definitions of Managed Objects for
(NTPv4) Network Time Protocol Version 4 (NTPv4)
draft-ietf-ntp-ntpv4-mib-07
Abstract Abstract
RFC Ed. : This draft refers to itself with RFC YYYY. When this draft
is published as an RFC, the RFC Editor is asked to replace "YYYY" (in
the RFC, including the MIB module part) with the assigned RFC number
and to remove this note. This draft also refers to
draft-ietf-ntp-ntpv4-proto. When this draft is published as an RFC,
the RFC Editor is asked to replace "draft-ietf-ntp-ntpv4-proto" (in
the RFC, including the MIB module part) with "RFC ZZZZ" (where ZZZZ
is the assigned RFC number) and to remove this note.
The Network Time Protocol (NTP) is used in networks of all types and The Network Time Protocol (NTP) is used in networks of all types and
sizes for time synchronization of servers, workstations and other sizes for time synchronization of servers, workstations, and other
networked equipment. As time synchronization is more and more a networked equipment. As time synchronization is more and more a
mission critical service, standardized means for monitoring and mission-critical service, standardized means for monitoring and
management of this subsystem of a networked host are required to management of this subsystem of a networked host are required to
allow operators of such a service to setup a monitoring system that allow operators of such a service to set up a monitoring system that
is platform- and vendor-independent. This document provides a is platform- and vendor-independent. This document provides a
standardized collection of data objects for monitoring the NTP entity standardized collection of data objects for monitoring the NTP entity
of such a network participant and it is part of the NTP Version 4 of such a network participant and it is part of the NTP version 4
standardization effort. standardization effort.
Status of this Memo 5Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on September 6, 2010. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc5907.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction ....................................................2
2. Conventions Used In This Document . . . . . . . . . . . . . . 4 2. Conventions Used in This Document ...............................3
3. The Internet-Standard Management Framework . . . . . . . . . . 4 3. The Internet-Standard Management Framework ......................3
4. Technical Description . . . . . . . . . . . . . . . . . . . . 4 4. Technical Description ...........................................3
5. MIB Definition . . . . . . . . . . . . . . . . . . . . . . . . 5 5. MIB Definition ..................................................4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 6. IANA Considerations ............................................23
7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 7. Security Considerations ........................................23
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 8. Acknowledgments ................................................24
8.1. Normative References . . . . . . . . . . . . . . . . . . . 26 9. References .....................................................24
8.2. Informative References . . . . . . . . . . . . . . . . . . 26 9.1. Normative References ......................................24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 9.2. Informative References ....................................2
1. Introduction 1. Introduction
The NTPv4 MIB Module is designed to allow SNMP to be used to monitor The NTPv4 MIB module is designed to allow Simple Network Management
and manage local NTP [I-D.ietf-ntp-ntpv4-proto] entities. It Protocol (SNMP) to be used to monitor and manage local NTP [RFC5905]
provides a collection of data objects that can be queried using the entities. It provides a collection of data objects that can be
SNMP protocol and represent the current status of the NTP entity. queried using the SNMP protocol and represent the current status of
This includes general information about the NTP entity itself the NTP entity. This includes general information about the NTP
(vendor, product, version) as well as connectivity to upstream NTP entity itself (vendor, product, version) as well as connectivity to
servers used as sources of reference time and to hardware reference upstream NTP servers used as sources of reference time and to
clocks like radio clocks. The most important values are included in hardware reference clocks like radio clocks. The most important
order to be able to detect failures before they can have an impact on values are included in order to be able to detect failures before
the overall time synchronization status of the network. There are they can have an impact on the overall time synchronization status of
also a collection of notification objects to inform about state the network. There are also a collection of notification objects to
changes in the NTP entity. There are objects to control these inform about state changes in the NTP entity. There are objects to
notifications as well. control these notifications as well.
2. Conventions Used In This Document 2. Conventions Used in This Document
The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in RFC2578 module that is compliant to the SMIv2, which is described in STD 58,
[RFC2578], RFC2579 [RFC2579] and RFC2580 [RFC2580]. RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
4. Technical Description 4. Technical Description
The NTPv4 MIB Module is divided into sections for general server The NTPv4 MIB module is divided into sections for general server
information, current NTP entity status, status information of all information, current NTP entity status, status information of all
mobilized associations (e.g. unicast upstream time servers, multicast mobilized associations (e.g., unicast upstream time servers,
or broadcast time references and hardware clocks), NTP entity control multicast or broadcast, time references, and hardware clocks), NTP
objects, NTP objects used only for notifications, as well as SNMP entity control objects, NTP objects used only for notifications, as
notification definitions for core events. well as SNMP notification definitions for core events.
The general server information section contains static information The general server information section contains static information
and can be queried to identify which NTP implementation is running on 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 a host. This includes the vendor and product name of the running NTP
software as well as version information, hardware/os platform software as well as version information, hardware/os platform
identity and the time resolution of the underlying OS. identity, and the time resolution of the underlying OS.
Section 2 (current NTP status) includes data objects that represent Section 2 (current NTP status) includes data objects that represent
the current operational status of the NTP entity. the current operational status of the NTP entity.
The third section contains data objects that represent the set of The third section contains data objects that represent the set of
time references ("associations") the NTP entity is currently working time references ("associations") with which the NTP entity is
with. currently working.
The fourth section contains objects that can be used to control the The fourth section contains objects that can be used to control the
NTP entity. The currently defined objects control how often the NTP entity. The currently defined objects control how often the
heartbeat interval notification is sent out and which notifications heartbeat interval notification is sent out and which notifications
are enabled. are enabled.
The fifth section contains objects that are only used as varbinds in The fifth section contains objects that are only used as varbinds in
notifications. There is currently only one object in this section--a notifications. There is currently only one object in this section --
message that adds a clear text event message to notifications. a message that adds a cleartext event message to notifications.
Certain important events can occur while the NTP entity is running. Certain important events can occur while the NTP entity is running.
The notification section defines SNMP notifications for a collection The notification section defines SNMP notifications for a collection
of the most important ones ("core events") and additionally provides of the most important ones ("core events") and additionally provides
a heartbeat notification as well as a test notification to allow a heartbeat notification as well as a test notification to allow
management systems to test the reception of NTP related notifications management systems to test the reception of NTP-related notifications
as well as enable heartbeat-based monitoring systems to assure that as well as enable heartbeat-based monitoring systems to assure that
the NTP entity is still up and running. the NTP entity is still up and running.
Some values are included both in numeric and in human-readable Some values are included both in numeric and in human-readable
(string) format. This has been done to simplify the representation (string) format. This has been done to simplify the representation
of a status information. If the two representations of a certain of a status information. If the two representations of a certain
value differ, the numeric representation takes precedence. value differ, the numeric representation takes precedence.
5. MIB Definition 5. MIB Definition
skipping to change at page 6, line 8 skipping to change at page 4, line 38
-- --
-- Authors: Heiko Gerstung (heiko.gerstung@meinberg.de) -- Authors: Heiko Gerstung (heiko.gerstung@meinberg.de)
-- Chris Elliott (chelliot@pobox.com) -- Chris Elliott (chelliot@pobox.com)
-- --
-- for the Internet Engineering Task Force (IETF) -- for the Internet Engineering Task Force (IETF)
-- NTP Working Group (ntpwg) -- NTP Working Group (ntpwg)
-- --
-- --
-- ********************************************************************* -- *********************************************************************
-- Rev 1.00 -- Rev 1.00
-- Published as RFC 5907
-- --
-- ********************************************************************* -- *********************************************************************
NTPv4-MIB DEFINITIONS ::= BEGIN NTPv4-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE , mib-2, Integer32, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE , mib-2, Integer32, NOTIFICATION-TYPE,
Unsigned32, Counter32, TimeTicks Unsigned32, Counter32, TimeTicks
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC 2580
DisplayString, TEXTUAL-CONVENTION DisplayString, TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC 2579
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB -- RFC4001 FROM INET-ADDRESS-MIB -- RFC 4001
Utf8String Utf8String
FROM SYSAPPL-MIB; -- RFC2287 FROM SYSAPPL-MIB; -- RFC 2287
ntpSnmpMIB MODULE-IDENTITY ntpSnmpMIB MODULE-IDENTITY
LAST-UPDATED "201003050000Z" -- March 5, 2010 LAST-UPDATED "201005170000Z" -- May 17, 2010
ORGANIZATION "The IETF NTP Working Group (ntpwg)" ORGANIZATION "The IETF NTP Working Group (ntpwg)"
CONTACT-INFO CONTACT-INFO
" WG Email: ntpwg@lists.ntp.isc.org " WG Email: ntpwg@lists.ntp.isc.org
Subscribe: Subscribe:
https://lists.ntp.isc.org/mailman/listinfo/ntpwg https://lists.ntp.isc.org/mailman/listinfo/ntpwg
Heiko Gerstung Heiko Gerstung
Meinberg Funkuhren Gmbh & Co. KG Meinberg Funkuhren Gmbh & Co. KG
Lange Wand 9 Lange Wand 9
Bad Pyrmont 31812 Bad Pyrmont 31812
skipping to change at page 7, line 14 skipping to change at page 5, line 45
Brian Haberman Brian Haberman
11100 Johns Hopkins Road 11100 Johns Hopkins Road
Laurel, MD 20723 Laurel, MD 20723
USA USA
Phone: +1-443-778-1319 Phone: +1-443-778-1319
Email: brian@innovationslab.net" Email: brian@innovationslab.net"
DESCRIPTION DESCRIPTION
"The Management Information Base for NTP time entities. "The Management Information Base for NTP time entities.
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as
document authors. All rights reserved. authors of the code. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Redistribution and use in source and binary forms, with or
Provisions Relating to IETF Documents without modification, is permitted pursuant to, and subject
(http://trustee.ietf.org/license-info) in effect on the date of to the license terms contained in, the Simplified BSD License
publication of this document. Please review these documents set forth in Section 4.c of the IETF Trust's Legal Provisions
carefully, as they describe your rights and restrictions with Relating to IETF Documents
respect to this document. Code Components extracted from this (http://trustee.ietf.org/license-info)."
document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the BSD License."
REVISION "201003050000Z" REVISION "201005170000Z"
DESCRIPTION DESCRIPTION
"This revision of the MIB module is published as RFC YYYY." "This revision of the MIB module is published as RFC 5907."
::= { mib-2 XXXXX } ::= { mib-2 197 }
ntpSnmpMIBObjects OBJECT IDENTIFIER ::= { ntpSnmpMIB 1 } ntpSnmpMIBObjects OBJECT IDENTIFIER ::= { ntpSnmpMIB 1 }
-- MIB contains 6 groups -- MIB contains 6 groups
ntpEntInfo OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 1 } ntpEntInfo OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 1 }
ntpEntStatus OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 2 } ntpEntStatus OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 2 }
ntpAssociation OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 3 } ntpAssociation OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 3 }
ntpEntControl OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 4 } ntpEntControl OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 4 }
ntpEntNotifObjects OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 5 } ntpEntNotifObjects OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 5 }
skipping to change at page 8, line 12 skipping to change at page 6, line 38
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NTP stratum, with 16 representing no stratum." "The NTP stratum, with 16 representing no stratum."
SYNTAX Unsigned32 (1..16) SYNTAX Unsigned32 (1..16)
NtpDateTime ::= TEXTUAL-CONVENTION NtpDateTime ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4d:4d:4d.4d" DISPLAY-HINT "4d:4d:4d.4d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"NTP date/time on the device, in 128-bit "NTP date/time on the device, in 128-bit
NTP date format. If time is not syncronized this NTP date format. If time is not syncronized, this
field shall be a zero-length string. field shall be a zero-length string.
This TC is not to be used for objects that are used This trusted certificate (TC) is not to be used for objects
to set the time of the node querying this object. that are used to set the time of the node querying this
NTP should be used for this--or at least SNTP." object. NTP should be used for this -- or at least SNTP."
REFERENCE "draft-ietf-ntp-ntpv4-proto, section 6" REFERENCE "RFC 5905, section 6"
SYNTAX OCTET STRING (SIZE (0 | 16)) SYNTAX OCTET STRING (SIZE (0 | 16))
-- --
-- Section 1: General NTP Entity information objects -- Section 1: General NTP Entity information objects
-- (relatively static information) -- (relatively static information)
-- --
ntpEntSoftwareName OBJECT-TYPE ntpEntSoftwareName OBJECT-TYPE
SYNTAX Utf8String SYNTAX Utf8String
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The product name of the running NTP version, e.g. 'ntpd'" "The product name of the running NTP version, e.g., 'ntpd'."
::= { ntpEntInfo 1 } ::= { ntpEntInfo 1 }
ntpEntSoftwareVersion OBJECT-TYPE ntpEntSoftwareVersion OBJECT-TYPE
SYNTAX Utf8String SYNTAX Utf8String
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The software version of the installed NTP implementation "The software version of the installed NTP implementation
as a full version string, e.g. 'ntpd-4.2.0b@1.1433 ...'" as a full version string, e.g., 'ntpd-4.2.0b@1.1433 ...'"
::= { ntpEntInfo 2 } ::= { ntpEntInfo 2 }
ntpEntSoftwareVendor OBJECT-TYPE ntpEntSoftwareVendor OBJECT-TYPE
SYNTAX Utf8String SYNTAX Utf8String
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor/author of the installed NTP version." "The vendor/author of the installed NTP version."
::= { ntpEntInfo 3 } ::= { ntpEntInfo 3 }
ntpEntSystemType OBJECT-TYPE ntpEntSystemType OBJECT-TYPE
SYNTAX Utf8String SYNTAX Utf8String
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General hardware/os platform information, "General hardware/os platform information,
e.g. 'Linux 2.6.12 / x86'" e.g., 'Linux 2.6.12 / x86'."
-- freely configurable, default is OS Version / Hardware platform -- freely configurable, default is OS Version / Hardware platform
::= { ntpEntInfo 4 } ::= { ntpEntInfo 4 }
ntpEntTimeResolution OBJECT-TYPE ntpEntTimeResolution OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time resolution in integer format, where the resolution "The time resolution in integer format, where the resolution
is represented as divisions of a second, e.g. a value of 1000 is represented as divisions of a second, e.g., a value of 1000
translates to 1.0 ms." translates to 1.0 ms."
::= { ntpEntInfo 5 } ::= { ntpEntInfo 5 }
ntpEntTimePrecision OBJECT-TYPE ntpEntTimePrecision OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity's precision in integer format, shows the precision. "The entity's precision in integer format, shows the precision.
A value of -5 would mean 2^-5 = 31.25 ms" A value of -5 would mean 2^-5 = 31.25 ms."
::= { ntpEntInfo 6 } ::= { ntpEntInfo 6 }
ntpEntTimeDistance OBJECT-TYPE ntpEntTimeDistance OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The distance from this NTP entity to the root time reference "The distance from this NTP entity to the root time reference
(stratum 0) source including the unit, e.g. '13.243 ms'" (stratum 0) source including the unit, e.g., '13.243 ms'."
::= { ntpEntInfo 7 } ::= { ntpEntInfo 7 }
-- --
-- Section 2: Current NTP status (dynamic information) -- Section 2: Current NTP status (dynamic information)
-- --
ntpEntStatusCurrentMode OBJECT-TYPE ntpEntStatusCurrentMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notRunning(1), notRunning(1),
notSynchronized(2), notSynchronized(2),
noneConfigured(3), noneConfigured(3),
syncToLocal(4), syncToLocal(4),
syncToRefclock(5), syncToRefclock(5),
syncToRemoteServer(6), syncToRemoteServer(6),
unknown(99) unknown(99)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current mode of the NTP. The definition of each possible "The current mode of the NTP. The definition of each possible
value is: value is:
notRunning(1) - NTP is not running notRunning(1) - NTP is not running.
notSynchronized(2) - NTP is not synchronized to any time notSynchronized(2) - NTP is not synchronized to any time
source (stratum = 16) source (stratum = 16).
noneConfigured(3) - NTP is not synchronized and does not noneConfigured(3) - NTP is not synchronized and does not
have a reference configured have a reference configured
(stratum = 16) (stratum = 16).
syncToLocal(4) - NTP is distributing time based on its syncToLocal(4) - NTP is distributing time based on its
local clock (degraded accuracy and/or local clock (degraded accuracy and/or
reliability) reliability).
syncToRefclock(5) - NTP is synchronized to a local syncToRefclock(5) - NTP is synchronized to a local
hardware refclock (e.g. GPS) hardware refclock (e.g., GPS).
syncToRemoteServer(6) - NTP is synchronized to a remote syncToRemoteServer(6) - NTP is synchronized to a remote
NTP server ('upstream' server) NTP server ('upstream' server).
unknown(99) - The state of NTP is unknown." unknown(99) - The state of NTP is unknown."
::= { ntpEntStatus 1 } ::= { ntpEntStatus 1 }
ntpEntStatusStratum OBJECT-TYPE ntpEntStatusStratum OBJECT-TYPE
SYNTAX NtpStratum SYNTAX NtpStratum
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NTP entity's own stratum value. Should be stratum of "The NTP entity's own stratum value. Should be a stratum of
syspeer + 1 (or 16 if no syspeer)" syspeer + 1 (or 16 if no syspeer)."
::= { ntpEntStatus 2 } ::= { ntpEntStatus 2 }
ntpEntStatusActiveRefSourceId OBJECT-TYPE ntpEntStatusActiveRefSourceId OBJECT-TYPE
SYNTAX Unsigned32 ( 0..99999 ) SYNTAX Unsigned32 ( 0..99999 )
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The association ID of the current syspeer." "The association ID of the current syspeer."
::= { ntpEntStatus 3 } ::= { ntpEntStatus 3 }
ntpEntStatusActiveRefSourceName OBJECT-TYPE ntpEntStatusActiveRefSourceName OBJECT-TYPE
SYNTAX Utf8String SYNTAX Utf8String
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The hostname/descriptive name of the current reference source "The hostname/descriptive name of the current reference source
selected as syspeer, e.g. 'ntp1.ptb.de' or 'GPS' or 'DCFi' ..." selected as syspeer, e.g., 'ntp1.ptb.de' or 'GPS' or
'DCFi', ..."
::= { ntpEntStatus 4 } ::= { ntpEntStatus 4 }
ntpEntStatusActiveOffset OBJECT-TYPE ntpEntStatusActiveOffset OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Time offset to the current selected reference time source "The time offset to the current selected reference time source
as a string including unit, e.g. '0.032 ms' or '1.232 s'" as a string including unit, e.g., '0.032 ms' or '1.232 s'."
::= { ntpEntStatus 5 } ::= { ntpEntStatus 5 }
ntpEntStatusNumberOfRefSources OBJECT-TYPE ntpEntStatusNumberOfRefSources OBJECT-TYPE
SYNTAX Unsigned32 (0..99) SYNTAX Unsigned32 (0..99)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of reference sources configured for NTP." "The number of reference sources configured for NTP."
::= { ntpEntStatus 6 } ::= { ntpEntStatus 6 }
ntpEntStatusDispersion OBJECT-TYPE ntpEntStatusDispersion OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The root dispersion of the running NTP entity, e.g. '6.927'" "The root dispersion of the running NTP entity, e.g., '6.927'."
::= { ntpEntStatus 7 } ::= { ntpEntStatus 7 }
ntpEntStatusEntityUptime OBJECT-TYPE ntpEntStatusEntityUptime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The uptime of the NTP entity, (i.e. the time since ntpd was "The uptime of the NTP entity, (i.e., the time since ntpd was
(re-)initialized not sysUptime!). The time is represented in (re-)initialized not sysUptime!). The time is represented in
hundreds of seconds since Jan 1, 1970 (00:00:00.000) UTC" hundreds of seconds since Jan 1, 1970 (00:00:00.000) UTC."
::= { ntpEntStatus 8 } ::= { ntpEntStatus 8 }
ntpEntStatusDateTime OBJECT-TYPE ntpEntStatusDateTime OBJECT-TYPE
SYNTAX NtpDateTime SYNTAX NtpDateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current NTP date/time on the device, in 128-bit "The current NTP date/time on the device, in 128-bit
NTP date format. If time is not syncronized this NTP date format. If time is not syncronized, this
field shall be a zero-length string. field shall be a zero-length string.
This object can be used to timestamp events on this This object can be used to timestamp events on this
node and allow a management station to coorelate node and allow a management station to correlate
different time objects. For example, a management different time objects. For example, a management
station could query this object and sysUpTime in station could query this object and sysUpTime in
the same operation to be able to relate sysUpTime the same operation to be able to relate sysUpTime
to NTP time. to NTP time.
This object is not to be used to set the time of This object is not to be used to set the time of
the node querying this object. NTP should be used the node querying this object. NTP should be used
for this--or at least SNTP." for this -- or at least SNTP."
REFERENCE "draft-ietf-ntp-ntpv4-proto, section 6" REFERENCE "RFC 5905, section 6"
::= { ntpEntStatus 9 } ::= { ntpEntStatus 9 }
ntpEntStatusLeapSecond OBJECT-TYPE ntpEntStatusLeapSecond OBJECT-TYPE
SYNTAX NtpDateTime SYNTAX NtpDateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Date the next known leap second will occur. If there is "Date the next known leap second will occur. If there is
no leap second announced then this object should be 0." no leap second announced, then this object should be 0."
::= { ntpEntStatus 10 } ::= { ntpEntStatus 10 }
ntpEntStatusLeapSecDirection OBJECT-TYPE ntpEntStatusLeapSecDirection OBJECT-TYPE
SYNTAX Integer32 (-1..1) SYNTAX Integer32 (-1..1)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Direction of next known leap second. If there is no "Direction of next known leap second. If there is no
leap second announced then this object should be 0." leap second announced, then this object should be 0."
::= { ntpEntStatus 11 } ::= { ntpEntStatus 11 }
ntpEntStatusInPkts OBJECT-TYPE ntpEntStatusInPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of NTP messages delivered to the "The total number of NTP messages delivered to the
NTP entity from the transport service. NTP entity from the transport service.
skipping to change at page 13, line 20 skipping to change at page 11, line 49
management system and at other times as indicated by management system and at other times as indicated by
discontinuities in the value of sysUpTime." discontinuities in the value of sysUpTime."
::= { ntpEntStatus 13 } ::= { ntpEntStatus 13 }
ntpEntStatusBadVersion OBJECT-TYPE ntpEntStatusBadVersion OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of NTP messages which were delivered "The total number of NTP messages that were delivered
to this NTP entity and were for an unsupported NTP to this NTP entity and were for an unsupported NTP
version. version.
Discountinuities in the value of this counter can occur Discountinuities in the value of this counter can occur
upon cold start or reinitialization of the NTP entity, the upon cold start or reinitialization of the NTP entity, the
management system and at other times as indicated by management system and at other times as indicated by
discontinuities in the value of sysUpTime." discontinuities in the value of sysUpTime."
::= { ntpEntStatus 14 } ::= { ntpEntStatus 14 }
ntpEntStatusProtocolError OBJECT-TYPE ntpEntStatusProtocolError OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 13, line 35 skipping to change at page 12, line 17
management system and at other times as indicated by management system and at other times as indicated by
discontinuities in the value of sysUpTime." discontinuities in the value of sysUpTime."
::= { ntpEntStatus 14 } ::= { ntpEntStatus 14 }
ntpEntStatusProtocolError OBJECT-TYPE ntpEntStatusProtocolError OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of NTP messages which were delivered "The total number of NTP messages that were delivered
to this NTP entity and this entity was not able to to this NTP entity and this entity was not able to
process due to an NTP protocol error. process due to an NTP protocol error.
Discountinuities in the value of this counter can occur Discountinuities in the value of this counter can occur
upon cold start or reinitialization of the NTP entity, the upon cold start or reinitialization of the NTP entity, the
management system and at other times as indicated by management system and at other times as indicated by
discontinuities in the value of sysUpTime." discontinuities in the value of sysUpTime."
::= { ntpEntStatus 15 } ::= { ntpEntStatus 15 }
ntpEntStatusNotifications OBJECT-TYPE ntpEntStatusNotifications OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "notifications" UNITS "notifications"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of SNMP notifications which this NTP "The total number of SNMP notifications that this NTP
entity has generated. entity has generated.
Discountinuities in the value of this counter can occur Discountinuities in the value of this counter can occur
upon cold start or reinitialization of the NTP entity, the upon cold start or reinitialization of the NTP entity, the
management system and at other times as indicated by management system and at other times as indicated by
discontinuities in the value of sysUpTime." discontinuities in the value of sysUpTime."
::= { ntpEntStatus 16 } ::= { ntpEntStatus 16 }
ntpEntStatPktModeTable OBJECT-TYPE ntpEntStatPktModeTable OBJECT-TYPE
SYNTAX SEQUENCE OF NtpEntStatPktModeEntry SYNTAX SEQUENCE OF NtpEntStatPktModeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 16, line 21 skipping to change at page 14, line 51
ntpAssocStatusJitter DisplayString, ntpAssocStatusJitter DisplayString,
ntpAssocStatusDelay DisplayString, ntpAssocStatusDelay DisplayString,
ntpAssocStatusDispersion DisplayString ntpAssocStatusDispersion DisplayString
} }
ntpAssocId OBJECT-TYPE ntpAssocId OBJECT-TYPE
SYNTAX Unsigned32 ( 1..99999 ) SYNTAX Unsigned32 ( 1..99999 )
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The association ID. This is an internal, unique ID." "The association ID. This is an internal, unique ID."
::= { ntpAssociationEntry 1 } ::= { ntpAssociationEntry 1 }
ntpAssocName OBJECT-TYPE ntpAssocName OBJECT-TYPE
SYNTAX Utf8String SYNTAX Utf8String
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The hostname or other descriptive name for the association." "The hostname or other descriptive name for the association."
::= { ntpAssociationEntry 2 } ::= { ntpAssociationEntry 2 }
skipping to change at page 16, line 47 skipping to change at page 15, line 28
"The refclock driver ID, if available." "The refclock driver ID, if available."
-- a refclock driver ID like "127.127.1.0" for non -- a refclock driver ID like "127.127.1.0" for non
-- uni/multi/broadcast associations -- uni/multi/broadcast associations
::= { ntpAssociationEntry 3 } ::= { ntpAssociationEntry 3 }
ntpAssocAddressType OBJECT-TYPE ntpAssocAddressType OBJECT-TYPE
SYNTAX InetAddressType { ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) } SYNTAX InetAddressType { ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of address of the association. Can be either IPv4 or "The type of address of the association. Can be either IPv4 or
IPv6 (both with or without zone index) and contains the type of IPv6 (both with or without zone index) and contains the type of
address for unicast, multicast and broadcast associations." address for unicast, multicast, and broadcast associations."
::= { ntpAssociationEntry 4 } ::= { ntpAssociationEntry 4 }
ntpAssocAddress OBJECT-TYPE ntpAssocAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (4|8|16|20)) SYNTAX InetAddress (SIZE (4|8|16|20))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address (IPv4 or IPv6, with or without zone index) of "The IP address (IPv4 or IPv6, with or without zone index) of
the association. The type and size depends on the the association. The type and size depends on the
ntpAssocAddressType object. Represents the IP address of a ntpAssocAddressType object. Represents the IP address of a
uni/multi/broadcast association." uni/multi/broadcast association."
::= { ntpAssociationEntry 5 } ::= { ntpAssociationEntry 5 }
ntpAssocOffset OBJECT-TYPE ntpAssocOffset OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time offset to the association as a string." "The time offset to the association as a string."
-- including unit, e.g. "0.032 ms" or "1.232 s" -- including unit, e.g., "0.032 ms" or "1.232 s"
::= { ntpAssociationEntry 6 } ::= { ntpAssociationEntry 6 }
ntpAssocStratum OBJECT-TYPE ntpAssocStratum OBJECT-TYPE
SYNTAX NtpStratum SYNTAX NtpStratum
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The association stratum value." "The association stratum value."
::= { ntpAssociationEntry 7 } ::= { ntpAssociationEntry 7 }
ntpAssocStatusJitter OBJECT-TYPE ntpAssocStatusJitter OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jitter in miliseconds as a string." "The jitter in milliseconds as a string."
::= { ntpAssociationEntry 8 } ::= { ntpAssociationEntry 8 }
ntpAssocStatusDelay OBJECT-TYPE ntpAssocStatusDelay OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network delay in miliseconds as a string." "The network delay in milliseconds as a string."
::= { ntpAssociationEntry 9 } ::= { ntpAssociationEntry 9 }
ntpAssocStatusDispersion OBJECT-TYPE ntpAssocStatusDispersion OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The root dispersion of the association." "The root dispersion of the association."
-- e.g. "6.927" -- e.g., "6.927"
::= { ntpAssociationEntry 10 } ::= { ntpAssociationEntry 10 }
ntpAssociationStatisticsTable OBJECT-TYPE ntpAssociationStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF NtpAssociationStatisticsEntry SYNTAX SEQUENCE OF NtpAssociationStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table of statistics for current associations." "The table of statistics for current associations."
::= { ntpAssociation 2 } ::= { ntpAssociation 2 }
skipping to change at page 19, line 21 skipping to change at page 17, line 49
discontinuities in the value of sysUpTime." discontinuities in the value of sysUpTime."
::= { ntpAssociationStatisticsEntry 2 } ::= { ntpAssociationStatisticsEntry 2 }
ntpAssocStatProtocolError OBJECT-TYPE ntpAssocStatProtocolError OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of NTP messages which were delivered "The total number of NTP messages that were delivered
to this NTP entity from this association and this entity to this NTP entity from this association and this entity
was not able to process due to an NTP protocol error. was not able to process due to an NTP protocol error.
Discountinuities in the value of this counter can occur Discountinuities in the value of this counter can occur
upon cold start or reinitialization of the NTP entity, the upon cold start or reinitialization of the NTP entity, the
management system and at other times as indicated by management system and at other times as indicated by
discontinuities in the value of sysUpTime." discontinuities in the value of sysUpTime."
::= { ntpAssociationStatisticsEntry 3 } ::= { ntpAssociationStatisticsEntry 3 }
-- --
-- Section 4: Control objects -- Section 4: Control objects
-- --
skipping to change at page 19, line 42 skipping to change at page 18, line 23
-- Section 4: Control objects -- Section 4: Control objects
-- --
ntpEntHeartbeatInterval OBJECT-TYPE ntpEntHeartbeatInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval at which the ntpEntNotifHeartbeat notification "The interval at which the ntpEntNotifHeartbeat notification
should be sent, in seconds. If set to 0 and the should be sent, in seconds. If set to 0 and the
entNotifHeartbeat bit in ntpEntNotifBits is 1 then entNotifHeartbeat bit in ntpEntNotifBits is 1, then
ntpEntNotifHeartbeat is sent once. ntpEntNotifHeartbeat is sent once.
This value is stored persistently and will be restored to its This value is stored persistently and will be restored to its
last set value upon cold start or restart." last set value upon cold start or restart."
DEFVAL { 60 } DEFVAL { 60 }
::= { ntpEntControl 1 } ::= { ntpEntControl 1 }
ntpEntNotifBits OBJECT-TYPE ntpEntNotifBits OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
notUsed(0), -- Used to sync up bit and notification notUsed(0), -- Used to sync up bit and notification
-- indices -- indices
skipping to change at page 20, line 18 skipping to change at page 18, line 47
entNotifSyspeerChanged(3), entNotifSyspeerChanged(3),
entNotifAddAssociation(4), entNotifAddAssociation(4),
entNotifRemoveAssociation(5), entNotifRemoveAssociation(5),
entNotifConfigChanged(6), entNotifConfigChanged(6),
entNotifLeapSecondAnnounced(7), entNotifLeapSecondAnnounced(7),
entNotifHeartbeat(8) entNotifHeartbeat(8)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A bit for each notification. A 1 for a particular bit enables "A bit for each notification. A 1 for a particular bit enables
that particular notification, a 0 disables it. that particular notification, a 0 disables it.
This value is stored persistently and will be restored to its This value is stored persistently and will be restored to its
last set value upon cold start or restart." last set value upon cold start or restart."
::= { ntpEntControl 2 } ::= { ntpEntControl 2 }
-- --
-- Section 5: Notification objects -- Section 5: Notification objects
-- --
ntpEntNotifMessage OBJECT-TYPE ntpEntNotifMessage OBJECT-TYPE
SYNTAX Utf8String SYNTAX Utf8String
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Used as a payload object for all notifications. Holds a clear "Used as a payload object for all notifications. Holds a
text event message." cleartext event message."
DEFVAL { "no event" } DEFVAL { "no event" }
::= { ntpEntNotifObjects 1 } ::= { ntpEntNotifObjects 1 }
-- --
-- SNMP notification definitions -- SNMP notification definitions
-- --
ntpEntNotifications OBJECT IDENTIFIER ::= { ntpSnmpMIB 0 } ntpEntNotifications OBJECT IDENTIFIER ::= { ntpSnmpMIB 0 }
ntpEntNotifModeChange NOTIFICATION-TYPE ntpEntNotifModeChange NOTIFICATION-TYPE
OBJECTS { ntpEntStatusCurrentMode } OBJECTS { ntpEntStatusCurrentMode }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when the NTP entity changes mode, "The notification to be sent when the NTP entity changes mode,
including starting and stopping (if possible)" including starting and stopping (if possible)."
::= { ntpEntNotifications 1 } ::= { ntpEntNotifications 1 }
ntpEntNotifStratumChange NOTIFICATION-TYPE ntpEntNotifStratumChange NOTIFICATION-TYPE
OBJECTS { ntpEntStatusDateTime, ntpEntStatusStratum, OBJECTS { ntpEntStatusDateTime, ntpEntStatusStratum,
ntpEntNotifMessage } ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when stratum level of NTP changes." "The notification to be sent when stratum level of NTP changes."
::= { ntpEntNotifications 2 } ::= { ntpEntNotifications 2 }
skipping to change at page 21, line 43 skipping to change at page 20, line 22
DESCRIPTION DESCRIPTION
"The notification to be sent when an association is "The notification to be sent when an association is
demobilized." demobilized."
::= { ntpEntNotifications 5 } ::= { ntpEntNotifications 5 }
ntpEntNotifConfigChanged NOTIFICATION-TYPE ntpEntNotifConfigChanged NOTIFICATION-TYPE
OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage } OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when the NTP configuration has "The notification to be sent when the NTP configuration has
changed, e.g. when the system connected to the internet and was changed, e.g., when the system connected to the Internet and
assigned a new IP address by the ISPs DHCP server" was assigned a new IP address by the ISPs DHCP server."
::= { ntpEntNotifications 6 } ::= { ntpEntNotifications 6 }
ntpEntNotifLeapSecondAnnounced NOTIFICATION-TYPE ntpEntNotifLeapSecondAnnounced NOTIFICATION-TYPE
OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage } OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when a leap second has been "The notification to be sent when a leap second has been
announced." announced."
::= { ntpEntNotifications 7 } ::= { ntpEntNotifications 7 }
ntpEntNotifHeartbeat NOTIFICATION-TYPE ntpEntNotifHeartbeat NOTIFICATION-TYPE
OBJECTS { ntpEntStatusDateTime, ntpEntStatusCurrentMode, OBJECTS { ntpEntStatusDateTime, ntpEntStatusCurrentMode,
ntpEntHeartbeatInterval, ntpEntNotifMessage } ntpEntHeartbeatInterval, ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent periodically (as defined by "The notification to be sent periodically (as defined by
ntpEntHeartbeatInterval) to indicate that the NTP entity is ntpEntHeartbeatInterval) to indicate that the NTP entity is
still alive." still alive."
skipping to change at page 22, line 25 skipping to change at page 21, line 4
::= { ntpEntNotifications 8 } ::= { ntpEntNotifications 8 }
-- --
-- Conformance/Compliance statements -- Conformance/Compliance statements
-- --
ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 2 } ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 2 }
ntpEntCompliances OBJECT IDENTIFIER ::= { ntpEntConformance 1 } ntpEntCompliances OBJECT IDENTIFIER ::= { ntpEntConformance 1 }
ntpEntGroups OBJECT IDENTIFIER ::= { ntpEntConformance 2 } ntpEntGroups OBJECT IDENTIFIER ::= { ntpEntConformance 2 }
ntpEntNTPCompliance MODULE-COMPLIANCE ntpEntNTPCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which use NTP and "The compliance statement for SNMP entities that use NTP and
implement the NTP MIB" implement the NTP MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ntpEntObjectsGroup1 ntpEntObjectsGroup1
} }
::= { ntpEntCompliances 1 } ::= { ntpEntCompliances 1 }
ntpEntSNTPCompliance MODULE-COMPLIANCE ntpEntSNTPCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which use SNTP and "The compliance statement for SNMP entities that use SNTP and
implement the NTP MIB" implement the NTP MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ntpEntObjectsGroup1 ntpEntObjectsGroup1
} }
GROUP ntpEntObjectsGroup2 GROUP ntpEntObjectsGroup2
DESCRIPTION DESCRIPTION
"optional object group" "Optional object group."
GROUP ntpEntNotifGroup GROUP ntpEntNotifGroup
DESCRIPTION DESCRIPTION
"optional notifications for this MIB" "Optional notifications for this MIB."
::= { ntpEntCompliances 2 } ::= { ntpEntCompliances 2 }
ntpEntObjectsGroup1 OBJECT-GROUP ntpEntObjectsGroup1 OBJECT-GROUP
OBJECTS { OBJECTS {
ntpEntSoftwareName, ntpEntSoftwareName,
ntpEntSoftwareVersion, ntpEntSoftwareVersion,
ntpEntSoftwareVendor, ntpEntSoftwareVendor,
ntpEntSystemType, ntpEntSystemType,
ntpEntStatusEntityUptime, ntpEntStatusEntityUptime,
ntpEntStatusDateTime, ntpEntStatusDateTime,
skipping to change at page 24, line 38 skipping to change at page 23, line 18
END END
6. IANA Considerations 6. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
ntpSnmp { mib-2 XXX } ntpSnmp { mib-2 197 }
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.
7. Security Considerations 7. Security Considerations
There are currently two management objects defined in this MIB module There are currently two management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the objects and their sensitivity/ network operations. These are the objects and their sensitivity/
vulnerability: vulnerability:
ntpEntHeartbeatInterval controls the interval of heartbeat ntpEntHeartbeatInterval controls the interval of heartbeat
notifications. If set to 1 this will cause the NTP entity to send notifications. If set to 1, this will cause the NTP entity to send
one notification each second. This is the maximum rate (1/s) that one notification each second. This is the maximum rate (1/s) that
can be generated automatically. If it is set to 0, then one single can be generated automatically. If it is set to 0, then one single
hearbeat notification will be created and no further automatically hearbeat notification will be created and no further automatically
generated notification is sent. This functionality can be used to generated notification is sent. This functionality can be used to
create notifications at a higher rate (as high as the object can be create notifications at a higher rate (as high as the object can be
written). written).
ntpEntNotifBits enables/disables notifications. Could be used to ntpEntNotifBits enables/disables notifications. Could be used to
switch off notifications in order to delay or eliminate the switch off notifications in order to delay or eliminate the
notification for critical and important events. notification for critical and important events.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
ntpEntSoftwareName, ntpEntSoftwareVersion, ntpEntSoftwareVendor and ntpEntSoftwareName, ntpEntSoftwareVersion, ntpEntSoftwareVendor, and
ntpEntSystemType all can be used to identify software and its version ntpEntSystemType all can be used to identify software and its version
as well as the operating system and hardware platform. This might as well as the operating system and hardware platform. This might
help a potential attacker to find security problems and therefore can help a potential attacker to find security problems and therefore can
be used in the preparation of an attack. be used in the preparation of an attack.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. It is RECOMMENDED that implementers consider the in this MIB module. It is RECOMMENDED that implementers consider the
security features as provided by the SNMPv3 framework (see RFC3410 security features as provided by the SNMPv3 framework (see RFC 3410
[RFC3410], section 8), including full support for the SNMPv3 [RFC3410], section 8), including full support for the SNMPv3
cryptographic mechanisms (for authentication and privacy). Further, cryptographic mechanisms (for authentication and privacy). Further,
deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED.
Instead, it is RECOMMENDED to deploy SNMPv3 and to enable Instead, it is RECOMMENDED to deploy SNMPv3 and to enable
cryptographic security. It is then a customer/operator cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. References 8. Acknowledgments
8.1. Normative References Bert Wijnen provided valuable feedback as the MIB Doctor for this
document.
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[I-D.ietf-ntp-ntpv4-proto] [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
Kasch, W., Mills, D., and J. Burbank, "Network Time "Network Time Protocol Version 4: Protocol and Algorithms
Protocol Version 4 Protocol And Algorithms Specification", Specification", RFC 5905, June 2010.
draft-ietf-ntp-ntpv4-proto-13 (work in progress),
October 2009. [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level
Managed Objects for Applications", RFC 2287,
February 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
8.2. Informative References 9.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
Authors' Addresses Authors' Addresses
Heiko Gerstung Heiko Gerstung
Meinberg Funkuhren Gmbh & Co. KG Meinberg Funkuhren Gmbh & Co. KG
Lange Wand 9 Lange Wand 9
Bad Pyrmont 31812 Bad Pyrmont 31812
Germany Germany
Phone: +49 5281 9309 25 Phone: +49 5281 9309 25
Email: heiko.gerstung@meinberg.de EMail: heiko.gerstung@meinberg.de
Chris Elliott Chris Elliott
1516 Kent St. 1516 Kent St.
Durham, NC 27707 Durham, NC 27707
USA USA
Phone: +1-919-308-1216 Phone: +1-919-308-1216
Email: chelliot@pobox.com EMail: chelliot@pobox.com
Brian Haberman (editor) Brian Haberman (editor)
Johns Hopkins University Applied Physics Lab Johns Hopkins University Applied Physics Lab
11100 Johns Hopkins Road 11100 Johns Hopkins Road
Laurel, MD 20723-6099 Laurel, MD 20723-6099
US US
Phone: +1 443 778 1319 Phone: +1 443 778 1319
Email: brian@innovationslab.net EMail: brian@innovationslab.net
 End of changes. 99 change blocks. 
189 lines changed or deleted 171 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/