StorageWorks Secure Path for Windows NT A High Availability Solution Installation Guide EK–WNTMP–MH.
While Compaq Computer Corporation believes the information included in this manual is correct as of the date of publication, it is subject to change without notice. Compaq makes no representations that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
Achtung! Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist. Avertissement! Cet appareil est un appareil de Classe A. Dans un environnement résidentiel cet appareil peut provoquer des brouillages radioélectriques. Dans ce cas, il peut être demandé à l’ utilisateur de prendre les mesures appropriées.
Contents Revision Record About This Guide Audience ...........................................................................................................................................................xi Document Structure .........................................................................................................................................xi Conventions....................................................................................................................................
StorageWorks Secure Path for Windows NT 4 Installing Secure Path Software 4.1 Summary .............................................................................................................................................4–1 4.2 Installing the Secure Path Software ..................................................................................................4–1 4.2.1 Description of the Secure Path Software ...................................................................................4–1 4.
Contents Appendix A Quick Setup RA7000 or ESA10000 (SCSI) and One Windows NT Server.................................................................A–2 RA7000 or ESA10000 (SCSI) and a Windows NT Cluster with SCSI Y-Cables..................................A–5 RA7000 or ESA10000 (SCSI) and a Windows NT Cluster with SCSI Hubs.........................................A–8 RA8000 or ESA12000 (Fibre Channel) and One Windows NT Server................................................
Revision Record This Revision Record provides a concise publication history of this manual. It lists the manual revision levels, release dates, and reasons for the revisions. The following revision history lists all revisions of this publication and their effective dates. The publication part number is included in the Revision Level column, with the last entry denoting the latest revision. Revision Level Date Summary of Changes EK–WNTMP–MH. A01 June 1998 Original release. Secure Path Software V1.
About This Guide This section defines the scope, structure and conventions of this guide. It identifies associated reference documentation, and the StorageWorks sales, service, and technical support contacts worldwide. Audience This guide is intended for administrators and system integrators of Intel or Alpha based host servers and StorageWorks RAID storage solutions.
StorageWorks Secure Path for Windows NT Chapter 5: Installing Secure Path Hardware This chapter provides the procedures for preparing the host bus adapters, and interconnecting Secure Path hardware components. Chapter 6: Using Secure Path Manager This chapter describes features of the Secure Path Manager. The Secure Path storage environment can be monitored and managed using the Secure Path Manager.
About This Guide Conventions In this guide, references to RAID, Array, subsystem, HSZ70, RA7000, ESA10000; HSG80, RA8000 or ESA12000 pertain to either of the following: • UltraSCSI Raid Array 7000 or Enterprise Storage Array (ESA) 10000 • Fibre Channel Raid Array 8000 or Enterprise Storage Array (ESA) 12000 This guide uses the following documentation conventions: Style Conventions Style Meaning boldface monospace type italic type plain monospace type To be input by the user.
1 Theory of Operation This section provides an overview of StorageWorks Secure Path v2.2 for Windows NT. 1.1 An Overview of Secure Path for Windows NT StorageWorks Secure Path is a high availability software product providing continuous data access for Ultra SCSI RAID Array 7000 / Enterprise Storage Array 10000 and Fibre Channel RAID Array 8000 / Enterprise Storage Array 12000 storage subsystems configured on Windows NT 4.0 Intel or Alpha platforms.
StorageWorks Secure Path for Windows NT 1.2 Secure Path Technology Key to Secure Path’s functionality is the capability of dual StorageWorks RAID controllers to operate in an active/active implementation referred to as dual-redundant multiple-bus mode. Multiple-bus mode allows each controller to be configured on its own bus and to process I/O independently under normal operation. Available storage units are preferred to one or the other of the two controllers by setting a PREFERRED_PATH unit attribute.
Chapter 1. Theory of Operation Secure Path also incorporates the custom Windows NT class driver, HszDisk, developed for use with StorageWorks RAID Array controllers. This class driver provides unique error handling features and performance enhancements not available in the native Windows NT disk class driver. Multiple-bus management is implemented using Secure Path Manager.
StorageWorks Secure Path for Windows NT Figure 1–1 Secure Path Single Host Configuration Figure 1–2 Secure Path Microsoft Cluster Configuration Network Interconnect WNT Server HBA HBA Clients RAID Subsystem WNT Server HBA HBA Controller A Controller B SHR-1274-99EPS 1-4 123995-002 EK-WNTMP-MH.
Chapter 1. Theory of Operation 1.5 The Secure Path Software for Microsoft Windows NT The Secure Path (v2.2) Software Kit for Microsoft Windows NT is comprised of the following software components: • HszDisk.sys is a Windows NT class driver that works with StorageWorks RAID Array controllers to enhance on-line storage availability and fault-tolerance. HszDisk works in single-host and cluster environments to maintain optimum subsystem performance during controller and storageset error recovery operations.
2 Choosing an Installation Method This chapter describes the two methods, available in this guide, to install and configure Secure Path for Windows NT. 2.1 Quick Setup Method Experienced system integrators and administrators may want to use the simplified installation instructions that are included in Appendix A, Quick Setup, to quickly establish a Secure Path environment. 2.
3 Pre-Installation Steps This section addresses the preparation needed before installing and configuring the Secure Path components. 3.1 Summary The procedures described in this guide require that you have already installed your storage subsystem in a single host/single path configuration or a dual host cluster/single path configuration.
StorageWorks Secure Path for Windows NT Table 3–1 Secure Path Prerequisites (cont) Additional Items Interconnect Hardware RAID Hardware Service Tools Technical Documentation Requirement As required Cables supplied with host RAID Array Platform kit Appropriate tools to service your equipment The reference guides for your RAID subsystem, the host server and the Windows NT software supplement this installation guide.
Chapter 3. Pre-Installation Steps 3. For SCSI Raid Array 7000 or ESA 10000 with Windows NT Clusters and SCSI Hubs QTY. 4. PART NO. DESCRIPTION 1 QB-669AA-SA Secure Path for Windows, version 2.2 2 AHA2944UW UltraSCSI Host Adapter 1 DS-DWZZH-03 UltraSCSI 3-port Hub 1 SWXKT-EA UltraSCSI Hub Cluster RAID Connection Kit For Fibre Channel Raid Array 8000 or ESA 12000 with One Windows NT Server QTY. 5. PART NO. DESCRIPTION 1 QB-669AA-SA Secure Path for Windows, version 2.
StorageWorks Secure Path for Windows NT 3.4 Examine the Current Configuration The next step is to ensure that the existing single path configuration conforms to Secure Path requirements. The requirements are as follows: Existing storage infrastructure must be robust – a) Verify that there is a serial connection to the storage subsystem and that you can communicate to it via SWCC or the CLI.
Chapter 3. Pre-Installation Steps 3.5.1 Preparing an Existing RAID Array for Secure Path Operation If you have an existing RAID Array that is currently being used in a production environment and plan to reconfigure for Secure Path operation, you should perform the following steps before proceeding to Chapter 4: 1. Follow normal procedures to backup the data stored on all drives configured on the RAID Array. 2. Check that your RAID Array subsystem does not make use of controller-based partitioning.
4 Installing Secure Path Software This chapter describes the software configuration procedures required to establish Secure Path operation to a RAID Subsystem. 4.
StorageWorks Secure Path for Windows NT 4.2.2 Installing the Secure Path Driver and Agent The following section describes how to install the Secure Path drivers and configuration management agent on the host server. 1. Insert the StorageWorks Secure Path Software (v2.2) for WNT distribution CD in your CD-ROM driver. 2. If you have CD AUTORUN enabled on your server, the Secure Path setup program will start automatically.
Installing Secure Path Software 4.3 Establishing a Serial Link to the RAID Subsystem While StorageWorks Command Console (SWCC) may be used to define and configure storagesets on the subsystem, it cannot be used to establish a Secure Path environment. Thus, the Command Line Interface (CLI) must be used to configure the controllers for multiple-bus mode operation. Controller status may be obtained through use of the SWCC CLI Window or a terminal emulation program via serial connection.
StorageWorks Secure Path for Windows NT HS*** > set nofailover The “other” controller will shutdown and must be manually restarted by momentarily depressing the reset button on the controller’s front panel. Wait for 2 minutes for the controller to boot before proceeding. HS*** > set multibus copy=this The controllers will restart in multiple-bus mode.
5 Installing Secure Path Hardware This chapter provides the procedures for installing and terminating a second individual I/O path between a StorageWorks RAID subsystem and an NT host server or a Microsoft Cluster Server, where currently a single I/O path exists. WARNING! Follow normal procedures to power off your server prior to cabling. 5.1 Summary Configuring Secure Path hardware components consists of three main tasks to be performed in sequence, as described in the following sections. 5.2 1.
StorageWorks Secure Path for Windows NT 5.2.1 Setting Up SCSI Host Adapters NOTE You must assure that the connection between host adapters on both servers is consistent. Use the PCI slot numbering on your servers as a guide. The adapters on each server that connect to one controller should be in the same PCI slot in each server. If it is not possible to install the adapters in the same slot in each server, you must install them in sequence.
Chapter 5. Installing Secure Path Hardware 5.3.1 Installing an RA7000 or ESA10000 (SCSI) and One Windows NT Server To establish two individual SCSI busses between a single Windows NT host server and a RAID subsystem, where one bus exists, reference Figure 5-1 and follow these steps: 1. Install the host adapter in the server. 2. Remove the link cable connecting both HSZ70 RAID controllers in the subsystem. 3.
StorageWorks Secure Path for Windows NT 5.3.2 Installing an RA7000 or ESA10000 (SCSI) and a Windows NT Cluster with Y-Cables. To establish two individual SCSI busses between clustered Windows NT host servers and a RAID subsystem, where one bus exists, reference Figure 5-2 and follow these steps: 1. Install the Host Bus Adapter in the servers. 2. Remove the link cable interconnecting both HSZ70 RAID controllers in the storage subsystem. 3.
Chapter 5. Installing Secure Path Hardware 5.3.3 Installing an RA7000 or ESA10000 (SCSI) and a Windows NT Cluster with SCSI Hubs. To establish two individual SCSI busses between clustered Windows NT host servers and a RAID subsystem, where one bus currently exists, reference Figure 5-3 and follow these steps: 1. Install the host adapter in the servers. 2. Remove the link cable interconnecting both HSZ70 RAID controllers in the storage subsystem. 3.
StorageWorks Secure Path for Windows NT 5.3.4 Installing an RA8000 or ESA12000 (Fibre Channel) and One Windows NT Server To establish two individual Fibre Channel busses between a single Windows NT host server and a RAID subsystem, where one bus currently exists, reference Figure 5-4 and follow these steps: 1. Install the host adapter in the server. 2. Connect the second hub to the second host adapter and to the second controller. NOTE You must use only one set of ports in the controller pair. 3.
Chapter 5. Installing Secure Path Hardware 5.3.5 Installing an RA8000 or ESA12000 (Fibre Channel) and a Windows NT Cluster To establish two individual Fibre Channel loops between clustered Windows NT host servers and a RAID subsystem, where one bus currently exists, reference Figure 5-5 and follow these steps: 1. Install the host adapters in the servers 2. Connect the second hub to the second host adapter in each server and to the second controller.
6 Using StorageWorks Secure Path Manager This chapter describes how to use StorageWorks Secure Path Manager to monitor and manage a StorageWorks Secure Path for Windows NT environment. 6.1 About StorageWorks Secure Path Manager (SPM) NOTE This chapter assumes that RAID Array storagesets have already been configured using SWCC or CLI and that the drives have been partitioned and formatted with Windows NT Disk Administrator.
StorageWorks Secure Path for Windows NT Figure 6–1 Invoking Secure Path Manager 6.2 Secure Path Manager Login and Agent Connection When Secure Path Manager starts it will prompt for login and password information (Figure 6-2). Enter the name of the Secure Path configured host (server) you wish to manage in single host environments, along with the corresponding password. For Microsoft Cluster Server (MSCS) environments, enter the names of each cluster host along with the password.
Chapter 6. Using Secure Path Manager Each instance of Secure Path Manager is capable of managing one single host configuration with multiple storage subsystems or a dual-host MSCS cluster with multiple subsystems. In order to manage multiple single host or MSCS configurations, additional instances of the Secure Path Manager are required, one for each single host or pair of clustered hosts.
StorageWorks Secure Path for Windows NT 6.3 Host Connection Status Monitor As shown in Figure 6-4, Secure Path Manager will display, immediately below the tool bar, an icon representing a connection to each active Secure Path host. If a connection is lost to a host, an "X" will appear over that host’s icon. Secure Path Manager periodically attempts to reconnect to selected hosts and will remove the "X" if the connection state is re-established.
Chapter 6. Using Secure Path Manager 6.4 Path and Drive Status Monitor The Secure Path Manager screen appears as shown in Figure 6 -6. The two paths (Controller A and Controller B) are displayed green by the Manager when both paths (host adapters, cabling and controllers), are functioning normally. The Manager keeps track of the primary path (bus assignment) for each disk in the RAID subsystem.
StorageWorks Secure Path for Windows NT The port/bus/target/lun information refers to the physical identity of the drive’s corresponding storageset (unit) as designated by the RAID Array subsystem. The disk # refers to the number assigned to a drive by Windows NT’s Disk Administrator and the drive letter, appearing above the drive icon, is assigned to that partition (if one exists). If a drive has more than one partition they will appear above the drive as well.
Chapter 6. Using Secure Path Manager 6.6 Balancing the I/O Load Between Paths As the storage demands of your Secure Path environment are defined and individual drive throughput requirements are understood, it is recommended that the disks generating the highest I/O loads be evenly balanced between the two paths to maximize overall throughput. The Manager may be used to statically load balance your Secure Path configuration by following the procedure noted below. 1.
StorageWorks Secure Path for Windows NT 6.8 Automatic Failover When a path fails, (Secure Path software detects the loss of drive I/O due to adapter, cable or controller malfunction), the Secure Path software will: • Perform an automatic failover and move the effected drive/s to the alternate path. • Log failover event/s in the Windows NT system Event Log. • Report the path failure via a Secure Path Manager pop-up message. • Reflect the drive/s reassignment to the failover path on the display.
Chapter 6. Using Secure Path Manager Figure 6–6 Automatic Disk Failover from Failed Path Controller A Colors for Figure 6-6: • The failed path (Controller A) turns red, (or yellow if inactive disk/s remains on it). • The failed-over disks appear green on their alternate path (Controller B). NOTES For a quick reference of the disk colors and their meaning, select Legend from the “VIEW” pull-down menu. The three possible drive states are identified and displayed in color.
StorageWorks Secure Path for Windows NT 6.9 Automatic Failback Auto-failback monitors a failed path and will automatically return failed-over storage units to their original path, once the path has been restored. With auto-failback enabled, Secure Path will attempt to failback a unit only twice within one hour. After two attempts, Secure Path will cancel further failback attempts to prevent repeatedly switching the storage unit(s) between paths.
Chapter 6. Using Secure Path Manager 6.10 Manual Failback and Status Reporting Once a failed path is restored, the disks that had been failed-over to an alternate path may be failed-back manually, one at a time. Manual failback can be used as an alternative to the auto-failback feature, enabling the administrator to fully validate the integrity of the restored path before returning the storagesets. The manual failback feature may also be used when the auto-failback feature is enabled.
StorageWorks Secure Path for Windows NT 6.11 Notification when No-Single-Point-of-Failure is Compromised When a server is booted, Secure Path software interrogates each managed device for its preferred path information, as well as expecting to discover redundant paths for each device. In some situations, broken or malfunctioning hardware at boot time may prevent the operation of one of the paths to one or more StorageWorks RAID Arrays.
Chapter 6. Using Secure Path Manager 6.11.1 No Preferred Path Detectable upon Server Boot If, during server boot operations, Secure Path is unable to detect the preferred path to one or more devices due to component failure ( i.e., a broken SCSI adapter), it indicates this condition through the use of a special warning icon. The warning icon, (a yellow circle containing the letter “M” crossed out with a red line), shown in Figure 6-8, overlays the normal icon of each device known to be affected.
StorageWorks Secure Path for Windows NT 6.11.2 No Redundant Path Detectable upon Server Boot If, during server boot, Secure Path finds a StorageWorks RAID Array that has devices which are accessible through their preferred path, but for which a redundant path cannot be detected, it will place an Information icon next to the “Subsystem” identifier at the top of the window.
Chapter 6. Using Secure Path Manager 6.12 Adding New Storagesets with Secure Path To add new storagesets to a Secure Path configuration, proceed as follows: 1. Use StorageWorks Command Console (SWCC) or CLI to create a new storageset/s on the RAID Array. 2. Use CLI to assign a preferred path to the new unit, as described in Section 4.4.2. 3. Use appropriate procedures to add a new volume to the NT server or cluster. 4.
A Quick Setup This section provides simplified installation instructions to enable experienced system integrators and administrators to quickly establish a Secure Path environment. For a more comprehensive installation method, please reference the roadmap provided in Chapter 2 of this guide.
StorageWorks Secure Path for Windows NT Quick Setup Guide for RA7000 or ESA10000 (SCSI) and One Windows NT Server NOTE Do not install Secure Path for Windows in an Alpha server which has FX!32 installed. STEP 1: Inventory Additional Components Needed Qty Part Number Description 1 QB-669AA-SA Secure Path for Windows (version 2.
Appendix A. Quick Setup STEP 4: Prepare the RAID Subsystem After the server has shutdown, perform the following actions: Action Serial Line (CLI) steps Set the controllers to multibus failover mode ✔ HS***> set nofailover The “other” controller will shutdown and must be manually restarted by momentarily depressing the reset button on the controller’s front panel .
StorageWorks Secure Path for Windows NT STEP 6: Confirm Installation ✔ Action Reboot the server Check event log for proper SCSI operation Launch Secure Path Manager A–4 123995–002 EK–WNTMP–MH.
Appendix A. Quick Setup Quick Setup Guide for RA7000 or ESA10000 (SCSI) and a Windows NT Cluster with SCSI Y-Cables NOTE Do not install Secure Path for Windows in an Alpha server which has FX!32 installed.
StorageWorks Secure Path for Windows NT STEP 4: Prepare the RAID Subsystem After the server has shutdown, perform the following actions: Action ✔ Serial Line (CLI) steps Set the controllers to multibus failover mode HS***> set nofailover The “other” controller will shutdown and must be manually restarted by momentarily depressing the reset button on the controller’s front panel .
Appendix A. Quick Setup STEP 6: Confirm Installation ✔ Action Reboot the servers Check event log for proper SCSI operation Launch Secure Path Manager EK–WNTMP–MH.
StorageWorks Secure Path for Windows NT Quick Setup Guide for RA7000 or ESA10000 (SCSI) and a Windows NT Cluster with SCSI Hubs NOTE Do not install Secure Path for Windows in an Alpha server which has FX!32 installed.
Appendix A. Quick Setup STEP 4: Prepare the RAID Subsystem After the server has shutdown, perform the following actions: Action Serial Line (CLI) steps Set the controllers to multibus failover mode ✔ HS***> set nofailover The “other” controller will shutdown and must be manually restarted by momentarily depressing the reset button on the controller’s front panel .
StorageWorks Secure Path for Windows NT STEP 6: Confirm Installation ✔ Action Reboot the servers Check event log for proper SCSI operation Launch Secure Path Manager A–10 123995–002 EK–WNTMP–MH.
Appendix A. Quick Setup Quick Setup Guide for RA8000 or ESA12000 (Fibre Channel) and One Windows NT Server NOTE Do not install Secure Path for Windows in an Alpha server which has FX!32 installed.
StorageWorks Secure Path for Windows NT STEP 4: Prepare the RAID Subsystem After the server has shutdown, perform the following actions: Action ✔ Serial Line (CLI) steps Set the controllers to multibus failover mode HS***> set nofailover The “other” controller will shutdown and must be manually restarted by momentarily depressing the reset button on the controller’s front panel .
Appendix A. Quick Setup Quick Setup Guide for RA8000 or ESA12000 (Fibre Channel) and a Windows NT Cluster NOTE Do not install Secure Path for Windows in an Alpha server which has FX!32 installed.
StorageWorks Secure Path for Windows NT STEP 4: Prepare the RAID Subsystem After the server has shutdown, perform the following actions: Action ✔ Serial Line (CLI) steps Set the controllers to multibus failover mode HS***> set nofailover The “other” controller will shutdown and must be manually restarted by momentarily depressing the reset button on the controller’s front panel .
B De-Installing Secure Path Software This appendix describes how to remove StorageWorks Secure Path software from your server as required to resume a single path RAID storage environment. B.1 How to De-Install StorageWorks Secure Path Software To remove Secure Path software from your system, perform the following steps: 1. Establish a serial connection to the storage subsystem (as described in Chapter 4). 2. Issue the de-installation commands (in bold text) below.
C Troubleshooting Secure Path Connection Problems This appendix describes general network configuration issues which might affect the ability of the Secure Path Client and Agent to establish connection. C.1 Client/Agent Considerations • Add each client’s NetBIOS name or Fully Qualified Domain Name (FQDN) to the agent’s list of authorized clients using the Agent Configuration utility, and set the password in the password dialog box.
StorageWorks Secure Path for Windows NT C.2 Network Considerations C–2 • Client names up to 15 letters without a dot (".") can be resolved by NetBIOS broadcast resolution as long as the client and agent nodes are configured on the same subnet. If the client and agent are located on different subnets then you must use either the LMHOSTs file, HOSTs file, WINS , or DNS to resolve the address.