Pinnacle Systems ISIS 7000 - 4.7 Setup Guide

Avid® ISIS® | 7500 - 7000
Setup Guide
Legal Notices
Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.
This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents
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 ISIS | 7500 - 7000 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 ISIS | 7500 - 7000. 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 © 2014 Avid Technology, Inc. and its licensors. All rights reserved.
The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:
Copyright © 1988–1997 Sam Leffler Copyright © 1991–1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
The following disclaimer is required by the Independent JPEG Group:
This software is based in part on the work of the Independent JPEG Group.
This Software may contain components licensed under the following conditions:
Copyright (c) 1989 The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Copyright (C) 1989, 1991 by Jef Poskanzer.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.
.
2
Copyright 1995, Trinity College Computing Center. Written by David Chappell.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.
Copyright 1996 Daniel Dardailler.
Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Daniel Dardailler makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Modifications Copyright 1999 Matt Koss, under the same license as above.
Copyright (c) 1991 by AT&T.
Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software.
THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
This product includes software developed by the University of California, Berkeley and its contributors.
The following disclaimer is required by Paradigm Matrix:
Portions of this software licensed from Paradigm Matrix.
The following disclaimer is required by Ray Sauers Associates, Inc.:
“Install-It” is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code equivalent of “Install-It,” including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be liable for any damages resulting from reseller’s failure to perform reseller’s obligation; or any damages arising from use or operation of reseller’s products or the software; or any other damages, including but not limited to, incidental, direct, indirect, special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised, knew or should have known of the possibility of such damages.
The following disclaimer is required by Videomedia, Inc.:
“Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with respect to its merchantability or its fitness for any particular purpose.”
“This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by Videomedia, Inc. and V-LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use of this software will allow “frame accurate” editing control of applicable videotape recorder decks, videodisc recorders/players and the like.”
The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample Source Code:
©1993–1998 Altura Software, Inc.
The following disclaimer is required by Interplay Entertainment Corp.:
The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products.
This product includes portions of the Alloy Look & Feel software from Incors GmbH.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/
© DevelopMentor
).
This product may include the JCifs library, for which the following notice applies:
JCifs © Copyright 2004, The JCIFS Project, is licensed under LGPL (http://jcifs.samba.org/). See the LGPL.txt file in the Third Party Software directory on the installation CD.
3
Avid Interplay contains components licensed from LavanTech. These components may only be used as part of and in connection with Avid Interplay.
Attn. Government User(s). Restricted Rights Legend
U.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.
Trademarks
003, 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 Ignite, 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, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Bruno, C|24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 002, Digi 003, DigiBase, 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, Do More, DPP-1, D-Show, DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, Euphonix, EUCON, 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, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, InGame, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, iS9, iS18, iS23, iS36, ISIS, IsoSync, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack, Massive Pack Pro, Maxim, Mbox, Media Composer, MediaFlow, MediaLog, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MIDI I/O, Mix Rack, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, NewsVision, Nitris, NL3D, NLP, NSDOS, NSWIN, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Painterly Effects, Palladium, Personal Q, PET, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools, Pro Tools|HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, 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, ScriptSync, SecureProductionEnvironment, Serv|GT, Serv|LT, Shape-to-Shape, ShuttleCase, Sibelius, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, SubCap, Sundance, Sundance Digital, SurroundScope, Symphony, SYNC HD, SYNC I/O, Synchronic, SynchroScope, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, TimeLiner, 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, Transit, TransJammer, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Video the Web Way, VideoRAID, VideoSPACE, VTEM, Work-N-Play, Xdeck, X-Form, Xmon and XPAND! are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.
Apple, Macintosh, and Safari are either registered trademarks or trademarks of Apple Computer, Inc., registered in the U.S. and other countries. HP is a registered trademark of Hewlett-Packard Company. Intel is a registered trademark of Intel Corporation. Java is a trademark of Sun Microsystems in the United States and/or other countries. Kingston is a registered trademarks of Kingston Technology Corporation. All other marks may be the property of their respective titleholders. Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners.
Avid ISIS | 7500 - 7000 Setup Guide • 0175-30978-00 Rev. C • June 2014• Created 6/4/14
4

Contents

Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Accessing the Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 1 Avid ISIS | 7500 - 7000 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Hardware Overview and Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
System Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
System Director Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
System Director Rear Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Second System Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Engine Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Engine Rear View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Integrated Ethernet Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Storage Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Storage Group Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chunk Size Support With ISB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Adding an ISB to the File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Adding or Removing ISBs (Mirrored or RAID). . . . . . . . . . . . . . . . . . . . . . . . . . 24
Moving Workspaces Between Storage Groups. . . . . . . . . . . . . . . . . . . . . . . . . 25
Mirrored Storage Groups, Single ISB Failure . . . . . . . . . . . . . . . . . . . . . . . . . . 25
RAID-6 Storage Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
RAID-6 Storage Groups, Single ISB Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
RAID-6 Storage Groups, Dual ISB Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Automatic Redistribution on Disk Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Network Zone Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5
Zone 1 Clients (Direct Connected). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
10 Gb Client Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Zone 2 Clients (Indirect Connect) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Zone 1 and Zone 2 Clients Mixed Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Zone 3 and Zone 4 Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Link Aggregation Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Connecting the Engine CX-4 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Removing the Avid Engine Interconnect Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
10 Gb Link Aggregation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Link Aggregation Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Recommended Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Supported Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Other Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Chapter 2 Avid Software and Hardware Install Checklist . . . . . . . . . . . . . . . . . . . . . . . 40
Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Hardware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
New System Director and Engine Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Switch and ISB Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Recreating a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Chapter 3 Installing the ISIS System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Rack-Mounting the Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Rack-Mounting Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Installing Rack-Mount Rails and Brackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Rack-mount Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Positioning the System Director in the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Separating the Slide Rails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Attaching Inner Slide Rails to the System Director . . . . . . . . . . . . . . . . . . . . . . 52
Attaching the Outer Rails to a Square-Hole Rack . . . . . . . . . . . . . . . . . . . . . . . 53
Attaching the Outer Rails to a Round-Hole Rack . . . . . . . . . . . . . . . . . . . . . . . 55
Securing the System Director in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6
Mounting the Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Installing Blades and Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Installing IXS and ISS Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Connecting a Keyboard, Monitor, and Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Connecting the Optional Application Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Connecting Power to Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Connecting Power Cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Three 20 Amp V AC Circuits for Three Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Three 20 Amp V AC Circuits for Two Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Two 20 Amp V AC Circuits for Two Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Turning System On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Connecting ISIS Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Engine Configuration v2.x Hardware Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Setting Up Network Addresses In the Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Two-Engine Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Three- to Twelve-Engine Stacking Summary With v2.x Switches . . . . . . . . . . . . . . 71
Three- to Twelve-Engine Connections With v2.x Switches . . . . . . . . . . . . . . . . . . . 72
Hi-Gig Link Aggregation Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 4 Installing Software and Configuring 10 Gb Link Aggregation . . . . . . . . . . 79
IP Addressing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Loading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Activating the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Installing the Optional Application Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Creating an Active File System on the System Director. . . . . . . . . . . . . . . . . . . . . . 85
Binding the Storage Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Checking the Status of the System Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Installing Software on the Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Engine Does Not Appear in Add Engine List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Check Switch IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Loading Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Configuring a 10 Gb Link Aggregation Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7
Chapter 5 Avid ISIS Software Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
What You Need to Activate the ISIS Software License. . . . . . . . . . . . . . . . . . . . . . . . . . 96
License Activation Using an Internet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
License Activation Without an Internet Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Deactivating the License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
License Requirement with Host Name Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Chapter 6 Configuring Two Stacks of ISIS Engines . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ISIS Two Stack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
External Switch Link Aggregation Connection Guidelines . . . . . . . . . . . . . . . . . . . 106
IP Address Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
IP Addressing With Two Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Static IP Addresses Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Connecting Two Stacks of Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Setting Up Two Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Reconfiguring One Stack into Two Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Chapter 7 Configuring System Director Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
System Director Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Enabling a System Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Setting IP Addresses for Crossover Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Configure a Failover Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Stopping and Restarting the System Directors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Chapter 8 Status LEDs and Stacking Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
LED Locations and Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
LED Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Recovering from Stacking Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Set One Switch Back to Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Rebuilding the Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Chapter 9 Avid ISIS | 7500 - 7000 Pre-Upgrade Information . . . . . . . . . . . . . . . . . . . . 128
Zone 2 Switch Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
System Director Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
ISIS Engine/Switch Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
On Site Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Spares Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8
Additional spares for a comprehensive spares parts list: . . . . . . . . . . . . . . . . . . . . 133
Chapter 10 Avid ISIS | 7500 - 7000 Upgrade Guidelines . . . . . . . . . . . . . . . . . . . . . . . . 134
Health Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Component Requirements From Previous ISIS | 7500 - 7000 Releases . . . . . . . . 136
ISIS | 7500 - 7000 Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Copying the Metadata to the New Default Location On the System Director . . . . 138
Avid ISIS Software Installation From the USB Flash Drive . . . . . . . . . . . . . . . . . . 140
Intel Network Driver and BIOS Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
64-bit System Director BIOS Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Intel RAID Controller Driver Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Record IP Addresses on the System Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
System Director Intel Pro Driver Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Post Upgrade System Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Chapter 11 Avid ISIS Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Overview and Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Software Component Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Software Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
FTP Server Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Install Control Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Monitoring Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Running the Avid ISIS Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Chapter 12 Avid ISIS Recommended Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Minimum Storage Space Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Daily Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Weekly Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Monthly Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Redistribution Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Saving ISIS Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Available Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Client Manager Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Status Indicators and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
9
Complete Server Room Shutdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
False Link Aggregation Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Displayed Link Alert Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Restart All Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Chapter 13 Adding and Replacing Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Adding Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Adding an Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Replacing an Engine Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Replacing an Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Replacing the System Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Replacing the Network Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Chapter A Using the Product Recovery USB for 64-bit System Directors. . . . . . . . . 176
Reinstalling the Windows Storage Server 2008 R2 Operating System . . . . . . . . . . . . 176
Configuring the System Drive Using Windows 2008 Storage Server Setup . . . . . . . . . 178
Chapter B Specifications and Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Uninterruptible Power Supply (UPS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Supported Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Appendix C Safety and Regulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Warnings and Cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Proposition 65 Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
FCC Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Class A Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Canadian Notice (Avis Canadien) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Class A Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
LED Safety Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
European Union Declaration of Conformity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Disposal of Waste Equipment by Users in the European Union. . . . . . . . . . . . . . . . . . 189
10
Argentina Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Australia and New Zealand EMC Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Japan EMC Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Class A Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Korean EMC Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Class A Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Taiwan EMC Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
11

Using This Guide

The Avid ISIS® media network provides a high-performance distributed file system that contains high-capacity shared media storage for workgroups of connected Avid
This document describes the features for all Avid ISIS | 7500 - 7000 shared storage networks.
n
Therefore, your system might not contain certain features that are covered in the documentation.

Symbols and Conventions

Avid documentation uses the following symbols and conventions:
Symbol or Convention Meaning or Action
n
c
w
> This symbol indicates menu commands (and subcommands) in the
A note provides important related information, reminders, recommendations, and strong suggestions.
A caution means that a specific action you take could cause harm to your computer or cause you to lose data.
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.
order you select them. For example, File > Import means to open the File menu and then select the Import command.
®
editing workstations.
This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.
(Windows) or (Macintosh) 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.
Symbol or Convention Meaning or Action
Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the

If You Need Help

If 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.
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
3. Check the documentation that came with your Avid application or your hardware for maintenance or hardware-related issues.
If You Need Help
mouse action. For example, Command+Option+C or Ctrl+drag.
www.avid.com/US/support.
4. Visit the online Knowledge Base at 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.
www.avid.com/US/support. Online services are

Accessing the Online Documentation

The Avid ISIS online documentation contains all the product documentation in PDF format. You can access the documentation in the AvidISISDocumentation folder on the Avid ISIS installer kit. Download and install Acrobat Reader on your Avid ISIS before you can access the PDF documentation.
To access the online documentation from the installer kit:
1. Insert your Avid ISIS USB flash drive with the Avid ISIS software kit into the USB port.
2. Navigate to the [USB flash drive]:\.AvidISISDocumentation folder, and double-click the PDF file for the document you want to view.
13

Avid Training Services

Avid 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 800-949-AVID (800-949-2843).
www.avid.com/support and follow the Training links, or call Avid Sales at
Avid Training Services
14

1 Avid ISIS | 7500 - 7000 System Overview

The Avid ISIS® system enables multiple clients to capture, play, and edit video and audio media. This chapter provides an overview of the Avid ISIS | 7500 - 7000 system and the basic function of each Avid hardware component within the system.
This guide describes how to connect cables between components that create a basic system and then how to connect more than one basic system together to create a larger, redundant system.
To prepare your site for installation of an Avid ISIS system, see the Avid Products and Network
n
Site Preparation Guide on the Avid Knowledge Base or included in the documentation folder on the top level of the Avid ISIS installer software installer kit.

Hardware Overview and Naming Convention

Each system component has a specific Avid name that defines its function. Become familiar with these terms while using the documentation. The following table, used in conjunction with the figure that follows the table, provides the actual nomenclature and the terms used in this guide to describe that nomenclature:
Product name Term used and description
Avid ISIS shared storage network System or shared network storage environment
The Avid ISIS consists of the hardware, Avid software, and other hardware supplied by the customer, such as external Ethernet
®
switches.
Hardware Overview and Naming Convention
Product name Term used and description
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 storage blade (labeled i500, i1000, i2000, i4000, i8000)
Avid ISIS Integrated Ethernet switch blade ISIS Integrated Switch (ISS)
Avid ISIS Expansion Integrated Ethernet switch blade
Integrated power supply and cooling fans Power supplies
Avid ISIS engine Called Chassis in the software interface
ISIS Storage Blade (ISB)
This hot swappable sled is accessible from the front of the ISIS engine and contains two SATA drives.
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.
ISIS Expansion Switch (IXS)
This hot swappable switch is accessible from the rear of the ISIS engine and is used to stack multiple ISIS engines. The IXS2000 indicates second generation hardware; first generation hardware is labeled IXS1000.
Three hot swappable power supplies are accessible from the rear of the ISIS engine.Two power supplies are required to power the ISIS engines.
Contains the ISBs, ISSs, IXSs, power supplies, and an internal midplane.
c
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
Although there are many components in Avid ISIS shared storage network, the basic components needed to create the system are a System Director, an engine containing ISIS Integrated Switch (ISS), ISIS Expansion Switch (IXS), ISIS Storage Blades (ISB), and one or more clients.
The second generation ISIS switches are branded with an IXS2000 and ISS2000 silk-screen. If your IXS and ISS switches are not labeled, consider them the earlier versions.
You cannot mix new switches (labeled IXS2000 and ISS2000) with original switch hardware (labeled IXS1000 and ISS1000). All switches in the engine, and engines in the stack must be from the same generation of hardware.
16

System Director

The Avid ISIS documentation refers to IXS2000 and ISS2000 switches as v2.x hardware and IXS1000 and ISS1000 switches as v1.x hardware.
Basic Avid ISIS | 7500 - 7000 Shared Storage Network Hardware
Rear view
ISIS Integrated Switch (ISS)
System Director
Front view
Power supply
ISIS Integrated Expansion Switch (IXS)
ISIS Storage Blade (ISB)
Engine
System Director front view
ID
The System Director is 1U in size (see “System Director Front Panel” on page 18) and manages the metadata by storing directory information and file attributes. The System Director does not store the data used by share clients (for example media files); these data files are stored on the ISBs within the engine.
The System Director password is preset to is-admin. The System Director Web Page
n
Administrator user has no default password (password is blank).
You can have two System Directors configured in a redundant configuration, one Active and the other Standby. If the Active System Director goes down, the Standby System Director takes over. You need at least one System Director to run the Avid ISIS system.
System Directors, workgroup servers, and clients must all be synchronized with a common time of day. For information on setting the Network Time Protocol (NTP), see
Addresses In the Stack” on page 67
.
17
“Setting Up Network
The System Director provides a location to coordinate file access modes (read/write), file
System disk (ID 1)System disk (ID 0)
ID
ID
Control panel
BCA
GHDFE
HALT
RST
locking, range locking, performance data collection, logging, file lookup, and directory change tracking for client systems. The System Director provides:
Identity of all storage elements connected to the system
Information about the ISS and IXS modules in the configuration.
List of workspaces including names and unique ID numbers
List of users and groups within the system
Identity of all System Directors in the system (if more than one)

System Director Front Panel

The following figure shows the front view and control panel of the System Director.
System Director Front View
System Director
The following table describes the control panel shown in the previous figure.
System Control Panel
Letter Component Description
A Universal Serial Bus (USB) port USB 2.0 device port on the front of the system supports one USB
device. Recommended for use when re-imaging the system drives or loading software. Two more USB ports are located on the back of the system.
B Halt or Non-maskable interrupt
(NMI) button
The halt or NMI signal halts the processor, which effectively halts the server. An NMI is the highest priority interrupt and cannot be masked by software.
If the Halt/NMI button is pressed, the NMI signal locks the
c
system and the system must be restarted to clear the interrupt.
18
System Director
Power supplies
Slots not used
Serial 1 Gb Ethernet VideoUSB
System Control Panel
Letter Component Description
C System reset button Preforms a soft reset when pressed. Do not use this button unless the
system has had a fatal error and must be restarted. A soft reset restarts the system; it clears all active program memory (you lose unsaved work) and shuts down all active programs.
D Four green network activity
LEDs
E Red System error LED Illuminates red when an error is detected with the system (fan, power
F System Drive activity LED Indicates drive activity from the onboard SATA controller and blinks
G System ID button When pressed it illuminates (blinks) blue and also illuminates an
H Power button Press to turn on the enclosure. Power button illuminates green when
Illuminates green when a good network connection is established and blinks when there is network activity on the four built-in 1 GB network ports.
The number beside the LED corresponds with the number beside the network port on the rear of the enclosure. For example, Connector 1 is LED 1 on the front. See
supply, temperature, voltage).
when either of the system drives is being accessed.
LED on the rear of the enclosure. The rear LED is also blue and is visible on the lower left-hand side of the Ethernet ports inside of the enclosure. This LED helps you to identify a system for servicing when it is installed in a high-density rack/cabinet populated with several other similar systems.
the power is on.
“System Director Rear Panel” on page 19.

System Director Rear Panel

The following figure shows the rear panel of the System Director and the function of each connection.
System Director Rear View
19

Second System Director

You can purchase a second System Director and configure it on the same subnets as the original System Director. This provides a redundant System Director that is in constant contact with the original System Director. The second System Director automatically takes over if the original System Director fails (called failover).
For true redundancy connect the second System Director to a different engine than the first
n
System Director. The Active and the Standby System Directors must be the same model server; you cannot mix SR2500 and AS3000 servers.

Engine

The engine contains the ISBs, ISSs, IXSs, power supplies, and an internal midplane. The engine stores the data created and shared by the clients. The data is passed in and out of the engine through the switches.
The engine components have the following properties and functions:
ISBs can support either 250 GB, 500 GB, 1 terabyte (TB), 2 terabyte, or 4 terabyte drives, with two drives in each ISB. The drive size is identified by the label on the front of the ISB (i500, i1000, i2000, i4000, i8000). As technology advances, the storage capacity of the drives could increase, allowing the total storage per ISB/engine to increase.
Engine
An ISS provides connections for clients though 1000BASE-T Ethernet ports. A 10 Gb Ethernet port using SFP+ transceivers connects clients or serves as an uplink port. The ISS has an engine interconnect port and a management port for configuration. See
Ethernet Switches” on page 22
An IXS connect multiple engines (one IXS for each subnet), providing up to 384 TB of storage, or 192 TB of mirrored storage. See

Engine Front View

The front of the engine allows access to the 16 ISBs. The first is in the upper left portion of the front and the last ISB is in the lower right.
“Integrated
.
“Integrated Ethernet Switches” on page 22.
20
Each ISB can be removed and replaced separately with the power on.
Fifth ISB
First ISB
Power supplies
IXS moduleISS module
1234 5678
12 345 6
7 8 9 10 11
If you replace an ISB with power on, the LEDs in all of the ISBs go off momentarily. This does
n
not represent a problem. All functions are still active and working properly.

Engine Rear View

The following figure shows the rear of the engine in a configuration that contains the following:
Three power supplies (with fans)
Engine
Integrated Switch blade (ISS)
Integrated Expansion Switch blade (IXS)
In a basic configuration containing two engines, each of the engines contains two ISS modules.
n
The IXS module is used with an ISS module in an engine only when the configuration exceeds two engines.
21

Power Supplies

The power supplies are turned on when the power cord is plugged in; they do not have power switches. The power supplies not only provide power, but they also contain fans that cool the system. The system only needs two of three power supplies to supply the needed power to function properly. You can remove and replace a power supply temporarily while the system is running if one fails.
Engine
c
w
Do not remove the failing supply until immediately before you replace it. Replace the power supply as soon as possible to maintain the proper airflow.
Only trained Avid technicians should remove and replace the power supply while the system is running. Since power to the system is still applied internally to the midplane always keep your hands outside the engine when a power supply is missing.

Integrated Ethernet Switches

The two integrated Ethernet switches, ISS and IXS, serve different purposes and contain different types of connections. You must have at least two switches in each engine for the system to operate.
ISS Module
The connections on the ISS module are used for the following:
Management connection — used to configure the Avid engine hardware during installation. This information is used by Avid representatives to originally configure your system before turning it over to you.
1 Gb (RJ-45 cable) — direct connect for clients and the System Directors.
High speed engine interconnect (CX-4 cable) — proprietary Avid bus that connects switch blades between engines allowing subnets to connect between the engines.
10 Gb XFP or SFP+ MSA form factor transceiver (for Optical cable) — used for a 10 Gb connection to a switch or 10 Gb Ethernet clients.
w
Use only an Avid recommended SFP+ transceiver in the 10 Gb XFP connection, and only Avid trained representatives should remove and replace the XFP transceiver. Avid currently supports Picolight XFP, Dell Networking XFP, and Foundry
22
®
XFP.

Storage Configurations

High speed engine interconnect (Hi-Gig)
Link
Activity
Management connection
Link
Activity
10-Gb connection
1-Gb connections
Status
123 4 5678
ACT LINK
10 GIG
Engine interconnections
Link
Activity
Management connection
1 2 3 4 5 6
7 8 9 10
10 1111
IXS Module
The IXS is needed only if you are connecting three or more engines. When connecting three or more engines, two IXS modules are installed in one engine. The IXS offers the following connections:
Management connection — used to configure the switch during installation and to monitor switch functions.
High speed engine interconnect (Hi-Gig) — proprietary Avid interconnection that stacks the switches to create one large virtual switch.
In a basic configuration containing one or two engines, each of the engines contains two ISS
n
modules. The IXS module is used with an ISS module in an engine only when the configuration exceeds two engines.
Storage Configurations
A maximum of twelve Avid ISIS Engines can be stacked and populated with either 250 GB, 500 GB, 1 terabyte (TB), 2 terabyte or 4 terabyte SATA drives. A fully populated Avid ISIS system with 1 TB drives provides up to 384 terabytes (TB) of storage, or 192 TB of mirrored storage.
23
You can have mixed ISB drive sizes in an engine (250 GB, 500 GB, 1 TB, 2 TB, and 4 TB drives). You can even mix different size ISBs in a Storage Group. However, the larger ISBs in the mixed Storage Group use only the amount of storage that is available in the smaller ISBs.

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 512 KB (default) or 256 KB chunk sizes. For more information about setting the chunk size, see the Avid ISIS Administration Guide.
Avid ISIS switch hardware shipped with v1.x (ISS1000 and IXS1000) does not support 512 KB
n
chunk sizes. If you have Avid ISIS v2.x software running on v1.x switches, you must select the 256KB chunk size when adding storage elements to the file system to create Storage Groups.
You cannot change the chunk size of a Storage Group after it has been created. To use a different chunk size, you must delete the Storage Group and create a new one with the desired chunk size. The chunk size selection is available only when adding the storage elements.
Storage Configurations
c
Chunk Size Support With ISB
Adding an ISB to the File System
Adding or Removing ISBs (Mirrored or RAID)
When you delete Storage Groups all data on that Storage Group is lost.
All ISBs (i500, i1000, and i2000, i4000 and i8000) with the latest v2.x switch hardware (ISS2000 and IXS2000) support the 512 KB chunk size.
If you add an ISB (displays as an available storage element) to your file system, make sure you match the chunk size of the new storage element to the chunk size of the existing Storage Group. New storage elements are added with a default chunk size of 512 KB. You cannot mix chunk sizes within a Storage Group. To change the chunk size of an ISB, you must remove the new storage element from the file system and add the storage element again choosing the correct chunk size.
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, after the ISB add or remove is complete. Examples of permanent changes include adding or removing an engine to the storage stack.
24
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 change minimizes the chances of running into issues if a full redistribution is required in the future, such as the storage blades becoming full during a full redistribution and requiring you to delete files to allow the redistribution to complete.
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 Performance and Redistribution Guide on the Knowledge Base at www.avid.com/US/support
Moving Workspaces Between Storage Groups
You can move workspaces between Storage Groups that use the same chunk sizes. Workspaces cannot be moved between Storage Groups of different chunk sizes (256 KB and 512 KB chunk sizes).
For information on how to move data from a 256 KB chunk size workspace to a 512 KB chunk size workspace, search the Avid Knowledge Base at
v2.x Moving Workspaces using RichCopy in the Avid ISIS Tech Alerts.
Clients should not access workspaces that are in the process of being moved between Storage
n
Groups that use a different chunk size. Avid recommends that clients unmount these workspaces until the move is complete to avoid an unintentional access. Once the move begins, it cannot be canceled.
Storage Configurations
.
www.avid.com/onlinesupport/ for Avid ISIS
Mirrored Storage Groups, Single ISB Failure
An “unprotected state” exists 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 compromises data accessibility. 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, Avid highly recommends initiating the remove redistribution process 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.
25

RAID-6 Storage Groups

Avid ISIS supports two types of data protection. Besides mirrored Storage Groups, you can create redundant array of independent disks (RAID) Storage Groups. RAID storage provides more storage at a lower cost per GB. 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 advantages to using RAID Storage Groups:
Migration from mirrored to RAID workspaces can become part of your normal workflow. You can move 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 increase available GB per physical engine from 50% of installed capacity in mirrored to 75% in RAID.
RAID workspaces have the following 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).
Storage Configurations
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 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 the Avid ISIS ReadMe.
Supports only resolutions that draw 16 MB/s (50 Mb/s) or less.
For example, you can run two streams of DV 50 or DNxHD 36. Bandwidths are listed by
n
resolution and number of streams on the Avid Knowledge Base. Search the Avid Knowledge Base for the Avid ISIS Performance and Redistribution Guide.
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.
To do a non-symmetrical full redistribution, limit the bandwidth used by your clients in that Storage Group. For more detailed guidance, see the Avid ISIS Performance and Redistribution Guide on the Knowledge Base at
26
www.avid.com/US/support.

Automatic Redistribution on Disk Failure

c
RAID-6 Storage Groups, Single ISB Failure
RAID-6 Storage Groups, Dual ISB Failure
Avid does not recommend a non-symmetric redistribution when your RAID Storage Group capacity exceeds 80%.
When a single ISB fails in an ISIS Storage Group configured with RAID protection, the Storage Group continues to function normally at a lower bandwidth. For more information see
Storage Groups, Single ISB Failure” on page 25
After confirming the failure of an ISB, initiate the remove redistribution process of the failed ISB immediately. There are two benefits to doing this:
All new writes to the Storage Group have the full benefit of RAID-6 protection (dual-parity protection).
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).
An “unprotected state” exists if there are 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), under certain circumstances that the system might be unable to correctly update the parity information when writing new data. As a result, 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.
“Mirrored
.
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, initiate the remove redistribution process of the failed ISB 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.
Automatic Redistribution on Disk Failure
Avid ISIS performs an automatic redistribution on Disk Failure notification. Storage Managers continuously monitor disk status and send a “Disk Failed” notification to the System Director upon determination that a disk is not usable. The System Director then removes the Storage Manager from its associated Storage Group. The removal of the Storage Manager from the
27
Automatic Redistribution on Disk Failure
Storage Group initiates redistributions on all workspaces associated with that Storage Group. The System Director then prevents the Storage Manager 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 Manager is removed from the Storage Group, but is not unbound from the ISIS Systems for the following reasons:
The Storage Manager participates in the removal redistribution. This is required to prevent data loss when there are unprotected workspaces or when full redundancy has not been attained for all data blocks.
The Storage Manager continues to report status, such as physically replacing the blade.
Auto removal status is reported in the System Event Log. A sequence of event log entries is generated for the initial report of the failure, the decision to remove the Storage Manager, and subsequent success or failure. Events are also logged for the start and stop of all the workspace redistributions.
When using Automatic Redistribution:
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.
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 Manager from the Storage Group but not from the file system. Once an automatic redistribution has occurred and completed, the removed Storage Manager should be removed from the file system. You must first remove the Storage Manager 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.
28

