Avid® ISIS® 7000Version 2.2.2 ReadMe

Date Revised Release Changes Made

9/16/2010 v2.2.2 Avid ISIS v2.2.2 corrects several reported issues. This release is a full infrastructure and client release. For details, see “New in Version 2.2.2” on page 10.

Avid has lifted the restriction on separating Apple® Final Cut Pro® data and Avid editor data.

8/5/2010 v2.2.1 Avid Unity ISIS has been renamed to Avid ISIS 7000. Name changes are only in the documentation and software interface changes are planed in a future release.

A virus protection statement has been added, see “Virus Protection” on page 46.

7/20/2010 v2.2.1 Avid ISIS v2.2.1 fixes an issue that was introduced in Avid ISIS v2.1.1. This release is a Windows® client release and is only supported in Avid ISIS v2.1.1 and v2.2 infrastructures. For details, see “New in Version 2.2.1” on page 11.

7/20/2010 v2.2 Added details on why v2.2 is an important update regarding an issue previously found with the Avid ISIS System Director. A combination of updates resolve this issue. For details, see “New in Version 2.2” on page 13.

Documented another fixed issue in v2.2 regarding the AirSpeed® and Low Res Encoder not previously mentioned, see page 26.

5/27/2010 v2.2 This release adds support for Windows® 7 clients and Macintosh® 10-Gb Ethernet connections for ultra high resolution clients (UHRC). For details, see “New in Version 2.2” on page 13.

In addition, Avid ISIS v2.2 client software now supports uncompressed RGB resolutions. For details, see “Client Support for RGB Resolutions” on page 17.

1/05/2010 v2.1.1 Avid has completed its characterization of Apple® Final Cut Pro® on RAID workspaces in an Avid ISIS v2.1.1 shared storage environment, see “Final Cut Pro Software Approved” on page 43. For information on how many streams were qualified per client at various resolutions, see the Avid ISIS v2.1.1 Performance and Redistribution Guide on the Knowledge Base at www.avid.com/support

A note was added pointing out that when the File Gateway is configured as a CIFS server, the maximum number of workspaces that can be shared out as a CIFS share is 22 workspaces. For details see “Avid ISIS File Gateway” on page 28.

2

Important Information

Avid® recommends that you read all the information in this ReadMe file thoroughly before installing software or attempting to use the Avid ISIS system. This ReadMe provides information that is not in the other Avid ISIS documentation.

n Search the Avid Knowledge Base for the most up-to-date ReadMe file, which contains the latest information that might have become available after the documentation was published. To view the online version, visit the Knowledge Base at www.avid.com/readme.

This document provides hardware and software requirements, a hardware overview, and other important information. This document also lists limitations and known issues. Physical connection of the system and loading of the system and client software is explained in the Avid ISIS 7000 Setup Guide. You can access the documentation in the top-level AvidUnityISISDocumentation folder on the Avid ISIS software installer DVD.

c Avid strongly recommends that you purchase installation services with your Avid ISIS system. Installing the Avid ISIS system yourself could void your warranty.

3

Contents

Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Product Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

If You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Accessing the Online Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

New in Version 2.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Apple and Avid Media in the Same Storage Group. . . . . . . . . . . . . . . . . . . . . . 10

Fixed In This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

New in Version 2.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Upgrade Instructions for v2.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Fixed In This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

New in Version 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Windows 7 Client and Internet Explorer 8 Support . . . . . . . . . . . . . . . . . . . . . . 13

Intel Pro Driver Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

New 10-Gb Board for Windows and Macintosh Clients . . . . . . . . . . . . . . . . . . 14

Installing the Myricom Board on Macintosh Clients . . . . . . . . . . . . . . . . . . 15

Installing the Myricom Board on Windows Clients . . . . . . . . . . . . . . . . . . . 15

Client Support for RGB Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Windows Client Captures Qualified on RAID Workspaces . . . . . . . . . . . . . . . . 17

Intel Network Driver and BIOS Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

64-bit System Director BIOS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Record IP Addresses on the System Director . . . . . . . . . . . . . . . . . . . . . . 18

Update Intel Driver on the System Director . . . . . . . . . . . . . . . . . . . . . . . . 18

Intel RAID Controller Driver Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

System Director Recovery DVD Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Fixed In This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

New in Version 2.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

RAID-6 Storage Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

RAID-6 Storage Groups, Single ISB Failure. . . . . . . . . . . . . . . . . . . . . . . . 28

RAID-6 Storage Groups, Dual ISB Failure . . . . . . . . . . . . . . . . . . . . . . . . . 28

Avid ISIS File Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4

Automatic Redistribution on Disk Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

New System Director Recovery DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Change in Order for Components for System Upgrades. . . . . . . . . . . . . . . . . . 31

Full Upgrade Instructions for v2.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Macintosh Snow Leopard Client Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Upgrades for v1.4 and Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Application Key Driver Update on the System Director . . . . . . . . . . . . . . . . . . . 34

Enabling Windows Updates on 64-Bit System Directors . . . . . . . . . . . . . . . . . . 36

Avid Interplay Media Indexer and AirSpeed Multi Stream Patch . . . . . . . . . . . . 37

Upgrading Unstacked Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Intel Pro 1000 Boards and Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Loading or Updating the Intel Pro Driver on Windows Clients . . . . . . . . . . 40

Dell Precision T3500 Integrated Network Port Not Supported . . . . . . . . . . 40

HP Z400 and HP Z800 Integrated Network Port Not Supported . . . . . . . . 40

Chelsio 10 Gb Board and Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

HP xw8600 Workstations and Broadcom Ethernet Connections. . . . . . . . . . . . 42

Layer 2 and Layer 3 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Final Cut Pro Software Approved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Special Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

User Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Client Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Fast User Switching Not Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Virus Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Avid ISIS v2.x Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

System Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Storage Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Storage Group Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chunk Size Support With ISB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Mirrored Storage Groups, Single ISB Failure . . . . . . . . . . . . . . . . . . . . . . . 48

Adding or Removing ISBs (Mirrored or RAID) . . . . . . . . . . . . . . . . . . . . . . 48

Adding an ISB to the File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Zone 1 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5

Full Redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Firmware Upgrade During a Redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Avid Interplay Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Workspace Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Macintosh Dual Port Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Avid ISIS 7000 IP Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Minimum Storage Space Requirement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Enabling the Distributed File System on Windows Vista . . . . . . . . . . . . . . . . . . 52

Spanning Tree PortFast Required with Dual Network Client Ports . . . . . . . . . . 53

Broadcom-Based Network Adapter Registry Key Setting . . . . . . . . . . . . . . . . . 53

Old Intel Driver On DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Replacing an Internal System Director Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Loading the System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Installing Macintosh Client Software Using Safari . . . . . . . . . . . . . . . . . . . . . . . 55

Changing the Default Drive for the System Director Software . . . . . . . . . . . . . . 55

Drivers and Installers Available on DVD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Flash Player Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Performance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Legal Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

6

Symbols and Conventions

Avid documentation uses the following symbols and conventions:

Symbol or Convention Meaning or Action

n A note provides important related information, reminders, recommendations, and strong suggestions.

c A caution means that a specific action you take could cause harm to your computer or cause you to lose data.

w A warning describes an action that could cause you physical harm. Follow the guidelines in this document or on the unit itself when handling electrical equipment.

> This symbol indicates menu commands (and subcommands) in the order you select them. For example, File > Import means to open the File menu and then select the Import command.

This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.

(Windows), (Windows only), (Macintosh), or (Macintosh only)

This text indicates that the information applies only to the specified operating system, either Windows or Macintosh OS X.

Bold font Bold font is primarily used in task instructions to identify user interface items and keyboard sequences.

Italic font Italic font is used to emphasize certain words and to indicate variables.

Courier Bold font Courier Bold font identifies text that you type.

Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the mouse action. For example, Command+Option+C or Ctrl+drag.

Product Terminology

7

Product Terminology

The major components used to create the Avid ISIS 7000 shared storage network are a System Director, an engine containing ISIS Integrated Switch (ISS), ISIS Integrated Expansion Switch (IXS), ISIS Storage Blade (ISB), and one or more clients.

Avid ISIS 7000 Shared Storage Network Hardware

If you are unfamiliar with the names of the Avid ISIS 7000 components, the following table provides the terms used in this and other Avid ISIS 7000 documents.

System Director front view

Rear view Front view

ISIS Integrated Switch (ISS)

ISIS Integrated Expansion Switch (IXS)

ISIS Storage Blade (ISB)

Power supply

Engine

Product Nomenclature

Product name Term used and description

Avid ISIS® storage blade (labeled i500, i1000, i2000)

ISIS Storage Blade (ISB)

This hot swappable sled is accessible from the front of the ISIS engine and contains two SATA drives.

8

Avid ISIS Integrated Ethernet switch blade ISIS Integrated Switch (ISS)

This hot swappable switch is accessible from the rear of the ISIS engine and connects 1 Gb and 10 Gb clients. The ISS2000 indicates second generation hardware; first generation hardware is labeled ISS1000.

Avid ISIS Integrated Expansion Ethernet switch blade

ISIS Expansion Switch (IXS)

This hot swappable switch is accessible from the rear of the ISIS engine is used to stack multiple ISIS engines. The IXS2000 indicates second generation hardware; first generation hardware is labeled IXS1000.

Integrated power supply and cooling fans Power supplies

Three hot swappable power supplies are accessible from the rear of the ISIS engine.Two power supplies is required to power the ISIS engines.

Avid ISIS engine Called Chassis in the software interface

Contains the ISBs, ISSs, IXSs, power supplies, and an internal midplane.

Avid ISIS System Director (Active and standby)

System Director, a server connected to the ISIS engine to manage the data and portions of the metadata

Avid ISIS client Client, defined as a user’s workstation or server with Avid ISIS client software that allows that system to mount workspaces

Avid ISIS shared storage network System or shared network storage environment

The Avid ISIS consist of the hardware, Avid software, and other hardware supplied by the customer, such as external Ethernet switches.

Zone 1, Zone 2, Zone 3, and Zone 4 Configurations

These are Avid-defined client configurations that connect the client to the Avid ISIS system. A complete explanation can be found in the Avid ISIS 7000 Setup Guide.

Product Nomenclature (Continued)

Product name Term used and description

If You Need Help

9

If You Need HelpIf you are having trouble using your Avid product:

1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow.

2. Check the latest information that might have become available after the documentation was published.

New information would be found in the ReadMe file supplied on your Avid installation DVD as a PDF document and is also available online.

You should always check online for the most up-to-date release notes or ReadMe because the online version is updated whenever new information becomes available. To view the online versions, visit the Knowledge Base at www.avid.com/US/support.

3. Check the documentation that came with your Avid application or your hardware for maintenance or hardware-related issues.

4. Visit the online Knowledge Base at www.avid.com/US/support. Online services are available 24 hours per day, 7 days per week. Search this online Knowledge Base to find answers, to view error messages, to access troubleshooting tips, to download updates, and to read or join online message-board discussions.

Accessing the Online Documentation

The Avid ISIS v2.x documentation is now accessible in PDF format from the Help menu in the Avid ISIS Management Console browser window as well as on the top-level AvidUnityISISDocumentation folder on the Avid ISIS software installer DVD.

n The documentation describes the features and hardware of all models. Therefore, your system might not contain certain features and hardware that are covered in the documentation.

To access the online documentation from the software installer DVD-ROM:

1. Insert the Avid ISIS software installer DVD-ROM into the drive.

2. Navigate to the [DVD drive]:\AvidUnityISISDocumentation folder, and double-click the PDF file for the document you want to view.

10

Avid Training ServicesAvid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment.

For information on courses/schedules, training centers, certifications, courseware, and books, please visit www.avid.com/support and follow the Training links, or call Avid Sales at 800-949-AVID (800-949-2843).

New in Version 2.2.2

