Ddpv3bestpractiseguide
Total Page:16
File Type:pdf, Size:1020Kb
DDPV3BestPractiseGuide November 27, 2013 1 Contents 1 Introduction 4 2 Best practises in setting up the ethernet network in combina- tion with the DDP 4 2.1 Each ethernet port on the DDP must be a unique subnet . 4 2.2 Autosensing or not . 4 2.3 A 1GbE infrastructure . 5 2.4 An all 10 GbE infrastructure . 5 2.5 1 GbE switch with 10 GbE uplink . 5 2.6 Flow Control, Bandwidth Limiting, Traffic Control and Switch buffer Overrun . 6 2.7 Subnet and VLAN . 6 2.8 Teaming, Bonding . 7 2.9 Firewall Protection . 7 3 Using DDP with Avid Applications except DS 7 3.1 Avid Facts To Know . 7 3.1.1 One Avid MediaFiles directory per DDP volume or fold- ervolume . 8 3.1.2 Not enough Drive Letters . 8 3.1.3 Do not use these characters with Avid . 8 3.2 Lock files and bins . 8 3.3 Sharing Methods . 9 3.3.1 Shared Bins . 9 3.3.2 Shared Bins and Projects . 9 3.3.3 Shared Bin and Project Limitations . 10 3.3.4 Shared Bin Lock Icon Limitation . 11 3.3.5 Naming Conventions . 11 3.3.6 Shared Bins and Windows Explorer . 12 3.4 Time Synchronization . 12 3.5 User Access Control with Avid edit applications and DDP . 12 3.6 Avid Editors and AMA material on Windows . 12 3.6.1 One large DDP volume and foldervolumes for all projects with a foldervolume for AMA material . 13 3.7 Using the DDP in combination with Avid Storage . 13 3.8 With AVID DS . 13 3.9 With Interplay . 14 3.10 Using DDP with Avid with Edit while Ingest applications . 14 3.11 Using DDP with EVS in an Avid environment . 15 3.12 Using DDP with EVS in a non Avid environment . 15 4 Using DDP with Final Cut Pro 15 5 Using DDP with Final Cut Pro X 16 6 Using DDP with ToolsOnAir with Ingest While Edit 16 2 7 Using DDP with Softron with Ingest While Edit 16 8 Using the DDP with Grass Valley Edius and K2 also with In- gest While Edit 17 9 Searching for Files 17 10 Using DDP with Telestream and rendering machines 17 11 Using DDP with Adobe products 18 12 DDP and DPX/Cin Applications 18 12.1 DDP and Scratch . 18 12.2 DDP and Autodesk . 18 12.3 DDP and DVS . 19 12.4 DDP and Digital Vision . 19 13 DDP and Linux Clients 19 14 DDP and Audio Applications 19 14.1 DDP and Pro Tools . 19 14.2 DDP and Fairlight . 20 15 DDP and MAM systems 20 16 DDP and Backup solutions 20 17 DDP and XSAN 21 18 DDP and Shares (CIFS, SMB) 21 19 DDP and SNMP 21 3 1 Introduction This manual assumes that the DDP drivers for Windows, Mac and Linux have been installed and that proper communication exists between desktops and DDP via optionally an ethernet switch. This BestPractiseGuide explains how to use DDP drives with Avid appli- cations, FinalCutPro, Pro Tools, Adobe Premiere, Edius, Fairlight, Avid DS, Resolve, Digital Vision, Autodesk, Tools on Air, Softron, Quadrus, Atempo, Primestream, Storage DNA, Archiware and many others. It shows an alterna- tive for Spotlight. The AVFS drivers in combination with the DDP software have enhance- ments implemented. There are enhancements for Avid, Final Cut Pro, FCPX, Edius, Digital Vision, Autodesk, DVS, Scratch, Adobe/Iridas, EVS, Telestream, Pro Tools, Fairlight, Merging, Nuendo, After Effects and others. 2 Best practises in setting up the ethernet network in combination with the DDP A remark upfront: at anytime during installation you can use ping to see if a connection is valid between ethernet endpoints. Ping also shows the roundtrip time which should always be less then 1ms. Once everything is properly in- stalled and a DDP drive is available on the desktops use the Aja or Blackmagic speedtest to confirm the bandwidth of the connection. 2.1 Each ethernet port on the DDP must be a unique subnet There are many ways to setup an ethernet infrastructure. To narrow this down we start with the capabilities of ethernet ports on a system (DDP or desktop). Each ethernet port on the DDP or desktop no matter if it is a 1 or 10 GbE port must have an unique subnet. To each subnet multiple endpoints (each endpoint is an ethernet port on a desktop) can be connected. The subnetmask defines the subnet. The factory settings of the ethernet ports on for example a DDP16D are NIC1: 172.16.5.4. NIC2: DHCP, NIC3: 172.17.5.4, NIC4: 172.18.5.4 and so on with the subnet set to 255.255.0.0. If the subnet mask would be 255.0.0.0. all ports would be in the same subnet and there is no way of knowing what is happening and the DDP might even crash. Because service connection (or VPN) is mandatory for DDP service, NIC2 is set to DHCP. Special care must be taken that the lease which this ports gets upon connection also has a subnet different from all other NICs. So if the DDP has 4 GbE ports and there are 20 desktops with one endpoint for each of these desktops one can for example decide to connect 5 Macs to each of the 4 subnets. 2.2 Autosensing or not There is always the discussion whether IP configuration on desktops and switches should be set to automatic (autosensing) or manual (fixed). A way to prevent confusion it to start with defining your requirements on the desktop and setting 4 these manually (such as flow control on, normal 1500 MTU or 9000, 1000baseT (1GbE)). The DDP itself uses autosensing but both frame size and flow control must be set manually on the DDP. They must be identical to the settings on the desktop. How and if switch settings should be set or altered will be discussed now. 2.3 A 1GbE infrastructure When solely a 1GbE/RJ45 infrastructure is available or installed simple stan- dard unmanaged 1GbE switches from brands such as Cisco budget series, Net- gear, SMC and many others can be used. Of course managed switches can also be used. Unmanaged switches sense what the settings of the endpoint are and act accordingly. Although most unmanaged switches may suppport jumbo frames (9000 size package) it is not always guaranteed. It is recommended in general not to use jumbo frames with an all 1GbE infrastructure because it is a setting which can easily be overlooked causing unexplanable intermittant prob- lems. When an application such as EVS for example strongly benefits from using jumbo frames, jumbo frames can be enabled on all components of the subnet. Flow control must be enabled on all ports and spanning tree must be switched off. 2.4 An all 10 GbE infrastructure Most 10 GbE infrastructures are short range (SR) fiber based with LC connec- tors. Most switches available have SFP+ electrical ports. In such ports optical transceivers with on one side SFP+ and on the other side an LC connector fits. A transceiver for SR can be the Finisar FTLX8571D3BCL. Ardis Technologies does not advise specific switch brands. One can use switches from Fujitsu, HP, Force but other will do as well. With some care regarding cable length also elec- trical cabling with SFP+ connections can be used. In the future also 10 GbE switches with RJ45 jacks will become more common. 10 GbE switches are man- aged. Flow control on all ports must be enabled. Spanning tree option should be inactive. Jumbo frames should be used to get the best performance. 10 GbE switches operate mostly in a fixed mode due to the transceivers plugged in there. When a 1 GbE switch with 10 GbE uplink is connected to the 10 GbE switch you must be careful when using jumbo frames. Make sure that all components of the subnet, switches and endpoints also are set to jumbo frames. 2.5 1 GbE switch with 10 GbE uplink There are many 1GbE switches with 10 GbE uplink. However not all support Jumbo frames and some of these switches such as those from SMC can not be used with flow control. Fujitsu and HP are good choices. When ordering such switch often three parts are needed: the switch, the electrical module which fits in it and has electrical interface such as SFP+ and the proper transceiver. Transceivers from the switch manufacturers can be costly and can always be purchased from a Finisar distributor for a better price. In standard installation it is best practise to enable flow control on all 1GbE ports and have flow control 5 off on the 10 GbE ports. Also it is best to use frame size of 1500 (standard) on all endpoints (DDP and desktops) unless needed otherwise. With flow control on on the 10 GbE line the 10 GbE bandwidth can get as low as 1GbE in some situations. On the other hand with flow control off on 10 GbE the amount of buffer memory in the switch determines when and if packet overrun occurs re- sulting in packet retransmission. In most cases however the 10 GbE bandwidth will still be okay. In larger and or critical installations Ardis Technologies can enable Traffic Control. With proper use of Traffic Control and flow control en- abled on 10 GbE line, the 10 GbE bandwidth remains intact and retransmission are absent. See further for an explanation of flow control, bandwidth limitation and traffic control. 2.6 Flow Control, Bandwidth Limiting, Traffic Control and Switch buffer Overrun When involved in IP infrastructure and DDP you will hear phrases such as Flow Control, Bandwidth Limiting, Traffic Control, buffer in switches and buffer overrun.