Académique Documents
Professionnel Documents
Culture Documents
Notices
The information in this document is subject to change without notice. While every effort has been made to ensure that all information in this document is accurate, the Authors accept no liability for any errors that may arise. No part of this document may be transmitted or copied in any form, or by any means, for any purpose, without the written permission of the Authors. Issue 2.3 August 22, 2008 Part No. 0078953-06A
Acknowledgments Microsoft, Windows, and Windows Server are registered trademarks of Microsoft Corporation. All names, brands, products or services are trademarks or registered trademarks of their respective companies.
ii
Contents
Contents
Preface ................................................................................................................................................... v Revision History ...................................................................................................................................... v 1 Introduction ..................................................................................................................................... 1.1 Introduction .................................................................................................................................. 1.2 System Requirements ................................................................................................................. 1.2.1 Hardware Requirements .................................................................................................... 1.2.2 Supported Operating Systems ........................................................................................... 1.2.3 Software Requirements ...................................................................................................... 1.3 Whats New ................................................................................................................................. 1.3.1 Support for Microsoft Windows Server 2008 ...................................................................... 1.3.2 Single Installer for All Hardware Types .............................................................................. 1.3.3 Upgrading No Longer Requires Uninstall ........................................................................... Installation ....................................................................................................................................... 2.1 Installation ................................................................................................................................... 2.2 Components ................................................................................................................................ 2.3 Uninstallation ............................................................................................................................... 1 1 1 2 2 2 2 2 2 3 5 5 6 6
User Interface .................................................................................................................................. 9 3.1 Control Panel ............................................................................................................................... 9 3.2 Advanced Configuration ............................................................................................................ 11 3.3 Change Host ............................................................................................................................. 12 3.4 Tech Support ............................................................................................................................. 13 3.5 Windows Server 2008 Integrated MPIO Interfaces ................................................................... 13 3.5.1 MPIO Control Panel Application ....................................................................................... 14 3.5.2 Device Manager MPIO Tab .............................................................................................. 16 How To ....................................................................................................................................... 4.1 How to Set the Path Selection Policy ........................................................................................ 4.2 How to Automatically Select Preferred Paths ............................................................................ 4.3 How to Manually Select Preferred Paths ................................................................................... 4.4 How to Manage a System Remotely ......................................................................................... 4.5 How to Determine Which Path is in Use ................................................................................... 19 19 19 20 20 21
5 6
Known Issues / Limitations .......................................................................................................... 23 Troubleshooting ............................................................................................................................ 6.1 Installation errors ....................................................................................................................... 6.1.1 Previous version detected ................................................................................................ 6.1.2 Device driver already loaded ............................................................................................ 6.2 The Storage Doesnt Appear ..................................................................................................... 6.3 The Problem Cant Be Resolved ............................................................................................... 25 25 25 26 26 27
iii
7.2 Error Messages ......................................................................................................................... 30 7.3 Informational Messages ............................................................................................................ 30 7.4 Warning Messages ................................................................................................................... 31 Glossary ............................................................................................................................................... 33
iv
Preface
Preface
What is in this guide This user guide gives you an overview of how to use the Xyratex StorView Path Manager for Windows to configure multipathing in a RAID system. Who should use this guide This user guide is for those needing to set up a multipath solution in the Windows environment. About this guide This user guide provides the following information: Chapter 1, Introduction, on page 1 provides an introduction and system requirements. Chapter 2, Installation, on page 5 gives details on how to set up the software, what components are included and how to uninstall. Chapter 3, User Interface, on page 9 details the graphical user interface. Chapter 4, How To , on page 19 provides step-by-step instructions for a number of common tasks. Chapter 5, Known Issues / Limitations, on page 23 gives warning of any limitations in the software. Chapter 6, Troubleshooting, on page 25 provides resolutions for some common problems. The Glossary on page 33 defines some of the terms used throughout this user guide.
Revision History
Version 1.0 1.1 2.0 2.1 2.2 2.3 Date Description of Change September 26, 2006 Initial Release. April 13, 2007 Updates for version 4.
September 19, 2007 Introduction of path selection policies. February 20, 2008 June 20, 2008 August 22, 2008 Added support for RS-1220-F4-6412E enclosure. Windows Server 2008 support, single installer for all enclosures. Minor updates.
vi
Introduction
Chapter 1
Introduction
1.1 Introduction
Xyratex StorView Path Manager for Windows is a Windows Multipath Input/Output (MPIO) solution. It utilizes the Microsoft Windows MPIO framework. Official Microsoft documentation concerning MPIO can be found here: http://www.microsoft.com/windowsserver2003/technologies/storage/mpio/default.mspx Multipathing is the use of multiple physical components (such as host bus adapters, cables and switches) to provide two or more data paths to a storage device and hence avoid a single point of failure. When a component in one path fails, a different path to the device will still be available for data transfer. A path is defined as the complete route from host to controller, including the HBA, cabling and possibly a switch. A multipath solution requires that there is more than one of these paths. The number of paths is easy to see if direct connections are made (it is simply the number of physical cables), but less obvious if a switch is used. If, for example, there are 3 HBAs connected to a switch, and the switch is connected to both ports of a controller, this results in a total of 6 paths. Xyratex StorView Path Manager for Windows can be configured to use various Path Selection Policies. A Path Selection Policy indicates how the software will decide which path to use for I/O at a given moment. For example, the path manager can be configured to always use the Preferred Path if it is available, or alternatively, to perform Load Balancing using a Round Robin path selection policy. For more information about Path Selection Policies, see 4.1, How to Set the Path Selection Policy, on page 19.
Introduction
hardware you have. Additionally, if you have more than one type of storage enclosure, a single GUI will manage all of them.
Installation
Chapter 2
Installation
2.1 Installation
Warning Due to the low-level nature of this software, you must not abort installation part-way through. Doing so may cause adverse effects, including system corruption. To install StorView Path Manager for Windows: 1 Note Disconnect all storage subsystems from the host system. If a storage subsystem is running the operating system for the host, do not disconnect this storage subsystem. Start Windows Explorer and double-click the executable installation file. Click Next at the Welcome message. Read the License Agreement. If you are happy with the terms of use, click I Agree. You will be reminded to remove all storage connections. Once you have done so, check the box marked I have physically removed all connections to my storage, other than storage that may serve as the operating system boot partition and click Next. Choose the folder in which to install the application (the default is: Program Files\StorView Path Manager 6.00). Click Install. If a previous version of Xyratex StorView Path Manager is detected, you will be prompted whether or not to updgrade to the new version. Click Yes to upgrade. Wait for installation to complete. Do not interrupt the installation. You will be prompted to restart your computer. Click Yes. Re-connect all storage subsystems.
2 3 4 5
8 9 10
2.2 Components
StorView Path Manager for Windows consists of the following files: MPIO drivers (mpio.sys, mpdev.sys, mpspfltr.sys) These are Microsoft's part of the MPIO solution. Version 1.20 of the drivers will be installed. Any existing vendor-specific MPIO solution will still work properly, since MPIO is backwards compatible. DSM driver (xyrsp2x0.sys) This is the Xyratex vendor-specific part of the MPIO solution. A DSM driver is installed for each type of Xyratex storage enclosure. Note that the numeric part of the filename may differ on older versions of the software. Control Panel GUI (svpmgui.exe) Used to manage the multipath solution. Installation program.
2.3 Uninstallation
Warning Due to the low-level nature of this software, you must not abort uninstallation. Doing so may cause adverse effects, including system corruption. StorView Path Manager for Windows can be uninstalled in the standard manner: 1 Note Disconnect all storage subsystems from all HBAs before uninstalling (if this is not done, uninstallation can take a long time, especially on a system with many paths). If a storage subsystem is running the operating system for the host, do not disconnect this storage subsystem. Click the Start button. Click Control Panel -> Add or Remove Programs. Find the entry for StorView Path Manager and click on it. Click the Remove button and follow the on-screen instructions. Reconnect the storage subsystems. If your Operating System is running on an MPIO device that is controlled by this StorView Path Manager installation, the uninstaller will not be able to completely remove the Microsoft MPIO drivers. The StorView Path Manager software will still be uninstalled by the uninstaller, and there will be no adverse affects on the system. If this happens, you may manually uninstall the Microsoft MPIO drivers after you reboot. This is optional, and can be done as follows: 1 Open the Windows Device Manager. 2 Expand the SCSI and RAID controllers node by clicking the + icon. 3 Right click on Multi-Path Support and select the Uninstall option.
2 3 4 5 6 Note
Installation
4 Click OK on the Confirm Device Removal window. 5 Reboot the system when prompted.
User Interface
Chapter 3
User Interface
3.1 Control Panel
Configuration of StorView Path Manager for Windows is available from the Windows Start Menu (All Programs -> StorView Path Manager -> StorView Path Manager). The control panel automatically updates about every 10 seconds.
Figure 31
At the top of the pane, the Managing Host line shows the network address of the computer currently being managed. By default, this is the local system. It can be changed using the Change Host link (see 3.3, Change Host, on page 12). The right hand pane shows one line for each multipathed logical drive with the following information: The Disk Number (as shown in the Windows Disk Management). The capacity in GB. The drive letters of any volumes seen by Windows. A maximum of two letters will be shown. If more exist, a ... will be shown and the rest can be viewed by hovering the mouse over the text and waiting for the tooltip to appear. The combined read/write rate in MB/s. The combined number of read/write IOPS (Input/Outputs Per Second). An icon identifying that the logical drive is part of a cluster, if applicable. The operating system would normally see each and every path as a separate logical drive, but MPIO enables it to see which paths point to the same logical drive and lists those paths under each drive accordingly. Clicking the plus sign (+) opens the multipath information for the Disk: The Path Selection Policy. This can be Failover, Failover/Failback, or Round Robin. See Setting the Path Selection Policy for details. The Serial Number (SN) as reported in byte 0x83 of the data format returned by a SCSI Inquiry command. The number of paths. For each path, the following is also shown: State: Active The path is healthy and is currently being used to handle I/O. Passive The path is healthy, but not currently in use. Failed The path has encountered errors. It is not healthy and cannot be used. It may be removed or may recover, depending on the situation. SCSI Address - In the form Port:Bus:Target:LUN: Port The HBA number. Bus The HBA port. Target The target ID of the logical drives (this may not match the controller target ID settings because Windows uses its own scheme for assigning target IDs). LUN The Logical Unit Number. Any two devices with the same Port, Bus and Target will be on the same physical path. Controller The controller and controller port to which the path is connected. This is in the form CxPy, where x is the controller number (0 or 1) and y is the port number (0 or 1). Preferred path - If the Path Selection Policy is set to Failover/Failback, the preferred path will be used in preference to any other. Also, if the preferred path fails and is subsequently restored, I/O will return to using this path. The preferred path is only applicable when the Path Selection Policy is Failover/Failback. The left hand pane contains two links: Advanced Configuration (see 3.2, Advanced Configuration, on page 11) allows fine-tuning of MPIO parameters. Tech Support (see 3.4, Tech Support, on page 13) version numbers and DSM trace control.
10
User Interface
Figure 32
Advanced Configuration
The options presented here have useful defaults and generally dont need to be changed to get MPIO running successfully. The following configuration items are present: Retry Count The number of times the driver will retry a failed path before it is declared invalid. It will then be removed after the period of time specified in the PDO Remove option. Retry Interval The time in seconds that the driver waits before retrying a path that returned an error. PDO Remove Period The amount of time to wait before removing Physical Device Objects that have been declared invalid. Path Verify If this option has a check mark, Passive paths (those with no I/O) will be tested in the background for validity and declared invalid if they fail. Path Verification Period The interval (in seconds) for checking idle paths see the Path Verify option above.
11
Auto Balance If this option has a check mark, preferred paths of all LUNs are automatically balanced evenly between host ports and controller ports. This enables distribution of I/O load by utilizing as many host ports and controller ports as possible. Additionally, when this feature is enabled, the storage administrator no longer has to manually manage preferred paths. Initial Rebalance Interval The time in seconds that the driver waits after booting up, before performing Auto Balance of preferred paths. If Auto Balance is not checked, this value is ignored. Auto Balance will occur if a path is added or removed. To avoid multiple rebalances as paths are initially discovered, this value allows a minimum time for the first Auto Balance occurrence. Rebalance Interval The time in seconds that the driver waits, after the initial rebalance interval has elapsed, before responding to configuration changes by performing Auto Balance of preferred paths. Auto Balance will occur if a path is added or removed. To avoid multiple rebalances in a short period of time, this value allows a minimum interval between Auto Balance occurrences. Click Apply to make changes, or Close to exit without altering the settings.
Figure 33
Change Host
Enter one of the following to connect to a different host computer: The Windows host name, for example: \\host1. The qualified host name, for example: host1.company.com. The IP address of the host, for example: 192.168.109.131. Note The user name and password of the remote host must be identical to that of the current host in order to make a connection. If a connection is established, the Managing label will change to the name of the new host computer and the Control Panel will reflect the settings on the new system. Otherwise an error message will appear.
12
User Interface
Figure 34
Tech Support
The following version numbers are shown: StorView Path Manager for Windows Version. This is the version of the Xyratex StorView Path Manager for Windows GUI. Microsoft MPIO Driver Version. This is the version number for the Microsoft part of the MPIO drivers. DSM traces can also be generated from this window. This is only necessary if you are experiencing problems with StorView Path Manager for Windows. The trace should be sent to your storage vendor as it may contain useful debug information. Traces can be enabled or disabled by clicking on the link of the same name (a reboot will be required for the change to take effect). To view a DSM trace click the Get Trace link. The results will be shown in Windows Notepad.
13
3.5.1.1
MPIO-ed Devices
This tab shows which storage products are under MPIO control and allows you to add and remove support for MPIO to storage devices. Note that if the Add button is used to add MPIO support to a storage device, the specified storage device will be under control of the generic Microsoft DSM and the specialized Xyratex driver will not be loaded. Instead of using the Add button on this tab, follow the Installation instructions documented in 2.1, Installation, on page 5. Similarly, you should not use the Remove button to remove MPIO support for Xyratex storage devices. Doing so will result in only a partial uninstall of Xyratex StorView Path Manager for Windows, and will result in difficulty when uninstalling or re-installing StorView Path Manager. When StorView Path Manager for Windows is installed on the system, the MPIO-ed Devices tab will show the Xyratex storage devices that are under MPIO control, as shown in the figure below.
Figure 35
MPIO-ed Devices
14
User Interface
3.5.1.2
Discover Multi-Paths
This tab allows the user to add MPIO support to storage devices. Note that if the Add button is used to add MPIO support to a storage device, the specified storage device will be under control of the generic Microsoft DSM and the specialized Xyratex driver will not be loaded. Instead of using the Add button on this tab, follow the Installation instructions documented in 2.1, Installation, on page 5. If Xyratex StorView Path Manager for Windows is installed, Xyratex storage devices will not show up on this tab. They will only show up on this tab if you have not installed the appropriate version of StorView Path Manager for Windows. The figure below shows the case where a RS-1220-F4-6412E (F6412E) is attached to the system, but StorView Path Manager for Windows has not yet been installed.
Figure 36
Discover Multi-Paths
15
3.5.1.3
DSM Install
This tab allows you to install a DSM using the raw driver files. Rather than using this tab, follow the Installation instructions documented in 2.1, Installation, on page 5.
Figure 37
DSM Install
Figure 38
16
User Interface
The preferred method of viewing and configuring MPIO properties for Xyratex storage is to use the StorView Path Manager User Interface, as described earlier in this chapter. However, limited support is provided for using the Device Manager MPIO tab. The Device Manager MPIO tab shows the Path Selection Policy for a Logical Drive (labeled as the Load Balance Policy), as well as a list of paths. The Load Balance Policy maps to the Path Selection Policy as follows: Table 31 Path Selection Policy <-> Load Balance Policy Load Balance Policy displayed on the Device Manager MPIO tab Fail Over Only Round Robin Vendor Specific
Path Selection Policy (see Section 4.1) Failover/Failback Round Robin Failover Note
Note the difference between the Xyratex terminology Failover and the Microsoft Device Manager terminology Fail Over Only. These are two different policies. The Device Manager MPIO tab can be used to modify the Path Selection Policy in a limited manner. To modify the Path Selection Policy using the Device Manager MPIO tab: Select Fail Over Only or Round Robin as the Load Balance Policy. Click OK. As noted in the table above, Fail Over Only maps to Failover/Failback. Since Vendor Specific cannot be selected as the Load Balance Policy, this means that the Device Manager MPIO tab cannot be used to set the Path Selection Policy to Failover. Please use the StorView Path Manager User Interface, as described earlier in this chapter 3, to perform this action. Selections other than Fail Over Only, Round Robin, and Vendor Specific may appear as choices for the Load Balance Policy. However, these are the only choices that are supported by Xyratex StorView Path Manager for Windows. The Device Manager MPIO tab can also be used to view and modify path properties. To view path properties, select a path and click Edit... The figure below shows the resulting screen.
17
Figure 39
From this screen, the user can modify the Preferred Path. To modify the Preferred Path using this screen: Edit the path that is to be made the Preferred Path check the Preferred checkbox, and click OK. Edit the path that was previously the Preferred Path, uncheck the Preferred checkbox, and click OK. Click OK on the Device Manager MPIO tab. Please note the following: The Preferred Path can only be modified in this manner for Logical Disks that have the Fail Over Only Load Balance Policy. Please use the StorView Path Manager User Interface, as described in Chapter 3, to modify the Preferred Path for other Logical Disks. If more than one path is marked as Preferred, no change to the Preferred Path will be made. Changes to the Path State are ignored.
18
How To ...
Chapter 4
How To
4.1 How to Set the Path Selection Policy
1 2 3 Open the User Interface (see 3.1, Control Panel, on page 9). Expand the disk in question by clicking the + button. Click on the Path Selection Policy for the logical disk. The Path Selection Policy shows up as a hyperlink and can be set to Failover, Failover/Failback, or Round Robin. The Path Selection Policy window will open. Select the policy you wish to use for this logical drive: Failover: The Preferred Path is the default path for I/O. If this path fails, I/O will failover to the next available path. If the previous path comes back online, I/O does not failback to the previous path. Failover/Failback: The Preferred Path is the default path for I/O. If this path fails, I/O will failover to the next available path. If the Preferred Path becomes available again, I/O will failback to the Preferred Path. Round Robin: I/O is distributed among all healthy paths in a round robin fashion. This can be used to achieve load balancing.
19
Wait for preferred paths to be automatically balanced. There may be a delay before this occurs.
20
How To ...
21
22
Chapter 5
23
24
Troubleshooting
Chapter 6
Troubleshooting
6.1 Installation errors
6.1.1 Previous version detected
This occurs if you receive the following error message: Setup has detected an existing version of this Multi Path Driver. Please uninstall the existing driver, then run this installer again. Make sure StorView Path Manager is not already installed. If it is, uninstall it via Add/Remove Programs, and run the installer again. If you are unable to uninstall StorView Path Manager via Add/Remove Programs, this could indicate that the installer was previously interrupted before it could complete. To manually eliminate the previous version, use the following procedure: 1 In C:\Program Files, if there are any folders named StorView Path Manager #.# (where #.# is the version number), delete the folder. Remove registry entries as follows: 1 From the Windows Start menu, select Run. 2 Enter regedit and click OK. 3 Navigate to: My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MPDEV. 4 If there is an entry named MPIOSupportedDeviceList, remove all entries matching the storage device you are trying to install. For example, if you are installing StorView Path Manager for a Xyratex F5402E, remove the entry that says XYRATEX 5402E. Note: Certain storage products are paired together. If your storage system is Xyratex F5402E, also remove the entry for Xyratex F5412E, and vice versa. If your storage system is Xyratex E5402E, also remove the entry for Xyratex E5412E, and vice versa.
25
5 Navigate to My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\. 6 Look for any entries named xyrsp200, xyrsp210, or xyrsp230. Delete these entries. 3 Run the installer again.
26
Troubleshooting
If you have doubts as to which device drivers are being used, they can be determined using the following procedure: 1 2 3 4 5 Open the Windows Device Manager. Expand the Disk Drives node by clicking the + icon. Right click on the desired drive and select the Properties option. Click on the Driver tab. Click the Driver Details button. If the driver named mpdev.sys is listed, the MPIO drivers are in use for this device.
27
28
Event Codes
Chapter 7
Event Codes
7.1 Events
Xyratex StorView Path Manager for Windows uses the standard Windows System event log to record any information or errors that may be of interest. The Source of an event generated by Xyratex StorView Path Manager for Windows will be of the form xyrsp2##, where ## is dependent on the version of the software in use. To view events: 1 2 In the Windows Control Panel, select Administrative Tools -> Event Viewer. Click on the System log to view system-level events.
29
3 4
Could not access the supported These errors can happen as a result of registry corruption. Try device list from the registry uninstalling and re-installing Xyratex StorView Path Manager for Windows to make sure the contents of the registry is valid. Could not access the path selection policy from the registry
The multi-path DSM has started The path manager driver has been loaded. This should happen every time the system boots. Found new logical drive [SN: <drive>] on path <path> A logical drive has been discovered. This typically happens at boot time for all logical drives that are managed by Xyratex StorView Path Manager for Windows. It also occurs when a new LD is created or discovered by the host.
259 260
Adding redundant path <path> to An additional path has been found for a logical drive. logical drive [SN: <drive>] The active path on logical drive The active path has switched from a non-preferred path to the [SN: <drive>] has been switched preferred path. to the preferred path on <path> The preferred path has been set The preferred path has been set via the Xyratex StorView to <path> on logical drive [SN: Path Manager for Windows control panel. <drive>] The controller time is <time> via Occurs when a path is discovered. The owning controller path <path> timestamps the event.
261
262
30
Event Codes
<path> The identifier for the path, in the form [LogicalDriveNumber port:bus:target:lun]. <time> The controller time.
514
515
The path for logical drive [SN: <drive>] has failed over to <path> because of a path error
<drive> The serial number of the drive. <path> The identifier for the path, in the form [LogicalDriveNumber port:bus:target:lun].
31
32
Glossary
Glossary
Auto Balance A feature that automatically balances preferred paths evenly among all available host ports and controller ports. This helps to spread I/O load by utilizing as many host ports and controller ports as possible. DSM Device Specific Module Code written by a vendor that allows their hardware to use Microsoft's MPIO. Failover Failover occurs when a path becomes unavailable and another path is used to route I/O. Note that the term Failover is different to the Microsoft Device Manager term Fail Over Only. Failover/Failback Failover occurs when a path becomes unavailable and another path is used to route I/O. Failback occurs when a preferred path is set, it fails, and is subsequently restored. In this case I/O will fail back to the preferred path once it is available again. MPIO Multipath Input/Output A multipath solution built into Microsoft server-grade operating systems. It requires a vendor-specific DSM to work with a given piece of hardware. Preferred Path When the Path Selection Policy is set to Failover/Failback, the preferred path is always used if it is available. If the preferred path fails, I/O will switch to another path. If it is later restored, I/O will switch back to the preferred path. Round Robin The Round Robin Path Selection Policy causes all healthy paths to be used for I/O. Paths are used in a round-robin order.
33
34