Time Synchronisation for Avid Interplay™ systems Rev.D

 A Guide to Time Synchronisation
for Avid® Interplay™ systems
Revision D – July 2011
Avid Technology EMEA | Enterprise Customer Success
Page 1 of 28 Time Synchronisation for Avid® Interplay™ systems
Table of Contents
Introduction ....................................................................................................................................................... 3 Included with this package: ................................................................................................................................ 3 1. Setting up an NTP Server ................................................................................................................................ 4 Windows Server 2003 ........................................................................................................................................ 4 Windows Server 2008R2 x64 .............................................................................................................................. 4 NTPD Installation ................................................................................................................................................ 6 Setting the Time Zone and Regional Settings ..................................................................................................... 9 Verifying the NTP Server Configuration ........................................................................................................... 10 Windows Server 2003 (CaptureManager or GPS) ....................................................................................... 10 Windows Server 2008R2 (Interplay Capture) ............................................................................................. 11 Avid Time Synchronization Service .................................................................................................................. 12 Windows Server 2003 (CaptureManager) .................................................................................................. 12 Windows Server 2003 (General Purpose Server) ........................................................................................ 12 Windows Server 2008R2 (Interplay Capture) ............................................................................................. 13 2. Windows Client Synchronisation ................................................................................................................... 14 NTP Configuration ............................................................................................................................................ 14 Locking to a single NTP server ..................................................................................................................... 14 Locking to dual redundant NTP servers ...................................................................................................... 15 Using ATSS with NTP ................................................................................................................................... 16 Setting the Time Zone and Regional Settings ............................................................................................. 16 ATSS (Avid Time Synchronization Service) synchronisation ............................................................................. 17 Unity MediaNetwork synchronisation ............................................................................................................. 18 Domain Time .................................................................................................................................................... 18 3. Macintosh Client Synchronisation ................................................................................................................. 19 NTP Configuration ............................................................................................................................................ 19 Setting the Time Zone and Regional Settings ................................................................................................... 20 Unity MediaNetwork synchronisation ............................................................................................................. 20 4. AirSpeed Time synchronisation ..................................................................................................................... 21 NTP Server address .......................................................................................................................................... 21 Setting the Time Zone ...................................................................................................................................... 21 Verifying Synchronisation ................................................................................................................................. 22 5. AirSpeed Multi Stream synchronisation ........................................................................................................ 23 Verifying Synchronisation ................................................................................................................................. 24 6. ALRE Time synchronisation ........................................................................................................................... 25 Setting NTP Server address and Time Zone ..................................................................................................... 25 Verifying Synchronisation ................................................................................................................................. 26 7. Unity ISIS Synchronisation ............................................................................................................................. 27 Avid Technology EMEA | Customer Success
Page 2 of 28 Time Synchronisation for Avid® Interplay™ systems
Introduction
Accurate time synchronisation is critical for all Avid® Interplay™ systems. For reliable operation, all devices which create media (such as editors, AirSpeeds, TransferManagers, etc) or which control the creation of media (such as CaptureManager servers, CaptureManager clients, etc) must have their time synchronised to within 2 seconds of incoming house time‐of‐day‐code and to each other. To keep the time‐stamp of the created media files consistent, the shared storage must also be synchronised. This document describes the tested installation procedure to configure a CaptureManager or Interplay Capture server as a reliable and accurate NTP (Network Time Protocol) server for a typical Avid Interplay™ system. Whilst the setup of the Avid Time Synchronization Service (ATSS – also known as Interplay Time Service or Framework Time Service) is also covered, be aware that AirSpeeds, Avid Low Resolution Encoders (ALREs), Clusters, System Directors and Unity ISIS blades are all unable to lock to ATSS and therefore NTP will always be required. Unless there is a compelling reason otherwise, it is wise to restrict a system to a single method of time synchronisation to avoid conflicts and so, if a system contains AirSpeeds, ALREs, one or more Windows Server Clusters and/or ISIS, NTP will usually be the time synchronisation method of choice. The standard NTP server service (W32time) supplied with Windows Server is, in fact, an SNTP server (Simple Network Time Protocol) which has proven problematic with Unix servers (i.e. AirSpeeds and ALREs). Furthermore, IPV (the manufacturers of the ALRE) have informed us that it is unsupported for use with ALREs. Following testing, the NTP Daemon or NTPD software (which is freeware, supplied by NTP.ORG and sponsored by Meinberg) has proved to be very effective as an NTP server providing that it is configured correctly. When planning a time synchronisation scheme, please refer to the document “Example Time Sync Hierarchy Flowcharts.pdf” (included in the package containing this document) to help you decide upon your specific implementation. Included with this package:
• This document (Time Synchronisation for Avid Interplay™ systems Rev.D.pdf) • NTPD “Lennon” release and configuration files (ntp‐4.2.4p8@lennon‐o‐win32‐setup.exe, ntp.conf, ntp.drift) • Adrienne 32‐bit drivers and software (AECtime.zip) • Adrienne 64‐bit drivers (AecPCIe_x64_signed.zip) • Example Time Sync Hierarchy Flowcharts.pdf Avid Technology EMEA | Customer Success
Page 3 of 28 Time Synchronisation for Avid® Interplay™ systems
1. Setting up an NTP Server
In a typical Avid Interplay™ installation, the CaptureManager server or Interplay Capture server will be configured as the time master. Typically, an Adrienne Timecode card will be installed in the server and will receive house time‐of‐day‐code. The server’s internal clock is then set to match the incoming timecode and the NTPD software will take it’s time from the internal clock. If redundant Interplay Capture servers are to be used then both should be configured as NTP masters and both NTP Server addresses specified for clients. If there is no ingest control server then the General Purpose Server (GPS) may be fitted with an Adrienne timecode card. Windows Server 2003
The Adrienne software (also known as AECtime) will typically be installed as part of the factory build but, if installation or re‐installation is necessary, a suitable version is included in the deployment package containing this document in the file AECtime.zip. To install it simply unzip the contents of the file into the folder C:\AECtime and then run the file ClkSampl.bat. This will install the AEC_NT_PCI_ClockSet_Service which synchronises the server’s internal clock to the incoming timecode. Note that any existing Adrienne software should be removed beforehand. Remove any existing service by running the file ClkSamplunload.bat and then deleting the contents of the C:\AECtime folder before proceeding to install with this version. The presence of incoming timecode can be verified by running the AecPciPoll.exe application found in the folder C:\AECtime. See Verifying the NTP Server Configuration below for more information. Windows Server 2008R2 x64
Unfortunately, the AEC_NT_PCI_ClockSet_Service will not run correctly under Windows Server 2008R2 x64 and so a different method of locking the server’s internal clock to timecode is required. Firstly, ensure that the Adrienne timecode card device driver is correctly installed in Device Manager as shown below: Fig.1.1 ‐ Aec PCIe (Adrienne) card in Device Manager under Windows Server 2008R2 Avid Technology EMEA | Customer Success
Page 4 of 28 Time Synchronisation for Avid® Interplay™ systems
If the card is not correctly installed, install the driver manually by using the appropriate button on the “Driver” tab. Do not allow Windows to install the driver automatically but instead browse to the driver file. On a standard Avid 2008R2 image this will be located at D:\Installables\Drivers\Timecode\Adrienne‐Electronics Time Code Card\AEC_PCI‐TCx64signed. If the driver is not present, please use the version contained in the file AecPCIe_x64.zip supplied with this package. Once the card is correctly installed, the Avid Time Synchronization Service should be used to lock the internal clock to timecode by selecting the options shown below: Fig.1.2 ‐ Using ATSS to lock the server’s internal clock to timecode Note that the function of the ATSS as described here is solely to set the server’s internal clock to match incoming time‐of‐day‐code. However, if ATSS is to be used to provide time synchronisation, then the settings above are appropriate for an ATSS Master for this purpose. Avid Technology EMEA | Customer Success
Page 5 of 28 Time Synchronisation for Avid® Interplay™ systems
NTPD Installation
A number of NTPD installation packages exist but the required version for reliable operation on both Windows Server 2003 and 2008R2 is 4.2.4p8 (also known as the Lennon release). This is included in the deployment package containing this document. The following instructions will configure the NTPD server software to synchronise to the internal clock. Any client synchronising to the NTP server is therefore also synchronous with house timecode. Run the executable (ntp‐4.2.4p8@lennon‐o‐win32‐setup.exe) from the CaptureManager or Interplay Capture desktop. Accept the license agreement and, after a few seconds, the following prompt will appear: Fig.1.3 ‐ NTPD Installation location To keep the installation consistent for ease of support, accept the default installation location and click “Next”. The following window will appear: Fig.1.4 ‐ NTPD Components Avid Technology EMEA | Customer Success
Page 6 of 28 Time Synchronisation for Avid® Interplay™ systems
Select all components (the space taken is very small) and click “Next”. The next prompt specifies the location of the configuration file that will be read by NTPD.EXE. Check the box “Create an initial configuration file with the following settings” and then “Add local clock as a last resort reference, Stratum:”, set the stratum to “2” as shown below and click “Next”. Fig.1.5 ‐ Options for NTP.CONF The following prompt appears. As the NTP server will be using the CaptureManager’s internal clock which is synchronized to the house timecode feed, click “Yes. Fig.1.6 ‐ Select Internal clock as master (locked to timecode) The following prompt will appear: Fig 1.6 ‐ Choose whether or not to review configuration file If you click “No”, a default file will be generated and the installation will continue. It will then be necessary to overwrite the default ntp.conf file in the folder C:\Program Files\NTP\etc with the file supplied with this document and the skip to the next section. Note that a reboot will then be required after installation in order to read this file. If a reboot will not be possible then click “Yes” and the default ntp.conf file will be opened for editing in Notepad. Avid Technology EMEA | Customer Success
Page 7 of 28 Time Synchronisation for Avid® Interplay™ systems
Make the changes highlighted below … # NTP Network Time Protocol
# Configuration File created by Windows Binary Distribution Installer Rev.: 1.16
mbg
# please check http://www.ntp.org for additional documentation and background information
# Use drift file
driftfile "C:\Program Files\NTP\etc\ntp.drift"
# your local system clock, could be used as a backup
# (this is only useful if you need to distribute time no matter how good or bad it is)
server 127.127.1.0
Ensure the “#” is removed from this line # but it should operate at a high stratum level to let the clients know and force them to
# use any other timesource they may have.
fudge 127.127.1.0 stratum 2
Ensure the “#” is removed from this line (stratum should be 2)
# End of generated ntp.conf --- Please edit this to suite your needs
Fig1.7 ‐ Modifications to the NTP.CONF file … and then save the file to continue the installation. The settings on the next screen determine which Windows User Account the NTPD service will use. Select the option for “SYSTEM” account. Note that all boxes are checked. Click “Next” Fig.1.8 ‐ Select the user for the NTPD service Click “Finish” on the final dialogue to complete the installation. Following this, navigate to the folder C:\Program Files\NTP\etc. This folder should contain the ntp.conf file either created by the installation or added by you as above. Add the file ntp.drift (supplied with this document) to this folder overwriting the existing file if there. If you do not have the ntp.drift file, a new one can be created in Notepad. Open Notepad, type “.001” (no quotes) followed by <Enter> and the save the file to ntp.drift in the folder C:\Program Files\NTP\etc. This completes the installation. If you copied the ntp.conf file supplied rather than editing it, you will need to reboot the server for this to take effect. See “Verifying the NTP Server Configuration” below for information on how to check the operation of NTPD. Avid Technology EMEA | Customer Success
Page 8 of 28 Time Synchronisation for Avid® Interplay™ systems
Setting the Time Zone and Regional Settings
Choose a Time Zone for the server which is appropriate to your location. If there will be Unix clients on the system, be sure to choose a Time Zone which is appropriate for both Windows and Unix or the Unix servers will be unable to lock. For example, GMT is the same to both Windows and Unix but an AirSpeed set to Eastern European Time will not lock to a Windows server set to Greek Time even though the actual Time Zone is the same. Note that a Windows client system set to use a 12‐hour clock will not be able to lock correctly to a time server set to use a 24‐hour clock and vice versa. As a guide, if the clock in the system tray shows “AM” or “PM” after the time then the system is most likely set to use a 12‐hour clock. Setting the Regional Options appropriately for your location will determine whether or not a 24‐hour clock is used. The default setting of “English (United States)” uses a 12‐hour clock. Changing this to “English (United Kingdom)” will change the clock to 24‐hour. This may be overridden by customising the Regional Settings; go to the Control Panel, select “Regional and Language Options”, click “Customise…” and select the “Time” tab. Avid Technology EMEA | Customer Success
Page 9 of 28 Time Synchronisation for Avid® Interplay™ systems
Verifying the NTP Server Configuration
The procedures for verifying the correct operation of an NTP server differ between Windows Server 2003 and Windows Server 2008R2. These are detailed separately below. Windows Server 2003 (CaptureManager or GPS)
The presence of incoming timecode can be verified by running the AecPciPoll.exe application found in the folder C:\AECtime. If timecode is being correctly received by the Adrienne card then it will be seen counting up in the window as shown: Timecode should be incrementing and should match both house timecode and the local PC clock Fig.1.9 ‐ Verifying incoming timecode The installation of both the Adrienne service and the NTPD service can be verified using the NTP tab of SvrPrep and selecting the “NTP Server” option as shown below: Fig.1.10‐ NTP Server not configured Fig.1.11 ‐ NTP Server correctly configured Fig.1.10 above shows that either the Timecode Card or the AEC_NT_PCI_ClockSet_Service are not installed, that NTPD is not installed and that the Windows W32time service is still running. In Fig.1.11 both the Timecode Card and NTPD are running correctly and the W32time service has been stopped by clicking the “Kill W32time Service” button. Avid Technology EMEA | Customer Success
Page 10 of 28 Time Synchronisation for Avid® Interplay™ systems
Alternatively, open the Services page in the System Management Console and verify that both the “NTPD” and “AEC_NT_PCI_ClockSet_Service” (or similar) services are running and that the “Windows Time” service is disabled and stopped. Windows Server 2008R2 (Interplay Capture)
Currently there is no application for checking incoming timecode on Windows Server 2008R2 however, when the Avid Service Framework v1.50 is released there will be an additional tab in the Avid Workgroup Properties application as shown below in Fig.1.12 and Fig.1.13: Fig.1.12 ‐ No valid timecode detected Fig 1.13 ‐ Incoming timecode displayed Avid Technology EMEA | Customer Success
Page 11 of 28 Time Synchronisation for Avid® Interplay™ systems
Avid Time Synchronization Service
Instances where NTP is not used on an Interplay system are very rare (i.e. no, AirSpeed, no ALRE, no clustered servers, no ISIS) and so the Avid Time Synchronization Service (ATSS) is unlikely to be the sole time synchronisation scheme in use. Care is required when configuring multiple synchronisation schemes to ensure that there are no conflicts. Serious consideration should be given to implementing a single scheme. If ATSS is to be used on the system then an ATSS “Master Mode” host must be configured. Windows Server 2003 (CaptureManager)
If the CaptureManager server is already the NTP server (and locked to house timecode) then it can also function as an ATSS master. Configure ATSS as shown in Fig.1.14 below: Fig.1.14 ‐ ATSS Time Master configuration on an NTP server Note that the service is configured to “Get Time Sync reference from the local PC clock”. As the local clock is locked to incoming timecode, the ATSS will also be synchronised. Do not use the option to “Get Time Sync reference from an Internal TimeCode Reader” under Windows Server 2003. Windows Server 2003 (General Purpose Server)
For systems where there is no Interplay Capture or CaptureManager server and NTP synchronisation is provided by an external (i.e. non‐Avid) server, another server can be nominated as the ATSS master. Configure the ATSS master server as a standard NTP Client (see Windows Client Synchronisation below) and then configure ATSS as shown in Fig.1.14 above. Alternatively, configure the ATSS to read directly from an NTP server as shown below: Fig.1.15 ‐ ATSS Time Master configuration on non‐NTP server Avid Technology EMEA | Customer Success
Page 12 of 28 Time Synchronisation for Avid® Interplay™ systems
Windows Server 2008R2 (Interplay Capture)
If the Interplay Capture server is already the NTP server (and locked to house timecode) then it can also function as an ATSS master. Configure ATSS as shown in Fig.1.16 below: Fig.1.16 ‐ Configuring a Windows Server 2008R2 server as an ATSS master Avid Technology EMEA | Customer Success
Page 13 of 28 Time Synchronisation for Avid® Interplay™ systems
2. Windows Client Synchronisation
Windows clients are set by default to use the W32time service synchronise their time every 7 days to an internet NTP server (usually time.windows.com). This is not suitable for Interplay client systems as their time must be locked to system timecode and the internal clock will drift by more than the allowable tolerance over the 7 day period. NTP Configuration
Windows clients should be set to resynchronise with the NTP server every 1‐3 hours to maintain an accurate time. This is especially important with older hardware where the internal battery which maintains the clock is reducing in voltage. Locking to a single NTP server
NTP client settings can be easily configured by using the NTP tab of either EdPrep or SvrPrep as shown below in Fig.2.1. This shows a typical set‐up for an Interplay client PC synchronising to a single NTP server: Client is set to resync every 3 hours Client is set to lock to server ETSG‐CM01 Service must be restarted
to apply changes Connection to the NTP server is good Local clock has synched with the NTP server Fig.2.1 ‐ Configuring a Windows client with EdPrep Avid Technology EMEA | Customer Success
Page 14 of 28 Time Synchronisation for Avid® Interplay™ systems
Locking to dual redundant NTP servers
If dual‐redundant Interplay Capture servers are to be used as NTP Masters then both addresses should be entered in the address box separated by a space as shown in Fig.2.2 below. Note that the delimiting character must be a space ‐ commas or semicolons will not work. Client is set to resync every 2 hours Client set to lock to either
ETSG‐IC01 or ETSG‐IC02 Service must be restarted
to apply changes Connection to the NTP server cannot be verified
Local clock has synched with an NTP server Fig.2.2 ‐ Configuring a Windows client with SvrPrep for dual redundant NTP servers Note that, when dual NTP servers are specified, the “Check Connection to NTP Server” of EdPrep and SvrPrep does not function correctly as it will try to ping both addresses simultaneously and fail. Avid Technology EMEA | Customer Success
Page 15 of 28 Time Synchronisation for Avid® Interplay™ systems
Using ATSS with NTP
When using NTP for synchronisation, you can install the ATSS but should disable it as shown in Fig.2.3 and Fig.2.4 below. The ATSS will continue to provide accurate time‐stamps for Interplay Log Files but not cause a conflict by trying to set the system’s internal clock. Fig.2.3 ‐ ATSS installed but not setting internal clock Fig.2.4 ‐ Workstation Service installed but not setting internal clock Setting the Time Zone and Regional Settings
Select an identical Time Zone for the client to that set on the NTP server. The client will fail to lock to a server set to a different Time Zone. Set the system’s Regional Settings to match the server and determine whether or not a 24‐hour clock is to be used. The clock setting for the selected locale may be overridden with the Regional Settings in Control Panel. See the section Setting the Time Zone and Regional Settings above for more information. Avid Technology EMEA | Customer Success
Page 16 of 28 Time Synchronisation for Avid® Interplay™ systems
ATSS (Avid Time Synchronization Service) synchronisation
If you have decided to use ATSS instead of NTP on a client you should first disable the Windows Time service. This can be done easily using the NTP tab of either EdPrep or SvrPrep as shown in Fig.2.5 below: Select the option “NTP not used” Ensure that the NTP service is stopped Fig.2.5 ‐ Turning off NTP with EdPrep Configure the Avid Time Synchronization Service itself as shown in Fig.2.6 making sure to check the option to “Set the local PC clock to match the ‘Workgroup’ time” option. An ATSS Master must be configured for the client to lock to ‐ see the section Avid Time Synchronization Service in Part.1 above for more information. Fig.2.6 ‐ ATSS Client configuration Avid Technology EMEA | Customer Success
Page 17 of 28 Time Synchronisation for Avid® Interplay™ systems
Unity MediaNetwork synchronisation
If the system is a Unity MediaNetwork Fibre Attached client then you may decide to use Connection Manager to synchronise with the File Manager or MediaEngine by selecting “Synchronise your system’s clock with the server’s clock” from the Advanced options as shown in Fig.2.7 below: Fig.2.7 ‐ Configuring Windows Connection Manager When using this feature, ATSS should not be used and the Windows Time Service (NTP) should be disabled locally. This can be easily performed with EdPrep as shown in Fig.2.5 above. Note that an Avid Unity MediaEngine should never be configured as an NTP server. To ensure that Unity MN clients which are synchronised by the above method receive an accurate time, the MediaEngine should be locked to an external NTP server in the same way as any other Windows client. Domain Time
In a domain environment, domain controllers can broadcast time stamps to the computers in the domain, most likely in conflict with NTP or ATSS. If using either of these please ensure that domain time is disabled. Domain time is difficult to synchronise with timecode and should be avoided unless absolutely required. If domain time is to be used, the domain controller must be synchronised to a time server which is, in turn, synchronous with house time‐of‐day‐code. In line with Avid recommendations, ensure that all Avid machines are in their own domain which has its own Active Directory and DNS and establish a trust to the in‐house domain. Avid Technology EMEA | Customer Success
Page 18 of 28 Time Synchronisation for Avid® Interplay™ systems
3. Macintosh Client Synchronisation
Most Macintoshes are set by default to synchronise their time with an internet NTP server (usually time.apple.com, time.euro.apple.com or time.asia.apple.com). This is not suitable for Interplay client systems as the time must be locked to system timecode with a tolerance of 100 frames. NTP Configuration
As a flavour of Unix, MacOS‐X runs an NTP daemon by default. To configure this to lock to the Capture or CaptureManager server, open the “Date & Time” dialogue by clicking on the clock at the top left of the screen and selecting “Date & Time Preferences …” as shown: Fig.3.1 – Macintosh Date & Time preferences You will then be presented with the following dialogue where the address of the NTP server can be entered: Fig.3.2 – Synchronising the Macintosh clock You should see the clock lock to the server fairly soon after entering the new address. Alternatively, open a terminal window and use the Unix command‐line commands NTPDC and NTPDATE as described in the AirSpeed Time Synchronisation section below. Avid Technology EMEA | Customer Success
Page 19 of 28 Time Synchronisation for Avid® Interplay™ systems
Setting the Time Zone and Regional Settings
Select an identical Time Zone for the client to that set on the NTP server. The Macintosh will fail to lock to a server set to a different Time Zone. Set the Mac’s Time Zone to match the server from the following dialogue: Fig.3.3 – Setting the MacOS time zone Unity MediaNetwork synchronisation
If the Macintosh is a Unity MediaNetwork Fibre Attached Client then you may decide to use Connection Manager to synchronise with the File Manager or MediaEngine by selecting “Synchronise the system clock with the server” as shown in Fig.3.4 below: etsg-mn01
Fig.3.4 Configuring Connection Manager This option is not available for Fibre Attached Clients which should be configured to use NTP Instead as described above. Avid Technology EMEA | Customer Success
Page 20 of 28 Time Synchronisation for Avid® Interplay™ systems
4. AirSpeed Time synchronisation
The original AirSpeed (FreeBSD Unix Operating System) runs NTPD by default. This is configured as follows: NTP Server address
Use VNC to access the AirSpeed GUI, go to the setup page, select the Network tab and check that the IP address of the NTP server is entered correctly as shown below: Fig.4.1 ‐ AirSpeed NTP Server not set Fig.4.2 ‐ AirSpeed NTP Server set correctly Once entered you will be prompted to restart the AirSpeed. If, when the unit has restarted, the NTP Server field remains blank and the indicator remains dark then the AirSpeed is unable to contact the NTP server. If the correct address was entered then the network configuration should be checked and rectified. Setting the Time Zone
To perform the following actions, connect to the AirSpeed via telnet either the Windows command‐line, PuTTY or another Telnet application with the following credentials: Login Name: maint
Password: mars
The Time Zone on an AirSpeed is set by copying (or creating a symbolic link to) a suitable “zoneinfo” file to the file “localtime” in the folder /etc. The following example shows how to set the time zone to GMT. At the % prompt type the following: cp /usr/share/zoneinfo/GMT /etc/localtime
This will copy the file GMT from the folder zoneinfo to the file localtime in the folder etc. Alternatively, create a symbolic link by typing the following commands at the % prompt: cd /etc
rm localtime
ln -s /usr/share/zoneinfo/GMT localtime
This will create a symbolic link to the file which has the advantage that you can see which time zone the AirSpeed is set to by typing the following command: ls -l /etc/loc*
[etsgas-1 ]% ls -l loc*
lrwxr-xr-x
1 root
wheel
-rw-r--r--
1 root
wheel
23 Jul
5 14:36 localtime -> /usr/share/zoneinfo/GMT
619 Oct 27
2003 locate.rc
Fig.4.3 ‐ Checking the time zone on an AirSpeed The above example shows how to set the time zone to GMT. If a different time zone is required then those available can be displayed by typing the following line at the % prompt: ls /usr/share/zoneinfo
Substitute the name of the chosen time zone file for “GMT” in the above examples (remember that Unix is case sensitive). Note that the zoneinfo folder contains further time zone files in various subdirectories. Avid Technology EMEA | Customer Success
Page 21 of 28 Time Synchronisation for Avid® Interplay™ systems
Verifying Synchronisation
To check that the AirSpeed is synchronised with the NTP server, type the following at the % prompt: Type date to check the current date, time and time zone Type ntpdate –u <NTP server IP Address> to force an update from the NTP server Type date again to check that the new date and time are correct Type ntpdc –c peers to check that the system is locked to the NTP server [etsgas-1]% date
Thu Nov
6 17:49:10 GMT 2010
[etsgas-1 ]% ntpdate -u 10.134.104.190
6 Nov 18:33:57 ntpdate[1104]: step time server 10.134.104.190 offset 10528.125687 sec
[etsgas-1 ]% date
Thu Nov
6 18:34:11 GMT 2010
[ingest7]% ntpdc -c peers
remote
local
st poll reach
delay
offset
disp
=======================================================================
*etsg-cm01.etsg. 10.134.104.190
3
128
377 0.00017
0.002198 0.00534
[etsgas-1 ]%
Fig.4.4 ‐ Verifying AirSpeed NTP synchronisation The “*” character just before the FQDN (Fully Qualified Domain Name) of the NTP server (shown here as etsg‐cm01.etsg) indicates that the machine is locked. A “=” sign just before the FQDN of the NTP server would indicate that a valid NTP server has been found but the system is not yet locked to it. If neither are present (i.e. a space character) then the NTP server cannot be contacted. Additionally, the AirSpeed’s “NTP Server” indicator (see above) will remain dark and the server address will not be retained. The network configuration should be checked and rectified. The Stratum will be around 3 when the system is time locked. If the ntpdate ‐u command is not used then the system will take about 45 minutes to settle automatically. This will be more rapid (about 2 minutes) the next time the machine is restarted. Avid Technology EMEA | Customer Success
Page 22 of 28 Time Synchronisation for Avid® Interplay™ systems
5. AirSpeed Multi Stream synchronisation
AirSpeed Multi Stream servers have ATSS installed by default but may, under some circumstances produce a status of “Unstable” in the Avid health monitor as shown below. Fig.5.1 ‐ Interplay Health Monitor showing Unstable time sync To resolve this (or to use NTP instead of ATSS) you can use NTP as the time synchronisation method. Unfortunately, the standard Microsoft W32time SNTP service does not work well on AMS so a local installation of NTPD must be performed. First, disable ATSS time synchronisation as shown in Fig.5.2 below: Fig.5.2 ‐ Disable ATSS in AMS Workstation service Following this, install NTPD as described above in the section NTPD Installation and proceed as described until you receive the following prompt: Fig.5.3 ‐ Prompt to modify the NTP.CONF file Avid Technology EMEA | Customer Success
Page 23 of 28 Time Synchronisation for Avid® Interplay™ systems
Select “Yes” and then make the changes to the configuration file as highlighted below: # NTP Network Time Protocol
# Configuration File created by Windows Binary Distribution Installer Rev.: 1.16
mbg
# please check http://www.ntp.org for additional documentation and background information
# Use drift file
driftfile "C:\Program Files\NTP\etc\ntp.drift"
# your local system clock, could be used as a backup
# (this is only useful if you need to distribute time no matter how good or bad it is)
server <NTP Server Address>
Remove the “#” from this line and enter the address of the NTP Server # but it should operate at a high stratum level to let the clients know and force them to
# use any other timesource they may have.
# fudge 127.127.1.0 stratum 2
# End of generated ntp.conf --- Please edit this to suite your needs
Fig.5.4 ‐ Modifying the NTP.CONF file for AirSpeed Multi Stream For <NTP Server Address> enter the IP address of the NTP server and then save the file to continue the installation and continue to proceed as described. Note that you may be required to reboot the AMS to complete the installation. Verifying Synchronisation
To check that the AMS is synchronised with the NTP server, open a command prompt at “C:\Program Files\NTP” (or whatever location you chose to install NTPD if different) and type the following: Type ntpdate –u -b <NTP server IP Address> to force an update from the NTP server Type ntpdc –c peers to check that the system is locked to the NTP server [ETSG-AMS01]
C:\Program Files\NTP>ntpdate -u -b 10.134.106.20
5 Jul 13:22:53 ntpdate[2848]: step time server 10.134.106.20 offset 0.006466 sec
[ETSG-AMS01]
remote
C:\Program Files\NTP>ntpdc -c peers
local
st poll reach
delay
offset
disp
=======================================================================
*etsg-cm01.etsg. 10.134.104.190
[ETSG-AMS01]
3
128
377 0.00019
0.003264 0.00174
C:\Program Files\NTP>
Fig.4.4 ‐ Verifying AirSpeed NTP synchronisation The “*” character just before the FQDN (Fully Qualified Domain Name) of the NTP server (shown here as etsg‐cm01.etsg) indicates that the machine is locked. A “=” sign just before the FQDN of the NTP server would indicate that a valid NTP server has been found but the system is not yet locked to it. If neither are present (i.e. a space character) then the NTP server cannot be contacted. The Stratum will be around 3 when the system is time locked. If the ntpdate ‐u ‐b command is not used then the system will take about 15 minutes to settle automatically. This will be more rapid (about 2 minutes) the next time the machine is restarted. Avid Technology EMEA | Customer Success
Page 24 of 28 Time Synchronisation for Avid® Interplay™ systems
6. ALRE Time synchronisation
Like most Unix systems, ALREs run an NTP Daemon by default. The time, date and current time zone may be set from here by clicking on the Adjust button as shown below: Fig.6.1 ‐ ALRE Main Page Fig.6.2 ‐ Setting ALRE time, date and time zone Setting NTP Server address and Time Zone
The address of the NTP server may be viewed and changed from the Configure page. Select Configure from the menu on the left and then click the Edit button to make changes if required: Fig.6.3 ‐ ALRE Configuration page Fig.6.4 ‐ Editing the ALRE configuration Enter the IP address of the NTP server in the NTP Servers box, select a suitable time zone (if not set above) from the combo box and apply the changes. This will return you to the Configure page where you will need to click the Update nSpectreAMS now button. A restart should not be necessary unless you have made any other changes. Avid Technology EMEA | Customer Success
Page 25 of 28 Time Synchronisation for Avid® Interplay™ systems
Verifying Synchronisation
To check the synchronisation you will need to connect to the ALRE via telnet using either the Windows command‐
line, PuTTY or another Telnet application with the following credentials: Login Name: root
Password: willywonka
To check that the ALRE is synchronised with the NTP server, type the following at the # prompt: Type date to check the current date, time and time‐zone Type ntpdate –u < NTP server IP Address> to force an update from the NTP server Type date again to check that the new date and time are correct Type ntpdc –c peers to check that the system is locked to the NTP server: [root@etsg-lr01 ~]# date
Tue Nov 11 09:00:10 WET 2008
[root@ etsg-lr01~]# ntpdate -u 10.134.104.190
11 Nov 11:55:57 ntpdate[1104]: step time server 10.134.104.190 offset 10528.125687 sec
[root@ etsg-lr01~]# date
Tue Nov 11 11:56:06 WET 2008
[root@ etsg-lr01~]# ntpdc -c peers
remote
local
st poll reach
delay
offset
disp
=======================================================================
*etsg-cm01.etsg. 10.134.104.190
3
64
377 0.00023 -0.000482 0.00266
[root@ etsg-lr01 ~]#
Fig.6.5 ‐ Verifying ALRE NTP synchronisation The “*” character just before the FQDN (Fully Qualified Domain Name) of the NTP server (shown here as etsg‐cm01.etsg) indicates that the machine is locked. A “=” sign just before the FQDN of the NTP server would indicate that a valid NTP server has been found but the system is not yet locked to it. If neither are present (i.e. a space character) then the NTP server cannot be contacted and the network configuration should be checked and rectified. The Stratum will be around 3 when the system is time locked. If the ntpdate ‐u command is not used then the system will take about 45 minutes to settle automatically. This will be more rapid (about 2 minutes) the next time the machine is restarted. Avid Technology EMEA | Customer Success
Page 26 of 28 Time Synchronisation for Avid® Interplay™ systems
7. Unity ISIS Synchronisation
In order to ensure that all media files are appropriately time stamped, both ISIS System Directors must be accurately time synchronised. It is not supported to install the Interplay Framework on System Directors and so they must be configured as NTP clients (see Windows Client Synchronisation above) in order to synchronise to the time server. Each ISIS Switch and Storage blade runs a Unix Operating System and an NTP Daemon should be enabled to ensure that each is on the correct time. Note that ISIS blades are not DST aware. All blades can be set simultaneously with a single operation through an ISIS Switch Blade Agent, preferably the stack master. Log into the ISIS Blade Agent (password: se-admin) and choose Basic from menu on the left. You will see a screen similar to that below. Check the Enable network time protocol box to enable the daemon, enter the NTP server address in the first box, set the Time Zone and click the submit button. If there are dual redundant Interplay Capture servers as NTP Masters, enter the address of both servers in the two boxes. Fig.7.1 ‐ ISIS Blade Synchronisation A screen showing progress of the operation will be displayed and the operation should complete after a short while. Note that there may be an interruption to the operation of the ISIS while this happens, so do not perform this operation at a critical time. Avid Technology EMEA | Customer Success
Page 27 of 28 Time Synchronisation for Avid® Interplay™ systems
Notes
EdPrep, SvrPrep and the package containing this document may be downloaded from http://emeacs.avid.com and may also be requested from Avid support staff. EdPrep and the package containing this document may also be downloaded from the Avid Knowledge base. EdPrep is also available for download outside Avid from http://www.preptools.net. Time Synchronisation for Avid Interplay™ systems Simon Dorricott Avid CS EMEA Revision D ‐ July 2011 Avid Technology EMEA | Customer Success
Page 28 of 28 
Download PDF
Similar pages