Installation and Configuration Guide HP StorageWorks HSG80 ACS Solution Software V8.8 for Windows NT, Windows 2000, and Windows Server 2003 (32-bit) Product Version: 8.8-1 First Edition (March 2005) Part Number: AA-RV1XA-TE This guide provides installation and configuration instructions and reference material for operation of the HSG80 ACS Solution Software V8.8-1 for Windows NT, Windows 2000, and Windows Server 2003 (32-bit).
© Copyright 2000-2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
contents About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Determining the Address of the CCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/Disabling CCL in SCSI-3 Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Numbers of Connections . . .
Contents Partition Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Partitioning Storagesets and Disk Drives . . . . . . . . . . . . . . . . . . . . . Changing Characteristics Through Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Switches . . . . . . . . . . . . . . . .
Contents Installing StorageWorks Command Console Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Launching Command Console Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Establishing a Serial Connection to the HSG80 Storage Window . . . . . . . . . . . . . . . . 114 Controller Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Creating Your First Virtual Disk . . . . . . . . . . . . .
Contents Installation and Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Network Connection for the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Installing the Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading the Host Kit Software From the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Setting Time and Verifying All Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plugging in the FC Cable and Verify Connections . . . . . . . . . . . . . . . . . . . . . . . . . Repeating Procedure for Each Host Adapter Connection . . . . . . . . . . . . . . . . . . . . Verifying Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents A Subsystem Profile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Storage Map Template 1 for the BA370 Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Storage Map Template 2 for the Second BA370 Enclosure. . . . . . . . . . . . . . . . . . . . . . . . .
Contents Two-Cluster Fibre Channel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster Fibre Channel Switch Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Fibre Channel Switch Configuration Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Installing Software for a Fibre Channel Cluster . . . . . . . . . . . .
Contents Installing and Configuring Cluster Software on Both Host Servers . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Device Driver Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the Windows Registry Device Driver Parameters . . . . . . . . . . . . . . . . . . . . Verifying Connectivity to the Fibre Channel Arbitrated Loop . . . . . . . .
Contents 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 12 Five-member RAIDset using parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Striped mirrorset (example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Striped mirrorset (example 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 65 66 67 68 Driver Letter Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All the Drive Letters Reassigned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Driver Initialization Event Log Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying FC-AL Connectivity RAID Array Subsystem. . . . . . . . . . . . . . . . . . . . . . . .
Contents 14 HSG80 ACS Solution Software V8.
about this guide About this Guide This Installation Guide describes how to install and configure the HSG80 ACS Solution Software Version 8.8-1 for Windows NT, Windows 2000, and Windows Server 2003 (32-bit).
About this Guide Overview This section covers the following topics: Intended Audience, page 16 Related Documentation, page 16 Intended Audience This book is intended for use by system administrators and system technicians who have a basic experience with storage and networking. Related Documentation In addition to this guide, corresponding information can be found in: 16 ■ ACS V8.
About this Guide ■ HP StorageWorks HSG80 ACS Solution Software Release Notes (platform-specific) ■ HP StorageWorks Enterprise/Modular Storage RAID Array Fibre Channel Arbitrated Loop Configurations for Windows, Tru64, and Sun Solaris Application Note (AA-RS1ZB-TE) - Solution software host support includes the following platforms: — IBM AIX — HP-UX — Linux (Red Hat x86/Alpha, SuSE x86/Alpha, Caldera x86) — Novell NetWare — Open VMS — Sun Solaris — Tru64 UNIX — Windows NT/2000/Windows Server 2003 (32-bit)
About this Guide Chapter Content Summary Table 1 below summarizes the content of the chapters. Table 1: Summary of Chapter Contents Chapters Description 1. Planning a Subsystem This chapter focuses on technical terms and knowledge needed to plan and implement storage array subsystems. 2. Planning Storage Configurations Plan the storage configuration of your subsystem, using individual disk drives (JBOD), storageset types (mirrorsets, stripesets, and so on), and/or partitioned drives.
About this Guide Table 1: Summary of Chapter Contents (Continued) Chapters Description Appendix A. Subsystem Profile Templates This appendix contains storageset profiles to copy and use to create your system profiles. It also contains an enclosure template to use to help keep track of the location of devices and storagesets in your shelves. Four (4) templates will be needed for the subsystem. Appendix B.
About this Guide Conventions Conventions consist of the following: ■ Document conventions ■ Symbols in Text ■ Symbols on Equipment Document conventions This document follows the conventions in Table 2.
About this Guide Note: Text set off in this manner presents commentary, sidelights, or interesting points of information. Symbols on Equipment Any enclosed surface or area of the equipment marked with these symbols indicates the presence of electrical shock hazards. Enclosed area contains no operator serviceable parts. WARNING: To reduce the risk of injury from electrical shock hazards, do not open this enclosure. Any RJ-45 receptacle marked with these symbols indicates a network interface connection.
About this Guide Any product or assembly marked with these symbols indicates that the component exceeds the recommended weight for one individual to handle safely. WARNING: To reduce the risk of personal injury or damage to the equipment, observe local occupational health and safety requirements and guidelines for manually handling material. Rack Stability WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that: • • • • • 22 The leveling jacks are extended to the floor.
About this Guide Getting Help If you still have a question after reading this guide, contact an HP authorized service provider or access our web site. Technical Support Telephone numbers for worldwide technical support are listed on the following HP web site: http://www.hp.com/support/. From this web site, select the country of origin. Note: For continuous quality improvement, calls may be recorded or monitored. Outside North America, call technical support at the nearest location.
About this Guide HP Authorized Reseller For the name of your nearest authorized reseller: ■ In the United States, call 1-800-345-1518 ■ In Canada, call 1-800-263-5868 ■ Elsewhere, see the Storage web site for locations and telephone numbers Configuration Flowchart A three-part flowchart (Figure 1, Figure 2, and Figure 3) is shown on the following pages. Refer to these charts while installing and configuring a new storage subsystem.
About this Guide Unpack subsystem See the unpacking instructions on shipping box Plan a Subsystem Chapter 1 Plan Storage Configurations Chapter 2 Prepare Host System Chapter 3 Make Local Connection page 156 Controller pair Single controller Cable the Controller page 158 Cable the Controllers page 164 Configure the Controller page 158 Configure the Controllers page 165 Installing SWCC ? No Yes B See Figure 3 on page 27 See Figure 2 on page 26 A Figure 1: General configuration flowchart (pane
About this Guide A Configure devices page 171 Create Storagesets and Partitions: Stripeset, page 171 Mirrorset, page 173 RAIDset, page 173 Striped Mirrorset, page 174 Single (JBOD) Disk, page 175 Continue creating units until you have completed your planned configuration. Partition, page 175 Assign Unit Numbers page 177 Select Configuration Options page 178 Verify Storage Setup page 182 Figure 2: General configuration flowchart (panel 2) 26 HSG80 ACS Solution Software V8.
About this Guide B Install Agent Chapter 4 Install Client Appendix B Create Storage See SWCC online help Verify Storage Set Up Figure 3: SWCC storage configuration flowchart (panel 3) HSG80 ACS Solution Software V8.
About this Guide 28 HSG80 ACS Solution Software V8.
Planning a Subsystem 1 This chapter provides information that helps you plan how to configure the storage array subsystem. This chapter focuses on the technical terms and knowledge needed to plan and implement storage subsystems. Note: This chapter frequently references the command line interface (CLI). For the complete syntax and descriptions of the CLI commands, see the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide.
Planning a Subsystem Defining Subsystems This section describes the terms this controller and other controller. It also presents graphics of the Model 2200 and BA370 enclosures. Note: The HSG80 controller uses the BA370 or Model 2200 enclosure. Controller Designations A and B The terms A, B, “this controller,” and “other controller,” respectively are used to distinguish one controller from another in a two-controller (also called dual-redundant) subsystem.
Planning a Subsystem BA370 Enclosure 1 2 3 4 5 2 1 3 4 5 6 6 EMU PVA Controller A Controller B Cache module A Cache module B CXO6283B Figure 5: Location of controllers and cache modules in a BA370 enclosure Controller Designations “This Controller” and “Other Controller” Some CLI commands use the terms “this” and “other” to identify one controller or the other in a dual-redundant pair. These designations are a shortened form of “this controller” and “other controller.
Planning a Subsystem Model 2200 Enclosure 1 2 CXO7366A 1 This controller 2 Other controller Figure 6: “This controller” and “other controller” for the Model 2200 enclosure BA370 Enclosure 1 2 CXO6468D 1 Other controller 2 This controller Figure 7: “This controller” and “other controller” for the BA370 enclosure 32 HSG80 ACS Solution Software V8.
Planning a Subsystem What is Failover Mode? Failover is a way to keep the storage array available to the host if one of the controllers becomes unresponsive. A controller can become unresponsive because of a controller hardware failure or, in multiple-bus mode only, due to a failure of the link between host and controller or host-bus adapter. Failover keeps the storage array available to the hosts by allowing the surviving controller to take over total control of the subsystem.
Planning a Subsystem At any time, host port 1 is active on only one controller, and host port 2 is active on only one controller. The other ports are in standby mode. In normal operation, both host port 1 on controller A and host port 2 on controller B are active. A representative configuration is shown in Figure 8. The active and standby ports share port identity, enabling the standby port to take over for the active one.
Planning a Subsystem Host 1 Host 2 Switch or hub Switch or hub Host port 1 active D0 Host 3 D1 Host port 1 standby Host port 2 standby Controller A D100 Controller B D101 D120 Host port 2 active CXO7036A Figure 8: Transparent failover—normal operation HSG80 ACS Solution Software V8.
Planning a Subsystem Host 1 Host 2 Switch or hub Switch or hub Host port 1 active D0 Host 3 D1 Host port 1 not available Host port 2 active Controller A D100 Controller B not available D101 D120 Host port 2 not available CXO7035A Figure 9: Transparent failover—after failover from controller B to controller A Multiple-Bus Failover Mode Multiple-bus failover mode has the following characteristics: ■ Host controls the failover process by moving the units from one controller to another ■ A
Planning a Subsystem In multiple-bus failover mode, you can specify which units are normally serviced by a specific controller of a controller pair. Units can be preferred to one controller or the other by the PREFERRED_PATH switch of the ADD UNIT (or SET unit) command. For example, use the following command to prefer unit D101 to “this controller”: SET D101 PREFERRED_PATH=THIS_CONTROLLER Note: This is an initial preference, which can be overridden by the hosts.
Planning a Subsystem Host 1 "RED" Host 2 "GREY" Host 3 "BLUE" FCA1 FCA2 FCA1 FCA2 FCA1 FCA2 Switch or hub Switch or hub Host port 1 active D0 Host port 2 active Controller A D1 D2 D100 D101 D120 All units visible to all ports Host port 1 active Controller B Host port 2 active NOTE: FCA = Fibre Channel Adapter CXO7094B Figure 10: Typical multiple-bus configuration 38 HSG80 ACS Solution Software V8.
Planning a Subsystem Selecting a Cache Mode The cache module supports read, read-ahead, write-through, and write-back caching techniques. The cache technique is selected separately for each unit. For example, you can enable only read and write-through caching for some units while enabling only write-back caching for other units. Read Caching When the controller receives a read request from the host, it reads the data from the disk drives, delivers it to the host, and stores the data in its cache module.
Planning a Subsystem operation is complete. This process is called write-through caching because the data actually passes through—and is stored in—the cache memory on its way to the disk drives. Enabling Mirrored Caching In mirrored caching, half of each controller’s cache mirrors the companion controller’s cache, as shown in Figure 11. The total memory available for cached data is reduced by half, but the level of protection is greater.
Planning a Subsystem What is the Command Console LUN? StorageWorks Command Console (SWCC) software communicates with the HSG80 controllers through an existing storage unit, or logical unit number (LUN). The dedicated LUN that SWCC uses is called the Command Console LUN (CCL). The CCL serves as the communication device for the HS-Series Agent and identifies itself to the host by a unique identification string. By default, a CCL device is enabled within the HSG80 controller on host port 1.
Planning a Subsystem Determining Connections The term “connection” applies to every path between a Fibre Channel adapter in a host computer and an active host port on a controller. Note: In ACS Version 8.8-1, the maximum number of supported connections is 96. Naming Connections It is highly recommended that you assign names to connections that have meaning in the context of your particular configuration. Note: Some non-alpha /numeric characters may not work with some hosts.
Planning a Subsystem Numbers of Connections The number of connections resulting from cabling one adapter into a switch or hub depends on failover mode and how many links the configuration has: ■ If a controller pair is in transparent failover mode and the port 1 link is separate from the port 2 link (that is, ports 1 of both controllers are on one loop or fabric, and port 2 of both controllers are on another), each adapter will have one connection, as shown in Figure 12.
Planning a Subsystem Host 1 "AQUA" Host 2 "BLACK" Host 3 "BROWN" FCA1 FCA1 FCA1 Switch or hub Switch or hub Connection AQUA1A1 Host port 1 active Host port 2 standby Controller A Connection BLACK1B2 Connection BROWN1B2 D0 D1 Host port 1 standby D100 Controller B D101 D120 Host port 2 active NOTE: FCA = Fibre Channel Adapter CXO7081B Figure 12: Connections in separate-link, transparent failover mode configurations 44 HSG80 ACS Solution Software V8.
Planning a Subsystem Host 1 "GREEN" Host 2 "ORANGE" Host 3 "PURPLE" FCA1 FCA1 FCA1 Switch or hub Connections GREEN1A1 ORANGE1A1 PURPLE1A1 Host port 1 active D0 Host port 2 standby Controller A D1 Host port 1 standby Connections GREEN1B2 ORANGE1B2 PURPLE1B2 D100 Controller B D101 D120 Host port 2 active NOTE: FCA = Fibre Channel Adapter CXO7079B Figure 13: Connections in single-link, transparent failover mode configurations HSG80 ACS Solution Software V8.
Planning a Subsystem Host 1 "VIOLET" FCA1 FCA2 Switch or hub Connection VIOLET1B1 Switch or hub Connection VIOLET1A1 Connection VIOLET2A2 Host port 1 active D0 Host port 2 active Controller A D1 D2 D100 Connection VIOLET2B2 D101 D120 All units visible to all ports Host port 1 active Controller B Host port 2 active NOTE: FCA = Fibre Channel Adapter CXO7080B Figure 14: Connections in multiple-bus failover mode 46 HSG80 ACS Solution Software V8.
Planning a Subsystem Assigning Unit Numbers The controller keeps track of the unit with the unit number. The unit number can be from 0−199 prefixed by a D, which stands for disk drive. A unit can be presented as different LUNs to different connections.
Planning a Subsystem If no value is specified for offset, then connections on port 1 have a default offset of 0 and connections on port 2 have a default offset of 100. For example, if all host connections use the default offset values, unit D2 will be presented to a port 1 host connection as LUN 2 (unit number of 2 minus offset of 0). Unit D102 will be presented to a port 2 host connection as LUN 2 (unit number of D102 minus offset of 100).
Planning a Subsystem An additional factor to consider when assigning unit numbers and offsets is SCSI version. If the SCSI_VERSION switch of the SET THIS_CONTROLLER/OTHER_CONTROLLER command is set to SCSI-3, the CCL is presented as LUN 0 to every connection, superseding any unit assignments. The interaction between SCSI version and unit numbers is explained further in the next section. In addition, the access path to the host connection must be enabled for the connection to access the unit.
Planning a Subsystem The PREFERRED_PATH switch of the ADD UNIT (or SET unit) command determines which controller of a dual-redundant pair initially accesses the unit. Initially, PREFERRED_PATH determines which controller presents the unit as Ready. The other controller presents the unit as Not Ready. Hosts can issue a SCSI Start Unit command to move the unit from one controller to the other.
Planning a Subsystem If SCSI_VERSION is set to SCSI-2 mode, the CCL floats, moving to the first available LUN location, depending on the configuration. StorageWorks recommends to use the following conventions when assigning host connection offsets and unit numbers in SCSI-2 mode: ■ Offsets should be divisible by 10 (for consistency and simplicity). ■ Unit numbers should be assigned at connection offsets (so that every host connection has a unit presented at LUN 0).
Planning a Subsystem The command syntax to disable is: HSG> SET this/other Default_Access=Disable The command syntax to enable is: HSG> SET this/other Default_Access=Enable {default after upgrade} When the command is invoked from one controller, the Default_Access from the other controller will be similarly modified. The setting is symmetrical and persistent across restarts, FRUTIL, etc.
Planning a Subsystem Host 1 "AQUA" Host 2 "BLACK" Host 3 "BROWN" FCA1 FCA1 FCA1 Switch or hub Switch or hub Connection AQUA1A1 Host port 1 active Host port 2 standby Controller A Connection BLACK1B2 Connection BROWN1B2 D0 D1 Host port 1 standby D100 Controller B D101 D120 Host port 2 active FCA = Fibre Channel Adapter CXO7081B Figure 16: Limiting host access in transparent failover mode Restricting Host Access by Disabling Access Paths If more than one host is on a link (that is, atta
Planning a Subsystem For example: In Figure 17, restricting the access of unit D101 to host 3, the host named BROWN can be done by enabling only the connection to host 3. Enter the following commands: SET D101 DISABLE_ACCESS_PATH=ALL SET D101 ENABLE_ACCESS_PATH=BROWN1B2 If the storage subsystem has more than one host connection, carefully specify the access path to avoid providing undesired host connections access to the unit.
Planning a Subsystem Note: StorageWorks recommends that you provide access to only specific connections, even if there is just one connection on the link. This way, if new connections are added, they will not have automatic access to all units. Restricting Host Access in Multiple-Bus Failover Mode In multiple-bus mode, the units assigned to any port are visible to all ports.
Planning a Subsystem Host 1 "RED" Host 2 "GREY" Host 3 "BLUE" FCA1 FCA2 FCA1 FCA2 FCA1 FCA2 Switch or hub Connections RED1B1 GREY1B1 BLUE1B1 Switch or hub Connections RED1A1 GREY1A1 BLUE1A1 Connections RED2A2 GREY2A2 BLUE2A2 Host port 1 active Host port 2 active Controller A D0 D1 D2 D100 Connections RED2B2 GREY2B2 BLUE2B2 D101 D120 All units visible to all ports Host port 1 active Controller B Host port 2 active NOTE: FCA = Fibre Channel Adapter CXO7078B Figure 17: Limiting host acc
Planning a Subsystem multiple-bus failover to work. For most operating systems, it is desirable to have all connections to the host enabled.
Planning a Subsystem For example: In Figure 17, assume all host connections initially have the default offset of 0. Giving all connections access to host BLUE, an offset of 120 will present unit D120 to host BLUE as LUN 0. Enter the following commands: SET BLUE1A1 UNIT_OFFSET=120 SET BLUE1B1 UNIT_OFFSET=120 SET BLUE2A2 UNIT_OFFSET=120 SET BLUE2B2 UNIT_OFFSET=120 Host BLUE cannot see units lower than its offset, so it cannot access any other units.
Planning a Subsystem In multiple-bus failover mode, each of the host ports has its own port ID: ■ Controller B, port 1—worldwide name + 1, for example 5000-1FE1-FF0C-EE01 ■ Controller B, port 2—worldwide name + 2, for example 5000-1FE1-FF0C-EE02 ■ Controller A, port 1—worldwide name + 3, for example 5000-1FE1-FF0C-EE03 ■ Controller A, port 2—worldwide name + 4, for example 5000-1FE1-FF0C-EE04 Use the CLI command, SHOW THIS_CONTROLLER/OTHER_CONTROLLER to display the subsystem’s worldwide name.
Planning a Subsystem 1 2 Node ID (Worldwide name) Checksum 1 WWN INFORMATION P/N: WWN: S/N: NNNN – NNNN – NNNN – NNNN Checksum: NN 2 CXO6873B Figure 19: Placement of the worldwide name label on the BA370 enclosure Caution: Each subsystem has its own unique worldwide name (node ID). If you attempt to set the subsystem worldwide name to a name other than the one that came with the subsystem, the data on the subsystem will not be accessible.
Planning Storage Configurations 2 This chapter provides information to help you plan the storage configuration of your subsystem. Storage containers are individual disk drives (JBOD), storageset types (mirrorsets, stripesets, and so on), and/or partitioned drives. Use the guidelines found in this section to plan the various types of storage containers needed.
Planning Storage Configurations Where to Start The following procedure outlines the steps to follow when planning your storage configuration. See Appendix A to locate the blank templates for keeping track of the containers being configured. 1. Determine your storage requirements. Use the questions in “Determining Storage Requirements” on page 63, to help you. 2. Review configuration rules. See “Configuration Rules for the Controller” on page 63. 3.
Planning Storage Configurations — Use SWCC. See the SWCC documentation for details. — Use the Command Line Interpreter (CLI) commands. This method allows you flexibility in defining and naming your storage containers. See the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide. Determining Storage Requirements It is important to determine your storage requirements.
Planning Storage Configurations Note: For the previous two storageset configurations, this is a combined maximum, limited to no more than 20 RAID 3/5 storagesets in the individual combination.
Planning Storage Configurations D100 RAID1 Disk 10000 Disk 20000 Host addressable unit number Storageset name Disk 30000 Controller PTL addresses CXO6186B Figure 20: Mapping a unit to physical disk drives The HSG80 controller identifies devices based on a Port-Target-LUN (PTL) numbering scheme, shown in Figure 21. The physical location of a device in its enclosure determines its PTL. ■ P—Designates the controller's SCSI device port number (1 through 6).
Planning Storage Configurations The controller can either operate with a BA370 enclosure or with a Model 2200 controller enclosure combined with Model 4214R, Model 4254, Model 4310R, Model 4350R, Model 4314R, or Model 4354R disk enclosures. The controller operates with BA370 enclosures that are assigned ID numbers 0, 2, and 3. These ID numbers are set through the PVA module. Enclosure ID number 1, which assigns devices to targets 4 through 7, is not supported.
Planning Storage Configurations Examples - Model 2200 Storage Maps, PTL Addressing The Model 2200 controller enclosure can be combined with the following: ■ Model 4214R disk enclosure — Ultra2 SCSI with 14 drive bays, single-bus I/O module. ■ Model 4254 disk enclosure — Ultra2 SCSI with 14 drive bays, dual-bus I/O module. Note: The Model 4214R uses the same storage maps as the Model 4314R, and the Model 4254 uses the same storage maps as the Model 4354R disk enclosures.
Planning Storage Configurations ■ Model 4354R disk enclosure — Ultra3 SCSI with 14 drive bays, dual-bus I/O module. Table 7 shows the addresses for each device in a three-shelf, dual-bus configuration. A maximum of three Model 4354R disk enclosures can be used with each Model 2200 controller enclosure. Note: Appendix A contains storageset profiles you can copy and use to create your own system profiles.
Planning Storage Configurations Table 4: PTL addressing, single-bus configuration, six Model 4320R enclosures Model 4310R Disk Enclosure Shelf 6 (Single-Bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID Disk61200 9 Disk61100 8 Disk61000 7 Disk60800 6 Disk60500 5 Disk60400 4 Disk60300 3 Disk60200 2 Disk60100 1 Disk60000 Bay Model 4310R Disk Enclosure Shelf 5 (Single-Bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID Disk51200 9 Disk51100 8 Disk51000
Planning Storage Configurations Table 4: PTL addressing, single-bus configuration, six Model 4320R enclosures (Continued) Model 4310R Disk Enclosure Shelf 1 (Single-Bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID Disk11200 9 Disk11100 8 Disk11000 7 Disk10800 6 Disk10500 5 Disk10400 4 Disk10300 3 Disk10200 2 Disk10100 1 Disk10000 Bay Model 4310R Disk Enclosure Shelf 2 (Single-Bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID Disk21200 9 Disk21100 8
Planning Storage Configurations Table 5: PTL addressing, dual-bus configuration, three Model 4350R enclosures Model 4350R Disk Enclosure Shelf 1 (Single-Bus) SCSCSI Bus ASI Bus A SCSI Bus B 10 SCSI ID 00 01 02 03 04 00 01 02 03 04 DISK ID Disk20400 9 Disk20300 8 Disk20200 7 Disk20100 6 Disk20000 5 Disk10400 4 Disk10300 3 Disk10200 2 Disk10100 1 Disk10000 Bay Model 4350R Disk Enclosure Shelf 2 (Single-Bus) SCSCSI Bus ASI Bus A SCSI Bus B 10 SCSI ID 00 01 02 03 04 00
Planning Storage Configurations Table 6: PTL addressing, single-bus configuration, six Model 4314R enclosures Model 4314R Disk Enclosure Shelf 6 (Single-Bus) 14 SCSI ID 00 01 02 03 04 05 08 09 10 11 12 13 14 15 DISK ID Disk61500 13 Disk61400 12 Disk61300 11 Disk61200 10 Disk61100 9 Disk61000 8 Disk60900 7 Disk60800 6 Disk60500 5 Disk60400 4 Disk60300 3 Disk60200 2 Disk60100 1 Disk60000 Bay Model 4314R Disk Enclosure Shelf 5 (Single-Bus) 14 SCSI ID 00 01 02
Planning Storage Configurations Table 6: PTL addressing, single-bus configuration, six Model 4314R enclosures (Continued) Model 4314R Disk Enclosure Shelf 2 (Single-Bus) 14 SCSI ID 00 01 02 03 04 05 08 09 10 11 12 13 14 15 DISK ID Disk21500 13 Disk21400 12 Disk21300 11 Disk21200 10 Disk21100 9 Disk21000 8 Disk20900 7 Disk20800 6 Disk20500 5 Disk20400 4 Disk20300 3 Disk20200 2 Disk20100 1 Disk20000 Bay Model 4314R Disk Enclosure Shelf 3 (Single-Bus) 14 SCSI ID
Planning Storage Configurations Disk40800 Disk40500 Disk40400 Disk40300 Disk40200 Disk40100 Disk40000 Disk30800 Disk30500 Disk30400 Disk30300 Disk30200 Disk30100 DISK ID Disk30000 Table 7: PTL addressing, dual-bus configuration, three Model 4354A enclosures (Continued) Model 4354R Disk Enclosure Shelf 3 (Dual-Bus) 14 SCSI ID 00 01 02 03 04 05 08 00 01 02 03 04 05 08 DISK ID Disk60800 13 Disk60500 12 Disk60400 11 Disk60300 10 Disk60200 9 Disk60100 8 Disk60000 7
Planning Storage Configurations Containers Partition Single devices (JBOD) Stripeset (R0) Mirrorset (R1) Striped mirrorset (R0+1) RAIDset (R3/5) Storagesets CXO6677A Figure 23: Storage container types HSG80 ACS Solution Software V8.
Planning Storage Configurations Table 8 compares the different kinds of containers to help you determine which ones satisfy your requirements.
Planning Storage Configurations Creating a Storageset Profile Creating a profile for your storagesets, partitions, and devices can simplify the configuration process. Filling out a storageset profile helps you choose the storagesets that best suit your needs and to make informed decisions about the switches you can enable for each storageset or storage device that you configure in your subsystem. For an example of a storageset profile, see Table 9.
Planning Storage Configurations Initialize Switches: Chunk size _X_ Automatic (default) Save Configuration ___No (default) Metadata _X_Destroy (default) ___ 64 blocks _X_Yes ___Retain ___ 128 blocks ___ 256 blocks Unit Switches: Caching Access by following hosts enabled Read caching_______X__ Read-ahead caching_____ Write-back caching___X__ Write-through caching____ _ALL_____________________________________________ ____________ _________________________________________________ ___________ ______
Planning Storage Configurations For example, in a three-member stripeset that contains disk drives Disk 10000, Disk 20000, and Disk 10100, the first chunk of an I/O request is written to Disk 10000, the second to Disk 20000, the third to Disk 10100, the fourth to Disk 10000, until all of the data has been written to the drives (Figure 24).
Planning Storage Configurations Virtual disk Operating system view Actual device mappings Block 0 Block 1 Block 2 Block 3 Block 4 Block 5 etc. Disk 1 Disk 2 Disk 3 Block 0 Block 3 etc. Block 1 Block 4 etc. Block 2 Block 5 etc. Stripeset CXO4592B Figure 25: Three-member RAID 0 stripeset (example 2) Keep the following points in mind as you plan your stripesets: ■ Reporting methods and size limitations prevent certain operating systems from working with large stripesets.
Planning Storage Configurations For this reason, you should avoid using a stripeset to store critical data. Stripesets are more suitable for storing data that can be reproduced easily or whose loss does not prevent the system from supporting its critical mission. ■ Evenly distribute the members across the device ports to balance the load and provide multiple paths. ■ Stripesets may contain between two and 24 members.
Planning Storage Configurations Mirrorset Planning Considerations Mirrorsets (RAID 1) use redundancy to ensure availability, as illustrated in Figure 26. For each primary disk drive, there is at least one mirror disk drive. Thus, if a primary disk drive fails, its mirror drive immediately provides an exact copy of the data. Figure 27 shows a second example of a Mirrorset.
Planning Storage Configurations Keep these points in mind when planning mirrorsets ■ Data availability with a mirrorset is excellent but comes with a higher cost—you need twice as many disk drives to satisfy a given capacity requirement. If availability is your top priority, consider using dual-redundant controllers and redundant power supplies. ■ You can configure up to a maximum of 20 RAID 3/5 mirrorsets per controller or pair of dual-redundant controllers. Each mirrorset may contain up to 6 members.
Planning Storage Configurations Virtual disk Operating system view Disk 1 Block 0 Block 5 Block 10 Block 15 Block 0 Block 1 Block 2 Block 3 Block 4 Block 5 etc.
Planning Storage Configurations ■ A RAIDset must include at least 3 disk drives, but no more than 14. ■ A storageset should only contain disk drives of the same capacity. The controller limits the capacity of each member to the capacity of the smallest member in the storageset. Thus, if you combine 9 GB disk drives with 4 GB disk drives in the same storageset, you waste 5 GB of capacity on each 9 GB member.
Planning Storage Configurations p t Mirrorset1 Mirrorset2 Disk 20000 Disk 10100 Disk 20200 A B C Disk 10000 Disk 20100 Disk 10200 B' C' A' Mirrorset3 CXO7289A Figure 29: Striped mirrorset (example 1) The failure of a single disk drive has no effect on the ability of the storageset to deliver data to the host. Under normal circumstances, a single disk drive failure has very little effect on performance.
Planning Storage Configurations Plan the mirrorset members, and plan the stripeset that will contain them. Review the recommendations in “Planning Considerations for Storageset” on page 78, and “Mirrorset Planning Considerations” on page 82. Storageset Expansion Considerations Storageset Expansion allows for the joining of two of the same kind of storage containers by concatenating RAIDsets, stripesets, or individual disks, thereby forming a larger virtual disk, which is presented as a single unit.
Planning Storage Configurations unpartitioned storageset or device. Partitions are separately addressable storage units; therefore, you can partition a single storageset to service more than one user group or application. Defining a Partition Partitions are expressed as a percentage of the storageset or single disk unit that contains them: ■ Mirrorsets and single disk units—the controller allocates the largest whole number of blocks that are equal to or less than the percentage you specify.
Planning Storage Configurations Changing Characteristics Through Switches CLI command switches allow the user another level of command options. There are three types of switches that modify the storageset and unit characteristics: ■ Storageset switches ■ Initialization switches ■ Unit switches The following sections describe how to enable/modify switches. They also contain a description of the major CLI command switches.
Planning Storage Configurations Specifying Storageset and Partition Switches The characteristics of a particular storageset can be set by specifying switches when the storageset is added to the controllers’ configuration. Once a storageset has been added, the switches can be changed by using a SET command. Switches can be set for partitions and the following types of storagesets: ■ RAIDset ■ Mirrorset Stripesets have no specific switches associated with their ADD and SET commands.
Planning Storage Configurations Partition Switches The following switches are available when creating a partition: ■ Size ■ Geometry For details on the use of these switches, refer to CREATE_PARTITION command in the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide. Specifying Initialization Switches Initialization switches set characteristics for established storagesets before they are made into units.
Planning Storage Configurations ■ CHUNKSIZE=DEFAULT lets the controller set the chunk size based on the number of disk drives (d) in a stripeset or RAIDset. If number of drives is less or equal to 9, then chunk size = 256. If the number of drives is greater than 9, then chunk size = 128. ■ CHUNKSIZE=n lets you specify a chunk size in blocks. The relationship between chunk size and request size determines whether striping increases the request rate or the data-transfer rate.
Planning Storage Configurations ■ Many parallel I/Os that use a small area of disk should use a chunk size of 10 times the average transfer request rate. ■ Random I/Os that are scattered over all the areas of the disks should use a chunk size of 20 times the average transfer request rate. If you do not know, then you should use a chunk size of 15 times the average transfer request rate.
Planning Storage Configurations Note: DO NOT use SAVE_CONFIGURATION in dual redundant controller installations. It is not supported and may result in unexpected controller behavior. Note: HP recommends that you do not use SAVE_CONFIGURATION on every unit and device on the controller. Destroy/Nodestroy Specify whether to destroy or retain the user data and metadata when a disk is initialized after it has been used in a mirrorset or as a single-disk unit.
Planning Storage Configurations ■ SECTORS_PER_TRACK—the number of sectors per track used. The range is from 1 to 255. Specifying Unit Switches Several switches control the characteristics of units. The unit switches are described under the SET unit-number command in the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide.
Planning Storage Configurations 2. Note the position of all the drives contained within D104. 3. Enter the following command to turn off the flashing LEDs: LOCATE CANCEL The following procedure is an example command to locate all the drives that make up RAIDset R1: 1. Enter the following command: LOCATE R1 2. Note the position of all the drives contained within R1. 3. Enter the following command to turn off the flashing LEDs: LOCATE CANCEL 96 HSG80 ACS Solution Software V8.
Planning Storage Configurations Example Storage Map—Model 4310R Disk Enclosure Table 11 shows an example of four Model 4310R disk enclosures (single-bus I/O).
Planning Storage Configurations Table 11: Model 4310 disk enclosure, example of storage map (Continued) Model 4310R Disk Enclosure Shelf 2 (Single-Bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 D100 R1 D101 S1 M1 D102 M3 D104 S2 D106 R2 D108 S3 D1 S4 M5 D2 R3 D3 S5 D4 M7 DISK ID Disk21200 9 Disk21100 8 Disk21000 7 Disk20800 6 Disk20500 5 Disk20400 4 Disk20300 3 Disk20200 2 Disk20100 1 Disk20000 Bay Model 4310R Disk Enclosure Shelf 3 (Single-Bus) 10 SCSI ID 00 01
Planning Storage Configurations ■ Unit D103 is a 2-member mirrorset named M4. M4 consists of Disk30200 and Disk40200. ■ Unit D104 is 3-member stripeset named S2. S2 consists of Disk10300, Disk20300, and Disk30300. ■ Unit D105 is a single (JBOD) disk named Disk40300. ■ Unit D106 is a 3-member RAID 3/5 storageset named R2. R2 consists of Disk10400, Disk20400, and Disk30400. ■ Unit D107 is a single (JBOD) disk named Disk40400. ■ Unit D108 is a 4-member stripeset named S3.
Planning Storage Configurations 100 HSG80 ACS Solution Software V8.
Preparing the Host System 3 3 This chapter describes how to prepare your Windows NT/Windows 2000/Windows Server 2003 (32-bit) host computer to accommodate the HSG80 controller storage subsystem.
Preparing the Host System Installing RAID Array Storage System WARNING: A shock hazard exists at the backplane when the controller enclosure bays or cache module bays are empty. Be sure the enclosures are empty, then mount the enclosures into the rack. DO NOT use the disk enclosure handles to lift the enclosure. The handles cannot support the weight of the enclosure. Only use these handles to position the enclosure in the mounting brackets.
Preparing the Host System 3. Install the elements. Install the disk drives. Make sure you install blank panels in any unused bays. Fibre Channel cabling information is shown to illustrate supported configurations. In a dual-bus disk enclosure configuration, disk enclosures 1, 2, and 3 are stacked below the controller enclosure—two SCSI Buses per enclosure (see Figure 33).
Preparing the Host System 1 8 2 3 4 5 7 6 CXO7383A 1 3 5 7 SCSI Bus 1 Cable SCSI Bus 3 Cable SCSI Bus 5 Cable AC Power Inputs 2 4 6 8 SCSI Bus 2 Cable SCSI Bus 4 Cable SCSI Bus 6 Cable Fibre Channel Ports Figure 33: Dual-Bus Enterprise Storage RAID Array Storage System 104 HSG80 ACS Solution Software V8.
Preparing the Host System 6 5 4 8 1 7 2 3 CXO7382A 1 3 5 7 SCSI Bus 1 Cable SCSI Bus 3 Cable SCSI Bus 5 Cable AC Power Inputs 2 4 6 8 SCSI Bus 2 Cable SCSI Bus 4 Cable SCSI Bus 6 Cable Fibre Channel Ports Figure 34: Single-Bus Enterprise Storage RAID Array Storage System HSG80 ACS Solution Software V8.
Preparing the Host System Making a Physical Connection To attach a host computer to the storage subsystem, install one or more host bus adapters into the computer. A Fibre Channel (FC) cable goes from the host bus adapter to an FC switch. Preparing to Install Host Bus Adapter Before installing the host bus adapter: 1. Perform a complete backup of the entire system. 2. Shut down the computer system or perform a hot addition of the adapter based upon directions for that server.
Preparing the Host System In order for Windows NT/Windows 2000/Windows Server 2003 (32-bit) to recognize new Enterprise Storage RAID Array Fibre Channel subsystem devices or changes to existing configurations, you must restart your system. Initial Setup Settings Windows NT/Windows 2000/Windows Server 2003 (32-bit) Settings Your new storage system components must be initially configured using a serial cable connection to the HSG80 array controllers.
Preparing the Host System Your choice will depend on how you later intend to use your storage system. In certain heterogeneous environments, you may be required to use SCSI-3 protocols (for example, if sharing your storage system with an OpenVMS-based server). You may choose to use SCSI-2 protocol if you are sharing your storage system with a server that requires SCSI-2 protocols. In this case, whether or not CCL is required may become an issue.
Preparing the Host System Installing RAID Windows NT, Windows 2000, and Windows Server 2003 (32-bit) Device Drivers The Fibre Channel Software and RAID Windows NT (HszDisk.sys) or Windows 2000 (HsxDisk.sys) Device Driver software is installed on your host server from the RAID Array Software Solution CD-ROM. After you insert the CD-ROM, the program should start automatically. Note: If the program does not start after inserting the CD-ROM, go to the CD-ROM drive directory and click launch.
Preparing the Host System Hsz/HsxDisk Driver Note: HsxDisk refers to the Windows 2000 device driver. HszDisk refers to the Windows NT device driver. The Hsz/HsxDisk driver works with the Hsz/HSG-family of RAID controllers to enhance the Windows 2000/Windows NT online storage availability and fault-tolerance.
Preparing the Host System RAID Array Fibre Channel system. These registry settings are required for single host and Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster configurations. Fibre Channel Switch The Fibre Channel Setup Utility makes all the driver changes to support fabric topology automatically. Fibre Channel Hub The default setting is to use soft addressing. If you desire a hard ALPA, use lputilnt.exe to assign an ALPA based on the table below.
Preparing the Host System Installing SWCC Client and Creating Your First Virtual Disk This section contains instructions for installing StorageWorks Command Console (SWCC), configuring the HSG80 array controller for Windows NT, Windows 2000 and Windows Server 2003 (32-bit) operation, and creating your first virtual disk. Note: For more information, use the online HELP in the SWCC Storage and CLI Windows.
Preparing the Host System Other Communication Methods After initial set up, you will be able to connect and communicate with your Enterprise Storage RAID Array Fibre Channel system over a network or the SCSI bus. ■ SCSI Bus Connection. A local connection method allows you to connect to your Enterprise Storage RAID Array Fibre Channel system over the SCSI bus. ■ Network Connection. You can communicate with your Enterprise Storage RAID Array Fibre Channel system over a TCP/IP network.
Preparing the Host System ■ CLI Window: HS-series controllers provide a feature called the Command Line Interpreter (CLI) for configuring and monitoring your storage controllers using text-based commands. With the CLI, you can connect a maintenance terminal directly to your controller and manage it using the complete set of CLI commands. You can also use a host-based, virtual terminal, such as Command Console's CLI Window, to make the connection. ■ StorageWorks Command Console HSG80 ACS V8.
Preparing the Host System 4. Select StorageWorks CC HSG80 ACS V8.5 or newer. 5. When the Connection Selection dialog box displays, click Serial, then click OK to display the Connect Serial dialog box. 6. On the Connect Serial dialog box perform the following actions: a. From the drop-down menu, select the PC COM port your HSG80 controller is connected to. b. Select the baud rate (controller default is 9600). c. Click Connect to display the Storage Window. You are now connected to your storage subsystem.
Preparing the Host System Note: After you change a parameter that causes a controller restart, there is approximately a 90-second delay while the controller reinitializes. 1. Access the controller's property sheets by double-clicking the controllers' icon in the Storage Window. When you double-click a controller's icon the General controller properties sheet displays. The controller has five property sheets. Each sheet is accessed by clicking on its tab. 2.
Preparing the Host System CLI window. First close the Storage Window, and establish a CLI connection. To invoke a CLI Window from the Command Console Client's Start menu, select Command Console, then the CLI Window option. The Connection Selection Window appears. Select Serial. At the next window select 9600 baud rate and click Connect to invoke the CLI window. Enter the following command to disable the Communication LUN: set this_controller nocommand_console_lun Close the CLI Window.
Preparing the Host System Start the Wizard To start the Command Console Virtual Disk Wizard perform the following actions: 1. Establish a serial connection to your Enterprise Storage RAID Array Fibre Channel Subsystem. 2. Access the subsystem's Storage Window. 3. Select Add Virtual Disk from the Storage menu. Create the Virtual Disk 1. Click the radio button of the RAID level you want, then click Next. 2. Select the devices you want to include in the virtual disk from a list of available storage devices.
Preparing the Host System Verifying/Installing Required Versions Note: HsxDisk refers to the Windows 2000 device driver. HszDisk refers to the Windows NT device driver. Windows Server 2003 does not require this driver. Before you run Disk Administrator or Disk Management, verify that Hsz/HsxDisk recognizes the volumes that you created in the Fibre Channel as follows: 1. Open the Event Viewer in the Administrative Tools group. 2. Look for an entry for Hsz/HsxDisk in the Event Viewer window.
Preparing the Host System Completing a New RAID Array Configuration This section summarizes how to use the Windows NT Disk Administrator, Windows 2000 and Windows Server 2003 (32-bit) Disk Management to complete a new subsystem configuration. For additional information, refer to your Windows NT/Windows 2000/Windows Server 2003 documentation. Note: Before you begin, remember to back up your system using normal back up procedures. .
Preparing the Host System — Verify that the capacity shown matches the size of the physical disk or subsystem. If it does not match, recheck the logical configuration for the Enterprise Storage RAID Array Fibre Channel system and its members. Note: Disk Administrator and Disk Management displays the “usable” capacity of a RAIDset and MIRRORset, not the combined total of the physical members.
Preparing the Host System Creating Partitions in Windows NT Using the Disk Administrator Note: To create format and assign drive letters to partitions from your Windows NT desktop perform the following procedures. See the CREATE_PARTITION command in the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide for a description of the partition switches.
Preparing the Host System Making Drive Letters Permanent The process of creating partitions assigns a logical name (letter “C”, “D”, and so forth) to each partition. These letter assignments, under Windows NT will normally “float”. As an option, you can make the drive letters permanent. To make the letter assignments permanent, starting from the Disk Administrator perform the following actions: 1. Access the Tools pull-down menu. 2. Select Drive Letter then choose To Assign.
Preparing the Host System Removing Disk Partitions Note: Before making changes, back up your system. When making changes to an existing RAID Array configuration, any existing disk partitions to be changed (or removed) must first be deleted using Windows NT Disk Administrator or Windows 2000/Server 2003 Disk Management. After they have been deleted, you may use the CLI to create new Storagesets. 1. From Disk Administrator or Disk Management, click the partition you wish to delete. 2.
Preparing the Host System Note: Solely for the purpose of performing upgrades to the ACS firmware, this Solution Software Kit supports previous ACS V8.6 and V8.7. Do not mix ACS versions in the same SAN. Refer to the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Maintenance and Service Guide and the Solution Software Release Notes for the latest information on upgrades. Note: If updating ACS firmware, complete the upgrade after all Windows server upgrades.
Preparing the Host System b. Click the Run Fibre Channel Utility link, then choose one of the Multi-Bus Fibre Channel setups, based on your configuration. c. Click the SWCC link (optional) to install SWCC components. Note: Do Not Restart the server at this time. 2. Using your Secure Path Software CD-ROM, install Secure Path 3.1A or Secure Path 4.0 in accordance with the instructions provided with that product. Then apply any Secure Path Service Pack download. 3. Restart the server. 4.
Preparing the Host System 3. Using the Add/Remove Program in Control Panel, uninstall: a. StorageWorks Command Console (SWCC) b. Large LUN Utility (if installed) Note: Do not Restart the server at this time. 4. Using your Solution Software CD-ROM, click the Solution Software v8.8 for Windows NT/2000/Server 2003 link. a. Click the Perform FCA Driver Update link to install the HBA driver. b.
Preparing the Host System 3. Using the Add/Remove Program in Control Panel, uninstall: a. StorageWorks Command Console (SWCC). b. Large LUN Utility (if installed) Note: Do not Restart the system at this time. 4. Using your Solution Software CD-ROM, click the Solution Software v8.8 for Windows NT/2000/Server 2003 link. a. Click the Perform Multi Driver Install/Update link to install the HBA driver. b.
Preparing the Host System Note: Do not Restart the server at this time. 4. Using your Secure Path Software CD-ROM, install Secure Path 3.1A or 4.0 in accordance with the instructions provided with that product. Then apply any Secure Path Service Pack download. 5. Reboot the server. 6. Using your Solution Software CD-ROM, click the Solution Software v8.8 for Windows NT/2000/Server 2003 link. a. Click the Perform FCA Driver Update link to install the HBA driver. b.
Preparing the Host System Note: Do not Restart the system at this time. 4. Using your Secure Path Software CD-ROM, install Secure Path 3.1A or 4.0 in accordance with the instructions provided with that product. Then apply the Secure Path 3.1A Service Pack 2 download. 5. Using your Solution Software CD-ROM, click the Solution Software v8.8 for Windows NT/2000/Server 2003 link. a. Click the Perform FCA Driver Update link to install the HBA driver. b.
Preparing the Host System 2. Restart the server. Updating an Existing Standalone Server Be sure you login to an account with administrator privileges. 1. Stop all applications that access storage. 2. Stop Steam Agent (SWCC) in Services. 3. Using the Add/Remove Program in Control Panel, uninstall: a. StorageWorks Command Console (SWCC) b. Large LUN Utility (if installed) Note: Do not Restart the server at this time. 4. Using your Solution Software CD-ROM, click the Solution Software v8.
Preparing the Host System Note: Keep Cluster Service running on all nodes. Stopping the Cluster Service during this procedure could result in a Cluster Service failure, and force a subsequent reinstallation. 2. Stop Steam Agent (SWCC) in Services. 3. Using the Add/Remove Program in Control Panel, uninstall: a. StorageWorks Command Console (SWCC). b. Large LUN Utility (if installed) Note: Do not Restart the system at this time. 4. Using your Solution Software CD-ROM, click the Solution Software v8.
Preparing the Host System The Silent Install can be used for: ■ Fibre Channel Software Setup for Transparent Switch ■ Fibre Channel Software Setup for Multibus Switch ■ Installing HBA drivers and/or Fibre Channel utilities. See the README files provided with the Solution Software Kit for these instructions. ■ Storageworks Command Console Client/Agent (While creating the response file for the Agent, choose Exit during the Agent Configuration of the installation.
Preparing the Host System At the Command Prompt (or from a batch file), the command should look like setup.exe -s -f1\setup.iss -f2\setup.log where the path after -f1 is to the Windows or Winnt directory and the path after -f2 is to where you want the setup.log file to be generated. To check the success of the installation, view the setup.log file. Under the “ResponseResult” section, a successful install shows ResultCode=0. If running setup.exe from the CD-ROM, the setup.
Preparing the Host System ■ The data can be saved to a text file to the location of choice. Figure 35: Component Identifier Program Figure 36: Dialog box that follows the Component Identifier Program HSG80 ACS Solution Software V8.
Preparing the Host System 136 HSG80 ACS Solution Software V8.
Installing and Configuring the HSG Agent 4 StorageWorks Command Console (SWCC) enables real-time configuration of the storage environment and permits you to monitor and configure the storage connected to the HSG80 controller.
Installing and Configuring the HSG Agent Why Use StorageWorks Command Console (SWCC)? StorageWorks Command Console (SWCC) enables you to monitor and configure the storage connected to the HSG80 controller. SWCC consists of Client and Agent. ■ The Client provides pager notification and lets you manage your virtual disks. The Client runs on Windows Server 2003 (32-bit), Windows 2000 with Service Pack 3 and 4, and Windows NT 4.0 with Service Pack 6A or above.
Installing and Configuring the HSG Agent Installation and Configuration Overview Table 13 provides an overview of the installation. Table 13: Installation and Configuration Overview Step Procedure 1. Verify that your hardware has been set up correctly. See the previous chapters in this guide. 2. Verify that you have a network connection for the Client and Agent systems.See “About the Network Connection for the Agent” on page 140. 3.
Installing and Configuring the HSG Agent About the Network Connection for the Agent The network connection, shown in Figure 37, displays the subsystem connected to a hub or a switch. SWCC can consist of any number of Clients and Agents in a network. However, it is suggested that you install only one Agent on a computer. By using a network connection, you can configure and monitor the subsystem from anywhere on the LAN. If you have a WAN or a connection to the Internet, monitor the subsystem with TCP/IP.
Installing and Configuring the HSG Agent 7 1 A T V A T -S H V T N E C O O A T V O 4 4 7 A T V A T -S H 2 V T N E C O O 5 4 3 6 CXO7240A 1 Agent system (has the Agent 5 Hub or switch software) 2 TCP/IP network 6 HSG80 controller and its device subsystem 3 Client system (has the Client 7 Servers software) 4 Fibre Channel cable Figure 37: An example of a network connection HSG80 ACS Solution Software V8.
Installing and Configuring the HSG Agent Before Installing the Agent The Agent requires the minimum system requirements, as defined in the release notes for your operating system. The program is designed to operate with the Client version 2.5 on Windows 2000, Windows NT, or Windows Server 2003 (32-bit). Verify that your system meets the minimum requirements by completing the following steps. 1. Log into an account that is a member of the administrator group.
Installing and Configuring the HSG Agent Downloading the Host Kit Software From the Web The host kit software is available for download. You can save the software to your computer or create a CD-ROM. Platform kit software is stored on the download web site based on operating system. Follow the steps below to obtain the software from the web site. 1. Go to http://h18006.www1.hp.com/products/storageworks/ma8kema12k/kits.html. 2. Select the kit for download. 3.
Installing and Configuring the HSG Agent 3. Click Next. Follow the instructions on the screen. After the computer installs the software, you are asked if you want to configure the Agent. 4. Click Continue to configure your Agent. The Windows NT Agent Configuration Step 1 of 3 window appears. 5. Enter your password in the New field, and retype it in the Verification field. The password must have 4 to 16 characters. 6. Click Next to continue. The following message appears: Password Validation Successful. 7.
Installing and Configuring the HSG Agent 9. Select one of the following for your access privileges: overall status, detailed status, and configuration. The access privilege level controls the client system's level of access to the storage subsystems.
Installing and Configuring the HSG Agent 14. Click OK. The computer asks the following: Would you like to start the Windows NT Agent service now? 15. Click Yes. The Agent starts. 16. Add this system to the Navigation Tree of each client system that you added to the Agent's list (File > Add System in the Command Console Client). Refer to the Command Console Client Help.
Installing and Configuring the HSG Agent 8. Click OK. The Welcome NT Agent Configuration Utility window appears. 9. Click Exit to quit the NT Agent Configuration Utility. 10. You must stop and restart the Agent for your changes to take effect. For instructions, see “Stopping and Starting the Agent” on page 153. Adding a Client System Entry For a client system to receive updates from the Agent, you must add the client system to the Agent’s list of client systems.
Installing and Configuring the HSG Agent The following message appears if you had previously added a subsystem: A previous storage list is detected. Would you like to scan the subsystem to update the information? (Subsystem names will revert to default settings.) If you click Yes, the software will automatically add entries for the new subsystems and restore default subsystem information for the existing entries. Or If you click No, the software will keep the current settings.
Installing and Configuring the HSG Agent Or If you click No, the software will keep the current settings. The NT Agent Configuration Step 3 of 3 window appears. 7. Click Finish. The following message appears: No subsystem information was added to the subsystem list. Subsystem list will not be created or modified. 8. Click OK. The Welcome NT Agent Configuration Utility window appears. 9. Click Exit to quit the NT Agent Configuration Utility. 10.
Installing and Configuring the HSG Agent 6. Click Finish. The following message appears: No subsystem information was added to the subsystem list. Subsystem list will not be created or modified. 7. Click OK. The Welcome NT Agent Configuration Utility window appears. 8. Click Exit to quit the NT Agent Configuration Utility. 9. You must stop and restart the Agent for your changes to take effect. For instructions, see “Stopping and Starting the Agent” on page 153.
Installing and Configuring the HSG Agent 5. Enter the name of the subsystem in the Selected Subsystem field. Enter the communication drive letter and monitoring interval in seconds. The monitoring interval is the rate at which the Agent queries the specified subsystem for status. A reasonable monitoring interval in seconds would be 120. When you select Subsystem Enabled, the subsystem is included in the Agent’s scans. When Subsystem Enabled is selected, the software configures the storage.
Installing and Configuring the HSG Agent 5. Select the subsystem that you want to modify in the Subsystems field. You may change the communication drive letter, the monitoring interval, and the subsystem’s name. The monitoring interval is the rate at which the Agent queries the specified subsystem for status. A reasonable monitoring interval in seconds would be 120. When you select Subsystem Enabled, the subsystem is included in the Agent’s scans.
Installing and Configuring the HSG Agent The NT Agent Configuration Step 3 of 3 window appears. 5. Select the subsystem that you want to delete in the Storage Subsystems field. Click Delete Subsystem. 6. Click Finish. A message, warning you to restart your Agent, appears. 7. Click OK. You exit the NT Agent Configuration Utility. 8. You must stop and restart the Agent for your changes to take effect. For instructions, see “Stopping and Starting the Agent” on page 153.
Installing and Configuring the HSG Agent Note: If you want to enable the Agent to start at system boot, change the startup type to automatic. From Windows NT 1. Double click Services in Control Panel. 2. Double click Steam. The Service window appears. Select Manual under Startup Type, and click OK. From Windows 2000 and Windows Server 2003 (32-bit) 1. Click Start > Settings > Control Panel > Administrative Tools > Component Services. 2. Under Console Root, select Services (Local). 3.
FC Configuration Procedures 5 This chapter describes procedures to configure a subsystem that uses Fibre Channel (FC) fabric topology. In fabric topology, the controller connects to its hosts through switches.
FC Configuration Procedures Establishing a Local Connection A local connection is required to configure the controller until a command console LUN (CCL) is established using the CLI. Communication with the controller can be through the CLI or SWCC. The maintenance port, shown in Figure 38, provides a way to connect a maintenance terminal. The maintenance port can be an EIA-423 compatible terminal or a computer running a terminal emulator program. The maintenance port accepts a standard RS-232 (RJ45) jack.
FC Configuration Procedures Setting Up a Single Controller Powering On and Establishing Communication 1. Connect the computer or terminal to the controller, as shown in Figure 38. The connection to the computer is through the COM1 or COM2 port. 2. Turn on the computer or terminal. 3. Apply power to the storage subsystem. 4. Verify that the computer or terminal is configured as follows: — 9600 baud — 8 data bits — 1 stop bit — no parity — no flow control 5. Press Enter.
FC Configuration Procedures 4 1 2 5 3 5 4 CXO6881B 1 Controller 4 Cable from the switch to the host Fibre Channel 2 Host port 1 adapter 3 Host port 2 5 FC switch Figure 39: Single controller cabling Configuring a Single Controller Using CLI To configure a single controller using CLI involves the following processes: ■ Verifying the Node ID and Checking for Any Previous Connections. ■ Configuring Controller Settings. ■ Restart the Controller. ■ Setting Time and Verifying all Commands.
FC Configuration Procedures The node ID is located in the third line of the SHOW THIS result: HSG80> SHOW THIS Controller: HSG80 ZG80900583 Software V8.8, Hardware E11 NODE_ID = 5000-1FE1-0001-3F00 ALLOCATION_CLASS = 0 If the node ID is present, go to step 5. If the node ID is all zeroes, enter node ID and checksum, which are located on a sticker on the controller enclosure.
FC Configuration Procedures Note: If SCSI-2 is selected, you must disable CCL using the command: SET THIS NOCOMMAND_CONSOLE_LUN 6. Set the topology for the controller. If both ports are used, set topology for both ports: SET THIS PORT_1_TOPOLOGY=FABRIC SET THIS PORT_2_TOPOLOGY=FABRIC If the controller is not factory-new, it may have another topology set, in which case these commands will result in an error message.
FC Configuration Procedures 2. Use the FRUTIL utility to set up the battery discharge timer. Enter the following command to start FRUTIL: RUN FRUTIL When FRUTIL asks if you intend to replace the battery, answer “Y”: Do you intend to replace this controller's cache battery? Y/N [N] Y FRUTIL will print out a procedure, but will not give you a prompt. Ignore the procedure and press the Enter key. 3. Set up any additional optional controller settings, such as changing the CLI prompt.
FC Configuration Procedures The following sample is a result of a SHOW THIS command, with the areas of interest in bold. Controller: HSG80 ZG94214134 Software V8.
FC Configuration Procedures 5. Turn on the switches, if not done previously. If you want to communicate with the Fibre Channel switches through Telnet, set an IP address for each switch. See the manuals that came with the switches for details. Plugging in the FC Cable and Verify Connections 6. Plug the Fibre Channel cable from the first host bus adapter into the switch. Enter the SHOW CONNECTIONS command to view the connection table: SHOW CONNECTIONS 7.
FC Configuration Procedures Setting Up a Controller Pair Powering Up and Establishing Communication 1. Connect the computer or terminal to the controller as shown in Figure 38. The connection to the computer is through the COM1 or COM2 ports. 2. Turn on the computer or terminal. 3. Apply power to the storage subsystem. 4. Configure the computer or terminal as follows: — 9600 baud — 8 data bits — 1 stop bit — no parity — no flow control 5. Press Enter.
FC Configuration Procedures Figure 40 shows a controller pair with failover cabling showing one HBA per server with HSG80 controller in transparent failover mode. 5 6 1 3 4 2 6 5 CXO6887B 1 Controller A 4 Host port 2 2 Controller B 5 Cable from the switch to the host FC adapter 3 Host port 1 6 FC switch Figure 40: Controller pair failover cabling Configuring a Controller Pair Using CLI To configure a controller pair using CLI: ■ Configuring Controller Settings. ■ Restarting the Controller.
FC Configuration Procedures The node ID is located in the third line of the SHOW THIS result: HSG80> show this Controller: HSG80 ZG80900583 Software V8.8, Hardware E11 NODE_ID = 5000-1FE1-0001-3F00 ALLOCATION_CLASS = 0 If the node ID is present, go to step 5. If the node ID is all zeroes, enter the node ID and checksum, which are located on a sticker on the controller enclosure.
FC Configuration Procedures 10. Assign an identifier for the communication LUN (also called the command console LUN, or CCL). The CCL must have a unique identifier that is a decimal number in the range 1 to 32767, and which is different from the identifiers of all units. Use the following syntax: SET THIS IDENTIFIER=N Identifier must be unique among all the controllers attached to the fabric within the specified allocation class. 11. Set the topology for the controller.
FC Configuration Procedures When FRUTIL asks if you intend to replace the battery, answer “Y”: Do you intend to replace this controller's cache battery? Y/N [N] Y FRUTIL will print out a procedure, but will not give you a prompt. Ignore the procedure and press Enter. 16. Set up any additional optional controller settings, such as changing the CLI prompt.
FC Configuration Procedures 18. Verify node ID, allocation class, SCSI version, failover mode, identifier, and port topology. The following display is a sample result of a SHOW THIS command, with the areas of interest in bold. Controller: HSG80 ZG94214134 Software V8.
FC Configuration Procedures 19. Turn on the switches if not done previously. If you want to communicate with the FC switches through Telnet, set an IP address for each switch. See the manuals that came with the switches for details. Plugging in the FC Cable and Verify Connections 20. Plug the FC cable from the first host adapter into the switch. Enter a SHOW CONNECTIONS command to view the connection table: SHOW CONNECTIONS The first connection will have one or more entries in the connection table.
FC Configuration Procedures Verifying Installation To verify installation for your Windows NT/Windows 2000/Windows Server 2003 (32-bit) host, enter the following command: SHOW DEVICES Configuring Devices The disks on the device bus of the HSG80 can be configured manually or with the CONFIG utility. The CONFIG utility is easier. Invoke CONFIG with the following command: RUN CONFIG WARNING: It is highly recommended to use the CONFIG utility only at reduced I/O loads.
FC Configuration Procedures Containers Partition Stripeset (R0) Single devices (JBOD) Mirrorset (R1) Striped mirrorset (R0+1) RAIDset (R3/5) Storagesets CXO6677A Figure 41: Storage container types Configuring a Stripeset 1. Create the stripeset by adding its name to the controller's list of storagesets and by specifying the disk drives it contains. Use the following syntax: ADD STRIPESET STRIPESET-NAME DISKNNNNN DISKNNNNN....... 2.
FC Configuration Procedures Configuring a Mirrorset 1. Create the mirrorset by adding its name to the controller's list of storagesets and by specifying the disk drives it contains. Optionally, you can append mirrorset switch values: ADD MIRRORSET MIRRORSET-NAME DISKNNNNN DISKNNNNN SWITCHES Note: See the ADD MIRRORSET command in the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide for a description of the mirrorset switches. 2.
FC Configuration Procedures Note: See the ADD RAIDSET command in the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide for a description of the RAIDset switches. 2. Initialize the RAIDset, specifying any desired switches: INITIALIZE RAIDSET-NAME SWITCH Note: HP recommends that you allow initial reconstruct to complete before allowing I/O to the RAIDset. Not doing so may generate forced errors at the host level.
FC Configuration Procedures See “Specifying Initialization Switches” on page 91 for a description of the initialization switches. 4. Verify the striped mirrorset configuration: SHOW STRIPESET-NAME 5. Assign the stripeset mirrorset a unit number to make it accessible by the hosts. See “Assigning Unit Numbers and Unit Qualifiers” on page 177.
FC Configuration Procedures 2. Create each partition in the storageset or disk drive by indicating the partition's size. Also specify any desired switch settings: CREATE_PARTITION STORAGESET-NAME SIZE=N SWITCHES or CREATE_PARTITION DISK-NAME SIZE=N SWITCHES where N is the percentage of the disk drive or storageset that will be assigned to the partition. Enter SIZE=LARGEST, on the last partition only, to let the controller assign the largest free space available to the partition.
FC Configuration Procedures Assigning Unit Numbers and Unit Qualifiers Each storageset, partition, or single (JBOD) disk must be assigned a unit number for the host to access. As the units are added, their properties can be specified through the use of command qualifiers, which are discussed in detail under the ADD UNIT command in the HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Command Line Interface (CLI) Reference Guide.
FC Configuration Procedures Preferring Units In multiple-bus failover mode, individual units can be preferred to a specific controller. For example, to prefer unit D102 to “this controller,” use the following command: SET D102 PREFERRED_PATH=THIS RESTART commands must be issued to both controllers for this command to take effect: RESTART OTHER_CONTROLLER RESTART THIS_CONTROLLER Note: The controllers need to restart together for the preferred settings to take effect.
FC Configuration Procedures Adding Disk Drives If you add new disk drives to the subsystem, the disk drives must be added to the controllers’ list of known devices: ■ To add one new disk drive to the list of known devices, use the following syntax: ADD DISK DISKNNNNN P T L ■ To add several new disk drives to the list of known devices, enter the following command: RUN CONFIG Adding a Disk Drive to the Spareset The spareset is a collection of spare disk drives that are available to the controller should
FC Configuration Procedures 2. Delete the desired disk drive entering the following command: DELETE SPARESET DISKNNNNN The RUN CONFIG command does not delete disks from the controllers’ device table if a disk has been physically removed or replaced. In this case, you must use the command: DELETE DISKNNNNN. 3.
FC Configuration Procedures Deleting a Storageset Note: If the storageset you are deleting is partitioned, you must delete each partitioned unit before you can delete the storageset. 1. Show the storageset’s configuration: SHOW STORAGESET-NAME 2. Delete the unit number that uses the storageset. Use the following command: DELETE UNIT-NUMBER 3. Delete the storageset. Use the following command: DELETE STORAGESET-NAME 4.
FC Configuration Procedures For example, the following command changes the replacement policy for RAIDset RAID1 to BEST_FIT: SET RAID1 POLICY=BEST_FIT Changing Device Switches Use the SET device-name command to change the device switches. For example, to request a data transfer rate of 20 MHz for DISK10000: SET DISK10000 TRANSFER_RATE_REQUESTED=20MHZ Changing Initialize Switches The initialization switches cannot be changed without destroying the data on the storageset or device.
Using CLI for Configuration 6 This chapter presents an example of how to configure a storage subsystem using the Command Line Interpreter (CLI). The CLI configuration example shown assumes: ■ A normal, new controller pair, which includes: — NODE ID set — No previous failover mode — No previous topology set ■ Full array with no expansion cabinet ■ PCMCIA cards installed in both controllers A storage subsystem example is shown in Figure 42.
Using CLI for Configuration Figure 42 shows an example storage system map for the BA370 enclosure. Details on building your own map are described in Chapter 2. Templates to help you build your storage map are supplied in Appendix A.
Using CLI for Configuration Host 1 "RED" Host 2 "GREY" Host 3 "BLUE" FCA1 FCA2 FCA1 FCA2 FCA1 FCA2 Switch or hub Connections RED1B1 GREY1B1 BLUE1B1 Switch or hub Connections RED1A1 GREY1A1 BLUE1A1 Connections RED2A2 GREY2A2 BLUE2A2 Host port 1 active Host port 2 active Controller A D0 D1 D2 D101 Connections RED2B2 GREY2B2 BLUE2B2 D102 D120 All units visible to all ports Host port 1 active Controller B Host port 2 active NOTE: FCA = Fibre Channel Adapter CXO7109B Figure 43: Example, t
Using CLI for Configuration Figure 44: .
Using CLI for Configuration "RED" "GREY" "BLUE" D1 D0 D2 D101 D102 D120 CXO7110B Figure 45: Example, logical or virtual disks comprised of storagesets CLI Configuration Example Text conventions used in this example are listed below: ■ Text in italics indicates an action you take. ■ Text in THIS FORMAT, indicates a command you type. Be certain to press Enter after each command. ■ Text enclosed within a box, indicates information that is displayed by the CLI interpreter.
Using CLI for Configuration SET THIS SCSI_VERSION=SCSI-3 SET THIS PORT_1_TOPOLOGY=FABRIC SET THIS PORT_2_TOPOLOGY=FABRIC SET OTHER PORT_1_TOPOLOGY=FABRIC SET OTHER PORT_2_TOPOLOGY=FABRIC SET THIS ALLOCATION_CLASS=1 RESTART OTHER RESTART THIS SET THIS TIME=10-Mar-2001:12:30:34 RUN FRUTIL Do you intend to replace this controller's cache battery? Y/N [Y] Y Plug serial cable from maintenance terminal into bottom controller. Note: Bottom controller (B) becomes “this” controller.
Using CLI for Configuration RENAME !NEWCON00 RED1B1 SET RED1B1 OPERATING_SYSTEM=WINNT RENAME !NEWCON01 RED1A1 SET RED1A1 OPERATING_SYSTEM=WINNT SHOW CONNECTIONS Note: Connection table sorts alphabetically.
Using CLI for Configuration RENAME !NEWCON02 RED2B2 SET RED2B2 OPERATING_SYSTEM=WINNT RENAME !NEWCON02 RED2A2 SET RED2A2 OPERATING_SYSTEM=WINNT SHOW CONNECTIONS Connection Name RED1A1 Operating System WINNT Controller OTHER Port 1 Address XXXXXX Status Unit Offset OL other 0 HOST_ID=XXXX-XXXX-XXXX-XXXX ADAPTER_ID=XXXX-XXXX-XXXX-XXXX RED1B1 1 WINNT THIS XXXXXX OL this 0 HOST_ID=XXXX-XXXX-XXXX-XXXX ADAPTER_ID=XXXX-XXXX-XXXX-XXXX RED2A2 2 WINNT OTHER XXXXXX OL other 0 HOST_ID=XXXX-XX
Using CLI for Configuration (Continued) Connection Name Operating System Controller BLUE1A1 WINNT OTHER Port 1 Address Status XXXXXX OL other Unit Offset 0 HOST_ID=XXXX-XXXX-XXXX-XXXX ADAPTER_ID=XXXX-XXXX-XXXX-XXXX BLUE1B1 1 WINNT THIS XXXXXX OL this 0 HOST_ID=XXXX-XXXX-XXXX-XXXX ADAPTER_ID=XXXX-XXXX-XXXX-XXXX BLUE2A2 2 WINNT OTHER XXXXXX OL other 0 HOST_ID=XXXX-XXXX-XXXX-XXXX ADAPTER_ID=XXXX-XXXX-XXXX-XXXX BLUE2B2 2 WINNT THIS XXXXXX OL this 0 HOST_ID=XXXX-XXXX-XXXX-
Using CLI for Configuration SET CONNECTION BLUE1A1 UNIT_OFFSET=100 SET CONNECTION BLUE1B1 UNIT_OFFSET=100 SET CONNECTION BLUE2A2 UNIT_OFFSET=100 SET CONNECTION BLUE2B2 UNIT_OFFSET=100 RUN CONFIG ADD RAIDSET R1 DISK10000 DISK20000 DISK30000 DISK40000 DISK50000 DISK60000 INITIALIZE R1 ADD UNIT D102 R1 DISABLE_ACCESS_PATH=ALL SET D102 ENABLE_ACCESS_PATH=(RED1A1, RED1B1, RED2A2, RED2B2) ADD RAIDSET R2 DISK10100 DISK20100 DISK30100 DISK40100 DISK50100 DISK60100 INITIALIZE R2 ADD UNIT D120 R2 DISABLE_ACCESS_PATH
Using CLI for Configuration HSG80 ACS Solution Software V8.
Using CLI for Configuration 194 HSG80 ACS Solution Software V8.
Backing Up, Cloning, and Moving Data 7 This chapter includes the following topics: ■ Backing Up Subsystem Configurations, page 196 ■ Creating Clones for Backup, page 197 ■ Moving Storagesets, page 201 HSG80 ACS Solution Software V8.
Backing Up, Cloning, and Moving Data Backing Up Subsystem Configurations The controller stores information about the subsystem configuration in its nonvolatile memory. This information could be lost if the controller fails or when you replace a module in the subsystem. Use the following command to produce a display that shows if the save configuration feature is active and which devices are being used to store the configuration.
Backing Up, Cloning, and Moving Data Creating Clones for Backup Use the CLONE utility to duplicate the data on any unpartitioned single-disk unit, stripeset, mirrorset, or striped mirrorset in preparation for backup. When the cloning operation is complete, you can back up the clones rather than the storageset or single-disk unit, which can continue to service its I/O load. When you are cloning a mirrorset, CLONE does not need to create a temporary mirrorset.
Backing Up, Cloning, and Moving Data Unit Unit Temporary mirrorset Disk10300 Disk10300 New member Unit Temporary mirrorset Unit Copy Disk10300 Disk10300 New member Clone Unit Clone of Disk10300 CXO5510A Figure 46: CLONE utility steps for duplicating unit members Use the following steps to clone a single-disk unit, stripeset, or mirrorset: 1. Establish a connection to the controller that accesses the unit you want to clone. 2. Start CLONE using the following command: RUN CLONE 3.
Backing Up, Cloning, and Moving Data The following example shows the commands you would use to clone storage unit D6. The clone command terminates after it creates storage unit D33, a clone or copy of D6. RUN CLONE CLONE LOCAL PROGRAM INVOKED UNITS AVAILABLE FOR CLONING: 98 ENTER UNIT TO CLONE? 98 CLONE WILL CREATE A NEW UNIT WHICH IS A COPY OF UNIT 98. ENTER THE UNIT NUMBER WHICH YOU WANT ASSIGNED TO THE NEW UNIT? 99 THE NEW UNIT MAY BE ADDED USING ONE OF THE FOLLOWING METHODS: 1.
Backing Up, Cloning, and Moving Data USE AVAILABLE DEVICE DISK20300(SIZE=832317) FOR MEMBER DISK10000(SIZE=832317) (Y,N) [Y]? Y MIRROR DISK10000 C_MB SET C_MB NOPOLICY SET C_MB MEMBERS=2 SET C_MB REPLACE=DISK20300 COPY IN PROGRESS FOR EACH NEW MEMBER. PLEASE BE PATIENT...
Backing Up, Cloning, and Moving Data Moving Storagesets You can move a storageset from one subsystem to another without destroying its data. You also can follow the steps in this section to move a storageset to a new location within the same subsystem. Caution: Move only normal storagesets. Do not move storagesets that are reconstructing or reduced, or data corruption will result. See the release notes for the version of your controller software for information on which drives can be supported.
Backing Up, Cloning, and Moving Data 5. Delete each disk drive, one at a time, that the storageset contained. Use the following syntax: DELETE DISK-NAME DELETE DISK-NAME DELETE DISK-NAME 6. Remove the disk drives and move them to their new PTL locations. 7. Again add each disk drive to the controller's list of valid devices. Use the following syntax: ADD DISK DISK-NAME PTL-LOCATION ADD DISK DISK-NAME PTL-LOCATION ADD DISK DISK-NAME PTL-LOCATION 8.
Backing Up, Cloning, and Moving Data New cabinet ADD DISK DISK10000 ADD DISK DISK10100 ADD DISK DISK20000 ADD DISK DISK20100 ADD RAIDSET RAID99 DISK10000 DISK10100 DISK20000 DISK20100 ADD UNIT D100 RAID99 HSG80 ACS Solution Software V8.
Backing Up, Cloning, and Moving Data 204 HSG80 ACS Solution Software V8.
Subsystem Profile Templates A This appendix contains storageset profiles to copy and use to create your profiles. It also contains an enclosure template to use to help keep track of the location of devices and storagesets in your shelves. Four (4) templates will be needed for the subsystem. Note: The storage map templates for the Model 4310R and Model 4214R or 4314R reflect the physical location of the disk enclosures in the rack.
Subsystem Profile Templates Storageset Profile Type of Storageset: _____ Mirrorset __X_ RAIDset _____ Stripeset _____ Striped Mirrorset ____ JBOD Storageset Name Disk Drives Unit Number Partitions: Unit # Unit # Unit # Unit # Unit # Unit # Unit # Unit # RAIDset Switches: Reconstruction Policy ___Normal (default) Reduced Membership __ _No (default) Replacement Policy ___Best performance (default) ___Fast ___Yes, missing: ___Best fit ___None Mirrorset Switches: Replacement Policy Copy
Subsystem Profile Templates Unit Switches: Caching Read caching__________ Read-ahead caching_____ Write-back caching______ Write-through caching____ Access by following hosts enabled _________________________________________________ ___________ _________________________________________________ ___________ _________________________________________________ ___________ _________________________________________________ ___________ HSG80 ACS Solution Software V8.
Subsystem Profile Templates Storage Map Template 1 for the BA370 Enclosure Use this template for: ■ BA370 single-enclosure subsystems ■ first enclosure of multiple BA370 enclosure subsystems 1 2 Port 3 4 5 6 Power Supply Power Supply 3 D10300 D20300 D30300 D40300 D50300 D60300 Power Supply Power Supply 2 D20200 D30200 D40200 D50200 Targets D10200 D60200 Power Supply Power Supply 1 D10100 D20100 D30100 D40100 D50100 D60100 Power Supply Power Supply 0 D10000 208 D20000
Subsystem Profile Templates Storage Map Template 2 for the Second BA370 Enclosure Use this template for the second enclosure of multiple BA370 enclosure subsystems.
Subsystem Profile Templates Storage Map Template 3 for the TSingle-Bushird BA370 Enclosure Use this template for the third enclosure of multiple BA370 enclosure subsystems.
Subsystem Profile Templates Storage Map Template 4 for the Model 4214R Disk Enclosure Use this template for a subsystem with a three-shelf Model 4214R disk enclosure (single-bus). You can have up to six Model 4214R disk enclosures per controller shelf.
Subsystem Profile Templates (Continued) 212 Bay 1 2 3 4 5 6 7 8 9 1 0 1 1 1 2 1 3 1 4 SCSI ID 0 0 0 1 0 2 0 3 0 4 0 5 0 8 0 9 1 0 1 1 1 2 1 3 1 4 1 5 DISK ID Disk30000 Disk30100 Disk30200 Disk30300 Disk30400 Disk30500 Disk30800 Disk30900 Disk31000 Disk31100 Disk31200 Disk31300 Disk31400 Disk31500 Model 4214R Disk Enclosure Shelf 3 (Single-Bus) HSG80 ACS Solution Software V8.
Subsystem Profile Templates Storage Map Template 5 for the Model 4254 Disk Enclosure Use this template for a subsystem with a three-shelf Model 4254 disk enclosure (dual-bus). You can have up to three Model 4254 disk enclosures per controller shelf.
Subsystem Profile Templates (Continued) Model 4254 Disk Enclosure Shelf 3 (Dual-Bus) 214 Bay 1 2 3 4 5 6 7 8 9 1 0 1 1 1 2 1 3 1 4 SCSI ID 0 0 0 1 0 2 0 3 0 4 0 5 0 8 0 0 0 1 0 2 0 3 0 4 0 5 0 8 DISK ID Disk50100 Disk50200 Disk50300 Disk50400 Disk50500 Disk50800 Disk60000 Disk60100 Disk60200 Disk60300 Disk60400 Disk60500 Disk60800 Bus B Disk50000 Bus A HSG80 ACS Solution Software V8.
Subsystem Profile Templates Storage Map Template 6 for the Model 4310R Disk Enclosure Use this template for a subsystem with a six-shelf Model 4310R disk enclosure (single-bus). You can have up to six Model 4310R disk enclosures per controller shelf.
Subsystem Profile Templates Model 4310R Disk Enclosure Shelf 1 (Single-Bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID Disk11200 9 Disk11100 8 Disk11000 7 Disk10800 6 Disk10500 5 Disk10400 4 Disk10300 3 Disk10200 2 Disk10100 1 Disk10000 Bay Model 4310R Disk Enclosure Shelf 2 (Single-Bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID Disk21200 9 Disk21100 8 Disk21000 7 Disk20800 6 Disk20500 5 Disk20400 4 Disk20300 3 Disk20200 2 Disk20100 1 Disk20000 Ba
Subsystem Profile Templates Storage Map Template 7 for the Model 4350R Disk Enclosure Use this template for a subsystem with a three-shelf Model 4350R disk enclosure (single-bus). You can have up to three Model 4350R disk enclosures per controller shelf.
Subsystem Profile Templates Storage Map Template 8 for the Model 4314R Disk Enclosure Use this template for a subsystem with a six-shelf Model 4314R disk enclosure. You can have a maximum of six Model 4314R disk enclosures with each Model 2200 controller enclosure.
Subsystem Profile Templates continued from previous page Model 4314R Disk Enclosure Shelf 1 (Single-Bus) 14 SCSI ID 00 01 02 03 04 05 08 09 10 11 12 13 14 15 DISK ID Disk11500 13 Disk11400 12 Disk11300 11 Disk11200 10 Disk11100 9 Disk11000 8 Disk10900 7 Disk10800 6 Disk10500 5 Disk10400 4 Disk10300 3 Disk10200 2 Disk10100 1 Disk10000 Bay Model 4314R Disk Enclosure Shelf 2 (Single-Bus) 14 SCSI ID 00 01 02 03 04 05 08 09 10 11 12 13 14 15 DISK ID
Subsystem Profile Templates Storage Map Template 9 for the Model 4354R Disk Enclosure Use this template for a subsystem with a three-shelf Model 4354R disk enclosure (dual-bus). You can have up to three Model 4354R disk enclosures per controller shelf.
Installing, Configuring, and Removing the Client B The following information is included in this appendix: ■ Why Install the Client?, page 222 ■ Before You Install the Client, page 223 ■ Installing the Client, page 224 ■ Installing the Integration Patch, page 225 ■ Troubleshooting Client Installation, page 227 ■ Adding Storage Subsystem and its Host to Navigation Tree, page 229 ■ Removing Command Console Client, page 231 ■ Where to Find Additional Information, page 232 HSG80 ACS Solution S
Installing, Configuring, and Removing the Client Why Install the Client? The Client monitors and manages a storage subsystem by performing the following tasks: 222 ■ Create mirrored device group (RAID 1) ■ Create striped device group (RAID 0) ■ Create striped mirrored device group (RAID 0+1) ■ Create striped parity device group (3/5) ■ Create an individual device (JBOD) ■ Monitor many subsystems at once ■ Set up pager notification HSG80 ACS Solution Software V8.
Installing, Configuring, and Removing the Client Before You Install the Client 1. Verify you are logged into an account that is a member of the administrator group. 2. Check the software product description that came with the software for a list of supported hardware. 3. Verify that you have the SNMP service installed on the computer. SNMP must be installed on the computer for this software to work properly. The Client software uses SNMP to receive traps from the Agent.
Installing, Configuring, and Removing the Client Installing the Client The following restriction should be observed when installing SWCC on Windows NT 4.0 Workstations. If you select all of the applets during installation, the installation will fail on the HSG60 applet and again on one of the HSG80 applets. The workaround is to install all of the applets you want except for the HSG60 applet and the HSG80 ACS 8.5 applet. You can then return to the setup program and install the one that you need. 1.
Installing, Configuring, and Removing the Client Installing the Integration Patch The integration patch determines which version of firmware the controller is using and launches the appropriate StorageWorks Command Console (SWCC) Storage Window within Insight Manager (CIM) version 4.23. Should I Install the Integration Patch? Install this patch if your HSG80 controller uses ACS 8.7 or later. This patch enables you to use the controller’s SWCC Storage Window within CIM to monitor and manage the controller.
Installing, Configuring, and Removing the Client Caution: If you remove the integration patch, HSG80 Storage Window V2.1 will no longer work and you will need to reinstall HSG80 Storage Window V2.1. The integration patch uses some of the same files as the HSG80 Storage Window V2.1. Integrating Controller’s SWCC Storage Window with CIM You can open the controller’s Storage Window from within the Windows-based CIM version 4.23 by doing the following: 1.
Installing, Configuring, and Removing the Client Finding the Controller’s Storage Window If you installed Insight Manager before SWCC, Insight Manager will be unable to find the controller’s Storage Window. To find the controller’s Storage Window, perform the following procedure: 1. Double-click the Insight Agents icon (Start > Settings > Control Panel). A window appears showing you the active and inactive Agents under the Services tab. 2. Highlight the entry for Fibre Array Information and click Add.
Installing, Configuring, and Removing the Client If the Network Information Services (NIS) are being used to provide named port lookup services, contact the network administrator to add the correct ports.
Installing, Configuring, and Removing the Client Adding Storage Subsystem and its Host to Navigation Tree The Navigation Tree enables you to manage storage over the network by using the Storage Window. If you plan to use pager notification, you must add the storage subsystem to the Navigation Tree. 1. Verify that you have properly installed and configured the HS-Series Agent on the storage subsystem host. 2. Click Start > Programs > Command Console > StorageWorks Command Console.
Installing, Configuring, and Removing the Client Figure 48: Navigation window showing storage host system “Atlanta” 6. Click the plus sign to expand the host icon. When expanded, the Navigation Window displays an icon for the storage subsystem. To access the Storage Window for the subsystem, double-click the Storage Window icon. Figure 49: Navigation window showing expanded “Atlanta” host icon 230 HSG80 ACS Solution Software V8.
Installing, Configuring, and Removing the Client Note: You can create virtual disks by using the Storage Window. For more information on the Storage Window, refer to HP StorageWorks Command Console Version 2.5, User Guide. Removing Command Console Client Before you remove the Command Console Client (CCL) from the computer, remove AES. This will prevent the system from reporting that a service failed to start every time the system is restarted. Steps 2 through 5 describe how to remove the CCL.
Installing, Configuring, and Removing the Client Note: This procedure removes only the Command Console Client (SWCC Navigation Window). You can remove the HSG80 Client by using the Add/Remove program. Where to Find Additional Information You can find additional information about SWCC by referring to the online Help and to HP StorageWorks Command Console Version 2.5, User Guide. About the User Guide HP StorageWorks Command Console Version 2.5, User Guide contains additional information on how to use SWCC.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters C This appendix provides step-by-step instructions for installation of the RAID Array RA/MA8000 and ESA/EMA12000 (Enterprise & Modular Storage RAID Array) Fibre Channel Cluster for Windows NT/Windows 2000/Windows Server 2003 (32-bit).
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters These Fibre Channel topologies simplify cluster configurations by eliminating many of the pitfalls that restrict the SCSI parallel bus when configured with multiple initiators. Issues such as bus termination, unfair arbitration, restrictive cable lengths and the ability to address devices are alleviated using the FC-AL topology.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Cluster Configuration Guidelines The RAID Array 8000 (RA8000) and Enterprise Storage Array 12000 (ESA12000) are Fibre Channel RAID systems that support Storage Area Network (SAN) constructs using Fibre Channel Switch and Arbitrated Loop topologies. These storage systems can be configured in high availability configurations using Microsoft Cluster Server and Secure Path Software.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters for the required MSCS configuration. Refer to your The RAIDBOOK - A Source for RAID Technology RAID Advisory Board Fibre Channel Storage Hub 12 Installation Guide (340662-001) for details on hub configuration and setup. The StorageWorks Fibre Channel Storage Switch is a 16 port Fibre Channel switch supported with the Enterprise & Modular Storage RAID Array.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Cluster Configurations This section highlights some of the possible Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster configurations that can be realized using either of these Fibre Channel topologies. Use the configuration maximums outlined in this section to determine the viability of Windows NT/Windows 2000/Windows Server 2003 (32-bit) cluster configurations that are not shown.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters NT Cluster A Windows NT Intel Server 1 Windows NT Intel Server 2 FC HBA FC HBA FC Hub RA8000 or ESA12000 FC Dual Controller Up to 84 Disks Active Standby Port 1 Port 2 Port 1 Port 2 SHR-2240A Figure 52: Single Cluster Fibre Channel Configuration 238 HSG80 ACS Solution Software V8.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters The Configuration in Figure 52 features the following attributes: ■ One Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster (MSCS) ■ Single Fibre Channel Loop ■ Up to 84 UltraSCSI drives with optional expansion enclosures ■ Dual-redundant HSG80 RAID controllers operating in transparent failover mode ■ Scalable to add a second Enterprise & Modular Storage RAID Array and both HSG80 host ports Adding a redundant I/O path to
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters ■ Secure Path V3.1a and Secure Path 4.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters NT Cluster A NT Cluster B Windows NT Intel Server 1 Windows NT Intel Server 2 FC HBA FC HBA FC Hub Windows NT Intel Server 3 Windows NT Intel Server 4 FC HBA FC HBA RA8000 or ESA12000 FC Dual Controller Up to 84 Disks Active Standby Port 1 Port 1 Port 2 Port 2 Standby Active FC Hub SHR-2242A Figure 54: Two-Cluster Fibre Channel Configuration The Configuration in Figure 54 features the following attributes: ■ Two Windows N
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters NT Cluster A NT Cluster B Windows NT Intel Server 1 Windows NT Intel Server 2 FC HBA2 FC HBA 1 FC HBA2 FC HBA 1 FC Hub1 FC Hub2 RA8000 or ESA12000 FC Dual Controller Up to 84 Disks Active Active Port 1 A Port 2 Port 1 B Port 2 Active Windows NT Intel Server 3 Windows NT Intel Server 4 FC HBA 1 FC HBA 2 FC HBA 1 FC HBA 2 FC Hub3 Active FC Hub4 Figure 55: Two-Cluster Fibre Channel Configuration with Secure Path The Configura
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Note: Refer to the StorageWorks Application note, Enterprise & Modular Storage RAID Array FC-Fabric Configurations for Windows NT/Windows 2000/Windows Server 2003 (32-bit) for an overview of Fibre Channel Switch Fabric configuration guidelines.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Figure 56 shows two Windows NT/Windows 2000/Windows Server 2003 (32-bit) Clusters configured on a Fibre Channel Switch. Three Enterprise & Modular Storage RAID Arrays configured in transparent failover mode are also connected to the switch. Each cluster has access to each Enterprise & Modular Storage RAID Array via storage access control primitives.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters ■ Dual-redundant HGS80 controllers running in Transparent failover mode ■ Up to 252 UltraSCSI drives with optional expansion enclosures Installing Software for a Fibre Channel Cluster This section describes the procedures and order to install software on a Fibre Channel Cluster.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Preparing the Enterprise & Modular Storage RAID Array Subsystem 1. Verify that your storage subsystem and FC host bus adapter settings are correct for your Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster configuration and Fibre Channel Topology. 2. Verify that your storage units are accessible to the servers in your Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster configuration. 3.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Preparing the Enterprise & Modular Storage RAID Array for an FC Cluster Your RA8000, IMA8000, ESA/EMA 12000 Fibre Channel system is preconfigured with specific parameters based on either the Fibre Channel Arbitrated Loop or Switch Fabric topology. You may need to change these parameters when implementing certain Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster configurations in a Fibre Channel Arbitrated Loop.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters StorageWorks recommends using the settings in Table 16 for your Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster configuration when configured for FC-AL topology.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Example 1 – Changing arbitrated loop physical address settings HSG80>Set This_Controller Port_1_AL_PA=73 HSG80>Set This_Controller Port_2_AL_PA=74 Note: You must restart both of your HSG80 controllers if you change the port topology or AL_PA settings.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters enable access to all hosts on a per LUN basis using the Command Line Interface (CLI). To enable access to the servers comprising your Windows NT/Windows 2000/Windows Server 2003 (32-bit), refer to Example 2.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Assigning/Removing Drive Letters for Windows 2000 and Windows Server 2003 (32-bit) This section discusses assigning and de-assigning drive letters on your Windows system. Temporarily Removing Drive Letters on Windows 2000 or Windows Server 2003 (32-bit) Note: This section is required only when you have created NTFS partitions on your Enterprise Storage RAID Array system before the installation of the HsxDisk driver.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Figure 58: Disk Management window showing the current partitions 2. Label your partitions if they are not already labeled, in order to distinguish each one. 3. Record the drive letters currently associated with each of the partition labels. 4. Click on an NTFS partition that exists on your Enterprise & Modular Storage RAID Array system. 5. Click on the partition, choose Change Drive Letter and Path.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Figure 59: Change Drive Letter and Paths dialog box 6. Click Remove (as shown in Figure 59). Caution: Do not remove the drive letters for any drive that is not connected to your Enterprise & Modular Storage RAID Array. A confirmation dialog box appears as shown in Figure 60.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters ■ Setting Fibre Channel Host Bus adapter registry settings. ■ Establishing Extended Configuration settings. ■ Checking the event log for specific error conditions. ■ Reviewing driver revision levels. The Fibre Channel Software and RAID Windows NT (HszDisk.sys) or Windows 2000 (HsxDisk.sys) Device Driver software is installed on your host server from the RAID Array Software Solution CD-ROM.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Verifying Successful HsxDisk filter Driver Installation After the host server is restarted, verify that the HsxDisk class driver installed successfully by performing the following procedure: 1. Open the Event Viewer from Computer Management. 2. Locate an information icon in the Event Viewer window with HsxDisk for the Source. 3. Double click on the HsxDisk entry and an entry detail screen displays. 4.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Assigning/Removing Drive Letters for Windows NT This chapter discusses assigning and de-assigning drive letters on your Windows NT system. Temporarily Removing Drive Letters This section is required only when you have created NTFS partitions on your Enterprise & Modular Storage RAID Array system before the installation of the HszDisk class driver.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Temporarily Removing Drive Letter Assignments 1. Start the Disk Administrator. shows the Disk Administrator window displaying current partitions. 2. Label your partitions if they are not already labeled, so that you can distinguish each one. 3. Record the drive letters currently associated with each of the partition labels. 4. Click on an NTFS partition that exists on your Enterprise & Modular Storage RAID Array system. 5.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Figure 62: Drive Letter Confirmation 7. Click Yes. The partition now appears without a drive letter designator similar to the screen shown in Figure 63. Figure 63: No Drive Letter Assignments 8. Repeat Steps 4 through 7 for each of your partitions except the local and start partitions. 258 HSG80 ACS Solution Software V8.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Running the Fibre Channel Software Setup Utility The Fibre Channel Software Setup Utility serves various purposes, including: ■ Installing the HszDisk Class driver for Windows NT. ■ Setting Fibre Channel Host Bus adapter registry settings. ■ Querying for Arbitrated Loop addresses. ■ Establishing Extended Configuration settings. ■ Checking the event log for specific error conditions. ■ Reviewing driver revision levels.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters NT/2000 Server Server 4 ALPA Assignment 8 0X08 Note: ALPA assignments are not applicable to a Fibre Channel Switch configuration. 5. Restart the system. Verifying Successful HszDisk Class Driver Installation After the host server is restarted, verify that the HszDisk class driver installed successfully by performing the following procedure: 1. Open the Event Viewer from the Administrative Tools group. 2.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Reassign Drive Letters This section describes how to reassign drive letters to NTFS partitions on a host if they were temporarily de-assigned. 1. Start the Disk Administrator which displays all the existing partitions, similar to the window shown in Figure 64. (The only partitions with drive letters are the boot partition and any non-disk devices, such as a CD-ROM drive).
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Figure 65: Driver Letter Availability 4. Perform one of the following actions: ■ Click OK if you want to assign the selected drive letter and go to step 7. ■ Click the Assign drive letter radio button and go to the next step. 5. In the Assign Drive Letter window, select another drive letter from the drop down list and click OK.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Figure 66: All the Drive Letters Reassigned Preparing Host A With the NTFS partition drive letters successfully reassigned, or newly created, as applicable, Host A is prepared for a cluster. To prepare Host B, return to “Preparing Both Host Servers for a FC Cluster” on page 250 and repeat all of the preceding steps on Host B. Preparing Host B With the NTFS partition drive letters successfully reassigned, Host B is prepared for a cluster.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Installing and Configuring Cluster Software on Both Host Servers Note: The Enterprise & Modular Storage RAID Array, Host A and Host B must be prepared for a Fibre Channel cluster before installing Windows NT Cluster software. You are now ready to install and configure Windows NT Cluster software on both of your host servers, as described in the manual provided with your cluster software.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters 3. Restart your machine. Example boot.ini [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINNT=”Windows NT Server, Enterprise Edition Version 4.00" /pcilock Figure 67: Device Driver Initialization Event Log Entry HSG80 ACS Solution Software V8.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Verify the Windows Registry Device Driver Parameters The FCA device driver parameters in the Windows NT/Windows 2000/Windows Server 2003 (32-bit) registry must be set correctly for proper operation of your Enterprise & Modular Storage RAID Array storage subsystem configured in a Windows NT/Windows 2000/Windows Server 2003 (32-bit) cluster.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Note: StorageWorks recommends using ALPA values 1 and 2 for the host bus adapters in a Fibre Channel Windows NT/Windows 2000/Windows Server 2003 (32-bit) Cluster. The HardAlpa is not applicable for the Fibre Channel Switch Topology. Additional parameters are included when the host is configured with Secure Path Software.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters 2. Verify that your Windows NT/Windows 2000/Windows Server 2003 (32-bit) Servers (hosts) are connected to the Fibre Channel Loop To verify that your Windows NT/Windows 2000/Windows Server 2003 (32-bit) servers are connected to the loop, issue the CLI command show connection. As shown in Figure A-3, the output of this command shows information about present and previous host connections to the loop.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters 3. Verifying the Storage Units have access to all host connections Using the StorageWorks Command Console utility to create your storage partitions will, by default, restrict host access to the storage devices. To check host access, issue the CLI command as shown in Example 1.
Configuring Windows NT/Windows 2000/Windows 2003 (32-bit) Clusters Figure 68: Verifying FC-AL Connectivity RAID Array Subsystem 270 HSG80 ACS Solution Software V8.
glossary Glossary This glossary defines terms pertaining to the ACS solution software. It is not a comprehensive glossary of computer terms Glossary 8B/10B A type of byte definition encoding and decoding to reduce errors in data transmission patented by the IBM Corporation. This process of encoding and decoding data for transmission has been adopted by ANSI. adapter A device that converts the protocol and hardware interface of one bus type into another without changing the function of the bus.
Glossary association set A group of remote copy sets that share selectable attributes for logging and failover. Members of an association set transition to the same state simultaneously. For example, if one association set member assumes the failsafe locked condition, then other members of the association set also assume the failsafe locked condition. An association set can also be used to share a log between a group of remote copy set members that require efficient use of the log space.
Glossary built-in self-test A diagnostic test performed by the array controller software on the controller policy processor. byte A binary character string made up of 8 bits operated on as a unit. cache memory A portion of memory used to accelerate read and write operations. cache module A fast storage buffer CCL CCL-Command Console LUN, a “SCSI Logical Unit Number” virtual-device used for communicating with Command Console Graphical User Interface (GUI) software.
Glossary controller A hardware device that, with proprietary software, facilitates communications between a host and one or more devices organized in an array. The HSG80 family controllers are examples of array controllers. copying A state in which data to be copied to the mirrorset is inconsistent with other members of the mirrorset. See also normalizing. copying member Any member that joins the mirrorset after the mirrorset is created is regarded as a copying member.
Glossary DOC DWZZA-On-a-Chip. ASCSI bus extender chip used to connect a SCSI bus in an expansion cabinet to the corresponding SCSI bus in another cabinet (See DWZZA). driver A hardware device or a program that controls or regulates another device. For example, a device driver is a driver developed for a specific device that allows a computer to operate with the device, such as a printer or a disk drive.
Glossary ESD Electrostatic discharge. The discharge of potentially harmful static electrical voltage as a result of improper grounding. extended subsystem A subsystem in which two cabinets are connected to the primary cabinet. external cache battery See ECB. F_Port A port in a fabric where an N_Port or NL_Port may attach. fabric A group of interconnections between ports that includes a fabric element.
Glossary FCC Federal Communications Commission. The federal agency responsible for establishing standards and approving electronic devices within the United States. FCC Class A This certification label appears on electronic devices that can only be used in a commercial environment within the United States. FCC Class B This certification label appears on electronic devices that can be used in either a home or a commercial environment within the United States.
Glossary FRU Field replaceable unit. A hardware component that can be replaced at the customer location by service personnel or qualified customer service personnel. FRUTIL Field Replacement utility. full duplex (n) A communications system in which there is a capability for 2-way transmission and acceptance between two sites at the same time. full duplex (adj) Pertaining to a communications method in which data can be transmitted and received at the same time.
Glossary host compatibility mode A setting used by the controller to provide optimal controller performance with specific operating systems. This improves the controller performance and compatibility with the specified operating system. hot disks A disk containing multiple hot spots. Hot disks occur when the workload is poorly distributed across storage devices which prevents optimum subsystem performance. See also hot spots. hot spots A portion of a disk drive frequently accessed by the host.
Glossary I/O Refers to input and output functions. I/O driver The set of code in the kernel that handles the physical I/O to a device. This is implemented as a fork process. Same as driver. I/O interface See interface. I/O module A 16-bit SBB shelf device that integrates the SBB shelf with either an 8-bit single ended, 16-bit single-ended, or 16-bit differential SCSI bus (see SBB).
Glossary logical unit number LUN. A value that identifies a specific logical unit belonging to a SCSI target ID number. A number associated with a physical device unit during a task I/O operations. Each task in the system must establish its own correspondence between logical unit numbers and physical devices. logon Also called login. A procedure whereby a participant, either a person or network connection, is identified as being an authorized network participant. loop See arbitrated loop.
Glossary mirrored write-back caching A method of caching data that maintains two copies of the cached data. The copy is available if either cache module fails. mirrorset See RAID level 1. MIST Module Integrity Self-Test. multibus failover Allows the host to control the failover process by moving the units from one controller to another. N_port A port attached to a node for use with point-to-point topology or fabric topology. NL_port A port attached to a node for use in all topologies.
Glossary normalizing Normalizing is a state in which, block-for-block, data written by the host to a mirrorset member is consistent with the data on other normal and normalizing members. The normalizing state exists only after a mirrorset is initialized. Therefore, no customer data is on the mirrorset. normalizing member A mirrorset member whose contents are the same as all other normal and normalizing members for data that has been written since the mirrorset was created or lost cache data was cleared.
Glossary PCMCIA Personal Computer Memory Card Industry Association. An international association formed to promote a common standard for PC card-based peripherals to be plugged into notebook computers. The card commonly known as a PCMCIA card is about the size of a credit card. PDU Power distribution unit. The power entry device for StorageWorks cabinets. The CDU provides the connections necessary to distribute power to the cabinet shelves and fans.
Glossary protocol The conventions or rules for the format and timing of messages sent and received. PTL Port-Target-LUN. The controller method of locating a device on the controller device bus. PVA module Power Verification and Addressing module. quiesce The act of rendering bus activity inactive or dormant. For example, “quiesce the SCSI bus operations during a device warm-swap.” RAID Redundant Array of Independent Disks.
Glossary RAID level 3/5 A RAID storageset that stripes data and parity across three or more members in a disk array. A RAIDset combines the best characteristics of RAID level 3 and RAID level 5. A RAIDset is the best choice for most applications with small to medium I/O requests, unless the application is write intensive. A RAIDset is sometimes called parity RAID. RAIDset See RAID level 3/5. RAM Random access memory.
Glossary remote copy set A bound set of two units, one located locally and one located remotely, for long-distance mirroring. The units can be a single disk, or a storageset, mirrorset, or RAIDset. A unit on the local controller is designated as the “initiator” and a corresponding unit on the remote controller is designated as the “target”. request rate The rate at which requests are arriving at a servicing entity. RFI Radio frequency interference.
Glossary SCSI ID number The representation of the SCSI address that refers to one of the signal lines numbered 0 through 15. SCSI-P cable A 68-conductor (34 twisted-pair) cable generally used for differential bus connections. SCSI port (1) Software: The channel controlling communications to and from a specific SCSI bus in the system. (2) Hardware: The name of the logical socket at the back of the system unit to which a SCSI device is connected.
Glossary StorageWorks A family of modular data storage products that allow customers to design and configure their own storage subsystems. Components include power, packaging, cabling, devices, controllers, and software. Customers can integrate devices and array controllers in StorageWorks enclosures to form storage subsystems. StorageWorks systems include integrated SBBs and array controllers to form storage subsystems.
Glossary tape inline exerciser (TILX) The controller diagnostic software to test the data transfer capabilities of tape drives in a way that simulates a high level of user activity. topology An interconnection scheme that allows multiple Fibre Channel ports to communicate with each other. For example, point-to-point, Arbitrated Loop, and switched fabric are all Fibre Channel topologies.
Glossary warm swap A device replacement method that allows the complete system to remain online during device removal or insertion. The system bus may be halted, or quiesced, for a brief period of time during the warm-swap procedure. Wide Ultra SCSI Fast/20 on a Wide SCSI bus. Worldwide name A unique 64-bit number assigned to a subsystem by the Institute of Electrical and Electronics Engineers (IEEE) and set by manufacturing prior to shipping. This name is referred to as the node ID within the CLI.
Glossary 292 HSG80 ACS Solution Software V8.
index A Index accessing the configuration menu Agent 146 ADD CONNECTIONS multiple-bus failover 49 transparent failover 47 ADD UNIT multiple-bus failover 49 transparent failover 47 adding subsystem entry Agent 150 virtual disks 232 adding a disk drive to the spareset configuration options 179 adding disk drives configuration options 179 Agent accessing the configuration menu 146 configuration menu 146 configuring 146 adding a subsystem entry 150 changing the Agent access password 146 deleting a client sys
Index Cables 235 cabling controller pair 165 multiple-bus failover fabric topology configuration 164 single controller 158 cache modules location 30, 31 read caching 39 write-back caching 39 write-through caching 39 caching techniques mirrored 40 read caching 39 read-ahead caching 39 write-back caching 39 write-through caching 39 CCL disabling 114 changing switches configuration options 181, 182 chunk size choosing for RAIDsets and stripesets 91 controlling stripesize 91 using to increase request rate 92 u
Index Configuration, Single 237 Configuration, Two-cluster 240 configuring Agent 146 pager notification 232 configuring devices fabric topology 171 connection methods SWCC 112 connections 42 hardware 119 naming 42 Connectivity to the Fibre Channel Arbitrated Loop 267 containers attributes 74 illustrated 75, 172 mirrorsets 82 planning storage 74 stripesets 80 controller verification of installation 171 controller verification installation 163, 171 controllers cabling 158, 165 location 30, 31 node IDs 58 pro
Index E enabling switches 89 enabling Agent startup 153 enabling startup Agent 153 Enterprise Storage RAID Array 235 erasing metadata 94 establishing a local connection 156 establishing a serial connection HSG80 storage window 114 F fabric topology configuration single controller cabling 157 failover 33 multiple-bus 36 transparent 33 FCA driver support 110 Fibre Channel Cluster Concept 234 Fibre Channel Cluster, Installing Software 245 Fibre Channel Host Bus Adapter 235 fibre channel hub 111, 259 Fibre Ch
Index there is no disk in the drive message 228 installation verification CLI commands 163, 171 installing Agent 143 Installing Software for a Fibre Channel Cluster 245 integrating SWCC 232 invalid network port assignments 227 J JBOD 76 L launching Client 113 LOCATE find devices 95 location cache module 30, 31 controller 30, 31 LUN IDs general description 60 LUN presentation 48 M maintenance port connection establishing a local connection 156 illustrated 156 mapping storagesets 95 messages there is no d
Index profiles creating 77 description 77 storageset 205 example 206 for mirrorsets 90 for RAIDsets 90 initialize 91 other controller 31 P pager notification 232 configuring 232 partitions assigning a unit number fabric topology 177 creation 122 defining 88 formatting 123 planning considerations 87 guidelines 88 removing 124 performance 83 Physical connection, making 106 planning 61 overview 77 striped mirrorsets 86 stripesets 80 planning configurations where to start 62 planning considerations 83 planni
Index S SAVE_CONFIGURATION 93 saving configuration 93 SCSI version offset 49 SCSI-2 assigning unit numbers 50 command console lun 50 SCSI-3 assigning unit numbers 50 command console lun 50 Second enclosure of multiple-enclosure subsystem storage map template 2 209 selective storage presentation 51 serial connection establishing HSG80 storage window 114 Servers 235 Servers, Designating as Host A and Host B 245 SET CONNECTIONS multiple-bus failover 49 transparent failover 47 SET UNIT multiple-bus failover 49
Index RAIDsets 83 striped mirrorsets 85 stripesets 78 profile 77 profiles 205 storageset profile 77 storageset switches SET command 90 storagesets creating a profile 77 moving 201 striped mirrorsets planning 86 planning considerations 85 stripesets distributing members across buses 81 planning 80 planning considerations 78 important points 80 subsystem saving configuration 93 subsystem configuration backup 196 subsystem entry Agent adding 150 SWCC 138 additional information 232 connection methods 112 integ
Index fabric topology 177 unit switches changing fabric topology 182 units LUN IDs 60 Upgrade procedures solution software 124 transparent failover 130 using the configuration menu Agent 146 V verification controller installation 163, 171 verification of installation controller 163, 171 Verifying Device Driver Initialization 264 Verifying/Installing Required Versions 119 virtual disk creation 112, 117 virtual disks adding 232 W Windows Clusters configure 233 worldwide names 58 NODE_ID 58 REPORTED PORT_I
