FTP on the K2 Storage System
Topics in this chapter include the following:
About networks and FTP
You must have a dedicated network for FTP/streaming transfers in and out of the K2 Storage System. This network is reserved for FTP/streaming traffic 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 that take the role of FTP server.
- Dedicated FTP ports on K2 Media Servers and other devices must have static IP addresses.
- For network hostname resolution, hostnames mapped to the static FTP IP addresses must have a “_he0” suffix appended to the name.
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.
The following example shows the contents of a default Windows hosts file with new lines added that match the IP addresses and host names in the previous sample diagram.All lines beginning with a # are comments and can be ignored or deleted.# Copyright (c) 1993-1995 Microsoft Corp.# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.# This file contains the mappings of IP addresses to host names. Each# entry should be kept on an individual line. The IP address should# be placed in the first column followed by the corresponding host name.# The IP address and the host name should be separated by at least one# space.# Additionally, comments (such as these) may be inserted on individual# lines or following the machine name denoted by a '#' symbol.## For example:# 102.54.94.97 rhino.acme.com # source server# 38.25.63.10 x.acme.com # x client host127.0.0.1 localhost10.16.42.10 K2-MediaClient10.0.0.10 K2-MediaClient_he010.16.42.21 K2-MediaClient-110.16.42.22 K2-MediaServer-110.0.0.22 K2-MediaServer-1_he010.16.42.23 ControlPointPC10.16.42.60 NewsEdit110.0.0.60 NewsEdit1_he010.16.42.31 SAN_XP110.0.0.32 SAN_XP1_he0 SAN_UIM1_he010.16.42.32 SAN_UIM1About the K2 FTP interface
An application writer may choose to initiate media file transfers via FTP. If you do not have a preferred brand of FTP software, you can use Microsoft Internet Explorer. The K2 FTP interface displays with a GXF folder and an MXF folder. Use the appropriate folder, depending on if you are transferring GXF or MXF.
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 internal storage K2 Media Clients (stand-alone), it is important to understand that it does not run on external 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. If you attempt to transfer FTP files to/from one of the K2 Storage System clients, the transfer fails. For information on streaming/transfer procedures in general, see the K2 Media Client User Guide.
NOTE: When using FTP in a shared storage environment, please ensure that all FTP communication takes place on the FTP/Streaming network, and not on the Command/Control network.The following section describes the supported FTP commands.
FTP commands supported
The following table lists the FTP commands that the K2 FTP server supports.
Copyright Grass Valley, Inc. http://www.thomsongrassvalley.com |