GRASS VALLEY K2 7.3.8 - RELEASE NOTES AND, K2 Summit Production Client, K2 Solo Media Server, K2 Summit SAN Quick Start Manual
Documentation path to install
071-8781-00
K2 Summit Production Client,
K2 Solo Media Server, and
K2 Summit SAN
Version 7.3.8
Release Notes & Upgrade Instructions
These release notes contain the most recent information and supersede previous
publications, as of 23 November 2010. Check the Grass Valley website at
www.grassvalley.com/docs for an updated version that contains additional important
information.
These release notes contain information for the following:
• K2 Summit models with internal storage
•
K2 Summit models with direct-connect storage
• K2 Solo Media Server
• The K2 Storage Area Network (SAN) with connected shared storage K2 Summit
Production Clients
K2 system with internal storage
Release
Notes
Documentation path to install
Copyright © Grass Valley, Inc. All rights reserved. Printed in the United States of America. Portions of software © 2000 – 2010, Microsoft Corporation. All rights reserved. This
document may not be copied in whole or in part, or otherwise reproduced except as specifically permitted under U.S. copyright law, without the prior written consent of Grass
Valley, Inc., P.O. Box 59900, Nevada City, California 95959-7900. This product may be covered by one or more U.S. and foreign patents.
Product options and specifications subject to change without notice. The information in this manual is furnished for informational use only, is subject to change without notice,
and should not be construed as a commitment by Grass Valley, Inc. Grass Valley, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in
this publication.
Grass Valley, K2, Aurora, Summit, Dyno, Solo, Infinity, Turbo, Profile, Profile XP, NetCentral, NewsBrowse, NewsEdit, NewsQ, NewsShare, NewsQ Pro, and Media Manager
are either registered trademarks or trademarks of Grass Valley, Inc. in the United States and/or other countries. Grass Valley, Inc. products are covered by U.S. and foreign
patents, issued and pending. Additional information regarding Grass Valley, Inc. trademarks and other proprietary rights may be found at www.grassvalley.com. Other
trademarks and logos used in this document are either registered trademarks or trademarks of the manufacturers or vendors of the associated products, such as Microsoft®
Windows® operating system, Windows Media® player, Internet Explorer® internet browser, and SQL Server™. QuickTime and the QuickTime logo are trademarks or
registered trademarks of Apple Computer, Inc., used under license therefrom.
K2 client with shared or direct-connect storage
Release
Notes
*Cabling Guide packed with RAID primary chassis
Quick Start
Guide
Grass Valley
K2
flxxxxx
xxxxxxxxxxxxxx
flxxxxx
*Cabling
Guide
flxxxxx
SAN Manual
(shared storage)
System
Guide
System
Guide
Quick Start
Guide
Contents
Grass Valley Product Support......................................................................................................................5
Release Summary........................................................................................................................................7
What's new in version 7.3.8......................................................................................................................7
Not supported in this release....................................................................................................................9
Changes and features in previous releases..............................................................................................9
Additional notes..........................................................................................................................................13
Using reference files...............................................................................................................................13
About QuickTime reference files.........................................................................................................13
About MXF reference files...................................................................................................................13
Configuring reference file type on a stand-alone K2 system...............................................................13
Configuring reference file type on a K2 SAN system..........................................................................14
Using the Export capture service............................................................................................................14
About the Export capture service........................................................................................................14
Prerequisites for using the Export capture service.............................................................................15
Considerations for using the Export capture service...........................................................................15
Configuring the Export Capture Service.............................................................................................15
Testing the Export Capture Service....................................................................................................18
Export capture service components....................................................................................................18
MXF interchange specification................................................................................................................18
MXF export behavior on K2 systems..................................................................................................19
QuickTime interchange specification......................................................................................................19
QuickTime video and key import specification....................................................................................20
P2 interchange specification...................................................................................................................21
About introducing ChannelFlex Suite on existing K2 systems................................................................22
Codec option matrix................................................................................................................................23
Managing the write filter..........................................................................................................................23
Passwords and security on K2 systems.................................................................................................25
About application security on the K2 SAN..........................................................................................26
Upgrading firmware on HP switch...........................................................................................................27
Configuring QOS on the GigE switch.....................................................................................................28
Operation considerations...........................................................................................................................30
Version compatibility...................................................................................................................................31
Compatible K2 Summit/Solo components..............................................................................................31
Compatible K2 Media Server components.............................................................................................33
Compatible K2 Control Point PC components........................................................................................33
Compatible HP ProCurve GigE switch components...............................................................................34
Compatible K2 RAID components..........................................................................................................35
Compatible K2 RAID disk drive firmware................................................................................................36
Compatible Grass Valley products..........................................................................................................39
Compatible third party products..............................................................................................................41
Compatible recovery applications...........................................................................................................41
Upgrading K2 systems...............................................................................................................................42
Upgrading a K2 SAN..............................................................................................................................42
About upgrading the K2 SAN with SiteConfig.....................................................................................42
Make recovery images........................................................................................................................43
Prepare SiteConfig for software deployment to K2 SAN devices........................................................43
Deploy control point PC software........................................................................................................44
Take SAN clients offline......................................................................................................................45
Manage multiple K2 Media Servers....................................................................................................45
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 2
Upgrade K2 Media Server...................................................................................................................46
Verify/upgrade switch firmware...........................................................................................................54
Upgrade RAID controller microcode...................................................................................................55
Upgrade RAID disk drive firmware......................................................................................................55
Reset Capture Services......................................................................................................................56
Manage redundancy on K2 Media Servers.........................................................................................57
Upgrade remaining K2 Media Servers................................................................................................58
Upgrade K2 client................................................................................................................................58
Upgrade Aurora Edit, Ingest, and Playout systems.............................................................................63
Upgrade NAS systems........................................................................................................................63
Upgrade Browse and MediaFrame systems.......................................................................................64
Upgrade other SAN clients..................................................................................................................64
Make recovery images........................................................................................................................64
Upgrading stand-alone K2 systems with SiteConfig...............................................................................64
About upgrading stand-alone K2 systems with SiteConfig.................................................................65
Make recovery images........................................................................................................................65
Prepare for K2 system upgrade..........................................................................................................66
Upgrade QuickTime............................................................................................................................66
Configure SNFS default.cfg file on stand-alone K2 system................................................................66
Prepare SiteConfig for software deployment to stand-alone K2 systems...........................................67
Check all currently installed software on stand-alone K2 systems......................................................68
Add software package to deployment group for stand-alone K2 systems...........................................68
Unlock K2 Summit Production Clients or K2 Solo Media Servers......................................................69
Upgrade software on stand-alone K2 systems....................................................................................69
Power cycle K2 system.......................................................................................................................71
Install required Windows update.........................................................................................................72
Upgrade LSI RAID controller driver.....................................................................................................73
Upgrade MegaRAID Storage Manager...............................................................................................73
Upgrade RAID Controller microcode on stand-alone K2 system........................................................74
Upgrade disk drive firmware on stand-alone K2 system.....................................................................76
Configure RTIO...................................................................................................................................77
Reset Capture Services......................................................................................................................78
Upgrade K2 Dyno Server software......................................................................................................79
Lock K2 Summit Production Clients....................................................................................................80
Upgrade K2 Dyno Controller...............................................................................................................81
Install MPEG-2/AVC-Intra field kit.......................................................................................................82
Make recovery images........................................................................................................................82
Deploy control point PC software........................................................................................................82
Upgrading stand-alone K2 systems without SiteConfig..........................................................................83
Make recovery images........................................................................................................................83
Prepare for K2 system upgrade..........................................................................................................83
Disable write filter................................................................................................................................84
Upgrade QuickTime............................................................................................................................84
Configure SNFS default.cfg file on stand-alone K2 system................................................................84
Uninstall K2 software from stand-alone K2 system.............................................................................85
Uninstall SNFS from K2 client.............................................................................................................86
Install K2 software...............................................................................................................................86
Install SNFS on stand-alone K2 system..............................................................................................89
Verify upgraded software.....................................................................................................................89
Install required Windows update.........................................................................................................90
Upgrade LSI RAID controller driver.....................................................................................................90
Upgrade MegaRAID Storage Manager...............................................................................................91
Upgrade RAID Controller microcode on stand-alone K2 system........................................................92
Upgrade disk drive firmware on stand-alone K2 system.....................................................................93
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 3
Configure RTIO...................................................................................................................................95
Reset Capture Services......................................................................................................................96
Upgrade K2 Dyno Server software......................................................................................................97
Upgrade remaining stand-alone K2 systems......................................................................................98
Enable write filter.................................................................................................................................99
Upgrade K2 Dyno Controller...............................................................................................................99
Install MPEG-2/AVC-Intra field kit.....................................................................................................100
Make recovery images......................................................................................................................101
Licensing K2 products..........................................................................................................................101
K2 licenses........................................................................................................................................101
About K2 system software licensing.................................................................................................102
Requesting a license.........................................................................................................................102
Adding a license................................................................................................................................104
Deleting licenses...............................................................................................................................104
Archiving licenses.............................................................................................................................105
Known Problems......................................................................................................................................106
4 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Grass Valley Product Support
To get technical assistance, check on the status of a question, or to report a new issue, contact Grass
Valley Product Support via e-mail, the Web, or by phone or fax.
Web Technical Support
To access support information on the Web, visit the product support Web page on the Grass Valley
Web site. You can download software or find solutions to problems.
World Wide Web: http://www.grassvalley.com/support/
Technical Support E-mail Address: gvgtechsupport@grassvalley.com
Grass Valley Knowledge Base: http://grassvalley.novosolutions.net/
In the Knowledge Base you can search by topic, search by product, or browse the Table of Contents
to find Frequently Asked Questions (FAQ).
Telephone Support
Use the following information to contact Product Support by phone.
International Support Centers
Our international support centers are available 24 hours a day, 7 days a week.
Authorized Local Support Representative
A local support representative may be available in your country. To locate a support center during
normal local business hours, refer to the following list. This list is regularly updated on the website
for Grass Valley Product Support
(http://www.grassvalley.com/support/contact/phone/)
After–hours local phone support is also available for warranty and contract customers.
In countryToll freeSupport Center
+33 1 48 25 20 20+800 80 80 20 20France
+1 530 478 4148+1 800 547 8949United States
TelephoneCountryRegion
+86 10 5883 7575ChinaAsia
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 5
+852 2531 3058Hong Kong, Taiwan, Korea,
Macau
+81 3 6848 5561Japan
+603 7492 3303Southeast Asia - Malaysia
+65 6379 1313Southeast Asia - Singapore
Grass Valley Product Support
TelephoneCountryRegion
+91 22 676 10324India
1 300 721 495AustraliaPacific
0800 846 676New Zealand
+61 3 8540 3650For callers outside Australia or
New Zealand
+55 11 5509 3440AllCentral America, South America
North America
North America, Mexico,
Caribbean
France
Eastern Europe
Ukraine, Uzbekistan
Near East and Africa
+1 800 547 8949;
+1 530 478 4148
+44 1189 230 499UK, Ireland, IsraelEurope
+31 (0) 35 62 38 421Benelux – Netherlands
+32 (0) 2 334 90 30Benelux – Belgium
+800 80 80 20 20;
+33 1 48 25 20 20
+49 6150 104 444Germany, Austria,
+7 495 258 09 20Belarus, Russia, Tadzhikistan,
+45 404 72 237Northern Europe
+39 06 87 20 35 28Southern Europe – Italy
+34 91 512 03 50Southern Europe – Spain
+971 4 299 64 40Middle EastMiddle East, Near East, Africa
+800 80 80 20 20;
+33 1 48 25 20 20
6 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Release Summary
What's new in version 7.3.8
The following features are available with the initial software release:
• Licensing for K2 system software — When upgrading, version 7.3.8 K2 system software installs
with a 30 day trial license. You must obtain a permanent license from Grass Valley. Version
7.3.8 is a free upgrade for anyone under a service contract or SLA. Customers with previous
versions who are outside the 1 year warranty can purchase an upgrade. When upgrading to version
7.3.8, make sure that you carefully follow the upgrade and licensing procedures later in these
release notes, so that licensing features are correctly installed.
• HotBin Export – Automatically export K2 clips in any format that the K2 system supports. The
feature requires the K2-HotBinExportService license. Refer to About the Export capture service
on page 14.
• P2 Export – AppCenter export supports P2 format.
• QuickTime Video+Key Import – Import QuickTime files with an alpha video channel encoded
using the Apple Animation codec for Video+Key (key-fill) clips. This feature requires the
AppCenterElite license. Refer to QuickTime video and key import specification on page 20.
• MXF reference files — When you create a simple K2 clip on a K2 system, K2 software can
create a corresponding reference file. The reference file is stored in a directory in the clip's folder
on the V: drive. You can configure the software to create QuickTime reference files, MXF
reference files, or no reference files. Refer to About MXF reference files on page 13.
• MXF and QuickTime export of complex movies – Complex movies are flattened during MXF
and QuickTime streaming export, as these formats do not directly support complex movies. MXF
interchange specification on page 18.
• Storage Utility features — Clean Unreferenced Files and Clean Unreferenced Movies are now
supported.
• Continuous record export — You can export a completed continuous (loop) record clip as
MXF or QuickTime, with the result being a flattened stream file. Recording must be complete
before you export the clip, however you can make sub-clips while record is underway and export
the sub-clips. For this feature, MPEG-2 long GoP is not supported.
• More robust performance — Improved recovery from interrupted video inputs.
• Turbo iDDR — Compatibility with Turbo iDDR no longer supported.
• K2 SAN Quality of Service (QOS) — A third level of QOS is available for better management
of generic iSCSI clients, such as editing workstations. Refer to the K2 SAN Installation and
Service Manual.
• SNFS file system — Upgrade to version 3.5.2.1b15620 is required. This version supports 64-bit
systems.
• K2 Dyno PA DLC tool — A DLC (Distributed LAN Client) tool streamlines the configuration
of a stand-alone K2 Summit system with the K2 Dyno PA application. For more information,
see the K2 Dyno PA documentation.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 7
Release Summary
The following hardware components and systems are available at some time after the initial software
release:
• K2 10G SAN systems with K2 10G RAID storage — A new storage infrastructure for SAN
systems provides increased bandwidth. Devices include the following:
• K2 10G RAID storage (NEC Condor) with 8 Gig (D4) controllers
• K2 Media Server (Dell 610) with 10 Gig iSCSI interface adapter (TOE) and SFP+ connection
• 2910 HP Switch with 10 Gig SFP+ connections
Features include the following:
• 10 Gig iSCSI connection between K2 Media Server and Ethernet switch.
• 8 Gig Fibre Channel connection for SAN between K2 Media Server and K2 10G RAID
storage.
• K2 Media Servers are 64-bit Windows Server 2008 operating system.
• Licensing of a single K2 Media Server provides multiple bandwidth levels without requiring
additional iSCSI interface adapters and K2 Media Servers. This leads to an overall system
simplification.
• K2 10G RAID for K2 client direct-connect — Provides 8 Gig Fibre Channel connection for
direct-connect between K2 client and K2 10G RAID storage.
• K2 Summit Transmission models — New SD and HD/SD models provide high value for
transmission and play-to-air solutions. All models support agile playback of DV/DCVPRO,
MPEG-2, SD and HD at bit rates up to 50Mbps. Channels for MPEG-2 record at up to 50Mbps
vary by model. Both SAN and stand-alone models are available. Stand-alone models offer 4 TB
and 16 TB storage.
In addition to these release notes, the following documentation is available for existing and new
systems with this version 7.3.8 release of software:
• K2 Documentation CD 063-8289-05 has been revised for use with this release of software.
• K2 Lx0 RAID Instruction Manual 071-8614-01. This manual has not been revised. Use this
manual for K2 Level 10-40 RAID storage (NEC Condor with 4 Gig D1 and D3 controllers).
• K2 10G RAID Instruction Manual 071-8778-00. This manual has been revised. Use this manual
for the new K2 10G RAID storage (NEC Condor with 8 Gig D4 controllers).
• K2 Storage Area Network Installation and Service Manual 071-8724-01. This manual has not
been revised. Use this manual for K2 Level 10-40 SAN systems (1 Gig TOEs and 4 Gig
controllers).
• K2 Storage Area Network Installation and Service Manual 071-8779-00. This manual has been
revised. Use this manual for K2 10G SAN systems (10 Gig TOEs and 8 gig controllers).
• K2 Storage Cabling Guide 071-8713-01. This manual has not been revised. Use this manual for
K2 Level 10-40 SAN systems (1 Gig TOEs and 4 Gig controllers) and K2 client direct-connect
storage with K2 Level 10-30 RAID storage (4 Gig controllers).
• K2 Storage Cabling Guide 071-8780-00. This manual has been revised. Use this manual for K2
10G SAN systems (10 Gig TOEs and 8 gig controllers) and K2 client direct-connect storage
with K2 10G RAID storage (8 gig controllers).
• Fibre Channel Switch Installation Manual 071-8713-02. This manual has been revised.
• K2 Summit/Solo Field Kit Upgrade Instructions 071-8721-01. This document has been revised.
Use it for all field kit upgrades.
• K2 AppCenter User Manual 071-8723-01, K2 System Guide 071-8726-01, Quickstart Guides,
and Service Manuals have not been revised. Use these manuals with this release of software,
with new features/changes as documented in these release notes.
8 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Not supported in this release
The following devices and functionality are not supported with 7.x versions of K2 software. Check
with your Grass Valley representative regarding availability.
• K2 Media Client — Compatible with 3.x versions of K2 software only.
Changes and features in previous releases
The following sections describe changes and features in past releases.
Version 7.2.7
• ChannelFlex Suite — Multiple inputs and outputs per channel are enabled by the AppCenter
Elite license. This license must be ordered from Grass Valley. The license is not included with
this version of software as a 30 day trial license. Refer to About introducing ChannelFlex Suite
on existing K2 systems on page 22 for more information. ChannelFlex Suite features are
summarized as follows:
Release Summary
• Super Slo-Mo — 2x and 3x frame rate record. Also requires HD license.
• Multi-Cam — Two SDI video inputs on a single channel.
• Video + Key — Record and playback.
• 3D — Left + Right eye. Record and playback.
• Super Out — This feature is enhanced with the display of additional information. Requires
AppCenter Pro license.
• K2 Summit Transmission Package — This model has 1 TB drives and is limited to DV and
MPEG formats at maximum 50 Mbps. Also limited to 1-IN/3-OUT or 4-OUT channel
configurations. Refer to the K2 System Guide for more information.
• K2 Dyno Replay Controller — The 1.6 Dyno software version is compatible with this release
of K2 software. Refer to compatibility information later in these release notes.
• AVC-Intra on K2 Solo Media Server — AVC-Intra 50/100 record/play is available on a K2
Solo Media Server as the K2-SOLO-ELITE model or as a field-kit upgrade.
• QuickTime AVC-Intra import — K2 storage supports import of QuickTime AVC-Intra. This
completes the AVC-Intra workflow, as export of QuickTime AVC-Intra is already supported.
• Nearline K2 SAN — The Nearline 120 redundant (NL120R) K2 SAN replaces the Nearline 10
and Nearline 10R K2 SAN. If using the K2 Storage Cabling Guide to cable the NL120R SAN,
the instructions for Nearline 10R apply.
• SNFS file system — Upgrade to version 3.5.2 is required.
• Compact Flash — The internal storage K2 system now supports multiple varieties of Compact
Flash for the system drive. To accommodate these varieties, when you re-image you must resize
partitions. Refer to your K2 product's Service Manual for instructions.
• K2 Dyno Production Assistant support — K2 Dyno PA can transfer a file from a stand-alone
K2 system to an Apple Xsan. The file can be edited while streaming. Also, on new systems and
if you make a new file system on existing systems, unique disk labels are created, which is
required for control by K2 Dyno PA. The disk labels and the file system name must be unique.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 9
Release Summary
Version 7.1.14
• Documentation – In addition to these release notes, use K2 Documentation CD 063-8289-04
April 2010 with this release of K2 software. The following manuals are revised:
• K2 Solo Media Server Service Manual 071-8709-01
• K2 Solo Media Server Quick Start Guide 071-8710-01
• K2 Storage Cabling Guide 071-8713-01
• K2 AppCenter User Manual 071-8723-01
• K2 Storage Area Network Installation and Service Manual 071-8724-01
• K2 Summit Client Service Manual 071-8725-01
• K2 System Guide 071-8726-01
• K2 Summit Client Quick Start Guide 071-8722-01
• AVC-Intra — AVC-Intra 50/100 record/play is available as an option or as a field-kit upgrade.
Requires HD license.
• P2 Import Capture Service — P2 material can be imported to K2 storage.
• QuickTime MPEG export/stream — The K2 system can export MPEG formats and stream
MPEG Long GoP.
• GPI — The commands Take Next Event, and Take Next Scheduled Event are supported.
• 4 GB USB Recovery Drive — A larger capacity recovery drive is available to ship on new
systems sometime after this release.
• K2 Summit drives — A new family of drives for K2 Summit Production Client internal storage
is available, with 600 GB and 450 GB capacities. 300 GB drives are no longer available.
• K2 Summit/Solo drive firmware — New systems have new drive firmware versions. If you
are upgrading an existing system, you must upgrade to the new version. Refer to compatibility
information later in these release notes.
• External storage drives — The Cheetah 7 family of drives for direct-connect and SAN storage
is available, with 600 GB, 450 GB, and 300 GB capacities. Larger drive capacities require
multiple LUNs per rank. For systems with multiple LUNs per RANK, expansion by bandwidth
is supported. Expansion by capacity is not supported.
• K2 Dyno Replay Controller — The 1.5 Dyno software version is compatible with this release
of K2 software. Refer to compatibility information later in these release notes.
• Event Scheduler — When licensed for Event Scheduler, the Event Monitor application is
available. This application is a monitor-only application that displays the list of events scheduled
in Event Server for a channel. The events must be scheduled by an application developed by a
third party application developer. There is Start menu item and desktop icon for licensing Event
Scheduler. Do not attempt to license Event Scheduler unless instructed to do so by Grass Valley
or your application developer.
• Documentation – In addition to these release notes, use either of following with this release of
K2 software:
• K2 Documentation CD – 063-8289-02 – November 2009
• K2 Documentation CD – 063-8289-03 – February 2010
Both CDs contain the same set of K2 Summit/SAN manuals that document this release of K2
software. K2 Documentation CD 063-8289-03 additionally provides a manual set for the 1.5
release of K2 Dyno software.
10 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Version 7.1.9
• MPEG-2 play — MPEG-2 Playback is a standard feature on all models, relative to current
licensing. MPEG-2 SD Playback is standard with or without the HD license. MPEG-2 HD
Playback is available only on systems that are licensed for HD.
• MPEG-2 record — MPEG-2 recording is a standard feature on MPEG models or as a field-kit
upgrade, relative to current licensing. MPEG-2 SD recording is standard with or without the HD
license. MPEG-2 HD recording is available only on systems that are licensed for HD.
• Solid State Disks — Solid State Disks (SSD) available.
• Super out — Timecode burn-in on monitor output. This is an AppCenter Pro feature.
• AFD support — Active Format Description (AFD) is supported for control of aspect ratio.
• Ancillary data — Support for SD ancillary data, including SD/HD data bridging.
• Capture services — The K2 Pathfire capture service and the K2 DG capture service are supported.
• Security — Based on Windows user accounts and groups, you can set permissions on bins and
on channels.
• SNFS — Upgrade to SNFS version 3.5.1 is required. With this version there is a change to SNFS
services, as displayed in the Service control panel. Also, on new systems and if you make a new
file system on existing systems, the name that Storage Utility creates for the SNFS volume (the
V: drive) is gvfs_hostname, where hostname is the name of the primary SNFS file system server.
• QuickTime update — Upgrade to QuickTime version 7.6 or higher is required.
• Licensing for K2 system software — When upgrading, version 7.1.9 K2 system software installs
with a 30 day trial license. You must obtain a permanent license from Grass Valley. When
upgrading to version 7.1.9, make sure that you carefully follow the upgrade and licensing
procedures later in these release notes, so that licensing features are correctly installed.
• 2910al series switch — A new Gigabit Ethernet switch, the “ProCurve Networking Switch
2910al Series” is qualified for use with K2 Storage Systems. Its use and configuration are the
same as the existing 2900 series switch, as documented in the K2 Storage Area Network
Installation and Service Manual.
• K2 Coder — The K2 Coder is supported on the K2 SAN. The K2 Coder compatible with this
version of K2 software does not have watch folders pre-configured, so you must create them
yourself, as documented in the K2 Storage Area Network Installation and Service Manual.
• Preroll setting — For mixed compression format playout (DV/MPEG/AVC-Intra), the preroll
is increased to 1 second. For same compression format playout, preroll remains at 10 frames.
This applies to AMP protocol, VDCP protocol, and Harris settings Disk Prerolls, Frames to send
Play early, and Frames to send Record early. These specifications supersede those in the K2
System Guide part number 071-8726-00.
Release Summary
Version 7.0.13
• K2 Media Servers — Dell PowerEdge R710 and R610 are supported as K2 Media Server
platforms.
• Live Production option — In K2Config, you can now create a Live Production K2 SAN. This
type of SAN has a shorter minimum delay between start record and start playout when the record
and play are on different SAN K2 Summit Production Clients. To support this feature, the K2
SAN must be sized for increased bandwidth. Contact your Grass Valley representative for
specifications relative to your needs.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 11
Release Summary
Version 7.0.12
Version 7.0.11
• K2 Dyno Reply Controller — For live event replay, the K2 Dyno Replay System includes a
K2 Dyno Controller and a K2 Summit Product Client.
• Final Cut Pro support — K2 FCP Connect is a licensable feature that allows your Macintosh
Final Cut Pro system to become a K2 SAN iSCSI client. This enables edit in place functionality
for K2 media via QuickTime reference files. Supports DV, IMX, HD, and XDCAM formats.
• K2 Summit Production Client — This new product is a SD/HD K2 client for replay in sports,
news, live, and live-to-tape applications. Its features are similar to the current K2 Media Client.
• Live Play — Extremely fast record-to-playout performance. Also known as Chase Play.
Playout to within ½ second of record point.
• DV formats — Supports the DV25, DV50, and DV100 (DVCPROHD) P2 acquisition formats
natively. Does not support MPEG.
• Transition effects — Dissolves and audio fades can be assigned to clip playout transitions.
This is an AppCenter Pro feature.
• Graphical User Interface design — AppCenter has a gray/brown color scheme with improved
buttons and fonts.
• Media file system — The file system with this release allows nested bins for better media
management and is supported on the K2 Summit Production Client only. It is not supported
on the K2 Media Client.
• Write filter — A file-based write filter prevents accidental or unintended changes. It must
be disabled before changes are made and enabled after changes are made.
• Metadata server role — The role of metadata server replaces the role of media database
server for a K2 Media Server. The metadata server role is required to support the media file
system with this release.
• AppCenter Video Monitor — Active video is provided on a locally connected VGA monitor
for AppCenter channels. You can also select the AppCenter view to display a four pane active
video monitor of all four channels. This is an AppCenter Pro feature.
• Modular channels — Codec and real-time functionality is combined on a two channel
module, allowing for two and four channel options.
• CompactFlash — The system drive is CompactFlash.
12 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Additional notes
The following sections contain additional information about this release.
Using reference files
When you create a simple K2 clip on a K2 system, K2 software can create a corresponding reference
file. The reference file is stored in a directory in the clip's folder on the V: drive. You can configure
the software to create QuickTime reference files, MXF reference files, or no reference files. The
following topics provide information about reference files on K2 systems.
About QuickTime reference files
For QuickTime reference files, the K2 clip must be a DV, AVC-Intra, XDCAM-EX, XDCAM-HD,
XDCAM-HD 422, or IMX format simple clip in order to create the reference file. With the QuickTime
reference file you can open the K2 clip with QuickTime tools, such as Final Cut Pro, for playback
and editing. The QuickTime tool must be run on another system. Running the QuickTime player or
other QuickTime tools on the K2 system is not supported. You have options for connections, access,
and software to support your workflow requirements.
About MXF reference files
For MXF reference files, the K2 clip can be any supported format simple clip. K2 software creates
the MXF reference file when you create a new simple clip by recording, importing, or copying. K2
software does not create the MXF reference file when you create a playlist, a program with
continuous-recorded material, or a clip with tracks having a duration less than the clip duration. The
reference file is a MXF OP1b file with external essence. The reference file gives you options for
connections, access, and software to support your workflow requirements.
Configuring reference file type on a stand-alone K2 system
1. In AppCenter, click File | System | Configuration.
Configuration Manager opens.
2. In Configuration Manager, click the System tab.
3. In Reference Files settings, for the Reference file type setting, select one of the following:
• None — K2 software does not create reference files.
• QuickTime — K2 software creates QuickTime reference files.
• MXF — K2 software creates MXF reference files.
4. Click OK to apply the setting.
5. Restart the stand-alone K2 system to put the change into effect.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 13
Additional notes
Configuring reference file type on a K2 SAN system
1. In the K2Config application, for the K2 Media Server with role of file system server, access the
File System Server Configuration page as follows:
• On a SAN that is already configured, in the tree view click File System Server.
• On a SAN that is not yet fully configured, work through the Configure K2 Server wizard until
you reach the File System Server Configuration page.
2. On the File System Server Configuration page select one of the following:
• No reference file — K2 software does not create reference files.
• QuickTime reference file — K2 software creates QuickTime reference files.
• MXF reference file — K2 software creates MXF reference files.
3. Click Check to apply the setting.
4. Manage the required K2 Media Server restart as follows:
• On a SAN that is already configured, you must restart the K2 Media Server to put the change
into effect. Follow the restart procedure appropriate for the basic or redundant K2 SAN.
• On a SAN that is not yet fully configured, continue to work through the Configure K2 Server
wizard. The restart at the end of the configuration process is sufficient.
If a redundant K2 SAN, you must configure similarly and restart both K2 Media Servers with role
of file system server.
Using the Export capture service
The following topics provide information for the Export capture service.
About the Export capture service
The Export capture service provides a way to have media automatically exported from a K2 system.
The capture service has a watched bin. The watched bin is a K2 storage system bin. You place the
media in the bin and it is exported from the K2 system.
You configure the watched bin to export the K2 media as your desired clip format. After you place
the K2 clip in the watched bin, the capture service goes into action and validates the media to make
sure it has the proper structure for the desired file format. If it is valid, the capture service then does
the necessary processing to export the clip to the destination folder.
The Export capture service and its watched bin must be on a K2 system that hosts the K2 FTP
interface, as follows:
• Stand-alone K2 system — When you place a K2 clip in the watched bin, the capture service
exports the clip from the internal storage or direct-connect media storage of the K2 system. The
watched bin must be on the K2 system’s V: drive.
14 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
• K2 Media Server with role of FTP server — When you place a K2 clip in the watched bin, the
capture service exports the clip from the shared media storage of the K2 SAN. The watched bin
must be on the K2 Media Server’s V: drive.
Prerequisites for using the Export capture service
Before you can configure and use the Export capture service, the following requirements must be
satisfied:
• The K2 system must support the clip format you plan to export. This could require specific
hardware and/or licenses.
• K2 system software must be at a version that supports the Export capture service. Refer to K2
Release Notes for information on Export capture service version compatibility.
• The capture service must be licensed on the stand-alone K2 system or K2 Media Server. This is
a Grass Valley software license.
Use topics in this section as appropriate to satisfy prerequisites.
Considerations for using the Export capture service
Additional notes
When you are configuring and using the Export capture service, bear in mind the following
considerations:
• You must be logged in with administrator privileges on the stand-alone K2 system or the K2
Media Server as well as having the appropriate security permissions to access the watched folder
or bin.
• If you have multiple source folders (for import) or destination folders (for export) on external
systems, use the same user account for all capture service access to all systems.
• If using the export capture service on a K2 SAN, the K2 Capture Services utility must be on a
K2 Media Server that is also an FTP server. If your K2 SAN has multiple FTP servers, the utility
must be on the primary FTP server.
Configuring the Export Capture Service
1. From the Start menu, access the Programs menu and select Grass Valley | K2 Capture Services.
If the write filter is enabled, a message appears that informs you about the write filter and prompts
you to restart.
2. If the write filter is enabled, restart as prompted, then repeat previous steps.
The K2 Capture Services utility dialog box is displayed.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 15
Additional notes
3. Click the HotBin Export tab.
4. Select Use HotBin Export.
If you have not yet licensed the HotBin Export capture service, a “…start the process of getting
a license now?” message appears. Follow on-screen instructions to obtain a license. After licensing,
restart the K2 Capture Services utility and continue with this procedure. Make sure the write
filter is disabled.
5. Select the number of streams.
Exports run serially. If you select one stream, only one export can occur at a time. If you select
multiple streams, multiple exports can occur at one time.
16 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
6. Click Add.
The Export Rule dialog box opens.
Additional notes
7. Configure as follows:
• Source K2 Bin Name — Required. This is the watched bin. The bin must be on the K2 system’s
V: drive. It must be in the K2 media database and appears in AppCenter as a media bin. When
valid clips are placed in this bin, the HotBin Export capture service automatically exports the
clips.
• Include Sub-Bins — Optional. When selected, clips are exported if they are in a bin nested
inside the Source K2 Bin.
• Rule — Do not configure this field. Leave the default value as it is.
• Destination Folder Path — Required. This is a standard file system directory. It receives the
files/directories exported by the Export capture service. If you specify a destination folder
that does not yet exist, the K2 system creates it when exporting. If the destination folder is
not on the local K2 system, you are prompted to enter user account credentials to access the
source directory. If part of a domain, enter the domain name.
NOTE: You must use the same user account for all capture service access to all systems.
• File Type — Required. Select the file format in which K2 clips are exported.
• Option — Do not configure this field. Leave the default value as it is.
8. Click OK to save settings and close the Export Rule dialog box.
9. Repeat previous steps to add additional Export HotBins.
10. When your capture service settings are complete, click Apply.
A message appears that informs you about the write filter and prompts you to restart.
11. Click OK.
The K2 system restarts.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 17
Additional notes
Testing the Export Capture Service
Export capture service components
1. Place the clips to export into the watched bin.
2. Verify that the media appears in the destination.
3. Play to verify success.
The following table describes the components that support Export capture service functionality.
DescriptionName
Grass Valley Import Service
Source K2 bin
Destination folder
MXF interchange specification
This specification applies to MXF file transfer, import, and export on K2 Summit, Solo, and SAN
systems.
MXF does not support multiple video tracks, such as 3D/Video + Key.
Formats are supported are as follows:
This is the service that provides the functionality for the capture
service. It is the service that automatically exports K2 clips from
the K2 media storage.
Configures K2 capture services.K2 Capture Services utility
This is the watched bin. It is a bin in K2 media storage. When
files are placed in this directory, the capture service automatically
exports them from K2 media storage.
The folder that receives the files exported from the K2 media
storage.
NotesSupported formats
—DVCPRO25Video
DVCPRO HD
D10
MPEG-2
18 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
—DVCPRO50
Super Slo-Mo requires software version 7.1.
x or higher
—DVCAM
See MXF export behavior for eVTR style
D10AES3.
Includes all MPEG-2 formats (IMX,
XDCAM, etc.) that can be stored on a K2
system
—AVC-Intra
—48 kHzAudio
Additional notes
NotesSupported formats
—16 bit, 24 bit
—PCM, Dolby-E, AC-3
VBIData
MXF supports either ancillary data packets
or VBI lines in the data track but not both,
so if ancillary data packets and VBI lines
have been recorded into the K2 clip’s data
track, then the VBI lines will be dropped
from the MXF data track on an MXF export.
—Ancillary
Interchange mechanisms are supported as follows:
SupportMechanism
YesImportFile based
YesExport
YesImportFTP stream
YesExport
You can export a completed continuous (loop) record clip as MXF or QuickTime, with the result
being a flattened stream file. Recording must be complete before you export the clip, however you
can make sub-clips while record is underway and export the sub-clips. For this feature, MPEG-2
long GoP is not supported.
MXF export behavior on K2 systems
Upon MXF export the K2 system checks media for specifications as they apply to industry standard
formats such as XDCAM and eVTR style D10AES3. If specifications match, the media is exported
as the appropriate format.
The K2 system allows you to alter clips so that they no longer match the specifications for the
industry-standard format. For example, you can add audio tracks to exceed the “# of Audio Tracks”
specification. If you alter a clip in this way, on MXF export the K2 system exports the clip but it is
not compatible with the industry-standard format.
QuickTime interchange specification
This specification applies to QuickTime file transfer, import, and export on K2 Summit, Solo, and
SAN systems.
Formats are supported are as follows:
NotesSupported formats
—DVCPRO25Video
—DVCPRO50
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 19
Additional notes
NotesSupported formats
DVCPRO HD
Super Slo-Mo requires software version 7.1.
x or higher
—DVCAM
—AVC-Intra
—D10/IMX
—XDCAM-HD
—XDCAM-EX
—XDCAM-HD422
48 kHzAudio
16 bit, 24 bit PCM
Audio tracks handled as stereo pairs on
export
—NoneData
Interchange mechanisms are supported as follows:
SupportMechanism
YesImportFile based
YesExport
NoImportFTP stream
NoExport
You can export a completed continuous (loop) record clip as MXF or QuickTime, with the result
being a flattened stream file. Recording must be complete before you export the clip, however you
can make sub-clips while record is underway and export the sub-clips. For this feature, MPEG-2
long GoP is not supported.
QuickTime video and key import specification
This specification applies to importing a QuickTime file with two video tracks for video and key
playout. This is a licensed feature.
The imported file must be QuickTime 32 with alpha RLE 32-bit raster encoding, as produced by
the Apple Animation Codec.
Supported video formats for import are as follows:
Frame RateScanFormat
29.97Interlaced720 x 480SD video
29.97Interlaced720 x 512
25Interlaced720 x 576
25Progressive720 x 608
20 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
29.97, 25Interlaced1920 x 1080HD video
Supported audio formats for import are as follows:
Format
Mono or stereo48 kHzAudio tracks
(if present)
16 bit, 24 bit
PCM
Interchange mechanisms are supported as follows:
SupportMechanism
YesImportFile based
NoExport
NoImportFTP stream
Additional notes
Frame RateScanFormat
59.94, 50Progressive1280 x 720
When K2 software imports a file that meets the above requirements, it creates a K2 clip with two
video tracks, in formats as follows:
HD video
100
100
Audio tracks, if present are imported.
Timecode data is imported as K2 striped timecode. The first timecode value is the starting value
and subsequent timecode is continuous.
The import process consumes system resource. Be aware of this if running other resource intensive
processes during import.
P2 interchange specification
NoExport
Data RateFrame RateFormat
50 CBR29.97720 x 512D10/IMXSD video
50 CBR25720 x 608D10/IMX
100 Mbps29.97, 251920 x 1080AVC-Intra
100 Mbps29.97, 251280 x 720AVC-Intra
This specification applies to P2 file transfer, import, and export on K2 Summit, Solo, and SAN
systems.
Formats are supported are as follows:
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 21
Additional notes
NotesSupported formats
Directory structure as specified by P2AVC-IntraVideo
DVCPRO25
DVCPRO50
DVCPRO HD
DVCAM
48 kHzAudio
16 bit, 24 bit PCM
Interchange mechanisms are supported as follows:
SupportMechanism
YesImportFile based
YesExport
NoImportFTP stream
NoExport
About introducing ChannelFlex Suite on existing K2 systems
When you upgrade to a K2 system software version that supports ChannelFlex Suite and then begin
to use ChannelFlex Suite features, you increase the number of inputs and outputs on the K2 system.
To support this increased load on system resources, you must adjust your system, as follows:
• Stand-alone K2 systems – This includes internal storage K2 Summit Production Clients,
direct-connect storage K2 Summit Production Clients, and K2 Solo Media Servers. These system
require an updated RTIO setting. You must update this setting when you upgrade.
• K2 SANs – These system might require additional disks for bandwidth and additional K2 Media
Servers to act as iSCSI bridges (TOEs), depending on the number and type of inputs and outputs
you are adding by your use of ChannelFlex Suite features. Contact your Grass Valley
representative to evaluate your system and its suitability for supporting your use of ChannelFlex
Suite.
22 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Codec option matrix
Standard and optional codec functionality is specified in the following table. You can order codec
functionality on a new system as an option or add it to an existing system as a field kit upgrade.
Codec options
Additional notes
DV
HDSDOption
encode
MPEG card
AVC-Intra card
Product nomenclature for options
Option
With MPEG card
With HD license and MPEG card
K2 Summit Production Client
nomenclature
K2-XPD-4SD-MPG
K2-XPD-4HD-MPG
DV
decode
MPEG
encode
MPEG
decode
XXXXStandard
XXXXXWith HD license
XXXXXWith MPEG card
XXXXXXWith HD license and
K2 Solo Media Server
nomenclature
NAK2-XDP-2SD, K2-XPD -4SDStandard
K2-SOLOK2-XDP-2HD, K2 -XPD-4HDWith HD license
NAK2-XDP-2SD-MPG,
K2- SOLO-MPEGK2-XDP-2HD-MPG,
AVC-I
encode
AVC-I
decode
XXXXXXXWith HD license and
With HD license and AVC-Intra card
Managing the write filter
The following topics describe the K2 Summit Production Client and K2 Solo Media Client write
filter.
About the write filter
The K2 Summit Production Client and K2 Solo Media Server have a file-based write filter, which
is a feature of the Windows embedded operating system. With the write filter enabled, files can be
created, modified, and deleted, but these changes are held in a memory cache. When the K2 system
restarts, these changes are lost and the K2 system returns to its original state. This protects the K2
system from changes and increases on-air reliability. For any system configuration change the write
filter must be disabled otherwise changes are lost at the next restart.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23
K2- SOLO-ELITEK2-XDP-2HD-AVCI,
K2-XPD-4HD-AVCI
Additional notes
Local software installation and the write filter
Some directories, such as C:\logs, C:\Profile\config, and C:\Profile\ChannelSuites, are
excluded from write filter protection, so that channel configuration and logs are saved. Do not
attempt to alter this list of excluded directories. If you suspect that write filter configuration has
been altered, use the recovery image process to restore to the default configuration.
To enable the write filter, the K2 Summit Production Client or K2 Solo Media Server must be
restarted. Likewise, to disable the write filter, the K2 system must be restarted. You can enable/disable
the write filter remotely using the SiteConfig lock/unlock feature on one K2 system at a time or on
a group of K2 systems all at once. You can also enable/disable the write filter from a local K2
system, but if you use the local method, do not also use the SiteConfig method. If you enable/disable
the write filter locally, the change is not automatically sent to SiteConfig, so SiteConfig can not
reliably indicate the current lock/unlock state.
When you manually install K2 client software at the local K2 Summit Production Client or K2 Solo
Media Server, the installation program helps you manage the write filter. Both the uninstall program
and the install program have the same behavior. When you run either the uninstall or the install
program, the program behaves as follows:
• If the write filter is enabled, the program notifies you and sets the writer filter to disabled, then
prompts you to restart. To continue the uninstall or install process, you must restart and then run
the program again, this time with the write filter disabled.
• If the write filter is disabled, the program sets it to be enabled so that after next restart the K2
system starts up with the write filter enabled.
In this way the write filter is disabled while software is installed. Changes made to system settings
or to the system drive before the restart following an install are preserved.
Once you have uninstalled or installed K2 Client software, at the next restart the write filter is
enabled. If you want to keep the write filter disabled after an install, run the Write Filter Utility and
disable the write filter before restarting.
SiteConfig software installation and the write filter
When you use SiteConfig to install K2 client software on a K2 Summit Production Client or K2
Solo Media Server, SiteConfig helps you manage the write filter. The SiteConfig "Lock" feature
enables the write filter and the "Unlock" feature disables the write filter. In addition, both uninstall
deployment tasks and install deployment tasks behave the same way in how they manage the write
filter, as follows:
• If the write filter is enabled (the K2 system is locked), SiteConfig does not allow the task to be
deployed. To deploy software, you must first disable (unlock) the write filter on the K2 system.
• If the write filter is disabled (the K2 system is unlocked), when the deployment task completes
SiteConfig keeps the write filter disabled. If you then restart the K2 system, the write filter is
still disabled after the restart. This allows you to deploy additional software.
When you are finished deploying software, use SiteConfig to enable (lock) the write filter on the
K2 system.
24 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Disable write filter
1. If you have not already done so, log on to the K2 system with Windows administrator privileges.
2. From the Windows desktop, click Start | All Programs | Grass Valley | Write Filter Utility.
FBWF Manager opens.
3. Under Filter Settings, set Filter to Disable.
Do not modify other settings.
4. Click OK.
5. When prompted, restart the K2 system.
Enable write filter
1. If you have not already done so, log on to the K2 Summit Production Client or K2 Solo Media
Server with Windows administrator privileges.
2. From the Windows desktop, click Start | All Programs | Grass Valley | Write Filter Utility.
FBWF Manager opens.
Additional notes
3. Under Filter Settings, set Filter to Enable.
4. Under Protected Volumes, set C: to Protected.
Do not modify other settings.
5. Click OK.
6. When prompted, restart the K2 Summit Production Client or K2 Solo Media Server.
Passwords and security on K2 systems
To provide a basic level of security, K2 systems recognize four different security levels based on
Windows users and groups, and the systems ship from the factory with accounts pre-configured
accordingly. To access the system you must login with the username and password for one of the
pre-configured accounts.
The following table shows the different types of K2 users and their privileges. Passwords are case
sensitive. The term “unknown user” applies to any user who logs in to the K2 System without using
the Windows administrator, K2 administrator, or K2 user login and password
administrator
Unknown userK2 userK2 administratorWindows
1
K2UserK2AdminAdministratorLogin
N/A
1
The unknown user, like all others who access the K2 system, must have a valid Windows login for the K2 client or the
control point PC through which the K2 system is being accessed.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 25
N/AK2userK2adminadminK2Password
Additional notes
Unknown userK2 userK2 administratorWindows
administrator
Can’t accessCan viewFull accessFull accessAppCenter
Configuration
Manager
Full accessFull accessAppCenter
Full accessWindows
Operating System
Limited access
(based on
Windows login
privileges)
To support FTP and security features, K2 systems also have movie, mxfmovie, and mpgmovie
accounts. Do not use these accounts to log in to the Windows operating system on K2 systems.
About application security on the K2 SAN
The K2Config application and the Storage Utility application both require that you be logged in to
the application with administrator privileges in order to modify any settings. These privileges are
based on the Windows account that you use when you log in to the K2Config application. When
you open Storage Utility from within the K2Config application, the account information is passed
to Storage Utility, so you do not need to log in separately to Storage Utility.
Full access;
requires an
account on the K2
Media Client(s)
Limited access
(based on
Windows login
privileges)
Can view channel
suites, channel
status, on-line help
and System Status
pane. Can export
logs.
Can’t accessCan’t accessFull accessFull accessStorage Utility
Can’t accessCan’t accessFull accessFull accessK2Config
Limited access
(based on
Windows login
privileges)
In SiteConfig you configure global and/or device-type credentials for device access. These credentials
are likewise based on Windows accounts.
You must use a Windows account that has local administrator privileges on the machine to be
configured. For example, when you are on a control point PC and you run the K2Config application
for the purpose of configuring a K2 Media Server, the account with which you log in to the K2Config
application must be present on the K2 Media Server and must have administrator privileges on the
K2 Media Server.
By default, all K2 SAN machines are set up with the following accounts:
Administrator
26 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
PasswordUsernameAccount
K2 Configuration
permissions
Storage Utility
permissions
Run/changeRun/changeadminK2AdministratorWindows
Run/changeRun/changeK2adminK2AdminK2 Administrator
No accessNo accessK2userK2UserK2 User
Additional notes
For initial setup and configuration, you can use the default Windows Administrator username and
password to log in to applications and machines as you work on your K2 SAN. However, for ongoing
security you should change the username/password and/or create unique accounts with similar
privileges. When you do this, you must ensure that the accounts are present locally on all K2 SAN
machines, including control point PCs, K2 Media Servers, K2 Media Clients, K2 Summit Production
Clients, and other iSCSI clients.
NetCentral also has accounts for security levels, as follows:
• NetCentral Administrator
• NetCentral Technician
• NetCentral User
Grass Valley recommends mapping the NetCentral administrator with the K2 administrator level.
If you are using the Grass Valley Control Point PC, this mapping is already done for you at the
factory, so you can log on to NetCentral as administrator using the K2 administrator
(K2Admin/K2admin) logon. You can also assign other NetCentral groups to users, as necessary for
your site’s security policies. You need Windows administrator privileges to add or modify a user’s
privileges. For more information on NetCentral security, see the NetCentral User Guide.
About credentials in SiteConfig
SiteConfig requires administrative privileges on devices in order to perform most of the network
configuration and deployment tasks. If you add a device based on a known device type, SiteConfig
knows the default administrator login and password to use. Then, when you use remote desktop or
perform software deployment to the device, SiteConfig automatically uses these credentials. These
credentials are called "global" credentials for the device since the same credentials are used on all
devices of that type in the system.
You can choose to override the default credentials for a given device type. For example, if you have
specified a different administrator account or a different password on the devices when commissioning
the system, then you want SiteConfig to use these modified credentials.
It is possible to also override the default credentials for a single device.
Upgrading firmware on HP switch
1. If you have not already done so, install a TFTP Server.
For example, to install tftpd32.exe, go to http://tftpd32.jounin.net/.
2. Open the TFTP Server.
3. Make sure your current working directory includes the *.swi file that you are using for the
upgrade.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 27
Additional notes
4. Execute the copy command with the following syntax:
copy tftp flash <ip-address> <remote-os-file> [ < primary | secondary
> ]
Note that if you do not specify the flash destination, the TFTP download defaults to the primary
flash.
For example, to download a software file named T_13_23.swi from a TFTP server with the IP
address of 10.16.34.3 1, use the following:
ProCurve # copy tftp flash 10.16.34.3 T_13_23.swi
5. When prompted The primary OS image will be deleted. continue [y/n]?, press
Y.
When the switch finishes downloading the software file from the server, it displays the progress
message Validating and Writing System Software to FLASH...
6. Wait until the CLI prompt re-appears, then continue with the next step in this procedure.
7. Check the version of firmware on the switch. To do this, type the following, then press Enter:
show flash
Information is displayed similar to the following example:
HP_iSCSI_switch1# show flash
Image Size(Bytes) Date Version
----- ---------- -------- ------Primary Image : 6737518 07/25/08 T.13.23
Secondary Image : 5886358 10/26/06 T.11.12
Boot Rom Version: K.12.12
Current Boot : Primary
8. Verify that the new software version is in the expected flash area (primary or secondary).
9. Restart the switch from the flash area that holds the new software (primary or secondary).
Configuring QOS on the GigE switch
Prerequisites for this procedure are as follows:
• The switch is HP ProCurve switch 29xx series.
• Trunks, VLANs and all other configuration is complete.
• The switch has an IP address
• You have network access to the switch
Use this procedure to make the Quality of Service (QOS) setting on the HP ProCurve switch 29xx
series.
1. If you have not already done so, from a network connected PC open the MS-DOS command
prompt and login to the switch as administrator, as follows:
a) Telnet to the switch. For example, if the switch’s IP address is 192.168.40.12, you type the
following, then press Enter.
telnet 192.168.40.12
b) Press Enter one or more times until the switch’s username prompt appears.
c) Type the switch’ s administrator username and press Enter, then type the switch’ s administrator
password and press Enter. The switch console command (CLI) prompt appears.
28 K2 Version 7.3.8 Release Notes & Upgrade Instructions 23 November 2010
Additional notes
2. Type the following, then press Enter:
config
You are now in configuration mode.
3. Type the following, then press Enter:
qos queue-config 2-queues
This limits the number of active queues within the switch giving the most buffering to VLANs
1 and 60
4. Type the following, then press Enter:
show qos vlan
The screen displays VLAN information. Note the ID number of the Media (iSCSI) VLAN. It
should be 60, as follows:
VLAN priorities
VLAN ID Apply rule | DSCP Priority
------- ----------- + ------ ---------- 1 No-override | No-override
60 No-override | No-override
5. a) Assign the Media VLAN the QOS priority of 3. For example, if the VLAN ID is 60, you type
the following, then press Enter.
vlan 60 qos priority 3
b) Type the following, then press Enter:
show qos vlan
The screen displays VLAN information. Make sure that the Priority column reports that the
Media VLAN has a value of 3.
Next, verify flow control settings.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 29
Operation considerations
• Do not neglect to make a “first birthday” image of each K2 product shortly after installation and
configuration is complete.
• Changing system video standards (NTSC/PAL) requires a restart as part of the channel changes
as soon as the new standard is selected. Configuration Manager causes an immediate restart of
the K2 client if the system reference standard is changed and AppCenter is being used.
• Refer to the “Remote control protocols” appendix in the K2 System Guide for operation
considerations related to AMP, VDCP, BVW, Harris, RS-422, etc.
• To import/export between systems using AppCenter, in Configuration Manager on the Remote
tab, add each system that you want to have available as a source or a destination. Do this for K2
systems as well as non-K2 systems, such as Profile XP.
• When transferring between K2 systems and other types of systems, such as Profile XP, you must
specify the IP address, path, and file name to initiate a transfer.
• Constrain media names and filepaths for support across systems. For example, on a K2 Summit
Production Client, AppCenter allows you to create bin names and clip names longer than 32
characters. However, names of this length are not supported on Aurora products.
• Tri-level sync is not supported on K2 systems.
• Before configuring audio tracks on a channel, eject all clips. This is required to put changes into
effect.
• The K2 client and K2 Media Server can operate continuously for a long period of time, but the
recommended operational practice is to restart at least once every three to six months.
• When restoring from a system-specific recovery image (an image you have created from your
K2 system or the image on your K2 system's USB recovery flash drive), follow the procedure
in the K2 product's service manual. When restoring from a generic recovery image (a baseline
image for the K2 product), you must also restore network configuration, install K2 software,
install SNFS software, and make a new file system.
• Mix effects (an AppCenter Pro feature) are supported as follows:
• Supported between like compression formats: DV-to-DV, MPEG-to-MPEG, etc.
• Not supported between between different compression formats.
• Not supported for MPEG long GoP.
• A 3D/Video+Key player channel does not support agile play, mix effects, or a two-head player
model.
• On a K2 Solo Media Server, before making a new file system, first upgrade drive firmware to
the latest version, as specified in Compatible K2 Summit/Solo components on page 31. Failure
to do so generates a Storage Utility error.
• Grass Valley recommends that you use a frame synchronizer on incoming video sources that are
recorded in AVC-Intra format.
• If Dyno PA connects to an internal storage K2 system, there are special requirements for media
disk labels. Refer to the Dyno Production Assistant Configuration Manual.
• When configuring editors on a K2 SAN with 1 Gig TOEs, do not assign editors and K2 clients
(K2 Summit or K2 Media Client) to the same TOE. Instead, assign editors to their own TOE.
• To export AVI format files to a shared CIFS drive, first export to the local disk, then copy the
file to the share.
23 November 2010 K2 Version 7.3.8 Release Notes & Upgrade Instructions 30
Loading...