PolyServe® Matrix Server Installation Guide PolyServe® Matrix Server 3.6.0 for Windows MxDB for SQL Server 3.6.0 MxFS for CIFS 3.6.
Copyright © 2004-2008 PolyServe, Inc. Use, reproduction and distribution of this document and the software it describes are subject to the terms of the software license agreement distributed with the product (“License Agreement”). Any use, reproduction, or distribution of this document or the described software not explicitly permitted pursuant to the License Agreement is strictly prohibited unless prior written permission from PolyServe has been received.
Contents 1 HP Technical Support HP Storage Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HP NAS Services Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 Configuration Information Supported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported HBA Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Requirements . . . . . . . . . . . . . . . . . . . . .
Contents iv 13. Run the mxcheck Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14. Install PolyServe Matrix Server . . . . . . . . . . . . . . . . . . . . . . . . 15. Install Hardware Snapshot Software (Optional) . . . . . . . . . . 16. Configure the Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test the Fencing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Stand-Alone Management Console . . . . . . . . . . . . . . . .
1 HP Technical Support Telephone numbers for worldwide technical support are listed on the following HP website: http://www.hp.com/support. From this website, select the country of origin. For example, the North American technical support number is 800-633-3600. NOTE: For continuous quality improvement, calls may be recorded or monitored.
HP Technical Support 2 HP NAS Services Website The HP NAS Services site allows you to choose from convenient HP Care Pack Services packages or implement a custom support solution delivered by HP ProLiant Storage Server specialists and/or our certified service partners. For more information, see us at http://www.hp.com/hps/storage/ns_nas.html.
2 Configuration Information PolyServe is continually expanding its supported hardware and operating system configurations. For the latest information, check the PolyServe Web site: http://www.polyserve.com On the Web page, click on Support and then click on Compatibility. Supported Hardware The following hardware can be used in a Matrix Server matrix. Hardware Configuration Limit Servers Two to 16 servers.
Chapter 2: Configuration Information 4 Supported HBA Drivers Before you install Matrix Server, we recommend that you install a supported HBA driver on the servers that will be in the matrix. See the PolyServe Hardware and Software Compatibility Guide for the supported drivers. If you do not install one of these drivers, the operating system will select the default driver, which has not been validated with Matrix Server.
Chapter 2: Configuration Information 5 • Matrix Server has been verified with the English locale. NOTE: To ensure that file times are consistent across the matrix, it is recommended that all matrix servers operate with synchronized time-of-day clocks. An NTP server is one commonly used mechanism for synchronizing system clocks.
Chapter 2: Configuration Information 6 Matrix SAN Configuration Guidelines Following are guidelines for configuring the matrix SAN to be used with Matrix Server: • For all FC switches, it is best practice to place each HBA port and its storage ports in a separate zone. No other initiator HBA port should be present in this zone. • When the matrix is configured for fabric fencing, arrays must operate in fabric or switch-attached mode (not arbitrated-loop-only devices).
Chapter 2: Configuration Information 7 “Administrative Considerations” in Chapter 3 for information about SAN restrictions. NOTE: You can attach a matrix server to other SANs that are not under Matrix Server control. These SANs can include tape drives and non-PSFS filesystems. You can use Windows utilities or other applications to access these devices and filesystems. Requirements for Active Directory Matrix Server requires that Active Directory be configured.
3 Install PolyServe Matrix Server This chapter describes how to perform a new installation of PolyServe Matrix Server on servers running Microsoft Windows. Contents of the Matrix Server Distribution The Matrix Server distribution contains the following files: • MxS_3.6.0...msi. The Matrix Server software package. The software is available in 32-bit and 64-bit versions. Be sure to install the version that corresponds to your operating system. • MxConsole_3.6.0..msi.
Chapter 3: Install PolyServe Matrix Server 9 • Windows Server 2003 SP2 Standard or Enterprise Edition (32-bit and 64-bit) • Windows Server 2003 R2 Standard or Enterprise Edition (32-bit and 64-bit) • Windows Server 2003 R2 SP2 Standard or Enterprise Edition (32-bit and 64-bit) User Authentication Matrix Server uses Windows credentials to authorize access to the matrix. By default, members of the machine local Administrators group have access to the matrix and can perform all matrix operations.
Chapter 3: Install PolyServe Matrix Server Action Description Review configuration requirements. See Chapter 2 for configuration requirements, including disabling 802.3x Ethernet flow control on all NICs. Set up the DNS hostname. Matrix Server requirements for DNS are located in section “1. Set Up the DNS Hostname” on page 11. Configure the server for WINS clients. This step is needed only if the server will be accessed by WINS clients. Install a firewall (optional).
Chapter 3: Install PolyServe Matrix Server 11 If you will be using a client PC outside the matrix to administer your matrix, you will also need to install the stand-alone Management Console package on that PC. 1. Set Up the DNS Hostname Each server running Matrix Server must be able to resolve its hostname in DNS. Matrix Server uses the first address returned by DNS as the server’s name in the matrix.
Chapter 3: Install PolyServe Matrix Server 12 • Add the server to the suffix search list. Select Settings > Control Panel > Network and Dial-Up Connections. Then select any network connection. On the Local Area Connection Properties window, select Internet Protocol (TCP/IP) and click Properties. On the Internet Properties window, click Advanced. Then, on the Advanced TCP/IP Settings window, select the DNS tab. Choose “Append these DNS suffixes (in order)”, and select Add to add your suffixes.
Chapter 3: Install PolyServe Matrix Server 13 5. Reboot the Server Reboot the server. This step ensures that the registry is in a known good most-recent state. You may also want to back up the current state of the server (such as files, registry, and so on). Repeat steps 1–5 on each server that will be in the matrix. 6. Install Emulex HBA API Libraries This step is needed only if your servers use Emulex HBAs.
Chapter 3: Install PolyServe Matrix Server 14 10. Configure FC Switches NOTE: For all FC switches, it is best practice to place each HBA port and its storage ports in a separate zone. No other initiator HBA port should be present in this zone.
Chapter 3: Install PolyServe Matrix Server 15 described here, certain Matrix Server commands can return more information. To configure FibreChannel switches, complete the following tasks: • Enable server access to the SAN. Each server that will be in the matrix must be able to access the disks in the SAN. You may need to enable server ports on the FC switches or to change the zoning configuration to give servers the necessary access to the SAN. • Modify the SNMP setup.
Chapter 3: Install PolyServe Matrix Server 16 11. Create LUNs for the Membership Partitions and Modify Partition Tables Matrix Server uses a set of membership partitions to control access to the SAN. The membership partitions are also used to store the device naming database, which includes the global device names that Matrix Server assigns to the SAN disks placed under its control. Matrix Server can use either one or three membership partitions.
Chapter 3: Install PolyServe Matrix Server 17 Disk Partition Alignment Many disk arrays are sensitive to misaligned I/O operations and require I/O to be aligned on block boundaries for performance reasons. For example, an array may “prefer” to have I/O operations occur on natural block boundaries, such as 4-KB blocks.
Chapter 3: Install PolyServe Matrix Server 18 This can be done either by rebooting the servers after you make the partition table changes, or by manually disabling the ports on the FibreChannel switch that connect the servers to the SAN. If using the second method, disable the ports before making the partition table changes, and then reenable the ports afterwards.
Chapter 3: Install PolyServe Matrix Server 19 • Miscellaneous check: other checks such as the non-paged pool setting. To run mxcheck, insert the Matrix Server CD into the CD drive or go to the directory where you downloaded the product and then double-click the file mxcheck.exe. Output from the utility appears on the screen and is also written to the Application Log section of the Event Viewer. We recommend that you fix any problems identified by mxcheck before you install Matrix Server. 14.
Chapter 3: Install PolyServe Matrix Server 20 Engenio Storage Arrays To take hardware snapshots on Engenio storage arrays, the latest version of SANtricity Storage Manager client software must be installed on all servers in the cluster. Also, the latest version of firmware must be installed on your storage array controllers. To obtain this software and firmware, contact your Engenio representative.
Chapter 3: Install PolyServe Matrix Server 21 • The IP address or hostname of each FibreChannel switch that is included in the SAN. (This step is required for FibreChannel switchbased fencing and optional for Web Management-based fencing via server reset/shutdown.) • The partitions or LUNs that you want to use for membership partitions. • If you will be using the snapshot feature, information about the appropriate snapshot method.
Chapter 3: Install PolyServe Matrix Server 22 1. Enter a name or description for this Matrix. The matrix name or description appears on the title bar of the PolyServe Management Console. The name or description can contain up to 80 characters. If you will be using a third-party manager, the name/description will be sent to the manager to help identify the source of SNMP traps or Windows events. 2. License.
Chapter 3: Install PolyServe Matrix Server 23 3. Secret Network Key. This password is required. It provides additional security for network communications among the matrix servers. To set this key, click the Set Secret Network Key button. You can enter anything you want for this password, up to 86 characters in length. NOTE: If more than one Matrix Server matrix is running on the same subnet, be sure that each matrix has a different Secret Network Key.
Chapter 3: Install PolyServe Matrix Server 24 FibreChannel fabric. The server must be rebooted to regain access to the SAN. This method is also called fabric-based fencing. • Web management-based fencing. Matrix Server uses remote management hardware on the server to remove its access to PSFS filesystems. This method is also called server-based fencing. (See the PolyServe Hardware and Software Compatibility Guide on the PolyServe Web site for a list of supported servers and firmware.
Chapter 3: Install PolyServe Matrix Server 25 Select your storage type and, for FibreChannel, specify the fencing method that you want to use. • Fibre-Channel switch-based fencing, below. • Web-based fencing FibreChannel Switch-Based Fencing Complete the following on the SAN & Fencing tab: 1. SAN Switches. Specify the hostnames or IP addresses of the FibreChannel switches that are directly connected to the nodes in the matrix.
Chapter 3: Install PolyServe Matrix Server 26 first FC switch. Repeat this procedure to specify the remaining FC switches, including cascading switches. If you are using an MPIO configuration, be sure to configure all of the switches. 2. SNMP Community String. The default SNMP community string for Matrix Server is private. If you want to use a custom community string, enter the appropriate value here.
Chapter 3: Install PolyServe Matrix Server 27 1. Remote Management Controller Vendor. Select the vendor for your Remote Management Controller. For an IBM Blade Center, also specify the Blade slot. 2. Remote Management Controller ID. Specify how Matrix Server should identify the Remote Management Controller associated with each server. Use one of the following methods. – Enter the hostname or IP address for the Remote Management Controller associated with this server.
Chapter 3: Install PolyServe Matrix Server 28 – Select “Cluster-wide Pattern” and then specify the common naming scheme that you are using for the Remote Management Controllers (either a hostname suffix or an IP address delta, as described below). Hostname Suffix. Specify the common suffix to append to each server name to determine the associated Remote Management Controller name.
Chapter 3: Install PolyServe Matrix Server 29 1. Shared configuration. Select the appropriate options. • Vendor and type selections apply to all servers. This option is enabled by default. Remove the checkmark if your Remote Management Controllers are from different vendors or if, in the case of IBM Remote Management Controllers, some are associated with IBM BladeCenter servers and others are not. • Login shared by all servers.
Chapter 3: Install PolyServe Matrix Server 30 2. Fencing Action. When a server needs to be restricted from the SAN, Matrix Server can either power-cycle the server or shut it down. Select the method that you want to use. If you have FibreChannel-connected storage and want to configure your FibreChannel switches into the matrix, go to the Switch Information tab. (This step is optional; however, if the switches are configured the PolyServe Management Console can display the switch ports used by the SAN.
Chapter 3: Install PolyServe Matrix Server 31 Repeat this procedure to specify the remaining FC switches, including cascading switches. 2. SNMP Community String. The default SNMP community string for Matrix Server is private. If you want to use a custom community string, enter the appropriate value here. The SNMP community string must be set to the same value on Matrix Server and on the SAN switches configured above. When the SAN & Fencing tab is complete, go to the Storage Settings tab.
Chapter 3: Install PolyServe Matrix Server 32 1. Membership Partitions. Matrix Server uses a set of membership partitions to control access to the SAN and to store the device naming database, which includes the global device names that Matrix Server assigns to the SAN disks placed under its control. You will need to select the LUN or disk partitions that should be used as membership partitions. Note the following: – LUNs must already be partitioned as described in step “11.
Chapter 3: Install PolyServe Matrix Server 33 Matrix Server can use either one or three membership partitions. To ensure that a membership partition is always available, we strongly recommend that you select three partitions. To create a membership partition, click Add. The Add Membership Partition window then lists all of the disks or LUNs that it can access. Select a disk or LUN for the first membership partition.
Chapter 3: Install PolyServe Matrix Server 34 NOTE: Array-based hardware snapshots are supported on Engenio storage arrays and Hewlett-Packard StorageWorks Enterprise Virtual Array (EVA) storage arrays. The appropriate Engenio or HP software must be installed as described under step “15. Install Hardware Snapshot Software (Optional)” on page 19. To configure the snapshot method, click Add, select the appropriate method, and then supply any requested configuration information. HP-EVA storage array.
Chapter 3: Install PolyServe Matrix Server 35 Apply the configuration. When you have completed the Storage Settings tab, click Apply (at the bottom of the Matrix Configuration window) to save the configuration that you have created. The configuration is then installed on the server that you are using to connect to the Management Console. You will then be asked whether you want to start the matrix on that server. If you configured Web management-based fencing, answer No. Otherwise, answer Yes.
Chapter 3: Install PolyServe Matrix Server 36 1. Add servers to the matrix. To specify the first server, click Add Server and type the IP address or hostname of the server on the Input form. Then click OK to add the server to the Address column. Repeat this procedure to add the remaining servers to the Address column. Copyright © 1999-2008 PolyServe, Inc. All rights reserved.
Chapter 3: Install PolyServe Matrix Server 37 2. Export the configuration. Click Select All to select all of the servers in the Address column. Then click Export. The Last Operation Progress column will display status messages as the configuration is exported to each server. If you are using Web Management-based fencing, you may be asked for additional information about each server.
Chapter 3: Install PolyServe Matrix Server 38 Matrix Server then fences the servers in accordance with the method you specified on the SAN & Fencing tab. If the correct server is not fenced, you will need to check the configuration. For example, if you specified a pattern for the Remote Management Controller, the server may not be configured to use that pattern.
4 Install MxDB for SQL Server and MxFS for CIFS This chapter describes how to perform new installations of MxDB for SQL Server and MxFS for CIFS. NOTE: Be sure to install a product version that corresponds to your operating system. Install the 32-bit version of the software on the 32-bit operating system, and install the 64-bit version of the software on the 64-bit operating system.
Chapter 4: Install MxDB for SQL Server and MxFS for CIFS software. Then double click the file MxDB_SQL_3.6.0...msi and run the Installation Wizard.
5 Uninstall PolyServe Software Uninstall Matrix Server To uninstall the Matrix Server package, select Start > Programs > PolyServe Matrix Server > Uninstall to start the Uninstall Wizard. When you select Remove, you can choose to retain or delete your existing Matrix Server configuration files. You can also use the Windows Add/Remove Programs feature to remove the PolyServe Matrix Server application; however, this method will remove the Matrix Server configuration files.
A Configure the Matrix from the Command Line Matrix Server provides mx commands that can be used to create the initial matrix configuration. These commands are equivalent to the Configure Matrix graphical user interface described in Chapter 3 and can be used in configuration scripts. We recommend that you review the description of the Configure Matrix window (see section “16. Configure the Matrix” on page 20) to become familiar with the actions performed by the mx commands.
Appendix A: Configure the Matrix from the Command Line 43 The command sequence is: mx --matrix nodeA config license mx --matrix nodeA config secret mx --matrix nodeA config protocol [Multicast|Unicast] mx --matrix nodeA config santype fc mx --matrix nodeA config fcswitch [--community ] ...
Appendix A: Configure the Matrix from the Command Line 44 mx --matrix nodeA config fcswitch [--community ] ... (This command is optional for santype fc and not applicable for santype iSCSI.
Appendix A: Configure the Matrix from the Command Line 45 • The values for the mx commands are specified in a file named cluster.conf. • The matrix specified by this script uses FibreChannel switch-based fencing. • Some commands such as mx config protocol are not included in the script because the default values for those commands will be used. Also note that mx config fcfencing does not need to be specified because that is the default. #!/bin/bash if [ ! -f cluster.conf ]; then echo "you need cluster.
Appendix A: Configure the Matrix from the Command Line 46 MP="6-6005-08B3-0090-A860-22BE-8098-CC0A-0041/1 6-6005-08B3-0090A860-22BE-8098-CC0A-0041/2 6-6005-08B3-0090-A860-22BE-8098-CC0A0041/3" # License File LICENSE="permanent.lic" # Community SNMP String used by Switches COMMUNITY="public" # The Secret Network Key SECRET="secret" # Authentication Information USER="Administrator" PASSWORD="Admin" Command Descriptions The mx commands used in the configuration specify the following information.
Appendix A: Configure the Matrix from the Command Line 47 The default SNMP community string for Matrix Server is private. If you want to use a custom community string, include the --community option. The SNMP community string must be set to the same value on Matrix Server and the SAN switches. mx config fcfencing With FibreChannel switch-based fencing, when a server needs to be fenced, Matrix Server will disable the server’s access in the FibreChannel fabric.
Appendix A: Configure the Matrix from the Command Line 48 mx config webfencing --ruser --vendor --mixedvendor yes|no --hostname |--hostsuffix |--ipdelta [--type reset|shutdown] [--bladeslot ] [--sharedlogin yes|no] [--rpassword ] Configure web management-based fencing, in which Matrix Server uses remote management hardware on the server to remove its access to PSFS filesystems. iSCSI storage must use this fencing method.
Appendix A: Configure the Matrix from the Command Line 49 [--rpassword ] The password for the Remote Management Controller. --ruser The Remote Management Controller user name. [--sharedlogin yes|no] Whether the login account is shared by all servers. --type reset|shutdown When a server needs to be restricted from the SAN, Matrix Server can either power-cycle the server or shut it down. Select the method that you want to use (either reset or shutdown).
