Installing the Level 3 Storage System


Use this chapter to install the K2 Level 3 (L3) storage system.

This chapter includes the following topics:

Work through these topics sequentially to install the storage system.

Level 3 system description

The level three storage system has two K2 media servers, between which the media server roles are distributed. Typically one media server runs as the media file system and database server while the other media server runs as the FTP server. This boosts performance, as the system resources of each server can be optimized for specific roles. In addition, both servers take the role of iSCSI bridge, so that there are a total of four iSCSI media connections for increased bandwidth.

The level three storage system has one L3 RAID chassis. Up to seven optional Expansion chassis are available for increased storage capacity.

K2 Media Clients and other iSCSI clients, such as NewsEdits, are connected to the GigE switch. Each client has one GigE connection for media and one GigE connection for control. The GigE switch is configured with V-LANs to keep the traffic on these connections 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.

The L3 RAID chassis is connected via a Fibre Channel connection to each media server. These connections access the disks simultaneously, providing increased bandwidth. The L3 RAID chassis is also connected to the GigE control network, which is required for SNMP (NetCentral) monitoring.

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 3 devices

Use the topics in this section to prepare each device so that it is ready to become part of the level 3 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:

Also refer to Control point PC description.

Setting up the level 3 GigE switch

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.

Refer to Level 3 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

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.

  1. 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:
    • Baud rate 9600
    • 8 data bits, 1 stop bit, no parity, and flow control set to Xon/Xoff
    • Also disable (uncheck) the “Use Function, Arrow, and Ctrl Keys for Windows” option
  2. Connect the PC to the switch’s Console Port using the console cable included with the switch.
  3. Turn on the PC’s power and start the PC terminal program.
  4. 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.
  5. At the prompt, enter setup to display the Switch Setup screen.
  6. Tab to the IP Config (DHCP/Bootp) field and use the Space bar to select the Manual option.
  7. Tab to the IP Address field and enter the switch’s control network IP address. Refer to Networking tips.
  8. Tab to the Subnet Mask field and enter the subnet mask used for your network.
  9. 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.
  10. From the main menu, choose Console Passwords and press Enter. The Set Password Menu opens.
  11. Chose Set Manager Password and press Enter.
  12. Enter a password. You can use the default K2 administrator password “K2admin” or your site’s password for administering the K2 Storage System.
  13. Return to the main menu
  14. Tab to Command Line (CLI) and press Enter. The command prompt appears.
  15. Type configure to change to configuration mode.
  16. 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:
    • password manager user-name K2admin.
  17. 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.
  18. 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. For example, if the community name is “K2”, type the following:
snmp-server community K2 unrestricted

This allows NetCentral to test the switch to verify that it can send its SNMP trap messages to NetCentral.

  1. Type menu to get to menu mode.
  2. 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):
    1. Select Switch Configuration.
    2. Choose selection 2, Port/Trunk Settings.
    3. Press the right-arrow key to choose Edit, then press Enter.
    4. Down arrow until at the bottom of the list of ports.
    5. Right-arrow over to the Group column.
    6. Use the Space bar and set the bottom port to Trk1.
    7. Set the next port up also to Trk1.
    8. 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.
  3. Choose Reboot Switch to restart the switch.
  4. You can now use the switch’s web browser interface for further configuration, as instructed in the next procedure.
  5. Close the PC terminal program and disconnect the console cable.

Continue with the next procedure Configuring the GigE switch VLANs.

Configuring the GigE switch VLANs

The following steps are for the HP ProCurve switch. Accomplish tasks similarly on a Cisco switch.

  1. 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.
  2. On the PC, open Internet Explorer and type the switch’s IP address in the Address field, as in the following example.
    • http://192.168.100.61
    This should be the name or IP address as currently configured on the switch.
  3. Press Enter to open the switch’s configuration application.
NOTE: The configuration application for the HP ProCurve switch requires Java.

Setting up the K2 media server

