Prepare system for bandwidth expansion – Grass Valley K2 Summit Storage Area Network Installation User Manual
Page 310

This keeps the existing media intact. The additional RANKs can be made up of new disks in existing
RAID chassis, disks in new Expansion Chassis, or disks in new primary RAID chassis.
After the file system is expanded, existing media is still striped across the original narrower stripe
group, so it can not take advantage of the increased bandwidth. Also, if there is a significant portion
of the storage pool occupied by this existing media, its presence reduces the extent to which new
media can use the increased bandwidth. For this reason the dynamic bandwidth expansion process
provides the Restripe Utility, which restripes the existing media across the new wider stripe group.
This enables both the existing media and new media to get full benefit of the increased bandwidth.
If the media on your file system has a high turnover rate and you know existing media is to be
deleted soon, you have the option of disabling the Restripe Utility. This saves the system resources
and time required to restripe media.
The expansion chassis that you add to your K2 SAN must have unbound, unlabeled disks. If it
currently has disks bound or labeled, connecting it to your system can cause errors.
Dynamic bandwidth expansion is supported only with K2 system software version 3.2 and higher.
Dynamic bandwidth expansion is supported on systems with one LUN per RANK and on systems
with multiple LUNs per RANK.
NOTE: Adding RAID storage devices changes your system design and must be specified for your
K2 SAN by Grass Valley. Do not attempt to add RAID storage devices without support from Grass
Valley.
Related Links
Procedures for expanding the media file system by bandwidth
on page 310
Expanding bandwidth for Aurora products
on page 313
on page 314
Procedures for expanding the media file system by bandwidth
Grass Valley personnel who have received K2 SAN training can use the following procedures.
Prepare system for bandwidth expansion
1. If a redundant K2 Storage System, do the following:
a) Verify that MPIO is updated to the latest version on all shared storage K2 clients.
b) Put the system into an “original primary” state.
This means that for all redundant devices (switches, servers, RAID controllers, etc.) the current
device acting as primary is the one that was initially configured as primary when the system
was originally installed.
310
K2 SAN Installation and Service Manual
18 November 2010
Administering and maintaining the K2 SAN