GRASS VALLEY K2 SAN, Installation And Service Manual

Page: 63 / 346

Setting up the K2 SAN infrastructure
Setting up the Ethernet switch
Consult with Grass Valley and use the following topics to determine the network and switch
configuration required for your site.
K2 SAN Ethernet switch requirements
K2 SAN Ethernet switch requirements are as follows:
• Redundancy — A redundant K2 SAN must have an “A” media network and a “B” media network
and requires at least two switches, so that the A network and the B network never share the same
switch. Media traffic does not cross between an “A” switch and a “B” switch.
• Separation of iSCSI traffic — Media (iSCSI) traffic must be kept separate from control traffic,
FTP/streaming traffic, and any other type of traffic. This separation may be provided by VLANs
or by using separate switches/fabrics.
• Inter Switch Links — Only control traffic and FTP traffic use ISLs. Media (iSCSI) traffic does
not use ISLs.
• VLAN — When building VLANs on connected switches, common VLANs must have the same
VLAN number. Never use VLAN 1 for anything other than the native VLAN.
• Trunks — Trunks must use LACP and must be tagged.
• Protocols — When integrating multiple switches, the spanning tree protocol must be MSTP. The
routing protocol must be RIP.
• Port security — Do not use port security.
• IGMP — Enable IGMP snooping on the control network and on the corporate LAN, to support
the low-resolution live streaming traffic generated by K2 Summit systems.
Default Ethernet switch design
A K2 SAN system that ships from Grass Valley with self-contained networks is described as follows.
This network and switch configuration meets the K2 SAN Ethernet switch requirements:
• Switches are HP ProCurve.
• A non-redundant K2 SAN has a single switch. Redundant K2 SANs have at least two switches
to support an “A” media network and a “B” media network.
• There are three 1 Gig Inter-Switch Links (ISLs) between redundant switches. This is the default
configuration for all K2 SANs and provides sufficient bandwidth for most FTP traffic loads.
• The ISLs are configured as a trunk using LACP. Trunk ports are labeled Trk1.
• Each switch has two VLANs, with half the switch’s ports on each VLAN. The media (iSCSI)
traffic uses one VLAN and all other traffic uses the other VLAN. This “other” traffic can include
both FTP and control traffic, as it is allowed that they be on the same VLAN.
• The control/FTP VLAN ID is 10. The media VLAN IS is 60.
• IGMP Snooping is enabled on the control/FTP VLAN, to support low-resolution live streaming.
• Even numbered ports are control/FTP VLAN. Odd numbered ports are media VLAN.
2014 01 27 K2 SAN Installation and Service Manual 63