Installing the Level 3R Storage System
Use this chapter to install the K2 Level 3 Redundant (L3R) storage system.
This chapter includes the following topics:
Work through these topics sequentially to install the storage system.
Level 3R system description
The level three redundant (Level 3R) storage system has four K2 media servers. They are configured as two redundant pairs. In this diagram, media servers 1A and 2A each take on a subset of the media server roles. For example, server 1A takes the roles of media file system server, database server, and iSCSI bridge, while server 2A takes the roles of FTP server, NAS server, and iSCSI bridge. The four media servers provide a total of four iSCSI media connections for increased bandwidth. Media server 1B is the redundant server to 1A. Media server 2B is the redundant server to 2B. In addition, the level three redundant storage system has one L3 RAID chassis. Up to five optional Expansion chassis are available for increased storage capacity.
K2 Media Clients have a teamed pair of Gigabit Ethernet ports for control and a teamed pair for media. Each port of a teamed pair is connected to a different switch. The GigE switches are configured with V-LANs to keep the control and media traffic separate.
Each K2 Media Server has two GigE connections for media, one GigE connection for control, one GigE connection for FTP, and one Fibre Channel connection to the RAID storage. The media server hosts iSCSI interface cards for the GigE media connections and a Fibre Channel card for the RAID storage connection. The iSCSI interface cards provide a bridge between GigE iSCSI and Fibre Channel SCSI. Each media server also runs the software components that allow it to function in its specific roles. Redundant K2 Media Servers with the role of media file system/database server are connected by a serial cable which suppports the heartbeat signal required for automatic system recovery (failover) features.
The L3 RAID chassis is connected via a Fibre Channel connection to each media server. The connections to media servers 1A and 2A access the disks simultaneously for increased bandwidth. Likewise the connections to media servers 1B and 2B access the disks simultaneously. In addtion, since the A connections and the B connections are redundant, at most two K2 Media Servers are active at any given time. Each controller in the L3 RAID chassis is also connected to the GigE control network, which is required for SNMP (NetCentral) monitoring.
Level 3 redundant systems have both RAID 1 and RAID 5 LUNs in the RAID storage. On the level 3 RAID chassis there are two RAID 1 LUNs for media file system metadata files and journal files. The remainder of the RAID storage is RAID 5 LUNs for media.
The K2 configuration control point PC is connected to the GigE control network. The K2 System Configuration application runs on this PC for configuring the storage system.
Refer to Description of K2 Storage Devices for more information.
Preparing level 3R devices
Use the topics in this section to prepare each device so that it is ready to become part of the level 3R storage system.
Setting up the control point PC
To set up the K2 configuration control point PC, you have the following options:
For either option, you must do the following for the control point PC that runs the K2 System Configuration application:
To use your own PC, you must additionally do the following:
- Verify that the PC that meets the following system requirements. You might have to install some supporting software:
- Install the Control Point software. Refer to Managing K2 software.
- Install and license NetCentral server software. You can install this on the the NetCentral server PC, which can be the K2 configuration control point PC. Refer to the NetCentral User Guide.
Also refer to Control point PC description.
Setting up the level 3R redundant GigE switches
These procedures are for the HP ProCurve switch. If you are using the Cisco Catalyst switch, make connections and settings to provide the same functionality. Refer to the documentation you received with the switch as necessary.
- Use CAT5 or higher cables. The maximum cable length is 50 meters.
- Assign an IP address and logon to each switch. Refer to Configuring the GigE switch via serial connection.
- Set up VLANs on each switch. Refer to Configuring the GigE switch VLANs.
- Install the switches in their permanent location.
- Provide power to the switches.
- Connect cables as follows:
To the media ports on switch A, make one media connection from each K2 Media Client or other iSCSI client, two media connections from media server 1A, and two media connections from media server 2A.To the media ports on switch B, make the second media connection from each K2 Media Client or other iSCSI client, two media connections from media server 1B, and two media connections from media server 2B.To the control ports on switch A, make one connection from each K2 Media Client or other iSCSI client, from media server 1A, from media server 2A, from RAID controller 0, and from the control point PC.To the control ports on switch B, make the second control connection from each K2 Media Client or other iSCSI client, from media server 1B, from RAID controller 1, and from media server 2B.Interconnect switch A and switch B with two 10 Gig ISLs.Refer to Level 3R system description for a diagram of the complete system.
Refer to cabling procedures later in this chapter for the GigE connections at each of the devices of the K2 Storage System.
Also refer to K2 Ethernet switch description.
Configuring the GigE switch via serial connection
For redundant systems with two switches, do the following on each switch.
Use a direct console connection to the switch, start a console session, and access the Switch Setup screen to set the IP address. The following procedure is for the HP ProCurve switch. If you have a Cisco switch, accomplish the same tasks as appropriate. Consult the documentation that came with the switch for more information.
- Configure the PC terminal emulator on the control point PC or another PC as a DEC VT-100 (ANSI) terminal or use a VT-100 terminal, and configure either one to operate with these settings:
- Connect the PC to the switch’s Console Port using the console cable included with the switch.
- Turn on the PC’s power and start the PC terminal program.
- Press Enter two or three times and you will see the copyright page and the message “Press any key to continue”. Press a key, and you will then see the switch console command (CLI) prompt.
- At the prompt, enter
setup
to display the Switch Setup screen.- Tab to the IP Config (DHCP/Bootp) field and use the Space bar to select the Manual option.
- Tab to the IP Address field and enter the switch’s control network IP address. Refer to Networking tips.
- Tab to the Subnet Mask field and enter the subnet mask used for your network.
- Press Enter, then right-arrow to Save. Press Enter again and revert to previous menu. If you are at the command (CLI) prompt, enter
menu
to go to the main menu screen.- From the main menu, choose Console Passwords and press Enter. The Set Password Menu opens.
- Chose Set Manager Password and press Enter.
- Enter a password. You can use the default K2 administrator password “K2admin” or your site’s password for administering the K2 Storage System.
- Return to the main menu
- Tab to Command Line (CLI) and press Enter. The command prompt appears.
- Type
configure
to change to configuration mode.- You now configure an administrator username. You can use the default K2 administrator username “K2admin” or your site’s username for administering the K2 Storage System. For example, to set the username to “K2admin” type the following:
- When prompted for the password, enter a password. You can use the default K2 password “K2admin” or your site’s password for administering the K2 Storage System.
- Decide your SNMP community name as explained in the following options, then proceed with the next step:
snmp-server community K2 unrestricted
This allows NetCentral to test the switch to verify that it can send its SNMP trap messages to NetCentral.
- Type
menu
to get to menu mode.- If you need trunks to gang switches together using 1 Gig connections, do the following (Note: This is not required if you use the 10 Gig ISL connections):
- Select Switch Configuration.
- Choose selection 2, Port/Trunk Settings.
- Press the right-arrow key to choose Edit, then press Enter.
- Down arrow until at the bottom of the list of ports.
- Right-arrow over to the Group column.
- Use the Space bar and set the bottom port to Trk1.
- Set the next port up also to Trk1.
- Press Enter, then right-arrow to Save. Press Enter again and revert to previous menu. If you are at the command (CLI) prompt, enter
menu
to go to the main menu screen.- Choose Reboot Switch to restart the switch.
- You can now use the switch’s web browser interface for further configuration, as instructed in the next procedure.
- Close the PC terminal program and disconnect the console cable.
- Repeat this procedure on the other switch.
Continue with the next procedure Configuring the GigE switch VLANs.
Configuring the GigE switch VLANs
For redundant systems with two switches, do the following on each switch.
The following steps are for the HP ProCurve switch. Accomplish tasks similarly on a Cisco switch.
- From the control point PC or another PC, make sure that you have a direct Ethernet cable connection to the switch, with no other switches or networking devices in between.
- On the PC, open Internet Explorer and type the switch’s IP address in the Address field, as in the following example.
This should be the name or IP address as currently configured on the switch.- Press Enter to open the switch’s configuration application.
NOTE: The configuration application for the HP ProCurve switch requires Java.
You can also access the switch’s configuration application from the K2 System Configuration application.- In the switch’s configuration application, choose Configuration, then Port Configuration.
- Select all ports, leave Mode as default of Auto and set Flow Control to Enable.
- Choose VLAN Configuration. If prompted, log in with the switch’s administrator username and password.
- Create a new Media (iSCSI) VLAN as follows:
- Configure the Media VLAN as follows:
- In the Media VLAN row, click Modify.
- Select all the odd numbered ports. (Tip: Use Ctrl + Click.)
- In the Mode drop-down list, select Untagged, then click Apply. This removes the odd ports from the default (Control) VLAN.
- In the Current Mode list box, scroll down and select the trunks.
- In the Mode drop-down list, select Tagged, then click Apply. This allows the trunks to carry traffic from either VLAN.
- Click the VLAN Configuration tab.
- Configure the default (Control) VLAN as follows:
- On the VLAN Configuration page, verify that for both VLANS the trunks are displayed in the Tagged Ports column.
- Repeat this procedure for the other Ethernet switch.
- Close the switch configuration application.
Setting up the K2 media server
Do the following to prepare each K2 media server:
- Install the server in its permanent location. Refer to the rack mount instructions that you received with the server’s product bundle.
- Provide power to the servers.
- Connect cables as follows:
Connect the two iSCSI interface adapters to media ports on the GigE switch.Connect the motherboard GigE port 1 and GigE port 2 to control ports on the GigE switch.Connect one of the Fibre Channel ports to the RAID storage device.Make a direct connection between the serial ports of redundant server pairs. Connect server 1A to server 1B, and connect server 2A to server 2B.- Assign a control network IP address to GigE port 1. Use standard Windows procedures. Refer to Networking tips.
- Configure SNMP properties so the trap destination points to the NetCentral server PC. If you are not using the SNMP community name “public”, configure the community name and set permissions to RW. Also make sure that the Authentication trap is enabled.
Also refer to K2 Media Server description.
Setting up the L3 RAID chassis
Do the following to prepare the L3 RAID storage devices:
In addition, you will configure network settings, SNMP settings, and bind LUNs. These tasks are part of the K2 System Configuration application and Storage Utility procedures later in this chapter. The process of binding LUNs can take a significant amount of time—as much as eight hours—so you might want to put priority on the tasks necessary to start the LUN binding process, then catch up with other tasks while the LUNs are binding.
Also refer to K2 Level 3 RAID storage description.
Assign Fibre Channel address ID
Every RAID controller must have a unique Fibre Channel address ID that identifies the controller on the Fibre Channel fabric. On the L3 RAID, you do not need to manually set the Fibre Channel address ID, as it is pre-set at the factory.
Connect the L3 RAID chassis
If you have one or two expansion chassis, connect RAID storage for a level 3 redundant system as follows:
If you have three or more expansion chassis, connect RAID storage for a level 3 redundant system as follows:
Connect Ethernet cabling as shown in the following diagram.
Assign chassis address on optional Expansion chassis
Every chassis must have a chassis address. The level three RAID chassis address is fixed at 0, so no configuration is required. However, if you have any L3 RAID Expansion chassis you must set their chassis addresses as shown in the following illustration. Also verify that the diagnostic ID switches are in the position shown.
Power on the L3 RAID chassis
Your preparations for L3 RAID storage are now complete.
Preparing K2 Storage System clients
Any devices that function as iSCSI clients to the K2 Storage System must be prepared with the following requirements:
Additional steps that are required for NewsEdits include the following:
For more information, refer to the NewsShare Technical Reference Guide.
Additional steps that are required for K2 Media Clients include the following:
For more information refer to the K2 Media Client System Guide.
Preparing K2 Media Clients
Do the following to each K2 Media Client in preparation for its addition to the K2 Storage System:
- Install the K2 Media Client in its permanent location.
- Provide power to the K2 Media Client.
- Connect cables as follows:
Connect GigE port 1 to a control port on the K2 Ethernet switch. For a redundant connection connect GigE ports 1 and 3 to control ports on the K2 Ethernet switch.Connect GigE port 2 to a media port on the K2 Ethernet switch. For a redundant connection connect GigE ports 2 and 4 to media ports on the K2 Ethernet switch.NOTE: The connections to GigE ports 2 and 4 documented here are only valid for external storage K2 Media Clients that access shared storage on a K2 Storage System. To connect GigE ports 2 and 4 on internal storage K2 Media Clients, refer to the K2 Media Client System Guide.
- Power on the K2 Media Client and log on to Windows as Windows adminstrator, which is username administrator and password adminK2 by default. Ignore startup messages referring to a missing media storage system.
- Assign a control network IP address and configure other network settings for the K2 Media Client. Refer to the networking section later in this chapter for networking information. Ports 1 and 3 are teamed, so even if are making a connection to port 1 only, you must configure network settings for the Control Team, as follows:
- On the Windows desktop, right-click My Network Places and select Properties. The Network Connections window opens.
- Look in the Device Name column and identify the entry named TEAM : Control Team.
- Right-click the icon for this entry and select Properties. The Properties dialog box opens.
- On the General tab select Internet Protocol (TCP/IP) and click the Properties button. The Internet Protocol (TCP/IP) Properties dialog box opens.
- Configure network settings as appropriate for the control network as implemented in your facility.
- Configure SNMP properties so the trap destination points to the NetCentral server PC. Use standard Windows procedures.
- If the K2 Media Client connects to the K2 Storage System with a redundant Ethernet fabric, such as in levels 2R and 3R, install Multi-Path I/O software. Refer to the next procedure Installing Multi-Path I/O Software.
- Copy the K2 Storage System hosts file onto the K2 Media Client. Refer to the networking sections later in this chapter for information about the hosts file and networking.
Installing Multi-Path I/O Software
The following procedure is required for external storage K2 Media Clients that have both Gigabit Media ports (ports 2 and 4) connected to the iSCSI Media network. Typically, this configuration is used for redundant K2 Storage Systems, such as Level 2R and Level 3R.
The installation files for the Multi-Path I/O software are copied on to the K2 Media Client when the K2 Client software is installed.
To install Multi-Path I/O software, do the following:
- If you have not already done so, connect keyboard, monitor, and mouse to the K2 Media Client and log on to Windows.
- Stop all media access. If AppCenter is open, close it.
- Click Start | Run, type
cmd
and press Enter. The MS-DOS command prompt window opens.- From the command prompt, navigate to the C:\profile\mpio directory.
- Type the following at the command prompt:
C:\profile\mpio>gdsminstall.exe -i c:\profile\mpio gdsm.inf Root\GDSM- Press Enter. The software is installed. The command prompt window reports the following:
- Restart the K2 Media Client.
- 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.
- In the left pane select Device Manager.
- In the right pane open the System devices node and verify that GVG ISCSI Multi-Path Device Specific Module is listed.
Sending K2 configuration to NetCentral
As you configure the K2 Storage System, information is automatically sent to NetCentral. When NetCentral receives the information it adds devices and populates its interface with a view of the K2 Storage System.
Before you begin using the K2 System Configuration application to configure the storage system, you must set up the NetCentral system according to the following requirements:
- NetCentral installed — NetCentral server software must be installed on a NetCentral server PC. This can be the K2 configuration control point PC or another PC that has network communication with the K2 Storage System control network.
- Device providers installed — A device provider must be installed on the NetCentral server PC for each type of device in the K2 Storage System. For a level 3R storage system, the following device providers must be installed:
- Control point PC device provider — This is the Windows monitoring device provider.
- K2 Media Server device provider
- HP Gigabit Switch device provider or Cisco Gigabit Switch device provider
- K2 Media Client device provider, if any K2 Media Clients are accessing the level 3R storage system.
- Device provider for iSCSI clients, if any iSCSI clients such as NewsEdits are accessing the level 3R storage system.
- K2 Level 3 RAID storage device provider
- Grass Valley PC Monitoring software installed — This software must be installed on the K2 configuration control point PC. It includes Grass Valley SNMP agents and other WMI based components to perform process monitoring. This provides the information for some of the SNMP trap messages that must be sent to NetCentral.
- Control point PC monitored by NetCentral — The K2 configuration control point PC must be added to the NetCentral system and fully monitored by NetCentral. This especially means that its SNMP trap destination is set to send SNMP traps to the NetCentral server PC. This is critical, as a SNMP trap is used as the mechanism by which the K2 configuration information is communicated to NetCentral. Whether the control point PC and the NetCentral server PC are the same PC or are different PCs, you must still add the control point PC to NetCentral.
In addition, NetCentral automatically changes its view of the K2 Storage System whenever you use the K2 System Configuration application to do one of the following:
Refer to the NetCentral User Guide to set up the NetCentral system. After installing a device provider, you can find additional documentation about monitoring that type of device on the NetCentral Help menu.
Networking for level 3R
Use the topics in this section to configure the Gigabit Ethernet (GigE) network for the level 3R storage system.
Networking requirements
Required networking strategies for a K2 Storage System are as follows:
- Three networks:
- Networks must be on separate subnets.
- The media (iSCSI) network is 100% physically separate. This separation is provided by dedicated Gigabit ports, cables, and by VLANs on a single switch or by separate switches.
- The streaming network and the control network are also physically separated by dedicated ports and cables, but the traffic can be mixed on the same VLAN or switch.
- Static IP addresses are required for the media network on K2 Storage System iSCSI devices. This includes the iSCSI clients connected to the storage, such as K2 Media Clients and NewsEdits, and the K2 Media Servers.
- Machine names (host names) assigned to each K2 device.
- Host tables (hosts files) provide name resolution for the media network on each K2 Media Client, iSCSI client, and K2 Media Server.
- IP addresses for FTP/streaming ports must have name resolution such that hostnames are appended with the “_he0” suffix. You can use host tables (as in Setting up host tables) or another mechanism to provide the name resolution. This directs the streaming traffic to the correct port. Refer to the K2 Media Client System Guide for a complete explanation.
- Only K2 Media Servers in the role of FTP server need to be on the streaming network. This is because all streaming traffic goes directly to the shared storage.
- On the K2 Media Client, the four GigE ports are configured as two teams. On external storage models, one team is for the control network and one team is for the media (iSCSI) network. Each team shares a single IP address. This provides redundancy. Do not attempt to un-team these ports.
Use the following procedures as necessary to implement your networking strategies.
NOTE: Media network (iSCSI) IP addresses and Streaming network IP addresses are assigned using the K2 System Configuration application.Networking tips
Establish a consistent convention for machine names and IP addresses. It is recommended that you embed a root name or other unique identifier for this particular K2 Storage System in the computer name. Also, a common convention for IP addresses is to use a numerical pattern or sequence in the IP addresses to indicate device-types and/or ports, as in the following example:
NOTE: This example assumes a subnet mask of 255.255.255.0Example of Level 3R names and IP addresses
Computer name Device type Streaming network addresses Control network addresses Media network addresses Comments root_server_1 Media server 192.168.101.111 192.168.100.11 192.168.99.11 These two servers are a redundant pair. 192.168.99.12 root_server_2 Media server 192.168.101.212 192.168.100.21 192.168.99.21 192.168.99.22 root_server_3 Media server 192.168.101.313 192.168.100.31 192.168.99.31 These two servers are a redundant pair. 192.168.99.32 root_server_4 Media server 192.168.101.414 192.168.100.41 192.168.99.41 192.168.99.42 root_raid_1 RAID — 192.168.100.51 — Each RAID controller is on the control network for monitoring. root_raid_2 RAID — 192.168.100.52 — root_gige_1 GigE switch — 192.168.100.61 — — root_gige_2 GigE switch — 192.168.100.62 — — root_cppc_1 Control point PC — 192.168.100.81 — — root_client_1 iSCSI client — 192.168.100.111 192.168.99.111 Redundant ports share a teamed IP address root_client_2 iSCSI client — 192.168.100.121 192.168.99.121 root_client_3 iSCSI client — 192.168.100.131 192.168.99.131 root_client_4 iSCSI client — 192.168.100.141 192.168.99.141
1This NIC is not used, since this server does not take the role of FTP server2This NIC is not used, since this server does not take the role of FTP server3This IP address must resolve to hostname root_server_3_he04This IP address must resolve to hostname root_server_4_he0Setting up host tables
The hosts file is used by the network to determine the IP address of devices on the network when only a the device name (hostname) is given. The steps that follow describe how to edit the hosts file located at C:\Windows\system32\drivers\etc\hosts on Windows XP and Windows 2003 Server operating system computers. If you include the names and addresses of all the devices on the network, then you can copy the same file onto all the other K2 devices instead of editing the hosts file on each K2 device.
Add the “_he0” suffix to hostnames associated with FTP/Streaming ports. Refer to the K2 Media Client System Guide for more information.
If transferring to or from a Profile XP or Open SAN system via UIM, the hosts file must also follow UIM naming conventions for those systems. Refer to the UIM Instruction Manual.
To edit the hosts file manually:
- Open the following file using Notepad or some other text editing application:
C:\Windows\system32\drivers\etc\hosts- Enter all IP addresses with machine names. The text format is simple. First type the Ethernet IP address, then use the TAB key or Space bar to insert a few spaces. Then type the machine name.
Here is an example:192.168.99.31 root_server_3
192.168.99.32 root_server_3
192.168.100.31 root_server_3
192.168.101.31 root_server_3_he0
192.168.100.51 root_raid_1
192.168.100.61 root_gige_1
- Save the file and exit the text editor.
- Copy the new hosts file onto all the other machines. This is easier than editing the file on each machine.
Testing the control network
To test the control network use the ping command as follows:
- On the control point PC, click Start | Run. The Run dialog box opens.
- Type
cmd
and click OK. The command prompt window opens.- Type
ping
, then a space, then the name of one of your K2 Storage System devices, such as the Gigabit Ethernet switch, as in the following example:- Press Enter.
The ping command should return the IP address of the device, as in the following example:This verifies that the name of the device is being correctly resolved to the IP address, which indicates that on the Control Point PC the host table entry is correct.- Ping the other K2 Storage System devices to which you have assigned control network IP addresses.
- Go to each Windows device in the K2 Storage System and repeat this procedure. This verifies that network communication is correct to and from all devices.
Configuring the level 3R storage system
Use the topics in this section to do the initial configuration of the level 3R storage system.
Prerequisites for initial configuration
Before beginning your initial configuration, make sure the devices of the K2 Storage System meet the following prerequisites. Refer to sections earlier in this manual for detailed information. Also refer to Description of K2 Storage Devices.
Defining a new K2 storage system
Define a level 3R K2 storage system as follows:
- On the control point PC, open the K2 System Configuration application. A login dialog box opens.
- Log in to the K2 System Configuration application with the Windows adminstrator account. By default this as follows:
Refer to Setting up application security for more information about administrator accounts and logging in to applications.
- Click New K2 System. The New K2 System wizard opens.
Follow the on-screen text to define your level 3R K2 Storage System, as described in the following table.
Your K2 Storage System appears in the tree view of the K2 System Configuration application.Continue with the next procedure Configuring the media server 1A - Part 1.
Configuring the media server 1A - Part 1
- In the K2 System Configuration application tree view, select [PrimaryK2Server].
- Click the Configure button.
The Configure K2 Server wizard opens. Follow the on-screen text to configure the media server for a level 3R K2 Storage System, as described in the following table:
On this page… Do this… Enter the name or IP address for the media server, as currently configured on the machine.Click Next Enter the name or IP address for the media server, as currently configured on the machine.For level 3 server roles, leave SNFS file system server, iSCSI bridge, and Media database server selected.Click Next Define server roles
Enter the name or IP address for the media server, as currently configured on the machine.Enter the name or IP address of the Ethernet switch, as currently configured on the switch, to which the media server is connected.For level 3 redundant server roles, leave SNFS file system server, iSCSI bridge, and Media database server selected.Click Next Software ConfigurationThis page checks for the software required to support the roles you selected on the previous page.
If software with Yes in the Required column reports as Not Installed, you must first install it on the media server before continuing. Refer to Managing K2 software. After installing the software, click Check Software. When all required software reports as Installed, click Next. Network ConfigurationThis 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.For Level 3R, since this server does not take the role of FTP server, configuring the second port here for the FTP/streaming network is not required.
The top port is the port over which the K2 System Configuration application is communicating with the media server. If correctly configured, it is already assigned the control network IP address, as displayed on this page.Select the other port and click Modify. A network configuration dialog box opens. Enter the FTP/Streaming IP address and the subnet mask and click Apply.Click Next. File System Server Configuration
Do not yet click Next. Do not yet enter anything in the File System Server #2 box.Click Launch Storage Manager. Storage Utility opens.- Continue with the next procedure Configuring RAID to use Storage Utility to configure the storage and file system.
Leave the Configure K2 Server wizard open while you are using Storage Utility. When you are done with Storage Utility, you continue with the wizard, as explained in Configuring the media server 1A - Part 2.Configuring RAID
Use Storage Utility to complete the configuration of the L3 RAID chassis, as explained in the following topics:
Refer to Prerequisites for initial configuration to confirm that the RAID storage is ready for configuration.
Configuring L3 RAID network and SNMP settings
Use the Storage Utility to configure the following settings for the level 3R RAID controllers:
For level 3R RAID, network and SNMP settings are set and stored on the RAID controller module. Therefore if the RAID chassis has two controllers, each controller has its own network settings and the RAID chassis exists as two entities on the control network. In addition, the RAID storage device is configured by default for the SNMP community name “public”. If your site’s policies require using a different SNMP community name, contact your Grass Valley representative.
To configure these settings, do the following:
- Launch Storage Utility from the K2 System Configuration application as in the previous procedure. If the RAID chassis has two controllers, you will configure the network settings on the controller currently selected when you launch Storage Utility.
- As prompted, wait while Storage Utility gathers system information, then Storage Utility opens.
- In Storage Utility tree view, expand the node for the L3 RAID, right-click the icon for a L3 RAID controller, and select Configuration | Network Properties. The Controller Network Settings dialog box opens. For a level 3R RAID chassis with two controllers, these settings are for controller connected to the K2 Media Server currently selected (or being configured) in the K2 System Configuration application.
- Enter the control network IP address and other network settings.
- You want SNMP trap messages go to the NetCentral server PC, so for SNMP Configuration enter the IP address of the NetCentral server PC. You can also enter IP addresses for other SNMP managers to which you want to send SNMP trap messages.
- Click OK and OK to save settings and close.
- For a level 3R RAID chassis with two controllers, you must also configure network settings on the other controller. You can do this when you configure the K2 media server connected to the other controller.
- In Storage Utility click View | Refresh. Continue with the next procedure Binding disk modules.
Binding disk modules
Use the following procedure to bind disk modules as required for the level 3R storage system.
NOTE: Binding destroys all user data on the disks.
- In the Storage Utility main window, identify bound LUNs and unbound disks by their placement in the hierarchy of the tree view. In the following illustration, disk numbers are represented by “XX”. Refer to Identifying disks for an explanation of how disks are actually numbered in Storage Utility.
Redundant systems store metadata files and journal files on the RAID chassis, which requires a RAID 1 LUN (two disks) for metadata storage and a RAID 1 LUN (two disks) for journal storage. These LUNs must be bound from the first four disks (counting from left to right as you face the front of the RAID chassis) in the primary RAID chassis. These disks must be 15K rpm drives. In addition, the fifth disk in the primary RAID chassis (also a 15K drive) is bound as a Hot Spare. This fifth 15K disk then provides Hot Spare functionality for the other four 15K disks (the RAID 1 LUNs) only. Optionally, you can also use some of your other 10K disks (in groups of five) as Hot Spares for your media storage LUNs. Refer to Binding Hot Spare drives for more information.View disk properties and identify the four disks you will use for the RAID 1 LUNs, the one 15K Hot Spare disk, any other disks that you intend to use for media LUN Hot Spares, and the remainder of the disks that are available for media storage LUNs. Make sure you select disks appropriately as you bind LUNs in the remainder of this procedure.- For redundant systems that use RAID 1 LUNs, you must now create the separate RAID 1 storage for metadata files and journal files. To bind unbound disks for metadata and journal storage, do the following:
- Right-click the Unbound node for the controller, then select Bind LUNs in the context menu. (If the RAID chassis has two controllers, both controllers are represented by the single “Controller” node)
The Bind LUN dialog box opens showing all unbound disks for the controller listed in the Available Disk list.
![]()
- In the LUN TYPE drop down box, select RAID 1.
NOTE: Leave Full Bind selected. Do not uncheck it.
- In the Available Disks box, select two contiguous disks at the top of the list. These should be the first two disks in the primary RAID chassis. (TIP: Use ‘shift-click’ or ‘control-click’ to select disks.) This creates a RAID 1 LUN for metadata storage.
- Click the add (arrow) button to add disks to the Selected Disks list.
NOTE: As an aid in identifying a disk module’s physical location, select it in the Selected Disks list, then click Identify Disks. This causes the disk drive light to flash.
- Click OK to close the Binding LUN dialog box and begin the binding process. The Progress Report dialog box opens, showing the status of the binding process.
- Close the Progress Report and repeat the previous steps, selecting two more contiguous disks to create another RAID 1 LUN for journal storage. These should be the next two disks in the primary RAID chassis.
- Make the fifth disk in the primary RAID chassis a Hot Spare. In the LUN TYPE drop down box, select Hot Spare.
- In the Available Disks box, select the fifth disk in the primary RAID chassis.
- Click the add (arrow) button to add the disk to the Selected Disks list.
- Click OK to close the dialog box and begin the binding process.
- To bind unbound disks for media storage, do the following:
- Right-click the Unbound node for a controller, then select Bind LUNs in the context menu. (If the RAID chassis has two controllers, both controllers are represented by the single “Controller” node)
The Bind LUN dialog box opens showing all unbound disks for the controller listed in the Available Disk list.
NOTE: Leave Full Bind selected. Do not uncheck it.
NOTE: As an aid in identifying a disk module’s physical location, select it in the Selected Disks list, then click Identify Disks. This causes the disk drive light to flash.
- Click OK to close the Binding LUN dialog box and begin the binding process. The Progress Report dialog box opens, showing the status of the binding process.
![]()
- 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, as explained in Binding Hot Spare drives. When you are done, if you did not bind any extra Hot Spares, you should have the following results:
For level three redundant storage, on the primary RAID chassis you should have two RAID 1 LUNs of two disks each, one Hot Spare Disk, and two RAID 5 LUNs of five disks each. For each optional Expansion chassis, you would have an additional three RAID 5 LUNs of five disks each.NOTE: L3 RAID controllers can take several hours to bind a LUN. Make sure you initiate multiple simultaneous binding processes to reduce the overall time.NOTE: Do not proceed until all LUNs are finished binding.
- Restart the K2 Media Server.
- Continue with the next procedure Creating a new file system.
Creating a new file system
- In Storage Utility, click Tools | Make New File System. The Setting dialog box opens.
- 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.
- If the K2 Storage System is to be accessed by only K2 Media Clients you can leave Windows Security unchecked. If accessed by NewsEdits, refer to the NewsShare Technical Reference Guide for instructions.
- Click OK. The Set Stripe Group dialog box opens.
- If you have RAID 1 LUNS, assign a RAID 1 LUN as a metadata stripe and another RAID 1 LUN as a journal stripe. You can distinguish RAID 1 LUNs from media LUNs by the value in the Number of Sectors column.
- Click OK. The Configuration File dialog box opens.
The configuration file for the media file system is displayed. You can verify media file system parameters by viewing this file. Do not edit this file. 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 media server, however the restart at the end of the Configure K2 Server wizard suffices, so you do not need to restart now.
- Close the Storage Utility.
- Continue with the next procedure Configuring the media server 1A - Part 2.
Configuring the media server 1A - Part 2
Configuring the redundant media server 1B
You must wait for the primary media server to restart before continuing. To verify, from the control point PC open the MS-DOS command prompt and use the “ping” command.
For level 3 redundant, after you have configured the first media server (server 1A) you next configure its redundant partner media server (server 1B).
- In the K2 System Configuration application tree view, select the media server you are configuring as server IB.
- Click the Configure button. The Configure K2 Storage System Server wizard opens. Follow the on-screen text to configure the server for a level 3R K2 Storage System, as described in the following table. Some screens require no input from you, as they are based on the configurations already completed on a previously configured media server.
On this page… Do this… Define server roles
Enter the name for the media server. This should be the current network name of the machine.Enter the name or IP address of the Ethernet switch, as currently configured on the switch, to which the media server is connected.For level 3 redundant, select SNFS file system server, iSCSI bridge, and Media database server.Click Next Software ConfigurationThis page checks for the software required to support the roles you selected on the previous page.
If software with Yes in the Required column reports as Not Installed, you must first install it on the media server before continuing. Refer to Managing K2 software. After installing the software, click Check Software. When all required software reports as Installed, click Next. Network ConfigurationThis 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.For Level 3R, since this server does not take the role of FTP server, configuring the second port here for the FTP/streaming network is not required.
The top port is the port over which the K2 System Configuration application is communicating with the media server. If correctly configured, it is already assigned the control network IP address, as displayed on this page.Select the other port and click Modify. A network configuration dialog box opens. Enter the FTP/Streaming IP address and the subnet mask and click Apply.Click Next. File System Server ConfigurationThis page checks on the configuration of the media server in one of its main roles as a file system server. The media server also functions as a file system client, which is also checked from this page.It is not necessary to bind LUNs or create a file system, since this task was completed when you configured the previous media server. However, if the level 3R RAID chassis has two controllers, you must launch Storage Utility from this page to configure controller 1 network settings.
If the RAID chassis has two controllers, click Launch Storage Utility. In the Storage Utility tree view, right-click the icon for the RAID controller, and select Configuration | Network Properties. Enter network and SNMP settings, then close dialog boxes and Storage Utility to return to this page. Refer to Configuring L3 RAID network and SNMP settings for similar Storage Utility procedures.Click Check. Confirm a “… default.cfg file copied…” message. When the wizard reports that the configuration check is successful, click Next. and Yes to confirm copying default.cfg to the other server.If you get a “The V: will not be available until this device is rebooted…” message, you can safely continue with this procedure and follow the instructions related to this message later in the procedure. iSCSI Bridge Server ConfigurationThis 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 LUNs are visible as iSCSI targets.
For level 3 redundant, select Backup.Select an iSCSI adapter and click Modify. A network configuration dialog box opens. Enter the media network IP address and subnet mask and click Apply. Do the same for the other iSCSI adapter.To verify drives, click Check then View Target Drives.Click Next. Database Server Configuration
You do not need to enter or configure anything on this page.Click Next. Completing the Configuration Wizard Click Finish. The wizard closes. The K2 Media Server restarts. Do not proceed until restart processes are finished. If you are not sure if startup is complete, wait 10 minutes.If you got a “The V: will not be available until this device is rebooted…” message on the File System Server Configuration page, after the K2 Media Server restarts, do the following:
Configuring media server 2A
For level 3 redundant, after you have configured the first server (server 1A) and its redundant partner media server (server 1B) you next configure the other “A” server (server 2A).
- In the K2 System Configuration application tree view, select the media server you are configuring as server 2A.
- Click the Configure button. The Configure K2 Server wizard opens. Follow the on-screen text to configure the server for a level 3R K2 Storage System, as described in the following table. Some screens require no input from you, as they are based on the configurations already completed on a previously configured media server.
On this page… Do this… Define server roles
Enter the name for the media server. This should be the current network name of the machine.For level 3 redundant, select iSCSI bridge, FTP server, and NAS server.Click Next Software ConfigurationThis page checks for the software required to support the roles you selected on the previous page.
If software with Yes in the Required column reports as Not Installed, you must first install it on the media server before continuing. Refer to Managing K2 software. After installing the software, click Check Software. When all required software reports as Installed, click Next. Network ConfigurationThis 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.
The top port is the port over which the K2 System Configuration application is communicating with the media server. If correctly configured, it is already assigned the control network IP address, as displayed on this page.Select the other port and click Modify. A network configuration dialog box opens. Enter the FTP/Streaming IP address and the subnet mask and click Apply.Click Next.. File System Client ConfigurationThis media server does not function as a file system server. It does function as a file system client, which is validated from this page.
Click Check. When the wizard reports that the configuration check is successful, click Next. iSCSI Bridge Server ConfigurationThis page manages the components that bridge between iSCSI (the GigE media network) and the the RAID storage. You configure network settings on the iSCSI adapter and the page validates that the media LUNs are visible as iSCSI targets.
For level 3 redundant, select Primary.Select an iSCSI adapter and click Modify. A network configuration dialog box opens. Enter the media network IP address and subnet mask and click Apply. Do the same for the other iSCSI adapter.To verify drives, click Check then View Target Drives.Click Next. Completing the Configuration Wizard Click Finish. The wizard closes. The K2 Media Server restarts. Do not proceed until restart processes are finished. If you are not sure if startup is complete, wait 10 minutes.Configuring the redundant media server 2B
You must wait for server 2A to restart before continuing.
For level 3 redundant, the last media server to configure is server 2B. It is the redundant partner to server 2A.
- In the K2 System Configuration application tree view, select the media server you are configuring as server 2B.
- Click the Configure button. The Configure K2 Server wizard opens. Follow the on-screen text to configure the server for a level 3R K2 Storage System, as described in the following table. Some screens require no input from you, as they are based on the configurations already completed on a previously configured media server.
On this page… Do this… Define server roles
Enter the name for the media server. This should be the current network name of the machine.For level 3 redundant, select iSCSI bridge, FTP server, and NAS server.Click Next Software ConfigurationThis page checks for the software required to support the roles you selected on the previous page.
If software with Yes in the Required column reports as Not Installed, you must first install it on the media server before continuing. Refer to Managing K2 software. After installing the software, click Check Software. When all required software reports as Installed, click Next. Network ConfigurationThis 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.
The top port is the port over which the K2 System Configuration application is communicating with the media server. If correctly configured, it is already assigned the control network IP address, as displayed on this page.Select the other port and click Modify. A network configuration dialog box opens. Enter the FTP/Streaming IP address and the subnet mask and click Apply.Click Next.. File System Client ConfigurationThis media server does not function as a file system server. It does function as a file system client, which is validated from this page.
Click Check. When the wizard reports that the configuration check is successful, click Next.If you get a “The V: will not be available until this device is rebooted…” message, you can safely continue with this procedure and follow the instructions related to this message later in the procedure. SCSI Bridge Server ConfigurationThis page manages the components that bridge between iSCSI (the GigE media network) and the the RAID storage. You configure network settings on the iSCSI adapter and the page validates that the media LUNs are visible as iSCSI targets.
For level 3 redundant, select Backup.Select an iSCSI adapter and click Modify. A network configuration dialog box opens. Enter the media network IP address and subnet mask and click Apply. Do the same for the other iSCSI adapter.Click Next. Completing the Configuration Wizard Click Finish. The wizard closes. The K2 Media Server restarts. Do not proceed until restart processes are finished. If you are not sure if startup is complete, wait 10 minutes.If you got a “The V: will not be available until this device is rebooted…” message on the File System Server Configuration page, after the K2 Media Server restarts, do the following:
Your configurations for the level 3R K2 storage system are complete.
Adding K2 Storage System clients
You can add now clients, such as K2 Media Clients or NewsEdits, to the K2 storage system and configure them using the K2 System Configuration application.
Adding K2 Media Clients
For each of your K2 Media Clients, use the procedures in this section to configure for operation using the K2 Storage System as the shared media storage.
Before beginning with these procedures, make sure the K2 Storage System and the K2 Media Clients are prepared as specified in the sections earlier in this chapter. Cabling must be complete, K2 Media Clients must be communicating on the control network, and the K2 Storage System must have a viable media file system.
Configuring a K2 Media Client
Configure a K2 Media Client as follows:
- On the K2 configuration control point PC, open the K2 System Configuration application. A login dialog box opens.
- Log in to the K2 System Configuration application with the correct adminstrator account. By default this as follows:
Refer to Setting up application security for more information about administrator accounts and logging in to applications.- In the K2 System Configuration application tree view, verify that the K2 Storage System is correctly defined.You should see the correct number of K2 Media Clients. If the correct number of K2 Media Clients is not currently added to the K2 Storage System, you can add or remove clients now (before clients are configured), as follows:
- Select the top K2 Media Client.
- Click the Configure button.
The K2 Media Client Configuration wizard opens. Follow the on-screen text as described in the following table.:
On this page… Do this… Page 1
Enter the IP address or network name for a K2 Media Client, as currently configured on the K2 Media Client. You should configure your highest bandwidth K2 Media Clients first, as this ensures load balancing is correct. Refer to the K2 Media Client System Guide for information on load balancing.For the Storage Access settings, leave iSCSI selected.Click Next Software ConfigurationThis page checks the K2 Media Client for required software.
If software with Yes in the Required column reports as Not Installed, you must first install it on the K2 Media Client before continuing. Refer to Managing K2 client system software. After installing the software, click Check Software. When all required software reports as Installed, click Next. Network ConfigurationThis page configures the Ethernet ports for both the control network and the media network. The K2 Media Client actually has four Gigabit Ethernet ports, but they are configured as two teamed pairs. Each teamed pair shares an IP address and appears on this page as a single port.
The top port is the port over which the K2 System Configuration application is communicating with the K2 Media Client. If correctly configured, it is already assigned the control network IP address, which is displayed in the window.Select the other port and click Modify. A network configuration dialog box opens. Enter the media network IP address and the subnet mask.Click Next. Database Client ConfigurationThis page connects the K2 Media Client as a media database client to the K2 Media Server taking the role of media database server. If there are redundant K2 Media Servers, both are listed on this page as database servers.
Verify that the K2 Media Client is connecting to the correct K2 Media Server or Servers, as follows:• For Level 1, the client connects to the L1 RAID storage device.• For Level 2, the client connects to the only server.• For Level 2R, the client connects to server A as database server 1 and sever B as database server 2.• For Level 3, the client connects to server 1.• For Level 3R, the client connects to server 1A as database server 1 and sever 1B as database server 2.If there are multiple FTP servers, the K2 System Configuration application automatically assigns the K2 Media Client to a FTP server to provide optimum FTP bandwidth across the system.Click Check. When the wizard reports that the configuration check is successful, click Next. File System Client ConfigurationThis page connects the K2 Media 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.
Verify that the K2 Media Client is connecting to the correct K2 Media Server or Servers, as follows:• For Level 1, the client connects to the L1 RAID storage device.• For Level 2, the client connects to the only server.• For Level 2R, the client connects to server A as file system server 1 and server B as file system server 2.• For Level 3, the client connects to server 1.• For Level 3R, the client connects to server 1A as file system server 1 and server 1B as file system server 2.Click Check. When the wizard reports that the configuration check is successful, click Next. iSCSI Initiator ConfigurationThis page load balances the K2 Media Client’s iSCSI connection to the K2 Storage System. The iSCSI adapters on your K2 Media Server or servers are listed here as iSCSI targets. The K2 System Configuration application determines the iSCSI target to which each K2 Media Client subscribes, based on the bandwidth values that you enter. This enforces policies by which each K2 Media Client has sufficient bandwidth for its intended use and no individual iSCSI target is oversubscribed.
Click Modify. The Bandwidth Input dialog box opens.Enter the channel count, bit rate, and track count per channel information according to your intended use of the K2 Media Client.Click Calculate and verify that the total bandwidth is correct according to the system design for your shared storage system. You should be configuring your highest bandwidth K2 Media Clients first, to ensure that they are distributed equally across iSCSI targets. To verify this, while you are on this page for your first K2 Media Client, you can temporarily enter information and calculate the bandwidth for each of your K2 Media Clients and compare bandwidth values.Click Assign Portal, then OK to confirm.If you have a redundant K2 Storage System, the K2 System Configuration application makes the appropriate assignment to the redundant server, as reported in the Secondary target box.Click Next. Completing the Configuration Wizard Click Finish. The K2 Media Client restarts and the wizard closes.- Repeat this procedure for each of your K2 Media Clients.
Basic operations for level 3R storage
Use the following procedures as you work on your level 3R storage system:
For other procedures refer to Administering and maintaining the K2 Storage System.
Level 3R power-off procedure
Use the following sequence to power-off the level 3R storage system.
- Power-off all K2 Media clients or other iSCSI clients.
- From the K2 System Configuration application, in the tree view select the name of the K2 Storage System, which is the top node of the storage system tree. Then click the Server Control Panel button.
The Server Control Panel opens.
- Take note of which is the primary K2 Media Server and which is the backup K2 Media Server. The order in which you put servers back into service when you power up the K2 Storage System is dependent on their primary/backup roles at the time when you power down the K2 Storage System.
- For the backup K2 Media Server, click Stop. This takes the server out of service.
- Shut down the backup K2 Media Server, if it does not shut down automatically.
- For the primary K2 Media Server, click Stop. This takes the server out of service.
- Shut down the primary K2 Media Server, if it does not shut down automatically.
- For your other two K2 Media Servers that are the FTP servers, first shut down the backup, then the primary.
- Power-off the RAID controller chassis. If expansion chassis are connected, make sure the power-off of the controller chassis is prior to or simultaneous with the power-off of its connected expansion chassis. Wait approximately 30 seconds for the disk drives to spin down before proceeding.
- Power-off all Ethernet switches.
- Power-off the control point PC and/or the NetCentral server PC, if necessary.
Level 3R power-on procedure
Use the following steps to power-on the level 3R storage system.
Using FTP for file transfer
Refer to FTP on the K2 Storage System.
Copyright Grass Valley, Inc. http://www.thomsongrassvalley.com |