Grass Valley K2 Dyno PA Configuration Manual v.2.0 - Manual (Page 11)

About the FsNameServers file in a K2 Summit standalone system on page 11
Ordering the network adapters for K2 Dyno PA on page 13
Creating a unique file system name and storage disk labels
Configuring the DLC server on a K2 Summit standalone on page 13
Enabling SNFS for the iSCSI client on the K2 Dyno PA in a K2 SAN system on page 30
About using Browse with a K2 Summit standalone
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. This requires modifying the FsNameServers file on each
machine.
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 in the K2 Dyno PA Release Notes. For
information on configuring the K2 Summit software, consult the K2 Summit Production Client
documentation.
• If upgrading from a version earlier than K2 7.2x software, the K2 Summit system needs a unique
file system name and storage disk labels, as described in About unique file systems and K2 Dyno
PA. File system names are case sensitive.
• The FsNameServers file on all the standalone K2 Summit Production Clients must contains the
IP address of the Control ports of the name servers. There can be a maximum of three name
servers. For more information, see About the FsNameServers file in a K2 Summit standalone.
• Network adapters configured for the Dyno PA Browse feature. 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 in the K2 Dyno PA Release Notes.
• 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 add
the SNFS-configured K2 Summit Production Client that will be used with that Dyno PA.
Related Links
About K2 Summit standalone system and K2 Dyno PA DLC configuration on page 10
About the FsNameServers file in a K2 Summit standalone system
To use the Browse feature of K2 Dyno PA, the FsNameServers file needs to be configured on each
K2 Summit standalone and Dyno PA machine 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:
22 June 2011 K2 Dyno Production Assistant Configuration Manual version 2.0 11
Configuring the standalone K2 Summit system and K2 Dyno PA