Grass Valley K2 Media Client System Guide v.3.3 - Manual (Page 77)

June 9, 2009 K2 Media Client System Guide 77
Modifying network settings
5. Close the Network Properties window.
The network configuration procedure is complete.
Modifying network settings
Before modifying network settings, consider the following:
• Loopback adapter — When you receive a K2 Media Client from the factory, it has
a loopback adapter installed. The loopback adapter allows the media file system to
continue operating if an Ethernet cable is disconnected. Do not modify the
loopback adapter. If you need to restore the loopback adapter, refer to the K2 Media
Client Service Manual.
The loopback IP address is 192.168.200.200. Keep that IP address reserved on your
network. Don’t assign it to any other device. (If this causes conflicts with your
existing network, consult your Grass Valley representative.)
• Hostname changes — If you change the host name when using a shared storage
system, AppCenter could have difficulty connecting. Grass Valley strongly
recommends that you do not change the host name IP address unless following the
documented K2 System Configuration procedure. For more information, refer to
the K2 Storage System Instruction Manual.
Using FTP for file transfer
An application writer may choose to initiate media file transfers via FTP. The K2 FTP
interface has a GXF folder and an MXF folder. Use the appropriate folder, depending
on if you are transferring GXF or MXF. Refer to
“FTP access by automation” on
page 79 for examples.
If connecting to the FTP server on a K2 system from a third-party Windows PC, make
sure that the PC has TCP Window scaling enabled. (For more information on TCP
Window scaling, see the Microsoft Support Knowledge Base web site.)
The K2 FTP server runs on K2 Media Servers that have the role of FTP server. While
it also runs on stand-alone K2 Media Clients, it is important to understand that it does
not run on shared storage K2 Media Clients. When you FTP files to/from a K2
Storage System, you use the FTP server on the K2 Media Server, not on the K2 Media
Client that accesses the shared storage on the K2 Storage System. For information on
streaming/transfer procedures in general, see the K2 Media Client User Guide.
K2 FTP protocol supports clip and bin names in non-English locales (international
languages) using UTF-8 character encoding. Refer to
“Internationalization” on
page 215 .
If clips are created by record or streaming on a K2 file system such that media files
have holes/gaps, i.e. unallocated disk blocks, in them, then that clip represents a
corrupt movie that needs to be re-acquired. The K2 system handles corrupt movies of
this type on a best-effort basis. There is no guarantee that all available media,
especially media around the edges of the holes/gaps, is streamed.
You can also apply K2 security features to FTP access. Refer to “Configuring K2
security” on page 134 .