Streaming video between K2 systems

It is required that FTP/streaming traffic be on a separate subnet from control traffic. To reserve bandwidth and keep FTP/streaming traffic routed to dedicated ports, IP addresses for FTP/streaming ports must have double name resolution such that hostnames are appended with the “_he0” suffix. You can use host tables or another mechanism, such as DNS, to provide the name resolution. This directs the streaming traffic to the correct port.

In most K2 systems, network name resolution is provided by host tables, which are found in hosts files. The following procedure describes how to set up hosts tables to provide name resolution for both the control network and the FTP/streaming network. If you are using other mechanisms for name resolution, use the host table examples here to guide you.

Setting up the K2 system for FTP/streaming transfer has the following network requirements:

• For stand-alone internal storage K2 systems, the K2 machine is the source/destination for FTP/streaming transfers. FTP/streaming traffic uses the FTP GigE port (Media Connection #1) on the K2 client.
• Some kind of name resolution process must be followed. You have the following options:
  • Set up hosts files located on each networked device so that you reference host names through the hosts files.
  • Edit the DNS entries. See your network administrator.
• The host name of all peer K2 systems and Profile XP systems must be added to a Remote host registry using the K2 AppCenter Configuration Manager.
• To import to or export from a K2 system, both the source and destination must be in the same domain.