Do the following to prepare each K2 media server:

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

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:

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.

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:

  1. If you have not already done so, connect keyboard, monitor, and mouse to the K2 Media Client and log on to Windows.
  2. Stop all media access. If AppCenter is open, close it.
  3. Click Start | Run, type cmd and press Enter. The MS-DOS command prompt window opens.
  4. From the command prompt, navigate to the C:\profile\mpio directory.
  5. Type the following at the command prompt:
  6. C:\profile\mpio>gdsminstall.exe -i c:\profile\mpio gdsm.inf Root\GDSM
  7. Press Enter. The software is installed. The command prompt window reports the following:
    • Pre-Installing the Multi-Path Adapter Filter...
      Success
      Installing the Multi-Path Bus Driver...
      Success
      Installing the Device Specific Module...
      Success
      Installing the Multi-Path Device Driver...
      Success (but need a reboot)
  8. Restart the K2 Media Client.
  9. 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.


  10. In the left pane select Device Manager.
  11. 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:

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 3

Use the topics in this section to configure the Gigabit Ethernet (GigE) network for the level 3 storage system.

Networking requirements

Required networking strategies for a K2 Storage System are as follows:

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.0

Example of Level 3 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
Media file system/database server
192.168.99.12
root_server_2
Media server
192.168.101.212
192.168.100.21
192.168.99.21
FTP server
192.168.99.22
root_raid_1
RAID
192.168.100.51
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
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 server
2This IP address must resolve to hostname root_server_2_he0

Setting 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:

  1. Open the following file using Notepad or some other text editing application:
  2. C:\Windows\system32\drivers\etc\hosts
  3. 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.
  4. Here is an example:
    192.168.99.21    root_server_2
    192.168.99.22    root_server_2
    192.168.100.21   root_server_2
    192.168.101.21   root_server_2_he0
    192.168.100.51   root_raid_1
    192.168.100.61   root_gige_1
  5. Save the file and exit the text editor.
  6. 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:

  1. On the control point PC, click Start | Run. The Run dialog box opens.
  2. Type cmd and click OK. The command prompt window opens.
  3. 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:
    • ping root_gige_1
  4. Press Enter.
  5. The ping command should return the IP address of the device, as in the following example:
      Pinging root_gige_1.mycorp.com [192.168.100.61] with 32 bytes of data:
      Reply from 192.168.100.61: bytes=32 time=10ms TTL=127
      Reply from 192.168.100.61: bytes=32 time<10ms TTL=127
      Reply from 192.168.100.61: bytes=32 time<10ms TTL=127
      Reply from 192.168.100.61: bytes=32 time<10ms TTL=127
    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.
  6. Ping the other K2 Storage System devices to which you have assigned control network IP addresses.
  7. 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 3 storage system

Use the topics in this section to do the initial configuration of the level 3 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.

Devices
Prerequisite for level 3 configuration
Control point PC
Ethernet cable connected
Control Point software installed
Control network IP address assigned
Network communication over the control network with all other K2 devices
Power on
Ethernet switch
Ethernet cables connected
Control network IP address assigned
VLANs set up
Power on
K2 Media Server
Ethernet cables connected
Fibre Channel cable connected
Software installed, as from the factory
Control network IP address assigned
Power on
L3 RAID chassis
Fibre Channel address ID assigned to RAID controller(s)
Fibre Channel cable(s) connected
Ethernet cable(s) connected
Power on
L3 RAID Expansion chassis
(optional)
Chassis address assigned (for Fibre Channel)
Fibre channel cable(s) connected
Power on
K2 Media Clients
Ethernet cables connected
Software installed, as from the factory
Control network IP address assigned
Power on

Defining a new K2 storage system

