Grass Valley K2 Summit Storage Area Network Installation - Manual (Page 309)

2. If a redundant K2 SAN, 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.
3. On the K2 Media Server with the role of primary media file system/metadata server, save a copy
of the following files to a different location:
D:\snfs\config\default.cfg (on some systems this file is named gvfs_hostname.cfg , where
hostname is the name of the SNFS file system server.)
D:\snfs\config\cvlabels
4. Power down the K2 SAN, including RAID storage devices.
5. Power up the RAID storage devices. Verify that they stabilize in an operational state with no
errors indicated.
6. Power down RAID storage devices.
7. Cable and configure the Expansion Chassis.
8. Power up the RAID storage devices. Verify that they stabilize in an operational state with no
errors indicated.
9. Start up the K2 SAN.
10. Bind the RANKs in the Expansions Chassis using Background Bind.
11. When binding is complete, put the K2 SAN in an offline state as follows:
a) You must access Storage Utility (via the K2Config application login) with permissions
equivalent to K2 administrator or higher.
b) When you access Storage Utility, the K2 SAN must be offline.
c) All iSCSI clients and K2 clients in the K2 SAN must be shut down.
12. Restart all K2 Media Servers. Do not use the standard startup processes here. Just start up the
server(s) and wait until the Windows desktop appears. Especially do not use Server Control
Panel or start Failover Monitor.
13. In Storage Utility, select Tools | Expand File System By Capacity .
The first of a series of informational screens opens.
14. Work through the informational screens to verify information. When the option to retry becomes
available, if the new disks are not labeled correctly, retry to start the process. If you are not sure,
you can retry to be sure. Doing so does not cause problems.
15. A message box reports progress. When a message reports success, the process is complete.
16. Restart the K2 SAN.
17. If a redundant K2 SAN, test failover capabilities.
Expanding the media file system by bandwidth
If you want to retain your media file system and yet expand the bandwidth of your K2 SAN, you
must use the following procedures for dynamic bandwidth expansion. This process allows you to
add RANKs to the stripe group, thereby expanding its width, without reinitializing the file system.
18 November 2010 K2 SAN Installation and Service Manual 309
Administering and maintaining the K2 SAN