draft-ietf-ntp-ntpv4-mib-02.txt   draft-ietf-ntp-ntpv4-mib-03.txt 
NTP H. Gerstung NTP H. Gerstung
Internet-Draft Meinberg Internet-Draft Meinberg
Expires: January 10, 2008 C. Elliott Expires: June 7, 2008 C. Elliott
Cisco Cisco
July 9, 2007 December 5, 2007
Definitions of Managed Objects for Network Time Protocol Version 4 Definitions of Managed Objects for Network Time Protocol Version 4
(NTPv4) (NTPv4)
draft-ietf-ntp-ntpv4-mib-02 draft-ietf-ntp-ntpv4-mib-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 10, 2008. This Internet-Draft will expire on June 7, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
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 setup a monitoring system that
is platform- and vendor-independant. This RFC draft provides a is platform- and vendor-independant. This Internet draft provides a
standardized collection of data objects for monitoring the NTP standardized collection of data objects for monitoring the NTP entity
service of such a network participant and it is part of the NTP of such a network participant and it is part of the NTP Version 4
Version 4 standardization effort. standardization effort.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Technical Description . . . . . . . . . . . . . . . . . . . . 3 3. Technical Description . . . . . . . . . . . . . . . . . . . . 3
4. MIB Definition . . . . . . . . . . . . . . . . . . . . . . . . 4 4. MIB Definition . . . . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.1. Normative References . . . . . . . . . . . . . . . . . . . 20 7.1. Normative References . . . . . . . . . . . . . . . . . . . 24
7.2. Informative References . . . . . . . . . . . . . . . . . . 20 7.2. Informative References . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 22 Intellectual Property and Copyright Statements . . . . . . . . . . 26
1. The Internet-Standard Management Framework 1. 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 [4]. RFC3410 [4].
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 RFC2578
[1], RFC2579 [2] and RFC2580 [3]. [1], RFC2579 [2] and RFC2580 [3].
2. Introduction 2. Introduction
The NTPv4 MIB Module is designed to allow SNMP to be used to monitor The NTPv4 MIB Module is designed to allow SNMP to be used to monitor
and manage local NTP service instances. It provides a collection of and manage local NTP entities. It provides a collection of data
data objects that can be queried using the SNMP protocol and objects that can be queried using the SNMP protocol and represent the
represent the current status of the NTP service instance. This current status of the NTP entity. This includes general information
includes general information about the NTP service instance itself about the NTP entity itself (vendor, product, version) as well as
(vendor, product, version) as well as connectivity to upstream NTP connectivity to upstream NTP servers used as sources of reference
servers used as sources of reference time and to hardware reference time and to hardware reference clocks like radio clocks. The most
clocks like radio clocks. The most important values are included in important values are included in order to be able to detect failures
order to be able to detect failures before they can have an impact on before they can have an impact on the overall time synchronization
the overall time synchronization status of the network. There are status of the network. There are also a collection of notification
also a collection of notification objects to inform about state objects to inform about state changes in the NTP entity. There are
changes in the NTP service. There are objects to control these objects to control these notifications as well.
notifications as well.
3. Technical Description 3. 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 service 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, multicast
or broadcast time references and hardware clocks), NTP service or broadcast time references and hardware clocks), NTP entity control
control objects, NTP objects used only for notifications, as well as objects, NTP objects used only for notifications, as well as SNMP
SNMP notification definitions for core events. 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 service implementation is and can be queried to identify which NTP implementation is running on
running on a host. This includes the vendor and product name of the a host. This includes the vendor and product name of the running NTP
running NTP software as well as version information, hardware/os software as well as version information, hardware/os platform
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 service instance. 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 instance is currently time references ("associations") the NTP entity is currently working
working with. with.
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 service. 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--a
message that adds a clear text event message to notifications. message that adds a clear text event message to notifications.
Certain important events can occur while the NTP instance is running. Certain important events can occur while the NTP entity is running.
The sixth section defines SNMP notifications for a collection of the The sixth section defines SNMP notifications for a collection of the
most important ones ("core events") and additionally provides a most important ones ("core events") and additionally provides a
heartbeat notification as well as a test notification to allow 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 service is still up and running. the NTP entity is still up and running.
4. MIB Definition 4. MIB Definition
-- *********************************************************************
-- --
--$Id: draft-ietf-ntp-ntpv4-mib-03.xml 1.12 2007/11/28 00:00:00Z chelliot $
--$Name: SUBMIT_1 $ --$Name: SUBMIT_1 $
-- --
-- The Network Time Protocol Version 4 -- The Network Time Protocol Version 4
-- Management Information Base (MIB) -- Management Information Base (MIB)
-- --
-- Authors: Heiko Gerstung (heiko.gerstung@meinberg.de) -- Authors: Heiko Gerstung (heiko.gerstung@meinberg.de)
-- Chris Elliott (chelliot@cisco.com) -- Chris Elliott (chelliot@cisco.com)
-- --
-- for the Internet Engineering Task Force (IETF) -- for the Internet Engineering Task Force (IETF)
-- NTP Working Group (ntpwg) -- NTP Working Group (ntpwg)
-- --
-- --
-- *********************************************************************
-- --
-- $Log: draft-ietf-ntp-ntpv4-mib-03.xml $
-- Revision 1.12 2007/11/28 00:00:00Z chelliot
-- MIB:
-- - Added protocol statistics at the entity and association level
-- XML/RFC:
-- - Changed a couple of instances of "instance" to "entity" and "srv"
-- to "ent".
-- - Changed Meinberg address and Heiko's phone number.
-- Revision 1.11 2007/07/23 00:00:00Z chelliot
-- MIB:
-- - Modified Contact Info
-- - Added Stratum and NTP time TCs
-- - Changed ntpEntNotifNotInSync to ntpEntNotifCurrentMode and
-- deleted ntpEntNotifEntityStarted and ntpEntNotifEntityStopped
-- - Added compliance for SNTP entities
-- - Changed ntpTime to ntpDateTime
-- Revision 1.10 2007/07/09 00:00:00Z chelliot -- Revision 1.10 2007/07/09 00:00:00Z chelliot
-- XML/RFC:
-- - Changed RFC to Internet
-- - Changed service and service instance* to entity/entities
-- - Revised the Security Considerations to include read-write object
-- security considerations
-- - Added Chris Elliott as an author
-- - Fixed several lines to be 72 characters long or less
-- MIB: -- MIB:
-- - Changed "service" and "service instance" to "entity", -- - Changed "service" and "service instance" to "entity",
-- - and Srv to Ent -- and Srv to Ent
-- - Changed RFC to Internet
-- - Changed status to mode -- - Changed status to mode
- and Srv to Ent
-- - Added association status object -- - Added association status object
-- - Added leap second objects -- - Added leap second objects
-- Revision 1.9 2007/03/04 06:59:44Z chelliot -- Revision 1.9 2007/03/04 06:59:44Z chelliot
-- MIB: -- MIB:
-- - Added time objects, comments, changed notifications -- - Added time objects, comments, changed notifications
-- - Changed server to service -- - Changed server to service
-- Revision 1.8 2006/10/23 03:37:44Z chelliot -- Revision 1.8 2006/10/23 03:37:44Z chelliot
-- MIB: -- MIB:
-- - Changed various object types, added notification control object -- - Changed various object types, added notification control object
-- Revision 1.7 2006/06/16 07:13:50Z heiko -- Revision 1.7 2006/06/16 07:13:50Z heiko
-- XML/RFC: -- XML/RFC:
-- - Added/changed comments about the to-be-done IANA SMI assignment
-- Revision 1.6 2006/06/16 07:04:43Z heiko -- Revision 1.6 2006/06/16 07:04:43Z heiko
-- RFC/XML: -- RFC/XML:
-- - phone number corrected -- - phone number corrected
-- - removed unused references -- - removed unused references
-- MIB: -- MIB:
-- - added ntpSrvTimePrecision -- - added ntpSrvTimePrecision
-- - changed INTEGER objects to Integer32 -- - changed INTEGER objects to Integer32
-- - changed default value for ntpSrvStatusStratum from 99 to 16 -- - changed default value for ntpSrvStatusStratum from 99 to 16
-- - changed default value for ntpSrvStatusActiveRefclockId from 99-0
-- - changed object names to ntpSrvStatusActiveRefSourceName -- - changed object names to ntpSrvStatusActiveRefSourceName
-- (from ntpSrvStatusActiveRefclockName) and to -- (from ntpSrvStatusActiveRefclockName) and to
-- ntpSrvStatusNumberOfRefSources (from
-- ntpSrvStatusNumberOfRefclocks)
-- - removed ntpSrvStatusAuthKeyId object -- - removed ntpSrvStatusAuthKeyId object
-- - added ntpSrvStatusDispersion to provide the current root
-- dispersion
-- - major rework of section 3 (Status of associations) to compile
-- cleanly,including:
-- - added dispersion to the association dataset -- - added dispersion to the association dataset
-- - renaming of objects -- - renaming of objects
-- - added an index to the association table -- - added an index to the association table
-- - formal changes -- - formal changes
-- - traps are now reverse mappable -- - traps are now reverse mappable
-- - traps are now define with payload where applicable -- - traps are now define with payload where applicable
-- - added compliance statements -- - added compliance statements
-- Revision 1.5 2006/02/27 08:28:16Z heiko -- Revision 1.5 2006/02/27 08:28:16Z heiko
-- - changed to RFC format and added header as well as -- - changed to RFC format and added header as well as
-- introduction and technical description -- introduction and technical description
-- - added other necessary RFC components (copyright statement etc.) -- - added other necessary RFC components (copyright statement etc.)
-- Revision 1.4 2006/02/27 07:06:49Z heiko -- Revision 1.4 2006/02/27 07:06:49Z heiko
-- - removed all objects with data type REAL -- - removed all objects with data type REAL
-- - everything that needs to be floating point is now defined as -- - everything that needs to be floating point is now defined as
-- DisplayString -- DisplayString
-- Revision 1.2 2006/01/23 08:58:11Z heiko -- Revision 1.2 2006/01/23 08:58:11Z heiko
-- - changed the datatype of offset, jitter and delay objects from
-- Integer32 to REAL
-- --
-- *********************************************************************
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 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
DisplayString DisplayString, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
ntpSnmpMIB MODULE-IDENTITY ntpSnmpMIB MODULE-IDENTITY
LAST-UPDATED "200707090000Z" -- July 9, 2007 LAST-UPDATED "200712050000Z" -- December 5, 2007
ORGANIZATION "The IETF NTP Working Group (ntpwg)" ORGANIZATION "The IETF NTP Working Group (ntpwg)"
CONTACT-INFO CONTACT-INFO
" WG Email: " WG Email: ntpwg@lists.ntp.isc.org
Subscribe: Subscribe:
https://lists.ntp.isc.org/mailman/listinfo/ntpwg
Editor 1 name Heiko Gerstung
Title Meinberg Funkuhren Gmbh & Co. KG
Employeer Lange Wand 9
Address Bad Pyrmont 31812
Phone Germany
email
Editor 2 name..." Phone: +49 5281 9309 25
Email: heiko.gerstung@meinberg.de
Chris Elliott
Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park 27709
USA
Phone: +1 919-392-2146
Email: chelliot@cisco.com"
DESCRIPTION DESCRIPTION
"The Management Information Base for NTP time entities." "The Management Information Base for NTP time entities."
REVISION "200712050000Z"
DESCRIPTION
"Multiple proposed changes for IETF 70"
REVISION "200707230000Z"
DESCRIPTION
"Multiple proposed changes for IETF 69"
REVISION "200707090000Z" REVISION "200707090000Z"
DESCRIPTION DESCRIPTION
"Multiple changes from IETF 68" "Multiple changes from IETF 68"
REVISION "200703040000Z" REVISION "200703040000Z"
DESCRIPTION DESCRIPTION
"More MIB review modifications." "More MIB review modifications."
REVISION "200610230000Z" REVISION "200610230000Z"
DESCRIPTION DESCRIPTION
"Modifications from MIB review." "Modifications from MIB review."
REVISION "200606190000Z" REVISION "200606190000Z"
DESCRIPTION DESCRIPTION
"First Draft Version" "First Draft Version"
REVISION "200512190000Z" REVISION "200512190000Z"
DESCRIPTION DESCRIPTION
"revised edition (added traps and stuff)" "revised edition (added traps and stuff)"
REVISION "200511160000Z" REVISION "200511160000Z"
DESCRIPTION DESCRIPTION
"Initial draft" "Initial draft"
::= { mib-2 99999 } ::= { mib-2 XXX }
ntpSnmpMIBObjects OBJECT IDENTIFIER ::= { ntpSnmpMIB 1 } ntpSnmpMIBObjects OBJECT IDENTIFIER ::= { ntpSnmpMIB 1 }
-- 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 }
ntpEntNotifPrefix OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 6 } ntpEntNotifPrefix OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 6 }
-- --
-- Textual Conventions
--
NtpStratum ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The NTP stratum, with 16 representing no stratum."
SYNTAX Unsigned32 (1..16)
NtpDateTime ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4d:4d:4d.4d"
STATUS current
DESCRIPTION
"NTP date/time on the device, in 128-bit
NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
section 6:
It includes a 64-bit signed seconds field
spanning 584 billion years and a 64-bit fraction
field resolving .05 attosecond (i.e. 0.5e-18).
For convenience in mapping between formats, the
seconds field is divided into a 32-bit era field
and a 32-bit timestamp field.
If time is not syncronized this field shall be a
zero-length string.
This TC is not to be used for objects that are used
to set the time of the node querying this object.
NTP should be used for this--or at least SNTP."
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 DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The product name of the installed NTP version." "The product name of the installed NTP version."
skipping to change at page 7, line 49 skipping to change at page 9, line 24
DESCRIPTION DESCRIPTION
"The software version of the installed NTP implementation." "The software version of the installed NTP implementation."
-- full version string, e.g. "ntpd-4.2.0b@1.1433 ..." -- full version string, e.g. "ntpd-4.2.0b@1.1433 ..."
::= { ntpEntInfo 2 } ::= { ntpEntInfo 2 }
ntpEntSoftwareVersionVal OBJECT-TYPE ntpEntSoftwareVersionVal OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Software version of installed NTP as an unsigned integer value." "Software version of installed NTP as an unsigned integer
-- e.g. if version string is "4.2.0b" this could be translated into 4202 value."
-- could be useful to find out if version of entity on a is newer or older -- e.g. if version string is "4.2.0b" this could be translated into
-- than version of the entity on b (without too much string parsing trouble) -- 4202. This could be useful to find out if version of entity on a
-- is newer or older than version of the entity on b (without too
-- much string parsing trouble)
::= { ntpEntInfo 3 } ::= { ntpEntInfo 3 }
ntpEntSoftwareVendor OBJECT-TYPE ntpEntSoftwareVendor OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
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 4 } ::= { ntpEntInfo 4 }
skipping to change at page 8, line 34 skipping to change at page 10, line 10
::= { ntpEntInfo 5 } ::= { ntpEntInfo 5 }
ntpEntTimeResolution OBJECT-TYPE ntpEntTimeResolution OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A string describing the time resolution of the running NTP "A string describing the time resolution of the running NTP
implementation." implementation."
-- e.g. "100 ns" -- e.g. "100 ns"
-- depends on the NTP implementation and the underlying OS. The current -- depends on the NTP implementation and the underlying OS. The
-- resolution should be used, so if the OS only supports 10ms and ntpd is -- current resolution should be used, so if the OS only supports
-- capable of 1ns, the 10ms should be advertised -- 10ms and ntpd is capable of 1ns, the 10ms should be advertised
::= { ntpEntInfo 6 } ::= { ntpEntInfo 6 }
ntpEntTimeResolutionVal OBJECT-TYPE ntpEntTimeResolutionVal 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." "The time resolution in integer format."
-- ntpEntTimeResolution in Integer format -- ntpEntTimeResolution in Integer format
-- shows the resolution based on 1 second, e.g. "1ms" translates to 1000 -- shows the resolution based on 1 second, e.g. "1ms" translates to
-- 1000
::= { ntpEntInfo 7 } ::= { ntpEntInfo 7 }
ntpEntTimePrecision OBJECT-TYPE ntpEntTimePrecision OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A string describing the precision with which the NTP entity "A string describing the precision with which the NTP entity
implementation/OS manages its time base." implementation/OS manages its time base."
-- e.g. "-18" means 2^-18 = 0.000003814697265625 seconds -- e.g. "-18" means 2^-18 = 0.000003814697265625 seconds
skipping to change at page 9, line 28 skipping to change at page 11, line 5
"The entity's precision in integer format." "The entity's precision in integer format."
-- ntpEntTimePrecision in signed Integer format -- ntpEntTimePrecision in signed Integer format
-- shows the precision. A value of -5 would mean 2^-5 = 31.25 ms -- shows the precision. A value of -5 would mean 2^-5 = 31.25 ms
::= { ntpEntInfo 9 } ::= { ntpEntInfo 9 }
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 instance to the root time reference "The distance from this NTP entity to the root time reference
(stratum 0) source." (stratum 0) source."
-- including the unit -- including the unit
-- e.g. "13.243 ms" -- e.g. "13.243 ms"
::= { ntpEntInfo 10 } ::= { ntpEntInfo 10 }
-- --
-- Section 2: Current NTP status (dynamic information) -- Section 2: Current NTP status (dynamic information)
-- --
ntpEntStatusCurrentMode OBJECT-TYPE ntpEntStatusCurrentMode OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual mode of NTP as a string" "The actual mode of NTP as a string"
--- possible strings: --- possible strings:
--- "not running" : NTP is not running --- "not running" : NTP is not running
--- "not synchronized" : NTP is not synchronized to any time source --- "not synchronized" : NTP is not synchronized to any time source
--- (stratum = 16) --- (stratum = 16)
--- "none configured" : NTP is not synchronized and does not have a server --- "none configured" : NTP is not synchronized and does not have a
--- configured --- server configured
--- (stratum = 16) --- (stratum = 16)
--- "sync to local" : NTP is synchronized to own local clock --- "sync to local" : NTP is synchronized to own local clock
--- (degraded reliability) --- (degraded reliability)
--- "sync to refclock" : NTP is synchronized to a local hardware refclock --- "sync to refclock" : NTP is synchronized to a local hardware
--- (e.g. GPS) --- refclock (e.g. GPS)
--- "sync to remote server" : NTP is synchronized to a remote NTP server --- "sync to remote server" : NTP is synchronized to a remote NTP
--- ("upstream" server) --- server ("upstream" server)
--- "unknown" : The state of NTP is unknown. --- "unknown" : The state of NTP is unknown.
::= { ntpEntStatus 1 } ::= { ntpEntStatus 1 }
ntpEntStatusCurrentModeVal OBJECT-TYPE ntpEntStatusCurrentModeVal 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),
skipping to change at page 10, line 31 skipping to change at page 12, line 8
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current mode of the NTP as integer value." "The current mode of the NTP as integer value."
-- see ntpEntStatusCurrentMode -- see ntpEntStatusCurrentMode
DEFVAL { 99 } DEFVAL { 99 }
::= { ntpEntStatus 2 } ::= { ntpEntStatus 2 }
ntpEntStatusStratum OBJECT-TYPE ntpEntStatusStratum OBJECT-TYPE
SYNTAX Unsigned32 (1..16) SYNTAX NtpStratum
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NTP entity's own stratum value." "The NTP entity's own stratum value."
-- should be stratum of syspeer + 1 (or 16 if no syspeer) -- should be stratum of syspeer + 1 (or 16 if no syspeer)
DEFVAL { 16 } DEFVAL { 16 }
::= { ntpEntStatus 3 } ::= { ntpEntStatus 3 }
ntpEntStatusActiveRefSourceId OBJECT-TYPE ntpEntStatusActiveRefSourceId OBJECT-TYPE
SYNTAX Unsigned32 ( 0..99999 ) SYNTAX Unsigned32 ( 0..99999 )
skipping to change at page 11, line 18 skipping to change at page 12, line 43
-- e.g. "ntp1.ptb.de" or "GPS" or "DCFi" ... -- e.g. "ntp1.ptb.de" or "GPS" or "DCFi" ...
-- maybe something like "RefClk(8)" = "hardware clock using driver 8" -- maybe something like "RefClk(8)" = "hardware clock using driver 8"
-- would be nice -- would be nice
::= { ntpEntStatus 5 } ::= { ntpEntStatus 5 }
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 as "The Time offset to the current selected reference time source
a string." 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"
::= { ntpEntStatus 6 } ::= { ntpEntStatus 6 }
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."
DEFVAL { 0 } DEFVAL { 0 }
::= { ntpEntStatus 7 } ::= { ntpEntStatus 7 }
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 instance." "The root dispersion of the running NTP entity."
-- e.g. "6.927" -- e.g. "6.927"
DEFVAL { "n/a" } DEFVAL { "n/a" }
::= { ntpEntStatus 8 } ::= { ntpEntStatus 8 }
ntpEntStatusEntityUptime OBJECT-TYPE ntpEntStatusEntityUptime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The uptime of the NTP entity in seconds." "The uptime of the NTP entity in seconds."
-- time since ntpd was (re-)started (not sysUptime!) -- time since ntpd was (re-)started (not sysUptime!)
DEFVAL { 0 } DEFVAL { 0 }
::= { ntpEntStatus 9 } ::= { ntpEntStatus 9 }
ntpEntStatusTime OBJECT-TYPE ntpEntStatusDateTime OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0 | 16)) SYNTAX NtpDateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current NTP time on the device, in 128-bit "The current NTP date/time on the device, in 128-bit
NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-04, NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
section 5: section 6:
It includes a 64-bit signed seconds field It includes a 64-bit signed seconds field
spanning 584 billion years and a 64-bit fraction spanning 584 billion years and a 64-bit fraction
field resolving .05 attosecond (i.e. 0.5e-18). field resolving .05 attosecond (i.e. 0.5e-18).
For convenience in mapping between formats, the For convenience in mapping between formats, the
seconds field is divided into a 32-bit era field seconds field is divided into a 32-bit era field
and a 32-bit timestamp field. and a 32-bit timestamp field.
If time is not syncronized this field shall be a If time is not syncronized this field shall be a
zero-length string. zero-length string.
skipping to change at page 12, line 40 skipping to change at page 14, line 16
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."
::= { ntpEntStatus 10 } ::= { ntpEntStatus 10 }
ntpEntStatusLeapSecond OBJECT-TYPE ntpEntStatusLeapSecond OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Date the next known leap second will occur" "Date the next known leap second will occur. If there is
no leap second announced then this object should be 0."
DEFVAL { 0 } DEFVAL { 0 }
::= { ntpEntStatus 11 } ::= { ntpEntStatus 11 }
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" "Direction of next known leap second. If there is no
leap second announced then this object should be 0."
DEFVAL { 0 } DEFVAL { 0 }
::= { ntpEntStatus 12 } ::= { ntpEntStatus 12 }
ntpEntStatusInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of NTP messages delivered to the
NTP entity from the transport service."
::= { ntpEntStatus 13 }
ntpEntStatusOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of NTP messages delivered to the
transport service by this NTP entity."
::= { ntpEntStatus 14 }
ntpEntStatusBadVersion OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of NTP messages which were delivered
to this NTP entity and were for an unsupported NTP
version."
::= { ntpEntStatus 15 }
ntpEntStatusProtocolError OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of NTP messages which were delivered
to this NTP entity and this entity was not able to
process due to an NTP protocol error."
::= { ntpEntStatus 16 }
ntpEntStatusNotifications OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of SNMP notifications which this NTP
entity has generated."
::= { ntpEntStatus 17 }
-- --
-- Section 3: The status of all currently mobilized associations -- Section 3: The status of all currently mobilized associations
-- --
ntpAssociationTable OBJECT-TYPE ntpAssociationTable OBJECT-TYPE
SYNTAX SEQUENCE OF NtpAssociationEntry SYNTAX SEQUENCE OF NtpAssociationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table of currently mobilized associations." "The table of currently mobilized associations."
skipping to change at page 13, line 33 skipping to change at page 16, line 10
INDEX { ntpAssocId } INDEX { ntpAssocId }
::= { ntpAssociationTable 1 } ::= { ntpAssociationTable 1 }
NtpAssociationEntry ::= SEQUENCE { NtpAssociationEntry ::= SEQUENCE {
ntpAssocId Unsigned32, ntpAssocId Unsigned32,
ntpAssocName DisplayString, ntpAssocName DisplayString,
ntpAssocRefId DisplayString, ntpAssocRefId DisplayString,
ntpAssocAddressType InetAddressType, ntpAssocAddressType InetAddressType,
ntpAssocAddress InetAddress, ntpAssocAddress InetAddress,
ntpAssocOffset DisplayString, ntpAssocOffset DisplayString,
ntpAssocStratum Integer32, ntpAssocStratum NtpStratum,
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
skipping to change at page 14, line 12 skipping to change at page 16, line 38
DESCRIPTION DESCRIPTION
"The hostname or other descriptive name for the association." "The hostname or other descriptive name for the association."
::= { ntpAssociationEntry 2 } ::= { ntpAssociationEntry 2 }
ntpAssocRefId OBJECT-TYPE ntpAssocRefId OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The refclock driver ID, if available." "The refclock driver ID, if available."
-- a refclock driver ID like "127.127.1.0" for non uni/multi/broadcast -- a refclock driver ID like "127.127.1.0" for non
-- associations -- uni/multi/broadcast associations
::= { ntpAssociationEntry 3 } ::= { ntpAssociationEntry 3 }
ntpAssocAddressType OBJECT-TYPE ntpAssocAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of address of the association." "The type of address of the association."
-- contains the type of address for uni/multi/broadcast associations -- contains the type of address for uni/multi/broadcast associations
::= { ntpAssociationEntry 4 } ::= { ntpAssociationEntry 4 }
skipping to change at page 14, line 44 skipping to change at page 17, line 22
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 Integer32 (1..16) 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
skipping to change at page 15, line 28 skipping to change at page 18, line 6
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
SYNTAX SEQUENCE OF NtpAssociationStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table of statistics for current associations."
::= { ntpAssociation 2 }
ntpAssociationStatisticsEntry OBJECT-TYPE
SYNTAX NtpAssociationStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table entry of statistics for current associations."
INDEX { ntpAssocId }
::= { ntpAssociationStatisticsTable 1 }
NtpAssociationStatisticsEntry ::= SEQUENCE {
ntpAssocStatInPkts Counter32,
ntpAssocStatOutPkts Counter32,
ntpAssocStatProtocolError Counter32
}
ntpAssocStatInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of NTP messages delivered to the
NTP entity from this association."
::= { ntpAssocStatisticsEntry 1 }
ntpAssocStatOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of NTP messages delivered to the
transport service by this NTP entity for this
association."
::= { ntpAssocStatisticsEntry 2 }
ntpAssocStatProtocolError OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of NTP messages which were delivered
to this NTP entity from this association and this entity
was not able to process due to an NTP protocol error."
::= { ntpAssocStatisticsEntry 3 }
-- --
-- Section 4: Control objects -- Section 4: Control objects
-- --
ntpEntHeartbeatInterval OBJECT-TYPE ntpEntHeartbeatInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval at which the ntpEntNotifHeartbeat notification should be "The interval at which the ntpEntNotifHeartbeat notification
sent, in seconds. If set to 0 and the srvNotifHeartbeat bit in should be sent, in seconds. If set to 0 and the
ntpEntNotifBits is 1 then ntpEntNotifHeartbeat is sent once." entNotifHeartbeat bit in ntpEntNotifBits is 1 then
ntpEntNotifHeartbeat is sent once."
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
srvNotifNotSync(1), entNotifModeChange(1),
srvNotifEntityStarted(2), entNotifStratumChange(2),
srvNotifEntityStopped(3), entNotifSyspeerChanged(3),
srvNotifStratumChange(4), entNotifAddAssociation(4),
srvNotifSyspeerChanged(5), entNotifRemoveAssociation(5),
srvNotifAddAssociation(6), entNotifConfigChanged(6),
srvNotifRemoveAssociation(7), entNotifLeapSecondAnnounced(7),
srvNotifConfigChanged(8), entNotifHeartbeat(8)
srvNotifLeapSecondAnnounced(9),
srvNotifHeartbeat(10)
} }
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."
::= { ntpEntControl 2 } ::= { ntpEntControl 2 }
-- --
-- Section 5: Notification objects -- Section 5: Notification objects
-- --
ntpEntNotifMessage OBJECT-TYPE ntpEntNotifMessage OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
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 text "Used as a payload object for all notifications. Holds a clear
event message." text event message."
DEFVAL { "no event" } DEFVAL { "no event" }
::= { ntpEntNotifObjects 1 } ::= { ntpEntNotifObjects 1 }
-- --
-- SNMP notification definitions -- SNMP notification definitions
-- --
ntpEntNotifications OBJECT IDENTIFIER ::= { ntpEntNotifPrefix 0 } ntpEntNotifications OBJECT IDENTIFIER ::= { ntpEntNotifPrefix 0 }
ntpEntNotifNotInSync NOTIFICATION-TYPE ntpEntNotifModeChange NOTIFICATION-TYPE
OBJECTS { ntpEntStatusCurrentModeVal } OBJECTS { ntpEntStatusCurrentModeVal }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when the NTP entity transistions to "The notification to be sent when the NTP entity changes mode,
not synchronised." including starting and stopping (if possible)"
::= { ntpEntNotifications 1 } ::= { ntpEntNotifications 1 }
ntpEntNotifEntityStarted NOTIFICATION-TYPE
OBJECTS { ntpEntNotifMessage }
STATUS current
DESCRIPTION
"The notification to be sent when NTP starts up."
::= { ntpEntNotifications 2 }
ntpEntNotifEntityStopped NOTIFICATION-TYPE
OBJECTS { ntpEntNotifMessage }
STATUS current
DESCRIPTION
"The notification to be sent when NTP stops."
::= { ntpEntNotifications 3 }
ntpEntNotifStratumChange NOTIFICATION-TYPE ntpEntNotifStratumChange NOTIFICATION-TYPE
OBJECTS { ntpEntStatusTime, 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 4 } ::= { ntpEntNotifications 2 }
ntpEntNotifSyspeerChanged NOTIFICATION-TYPE ntpEntNotifSyspeerChanged NOTIFICATION-TYPE
OBJECTS { ntpEntStatusTime, ntpEntStatusActiveRefSourceId, OBJECTS { ntpEntStatusDateTime, ntpEntStatusActiveRefSourceId,
ntpEntNotifMessage } ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when a (new) syspeer has been selected." "The notification to be sent when a (new) syspeer has been
::= { ntpEntNotifications 5 } selected."
::= { ntpEntNotifications 3 }
ntpEntNotifAddAssociation NOTIFICATION-TYPE ntpEntNotifAddAssociation NOTIFICATION-TYPE
OBJECTS { ntpEntStatusTime, ntpAssocName, ntpEntNotifMessage } OBJECTS { ntpEntStatusDateTime, ntpAssocName, ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when a new association is mobilized." "The notification to be sent when a new association is
::= { ntpEntNotifications 6 } mobilized."
::= { ntpEntNotifications 4 }
ntpEntNotifRemoveAssociation NOTIFICATION-TYPE ntpEntNotifRemoveAssociation NOTIFICATION-TYPE
OBJECTS { ntpEntStatusTime, ntpAssocName, ntpEntNotifMessage } OBJECTS { ntpEntStatusDateTime, ntpAssocName, ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when an association is demobilized." "The notification to be sent when an association is
::= { ntpEntNotifications 7 } demobilized."
::= { ntpEntNotifications 5 }
ntpEntNotifConfigChanged NOTIFICATION-TYPE ntpEntNotifConfigChanged NOTIFICATION-TYPE
OBJECTS { ntpEntStatusTime, ntpEntNotifMessage } OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when the NTP configuration has changed." "The notification to be sent when the NTP configuration has
changed."
-- e.g. when the system connected to the internet and was assigned -- e.g. when the system connected to the internet and was assigned
-- a new IP address by the ISPs DHCP server -- a new IP address by the ISPs DHCP server
::= { ntpEntNotifications 8 } ::= { ntpEntNotifications 6 }
ntpEntNotifLeapSecondAnnounced NOTIFICATION-TYPE ntpEntNotifLeapSecondAnnounced NOTIFICATION-TYPE
OBJECTS { ntpEntStatusTime, ntpEntNotifMessage } OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification to be sent when a leap second has been announced." "The notification to be sent when a leap second has been
::= { ntpEntNotifications 9 } announced."
::= { ntpEntNotifications 7 }
ntpEntNotifHeartbeat NOTIFICATION-TYPE ntpEntNotifHeartbeat NOTIFICATION-TYPE
OBJECTS { ntpEntStatusTime, ntpEntStatusCurrentModeVal, OBJECTS { ntpEntStatusDateTime, ntpEntStatusCurrentModeVal,
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 still ntpEntHeartbeatInterval) to indicate that the NTP entity is
alive." still alive."
::= { ntpEntNotifications 10 } ::= { ntpEntNotifications 8 }
-- --
-- Conformance/Compliance statements -- Conformance/Compliance statements
-- --
ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 6 } ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 6 }
ntpEntCompliances OBJECT IDENTIFIER ::= { ntpEntConformance 1 } ntpEntCompliances OBJECT IDENTIFIER ::= { ntpEntConformance 1 }
ntpEntGroups OBJECT IDENTIFIER ::= { ntpEntConformance 2 } ntpEntGroups OBJECT IDENTIFIER ::= { ntpEntConformance 2 }
ntpEntCompliance MODULE-COMPLIANCE ntpEntNTPCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement the NTP "The compliance statement for SNMP entities which use NTP and
MIB" implement the NTP MIB"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ntpEntObjectsGroup, ntpEntObjectsGroup1,
ntpEntObjectsGroup2,
ntpEntNotifPrefixGroup ntpEntNotifPrefixGroup
} }
::= { ntpEntCompliances 1 } ::= { ntpEntCompliances 1 }
ntpEntObjectsGroup OBJECT-GROUP ntpEntSNTPCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which use SNTP and
implement the NTP MIB"
MODULE -- this module
MANDATORY-GROUPS {
ntpEntObjectsGroup1
}
::= { ntpEntCompliances 2 }
ntpEntObjectsGroup1 OBJECT-GROUP
OBJECTS { OBJECTS {
ntpEntSoftwareName, ntpEntSoftwareName,
ntpEntSoftwareVersion, ntpEntSoftwareVersion,
ntpEntSoftwareVersionVal, ntpEntSoftwareVersionVal,
ntpEntSoftwareVendor, ntpEntSoftwareVendor,
ntpEntSystemType, ntpEntSystemType,
ntpEntStatusEntityUptime,
ntpEntStatusDateTime,
ntpAssocName,
ntpAssocRefId,
ntpAssocAddressType,
ntpAssocAddress
}
STATUS current
DESCRIPTION
"A collection of objects for the NTP MIB that all NTP
or SNTP entities should implement."
::= { ntpEntGroups 1 }
ntpEntObjectsGroup2 OBJECT-GROUP
OBJECTS {
ntpEntTimeResolution, ntpEntTimeResolution,
ntpEntTimeResolutionVal, ntpEntTimeResolutionVal,
ntpEntTimePrecision, ntpEntTimePrecision,
ntpEntTimePrecisionVal, ntpEntTimePrecisionVal,
ntpEntTimeDistance, ntpEntTimeDistance,
ntpEntStatusCurrentMode, ntpEntStatusCurrentMode,
ntpEntStatusCurrentModeVal, ntpEntStatusCurrentModeVal,
ntpEntStatusStratum, ntpEntStatusStratum,
ntpEntStatusActiveRefSourceId, ntpEntStatusActiveRefSourceId,
ntpEntStatusActiveRefSourceName, ntpEntStatusActiveRefSourceName,
ntpEntStatusActiveOffset, ntpEntStatusActiveOffset,
ntpEntStatusNumberOfRefSources, ntpEntStatusNumberOfRefSources,
ntpEntStatusDispersion, ntpEntStatusDispersion,
ntpEntStatusEntityUptime,
ntpEntStatusTime,
ntpEntStatusLeapSecond, ntpEntStatusLeapSecond,
ntpEntStatusLeapSecDirection, ntpEntStatusLeapSecDirection,
ntpAssocName, ntpEntStatusInPkts,
ntpAssocRefId, ntpEntStatusOutPkts,
ntpAssocAddressType, ntpEntStatusBadVersion,
ntpAssocAddress, ntpEntStatusProtocolError,
ntpEntStatusNotifications,
ntpAssocOffset, ntpAssocOffset,
ntpAssocStratum, ntpAssocStratum,
ntpAssocStatusJitter, ntpAssocStatusJitter,
ntpAssocStatusDelay, ntpAssocStatusDelay,
ntpAssocStatusDispersion, ntpAssocStatusDispersion,
ntpAssocStatInPkts,
ntpAssocStatOutPkts,
ntpAssocStatProtocolError,
ntpEntHeartbeatInterval, ntpEntHeartbeatInterval,
ntpEntNotifBits, ntpEntNotifBits,
ntpEntNotifMessage ntpEntNotifMessage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects for the NTP MIB" "A collection of objects for the NTP MIB that are optional
::= { ntpEntGroups 1 } for NTP or SNTP entities to implement."
::= { ntpEntGroups 2 }
ntpEntNotifPrefixGroup NOTIFICATION-GROUP ntpEntNotifPrefixGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
ntpEntNotifNotInSync, ntpEntNotifModeChange,
ntpEntNotifEntityStarted,
ntpEntNotifEntityStopped,
ntpEntNotifStratumChange, ntpEntNotifStratumChange,
ntpEntNotifSyspeerChanged, ntpEntNotifSyspeerChanged,
ntpEntNotifAddAssociation, ntpEntNotifAddAssociation,
ntpEntNotifRemoveAssociation, ntpEntNotifRemoveAssociation,
ntpEntNotifConfigChanged, ntpEntNotifConfigChanged,
ntpEntNotifLeapSecondAnnounced, ntpEntNotifLeapSecondAnnounced,
ntpEntNotifHeartbeat ntpEntNotifHeartbeat
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of notifications for the NTP MIB" "A collection of notifications for the NTP MIB"
::= { ntpEntGroups 2 } ::= { ntpEntGroups 3 }
END END
5. IANA Considerations 5. 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
---------- ----------------------- ---------- -----------------------
skipping to change at page 20, line 25 skipping to change at page 24, line 25
ntpSnmp { mib-2 XXX } ntpSnmp { mib-2 XXX }
RFC Ed. : the IANA is requested to assign a value for "XXX" under the 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 'mib-2' subtree and to record the assignment in the SMI Numbers
registry. When the assignment has been made, the RFC Editor is asked 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 to replace "XXX" (here and in the MIB module) with the assigned value
and to remove this note. and to remove this note.
6. Security Considerations 6. Security Considerations
All data objects in this MIB are read-only and therefore security is Most data objects in this MIB are read-only. The two read-write
managed by the implementation of the SNMP agent providing the data objects control notifications. The security provided by the
objects in this MIB. The general access management methods used for implementation of the SNMP agent providing the data objects in this
SNMP agents apply. 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.
7. References 7. References
7.1. Normative References 7.1. Normative References
[1] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, [1] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder,
Ed., "Structure of Management Information Version 2 (SMIv2)", Ed., "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
[2] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, [2] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder,
skipping to change at page 21, line 9 skipping to change at page 25, line 15
7.2. Informative References 7.2. Informative References
[4] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction [4] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
and Applicability Statements for Internet-Standard Management and Applicability Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
Authors' Addresses Authors' Addresses
Heiko Gerstung Heiko Gerstung
Meinberg Funkuhren Gmbh & Co. KG Meinberg Funkuhren Gmbh & Co. KG
Auf der Landwehr 22 Lange Wand 9
Bad Pyrmont 31812 Bad Pyrmont 31812
Germany Germany
Phone: +49 5281 9309 29 Phone: +49 5281 9309 25
Email: heiko.gerstung@meinberg.de Email: heiko.gerstung@meinberg.de
Chris Elliott Chris Elliott
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park 27709 Research Triangle Park 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
Email: chelliot@cisco.com Email: chelliot@cisco.com
 End of changes. 91 change blocks. 
163 lines changed or deleted 372 lines changed or added

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