® Interplay | Engine Failover Guide for AS3000 Servers September 2014
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 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. This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents. This document is protected under copyright law.
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.
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.
Contents Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Renaming the Local Area Network Interface on Each Node . . . . . . . . . . . . . . . . . . 39 Configuring the Private Network Adapter on Each Node . . . . . . . . . . . . . . . . . . . . . 42 Configuring the Binding Order Networks on Each Node . . . . . . . . . . . . . . . . . . . . . 46 Configuring the Public Network Adapter on Each Node. . . . . . . . . . . . . . . . . . . . . . 47 Configuring the Cluster Shared-Storage RAID Disks on Each Node . . . . . . . . . . . . 48 Configuring the Cluster Service . .
Appendix A Windows Server Settings Included in Revision 4 and Later Images . . . . 116 Creating New GUIDs for the AS3000 Network Adapters . . . . . . . . . . . . . . . . . . . . . . . 116 Removing the Web Server IIS Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Removing the Failover Clustering Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Disabling IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using This Guide Congratulations on the purchase of Interplay | Production, a powerful system for managing media in a shared storage environment. This guide is intended for all Interplay Production administrators who are responsible for installing, configuring, and maintaining an Interplay | Engine with the Automatic Server Failover module integrated. This guide is for Interplay Engine clusters that use Avid AS3000 servers.
Symbols and Conventions Date Revised Changes Made January 10, 2012 Corrected step 1 in “Starting the Installation and Accepting the License Agreement” on page 78 and added cross-reference in “Testing the Complete Installation” on page 108. January 6, 2012 Revised “Testing the Cluster Installation” on page 71 for additional enhancements. December 12, 2011 Revised “Testing the Cluster Installation” on page 71 to describe command line method.
If You Need Help Symbol or Convention Meaning or Action 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. | (pipe character) The pipe character is used in some Avid product names, such as Interplay | Production.
Avid Training Services You can access the Interplay Production User Information Center through a browser from any system in the Interplay Production environment. You can also access it through the Help menu in Interplay | Access and the Interplay | Administrator. The Interplay Production Help combines information from all Interplay Production guides in one Help system. It includes a combined index and a full-featured search.
1 Automatic Server Failover Introduction This chapter covers the following topics: • Server Failover Overview • How Server Failover Works • Installing the Failover Hardware Components • Clustering Technology and Terminology Server Failover Overview The automatic server failover mechanism in Avid Interplay allows client access to the Interplay Engine in the event of failures or during maintenance, with minimal impact on the availability.
How Server Failover Works The following diagram illustrates the components of a cluster group, including sample IP addresses. For a list of required IP addresses and node names, see “List of IP Addresses and Network Names” on page 31. Cluster Group Intranet Resource groups Clustered services Failover Cluster 11.22.33.200 Node #1 Intranet: 11.22.33.44 Private: 10.10.10.10 Interplay Server (cluster application) 11.22.33.201 Private Network Node #2 Intranet: 11.22.33.45 Private: 10.10.10.
How Server Failover Works When the server is online, the resource monitor regularly checks its availability and automatically restarts the server or initiates a failover to the other node if a failure is detected. The exact behavior can be configured using the Failover Cluster Manager. Because clients connect to the virtual network name and IP address, which are also taken over by the failover node, the impact on the availability of the server is minimal.
Server Failover Configurations Server Failover Configurations There are two supported configurations for integrating a failover cluster into an existing network: • A cluster in an Avid ISIS environment that is integrated into the intranet through two layer-3 switches (VLAN 30 in Zone 3). This “redundant-switch” configuration protects against both hardware and network outages and thus provides a higher level of protection than the dual-connected configuration.
Server Failover Configurations Two-Node Cluster in an Avid ISIS Environment (Redundant-Switch Configuration) Avid network switch 2 running VRRP or HSRP VLAN 30 Avid network switch 1 running VRRP or HSRP VLAN 30 Interplay editing clients Interplay Engine cluster node 1 Private network for heartbeat Cluster-storage RAID array Interplay Engine cluster node 2 LEGEND 1 GB Ethernet connection Fibre Channel connection The following table describes what happens in the redundant-switch configuration as a result
Server Failover Configurations Dual-Connected Configuration The following diagram illustrates the failover cluster architecture for an Avid ISIS environment. In this environment, each cluster node is “dual-connected” to the network switch: one network interface is connected to the VLAN 10 subnet and the other is connected to the VLAN 20 subnet. If one of the subnets fails, the virtual server remains online through the other subnet.
Server Failover Requirements Server Failover Requirements You should make sure the server failover system meets the following requirements. Hardware The automatic server failover system was qualified with the following hardware: c • Two Avid AS3000 servers functioning as nodes in a failover cluster. For installation information, see the Avid AS3000 Setup Guide. • Two ATTO Celerity FC-81EN Fibre Channel host adapters (one for each server in the cluster), installed in the top PCIe slot.
Server Failover Requirements Disk Infortrend S12F-R1440 Disk 3 Database disk 814 GB or larger Disk HP MSA 2040 Disk 1 Quorum disk 10 GB Disk 2 Database disk 870 GB or larger Antivirus Software You can run antivirus software on a cluster, if the antivirus software is cluster-aware. For information about cluster-aware versions of your antivirus software, contact the antivirus vendor.
Installing the Failover Hardware Components Installing the Failover Hardware Components A failover cluster system includes the following components: • Two Interplay Engine nodes or two Interplay Archive nodes (two AS3000 servers) • One of the following shared-storage RAID arrays: - Infortrend S12F-R1440 - HP MSA 2040 The following topics provide information about installing the failover hardware components for the supported configurations: • “AS3000 Slot Locations” on page 20 • “Failover Cluster
Installing the Failover Hardware Components Failover Cluster Connections: Avid ISIS, Redundant-Switch Configuration Make the following cable connections to add a failover cluster to an Avid ISIS environment, using the redundant-switch configuration: • • First cluster node: - Top-right network interface connector (2) to layer-3 switch 1 (VLAN 30) - Bottom-left network interface connector (3) to the bottom-left network interface connector on the second cluster node (private network for heartbeat) - Fi
Installing the Failover Hardware Components Failover Cluster Connections: Avid ISIS, Redundant-Switch Configuration, Infortrend Interplay Engine Cluster Node 1 AS3000 Back Panel 1 2 3 4 Ethernet to Avid network switch 1 Ethernet to node 2 (Private network) Fibre Channel to Infortrend Infortrend RAID Array Back Panel Fibre Channel to Infortrend Interplay Engine Cluster Node 2 AS3000 Back Panel 1 2 3 4 Ethernet to Avid network switch 2 LEGEND 1 GB Ethernet connection Fibre Channel connection 22
Installing the Failover Hardware Components Failover Cluster Connections: Avid ISIS, Redundant-Switch Configuration, HP MSA Interplay Engine Cluster Node 1 AS3000 Back Panel 1 2 3 4 Ethernet to Avid network switch 1 Ethernet to node 2 (Private network) Fibre Channel to HP MSA HP MSA RAID Array Back Panel Fibre Channel to HP MSA Interplay Engine Cluster Node 2 AS3000 Back Panel 1 2 3 4 Ethernet to Avid network switch 2 LEGEND 1 GB Ethernet connection Fibre Channel connection 23
Installing the Failover Hardware Components Failover Cluster Connections, Dual-Connected Configuration Make the following cable connections to add a failover cluster to an Avid ISIS environment as a dual-connected configuration: • • First cluster node (AS3000): - Top-right network interface connector (2) to the ISIS left subnet (VLAN 10 public network) - Bottom-right network interface connector (4) to the ISIS right subnet (VLAN 20 public network) - Bottom-left network interface connector (3) to the
Installing the Failover Hardware Components Failover Cluster Connections, Avid ISIS, Dual-Connected Configuration, Infortrend Interplay Engine Cluster Node 1 AS3000 Back Panel 1 2 3 4 Ethernet to ISIS left subnet Ethernet to ISIS right subnet Ethernet to node 2 (Private network) Fibre Channel to Infortrend Infortrend RAID Array Back Panel Fibre Channel to Infortrend Interplay Engine Cluster Node 2 AS3000 Back Panel 1 2 3 4 Ethernet to ISIS left subnet Ethernet to ISIS right subnet LEGEND 1 GB
Installing the Failover Hardware Components Failover Cluster Connections, Avid ISIS, Dual-Connected Configuration, HP MSA Interplay Engine Cluster Node 1 AS3000 Back Panel 1 2 3 4 Ethernet to ISIS left subnet Ethernet to ISIS right subnet Ethernet to node 2 (Private network) Fibre Channel to HP MSA HP MSA RAID Array Back Panel Fibre Channel to HP Interplay Engine Cluster Node 2 AS3000 Back Panel 1 2 3 4 Ethernet to ISIS left subnet Ethernet to ISIS right subnet LEGEND 1 GB Ethernet connection
Clustering Technology and Terminology Clustering Technology and Terminology Clustering is not always straightforward, so it is important that you get familiar with the technology and terminology of failover clusters before you start. A good source of information is the Windows Server 2008 R2 Failover Clustering resource site: www.microsoft.com/windowsserver2008/en/us/failover-clustering-technical.aspx The following link describes the role of the quorum in a cluster: http://technet.microsoft.
2 Creating a Microsoft Failover Cluster This chapter describes the processes for creating a Microsoft failover cluster for automatic server failover. It is crucial that you follow the instructions given in this chapter completely, otherwise the automatic server failover will not work.
Before You Begin the Server Failover Installation For more details about Microsoft clustering technology, see the Windows Server 2008 R2 Failover Clustering resource site: www.microsoft.com/windowsserver2008/en/us/failover-clustering-technical.aspx Before You Begin the Server Failover Installation Before you begin the installation process, you need to do the following: • Make sure all cluster hardware connections are correct. See “Installing the Failover Hardware Components” on page 20.
Before You Begin the Server Failover Installation use sqauser as an example of a Server Execution User. This account is automatically added to the Local Administrators group on each node by the Interplay Engine software during the installation process. n The Server Execution User is not used to start the cluster service for a Windows Server 2008 installation. Windows Server 2008 uses the system account to start the cluster service.
Before You Begin the Server Failover Installation The account for these objects must be disabled so that when the Create Cluster wizard and the Interplay Engine installer are run, they can confirm that the account to be used for the cluster is not currently in use by an existing computer or cluster in the domain. The cluster creation process then enables the entry in the AD.
Before You Begin the Server Failover Installation The following table provides a list of example names that you can use when configuring the cluster for an ISIS redundant-switch configuration. You can fill in the blanks with your choices to use as a reference during the configuration process. IP Addresses and Node Names: ISIS Redundant-Switch Configuration Node or Service Item Required Example Name Where Used Cluster node 1 • SECLUSTER1 See “Creating the Cluster Service” on page 55.
Before You Begin the Server Failover Installation The following table provides a list of example names that you can use when configuring the cluster for an ISIS dual-connected configuration. Fill in the blanks to use as a reference. IP Addresses and Node Names: ISIS Dual-Connected Configuration Node or Service Item Required Example Name Where Used Cluster node 1 • SECLUSTER1 See “Creating the Cluster Service” on page 55. SECLUSTER2 See “Creating the Cluster Service” on page 55.
Before You Begin the Server Failover Installation IP Addresses and Node Names: ISIS Dual-Connected Configuration (Continued) Node or Service Item Required Example Name Where Used Interplay Engine service • SEENGINE 1 Network Name (virtual host name) ______________________ • 2 ISIS IP addresses - public (virtual IP addresses) See “Specifying the Interplay Engine Details” on page 80 and “Specifying the Interplay Engine Service Name” on page 82.
Preparing the Server for the Cluster Service Windows Server 2003: DNS Entries Component Computer Account in DNS Dynamic Active Directory Entrya DNS Static Entry b Cluster node 1 node_1_name Yes No Cluster node 2 node_2_name Yes No MSDTC No No Yes Microsoft cluster service No No Yes Interplay Engine service (virtual) No No Yes a. Entries are dynamically added to the DNS when the node logs on to Active Directory. b.
Preparing the Server for the Cluster Service Changing Default Settings for the ATTO Card on Each Node You need to use the ATTO Configuration Tool to change some default settings on each node in the cluster. To change the default settings for the ATTO card: 1. On the first node, click Start, and select Programs > ATTO ConfigTool > ATTO ConfigTool. The ATTO Configuration Tool dialog box opens. 2. In the Device Listing tree (left pane), click the expand box for “localhost.” A login screen is displayed. 3.
Preparing the Server for the Cluster Service 6. Change the following settings if necessary: - Boot driver: Enabled. - Execution Throttle: 32 - Device Discovery: Node WWN - Data Rate: - For connection to Infortrend, select 4 Gb/sec. - For connection to HP MSA, select 8 Gb/sec. - Interrupt Coalesce: Low - Spinup Delay: 30 You can keep the default values for the other settings. 7. Click Commit.
Preparing the Server for the Cluster Service 8. Reboot the system. 9. Open the Configuration tool again and verify the new settings. 10. On the other node, repeat steps 1 through 6. Changing Windows Server Settings on Each Node Revision 4 and later images for the AS3000 Windows Server 2008 R2 Standard includes system settings that previously required manual changes. For information about these settings, see “Windows Server Settings Included in Revision 4 and Later Images” on page 116.
Preparing the Server for the Cluster Service Configuring Local Software Firewalls Make sure any local software firewalls used in a failover cluster, such as Symantec End Point (SEP), are configured to allow iPv6 communication and IPv6 over IPv4 communication. Currently the SEP Firewall does not support IPv6. Allow this communication in the SEP Manager.
Preparing the Server for the Cluster Service n The top left network connector on the AS3000 (number 1) is not used and can be disabled. To disable it, select the corresponding Local Area Connection entry and select File > Disable. 3. Determine which numbered connection (physical port) refers to which device name. You can determine this by connecting one interface at a time.
Preparing the Server for the Cluster Service Naming Network Connections Network Interface Label New Names New Names on (Redundant-switch (Dual-connected AS3000 configuration) configuration) Device Name Top left network 1 connector Not used Not used Intel(R) 82567LM-4 Gigabit Network Connection Top right network connector Not used Right Intel(R) PRO/1000 PT Dual Port Server Adapter 2 This is a public network connected to network switch. You can include the subnet number of the interface.
Preparing the Server for the Cluster Service 5. Depending on your Avid network and the device you selected, type a new name for the network connection and press Enter. 6. Repeat steps 4 and 5 for each network connection. The following Network Connections window shows the new names used in a dual-connected Avid ISIS environment. 7. Close the Network Connections window. 8. Repeat this procedure on node 2, using the same names that you used for node 1.
Preparing the Server for the Cluster Service 4. On the Networking tab, click the following check box: - Internet Protocol Version 4 (TCP/IPv4) Uncheck all other components. Select this check box. All others are unchecked.
Preparing the Server for the Cluster Service 5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box opens. Type the private IP address for the node you are configuring. 6. On the General tab of the Internet Protocol (TCP/IP) Properties dialog box: n a. Select “Use the following IP address.” b. IP address: type the IP address for the Private network connection for the node you are configuring.
Preparing the Server for the Cluster Service d. Make sure the “Default gateway” and “Use the Following DNS server addresses” text boxes are empty. 7. Click Advanced. The Advanced TCP/IP Settings dialog box opens. 8. On the DNS tab, make sure no values are defined and that the “Register this connection’s addresses in DNS” and “Use this connection’s DNS suffix in DNS registration” are not selected. 9. On the WINS tab, do the following: t Make sure no values are defined in the WINS addresses area.
Preparing the Server for the Cluster Service Configuring the Binding Order Networks on Each Node Repeat this procedure on each node and make sure the configuration matches on both nodes. To configure the binding order networks: 1. On node 1, click Start > Control Panel > Network and Sharing Center. The Network and Sharing Center window opens. 2. Click “Change adapter settings” on the left side of the window. The Network Connections window opens. 3. From the Advanced menu, select Advanced Settings.
Preparing the Server for the Cluster Service 4. In the Connections area, use the arrow controls to position the network connections in the following order: - - For a redundant-switch configuration in an Avid ISIS environment, use the following order: - Public - Private For a dual-connected configuration in an Avid ISIS environment, use the following order, as shown in the illustration: - Left - Right - Private 5. Click OK. 6.
Preparing the Server for the Cluster Service Avid recommends that you disable IPv6 for the public network adapters, as shown in the following illustration: “Configuring the Public Network Adapter on Each Node” on page 47 Configuring the Cluster Shared-Storage RAID Disks on Each Node Both nodes must have the same configuration for the cluster shared-storage RAID disk. When you configure the disks on the second node, make sure the disks match the disk configuration you set up on the first node.
Preparing the Server for the Cluster Service The Disk Management window opens. The following illustration shows the shared storage drives labeled Disk 1, Disk 2, and Disk 3. In this example they are offline, not initialized, and unformatted. 3. If the disks are offline, right-click Disk 1 (in the left column) and select Online. Repeat this action for Disk 3. Do not bring Disk 2 online. 4. If the disks are not already initialized, right-click Disk 1 (in the left column) and select Initialize Disk.
Preparing the Server for the Cluster Service Select Disk 1 and Disk 3 and make sure that MBR is selected. Click OK. 5. Use the New Simple Volume wizard to configure the disks as partitions. Right-click each disk, select New Simple Volume, and follow the instructions in the wizard. Use the following names and drive letters: n Disk Name and Drive Letter Infortrend S12F-R1440 Disk 1 Quorum (Q:) 10 GB Disk 3 Databases (S:) 814 GB or larger Do not assign a name or drive letter to Disk 2.
Preparing the Server for the Cluster Service n Disk Name and Drive Letter HP MSA 2400 Disk 1 Quorum (Q:) 10 GB Disk 2 Databases (S:) 870 GB or larger If you need to change the drive letter after running the wizard, right-click the drive letter in the right column and select Change Drive Letter or Path. If you receive a warning tells you that some programs that rely on drive letters might not run correctly and asks if you want to continue. Click Yes.
Configuring the Cluster Service 8. On the second node, bring the disks online and assign drive letters. You do not need to initialize or format the disks. a. Open the Disk Management tool, as described in step 2. b. Bring Disk 1 and Disk 3 online, as described in step 3. c. Right-click a partition, select Change Drive Letter, and enter the appropriate letter. d. Repeat these actions for the other partitions. 9. Boot the first node. 10.
Configuring the Cluster Service Installing the Failover Clustering Feature The Failover Clustering feature is a Windows Server 2008 feature that contains the complete Failover functionality. The Failover Cluster Manager, which is a snap-in to the Server Manager, is installed as part of the Failover Clustering installation. To install the Failover Clustering featurer: 1. On the first node, right-click My Computer and select Manage. The Server Manager window opens. 2.
Configuring the Cluster Service 4. Select Failover Clustering from the list of features and click Next. 5. On the next screen, click Install. The Failover Cluster Manager installation program starts. At the end of the installation, a message states that the installation was successful. 6. Click Close. To check if the feature was installed, open the Server Manager and open Features. The Failover Cluster Manager should be displayed. 7. Repeat this procedure on the second node.
Configuring the Cluster Service 5. Click OK. Creating the Cluster Service To create the cluster service: 1. Make sure all storage devices are turned on. 2. Log in to the operating system using the cluster installation account (see “Requirements for Domain User Accounts” on page 29). 3. On the first node, right-click My Computer and select Manage. The Server Manager window opens. 4. In the Server Manager list, open Features and click Failover Cluster Manager.
Configuring the Cluster Service 5. Click Create a Cluster. The Create Cluster Wizard opens with the Before You Begin window. 6. Review the information and click Next (you will validate the cluster in a later step).
Configuring the Cluster Service 7. In the Select Servers window, type the simple computer name of node 1 and click Add. Then type the computer name of node 2 and click Add.
Configuring the Cluster Service 10. In the Access Point for Administering the Cluster window, type a name for the cluster, then click in the Address text box and enter an IP address. If you are configuring a dual-connected cluster, you need to add a second IP address after renaming and deleting cluster disks. This procedure is described in “Adding a Second IP Address to the Cluster” on page 66. 11. Click Next. A message informs you that the system is validating settings.
Configuring the Cluster Service 12. Review the information and if it is correct, click Next. The Create Cluster Wizard creates the cluster. At the end of the process, a Summary window opens and displays information about the cluster. You can click View Report to see a log of the entire cluster creation. 13. Click Finish.
Configuring the Cluster Service Now when you open the Failover Cluster Manager in the Server Manager, the cluster you created and information about its components are displayed, including the networks available to the cluster (cluster networks). The following illustration shows components of a dual-connected cluster. Cluster Network 1 and Cluster Network 2 are external networks connected to VLAN 10 and VLAN 20 on Avid ISIS, and Cluster Network 3 is a private, internal network for the heartbeat.
Configuring the Cluster Service The following illustration shows components of a cluster in a redundant-switch ISIS environment. Cluster Network 1 is an external network connecting to one of the redundant switches, and Cluster Network 2 is a private, internal network for the heartbeat. Renaming the Cluster Networks in the Failover Cluster Manager You can more easily manage the cluster by renaming the networks that are listed under the Failover Cluster Manager. To rename the networks: 1.
Configuring the Cluster Service 5. Click in the Name text box, and type a meaningful name, for example, a name that matches the name you used in the TCP/IP properties. For a redundant-switch configuration, use Public. For a dual-connected configuration, use Left, as shown in the following example. For this network, keep the option “Allow clients to connect through this network.” 6. Click OK. 7. If you are configuring a dual-connected cluster configuration, rename Cluster Network 2, using Right.
Configuring the Cluster Service 8. Rename the other network Private. This network is used for the heartbeat. For this private network, leave the option “Allow clients to connect through this network” unchecked. Renaming Cluster Disk 1 and Deleting the Remaining Cluster Disks You can more easily manage the cluster by renaming Cluster Disk 1, which is listed under the Failover Cluster Manager. You must delete any disks other than Cluster Disk 1 that are listed.
Configuring the Cluster Service To rename Cluster Disk 1: 1. Right-click My Computer and select Manage. The Server Manager window opens. 2. In the Server Manager list, open Features > Failover Cluster Manager > cluster_name. 3. Click Storage. 4. In the Storage window, right-click Cluster Disk 1 and select Properties.
Configuring the Cluster Service The Properties dialog box opens. 5. In the Resource Name dialog box, type a name for the cluster disk. In this case, Cluster Disk 1 is the Quorum disk, so type Quorum as the name. To remove all disks other than Cluster Disk 1 (Quorum) 1. In the Storage window, right-click Cluster Disk 2 and select Delete. 2. In the Storage window, right-click Cluster Disk 3 if available (or Databases, if you renamed it) and select Delete.
Configuring the Cluster Service Adding a Second IP Address to the Cluster If you are configuring a dual-connected cluster, you need to add a second IP address for the cluster application (virtual server). To add a second IP address to the cluster: 1. Right-click My Computer and select Manage. The Server Manager window opens. 2. In the Server Manager list, open Features > Failover Cluster Manager > cluster_name.
Configuring the Cluster Service 3. Click Networks. Make sure that Cluster Use is enabled for both ISIS networks, as shown in the following illustration. If a network is not enabled, right-click the network, select Properties, and select “Allow clients to connect through this network.
Configuring the Cluster Service 4. In the Failover Cluster Manager, select the cluster application by clicking on the Cluster name in the left column of the Failover Cluster Manager. 5. In the Actions panel (right column), select Properties in the Name section.
Configuring the Cluster Service The Properties dialog box opens. In the network column, if or is displayed instead of the network identifier, close the Server Manager window, and after waiting a few seconds open it again.
Configuring the Cluster Service 6. In the General tab, do the following: a. Click Add. b. Type the IP address for the other ISIS network. c. Click OK. The General tab shows the IP addresses for both ISIS networks. 7. Click Apply. A confirmation box asks you to confirm that all cluster nodes need to be restarted. You will restart the nodes later in this procedure, so select Yes.
Configuring the Cluster Service 8. Click the Dependencies tab and check if the new IP address was added with an OR conjunction. If the second IP address is not there, click “Click here to add a dependency.” Select “OR” from the list in the AND/OR column and select the new IP address from the list in the Resource column. 9. Click OK and restart both nodes. Start with node one and after it is back online, restart the other node.
Configuring the Cluster Service 3. Open a Command Prompt and enter the following command: cluster group “Cluster Group” /move:node_hostname This command moves the cluster group, including the Quorum disk, to the node you specify. To test the failover, use the hostname of the non-active node. The following illustration shows the command and result if the non-active node (node 2) is named warrm-ipe4. The status “Partially Online” is normal.
Configuring the Cluster Service 4. Open the Server Manager and select Features > Failover Cluster Manager > cluster_name > Storage. Make sure that the Quorum disk is online and that current owner is node 2, as shown in the following illustration. 5. In the Server Manager, select Features > Failover Cluster Manager > cluster_name > Networks. The status of all networks should be “Up.” The following illustration shows networks for a dual-connected configuration. 6.
3 Installing the Interplay | Engine for a Failover Cluster After you set up and configure the cluster, you need to install the Interplay Engine software on both nodes.
Installing the Interplay | Engine on the First Node Installing the Interplay | Engine on the First Node The following sections provide procedures for installing the Interplay Engine on the first node. For a list of example entries, see “List of IP Addresses and Network Names” on page 31.
Installing the Interplay | Engine on the First Node c n Shut down the second node when installing Interplay Engine for the first time. When installing the Interplay Engine for the first time on a machine with cluster services, you are asked to choose between clustered and regular installation. The installation on the second node (or later updates) reuses the configuration from the first installation without allowing you to change the cluster-specific settings.
Installing the Interplay | Engine on the First Node If Disk 3 is online, you can skip the following steps. 3. Right-click Disk 3 (in the left column) and select Online. 4. Make sure the drive letter is correct (S:) and the drive is named Databases. If not, you can change it here. Right-click the disk name and letter (right-column) and select Change Drive Letter or Path.
Installing the Interplay | Engine on the First Node If you attempt to change the drive letter, you receive a warning tells you that some programs that rely on drive letters might not run correctly and asks if you want to continue. Click Yes. Starting the Installation and Accepting the License Agreement To start the installation: 1. Make sure the second node is shut down. 2. Insert the Avid Interplay Servers installation flash drive. A start screen opens. 3.
Installing the Interplay | Engine on the First Node • “Specifying the Share Name” on page 85 • “Specifying the Configuration Server” on page 86 • “Specifying the Server User” on page 87 • “Specifying the Server Cache” on page 88 • “Enabling Email Notifications” on page 89 • “Installing the Interplay Engine for a Custom Installation on the First Node” on page 91 For information about updating the installation, see “Updating a Clustered Installation (Rolling Upgrade)” on page 110.
Installing the Interplay | Engine on the First Node 3. Select Cluster and click Next to continue the installation in cluster mode. The Specify Interplay Engine Details dialog box opens. Specifying the Interplay Engine Details In this dialog box, provide details about the Interplay Engine.
Installing the Interplay | Engine on the First Node To specify the Interplay Engine details: 1. Type the following values: - Virtual IP address: This is the Interplay Engine service IP Address, not the Cluster service IP address. For a list of examples, see “List of IP Addresses and Network Names” on page 31. For a dual-connected configuration, you set the other public network connection after the installation. See “Adding a Second IP Address (Dual-Connected Configuration)” on page 96.
Installing the Interplay | Engine on the First Node Specifying the Interplay Engine Service Name In this dialog box, type the name of the Interplay Engine service. To specify the Interplay Engine name: 1. Specify the public names for the Avid Interplay Engine service by typing the following values: - The Network Name will be associated with the virtual IP Address that you entered in the previous Interplay Engine Details dialog box.
Installing the Interplay | Engine on the First Node Specifying the Destination Location In this dialog box specify the folder in which you want to install the Interplay Engine program files. To specify the destination location: 1. Avid recommends that you keep the default path C:\Program Files\Avid\Avid Interplay Engine. c Under no circumstances attempt to install to a shared disk; independent installations are required on both nodes. This is because local changes are also necessary on both machines.
Installing the Interplay | Engine on the First Node Specifying the Default Database Folder In this dialog box specify the folder where the database data is stored. To specify the default database folder: 1. Type S:\Workgroup_Databases. Make sure the path specifies the shared drive (S:). This folder must reside on the shared drive that is owned by the resource group of the server. You must use this shared drive resource so that it can be monitored and managed by the cluster service.
Installing the Interplay | Engine on the First Node Specifying the Share Name In this dialog box specify a share name to be used for the database folder. To specify the share name: 1. Accept the default share name. Avid recommends you use the default share name WG_Database$. This name is visible on all client platforms, such as Windows NT Windows 2000 and Windows XP.The “$” at the end makes the share invisible if you browse through the network with the Windows Explorer.
Installing the Interplay | Engine on the First Node Specifying the Configuration Server In this dialog box, indicate whether this server is to act as a Central Configuration Server. Set for both nodes. Use this option for Interplay Archive Engine A Central Configuration Server (CCS) is an Avid Interplay Engine with a special module that is used to store server and database-spanning information. For more information, see the Interplay | Engine and Interplay | Archive Engine Administration Guide.
Installing the Interplay | Engine on the First Node 2. Click Next. The Specify Server User dialog box opens. Specifying the Server User In this dialog box, define the Cluster Service account (Server Execution User) used to run the Avid Interplay Engine. The Server Execution User is the Windows domain user that runs the Interplay Engine and the cluster service. This account is automatically added to the Local Administrators group on the server.
Installing the Interplay | Engine on the First Node 2. Click Next. The Specify Preview Server Cache dialog box opens. If necessary, you can change the name of the Server Execution User after the installation. For more information, see “Troubleshooting the Server Execution User Account” and “Re-creating the Server Execution User” in the Interplay | Engine and Interplay | Archive Engine Administration Guide and the Interplay ReadMe.
Installing the Interplay | Engine on the First Node Enabling Email Notifications The first time you install the Avid Interplay Engine, the Enable Email Notification dialog box opens. The email notification feature sends emails to your administrator when special events, such as “Cluster Failure,” “Disk Full,” and “Out Of Memory” occur. Activate email notification if you want to receive emails on special events, server or cluster failures. To enable email notification: 1.
Installing the Interplay | Engine on the First Node 2. Type the administrator's email address and the email address of the server, which is the sender. If an event, such as “Resource Failure” or “Disk Full” occurs on the server machine, the administrator receives an email from the sender's email account explaining the problem, so that the administrator can react to the problem. You also need to type the static IP address of your SMTP server.
Installing the Interplay | Engine on the First Node Installing the Interplay Engine for a Custom Installation on the First Node In this dialog box, begin the installation of the engine software. To install the Interplay Engine software: 1. Click Next. Use the Back button to review or change the data you have entered. You can also terminate the installer using the Cancel button, because no changes have been done to the system yet.
Installing the Interplay | Engine on the First Node The Windows Firewall is turned off by the server image (see “Windows Server Settings Included in Revision 4 and Later Images” on page 116). If the Firewall is turned on, you get messages that the Windows Firewall has blocked nxnserver.exe (the Interplay Engine) and the Apache server from public networks.
Installing the Interplay | Engine on the First Node 3. Do one of the following: t Click Finish. t Analyze and resolve any issues or failures reported. 4. Click OK if prompted for a restart the system. The installation procedure requires the machine to restart (up to twice). For this reason it is very important that the other node is shut down, otherwise the current node loses ownership of the Avid Workgroup resource group. This applies to the installation on the first node only.
Installing the Interplay | Engine on the First Node The Server Name and IP Address, File Server, and Avid Workgroup Disk resources should be online and all other resources offline. S$ and WG_Database$ should be listed in the Shared Folders section. Take one of the following steps: - If the File Server resource or the shared folder WG_Database$ is missing, you must create it manually, as described in “Creating the Database Share Manually” on page 95.
Installing the Interplay | Engine on the First Node - n If you are setting up an Avid ISIS dual-connected configuration, proceed to “Adding a Second IP Address (Dual-Connected Configuration)” on page 96. Avid does not recommend starting the server at this stage, because it is not installed on the other node and a failover would be impossible.
Installing the Interplay | Engine on the First Node Adding a Second IP Address (Dual-Connected Configuration) If you are setting up an Avid ISIS dual-connected configuration, you need use the Failover Cluster Manager to add a second IP address. To add a second IP address: 1. In the Failover Cluster Manager, select Avid Workgroup Server. 2. Bring the Name, IP Address, and File Server resources offline by doing one of the following: - Right-click the resource and select “Take this resource offline.
Installing the Interplay | Engine on the First Node c Note that the Resource Name is listed as “Avid Workgroup Name.” Make sure to check the Resource Name after adding the second IP address and bringing the resources on line in step 9. If the Kerberos Status is offline, you can continue with the procedure. After bringing the server online, the Kerberos Status should be OK. 4. Click the Add button below the IP Addresses list. The IP Address dialog box opens.
Installing the Interplay | Engine on the First Node The second ISIS sub-network and a static IP Address are already displayed. 5. Type the second Interplay Engine service Avid ISIS IP address. See “List of IP Addresses and Network Names” on page 31. Click OK. The Properties dialog box is displayed with two networks and two IP addresses.
Installing the Interplay | Engine on the First Node 6. Check that you entered the IP address correctly, then click Apply. 7. Click the Dependencies tab and check that the second IP address was added, with an OR in the AND/OR column.
Installing the Interplay | Engine on the First Node 8. Click OK. The resources screen should look similar to the following illustration. 9. Bring the Name, both IP addresses, and the File Server resource online by doing one of the following: - Right-click the resource and select “Bring this resource online.” - Select the resources and select “Bring this resource online” in the Actions panel.
Installing the Interplay | Engine on the First Node The following illustration shows the resources online. 10. Right-click the Name resource and select Properties.
Installing the Interplay | Engine on the First Node The Resource Name must be listed as “Avid Workgroup Name.” If it is not, see “Changing the Resource Name of the Avid Workgroup Server” on page 102. 11. Leave this node running so that it maintains ownership of the resource group and proceed to “Installing the Interplay | Engine on the Second Node” on page 104.
Installing the Interplay | Engine on the First Node 2. Browse through the GUID named subkeys looking for the one subkey where the value “Type” is set to “Network Name” and the value “Name” is set to . 3. Change the value “Name” to “Avid Workgroup Name.” 4. Do the following to shut down the cluster: c Make sure you have edited the registry entry before you shut down the cluster. a. In the Server Manager tree (left panel) select the cluster.
Installing the Interplay | Engine on the Second Node 5. Do the following to bring the cluster on line: a. In the Server Manager tree (left panel) select the cluster. b. In the context menu or the Actions panel on the right side, select “Start Cluster Service.” Installing the Interplay | Engine on the Second Node To install the Interplay Engine on the second node: 1. Leave the first machine running so that it maintains ownership of the resource group and start the second node.
Bringing the Interplay | Engine Online c Make sure you use the installation mode that you used for the first node and enter the same information throughout the installer. Using different values results in a corrupted installation. 5. The installation procedure requires the machine to restart (up to twice). Allow the restart as requested. c If you receive a message that the Avid Workgroup Name resource was not found, you need to check the registry.
After Installing the Interplay | Engine All resources are now online, as shown in the following illustration. After Installing the Interplay | Engine After you install the Interplay Engine, install the following applications on both nodes: n • Interplay Access: From the Interplay Server Installer Main Menu, select Servers > Avid Interplay Engine > Avid Interplay Access. • Avid ISIS client: See the Avid ISIS System Setup Guide.
Creating an Interplay | Production Database Then create an Interplay database, as described in “Creating an Interplay | Production Database” on page 107. Creating an Interplay | Production Database Before testing the failover cluster, you need to create a database. The following procedure describes basic information about creating a database. For complete information, see the Interplay | Engine and Interplay | Archive Engine Administration Guide. To create an Interplay database: 1.
Testing the Complete Installation Testing the Complete Installation After you complete all the previously described steps, you are now ready to test the installation. Make yourself familiar with the Failover Cluster Manager and review the different failover-related settings. n If you want to test the Microsoft cluster failover process again, see “Testing the Cluster Installation” on page 71. To test the complete installation: 1.
Installing a Permanent License Installing a Permanent License During Interplay Engine installation a temporary license for one user is activated automatically so that you can administer and install the system. There is no time limit for this license. A permanent license is provided by Avid in the form of a file (*.nxn), usually on a USB flash drive. A license for an Interplay Engine failover cluster includes two hardware IDs. You install this license through the Interplay Administrator.
Updating a Clustered Installation (Rolling Upgrade) Updating a Clustered Installation (Rolling Upgrade) A major benefit of a clustered installation is that you can perform “rolling upgrades.” You can keep a node in production while updating the installation on the other, then move the resource over and update the second node as well. n For information about updating specific versions of the Interplay Engine and a cluster, see the Avid Interplay ReadMe.
Updating a Clustered Installation (Rolling Upgrade) 3. If the current host of the cluster is not the active node, you need to stop the cluster service of the non-active node, which moves it to the active node. a. In the Server Manager tree, right-click the node that you want to go offline and select More Actions > Stop Cluster Service. b. After the Cluster Service has stopped, right-click the node for which you just stopped the cluster service and select More Actions > Start Cluster Service. 4.
Uninstalling the Interplay | Engine on a Clustered System Uninstalling the Interplay | Engine on a Clustered System To uninstall the Avid Interplay Engine, use the Avid Interplay Engine uninstaller, first on the inactive node, then on the active node. c The uninstall mechanism of the cluster resources only functions properly if the names of the resources or the resource groups are not changed. Never change these names. To uninstall the Interplay Engine: 1.
Uninstalling the Interplay | Engine on a Clustered System 8. After the uninstallation on the inactive node is complete, wait until the last restart is done. Then open the Failover Cluster Manager on the active node and make sure the inactive node is shown as online. 9. Start the uninstallation on the active node (the node that owns the Avid Workgroup Resource Group). 10. When you are asked if you want to delete the cluster resources, click Yes. A confirmation dialog box opens. 11. Click Yes. 12.
4 Automatic Server Failover Tips and Rules This chapter provides some important tips and rules to use when configuring the automatic server failover. Don't Access the Interplay Engine Through Individual Nodes Don't access the Interplay Engine directly through the individual machines (nodes) of the cluster. Use the virtual network name or IP address that has been assigned to the Interplay Engine resource group (see “List of IP Addresses and Network Names” on page 31).
Interplay Engine execution user has to stay fixed as well. For more information, see “Troubleshooting the Server Execution User Account” in the Interplay | Engine and Interplay | Archive Engine Administration Guide. Do Not Edit the Registry While the Server is Offline If you edit the registry while the server is offline, you will lose your changes. This is something that most likely will happen to you since it is very easy to forget the implications of the registry replication.
A Windows Server Settings Included in Revision 4 and Later Images The latest images for the AS3000 Windows Server 2008 R2 Standard (starting with Rev. 4, October 17, 2012) include system settings that required manual changes in previous versions of the image. This appendix lists those settings for reference.
Creating New GUIDs for the AS3000 Network Adapters To create a new GUIDs: 1. Disconnect the ISIS client from the System Director and disconnect the network cables from all network ports at the back of the AS3000. 2. Use the registry editor to delete registry keys, as follows: a. Click Start, type regedit.exe, and press Enter. b. Navigate to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network c. Select the REG_BINARY value “config” and press Delete. d.
Creating New GUIDs for the AS3000 Network Adapters 6. In the pop-up dialog box, make sure that “Delete the driver software for this device” is not selected, then click OK. After the last adapter is removed, the Network Adapters category disappears. 7. Select Action > Scan for hardware changes Wait until all four network adapters are repopulated. 8. Reconnect the network cables and reboot the host.
Removing the Web Server IIS Role Removing the Web Server IIS Role c This procedure is not needed with Rev. 4 and later server images. To remove the Web Server IIS role: 1. Click Start > All Programs> Administrative Tools > Server Manager. 2. Click Roles on the left side of the window. 3. Click Remove Roles and click Server Roles. The Remove Server Roles dialog box opens. 4. Uncheck Web Server (IIS). A dialog box opens and asks if you want to remove the dependent features. 5.
Removing the Failover Clustering Feature 4. Clear the check box for Failover Clustering. A message asks if you have removed this server from a cluster. Select “Yes.” 5. In the Select Features screen, click Next. The Confirm Removal Selections screen opens.
Removing the Failover Clustering Feature 6. Click Remove. 7. Follow the system prompts to restart the server.
Disabling IPv6 The following illustration shows the Removal Results screen that is displayed after you restart. Disabling IPv6 Disabling IPv6 completely is no longer recommended. IPv6 is enabled in Rev. 4 and later server images. Binding network interface cards (NICs) to IPv6 is not recommended. See “Configuring the Public Network Adapter on Each Node” on page 47.
Switching the Server Role to Application Server Switching the Server Role to Application Server c This procedure is not needed with Rev. 4 and later server images. To switch the Server Role to Application Server: 1. Click Control Panel > System and Security > System. The System control panel opens.
Switching the Server Role to Application Server 2. Click “Advanced system settings” on the left of the window. The System Properties dialog box opens. 3. Click the Advanced tab and click Settings in the Performance area. The Performance Options dialog box opens. 4. Click the Advanced tab.
Disabling the Windows Firewall 5. In the Processor scheduling area, under “Adjust for best performance of,” select Programs, as shown in the following illustration. 6. Click Apply, then click OK to close the window. 7. Click OK to close the System properties window, then close the System window. Disabling the Windows Firewall c This procedure is not needed with Rev. 4 and later server images. Disabling the Windows Firewall is not required for a cluster configuration.
Disabling the Windows Firewall To disable the Windows Firewall: 1. Open All Programs > Administrative Tools > Windows Firewall with Advanced Security. 2. In the Actions section on the right, select Properties, as shown in the following illustration. 3. Set the Firewall state to Off in at least the Domain and the Private Profile tabs. n If your site allows it, also set the state to Off in the Public Profile tab.
Disabling the Windows Firewall The following illustration shows the Firewall state tuned off for the Domain Profile. 4. Click OK. The Overview section in the center column shows that the firewall is off, as shown in the following illustration.
B Enabling TCP/IPv6 in the Registry Disabling the TCP/IPv6 protocol completely on Interplay Engine servers is no longer recommended. IPv6 is enabled in Rev. 4 and later server images. However, binding network interface cards (NICs) to IPv6 is not recommended. See “Configuring the Public Network Adapter on Each Node” on page 47. Some installations might have IPv6 disabled through the DisabledComponents registry key. The following illustration shows the registry key set to disabled.
To enable IPv6: 1. Use a text editor to create a file named SetDisabledComponentsToZero.reg. 2. Enter the following text: REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters ] "DisabledComponents"=dword:0 3. Save the file. 4. Right-click the file name and select Merge. The key is set to zero.
Index A Active Directory domain adding cluster servers 52 Antivirus software running on a failover cluster 18 Apache web server on failover cluster 74 AS3000 server slot locations (failover cluster) 20 ATTO card setting link speed 36 Avid online support 10 training services 11 Avid ISIS failover cluster configurations 15 failover cluster connections for dual-connected configuration 24 failover cluster connections for redundant-switch configuration 21 Avid Unity MediaNetwork failover cluster configuration 1
Index F Interplay Engine Central Configuration Server, specifying for failover cluster 86 cluster information for installation 80 default database location for failover cluster 84 enabling email notifications 89 installing on first node 75 preparation for installing on first node 75 Server Execution User, specifying for failover cluster 87 share name for failover cluster 85 specify engine name 82 specifying server cache 88 uninstalling 112 Interplay Portal viewing 10 IP addresses (failover cluster) privat
Index O described 29 specifying for failover cluster 87 Server Failover overview 12 See also Failover cluster Server Role switching to Application Server 123 Service name examples for failover cluster 31 Services dependencies 114, 116 Shared drive bringing online 76 configuring for failover cluster 48 specifying for Interplay Engine 80 Slot locations AS3000 server (failover cluster) 20 Software requirements for failover cluster system 18 Subnet Mask 80 Online resource defined 27 Online support 10 P Perm
Index W Web Server IIS role removing 119 Web servers disabling 74 Windows Firewall disabling 125 Windows server settings changing before installation 38, 116 133
Avid Technical Support (USA) Product Information 75 Network Drive Burlington, MA 01803-2756 USA Visit the Online Support Center at www.avid.com/support For company and product information, visit us on the web at www.avid.
