Grass Valley K2 Storage System Instruction Manual v.3.2 Aug.01 2007 - Manual (Page 195)

July 3, 2007 K2 Storage System Instruction Manual 195
Networking for Level 3R
Networking for Level 3R
Use the topics in this section to configure the Gigabit Ethernet (GigE) network for the
Level 3R storage system.
• “Networking requirements” on page 195
• “Networking tips” on page 196
• “Setting up host tables” on page 197
• “Testing the control network” on page 199
Networking requirements
Required networking strategies for a Level 3R (a redundant K2 Storage System) are
as follows:
• Four networks:
• Media network A — Exclusively for iSCSI traffic. For failover purposes, this
network restricts traffic between an “A” media port on a K2 Media Client and
the “A” K2 Media Server with the role of media file system/database server.
• Media network B — Exclusively for iSCSI traffic. For failover purposes, this
network restricts traffic between a “B” media port on a K2 Media Client and the
“B” K2 Media Server with the role of media file system/database server.
• Streaming/FTP network — For media transfers and FTP traffic.
• Control network — For all other non-streaming, non-iSCSI traffic.
• Networks must be on separate subnets.
• The real-time iSCSI traffic of the media networks (A and B) is kept separate from
traffic that is not real-time, such as that of the streaming/FTP network and the
control network. This separation is provided by dedicated Gigabit ports, cables,
and by a dedicated VLAN on the HP GigE switch or by separate switches.
• K2 Media Servers have a dedicated FTP port. If the server takes the role of FTP
server, make a dedicated FTP connection to the FTP port.
• While control and FTP traffic is each on its own subnet, it is not required that each
type of traffic has its own VLAN on GigE switches. For example, you make both
FTP and control connections to the “control” ports (DEFAULT_VLAN) on the HP
GigE switch.
• Static IP addresses are required for the media networks on K2 Storage System
iSCSI devices. This includes K2 Media Servers, generic iSCSI clients (such as
Aurora Edits), and K2 Media Clients.
• Machine names (host names) assigned to each K2 device.
• Host tables (hosts files) provide name resolution on each K2 Media Client, iSCSI
client, and K2 Media Server.
• IP addresses for FTP/streaming ports must have name resolution such that
hostnames are appended with the “_he0” suffix. You can use host tables (as in
“Setting up host tables” on page 197 ) or another mechanism to provide the name