Grass Valley K2 Summit Storage Area Network v.7.1 - Manual (Page 344)

26 October 2009 K2 Storage Area Network Installation and Service Manual 344
Determining K2 client bandwidth requirements
Determining K2 client bandwidth requirements
The K2 System Configuration application provides a page in the Configure K2 Client
wizard that calculates the bandwidth requirement for a K2 client. On this page you
enter information regarding the channel count, bit rate, and tracks per channel for your
intended use of the K2 client. The page then calculates the bandwidth requirement and
make it available for load balancing.
Preparing the K2 SAN
The following K2 SAN preparations are required to support K2 clients:
• All K2 Media Servers and/or K2 RAID storage devices must be installed and
cabled.
• The control network must be operational with K2 devices communicating. At the
command prompt, use the ping command to verify.
• For non-redundant K2 SANs, the media network must be operational. You can
check this with the K2 System Configuration application.
• For redundant K2 SANs, media network A and media network B must be
operational. You can check this with the K2 System Configuration application.
• K2 RAID devices must have disks bound and be configured as required for
operation on the K2 SAN.
• K2 Media Servers must be configured such that an operational media file system
is present.
• K2 Ethernet switches must be configured and have V-LANs set up.
• The SAN to which you are adding your K2 clients must be defined with the
appropriate number and type of clients. In other words, in the K2 System
Configuration application tree view you should see the K2 clients you are about to
add represented as unconfigured devices.
NOTE: Do not run Storage Utility on a shared storage K2 client. For shared
storage, run Storage Utility only via the K2 System Configuration application.
Preparing K2 clients
Do the following to each K2 client in preparation for its addition to the K2 SAN:
1. If you have not already done so, rack, cable, and provide power.
2. Power on the K2 client and log on to Windows as Windows administrator, which
is username Administrator and password adminK2 by default. Ignore startup
messages referring to a missing media storage system.
3. Assign a control network IP address and configure other network settings for the
K2 client. Use SiteConfig for this step. The two control ports are teamed, so even
if are making a connection to port 1 only, you must configure network settings for
the Control Team.
4. Optionally, use SiteConfig to configure media (iSCSI) networks at this time. You