Client

A client uses services provided by the Avid ISIS architecture. The client system, using a 1 Gb or 10 Gb Ethernet connection, communicates with the ISBs through the ISS to create, modify, and read files stored in the actual ISB. Avid ISIS | 7500 - 7000 supports 330 clients (150 active clients), each using dual-stream video and up to 8 tracks of audio.
A client uses mechanisms specific to the operating system to display, create, and delete files within the Avid ISIS shared storage network system. For example, when viewed from a Windows operating system, the system sees a server containing many shares that are mapped to drive letters.

Network Zone Configurations

All clients in the shared storage network are classified by zones, depending on how they connect to the network. The following list defines the clients in each network layer by their zone classification:
A System Director must be attached to both subnets, but can be attached only once to each
n
subnet.
Client
Zone 1 Client — Connected to ISIS VLANs with an ISS 1 Gb or 10 Gb port (direct connect)
Zone 2 Client — Connected to ISIS VLANs with a 1 Gb or 10 Gb port on an Avid qualified layer-2 switch (non-routed)
Zone 3 Client — Connected to an Avid qualified layer-3 switch (routed) with known Quality of Service (QoS); traffic routed to ISIS (one hop) and load-balanced across ISIS VLANs (approximately a 60/40 ratio)
Zone 4 Client — Connected to the house network using an edge or a core switch with unknown QoS; traffic routed to Avid ISIS (measured by the number of hops) and load-balanced across ISIS VLANs (approximately a 60/40 ratio)
Clients that can connect to one zone can run in any lower-numbered zone — for example, a
n
Zone 3 client can also run as a Zone 2 or Zone 1 client.
Support for different client and device types vary by zone:
Zone 1 — AirSpeed playout, Transfer Manager
Zone 2 — AirSpeed ingest, editors, Interplay
Zone 3 — Instinct, Assist, certain editors
Zone 4 — Instinct, Assist; typical formats include DV25, MPEG-2 proxy (2 Mb/s)
29
The following examples describe different types of Avid ISIS | 7500 - 7000 configurations.
Zone 1
Chassis interconnect
10 GB ethernet
Engine
Engine
Intel Pro 1000 MT/PT board
Client systems
in Zone 1
1 GB ethernet
10 GB ethernet
10 GB board
10 GB board
System Director
ISS VLAN 10
ISS VLAN 20
ISS VLAN 20ISS VLAN 10

Zone 1 Clients (Direct Connected)

Any client that is connected directly to an ISIS is considered a Zone 1 or direct connected client. Each Integrated Switch Blade has a total of eight 1 Gb Ethernet ports and one 10 Gb Ethernet port. A single engine has the capacity to support 18 clients or servers, subtracting any ports that are to be used by the System Directors. The following table defines the total number of 1 Gb ports in Zone 1 based on what is available by the number of engines and System Directors in the configuration. In addition, each ISS2000 provides a 10 Gb Ethernet port connection for one 10 Gb client.
Connect TransferManagers and AirSpeed servers to Zone 1 or Zone 2.
n
A Zone 1 (direct connect) configuration consists of a group of clients connected directly to the 1-Gb and 10 Gb connections of the ISS in the engine. The System Director also connects to both subnets through both ISS modules using a 1 Gb port.
Avid ISIS | 7500 - 7000 Zone 1 Network Configuration
Network Zone Configurations
30
Loading...
+ 171 hidden pages