Table of Contents
Advertisement
Chapter 11 FTP on the K2 Storage System
FTP commands supported
For a list of the FTP commands supported by the K2 FTP interface refer to the K2
Media Client System Guide.
About networks and FTP
The requirements for FTP/streaming transfers in and out of online K2 systems are as
follows:
• The FTP/streaming traffic must be on a separate subnet. Do not put control and
• Dedicated GigE connections must be made to the dedicated FTP GigE port on
• For some system client, non-K2 devices, it is permissible to use one NIC with two
• For network hostname resolution, hostnames mapped to FTP IP addresses must
• On optional step is to provide "error correction" aliasing for external storage
Also refer to the networking sections in the installation chapters earlier in this manual
for network information specific to each K2 Storage System level.
Sample network configuration and hosts file
The following diagram illustrates one possible configuration setup, with both the
control network and the FTP/Streaming network shown. The media (iSCSI) network
is not shown. This diagram includes a K2 Media Client with internal storage, a K2
Media Client with external storage (as on a K2 Storage System), a K2 Media Server
(as an FTP server on K2 Storage System), as well as other Grass Valley systems.
330
K2 Storage System Instruction Manual
FTP traffic on the same subnet. FTP traffic can potentially consume so much
bandwidth that it interferes with control traffic, which can cause errors in real-time
record/play operations.
internal storage (stand-alone) K2 Media Clients and on K2 Media Servers that take
the role of FTP server.
IP addresses. One address is on the control subnet and one is on the FTP subnet.
An example of such a client is the Aurora Edit.
have a "_he0" suffix appended to the name.
(SAN) K2 Media Clients as well. For each external storage K2 Media Client, add
the "_he0" extension to the hostname but then associate that hostname with the K2
Media Server's FTP/streaming network IP address, not the K2 Media Client's IP
address. Aliasing K2 Media Client hostnames in this way would not be required if
the transfer source/destination was always correctly specified as the K2 Media
Server. However, a common mistake is to attempt a transfer in which the source/
destination is incorrectly specified as the K2 Media Client. This "error correction"
host file aliasing redirects to the K2 Media Server, which is the correct transfer
source/destination. Use this technique with caution, as it can mask transfer
problems and hamper your ability to troubleshoot and find the root cause.
September 6, 2006
Advertisement
Table of Contents
