| cntpSysLeap | 
      .1.3.6.1.4.1.9.9.168.1.1.1 | 
    
    
      | 
        Two-bit code warning of an impending leap second to
        be inserted in the NTP timescale. This object can be
        set only when the cntpSysStratum has a value of 1.
       | 
    
    
      | cntpSysStratum | 
      .1.3.6.1.4.1.9.9.168.1.1.2 | 
    
    
      | 
        The stratum of the local clock. If the value is set
        to 1, i.e., this is a primary reference, then the
        Primary-Clock procedure described in Section 3.4.6,
        in RFC-1305 is invoked.
       | 
    
    
      | cntpSysPrecision | 
      .1.3.6.1.4.1.9.9.168.1.1.3 | 
    
    
      | 
        Signed integer indicating the precision
        of the system clock, in seconds to the nearest
        power of two.  The value must be rounded to the
        next larger power of two; for instance, a 50-Hz
        (20 ms) or 60-Hz (16.67 ms) power-frequency clock
        would be assigned the value -5 (31.25 ms), while a
        1000-Hz (1 ms) crystal-controlled clock would be
        assigned the value -9 (1.95 ms).
       | 
    
    
      | cntpSysRootDelay | 
      .1.3.6.1.4.1.9.9.168.1.1.4 | 
    
    
      | 
        A signed fixed-point number indicating the total
        round-trip delay in seconds, to the primary reference
        source at the root of the synchronization subnet.
       | 
    
    
      | cntpSysRootDispersion | 
      .1.3.6.1.4.1.9.9.168.1.1.5 | 
    
    
      | 
        The maximum error in seconds, relative to the
        primary reference source at the root of the
        synchronization subnet.  Only positive values greater
        than zero are possible.
       | 
    
    
      | cntpSysRefId | 
      .1.3.6.1.4.1.9.9.168.1.1.6 | 
    
    
      | 
        The reference identifier of the local clock.
       | 
    
    
      | cntpSysRefTime | 
      .1.3.6.1.4.1.9.9.168.1.1.7 | 
    
    
      | 
        The local time when the local clock was last
        updated.  If the local clock has never been
        synchronized, the value is zero.
       | 
    
    
      | cntpSysPoll | 
      .1.3.6.1.4.1.9.9.168.1.1.8 | 
    
    
      | 
        The interval at which the NTP server polls other NTP
        servers to synchronize its clock.
       | 
    
    
      | cntpSysPeer | 
      .1.3.6.1.4.1.9.9.168.1.1.9 | 
    
    
      | 
        The current synchronization source.  This will
        contain the unique association identifier
        cntpPeersAssocId of the corresponding peer entry in
        the cntpPeersVarTable of the peer acting as the
        synchronization source.  If there is no peer, the
        value will be 0.
       | 
    
    
      | cntpSysClock | 
      .1.3.6.1.4.1.9.9.168.1.1.10 | 
    
    
      | 
        The current local time.  Local time is derived from
        the hardware clock of the particular machine and
        increments at intervals depending on the design used.
       | 
    
    
      | cntpPeersVarEntry | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1 | 
    
    
      | 
        Each peers' entry provides NTP information retrieved
        from a particular peer NTP server.  Each peer is
        identified by a unique association identifier.
        Entries are automatically created when the user
        configures the NTP server to be associated with remote
        peers.  Similarly entries are deleted when the user
        removes the peer association from the NTP server.
        Entries can also be created by the management station
        by setting values for the following objects:
        cntpPeersPeerAddress or cntpPeersPeerName,
        cntpPeersHostAddress and
        cntpPeersMode and making the cntpPeersEntryStatus as
        active(1).  At the least, the management station has
        to set a value for cntpPeersPeerAddress or
        cntpPeersPeerName to make the row active.
       | 
    
    
      | cntpFilterRegisterEntry | 
      .1.3.6.1.4.1.9.9.168.1.3.2.1 | 
    
    
      | 
        Each entry corresponds to one stage of the shift
        register, i.e., one reading of the variables clock
        delay, clock offset and clock dispersion.
        Entries are automatically created whenever a peer is
        configured and deleted when the peer is removed.
       | 
    
  
  
    
      | cntpPeersAssocId | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.1 | 
    
    
      | 
        An integer value greater than 0 that uniquely
        identifies a peer with which the local NTP server
        is associated.
       | 
    
    
      | cntpPeersConfigured | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.2 | 
    
    
      | 
        This is a bit indicating that the association
        was created from configuration information and
        should not be de-associated even if the peer
        becomes unreachable.
       | 
    
    
      | cntpPeersPeerAddress | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.3 | 
    
    
      | 
        The IP address of the peer.  When creating a new
        association, a value should be set either for this
        object or the corresponding instance of
        cntpPeersPeerName, before the row is made active.
       | 
    
    
      | cntpPeersPeerPort | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.4 | 
    
    
      | 
        The UDP port number on which the peer receives NTP
        messages.
       | 
    
    
      | cntpPeersHostAddress | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.5 | 
    
    
      | 
        The IP address of the local host.  Multi-homing can
        be supported using this object.
       | 
    
    
      | cntpPeersHostPort | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.6 | 
    
    
      | 
        The UDP port number on which the local host receives
        NTP messages.
       | 
    
    
      | cntpPeersLeap | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.7 | 
    
    
      | 
        Two-bit code warning of an impending leap
        second to be inserted in the NTP timescale of
        the peer.
       | 
    
    
      | cntpPeersMode | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.8 | 
    
    
      | 
        The association mode of the NTP server, with values
        coded as follows,
        0, unspecified
        1, symmetric active - A host operating in this mode
        sends periodic messages regardless of the
        reachability state or stratum of its peer.  By
        operating in this mode the host announces its
        willingness to synchronize and be synchronized
        by the peer
        2, symmetric passive - This type of association is
        ordinarily created upon arrival of a message
        from a peer operating in the symmetric active
        mode and persists only as long as the peer is
        reachable and operating at a stratum level
        less than or equal to the host; otherwise, the
        association is dissolved.  However, the
        association will always persist until at least
        one message has been sent in reply.  By
        operating in this mode the host announces its
        willingness to synchronize and be synchronized
        by the peer
        3, client -  A host operating in this mode sends
        periodic messages regardless of the
        reachability state or stratum of its peer.  By
        operating in this mode the host, usually a LAN
        workstation, announces its willingness to be
        synchronized by, but not to synchronize the peer
        4, server - This type of association is ordinarily
        created upon arrival of a client request message
        and exists only in order to reply to that
        request, after which the association is
        dissolved.  By operating in this mode the host,
        usually a LAN time server, announces its
        willingness to synchronize, but not to be
        synchronized by the peer
        5, broadcast - A host operating in this mode sends
        periodic messages regardless of the
        reachability state or stratum of the peers.
        By operating in this mode the host, usually a
        LAN time server operating on a high-speed
        broadcast medium, announces its willingness to
        synchronize all of the peers, but not to be
        synchronized by any of them
        6, reserved for NTP control messages
        7, reserved for private use.
        When creating a new peer association, if no value
        is specified for this object, it defaults to
        symmetricActive(1).
       | 
    
    
      | cntpPeersStratum | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.9 | 
    
    
      | 
        The stratum of the peer clock.
       | 
    
    
      | cntpPeersPeerPoll | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.10 | 
    
    
      | 
        The interval at which the peer polls the local host.
       | 
    
    
      | cntpPeersHostPoll | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.11 | 
    
    
      | 
        The interval at which the local host polls the peer.
       | 
    
    
      | cntpPeersPrecision | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.12 | 
    
    
      | 
        Signed integer indicating the precision of the peer
        clock, in seconds to the nearest power of two.  The
        value must be rounded to the next larger power of
        two; for instance, a 50-Hz (20 ms) or 60-Hz
        (16.67 ms) power-frequency clock would be assigned
        the value -5 (31.25 ms), while a 1000-Hz (1 ms)
        crystal-controlled clock would be assigned the value
        -9 (1.95 ms).
       | 
    
    
      | cntpPeersRootDelay | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.13 | 
    
    
      | 
        A signed fixed-point number indicating the total
        round-trip delay in seconds, from the peer to the
        primary reference source at the root of the
        synchronization subnet.
       | 
    
    
      | cntpPeersRootDispersion | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.14 | 
    
    
      | 
        The maximum error in seconds, of the peer clock
        relative to the primary reference source at the root
        of the synchronization subnet.  Only positive values
        greater than zero are possible.
       | 
    
    
      | cntpPeersRefId | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.15 | 
    
    
      | 
        The reference identifier of the peer.
       | 
    
    
      | cntpPeersRefTime | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.16 | 
    
    
      | 
        The local time at the peer when its clock was last
        updated.  If the peer clock has never been
        synchronized, the value is zero.
       | 
    
    
      | cntpPeersOrgTime | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.17 | 
    
    
      | 
        The local time at the peer, when its latest
        NTP message was sent.  If the peer becomes unreachable
        the value is set to zero.
       | 
    
    
      | cntpPeersReceiveTime | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.18 | 
    
    
      | 
        The local time, when the latest NTP message from
        the peer arrived.  If the peer becomes unreachable
        the value is set to zero.
       | 
    
    
      | cntpPeersTransmitTime | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.19 | 
    
    
      | 
        The local time at which the NTP message departed the
        sender.
       | 
    
    
      | cntpPeersUpdateTime | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.20 | 
    
    
      | 
        The local time, when the most recent NTP message was
        received from the peer that was used to calculate the
        skew dispersion.  This represents only the 32-bit
        integer part of the NTPTimestamp.
       | 
    
    
      | cntpPeersReach | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.21 | 
    
    
      | 
        A shift register of used to determine the
        reachability status of the peer, with bits entering
        from the least significant (rightmost) end.  A peer is
        considered reachable if at least one bit in this
        register is set to one i.e, if the value of this
        object is non-zero.
        The data in the shift register would be populated by
        the NTP protocol procedures.
       | 
    
    
      | cntpPeersTimer | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.22 | 
    
    
      | 
        The interval in seconds, between transmitted NTP
        messages from the local host to the peer.
       | 
    
    
      | cntpPeersOffset | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.23 | 
    
    
      | 
        The estimated offset of the peer clock relative to
        the local clock, in seconds.  The host determines the
        value of this object using the NTP clock-filter
        algorithm.
       | 
    
    
      | cntpPeersDelay | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.24 | 
    
    
      | 
        The estimated round-trip delay of the peer clock
        relative to the local clock over the network path
        between them, in seconds.  The host determines the
        value of this object using the NTP clock-filter
        algorithm.
       | 
    
    
      | cntpPeersDispersion | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.25 | 
    
    
      | 
        The estimated maximum error of the peer clock
        relative to the local clock over the network path
        between them, in seconds.  The host determines the
        value of this object using the NTP clock-filter
        algorithm.
       | 
    
    
      | cntpPeersFilterValidEntries | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.26 | 
    
    
      | 
        The number of valid entries for a peer in the
        Filter Register Table. Since, the Filter Register
        Table is optional, this object will have a value 0
        if the Filter Register Table is not implemented.
       | 
    
    
      | cntpPeersEntryStatus | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.27 | 
    
    
      | 
        The status object for this row. When a management
        station is creating a new row, it should set the
        value for cntpPeersPeerAddress at least, before the
        row can be made active(1).
       | 
    
    
      | cntpPeersUpdateTimeRev1 | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.28 | 
    
    
      | 
        The local time, when the most recent NTP message was
        received from the peer that was used to calculate the
        skew dispersion.  This represents only the 32-bit
        integer part of the NTPTimestamp.
       | 
    
    
      | cntpPeersPrefPeer | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.29 | 
    
    
      | 
        This object specifies whether this peer is the
        preferred one over the others. By default, when
        the value of this object is 'false', NTP chooses
        the peer with which to synchronize the time on
        the local system. If this object is set
        to 'true', NTP will choose the corresponding
        peer to synchronize the time with. If multiple
        entries have this object set to 'true', NTP will
        choose the first one to be set. This object is
        a means to override the selection of the peer by
        NTP.
       | 
    
    
      | cntpPeersPeerType | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.30 | 
    
    
      | 
        Represents the type of the corresponding instance
        of cntpPeersPeerName object.
       | 
    
    
      | cntpPeersPeerName | 
      .1.3.6.1.4.1.9.9.168.1.2.1.1.31 | 
    
    
      | 
        The address of the peer. When creating a new
        association, a value must be set for either this
        object or the corresponding instance of
        cntpPeersPeerAddress object, before the row
        is made active.
       | 
    
    
      | cntpFilterIndex | 
      .1.3.6.1.4.1.9.9.168.1.3.2.1.1 | 
    
    
      | 
        An integer value in the specified range that is used
        to index into the table.  The size of the table is
        fixed at 8.  Each entry identifies a particular
        reading of the clock filter variables in the shift
        register.
        Entries are added starting at index 1.  The index
        wraps back to 1 when it reaches 8.  When the index
        wraps back, the new entries will overwrite the old
        entries effectively deleting the old entry.
       | 
    
    
      | cntpFilterPeersOffset | 
      .1.3.6.1.4.1.9.9.168.1.3.2.1.2 | 
    
    
      | 
        The offset of the peer clock relative to the
        local clock in seconds.
       | 
    
    
      | cntpFilterPeersDelay | 
      .1.3.6.1.4.1.9.9.168.1.3.2.1.3 | 
    
    
      | 
        Round-trip delay of the peer clock relative to the
        local clock over the network path between them, in
        seconds.  This variable can take on both positive and
        negative values, depending on clock precision and
        skew-error accumulation.
       | 
    
    
      | cntpFilterPeersDispersion | 
      .1.3.6.1.4.1.9.9.168.1.3.2.1.4 | 
    
    
      | 
        The maximum error of the peer clock relative to the
        local clock over the network path between them, in
        seconds.  Only positive values greater than zero are
        possible.
       |