|
This topic comprises 2 pages: 1 2
|
Author
|
Topic: Managed switch that can act as an NTP server?
|
Leo Enticknap
Film God
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 04-01-2018 11:28 AM
I've now hit the same problem at several sites, mainly single screen arthouse type places that don't have a TMS or a connection to the Internet, and therefore no source for the DCP sever to get an NTP sync from. The issue lies dormant for years, until eentually the media block's clock drifts so far that it causes a problem with KDM windows.
At sites where we install a remote access PC, the Windows time service can be used, which solves the problem. But in booths that don't have them, the problem remains.
Looking around the Internet, the only immediately obvious solution is a GPS-based dedicated NTP server, for which you won't get much change out of a grand. I was wondering if anyone knew of any model of managed switch that could provide an NTP time to the devices connected to it? Of course, if the switch itself has no Internet connection, the owner would need to keep checking and correcting its own clock manually, but if they did that often enough for the server to be getting a time from it that was within the DCI budget, this would potentially be a solution. I can't find any model specs online that specifically lists this feature, but wondered if anyone here knew of any models.
| IP: Logged
|
|
|
Steve Guttag
We forgot the crackers Gromit!!!
Posts: 12814
From: Annapolis, MD
Registered: Dec 1999
|
posted 04-01-2018 01:53 PM
Leo...it isn't enough that there is a clock that the server can sync off of. If that source doesn't show that its time is good, the server should disregard the time.
Furthermore, the NTP logs of the device should let one know what Stratum they are (how far away from the reference) with a Stratum 1 typically a master reference like NIST. So even if you have a PC doing the work via the internet, at best, the PC would identify as Stratum 2.
But if there is no actual reference, then the thing that is using it as a reference will know that it is a non-referenced time.
Note too, most servers rely on their secure clock's precision to keep time for the security manager and what the NTP reference is for is for a show clock, not the secure clock. Most have a means of manually adjusting the secure clock up to +/- 6 minutes a year. Most will reference the secure clock time, absent NTP. The only secure clock that I know that is less than worthless is the CAT745 clock. If it is without power, it will drift fast, rather rapidly. With power, it isn't too bad but who wants to run their projectors 24/7? GDC often isn't right but one can also adjust it but even when right it will start shows about 10 seconds late. And Doremi...who knows when/what shows it starts? It is a mystery up until it does it
| IP: Logged
|
|
|
|
|
Leo Enticknap
Film God
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 04-01-2018 11:56 PM
quote: Scott Norwood If you don't have Internet access at a particular site, a GPS-based NTP appliance is probably the best option and likely cheaper than the difference between whatever switches you would normally buy and enterprise-grade gear.
Many thanks, Scott (and everyone) - that is the conclusion I was heading towards after reading yours, Mark's and Steve's replies. So it looks like the solution is high three figures (in hardware cost) rather than low three figures, but at least I know what I have to offer the next time I come up against this situation.
Steve - I'd guess that Stratum 2 is allowable for DCI purposes, because we regularly install remote access PCs running Windows, that sit in the booth to enable us to Teamviewer in as a first line support mechanism for operational problems. Typically, the screen servers get their NTP sync from the TMS, and the TMS gets its from the remote access PC's Windows time service. This arrangement works, as long as the remote access PC doesn't lose its Internet connection for any significant length of time.
quote: Steve Guttag he only secure clock that I know that is less than worthless is the CAT745 clock. If it is without power, it will drift fast, rather rapidly.
Amen to that. This bit me in the rear somewhat spectacularly recently, when the DSL200 TMS in an 11-plex I look after crapped out (RAID controller card died). Their normal operating routine was to shut down the individual screen servers (DSS220/cat745) overnight, and has been since they were installed several years ago: so for the last few years, those IMBs have spent around 12 hours out of every 24 without power, and their clocks being maintained on battery power. If a screen server receives a valid NTP time from 192.168.241.2 (the TMS, on the theatre network) on bootup, all is good. But if it can't, it falls back to using the cat745's secure clock. They had all drifted forward around two hours by the time the TMS went down. So, when that happened in the middle of one night, the first they knew they had a problem was when the next day's shows started about two hours before they should have done, because the cat745 clocks were now being used for scheduling purposes as well. Uh oh...
| IP: Logged
|
|
|
|
|
|
|
|
|
Carsten Kurz
Film God
Posts: 4340
From: Cologne, NRW, Germany
Registered: Aug 2009
|
posted 04-24-2018 05:51 AM
Well, as it seems, the CAT745 has not been designed by Dolby ;-)
But Dolby show clock and secure clock time reference issues were in fact notorious for a long time, it has only improved lately.
That said - a collegue recently reported issues with their ATMOS installation dropping out of ATMOS regularly for unknown reasons. After analyzing the log files, the techs found out that the CP850 clock deviated more than 23 hours.
The trouble is, in most cinemas, no one wants the equipment to have any internet connections at all for security reasons. Most DCI servers run on stable Linux operating systems, but these are not patched regularly, neither do they run virus protection software. So, no one want's them to be exposed. But the easiest way to have a common time is to dial into an outside NTP server. If you don't want that, you need to setup your own internal time server.
The problem is, time servers are usually built to supply very accurate time, and yre built in low quantities for high profile applications, thus are very expensive. Where as in a cinema, the supplied time does not need to be overly accurate ( down to a few seconds would do). But there is no market for cheap, low cost, decently inaccurate time servers.
It is very easy to build your own time server from a cheap GPS receiver, but these need an external wire run for the antenna on a roof. Radio controlled clocks are another option. Seems a prominent solution is to have a dedicated PC running all the time, relaying external NTP.
- Carsten
| IP: Logged
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 2 pages: 1 2
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|