GRASS VALLEY K2 BASECAMP EXPRESS, Instruction Manual

Page: 281 / 394

July 3, 2007 K2 Storage System Instruction Manual 281
Using FTP for file transfer
Using FTP for file transfer
Since the Nearline system has no media database, procedures that apply to “online”
K2 storage systems (Levels 2, 3, and 4) do not globally apply to the Nearline storage
system. This includes procedures for streaming, import, export, and FTP.
The rules for transferring to/from a K2 Nearline storage system are as follows:
• Transfer files only. Streaming media, as in AppCenter’s
Import/Send to | Stream
feature, is not supported.
• K2 media must be transferred to/from the Nearline system as a GXF or MXF file.
• Passive FTP mode is supported. You must use this mode for FTP transfers.
• For the list of FTP commands supported, refer to “FTP commands supported” on
page 318 .
• In addition to FTP transfers, you can also map shared drives and use basic
Windows networking to move files to/from a Nearline storage system.
You should use the dedicated K2 FTP/streaming network. The rules for this network
are summarized as follows:
• The network must be on a separate subnet.
• Dedicated GigE cables must be connected to the FTP GigE port on K2 Media
Servers.
• For network hostname resolution, hostnames mapped to FTP IP addresses must
have a “_he0” suffix appended to the name.
For more information about the FTP/streaming network, refer to “About networks
and FTP” on page 318
Additional information about Nearline FTP is as follows:
• K2 FTP protocol supports clip and bin names in non-English locales (international
languages) using UTF-8 character encoding. Refer to specifications for
internationalization in the K2 Media Client System Guide.
• The Nearline FTP interface does not have GXF and MXF folders to support
format-specific functionality, as does the K2 FTP interface for “online” K2
systems. This means the Nearline FTP interface treats all files, including GXF and
MXF, as generic files with no particular consideration for any file format.