I don't know if it's the recommended solution, but I encountered a similar
problem a while back. My solution was to use pmc as follows:
# pmc -u -b 0 'set GRANDMASTER_SETTINGS_NP clockClass 248 clockAccuracy
0xfe offsetScaledLogVariance 0xffff currentUtcOffset 37 leap61 0 leap59 0
currentUtcOffsetValid 1 ptpTimescale 1 timeTraceable 0 frequencyTraceable 0
timeSource 0xa0'
Hopefully someone more knowledgeable will have something better to suggest,
but this does work.
Thanks,
Scott Silverman | IT | Simplex | 312-360-2444
230 S. LaSalle St., Suite 4-100, Chicago, IL 60604
On Wed, Jun 21, 2017 at 12:57 PM, Boris Boucher <boris.bouc...@gmail.com>
wrote:
> Hi all,
>
> I have a system with a grand master clock that is GPS synchronized (secure
> sync),
> a SERVER machine running Linux/ptp4l acting as boundary clock for set of
> CLIENTS systems.
>
> The SERVER and the CLIENTS behind it requires precise time
> synchronization, hence
> the usage of PTP.
>
> The grand master is aware that the current UTC offset is 37s today.
>
> My SERVER on the other hand, is built with a code base from 2016 and think
> the UTC offset is 36s. But as long as the grand master is present, the
> boundary clock
> distribute time with the correct offset.
>
> The problem is, if the grand master is lost (power failure, network
> issue....), my boundary
> clock promotes itself as grand master, and uses its own knowledge of the
> UTC offset instead
> of the last known offset from the secure sync, and this cause a 1s step on
> the UTC time !
>
> This change propagate to the CLIENTS and also to the system clock of the
> SERVER via phc2sys.
> And during 1 or 2 minutes, the system clock of the SERVER and the CLIENTS
> are not fully synchronized,
> causing the system to fail to provide its service.
>
> Looking at the documentation, I can't find any way of updating the UTC
> offset of the SERVER in a simple
> manner.
>
> Rebuilding the SERVER with a new code base each time a new leap second is
> inserted is not an option (the system
> once deployed can not be updated easily).
>
> What are my options ?
>
> Thank you in advance for your advice !
>
> Boris Boucher
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linuxptp-users mailing list
> Linuxptp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users
>
>
--
DISCLAIMER: NOTICE REGARDING PRIVACY AND CONFIDENTIALITY
The information contained in and/or accompanying this communication is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information. If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this information, and any
attachments thereto, is strictly prohibited. If you have received this
e-mail in error, please immediately notify the sender and permanently
delete the original and any copy of any e-mail and any printout thereof.
Electronic transmissions cannot be guaranteed to be secure or error-free.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message which arise as a result of e-mail
transmission. Simplex Trading, LLC and its affiliates reserves the right to
intercept, monitor, and retain electronic communications to and from its
system as permitted by law. Simplex Trading, LLC is a registered Broker
Dealer with CBOE and a Member of SIPC.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
