ADC List Redundancy Control Client

Transcription

1 ADC List Redundancy Control Client 8-June-2015 Revision: Release

2 Publication Information 2015 Imagine Communications Corp. Proprietary and Confidential. Imagine Communications considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine Communications. All others uses are illegal. This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product. Trademarks Product names and other appropriate trademarks, e.g. ADC, D-Series, Nexio Insight, Nexio Motion, PowerSmart, Versio are trademarks or trade names of Imagine Communications or its subsidiaries. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies. Contact Information Imagine Communications has office locations around the world. For domestic and international location and contact information, visit our Contact page ( Support Contact Information For domestic and international support contact information see: Support Contacts ( ecustomer Portal ( Academy Training ( Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 2

3 Contents Contents List Redundancy Overview... 6 About List Redundancy... 6 Functions... 7 List Redundancy Control Client (LRCC)... 9 Configuration Requirements ADC Files for List Redundancy UserCons.Inc UserDefs.Inc Device Server Configuration Requirements Time Code Networking RAN.ini File Setting the TCP-IP socket port number Missing Events Management Devices and Lists Configuration Parameters Prerolls/Postrolls Parameters Effect Duration Configuration List Options Transmission: Parameters Configuration List Options TRANSMISSION Options Configuration List Options TRANSMISSION Mix/Wipe Configuration Make the SLAVE list Lookahead follow the MASTER list Lookahead Lookahead in events only List Options Configuration Mirroring and Synchronization Control About Mirroring and Synchronization loss Installing the List Redundancy Control Client Introduction Installation of the LRCC Application List Redundancy Control Client File Location Create a shortcut to LRCC.exe Installation of the Sealevel 8011 GPI board (for Tally) in LRCC station Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 3

4 Contents GPI Wiring Schematic List Redundancy Control Client Application About the Application About assuming direct control of a slave list Start / Stop the application To Start the LRCC application To Stop the LRCC application Troubleshooting a Restart after a Device Server Crash Administration To Log In User Account Types Change User function Configuring the LRCC and LR Channels Properties Menu Device Servers Configuration Device Servers Configuration Screen Device Servers Configuration Window Controls Diagnostic Function Access Device Server Properties Screen Editing a Device Server Entry Tallies Configuration Tally Properties LR Channels Configuration LR Configuration Screen LR Configuration Table Columns LR Channels Configuration Screen Buttons Defining the Redundant Lists of a Channel LR Channel Properties Screen: Define the Tally Environment Configuration Admin Password Log setup List Redundancy Control Client Console Introduction Main Console Menus Operation Menu Configurations Menu View Menu Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 4

5 Contents Help Menu Main Console Buttons for a Given LR Channel and Related Confirmation Windows Confirmation Window: Main Console Status and Information Each LR Channel, from Left to Right Disable List Redundancy Error Messages in LR Channel Status Bar Error Messages in Console Status Bar Error Messages for LR Channel Connection / Comms / Config Status in LR Channel Console Operation Menus Diagnostic Logging About LR Logging To use Logging About Device Server Debug Logging Switch Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 5

6 List Redundancy Overview List Redundancy Overview About List Redundancy List Redundancy is an option of the ADC Device Server that is designed to add extra security to the automated broadcast system playout. Since this feature is only useful for the play out, the feature is only applied to transmission lists and not to media lists, GMT lists and so on IMPORTANT: This section only provides fundamental Device Server setup reference information as it pertains to List Redundancy Client. For details on configuring List Redundancy see "Device Server and Config Tool Install and Configuration ". Cloning and List Redundancy are considered mutually exclusive functionalities. Purchase Note: List Redundancy is a for-purchase option to Device Server. Contact your Automation Sales representative. About Screen Shots in this document: The List Redundancy option is available for ADC v11 systems and ADCv12 systems. The screen shots used in this document were chosen to provide a standard look and feel for the content and represent equivalent functionality available across all systems. Your system screens may look different. Note: List Redundancy and LinkList can coexist on the same ADC system, but not use the same lists. List Redundancy uses two Transmission Lists running the same programs in parallel, and independently, from distinct but similar devices (mostly videodisks) - if a problem occurs on one of the redundant lists, due to a device error for instance, the other redundant lists will keep on playing. These lists can run on two Device Servers (MAIN & BACKUP) simultaneously. To achieve this, both lists must have the same event content, e.g. the lists are mirrored, and must be synchronized to play out events in a synchronous way. The List Redundancy gives a control on the Mirroring and on the Synchronization to the operator. In order to have both redundant lists mirrored and synchronized, one redundant list has to provide all needed information to the other. So, the list providing information is called the Master List and the list receiving information is called the Slave List. Editing the Air Client connected to the Master List will automatically make the same edits to the Slave list. Same program: The List Redundancy guaranties that the Master List is mirrored into the Slave List, and so that both lists have the same content. Same running point: The List Redundancy guaranties that Master List and Slave List are synchronized, and so that programs are running the same way Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 6

7 List Redundancy Overview Overall control: The List Redundancy gives operators the ability to manually control the above functions. List Redundancy Process Insert 1 Device Server A MASTER LIST 2 Insert Freeze Play List Device Server B MASTER LIST Freeze Play DEVICE 3 Device Server C DEVICE 1 An operator inserts an event into the Master List. SLAVE LIST SLAVE LIST DEVICE 2 The command is echoed to the related Slave List, if the list content or state has changed. 3 The Slave List refreshes its content. DEVICE Functions The List Redundancy provides following major functions: Master List / Slave List For a given transmission channel, Master and Slave Lists can use their own controlled devices to do play out, they can also share some of devices (normally assigned to the Master List). The Slave List handles the missing media, and keeps the synchronicity with the Master List when the Master List is malfunctioning, and allows the operator to use the Slave List to control program play out. Note: If an operator attempts to use the Control Panel to edit or control a slave playlist, a warning/error message is displayed indicating "the operation can't be applied to slave list." List Mirroring The List Mirroring guaranties that both redundant transmission lists have the same content. List Synchronization The List Synchronization guaranties that both redundant transmission lists have the same running point. Note: Synchronization should not be started while the system is playing an upcount event 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 7

8 List Redundancy Overview About SyncSkip A SyncSkip mechanism was added to Air Client and Device Server to provide synchronous playout of commercials across multiple lists. Implementation required changes in Device Server and in Air Client. Since List Redundancy is used to synchronize lists and to keep the up-to-date copy of Master list, it was also expanded to support the new SyncSkip command. The SyncSkip command concept is that the next event with a designated sequential Seg # becomes equal to the remaining part of the current event. Since each of these events represent the entire program, the SOM of the next event is shifted to the EOM point of the current event and the DUR of the next event is made equal to the remaining DUR of the current event. Note: For details see Air Client v Operations, section On-Air Playback Operations > Using SyncSkip. SyncSkip informational warnings Device Server v12.23 and higher support Informational Warnings with the SyncSkip functionality. Now when Air Client sends ListSyncSkipEvent API command: Air Client waits for a reply to ListSyncSkipEvent command. If the reply contains an error status, an appropriate error message is displayed. When the Device Server receives a ListSyncSkipEvent API command, the Device Server verifies the value of the resulting duration. If it is more than preroll, normal status is returned as a response to ListSyncSkipEvent command. If duration is less than preroll, an appropriate error status is returned. If duration is negative, it is populated with 00:00:00.00 and an appropriate error status is returned. Note. Negative duration is impossible. When performing SyncSkip, server subtracts the preroll value from the remaining clip duration. However, if the remaining duration is less than the preroll, SyncSkip isn t executed (as well as normal Skip). "Auto Ripple Times", "Timed List" and "Update On-Air Time" "Auto Ripple Times", "Timed List" and "Update On-Air Time" are necessary for List Redundancy. As soon as an LR pair is configured, these options are always on. They are important for LR synchronization, it can't be executed correctly if events are not rippled. When LR channel is removed from LRCC, the user can disable these options Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 8

9 List Redundancy Overview List Redundancy Control Client (LRCC) The List Redundancy Control client is a separate client application that runs on its own dedicated station PC. It allows the operator to change the Master/Slave status of redundant lists at any time. The LRCC manages the List Redundancy API and allows the List Redundancy Control application to fully control the List Redundancy feature within Device Servers. LRCC API Functions This LRCC API allows: The List Redundancy configuration (which Device Server, which lists to mirror). The List Redundancy monitoring (which list is Master, communication status,.etc.). The List Redundancy control of the LR channels defined for it (set as Master, resynchronization, etc...). LRCC Application Functions The List Redundancy Control client application functions include: The ability to handle a Tally signal in order to automatically disable the List Redundancy mechanism in case of a problem (with a procedure to restore the normal situation) and set the Master/Slave status of the lists. For one (or several) transmission channel(s), it provides the operator with information about: The Master and Slave lists statuses related to List Redundancy: Master, Slave, Mirrored, Synchronized Communication dynamic statuses between applications (List Redundancy modules of the Device Servers, Redundancy Control client) Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 9

10 List Redundancy Overview For one (or several) transmission channel(s), it allows a manual control on the List Redundancy mechanism the operator through specific buttons or functions: Disable List Redundancy (mirroring and synchronization disabled), Define which list is Master, Enable mirroring, Enable synchronization, Resynchronize Slave list (resynchronize on next event) without incidence on the playing event, Resynchronize Slave list in segmented mode on the playing event as soon as possible. Displays status information of up to 16 redundant playlists. The following is an example of the LRCC screen for 2 of the possible 16 play lists: ADC List Redundancy (LR) allows manual synchronization by an operator during up-counting events on transmission lists. While an up-counting event is playing, if an operator clicks the Start-Sync key and chooses "Synchronize in Certain Seconds" from the LRCC, the master list sends out a Sync Event to the slave list. The Sync Event is an "AUO" (Auto-start, Up-counting, On-timed) event; its start time equals the current time plus a pre-defined Sync Delay Time (such as 10 seconds). When the slave list receives the Sync Event, it updates it to the current event. After the pre-defined Sync Delay Time has elapsed, the Sync Event starts in the slave list and the LRCC shows the list Sync is "ON". When both lists are playing, the SOMs and Durations of both events in both lists may appear different. This difference does not affect a switch-only event s synchronization; it is ignored and both lists are kept playing. In this state, when an operator clicks Skip or Roll key in the Control Panel of Air Client, both master and slave list simultaneously skip to the next event, and the list keeps synchronized. Defined Limitations To make the Sync or Re-Sync function work while the current event is in up-counting, and to prevent/introduce side effects to current list functions, the following limitations are implemented: Synchronization should not be started while the system is playing an upcount event. Synchronize in Certain Seconds: The only chance to synchronize lists on an up-counting event is at the beginning of the up-counting event. Since the up-counting event is usually a switch-only event, the "Synchronize in Certain Seconds" function ignores the SOM and Duration synchronization. Note: This function does not support disk and tape up-counting. Auto Re-sync: The Auto Re-sync function no longer works during the up-counting event. This is because the "Auto Re-sync" function is used to keep the disk playing with both source contents in sync, and the up-counting event is typically a switch-only event that doesn t have disk content associated with it. Sync on Next Event: The "Sync on Next Event function", is available for up-counting events only if the "Enable Sync on Next Event During Upcounting" configuration is enabled in List Options. It is 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 10

11 List Redundancy Overview recommended that this function only be used when there is sufficient time left in the up-counting event to allow for the List Re-sync (more than 10 seconds). Note: If a Re-sync is performed while the up-counting event is counting down then the List Re-sync is complete. If a Re-sync is performed while the up-counting event is counting up then The Slave List will do re-sync about every 10 seconds. Warning: Make sure that the Slave List is playing the up-counting event before Skipping out of the event on the Master List Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 11

12 Configuration Requirements Configuration Requirements ADC Files for List Redundancy The LRCC application uses an Air Client 32 bit connection type, and uses Netbeui protocol to connect to the Device Server(s). ADC builds must include the corresponding connections. Parameters in red on yellow background in the UserCons.Inc and UserDefs.Inc files examples below are related to List Redundancy. UserCons.Inc 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 12

13 Configuration Requirements When four lists are set to be redundant, as in the following example: MaxRedSeqLists = 4 in an ADC build, it is necessarily the four first lists (List 1 to List 4). It is important, that only several transmission lists support List Redundancy feature. This amount is determined by value maxredseqlists in file "Usercons.inc". By default this value is equal to 4 and lists 1-4 support List Redundancy. If you are not exactly sure about amount of LR lists, you can look at list properties in Config Tool. If there is tab List Redundancy there, this list supports LR. If you try to connect LR Channel, containing list, which doesn t support List Redundancy, this channel will never be connected. UserDefs.Inc 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 13

14 Configuration Requirements The LR modules of connected ADC applications can use Netbeui through Automation LAN, or TCP-IP through RAN (Redundant Array Network) dedicated LAN to interconnects. If Netbeui is used: If TCP-IP is used: Device Server Configuration Requirements The Device Servers and LRCC must be configured properly before start of using List Redundancy. The following Device Server requirements are necessary for List Redundancy operations. Time Code The Device Servers connected to a system with List Redundancy must be synchronized with the same Time Code reference. Some List Redundancy commands are timed stamped. Networking The following are Device Server networking requirements. When using a 100 BaseT Network When LRCC is running with ADC Automation using at 100 BaseT Network: A second Ethernet port and LAN (specific hub or switch) must be used On the Device Server the second Ethernet port can be used 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 14

15 Configuration Requirements When using a GigE Network When LRCC is running with ADC using a GigE network, it is recommended to use one network only for Automation and List Redundancy. Ensure the LRCC connects through the Automation Network GigE network. This is done by changing the IP addresses in the c:\ran.ini to point to the Automation NICs on the Master and Slave Device Servers. The following is an example of ran.ini which lives on the root c:\ran.ini on MAIN & BACKUP Device Server. IMPORTANT: LRCC may require several seconds to perform disconnection with servers and ultimately display correct status of servers and channels. This time is variable and is reliant upon the condition of the network layer: if there is data which still isn t read from the completion port, the network layer waits for 5 seconds before destroying the connection. RAN.ini File The RAN.ini file must be created and placed in the C:\ directory of each Device Server. The RAN.ini file contains required information about the Device Servers on the List Redundancy network, or Redundant Array Network (RAN); it should contain handles, names and IP-addresses of servers. This is a manually edited file, copied to the C:\ directory of the Device Server(s) on the RAN. Once this file has been created, please restart Device Servers, as they read information from "RAN.ini" file only during start-up. The file must be updated at every instance if a new Device Server is added to the RAN, or if the TCP-IP address of an existing Device Server is changed. Also if you already have "RAN.ini" file with specified server s handles, then you start Device Server and found out that its handle doesn t match with handle in "RAN.ini" change Device Server s handle and restart Device Server. Note: For GigE Networking see above: Using a GigE Network (see "When using a GigE Network" on page 15) Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 15

16 Configuration Requirements Content of a RAN.ini File [GlobalParameters] RAN_IP_Port=10520 [DeviceServer1] DS_Handle=1 DS_Name="MAIN1" DS_IPAddress=" " [DeviceServer2] DS_Handle=2 DS_Name="MAIN2" DS_IPAddress=" " [DeviceServer3] DS_Handle=11 DS_Name="BACKUP1" DS_IPAddress=" " Setting the TCP-IP socket port number In the [GlobalParameters] section of RAN.ini file, set the TCP-IP socket port number to be used to interconnect the LR modules of the ADC: RAN_IP_Port= parameter. Examples of usable port numbers (normally available): 10520, 10521, 10550, If there is no [GlobalParameters] section in the RAN.ini file, then IP port 8000 is used by default. CAUTION: RAN_IP_Port (the socket port used for LR connection between Device Servers) is different than TCP-IP Socket Listen Port (10052 by default). Use a different port number To Determine the Current TCP/IP Listen Port of an ADC Server From the Device Server main menu select File > TCP/IP Networking Properties. The TCP/IP Networking Properties dialog is displayed showing the specified TCP/IP Socket Listen port Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 16

17 Configuration Requirements To Select a Different Port (if Default Port is in use) If default Port 8000 is in use by another device, select a port not in use. To get the list of TCP-IP ports used on a machine, in a DOS prompt type: NETSTAT a more 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 17

18 Configuration Requirements Missing Events Management For Missing Event Management, one or several Switch Only Device (missing) events must be configured. This simulates the playback of the missing events, usually on the Slave List. Shared devices between Master (Main) List and Slave (Backup) List keep the synchronization between the two redundant lists. CAUTION: Assigning a Switch Only Device (missing) to a List, changes the device s missing event management. The Skip Bad Event parameter has no effect. The missing events are not skipped, and the List does not stop, on missing events. The Switch Only Device (missing) allows a source on air to switch, through the Audio/Video path, while simulating the playback of a missing clip. This creates a third way to manage missing media reaching air time, which should not occur in the On Air List (Master for LR), but can occur in the On Line (Slave for LR) because of shared devices connected to the Device Server of Master List, and not to the Device Server of Slave List. Devices and Lists Configuration Parameters The two lists of a List Redundancy channel must have some identical parameters to keep them synchronized. The following List Configuration parameters should be identical between both Lists, especially the timing parameters: List Pre-Roll / Post Roll Effect Speeds Instant Roll) 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 18

19 Configuration Requirements For security, the List Redundancy mechanism reports the parameters of the Master List to the Slave List, when the LR channel is configured. This is true for parameters that affect synchronization of both lists (not for all their parameters). Prerolls/Postrolls Parameters The circled fields must be identical on both redundant lists. Effect Duration Configuration The circled fields must be identical on both redundant lists Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 19

20 Configuration Requirements List Options Transmission: Parameters Configuration The circled fields must be identical on both redundant lists. List Options TRANSMISSION Options Configuration The circled fields must be identical on both redundant lists Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 20

21 Configuration Requirements List Options TRANSMISSION Mix/Wipe Configuration The circled fields must be identical on both redundant lists. Make the SLAVE list Lookahead follow the MASTER list Lookahead ADCv11.60 and higher adds the ability to make the Lookahead on the SLAVE list follow the value of the Lookahead that is set on the MASTER list. To enable/disable this feature the configuration option "Enable Copy Lookahead Value from Master List to Slave" has been added to the "List Redundancy" tab of the List Options configuration the in Config Tool. If this option is enabled/disabled on the Master list, it is automatically enabled/disabled on the Slave list (but on Slave list it is always grayed-out). If the value of Lookahead on Master and Slave list is different and this option is enabled, the Lookahead value is automatically copied from the Master list to the Slave list. Lookahead in events only This feature regards only the value of Lookahead in events (specified both in the Config Tool and Air Client), but not duration-based Lookahead Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 21

22 Example Air Client v12 Example Config Tool ADC List Redundancy Control Client Configuration Requirements List Options Configuration 1. From the Config Tool select a server and then from the menu select File>List Configurations. 2. From the list Assignments screen select a Transmission List (PlayList) in the Lists pane. 3. Right-click on the entry and then from the pop-up menu select Properties Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 22

23 Configuration Requirements 4. Select the List Redundancy tab. This tab contains general configuration options for Transmission Lists. Some options are commonly used and enabled by default. Configure the following options to enable list linking as required: Enable Auto Resync Function: Enable/Disable Auto Resync. Checked: (Recommended) Enable auto re-sync function of List Redundancy. Unchecked: Disable auto re-sync function of List Redundancy. About the current Re-Sync mechanism of List Redundancy: Users should send Mirror and Sync command manually from LRCC to start the Sync. When the Master List receives both the Mirror and Sync commands, the Auto Re-Sync mechanism is turned on, and users can disable Auto Re-Sync by sending one of the commands of Disable LR, Stop Sync, or Stop Mirror. The Master List and Slave List exchanges the current playing event and frame every second. If the Events are different or the frames from two lists differ more than 3 frames, out of sync is considered to have happened once. If out of sync happens continuously, i.e. more than 20 times, the Auto Re-Sync function is triggered. The auto re-sync function makes it possible to synchronize with all short events. When the Master List receives a Sync in 10 seconds command from LRCC, it calculates the current event s duration. If it is shorter than 10 seconds, it adds the next events duration, until there is enough time to put an AO flag (Automatic Ontime) to an event in the Slave List. If for any reason, the Sync operation fails, the Auto Re-Sync is triggered. So users only need to send the first Sync command from LRCC. The Auto Re-Sync mechanism will handle the rest until successfully Synchronized. Enable Auto Swap Function: Enable/Disable Auto Swap. Checked: Enable Auto Swap Function. Unchecked: (Recommended) Disable Auto Swap Function. If the master list is stopped and the slave list is still running, the Auto swap function automatically swaps the role of the master list with the slave list. NOTE: Currently, the Auto Swap Function cannot operate swap, so even if the master and slave list swap roles, the output stream will be still from the former master list s device Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 23

24 Configuration Requirements Enable Sync on Next Event During Upcounting: Check to permit the system to partially synchronize lists on the current upcounting event. Usually, to sync on the next event, an AO must be put on the next event in both Master and Slave lists. But for an upcounting event, the start time of next event is unknown, so an AO cannot be put on the next event. This means we can never sync on an event next to an AO event. Partially synchronizing on the event overcomes this problem (i.e. On the current upcounting event, when operator skips to next event, both Master and Slave list roll together and keep synchronized on the next event. Enable Copy Lookahead Value from Master List to Slave: When using List Redundancy, enabling this option makes the Lookahead on the SLAVE list follow the value of the lookahead that is set on the MASTER list. Check to enable this feature and copy the Lookahead Value from the Master List to the Slave List. The value of this option is saved in INI-file. Uncheck (Default) to disable this feature. Note: To reduce the chance of errors, this option can only be enabled/disabled on a Master list. This option is grayed out on a Slave list. This option only works if option "Enable Copy Lookahead Value from Master List to Slave" is enabled, a pair of lists (channel) is created in LRCC and their behavior is specified (Master/Slave). If the value of Lookahead is changed on the Master list, it is automatically copied to the Slave list. And on a Slave list the Lookahead spin-edit is grayed out. Note: This enhancement involves only the value of Lookahead in events, which can be specified both in the Config Tool and Air Client, but not invoked duration-based Lookahead. Copy Lookahead Enabling Rules: If option "Enable Copy Lookahead Value from Master List to Slave" is enabled/disabled on a Master list, it is automatically enabled/disabled on a Slave list (but on the Slave list it is always grayed-out). If the value of Lookahead on Master and Slave list is different and the user turns on option "Enable Copy Lookahead Value from Master List to Slave", the Lookahead value is automatically copied from the Master to Slave at this moment. Meaning of the diagnostic information items: Redundant Server: The name of the server, which the redundant list of this list is in. Redundant Handle: The server handle and list handle of the redundant list of this list. Redundant Latency: When the master list receives a command, it sends the command to the slave list and executes the command on both sides after this latency time Behavior: Master or Slave or not decided Status: LR link status RAN IP: This is the server s RAN network IP address. RAN Port: This server s RAN IP port RAN Latency: If Master and Slave cannot get connected after this latency (default 20 seconds), they will give up and run separately. Select the List Redundancy tab Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 24

25 Configuration Requirements Mirroring and Synchronization Control List Redundancy includes Mirroring and Synchronization control. Mirroring allows keeping an actual copy of Master list; when event is inserted/deleted/edited in Master list, this change is immediately replicated to Slave. Synchronization is used to keep Slave list at the same playout point as Master list. Usually synchronization is achieved by adding AO event to the Slave list; on-air time of this event corresponds to the on-air time of the appropriate event in Master list. Besides this, the two lists simultaneously perform list control commands, such as Play, Skip, Hold, etc. However, at all other moments, lists play independently, and List Redundancy verifies status of each list and catch a moment, when lists are out of Sync or out of Mirror. Synchronization status is verified according to Master and Slave schedule. Mirroring status is verified according to Master and Slave left events count. About Mirroring and Synchronization loss There are different reasons of Mirror and Sync Loss: video disk failure, short events (RAN SHORT), long events (LONG), etc. List Redundancy behavior in case of Mirror or Sync Loss depends on enabled options and list statuses. If Master and Slave lists are playing, but their schedule is different, LR detects Sync Loss, LRCC shows "Sync OFF". If option "Auto Resync" is enabled, lists try to resync by adding AO event to Slave list. As soon as this AO starts, LRCC shows "Sync ON". If option "Auto Resync" is disabled, lists remain unsynchronized. If Master and Slave lists are playing, but their left events count is different, LR detects Mirr and Sync Loss. If option "Auto Resync" is enabled, Slave list is immediately re-mirrored. LRCC shows "Mirr ON", "Sync OFF". Then LR adds AO event to Slave list. As soon as this AO starts, LRCC shows "Sync ON". If option "Auto Resync" is disabled, lists remain unmirrored and unsynchronized. LRCC shows "Mirr OFF", "Sync OFF". If Master list is playing and Slave list stops (disk failure), LR detects Mirr Loss and Sync Loss. If option "Auto Resync" is enabled, Slave list is immediately re-mirrored. LRCC shows "Mirr ON", "Sync OFF". Then LR adds AO event to Slave list. As soon as this AO starts, LRCC shows "Sync ON". If option "Auto Resync" is disabled, lists remain unmirrored and unsynchronized. LRCC shows "Mirr OFF", "Sync OFF". If Slave list is playing and Master list stops (disk failure), LR detects Mirr Loss and Sync Loss. If option "Auto Swap" is enabled, Slave list becomes new Master. Further behavior is similar to item Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 25

26 Configuration Requirements If option "Auto Swap" is disabled, Mirroring and Synchronization is stopped Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 26

27 Installing the List Redundancy Control Client Installing the List Redundancy Control Client Introduction The List Redundancy Control Client application uses an Air Client 32 bit connection, and Netbeui protocol to connect to the Device Server(s). Note: For information on configuring automation Client Computers for ODBC connectivity to SQL Server 2012, see ADC_SQL_Server_2012_Installation_Guide. For information on system networking, see ADC_Networking_Best_Practices. Installation of the LRCC Application A List Redundancy Control Client station must be pre-configured similarly to an Air Client station, especially network settings (protocols, lana numbers). A network drive must be configured to provide access to the Administration file (ADCOPTS.INI) that the List Redundancy Control Client uses. Similar to an Air Client application. List Redundancy Control Client File Location The LRCC.exe file is installed in a directory (i.e. C:\LRCC\) with NBIOS32.dll, APILIB32.dll and Tally.dll. NBIOS32.dll and APILIB32.dll allow the List Redundancy Control Client connection to the Device Server(s) through Netbeui protocol. The version must be the same as used of the Device Server(s). These are not provided with the LRCC.exe executable file. Tally.dll (for Tally signal reception and management) is provided with the LRCC.exe executable file Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 27

28 Installing the List Redundancy Control Client Create a shortcut to LRCC.exe The Configuration Manager Tool is used to configure the device drivers for devices controlled by a specific Device Server. 1. Use standard Microsoft procedures to create a shortcut to LRCC.exe on the desktop. 2. Edit the properties, and add [LRCC connection name] in the Target field. 3. LRCC connection name: Connection name to Device Server(s) for the LRCC application. This must be unique in the system. Note: The Device Server(s) to which the LRCC must connect are defined through the LRCC configuration menus (not in the shortcut properties). 4. Click on this shortcut icon to launch the LRCC. The LRCC uses a 32 bits Air Client login type, so this connection must be available in the ADC build(s). Only one instance of LRCC application can run on a given station. An Error Message is generated if a second instance is launched Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 28

29 Installing the List Redundancy Control Client Installation of the Sealevel 8011 GPI board (for Tally) in LRCC station To support ADC tally functions the GPI Card installed in the Air Client (our standard Device Server GPI card = SeaLevel 8011 card) requires installation of the SeaLevel drivers: al-interface.html ( al-interface.html) Note: SeaLevel is a 3rd party company that produces our GPI/RS422 cards. The LRCC application can use one or several PCI GPI boards (Sealevel 8011 with 8 inputs), installed in the station to retrieve the Tally information of the Lists. If the LRCC has to consider Tally signal(s) then the PCI GPI board must be installed in a PCI slot of the station, and its drivers for Windows must be installed. This GPI board is the same model used in the Device Server, and the same breakout panel can be used. If not a specific wiring must be done to receive the Tally signals on the GPI inputs. GPI Wiring Schematic 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 29

30 List Redundancy Control Client Application List Redundancy Control Client Application About the Application The List Redundancy Control Client (LRCC) application uses the automation API to connect to ADC List Redundancy modules. The LRCC configures and the controls the List Redundancy (LR) channels defined for it. The LRCC application runs on a dedicated station. Note: It is strongly recommended to install the LRCC application on a unique station (not on an Air Client station). If LRCC is installed and running on an Air Client station there may be some problems with the as run logs generation by the Air Client. ADC Client applications running on the same station cause problems with as run logs: The last client application started would not receive as run logs notifications. Running an Air Client and an LRCC on the same station may cause the Air Client to not generate the as run logs if the LRCC was already running. See ER#2979. Several LRCC can connect to the same Device Server, if the corresponding number of Air Client 32 bit connections is allowed. One LRCC can connect to several Device Servers. For one (or several) transmission channel(s), LRCC provides the following information: The Master and Slave lists statuses related to List Redundancy: Master Slave Mirrored Synchronized Communication dynamic statuses between applications: List Redundancy modules of the Device Servers Redundancy Control Client All the aspects of a List Redundancy Control application are configurable. For one (or several) transmission channel(s), the operator has manual control of the List Redundancy mechanism using specific buttons or functions: Disable List Redundancy (mirroring and synchronization disabled) 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 30

31 List Redundancy Control Client Application Define which list is Master Enable mirroring Enable synchronization Resynchronize Slave List without incidence on the playing event Resynchronize on next event Resynchronize Slave List in segmented mode on the playing event as soon as possible About assuming direct control of a slave list To assume direct control of the slave list, List Redundancy must be stopped from mirroring. To do this first requires mirroring operations be correctly initialized. When done the Disable List Redundancy button will become active allowing mirroring operations to be halted. Not following the correct steps to initialize mirroring operations will result in a situation where the slave list cannot be controlled manually. As an example, here are the steps for enabling and disabling List Redundancy: 1. In LRCC configure Device Servers and LR channel 2. Thread and play TransmissionListA (Master) 3. In LRCC click on arrow button 4. Start Mirroring and Start Synchronization 5. Disable List Redundancy using "Disable List Redundancy" button Start / Stop the application Use the following procedure to start/stop the application. To Start the LRCC application 1. Click on the LRCC shortcut icon location on the desktop to launch the LRCC. The LRCC uses a 32 bits Air Client login type, so this connection must be available in the ADC build(s). Only one instance of LRCC application can run on a given station. An Error Message is generated if a second instance is launched. To Stop the LRCC application 1. From the Operation menu select Exit 2. A Confirm exit dialog is displayed that allows the user to exit the application, after confirmation. Click OK to exit Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 31

32 List Redundancy Control Client Application Troubleshooting a Restart after a Device Server Crash Should the MAIN Device Server crash and LRCC fails to work after a restart, use the following workarounds to address this issue. Check that the RedundantHandle is set correcty in the INI files for the MAIN & BACKUP Device Server. For example, the MAIN DSs List 1 would have RedundantHandle , in the INI file, where 2000 is the handle of the BACKUP DS in the List Redundancy pair & 1 is the list number. Use "tcpview.exe" to disconnect any multiple LR connections between Device Servers, so that only one remains in "Netstat -an" and only 1 RAN icon is shown in the Device Server s "View Connections" window. Administration This section outlines typical administration procedures. To Log In 1. Start the LRCC application. The Login windows appears: 2. Enter a valid User Name. 3. Enter a valid User Password. 4. Select OK. The LRCC is started with the corresponding rights for that user. NOTE: User Name and User Password are case sensitive, and must be contiguous characters with no spaces. If an incorrect User Name or corresponding User Password is entered, then the following error message is displayed: The login window re-appears with the previously entered values. 5. Additional options are: Cancel closes the LRCC Console. Logout is grayed on first login, after the application is launched Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 32

33 List Redundancy Control Client Application User Account Types Three types of users can access the LRCC: 1. Admin. Operation and configuration rights, with a specific password set in the Properties / Set Admin password function and saved encrypted in LRCC.ini file. The encryption algorithm used is the same as the Air Client configuration file (aclnt32.ini). This Admin User Name gives full rights on the LRCC Console (operation and configuration). 2. Default. This user name receives no rights on the LRCC console, except for display functions and Login or Exit. The password is not taken into account for this user. All the menu functions are grayed, except: View menu (Expand All, Reduce All)? menu (LRCC Help, About) Operation menu (Change User, Exit). All the buttons are grayed, except the Expand/Reduce buttons of the different LR channels in the main console. This user name is also accessible with Logout button of Login function accessed through Operation / Change User function. The Logout button is grayed on the first login after the application is launched. 3. User Name. Individual user, by name, defined through the Automation AdminTool. The LRCC will check if the User Name and Password entered are defined in the ADCOPTS.INI file. Passwords are encrypted in the ADCOPTS.INI file. The user will gain operation right on the LRCC, with access to the following functions: All the buttons of the main console Device Servers function of the Properties menu and in the corresponding ADC Connections window, Connect /Disconnect buttons. All other functions are grayed. LRCC Title Bar: After login, the user account/name is displayed in the title bar of the LRCC Console Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 33

34 List Redundancy Control Client Application Change User function When previously logged in, the Operation / Change User function will open the Change User window. This screen is similar to Login, but with the Logout button active. Selecting Cancel will return the user to the LRCC Console with the previous login, and corresponding rights Selecting Logout will login the user as Default The LRCC Console is active in display only. LR Control Denied message is displayed in the main console. The only active function is the Change User function of the Operation menu. A user or admin may log in. The Exit application, and button in Title bar, remain active when logged in as Default, or after a Logout. Entering a valid user name and corresponding user password, and selecting OK will return to the LRCC Console with the new login, and corresponding rights. Until logged in as Admin or user name, the functions and buttons of LRCC Console are inactive, but the display in the console displays status updates Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 34

35 Configuring the LRCC and LR Channels Configuring the LRCC and LR Channels Properties Menu Use the Properties menu to configure the LRCC. The Properties menu contains the following functions : Device Servers configuration Tallies configuration LR Channels configuration Environment configuration Admin password When logged in as Admin all the functions of the Configuration menu are active. When logged in as any other user only the Device Servers function is active. Device Servers Configuration The Device Servers connected to the LRCC use the Properties / Device Servers Configuration function. The ADC connections configuration window will open. The Device Servers Configuration window does the following: Configures the name of the Device Servers to which the LRCC can connect to automatically or manually Configures the order in which the Device Servers are automatically connected When the application is launched, the automatic connection to the Device Servers is performed in the order of the list, from top to bottom. Manually connects or disconnect the LRCC to or from one of the configured Device Servers Configures each Device Server to the redundant list, number and name 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 35

36 Configuring the LRCC and LR Channels Device Servers Configuration Screen Servers" column: Lists the configured Device Servers names. Connection column: Gives the connection status between the current LRCC and these Device Servers. Possible values: Connected Disconnected Connecting Mode column: A pull down menu: Manual Automatic Listed Device Servers automatically connect to the LRCC upon application launch, or will try to reconnect after a disconnection. Device Server Configuration Update When the connection mode to a given Device Server is changed, the following message is displayed. Select OK. The new setting is saved immediately in the LRCC.ini file, but it is only activated when the LRCC is restarted. There is no time-out for a manual or automatic configured connection. The application stays in connecting status and tries constantly to reconnect to the configured Device Server. The automatic connection to the Device Server(s) must not degrade the performances of the application. Connect button 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 36

37 Configuring the LRCC and LR Channels Allows for a manual connection between the LRCC and a Device Server listed in the table. Disconnect button Allows for a manual connection between the LRCC and a Device Server listed in the table. LR Channel Disconnect Confirmation If the Device Server selected is used in an LR Channel the following confirmation window appears: Device Servers Configuration Window Controls Edit button: After selecting a configured Device Server in the table, this will open the Device Server Properties window to edit the index and name (or mnemonic) of its Redundant List. Add button: Opens a blank Device Server Properties window to add a new Device Server to the table, and the index and name (or mnemonic) of its Redundant List. Remove button: Allows removing the selected Device Sever from the table. If a List of the Device Server selected is used in a configured LR Channel, or if the LRCC is connected to that Device Server, the Remove button is grayed. Up & Down buttons: Allows setting this order by positioning the Device Server names in the table. OK button: Closes the window and saves the configuration, connection mode, and position of the configured Device Servers in the window, and in the LRCC.ini file Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 37

38 Configuring the LRCC and LR Channels Up, Down, Connect and Disconnect functions act as the corresponding buttons on the selected Device Server. Diagnostic Function Access The Diagnostic function can be accessed by right-selecting a Device Server entry, and then selecting Diagnostic from the pull-down menu. The MAIN Diagnostic screen opens, showing all the Lists of the selected Device Server. Lists that are associated with LR channels, show the Redundant List displayed in the Redundant list column. Device Server name : List number This information is generated by the Device Server configuration, reflecting parameters of the LISTCONF.INI file, and not the LRCC configuration: RedundantHandle=2 1 RANLatency= Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 38

39 Configuring the LRCC and LR Channels The Remove LR Configuration Function Right-selecting a List entry with a Redundant List, displays the Remove LR Configuration function. This function clears the relative parameters in the LISTCONF.INI Device Server configuration file. It is used for restarting an LR channel configuration. NOTE: This must be used only if there are incompatible LR configurations in Device Servers, and the LRCC cannot apply the required change. Device Server Properties Screen This Device Server Properties screen is accessible from the Add or Edit buttons of the Device Servers Configuration screen. It is used to define a new Device Server in the table, and the index and name (or mnemonic) of its Redundant List. ADC Name field: When the window has been opened with the Edit button of the parent window 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 39

40 Configuring the LRCC and LR Channels The ADC Name field is not editable if the Device Server is used in a configured LR Channel, or if it is connected to the LRCC. When the window has been opened with the Add button of the parent window. The ADC Name field is editable. The Device Server for which the new Redundant List is going to be configured, is entered here. Enter a Device Server name. The OK button is grayed until this is done. Selecting the Add button opens a blank List Properties screen The List Properties screen creates the name of a new Redundant List for the Device Server, which is then usable in an LR Channel. The Index pull-down list is of the Device Servers, by list number, which are not already configured in the Redundant Lists table. Enter a List name The OK button is grayed until this is done. The Cancel button remains active. Editing a Device Server Entry To edit a Device Server entry, in the Device Server Properties screen do the following: Select the List for the Device Server to be edited and select the Edit button. The List Properties screen for the selected List will open Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 40

41 Configuring the LRCC and LR Channels The List Properties screen allows changing the name of the selected Redundant List for a Device Server. If the List has been erased it is required to enter a new List name: The OK button is grayed until this is done. The Cancel button remains active. If the List to edit is used in an active LR Channel, managed by the LRCC, it is possible to edit the Alias Name. The change will be active after OK. The Remove button removes the selected List from the Redundant Lists table for the given Device Server. If the List to be removed is used in an active LR Channel managed by the LRCC, the Remove button is grayed. The OK button saves the configuration as defined in the window of the LRCC.ini file. The Cancel button exits the window without saving the changes. Tallies Configuration The List Redundancy Control application can retrieve Tally information through a GPI board for the LR Channels that it manages. On the Tally Configuration Screen Name column: Gives the Mnemonic name configured for the given Tally GPI board / Input columns: Displays the GPI board and input used to receive this Tally signal. Status column: Shows which value is currently applied to the corresponding Tally signal (depending on the On Air value parameter). The Edit or Add buttons opens the Tally Properties screen, to configuring a new or existing Tally Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 41

42 Configuring the LRCC and LR Channels Tally Properties On the Tally Properties Screen Name field: Sets the name of the configured Tally. It is required to enter a Tally name. The OK button is grayed until this is done. The Cancel button remains active. GPI Board / Input pull-down fields: Set the GPI board & Input values associated with the configured Tally. The GPI Board pull-down lists the number of GPI boards installed on the station (detected by the Sealevel driver). GPI Board values: None, 1 to 4. GPI Input values: None, 1 to 8. The None value (displayed blank), is a configuration for no GPI board and input present. This none value is pre-selected when a new Tally is added to the configuration. The GPI Input pull-down lists the available inputs, not already configured for a Tally, of the selected GPI Board. The None value (displayed blank), is a configuration for no input board present. On Air value radio buttons: For the given GPI input, this parameter sets the value (0 or 1) corresponding to the On Air status of the Tally OK closes the configuration screen and saves the configuration as defined in the window of the LRCC.ini file. Cancel exits the screen without saving the changes. Remove removes a configured Tally. It is not possible to edit or remove a Tally which is configured to an LR Channel. The Edit and Remove buttons are grayed in these cases. The changes made to an LR configuration with the Tallies Configuration screen are immediately active and saved in LRCC.ini file. LR Channels Configuration The function Properties / LR Channels configuration defines the LR Channels managed by the LRCC Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 42

43 Configuring the LRCC and LR Channels An LR channel is an association of two redundant lists: List n of Device Server X is redundant with List m of Device Server Y. Once an LR Channel is configured, the relative information is saved in the ListConf.ini file of the Device Servers. LR Configuration Screen The following configuration screen views or sets the LR channels, which are managed by the current LRCC, and how they appear in the main console. This configuration is saved in the LRCC.ini file when OK is pressed. LR Configuration Table Columns LR Channel: Displays the name of the configured LR Channels. Up to 16 LR Channels are configurable in the console. LR / CTRL Status: Displays the List Redundancy and Control status of the configured LR Channels. The normal sequence is: Connecting, Connected, Mirror, Mirror & Sync. Problematic display: Disconnected, Invalid,??? in List A or List B field. No Control if no connection with a Device Server List A: List of the LR Channel configured to be displayed on the left of the main console. List B: List of the LR Channel configured to be displayed on the right of the main console. Tally: Tally connected to the LR Channel. Tally Status: Current status (On Air / On Line) of the corresponding Tally. LR Channels Configuration Screen Buttons Add / Edit Opens an LR Channel Properties configuration screen. This defines a new LR Channel by associating two Lists of two Device Servers (or of the same one), editing an existing inactive LR channel, and checking or changing the parameters. It is possible to edit an LR Channel only when it is inactive (Mirroring OFF). The Edit button is grayed for an active LR Channel (with Mirroring ON) Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 43

44 Configuring the LRCC and LR Channels Remove Removes an LR Channel from the configuration, and disconnects the two Lists. The Remove button is grayed for an active LR Channel (with Mirroring ON). Up / Down Configure the vertical position of the LR Channels in the table, and in the main console. The changes to the LR configuration made in the LR Channels Configuration screen are immediately active, and saved in the LRCC.ini file and Listconf.ini file of the connected Device Server(s). OK Closes the configuration screen. Defining the Redundant Lists of a Channel The LR Channel Properties Screen displays parameters configured for the LR channel. On the LR Channel Properties Screen the parameters configured for the LR channel are active only when OK is pressed. Commands are sent to the relevant Device Servers at that time. Name: Mnemonic name of the LR Channel as displayed in the console Confirm Actions: If enabled, any action on the main console buttons will have to be confirmed for this LR channel. Redundant Lists Server A / Server B: These pull-down lists select a Device Server set in the Properties / Device Server configuration screen. A None value exists which will disable an LR channel. Pre-selected values for Servers/Lists when starting a new configuration: None Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 44

45 Configuring the LRCC and LR Channels List A / List B: These pull-down lists select a Redundant List for the configured Device Server. Only the lists not already used in another LR Channel are displayed in the pull-down lists, if the LRCC is connected to the relevant Device Server(s). If not, the List configured in the Device Server Properties screen are displayed in the pull-down list. It is recommended that a connection from the LRCC to the relevant Device Server(s) is established before starting the LR Channels configuration Error for Duplicate Lists If the same List (of the same Device server) is configured as List A and List B, then the following error message is displayed: Console Error Message for Duplicate List List A is displayed on the left of the parent window, and the LRCC console List B, is on the right. Preferred Control A radio button to set the LRCC / Device Server connection used to control the LR channel when both Device Servers are configured to be connected to the LRCC. The purpose of this feature is to avoid useless network loading. The LRCC connects to both Device Servers but uses one connection only to control the LR Channel. If this connection is lost, the LRCC will try automatically to use the other one, depending on the network architecture. If one connection only is possible, then it will be used independently of this parameter. List Control Actions Latency Sets the latency for application of manual commands. The value configured applies to both lists. Unit Frames Range or possible values: From 1 to 255. Default value: 1. Default Segmented Re-Synchronization Delay Sets the default value in the Start Synchronization or Re-synchronize confirmation window, if Sync. Mode In [xxx] seconds is selected Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 45

46 Configuring the LRCC and LR Channels This default value determines the delay when the Slave will be re-synchronized in segmented mode. It can be manually changed in the Re-synchronize screen. Re-sync. on Next Event is selected by default when this screen is opened. Unit: Seconds. Range or possible values: From 5 to 255. Default value: 5. LR Channel Properties Screen: Define the Tally The Tally information can be used to: Determine which List of an LR channel is On air. Normally it is the MASTER List. Automatically disable the List Redundancy mechanism if the SLAVE List is manually switched on air by a change over, or a matrix. It can also happen that the SLAVE List becomes the MASTER for an LR Channel, either manually or through the change over Tally. When the normal situation is restored, and the operator does not want to disable the LR, it will require the re-mirror & re-synchronizing of the Slave List. LR Channel Properties Screen Defining the Tally The LRCC uses one or several PCI GPI boards (Sealevel 8011 with 8 inputs) installed in the station for retrieving the Tally information of the Lists. This GPI Board can be used at the same time by other applications (i.e.: Air Client). The maximum number of GPI boards depends on the number of PCI slots available in the station. Use Tally Information 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 46

47 Configuring the LRCC and LR Channels If this parameter is enabled then all the following parameters are active. If disabled, all the following parameters are not configurable (grayed). Tally: Choose which Tally is used for the LR Channel. This Tally is one of the two Lists for the LR channel. Associated with List A / List B: Radio button to select which List the selected Tally is associated with. Disable LR on Tally Change: When enabled any change in the Tally value will disable the Mirroring and Synchronization for the LR channel. If this parameter is disabled, the Keep LR on next Tally change check box is not displayed in the main console for the corresponding LR channel. Master follows "On Air": When enabled, the Master List always corresponds to the On Air List. If Master follows Tally is enabled, the Master / Slave status of the two lists depends on the Tally configuration and statuses are automatically set. The buttons -> and <- are grayed. If Master follows Tally is disabled, the Master / Slave status of the two lists is manually set and/or confirmed through the main console when the mirroring is activated. The buttons -> and <- are active. Colors: The Color Selector configuration screen sets the Foreground and Background colors for On Air / On Line indicators in the main console. Environment Configuration The Properties / Environment Configuration sets the path of the ADCOPTS.INI file used for login using the following Environment Options configuration window: 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 47

48 Configuring the LRCC and LR Channels Selecting the " " button opens the Administration Database Directory configuration screen that selects the path to find the ADCOPTS.INI file for the rights administration on the current LRCC application. Only the path has to be configured (no selection of the ADCOPTS.INI file is required). The visualization field checks that there is the ADCOPTS.INI file in the selected path. The changes to the Environment configuration are immediately saved in LRCC.ini file, but the LRCC must be restarted. The following Change Information message is displayed when exiting the Environment configuration window: Admin Password The Properties / Admin Password function opens the Set Admin Password screen to configure the password for the Admin user name : This password is encrypted in the LRCC.ini file, the same encryption as the Air Client application. At the initial launching of LRCC there is no password for the Admin user name Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 48

49 Configuring the LRCC and LR Channels Log setup Not implemented in Phase Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 49

50 Reduced View Expanded View ADC List Redundancy Control Client List Redundancy Control Client Console List Redundancy Control Client Console Introduction The different List Redundancy channels managed on a List Redundancy Control Client are displayed in the main console after login. The console is the user interface to configure and manage the List redundancy channels with access to the different menus. The console cannot be minimized or maximized. The console will adapt the vertical size, depending on the number of LR channels managed in the LRCC, but the vertical size will never be more than the vertical size of the desktop. A vertical and horizontal scroll bar will appear if required. If an error occurs on one or several of the managed LR channels (error status active) and it is in the background, then a button in the Windows Task Bar will blink. For a given LR channel it is possible to select a "Reduced" view, or an "Expanded" view Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 50

51 Expanded View of the Console ADC List Redundancy Control Client List Redundancy Control Client Console These two different views can be toggled for each LR channel with the Expand / Reduce button, or globally (for all the LR channels configured in the console) with the Expand all / Reduce all functions of the View menu. Below is an example of an LRCC console, combining an expanded view for the first LR Channel, and a reduced view for the second one. Main Console Menus The following menus are available for the main console. Operation Menu Operation Change User Exit Configurations Menu Configurations ADC configuration Tallies configuration LR Channels configuration 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 51

52 List Redundancy Control Client Console Environment configuration Admin password View Menu View Expand all Reduce all Help Menu? LRCC Help About Main Console Buttons for a Given LR Channel and Related Confirmation Windows If the Confirm actions parameter of a LR Channel is enabled in Properties / LR Channel, each operator action for this LR channel in the main console will have to be confirmed before being executed. The confirmation window for re-synchronize is displayed even if Confirm actions is disabled. The confirmation messages for manual actions appears only on the LRCC from where the action is done. If another LRCC is monitoring the same LR Channel, it will not display the corresponding message. The buttons in the main console behave as for the LR Channel. Reduce / Expand buttons: Displays Reduce when corresponding LR channel display is expanded, Expand when LR channel display is reduced. No confirmation window for this button. Diagnose button: Provides List Redundancy logging to allow determination of List Redundancy faults. Confirmation window for this button Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 52

53 List Redundancy Control Client Console Disable List Redundancy button: Disables Redundancy by disabling Mirroring. Synchronization is automatically disabled when Mirroring is disabled. This button is active when Mirroring is ON, it is grayed when Mirroring is OFF. Confirmation Window LR Channel : LR Channel name Disable LR? OK or Cancel Re-Synchronize button: This button is active when Synchronization is ON, it is grayed when Synchronization is OFF. The use of this buttons acts as a "macro": Stop synchronization and then Start synchronization. The confirmation window for Re-synchronize is displayed even if Confirm actions is disabled, as a choice has to be considered. Confirmation Window: Sync. Mode On Next event is selected by default when the Start Synchronization screen is opened. If OK, the SLAVE List is re-synchronized with the MASTER List, at the next (primary) event. If Sync. Mode In [xxx] seconds is selected, and OK is selected, the SLAVE List is re-synchronized in segmented mode (usable mainly with class 3 videodisks), with the MASTER List on current event in the delay selected. This delay can be manually changed. By default, when the confirmation screen is opened, the value configured for Default segmented re-synchronization delay of the relative channel is set. -> and <- (Set Master) : The two buttons are inactive (grayed) if the parameter Master follows Tally is ON for the LR Channel. The two buttons are active after the connection of the two Lists of the LR Channel, if Masterfollows Tally is disabled. (LR status: ) The Master/Slave status of the two Lists can be inconsistent. Only the button changing the current direction is active in normal operation. The other button is grayed. Confirmation Window LR Channel : LR Channel name Set List name as Master? OK or Cancel 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 53

54 List Redundancy Control Client Console Start / Stop Mirroring This button is always active (never grayed). The text in the button is contextual (Start if Mirroring is OFF, Stop if Mirroring is ON). Confirmation Window LR Channel : LR Channel name Start / Stop (contextual) Mirroring? OK or Cancel Start / Stop Synchronization This button is active when the Mirroring is ON (otherwise it is grayed). The text in the button is contextual (Start if Synchronization is OFF, Stop if Synchronization is ON). Confirmation window for "Start Synchronization": Same as for "Re-Synchronize. Confirmation window for Stop Synchronization LR Channel : LR Channel name Stop Synchronization? OK or Cancel NOTE: If the parameter Master follows On Air and Confirm actions is disabled, there is a Confirmation if Start Mirroring or Re-synchronize is asked for by the On Air List (according to Tally). Keep List Redundancy on Next Tally Change This check box is active for the LR Channel if the parameter Disable LR on Tally Change is active (otherwise it is grayed). When the box is checked, the next Tally change will NOT disable the Mirroring on the LR Channel. The next Tally change causes the check box to be automatically unchecked (remains active). When the box is unchecked the next Tally change will disable the Mirroring on the LR Channel. Confirmation Window LR Channel : LR Channel name Keep / Disable (contextual) LR on next tally change? OK or Cancel 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 54

55 List Redundancy Control Client Console Main Console Status and Information Each LR Channel, from Left to Right : A green led, blinking each second, indicates good communication between the LRCC and the Device Server(s) connected to the LR Channel. Otherwise a red (not blinking) led is displayed:. LR Channel Name: As configured (i.e. : BLANC TX). The Status of the LR Channel CTRL : Connected / Disconnected. Indicates the connection status between the LRCC and at least one of the two Device Servers connected to the LR Channel. This information is the same as /. LR : Disconnected / Connecting / Connected. Indicates the connection between the two Lists connected to the LR Channel Mirroring : ON / OFF. Indicates if Mirroring is active on the LR Channel. Synchronization : ON / OFF. Indicates if Synchronization is active on the LR Channel. List A statuses LR List name configured to be displayed on the left side of the console (List A), with color corresponding to Tally (if Use Tally information is enabled), and in bold if the Master. [Device Server name]: [List name] Master / Slave status List status : Unthread, Thread, Playing Tally status Graphic status for MASTER/SLAVE list, Mirroring ON/OFF, Synchronization ON/OFF : Master (on left side) with mirroring and synchronization OFF (LR stopped). : Master (on left side) with mirroring ON and synchronization OFF,. : Master (on left side) with mirroring and synchronization ON The clock blinks if synchronization was asked for but not yet implemented in the Slave list Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 55

56 List Redundancy Control Client Console : After the configuration of an LR Channel or the starting of the connected Device Servers, and before the activation of Mirroring, the MASTER/SLAVE status of the two Lists can be uncertain. The two lists can have the same status. If Master follows Tally is not set, before activating the mirroring on an LR Channel, the LR status is indicated by the picot, and the Start Mirroring button is grayed. The right direction must be set before starting to Mirror. The Operator must select a button -> or <- to define which List must be the MASTER before activating the Mirroring. Disable List Redundancy : Indicates an Invalid status (LR configuration is not correct). : If the MASTER List is on the right side of the console (List B). List B status LR List name configured to be displayed on the right side of the console (List A), with color corresponding to Tally (if Use Tally information is enabled), and in bold if the Master. [Device Server name]: [List name] Master / Slave status List status : Unthread, Thread, Playing Tally status : On Air / On Line if a Tally is configured for the LR Channel (if not on status) Error ( ) / No Error ( ) graphic status This status displays "Errors" in cases of disconnection between connected LR modules, or between LRCC and Device Servers (depending on the configuration). The red Error Icon is displayed if the LR Channel becomes disconnected. The green No Error icon is displayed as soon as the LR Channel becomes connected again. The user is able to see all error messages in the status bar if necessary. Error Messages in LR Channel Status Bar Before acknowledgement: Connection Lost Unknown Status 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 56

57 List Redundancy Control Client Console List A and B status: Only the status that can be read through the LRCC to Device Server connection or LR Channel List to List connections are displayed. In case of disconnection the unknown statuses are blanked. Example : LR disconnection Only the List and Tally status of the List of the Device Server used to control the LR channel can be retrieved. : Green led: The LRCC to Device Server connection is OK. : Error because the LR connection is lost Error Messages in Console Status Bar For each LR Channel managed and monitored on the LRCC, a Status Line is visible in the Expanded mode. If an error occurs on a given LR Channel (Disconnection from Device Server(s), LR Disconnection): The No Error ( ) graphic status is replaced by the Error ( ) graphic status Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 57

58 List Redundancy Control Client Console The error message is displayed and the icon appears in the status bar of the LR Channel. A click on icon erases the current message from the status bar, and allows the next message (if any) to be displayed. When all the messages have been cleared the icon disappears. The Error ( ) graphic status remains until the error condition (Disconnection from Device Server(s), LR Disconnection) is fixed. When the error condition (Disconnection from Device Server(s), LR Disconnection) is fixed the No Error ( ) graphic status appears. Error Messages for LR Channel Connection / Comms / Config Invalid configuration request : This error message is displayed when a invalid configuration is requested for an LR channel. If no RAN.ini file is found in the C:\ drive of the Device Server connected to the LR Channel. Control connection lost with [Device Server name] : This error message is displayed in case of a disconnection between the LRCC and the Device Server(s) used to control the LR Channel, and if the non preferred control connection is not available (resulting in a lost of control on the connected LR Channel). LR communication disturbed on [LR Channel name] : This error message is displayed in case of a short disconnection between the two Lists of an LR Channel. LR connection lost on [LR Channel name] : This error message is displayed in case of long (more than a few seconds disconnection between the two Lists of an LR Channel. Channel Disconnected Error MAIN 24/04/ :17:51 : Control Connection lost with MAIN French regional settings, Device Server disconnected. Channel Disconnected Error Channel 1 4/24/2003 3:32:33 PM : LR connection lost on Channel Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 58

59 List Redundancy Control Client Console US regional settings. Channel Disturbed Error 4/24/2003 3:32:24 PM : LR communication disturbed on Channel 1 US regional settings. Invalid Configuration Request 28/04/ :36:17: Invalid Configuration Request French regional settings Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 59

60 List Redundancy Control Client Console Control Connection Lost This error occurs when LRCC client loses connection with one of the two Device Servers, involved into LR Channel. LRCC client displays an appropriate error message with the name of the Device Server (e.g. Turkina). This error can appear if there are any network problems which cause connection lost with Device Server or if the user manually disconnects this Device Server from LRCC ("Configuration" "Device Servers" button "Disconnect"). If LRCC loses connection with one Device Server involved in a redundant pair, it still receives statuses from the other Device Server. This means that LRCC is still able to show correct information about the LR Channel even if it is communicating only with one Device Server. However, (as shown in the following graphic) if LRCC loses connection with both servers, it can t display the real status of LR Channel. LR Connection Lost LR Connection Lost error appears if the communication between two lists in LR Channel is broken. This can happen because of any network problems or because one DS was turned off. Note: Even if the connection between two lists is lost the lists continue trying ro reconnect and as soon as all problems are eliminated the LR Channel becomes connected again Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 60

61 List Redundancy Control Client Console LR Communication restored This message is shown after the connection between two lists is restored (see 2. LR Connection Lost). This message indicates that the lists are successfully connected again. Invalid configuration request This error can appear if there are any problems in configuration. For example, value of Server Handle for Device Server1 in RAN.ini file differs from actual handle of Device Server1. When this error occurs it is necessary to verify all configuration, eliminate errors and try to connect LR Channel again. In the example with incorrect DS handle it is necessary to correct the server s handle and to restart the server. Scenario: An attempt to configure a list which is currently involved in other redundant pair. Suppose that list1 on DS1 is currently connected with list1 on DS2. Attempting to connect list1 on DS1 with list2 on DS2 (for example) fails because list1 is actually included in another redundant pair. Currently these notifications are shown in LRCC: For example, the following image shows that Turkina List1 is currently configured with PROKHOROV List1 and can t be connected with any other list (here was an attempt to connect it with PROKHOROV List3) Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 61

62 List Redundancy Control Client Console Status in LR Channel Console The following statuses are displayed in the LR Channel Console. Channel Console Status: LR Channel configured, but Lists not specified. Lists Pending: Connection pending. Local Configuration: LR not configured (with Diagnostic function), so LR is not configured at DS level, and configured at LRCC level. Incompatible Configuration: Configuration of an LR Channel for the LRCC (MAIN : List01 BACKUP: List02) incompatible with the configuration in the connected Device Servers (MAIN : List01 BACKUP: List01) Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 62

63 List Redundancy Control Client Console Example: List Configuration Error. In the following example, MAIN : List01 is configured to be redundant with BACKUP : List01, but BACKUP : List01 is already configured to be redundant with MAIN : List03, so the message "Configured with MAIN : List03" is displayed in the console of the LR Channel Operation Menus The folllowing operation menu options are available: Change User: See section Change User function (on page 34). The configuration is not saved, but the different configuration windows are closed after OK prompt. Exit: Displays the Confirm exit dialog, allows the user to exit the application, after confirmation. Properties menu: See section: Properties menu (on page 35). View menu: Expand All : Puts all the LR Channels displayed in the main GUI in expanded mode. Reduce All : Puts all the LR Channels displayed in the main GUI in reduced mode. About menu The About dialog: Displays the About window of the application (date format depending on Regional settings) Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 63

64 Diagnostic Logging Diagnostic Logging About LR Logging List Redundancy logging allows for determination of List Redundancy faults. Information logged includes: Logging of the date, time and list number of the Master & Slave lists of all events that are mirrored from the Master to the Slave list. Logging of the date, time and list number of the Master & Slave lists, when a Slave list is re-synced to the Master. If an event is moved, deleted or copied on the Master list, then log (date, time & list numbers) the update to the Slave list. See also Mirroring and Synchronization Control (on page 25). To use Logging 1. A Diagnose Button is available on the List Redundancy Channel Panel: 2. When the operator selects the Diagnose button, a pop up window of Log Levels Choice is displayed: 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 64

65 Diagnostic Logging 3. Specify the Log Levels. The operator may choose the Log Levels to only log the information necessary for their operations and to reduce the traffic between LRCC and the Servers. Each check-box with log level name is accompanied by hint describing its purpose. Keep left mouse button over the check-box to see the hint. Available Log Levels are: Event Control: log commands to handle mirroring (insert/edit/delete events) LR Control: log control commands from LRCC to servers (Master/Slave behavior, start Mirroring, start Sync) System: log the most important statuses of Master and Slave lists Error: log connection errors Warning: log connection warnings Status: log packages exchanged between redundant lists to monitor status of LR connection LRCC: log packages exchanged between servers and LRCC to monitor connection, behavior, mirroring and sync statuses. ACK: log ACK replies to redundancy commands Event xchange: log current event and list state packages exchanged between redundant lists. This log contains the most detailed information about state of each list. LRCC config: log LRCC configuration commands sent from LRCC to servers LRCC control: log LRCC control commands sent from LRCC to servers Hints on using Logging Parameters: Use the log function wisely and safely. Because log information is transferred from servers to LRCC, the more detail it logs, the more network bandwidth it occupies. The following 3 items are sufficient to provide the most important information about lists statuses and behavior: "Event Control", "LR Control" and "System". These logs are not large and detailed, so they can be kept working all the time. Status, LRCC, ACK, Event xchange, LRCC config and LRCC control messages are written frequently and contain a lot of information. Do Not Keep Them Enabled for an extended period of time, because they occupy too much network bandwidth, and the log items usually accumulate on the server side and take a long time to reach LRCC. To diagnose an LR Mirroring and Synchronization problem, enable "Event xchange" log. This log provides the most detailed information. 4. Managing log files: In the bottom part of the Log Levels window, there are two text boxes for log files management: Keep Log History: This is used to set how many days the operator wants the log files saved in LRCC hard disk. Log File Size: This is used to set how big a log file can become. If a log file exceeds this size, it is split it to two or more files. About Log File Management: All log levels except for LRCC config and LRCC control are prepared on Device Server side. Then they are transferred over network to LRCC application and written to text file with the name like "DBG LRCC.exe _001-ServerName-ListNumber.log". LRCC creates two files for one LR Channel, one file for each list in channel. LRCC config and LRCC control messages are prepared and written on LRCC application side. They are included into standard LRCC debug file named like "DBG LRCC.exe _001.log" 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 65

66 Diagnostic Logging The log function is LR Channel based, so the operator can turn on a specific LR list pair s log. The log file for specific days is saved in the./log sub folder of the LRCC running folder. The log file is list based with each list in each server having a dedicated log file. For each new day, the log file will change to a new name. If the log file reaches the specified size, a new file is generated. A typical log file name looks like this: DBG LRLOG _003-M log. Where, "DBG LRLOG" is the leading word of LR log files is the date (YYYY-MM-DD) "003" indicates this is the 3rd file of this day because the first two files already exceed the size limitation. "M1330" is the server name. "02" is the 2nd list in this server. If they are still required, copy off the out of date files. In each new day, the log system checks all the files in the /log folder and deletes files older than the specified number of day s files. (See keep Log History) 5. When finished Click OK to save the settings and exit. Other action options are: The "Clear All" button resets all the log choices and exit to main window. The "Cancel" button cancels the setting and exit to main window. About Device Server Debug Logging Switch The ADC Device Server has an opportunity to store List Redundancy log information to its own debug log (its name is similar to: DBG A log). This option can be enabled/disabled by buttons combination shift+ctrl+alt+f5. If this log is enabled the Device Server looks like this (letter R appears): If this option is enabled, the debug log will contain all LR information (about statuses, errors, warnings, events, etc.), because server LR log is independent from Log Level settings in LRCC client. Server and LRCC logs can be enabled simultaneously and LR information will be stored both in LR log (according to chosen log levels) and in Device Server debug log (all information). Server log file grows quickly, so use server LR logging only for diagnostic purposes. In ADC Device Server v11 this log is turned on even if the log in LRCC is turned on (at least one log level was checked) and no matter whether combination shift+ctrl+alt+f5 is used. So if LRCC log is enabled, all information is also stored to Device Server debug log. In ADC Device Server v12. if log in LRCC is enabled, the information is stored only to LRCC logs, which are in subdirectory "\log" of LRCC run directory. And if LR log is enabled in the Device Server (by shift+ctrl+alt+f5) the information is stored to the Device Server debug log. The two logs can be 2015 Imagine Communications Corp. Proprietary and Confidential. 8-June-2015 Page 66