This object contains global parameters relating to the NTP time clients and or servers that are active in the device. This object can be used to model SNTP and NTP clients and servers. Both NTP and SNTP have identical packet formats and use the same mathematical operations to calculate client time, clock offset, and roundtrip delay. From the perspective of an NTP or SNTP server, there is no difference between NTP and SNTP clients, and from the perspective of an NTP or SNTP client, there is no difference between NTP and SNTP servers. SNTP servers are stateless like NTP servers in non-symmetric modes and can handle numerous clients, but SNTP clients usually operate with only one server at a time, unlike most NTP clients. Enables or disables all the time clients and servers. Reflects the global time synchronisation status of the CPE. {{enum}} Indicates that the CPE's time client services are disabled. Indicates that the CPE's absolute time has not yet been set by any of the configured time clients. Indicates that the CPE has acquired accurate absolute time; its current time is accurate. One or more time client was able to configure the time of the CPE. {{deprecated|2.16|due to the introduction of {{object|Client}}}} {{obsoleted|2.18}} {{deleted|2.19}} MAY be used by the CPE to indicate a locally defined error condition. None of the configured Time clients were able to synchronize the time. First NTP timeserver. Either a host name or IP address. {{deprecated|2.16|due to the introduction of {{object|Client}}}} {{obsoleted|2.18}} {{deleted|2.19}} Second NTP timeserver. Either a host name or IP address. {{deprecated|2.16|due to the introduction of {{object|Client}}}} {{obsoleted|2.18}} {{deleted|2.19}} Third NTP timeserver. Either a host name or IP address. {{deprecated|2.16|due to the introduction of {{object|Client}}}} {{obsoleted|2.18}} {{deleted|2.19}} Fourth NTP timeserver. Either a host name or IP address. {{deprecated|2.16|due to the introduction of {{object|Client}}}} {{obsoleted|2.18}} {{deleted|2.19}} Fifth NTP timeserver. Either a host name or IP address. {{deprecated|2.16|due to the introduction of {{object|Client}}}} {{obsoleted|2.18}} {{deleted|2.19}} The current date and time in the CPE's local time zone. The local time zone definition, encoded according to IEEE 1003.1 (POSIX). The following is an example value: : EST+5 EDT,M4.1.0/2,M10.5.0/2 {{numentries}} {{numentries}} This object contains parameters relating to an time client instance. Enables or disables the time client. Status of Time support for this client. {{enum}} Indicates that the time client service is being disabled Indicates that the time client absolute time has not yet been set. Indicates that the time client has acquired accurate absolute time; its current time is accurate. The NTP client attempted to contact the remote NTP server but failed to acquire accurate absolute time. The current time remains inaccurate. MAY be used by the time client to indicate a locally defined error condition. Specifies in which mode the NTP client must be run. {{enum}} Support for the NTP client in unicast mode. Support for the NTP client in broadcast mode. Support for the NTP client in multicast mode. Support for the NTP client in manycast mode. Specify the port used to send NTP packets. {{bibref|RFC5905|Section 7.2}} Specifies the server currently used for time synchronization. The value reported is the exact server entry as configured in the {{param|Servers}} parameter. If the server is specified as a Fully Qualified Domain Name (FQDN) in the {{param|Servers}} parameter, the configured FQDN will be reported here, not the resolved IP address or CNAME. Specifies the supported NTP version. Possible versions are 1-4. Points to a CSV list of NTP servers or pools. A NTP server can either be specified as an IP address or a host name. It is expected that the NTP client resolves multiple addresses which can change over time when {{param|ResolveAddresses}} is enabled. When this option is enabled the NTP client must resolve the multiple addresses associated with the host name(s) that are specified in the {{param|Servers}} field. When {{param|ResolveAddresses}} is enabled, This parameter specifies the maximum number of IP addresses that the NTP client can resolve. 0 means that all addresses must be resolved. Use symmetric active association mode. This device may provide synchronization to the configured NTP server. This is the minimum polling interval, in {{units}} to the power of two, allowed by any peer of the Internet system, currently set to 6 (64 seconds). {{bibref|RFC5905|Section 7.2}} This is the maximum polling interval, in {{units}} to the power of two, allowed by any peer of the Internet system, currently set to 10 (1024 seconds) {{bibref|RFC5905|Section 7.2}} If the {{param}} parameter is enabled, and this is the first packet sent when the server has been unreachable, the client sends a burst. This is useful to quickly reduce the synchronization distance below the distance threshold and synchronize the clock. {{bibref|RFC5905}}. If the {{param}} parameter is enabled and the server is reachable and a valid source of synchronization is available, the client sends a burst of BCOUNT (8) packets at each poll interval. The interval between packets in the burst is two seconds. This is useful to accurately measure jitter with long poll intervals. {{bibref|RFC5905}}. The IP Interface associated with the ''Client'' entry. Specifies how the client sockets are bound. {{enum}} The client sockets are bound to a local IP address. The client sockets are bound to a network device. This can be useful when the local address is dynamic. This object contains parameters relating to enabling security for the time client. Enables or disables authentication of the time client. Points to the certificate that must be used by the NTS-KE client. On this port the NTS Key Establishment protocol is being provided. This object specifies the statistic parameters for the time client. {{bibref|RFC9249|Chapter 8 NTP Yang Module}} Specifies the number of packets that have been successfully sent from the NTP client to the NTP server. Specifies the number of packets that were not successfully sent to the NTP server. Specifies the number of packets that have been successfully received by the NTP client from the NTP server. Specifies the number of packets that were received by the NTP client but were not successfully processed or handled due to errors or other issues. This object contains parameters relating to an time server instance. Enables or disables the time server. Status of Time server instance. {{enum}} Indicates that the NTP server instance is enabled and working. Indicates that the NTP server instance is disabled and thus not working. MAY be used by the NTP server instance to indicate a locally defined error condition. Specifies in which mode the NTP server must be ran. {{enum}} Support for the NTP server in unicast mode. Support for the NTP server in broadcast mode. Support for the NTP server in multicast mode. Support for the NTP server in manycast mode. Specifies the supported NTP version. Possible versions are 1-4. Specify the port used to receive NTP packets. {{bibref|RFC5905|Section 7.2}} The IP Interface associated with the ''Server'' entry. Specifies how the client sockets must be bounded. {{enum}} The server sockets are bound to a local IP address. The server sockets are bound to a network device. This can be useful when the local address is dynamic. This is the minimum polling interval, in {{units}} to the power of two, allowed by any peer of the Internet system, currently set to 6 (64 seconds). {{bibref|RFC5905|Section 7.2}} This is the maximum polling interval, in {{units}} to the power of two, allowed by any peer of the Internet system, currently set to 10 (1024 seconds) {{bibref|RFC5905|Section 7.2}} Specifies the time to live (TTL) for a broadcast/multicast packet. {{bibref|RFC5905|Section 3.1}} This object contains parameters relating to enabling security for the NTP Server. Enables or disables authentication of the NTP server. Points to the certificate that must be used by the NTS-KE client. Points to a CSV list of NTP servers. A NTP server can either be specified as an IP address or a host name. When used the NTS-KE server will tell the remote NTS-KE client the NTP hostname or address of the NTP server(s) that should be used. This allows to separate the NTP server and NTS-KE server implementation. This object specifies the statistic parameters for the NTP server. {{bibref|RFC9249|Chapter 8 NTP Yang Module}} Specifies the number of packets that have been successfully sent from the NTP server to the NTP client. Specifies the number of packets that were not successfully sent to the NTP client. Specifies the number of packets that have been successfully received by the NTP server from a NTP client. Specifies the number of packets that were received by the NTP server but were not successfully processed or handled due to errors or other issues.