1
2-- *****************************************************************
3-- CISCO-NTP-MIB.my:  NTP MIB
4--
5-- February 2000, Vinod B C
6--
7-- Copyright (c) 2000, 2002-2003, 2006 by cisco Systems, Inc.
8-- All rights reserved.
9--
10-- *****************************************************************
11
12CISCO-NTP-MIB DEFINITIONS ::= BEGIN
13
14IMPORTS
15    MODULE-IDENTITY,
16    OBJECT-TYPE,
17    NOTIFICATION-TYPE,
18    Integer32,
19    IpAddress,
20    Gauge32,
21    Unsigned32
22        FROM SNMPv2-SMI
23    MODULE-COMPLIANCE,
24    OBJECT-GROUP,
25    NOTIFICATION-GROUP
26        FROM SNMPv2-CONF
27    TEXTUAL-CONVENTION,
28    TruthValue,
29    RowStatus
30        FROM SNMPv2-TC
31    InetAddress,
32    InetAddressType
33        FROM INET-ADDRESS-MIB
34    ciscoMgmt
35        FROM CISCO-SMI;
36
37
38ciscoNtpMIB MODULE-IDENTITY
39    LAST-UPDATED    "200607310000Z"
40    ORGANIZATION    "Cisco Systems, Inc."
41    CONTACT-INFO
42            "Cisco Systems
43            Customer Service
44
45            Postal: 170 W. Tasman Drive
46            San Jose, CA 95134
47            USA
48
49            Tel: +1 800 553-NETS
50
51            E-mail: cs-snmp@cisco.com"
52    DESCRIPTION
53            "This MIB module defines a MIB which provides
54            mechanisms to monitor an NTP server.
55
56            The MIB is derived from the Technical Report
57            #Management of the NTP with SNMP# TR No. 98-09
58            authored by A.S. Sethi and Dave Mills in the
59            University of Delaware.
60
61            Below is a brief overview of NTP system architecture
62            and implementation model. This will help understand
63            the objects defined below and their relationships.
64
65            NTP Intro:
66            The Network Time Protocol (NTP) Version 3, is used to
67            synchronize timekeeping among a set of distributed
68            time servers and clients.  The service model is based
69            on a returnable-time design which depends only on
70            measured clock offsets, but does not require reliable
71            message delivery.  The synchronization subnet uses a
72            self-organizing, hierarchical master-slave
73            configuration, with synchronization paths determined
74            by a minimum-weight spanning tree.  While multiple
75            masters (primary servers) may exist, there is no
76            requirement for an election protocol.
77
78            System Archiecture:
79            In the NTP model a number of primary reference
80            sources, synchronized by wire or radio to national
81            standards, are connected to widely accessible
82            resources, such as backbone gateways, and operated as
83            primary time servers.  The purpose of NTP is to convey
84            timekeeping information from these servers to other
85            time servers via the Internet and also to cross-check
86            clocks and mitigate errors due to equipment or
87            propagation failures.  Some number of local-net hosts
88            or gateways, acting as secondary time servers, run NTP
89            with one or more of the primary servers.  In order to
90            reduce the protocol overhead, the secondary servers
91            distribute time via NTP to the remaining local-net
92            hosts.  In the interest of reliability, selected hosts
93            can be equipped with less accurate but less expensive
94            radio clocks and used for backup in case of failure of
95            the primary and/or secondary servers or communication
96            paths between them.
97
98            NTP is designed to produce three products: clock
99            offset, round-trip delay and dispersion, all of which
100            are relative to a selected reference clock.  Clock
101            offset represents the amount to adjust the local clock
102            to bring it into correspondence with the reference
103            clock.  Roundtrip delay provides the capability to
104            launch a message to arrive at the reference clock at a
105            specified time.  Dispersion represents the maximum
106            error of the local clock relative to the reference
107            clock.  Since most host time servers will synchronize
108            via another peer time server, there are two components
109            in each of these three products, those determined by
110            the peer relative to the primary reference source of
111            standard time and those measured by the host relative
112            to the peer.  Each of these components are maintained
113            separately in the protocol in order to facilitate
114            error control and management of the subnet itself.
115            They provide not only precision measurements of offset
116            and delay, but also definitive maximum error bounds,
117            so that the user interface can determine not only the
118            time, but the quality of the time as well.
119
120            Implementation Model:
121            In what may be the most common client/server model a
122            client sends an NTP message to one or more servers and
123            processes the replies as received.  The server
124            interchanges addresses and ports, overwrites certain
125            fields in the message, recalculates the checksum and
126            returns the message immediately.  Information included
127            in the NTP message allows the client to determine the
128            server time with respect to local time and adjust the
129            local clock accordingly.  In addition, the message
130            includes information to calculate the expected
131            timekeeping accuracy and reliability, as well as
132            select the best from possibly several servers.
133
134            While the client/server model may suffice for use on
135            local nets involving a public server and perhaps many
136            workstation clients, the full generality of NTP
137            requires distributed participation of a number of
138            client/servers or peers arranged in a dynamically
139            reconfigurable, hierarchically distributed
140            configuration.  It also requires sophisticated
141            algorithms for association management, data
142            manipulation and local-clock control.
143
144            Glossary:
145            1. Host: Refers to an instantiation of the NTP
146                    protocol on a local processor.
147            2. Peer: Refers to an instantiation of the NTP
148                    protocol on a remote processor connected by
149                    a network path from the local host."
150    REVISION        "200607310000Z"
151    DESCRIPTION
152            "Added ciscoNtpSysExtGroup and ciscoNtpSrvNotifGroup groups
153             to support monitoring of NTP server status.
154             ciscoNtpMIBComplianceRev3 is deprecated and replaced
155             by ciscoNtpMIBComplianceRev4."
156    REVISION        "200407230000Z"
157    DESCRIPTION
158            "Added cntpPeersPeerName and cntpPeersPeerType
159            objects to cntpPeerVarTable."
160    REVISION        "200307290000Z"
161    DESCRIPTION
162            "Added cntpPeersPrefPeer object to
163            cntpPeersVarTable."
164    REVISION        "200307070000Z"
165    DESCRIPTION
166            "ciscoNtpPeersGroup is deprecated by
167            ciscoNtpPeersGroupRev1.
168            ciscoNtpMIBCompliance is deprecated by
169            ciscoNtpMIBComplianceRev1."
170    REVISION        "200202200000Z"
171    DESCRIPTION
172            "cntpPeersUpdateTime is deprecated by
173            cntpPeersUpdateTimeRev1."
174    REVISION        "200006160000Z"
175    DESCRIPTION
176            "Initial version of this MIB module."
177          ::= { ciscoMgmt 168 }
178
179
180-- The various groups defined within this MIB definition:
181ciscoNtpMIBNotifs       OBJECT IDENTIFIER ::= { ciscoNtpMIB 0 }
182ciscoNtpMIBObjects      OBJECT IDENTIFIER ::= { ciscoNtpMIB 1 }
183ciscoNtpMIBConformance  OBJECT IDENTIFIER ::= { ciscoNtpMIB 2 }
184
185cntpSystem  OBJECT IDENTIFIER
186    ::= { ciscoNtpMIBObjects 1 }
187
188cntpPeers  OBJECT IDENTIFIER
189    ::= { ciscoNtpMIBObjects 2 }
190
191cntpFilter  OBJECT IDENTIFIER
192    ::= { ciscoNtpMIBObjects 3 }
193
194-- Textual Conventions
195
196NTPTimeStamp ::= TEXTUAL-CONVENTION
197    STATUS          current
198    DESCRIPTION
199            "NTP timestamps are represented as a 64-bit
200            unsigned fixed-point number, in seconds relative to
201            00:00 on 1 January 1900.  The integer part is in the
202            first 32 bits and the fraction part is in the last
203            32 bits."
204
205    REFERENCE
206            "D.L. Mills, 'Network Time Protocol (Version 3)',
207                RFC-1305, March 1992, Section 3.1"
208    SYNTAX          OCTET STRING (SIZE (8))
209
210NTPLeapIndicator ::= TEXTUAL-CONVENTION
211    STATUS          current
212    DESCRIPTION
213            "This is a two-bit code warning of an impending leap
214            second to be inserted in the NTP timescale.  The bits
215            are set before 23:59 on the day of insertion and reset
216            after 00:00 on the following day.  This causes the
217            number of seconds (rollover interval) in the day of
218            insertion to be increased or decreased by one.  The two
219            bits are coded as below,
220            00, no warning
221            01, last minute has 61 seconds
222            10, last minute has 59 seconds
223            11, alarm condition (clock not synchronized)"
224
225    REFERENCE
226            "D.L. Mills, 'Network Time Protocol(Version 3)',
227                RFC-1305, March 1992, Section 3.2.1"
228    SYNTAX          INTEGER  {
229                        noWarning(0),
230                        addSecond(1),
231                        subtractSecond(2),
232                        alarm(3)
233                    }
234
235NTPSignedTimeValue ::= TEXTUAL-CONVENTION
236    STATUS          current
237    DESCRIPTION
238            "The time in seconds that could represent signed
239            quantities like time delay with respect to some
240            source.  This textual-convention is specific to Cisco
241            implementation of NTP where 32-bit integers are used
242            for such quantities.  The signed integer part is in
243            the first 16 bits and the fraction part is in the
244            last 16 bits."
245
246    REFERENCE
247            "D.L. Mills, 'Network Time Protocol (Version 3)',
248                RFC-1305, March 1992, Sections 2,  3.2.1"
249    SYNTAX          OCTET STRING (SIZE (4))
250
251NTPUnsignedTimeValue ::= TEXTUAL-CONVENTION
252    STATUS          current
253    DESCRIPTION
254            "The time in seconds that could represent unsigned
255            quantities like maximum error of the local clock
256            with respect to some source.  This textual-convention
257            is specific to Cisco implementation of NTP where
258            32-bit integers are used for such quantities.  The
259            unsigned integer part is in the first 16 bits and the
260            fraction part is in the last 16 bits."
261
262    REFERENCE
263            "D.L. Mills, 'Network Time Protocol (Version 3)',
264                RFC-1305, March 1992, Sections 2, 3.2.1"
265    SYNTAX          OCTET STRING (SIZE (4))
266
267NTPStratum ::= TEXTUAL-CONVENTION
268    STATUS          current
269    DESCRIPTION
270            "Indicates the stratum of the clock.  The stratum
271            defines the accuracy of a time server.  Higher the
272            stratum, lower the accuracy.
273            0, unspecified
274            1, primary reference (e.g., calibrated atomic clock,
275               radio clock)
276            2-255, secondary reference (via NTP)"
277
278    REFERENCE
279            "D.L. Mills, 'Network Time Protocol (Version 3)',
280                RFC-1305, March 1992, Section 2.2"
281    SYNTAX          Integer32 (0..255 )
282
283NTPRefId ::= TEXTUAL-CONVENTION
284    STATUS          current
285    DESCRIPTION
286            "The reference clock identifier.  In the case of
287            stratum 0 (unspecified) or stratum 1 (primary
288            reference source), this is a four-octet,
289            left-justified, zero-padded ASCII string as defined
290            in RFC-1305.  In the case of stratum 2 and greater
291            (secondary reference) this is the four-octet Internet
292            address of the peer selected for synchronization.
293
294            Some examples of stratum 0 identifiers are,
295            DCN, DCN routing protocol
296            NIST, NIST public modem
297            TSP, TSP time protocol
298            DTS, Digital Time Service
299
300            Some examples of stratum 1 identifiers are,
301            ATOM, Atomic clock (calibrated)
302            VLF, VLF radio (OMEGA,, etc.)
303            LORC, LORAN-C radionavigation
304            GOES, GOES UHF environment satellite
305            GPS, GPS UHF satellite positioning"
306
307    REFERENCE
308            "D.L. Mills, Network Time Protocol (Version 3)',
309                RFC-1305, March 1992, Section 3.2.1"
310    SYNTAX          OCTET STRING (SIZE (4))
311
312NTPPollInterval ::= TEXTUAL-CONVENTION
313    STATUS          current
314    DESCRIPTION
315            "The minimum interval between transmitted NTP
316            messages, in seconds as a power of two.  For
317            instance, a value of six indicates a minimum
318            interval of 64 seconds."
319    SYNTAX          Integer32 (-20..20 )
320
321NTPAssocIdentifier ::= TEXTUAL-CONVENTION
322    STATUS          current
323    DESCRIPTION
324            "The association identifier of the peer.  Every peer
325            with which an NTP server is associated with is
326            identified by an association identifier."
327    SYNTAX          Integer32 (0..2147483647 )
328
329-- System Group
330cntpSysLeap OBJECT-TYPE
331    SYNTAX          NTPLeapIndicator
332    MAX-ACCESS      read-write
333    STATUS          current
334    DESCRIPTION
335            "Two-bit code warning of an impending leap second to
336            be inserted in the NTP timescale. This object can be
337            set only when the cntpSysStratum has a value of 1."
338    ::= { cntpSystem 1 }
339
340cntpSysStratum OBJECT-TYPE
341    SYNTAX          NTPStratum
342    MAX-ACCESS      read-write
343    STATUS          current
344    DESCRIPTION
345            "The stratum of the local clock. If the value is set
346            to 1, i.e., this is a primary reference, then the
347            Primary-Clock procedure described in Section 3.4.6,
348            in RFC-1305 is invoked."
349    ::= { cntpSystem 2 }
350
351cntpSysPrecision OBJECT-TYPE
352    SYNTAX          Integer32 (-20..20 )
353    MAX-ACCESS      read-only
354    STATUS          current
355    DESCRIPTION
356            "Signed integer indicating the precision
357            of the system clock, in seconds to the nearest
358            power of two.  The value must be rounded to the
359            next larger power of two; for instance, a 50-Hz
360            (20 ms) or 60-Hz (16.67 ms) power-frequency clock
361            would be assigned the value -5 (31.25 ms), while a
362            1000-Hz (1 ms) crystal-controlled clock would be
363            assigned the value -9 (1.95 ms)."
364    ::= { cntpSystem 3 }
365
366cntpSysRootDelay OBJECT-TYPE
367    SYNTAX          NTPSignedTimeValue
368    UNITS           "seconds"
369    MAX-ACCESS      read-only
370    STATUS          current
371    DESCRIPTION
372            "A signed fixed-point number indicating the total
373            round-trip delay in seconds, to the primary reference
374            source at the root of the synchronization subnet."
375    REFERENCE
376            "D.L. Mills, 'Network Time Protocol (Version 3)',
377                RFC-1305, March 1992, Sections 2.2, 3.2.1"
378    ::= { cntpSystem 4 }
379
380cntpSysRootDispersion OBJECT-TYPE
381    SYNTAX          NTPUnsignedTimeValue
382    UNITS           "seconds"
383    MAX-ACCESS      read-only
384    STATUS          current
385    DESCRIPTION
386            "The maximum error in seconds, relative to the
387            primary reference source at the root of the
388            synchronization subnet.  Only positive values greater
389            than zero are possible."
390    REFERENCE
391            "D.L. Mills, 'Network Time Protocol (Version 3)',
392                RFC-1305, March 1992, Sections 2, 2.2, 3.2.1"
393    ::= { cntpSystem 5 }
394
395cntpSysRefId OBJECT-TYPE
396    SYNTAX          NTPRefId
397    MAX-ACCESS      read-only
398    STATUS          current
399    DESCRIPTION     "The reference identifier of the local clock."
400    ::= { cntpSystem 6 }
401
402cntpSysRefTime OBJECT-TYPE
403    SYNTAX          NTPTimeStamp
404    MAX-ACCESS      read-only
405    STATUS          current
406    DESCRIPTION
407            "The local time when the local clock was last
408            updated.  If the local clock has never been
409            synchronized, the value is zero."
410    ::= { cntpSystem 7 }
411
412cntpSysPoll OBJECT-TYPE
413    SYNTAX          NTPPollInterval
414    MAX-ACCESS      read-only
415    STATUS          current
416    DESCRIPTION
417            "The interval at which the NTP server polls other NTP
418            servers to synchronize its clock."
419    ::= { cntpSystem 8 }
420
421cntpSysPeer OBJECT-TYPE
422    SYNTAX          NTPAssocIdentifier
423    MAX-ACCESS      read-only
424    STATUS          current
425    DESCRIPTION
426            "The current synchronization source.  This will
427            contain the unique association identifier
428            cntpPeersAssocId of the corresponding peer entry in
429            the cntpPeersVarTable of the peer acting as the
430            synchronization source.  If there is no peer, the
431            value will be 0."
432    ::= { cntpSystem 9 }
433
434cntpSysClock OBJECT-TYPE
435    SYNTAX          NTPTimeStamp
436    MAX-ACCESS      read-only
437    STATUS          current
438    DESCRIPTION
439            "The current local time.  Local time is derived from
440            the hardware clock of the particular machine and
441            increments at intervals depending on the design used."
442    ::= { cntpSystem 10 }
443
444cntpSysSrvStatus OBJECT-TYPE
445    SYNTAX          INTEGER  {
446                        unknown(1),
447                        notRunning(2),
448                        notSynchronized(3),
449                        syncToLocal(4),
450                        syncToRefclock(5),
451                        syncToRemoteServer(6)
452                    }
453    MAX-ACCESS      read-only
454    STATUS          current
455    DESCRIPTION
456            "Current state of the NTP server with values coded as follows:
457            1: server status is unknown
458            2: server is not running
459            3: server is not synchronized to any time source
460            4: server is synchronized to its own local clock
461            5: server is synchronized to a local hardware refclock (e.g. GPS)
462            6: server is synchronized to a remote NTP server"
463    DEFVAL          { unknown }
464    ::= { cntpSystem 11 }
465-- Peers Group
466--
467
468--
469-- Peer Variables Table
470
471cntpPeersVarTable OBJECT-TYPE
472    SYNTAX          SEQUENCE OF CntpPeersVarEntry
473    MAX-ACCESS      not-accessible
474    STATUS          current
475    DESCRIPTION
476            "This table provides information on the peers with
477            which the local NTP server has associations.  The
478            peers are also NTP servers but running on different
479            hosts."
480    ::= { cntpPeers 1 }
481
482cntpPeersVarEntry OBJECT-TYPE
483    SYNTAX          CntpPeersVarEntry
484    MAX-ACCESS      not-accessible
485    STATUS          current
486    DESCRIPTION
487            "Each peers' entry provides NTP information retrieved
488            from a particular peer NTP server.  Each peer is
489            identified by a unique association identifier.
490
491            Entries are automatically created when the user
492            configures the NTP server to be associated with remote
493            peers.  Similarly entries are deleted when the user
494            removes the peer association from the NTP server.
495
496            Entries can also be created by the management station
497            by setting values for the following objects:
498            cntpPeersPeerAddress or cntpPeersPeerName,
499            cntpPeersHostAddress and
500            cntpPeersMode and making the cntpPeersEntryStatus as
501            active(1).  At the least, the management station has
502            to set a value for cntpPeersPeerAddress or
503            cntpPeersPeerName to make the row active."
504    INDEX           { cntpPeersAssocId }
505    ::= { cntpPeersVarTable 1 }
506
507CntpPeersVarEntry ::= SEQUENCE {
508        cntpPeersAssocId            NTPAssocIdentifier,
509        cntpPeersConfigured         TruthValue,
510        cntpPeersPeerAddress        IpAddress,
511        cntpPeersPeerPort           Integer32,
512        cntpPeersHostAddress        IpAddress,
513        cntpPeersHostPort           Integer32,
514        cntpPeersLeap               NTPLeapIndicator,
515        cntpPeersMode               INTEGER ,
516        cntpPeersStratum            NTPStratum,
517        cntpPeersPeerPoll           NTPPollInterval,
518        cntpPeersHostPoll           NTPPollInterval,
519        cntpPeersPrecision          Integer32,
520        cntpPeersRootDelay          NTPSignedTimeValue,
521        cntpPeersRootDispersion     NTPUnsignedTimeValue,
522        cntpPeersRefId              NTPRefId,
523        cntpPeersRefTime            NTPTimeStamp,
524        cntpPeersOrgTime            NTPTimeStamp,
525        cntpPeersReceiveTime        NTPTimeStamp,
526        cntpPeersTransmitTime       NTPTimeStamp,
527        cntpPeersUpdateTime         Integer32,
528        cntpPeersReach              Integer32,
529        cntpPeersTimer              Integer32,
530        cntpPeersOffset             NTPSignedTimeValue,
531        cntpPeersDelay              NTPSignedTimeValue,
532        cntpPeersDispersion         NTPUnsignedTimeValue,
533        cntpPeersFilterValidEntries Gauge32,
534        cntpPeersEntryStatus        RowStatus,
535        cntpPeersUpdateTimeRev1     Unsigned32,
536        cntpPeersPrefPeer           TruthValue,
537        cntpPeersPeerType           InetAddressType,
538        cntpPeersPeerName           InetAddress
539}
540
541cntpPeersAssocId OBJECT-TYPE
542    SYNTAX          NTPAssocIdentifier
543    MAX-ACCESS      not-accessible
544    STATUS          current
545    DESCRIPTION
546            "An integer value greater than 0 that uniquely
547            identifies a peer with which the local NTP server
548            is associated."
549    ::= { cntpPeersVarEntry 1 }
550
551cntpPeersConfigured OBJECT-TYPE
552    SYNTAX          TruthValue
553    MAX-ACCESS      read-only
554    STATUS          current
555    DESCRIPTION
556            "This is a bit indicating that the association
557            was created from configuration information and
558            should not be de-associated even if the peer
559            becomes unreachable."
560    ::= { cntpPeersVarEntry 2 }
561
562cntpPeersPeerAddress OBJECT-TYPE
563    SYNTAX          IpAddress
564    MAX-ACCESS      read-create
565    STATUS          current
566    DESCRIPTION
567            "The IP address of the peer.  When creating a new
568            association, a value should be set either for this
569            object or the corresponding instance of
570            cntpPeersPeerName, before the row is made active."
571    ::= { cntpPeersVarEntry 3 }
572
573cntpPeersPeerPort OBJECT-TYPE
574    SYNTAX          Integer32 (1..65535 )
575    MAX-ACCESS      read-only
576    STATUS          current
577    DESCRIPTION
578            "The UDP port number on which the peer receives NTP
579            messages."
580    ::= { cntpPeersVarEntry 4 }
581
582cntpPeersHostAddress OBJECT-TYPE
583    SYNTAX          IpAddress
584    MAX-ACCESS      read-create
585    STATUS          current
586    DESCRIPTION
587            "The IP address of the local host.  Multi-homing can
588            be supported using this object."
589    ::= { cntpPeersVarEntry 5 }
590
591cntpPeersHostPort OBJECT-TYPE
592    SYNTAX          Integer32 (1..65535 )
593    MAX-ACCESS      read-only
594    STATUS          current
595    DESCRIPTION
596            "The UDP port number on which the local host receives
597            NTP messages."
598    ::= { cntpPeersVarEntry 6 }
599
600cntpPeersLeap OBJECT-TYPE
601    SYNTAX          NTPLeapIndicator
602    MAX-ACCESS      read-only
603    STATUS          current
604    DESCRIPTION
605            "Two-bit code warning of an impending leap
606            second to be inserted in the NTP timescale of
607            the peer."
608    ::= { cntpPeersVarEntry 7 }
609
610cntpPeersMode OBJECT-TYPE
611    SYNTAX          INTEGER  {
612                        unspecified(0),
613                        symmetricActive(1),
614                        symmetricPassive(2),
615                        client(3),
616                        server(4),
617                        broadcast(5),
618                        reservedControl(6),
619                        reservedPrivate(7)
620                    }
621    MAX-ACCESS      read-create
622    STATUS          current
623    DESCRIPTION
624            "The association mode of the NTP server, with values
625            coded as follows,
626            0, unspecified
627            1, symmetric active - A host operating in this mode
628                    sends periodic messages regardless of the
629                    reachability state or stratum of its peer.  By
630                    operating in this mode the host announces its
631                    willingness to synchronize and be synchronized
632                    by the peer
633            2, symmetric passive - This type of association is
634                    ordinarily created upon arrival of a message
635                    from a peer operating in the symmetric active
636                    mode and persists only as long as the peer is
637                    reachable and operating at a stratum level
638                    less than or equal to the host; otherwise, the
639                    association is dissolved.  However, the
640                    association will always persist until at least
641                    one message has been sent in reply.  By
642                    operating in this mode the host announces its
643                    willingness to synchronize and be synchronized
644                    by the peer
645            3, client -  A host operating in this mode sends
646                    periodic messages regardless of the
647                    reachability state or stratum of its peer.  By
648                    operating in this mode the host, usually a LAN
649                    workstation, announces its willingness to be
650                    synchronized by, but not to synchronize the peer
651            4, server - This type of association is ordinarily
652                    created upon arrival of a client request message
653                    and exists only in order to reply to that
654                    request, after which the association is
655                    dissolved.  By operating in this mode the host,
656                    usually a LAN time server, announces its
657                    willingness to synchronize, but not to be
658                    synchronized by the peer
659            5, broadcast - A host operating in this mode sends
660                    periodic messages regardless of the
661                    reachability state or stratum of the peers.
662                    By operating in this mode the host, usually a
663                    LAN time server operating on a high-speed
664                    broadcast medium, announces its willingness to
665                    synchronize all of the peers, but not to be
666                    synchronized by any of them
667            6, reserved for NTP control messages
668            7, reserved for private use.
669
670            When creating a new peer association, if no value
671            is specified for this object, it defaults to
672            symmetricActive(1)."
673    REFERENCE
674            "D.L. Mills, 'Network Time Protocol (Version 3)',
675                RFC-1305, March 1992, Section 3.3"
676    ::= { cntpPeersVarEntry 8 }
677
678cntpPeersStratum OBJECT-TYPE
679    SYNTAX          NTPStratum
680    MAX-ACCESS      read-only
681    STATUS          current
682    DESCRIPTION     "The stratum of the peer clock."
683    ::= { cntpPeersVarEntry 9 }
684
685cntpPeersPeerPoll OBJECT-TYPE
686    SYNTAX          NTPPollInterval
687    MAX-ACCESS      read-only
688    STATUS          current
689    DESCRIPTION
690            "The interval at which the peer polls the local host."
691    ::= { cntpPeersVarEntry 10 }
692
693cntpPeersHostPoll OBJECT-TYPE
694    SYNTAX          NTPPollInterval
695    MAX-ACCESS      read-only
696    STATUS          current
697    DESCRIPTION
698            "The interval at which the local host polls the peer."
699    ::= { cntpPeersVarEntry 11 }
700
701cntpPeersPrecision OBJECT-TYPE
702    SYNTAX          Integer32 (-20..20 )
703    MAX-ACCESS      read-only
704    STATUS          current
705    DESCRIPTION
706            "Signed integer indicating the precision of the peer
707            clock, in seconds to the nearest power of two.  The
708            value must be rounded to the next larger power of
709            two; for instance, a 50-Hz (20 ms) or 60-Hz
710            (16.67 ms) power-frequency clock would be assigned
711            the value -5 (31.25 ms), while a 1000-Hz (1 ms)
712            crystal-controlled clock would be assigned the value
713            -9 (1.95 ms)."
714    ::= { cntpPeersVarEntry 12 }
715
716cntpPeersRootDelay OBJECT-TYPE
717    SYNTAX          NTPSignedTimeValue
718    UNITS           "seconds"
719    MAX-ACCESS      read-only
720    STATUS          current
721    DESCRIPTION
722            "A signed fixed-point number indicating the total
723            round-trip delay in seconds, from the peer to the
724            primary reference source at the root of the
725            synchronization subnet."
726    ::= { cntpPeersVarEntry 13 }
727
728cntpPeersRootDispersion OBJECT-TYPE
729    SYNTAX          NTPUnsignedTimeValue
730    UNITS           "seconds"
731    MAX-ACCESS      read-only
732    STATUS          current
733    DESCRIPTION
734            "The maximum error in seconds, of the peer clock
735            relative to the primary reference source at the root
736            of the synchronization subnet.  Only positive values
737            greater than zero are possible."
738    ::= { cntpPeersVarEntry 14 }
739
740cntpPeersRefId OBJECT-TYPE
741    SYNTAX          NTPRefId
742    MAX-ACCESS      read-only
743    STATUS          current
744    DESCRIPTION     "The reference identifier of the peer."
745    ::= { cntpPeersVarEntry 15 }
746
747cntpPeersRefTime OBJECT-TYPE
748    SYNTAX          NTPTimeStamp
749    MAX-ACCESS      read-only
750    STATUS          current
751    DESCRIPTION
752            "The local time at the peer when its clock was last
753            updated.  If the peer clock has never been
754            synchronized, the value is zero."
755    ::= { cntpPeersVarEntry 16 }
756
757cntpPeersOrgTime OBJECT-TYPE
758    SYNTAX          NTPTimeStamp
759    MAX-ACCESS      read-only
760    STATUS          current
761    DESCRIPTION
762            "The local time at the peer, when its latest
763            NTP message was sent.  If the peer becomes unreachable
764            the value is set to zero."
765    ::= { cntpPeersVarEntry 17 }
766
767cntpPeersReceiveTime OBJECT-TYPE
768    SYNTAX          NTPTimeStamp
769    MAX-ACCESS      read-only
770    STATUS          current
771    DESCRIPTION
772            "The local time, when the latest NTP message from
773            the peer arrived.  If the peer becomes unreachable
774            the value is set to zero."
775    ::= { cntpPeersVarEntry 18 }
776
777cntpPeersTransmitTime OBJECT-TYPE
778    SYNTAX          NTPTimeStamp
779    MAX-ACCESS      read-only
780    STATUS          current
781    DESCRIPTION
782            "The local time at which the NTP message departed the
783            sender."
784    ::= { cntpPeersVarEntry 19 }
785
786cntpPeersUpdateTime OBJECT-TYPE
787    SYNTAX          Integer32 (0..2147483647 )
788    MAX-ACCESS      read-only
789    STATUS          deprecated
790    DESCRIPTION
791            "The local time, when the most recent NTP message was
792            received from the peer that was used to calculate the
793            skew dispersion.  This represents only the 32-bit
794            integer part of the NTPTimestamp."
795    ::= { cntpPeersVarEntry 20 }
796
797cntpPeersReach OBJECT-TYPE
798    SYNTAX          Integer32 (0..255 )
799    MAX-ACCESS      read-only
800    STATUS          current
801    DESCRIPTION
802            "A shift register of used to determine the
803            reachability status of the peer, with bits entering
804            from the least significant (rightmost) end.  A peer is
805            considered reachable if at least one bit in this
806            register is set to one i.e, if the value of this
807            object is non-zero.
808            The data in the shift register would be populated by
809            the NTP protocol procedures."
810    REFERENCE
811            "D.L. Mills, 'Network Time Protocol (Version 3)',
812                RFC-1305, March 1992, Section 3.2.3"
813    ::= { cntpPeersVarEntry 21 }
814
815cntpPeersTimer OBJECT-TYPE
816    SYNTAX          Integer32 (0..2147483647 )
817    UNITS           "seconds"
818    MAX-ACCESS      read-only
819    STATUS          current
820    DESCRIPTION
821            "The interval in seconds, between transmitted NTP
822            messages from the local host to the peer."
823    REFERENCE
824            "D.L. Mills, 'Network Time Protocol (Version 3)',
825                RFC-1305, March 1992, Section 3.2.3"
826    ::= { cntpPeersVarEntry 22 }
827
828cntpPeersOffset OBJECT-TYPE
829    SYNTAX          NTPSignedTimeValue
830    UNITS           "seconds"
831    MAX-ACCESS      read-only
832    STATUS          current
833    DESCRIPTION
834            "The estimated offset of the peer clock relative to
835            the local clock, in seconds.  The host determines the
836            value of this object using the NTP clock-filter
837            algorithm."
838    REFERENCE
839            "D.L. Mills, 'Network Time Protocol (Version 3)',
840                RFC-1305, March 1992, Section 3.2.5"
841    ::= { cntpPeersVarEntry 23 }
842
843cntpPeersDelay OBJECT-TYPE
844    SYNTAX          NTPSignedTimeValue
845    UNITS           "seconds"
846    MAX-ACCESS      read-only
847    STATUS          current
848    DESCRIPTION
849            "The estimated round-trip delay of the peer clock
850            relative to the local clock over the network path
851            between them, in seconds.  The host determines the
852            value of this object using the NTP clock-filter
853            algorithm."
854    REFERENCE
855            "D.L. Mills, 'Network Time Protocol (Version 3)',
856                RFC-1305, March 1992, Section 3.2.5"
857    ::= { cntpPeersVarEntry 24 }
858
859cntpPeersDispersion OBJECT-TYPE
860    SYNTAX          NTPUnsignedTimeValue
861    UNITS           "seconds"
862    MAX-ACCESS      read-only
863    STATUS          current
864    DESCRIPTION
865            "The estimated maximum error of the peer clock
866            relative to the local clock over the network path
867            between them, in seconds.  The host determines the
868            value of this object using the NTP clock-filter
869            algorithm."
870    REFERENCE
871            "D.L. Mills, 'Network Time Protocol (Version 3)',
872                RFC-1305, March 1992, Section 3.2.5"
873    ::= { cntpPeersVarEntry 25 }
874
875cntpPeersFilterValidEntries OBJECT-TYPE
876    SYNTAX          Gauge32
877    MAX-ACCESS      read-only
878    STATUS          current
879    DESCRIPTION
880            "The number of valid entries for a peer in the
881            Filter Register Table. Since, the Filter Register
882            Table is optional, this object will have a value 0
883            if the Filter Register Table is not implemented."
884    ::= { cntpPeersVarEntry 26 }
885
886cntpPeersEntryStatus OBJECT-TYPE
887    SYNTAX          RowStatus
888    MAX-ACCESS      read-create
889    STATUS          current
890    DESCRIPTION
891            "The status object for this row. When a management
892            station is creating a new row, it should set the
893            value for cntpPeersPeerAddress at least, before the
894            row can be made active(1)."
895    ::= { cntpPeersVarEntry 27 }
896
897cntpPeersUpdateTimeRev1 OBJECT-TYPE
898    SYNTAX          Unsigned32
899    MAX-ACCESS      read-only
900    STATUS          current
901    DESCRIPTION
902            "The local time, when the most recent NTP message was
903            received from the peer that was used to calculate the
904            skew dispersion.  This represents only the 32-bit
905            integer part of the NTPTimestamp."
906    ::= { cntpPeersVarEntry 28 }
907
908cntpPeersPrefPeer OBJECT-TYPE
909    SYNTAX          TruthValue
910    MAX-ACCESS      read-create
911    STATUS          current
912    DESCRIPTION
913            "This object specifies whether this peer is the
914            preferred one over the others. By default, when
915            the value of this object is 'false', NTP chooses
916            the peer with which to synchronize the time on
917            the local system. If this object is set
918            to 'true', NTP will choose the corresponding
919            peer to synchronize the time with. If multiple
920            entries have this object set to 'true', NTP will
921            choose the first one to be set. This object is
922            a means to override the selection of the peer by
923            NTP."
924    DEFVAL          { false }
925    ::= { cntpPeersVarEntry 29 }
926
927cntpPeersPeerType OBJECT-TYPE
928    SYNTAX          InetAddressType
929    MAX-ACCESS      read-create
930    STATUS          current
931    DESCRIPTION
932            "Represents the type of the corresponding instance
933            of cntpPeersPeerName object."
934    DEFVAL          { ipv4 }
935    ::= { cntpPeersVarEntry 30 }
936
937cntpPeersPeerName OBJECT-TYPE
938    SYNTAX          InetAddress
939    MAX-ACCESS      read-create
940    STATUS          current
941    DESCRIPTION
942            "The address of the peer. When creating a new
943            association, a value must be set for either this
944            object or the corresponding instance of
945            cntpPeersPeerAddress object, before the row
946            is made active."
947    ::= { cntpPeersVarEntry 31 }
948
949
950-- Filter Group
951--
952-- Implementation of this group is optional.  It must be implemented
953-- when the filter and selection algorithms described in Section 4
954-- of RFC 1305 are used.
955--
956
957--
958-- Filter Register Table
959
960cntpFilterRegisterTable OBJECT-TYPE
961    SYNTAX          SEQUENCE OF CntpFilterRegisterEntry
962    MAX-ACCESS      not-accessible
963    STATUS          current
964    DESCRIPTION
965            "The following table contains NTP state variables
966            used by the NTP clock filter and selection algorithms.
967            This table depicts a shift register.  Each stage in
968            the shift register is a 3-tuple consisting of the
969            measured clock offset, measured clock delay and
970            measured clock dispersion associated with a single
971            observation.
972
973            An important factor affecting the accuracy and
974            reliability of time distribution is the complex of
975            algorithms used to reduce the effect of statistical
976            errors and falsetickers due to failure of various
977            subnet components, reference sources or propagation
978            media.  The NTP clock-filter and selection algorithms
979            are designed to do exactly this.  The objects in the
980            filter register table below are used by these
981            algorthims to minimize the error in the calculated
982            time."
983    REFERENCE
984            "D.L. Mills, 'Network Time Protocol (Version 3)',
985                RFC-1305, March 1992, Section 3.2.5"
986    ::= { cntpFilter 2 }
987
988cntpFilterRegisterEntry OBJECT-TYPE
989    SYNTAX          CntpFilterRegisterEntry
990    MAX-ACCESS      not-accessible
991    STATUS          current
992    DESCRIPTION
993            "Each entry corresponds to one stage of the shift
994            register, i.e., one reading of the variables clock
995            delay, clock offset and clock dispersion.
996
997            Entries are automatically created whenever a peer is
998            configured and deleted when the peer is removed."
999    INDEX           {
1000                        cntpPeersAssocId,
1001                        cntpFilterIndex
1002                    }
1003    ::= { cntpFilterRegisterTable 1 }
1004
1005CntpFilterRegisterEntry ::= SEQUENCE {
1006        cntpFilterIndex           Integer32,
1007        cntpFilterPeersOffset     NTPSignedTimeValue,
1008        cntpFilterPeersDelay      NTPSignedTimeValue,
1009        cntpFilterPeersDispersion NTPUnsignedTimeValue
1010}
1011
1012cntpFilterIndex OBJECT-TYPE
1013    SYNTAX          Integer32 (1..8 )
1014    MAX-ACCESS      not-accessible
1015    STATUS          current
1016    DESCRIPTION
1017            "An integer value in the specified range that is used
1018            to index into the table.  The size of the table is
1019            fixed at 8.  Each entry identifies a particular
1020            reading of the clock filter variables in the shift
1021            register.
1022
1023            Entries are added starting at index 1.  The index
1024            wraps back to 1 when it reaches 8.  When the index
1025            wraps back, the new entries will overwrite the old
1026            entries effectively deleting the old entry."
1027    ::= { cntpFilterRegisterEntry 1 }
1028
1029cntpFilterPeersOffset OBJECT-TYPE
1030    SYNTAX          NTPSignedTimeValue
1031    UNITS           "seconds"
1032    MAX-ACCESS      read-only
1033    STATUS          current
1034    DESCRIPTION
1035            "The offset of the peer clock relative to the
1036            local clock in seconds."
1037    ::= { cntpFilterRegisterEntry 2 }
1038
1039cntpFilterPeersDelay OBJECT-TYPE
1040    SYNTAX          NTPSignedTimeValue
1041    UNITS           "seconds"
1042    MAX-ACCESS      read-only
1043    STATUS          current
1044    DESCRIPTION
1045            "Round-trip delay of the peer clock relative to the
1046            local clock over the network path between them, in
1047            seconds.  This variable can take on both positive and
1048            negative values, depending on clock precision and
1049            skew-error accumulation."
1050    ::= { cntpFilterRegisterEntry 3 }
1051
1052cntpFilterPeersDispersion OBJECT-TYPE
1053    SYNTAX          NTPUnsignedTimeValue
1054    UNITS           "seconds"
1055    MAX-ACCESS      read-only
1056    STATUS          current
1057    DESCRIPTION
1058            "The maximum error of the peer clock relative to the
1059            local clock over the network path between them, in
1060            seconds.  Only positive values greater than zero are
1061            possible."
1062    ::= { cntpFilterRegisterEntry 4 }
1063
1064
1065-- Notifications
1066
1067
1068ciscoNtpSrvStatusChange NOTIFICATION-TYPE
1069    OBJECTS         { cntpSysSrvStatus }
1070    STATUS          current
1071    DESCRIPTION
1072            "This notification is generated whenever the value of
1073            cntpSysSrvStatus changes."
1074   ::= { ciscoNtpMIBNotifs 1 }
1075
1076
1077ciscoNtpHighPriorityConnFailure NOTIFICATION-TYPE
1078    OBJECTS         { cntpPeersPeerAddress }
1079    STATUS          current
1080    DESCRIPTION
1081            "A failure to connect with an high priority NTP server
1082            (e.g. a server at the lowest stratum) is detected."
1083   ::= { ciscoNtpMIBNotifs 2 }
1084
1085
1086ciscoNtpHighPriorityConnRestore NOTIFICATION-TYPE
1087    OBJECTS         { cntpPeersPeerAddress }
1088    STATUS          current
1089    DESCRIPTION
1090            "A connection with an high priority NTP server
1091            (e.g. a server at the lowest stratum) is restored."
1092   ::= { ciscoNtpMIBNotifs 3 }
1093
1094
1095ciscoNtpGeneralConnFailure NOTIFICATION-TYPE
1096    STATUS          current
1097    DESCRIPTION
1098            "This trap is sent when the device loses connectivity
1099            to all NTP servers."
1100   ::= { ciscoNtpMIBNotifs 4 }
1101
1102
1103ciscoNtpGeneralConnRestore NOTIFICATION-TYPE
1104    OBJECTS         { cntpPeersPeerAddress }
1105    STATUS          current
1106    DESCRIPTION
1107            "This trap is sent when the connection with at least
1108            one NTP server has been restored
1109            (e.g. after a ciscoNtpGeneralConnFailure)."
1110   ::= { ciscoNtpMIBNotifs 5 }
1111
1112-- Conformance
1113ciscoNtpMIBCompliances  OBJECT IDENTIFIER
1114    ::= { ciscoNtpMIBConformance 1 }
1115
1116ciscoNtpMIBGroups  OBJECT IDENTIFIER
1117    ::= { ciscoNtpMIBConformance 2 }
1118
1119-- Compliance Statement
1120ciscoNtpMIBCompliance MODULE-COMPLIANCE
1121    STATUS          deprecated
1122    DESCRIPTION
1123            "The compliance statement for Cisco agents which
1124            implement the Cisco NTP MIB."
1125    MODULE          -- this module
1126    MANDATORY-GROUPS {
1127                        ciscoNtpSysGroup,
1128                        ciscoNtpPeersGroup
1129                    }
1130
1131    GROUP           ciscoNtpFilterGroup
1132    DESCRIPTION
1133            "This group is required only if the
1134            clock-filer algorithms defined in RFC-1305,
1135            Section 4 are implemented by the agent."
1136    ::= { ciscoNtpMIBCompliances 1 }
1137
1138ciscoNtpMIBComplianceRev1 MODULE-COMPLIANCE
1139    STATUS          deprecated
1140    DESCRIPTION
1141            "The compliance statement for Cisco agents which
1142            implement the Cisco NTP MIB."
1143    MODULE          -- this module
1144    MANDATORY-GROUPS {
1145                        ciscoNtpSysGroup,
1146                        ciscoNtpPeersGroupRev1
1147                    }
1148
1149    GROUP           ciscoNtpFilterGroup
1150    DESCRIPTION
1151            "This group is required only if the
1152            clock-filer algorithms defined in RFC-1305,
1153            Section 4 are implemented by the agent."
1154    ::= { ciscoNtpMIBCompliances 2 }
1155
1156ciscoNtpMIBComplianceRev2 MODULE-COMPLIANCE
1157    STATUS          deprecated
1158    DESCRIPTION
1159            "The compliance statement for Cisco agents which
1160            implement the Cisco NTP MIB."
1161    MODULE          -- this module
1162    MANDATORY-GROUPS {
1163                        ciscoNtpSysGroup,
1164                        ciscoNtpPeersGroupRev1
1165                    }
1166
1167    GROUP           ciscoNtpFilterGroup
1168    DESCRIPTION
1169            "This group is required only if the
1170            clock-filer algorithms defined in RFC-1305,
1171            Section 4 are implemented by the agent."
1172
1173    GROUP           ciscoNtpPeerExtGroup
1174    DESCRIPTION
1175            "This group is mandatory for agents that
1176            support extended NTP configuration."
1177    ::= { ciscoNtpMIBCompliances 3 }
1178
1179ciscoNtpMIBComplianceRev3 MODULE-COMPLIANCE
1180    STATUS          deprecated -- replaced by ciscoNtpMIBComplianceRev4
1181    DESCRIPTION
1182            "The compliance statement for Cisco agents which
1183            implement the Cisco NTP MIB."
1184    MODULE          -- this module
1185    MANDATORY-GROUPS {
1186                        ciscoNtpSysGroup,
1187                        ciscoNtpPeersGroupRev2
1188                    }
1189
1190    GROUP           ciscoNtpFilterGroup
1191    DESCRIPTION
1192            "This group is required only if the
1193            clock-filer algorithms defined in RFC-1305,
1194            Section 4 are implemented by the agent."
1195
1196    GROUP           ciscoNtpPeerExtGroup
1197    DESCRIPTION
1198            "This group is mandatory for agents that
1199            support extended NTP configuration."
1200
1201    ::= { ciscoNtpMIBCompliances 4 }
1202
1203ciscoNtpMIBComplianceRev4 MODULE-COMPLIANCE
1204    STATUS          current
1205    DESCRIPTION
1206            "The compliance statement for Cisco agents which
1207            implement the Cisco NTP MIB."
1208    MODULE          -- this module
1209    MANDATORY-GROUPS {
1210                        ciscoNtpSysGroup,
1211                        ciscoNtpPeersGroupRev2
1212                    }
1213
1214    GROUP           ciscoNtpFilterGroup
1215    DESCRIPTION
1216            "This group is required only if the
1217            clock-filer algorithms defined in RFC-1305,
1218            Section 4 are implemented by the agent."
1219
1220    GROUP           ciscoNtpPeerExtGroup
1221    DESCRIPTION
1222            "This group is mandatory for agents that
1223            support extended NTP configuration."
1224
1225    GROUP           ciscoNtpSysExtGroup
1226    DESCRIPTION
1227            "This group is mandatory for agents that
1228            support extended NTP system variables."
1229
1230    GROUP           ciscoNtpSrvNotifGroup
1231    DESCRIPTION
1232            "This group is mandatory for agents that
1233            support NTP server notifications."
1234    ::= { ciscoNtpMIBCompliances 5 }
1235
1236-- Units of Conformance:
1237ciscoNtpSysGroup OBJECT-GROUP
1238    OBJECTS         {
1239                        cntpSysLeap,
1240                        cntpSysStratum,
1241                        cntpSysPrecision,
1242                        cntpSysRootDelay,
1243                        cntpSysRootDispersion,
1244                        cntpSysRefId,
1245                        cntpSysRefTime,
1246                        cntpSysPoll,
1247                        cntpSysPeer,
1248                        cntpSysClock
1249                    }
1250    STATUS          current
1251    DESCRIPTION     "The NTP system variables."
1252    ::= { ciscoNtpMIBGroups 1 }
1253
1254ciscoNtpPeersGroup OBJECT-GROUP
1255    OBJECTS         {
1256                        cntpPeersConfigured,
1257                        cntpPeersPeerAddress,
1258                        cntpPeersPeerPort,
1259                        cntpPeersHostAddress,
1260                        cntpPeersHostPort,
1261                        cntpPeersLeap,
1262                        cntpPeersMode,
1263                        cntpPeersStratum,
1264                        cntpPeersPeerPoll,
1265                        cntpPeersHostPoll,
1266                        cntpPeersPrecision,
1267                        cntpPeersRootDelay,
1268                        cntpPeersRootDispersion,
1269                        cntpPeersRefId,
1270                        cntpPeersRefTime,
1271                        cntpPeersOrgTime,
1272                        cntpPeersReceiveTime,
1273                        cntpPeersTransmitTime,
1274                        cntpPeersUpdateTime,
1275                        cntpPeersReach,
1276                        cntpPeersTimer,
1277                        cntpPeersOffset,
1278                        cntpPeersDelay,
1279                        cntpPeersDispersion,
1280                        cntpPeersFilterValidEntries,
1281                        cntpPeersEntryStatus
1282                    }
1283    STATUS          deprecated
1284    DESCRIPTION     "The NTP peer variables."
1285    ::= { ciscoNtpMIBGroups 2 }
1286
1287ciscoNtpFilterGroup OBJECT-GROUP
1288    OBJECTS         {
1289                        cntpFilterPeersOffset,
1290                        cntpFilterPeersDelay,
1291                        cntpFilterPeersDispersion
1292                    }
1293    STATUS          current
1294    DESCRIPTION     "The NTP clock-filter variables."
1295    ::= { ciscoNtpMIBGroups 3 }
1296
1297ciscoNtpPeersGroupRev1 OBJECT-GROUP
1298    OBJECTS         {
1299                        cntpPeersConfigured,
1300                        cntpPeersPeerAddress,
1301                        cntpPeersPeerPort,
1302                        cntpPeersHostAddress,
1303                        cntpPeersHostPort,
1304                        cntpPeersLeap,
1305                        cntpPeersMode,
1306                        cntpPeersStratum,
1307                        cntpPeersPeerPoll,
1308                        cntpPeersHostPoll,
1309                        cntpPeersPrecision,
1310                        cntpPeersRootDelay,
1311                        cntpPeersRootDispersion,
1312                        cntpPeersRefId,
1313                        cntpPeersRefTime,
1314                        cntpPeersOrgTime,
1315                        cntpPeersReceiveTime,
1316                        cntpPeersTransmitTime,
1317                        cntpPeersUpdateTimeRev1,
1318                        cntpPeersReach,
1319                        cntpPeersTimer,
1320                        cntpPeersOffset,
1321                        cntpPeersDelay,
1322                        cntpPeersDispersion,
1323                        cntpPeersFilterValidEntries,
1324                        cntpPeersEntryStatus
1325                    }
1326    STATUS          deprecated
1327    DESCRIPTION     "The NTP peer variables."
1328    ::= { ciscoNtpMIBGroups 4 }
1329
1330ciscoNtpPeerExtGroup OBJECT-GROUP
1331    OBJECTS         { cntpPeersPrefPeer }
1332    STATUS          current
1333    DESCRIPTION     "The extended set of NTP peer variable(s)."
1334    ::= { ciscoNtpMIBGroups 5 }
1335
1336ciscoNtpPeersGroupRev2 OBJECT-GROUP
1337    OBJECTS         {
1338                        cntpPeersConfigured,
1339                        cntpPeersPeerAddress,
1340                        cntpPeersPeerPort,
1341                        cntpPeersHostAddress,
1342                        cntpPeersHostPort,
1343                        cntpPeersLeap,
1344                        cntpPeersMode,
1345                        cntpPeersStratum,
1346                        cntpPeersPeerPoll,
1347                        cntpPeersHostPoll,
1348                        cntpPeersPrecision,
1349                        cntpPeersRootDelay,
1350                        cntpPeersRootDispersion,
1351                        cntpPeersRefId,
1352                        cntpPeersRefTime,
1353                        cntpPeersOrgTime,
1354                        cntpPeersReceiveTime,
1355                        cntpPeersTransmitTime,
1356                        cntpPeersUpdateTimeRev1,
1357                        cntpPeersReach,
1358                        cntpPeersTimer,
1359                        cntpPeersOffset,
1360                        cntpPeersDelay,
1361                        cntpPeersDispersion,
1362                        cntpPeersFilterValidEntries,
1363                        cntpPeersEntryStatus,
1364                        cntpPeersPeerName,
1365                        cntpPeersPeerType
1366                    }
1367    STATUS          current
1368    DESCRIPTION     "The NTP peer variables."
1369    ::= { ciscoNtpMIBGroups 6 }
1370
1371ciscoNtpSysExtGroup OBJECT-GROUP
1372    OBJECTS         { cntpSysSrvStatus }
1373    STATUS          current
1374    DESCRIPTION     "The extended set of NTP system variable(s)."
1375    ::= { ciscoNtpMIBGroups 7 }
1376
1377ciscoNtpSrvNotifGroup NOTIFICATION-GROUP
1378   NOTIFICATIONS    {
1379                        ciscoNtpSrvStatusChange,
1380                        ciscoNtpHighPriorityConnFailure,
1381                        ciscoNtpHighPriorityConnRestore,
1382                        ciscoNtpGeneralConnFailure,
1383                        ciscoNtpGeneralConnRestore
1384                    }
1385    STATUS          current
1386    DESCRIPTION
1387            "The collection of notifications for the NTP Server."
1388    ::= { ciscoNtpMIBGroups 8 }
1389
1390END
1391
1392
1393
1394