A live sports broadcasting enterprise with multiple sites and a distributed network was getting its time references via internet time servers, including regional NIST and NTP pool servers … and it wasn’t working out. Their applications were very sensitive to time sync delays, and their time traffic was passing though insecure firewalls. They needed to do better.  Orolia suggested an enterprise hierarchical timing topology instead, utilizing multiple layers: a time reference layer, a time distribution layer, and a client hand-off layer.
Monday, October 5, 2020
Document Type: 
Case Studies
Enterprise Network Timing