HP StorageWorks HP PolyServe Matrix Server installation guide HP PolyServe Software 4.0.
Legal and notice information © Copyright 2002, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Configuration information ................................................... 5 Supported hardware ............................................................................................ Supported HBA drivers .................................................................................. Server requirements ....................................................................................... Network configuration requirements .............................................................
14. Install HP PolyServe Matrix Server ........................................................... 15. Install hardware snapshot software (optional) ............................................ HP EVA storage arrays .......................................................................... HP MSA2000 storage arrays ................................................................. Engenio storage arrays ......................................................................... 16. Configure the matrix .......
1 Configuration information PolyServe is continually expanding its supported hardware and operating system configurations. Supported hardware The following hardware can be used in a Matrix Server matrix. Hardware Configuration Limit Servers Two to 16 servers. Network Interface Cards (any card supported by Microsoft Windows Server 2008) Up to four network interfaces per server.
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. Server requirements The minimum requirements for cluster servers are: • AMD Opteron or Intel EM64T servers running a supported 64-bit operating system. • A supported operating system (see Supported operating systems, page 11). • 512 MB of memory. • 1 GB of disk space on the installation drive for Matrix Server and its log and runtime files.
• Assigning multiple IP addresses to the same NIC is supported only for VLAN tagging. • Matrix Server does not support multiple NICs connected to the same subnet without the use of bonding or teaming. • Network interfaces should be multicast-capable. If an interface does not provide this capability, contact HP Support for assistance. • 802.3x Ethernet flow control cannot be used. Be sure to check the driver settings for your NICs to ensure that this feature is disabled.
See Chapter 2 of the HP PolyServe Matrix Server Administration Guide for more information about supported matrix configurations. Also see “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. You should be aware of the following: • All Matrix Server nodes must be members of an Active Directory domain. This is necessary for filesystem security. • Active Directory user and groups should be used in filesystem ACLs and SQL Server service accounts and roles. Do not use local users and groups for these purposes because they are meaningless to other nodes in the matrix.
Configuration information
2 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_4.0.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_4.0.0...msi.
Before the installation Before starting the installation, be sure to review the configuration and hardware requirements specified in Chapter 1. Also note the following. System drive requirement Windows 2008 requires that a device have an assigned drive letter or mount path before it will allow read or write access to a partition. Consequently, Matrix Server requires that the system drive (typically C:) be on an NTFS filesystem.
Action Description Reboot the server. You may also want to do a backup. Configure the storage array. Set up the storage array as described in the array product documentation. Install the iSCSI initiator (iSCSI only). Install the Microsoft iSCSI initiator on each server according to the product documentation. Install third-party MPIO software (optional). If you will be using HP or third-party MPIO software, install it according to the product documentation. Configure FC switches if necessary.
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. When configuring DNS, keep the following guidelines in mind: • If you have multiple public networks across the cluster, only one of the interfaces should be registered in DNS, and all nodes need to be registered on the same network.
2. Configure the server for WINS clients WINS clients may be unable to access multi-homed matrix servers (servers having multiple NICs) if NetBIOS and Microsoft client/server network bindings are enabled on all interfaces. These settings should be enabled only on publicly-reachable (routeable) interfaces.
IMPORTANT: In Windows 2008, the SAN storage is kept offline by default, as the SAN policy is set to “Offline Shared.” Use the command-based diskpart utility or the GUI-based Windows Disk Management utility to bring the storage online for the first node being configured. If the diskpart utility is used, you will need to clear the read-only disk attributes after the storage is online. If you will be using the XIOtech MAGNITUDE storage array, see the following document: http://h20000.www2.hp.
and communicate with other servers in the matrix, Matrix Server must remove the server’s access to filesystems to preserve data integrity. This step is called fencing. When you configure the matrix later in this procedure, you can select the fencing method that you want to use: • FibreChannel Switch-based fencing (also called “fabric fencing”). When a server needs to be fenced, Matrix Server disables the server’s access in the FibreChannel fabric.
Typically these tasks can be performed from the FC switch or from third-party applications. Refer to your FC switch or application documentation for more information. 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.
“prefer” to have I/O operations occur on natural block boundaries, such as 4-KB blocks. If a partition starts at a non-block boundary, a single logical write can span more physical blocks that it would on a partition starting on a block boundary, resulting in additional I/O operations. The exact alignment characteristics vary by manufacturer and model; consult your storage vendor for alignment recommendations.
Partition sizing It is important to properly size the partitions that will be used for membership partitions. (The minimum size is 1 GB.) 12. Log into iSCSI targets (iSCSI configurations only) Log into each iSCSI target via the iSCSI initiator and set the iSCSI Initiator Properties. On the Log On to Target dialog, be sure to check Automatically restore this connection when the system reboots. You will need to complete this step on each server. 13.
2. Right-click the file MxS_4.0.0...msi and select Run as Administrator to start the Installation Wizard. By default, Matrix Server is installed in the %SystemDrive%\Program Files\Polyserve\MatrixServer directory; however, you can specify another location. NOTE: If an event such as a power failure causes the installation to fail, reboot the server using the “Last known good configuration.” This option is available when you press F8 during startup.
Only the filesystems located on Master Volumes (not Standard Volumes) are snapshot capable. To locate MSA2000 array controller firmware, or snapshot license information, contact your HP representative. 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.
NOTE: If you are logged onto Windows as a user that is not a member of the machine local administrators group on the target server, click the As User button next to the “Connect to” field. You will then be prompted for a user name and password. After specifying the credentials, click Configure on the Matrix Server Connect dialog. The Configure Matrix window now appears.
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. License. Matrix Server can be used with either a temporary or a permanent license, which is provided in a separate license file.
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. This step ensures that the multicast traffic is targeted only at the servers with the same Secret Network Key. Cluster Administrative Traffic Protocol. Select either multicast or unicast mode. Multicast mode is recommended; however, if your network configuration does not allow multicast traffic through the network, you can use unicast mode.
Notes regarding fencing Before configuring fencing, you should be aware of the following: • If you will be using the Virtual Connect Fibre Channel Module on the HP c-Class Blade System, you must configure web mangement-based fencing. Switch-based fencing cannot be used with these modules. • If you will be using IPMI interfaces with web mangement-based fencing, you will need to change the password from the factory default. The fencing feature will not work correctly if the password is not changed.
Select your storage type and, for FibreChannel, specify the fencing method that you want to use. • Fibre-Channel switch-based fencing, below. • Web management-based fencing Fibre Channel switch-based fencing Complete the following on the SAN & Fencing tab: SAN Switches. Specify the hostnames or IP addresses of the FibreChannel switches that are directly connected to the nodes in the matrix. Click Add and then specify the hostname or IP address of the first FC switch.
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 you have completed the information, go to the Storage Settings tab, page 32.
Remote Management Controller Vendor. Select the vendor for your Remote Management Controller. For an IBM BladeCenter, also specify the Blade slot. 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.
your server names are server1 and server2 and their Remote Management Controllers are server1-iLO and server2-iLO, enter -iLO as the suffix. IP Delta. Specify the delta to add to each server’s IP address to determine the IP addresses of the associated Remote Management Controllers. For example, if your servers are 1.255.200.12 and 1.255.200.15 and their Remote Management Controllers are 1.255.201.112 and 1.255.201.115, enter 0.0.1.100 as the delta. Remote Management Controller Access.
• 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. Check this option if all servers in the matrix will be sharing the login account that you specified on the Remote Management Controller tab.
SAN Switches. Specify the hostnames or IP addresses of the FibreChannel switches that are directly connected to the nodes in the matrix. Click Add, and then specify the hostname or IP address of the first FC switch. Repeat this procedure to specify the remaining FC switches, including cascading switches. 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.
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. Create LUNs for the membership partitions and modify partition tables, page 18.
All of the available partitions on that disk or LUN then appear in the bottom of the window. Select one of these partitions and click Add. (The minimum size for a membership partition is 1 GB.) Repeat this procedure to select two more membership partitions. We recommend that the partitions be on different disks. When selecting partitions for use as membership partitions, be sure that they do not contain any needed data. When the membership partitions are created, any existing data will be erased.
NOTE: Array-based hardware snapshots are supported on HP EVA, HP MSA2000, and Engenio storage arrays. The appropriate HP or Engenio software must be installed as described under step 15. Install hardware snapshot software (optional), page 21. To configure the snapshot method, click Add, select the appropriate method, and then supply any requested configuration information. HP-EVA storage array. You will be asked for the hostname and authentication information for the management appliance.
Engenio storage array. You will be asked for the hostnames or IP addresses and the password for your storage array controllers. 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.
Go to the Matrix-Wide Configuration tab. Matrix-Wide Configuration tab This tab is used to export the matrix configuration to the other servers that will be in the matrix. It can also be used to start or stop Matrix Server on specific servers. 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. 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.
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. If an incorrect hostname or IP address was specified for the Remote Management Controller associated with the server, export the matrix configuration to that server again and then supply the correct information.
Install PolyServe Matrix Server
3 Install HP PolyServe Software This chapter describes how to perform new installations of HP PolyServe Software for Microsoft SQL Server and HP PolyServe Software for Windows File Serving. Install HP PolyServe Software for Microsoft SQL Server Prerequisites Before installing HP PolyServe Software for Microsoft SQL Server, the following prerequisites should be met: • PolyServe Matrix Server must be installed on each node. • Microsoft Cluster Services (MSCS) must not be installed. • The Microsoft .
Install HP PolyServe Software for Windows File Serving Prerequisites Before installing this product, you will need to install PolyServe Matrix Server on each node in the matrix. Installation procedure HP PolyServe Software for Windows File Serving must be installed on each server in the matrix that will be providing file shares. To install the product, insert the product CD into the CD drive or go to the location where you have downloaded the software. Then right-click the file MxFS_CIFS_4.0.0..
4 Remove HP PolyServe Software Remove Matrix Server To remove the Matrix Server package, select Start > All 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 Programs and Features interface to remove the PolyServe Matrix Server application; however, this method will remove the Matrix Server configuration files.
Remove HP PolyServe Software
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 2 and can be used in configuration scripts. We recommend that you review the description of the Configure Matrix window (see “16. Configure the matrix” on page 22) to become familiar with the actions performed by the mx commands.
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 ] ...
mx --matrix nodeA config snapshot add --method [--options ] (This command is needed only if you will be using the snapshot feature.) mx --matrix nodeA server add nodeA mx --matrix nodeA server start nodeA mx --matrix nodeA config description The matrix is now configured and Matrix Server is running on nodeA. Repeat the following set of commands to add the remaining nodes to the matrix and export the configuration to them.
fi set -x source cluster.conf MX="mx --matrix ${MATRIX} --user ${USER} --password ${PASSWORD}" # Configure cluster. ${MX} config license ${LICENSE} || exit 1 ${MX} config secret ${SECRET} || exit 1 ${MX} config fcswitch --community ${COMMUNITY} ${SWITCHES} || exit 1 ${MX} config mp set ${MP} || exit 1 # Export the config to all the other nodes and start them up.
Command descriptions The mx commands used in the configuration specify the following information. mx config license The location of the Matrix Server license file. The file must be present on the server running the command. mx config secret This password provides additional security for network communications among the servers in the matrix. The password can contain up to 127 characters.
• The minimum size for a membership partition is 1GB. mx server add Add the specified node to the matrix. mx server start Start Matrix Server on the specified node. mx config description 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.
For IBM Blade Center only, the blade slot. --mixedvendor yes|no Whether the vendor and type settings apply to all servers. [--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.
Configure the matrix from the command line
B Support and other resources HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
