Grass Valley K2 Storage System Instruction Manual v.3.2 Sep.24 2007 - Manual (Page 514)

514 K2 Storage System Instruction Manual September 7, 2007
Chapter 11 Installing the Level 30 Storage System
Networking for Level 30
Use the topics in this section to configure the Gigabit Ethernet (GigE) network for the
Level 30 storage system.
• “Networking requirements” on page 514
• “Networking tips” on page 515
• “Setting up host tables” on page 516
• “Testing the control network” on page 517
Networking requirements
Required networking strategies for a Level 30 K2 Storage System (a non-redundant
K2 Storage System) are as follows:
• Three networks:
• Media network — Exclusively for iSCSI traffic.
• 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 Media (iSCSI) network traffic is kept separate from any other traffic. 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. 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 network 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 516 ) or another mechanism to provide the name
resolution. This directs the streaming traffic to the correct port. Refer to the K2
Media Client System Guide for a complete explanation.
• K2 Media Servers (including optional NH servers) must be on the streaming
network, as they provide the FTP interface for shared storage streaming traffic.
Shared storage K2 Media Clients do not need to be on the streaming network
because they do not send or receive streaming traffic.