Transfers with k2 systems – Grass Valley UIM v.2.1.1 User Manual
Page 19

February 5, 2008
UIM Instruction Manual
19
Transfers with K2 systems
Refer to the following examples of host file entries:
#Open SAN entries
192.168.100.151
SAN1_XP1
192.168.100.152
SAN1_XP2
192.168.100.153
SAN1_XP3
192.168.100.154
SAN1_XP4
192.168.100.155
SAN1_FSM1
192.168.100.156
SAN1_FSM2
192.168.100.157
SAN1_UIM1 SAN1_XP1_UIM SAN1_XP2_UIM
192.168.100.158
SAN1_UIM2 SAN1_XP3_UIM SAN1_XP4_UIM
192.168.200.157
SAN1_UIM1_he0 SAN1_XP1_he0 SAN1_XP2_he0
192.168.200.158
SAN1_UIM2_he0 SAN1_XP3_he0 SAN1_XP4_he0
#Stand-alone Profile XP entries
192.168.100.105
XP5
192.168.205.105
XP5_fc0
192.168.100.115
XP5_UIM
192.168.205.115
XP5_UIM_fc0
192.168.200.115
XP5_he0 XP5_UIM_he0 #Streaming NIC of XP5_UIM
#Control connection for Stand-alone K2 Media Client
192.168.100.211
K2StandAlone1
#FTP connection for Stand-alone K2 Media Client
192.168.200.211
K2StandAlone1_he0
#Control connections for SAN K2 Media Clients
192.168.100.111
K2client1
192.168.100.121
K2client2
192.168.100.131
K2client3
192.168.100.141
K2client4
#FTP connection for K2 Media Server (with K2 Media Client aliasing)
192.168.200.11
K2Server1_he0 K2client1_he0 K2client2_he0 K2client3_he0 K2client4_he0
In addition, on both stand-alone and SAN K2 Media Clients, you must open
Configuration Manager and add Profile XPs as Remote Hosts. Enter the Profile XP
actual hostname, without any added suffixes. Also, if you are using remote protocols
to perform transfers, add a unique Controller ID for each Remote Host.
Refer to the K2 Media Client System Guide for complete explanations of FTP/
streaming transfers on K2 systems.