K2 10Gv2 Storage Area Network Installation and Service Manual Software Version 9.
K2 10Gv2 Storage Area Network Installation and Service Manual Software Version 9.
Contents Safety Summaries......................................................................................................................................11 Preface.......................................................................................................................................................23 About documentation for previous K2 SANs...........................................................................................23 Product description....................................
Contents K2 RAID basic online/production........................................................................................................53 K2 RAID redundant online/production.................................................................................................53 K2 RAID basic nearline.......................................................................................................................54 K2 RAID redundant nearline...........................................................
Contents Configuring and licensing the K2 SAN.....................................................................................................121 About K2 SAN licensing........................................................................................................................121 About QOS on the K2 SAN...................................................................................................................121 Importing a SiteConfig system description into K2Config..................
Contents Basic K2 SAN power on procedure...................................................................................................239 Redundant K2 SAN power on procedure..........................................................................................240 Nearline K2 SAN power on procedure..............................................................................................242 Powering on K2 G10v2 RAID..................................................................................
Contents Using the Stop button in Server Control Panel..................................................................................280 Placing a K2 Media Server in service ..............................................................................................281 Shutting down or restarting a K2 Media Server................................................................................281 Identifying K2 Media Server software versions..............................................................
Contents System diagrams..................................................................................................................................335 iSCSI extended (redundant FSMs)...................................................................................................336 Fibre Channel connected clients (redundant FSMs).........................................................................337 Explanations and procedures...................................................................
Safety Summaries Safety Summary Read and follow the important safety information below, noting especially those instructions related to risk of fire, electric shock or injury to persons. Additional specific warnings not listed here may be found throughout the manual. WARNING: Any instructions in this manual that require opening the equipment cover or enclosure are for use by qualified service personnel only.
Safety Summaries Identifies a protective grounding terminal which must be connected to earth ground prior to making any other equipment connections. Identifies an external protective grounding terminal which may be connected to earth ground as a supplement to an internal grounding terminal. Indicates that static sensitive components are present which may be damaged by electrostatic discharge. Use anti-static procedures, equipment and surfaces during servicing.
Safety Summaries — If this product lacks auto-ranging power supplies, before applying power ensure that the each power supply is set to match the power source. Use correct voltage setting — To prevent product overheating, provide equipment ventilation in accordance with installation instructions. Provide proper ventilation — Static sensitive components are present which may be damaged by electrostatic discharge. Use anti-static procedures, equipment and surfaces during servicing.
Safety Summaries WARNUNG: Warnungen weisen auf Situationen oder Vorgehensweisen hin, die Verletzungs- oder Lebensgefahr bergen. VORSICHT: Vorsichtshinweise weisen auf Situationen oder Vorgehensweisen hin, die zu Schäden an Ausrüstungskomponenten oder anderen Gegenständen oder zum zeitweisen Ausfall wichtiger Komponenten in der Arbeitsumgebung führen können.
Safety Summaries – Berühren Sie bei eingeschalteter Stromzufuhr keine offen liegenden Leitungen, Komponenten oder Schaltungen. Keine offen liegenden Leiter berühren Richtiges Netzkabel verwenden – Verwenden Sie nur das mitgelieferte Netzkabel oder ein Netzkabel, das den Spezifikationen für dieses Produkt entspricht. Gerät erden – Schließen Sie den Erdleiter des Netzkabels an den Erdungskontakt an. – Schalten Sie dieses Gerät nicht ein, wenn die Abdeckungen oder Gehäuseseiten entfernt wurden.
Safety Summaries – Verlegen Sie Netzkabel und andere Kabel so, dass Sie nicht beschädigt werden. Stützen Sie schwere Kabelbündel ordnungsgemäß ab, damit die Anschlüsse nicht beschädigt werden. Kabel richtig verlegen Richtige Netzkabel verwenden – Wenn Netzkabel mitgeliefert wurden, erfüllen diese alle nationalen elektrischen Normen. Der Betrieb dieses Geräts mit Spannungen über 130 V AC erfordert Netzkabel, die NEMA-Konfigurationen entsprechen.
Safety Summaries AVERTISSEMENT — Risque de danger non imminent pour l’utilisateur. MISE EN GARDE — Risque d’endommagement du produit, des installations ou des autres équipements. Symboles apposés sur le produit Les symboles suivants peut être apposés sur le produit : Signale la présence d’une tension élevée et dangereuse dans le boîtier de l’équipement ; cette tension peut être suffisante pour constituer un risque de décharge électrique.
Safety Summaries Utilisez le bon fusible — Utilisez exclusivement un fusible du type et du calibre spécifiés pour ce produit. Utilisez ce produit exclusivement dans un environnement sec — N’utilisez pas ce produit dans un environnement humide. Utilisez ce produit exclusivement dans un environnement non explosible — N’utilisez pas ce produit dans un environnement dont l’atmosphère est explosible.
Safety Summaries — Ce produit renferme une pile. Pour réduire le risque d’explosion, vérifiez la polarité et ne remplacez la pile que par une pile du même type, recommandée par le fabricant. Mettez les piles usagées au rebut conformément aux instructions du fabricant des piles. Utilisez une pile de remplacement adéquate Cette unité ne contient aucune partie qui peut faire l’objet d’un entretien par l’utilisateur. Si un problème survient, veuillez contacter votre distributeur local.
Safety Summaries Laser compliance Laser safety requirements This product may contain a Class 1 certified laser device. Operating this product outside specifications or altering its original design may result in hazardous radiation exposure, and may be considered an act of modifying or new manufacturing of a laser product under U.S. regulations contained in 21CFR Chapter 1, subchapter J or CENELEC regulations in HD 482 S1.
Safety Summaries Recommended ESD Guidelines Follow these guidelines when handling Grass Valley equipment: • Only trained personnel that are connected to a grounding system should handle ESDS items. • Do not open any protective bag, box, or special shipping packaging until you have been grounded.
Safety Summaries Grounding Requirements for Personnel The information in this section is provided to assist you in selecting a grounding method. This information is taken from ANSI/ESD S20.20-2007 (Revision of ANSI/ESD S20.20-1999). Product Qualification Personnel Grounding Technical Requirement Test Method Required Limits Wrist Strap System* ANSI/ESD S1.1 (Section 5.11) < 3.5 x 107 ohm Flooring / Footwear System – Method 1 ANSI/ESD STM97.1 < 3.
Preface About this document This is a K2™ product manual. It describes the K2 10Gv2 Storage Area Network (SAN) and provides instructions for installing and using the product in a variety of applications. The manual contains information for K2 storage in both basic (non-redundant) and redundant configurations. Refer to the sections that apply your K2 SAN's configuration.
Preface Find this document… In these locations… In these formats: 1 K2 Release Notes Grass Valley Website PDF file 2 Quick Start Guide for the K2 product K2 product shipping box Printed K2 Documentation Set PDF file Grass Valley Website PDF file K2 Documentation Set PDF file Grass Valley Website PDF file 3 K2 System Guide For the installer of a K2 product with direct connect storage If you are installing a standalone K2 system, such as a K2 Summit system, with direct connect external R
Preface Find this document… 4 5 In these locations… K2 SAN Installation and Service Manual K2 Documentation Set K2 System Guide In these formats: PDF file Grass Valley Website PDF file K2 Documentation Set PDF file Grass Valley Website PDF file K2 Release Notes Contains the latest information about the software shipped on your system, including software upgrade instructions, software specifications and requirements, feature changes from the previous releases, and any known problems.
Preface K2 SAN Installation and Service Manual Contains installation, configuration, and maintenance procedures for shared storage options. K2 Storage Cabling Guide The cabling guide provides instructions for K2 Storage Area Network (SAN) cabling and external configuration. The cabling guide provides instructions for each level of K2 SAN and covers both redundant and basic (non-redundant) systems. It also provides instructions for connecting direct-connect external RAID storage to K2 Summit systems.
Preface http://www.grassvalley.com Dell Server Documentation If your system includes a Grass Valley product on a Dell server platform, refer to the applicable Grass Valley product manual for installation and configuration information. However, a full set of Dell server documentation has been provided on the Dell Product Documentation CD-ROM. Refer to the documents on this CD-ROM only as required by procedures in Grass Valley product manual.
Preface 28 K2 Installation and Service Manual 2013 07 20
Product description K2 SAN overview description The K2 Storage Area Network (SAN) is Grass Valley’s shared storage solution that gives multiple clients access to a common pool of media. In the iSCSI SAN, clients access the shared media storage via a Gigabit Ethernet network and a Fibre Channel connection. Data is communicated using the Small Computer System Interface (SCSI) data transfer interface and the Internet SCSI (iSCSI) protocol.
Product description K2 SAN key features The key features of the iSCSI K2 SAN are as follows: • • • • • • • • • • iSCSI storage access protocol Gigabit Ethernet connectivity RAID 5 and RAID 6 storage FTP transfers Enhanced IT networked storage configurations to fit a wide variety of size and performance requirements.
Product description low cost, high capacity drives, such as 7.2K SAS drives. In a typical workflow, production is finished on the production storage and then the content is pushed to an online K2 system for playout. Production storage is configured similar to Online storage, but with the 7.2K SAS RAID devices and drives. Production storage can be iSCSI or Fibre Channel.
Product description Basic K2 SAN description K2 clients Media Control Media Control Media Control FTP/streaming Ethernet Switch Control Con tr FTP ol Media Control FTP Control Control point PC NH Server (optional) K2 Media Server Fibre Channel RAID Primary Chassis RAID Expansion Chassis (optional) The basic (non-redundant) K2 SAN can be an online SAN or a production SAN. The SAN has one Ethernet switch, one K2 Media Server, and one basic K2 RAID chassis.
Product description FTP/streaming traffic accesses the K2 SAN via the FTP GigE port on K2 Media Servers. FTP/streaming traffic does not go to K2 clients.
Product description Servers are connected by a serial cable which supports the heartbeat signal required for automatic system recovery (failover) features. The redundant K2 RAID chassis has redundant RAID controllers to support the Fibre Channel connections from the K2 Media Servers. The redundant K2 RAID chassis is also connected to the GigE control network. It also must be connected to the GigE control network.
Product description The basic Nearline SAN has one Ethernet switch. The SAN also has one 10 Gig NH K2 Media Server. The NH server for a Nearline system has two ports for Fibre Channel connections. NH servers do not have media (iSCSI) ports. A NH server on a Nearline system is configured with roles of FTP server and Media file system server. In the Nearline system no K2 Media Servers take the role of iSCSI bridge or media database server.
Product description This is because the Nearline system has no media database to support “movies” or “clips”, such as there is on an “online” K2 SAN. However, the files on a Nearline system can be readily available to an online K2 system via FTP transfer. The redundant Nearline SAN has two Ethernet switches, connected by Inter-Switch Links (ISLs) to support a redundant Ethernet fabric. The SAN also has two 10 Gig NH K2 Media Servers.
Preparing for installation K2 SAN installation checklists Use the following sequence of checklists to guide the overall task flow of installing and commissioning a K2 SAN. Pre-installation planning checklist Task Instructions Comment Procure existing or create new About developing a system SiteConfig system description description on page 73 You can do this before arriving at the customer site.
Preparing for installation Task Instructions Comment Verify/modify device interfaces Modifying K2 client unassigned (unmanaged) interface on page 82, Modifying K2 Media Server unassigned (unmanaged) interface on page 84 Do not proceed until the system description accurately represents all aspects of the actual system. Refer to SiteConfig Help Topics . Use procedures as appropriate for your site.
Preparing for installation SAN configuration checklist Task Instructions Comment Import SiteConfig system description into K2Config Importing a SiteConfig system — description into K2Config on page 122 Configure SAN in K2Config Configuring and licensing the — K2 SAN Use the appropriate instructions for your K2 SAN. Verify SAN license Verify license on K2 Media Server on page 224 The K2 Media Server with role of file system server must be licensed for your SAN's design and bandwidth requirements.
Preparing for installation • K2 Media Server - Redundant K2 Media Servers with role of media file system/metadata server are balanced between the A and B sides. One server is on the A side and the other server is on the B side. K2 Media Servers with other roles, such as FTP server, are likewise balanced between A and B sides. • K2 RAID - When a K2 RAID device has redundant controllers, controller 0 is on the A side and controller 1 is on the B side.
Preparing for installation Redundant K2 SANs have redundant media networks: an A media network and a B media network. The two networks are on separate subnets and are also physically separated onto the A Ethernet switch and the B Ethernet switch. InterSwitch Links (ISLs) between switches do not carry media (iSCSI) traffic. ISLs provide redundant paths for control network traffic and streaming/FTP network traffic only.
Preparing for installation Here is an example of IP addresses and names associated in a hosts file: 192.168.100.11 192.168.101.11 192.168.100.21 192.168.101.21 192.168.100.31 192.168.101.31 192.168.100.41 192.168.101.41 192.168.100.51 192.168.100.61 root_server_1 root_server_1_he0 root_server_2 root_server_2_he0 root_server_3 root_server_3_he0 root_server_4 root_server_4_he0 root_raid_1 root_gige_1 In this example 192.168.100.xx is the control network and 192.168.101.xx is the streaming/FTP network.
Cabling K2 SAN devices To follow cabling instructions To follow cabling instructions for your K2™ Storage Area Network (SAN), do the following: 1. Find the system cabling diagram that matches your K2 system. 2. Follow the references below the system diagram to locate cabling instructions for the individual devices of your K2 system.
Cabling K2 SAN devices To cable this K2 SAN device… Of this model or platform… Turn to these instructions: NH10GE K2 Media Server (optional) Dell R620 K2-SVR-NH10GE online/production Dell R620 on page 51 K2 RAID K2 RAID K2 RAID basic online/production on page 53 This manual documents the default GigE switch configuration. Other configurations are available, depending on your port count and FTP bandwidth requirements.
Cabling K2 SAN devices This manual documents the default GigE switch configuration. Other configurations are available, depending on your port count and FTP bandwidth requirements.
Cabling K2 SAN devices To cable this K2 SAN device… Of this model or platform… Turn to these instructions: Gigabit Ethernet Switch HP 2910 K2-SWE redundant nearline on page 49 NH10GE K2 Media Server Dell R620 K2-SVR-NH10GE redundant nearline Dell R620 on page 52 K2 RAID K2 RAID K2 RAID redundant nearline on page 55 Cable K2 Summit system As directed by the system diagram for your K2 storage, cable the K2 Summit system using the instructions in this section.
Cabling K2 SAN devices Cable Ethernet switch As directed by the system diagram for your storage system, cable the switch or switches for your system using the instructions in this section. These instructions are for the HP ProCurve switch 2900 and 2910 series. You must use this switch for iSCSI traffic. For control and FTP/streaming traffic, it is allowed to use a different brand of switch, such as a Cisco Catalyst switch, if required by your site.
Cabling K2 SAN devices K2-SWE redundant online/production These cabling instructions apply to the following: • HP 29xx series Gigabit Ethernet switch on a redundant online or production K2 SAN. Front view Rear view If you have other iSCSI clients, such as GV STRATUS high-resolution clients, that have just one iSCSI connection and one control connection, approximately half of the clients should be connected to switch A and half of the clients should be connected to switch B.
Cabling K2 SAN devices K2-SWE basic nearline These cabling instructions apply to the following: • HP 29xx series Gigabit Ethernet switch on a nearline K2 SAN with one NH K2 Media Server. Front view Rear view To server 10 Gig Use SFP+ cable with integrated GBIC K2-SWE redundant nearline These cabling instructions apply to the following: • HP 29xx series Gigabit Ethernet switch on a nearline K2 SAN.
Cabling K2 SAN devices Cable K2 Media Server As directed by the system diagram for your K2 SAN, cable the K2 Media Server or Servers for your K2 SAN using the instructions in this section. K2-SVR basic Dell R620 These cabling instructions apply to the following: • Dell R620 PowerEdge Server on a basic (non-redundant) online or production K2 SAN. K2-SVR redundant Dell R620 These cabling instructions apply to the following: • Dell R620 PowerEdge Server on a redundant online or production K2 SAN.
Cabling K2 SAN devices Redundant server heartbeat serial cable Take care to use the proper serial cable to interconnect redundant K2 Media Servers that take the role of file system/database servers. This cable supports the heartbeat mechanism whereby the servers monitor each other’s health. It is a 9 pin serial cable, but it is not a standard RS-232 null modem cable.
Cabling K2 SAN devices If you have more than one NH1 server, balance servers between controller 0 and controller 1. K2-SVR-NH10GE basic nearline Dell R620 These cabling instructions apply to the following: • Dell R620 PowerEdge Server NH10GE on a basic nearline K2 SAN. K2-SVR-NH10GE redundant nearline Dell R620 These cabling instructions apply to the following: • Dell R620 PowerEdge Server NH10GE on a nearline K2 SAN.
Cabling K2 SAN devices Cable K2 RAID Before cabling, install the K2 RAID chassis in its permanent location. After mounting the chassis in the rack, you must secure brackets to the front rail to support the Grass Valley bezel. Refer to related topics in this document for rack mount instructions. You do not need to manually set a Fibre Channel address ID on controllers or a chassis address on Expansion chassis.
Cabling K2 SAN devices Continue this cable pattern for additional Expansion Chassis. K2 RAID basic nearline These cabling instructions apply to the following: • K2 10Gv2 RAID on a basic nearline K2 SAN.
Cabling K2 SAN devices Continue this cable pattern for additional Expansion Chassis. K2 RAID redundant nearline These cabling instructions apply to the following: • K2 10Gv2 RAID on a Nearline K2 SAN. Continue this cable pattern for additional Expansion Chassis.
Cabling K2 SAN devices 56 K2 Installation and Service Manual 2013 07 20
Setting up the K2 SAN infrastructure Setting up the Ethernet switch These procedures are for the HP ProCurve switch 2900 and 2910 series. You must use this switch for iSCSI traffic. For control and FTP/streaming traffic, it is allowed to use a different brand of switch, such as a Cisco Catalyst switch, if required by your site. If you are using a non-HP switch, apply the information in the following procedures accordingly. Refer to the documentation you received with the switch as necessary.
Setting up the K2 SAN infrastructure 8. Select IP Configuration, then press Enter. 9. Press the right-arrow key to choose Edit, then press Enter. Tab to fields and enter information as follows: a) Change Gateway to be the default router. b) Tab to the IP Config (DHCP/Bootp) field and use the Space bar to select the Manual option. c) Tab to the IP Address field and enter the switch’s control network IP address. d) Tab to the Subnet Mask field and enter the subnet mask used for your network. 10.
Setting up the K2 SAN infrastructure 22. Decide your SNMP community name as explained in the following options, then proceed with the next step: • If you decide to use a unique SNMP community name (not “public”), add the community and set its RW permissions.
Setting up the K2 SAN infrastructure 29. Check the version of firmware on the switch. To do this, type the following, then press Enter: show flash Information is displayed similar to the following example: HP_iSCSI_switch1# show flash Image Size(Bytes) Date -------------- -------Primary Image : 6737518 07/25/08 Secondary Image : 5886358 10/26/06 Boot Rom Version: K.12.12 Current Boot : Primary Version ------T.13.23 T.11.12 30.
Setting up the K2 SAN infrastructure 4. In the switch’s configuration application, choose Configuration, then Device Features. 5. Set Spanning Tree to On and click Apply Changes. If prompted, log in with the switch’s administrator username and password. 6. Click Port Configuration. 7. Scroll to the bottom of the list and verify that the SFP+ port is port A1. Re-cable if necessary to correct the SFP+ port.
Setting up the K2 SAN infrastructure 8. If you do not need trunks, such as on a one-switch system, skip to the next step in this procedure. If you need trunks, such as on a two-switch system with ISLs, do the following: a) Select (Ctrl + Click) the trunked ports. Typically the trunked ports are at the bottom of the list and are labeled Trk1. b) Click Modify Selected Ports. If prompted, log in as administrator. c) For the trunked ports, set Port Enabled to Yes.
Setting up the K2 SAN infrastructure 10. Click Modify Selected Ports. 11. Make sure Port Enabled is set to Yes, leave Mode as default of Auto. 12. Set Flow Control as follows: Set to Disable. 13. Click Apply Settings. Wait until settings are applied and the Web interface becomes active. 14. Proceed as follows: • If the switch carries no media (iSCSI) traffic, such as for a Nearline system, there is no need to configure VLANs. Skip to the end of this procedure.
Setting up the K2 SAN infrastructure 15. Choose VLAN Configuration. If prompted, log in with the switch’s administrator username and password. 16. Create a new Media (iSCSI) VLAN as follows: a) Click Add/Remove VLANs. b) c) d) e) f) 64 In the VLAN Name field enter Media. In the VLAN ID field enter 60. Click Add VLAN. If prompted, log in as administrator. Click Main Screen to return to VLAN Configuration.
Setting up the K2 SAN infrastructure 17. Configure the Media VLAN as follows: a) In the Media VLAN row, click Modify. b) Select all the odd numbered ports. (Tip: Use Ctrl + Click.) c) Also select port A1. This is the 10 Gig SFP+ port on the back of the switch that connects to the K2 Media Server for media (iSCSI) traffic. If you have a NH10GE K2 Media Server for FTP traffic, the 10 Gig SFP+ port on the back of the switch that connects to this server does not go in the Media VLAN.
Setting up the K2 SAN infrastructure 20. Click the VLAN Configuration tab. 21. If you have a trunk, verify that for the default VLAN the trunk is displayed in the Tagged Ports column. 22. If you have two switches, repeat this procedure for the other switch. 23. Close the switch configuration application. Next, configure QOS on the GigE switch. Configuring QOS on the GigE switch Prerequisites for this procedure are as follows: • • • • The switch is HP ProCurve switch 29xx series.
Setting up the K2 SAN infrastructure 2. Type the following, then press Enter: config You are now in configuration mode. 3. Type the following, then press Enter: qos queue-config 2-queues This limits the number of active queues within the switch giving the most buffering to VLANs 1 and 60 4. Type the following, then press Enter: show qos vlan The screen displays VLAN information. Note the ID number of the Media (iSCSI) VLAN.
Setting up the K2 SAN infrastructure • You have network access to the switch Use this procedure to check flow control settings, and if necessary, configure flow control to “off” (disabled) for all ports. 1. If you have not already done so, from a network connected PC open the MS-DOS command prompt and login to the switch as administrator, as follows: a) Telnet to the switch. For example, if the switch’s IP address is 192.168.40.12, you type the following, then press Enter. telnet 192.168.40.
Setting up the K2 SAN infrastructure 4. Execute the copy command with the following syntax: copy tftp flash [ < primary | secondary > ] Note that if you do not specify the flash destination, the TFTP download defaults to the primary flash. For example, to download a software file named T_13_23.swi from a TFTP server with the IP address of 10.16.34.3 1, use the following: ProCurve # copy tftp flash 10.16.34.3 T_13_23.swi 5. When prompted The primary OS image will be deleted.
Setting up the K2 SAN infrastructure Install SiteConfig on control point PC Work through the following topics to install the SiteConfig application on the control point PC. About installing SiteConfig SiteConfig uses a protocol that involves sending Ethernet broadcast messages to discover and configure devices. To enable this protocol to work correctly, there must be unrestricted network access between the PC that hosts SiteConfig and the devices to be discovered.
Setting up the K2 SAN infrastructure Installing/upgrading SiteConfig Prerequisites: • The PC on which you are installing SiteConfg meets system requirements. • The PC is connected to the LAN on which all the devices to be managed are connected. • There are no routed paths to the devices to be managed. 1. Procure SiteConfig installation files from the Grass Valley website or via other distribution mechanisms.
Setting up the K2 SAN infrastructure 5. Open the Windows operating system Services control panel on the PC and look for an entry called " ProductFrame Discovery Agent". The Discovery Agent must be installed on the SiteConfig PC so that the PC can be discovered by SiteConfig and added to the system description as a managed device. This is necessary to ensure name resolution in SiteConfig's hosts file. The Discovery Agent is also known as the Network Configuration Connect Kit.
Planning and implementing a K2 SAN with SiteConfig About developing a system description You use SiteConfig to create or modify a system description for the K2 SAN. You can do this in your planning phase, even before you have devices installed or cabled. Your goal is to have the SiteConfig system description accurately represent all aspects of your devices and networks before you begin actually implementing any networking or other configuration tasks.
Planning and implementing a K2 SAN with SiteConfig The current system description is closed and the system description you are importing is displayed in SiteConfig. About device and host names In SiteConfig, a device can have different names, as follows: • Device name — This is a name for display in SiteConfig only. It is stored in the SiteConfig system description, but not written to the actual device. It is displayed in the device tree view and in the device list view.
Planning and implementing a K2 SAN with SiteConfig 2. Proceed as follows: • In the list view, right-click the Control network and select Details. The Network Settings dialog box opens.
Planning and implementing a K2 SAN with SiteConfig 3. Configure the settings for the network as follows: Setting... For control network Type Ethernet is required Usage Control is required Redundancy None is required. This is true even on a redundant K2 SAN. (Only the iSCSI network is redundant on a redundant K2 SAN.
Planning and implementing a K2 SAN with SiteConfig 2. Proceed as follows: • In the list view, right-click the Streaming network and select Details. The Network Settings dialog box opens.
Planning and implementing a K2 SAN with SiteConfig 3. Configure the settings for the network as follows: Setting... For FTP/streaming network Type Ethernet is required Usage FileTransfer is required Redundancy None is required. This is true even on a redundant K2 SAN. (Only the iSCSI network is redundant on a redundant K2 SAN.
Planning and implementing a K2 SAN with SiteConfig 2. Proceed as follows: • If the K2 SAN is basic (non-redundant), in the list view, right-click the iSCSI network and select Details. • If the K2 SAN is redundant, in the list view, first right-click the primary iSCSI network and select Details. Then proceed to modify the primary iSCSI network. After the primary iSCSI network is modified, repeat these steps and modify the secondary iSCSI network. The Network Settings dialog box opens.
Planning and implementing a K2 SAN with SiteConfig 3. Configure the settings for the network as follows: Setting...
Planning and implementing a K2 SAN with SiteConfig Placeholder device IP configuration On a placeholder device, you edit network interfaces using the Unmanaged Network Interfaces dialog box. The Unmanaged Network Interfaces dialog box allows you only to save changes to the system description. Discovered device IP configuration On a discovered device, you edit network interfaces using the Managed Network Interfaces dialog box.
Planning and implementing a K2 SAN with SiteConfig The Managed Network Interfaces dialog box allows you to edit and save changes to the device. Modifying K2 client unassigned (unmanaged) interface Prerequisites for this task are as follows: • The system description has a SAN K2 client that is a placeholder device. • The placeholder device has a one or more unmanaged network interfaces. Use this task to modify unmanaged network interfaces on a K2 SAN device as follows: • K2 Summit Production Client 1.
Planning and implementing a K2 SAN with SiteConfig 2. In the interfaces list view, right-click an interface and select Edit. The Unmanaged Network Interface Details dialog box opens.
Planning and implementing a K2 SAN with SiteConfig 3. Configure the settings for the interface as follows: Setting... For control network interface Network Control is required IP Address The IP address for this interface on the network. Required. Interface Name The device host name. Required. Set to Default Not recommended. Sets the interface name to SiteConfig default convention, based on the root Site name and device-type. ...use Interface Unselected is required.
Planning and implementing a K2 SAN with SiteConfig • The placeholder device has a one or more unmanaged network interfaces. Use this task to modify managed network interfaces on a K2 SAN device as follows: • K2 Media Server • NH K2 Media Server For the K2 Media Server, do not configure the Fibre Channel interface. SiteConfig does not manage this interface. It is represented in SiteConfig only to complete the description of the K2 Media Server. 1.
Planning and implementing a K2 SAN with SiteConfig 3. Configure the settings for the interface as follows: Setting... For control network interface Network Control is required IP Address The IP address for this interface on the network. Required. Interface Name The device host name. Required. Set to Default Not recommended. Sets the interface name to SiteConfig default convention, based on the root Site name and device-type. ...use Interface Unselected is required.
Planning and implementing a K2 SAN with SiteConfig Setting... For media (iSCSI) network interface Set to Default Disabled, since names are excluded from the hosts file. Disregard. ...use Interface Disabled, since names are excluded from the hosts file. Disregard. Name/Aliases in Host Files... Aliases Disabled, since names are excluded from the hosts file. Disregard. DNS Suffix Disabled, since names are excluded from the hosts file. Disregard. 4. Click OK to save settings and close.
Planning and implementing a K2 SAN with SiteConfig 2. In the toolbar, click the discover devices button. The Discover Devices dialog box opens. A list of discovered devices is displayed. 3. Click Rescan to re-run the discovery mechanism. You can do this if a device that you want to discover has its network connection restored or otherwise becomes available. Additional devices discovered are added to the list.
Planning and implementing a K2 SAN with SiteConfig 3. To also view previously discovered devices that have already been assigned to a device in the system description, select Show … currently assigned devices. The currently assigned devices are added to the list. Viewing both assigned and unassigned devices in this way can be helpful to verify the match between discovered devices and placeholder devices. 4.
Planning and implementing a K2 SAN with SiteConfig 2. In the Interfaces list view determine the interface to configure, as follows: • Identify the interface with which SiteConfig is currently communicating, indicated by the green star overlay icon. This should be the control network interface. • Verify that the interface over which SiteConfig is currently communicating is in fact the interface defined for the control network in the system description.
Planning and implementing a K2 SAN with SiteConfig 5. Identify the interface on the discovered device that you are configuring. • Identify Ethernet LAN adapters by their "Description" name. This is the Windows connection name. SiteConfig reads this name from the device and displays it at the top of this dialog box. This is the most accurate way to identify the network adapter on the discovered device that you are configuring. 6. Configure naming settings as follows: Setting...
Planning and implementing a K2 SAN with SiteConfig 8. To modify planned settings, do the following: a) Select the network settings and click Edit. The Edit IP Address dialog box opens. b) Edit IP address settings as follows: Setting... For network interface Control Team Network Control is required Address Allocation Static is recommended. IP Address The IP address for this interface on the network. Required. Setting...
Planning and implementing a K2 SAN with SiteConfig The networks listed in the Edit IP Address dialog box are those currently defined in the system description, with available settings restricted according to the network definition. If you require settings that are not available, you can close dialog boxes and go to the Network Configuration | Networks tab to modify network settings, then return to the Edit IP Address dialog box to continue. 9.
Planning and implementing a K2 SAN with SiteConfig • NH K2 Media Server 1. In the Interfaces list view determine the interface to configure, as follows: • Identify the interface with which SiteConfig is currently communicating, indicated by the green star overlay icon. This should be the control network interface. • Verify that the interface over which SiteConfig is currently communicating is in fact the interface defined for the control network in the system description.
Planning and implementing a K2 SAN with SiteConfig 3. In the Interfaces list view, right-click the interface you are configuring and select Edit. The Managed Network Interface Details dialog box opens. 4. Identify the interface on the discovered device that you are configuring. • Identify Ethernet LAN adapters by their "Description" name. This is the Windows connection name. SiteConfig reads this name from the device and displays it at the top of this dialog box.
Planning and implementing a K2 SAN with SiteConfig 5. Configure naming settings as follows: Setting... For network interface Control Connection Interface Name The device host name. Required. Set To Default Not recommended DNS Suffix Allowed, if applicable to the network. The DNS suffix is added to the interface name. Aliases Not allowed Use Interface Unselected is required. Since not selected, the default behavior occurs, which Name/Aliases in is to use the device host name in the hosts file.
Planning and implementing a K2 SAN with SiteConfig 7. To modify planned settings, do the following: a) Select the network settings and click Edit. The Edit IP Address dialog box opens. b) Edit IP address settings as follows: Setting... For network interface Control Connection Network Control is required Address Allocation Static is recommended. IP Address The IP address for this interface on the network. Required. Setting...
Planning and implementing a K2 SAN with SiteConfig Setting... For redundant SAN K2 Media Server A any network interface of type iSCSI IP Address The IP address for this interface on the network. Required. Setting... For redundant SAN K2 Media Server B any network interface of type iSCSI Network iSCSI (Secondary Redundant) is required Address Allocation Static is required. IP Address The IP address for this interface on the network. Required.
Planning and implementing a K2 SAN with SiteConfig 4. If enabled, click Set to Device Name. This changes the host name to be the same as the device name. 5. Click OK. 6. When prompted, restart the device. Pinging devices from the PC that hosts SiteConfig Prerequisites: • The devices you are pinging are in the SiteConfig system description. You can send the ping command to one or more devices in the system description over the network to which the SiteConfig host PC is connected.
Planning and implementing a K2 SAN with SiteConfig SiteConfig does not automatically deploy hosts files to managed devices as you add or remove devices. If you add or remove devices from the system description, you must re-deploy the modified hosts file to all devices.
Planning and implementing a K2 SAN with SiteConfig 4. Do one of the following: • If you are managing host table information yourself, click Save As and save a copy of the hosts file to a location on the control point PC. Then open the copy of the hosts file, copy the desired host table information from it, and paste it into your facility hosts file as desired. Then you can use your own process to distribute the facility hosts file to devices.
Planning and implementing a K2 SAN with SiteConfig 102 K2 Installation and Service Manual 2013 07 20
Managing K2 Software Configuring K2 software deployment Take the following into consideration when using SiteConfig to deploy K2 SAN software. • You typically configure one deployment group for K2 clients and one deployment group for K2 Media Servers. This allows you to target and sequence software deployment tasks to the different types of devices. • You typically upgrade K2 Media Servers first, then K2 Media Clients.
Managing K2 Software 3. Right-click the deployment group and select Add Target Device. The Add Target Device(s) wizard opens. 4. In the Available Target Devices tree view, select the node that displays the devices that you are combining as a deployment group. 5. In the right-hand pane, select the devices that you are combining as a deployment group. To select multiple devices, you can drag through the devices, use Ctrl + Click, or use Shift + Click. 6. Click OK.
Managing K2 Software The package appears in the Managed Packages list for the selected deployment group. SiteConfig creates new software deployment tasks for the package and displays them in the Tasks list view. Checking all currently installed software on devices Prerequisites for this task are as follows: • The device is assigned in the SiteConfig system description and network connectivity is present.
Managing K2 Software • The D: drive is for the media file system (SNFS) and database. This allows you to restore the Windows operating system on the C: drive, yet keep the files on the D: drive intact. You can also restore the D: drive itself, however your backup and recovery strategy is different for non-redundant and redundant systems, as follows: • On non-redundant servers the media file system program, metadata, and journal files are on the D: drive. Also the media database program is on the D: drive.
Managing K2 Software At the K2 Media Server first birthday... 1. Boot from the Recovery CD. 2. Create a set of disk image recovery CDs. These CDs contain the C:, D:, and E: partitions. 3. Create a disk image, writing the disk image to the E: partition. This disk image contains the C: and D: partitions. 4. Copy the disk image from the E: partition to another location, such as a network drive. At milestones, such as after software upgrades… 1. Boot from the Recovery CD. 2.
Managing K2 Software 5. In the Acronis main window, click Backup. The Create Backup Wizard opens. 6. On the Welcome page, click Next. 7. On the Partitions Selection page, do the following: a) Select the (C:) and the (D:) partitions and then click Next. 8. On the Backup Archive Location page, do the following: a) In the tree view select the Backup (E:) partition and enter the name of the image file you are creating. Create the file name using the machine hostname and the date. Name the file with the .
Managing K2 Software 4. At the startup screen, select True Image Server OEM (Full Version). The Acronis main window appears. 5. In the Acronis main window, click Recovery. The Restore Data Wizard opens. 6. On the Welcome page, click Next. 7. On the Backup Archive Selection page, in the tree view expand the node for the E: partition and select the image file, then click Next. 8. On the Restoration Type Selection page, select Restore disks or partitions and then click Next. 9.
Managing K2 Software Restoring from the generic recovery disk image on E: Dell R610 There can be multiple versions of the generic recovery disk image on the server’s E: partition. Refer to related topics in the server product's release notes to determine which version you should use. This procedure can be used on a server that needs to be restored to its factory default state. For example, if you neglected to make a first birthday image, you might need to use this procedure.
Managing K2 Software 16. On the Partition or Disk to Restore page, select (D:) and then click Next. 17. On the Restored Partition Location page, select (D:) and then click Next. opens. 18. On the Restored Partition Type page, leave the selection at Primary and then click Next. 19. On the Restored Partition Size page, leave settings at their defaults. The size reported in the upper pane is the size detected of the actual D: partition.
Managing K2 Software 2. Connect all motherboard NICs to LAN connections. 3. If you have not already done so, connect keyboard, monitor, and mouse. 4. Do the following: a) Insert the Recovery CD. b) Restart the machine. If there is a problem restarting, hold the standby button down for five seconds to force a hard shutdown. Then press the standby button again to startup. The system boots from the Recovery CD. The Acronis program loads. 5.
Managing K2 Software The backup consists of a directory and multiple files. Keep all files and directories intact. Do not delete or separate. Restoring from the system-specific recovery disk image on E: Dell R620 Use this task to restore a server using an image made from that particular server. If restoring from a generic factory default image, do not use this task. 1. Make sure that media access is stopped and that the system on which you are working is not being used. 2.
Managing K2 Software 11. On the Recover data page, under Where to recover, verify the following: Recover to: Physical machine Clear all Recover 'NTFS (C:)' to... Properties....Size:.......Letter: C Clear Disk 1/NTFS (C:) Recover 'NTFS (D:)' to... Properties....Size:.......Letter: D Clear Disk 1/NTFS (D:) 12. On the Recover Data page, click OK. The restore process begins. 13. On the My Recovery Details page, select the Progress tab to view the progress. The image loads in approximately 9 minutes. 14.
Managing K2 Software 7. On the Recover Data page, under What to Recover page, select Select Data. The Data to Recover Selection dialog box opens. 8. On the Data to Recover Selection dialog box, do the following: a) Select Browse. b) In the tree view, select the USB drive that contains the generic recovery disk image. Even though your backup is on the drive, it is not yet visible. c) Click OK. On the Archive View tab, your backup name is listed. 9. On the Archive View tab, select your backup. 10.
Managing K2 Software 14. When the data is successfully restored, click OK. 15. Close all Acronis pages and the Acronis main window. The machine restarts automatically. 16. Remove the recovery media while the machine is shutting down. 17. When prompted, enter the machine name. Make sure the name is identical to the name it previously had. After start up, one or more device discovery windows can open. Allow processes to complete without interference.
Managing K2 Software 3. To launch the program that installs the ProductFrame Discovery Agent Service do the following: a) Copy the Discovery Agent Setup directory to the device. b) In the directory, double-click the DiscoveryAgentServiceSetup.msi file. The setup program launches to install the SiteConfig Discovery Agent. c) Follow the setup wizard. 4. When presented with a list of device types, select the following: • K2Server 5. Complete the setup wizard and restart the device.
Managing K2 Software 5. Wait for the connection. If the system times out, you are prompted for entering information in the Internet Protocol Connection dialog. Enter the proxy address and port number as appropriate for your facility’s connections. 6. Ensure that “You have successfully activated your copy of Windows” message appears in Activate Windows. 7. Click OK to close the Activate Windows.
Managing K2 Software • Make sure that Embedded Security is not in Update mode when using SiteConfig to install software. Update mode interferes with SiteConfig's automatic management of Embedded Security and causes problems running the software installed. • Leave Embedded Security enabled for normal operation of your Grass Valley system. Do not disable Embedded Security except as instructed by Grass Valley product documentation or as directed by Grass Valley Support.
Managing K2 Software 2. Manage the Update mode as follows: • If Embedded Security is not in Update mode, click Enter to put it in Update mode. • If Embedded Security is already in Update mode, click Leave to take it out of Update mode. A restart is not required after you change the Update mode.
Configuring and licensing the K2 SAN About K2 SAN licensing When you purchase your K2 SAN, Grass Valley sizes the SAN according to your requirements for bandwidth and other considerations. Part of this sizing exercise is the application of the appropriate license for your SAN. The K2 SAN license enables bandwidth in increments. A SAN with no license allows the lowest amount of bandwidth.
Configuring and licensing the K2 SAN The exact QOS values for your K2 SAN are calculated by Grass Valley to meet your workflow requirements. When you operate your K2 SAN within the bounds of those requirements you should have no bandwidth problems, even during peak bandwidth events. If your workflow requirements change, allow Grass Valley to re-calculate your QOS values. Some versions of K2 software have a RVIO calculator in the K2Config application.
Configuring and licensing the K2 SAN Prerequisites for initial configuration - Basic K2 SAN Before beginning your initial configuration, make sure the devices of the K2 SAN meet the following prerequisites.
Configuring and licensing the K2 SAN Defining a new K2 SAN If you import a SiteConfig system description file in which the SAN is defined, you do not need to define a new SAN. You can skip this task and instead start by configuring the first K2 Media Server. 1. On the control point PC, open the K2Config application. A log on dialog box opens. 2. Log on to the K2Config application with the Windows administrator account. The K2Config application opens. 3. Click New K2 System.
Configuring and licensing the K2 SAN The New K2 System wizard opens to page 1. Related Topics About application security on the K2 SAN on page 266 Configure New K2 System page 1 - Basic K2 SAN 1. Create a name for your system and type it in the Name box. 2. Select L30. 3. If so designed, select Enable Live Production mode. Do not select the Server redundancy option. 4. Click Next. Page 2 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 2 - Basic K2 SAN 1. Move the following into the Number of devices box: • • • • One K2 Media Server One Ethernet switch K2 clients as appropriate for your system. (Optional) One or more K2 Media Servers to represent each NH K2 Media Server on your system. • (Optional) Other devices as appropriate for your system. 2. Click Next. Page 3 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 3 - Basic K2 SAN 1. Review the information on this page and verify that you have correctly defined your K2 SAN. For a basic K2 SAN you should have the following: • • • • One Gigabit Ethernet switch One K2 Media Server Optionally, one or more NH K2 Media Servers The number and type of clients appropriate for your system. 2. Click Finish. The Define New K2 Storage System wizard closes.
Configuring and licensing the K2 SAN Configure Define Server Roles page - Basic K2 SAN 1. Enter the name for the K2 Media Server, as currently configured on the machine. 2. Select all roles, except as follows: If the K2 SAN has one or more optional NH servers, then FTP traffic should go to the NH server, not the K2 Media Server you are now configuring. In this case, do not select the FTP server role or the NAS server role 3. Click Next. The Software Configuration page opens.
Configuring and licensing the K2 SAN Configure Software Configuration page - Basic K2 SAN This page checks for the software required to support the roles you selected on the previous page. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring and licensing the K2 SAN Configure Network Configuration page - Basic K2 SAN This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. NOTE: This page does not configure the iSCSI interface (media network) ports. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating.
Configuring and licensing the K2 SAN Configure File System Server Configuration page - Basic K2 SAN This page checks on the configuration of the K2 Media Server in one of its main roles as a file system server. The K2 Media Server also functions as a file system client, which is also checked from this page. 1. Click Launch Storage Manager. Storage Utility opens. 2. Leave the Configure K2 Server wizard open while you use Storage Utility. When you are done with Storage Utility, you continue with the wizard.
Configuring and licensing the K2 SAN • Power on Use the Storage Utility to configure the following settings for the K2 RAID controller: • • • • IP address Subnet mask Gateway Address SNMP trap destinations For K2 RAID, network and SNMP settings are set and stored on the RAID controller module, so the combined RAID storage devices, including the optional Expansion chassis, exist as a single entity on the control network.
Configuring and licensing the K2 SAN 5. Enter the control network IP address and other network settings. 6. For SNMP Configuration, enter the IP address of the SNMP manager PC. You can also enter IP addresses for other SNMP managers to which you want to send SNMP trap messages. 7. Click OK to save settings and close. 8. In Storage Utility click View | Refresh. Next, bind disk modules.
Configuring and licensing the K2 SAN 4. Right-click the Unbound node for a controller, then select Bind in the context menu. If the RAID chassis has two controllers, both controllers are represented by the single “Controller” node. The Bind dialog box opens showing all unbound disks for the controller listed in the Available Disk list. 5. Leave Full Bind unchecked. 6. In the Bind Type drop down box, select RAID 5 or RAID 6, as specified by your system design. 7.
Configuring and licensing the K2 SAN 9. Click OK to close the Bind dialog box and begin the binding process. The Progress Report dialog box opens, showing the status of the binding process. 10. Close the Progress Report and repeat these steps for other unbound disks. If specified by your system design, you can bind some disks as Hot Spares.
Configuring and licensing the K2 SAN • Disks bound 1. If you have not already done so, launch Storage Utility from the K2Config application. 2. As prompted, wait while Storage Utility gathers system information, then Storage Utility opens. 3. In Storage Utility, click Tools | Make New File System. The Setting dialog box opens. 4. For the Real Time Input/Output (RTIO) rate, enter the value specified by your system design. If you do not know this value, contact your Grass Valley representative. 5.
Configuring and licensing the K2 SAN 6. Click OK. The Configuration File dialog box opens. The configuration file for the media file system is displayed. 7. Verify media file system parameters. Do not edit the configuration file for the media file system. 8. Click Accept. A “…Please wait…” message box displays progress and a “…succeeded…” message confirms the process is complete.
Configuring and licensing the K2 SAN • New file system made This page checks on the configuration of the K2 Media Server in one of its main roles as a file system server. The K2 Media Server also functions as a file system client, which is also checked from this page. 1. In K2Config open the server's File System Server Configuration page, if the page is not already open. 2. If desired, configure reference file generation. 3. Click Check. 4.
Configuring and licensing the K2 SAN Configure iSCSI Bridge Server Configuration page - Basic K2 SAN This page manages the components that bridge between iSCSI (the GigE media network) and the Fibre Channel connection to the RAID storage. You configure network settings on the iSCSI adapters and the page validates that the Fibre Channel adapter is in place and that the media RANKs are visible as iSCSI targets. 1. Select an iSCSI adapter and do the following: a) Click Modify.
Configuring and licensing the K2 SAN 3. Click Check. The Validation Report opens. 4. Confirm that the iSCSI configuration is successful. 5. Close the Validation Report. 6. Click Next. The Database Server Configuration page opens.
Configuring and licensing the K2 SAN Click Next. You do not need to enter or configure anything on this page. The FTP Server Configuration page opens. Configure FTP Server Configuration page - Basic K2 SAN This page appears only if the server has the role of FTP server. Do not modify these settings. Leave at default values of Max FTP streams = 4, FTP Data Socket Timeout = 60, and FTP Port = 21.
Configuring and licensing the K2 SAN • If you do not have NH servers, configure K2 clients and/or other iSCSI clients on the K2 SAN next. Configuring optional NH servers If you have one or more optional NH K2 Media Servers, you next configure those servers. This section applies to both NH1 (1 Gig FTP) servers and NH10GE (10 Gig FTP) servers. NOTE: Multiple NH servers on a K2 SAN must be of the same type, either all NH1 or all NH10GE. 1.
Configuring and licensing the K2 SAN Configure Software Configuration page - NH server This page checks for the software required to support the roles you selected on the previous page. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring and licensing the K2 SAN Configure Network Configuration page - NH server This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating. If correctly configured, it is already assigned the control network IP address, as displayed on this page. 2. Verify that the FTP/Streaming port is configured correctly.
Configuring and licensing the K2 SAN Configure File System Client Configuration page - NH server This system does not function as a file system server. It does function as a file system client, which is validated from this page. 1. Do not select Reserved Bandwidth unless instructed to do so by Grass Valley. This system is usually not configured for RVIO. 2. Click Check. 3. When the wizard reports that the configuration is correct, click Next.
Configuring and licensing the K2 SAN Configure FTP Server Configuration page - Basic SAN NH server This page appears only if the server has the role of FTP server. Do not modify these settings. Leave at default values of Max FTP streams = 4, FTP Data Socket Timeout = 60, and FTP Port = 21. Only qualified Grass Valley personnel should specify other values, as these settings are intended for use only with custom systems designed by Grass Valley. 1.
Configuring and licensing the K2 SAN Prerequisites for initial configuration - Redundant K2 SAN Before beginning your initial configuration, make sure the devices of the K2 SAN meet the following prerequisites.
Configuring and licensing the K2 SAN Defining a new K2 SAN If you import a SiteConfig system description file in which the SAN is defined, you do not need to define a new SAN. You can skip this task and instead start by configuring the first K2 Media Server. 1. On the control point PC, open the K2Config application. A log on dialog box opens. 2. Log on to the K2Config application with the Windows administrator account. The K2Config application opens. 3. Click New K2 System.
Configuring and licensing the K2 SAN The New K2 System wizard opens to page 1. Related Topics About application security on the K2 SAN on page 266 Configure New K2 System page 1 - Redundant K2 SAN 1. 2. 3. 4. 5. Create a name for your system and type it in the Name box. Select L30. If so designed, select Enable Live Production mode. Select the Server redundancy option. Click Next. Page 2 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 2 - Redundant K2 SAN 1. Move the following into the Number of devices box: • • • • Two K2 Media Servers Two Ethernet switches K2 clients as appropriate for your system. (Optional) One or more K2 Media Servers to represent each NH K2 Media Server on your system. • (Optional) Other devices as appropriate for your system. 2. Click Next. Page 3 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 3 - Redundant K2 SAN 1. Review the information on this page and verify that you have correctly defined your K2 SAN. For a basic K2 SAN you should have the following: • • • • One Gigabit Ethernet switch One K2 Media Server Optionally, one or more NH K2 Media Servers The number and type of clients appropriate for your system. 2. Click Finish. The Define New K2 Storage System wizard closes.
Configuring and licensing the K2 SAN Configure Define Server Roles page - Redundant K2 SAN server A and server B 1. Enter the name for the K2 Media Server, as currently configured on the machine. 2. Enter the name or IP address of the Ethernet switch, as currently configured on the switch, to which the K2 Media Server is connected. 3.
Configuring and licensing the K2 SAN Configure Software Configuration page - Redundant K2 SAN server A and server B This page checks for the software required to support the roles you selected on the previous page. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring and licensing the K2 SAN Configure Network Configuration page - Redundant K2 SAN server A and server B This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. NOTE: This page does not configure the iSCSI interface (media network) ports. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating.
Configuring and licensing the K2 SAN 2. Click Launch Storage Manager. Storage Utility opens. 3. Leave the Configure K2 Server wizard open while you use Storage Utility. When you are done with Storage Utility, you continue with the wizard. Next, use Storage Utility to configure the RAID storage and file system. Configuring RAID Use Storage Utility to complete the configuration of the K2 RAID storage devices, as explained in the following topics.
Configuring and licensing the K2 SAN 3. In Storage Utility tree view, expand the node for the K2 RAID, right-click the icon for a RAID controller, and select Configuration | Network Properties. The Controller Network Settings dialog box opens. 4. In the Controller Slot Number field enter 0 and then press Enter. The settings from controller 0 are loaded into the Controller Network Settings dialog box and are available for you to modify. 5. Enter the control network IP address and other network settings. 6.
Configuring and licensing the K2 SAN Binding disk modules - Redundant K2 SAN Prerequisites for the K2 RAID chassis are as follows: • Fibre Channel cable(s) connected • Ethernet cable(s) connected • Power on Prerequisites for the optional K2 RAID Expansion chassis (if present) are as follows: • Fibre channel cable(s) connected • Power on NOTE: Binding destroys all user data on the disks. 1. If you have not already done so, launch Storage Utility from the K2Config application. 2.
Configuring and licensing the K2 SAN 4. For systems that use RAID 1 RANKs, you must now create the separate RAID 1 storage for file system metadata files and journal files. To bind unbound disks for metadata and journal storage, do the following: a) Right-click the Unbound node for the controller, then select Bind in the context menu.
Configuring and licensing the K2 SAN 5. Right-click the Unbound node for a controller, then select Bind in the context menu. If the RAID chassis has two controllers, both controllers are represented by the single “Controller” node. The Bind dialog box opens showing all unbound disks for the controller listed in the Available Disk list. 6. Leave Full Bind unchecked. 7. In the Bind Type drop down box, select RAID 5 or RAID 6, as specified by your system design. 8.
Configuring and licensing the K2 SAN 10. Click OK to close the Bind dialog box and begin the binding process. The Progress Report dialog box opens, showing the status of the binding process. 11. Close the Progress Report and repeat these steps for other unbound disks. If specified by your system design, you can bind some disks as Hot Spares.
Configuring and licensing the K2 SAN • Power on • Disks bound 1. If you have not already done so, launch Storage Utility from the K2Config application. 2. As prompted, wait while Storage Utility gathers system information, then Storage Utility opens. 3. In Storage Utility, click Tools | Make New File System. The Setting dialog box opens. 4. For the Real Time Input/Output (RTIO) rate, enter the value specified by your system design. If you do not know this value, contact your Grass Valley representative.
Configuring and licensing the K2 SAN 6. Click OK. The Set Stripe Group dialog box opens. 7. If you have RAID 1 RANKS, assign a RAID 1 RANK for both MetaStripe and JournalStripe. You can distinguish RAID 1 RANK from media RANKs by the value in the Number of Sectors column.
Configuring and licensing the K2 SAN 8. Click OK. The Configuration File dialog box opens. The configuration file for the media file system is displayed. 9. Verify media file system parameters. Do not edit the configuration file for the media file system. 10. Click Accept. A “…Please wait…” message box displays progress and a “…succeeded…” message confirms the process is complete.
Configuring and licensing the K2 SAN • New file system made This page checks on the configuration of the K2 Media Server in one of its main roles as a file system server. The K2 Media Server also functions as a file system client, which is also checked from this page. 1. In Storage Utility open the server's File System Server Configuration page, if the page is not already open. 2. If you have not already done so, enter the name or IP address of the redundant K2 Media Server (server B). 3.
Configuring and licensing the K2 SAN Configure iSCSI Bridge Server Configuration page - Redundant K2 SAN server A This page manages the components that bridge between iSCSI (the GigE media network) and the Fibre Channel connection to the RAID storage. You configure network settings on the iSCSI adapters and the page validates that the Fibre Channel adapter is in place and that the media RANKs are visible as iSCSI targets. 1. Select Primary. 2. Select an iSCSI adapter and do the following: a) Click Modify.
Configuring and licensing the K2 SAN 4. Click Check. The Validation Report opens. 5. Confirm that the iSCSI configuration is successful. 6. Close the Validation Report. 7. Click Next. The Database Server Configuration page opens. Configure Database Server Configuration page - Redundant K2 SAN server A 1. Enter the name or IP address of K2 Media server B. This is the redundant partner of the server you are now configuring.
Configuring and licensing the K2 SAN 2. Click Next. The FTP Server Configuration page opens. Configure FTP Server Configuration page - Redundant K2 SAN server A This page appears only if the server has the role of FTP server. Do not modify these settings. Leave at default values of Max FTP streams = 4, FTP Data Socket Timeout = 60, and FTP Port = 21. Only qualified Grass Valley personnel should specify other values, as these settings are intended for use only with custom systems designed by Grass Valley.
Configuring and licensing the K2 SAN • The restart of server A after it is configured is complete After you have configured the first K2 Media Server (server A) you next configure the redundant K2 Media Serer (server B). 1. Verify that server A has restarted by opening the MS-DOS command prompt and use the “ping” command. 2. In the K2 System Configuration application tree view, select the K2 Media Server you are configuring as server B. 3. Click the Configure button.
Configuring and licensing the K2 SAN Configure Software Configuration page - Redundant K2 SAN server A and server B This page checks for the software required to support the roles you selected on the previous page. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring and licensing the K2 SAN Configure Network Configuration page - Redundant K2 SAN server A and server B This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. NOTE: This page does not configure the iSCSI interface (media network) ports. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating.
Configuring and licensing the K2 SAN Configure File System Server Configuration page - Redundant K2 SAN server B This page checks on the configuration of the K2 Media Server in one of its main roles as a file system server. The K2 Media Server also functions as a file system client, which is also checked from this page. It is not necessary to bind RANKs or create a file system, since this task was completed when you configured the previous K2 Media Server. 1. 2. 3. 4. 5.
Configuring and licensing the K2 SAN Configure iSCSI Bridge Server Configuration page - Redundant K2 SAN server B This page manages the components that bridge between iSCSI (the GigE media network) and the Fibre Channel connection to the RAID storage. You configure network settings on the iSCSI adapters and the page validates that the Fibre Channel adapter is in place and that the media RANKs are visible as iSCSI targets.
Configuring and licensing the K2 SAN 4. Click Check. The Validation Report opens. 5. Confirm that the iSCSI configuration is successful. 6. Close the Validation Report. 7. Click Next. The Database Server Configuration page opens.
Configuring and licensing the K2 SAN Click Next. You do not need to enter or configure anything on this page. The FTP Server Configuration page opens. Configure FTP Server Configuration page - K2 SAN server B This page appears only if the server has the role of FTP server. Do not modify these settings. Leave at default values of Max FTP streams = 4, FTP Data Socket Timeout = 60, and FTP Port = 21.
Configuring and licensing the K2 SAN Check the V: drive Prerequisites: • The K2 Media Server is configured • The restart of the K2 Media Server after it is configured is complete This task is required for NAS server functionality. 1. Verify that the K2 Media Server has restarted by opening the MS-DOS command prompt and use the “ping” command. 2. In the K2Config application tree view, under the K2 Media Server select the File System Server node. The File System Server Configuration page appears. 3.
Configuring and licensing the K2 SAN Configure Define Server Roles page - NH server 1. Enter the name for the K2 Media Server, as currently configured on the machine. 2. Select FTP server and NAS server. 3. Click Next. The Software Configuration page opens.
Configuring and licensing the K2 SAN Configure Software Configuration page - NH server This page checks for the software required to support the roles you selected on the previous page. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring and licensing the K2 SAN Configure Network Configuration page - NH server This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating. If correctly configured, it is already assigned the control network IP address, as displayed on this page. 2. Verify that the FTP/Streaming port is configured correctly.
Configuring and licensing the K2 SAN Configure File System Client Configuration page - NH server This system does not function as a file system server. It does function as a file system client, which is validated from this page. 1. Do not select Reserved Bandwidth unless instructed to do so by Grass Valley. This system is usually not configured for RVIO. 2. Click Check. 3. When the wizard reports that the configuration is correct, click Next.
Configuring and licensing the K2 SAN Configure FTP Server Configuration page - Redundant K2 SAN NH server This page appears only if the server has the role of FTP server. Do not modify these settings. Leave at default values of Max FTP streams = 4, FTP Data Socket Timeout = 60, and FTP Port = 21. Only qualified Grass Valley personnel should specify other values, as these settings are intended for use only with custom systems designed by Grass Valley. 1.
Configuring and licensing the K2 SAN • The restart of the K2 Media Server after it is configured is complete This task is required for NAS server functionality. 1. Verify that the K2 Media Server has restarted by opening the MS-DOS command prompt and use the “ping” command. 2. In the K2Config application tree view, under the K2 Media Server select the File System Server node. The File System Server Configuration page appears. 3. Click Check and verify that the V: drive is shared.
Configuring and licensing the K2 SAN • Power on for all servers K2 RAID chassis • Fibre Channel cable(s) connected • Ethernet cable(s) connected • Power on K2 RAID Expansion chassis (optional) • Fibre channel cable(s) connected • Power on Defining a new K2 SAN If you import a SiteConfig system description file in which the SAN is defined, you do not need to define a new SAN. You can skip this task and instead start by configuring the first K2 Media Server. 1.
Configuring and licensing the K2 SAN 2. Log on to the K2Config application with the Windows administrator account. The K2Config application opens. 3. Click New K2 System. The New K2 System wizard opens to page 1.
Configuring and licensing the K2 SAN Configure New K2 System page 1 - Nearline K2 SAN 1. Create a name for your system and type it in the Name box. 2. Select Nearline. The Server redundancy option is not selected and is disabled. This option applies to media database redundancy. Since the Nearline system has no media database, this setting is correct for both redundant and non-redundant Nearline systems. 3. Click Next. Page 2 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 2 - Nearline K2 SAN 1. Move the following into the Number of devices box: • One K2 Media Server • One Ethernet switch 2. Click Next. Page 3 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 3 - Nearline K2 SAN 1. Review the information on this page and verify that you have correctly defined your K2 SAN. For a redundant nearline K2 SAN you should have the following: • Two Gigabit Ethernet switches • Two K2 Media Servers 2. Click Finish. The Define New K2 Storage System wizard closes. Your storage system appears in the tree view of the K2Config application. Next, configure the server. Configuring NH server - Part 1 1.
Configuring and licensing the K2 SAN Configure Define Server Roles page - NH server 1. Enter the name for the K2 Media Server, as currently configured on the machine. For Nearline server roles, selections are disabled. Leave SNFS file system server, FTP server, and NAS server selected. The wizard does not allow you to select Media Database Server. There is no Media Database Server in a nearline system. 2. Click Next. The Software Configuration page opens.
Configuring and licensing the K2 SAN Configure Software Configuration page - NH server This page checks for the software required to support the roles you selected on the previous page. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring and licensing the K2 SAN Configure Network Configuration page - NH server This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating. If correctly configured, it is already assigned the control network IP address, as displayed on this page. 2. Verify that the FTP/Streaming port is configured correctly.
Configuring and licensing the K2 SAN Configure File System Server Configuration page - NH server This page checks on the file system server role. The server also functions as a file system client, which is also checked from this page. 1. Do not select Reserved Bandwidth unless instructed to do so by Grass Valley. This system is usually not configured for RVIO. 2. Click Launch Storage Manager. Storage Utility opens. 3. Leave the Configure K2 Server wizard open while you use Storage Utility.
Configuring and licensing the K2 SAN • Power on Use the Storage Utility to configure the following settings for the K2 RAID controller: • • • • IP address Subnet mask Gateway Address SNMP trap destinations For K2 RAID, network and SNMP settings are set and stored on the RAID controller module, so the combined RAID storage devices, including the optional Expansion chassis, exist as a single entity on the control network.
Configuring and licensing the K2 SAN 5. Enter the control network IP address and other network settings. 6. For SNMP Configuration, enter the IP address of the SNMP manager PC. You can also enter IP addresses for other SNMP managers to which you want to send SNMP trap messages. 7. Click OK to save settings and close. 8. In Storage Utility click View | Refresh. Next, bind disk modules.
Configuring and licensing the K2 SAN 3. In the Storage Utility main window, identify bound RANKs and unbound disks by their placement in the hierarchy of the tree view. In the following illustration, disk numbers are represented by “XX”. Nearline systems store media files across both the primary RAID chassis and the optional Expansion chassis. In addition, file system metadata files and journal files are mixed in with the media files. The RAID configuration is the same on all chassis.
Configuring and licensing the K2 SAN 4. Right-click the Unbound node for a controller, then select Bind in the context menu. If the RAID chassis has two controllers, both controllers are represented by the single “Controller” node. The Bind dialog box opens showing all unbound disks for the controller listed in the Available Disk list. 5. Leave Full Bind unchecked. 6. In the Bind Type drop down box, select RAID 6. 7. In the Available Disks box, select twelve contiguous disks at the top of the list.
Configuring and licensing the K2 SAN 9. Click OK to close the Bind dialog box and begin the binding process. The Progress Report dialog box opens, showing the status of the binding process. 10. Close the Progress Report and repeat these steps for other unbound disks. If specified by your system design, you can bind some disks as Hot Spares.
Configuring and licensing the K2 SAN • Disks bound 1. If you have not already done so, launch Storage Utility from the K2Config application. 2. As prompted, wait while Storage Utility gathers system information, then Storage Utility opens. 3. In Storage Utility, click Tools | Make New File System. The Setting dialog box opens. 4. For a Nearline system, enter zero as the Real Time Input/Output (RTIO) rate. 5. Leave Windows Security unchecked. 6. Click OK. The Configuration File dialog box opens.
Configuring and licensing the K2 SAN 7. Verify media file system parameters. Do not edit the configuration file for the media file system. 8. Click Accept. A “…Please wait…” message box displays progress and a “…succeeded…” message confirms the process is complete. A message informs you that you must restart the server, however the restart at the end of the Configure K2 Server wizard suffices, so you do not need to restart now. 9. Close the Storage Utility.
Configuring and licensing the K2 SAN 2. Do not select Reserved Bandwidth unless instructed to do so by Grass Valley. This system is usually not configured for RVIO. 3. Click Check. 4. When the wizard reports that the configuration is correct, click Next. If you get a “The V: will not be available until this device is rebooted…” message, you can safely continue now and reboot later when instructed to do so. The FTP Server Configuration page opens.
Configuring and licensing the K2 SAN Check the V: drive Prerequisites: • The K2 Media Server is configured • The restart of the K2 Media Server after it is configured is complete This task is required for NAS server functionality. 1. Verify that the K2 Media Server has restarted by opening the MS-DOS command prompt and use the “ping” command. 2. In the K2Config application tree view, under the K2 Media Server select the File System Server node. The File System Server Configuration page appears. 3.
Configuring and licensing the K2 SAN K2 Media Server • • • • • • • Ethernet cables connected Fibre Channel cable connected Redundant servers connected by serial cable Software installed, as from the factory, including QuickTime 7 MPIO software installed.
Configuring and licensing the K2 SAN 2. Log on to the K2Config application with the Windows administrator account. The K2Config application opens. 3. Click New K2 System. The New K2 System wizard opens to page 1.
Configuring and licensing the K2 SAN Configure New K2 System page 1 - Nearline K2 SAN 1. Create a name for your system and type it in the Name box. 2. Select Nearline. The Server redundancy option is not selected and is disabled. This option applies to media database redundancy. Since the Nearline system has no media database, this setting is correct for both redundant and non-redundant Nearline systems. 3. Click Next. Page 2 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 2 - Nearline K2 SAN 1. Move the following into the Number of devices box: • Two K2 Media Servers • Two Ethernet switches 2. Click Next. Page 3 opens.
Configuring and licensing the K2 SAN Configure New K2 System page 3 - Nearline K2 SAN 1. Review the information on this page and verify that you have correctly defined your K2 SAN. For a redundant nearline K2 SAN you should have the following: • Two Gigabit Ethernet switches • Two K2 Media Servers 2. Click Finish. The Define New K2 Storage System wizard closes. Your storage system appears in the tree view of the K2Config application. Next, configure the server. Configuring NH server A - Part 1 1.
Configuring and licensing the K2 SAN Configure Define Server Roles page - NH server 1. Enter the name for the K2 Media Server, as currently configured on the machine. For Nearline server roles, selections are disabled. Leave SNFS file system server, FTP server, and NAS server selected. The wizard does not allow you to select Media Database Server. There is no Media Database Server in a nearline system. 2. Click Next. The Software Configuration page opens.
Configuring and licensing the K2 SAN Configure Software Configuration page - NH server This page checks for the software required to support the roles you selected on the previous page. NOTE: MPIO software is required on servers in redundant systems. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring and licensing the K2 SAN Configure Network Configuration page - NH server This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating. If correctly configured, it is already assigned the control network IP address, as displayed on this page. 2. Verify that the FTP/Streaming port is configured correctly.
Configuring and licensing the K2 SAN Configure File System Server Configuration page - NH server This page checks on the file system server role. The server also functions as a file system client, which is also checked from this page. 1. Do not select Reserved Bandwidth unless instructed to do so by Grass Valley. This system is usually not configured for RVIO. 2. Click Launch Storage Manager. Storage Utility opens. 3. Leave the Configure K2 Server wizard open while you use Storage Utility.
Configuring and licensing the K2 SAN • Power on Use the Storage Utility to configure the following settings for the K2 RAID controller: • • • • IP address Subnet mask Gateway Address SNMP trap destinations For K2 RAID, network and SNMP settings are set and stored on the RAID controller module. For the RAID chassis with two controllers, each controller has its own network settings and the RAID chassis exists as two entities on the control network.
Configuring and licensing the K2 SAN 5. Enter the control network IP address and other network settings. 6. For SNMP Configuration, enter the IP address of the SNMP manager PC. You can also enter IP addresses for other SNMP managers to which you want to send SNMP trap messages. 7. For the RAID chassis with two controllers, in the Controller Slot Number field enter 1 and then press Enter.
Configuring and licensing the K2 SAN 3. In the Storage Utility main window, identify bound RANKs and unbound disks by their placement in the hierarchy of the tree view. In the following illustration, disk numbers are represented by “XX”. Nearline systems store media files across both the primary RAID chassis and the optional Expansion chassis. In addition, file system metadata files and journal files are mixed in with the media files. The RAID configuration is the same on all chassis.
Configuring and licensing the K2 SAN 4. Right-click the Unbound node for a controller, then select Bind in the context menu. If the RAID chassis has two controllers, both controllers are represented by the single “Controller” node. The Bind dialog box opens showing all unbound disks for the controller listed in the Available Disk list. 5. Leave Full Bind unchecked. 6. In the Bind Type drop down box, select RAID 6. 7. In the Available Disks box, select twelve contiguous disks at the top of the list.
Configuring and licensing the K2 SAN 9. Click OK to close the Bind dialog box and begin the binding process. The Progress Report dialog box opens, showing the status of the binding process. 10. Close the Progress Report and repeat these steps for other unbound disks. If specified by your system design, you can bind some disks as Hot Spares.
Configuring and licensing the K2 SAN • Disks bound 1. If you have not already done so, launch Storage Utility from the K2Config application. 2. As prompted, wait while Storage Utility gathers system information, then Storage Utility opens. 3. In Storage Utility, click Tools | Make New File System. The Setting dialog box opens. 4. For a Nearline system, enter zero as the Real Time Input/Output (RTIO) rate. 5. Leave Windows Security unchecked. 6. Click OK. The Configuration File dialog box opens.
Configuring and licensing the K2 SAN 7. Verify media file system parameters. Do not edit the configuration file for the media file system. 8. Click Accept. A “…Please wait…” message box displays progress and a “…succeeded…” message confirms the process is complete. A message informs you that you must restart the server, however the restart at the end of the Configure K2 Server wizard suffices, so you do not need to restart now. 9. Close the Storage Utility.
Configuring and licensing the K2 SAN 2. Do not select Reserved Bandwidth unless instructed to do so by Grass Valley. This system is usually not configured for RVIO. 3. Click Check. 4. When the wizard reports that the configuration is correct, click Next. If you get a “The V: will not be available until this device is rebooted…” message, you can safely continue now and reboot later when instructed to do so. The FTP Server Configuration page opens.
Configuring and licensing the K2 SAN Next, configure the other NH server. Configuring NH server B Prerequisites: • Server A is configured • The restart of server A after it is configured is complete On nearline systems, both NH K2 Media Servers are identical, with the exception that only one server can be the active media file system server at any time.
Configuring and licensing the K2 SAN 2. Click Next. The Software Configuration page opens. Configure Software Configuration page - NH server This page checks for the software required to support the roles you selected on the previous page. NOTE: MPIO software is required on servers in redundant systems. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next.
Configuring and licensing the K2 SAN Configure Network Configuration page - NH server This page displays the control network Ethernet port, and allows you to configure the FTP/Streaming network Ethernet port. 1. Verify that the top port is configured correctly. The top port is the port over which the K2Config application is communicating. If correctly configured, it is already assigned the control network IP address, as displayed on this page. 2. Verify that the FTP/Streaming port is configured correctly.
Configuring and licensing the K2 SAN Configure File System Server Configuration page - NH server B This page checks on the configuration of the K2 Media Server in one of its main roles as a file system server. The K2 Media Server also functions as a file system client, which is also checked from this page. It is not necessary to bind RANKs or create a file system, since this task was completed when you configured the previous K2 Media Server. 1.
Configuring and licensing the K2 SAN Configure FTP Server Configuration page - K2 SAN server B This page appears only if the server has the role of FTP server. Do not modify these settings. Leave at default values of Max FTP streams = 4, FTP Data Socket Timeout = 60, and FTP Port = 21. Only qualified Grass Valley personnel should specify other values, as these settings are intended for use only with custom systems designed by Grass Valley. 1.
Configuring and licensing the K2 SAN • The restart of the K2 Media Server after it is configured is complete This task is required for NAS server functionality. 1. Verify that the K2 Media Server has restarted by opening the MS-DOS command prompt and use the “ping” command. 2. In the K2Config application tree view, under the K2 Media Server select the File System Server node. The File System Server Configuration page appears. 3. Click Check and verify that the V: drive is shared.
Configuring clients on the K2 SAN About iSCSI bandwidth When you purchase a K2 SAN to provide the shared storage for your K2 clients, your Grass Valley representative sizes the storage system and recommends the appropriate license level and QOS level based on your bandwidth requirements. These bandwidth requirements are based on how you intend to use the channels of your K2 clients. The bit rates, media formats, and ratio of record channels to play channels all effect your bandwidth requirements.
Configuring clients on the K2 SAN K2 SAN prerequisites for adding clients The following K2 SAN preparations are required to support adding SAN 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 basic, non-redundant K2 SANs, the media network must be operational. You can check this with the K2Config application.
Configuring clients on the K2 SAN 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 can use either SiteConfig or K2Config to configure media networks.
Configuring clients on the K2 SAN 8. After restart, to verify that the software is installed, on the Windows desktop right-click My Computer and select Manage. The Computer Management window opens. 9. In the left pane select Device Manager. 10. In the right pane open the System devices node and verify that GVG ISCSI Multi-Path Device Specific Module is listed. Configuring a K2 client for the K2 Storage System 1. On the PC that hosts K2Config, open the K2Config application. A log on dialog box opens. 2.
Configuring clients on the K2 SAN 3. In the K2Config application tree view, verify that the K2 SAN has the correct number of clients, according to your system design. If the correct number of clients is not currently added to the K2 SAN, you can add or remove clients now (before clients are configured), as follows: • To add a client, select the top node of the storage system and click the Add Device button. • To remove a client, select an unconfigured client and click the Remove button. 4.
Configuring clients on the K2 SAN Configure Software Configuration page - K2 client This page checks the client for required software. NOTE: Multi-Path I/O software must be installed on K2 clients connected to a redundant K2 SAN. 1. If software with Yes in the Required column reports as Not Installed, install the software. 2. Click Check Software. 3. When all required software reports as Installed, click Next. The Network Configuration page opens.
Configuring clients on the K2 SAN Configure Network Configuration page - K2 client This page configures both control and media (iSCSI) network connections. The K2 client actually has four Gigabit Ethernet ports, but two ports are configured as a teamed pair (the control team), while the other two ports (the media connections) are individual. The teamed pair shares an IP address and appears on this page as a single port. 1. Verify that the top port is configured correctly.
Configuring clients on the K2 SAN 6. Verify or enter an IP address for the “B” media (iSCSI) network. Also enter the subnet mask. 7. Click Next. The Database Client Configuration page opens. Configure Database Client Configuration page - K2 client This page connects the SAN client as a media database client to the K2 Media Server taking the role of metadata (database) server. If there are redundant K2 Media Servers, both are listed on this page as database servers. 1.
Configuring clients on the K2 SAN Configure iSCSI Initiator Configuration page - K2 client This page lists the iSCSI adapter on your K2 Media Server as an iSCSI target. The K2Config application subscribes the SAN client to the iSCSI target and allocates bandwidth, based on the bandwidth values that you enter.
Configuring clients on the K2 SAN If a custom K2 SAN, qualified system designers can view subnets to help assign iSCSI targets. 1. Click Modify. The Bandwidth Input dialog box opens. 2. Enter the channel count, bit rate, and track count per channel information according to your intended use of the K2 client. If using ChannelFlex Suite with multiple inputs and/or outputs per channel, do not enter the number of channels.
Configuring clients on the K2 SAN Configure File System Client Configuration page This page connects the SAN client as a media file system client to the K2 Media Server taking the role of media file system server. If there are redundant K2 Media Servers, both are listed on this page as file system servers. 1. Verify that the K2 client is connecting to the correct K2 Media Server or Servers, as follows: • For a basic (non-redundant) K2 SAN, the client connects to the only server.
Configuring clients on the K2 SAN 3. 4. 5. 6. Click Add Device. The Add Device dialog box opens. Select the type of client you are adding. Click OK. The new client appears in the tree view. Configure the client as appropriate. Refer to the documentation for the device. Enter the RVIO value as provided by Grass Valley. Do not attempt to calculate the RVIO value on your own.
Configuring clients on the K2 SAN 2. Shut down the SAN client.
Configuring clients on the K2 SAN 236 K2 Installation and Service Manual 2013 07 20
Operating the K2 SAN Powering off the K2 SAN Use the following procedures to do an orderly power off of the complete K2 SAN. Power off K2 Media Servers 1. Stop all media access as follows: • For nearline systems, stop all FTP streams or other media operations. • For online systems, power-off all K2 clients or other iSCSI clients. 2. Shut down K2 Media Servers as follows: • For nearline systems, shut down all K2 Media Servers.
Operating the K2 SAN 3. Shut down any remaining K2 Media Servers, such as NH FTP servers. Next, power off K2 RAID devices. Powering off K2 G10v2 RAID Prerequisites for this task are as follows: • K2 Media Servers are powered off 1. On the primary RAID chassis controller, identify the Ready LED. It blinks at a rate of 1 blink per second during normal operation. 2. Tap the power button on a RAID controller.
Operating the K2 SAN Basic K2 SAN power on procedure 2013 07 20 K2 Installation and Service Manual 239
Operating the K2 SAN Redundant K2 SAN power on procedure 240 K2 Installation and Service Manual 2013 07 20
Operating the K2 SAN 2013 07 20 K2 Installation and Service Manual 241
Operating the K2 SAN Nearline K2 SAN power on procedure 242 K2 Installation and Service Manual 2013 07 20
Operating the K2 SAN Powering on K2 G10v2 RAID This topic applies to K2 G10v2 (M100) RAID. 1. Verify power and cabling. 2. Tap the power button on the controller, as shown. NOTE: Do not press and hold down the power button. If the RAID chassis has two controllers, you can tap the power button on either controller. You do not need to tap both power buttons. Tapping the power button on a controller also powers on any connected Expansion chassis. There are no power buttons on Expansion chassis. 3.
Operating the K2 SAN 2. Start and log on to the SNMP manager. 3. The SNMP manager reports devices as offline. As each device of the K2 SAN is powered on, check the SNMP manager to verify the device’s status. Failover behaviors If a fault occurs and one of the failover mechanisms is triggered, an online redundant iSCSI K2 SAN behaves as explained in the following sections. The diagrams that follow are representative of a generic redundant K2 SAN.
Operating the K2 SAN Control Team failover behavior K2 SAN-attached system Media Control Media Control Connection Failure X ISLs A Ethernet switches B Media Control FTP Media Control FTP A K2 Media Servers B Fibre Channel connections K2 RAID If the following system connection or component fails to respond to network communication: • The control connection between a K2 SAN-attached system and GigE switch “A”. Then the following failover behavior occurs: 1.
Operating the K2 SAN K2 client media (iSCSI) connection failover behavior K2 SAN-attached system Media Control Media Control Connection Failure X ISLs A A Media Control FTP Media Control FTP Control traffic goes to server A, which is still the media file system/database server. Ethernet switches B iSCSI traffic uses the iSCSI adapter on server B.
Operating the K2 SAN Control Team failover behavior K2 SAN-attached system Media Control Media Control Connection Failure X ISLs A Ethernet switches B Media Control FTP Media Control FTP A K2 Media Servers B Fibre Channel connections K2 RAID If the following system connection or component fails to respond to network communication: • The control connection between a K2 SAN-attached system and GigE switch “A”. Then the following failover behavior occurs: 1.
Operating the K2 SAN K2 Media Server failover behavior K2 SAN-attached systems Media Control Media Control ISLs A 2 X Media Control FTP Media Control FTP 1 3 Ethernet switches B X X A 4 K2 Media Servers B X Fibre Channel connections K2 RAID If the following system connection or component fails to respond to network communication: 1 Either of the Media (iSCSI) network “A” connections between the GigE switch and the K2 Media Server 2 The control connection between GigE switch “A” and K2 M
Operating the K2 SAN K2 Media Server failover with Control team failover behavior K2 SAN-attached systems Media Control Media Control A X ISLs A Media Control FTP Media Control FTP Component Failure Ethernet switches B K2 Media Servers B Fibre Channel connections K2 RAID If the following system connection or component fails to respond to network communication: • The “A” GigE switch Then the following failover behavior occurs: 1.
Operating the K2 SAN 250 K2 Installation and Service Manual 2013 07 20
Description of K2 SAN Devices Device terminology K2 Media Client The K2 product originally released with version 3.x K2 software. It can have internal storage, direct-connect storage, or shared (SAN) storage. First generation K2 Summit system The K2 Summit Production Client product originally release with version 7.x K2 software. It can have internal storage, direct-connect storage, or shared (SAN) storage. K2 Summit 3G system The K2 Summit 3G Production Client product originally release with version 8.
Description of K2 SAN Devices You can purchase a control point PC from Grass Valley. In this case the PC has all the above software pre-installed at the factory. When you receive the PC it is ready to install on the K2 SAN control network and begin using with minimal configuration. You can also build your own control point PC by installing and configuring software on an existing PC. Refer to the K2 System Guide for specifications and instructions.
Description of K2 SAN Devices Characteristic Specification Weight 10.92 lb. (4.95 kg) Voltage 100-127 / 200-240 VAC Power consumption Idle power: 49 W; Maximum power rating: 82 W Temperature Operating: 32ºF to 131ºF (0ºC to 55ºC); Non-operating: -40ºF to 158ºF (-40ºC to 70ºC) Relative humidity: Operating: 15% to 95% @ 104ºF (40ºC) (non-condensing) 15% to 95% @ 149ºF (65ºC) Maximum altitude Up to 10,000 ft.
Description of K2 SAN Devices Dell PowerEdge R610 server Characteristic Specification Operating System Microsoft® Windows® Server 2008 R2 Fibre Channel Adapter ATTO Celerity FC-81ENSingle-Channel 8Gb/s Fibre Channel PCIe 2.
Description of K2 SAN Devices NH K2 Media Server specifications The NH K2 Media Server is built on a Dell PowerEdge R610 and R620 server platform. Specifications that are unique to it purpose as a K2 Media Server are listed in the following table. For a complete list of specifications, refer to Dell documentation.
Description of K2 SAN Devices The RAID Expansion Chassis provides additional storage capacity. The Expansion Chassis has two Expansion Adapters installed. Refer to the installation chapters earlier in this manual for connection and configuration instructions. The K2 10Gv2 RAID is NEC Storage M100 Series. For specifications and servicing information, refer to NEC Storage M100 Series manuals.
Overview of K2 Storage Tools About SiteConfig SiteConfig is Grass Valley's tool for network configuration and software deployment. SiteConfig is a ProductFrame application. ProductFrame is an integrated platform of tools and product distribution processes for system installation and configuration. You can use SiteConfig as a stand-alone tool for planning and system design, even before you have any devices installed or cabled.
Overview of K2 Storage Tools The left side of the screen shows the tree view of the currently loaded system description. The Network Configuration and Software Deployment buttons at the bottom of the tree view activate either the network configuration workspace or the software deployment workspace. The network configuration workspace on the left has two tabs: a Devices tab to display the tree of devices in the system and a Networks tab to show the hierarchy of networks defined in the system.
Overview of K2 Storage Tools configuration, you can import the SiteConfig system description file into the K2Config application to get you started with your SAN configuration. After your K2 SAN is initially installed and configured, if you need to reconfigure the system you should do so using SiteConfig and the K2Config application. This enforces consistent policy and sequencing for configuration tasks, which makes the system easier to maintain and aids in troubleshooting should a problem arise.
Overview of K2 Storage Tools 3. The K2Config application opens. If you have one or more K2 SANs currently configured, the K2Config application displays the systems in the tree view. If you have not yet configured a K2 SAN, the K2Config application opens with the tree view blank. Server Control Panel Server Control Panel allows you to monitor and control the current status of a K2 Media Server in its roles as the media file system server and the metadata server.
Overview of K2 Storage Tools NOTE: Do not click Stop or Start unless you intend to manually control the current primary/redundant roles. Using these buttons can trigger an automatic system recovery (failover) event. To launch Server Control Panel, in the K2Config application, click the Server Control Panel button. On the local K2 Media Server, you must log in with administrator-level privileges in order to use Server Control Panel.
Overview of K2 Storage Tools The Storage Utility’s primary functionality is hosted by the K2 Media Server. The Storage Utility uses the Fibre Channel connection between the K2 Media Server and the RAID storage device for access and configuration. When you launch Storage Utility from the K2Config application on the control point PC, you use a Storage Utility remote interface to control the main application as it runs on the K2 Media Server.
Overview of K2 Storage Tools Drives RAID 5 RAID 6 1 TB 7.2K 4 LUNS/RANK 2 LUNS/RANK Windows Remote Desktop Connection You can use the Microsoft Windows Remote Desktop Connection application to make a remote connection to a Grass Valley system that runs the Windows operating system. Take the following into consideration when connecting to K2 systems: • Before you can use the Remote Desktop Connection, you need network access and permissions to connect to the K2 system.
Overview of K2 Storage Tools 264 K2 Installation and Service Manual 2013 07 20
Administering and maintaining the K2 SAN Passwords and security on Grass Valley systems To provide a basic level of security, Grass Valley systems recognize three different security levels based on Windows users and groups, and the systems ship from the factory with accounts pre-configured accordingly. To access the system you must log on with the user name and password for one of the pre-configured accounts. The following table shows the different types of users and their privileges.
Administering and maintaining the K2 SAN About application security on the K2 SAN The K2Config application and the Storage Utility application both require that you be logged in to the application with administrator privileges in order to modify any settings. These privileges are based on the Windows account that you use when you log in to the K2Config application.
Administering and maintaining the K2 SAN Accessing K2 SAN features In the K2Config, use the following features to K2 SAN settings: About SiteConfig and K2Config settings Many settings and operations, such as network settings, adding/removing devices, and software versions, are managed by both the SiteConfig application and the K2Config application. Each application has its own XML file in which information is stored.
Administering and maintaining the K2 SAN Operation Task flow context and policies Import SiteConfig system Use this operation for initial install/commission description file into (greenfield) sites. First define the site topology K2Config using SiteConfig and complete network configuration and software deployment. Then import the SiteConfig system description into K2Config and complete the K2 SAN configuration.
Administering and maintaining the K2 SAN Operation Task flow context and policies Additional information Change IP address (except Use SiteConfig for IP address changes. Then in — address of TOE on K2 K2Config, click on the changed device's Media Server) network configuration node. This refreshes the K2Config view of IPs from the device. Change IP address of TOE For TOE IP changes and/or TOE card removal, — on K2 Media Server use K2Config.
Administering and maintaining the K2 SAN However, if a situation arises in which you want to purge the information in the configuration file or otherwise control the rules for writing the K2Config information to the Control Panel Service host, you can do so as explained in this topic. 1. Make sure the GV STRATUS Core server is running. 2. Open the K2Config application. 3.
Administering and maintaining the K2 SAN Renaming a K2 SAN Prerequisites for renaming an existing K2 SAN are as follows: • You must be logged in to the K2 System Configuration application with permissions equivalent to K2 administrator or higher. • The devices of the K2 SAN do not need to be offline, and there is no restart of devices required. 1. In the K2 System Configuration application tree view, select the current name of the K2 SAN, which is the top node of the storage system tree. 2. Click Rename.
Administering and maintaining the K2 SAN 2. In the K2 System Configuration application tree view, select the name of the K2 SAN, which is the top node of the storage system tree. 3. Click Add Device. The Add Device dialog box opens. 4. Select Ethernet Switch. 5. Click OK. The new switch appears in the tree view. 6. Configure the switch as appropriate.
Administering and maintaining the K2 SAN 2. In the K2Config application tree view, select the name of the K2 SAN, which is the top node of the storage system tree. 3. Click Remove. The SAN is removed from the tree view. Accessing a K2 SAN from multiple PCs It is recommended that you install the SiteConfig application and the K2 System Configuration (K2Config) application on one PC only in your facility. This eliminates potential problems in the installation, configuration, and maintenance of your K2 SAN.
Administering and maintaining the K2 SAN 2. Shut down all K2 clients and all generic clients. You can do this via SiteConfig. 3. Take all K2 Media Servers out of service. If you have redundant servers, make sure that you know which server is the current primary and which server is the current backup, and that you take primary/backup servers out of service in the proper order. Related Topics Taking a K2 Media Server out of service on page 279 Bringing a K2 SAN online 1.
Administering and maintaining the K2 SAN About QuickTime reference files The following formats are supported as QuickTime reference files: • • • • • • • DV AVC-Intra XDCAM-EX XDCAM-HD XDCAM-HD 422 IMX Avid DNxHD The K2 clip must be a simple clip in order to create the reference file. With the QuickTime reference file you can open the K2 clip with QuickTime tools, such as Final Cut Pro, for playback and editing.
Administering and maintaining the K2 SAN If a redundant K2 SAN, you must configure similarly and restart both K2 Media Servers with role of file system server. Managing redundancy on a K2 SAN If you have a redundant K2 SAN, use the procedures in this section to control the primary/redundant roles of the K2 Media Servers.
Administering and maintaining the K2 SAN Identifying primary/backup from the local K2 Media Server The following procedure assumes that you are at the local K2 Media Server and you need to check its status in its role of media file system/metadata server, especially regarding redundancy. The recommended mode for local operation of a K2 Media Server is to use a connected keyboard, monitor, and mouse.
Administering and maintaining the K2 SAN qualified to take control of the K2 SAN. Be aware that the failover capabilities of the -K2 SAN are degraded until you place the machine back into service as the backup K2 Media Server. You should stop all media access before attempting this procedure. If media access is underway, there will be period of time in which media loss will occur. In the following procedures, K2server1 and K2server2 represent your redundant K2 Media Servers.
Administering and maintaining the K2 SAN 7. All failover processes are complete. All media management mechanisms are now running and K2server1 is now qualified and acting as the backup. Related Topics Powering on the K2 SAN on page 238 Working with K2 Media Servers Use the procedures in this section when doing configuration or service work on a K2 Media Server that is part of an operational K2 SAN.
Administering and maintaining the K2 SAN 4. Identify the K2 Media Server you intend to take out of service. If there are redundant K2 Media Servers, consider that you might trigger a failover event. Use the Stop button in Server Control Panel as appropriate for the action that you want to take. 5. When you are sure that you understand the implications of taking the K2 Media Server out of service, click the Stop button for that server. 6.
Administering and maintaining the K2 SAN On a system with this configuration of media file system/metadata K2 Media Servers… With server(s) in this state… When you click the Stop button on this server… One (non-redundant) server The server is in service Primary (the only server) The following behavior occurs. The media file system services stop, but the server continues to run. It does not automatically shut down. The server is now out of service.
Administering and maintaining the K2 SAN Modifying K2 Media Server network settings Read the following sections for considerations and procedures for modifying network settings on a K2 Media Server. Whenever you modify control network settings or FTP/streaming network settings on any device, you must then redeploy the hosts file if that is your name resolution mechanism.
Administering and maintaining the K2 SAN 9. In K2Config, add each iSCSI client again and reconfigure. Make sure you add them in the correct order (highest bandwidth first) and enter the same bandwidth values (load balancing) for each client as the values originally configured. 10. Place the devices of the K2 SAN back online. Configuring Server 2008 for domain This topic applies to Grass Valley servers with a base disk image created prior to mid-2011.
Administering and maintaining the K2 SAN 3. At the bottom of the Overview section, click Windows Firewall Properties. The Properties dialog box opens. 4. 5. 6. 7. On the Domain Profile tab, set Firewall state to Off. On the Private Profile tab, set Firewall state to Off. On the Public Profile tab, set Firewall state to Off. Click OK to save settings and close.
Administering and maintaining the K2 SAN rather than by the enumeration assigned by the Windows operating system and verify or modify the adapter name as necessary. 1. If not already open, open Network Connections as follows: a) Open the Windows Network and Sharing Center control panel. b) Click Change Adapter Settings. Network Connections opens. 2.
Administering and maintaining the K2 SAN 4.
Administering and maintaining the K2 SAN • The team and loopback are named 1. If not already open, open Network Connections as follows: a) Open the Windows Network and Sharing Center control panel. b) Click Change Adapter Settings. Network Connections opens. 2. Select Advanced, then Advanced Settings… 3.
Administering and maintaining the K2 SAN Configure static IP address on Server 2008 This task required on systems with Microsoft Windows Server 2008 operating system only. SiteConfig cannot discover systems with the Microsoft Windows Server 2008 operating system that have no IP address, such as those that are configured for DHCP. Therefore you must configure the system with a static IP address. You can use any IP address.
Administering and maintaining the K2 SAN 5. If the server hosts an iSCSI interface adapter, in the K2Config application, remove the K2 clients and other iSCSI clients that use the faulty server as their iSCSI target, as determined earlier in this procedure. 6. Stop all media access and power down all K2 clients and other iSCSI clients. 7. If the faulty server is a media file system/metadata server, take the K2 Media Server out of service.
Administering and maintaining the K2 SAN Replacing an iSCSI interface adapter (TOE card) Prerequisites are as follows: • The K2 SAN must be at K2 system software version 3.2.7 or higher before you begin this procedure. • K2 system software version must be the same on all K2 Media Servers, before and after you replace the iSCSI interface adapter or adapters.
Administering and maintaining the K2 SAN 13. Place the devices of the K2 SAN back online. Installing the Fibre Channel card driver When you restore a K2 Media Server from the generic disk image, the 8Gb Fibre Channel card driver is not on the disk image. After restoring the disk image, you must install the Fibre Channel card driver as instructed in this procedure. 1. After restoring the disk image and restarting the K2 Media Server, a Found New Hardware wizard opens.
Administering and maintaining the K2 SAN 8. Select Yes. The K2 Media Server restarts as normal. When startup completes, normal operation is restored. Checking K2 Media Server services The following table specifies the startup type of services for the different K2 Media Server roles. Depending on a K2 Media Server's roles, some services have different startup types. Unless otherwise noted, services with startup type Automatic are started, while services with startup type Manual or Disabled are not started.
Administering and maintaining the K2 SAN Service SNFS file system server iSCSI bridge Metadata server FTP server NAS server Grass Valley Performance Status Maker Manual Manual Manual Manual Manual Grass Valley SabreToothWS Manual Manual Manual Manual Manual Grass Valley Server Monitor Automatic Automatic Automatic Automatic Automatic Grass Valley SNFS SetRtio Automatic Automatic Automatic Automatic Automatic Grass Valley Storage Utility Host Automatic Automatic Automatic A
Administering and maintaining the K2 SAN operations such as changing the System Processor card, you must obtain a new license based on the new MAC address. Use these procedures to license a K2 Media Server for your K2 SAN as designed by Grass Valley. Consult with Grass Valley before attempting to add a license to an existing K2 SAN. To license a K2 SAN, the license must be installed on the K2 Media Server with role of file system server.
Administering and maintaining the K2 SAN 7. Do one of the following: • Attach the License Request text file to an email. • Paste the text directly into an email message. You might want to keep a copy of the message for your records. 8. Send the email as instructed by the License Request Wizard. An email will be sent from Grass Valley to the return email address you specified; your SabreTooth software license will be provided as a text file. 9. Save this email in case you ever need to re-image this machine.
Administering and maintaining the K2 SAN Deleting licenses Deleting a license disables the feature that it enabled. You might want to delete a temporary license prior to its expiry if you have decided not to purchase the feature. You can delete a temporary license after the permanent license has been installed without disabling the licensed product. 1. Select the license in the SabreTooth License Manager. 2. Use the Delete key on your keyboard or right click with your mouse and select Delete.
Administering and maintaining the K2 SAN Shutting down or restarting a K2 client Prerequisites are as follows: • Stop all media access on the K2 client. Your options for shutting down a K2 client are as follows: • Do a local shutdown/restart via AppCenter. Assuming a keyboard, monitor, and mouse is connected to the local K2 client, in AppCenter select System | Shutdown, then select Shutdown or Restart and OK. AppCenter exits, Windows shuts down and powers off the K2 client.
Administering and maintaining the K2 SAN • The K2 client must be connected to appropriate networks and be powered up. 1. In SiteConfig, add the K2 client to the SAN as follows: a) In the Network Configuration tree view, add the client as a placeholder device next to existing clients. b) Discover devices. c) Identify the K2 client you are adding. d) Assign the discovered K2 client to placeholder K2 client. e) Verify that networks are assigned and planned network interface settings applied. 2.
Administering and maintaining the K2 SAN Whenever you modify control network settings or FTP/streaming network settings on any device, you must then redeploy the hosts file if that is your name resolution mechanism. 1. Make sure you know the load balancing (bandwidth) parameters currently set for the K2 client in the K2Config application. You must reconfigure these parameters later in this procedure. 2. In SiteConfig, remove the K2 client. 3.
Administering and maintaining the K2 SAN This task required a restart. You can use the K2Config application to configure multicast settings on all the K2 Summit systems attached to a K2 SAN. Refer to related topics in "K2 System Guide" for live streaming technical details. 1. On the PC that hosts K2Config, open the K2Config application. A log on dialog box opens. 2. Log on to the K2Config application with the administrator account. The K2Config application opens. 3.
Administering and maintaining the K2 SAN 6. Select the multicast port base. This is the first UDP port address for elementary streams. 7. Click Apply Multicast Base to apply the settings. 8. When prompted, confirm your change and the restart of the K2 Summit systems. The multicast settings are applied to all K2 Summit system attached to the K2 SAN.
Administering and maintaining the K2 SAN Overview of Storage Utility The Storage Utility user interface includes a tree view in the left-hand pane, and a status information area displayed in the right-hand pane. The tree view displays the hardware that make up the RAID storage system. The context menus in the tree view are used to configure storage. The right-hand status pane displays information about the item selected in the tree view.
Administering and maintaining the K2 SAN Checking the media file system Prerequisites are as follows: • You must access Storage Utility (via the K2Config application login) with permissions equivalent to K2 administrator or higher. • When you access Storage Utility, the K2 SAN must be offline. • All iSCSI clients and K2 clients in the K2 SAN must be offline. • K2 Media Servers with role of file system/metadata server, both primary and redundant, must be powered up but offline.
Administering and maintaining the K2 SAN • K2 Media Servers with role of file system/metadata server, both primary and redundant, must be powered up but online. These procedures allow you to keep the media database and the media files in sync. You can check the movies (clips) in the media database for the references to media files that should be currently stored on the media disks. Likewise, you can check for media files that are not referenced by a movie in the media database.
Administering and maintaining the K2 SAN 3. In Storage Utility, click Tools | Make New File System. The Setting dialog box opens. 4. For the Real Time Input/Output (RTIO) rate, enter the value specified by your system design. If you do not know this value, contact your Grass Valley representative. 5. Configure Windows Security as follows: • If the K2 SAN is on a network Workgroup (not domain), do not select Windows Security . • If the K2 SAN is on a network domain, you may select Windows Security.
Administering and maintaining the K2 SAN 6. Click OK. The Configuration File dialog box opens. The configuration file for the media file system is displayed. 7. Verify media file system parameters. Do not edit the configuration file for the media file system. 8. Click Accept. A “…Please wait…” message box displays progress and a “…succeeded…” message confirms the process is complete. 9. Restart the K2 Media Server. 10. You now have a blank (empty) file system. Proceed as follows: • On a 7.
Administering and maintaining the K2 SAN 11. Close Storage Utility. 12. If you have Macintosh systems accessing the K2 SAN, you should check that the SNFS file system volume is configured correctly on the Macintosh systems. 13. Place the K2 SAN back online. Expanding the media file system by capacity Prerequisites are as follows: • The system must have one LUN per RANK. Expansion by capacity is not supported on systems with multiple LUNs per RANK.
Administering and maintaining the K2 SAN 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.
Administering and maintaining the K2 SAN 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.
Administering and maintaining the K2 SAN 8. From the control point PC, open the K2Config application and launch Storage Utility. Make sure that versions are correct and consistent on both new and existing RAID storage devices. 9. Verify versions of controller microcode and disk firmware. Update if necessary. Make sure that versions are compatible on both new and existing disks and RAID storage devices. 10. Bind RANKs using the new disks. Wait for the binding process to complete.
Administering and maintaining the K2 SAN 6. A dialog box opens asking if you want to restripe existing media after bandwidth expansion. Proceed as follows: • Click Yes in most cases. This is the typical response. In any case this does no harm. • Click No only if you are sure you do not need to restripe existing media, such as in the following cases: • You have very little existing media so the fact that it cannot use the new stripe group does not impact future media operations or capacity.
Administering and maintaining the K2 SAN 14. In the K2Config application, do the following for each K2 Media Server with role of iSCSI bridge to verify that you see the correct number of drives: a) On the iSCSI Bridge Server Configuration page, click View Target Drives and proceed as follows: • If you see all drives, both old and new, no further sub-steps are necessary. Skip to the next step in this procedure. • If some drives are listed as unexposed, continue with the remaining sub-steps in this step.
Administering and maintaining the K2 SAN 2. You can start and stop the Restripe Utility manually as follows: • At any time while the Restripe Utility is in the process of restriping clips, you can right-click the icon in the system tray, and select Abort. This stops the restripe process and closes the Restripe Utility. NOTE: Stopping the Restripe Utility before it completes its processes leaves some of your existing media still striped across the original narrower stripe group.
Administering and maintaining the K2 SAN 4. Stop the Grass Valley MetaDataService as follows: • If a stand-alone K2 system, use the Services control panel to stop the service. • If a K2 SAN, use Server Control Panel to stop the service on primary, and if present, backup K2 Media Server with role of file system server. 5. Determine which backup file is the most recent good file by examining the file modification date on each backup file. 6. Rename the current media.
Administering and maintaining the K2 SAN Item in tree view Status information displayed RANK Binding Type, such as RAID 1 State (online or offline) Number of Logical Units Disk Firmware Vendor State Product ID Capacity Unbound Number of disks Checking controller microcode As explained in the previous section, to check controller microcode, in Storage Utility select the controller in the tree view and the microcode version is displayed.
Administering and maintaining the K2 SAN Chassis Disk numbering Expansion 3 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 Disk numbering for 3.5 inch disks In Storage Utility, RAID disks are numbered with a hexadecimal convention. Disk modules are identified based on the chassis address and physical location as follows: Chassis...
Administering and maintaining the K2 SAN Flashing disk LEDs Storage Utility’s Identify feature allows you to flash the disk LEDs so that you can physically locate a specific disk module or group of disk modules that make up a RANK. Always use the disk identify feature before removing and replacing a failed disk module. Accidentally removing the wrong disk module can destroy data. 1. Open Storage Utility and in the tree view expand all nodes so that all disks are displayed. 2.
Administering and maintaining the K2 SAN Unbind RANK Prerequisites are as follows: • You must access Storage Utility (via the K2Config application login) with permissions equivalent to K2 administrator or higher. • All iSCSI clients and K2 clients in the K2 SAN must be shut down. Unbinding reverses the bind process. Unbinding might be needed when reconfiguring a SAN. CAUTION: Unbinding destroys all data stored on disk modules 1. In the tree view, right-click the RANK and select Unbind. 2.
Administering and maintaining the K2 SAN About full/background bind When binding RAID disks, you can choose to do either a full bind or a background bind. Background bind is recommended. These binding processes are described as follows: • Full bind — During this process, the K2 SAN must be in the offline mode. While the full bind process is underway, disks are not available for data access of any kind. On a large SAN, the full bind process can take many hours, so you should plan ahead for this process.
Administering and maintaining the K2 SAN For simplicity, the Storage Utility only allows binding the first available (at the top of the Available Disks list) contiguous disk modules into RANKs. After binding, disk modules become slot specific and cannot be moved to other disk module slots. 1. In the tree view, right-click the Unbound node and select Bind. (Peer controllers that share the same set of disks are automatically selected as a pair.
Administering and maintaining the K2 SAN Binding Hot Spare drives Prerequisites are as follows: • You must access Storage Utility (via the K2 System Configuration application login) with permissions equivalent to K2 administrator or higher. • When you access Storage Utility, the K2 SAN must be offline. • All iSCSI clients and K2 clients in the K2 SAN must be shut down. You can bind disks as hot spare drives. Hot spare drives are on standby and are used in the event of a drive failure in a RANK.
Administering and maintaining the K2 SAN 2. In Storage Utility, right-click a controller in the tree view, then do one of the following: • To load controller microcode select Advanced | Load Controller Microcode • To load expansion chassis microcode select Advanced | Load Disk Enclosure Microcode Redundant controllers that share the same set of disks are automatically selected and upgraded as a pair. The Login Information dialog box opens. 3.
Administering and maintaining the K2 SAN 4. Work through the wizard as follows: a) At each wizard page, read messages in the center window to follow progress and wait until the green indicator verifies that operations are complete. Then click Next to proceed. b) When prompted, browse to and select the folder that contains the controller microcode. c) When waiting for the controller to reboot, proceed after a "Controller...back online" message is displayed in the center window.
Administering and maintaining the K2 SAN 3. In the Open File dialog box, browse to the desired firmware file for your disks, select the file, and click OK. As instructed by a message that appears, watch the lights on the drives. For each drive, one at a time, the lights flash as firmware loads. Wait until the lights on all the drives on which you are downloading firmware have completed their flashing pattern. This can take several minutes.
Administering and maintaining the K2 SAN 5. On inserting the replacement RAID controller, it initializes and is automatically enabled to become the “backup” RAID controller. Related Topics Identifying disks on page 315 Replacing a K2 10Gv2 RAID controller The K2 10Gv2 RAID controller must be connected to the control network to support the operations in this topic. If the RAID chassis has a single controller (non-redundant), you must take the K2 SAN offline before replacing a failed controller.
Administering and maintaining the K2 SAN 3. Select the controller and check its status, then proceed as follows: • If the faulty controller reports as disabled, proceed to the next step in this procedure. • If the faulty controller reports as online, right-click the controller icon in the tree view, and select Advanced | Disable Controller 0 or Disable Controller 1, then click OK to continue. The Login Information dialog box opens. 4.
Administering and maintaining the K2 SAN Network and SNMP settings are set and stored on the RAID controller. Therefore, if the RAID chassis has two controllers, each controller must be configured separately, as in the following procedure. 1. In the K2Config application tree view, open the node for a K2 Media Server and select the File System Server node to open its property page. On the property page click Launch Storage Utility. Storage Utility opens.
Administering and maintaining the K2 SAN Replacing a controller If the RAID chassis has a single controller (non-redundant), you must take the K2 SAN offline before replacing a failed controller. Refer to procedures in the Instruction Manual for your RAID storage chassis. The remainder of this procedure does not apply to non-redundant systems.
Administering and maintaining the K2 SAN Design considerations for Ethernet switches The following information was qualified using the HP ProCurve switch. You must use the HP ProCurve switch for iSCSI traffic. However, for control and FTP/streaming traffic, it is allowed to use a different brand of switch, such as a Cisco Catalyst switch, if required by your site. If you are using a non-HP switch, apply the information accordingly. Refer to the documentation you received with the switch as necessary.
Administering and maintaining the K2 SAN Based on these factors, determine the number of switches, the number of ports on each switch, and the ISLs required for your system needs. You can find procedures for configuring the HP ProCurve switch in the chapters elsewhere in this manual for installing each level. Adapt the procedures according to your switch design as you configure your switches.
Administering and maintaining the K2 SAN 4. Check the version of firmware on the switch. To do this, type the following, then press Enter: show flash Information is displayed similar to the following example: HP_iSCSI_switch1# show flash Image Size(Bytes) Date -------------- -------Primary Image : 6737518 07/25/08 Secondary Image : 5886358 10/26/06 Boot Rom Version: K.12.12 Current Boot : Primary Version ------T.13.23 T.11.12 5.
Administering and maintaining the K2 SAN 2. If you have not already done so, telnet to the switch and login with the administrator username and password. 3. At the switch console command (CLI) prompt, type the following and then press Enter: configure You are now in configuration mode. 4. Set spanning tree to RSTP. To do this, type the following, then press Enter: spanning-tree force-version rstp-operation This configures spanning tree, but it does not turn spanning tree on.
Administering and maintaining the K2 SAN 4. In the switch’s configuration application, choose Configuration, then Device Features. 5. Set Spanning Tree to On and click Apply Changes. If prompted, log in with the switch’s administrator username and password. 6. Close the switch configuration application. 7. Restart the switch to put changes into effect. Upgrading firmware on HP switch 1. If you have not already done so, install a TFTP Server. For example, to install tftpd32.exe, go to http://tftpd32.
Administering and maintaining the K2 SAN 6. Wait until the CLI prompt re-appears, then continue with the next step in this procedure. 7. Check the version of firmware on the switch. To do this, type the following, then press Enter: show flash Information is displayed similar to the following example: HP_iSCSI_switch1# show flash Image Size(Bytes) Date -------------- -------Primary Image : 6737518 07/25/08 Secondary Image : 5886358 10/26/06 Boot Rom Version: K.12.12 Current Boot : Primary Version ------T.
Custom K2 SAN systems About custom K2 SAN systems Custom systems extend the infrastructure of standard K2 SAN product bundles. For example, a custom K2 SAN has multiple primary RAID chassis connecting to K2 Media Servers via a Fibre Channel fabric consisting of one or more Fibre Channel switches. This is an extension of the Fibre Channel infrastructure of a standard K2 SAN, which has a single primary RAID chassis connecting to one or more K2 Media Servers via direct Fibre Channel connection.
Custom K2 SAN systems iSCSI extended (redundant FSMs) Control Point PC FSM/Bridge K2 Media Servers K2 MEDIA SERVER FTP/Bridge K2 Media Servers K2 MEDIA SERVER K2 MEDIA SERVER K2 SAN-attached client systems K2 MEDIA SERVER K2 ! K2 MEDIA SERVER K2 MEDIA SERVER ! MEDIA SERVER ! iSCSI iSCSI iSCSI iSCSI iSCSI iSCSI iSCSI GigE Fabric Key to illustrated cable paths: Gigabit Ethernet carrying real-time media Fibre Channel carrying real-time media Gigabit Ethernet carrying traffic that is not rea
Custom K2 SAN systems Fibre Channel connected clients (redundant FSMs) Control Point PC K2 Media Servers K2 MEDIA SERVER K2 MEDIA SERVER K2 SAN-attached client systems K2 MEDIA SERVER K2 K2 MEDIA SERVER ! ! K2 MEDIA SERVER MEDIA SERVER ! GigE Fabric Key to illustrated cable paths: Fibre Channel carrying real-time media Gigabit Ethernet carrying traffic that is not real-time media Fibre Channel Fabric A black/gray pair denotes redundant cables K2 RAID STORAGE ! POWER SERVICE K2 RAID STOR
Custom K2 SAN systems Explanations and procedures The following information might or might not apply to your particular custom system. Make sure you understand the application of the information to your own custom system. General guidelines The following guidelines apply to all systems: • • • • Update to version 3.0.1.21 or higher before attempting to configure a custom system. When you change the RTIOS, you must reboot the system for it to take effect.
Custom K2 SAN systems configuration must therefore be at the K2 Client/K2 Server level. For example, in a L3 redundant system, K2 clients can connect to either of a redundant K2 Server pair. This means that if K2 Server 1A goes down, K2 Clients connect to K2 Server 1B. FC port redundant NOTE: Do not use the FC port redundant configuration without first consulting with Grass Valley Server Engineering. Two K2 Servers each connect to two RAID controllers. Servers A and B are redundant.
Custom K2 SAN systems Uninstalling SANsurfer Switch Manager software When uninstalling the software, use the QLogic uninstall program in Program Files. NOTE: Do not attempt to use Windows Control Panel Add/Remove Programs to uninstall SANsurfer Switch Manager. The UninstallerData folder in the Install directory contains the uninstall program. Also, a shortcut/link to the uninstall program was installed in the installation directory during the SANsurfer Switch Manager installation process.
Custom K2 SAN systems 2. Open the Switch menu and select Switch Properties. The Switch Properties dialog box opens. 3. Set Domain ID to 1. 4. Set Domain ID lock to Enable. 5. Click OK. SANsurfer Switch Manager updates the switch. When a message box reports status complete, click OK. The Switch Properties dialog box closes. 6. Open the Zoning menu, and select Edit Zoning to open the Edit Zoning dialog.
Custom K2 SAN systems 7. Open the Edit menu, and select Create Zone Set to open the Create A Zone Set dialog. 8. Enter ZoneSetA as the name for the zone set, and click the OK button. The new zone set name is displayed in the Zone Sets tree. A zone set name must begin with a letter and be no longer than 64 characters. Valid characters are 0-9, A-Z, a-z, _, -, ^, and $. 9. Right-click ZoneSetA and select Create A Zone from the popup menu. 10.
Custom K2 SAN systems 12. In the Create a Zone dialog, enter Zone2 as the name for the new zone, and click the OK button. The new zone name is displayed in the Zone Sets tree. 13. Click the Apply button. In the Save Zoning & Error Check dialog, click Save Zoning, then Yes, OK, and Close on subsequent message boxes. You can ignore a "Error activating zone set" message. 14. When a zone is created, its zone type is soft.
Custom K2 SAN systems 18. Click the Apply button. In the Save Zoning & Error Check dialog, click Save Zoning, then Yes, OK, and Close on to save changes to the zoning database. 19. Close the Edit Zoning dialog box. 20. Connect to the other switch as necessary to configure. In SANsurfer Switch Manager, expand the tree view and select the other Fibre Channel switch. For the purposes of this procedure, this switch is designated as switch B. The Faceplate display opens. 21.
Custom K2 SAN systems 33. When a zone is created, its zone type is soft. For Zone3 and Zone4, change the zone type to a hard zone as follows: a) In the Zone Sets tree, right-click the zone and select Set Zone Type from the popup menu. b) In the Set Zone Type dialog, open the Zone Type pull-down menu and select ACL, then click the OK button. c) Repeat steps for the other zone. 34.
Custom K2 SAN systems • Each K2 RAID storage chassis is connected to all four zones. For example, connect RAID chassis 1 as follows: • • • • Connect controller 0 port HP0 to switch A port 1 (Zone 1) Connect controller 0 port HP1 to switch A port 9 (Zone 2) Connect controller 1 port HP0 to switch B port 1 (Zone 3) Connect controller 1 port HP1 to switch B port 9 (Zone 4) Connect RAID chassis 2, 3, and 4 similarly.
Index A Acronis, See recovery adapters identifying 284 naming 285 reordering 286 administrative share on SiteConfig control point PC 70 B backup, See recovery bandwidth about iSCSI 223 determining K2 client iSCSI 223 basic nearline K2 SANs configuring 181, 184, 202 configuring file system servers 190, 197, 208, 215 configuring FTP servers 198 configuring networks 144, 178, 189, 207, 219 configuring server roles 187, 205, 217 configuring servers 186, 197 configuring software 188 defining 124, 148, 182, 200
Index connect kit SiteConfig 71 control network SiteConfig 74 control networks descriptions 39 control point PCs accessing K2 SANs from multiple PCs 273 description 251 installing SiteConfig 70 powering on 243 setting up 69 system requirements 70 controllers replacing 325 custom K2 SANs 335 D database servers configuring basic online and production 140 configuring redundant online and production 166 configuring redundant online and production server B 173 databases configuring K2 clients on SANs 230 recov
Index F failover recovering 278 triggering 277 failover behaviors 244 control team 245, 247 K2 Media Server 248 K2 Media Server with control team 249 media (iSCSI) 245, 247 pre-failover 244 features K2 SANs 30 new 30 Fibre Channel address ID 53 SiteConfig 93 fabric cabling 345 installing driver 291 K2 client connections 337 port redundant configuration 338 switch manager software 339 switch zones 340 file system clients configuring K2 clients on SANs 233 file system servers configuring basic nearline K2 SA
Index installing SiteConfig system requirements 70 iSCSI about bandwidth 223 configuring basic online and production bridges 139 configuring initiator for K2 clients on SANs 231 configuring redundant online and production bridges 165 configuring redundant online and production server B bridges 172 determining K2 client bandwidth 223 media (iSCSI) network descriptions 40 replacing interface adapter 290 viewing assignments 274 iSCSI network SiteConfig 78 J java 70 K K2 client SiteConfig support 87 K2 clien
Index K2 System Configuration, See K2Config K2Config about 258 and SiteConfig settings 267 opening 259 synchronizing with STRATUS Control Panel 269 L LEDs flashing RAID 317 Level 40 335 licenses verify on servers 224 licensing adding 295 archiving 296 deleting 296 difficulties 295 K2 SANs 121 requesting 294 live streaming configure multicast 299 login SiteConfig 266 logs RAID controller 317 LUNs in Storage Utility 262 M mapped network drive on SiteConfig control point PC 70 McAfee, See embedded security
Index networks (continued) modifying K2 Media Server control network settings 282 modifying K2 Media Server FTP network settings 282 modifying K2 Media Server media network settings 282 modifying media network settings on K2 client 299 restoring configuration on K2 Media Server 284 streaming/FTP network descriptions 40 tips 41 NH K2 Media Servers descriptions 254 specifications 255 NH servers configuring redundant online and production 142, 175 NH10GE servers cable redundant nearline 52 cable basic nearlin
Index RAID (continued) configuring networks and SNMP redundant nearline 155, 208 configuring networks and SNMP redundant online and production 155, 208 configuring redundant nearline 131, 155, 190, 208 configuring redundant online and production 131, 155, 190, 208 controller logs 317 descriptions 255 identifying disks 315 loading controller microcode 321 loading disk firmware 323 replacing controller 325 replacing disk module 324 unbind RANK 318 See also K2 RAID RANKs in Storage Utility 262 recovery about
Index roles (continued) configuring redundant nearline K2 SANs 187, 205, 217 configuring redundant nearline server B 187, 205, 217 configuring redundant online and production K2 SANs 152, 168 configuring redundant online and production NH servers 142, 176 configuring redundant online and production server B 152, 168 routers and SiteConfig 70 RSTP settings on switches 331 S sales tool 73 SAN configurations checklists 39 security applications 266 embedded solution 118, 119 on K2 systems 265 serial cable pin
Index STRATUS (continued) Control Panel synchronizing with K2Config 269 streaming network SiteConfig 76 streaming/FTP networks descriptions 40 Summit, See K2 Summit switch See also Ethernet rack 47 See also Ethernet switch HP cable basic nearline 49 cable basic online or production 47 cable redundant nearline 49 cable redundant online or production 48 switches Ethernet and SiteConfig 70 system concepts 39 system descriptions K2 SAN 73 importing into SiteConfig 122 system diagram K2 SAN basic nearline 45 K2
Index 356 K2 Installation and Service Manual 2013 07 20
