HP Smart Array Multipath Software User Guide October 2003 (Third Edition) Part Number 307958-003 HP CONFIDENTIAL Writer: Rob Weaver File Name: a-frnt.
© 2003 Hewlett-Packard Development Company, L.P. Microsoft® and Windows®are U.S. registered trademarks of Microsoft Corporation. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products.
Contents About This Guide Audience Assumptions........................................................................................................v Important Safety Information ..............................................................................................v Symbols in Text................................................................................................................. vi Related Documents.....................................................................................
Contents Chapter 2 Installation and Operation Preparing for Software Installation..................................................................................2-1 Installing the Smart Array Multipath Software................................................................2-2 Upgrade Procedures for Microsoft Operating Systems.............................................2-2 Uninstalling Smart Array Multipath Software Driver...............................................2-3 First-Time Installation........
About This Guide This guide provides installation and troubleshooting procedures for the Smart Array Multipath software for the HP StorageWorks Modular Smart Array 500 system. Audience Assumptions This guide is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
About This Guide Symbols in Text These symbols may be found in the text of this guide. They have the following meanings. WARNING: Text set off in this manner indicates that failure to follow directions in the warning could result in bodily harm or loss of life. CAUTION: Text set off in this manner indicates that failure to follow directions could result in damage to equipment or loss of information.
About This Guide Technical Support In North America, call the HP Technical Support Phone Center at 1-800-652-6672. This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. Outside North America, call the nearest HP Technical Support Phone Center. Telephone numbers for worldwide Technical Support Centers are listed on the HP website, www.hp.com.
About This Guide Reader’s Comments HP welcomes your comments on this guide. Please send your comments and suggestions by e-mail to ServerDocumentation@hp.com. viii HP Smart Array Multipath Software User Guide HP CONFIDENTIAL Writer: Rob Weaver File Name: a-frnt.
1 System Preparation Overview Smart Array Multipath software delivers dual path functionality and supports failover capability for redundant host bus adapters (HBAs) in a server with redundant cabling to an HP StorageWorks Modular Smart Array 500 system. This fault-tolerant tool enhances availability in clustering and direct attached storage (DAS) solutions with up to two servers managing up to 2 TB of stored data. The software supports multiple I/O paths to the same logical volumes.
System Preparation • An MSA500 system with the following: — At least one HP StorageWorks Modular Smart Array 500 controller — A 2-Port Shared Storage Module and two SCSI cables or — A 4-Port Shared Storage Module and four SCSI cables For the latest versions of firmware, refer to www.hp.
System Preparation Microsoft Feature Support Features supported under Microsoft operating systems include: • Static LUN balancing enables the administrator to optimize I/O by assigning specific volumes to specific paths in the storage system. If one path fails, the system moves volumes to the path for the redundant HBA for I/O management.
System Preparation Supported Four-Node Configurations The following sections identify supported multipath configurations with their respective 4-Port Shared Storage Module connections and locations for boot and data volumes. These configurations require two or three servers attached with four SCSI cables to the MSA500 system. Two-Server External Boot Configuration (Microsoft Only) All boot and data volumes reside on the MSA500 system.
System Preparation Two-Server Mixed Boot Configuration One boot volume resides on its respective server, while the other boot volume resides on the MSA500 system. Both data volumes reside on the storage system. Table 1-3: Two-Server Mixed Boot Configuration Server Port (Bus) 1 A1 Boot Volume Location Data Volume Location Storage system* Storage system Server 2 Storage system B1 2 A2 B2 *Linux operating systems support boot volumes on servers only.
System Preparation Three-Server External Boot Configuration (Microsoft Only) All boot and data volumes reside on the MSA500 system. One server connects to two ports. Table 1-5: Three-Server External Boot Configuration (Microsoft Only) Server Port (Bus) 1 A1 Boot Volume Location Data Volume Location Storage system Storage system B1 2 A2 3 B2 Three-Server Internal Boot Configuration Boot volumes reside on their respective servers, while data volumes reside on the MSA500 system.
System Preparation Three-Server Mixed Boot Configuration Two boot volume resides on their respective servers, while one boot volume resides on the MSA500 system. All data volumes reside on the storage system. One server connects to two ports. Table 1-7: Three-Server Mixed Boot Configuration Server Port (Bus) 1 A1 Boot Volume Location Data Volume Location Storage system* Storage system B1 2 A2 Server 2 3 B2 Server 3 *Linux operating systems support boot volumes on servers only.
System Preparation Additional Red Hat and SuSE Linux Preparations IMPORTANT: For Red Hat and SuSE operating sytems, configure the system for multipath before installing the software from the CD. For configuration instructions for UnitedLinux operating systems, refer to Chapter 2, “Installation and Operation.
System Preparation b. Identify the kernel. An example is 2.4.9-e.3enterprise, where “enterprise” is the name of the kernel. Remember the name for use in later procedures. 2. Use an editor to modify the Makefile. For example, enter: vi Makefile 3. In the EXTRAVERSION field, replace the current value (typically -e.3custom) by entering: –e.3enterprise using the name of your kernel in place of “enterprise.” Overwriting the Active .Config File Depending on the operating system, use the procedures below.
System Preparation SLES 7 Operating System To overwrite the active .config file for the SLES 7 operating system: 1. Locate the specific .config file for the modified kernel: a. From the root level, enter: cd /boot b. Identify the appropriate .config file by name, for example vmlinuz.config 2. Copy the kernel to the root level directory and overwrite the active .config file. Enter: cp vmlinuz.config /usr/src/linux/arch/i386 3. Go to the root directory. Enter: cd /usr/src/linux/arch/i386 4.
System Preparation 6. Be sure that the Multipath I/O support option is set as a module. If it is not set as a module, use the space bar to cycle through the settings until an “M” appears next to the option. 7. Press the Esc key twice to exit the menus. 8. When prompted to save the new kernel configuration, press the Enter key to select Yes. 9. Make the kernel: a. From the root level, enter: make b. Wait for the kernel to be made.
System Preparation Modifying the RAIDTAB Configuration File To perform multipath operations with a Linux operating system, a raidtab configuration file must be present. Use the instructions in the following sections to be sure the raidtab configuration file contains the appropriate information.
System Preparation The raidtab configuration file must reside in the /etc directory.
System Preparation raiddev /dev/md2 raid-level multipath nr-raid-disks 2 persistent-superblock 1 chunk-size 8 device /dev/cciss/c0d2p3 raid-disk 0 device /dev/cciss/c1d2p3 raid-disk 1 Completing the Linux Multipath Setup After a valid raidtab file is created in the /etc directory, verify that the correct drivers and modules are loaded. To verify properly loaded files: 1. Verify that the md and multipath drivers are loaded, either statically or by a module load.
System Preparation 2. Verify that the md driver is in the kernel. Enter: dmesg | grep md | more This command shows the boot-time messages. If the md driver was loaded, several messages should appear, similar to the following messages: md: md driver version X.X md: Autodetecting RAID arrays md: autorun… md: …autorun DONE 3. If the multipath driver was built as a module but not loaded, load the module. Enter: insmod multipath This command loads the driver.
System Preparation b. Make filestystems on the raid devices. Enter: mkfs –t ext2 /dev/md0 mkfs –t ext2 /dev/md1 mkfs –t ext2 /dev/md2 mkfs –t ext2 /dev/md3 mkfs –t ext2 /dev/md4 IMPORTANT: The example in step 5b uses ext2 because known bugs in the ext3 filesystem can cause data corruption. 6. The multipath RAID device should be functioning.
2 Installation and Operation Preparing for Software Installation To prepare for software installation: 1. Complete the MSA500 system hardware installation: a. Install the MSA500 system. b. Install the 4-Port Shared Storage Module. c. Install the controllers. d. Update the system firmware, if needed. 2. Complete the server installation: a. Install all hardware, including a second supported HBA IMPORTANT: For Microsoft operating system installation, the server only supports one SCSI path during installation.
Installation and Operation 4. Depending on the operating system, do one of the following: — If the server has a Microsoft operating system, be sure that only one SCSI cable is connected from the server to the MSA500 system. During installation, the Smart Array Multipath software supports only one SCSI path per Microsoft-based server. — If the server has a Red Hat or SuSE Linux operating system, edit the active kernel and modify the RAIDTAB configuration.
Installation and Operation 1. Uninstall Smart Array Multipath software, if installed. Refer to “Uninstalling Smart Array Multipath Software Driver” in this chapter. 2. Upgrade to Windows Server 2003. 3. Install Smart Array Multipath software v2.0 or later. Refer to “First-Time Installation” in this chapter. Upgrading from v1.0 to v2.0 1. Uninstall Smart Array Multipath software v1.0. Refer to “Uninstalling Smart Array Multipath Software Driver” in this chapter. 2. Install Smart Array Multipath software v2.
Installation and Operation 8. Click OK. NOTE: A Microsoft Windows Server 2003 system does not indicate progress during the removal. Wait at least 10 minutes to allow the system to complete the removal. 9. Click Cancel. 10. Shut down the server. 11. Disconnect the SCSI cable from the redundant HBA. First-Time Installation 1. To install the Smart Array Multipath software, refer to the HP Smart Array Multipath Software CD Installation Instructions that ship with the CD. 2.
Installation and Operation UnitedLinux Configuration After installing Smart Array Multipath software on a server with a UnitedLinux operating system, configure for multipath operations. Review the following sample configuration procedure. This sample assumes that the user wants to set /dev/cciss/c1d0p2 and /dev/cciss/c2d0p2 to point to the same volume as a multipath device. To configure the system for multipath use: 1.
Installation and Operation Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Number Major Minor RaidDevice State 0 106 2 0 active sync /dev/cciss/c2d0p2 1 105 2 1 active sync /dev/cciss/c1d0p2 UUID : b1ec5895:5ed49b44:7ec7d4a8:397e19b1 IMPORTANT: You can also review status by running: /proc/mdstat Results would look similar to the following: Personalities : [multipath] read_ahead 1024 sectors md0 : active multipath cciss/c2d0p2[0] cciss/c1d0p2[1] 14683328 blocks [2/2] [UU] unused dev
Installation and Operation Multipath Operations Microsoft Browser Security Settings For Windows Server 2003, the modified version of Internet Explorer 6.0 defaults all servers to the “Internet zone,” which enables the highest level of security. At this security level, browsing to HP Management agents generates many security messages. To avoid these security messages: 1. Open Internet Explorer 6.0. 2. Select Tools>Internet Options. 3. Select the Security tab. 4. Click Local intranet. 5.
Installation and Operation 4. Right-click one of the array controller icons and click Properties. 5. When the Properties window opens, click the Redundancy Configuration tab. From the Redundancy Configuration tab, the administrator can view the following controller information: — Name — Slot number — Status — Slot number of redundant controller — Controller tree 6. In the controller tree, right-click one of the logical volumes and then click Switch Path.
Installation and Operation 8. From the Multipath Management and Configuration screen, do one of the following: — To move all drives from the current path to the redundant path, click the link for the controller and select Switch All Paths. The system moves all drives to the redundant path. — To move a drive from one path to the redundant path, click the link for the drive and select Switch Path.
3 Troubleshooting Problem Diagnosis When a problem exists with the multipath I/O, consult the Insight Management Agents and do one of the following: • For Microsoft operating systems: — Use the ProLiant Storage Manager FAQs — Use the ProLiant Storage Manager software and the Device Manager Extension to identify I/O path status.
Troubleshooting 3. Be sure that the hardware installation meets the minimum requirements for the software. Refer to “Minimum Requirements” in Chapter 1, “System Preparation.” 4. Be sure that the SCSI cabling configuration is complete. Refer to “Supported Four-Node Configurations” in Chapter 1, “System Preparation.” 5. Be sure that the HBA is functioning properly. Refer to the appropriate server and HBA documentation. If the HBA has failed, refer to “HBA Failure” in this chapter. 6.
Troubleshooting HBA Failure If one of the HBAs in the server fails, the redundant HBA performs all I/O operations. To replace the failed HBA: 1. Power down the HBA in one of the following ways: — For a PCI-based HBA in a Microsoft operating system environment, use the PCI Hot Plug functionality in the server to power down the HBA while the server is online. — For an embedded HBA in a Microsoft operating system environment, power down the server.
Troubleshooting Cable Failure To replace the failed cable: 1. Power down the HBA in one of the following ways: — For a PCI-based HBA in a Microsoft operating system environment, use the PCI Hot Plug functionality in the server to remove the HBA while the server is online. — For an embedded HBA in a Microsoft operating system environment, power down the server. — For an HBA in a Linux operating system environment, power down the server. 2. Disconnect the SCSI cable: a.
Index A K additional preparations 1-7 Array Configuration Utility 2-9 array controllers, supported 1-1 authorized reseller vii kernel procedures 1-10 L C Linux additional preparations 1-8 feature support 1-3 cable failure 3-4 Config file overwriting 1-9 configurations, four-node 1-4 M D Device Manager Extension 2-7 F firmware updates 2-1 Makefile modifications 1-8 Microsoft additional preparations 1-7 feature support 1-3 minimum requirements 1-1 modules in Linux 1-11 multipath operations 2-7 O
Index P PCI Hot Plug functionality 1-3 multiple operating systems 1-3 operating systems 1-2 static LUN balancing 1-3 symbols in text vi R raidtab configuration file 1-12 requirements, minimum 1-1 S static load (read-only) balancing functionality 2-9 support 1-3 static LUN balancing support 1-3 with Device Manager 2-7 with ProLiant Storage Manager 2-8 support array controllers 1-1 configurations, four-node 1-4 Index-2 T technical support vii telephone numbers vii troubleshooting cable failure 3-4 HBA f
