About networks, Control network description, Streaming/ftp network description – Grass Valley K2 System Guide v.9.0 User Manual
Page 62: Media (iscsi) network description, Network considerations and constraints, Network connections

About networks
The following section describe networks as they apply to K2 systems. Also refer to the K2 SAN
Installation and Configuration Guide for more detailed information about K2 SAN networking.
Control network description
The control network is for communication between devices and components. It does not have
real-time media traffic or streaming/FTP media traffic. The control network must be on a different
subnet than the streaming/FTP network and the media (iSCSI) network. The control network and
the streaming/FTP network may be on the same VLAN. The control network and the media (iSCSI)
network must not be on the same VLAN. Static IP addresses with name resolution via host files are
recommended for the control network.
Streaming/FTP network description
The streaming/FTP network is for media transfers and FTP traffic. It must be on a different subnet
than the control network and the media (iSCSI) network. The control network and the streaming/FTP
network may be on the same VLAN. The control network and the media (iSCSI) network must not
be on the same VLAN. Static IP addresses with name resolution via host files are recommended for
the streaming/FTP network. Hostnames of network adapters that are dedicated to the streaming/FTP
network must be aliased in the hosts file with the
_he0
suffix. This directs the streaming traffic to
the correct port.
Media (iSCSI) network description
The media network is exclusively for real-time iSCSI traffic on a K2 SAN. It must be on a different
subnet than the control network and the streaming/FTP network. Furthermore, its traffic is kept
physically separate from that of other networks. This separation is provided by dedicated ports,
cables, and by a dedicated VLAN on the Ethernet switch or by separate switches. Static IP addresses
are required for the media network. Name resolution is not necessary, so media network IP addresses
are not required in host files.
Network considerations and constraints
•
Do not use any 10.1.0.n or 10.2.0.n IP addresses. These are used by the K2 RAID maintenance
port and must be reserved for that purpose. If these addresses are otherwise used, maintenance
port communication errors occur.
Network connections
Use the information in this section as appropriate to connect the Gigabit (1GBaseT) Ethernet network
for your application:
62
K2 System Guide
06 November 2012
System connections and configuration