Define a level 3 K2 storage system as follows:

  1. On the control point PC, open the K2 System Configuration application. A login dialog box opens.


  2. Log in to the K2 System Configuration application with the Windows adminstrator account. By default this as follows:
    • Username: administrator
    • Password: adminK2
    Refer to Setting up application security for more information about administrator accounts and logging in to applications.



  3. Click New K2 System. The New K2 System wizard opens.
  4. Follow the on-screen text to define your level 3 K2 Storage System, as described in the following table.

    On this page…
    Do this…
    Page 1

    Create a name for your level 3 K2 Storage System and type it in the Name box.
    Select Level 3.
    Leave the Server redundancy option unchecked.
    Click Next
    Page 2

    Move clients into the Number of Devices box as appropriate for your system.
    You cannot change the number of K2 Media Servers or Ethernet Switches, as these are pre-configured based on the level you selected in the previous page.
    Click Next.
    Page 3

    Review the information on this page and verify that you have correctly defined your K2 Storage System.
    For a level 3 storage system you should have the following:
    • One Gigabit Ethernet switch
    • Two K2 Media Servers
    • The number and type of clients appropriate for your system.
    Click Finish. The Define New K2 Storage System wizard closes.
    Your K2 Storage System appears in the tree view of the K2 System Configuration application.

Continue with the next procedure Configuring the media server - Part 1.

Configuring the media server - Part 1

  1. In the K2 System Configuration application tree view, select [PrimaryK2Server].
  2. Click the Configure button. The Configure K2 Server wizard opens. Follow the on-screen text to configure the media server for a level 3 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
    Define server roles

    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
    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 Configuration
    This 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 Configuration
    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.
    For Level 3, 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

    Click Launch Storage Manager. Storage Utility opens.
  3. Continue with the next procedure Configuring RAID to use Storage Utility to configure the storage and file system.
  4. 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 - 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 3 RAID controller:

For level 3 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:

  1. 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.
  2. As prompted, wait while Storage Utility gathers system information, then Storage Utility opens.
  3. 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 3 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.


  4. Enter the control network IP address and other network settings.
  5. 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.
  6. Click OK and OK to save settings and close.
  7. For a level 3 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.
  8. 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 3 storage system.

NOTE: Binding destroys all user data on the disks.
  1. 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.


  2. To bind unbound disks for media storage, do the following:
    1. Right-click the Unbound node for a controller, then select Bind LUNs in the context menu.
    2. 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.
    1. In the LUN TYPE drop down box, select RAID 5.
    2. In the Available Disks box, select five contiguous disks at the top of the list. (TIP: Use ‘shift-click’ or ‘control-click’ to select disks.).
    3. 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.
    1. 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.
    2. 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:
    3. For level three storage you should have three RAID 5 LUNs of five disks each on a RAID storage device. 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.
    1. Upon 100% completion, click Close in Progress Report window.
NOTE: Do not proceed until all LUNs are finished binding.
  1. Restart the K2 Media Server.
  2. Continue with the next procedure Creating a new file system.

Creating a new file system

  1. In Storage Utility, click Tools | Make New File System. The Setting dialog box opens.


  2. 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.
  3. 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.
  4. Click OK. The Configuration File dialog box opens.


  5. 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.
  6. 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.
  7. Close the Storage Utility.
  8. Continue with the next procedure Configuring the media server - Part 2.

Configuring the media server - Part 2

  1. Return to the Configure K2 Server page from which you launched Storage Utility and proceed as described in the following table:



On this page…
Do this…
File System Server Configuration
This 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.

Click Check. 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 with this procedure and follow the instructions related to this message later in the procedure.
iSCSI Bridge Server Configuration
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 LUNs are visible as iSCSI targets.

Select an iSCSI adapter and click Modify. A network configuration dialog box opens. Enter the media network IP address and the subnet mask and click Apply. Do the same for the other iSCSI adapter.
Click Check. The Validation Report opens.
Confirm that the iSCSI configuration is successful. Close the Validation Report and then 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. Wait until all startup processes have completed before continuing. If you are not sure if startup is complete, wait 10 minutes.

Configuring media server 2

For level 3, after you have configured your first media server (server 1) you next configure the other media server (server 2).

  1. In the K2 System Configuration application tree view, select the media server you are configuring as server 2.
  2. Click the Configure button. The Configure K2 Server wizard opens. Follow the on-screen text to configure the server for a level 3 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, select iSCSI bridge, FTP server, and NAS server.
    Click Next
    Software Configuration
    This 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 Configuration
    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.

    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 Configuration
    This 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 Configuration
    This 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, 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.

