User manual GRASS VALLEY K2 DYNO PA CONFIGURATION MANUAL V1.5

[. . . ] K2 Dyno PA LIVE PRODUCTION CONTENT MANAGEMENT SYSTEM Configuration Manual Software Version 1. 5 071-8763-01 October 2010 Affiliate with the N. V. KEMA in The Netherlands CERTIFICATE Certificate Number: 510040. 001 The Quality System of: it's wordwide Thomson Inc, and its wor dwide Grass Valley division affiliates DBA GRASS VALLEY Headquarters 400 Providence Mine Rd Nevada City, CA 95959 United States 15655 SW Greystone Ct. Beaverton, OR 97006 United States 10 Presidential Way Suite 300 Woburn, MA 01801 United States 2300 So. Salt Lake City, UT 84119 United States Technopole Brest-Iroise Site de la Pointe du Diable CS 73808 29238 Brest Cedex 3 France Brunnenweg 9 D-64331 Weiterstadt Germany Kapittelweg 10 4827 HG Breda The Nederlands Rue du Clos Courtel CS 31719 35517 Cesson-Sevigné Cedex France 40 Rue de Bray 2 Rue des Landelles 35510 Cesson Sevigné France Carl-Benz-Strasse 6-8 67105 Schifferstadt Germany 7140 Baymeadows Way Ste 101 Jacksonville, FL 32256 United States 1 rue de l'Hautil Z. I. [. . . ] If using a standalone K2 system, the file system name must be unique to this K2 Summit system, for example gvfs_summit1. NOTE: The file system name can be found in the Windows Explorer tree view, next to the V: drive. If using a standalone K2 system, specify the maximum number of clients. This is the number of Dyno PA clients that can access assets on a K2 Summit system at the same time. Depending on your workflow, proceed to Adding a bin or Adding a repository. Related Links Configuring the K2 Summit SAN and K2 Dyno PA on page 21 Configuring the standalone K2 Summit system and K2 Dyno PA on page 33 About standalone K2 Summit system and K2 Dyno PA DLC configuration on page 34 32 K2 Dyno Production Assistant Configuration Manual version 1. 5 15October 2010 Chapter 4 This section contains the following topics: · · · · · · · About standalone K2 Summit system and K2 Dyno PA DLC configuration Ordering the network adapters for K2 Dyno PA Configuring the DLC server About the K2 Dyno PA application and the Grass Valley platform service Starting the K2 Dyno PA application Adding a server Configuring SNFS for the DLC or iSCSI client on the K2 Dyno PA Configuring the standalone K2 Summit system and K2 Dyno PA 15October 2010 K2 Dyno Production Assistant Configuration Manual version 1. 5 33 Configuring the standalone K2 Summit system and K2 Dyno PA About standalone K2 Summit system and K2 Dyno PA DLC configuration To use the Browse feature in a system with a standalone K2 Summit Production Client, the Quantum StorNext Distributed LAN Client (DLC) on the K2 Summit (the DLC server) and K2 Dyno PA (the DLC client) systems must be configured. On a standalone K2 Summit Production Client, run the DLC Configuration tool to add, edit, or remove the IP addresses from the FsNameServers file. To set up DLC on the K2 Summit and Dyno PA systems, you need: On the standalone K2 Summit system: · The requirements described in K2 Dyno PA Prerequisites. For information on configuring the K2 7. 2. x software, consult the K2 Summit Production Client documentation. · If upgrading to K2 7. 2x software from an earlier version, the K2 Summit system needs a unique file system name and storage disk labels, as described in Creating a unique file system name and storage disk labels. This tool ensures that the FsNameServers file on all the standalone K2 Summit Production Clients contains the IP address of the Control ports of the name servers. For more information, see Ordering the Network Adapters for K2 Dyno PA. On the K2 Dyno PA machine: · The requirements described in K2 Dyno PA Prerequisites. · The identical FsNameServers file that was required for the K2 Summit system must also be located in the C:\SNFS\Config folder of every Dyno PA machine that is sharing the platform service. · In the Dyno PA application, the administrator must use the SNFS configuration button to map drives for each SNFS-configured K2 Summit system that will be used with that Dyno PA. Related Links Configuring the standalone K2 Summit system and K2 Dyno PA on page 33 About the FsNameServers file on page 35 Ordering the network adapters for K2 Dyno PA on page 36 Creating a unique file system name and storage disk labels Configuring the DLC server manually on page 40 Configuring SNFS for the DLC or iSCSI client on the K2 Dyno PA on page 47 34 K2 Dyno Production Assistant Configuration Manual version 1. 5 15October 2010 Configuring the standalone K2 Summit system and K2 Dyno PA About the FsNameServers file To use the Browse feature of K2 Dyno PA, the FsNameServers file needs to be configured on each K2 Summit and Dyno PA machines in the system. The FsNameServers file contains the Control network port IP addresses for each host name server in the system (up to a total of three host name servers). For example, if you have the following: Machine K2 Summit SAN #1 (Host name server) K2 Summit SAN #2 (Host name server) K2 Summit SAN #3 K2 Summit Standalone K2 Summit Standalone K2 Dyno PA #1 K2 Dyno PA #2 IP address for the Control network port on the machine 10. 0. 0. 1 10. 0. 0. 2 10. 0. 0. 3 10. 0. 0. 4 10. 0. 0. 5 10. 0. 0. 101 10. 0. 0. 102 In this example, the FsNameServers file would look like this: The FsNameServers file must be located in the C:\SNFS\Config directory in each K2 Summit and Dyno PA machines in the system. 15October 2010 K2 Dyno Production Assistant Configuration Manual version 1. 5 35 Configuring the standalone K2 Summit system and K2 Dyno PA Related Links About configuring K2 Summit SAN systems on page 22 About standalone K2 Summit system and K2 Dyno PA DLC configuration on page 34 Ordering the network adapters for K2 Dyno PA Prerequisites: · The K2 7. 2. x software must be installed and configured as specified in the K2 Summit documentation. · The file system name and storage disk labels on the K2 Summit system need to be unique. If the system has been upgraded to 7. 2. x from an earlier version, the file system must be re-created with the Storage Utility tool, as specified in the K2 System Guide. To enable the Browse feature on K2 Dyno PA, SNFS requires that the first network adapter on the K2 Summit system must be the Control connection; the loopback adapter cannot be the first network adapter. If you are going to use the DLC Tool to configure the FsNameServers file, skip to step 5. Otherwise, navigate to c:\snfs\config. 36 K2 Dyno Production Assistant Configuration Manual version 1. 5 15October 2010 Configuring the standalone K2 Summit system and K2 Dyno PA 4. Edit the FsNameServers file to add a line containing the IP address of the Control network for each host name server. [. . . ] From the Server drop-down list, select the K2 system that has the channel you want to manage. From the Channel drop-down list, select the channel that you wish to manage and click OK A managed channel appears in the Managed Channels pane. Related Links Managing K2 Dyno PA on page 49 15October 2010 K2 Dyno Production Assistant Configuration Manual version 1. 5 55 Managing K2 Dyno PA Adding or replacing a K2 Summit system in an existing K2 Dyno PA system If using the Browse feature in Dyno PA, and a K2 Summit system needs to be added or replaced, follow these steps. When adding a new or replacing an existing K2 Summit system in a K2 Dyno PA system, the FsNameServers file in the C:\SNFS\Config folder must be identical to the other FsNameServers files in the system. This file contains the IP addresses of the Control network ports on up to three name servers. [. . . ]