There are basically two ways to take the leap second into account in your own IT time system. The first solution (DTS4160, DTS4210) is that the leap second is automatically read in via the GPS receiver and the time server can implement this in the NTP time stamp that is output. The background to this device automatism is that the GPS satellite operators usually take the IERS specification into account accordingly, which is guaranteed by advance notice and the actual leap second itself. Only on the basis of both components can GPS receivers and time servers process the leap second correctly and at exactly the right time and also implement it in terms of system technology.
Some operators of critical infrastructures, on the other hand, prefer the manual procedure because there is a certain residual risk with regard to the secure reception of both of the above-mentioned components and the leap second usually has to be tracked separately for other IT systems anyway. Also, the definition of leap seconds is not a standard procedure, so that this may also speak for a conscious, then manual, process on the part of the user. With this alternative solution of manual setting, you can make a corresponding setting in good time with our DTS devices, for example via MOBA NMS or Telnet SSH, whereby the DTS time server then safely processes the leap second and implements it accordingly.
