Grass Valley K2 Storage System Instruction Manual v.3.2 Nov.18 2008 - Manual (Page 426)

426 K2 Storage System Instruction Manual July 15, 2008
Chapter 12 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.
FTP security
K2 security features that affect the K2 FTP interface are based on the logon user
account for the FTP session. For an explanation of these security features, 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
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.
• Dedicated GigE connections must be made to the dedicated FTP GigE port on
stand-alone storage K2 Media Clients and on K2 Media Servers that take the role
of FTP server.
• For some system client, non-K2 devices, it is permissible to use one NIC with two
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.
• For network hostname resolution, hostnames mapped to FTP IP addresses must
have a “_he0” suffix appended to the name.
• Use the following tip with care. While it can solve a problem, it also introduces a
name resolution “anomaly” that might be confusing if not considered in future
troubleshooting activities.
You can provide “error correction” aliasing for shared storage (SAN) K2 Media
Clients. For each shared 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.
Also refer to the networking sections in the installation chapters elsewhere 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 stand-alone K2 Media Client with its own