Your configurations for the level 3 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:

  1. On the K2 configuration control point PC, open the K2 System Configuration application. A login dialog box opens.


  2. Log in to the K2 System Configuration application with the correct adminstrator account. By default this as follows:
    • Username: administrator
    • Password: adminK2
    Refer to Setting up application security for more information about administrator accounts and logging in to applications.
  3. 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 node of the storage system and click the Add Device button
    • Select a unconfigured K2 Media Client and click the Remove button.
  4. Select the top K2 Media Client.
  5. 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 Configuration
    This 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 Configuration
    This 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 Configuration
    This 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 Configuration
    This 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 Configuration
    This 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.
  6. Repeat this procedure for each of your K2 Media Clients.

Basic operations for level 3 storage

Use the following procedures as you work on your level 3 storage system:

For other procedures refer to Administering and maintaining the K2 Storage System.

Level 3 power-off procedure

Use the following sequence to power-off the level 3 storage system.

  1. Power-off all K2 Media clients or other iSCSI clients.
  2. Shut down the K2 Media Server that is the media file system and database server.
  3. Shut down the K2 Media Server that is the FTP server.
  4. 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.
  5. Power-off all Ethernet switches.
  6. Power-off the control point PC and/or the NetCentral server PC, if necessary.

Level 3 power-on procedure

Use the following steps to power-on the level 3 storage system.

Device
Verification instructions
1.
Power-on the control point PC and/or the NetCentral server PC.
After log on, start NetCentral. NetCentral reports devices as offline. As each device is powered on, check NetCentral to verify the device’s status.
2.
Power-on the Ethernet switch.
This description is for the HP ProCurve switch. For the Cisco Catalyst switch, refer to the documentation you received with the switch.
The switch performs its diagnostic self test, which takes approximately 50 seconds to complete. LED Behavior during the self test is as follows:
• Initially, all the status, LED Mode and port LEDs are on for most of the duration of the test.
• Most of the LEDs go off and then may come on again during phases of the self test. For the duration of the self test, the Test LED stays on.
When the self test completes successfully, the Power and Fan Status LEDs remain on, the Fault and Test LEDs go off, and the port LEDs on the front of the switch go into their normal operational mode, which is as follows:
• If the ports are connected to active network devices, the LEDs behave according to the LED Mode selected. In the default view mode (Link), the LEDs should be on.
• If the ports are not connected to active network devices, the LEDs will stay off.
If the LED display is different than what is described above, especially if the Fault and Test LEDs stay on for more than 60 seconds or they start blinking, the self test has not completed correctly. Refer to the manual you received with the switch for troubleshooting information.
3.
Power-on RAID storage devices.
Power-on expansion chassis (if present) prior to or simultaneous with the power-on for the main Fibre Channel chassis.
NOTE: Always power-on the RAID Expansion chassis prior to, or simultaneously with the RAID Controller chassis.
Verify that start-up indicators show normal start-up processes, as follows:
• DIR and SVP LEDs on the RAID controllers are blinking green
• Disk Link LED is steady ON green.
• FLT and BAT LEDs are OFF.
• The front Power LED is ON, Service LED is OFF after about 5 minutes.
Refer to the L3 RAID Instruction Manual to interpret other disk access LED or status LED behavior.
4.
Power-on the K2 Media Server that is the media file system/database server.
Flip down the front bezel and press the stand-by button.
The LCD display lights during normal system operation.
Wait until start up processes are complete before powering up clients. When the server responds to the ping command, startup is complete. If you are not sure, wait 10 minutes.
5.
Power-on the remaining K2 Media Server. This is the FTP server.
Flip down the front bezel and press the stand-by button.
The LCD display lights during normal system operation.
Wait until start up processes are complete before proceeding. When the server responds to the ping command, startup is complete. If you are not sure, wait 10 minutes.
6.
Power-on K2 Media Clients and other iSCSI clients.

Using FTP for file transfer

Refer to FTP on the K2 Storage System.


Copyright Grass Valley, Inc.
http://www.thomsongrassvalley.com