idnits 2.17.1 draft-ietf-ntp-ntpv4-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 785. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 762. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 769. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 775. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 39 instances of too long lines in the document, the longest one being 107 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 2006) is 6489 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 4 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NTP H. Gerstung 3 Internet-Draft Meinberg 4 Expires: January 2, 2007 July 2006 6 Definitions of Managed Objects for Network Time Protocol Version 4 7 (NTPv4) 8 draft-ietf-ntp-ntpv4-mib-00 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on January 2, 2007. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 The Network Time Protocol (NTP) is used in networks of all types and 42 sizes for time synchronization of servers, workstations and other 43 networked equipment. As time synchronization is more and more a 44 mission critical service, standardized means for monitoring and 45 management of this subsystem of a networked host are required to 46 allow operators of such a service to setup a monitoring system that 47 is platform- and vendor-independant. This RFC draft provides a 48 standardized collection of data objects for monitoring the NTP 49 service of such a network participant and it is part of the NTP 50 Version 4 standardization effort. 52 Table of Contents 54 1. The Internet-Standard Management Framework . . . . . . . . . . 3 55 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Technical Description . . . . . . . . . . . . . . . . . . . . 3 57 4. MIB Definition . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 59 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 60 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 61 7.1. Normative References . . . . . . . . . . . . . . . . . . . 16 62 7.2. Informative References . . . . . . . . . . . . . . . . . . 17 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18 64 Intellectual Property and Copyright Statements . . . . . . . . . . 19 66 1. The Internet-Standard Management Framework 68 For a detailed overview of the documents that describe the current 69 Internet-Standard Management Framework, please refer to section 7 of 70 RFC3410 [4]. 72 Managed objects are accessed via a virtual information store, termed 73 the Management Information Base or MIB. MIB objects are generally 74 accessed through the Simple Network Management Protocol (SNMP). 75 Objects in the MIB are defined using the mechanisms defined in the 76 Structure of Management Information (SMI). This memo specifies a MIB 77 module that is compliant to the SMIv2, which is described in RFC2578 78 [1], RFC2579 [2] and RFC2580 [3]. 80 2. Introduction 82 The NTPv4 MIB Module is designed to allow SNMP to be used to monitor 83 and manage local NTP service instances. It provides a collection of 84 data objects that can be queried using the SNMP protocol and 85 represent the current status of the NTP service instance. This 86 includes general information about the NTP service instance itself 87 (vendor, product, version) as well as connectivity to upstream NTP 88 servers used as sources of reference time and to hardware reference 89 clocks like radio clocks. The most important values are included in 90 order to be able to detect failures before they can have an impact on 91 the overall time synchronization status of the network. 93 3. Technical Description 95 The NTPv4 MIB Module is divided into sections for general server 96 information, current NTP service status, status information of all 97 mobilized associations (e.g. unicast upstream time servers, multicast 98 or broadcast time references and hardware clocks) as well as SNMP 99 trap definitions for core events. 101 The general server information section contains static information 102 and can be queried to identify which NTP service implementation is 103 running on a host. This includes the vendor and product name of the 104 running NTP software as well as version information, hardware/os 105 platform identity and the time resolution of the underlying OS. 107 Section 2 (current NTP status) includes data objects that represent 108 the current operational status of the NTP service instance. 110 The third section contains data objects that represent the set of 111 time references ("associations") the NTP instance is currently 112 working with. 114 Certain important events can occur while the NTP instance is running. 115 The fourth section defines SNMP traps for a collection of the most 116 important ones ("core events") and additionally provides a heartbeat 117 trap as well as a test trap to allow management systems to test the 118 reception of NTP related traps as well as enable heartbeat-based 119 monitoring systems to assure that the NTP service is still up and 120 running. 122 4. MIB Definition 124 -- ************************************************************************** 125 -- 126 -- $Id: draft-ietf-ntp-ntpv4-mib-00.xml 1.7 2006/06/16 07:13:50Z heiko TRASH $ 127 -- $Name: SUBMIT_1 $ 128 -- 129 -- The Network Time Protocol Version 4 130 -- Management Information Base (MIB) 131 -- 132 -- Author: Heiko Gerstung (heiko.gerstung@meinberg.de) 133 -- for the Internet Engineering Task Force (IETF) 134 -- NTP Working Group (ntpwg) 135 -- 136 -- 137 -- ************************************************************************** 138 -- 139 -- $Log: draft-ietf-ntp-ntpv4-mib-00.xml $ 140 -- Revision 1.7 2006/06/16 07:13:50Z heiko 141 -- XML/RFC: 142 -- - added/changed comments about the to-be-done IANA SMI assignment 143 -- Revision 1.6 2006/06/16 07:04:43Z heiko 144 -- RFC/XML: 145 -- - phone number corrected 146 -- - removed unused references 147 -- MIB: 148 -- - added ntpSrvTimePrecision 149 -- - changed INTEGER objects to Integer32 150 -- - changed default value for ntpSrvStatusStratum from 99 to 16 151 -- - changed default value for ntpSrvStatusActiveRefclockId from 99 to 0 152 -- - changed object names to ntpSrvStatusActiveRefSourceName (from ntpSrvStatusActiveRefclockName) and to ntpSrvStatusNumberOfRefSources (from ntpSrvStatusNumberOfRefclocks) 153 -- - removed ntpSrvStatusAuthKeyId object 154 -- - added ntpSrvStatusDispersion to provide the current root dispersion 155 -- - major rework of section 3 (Status of associations) to compile cleanly 156 -- including: 157 -- - added dispersion to the association dataset 158 -- - renaming of objects 159 -- - added an index to the association table 160 -- - formal changes 161 -- - traps are now reverse mappable 162 -- - traps are now define with payload where applicable 163 -- - added compliance statements 164 -- Revision 1.5 2006/02/27 08:28:16Z heiko 165 -- - changed to RFC format and added header as well as 166 -- introduction and technical description 167 -- - added other necessary RFC components (copyright statement etc.) 168 -- Revision 1.4 2006/02/27 07:06:49Z heiko 169 -- - removed all objects with data type REAL 170 -- - everything that needs to be floating point is now defined as DisplayString 171 -- Revision 1.2 2006/01/23 08:58:11Z heiko 172 -- - changed the datatype of offset, jitter and delay objects from Integer32 173 -- to REAL 174 -- 175 -- ************************************************************************** 177 NTPv4-MIB DEFINITIONS ::= BEGIN 179 IMPORTS 180 MODULE-IDENTITY, OBJECT-TYPE , mib-2, TimeTicks, Integer32, NOTIFICATION-TYPE 181 FROM SNMPv2-SMI 182 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 183 FROM SNMPv2-CONF 184 DisplayString FROM SNMPv2-TC; 186 ntpSnmp MODULE-IDENTITY 187 LAST-UPDATED "200606190000Z" 188 ORGANIZATION "www.ietf.org" 189 CONTACT-INFO 190 " The IETF NTP Working Group (ntpwg)" 191 DESCRIPTION 192 " Management Information Base for NTP time servers" 193 REVISION "200606190000Z" 194 DESCRIPTION 195 "First Draft Version" 196 REVISION "200512190000Z" 197 DESCRIPTION 198 "revised edition (added traps and stuff)" 199 REVISION "200511160000Z" 200 DESCRIPTION 201 "Initial draft" 202 ::= { mib-2 XXX } 204 -- 205 -- Section 1: General Server information objects (static information) 206 -- 208 ntpSrvInfo OBJECT IDENTIFIER ::= { ntpSnmp 0 } 210 ntpSrvSoftwareName OBJECT-TYPE 211 SYNTAX DisplayString 212 MAX-ACCESS read-only 213 STATUS current 214 DESCRIPTION 215 "product name of the installed NTP version" 216 -- the product name of the running ntp implementation, e.g. "ntpd" 217 ::= { ntpSrvInfo 1 } 219 ntpSrvSoftwareVersion OBJECT-TYPE 220 SYNTAX DisplayString 221 MAX-ACCESS read-only 222 STATUS current 223 DESCRIPTION 224 "Software version of the installed NTP implementation" 225 -- full version string, e.g. "ntpd-4.2.0b@1.1433 ..." 226 ::= { ntpSrvInfo 2 } 228 ntpSrvSoftwareVersionVal OBJECT-TYPE 229 SYNTAX Integer32 (-2147483648..2147483647) 230 MAX-ACCESS read-only 231 STATUS current 232 DESCRIPTION 233 "Software version of installed NTP as an Integer32 value" 234 -- e.g. if version string is "4.2.0b" this could be translated into 4202 235 -- could be useful to find out if version of server a is newer or older 236 -- than version of server b (without too much string parsing trouble) 237 ::= { ntpSrvInfo 3 } 239 ntpSrvSoftwareVendor OBJECT-TYPE 240 SYNTAX DisplayString 241 MAX-ACCESS read-only 242 STATUS current 243 DESCRIPTION 244 "the vendor/author of the installed NTP version" 245 ::= { ntpSrvInfo 4 } 247 ntpSrvSystemType OBJECT-TYPE 248 SYNTAX DisplayString 249 MAX-ACCESS read-only 250 STATUS current 251 DESCRIPTION 252 "general hardware/os platform information" 253 -- e.g. "Linux 2.6.12 / x86" 254 -- freely configurable, default is OS Version / Hardware platform 255 ::= { ntpSrvInfo 5 } 257 ntpSrvTimeResolution OBJECT-TYPE 258 SYNTAX DisplayString 259 MAX-ACCESS read-only 260 STATUS current 261 DESCRIPTION 262 "string describing the time resolution of the running NTP 263 implementation" 264 -- e.g. "100 ns" 265 -- depends on the NTP implementation and the underlying OS. The current 266 -- resolution should be used, so if the OS only supports 10ms and ntpd is 267 -- capable of 1ns, the 10ms should be advertised 268 ::= { ntpSrvInfo 6 } 270 ntpSrvTimeResolutionVal OBJECT-TYPE 271 SYNTAX Integer32 272 MAX-ACCESS read-only 273 STATUS current 274 DESCRIPTION 275 "time resolution in integer format" 276 -- ntpSrvTimeResolution in Integer format 277 -- shows the resolution based on 1 second, e.g. "1ms" translates to 1000 278 ::= { ntpSrvInfo 7 } 280 ntpSrvTimePrecision OBJECT-TYPE 281 SYNTAX DisplayString 282 MAX-ACCESS read-only 283 STATUS current 284 DESCRIPTION 285 "string describing the precision with which the NTP server 286 implementation/OS manages its time base" 287 -- e.g. "-18" means 2^-18 = 0.000003814697265625 seconds 288 -- "-5" means 2^-5 = 0.03125 seconds 289 -- depends on the NTP implementation and the underlying OS. 290 ::= { ntpSrvInfo 8 } 292 ntpSrvTimePrecisionVal OBJECT-TYPE 293 SYNTAX Integer32 294 MAX-ACCESS read-only 295 STATUS current 296 DESCRIPTION 297 "precision in integer format" 298 -- ntpSrvTimePrecision in signed Integer format 299 -- shows the precision. A value of -5 would mean 2^-5 = 31.25 ms 300 ::= { ntpSrvInfo 9 } 302 ntpSrvTimeDistance OBJECT-TYPE 303 SYNTAX DisplayString 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "The distance from this NTP instance to the root time reference (stratum 0) source" 308 -- including the unit 309 -- e.g. "13.243 ms" 310 ::= { ntpSrvInfo 10 } 312 -- 313 -- Section 2: Current NTP status (dynamic information) 314 -- 315 ntpSrvStatus OBJECT IDENTIFIER ::= { ntpSnmp 1 } 317 ntpSrvStatusCurrentState OBJECT-TYPE 318 SYNTAX DisplayString 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "actual status of NTP as a string" 323 --- possible strings: 324 --- "not running" : NTP is not running 325 --- "not synchronized" : NTP is not synchronized to any time source 326 --- (stratum = 16) 327 --- "sync to local" : NTP is synchronized to own local clock 328 --- (degraded reliability) 329 --- "sync to refclock" : NTP is synchronized to a local hardware refclock 330 --- (e.g. GPS) 331 --- "sync to remote server" : NTP is synchronized to a remote NTP server 332 --- ("upstream" server) 333 ::= { ntpSrvStatus 1 } 335 ntpSrvStatusCurrentStateVal OBJECT-TYPE 336 SYNTAX INTEGER { 337 notRunning(0), 338 notSynchronized(1), 339 syncToLocal(2), 340 syncToRefclock(3), 341 syncToRemoteServer(4), 342 unknown(99) 343 } 345 MAX-ACCESS read-only 346 STATUS current 347 DESCRIPTION 348 "current state of the NTP as integer value" 350 -- see ntpSrvStatusCurrentState 351 DEFVAL { 99 } 352 ::= { ntpSrvStatus 2 } 354 ntpSrvStatusStratum OBJECT-TYPE 355 SYNTAX Integer32 (1..16) 356 MAX-ACCESS read-only 357 STATUS current 358 DESCRIPTION 359 "own stratum value" 360 -- should be stratum of syspeer + 1 (or 16 if no syspeer) 361 DEFVAL { 16 } 362 ::= { ntpSrvStatus 3 } 364 ntpSrvStatusActiveRefSourceId OBJECT-TYPE 365 SYNTAX Integer32 ( 0..99999 ) 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "the association ID of the current syspeer" 370 DEFVAL { 0 } 371 ::= { ntpSrvStatus 4 } 373 ntpSrvStatusActiveRefSourceName OBJECT-TYPE 374 SYNTAX DisplayString 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The hostname/descriptive name of the current reference source selected 379 as syspeer" 380 -- e.g. "ntp1.ptb.de" or "GPS" or "DCFi" ... 381 -- maybe something like "RefClk(8)" = "hardware clock using driver 8" 382 -- would be nice 383 ::= { ntpSrvStatus 5 } 385 ntpSrvStatusActiveOffset OBJECT-TYPE 386 SYNTAX DisplayString 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "Time offset to the current selected reference time source as string" 391 -- including unit, e.g. "0.032 ms" or "1.232 s" 392 ::= { ntpSrvStatus 6 } 394 ntpSrvStatusNumberOfRefSources OBJECT-TYPE 395 SYNTAX Integer32 (0..99) 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "Number of reference sources configured for NTP " 400 DEFVAL { 0 } 401 ::= { ntpSrvStatus 7 } 403 ntpSrvStatusDispersion OBJECT-TYPE 404 SYNTAX DisplayString 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "Root dispersion of the running NTP instance" 409 -- e.g. "6.927" 410 DEFVAL { "n/a" } 411 ::= { ntpSrvStatus 8 } 413 ntpSrvStatusServiceUptime OBJECT-TYPE 414 SYNTAX TimeTicks 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "Uptime of NTP service" 419 -- time since ntpd was (re-)started (not sysUptime!) 420 DEFVAL { 0 } 421 ::= { ntpSrvStatus 9 } 423 -- 424 -- Section 3: Status of all currently mobilized associations 425 -- 427 ntpAssociation OBJECT IDENTIFIER ::= { ntpSnmp 3 } 429 ntpAssociationTable OBJECT-TYPE 430 SYNTAX SEQUENCE OF NtpAssociationEntry 431 MAX-ACCESS not-accessible 432 STATUS current 433 DESCRIPTION 434 "Table of currently mobilized associations" 435 ::= { ntpAssociation 1 } 437 ntpAssociationEntry OBJECT-TYPE 438 SYNTAX NtpAssociationEntry 439 MAX-ACCESS not-accessible 440 STATUS current 441 DESCRIPTION 442 "Table entry of currently mobilized associations" 443 INDEX { ntpAssocIndex } 444 ::= { ntpAssociationTable 1 } 446 NtpAssociationEntry ::= SEQUENCE { 447 ntpAssocIndex Integer32, 448 ntpAssocId Integer32, 449 ntpAssocName DisplayString, 450 ntpAssocAddress DisplayString, 451 ntpAssocOffset DisplayString, 452 ntpAssocStatusJitter DisplayString, 453 ntpAssocStatusDelay DisplayString, 454 ntpAssocStatusDispersion DisplayString 455 } 457 ntpAssocIndex OBJECT-TYPE 458 SYNTAX Integer32 ( 0..99999 ) 459 MAX-ACCESS not-accessible 460 STATUS current 461 DESCRIPTION 462 "Association Index" 463 ::= { ntpAssociationEntry 1 } 465 ntpAssocId OBJECT-TYPE 466 SYNTAX Integer32 ( 0..99999 ) 467 MAX-ACCESS read-only 468 STATUS current 469 DESCRIPTION 470 "Association ID" 471 ::= { ntpAssociationEntry 2 } 473 ntpAssocName OBJECT-TYPE 474 SYNTAX DisplayString 475 MAX-ACCESS read-only 476 STATUS current 477 DESCRIPTION 478 "Hostname or other descriptive name for association" 479 ::= { ntpAssociationEntry 3 } 481 ntpAssocAddress OBJECT-TYPE 482 SYNTAX DisplayString 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "IP address (IPv4 or IPv6) of association OR refclock driver ID" 487 -- contains IP address of uni/multi/broadcast associations or 488 -- a refclock driver ID like "127.127.1.0" for other associations 489 ::= { ntpAssociationEntry 4 } 491 ntpAssocOffset OBJECT-TYPE 492 SYNTAX DisplayString 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "Time offset to the association as string" 497 -- including unit, e.g. "0.032 ms" or "1.232 s" 498 ::= { ntpAssociationEntry 5 } 500 ntpAssocStatusJitter OBJECT-TYPE 501 SYNTAX DisplayString 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "Jitter in miliseconds as string" 506 ::= { ntpAssociationEntry 6 } 508 ntpAssocStatusDelay OBJECT-TYPE 509 SYNTAX DisplayString 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "Network delay in miliseconds as string" 514 ::= { ntpAssociationEntry 7 } 516 ntpAssocStatusDispersion OBJECT-TYPE 517 SYNTAX DisplayString 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "Root dispersion of the association" 522 -- e.g. "6.927" 523 ::= { ntpAssociationEntry 8 } 525 -- 526 -- Section 4: Server SNMP trap definitions 527 -- 529 ntpSrvNotifications OBJECT IDENTIFIER ::= { ntpSnmp 4 } 530 ntpSrvTraps OBJECT IDENTIFIER ::= { ntpSrvNotifications 0 } 532 ntpSrvTrapNotSync NOTIFICATION-TYPE 533 OBJECTS { ntpSrvStatusCurrentStateVal } 534 STATUS current 535 DESCRIPTION 536 "trap to be sent when NTP is not synchronised " 537 ::= { ntpSrvTraps 1 } 539 ntpSrvTrapServiceStarted NOTIFICATION-TYPE 540 OBJECTS { ntpSrvTrapMessage } 541 STATUS current 542 DESCRIPTION 543 "trap to be sent when NTP starts up " 544 ::= { ntpSrvTraps 2 } 546 ntpSrvTrapServiceStopped NOTIFICATION-TYPE 547 OBJECTS { ntpSrvTrapMessage } 548 STATUS current 549 DESCRIPTION 550 "trap to be sent when NTP stopps " 551 ::= { ntpSrvTraps 3 } 553 ntpSrvTrapStratumChange NOTIFICATION-TYPE 554 OBJECTS { ntpSrvStatusStratum, ntpSrvTrapMessage } 555 STATUS current 556 DESCRIPTION 557 "trap to be sent when stratum level of NTP changes" 558 ::= { ntpSrvTraps 4 } 560 ntpSrvTrapSyspeerChanged NOTIFICATION-TYPE 561 OBJECTS { ntpSrvStatusActiveRefSourceId, ntpSrvTrapMessage } 562 STATUS current 563 DESCRIPTION 564 "trap to be sent when a (new) syspeer has been selected" 565 ::= { ntpSrvTraps 5 } 567 ntpSrvTrapAddAssociation NOTIFICATION-TYPE 568 OBJECTS { ntpAssocId, ntpSrvTrapMessage } 569 STATUS current 570 DESCRIPTION 571 "trap to be sent when a new association is mobilized" 572 ::= { ntpSrvTraps 6 } 574 ntpSrvTrapRemoveAssociation NOTIFICATION-TYPE 575 OBJECTS { ntpAssocId, ntpSrvTrapMessage } 576 STATUS current 577 DESCRIPTION 578 "trap to be sent when an association is demobilized" 579 ::= { ntpSrvTraps 7 } 581 ntpSrvTrapConfigChanged NOTIFICATION-TYPE 582 OBJECTS { ntpSrvTrapMessage } 583 STATUS current 584 DESCRIPTION 585 "trap to be sent when NTP configuration has changed" 586 -- e.g. when the system connected to the internet and was assigned 587 -- a new IP address by the ISPs DHCP server 588 ::= { ntpSrvTraps 8 } 590 ntpSrvTrapLeapSecondAnnounced NOTIFICATION-TYPE 591 OBJECTS { ntpSrvTrapMessage } 592 STATUS current 593 DESCRIPTION 594 "trap to be sent when a leap second has been announced " 595 ::= { ntpSrvTraps 9 } 597 ntpSrvTrapHeartbeat NOTIFICATION-TYPE 598 OBJECTS { ntpSrvTrapMessage } 599 STATUS current 600 DESCRIPTION 601 "trap to be sent periodically to indicate that the NTP server 602 is still alive " 603 ::= { ntpSrvTraps 88 } 605 ntpSrvTrapTestNotification NOTIFICATION-TYPE 606 OBJECTS { ntpSrvTrapMessage } 607 STATUS current 608 DESCRIPTION 609 "trap to be sent when a test notification has been requested " 610 ::= { ntpSrvTraps 99 } 612 ntpSrvTrapMessage OBJECT-TYPE 613 SYNTAX DisplayString 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "used as a payload object for all traps, holds a clear text event message" 618 DEFVAL { "no event" } 619 ::= { ntpSrvTraps 100 } 621 -- 622 -- Conformance/Compliance statements 623 -- 625 ntpSrvConformance OBJECT IDENTIFIER ::= { ntpSnmp 90 } 626 ntpSrvCompliances OBJECT IDENTIFIER ::= { ntpSrvConformance 1 } 627 ntpSrvGroups OBJECT IDENTIFIER ::= { ntpSrvConformance 2 } 629 ntpSrvCompliance MODULE-COMPLIANCE 630 STATUS current 631 DESCRIPTION 632 "The compliance statement for SNMP entities which implement version 2 633 of the Server MIB" 634 MODULE -- this module 635 MANDATORY-GROUPS { 636 ntpSrvObjectsGroup, 637 ntpSrvTrapsGroup 639 } 640 ::= { ntpSrvCompliances 1 } 642 ntpSrvObjectsGroup OBJECT-GROUP 643 OBJECTS { 644 ntpSrvSoftwareName, 645 ntpSrvSoftwareVersion, 646 ntpSrvSoftwareVersionVal, 647 ntpSrvSoftwareVendor, 648 ntpSrvSystemType, 649 ntpSrvTimeResolution, 650 ntpSrvTimeResolutionVal, 651 ntpSrvTimePrecision, 652 ntpSrvTimePrecisionVal, 653 ntpSrvTimeDistance, 654 ntpSrvStatusCurrentState, 655 ntpSrvStatusCurrentStateVal, 656 ntpSrvStatusStratum, 657 ntpSrvStatusActiveRefSourceId, 658 ntpSrvStatusActiveRefSourceName, 659 ntpSrvStatusActiveOffset, 660 ntpSrvStatusNumberOfRefSources, 661 ntpSrvStatusDispersion, 662 ntpSrvStatusServiceUptime, 663 ntpAssocId, 664 ntpAssocName, 665 ntpAssocAddress, 666 ntpAssocOffset, 667 ntpAssocStatusJitter, 668 ntpAssocStatusDelay, 669 ntpAssocStatusDispersion, 670 ntpSrvTrapMessage 671 } 672 STATUS current 673 DESCRIPTION 674 "The collection of objects for the Server MIB" 675 ::= { ntpSrvGroups 1 } 677 ntpSrvTrapsGroup NOTIFICATION-GROUP 678 NOTIFICATIONS { 679 ntpSrvTrapNotSync, 680 ntpSrvTrapServiceStarted, 681 ntpSrvTrapServiceStopped, 682 ntpSrvTrapStratumChange, 683 ntpSrvTrapSyspeerChanged, 684 ntpSrvTrapAddAssociation, 685 ntpSrvTrapRemoveAssociation, 686 ntpSrvTrapConfigChanged, 687 ntpSrvTrapLeapSecondAnnounced, 688 ntpSrvTrapHeartbeat, 689 ntpSrvTrapTestNotification 690 } 691 STATUS current 692 DESCRIPTION 693 "The collection of traps for the Server MIB" 694 ::= { ntpSrvGroups 2 } 696 END 698 5. IANA Considerations 700 The MIB module in this document uses the following IANA-assigned 701 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 703 Descriptor OBJECT IDENTIFIER value 704 ---------- ----------------------- 706 ntpSnmp { mib-2 XXX } 708 RFC Ed. : the IANA is requested to assign a value for "XXX" under the 709 'mib-2' subtree and to record the assignment in the SMI Numbers 710 registry. When the assignment has been made, the RFC Editor is asked 711 to replace "XXX" (here and in the MIB module) with the assigned value 712 and to remove this note. 714 6. Security Considerations 716 All data objects in this MIB are read-only and therefore security is 717 managed by the implementation of the SNMP agent providing the data 718 objects in this MIB. The general access management methods used for 719 SNMP agents apply. 721 7. References 723 7.1. Normative References 725 [1] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, 726 Ed., "Structure of Management Information Version 2 (SMIv2)", 727 STD 58, RFC 2578, April 1999. 729 [2] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, 730 Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, 731 April 1999. 733 [3] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance 734 Statements for SMIv2", STD 58, RFC 2580, April 1999. 736 7.2. Informative References 738 [4] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction 739 and Applicability Statements for Internet-Standard Management 740 Framework", RFC 3410, December 2002. 742 Author's Address 744 Heiko Gerstung 745 Meinberg Funkuhren Gmbh & Co. KG 746 Auf der Landwehr 22 747 Bad Pyrmont 31812 748 Germany 750 Phone: +49 5281 9309 25 751 Email: heiko.gerstung@meinberg.de 753 Intellectual Property Statement 755 The IETF takes no position regarding the validity or scope of any 756 Intellectual Property Rights or other rights that might be claimed to 757 pertain to the implementation or use of the technology described in 758 this document or the extent to which any license under such rights 759 might or might not be available; nor does it represent that it has 760 made any independent effort to identify any such rights. Information 761 on the procedures with respect to rights in RFC documents can be 762 found in BCP 78 and BCP 79. 764 Copies of IPR disclosures made to the IETF Secretariat and any 765 assurances of licenses to be made available, or the result of an 766 attempt made to obtain a general license or permission for the use of 767 such proprietary rights by implementers or users of this 768 specification can be obtained from the IETF on-line IPR repository at 769 http://www.ietf.org/ipr. 771 The IETF invites any interested party to bring to its attention any 772 copyrights, patents or patent applications, or other proprietary 773 rights that may cover technology that may be required to implement 774 this standard. Please address the information to the IETF at 775 ietf-ipr@ietf.org. 777 Disclaimer of Validity 779 This document and the information contained herein are provided on an 780 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 781 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 782 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 783 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 784 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 785 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 787 Copyright Statement 789 Copyright (C) The Internet Society (2006). This document is subject 790 to the rights, licenses and restrictions contained in BCP 78, and 791 except as set forth therein, the authors retain all their rights. 793 Acknowledgment 795 Funding for the RFC Editor function is currently provided by the 796 Internet Society.