Grass Valley K2 System Guide v.7.2 - Manual (Page 44)

44 K2 System Guide 07 April 2010
Chapter 3 System connections and configuration
Making network connections
Connect network ports as appropriate for the K2 Summit Production Client or K2
Solo Media Server storage option, as follows:
On a K2 Solo Media Server, an internal storage K2 Summit Production Client, or a
direct-connect storage K2 Summit Production Client, connect the control network to
port 1, which is the first port of the control team. If you have a FTP/streaming network,
it is connected to port 2. Port 3 is not used. In most cases port 4, which is the second port
of the control team, is not used, although it is available to provide additional redundancy
for the control network connection.
On a non-redundant shared storage (SAN) K2 Summit Production Client, connect the
control network to port 1, which is the first port of the control team. Port 2 must be
connected to the media (iSCSI) network. Port 3 is not used. Port 4, which is the second
port of the control team, is not used except as follows: Port 4 may be used only if you
extend your control network to provide the same redundancy as that of a redundant
K2 SAN.
Refer to the K2 SAN Installation and Service Manual for more information.
C4
!
OK
~AC
100BT/1000BT
GPI
VGA REF. LOOP THROUGH
SDI IN1 SDI OUT1 SDI OUT2 LTC I/O
AES AUDIO RS422
SDI OUT1 SDI OUT2
AES AUDIO RS422
LTC I/O SDI IN2 SDI IN3 SDI IN1 SDI IN2 SDI IN3
Control network Optional connection for
redundant control network
Port
1
Port
2
Port
3
Port
4
FTP/streaming
network
Stand-alone storage K2 Summit/Solo network connections
C4
!
OK
~AC
100BT/1000BT
GPI
VGA REF. LOOP THROUGH
SDI IN1 SDI OUT1 SDI OUT2 LTC I/O
AES AUDIO RS422
SDI OUT1 SDI OUT2
AES AUDIO RS422
LTC I/O SDI IN2 SDI IN3 SDI IN1 SDI IN2 SDI IN3
Control network Optional connection for
redundant control network
Port
1
Port
2
Port
3
Port
4
Media (iSCSI)
network
Basic shared storage (SAN) K2 Summit Production Client network connections