Avid ISIS v2.2.2 fixes several reported issues. This is a full software release (including servers, engines, and clients), see “Full Upgrade Instructions for v2.2.2” on page 31. The Avid ISIS v2.2.2 software is available on the Avid Download Center (http://www.avid.com/US/support/downloads).

Apple and Avid Media in the Same Storage Group

Avid is lifting the restriction that required you to store Apple Final Cut Pro media and Avid editor media in separate Storage Groups. Media from both editors can now be stored in the same Storage Group without any performance loss.

Fixed In This Release

The following issues were fixed in Avid ISIS v2.2.2.

➤ Data in unmirrored workspaces was being marked as “suspect” during the file rectification process because of missing mirrors (only mirror protected blocks should be marked suspect). The result caused ISBs to assert and restart every 30 days when there is unmirrored data in the Storage Group. This issue no longer occurs.

➤ Macintosh Snow Leopard (Mac OS 10.6.x) clients using the combination of the High Resolution setting (Preference > General > Client Type) with an application that uses I/Os larger than 16 MB/s, caused a Network Degraded status on the ISIS system. The System Director now handles this I/O pattern correctly and no longer causes Network Degraded errors.

➤ The Interplay Archive Provider and Interplay Media Indexer servers were experiencing random fatal errors to a blue screen. An updated Windows development kit has corrected this issue.

New in Version 2.2.1

11

➤ Avid’s TdITrans driver was causing a fatal error to a blue screen in the ISIS clients when it received a failure from a lower level network driver. This issues is now handled appropriately.

➤ The ISIS client was attempting to reference Storage Elements that were no longer part of the file system. The client would then lose connection with Storage Elements; which meant the client stopped working for a few minutes. Clients no longer lose connection with Storage Elements or experience delays.

➤ When using “Reveal File” on an XDCAM clip in the editing application, the ISIS client could result in a fatal error to a blue screen. This condition has been corrected.

➤ When browsing though many nested directories with Window 7 10 Gb ISIS clients, the ISIS client could result in a fatal error to a blue screen. This condition has been corrected.

New in Version 2.2.1

Avid ISIS v2.2.1 fixes an issue that was introduced in Avid ISIS v2.1.1. The issue is in the Windows client driver, therefore release only applies to Windows clients. The Windows ISIS client v2.2.1 software is only supported in Avid ISIS v2.1.1 and v2.2 infrastructures (ISBs, ISSs, and System Directors). Use the following instructions to upgrade your Windows clients to Avid ISIS v2.2.1.

Upgrade Instructions for v2.2.1

The upgrade includes the 32-bit and 64-bit windows client installers. It does not include the System Director “Client Installers” installer. You have two options for upgrading your Windows clients.

• Replace the two Windows installers on both your System Directors. Clients can download the installer from the Management Console, then upgrade the Windows clients in the normal way.

• Take the Windows client .msi installer file to the Windows client, uninstall the existing Client Manager software, then install the v2.2.1 client software.

n You do not need to stop the System Director to perform this upgrade.

To upgrade clients through the Management Console (recommended):

1. Copy the v2.2.1 zipped file you downloaded (ISIS_2.2.1.zip) to the System Director.

2. Extract the zipped files.

12

3. Navigate to the following location:

C:\Program Files (x86)\Common Files\Avid ISIS Shared\ftp\WinClient

4. Replace the two client installers on the System Director with the ones included in the v2.2.1 download (AvidUnityISIS Client.msi and AvidUnityISISclientx64.msi).

5. Repeat steps 1 though 4 on the second System Director.

6. Go to each Windows client and uninstall ISIS v2.2 client software and install the new version using the standard Management Console procedure.

7. Once installed, verify the ISIS client software version displays as v2.2.1.20 in the bottom of the Client Manager window.

To upgrade the Windows client software to v2.2.1 using a USB flash drive:

1. Copy the unzipped file you downloaded for the v2.2.1 release to a USB flash drive (AvidUnityISIS Client.msi and AvidUnityISISclientx64.msi).

2. Go to each Windows client and uninstall ISIS v2.1.1 or v2.2 client software using the Windows Control Panel.

3. Browse to your USB flash drive and install the v2.2.1 client software by double-clicking the appropriate Windows client software (32-bit or 64-bit).

4. Once installed, Verify the ISIS client software version displays as v2.2.1.20 in the bottom of the Client Manager window.

c If you upgrade your Windows Client software from the USB Flash drive without updating the System Director installers, you might unintentionally install the older version on new Windows clients in the future.

Fixed In This Release

The following issue was fixed in Avid ISIS v2.2.1.

➤ ISIS v2.1.1 introduced a change which caused detrimental client behavior after a System Director failover. When a failover is triggered by stopping or shutting down the Active System Director, windows clients were experiencing periodic I/O delays until the Active System Director was restarted. A correction has been made to the v2.2.1 Windows Client driver providing the proper reaction after a System Director failover.

New in Version 2.2

13

New in Version 2.2

Avid ISIS v2.2 adds support for Windows 7 and Macintosh ultra high resolution clients (UHRC). Avid ISIS v2.2 is a full infrastructure and client software release and is available on the Avid Download Center. The Avid ISIS v2.2 client software is supported in v2.0.4 and later infrastructures. The following sections describe the new features in Avid ISIS v2.2.

This release includes an important update regarding an issue previously found with the Avid ISIS System Director. With the Intel RAID driver v2.20.0.64 installed on a SR2500 System Director, it was possible to lose data after an unexpected system shut down (typically the result of a power loss). After installing the Avid ISIS v2.0.6 or v2.2 and later (not v2.1.1) and updating the Intel RAID driver to the v3.11.0.xx, this issue is resolved.

Windows 7 Client and Internet Explorer 8 Support

Avid ISIS now supports clients with the 64-bit version of the Windows 7 operating systems.

n Testing of the Windows 7 operating system with the Avid editing application has been done with a clean install of Windows 7. Avid does not know of any limitations when performing an upgrade from an existing Windows Vista 64-bit operating system to the Windows 7 64-bit operating system, but Avid recommends a clean install.

Avid has also qualified the use of Internet Explorer 8 (IE8) with the ISIS Management Console. Both the 32- bit and 64-bit versions of IE8 are available from the Windows 7 Start menu but, only the 32-bit version is supported with Avid ISIS. Make sure you select the IE8 application without the “(64-bit)” in the Start menu (Start > All programs> Internet Explorer).

Avid ISIS Windows 7 client upgrades require that you:

1. Remove the old version of the ISIS client software using the Windows Control Panel.

2. Perform a clean install of Windows 7 (see your Windows documentation).

3. Install the latest ISIS client software.

Intel Pro Driver Versions

The Intel Pro 1000 v14.7 driver version has been added in the kit and can be found on the Avid ISIS software installer DVD in the \Tools_3rdParty\Drivers_and_Firmware\Intel_Pro1000_14.7 folder.

14

The Intel Pro 1000 driver versions qualified in v2.2 are as follows. For instruction on updating the Intel Pro driver, see “Update Intel Driver on the System Director” on page 18.

• 64-bit System Directors qualified with v12.4 or v14.7

• 32-bit System Directors qualified with v12.3 or earlier versions

• Windows 7 clients that use the Intel Pro 1000 PT or PF (PCI Express) boards were qualified with the v14.7 driver

• Windows XP and Windows Vista clients are qualified with v12.4 or v14.7 drivers

c Clients that use the Intel Pro 1000 MT or MF (PCI-X) boards, need to use the v12.4 driver.

New 10-Gb Board for Windows and Macintosh Clients

Avid ISIS v2.2 and later now supports Macintosh ultra high resolution clients (UHRC) as well as Windows UHRC. Macintosh clients require the Myricom® 10-Gb Ethernet adapter. Previously Avid ISIS qualified the Chelsio 10-Gb Ethernet adapter with Windows clients. The Myricom 10-Gb Ethernet adapter has been qualified on both the Windows and Macintosh operating systems for Avid editing clients. These 10-Gb clients can connect directly into the ISS2000 10-Gb port on the Avid ISIS Engine. Two 10-Gb clients can connect into one engine; one client to each ISS2000. Engines with v1.x ISS1000 hardware do not support 10-Gb clients.

If your client cannot connect directly to an Avid ISIS Engine, Avid has qualified several switches that provide 10-Gb connections for more remote locations, see “Layer 2 and Layer 3 Switches” on page 42.

n Access the Knowledge Base at www.avid.com/support to download the Avid ISIS Switch Reference Guide and sample configuration files. This document provides configuration information on the Ethernet switches that are qualified with the Avid ISIS shared storage network.

The Myricom adapter board has been qualified in the following configurations:

• Slot 2 in the Macintosh Pro Nehalem 2.66 GHz and 2.93 GHz

• Slot 4 in the HP Z800

• Slot 4 in the HP Z400 (local storage is not supported when the Myricom board is installed)

n The HP xw8400 and HP xw8600 were qualified with a 10-Gb Chelsio adapter board, but the 10-Gb Myricom adapter board is not supported on the HP xw8400 or HP xw8600.

New in Version 2.2

15

Once your Avid ISIS 10-Gb client hardware and software is installed, the following requirements are needed with the UHRC:

• You need to use the Ultra High Resolution setting in the Client Manager Preferences with Avid editing clients

• Your workspace must be set to a 512 KB chunk size (for information on chunk sizes, see “Storage Group Size” on page 47)

• Your Avid ISIS infrastructure must be using v2.x switches (ISS2000 and IXS2000)

Installing the Myricom Board on Macintosh Clients

The Avid ISIS v2.2 software is available on the Avid Download Center (http://www.avid.com/US/support/downloads). Download the files on your Avid editing client and use the following information to setup and Myricom 10-Gb adapter board.

To install the Myricom adapter board in Macintosh clients:

1. Shutdown the Avid editing system.

2. Install the Myricom adapter board in slot 2 of a Macintosh Pro Nehalem system (2.66 GHz or 2.93 GHz). For slot information, search the Avid Knowledge Base for System Configuration Guidelines and Slot Configurations.

3. Double-click the myri10ge-macosx-1.2.0-10_6.tgz file you downloaded to expand the compressed file.

The file (myri10ge-macosx-1.2.0-10_6.tgz) can be found on the Avid ISIS software installer DVD in the Tools_3rdParty/Drivers_and_Firmware/Myricom/ folder.

4. Double-click the install package.

5. Install Avid ISIS client software.

6. Restart the client after the installation is complete.

7. Start the Avid ISIS client software and select the following UHRC requirements.

- Select the Ultra High Resolution setting in the Client Manager Preferences.

- Mount a 512 KB chunk size workspace.

Installing the Myricom Board on Windows Clients

The Avid ISIS v2.2 software is available on the Avid Download Center (http://www.avid.com/US/support/downloads). Download the files on your Avid editing client and use the following information to setup and Myricom 10-Gb adapter board.

16

To install the Myricom adapter board in Windows clients:

1. Shutdown the Avid editing system.

2. Install Myricom adapter board in the slot and system that has been qualified:

- Slot 4 in the HP Z800

- Slot 4 in the HP Z400

For slot information, search the Avid Knowledge Base for System Configuration Guidelines and Slot Configurations.

3. Double-click the myri10ge-1.1.0.1-x64-wlh.zip (64-bit) or myri10ge-1_1-x86.zip (32-bit) file you downloaded to expand the compressed file.

n There are two drivers provided in the Myricom folder; as 32-bit and 64-bit version. The 64-bit is for Windows 7 and Windows Vista 64-bit operating systems. The 32-bit driver is for Windows XP operating system.

The Myricom drivers can be found on the Avid ISIS software installer DVD in the Tools_3rdParty/Drivers_and_Firmware/Myricom/ folder

4. Apply the Myricom driver using the Device Manager.

a. Right-click My Computer, and select Manage.

b. Click Device Manager in the left pane.

c. Double-click the device or adapter category in the right pane to expand the list.

The Myricom adapter board could be listed is listed under one of the following:

- Network Adapters

- Unknown Devices

- Other Devices

d. Right-click on the Myricom adapter and select Properties.

e. Click the driver tab.

f. Click update driver.

g. Follow the Hardware Wizard prompts.Browse to the location of file you downloaded and expanded, then select the Myricom driver.

h. Accept the defaults to finish the driver installation.

5. Install Avid ISIS client software.

6. Restart the client after the installation is complete.

7. Start the Avid ISIS client software and select the following UHRC requirements.

- Select the Ultra High Resolution setting in the Client Manager Preferences.

- Mount a 512 KB chunk size workspace.

New in Version 2.2

17

Client Support for RGB Resolutions

Avid ISIS v2.2 client software now supports the Windows and Macintosh editing applications that use uncompressed RGB resolutions. Some editing applications and input/output hardware devices let you work in either the YCbCr or the RGB color space. RGB and YCbCr both separate colors into three channels, but they store color information differently. RGB produces higher quality images and effects, but takes up more space.

If you want to use uncompressed RGB resolutions you need to convert your Avid ISIS client to a 10 Gb Ethernet connection and upgrade your Avid ISIS client software to v2.2. Uncompressed RGB resolutions are only supported in an Avid ISIS v2.1.1 and later infrastructure.

Windows Client Captures Qualified on RAID Workspaces

When RAID Storage Groups initially was released (v2.1.1), capturing from editing client workstations was only supported from Macintosh clients. Support for capturing from Windows editing client workstations was added in Avid ISIS v2.2. For more information on RAID Storage Groups, see “RAID-6 Storage Groups” on page 26.

Intel Network Driver and BIOS Update

Avid has qualified an Intel system BIOS upgrade on the 64-bit System Director (SR2500) and File Gateway. This BIOS and Intel Pro driver upgrade combination corrects a condition where the network connection fails during a restart. The following sections describe the updates.

n If you find it necessary to reimage the System Director or File Gateway, you need to updated the network driver again. The BIOS is not affected when you reimage your server.

64-bit System Director BIOS Upgrade

Avid is recommending you update the BIOS on the 64-bit System Director and File Gateway. To do that, you can visit the Intel web site and follow their instructions, or use the files and instructions posted on the Avid Download Center (http://www.avid.com/US/support/downloads).

The procedure on the Avid Download Center requires you to create an Intel Deployment Assistant DVD and use a USB flash drive to load the BIOS update package on the System Director and File Gateway. Instructions for running the Intel BIOS Upgrade Utility and installing the BIOS are included with the image for the utility and the BIOS package.

18

n Check your current BIOS version before upgrading the BIOS. If your BIOS is at version 98, you have the recommended BIOS version for this release. Enter BIOS Setup by pressing the F2 Key during POST and the version is displayed as S5000.86B.12.00.0098 in the Main tab.

Record IP Addresses on the System Director

Before you update your Intel Pro network driver, Avid recommends you record the current IP address used on the System Directors. This precaution allows you to restore the IP addresses to the current settings if your network configuration is accidently lost.

To record the current IP addresses used by the System Director:

1. Open a command window on the System Director. Click Start > Programs > Accessories > and select Command Prompt.

2. Type ipconfig /all > c:\ip.txt in the Command Prompt window.

This command saves a text file (named ip.txt) to the root directory on the System Director. Open this text file if need to reconfigure the IP addresses to the addresses used before performing this network configuration update.

Update Intel Driver on the System Director

Use the following instructions to upgrade the Intel Pro network driver v12.4 on your 64-bit System Director, and configure the dual network ports. System Directors always have an Intel driver installed by default. You do not need to removed the older version.

To identify your current Intel Pro driver version on the System Director:

1. Open the Windows Add or Remove Programs control panel. Click Start > Settings > Control Panel > and select Add or Remove Programs.

2. Verify the version number beside the Intel Network Connections in the “Currently installed programs” list.

n The Intel Network Connections driver version number shipped with Windows 64-bit operating systems is v12.4.38.0. System Directors with Windows 32-bit operating systems have v12.3 or earlier. Do not upgrade System Directors with Windows 32-bit operating systems.

To update the Intel network driver on the System Director:

1. Stop the Standby System Director.

2. Insert the Avid ISIS software installer DVD into the client DVD drive. The software installation window opens after several seconds.

3. Click the Exit button to close the installation window.

New in Version 2.2

19

4. Browse to the appropriate Intel network driver folder on the Avid ISIS software installer DVD depending on the Windows operating system on your System Director.

[DVD drive] \Tools_3rdParty\Drivers_and_Firmware\Intel_Pro1000_14.7

5. Double-click the executable file (Autorun.exe).

6. Click Install Drivers and Software.

7. Accept the default settings to install the driver.

8. Click Finish.

9. Right-click My Network Places and select Properties.

10. Right-click the right side network connection and select Properties.

The Properties dialog window opens.

11. Click Configure.

12. If prompted, click Yes to proceed.

The Intel Pro Server Adapter Properties dialog box displays.

13. Click the Advanced tab.

Change the configuration as described in one of the following two steps. The dialog boxes in these steps are based on the version and driver installation.

20

14. (Option) If your Server Adapter Properties dialog box display looks like the following, change the configuration as described after the screen capture.

n If you are using a Remote Desktop Connection the Advanced tab does not appear.

a. Click Flow Control and set the Value to off.

b. Click Interrupt Moderation Rate and set the Value to off

c. Check that the Receive Descriptors and set the Value to 1024.

d. Check that the Transmit Descriptors and set the Value to 1024.

e. Click OK Server Adapter Properties dialog box.

New in Version 2.2

21

15. (Option) If your Server Adapter Properties dialog box display looks like the following, change the configuration as described after the screen capture.

a. Click the Performance Options in the Setting list.

b. Click Properties.

c. Click Flow Control and set the Value to off.

d. Click Interrupt Moderation Rate and set the Value to off

e. Check that the Receive Buffers and set the Value to 1024.

f. Check that the Transmit Buffers and set the Value to 1024.

g. Click OK to close the Performance Options.

h. Click OK to close the Server Adapter Properties dialog box.

16. Repeat steps 9 through 17 for the left side network connection.

17. Restart the Standby System Director.

18. Stop the Active System Director and repeat steps 1 through 17 to update the Intel Pro driver and configure the dual network ports on the Active System Director.

22

Intel RAID Controller Driver Update

This section describes the process for updating the Intel driver and registry key for the internal RAID controller on the Intel SR2500 server using the SROMBSAS18E Intel hardware RAID controller. This RAID controller is used in the Avid ISIS SR2500 System Director and the Avid Interplay 64-bit Media Indexer. This driver does not apply to the other SR2500 configurations using the embedded SATA RAID ESRTII.

n The majority of the Intel SR2500 Avid ISIS System Directors use a 64-bit operating system. Avid did ship some Intel SR2500 System Directors with a 32-bit operating system before the 64-bit operating systems were released. All Avid ISIS System Directors using the Intel SR2500 server require this RAID controller driver update.

The RAID controller update requires a driver update and a registry change. Access the update package from one of the following locations. Create a new folder on the server that you are updating and place the update files in it.

This RAID controller driver is available from two locations:

• Download the Intel hardware RAID controller SROMBSAS18E update package from (http://www.avid.com/US/support/downloads).

• This version of the Intel driver has been added in the Avid ISIS software installer DVD and can be found on the Avid ISIS software installer DVD in the Tools_3rdParty\Drivers_and

_Firmware\IntelSROMBSAS18E_Raid_Controller\Intel_Raid_v3.11.0.xx folder.

To upgrade the SROMBSAS18E Intel driver:

1. Access the Standby System Director and stop the System Director service using the ISIS Control Panel.

2. Right-click on My Computer and select Manage. The Computer Management Window opens.

3. Select Device Manager. The Device Manager opens

4. Click the plus sign (+) next to SCSI and RAID Controllers.

New in Version 2.2

23

5. Right-click on the Intel RAID Controller SROMBSAS18E and select Properties.

6. Click the Driver tab in the Properties window.

7. Click Update Driver in Driver tab.

8. In Hardware Update Wizard, do not let Windows select the driver:

a. Select “No, not at this time” and click Next.

b. Select “Install from a list of specific location (Advanced)” and click Next.

c. Select “Don’t search. I will choose the driver to install” and click Next.

d. Click “Have Disk.”

e. Click Browse and locate the oemsetup.inf file in the package you copied to the server.

- 64-bit System Director and Media Indexer — IntelSROMBSAS18E_Raid_Controller\Intel_Raid_v3.11.0.xx\W2K3X64 folder

- 32-bit System Director — IntelSROMBSAS18E_Raid_Controller\Intel_Raid_v3.11.0.xx\XP folder

24

f. Click Open, in the Locate File dialog box.

g. Click OK, in the Install From Disk dialog box.

h. Click Next in the Hardware Update Wizard.

9. Once you complete the driver install, click No when prompted to restart the server.

10. Close the Properties window.

11. Apply the registry key by browsing to the RegKey_Updates folder in the package you copied to the server.

t 64-bit System Director — double-click the w2k3.reg file to apply the registry key change.

The following two entries are added to the 64-bit System Director registry location: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msas2k3\Parameters\Device

DriverParameters = flushrequest= 3DriverParameter = flushrequest= 3

t 32-bit System Director — double-click the winXP.reg file to apply the registry key change.

The following two entries are added to the 32-bit System Director registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\megasas\Parameters\Device\

DriverParameters = flushrequest= 3DriverParameter = flushrequest= 3

12. Restart the Standby System Director.

13. After the StandBy System Director has restarted, turn off the Active System Director to failover to the updated Standby System director. Repeat this procedure on the second System Director.

System Director Recovery DVD Change

A new Product Recovery DVD for 64-bit System Directors and File Gateway is getting phased-in for this release. The Product Recovery DVD for Avid ISIS v2.1.1 was modified to support both the File Gateway server and 64-bit System Director (labeled sd_x64_pis21_mbs5000xalr_v05_dvd). The Product Recovery DVD for Avid ISIS v2.2 File Gateway server and 64-bit System Director is sd_x64_pis21_mbs5000xalr _v04_dvd.

The version number of the image can be found in the c:\IMAGE.TXT file on the System Director root directory. The image does not restore the Avid ISIS software. The Avid ISIS software must be reinstalled separately, after the operating system recovery is complete. The following list the latest updates per Product Recovery image.

New in Version 2.2

25

Fixed In This Release

The following issues have been fixed in Avid ISIS v2.2.

➤ The ISIS client code has been optimized to perform more efficiently when required to retrieve a mirror block. In the previous release, clients using DNx145 and higher might experience failed digital cuts, or dropped frames during a redistribution. This no longer occurs with ISIS 2.2.

➤ Assigned drive letters for workspaces on Avid ISIS Windows clients are no longer hidden or overwritten in Client Manager's workspace list by the displayed UNC path.

➤ When operating in sub-optimal network environments, there is a very rare condition under which Windows clients might experience a fatal system error resulting in a blue screen. This issue has been corrected in v2.2.

➤ In previous releases, when the client is idle, there was a time-out issue which caused the ISB to end client sessions prematurely. This in turn caused erroneous network activity. In some rare cases, this could also cause an ISB to assert and restart. This condition no longer occurs.

Included in the Recovery image for the Last Three 64-Bit System Directors images

UpdateRecovery Imagev_03

Recovery Imagev_05

Recovery Imagev_04a

a. The v_04 recovery image was pulled back and re-released after v_05. Image v_04 is the version recommended for ISIS v2.2.

Intel RAID controller driver for system drives on the System Director

Needed Needed Included

Intel Pro Driver Configuration Update Needed Included Included

Enabling Windows Updates on 64-Bit System Directors

Needed Included Included

Application Key Driver Update on the System Director

Included Included Included

Support the Avid ISIS File Gateway No Yes Yes

26

➤ When automounting workspaces prior to Avid ISIS v2.1.1, workspaces were mounted alphabetically. In v2.1.1 client workspace mounting changed the mounting order to random mounting. In Avid ISIS v2.2 the automount refresh runs in two passes, where the workspaces with assigned mountpoints are mounted before the workspaces with no assignment are mounted. Example: Workspace “Beta” with Z: assignment is mounted before workspace “Alpha” with no assignment.

In addition, the automount refresh looks for case-insensitive alphabetical order. Example: Workspace “beta” gets automounted before workspace “Gamma,” provided they both have unassigned or assigned mountpoints.

➤ Previous releases of Avid ISIS did not support the use of the percent sign (%) character in user passwords. Avid ISIS v2.2 now supports the % character in user passwords.

➤ There was a 1 TB limit when capturing media using a 10 Gb Macintosh client. This limit was reached in approximately 1.9 hours with 10-bit uncompressed resolutions. If you exceeded that limit, the capture would fail and errors were displayed. This issue has been corrected in v2.2.

➤ Specific Avid editing releases (Media Composer v5.x, NewsCutter 9.x, and Symphony 5.x) display the following error during 9-way MultiCamera playback in ISIS v2.1.1 and earlier environments (including v1.x):

Exception: DIDReader::XraiseUnexpectedStreamStatus async timeout error

This problem has been fixed in ISIS v2.2.

➤ It was possible for the Low Res Encoder and the AirSpeed (classic) client to both stop functioning during a write operation. The Both systems needed to be restarted to recover from this condition. This issue no longer occurs.

New in Version 2.1.1

The following sections describe the changes and new features in Avid ISIS v2.1.1. This is a full software release (including servers, engines, and clients), see “Full Upgrade Instructions for v2.2.2” on page 31.

RAID-6 Storage Groups

Avid ISIS v2.1.1 now supports a second type of data protection. Besides mirrored Storage Groups, you can now create redundant array of independent disks (RAID) Storage Groups. RAID storage offers more value in that it provides more storage at a lower cost per GB.

New in Version 2.1.1

27

Using the Avid Interplay Copy/Move service, data files can be moved from mirrored Storage Groups to and from RAID Storage Groups. The following are two obvious advantages to using RAID Storage Groups:

• Migration from mirrored to RAID workspaces can become part of your normal workflow. You can move the data that is no longer used in the mirrored workspaces to RAID workspaces for longer term storage. This frees up faster storage elements (mirrored) for higher performance work.

• RAID Storage Groups allow you to work on a lower resolution workflow at less cost.

• RAID Storage Groups increases available GB per physical engine from 50% in mirrored to 75% in RAID of installed capacity.

The following is a list of RAID workspace restrictions:

• Requires a Storage Group with a 512 KB chunk size (256 KB chunk sizes are not supported).

• Requires ISIS v2.x generation switches (ISS2000/IXS2000) in the ISIS Engines (these switches are also required for 512 KB chunk sizes).

• Avid recommends RAID Storage Groups have a minimum of 16 ISBs (one engine). The Management Console allows you to create and use RAID Storage Groups with eight ISBs but with in a RAID Storage Group of eight, you must add an ISB before you can remove an ISB.

• Avid ISIS client software versions before v2.1.1 are not supported with RAID.

• RAID workflows require specific releases of Avid products that support the workflow (AirSpeed Multi Stream, Avid editing applications, and Interplay), see “Hardware and Software Requirements” on page 38.

• Supports only resolutions that draw 16 MB/s (50 Mb/s) or less.

n For example, you can run two streams of DV 50 or DNxHD 36. Bandwidths are listed by resolution and number of streams on the Avid Knowledge Base. Search the Avid Knowledge Base for the Avid ISIS Performance and Redistribution Guide.

• Capturing from an editing client workstation is only supported from Macintosh clients in Avid ISIS v2.1.1. (Support for capturing from Windows editing client workstations was added in Avid ISIS v2.2.)

• If a RAID Storage Group experiences two disk failures, no writes to any of the workspaces in that Storage Group are supported until the error condition is corrected.

• If you need to do a non-symmetrical full redistribution, you must first limit the bandwidth used by your clients in that Storage Group. For more detailed guidance, see the Avid ISIS v2.1.1 Performance and Redistribution Guide on the Knowledge Base at www.avid.com/US/support.

28

c Avid does not recommend a non-symmetric redistribution when your RAID Storage Group capacity exceeds 80%.

RAID-6 Storage Groups, Single ISB Failure

When there is a single ISB failure in an ISIS Storage Group configured with RAID protection, the Storage Group continues to function normally at a lower bandwidth. For mirrored Storage Groups, see “Mirrored Storage Groups, Single ISB Failure” on page 48.

After confirming the failure of an ISB, it is highly recommended that you initiate the remove redistribution process of the failed ISB immediately. There are two benefits to doing this:

• First, immediately upon initiation of the remove redistribution, all new writes to the Storage Group have the full benefit of RAID-6 protection (dual-parity protection).

• Second, upon completion of the remove redistribution process, existing data in the Storage Group is once again fully protected. Prior to completion, if another ISB were to fail, the Storage Group would be in an unprotected state (though no data would be lost).

RAID-6 Storage Groups, Dual ISB Failure

It is considered an “unprotected state” if you are with two failed ISBs in a RAID-6 Storage Group. In an unprotected state with no additional failures, read operations continue to function normally at a lower bandwidth.

However, in an unprotected state, due to the distributed architecture of the ISIS file system (optimized for real-time performance), it is possible under certain circumstances that the system would not be able to correctly update the parity information when writing new data. As a result under these circumstances, the file system could return a failure status when writing. While the failure rate percentage on the total number of write operations is low, heavy workloads on the system would result in enough write failures to disrupt operations.

This issue only applies when the Storage Group is in an unprotected state and the remove redistribution process on the failed ISBs has not been initiated. Therefore, it is highly recommended that the remove redistribution process is initiated immediately upon confirmation of any ISB failure. This ensures immediate protection (RAID or mirroring) of new data being written, and full protection of all stored data at the earliest possible time.

Avid ISIS File Gateway

The Avid ISIS File Gateway server enables network users to access Avid ISIS workspaces in a non-realtime scenario. Depending on the access permissions, network users can read, write, and delete files on workspaces without using up ISIS client licenses. The File Gateway uses the Common Internet File System (CIFS) protocol to request files from a server over the network. It is based on the Server Message Block (SMB) protocol. In

New in Version 2.1.1

29

addition you can move data in and out of workspaces using a File Transfer Protocol (FTP) connection. The File Gateway server is configured for FTP using the Windows FTP Site Creation Wizard.

n When the File Gateway is configured as a CIFS server, workspaces are mapped to drive letters on the File Gateway. Depending on the number of drives in the File Gateway, the maximum number of workspaces that can be shared out as a CIFS share is 22 workspaces.

The File Gateway is a 64-bit Intel® SR2500 server with the same image shipped on the internal RAID drives for the Avid ISIS v2.1.1 64-bit System Director. The v2.1.1 System Director image was modified to support the File Gateway server or 64-bit System Director. If you currently have a previous release of a 64-bit System Director you convert that System Director to a File Gateway by running the new product recovery DVD and install the File Gateway software.

n The Avid ISIS File Gateway Setup and User’s Guide provides instructions on setting up the File Gateway server. Navigate to the [DVD drive]:\AvidUnityISISDocumentation folder, and double-click AvidUnityISISFileGateway.PDF.

Automatic Redistribution on Disk Failure

Avid ISIS v2.1.1 now performs an automatic redistribution on Disk Failure notification. Storage Elements continuously monitors disk status and sends a “Disk Failed” notification to the System Director upon determination that a disk is not usable. The System Director then removes the Storage Element from its associated Storage Group. The removal of the Storage Element from the Storage Group initiates redistributions on all workspaces associated with that Storage Group. The System Director then prevents the Storage Element that reported the disk failure from being added to a Storage Group.

The Automatic Removal feature is controlled by a system preference that is configured using the ISIS Management Console Preferences tool. The preference is called “Auto Remove Redistribution on Disk Failure” The default setting is “enabled.” The Storage Element is only removed from the Storage Group. It is not unbound from the ISIS Systems for the following reasons:

• The Storage Element participates in the removal redistribution. This is required to prevent data loss when there are un-protected workspaces or when full redundancy has not been attained for all data blocks.

• The Storage Element continues to report status, such as physically replacing the blade.

Auto removal status is reported by way of the System Event Log. A sequence of event log entries are generated for the initial report of the failure, the decision to remove the Storage Element, and subsequent success or failure. Events are also logged for the start and stop of all the workspace redistributions.

30

The following are important considerations when using Automatic Redistribution:

• When automatic redistribution is enabled, be sure to keep at least 7% of your Storage Group unused at all times. Failure to do so can cause the system to run out of space after an automatic redistribution has initiated and cause a client outage. For more information on keeping 7% of your Storage Group available, see “Minimum Storage Space Requirement” on page 52.

• If an automatic redistribution of a Storage Group is started during a critical time the overall system performance can degrade significantly and be disruptive. For more information on understanding the performance characteristics during remove redistribution, see the Avid ISIS Performance and Redistribution Guide.

• An automatic redistribution removes the Storage Element from the Storage Group but not from the file system. Once an automatic redistribution has occurred and completed, the removed Storage Element should be removed from the file system. You must first removed the Storage Element with the software and then physically replace it. A replacement ISB must then be added to the file system and then the Storage Group, triggering another redistribution.

• If unmirrored workspaces are in use, the data will be damaged on those workspaces in that Storage Group.

New System Director Recovery DVD

The Product Recovery DVD for 64-bit System Directors has been updated to include several new components that have changed since the initial release of Avid ISIS 2.0. The image for the Avid ISIS v2.1.1 release modified the System Director image to support both the File Gateway server and 64-bit System Director. The Product Recovery DVD (sd_x64_pis21_mbs5000xalr_v05_dvd) restores the Windows operating system and the hardware drivers. The image version number can be found in the c:\IMAGE.TXT file on the System Director root directory. It does not restore the Avid ISIS software. The Avid ISIS software must be reinstalled separately, after the operating system recovery is complete. The major new components include:

• System Director Intel Pro Driver Configuration Update

• Application Key Driver Update on the System Director

• Enabling Windows Updates on 64-Bit System Directors

• Code to support the Avid ISIS File Gateway

Full Upgrade Instructions for v2.2.2

31

Change in Order for Components for System Upgrades

In the past, Avid had recommended you upgrade the Avid ISIS infrastructure first and then upgrade the Avid ISIS clients at your earliest convenience. In this release, Avid ISIS clients need to be upgraded before you upgrade the infrastructure. This is necessary because ISIS client software before v2.1.1 is not supported in the ISIS v2.1.1 infrastructure. Although, v2.1.1 client software is supported in v1.4 and later infrastructures. For more upgrade instruction, see “Full Upgrade Instructions for v2.2.2” on page 31.

Full Upgrade Instructions for v2.2.2

To upgrade to ISIS v2.1.1 and later infrastructures, Avid ISIS clients need to be upgraded before you upgrade the infrastructure. This is necessary because ISIS client software before v2.1.1 is not supported in the ISIS v2.1.1 and later infrastructures. Although, v2.1.1 and later client software is supported in v2.0.4 and later infrastructures. Once the clients have been upgraded, you can upgrade Avid ISIS v2.1.1 and later infrastructures.

n Avid ISIS v2.1.1 and later Macintosh client software is supported for ISIS Snow Leopard clients (Mac OS v10.6.2 and later) in the Avid ISIS v1.7 and later infrastructure.

The clients are defined as follows:

• Avid editing applications

• Interplay Assist and Instinct

• Interplay Access

• Avid Approved Applications Initiative such as Pro Tools and Final Cut Pro

The infrastructure is defined as follows:

• System Director — System Director software and upgrade Storage Blades (ISBs) and Switch Blades (ISS/ISXs) in the Avid ISIS Engines to the v2.2 firmware

• Interplay servers — Interplay Engine, Interplay Media Indexer, Interplay Transfer, and CaptureManager

• Capture devices — AirSpeed, AirSpeed Multi Stream, and Avid Interplay Low-Res Encoder

n If updating from an ISIS v1.x infrastructure you must do a full redistribution on your workspace after you have updated the infrastructure to v2.x. A full redistribution is needed to take advantage of the performance improvements. The redistribution is required even if the system has zero (0) configuration changes listed.

32

n Avid ISIS v2.1.1 SR2500 64-bit System Directors shipped with an SD_X64_PIS21_MBS5000XALR_v05_DVD image on the internal RAID drives. The image version number can be found in the c:\IMAGE.TXT file on the System Director root directory. If upgrading your 64-bit System Director from Avid ISIS v2.0.1 or earlier Avid recommends you reimage the System Directors to reduce the number if updates required in this release. For instructions on how to reimage the System Director, see the Avid ISIS 7000 Setup Guide.

Macintosh Snow Leopard Client Upgrades

Avid ISIS clients that use Macintosh Snow Leopard operating systems (Mac® OS version 10.6.2 and later) require a clean install of Snow Leopard (Mac OS v10.6) and then perform the upgrade to Mac OS v10.6.2 and later. You cannot just perform an upgrade to your existing Leopard system and have Snow Leopard work properly with Avid editing applications.

Avid ISIS Macintosh client upgrades require that you:

1. Remove the old version of the ISIS client software using the uninstaller in the Applications > Avid_Uninstallers folder.

2. Perform a clean install of Snow Leopard (see your Macintosh documentation).

3. Install ISIS client software v2.2.

Upgrades for v1.4 and Later

The following process summarizes the upgrade process from v1.4 and later to v2.x.

If you are upgrading from Avid ISIS v2.0.1 or earlier, Avid suggest you consider reimaging the 64-bit System Director. For information on reimaging, see the Avid ISIS 7000 Setup Guide. Several configuration changes and driver versions have been updated in the 64-bit System Director and you might find it easier than following the referenced procedures listed in the following procedure. If you do decide to reimage, perform a failover, then reimage the Standby System Director first.

n If you are upgrading from a version earlier than Avid ISIS v1.4, you must first upgrade to Avid ISIS v1.4 before upgrading to v2.2.2, For instructions, see the v1.4 documentation.

To upgrade from v1.4 and later to v2.2.2:

1. Update your Avid ISIS clients to the v2.2.2 software.

Do not continue to the next step until all your clients are updated. For information on saving your client preferences, see “Client Preferences” on page 45.

Full Upgrade Instructions for v2.2.2

33

n The Avid Interplay Media Indexer and AirSpeed Multi Stream patch is no longer needed with Avid ISIS v2.0.2 and later. You must uninstall the patch and ISIS v2.x client software before installing the ISIS v2.2.2 client software, see “Avid Interplay Media Indexer and AirSpeed Multi Stream Patch” on page 37.

2. Start the System Director and Log into Administrator account.

3. (For new installs or re-imaged System Directors) If your System Director has Internet Explorer 7, start Internet Explorer 7 and change the following settings.

n System Directors with 32-bit operating systems include Internet Explorer 6 and the Internet Explorer settings do not need to edited. This Internet Explorer 7 requirement applies mostly to new System Directors with 64-bit operating systems where Internet Explorer 7 is qualified as the default browser.

a. Click Tools > Internet Options and change the Security following:

- Internet — Medium

- Trusted — Low

b. Click the Advanced tab and change the following:

- Phishing Filter — Disabled

- Use SSL 2.0 — Enabled (checked)

- Use TLS 1.0 — Disabled (unchecked)

4. (Skip this step if updating from ISIS v2.2 and later) Update the System Director Intel system BIOS on the 64-bit System Director (SR2500), see “64-bit System Director BIOS Upgrade” on page 17.

5. (Skip this step if updating from ISIS v2.2 and later) Update the Intel RAID controller driver and registry key on the 64-bit System Director, see “Intel RAID Controller Driver Update” on page 22.

6. (Skip this step if updating from ISIS v2.2 and later) Update the Intel Pro driver configuration on the System Director, see “Update Intel Driver on the System Director” on page 18.

7. Upgrade System Director software, load the ISIS Blade Installers, and load the ISIS client Installers on the System Director. For more information, see the Avid ISIS 7000 Setup Guide.

Avid ISIS v2.1.1 and later requires a metadata conversion. Attempting to replicate between System Directors of differing versions is not recommended. To properly perform the metadata conversion. Use the following upgrade procedure.

a. Stop Standby System Director.

b. Stop Active System Director.

34

c. Upgrade Active System Director and wait until the System Director is up and running.

d. Once the Active is up and running, upgrade the Standby System Director.

8. (Skip this step if updating from ISIS v2.0.2 and later) Update the System Director application key (dongle), see “Application Key Driver Update on the System Director” on page 34.

9. (Skip this step if updating from ISIS v2.0.4 and later) Update the System Director to allow Windows Updates, see “Enabling Windows Updates on 64-Bit System Directors” on page 36.

10. Upgrade all your ISBs and ISS/ISXs. Using the ISIS Management Console, select all the ISBs and click Upgrade Storage Blades and then select all your ISS/ISXs and click Upgrade Switch Blades. You do not need to wait for the ISBs to be finished, you can upgrade ISBs and ISS/ISXs at the same time.

11. Watch the upgrade progress in your Monitoring tool and wait until every ISS/ISXs is at the “Install Waiting” state and then power down all the Avid ISIS Engines.

n If you already have Avid ISIS v2.x installed in your environment you do not need to power cycle the Avid ISIS Engines. Power cycling the engines is only required when updating from v1.x to v2.x.

12. Power on the Avid ISIS Engines in 1 minute intervals starting with the chassis that has the ISS/ISXs. This reduces stress on the stack.

After the Avid ISIS Engines restart, the ISSs continue with the install (no additional user intervention is necessary).

Application Key Driver Update on the System Director

After upgrading to Avid ISIS v2.0.2 and later, you must upgrade your Avid ISIS application key (dongle) driver on the System Director (see “Full Upgrade Instructions for v2.2.2” on page 31). The driver name for the application key is the Sentinel Protection Installer. If you do not update your application key, the Active Clients tab in the System Director Control Panel displays “0 licenses allowed by dongle” and the Client Manager displays the following error:

Failed to authenticate user: “Administrator” on System Director: “SQADATA” ERROR: Not enough user

This Sentinel v7.4.2 driver upgrade pertains to System Directors with Windows XP Embedded 32-bit operating systems. System Directors running Windows Server 2003 64-bit operating systems already have this driver version installed.

Full Upgrade Instructions for v2.2.2

35

To upgrade the Sentinel driver:

1. Open the Standby System Director Control Panel and click Stop System Director to stop the service.

2. Remove the application key from the USB port on the Standby System Director.

3. Uninstall the old version of the Sentinel driver using the Windows Control Panel.

a. Click Start > Settings > Control Panel > and select Add or Remove Programs.

b. Locate the Sentinel Protection Installer and click Remove.

c. Restart the System Director.

4. When the System Director restarts, log-in, open the System Director Control Panel, and click Stop System Director to stop the service.

5. Run the SafeNet® SSD Cleanup utility.

a. Download the SSD Cleanup utility (32-bit) from:

http://www.safenet-inc.com/support/tech/sentinel.asp

b. Save the utility on your System Director.

c. Extract the .zip file.

d. Double-click the SSDCleanup.exe file and follow the prompts.

e. Restart the System Director.

6. When the System Director restarts, log-in, open the System Director Control Panel, and click Stop System Director to stop the service.

7. Double-click the SentinelProtectionInstaller7.4.2.exe file located in the following folder on the System Director.

D:\Program Files\Avid Technology\AvidUnityISISSystemDirector\Sentinel Driver Installer

8. Install the Sentinel driver as follows (Complete installation).

a. Click Next.

b. Accept the license agreement and click Next.

c. Continue with accepting the defaults to finish the installation.

9. Reinsert the application key in the USB port on the System Director.

10. When prompted for the SNTNLUSB.SYS file, navigate to:

C:\Program Files\Common Files\SafeNet Sentinel\Sentinel System Driver

36

11. Open the System Director Control Panel and click Start System Director to start the service.

When started, the Active Clients tab in the System Director Control Panel displays the correct number of licenses and the clients.

c If the Active Clients tab does not display the correct number of licenses and clients, contact your Avid Representative before trying to upgrade your Active System Director.

12. Repeat this procedure on the Active System Director.

n Stopping the Active System Director induces a failover to the Standby System Director.

Enabling Windows Updates on 64-Bit System Directors

Currently, Windows updates are disabled on 64-bit System Directors running Windows Storage Server 2003. Avid ISIS v2.0.4 and later includes a hotfix to enable the Windows Update service and allow you to update your System Director.

n Automatic Updates remain disabled for security reasons. To update your System Director in the future, you need to use the Windows Update web site.

After enabling Windows Updates on your 64-bit System Director, access the Knowledge Base at www.avid.com/securityupdate and review the Microsoft Security Bulletin Addendum document. This link also includes antivirus software support on Avid products which can be found in the Avid Security Guidelines and Best Practices document.

c This procedure will result in workflow interruptions, and should be performed during a scheduled maintenance interval.

To enable Windows Updates on the System Director:

1. Extract the Avid ISIS update zip archive to the standby System Director.

2. Open the System Director Control Panel and click Stop System Director to stop the service.

3. In the extracted update zip archive, navigate to Tools_3rdParty\ISISUtilities\ and double-click the file enableAutoUpdateServiceWithUpdatesOff.cmd to execute it.

4. Open Internet Explorer and click Tools > Windows Update.

5. Follow the prompts to install the Windows Update ActiveX control.

6. Once the Windows Update software is installed, click the Custom button.

Full Upgrade Instructions for v2.2.2

37

7. Click to deselect the check box for Internet Explorer 8 (this version has not been qualified). Leave the rest of the updates selected.

8. Click “Review and install updates.”

9. Click the “Install Updates” button.

10. Follow any prompts that appear, and restart the System Director when the updates have been installed.

11. When the System Director has restarted, check the Windows event logs for any unusual events.

12. Open the System Director control panel, and verify that the metadata status is Synchronized.

13. Repeat this procedure on the active System Director.

n Stopping the active System Director will invoke a failover event, and cause a brief interruption in workflow.

Avid Interplay Media Indexer and AirSpeed Multi Stream Patch

In Avid ISIS v2.0 and v2.0.1, the Avid Interplay Media Indexer server and AirSpeed Multi Stream needed a specific patch installed with the Avid ISIS client installer. This separate patch is no longer needed on the Media Indexer and AirSpeed Multi Stream servers with Avid ISIS v2.0.2 and later.

However, you do need to uninstall the patch and earlier client software version from the Media Indexer and AirSpeed Multi Stream servers before installing the ISIS v2.0.2 and later client software.

n When installing the ISIS client software on your Media Indexer and AirSpeed Multi Stream servers, you do not need to restart the server between uninstalling the patch and the client software. Restart the server after the new ISIS client software is installed.

To update Media Indexer and AirSpeed Multi Stream servers client software:

1. Uninstall patch using the Windows Control Panel.

t Windows 32-bit Media Indexer — AvidUnityISISClientMiPatch.msi

t Windows 62-bit Media Indexer — AvidUnityISISClientMiPatchx64.msi

2. Uninstall ISIS client using the Windows Control Panel.

3. Install the ISIS v2.1.x client software.

38

Upgrading Unstacked Switches

If you need to upgrade switches that are not yet stacked, the Avid ISIS software installer DVD includes the Avid ISIS Upgrade Utility. This stand-alone application allows field engineers to start and monitor the installation of switch and ISB upgrades from a laptop connected to Avid ISIS switch through the management port. This utility does not replace the current upgrade process. Its primary function is for upgrading a switch or a pair of switches that is incompatible with an existing stacked network. Insertion of these switches into the network before the upgrade could disrupt or compromise the network’s operation. For instruction on using the utility, see the Avid ISIS 7000 Setup Guide.

The Avid ISIS Upgrade Utility (AvidUnityISISTools.msi) can be found on the Avid ISIS software installer DVD in the \Tools_3rdParty\ISISUtilities folder.

n Avid manufacturing continues to stock ISS1000 and IXS1000 switches with Avid ISIS v1.4 firmware to support existing customers. If you are upgrading your software to, Avid ISIS v2.x, you need to upgrade your ISS1000 and IXS1000 switch firmware.

Hardware and Software Requirements

The following table provides a list of product clients and required software versions needed to work with Avid ISIS v2.1.1 and later. The versions of the Avid applications might differ depending on the type of workspaces you are using (mirrored or RAID workspaces). In general this release requires Avid software release in Q2 2009 or later.

n All Windows editing clients must use the 1-Gb Intel® Pro 1000 Ethernet board to connect to the Avid ISIS system. For instructions on installing the board and software, see for Avid ISIS 7000 Client Guide. If using the HP® xw8600 workstation, see “HP xw8600 Workstations and Broadcom Ethernet Connections” on page 42.

Software

Qualified Client Release with Mirrored Workspaces

Qualified Client Release with RAID Workspacesa Required Hardware

Avid Interplay® v1.6.2 and later v1.6.2 and later Workgroup Environment

Media Composer® v3.5.4 and later

MacOS 10.5.3 and later

v3.5.9 and later Dual Processor HP XW8000, HP xw8200, HP xw8400, HP xw8600, Z400, or Z800

Mac Pro systems and newer

Hardware and Software Requirements

39

Media Composer 10-Gb client

v3.5.4 and later v3.5.9 and laterb HP xw8600, dual quad-core HP xw8400, Z400, or Z800

Avid Symphony™ Nitris®

v3.5.4 and later

MacOS 10.5.3 and later

v3.5.9 and later Dual Processor HP XW8000, HP xw8200, HP xw8400, HP xw8600, Z400, or Z800

Mac Pro systems and newer

Avid Symphony Nitris DX 10-Gb client

v3.5.4 and later v3.5.9 and laterb HP xw8600, dual quad-core HP xw8400, Z400, or Z800

NewsCutter® v7.5.4 and later v7.5.9 and later Dual Processor HP XW8000, HP xw8200, HP xw8400, HP xw8600, Z400, or Z800

NewsCutter 10-Gb client

v7.5.4 and later v7.5.9 and laterb HP xw8600, dual quad-core HP xw8400, Z400, or Z800

Avid DS Not supp rted n For the most up to date information, search for ISIS support at: http://www.avid.com/US/products/avid-DS

Avid Interplay Low-Res Encode

v2.3 and later v2.3 and later Interplay component, newer version than supplied in Interplay v1.6.2

Avid Instinct® v2.0.2 and later v2.0.2 and later Workgroup Environment

AirSpeed® v2.7.2 and later v2.7.3 and later

AirSpeed Multi Stream

v1.0 and later v1.2 and later

Digidesign® Pro Tools®

v8.x and later

Windows — Real-time support based on the number of clients, drives, sample rate, and edit density.

Macintosh — No real-time support (push/pull only)

No real-time support (push/pull only n For the most up to date

information, search for ISIS support at: http://www.digidesign.com

Software

Qualified Client Release with Mirrored Workspaces

Qualified Client Release with RAID Workspacesa Required Hardware

40

Intel Pro 1000 Boards and Driver

The Intel Pro 1000 boards are required in editing systems that connect to the Avid ISIS system. There is an exception to this requirement when using the HP xw8600, see the note in “Hardware and Software Requirements” on page 38. The Intel Pro 1000 MT and Intel Pro 1000 PT are copper boards, and the Intel Pro 1000 MF and Intel Pro 1000 PF are optical boards. Depending on the Intel board used in your system, you must load the appropriate driver from the appropriate folder. The Intel drivers qualified in this release are included in the kit and can be found on the Avid ISIS software installer DVD in the \Tools_3rdParty\ Drivers_and_Firmware\Intel_Pro1000_xx.x folder. Check the driver version listed in the Windows Control Panel, see “To identify your current Intel Pro driver version on the System Director:” on page 18.

c The Intel drivers on Avid Interplay Engine cluster systems do not require updating for this release. Doing so could compromise the integrity of the cluster. In general, do not update the hardware drivers on a cluster system unless instructed to do so by the Interplay ReadMe or by Customer Support.

Loading or Updating the Intel Pro Driver on Windows Clients

To load the Intel Pro driver on a Windows client:

1. Double-click the executable file; found on the Avid ISIS software installer DVD in the \Tools_3rdParty\ Drivers_and_Firmware\Intel_Pro1000_xx.x folder.

2. Accept the default settings to install the driver.

3. After the Intel driver is installed, restart the Windows client.

Dell Precision T3500 Integrated Network Port Not Supported

The integrated Broadcom® 5761 gigabit Ethernet controller in Dell® Precision™ T3500 Workstation is not supported as an ISIS client connection. The Dell Precision T3500 requires the installation of the Intel Pro 1000 PT.

HP Z400 and HP Z800 Integrated Network Port Not Supported

The integrated Broadcom BCM5764 gigabit Ethernet controller in HP Z400 and HP Z800 Workstation is not supported as an ISIS client connection. The HP Z400 and HP Z800 require the installation of the Intel Pro 1000 PT.

a. Supports only resolutions that draw 16 MB/s (50 Mb/s) or less. For more information see “RAID-6 Storage Groups” on page 26.

b. Ultra High Resolution Clients can mount RAID workspaces although, only resolutions that draw 16 MB/s (50 Mb/s) or less are supported. For more information, see “RAID-6 Storage Groups” on page 26.

Hardware and Software Requirements

41

Chelsio 10 Gb Board and Driver

Avid ISIS v2.0 and later supports ultra high resolution clients (UHRC) clients. These clients require the Chelsio™ 10-Gb Ethernet adapter. Clients with the Chelsio 10-Gb adapter board can connect directly into the ISS2000 10-Gb port on the Avid ISIS Engine. These 10-Gb Ethernet clients support two streams of 1:1 uncompressed HD. Two 10-Gb clients can connect into one engine; one client to each ISS2000. Engines with v1.x ISS1000 hardware do not support 10-Gb clients.

c The Chelsio 10-Gb adapter board is shipped with a Small Form-factor Pluggable (SFP)+ optical transceiver. The Chelsio 10-Gb adapter board and SFP+ transceiver are tested and qualified to work as a single component. Do not remove or swap the SFP+ optical transceivers. The Chelsio adapter board and SFP+ transceivers are replaced as a single component.

If your client cannot connect directly to an Avid ISIS Engine, Avid has qualified several switches that provide 10-Gb connections for more remote locations, see “Layer 2 and Layer 3 Switches” on page 42.

n Access the Knowledge Base at www.avid.com/US/support to download the Avid ISIS Switch Reference Guide and sample configuration files. This document provides configuration information on the Ethernet switches that are qualified with the Avid ISIS shared storage network.

Instructions for installing the Chelsio 10-Gb adapter board, Chelsio driver, and Avid ISIS client software are provided in the Avid ISIS 7000 Client Guide. The Chelsio adapter board has been qualified in the following configurations:

• Slot 4 in the HP xw8400 (supported on dual quad-core processor systems only)

• Slot 6 in the HP xw8600

• Slot 3 in the HP Z400

• Slot 4 in the HP Z800

Once your Avid ISIS 10-Gb client hardware and software is installed, the following requirements are needed with the UHRC:

n See the Avid Interplay Software Installation and Configuration Guide for instructions on setting up and configuring the Avid Interplay Copy and Move Services.

• You need to use the Ultra High Resolution setting in the Client Manager Preferences with Avid editing clients

• Your workspace must be set to a 512 KB chunk size

• Your Avid ISIS infrastructure must be using v2.x switches (ISS2000 and IXS2000)

42

HP xw8600 Workstations and Broadcom Ethernet Connections

Avid ISIS clients using a built-in network port utilizing the Broadcom chipset and a Storage Group with a 512 KB chunk size, are limited to resolutions that draw 16 MB/s (50 Mb/s) or less. These clients include; laptops, Avid Interplay Assist, Avid iNews Instinct, and the HP xw8600 workstation using the built-in network port.

The built-in network port can be used for Ethernet connections to the Avid ISIS infrastructure when:

• using workspaces with 256 KB chunk sizes

• using workspaces with 512 KB chunk sizes and bandwidths of 16 MB/s or less

n For example, you can use the built-in Broadcom chipset to run two streams of DV 50 or DNxHD 36. Bandwidths are listed by resolution and number of streams on the Avid Knowledge Base. Search the Avid Knowledge Base for the Avid ISIS Performance and Redistribution Guide.

You are required to use the Intel Pro 1000 PT for your network connection in the xw8600 when:

• using workspaces with 512 KB chunk sizes and your xw8600 workstation using bandwidths higher than 16 MB/s

• using a Windows Vista, 64-bit client connected to an Avid Adrenaline

Layer 2 and Layer 3 Switches

Avid supplies the following layer 2 and layer 3 switches used in a Zone 2 and Zone 3 configurations.

• Cisco® 4900M containing 40 1-Gb ports and eight X2 based 10-Gb ports (Avid supports both LR and SR X2s)

• Cisco 4948-10GE containing 48 1-Gb ports and two X2 based 10-Gb ports (Avid supports both LR and SR X2s)

• Foundry Networks® FastIron® Edge X (FESX) 424 containing 24 1-Gb ports and two XFPs based on 10-Gb ports (Avid supports both LR and SR XFPs)

• SMC 8724ML3 containing 24 1-Gb ports and no 10-Gb ports

n Access the Knowledge Base at www.avid.com/US/support to download the Avid ISIS Switch Reference Guide and sample configuration files. This document provides configuration information on the Ethernet switches that are qualified with the Avid ISIS shared storage network.

Hardware and Software Requirements

43

Navigate to the [DVD drive]:\Tools_3rdParty\Switch_Configuration folder, and select the folder for your model switch.

Final Cut Pro Software Approved

Avid has tested Final Cut Pro as a client in the Avid ISIS shared storage environment. Initial testing was done with Avid ISIS v2.0.1 and Final Cut Pro v6.0.4. There is no Avid restriction on the QuickTime version. Use the QuickTime version recommended in the Final Cut Pro application. QuickTime v7.6 was the version used in the Avid testing. For information on

Minimum Supported Switch Firmware and IOS Versions

Manufacturer Model Firmware/IOS Description

Cisco 4900M Rommon: 12.2(44r)SG (and later)

IOS: 12.2 (46)SG (and later)

40 GigE (RJ-45), WS-X4920-GB-RJ45

or

8 10 Gb (X2/SC)WS-X4904-10GE8 10 Gb (X2/SC)

Cisco 4948 10GE Rommon: 12.2(31r)SGA (and later)

IOS: 12.2 (25) EWA8 (and later)

48 GigE (RJ-45), 2-10 Gb (X2/SC)

Foundry FESX 424 Firmware v02.3.01T3e3Boot ROM v02.3.01Te6(and later)

24 GigE (RJ-45), 4 GigE (SFP), 2-10 Gb (XFP/LC)

SMC 8724ML3

n This switch is approved for routing only data traffic to and from the corporate network. You cannot use this switch to do real-time video.

Loader v3.1.0.0Boot ROM v3.1.0.0Operation Code v3.1.1.56(and later)

24 GigE (RJ-45)4 GigE (SFP)

44

how many streams were qualified per client at various resolutions, see the Avid ISIS v2.1.1 Performance and Redistribution Guide on the Knowledge Base at www.avid.com/US/support.

n Avid Interplay Access supports the Mac OSX platform, and through this application Final Cut Pro QuickTime files and projects can be checked into Interplay. Any Interplay workstation can search for these files and edit their Interplay metadata, though there is currently no tightly integrated workflow between Avid Media Composer and Final Cut Pro within Interplay.

The following list characterizes the setup guidelines for your Final Cut Pro client with Avid ISIS:

• You need to stay in line with the general client parameters specified for all Avid ISIS Macintosh clients. The following are the specific hardware details used in Avid testing:

- Platforms — Mac Pro (early 2008) “Harpertown” Dual Quad-Core 3.0 or 3.2 GHz. Avid does not recommend using any Macintosh systems earlier than the Mac Pro platform with Final Cut Pro on Avid shared storage.

- Operating system — Mac OS 10.5.4 and later.

- Avid ISIS — Ethernet connection using the built-in network ports on the Macintosh system.

• Final Cut Pro editing software was characterized with the AJA KONA™3 hardware. The complete Apple Studio 2 bundle was installed.

• Verification tests on Apple Color and Sound Track Pro were run to verify push/pull capabilities.

• Final Cut Pro Storage Groups can be configured to either operate using 256 KB or 512 KB chunk sizes.

• Final Cut Pro clients are supported in ISIS Zones 1 and Zone 2 (not Zone 3).

Testing Performed as of the Avid ISIS v2.1.1 and Later

Final Cut Pro Version

Macintosh Operating System Version

Avid ISIS Client Version

Avid ISISInfrastructure Version

v6.0.4 v10.5.4 (32-bit) v2.0.1 v2.0.1

v6.0.5, v7.0 v10.5.4, v10.5.6 (32-bit) v2.0.4 v2.0.4

v6.0.5, v7.0 v10.6 (32-bit) v2.1 v1.7, v2.0.4

v6.0.5, v7.0 v10.6.2 (32-bit) v2.1.1 v1.8, v2.1.1

Special Notes

45

• The Avid ISIS Client Manager preference settings follow the same guidelines as for Avid editors. The default setting is set to Medium Resolution (limited to resolutions that draw 16 MB/s or less). Use the High Resolution setting when working with High Definition media (resolutions that draw higher than 16 MB/s). For data rate specifications, see the Avid ISIS Performance and Redistribution Guide.

• Digidesign Pro Tools software was not tested with Final Cut Pro clients.

Special Notes

This section contains important information about the Avid ISIS environment.

User Permissions

A user account with Administrator privileges is required to install Avid ISIS client software on Windows and Macintosh workstations.

Client Preferences

Client Preferences are automatically saved on upgrades or reinstalls from Avid ISIS v1.4 and later. They can be saved manually when you are upgrading from Avid ISIS v1.3. The Avid ISIS software installer DVD provides an application (SaveISISPreferences.exe) that can be used to manually save your ISIS client preferences when you are upgrading from Avid ISIS v1.3. This application is located in the: DVD drive:\AvidUnityISISClient folder. For information about manually saving preferences, see the Avid ISIS 7000 Client Guide.

The following is a summary of when it is necessary to manually save your preferences:

• Upgrading from v1.2 (32-bit or 64-bit) — save manually using 32-bit version of provided application. Restoration automatic on install of v1.4.

• Upgrading from v1.3 (32-bit) — saving and restoration is automatic.

• Upgrading from v1.3 (64-bit) — same as for upgrading from v1.2.

• Reinstallation of v1.4 (32-bit or 64-bit) — saving and restoration is automatic.

• When upgrading to ISIS v2.1.1 and later, the following client preferences are not carried over to v2.x and need to be reselected (if used):

- (Windows) Client Type preference setting — If upgrading your Windows clients from v1.6 and v1.7, your General > Client Type preference setting is not saved and is reset to the Medium Resolution setting (default). You must re-select your Client Type preference setting.

46

- (Macintosh) Client Type preference setting — If upgrading your Macintosh clients from v1.x, your General > Client Type preference setting is not saved and is reset to the Medium Resolution setting (default). In v2.0.x, your Remote Hosts preference setting is not saved. You must re-select these preference settings.

- (Windows and Macintosh) Auto mounted workspaces — You need to reselect any workspaces you want automatically mounted.

- (Windows and Macintosh) The “Assign Mount Point” option for workspaces — You need to reselect any workspaces you want mounted to a specific path or drive letter (selected from the right-click menu).

- (Windows and Macintosh) Auto Reserve (This option is deselected by default and is rarely used) — You need to reselect the Auto Reserve checkbox in the System Bandwidth dialog box. Only available when you have the Preferences > Enable Bandwidth Dialog selected.

Fast User Switching Not Supported

Fast User Switching is a Windows feature that allows multiple user accounts to log on to a computer simultaneously. Fast User Switching is enabled by default in Windows computers. The Fast User Switching feature and multiple concurrent logged on user modes are not supported in the Avid ISIS environment. The ISIS software does not distinguish the different drive letters mapped to the same workspaces on the same computer. Conflicts appear in the following two scenarios:

• When one user maps a drive letter to one workspace and another user maps the same drive letter to a different workspace

• When one user maps a workspace to one drive letter, and another user maps a different drive letter for the same workspace.

Virus Protection

Windows updates are not installed automatically on the System Director. If you are connected to the internet, Avid recommends you manually select your Windows updates and install them during a scheduled maintenance intervals. Some updates require that you restart the System Director. In addition, antivirus programs that contain autoscanning features (for example File System Auto-protect or scanning files on network drives) are not supported.

Access the Knowledge Base at www.avid.com/securityupdate and review the Microsoft Security Bulletin Addendum document. This link also includes antivirus software support on Avid products which can be found in the Avid Security Guidelines and Best Practices document.

Special Notes

47

c Virus protection software and Windows updates will result in workflow interruptions, and should be performed during a scheduled maintenance interval.

Avid ISIS v2.x Behavior

If you are updating from Avid ISIS v1.x to v2.x, the following sections summarize some of the highlights in the behavior not available in v1.x.

System Director

The Avid ISIS System Director uses an Intel® SR2500 server with 9 GB of memory and a 64-bit Window operating system. The new 64-bit System Director provides the following support:

• 64-bit System Director — 10 million files32-bit System Director — 2.5 million files

• 64-bit System Director — 500,000 folders (25,000 files per folder)32-bit System Director — 10,000 folders

• 5638 users

• 1000 groups — a user can be in 16 groups

Storage Blades

Avid ISIS has been qualified for use with 1 terabyte (TB) drives. The ISBs with the two 1 TB drives are referred to as i2000s. The i2000 ISBs require 512 KB chunk size, see “Storage Group Size” on page 47.

Storage Group Size

Storage elements are combined to create storage groups in the ISIS file system. These Storage Groups can be configured to operate using either 512 KB (default) or 256 KB chunk sizes. Earlier Avid ISIS releases used 256 KB chunk sizes. For more information about setting the chunk size, see the Avid ISIS 7000 Administration Guide.

n Avid ISIS switch hardware shipped with v1.x (ISS1000 and IXS1000) does not support 512 KB chunk sizes. If you have Avid ISIS v2.x software running on v1.x switches, you must select the 256 KB chunk size when adding storage elements to the file system to create Storage Groups.

You cannot change the chunk size of a Storage Group once the Storage Group has been created. To change the chunk size of an existing Storage Group, you must delete the Storage Group and create a new Storage Group with the desired chunk size. The chunk size selection is only available when adding the storage elements.

48

n Avid Unity MediaManager and Avid Unity TransferManager (workgroup 4) do not support 512 KB chunk sizes.

Chunk Size Support With ISB

All ISBs (i500, i1000, and i2000) support the 512 KB chunk size, although you must have v2.x switch hardware (ISS2000 and IXS2000) to use the 512 KB chunk size.

Mirrored Storage Groups, Single ISB Failure

It is considered an “unprotected state” if you have a single ISB failure in a mirrored Storage Group. In an unprotected state with no additional failures, read operations continue to function normally.

However, in an unprotected state a subsequent or infrastructure failure will cause operational issues which could result in failures when writing new data or prevent you from accessing data in the Storage Group. An additional ISB failure creates a situation in which data accessibility has been compromised. Networking issues, on the other hand, will not cause accessibility issues on previously written data but might prevent the successful completion of the active write operation.

This issue only applies when the Storage Group is in an unprotected state and the remove redistribution process on the failed ISBs has not been initiated. Therefore, it is highly recommended that the remove redistribution process is initiated immediately upon confirmation of any ISB failure. This ensures immediate protection (RAID or mirroring) of new data being written, and full protection of all stored data at the earliest possible time.

Adding or Removing ISBs (Mirrored or RAID)

When permanently adding or removing ISBs from an ISIS Storage Group it is recommended to do a full redistribution for all workspaces in the Storage Group. The full redistribution should be done after the ISB add or remove is complete. Examples of permanent changes would be adding or removing an engine to the storage stack.

The full redistribution makes sure all blocks in the Storage Group are optimally distributed based on the new permanent configuration. Doing a full redistribution immediately after the permanent adds or removes minimizes the chances of running into issues if a full redistribution is required in the future. One potential issue would be the storage blades getting full during a full redistribution and requiring the user to delete files to allow the redistribution to complete.

Special Notes

49

This recommendation does not apply to the case of removing and then replacing failed storage blades. For other examples of symmetric and non-symmetric redistributions, see the Avid ISIS v2.1.1 Performance and Redistribution Guide on the Knowledge Base at www.avid.com/US/support.

Adding an ISB to the File System

If you add an ISB (displays as an available storage element) to your file system, make sure you match the Protection and Chunk Size of the new storage element to the Protection and Chunk Size of the existing storage group. New storage elements are added with a default chunk size of 512 KB. You cannot mix the protection and chunk sizes within a Storage Group. To change the protection or chunk size of an ISB, you must remove the new storage element from the file system and add the storage element again select the same protection and chunk size of the existing Storage Group.

Zone 1 Switches

The ISIS v2.x generation ISX and ISS switches install in the same engines as earlier releases, the chassis has not changed. However, all the switches in the engines need to be of the same generation. The two new switches are labeled with ISX2000 and ISS2000. The new switches cannot be mixed in ISIS Engines with earlier versions of the switches (labeled ISX1000 and ISS1000). If your ISX and ISS switches are not labeled, consider them the earlier versions. The ISS2000 switches are required for 10-Gb clients and 512 KB chunk size, see “Storage Group Size” on page 47.

The Avid ISIS documentation refers to ISX2000 and ISS2000 switches as v2.x hardware and ISX1000 and ISS1000 switches as v1.x hardware.

Full Redistribution

Significant improvements have been made in this release when performing a full redistribution. After updating the Avid ISIS server software, and the ISIS software on all the clients, Avid recommends you do a full redistribution (onetime full remapping redistribution) at your earliest convenience to take advantage of the performance optimization introduced with Avid ISIS v2.x. After the full remapping redistribution, full redistributions that might have taken several hours in earlier releases can be performed in a matter of minutes, depending on the system load.

c Once you do a full redistribution with v2.x, v1.x clients cannot read from, or write to, those workspaces. For more details, see “Full Upgrade Instructions for v2.2.2” on page 31.

50

The faster full redistributions only apply to workspaces that have had symmetric configuration changes. This means that the same number of ISBs that were removed from a storage group need to then be added in a single configuration change. For examples of symmetric configuration changes search the Avid Knowledge Base for the Avid ISIS Performance and Redistribution Guide. As with all full redistributions, all workspaces in the storage group should be selected for the full redistribution.

A full redistribution is still recommended at 10 configuration changes. At 32 configuration changes the Avid ISIS software automatically performs a full redistribution.

Firmware Upgrade During a Redistribution

Do not perform an ISB firmware upgrade while a Redistribution is in process. Make sure all firmware upgrades are completed before any redistribution is started. The following events trigger redistribution:

• Moving a Workspace

• Clicking “Full Redistribution” on a Workspace

• Adding a Storage Element to a Storage Group

• Removing a Storage Element from a Storage Group

• Changing the state of a Workspace to mirrored or unmirrored

If a firmware upgrade must be done and a redistribution in progress, do the following:

1. Suspend the active redistribution using the Advanced Commands in Workspace window.

2. Verify that the Workspace displays “redistribution suspended” in the Status column and all other workspaces do not have “redistribution in progress” displayed.

3. Perform the firmware upgrade on the ISB(s) that must be upgraded.

4. Wait until the firmware upgrade is completed successfully.

5. Resume the redistribution using the Workspace window.

Avid Interplay Authentication

Avid Interplay Authentication requires the Avid ISIS System Director to use a virtual name. The System Director’s virtual name must not match the actual host name and must be entered in the General Configuration Options dialog box even if your Avid ISIS system configuration only has one System Director. For instructions on adding the virtual name, search the Avid ISIS 7000 Administration Guide for General Configuration Options.

Special Notes

51

Workspace Names

You must use Unicode characters in workspace names. The following is a list of 16 illegal characters you should not use in workspace names, workgroup names, filenames, user names, device names, and storage group names: \ / = @ [ ] % * ? + | : " ; , < >. You also should not use a period (.) as either the first or last character in the names you create, and you should not include a space in workspace names when in an Avid Interplay environment.

n The System Director does not support viewing regional language characters in the Management Console.

Workspace names beginning or ending with a period are no longer valid in Avid ISIS v1.4 and later. If you already have workspace names with periods and upgrade to Avid ISIS v1.4, the original issues continue to exist as outlined below:

• Windows — Data is preserved and intact with display issues. A filename or directory with a period at the end is invalid in Windows. As a result the Avid ISIS client is trying to interpret a period at the end of a workspace into something Windows can understand. This interpretation appears as a graphic instead of a period.

• Macintosh — Data is preserved and intact, but any workspace with a name that starts with a period is treated as a hidden directory by Mac OS X. By default such a workspace cannot be accessed via the Desktop and cannot be seen in the “/Volumes” folder in the Finder.

To access the contents of the Macintosh workspace:

t Click Go > Go to Folder… menu in the Finder and type the path “/Volumes/” followed by the workspace name (for example, “/Volumes/.MyWorkspace”).

A window opens showing the contents of the workspace and make the workspace temporarily visible as a subdirectory of “/Volumes.”

Macintosh Dual Port Network Connections

Macintosh clients do not support dual port network connections in the Avid ISIS environment.

Avid ISIS 7000 IP Port Usage

Avid ISIS v1.4 and later uses ports 4200–4599 on a dynamic basis for Firewall access. This access is for data transfers between the client and ISBs, as well as incoming message traffic from the System Director or ISBs. Previous releases used the port number range 4000–4399. For a complete list of the ports used in all Avid Products search the Avid Knowledge Base for the Avid Products and Network Site Preparation Guide.

52

Network Connections

The ISIS network topology uses two separate domains, with one domain represented by the ISSs on the left side of the ISIS Engine and the second domain represented by the ISSs on the right side. The default network IP address configuration is shown in the following table:

For more addressing information, see “IP Addressing Overview” in the Avid ISIS 7000 Setup Guide.

Avid ISIS does not support Zone 1, 10/100 BASE-T network interface connections. 10/100 BASE-T clients must be attached as a Zone 2 or 3 client.

n AirSpeed devices and TransferManagers must be connected as Zone 1 or Zone 2 clients.

Minimum Storage Space Requirement

Previously, the recommended amount space that you should keep available was one ISB for background functionality and failures. The revised space requirement statement is that you must now maintain 7% of free space in each Storage Group. In other words, you should not fill Storage Group more than 93% full. Exceeding 93% used space can produce severe performance issues in some situations.

To calculate the right amount of free space, log into the ISIS management Console and navigate to the Storage Group window. For each Storage Group, take the Effective number and multiply by 0.07. This will be your recommended free space in GBs. To assure that your Storage Group never exceeds the recommended space, create a new workspace in this Storage Group with the same size and label it “Headroom” and do not give anyone access to this workspace.

Enabling the Distributed File System on Windows Vista

Avid ISIS v2.0.4 and earlier disabled the Windows Vista Distributed File System (DFS) on Windows Vista clients. DFS was disabled because Avid ISIS clients running Windows Vista were experiencing delays when opening files over the shared storage network with DFS enabled. Windows Vista service pack 2 (SP2) corrects the delays experienced with DFS enabled. Avid ISIS v2.0.5 and later client software detects the service pack version installed

Default Network Addresses for Avid ISIS Engines

Location Network IP Addresses Subnet Mask

Left side of engine 192.168.10.0 255.255.255.0

Right side of engine 192.168.20.0 255.255.255.0

Special Notes

53

on the Windows Vista client and leaves DFS enabled if using Windows Vista SP2. If you have Windows Vista SP1 installed, DFS is disabled. If you need to run DFS on your Windows Vista client, perform the Windows Vista update to installs SP2 and reinstall the Avid ISIS v2.0.5 and later client software.

Spanning Tree PortFast Required with Dual Network Client Ports

If Spanning Tree PortFast is disabled when your system is recovering from a link failure using a dual network client port, a “semaphore time-out” error message appears.

Broadcom-Based Network Adapter Registry Key Setting

If you are connecting an Avid ISIS client that uses a Broadcom®-based network adapter you might need to use the following procedure to reduce the risk of Reassembly Failures, especially at higher resolutions (such as Avid DNxHD® 145). Although the Broadcom network adapter does not have a provision today for setting the Transmit (Tx) or Receive (Rx) Descriptors like the Intel MT Server network adapter, there is a registry key that can be changed on the Rx side (the side that is important for improved Read performance) to minimize the risk of packet loss.

The Avid ISIS v2.x client software includes the registry adjustment for the following computers.

• HP xw8600 workstation

• HP xw4400 workstation

• HP xw4600 workstation

If you install Avid ISIS client software on other clients that use the Broadcom-based network adapter, you need to perform the following procedure to change the Rx registry key value.

To check if your computer or laptop uses a Broadcom-based network adapter:

1. Right-click My Computer, and select Manage.

2. Click Device Manager in the left pane.

3. Click Network Adapters in the right pane to expand the list.

Broadcom is listed under the Network Adapters if you have a Broadcom Ethernet connection.

To change the Rx registry key value:

1. Click Start > Run.

2. Type Regedit to enter the Registry Editor application

54

3. Make sure that the highest level in the left pane of the Registry Editor is highlighted to ensure a complete search of the Registry. This is usually “My Computer.”

4. Select Edit > Find, or press Ctrl+F.

5. In the “Find What” field, type RxStdDescCnt and click Find Next.

6. Change the value of RxStdDescCnt from 200 (default) to 511 (no higher).

7. Select Edit > Find Next, or press F3.

n There are likely two or three (possibly more) instances of this key present. You need to change all instances to ensure the correct value is active at a given time.

8. Continue to search the Registry using the Find Next button until all instances of the key are found and have been changed to the value of 511.

9. Restart the computer.

After the restart, consider opening the Registry to confirm the setting has changed. Keep in mind that if the computer is re-imaged, or a new driver is installed, it is likely that this setting would manually need to be changed again.

Old Intel Driver On DVD

Requests have been made to include the Intel Pro 1000 v12.3 driver with the software installer DVD. This version of the Intel driver has been added in the kit and can be found on the Avid ISIS software installer DVD in the \Tools_3rdParty\Drivers_and_Firmware\Intel_Pro1000_12.3 folder.

The Intel Pro 1000 v12.3 driver is the highest Intel Pro driver version qualified on the 32-bit System Directors. If your 32-bit System Director is not at this version, do not update the driver. Updating the driver on the System Directors removes all assigned IP addresses. For more information on the Intel Pro driver, see “Update Intel Driver on the System Director” on page 18.

Replacing an Internal System Director Drive

To replace the System Director drive:

1. Remove the failed drive from the front of the System Director by releasing the drive latch on the front of the drive and pulling the drive from the chassis.

2. Insert the new drive completely into the open drive slot and close the drive latch.

The new drive initiates and completes the repair with no other intervention.

Loading the System Software

55

Loading the System Software

The Avid ISIS 7000 System Setup Guide contains complete instructions for loading the software onto the system. You can access the documentation in the top-level AvidUnityISISDocumentation folder on the Avid ISIS software installer DVD. For a summarized version of the procedure, see “Full Upgrade Instructions for v2.2.2” on page 31. The following sections include important information about each installation.

Installing Macintosh Client Software Using Safari

When installing the Avid ISIS software on a Macintosh client using the Safari™ browser; Safari completes the download, mounts the disk image, and starts the installer. Be aware that other browser applications do not automatically mount the disk image. After the software is successfully installed, dismount the installer volume.

To dismount the Avid ISIS installer volume on a Macintosh client:

1. Locate the mounted volumes listed in the left pane of the Finder window.

2. Select the volume that contains “AvidUnityISIS” in the name.

3. Click the eject button that appears to the right of the volume name.

Changing the Default Drive for the System Director Software

During installation, the installer defaults to loading the System Director software on drive D:. You can change that location by specifying a different drive for installation.

If you install the application to a location different from the default drive D, and then later install the application to the default drive, the new software does not function properly. You can correct this either before or after installation by copying three files from drive C to drive D.

To change the default installation directory before reinstalling the Avid ISIS application:

1. On drive D, create the following directory structure.

n You must spell the names exactly as they appear on drive C.

D:\Program Files\Avid Technology\AvidUnityISISSystemDirector

2. Copy the following files from the AvidUnityISISSystemDirector folder on drive C to the AvidUnityISISSystemDirector folder you created on drive D.

- Partition0

- Partition1

- PartitionDump.bin

56

3. Complete the installation, checking to see that installer places the application in the folder that was created and the System Director uses the correct files.

To change the default installation directory after reinstalling the Avid ISIS application:

1. Stop the System Director Service.

2. Copy the files listed below from their location on drive C to the same location on drive D:

- Partition0

- Partition1

- PartitionDump.bin

Drivers and Installers Available on DVD

The Avid ISIS installation DVD contains the following installers and drivers:

• Installers — The following installers are needed when connecting to an Avid ISIS system. Procedures for loading the installers are included in the Avid ISIS 7000 Setup Guide or the specific documentation for the device, such as AirSpeed.

- Avid ISIS System Director

- Avid ISIS Blade Installers

- Avid ISIS client Installers (the Windows client installer can be used directly from the DVD)

• Drivers — The following drivers can be found on the Avid ISIS software installer DVD:

- Drivers, firmware, and configuration files for external switches

- Drivers for the supported Intel Ethernet boards

- Java™

Java Runtime Environment

The Avid ISIS Client Manager requires version 6 (build 1.6) or higher of the Java Runtime Environment (JRE). Avid provides a qualified version of JRE for Windows systems on the Avid ISIS software installer DVD in the [DVD drive]:\Tools_3rdParty\Java folder.

For clients using a Macintosh system, download the Java software from the Apple® Web site (www.apple.com) or use the Apple Software Update.

Known Issues

57

Flash Player Software

To use the ISIS Management Console, you need to have the Adobe® Flash® Player installed on your system. If you encounter problems with the ISIS Management Console display, you might have an outdated version or multiple versions of the Flash Player installed. Uninstall any previous versions of Flash Player and install the Flash Player included on the Avid ISIS software installer DVD. Avid ISIS v2.x requires Flash Player v9.x and later.

Performance Overview

The performance for Avid ISIS clients and servers is based on the generation of the switch hardware (ISS and IXS) in the engine and the Chunk Size. The following gives you a base number of the MB/s you can expect of each generation. For the most up-to-date performance data on Avid ISIS, search the Avid Knowledge Base for the Avid ISIS Performance and Redistribution Guide.

• Avid ISIS v2.x hardware (ISS2000 and IXS2000) — The ISS2000 10-Gb port is able to support 600 MB/s per 10-Gb port to a Zone 2 switch. The 10-Gb clients are able get 300 MB/s regardless if they are connected to Zone 1 (direct connect) or Zone 2.

• Avid ISIS v1.x hardware (ISS1000 and IXS1000) — The ISS1000 10-Gb port is able to support 230 MB/s per 10-Gb port to a Zone 2 switch. The ISS1000 is able to support up to the total 260 MB/s. The remainder of the network bandwidth on that ISS can then be allocated to Zone 1 clients.

For example, 14 DV 50 clients are connected to an ISS by way of a supported Zone 2 switch. The total bandwidth of these clients is approximately 224 MB/s. This allows for up to 36 MB/s of additional network bandwidth that can be used by Zone 1 clients or servers on the same ISS.

Known Issues

The following are known issues with the Avid ISIS software. When a workaround exists, it appears in the paragraph directly following the issue description.

➤ If a Windows Client has a workspace mounted and that workspace is deleted, the Client Manager might continue to display a green icon indicating the workspace is still mounted.

Workaround: You need to restart the Client Manager and the missing workspace will no longer be displayed.

58

➤ If playing two streams of media during a non-symmetrical full redistribution on an Avid editor with a Nitris DX or Mojo DX attached, you will drop frames.

Workaround: You have the following options.

• Work with your media after the redistribution is finished.

• Start the Management Console Tool and suspend the redistribution. Finish working with your media and then resume the redistribution.

n Do not leave the redistribution in a suspended state for an extended period of time.

➤ The Avid ISIS File Gateway does not support Macintosh Common Internet File System (CIFS) clients that have non-ASCII usernames (including Asian and Diacritical characters). An error occurs on the Macintosh client indicating you have incorrect URL

➤ Macintosh CIFS Clients connected to the Avid ISIS File Gateway clients using the Terminal application hang when attempting to create a filename with invalid characters. Invalid characters are as follows:

? * < > | : " \ /

This hang occurs on Mac OS 10.6.2 and later. You must force quit or restart the Terminal application to clear the condition.

➤ If copying between the Avid ISIS File Gateway and a Macintosh CIFS client and the “share name” is renamed in the configuration file (on File Gateway server), the copy operation on the Macintosh client gets interrupted with an appropriate error message. Clicking OK closes the error message but the copy dialog remains displayed although nothing is being actually copied. Clicking cancel on the copy dialog also does not close dialog box. The CIFS share cannot be ejected since it still appears to be in use.

Workaround: You must force quit or restart the Macintosh Finder to clear the copy dialog box.

➤ The Profile tool detects the current versions of required software, drivers, and hardware components that are installed on a System Director and ISIS clients. The Avid ISIS software has not been updated to detect Windows Service Pack 3 (SP3). If your System Director or client has SP3 installed, the Profile results display as Failed. There is no action to take to correct the failure. This will be corrected in a future Avid ISIS software release.

Known Issues

59

➤ If you monitor the performance in the Windows Monitor counters, you will notice there is no Chelsio network interface board listed in the Windows Vista clients. The 10-Gb Chelsio driver has not been updated for the Windows Vista operating system. Chelsio needs to update their driver for the Windows Vista 64-bit operating system before these counters are displayed.

To open the Performance Monitor:

1. Click Start > Control Panel > Performance Information and Tools > Advanced Tools > Open Reliability and Performance Monitor.

2. Select Performance Monitor.

3. Click Add then select “Network Interface.” The Chelsio network interface board is not listed.

➤ There is a limitation with the Windows XP 32-bit operating system that limits the line speed of 10 Gbps to display as 1.4 Gbps. This operating system limitation does not affect the actual network interface speed. This limitation is seen in the 10-Gb Chelsio driver Interface Status dialog box (Network Places > Properties > Chelsio > Status, the speed displays as 1.4Gbps).

➤ If you attempt to install the client software again (without uninstalling), a “Repair/Remove” screen is displayed. If you select to “Repair” the ISIS client software, does the repair and prompts you to restart the client. After the client has started, the Client Manager software is unable to locate the ISIS system.

➤ The 64-bit clients might experience a fatal error to a blue screen when traversing through deeply nested directories. Avid experienced this error under the following condition: 64-bit client, 115 or more nested directories with path name more than 235 characters, with quick changes. Avoid using a file structure in your editing systems that exceeds these parameters.

➤ If the ISIS Management Console is opened from the Client Manager, and an Avid ISIS System Director failover occurs while the ISIS Management Console is open, the ISIS Management Console does not automatically reconnect to the new Active System Director.

Workaround: Once the Client Manager reconnects to the new Active System Director, you need to restart the ISIS Management Console within the Client Manager to connect to the new Active System Director.

60

➤ If you attempt to reinstall the client software from the Avid ISIS software installer DVD and select the repair option, an error message is displayed. The repair function is not supported in the Avid ISIS software.

Workaround: You must uninstall the Avid ISIS client software before installing a new version.

➤ If you attempt to mount more than 1800 workspaces, you might see an error message on Windows 64-bit systems stating, “The JVM could not be started. The main method may have thrown an exception.”

➤ The estimated amount of space available (which is usually measured in an amount of time at a particular resolution) might differ between what Avid ISIS calculates and what the Avid editing system calculates.

Avid ISIS accurately reports how much space is available for raw media at a particular resolution.

The Avid editing application accounts for overhead in formatting of the media and is more conservative in reporting how much space is available.

➤ ISIS v2.x has a new install status of “Downloading” when updating the ISB and switch firmware. While in the downloading state, the blade is downloading the firmware package from the FTP Publishing service on the System Director.

If a blade is in the downloading state for more than 15 minutes, it indicates that there is a problem retrieving the package or connecting to the FTP service.

Workaround: Open the Agent page for the blade and click the Statistics tab and click Network. Look for errors on either eth0 of eth1. If there are errors:

• Select “offline ISB”

• If possible move the ISB to a new engine. If problem persists, the ISB should be replaced.

• If the ISB cannot be moved to a new engine, move it to a different slot. If the problem persists, reseat the switch associated with the network errors (eth0 is associated with the right switch, eth1 is associated with the left switch). If the problem persists the ISB should be replaced.

If no errors are displayed in the Network view of the Agent page, check cabling between the System Director and engine. Verify the FTP Publishing service is running on the System Director (right-click My Computer > Manage > Services).

Known Issues

61

➤ When a new engine that has 10 Gb Link Aggregation disabled is added to an existing stack that has 10 Gb Link Aggregation enabled, the Link Aggregation software might be stuck in a resolution state for up to 20 minutes. At the end of this resolution cycle, the Link Aggregation functionality will be disabled on all chassis. At this point, the existing Link Aggregation groups need to be deleted and recreated. Once the groups have been recreated, 10 Gb Link Aggregation needs to be enabled.

Workaround: Enable 10 Gb Link Aggregation on the engine that is going to be added to the stack. When Link Aggregation is enabled on the engine to be added, it will automatically take the trunking information from the stack.

➤ If a client has a workspace mounted and that workspace is deleted within the Management Console and then recreated using the exact same name, the mounted workspace becomes inaccessible to the client, although it displays a green icon within Client Manager indicating that it is still accessible.

Workaround: To access that workspace again, unmount the workspace using the client manager and then mount it again.

➤ The Execute Disk Tests function of the Disk Analyzer tool found in the ISIS Toolbox is not supported in ISIS v2.1.1 and later. Running this tool causes the ISBs to assert and restart.

➤ If you have ISBs or ISSs that are not able to be contacted, the Avid ISIS Log Aggregator and ISB Connection Analysis tools hang waiting for a response from that component, requiring you to use the Windows Task Manager to quit the application.

For Log Aggregator, deselect the non-responsive hardware and re-run the application. For Connection Analyzer, you must resolve the hardware issue before using the application. To help investigate the problem, see Switch Infrastructure Diagnostics in the Avid ISIS 7000 Administration Guide.

➤ When attempting to consolidate media from an Avid editing client on a RAID workspace that has a failed ISB, the consolidate function in the editing application might fail with an Exception error.

Workaround: If the ISB failure cannot be repaired within your time frame, retry the consolidation again. The failure is intermittent.

➤ When the maximum number of licensed users are logged in to the Avid ISIS environment and another client attempts to log in, an “Invalid username or password” error displays.

The message should state that the maximum number of licenses has been reached.

62

n The client limit that you are licensed for is programmed into the System Director's application key (dongle).

➤ When you make any changes in the storage group Details pane and click the Close button, you are asked if you would like to save your changes. If you click Yes, your changes are not saved. You must re-apply the changes and click Apply before you click the Close button.

Workaround: To avoid this issue, always click Apply before you click the Close button.

➤ When exporting a QuickTime file to a local disk or shared Avid workspace, whose file size is larger than segment limit value set on Final Cut Pro v6.0.5, a general error message appears and the export fails. This error does not occurs with Final Cut Pro v7.0 and the export succeeds.

➤ When the Final Cut Pro Scratch Disk is saved to an ISIS workspace using the Autosave Vault feature, the copies of the project in Autosave Vault folder cannot be opened with Final Cut Pro. An error message is displayed stating “File error: Wrong type.”

➤ When the Final Cut Pro Scratch Disk is saved to an ISIS workspace using the Autosave Vault feature, more copies are automatically saved than is set in the Autosave Vault setting.

➤ Final Cut Pro v6.0.5 sometimes stops functioning if you Eject the ISIS workspace using the Final Cut Pro Open menu. When you finish with the ISIS workspace unmount the workspace using the Client Manager window.

➤ The Final Cut Pro “Modify > Make Offline > Move them to the Trash” option is not supported with Avid ISIS workspaces.

➤ The Avid ISIS client bandwidth allocation feature is not supported with Final Cut Pro.

➤ Macintosh Snow Leopard (Mac OS v10.6.2 and later) clients display an “END_MEDIA_EDITS_Video FAILED” error when exporting QuickTime movies to workspaces when the workspace name is greater nine characters.

➤ The Macintosh Finder might display the Avid ISIS folder contents incorrectly. For example, the contents of folders containing items whose name includes a pound sign (#) followed by numeric characters. For example, “project # 12” might be erroneously displayed with some items duplicated and some items missing.

Workaround: Avid recommends avoiding the use of names that include a pound sign (#) followed by numeric characters.

Known Issues

63

➤ Do not disconnect the PCI interface cable from either a Nitris DX or Mojo DX while it is powered up on the Macintosh editing system. If Avid ISIS is running on this system and the cable is removed, the Macintosh produces a kernel panic and reports ISIS as the problem. You must power down Macintosh prior to removing the PCI interface cable between the Macintosh and the Nitris DX or Mojo DX. The only way to power down the Nitris DX or Mojo DX system is to shut down the client connected to it.

➤ Close all applications that use an Avid ISIS workspace and unmount all workspaces before you attempt to restart or shut down your Macintosh client. If the mounted workspace is busy, you might see an error message from Client Manager about not being able to unmount the workspaces.

Workaround: Manually unmount the workspaces on the Macintosh client as follows:

1. Start the Terminal application:

Macintosh HD > Applications > Utilities > Terminal.app

2. At the command prompt in the Terminal Window, type:

umount /Volumes/<workspace-name> and press Enter

➤ The Path Diagnostics customized setting for Posix® tests does not work correctly on the Macintosh clients.

Workaround: Use the default option to automatically select the File Access Method instead.

➤ Deleting an ISS from a stack does not clear engine configuration.

Use the Reset Factory defaults button to clear stack configuration info.

➤ If your Avid ISIS environment includes an Avid Unity MediaManager as a client running on Windows Server 2000 SP4, the application event log on the system enters five informational messages in the Application Log regarding the AvidUnityISISClientAgent on every restart of the system. These extra error messages are harmless and have no affect on the application or environment.

➤ When in the Advanced tab of the Switch Agent page, if you select Switch Blade > “Reset to factory defaults” and enter the password to confirm the reset, one of the two switches in the engine becomes the master and the other switch keeps restarting.

Workaround: Log into the ISS Agent on the new master, click the System tab and select Basic, then click Submit in the Chassis Configuration window to correct the restarting issue.

Legal NoticesProduct specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.

This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be used in accordance with the license agreement.

Avid ISIS products or portions thereof are protected by one or more of the following United States Patents: 6,374,336; 6,415,373; 6,449,688; 6,760,808; 6,785,768; 7,111,115; 7,487,309; 7,660,947. Other patents are pending.

Avid products or portions thereof are protected by one or more of the following European Patents: 1040419. Other patents are pending.

Avid products or portions thereof are protected by one or more of the following United States Patents: 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601; 5,644,364; 5,654,737; 5,715,018; 5,724,605; 5,726,717; 5,745,637; 5,752,029; 5,754,851; 5,799,150; 5,812,216; 5,828,678; 5,842,014; 5,852,435; 5,987,501; 6,223,211; 6,532,043; 6,546,190; 6,747,705; 6,763,523. Other patents are pending.

Avid products or portions thereof are protected by one or more of the following European Patents: 0506870; 0635188; 0674414; 0752184; 1111910. Other patents are pending.

Part of the software embedded in this product is gSOAP software.

Portions created by gSOAP are Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This document is protected under copyright law. An authorized licensee of Avid Unity may reproduce this publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This document is supplied as a guide for Avid Unity. Reasonable care has been taken in preparing the information it contains. However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept responsibility of any kind for customers’ losses due to the use of this document. Product specifications are subject to change without notice.

Copyright © 2009 - 2010 Avid Technology, Inc. and its licensors. All rights reserved.

Attn. Government User(s). Restricted Rights LegendU.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or “commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.

Trademarks003, 192 Digital I/O, 192 I/O, 96 I/O, 96i I/O, Adrenaline, AirSpeed, ALEX, Alienbrain, AME, AniMatte, Archive, Archive II, Assistant Station, AudioPages, AudioStation, AutoLoop, AutoSync, Avid, Avid Active, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid DNxHD, Avid DS Assist Station, Avid Liquid, Avid Media Engine, Avid Media Processor, Avid MEDIArray, Avid Mojo, Avid Remote Response, Avid Unity, Avid Unity ISIS, Avid VideoRAID, AvidRAID, AvidShare, AVIDstripe, AVX, Axiom, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Boom, Bruno, C|24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8, Conectiv, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, Dazzle, Dazzle Digital Video Creator, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 003, DigiBase, DigiDelivery, Digidesign, Digidesign Audio Engine, Digidesign Development Partners, Digidesign Intelligent Noise Reduction, Digidesign TDM Bus, DigiLink, DigiMeter, DigiPanner, DigiProNet, DigiRack, DigiSerial, DigiSnake, DigiSystem, Digital Choreography, Digital Nonlinear Accelerator, DigiTest, DigiTranslator, DigiWear, DINR, DNxchange, DPP-1, D-Show,

Legal Notices

65

DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, EveryPhase, Expander, ExpertRender, Fader Pack, Fairchild, FastBreak, Fast Track, Film Cutter, FilmScribe, Flexevent, FluidMotion, Frame Chase, FXDeko, HD Core, HD Process, HDPack, Home-to-Hollywood, HYBRID, HyperControl, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, ISIS, IsoSync, iS9, iS18, iS23, iS36, ISIS, IsoSync, KeyRig, KeyStudio, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, Luna, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack, Massive Pack Pro, M-Audio, M-Audio Micro, Maxim, Mbox, Media Composer, MediaDock, MediaDock Shuttle, MediaFlow, MediaLog, MediaMatch, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MicroTrack, MIDI I/O, Midiman, Mix Rack, MixLab, Moviebox, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, Nitris, NL3D, NLP, Nova, NRV-10 interFX, NSDOS, NSWIN, Octane, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Ozone, Ozonic, Painterly Effects, Palladium, Personal Q, PET, Pinnacle, Pinnacle DistanTV, Pinnacle GenieBox, Pinnacle HomeMusic, Pinnacle MediaSuite, Pinnacle Mobile Media, Pinnacle Scorefitter, Pinnacle Studio, Pinnacle Studio MovieBoard, Pinnacle Systems, Pinnacle VideoSpin, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools|HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, Pro Tools, QuickPunch, QuietDrive, Realtime Motion Synthesis, Recti-Fi, Reel Tape Delay, Reel Tape Flanger, Reel Tape Saturation, Reprise, Res Rocket Surfer, Reso, RetroLoop, Reverb One, ReVibe, Revolution, rS9, rS18, RTAS, Salesview, Sci-Fi, Scorch, Scorefitter, ScriptSync, SecureProductionEnvironment, Serv|LT, Serv|GT, Session, Shape-to-Shape, ShuttleCase, Sibelius, SIDON, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, Solaris, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, Strike, Structure, Studiophile, SubCap, Sundance Digital, Sundance, SurroundScope, Symphony, SYNC HD, Synchronic, SynchroScope, SYNC I/O, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, Titansync, Titan, TL Aggro, TL AutoPan, TL Drum Rehab, TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, tools for storytellers, Torq, Torq Xponent, Transfuser, Transit, TransJammer, Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, VTEM, Work-N-Play, Xdeck, X-Form, Xmon, XPAND!, Xponent, X-Session, and X-Session Pro are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

Alacritech is a registered trademark of Alacritech, Inc. Apple, Macintosh, and Safari are either registered trademarks or trademarks of Apple Computer, Inc., registered in the U.S. and other countries. ATTO is a trademark of ATTO Technology, Inc. Chelsio Communications and the Chelsio logo, and combinations thereof, are trademarks of Chelsio Communications, Inc. Dell and Dell Precision are trademarks or registered trademarks of Dell Computer Corporation. HP is a registered trademark of Hewlett-Packard Company. Intel is a registered trademark of Intel Corporation. Firefox is a trademark of Mozilla Corporation. Java is a trademark of Sun Microsystems in the United States and/or other countries. Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. SafeNet and Sentinel are either registered trademarks or trademarks of SafeNet, Inc. All other trademarks contained herein are the property of their respective owners.

Avid ISIS 7000 Version 2.2.2 ReadMe • 0130-30223-01 Rev. E • September • 9/9/10