Grass Valley K2 System Guide v.7.2 - Manual (Page 48)

48 K2 System Guide 07 April 2010
Chapter 3 System connections and configuration
Media Connection #1
This is GigE port 2 on the rear panel.
7. If prompted, shutdown and restart Windows.
8. If you are going to FTP/stream video between K2 systems, proceed to “Streaming
video between K2 systems” ; otherwise, the K2 system is ready for standard data
networking tasks.
9. Enable the write filter. Refer to “Enabling the write filter” on page 156 .
Streaming video between K2 systems
It is required that FTP/streaming traffic be on a separate subnet from control traffic
and, in the case of a K2 SAN with shared storage K2 clients, separate from media
(iSCSI) traffic. To reserve bandwidth and keep FTP/streaming traffic routed to
dedicated ports, IP addresses for FTP/streaming ports must have double name
resolution such that hostnames are appended with the “_he0” suffix. You can use host
tables or another mechanism, such as DNS, to provide the name resolution. This
directs the streaming traffic to the correct port.
In most K2 systems, network name resolution is provided by host tables, which are
found in hosts files. The following procedure describes how to set up hosts tables to
provide name resolution for both the control network and the FTP/streaming network.
If you are using other mechanisms for name resolution, use the host table examples
here to guide you. For shared storage K2 clients, also refer to the K2 SAN Installation
and Service Manual for a discussion of host tables.
Setting up the K2 system for FTP/streaming transfer has the following network
requirements:
• For stand-alone internal storage K2 systems, the K2 machine is the source/
destination for FTP/streaming transfers. FTP/streaming traffic uses the FTP GigE
port (Media Connection #1) on the K2 client.
• For K2 Summit Production Clients or K2 Media Clients with shared storage on a
K2 SAN, a K2 Media Server is the source/destination for FTP/streaming transfers.
FTP/streaming traffic uses the FTP GigE port on the K2 Media Server. No transfers
go to/from the shared storage K2 client directly.
• Some kind of name resolution process must be followed. You must either reference
host names through hosts files located on each networked device or edit the DNS
entries. To edit the DNS entries, see your network administrator. To set up host
files, see
“Set up hosts files” on page 48 .
• The host name of all peer K2 systems and Profile XP systems must be added to a
Remote host registry using the K2 AppCenter Configuration Manager.
• To import to or export from a K2 system, both the source and destination must be
in the same domain.
Set up hosts files
Set up a hosts file located in c:\WINDOWS\system32\drivers\etc\hosts on each K2
system. If you include the names and addresses of all the systems on the network, then
you can copy this information to all the machines instead of entering it in the hosts
file on each machine.