Installation and Configuration Guide HP StorageWorks HSG80 ACS Solution Software V8.8 for IBM AIX Product Version: 8.8-1 First Edition (March 2005) Part Number: AA–RV1HA–TE This guide provides installation and configuration instructions and reference material for operation of the HSG80 ACS Solution Software V8.8-1 for IBM AIX.
© 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 Contents About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Determining the Address of the CCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/Disabling the CCL in SCSI-2 Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling the CCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling the CCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/Disabling CCL in SCSI-3 Mode. . .
Contents RAIDset Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keep these points in mind when planning RAIDsets:. . . . . . . . . . . . . . . . . . . . . . . . Striped Mirrorset Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storageset Expansion Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partition Planning Considerations . . . . . . . . . . . . . . .
Contents 4 Installing and Configuring HSG Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Why Use StorageWorks Command Console (SWCC)?. . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Installation and Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 About the Network Connection for the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Before Installing the Agent. . . . . . . . . . .
Contents Assigning Unit Numbers and Unit Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning a Unit Number to a Storageset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning a Unit Number to a Single (JBOD) Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning a Unit Number to a Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Options . . . . . . . . . . . . . . . . . . . . . .
Contents A Subsystem Profile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195 Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Storage Map Template 1 for the BA370 Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Storage Map Template 2 for the Second BA370 Enclosure. . . . . . . . . . . . . . . . . . . . . . . . .
Contents Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Figures 1 General configuration flowchart (panel 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2 General configuration flowchart (panel 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Single-bus enterprise storage RAID array storage system. . . . . . . . . . . . . . . . . . . . . . . An example of a network connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance port connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single controller cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
about this guide About this Guide This installation guide for HSG80 ACS Solution Software V8.8-1 for IBM AIX provides information to help you: About this Guide ■ Plan the storage array subsystem. ■ Install and configure the storage array subsystem on individual operating system platforms.
About this Guide Overview This section covers the following topics: ■ "Intended Audience", page 12 ■ "Related Documentation", page 12 Intended Audience This book is intended for use by systems administrators and systems technicians who are experienced with the following: ■ Storage ■ Networking Related Documentation In addition to this guide, HP provides corresponding information: 12 ■ ACS V8.
About this Guide Solution software host support includes the following platforms: — IBM AIX — HP-UX — Linux (Red Hat x86, SuSE x86) — Novell NetWare — Open VMS — Sun Solaris — Tru64 UNIX — Windows NT/2000/Windows Server 2003 (32-bit) Additional support required by HSG80 ACS Solution Software V8.
About this Guide Chapter Content Summary Table 1 below summarizes the content of the chapters. Table 1: Summary of chapter contents Chapters 14 Descriptions 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 Descriptions 7. Backing Up, Cloning, and Moving Data Description of common procedures that are not mentioned elsewhere in this guide. ■ Backing Up Subsystem Configuration ■ Cloning Data for Backup ■ Creating Clones and Snapshots for Volume Groups ■ Moving Storagesets Appendix A. Subsystem Profile Templates This appendix contains storageset profiles to copy and use to create your system profiles.
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 Tip: Text in a tip provides additional help to readers by providing nonessential or optional techniques, procedures, or shortcuts. Note: Text set off in this manner presents commentary, sidelights, or interesting points of information. Symbols on Equipment The following equipment symbols may be found on hardware for which this guide pertains.
About this Guide Power supplies or systems marked with these symbols indicate the presence of multiple sources of power. WARNING: To reduce the risk of personal injury from electrical shock, remove all power cords to completely disconnect power from the power supplies and systems. Any product or assembly marked with these symbols indicates that the component exceeds the recommended weight for one individual to handle safely.
About this Guide Rack Stability Rack stability protects personnel and equipment. WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that: ■ The leveling jacks are extended to the floor. ■ The full weight of the rack rests on the leveling jacks. ■ In single rack installations, the stabilizing feet are attached to the rack. ■ In multiple rack installations, the racks are coupled. ■ Only one rack component is extended at any time.
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 http://www.hp.com. HP 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.
About this Guide HP Authorized Reseller For the name of your nearest HP authorized reseller: ■ In the United States, call 1-800-345-1518 ■ In Canada, call 1-800-263-5868 ■ Elsewhere, see the HP web site for locations and telephone numbers http://www.hp.com. HSG80 ACS Solution Software V8.
About this Guide Configuration Flowchart A three-part flowchart (Figures 1-3) is shown on the following pages. Refer to these charts while installing and configuring a new storage subsystem. All references in the flowcharts pertain to pages in this guide, unless otherwise indicated. 22 HSG80 ACS Solution Software V8.
About this Guide See the unpacking instructions on shipping box Unpack subsystem Plan a subsystem Chapter 1 Plan storage configurations Chapter 2 Prepare host system Chapter 3 Make local connection page 134 Controller pair Single controller Cable controller page 135 Cable controllers page 145 Configure controller page 136 Configure controllers page 146 Installing SWCC ? No A Yes B See Figure 3 on page 25 See Figure 2 on page 24 Figure 1: General configuration flowchart (panel 1) HSG80 ACS
About this Guide A Configure devices page 152 Create storagesets and partitions: Stripeset, page 154 Mirrorset, page 154 RAIDset, page 155 Striped mirrorset, page 156 Single (JBOD) disk, page 157 Continue creating units until you have you have completed your planned configuration. Partition, page 157 Assign unit numbers page 159 Setting configuration options page 160 Verify storage setup page 164 Figure 2: General configuration flowchart (panel 2) 24 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 setup page 164 Figure 3: Configuring storage with SWCC flowchart (panel 3) HSG80 ACS Solution Software V8.
About this Guide 26 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 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 30 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 36 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 Write-Through Caching Write-through caching is enabled when write-back caching is disabled. When the controller receives a write request from the host, it places the data in its cache module, writes the data to the disk drives, then notifies the host when the write 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. 38 HSG80 ACS Solution Software V8.
Planning a Subsystem 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 The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
Planning a Subsystem The CCL does the following: ■ Allows the RAID Array to be recognized by the host as soon as it is attached to the SCSI bus and configured into the operating system. ■ Serves as a communications device for the HS-Series Agent. The CCL identifies itself to the host by a unique identification string. In dual-redundant controller configurations, the commands described in the following sections alter the setting of the CCL on both controllers. The CCL is enabled only on host port 1.
FC Configuration Procedures 19. Turn on the switches, if not done previously. Plugging in the FC Cable and Verifying Connections 20. Plug the FC cable from the first host adapter into the switch or hub. Enter a SHOW CONNECTIONS command to view the connection table: HSG > SHOW CONNECTIONS The first connection has one or more entries in the connection table.
FC Configuration Procedures 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: HP recommends that you use the CONFIG utility only at reduced I/O loads. The CONFIG utility takes about two minutes to discover and to map the configuration of a completely populated storage system. 152 HSG80 ACS Solution Software V8.
FC Configuration Procedures Configuring Storage Containers For a technology refresher on this subject, refer to "Choosing a Container Type", page 76. In choosing a container, you choose between independent disks (JBODs) or one of several storageset types, as shown in Figure 39. The independent disks and the selected storageset may also be partitioned.
FC Configuration Procedures 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. Initialize the stripeset, specifying any desired switches: INITIALIZE STRIPESET-NAME SWITCHES See "Specifying Initialization Switches", page 93, for a description of the initialization switches. 3.
FC Configuration Procedures 3. Verify the mirrorset configuration: SHOW MIRRORSET-NAME 4. Assign the mirrorset a unit number to make it accessible by the hosts. See "Assigning Unit Numbers and Unit Qualifiers", page 159. For example: The commands to create Mirr1, a mirrorset with two members (DISK10000 and DISK20000), and to initialize it using default switch settings: ADD MIRRORSET MIRR1 DISK10000 DISK20000 INITIALIZE MIRR1 SHOW MIRR1 Configuring a RAIDset 1.
FC Configuration Procedures 4. Assign the RAIDset a unit number to make it accessible by the hosts. See "Assigning Unit Numbers and Unit Qualifiers", page 159. For example: The commands to create RAID1, a RAIDset with three members (DISK10000, DISK20000, and DISK10100) and to initialize it with default values: ADD RAIDSET RAID1 DISK10000 DISK20000 DISK30000 INITIALIZE RAID1 SHOW RAID1 Configuring a Striped Mirrorset 1. Create, but do not initialize, at least two mirrorsets.
FC Configuration Procedures Configuring a Single-Disk Unit (JBOD) 1. Initialize the disk drive, specifying any desired switches: INITIALIZE DISK-NAME SWITCHES See "Specifying Initialization Switches", page 93, for a description of the initialization switches. 2. Verify the configuration by entering the following command: SHOW DISK-NAME 3. Assign the disk a unit number to make it accessible by the hosts. See "Assigning Unit Numbers and Unit Qualifiers", page 159. Configuring a Partition 1.
FC Configuration Procedures or SHOW DISK-NAME The partition number is displayed in the first column, followed by the size and starting block of each partition. 4. Assign the partition a unit number to make it accessible by the hosts. See "Assigning Unit Numbers and Unit Qualifiers", page 159. For example: The commands to create RAID1, a three-member RAIDset, then partition it into two storage units are shown below.
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 Reference Guide.
FC Configuration Procedures Configuration Options There are multiple options that allow you to configure your system. Changing the CLI Prompt To change the CLI prompt, enter a 1- to 16- character string as the new prompt, according to the following syntax: SET THIS_CONTROLLER PROMPT = “NEW PROMPT” If you are configuring dual-redundant controllers, also change the CLI prompt on the “other controller.
FC Configuration Procedures Note: This procedure assumes that the disks that you are adding to the spareset have already been added to the controller's list of known devices. To add the disk drive to the controller's spareset list, use the following syntax: ADD SPARESET DISKNNNNN Repeat this step for each disk drive you want to add to the spareset: For example: The following example shows the syntax for adding DISK11300 and DISK21300 to the spareset.
FC Configuration Procedures To disable autospare, use the following command: SET FAILEDSET NOAUTOSPARE During initialization, AUTOSPARE checks to see if the new disk drive contains metadata. Metadata is information the controller writes on the disk drive when the disk drive is configured into a storageset. Therefore, the presence of metadata indicates that the disk drive belongs to, or has been used by, a storageset. If the disk drive contains metadata, initialization stops.
FC Configuration Procedures Displaying the Current Switches To display the current switches for a storageset or single-disk unit, enter a SHOW command, specifying the FULL switch: SHOW STORAGESET-NAME or SHOW DEVICE-NAME Note: FULL is not required when showing a particular device. It is used when showing all devices, for example, SHOW DEVICES FULL.
FC Configuration Procedures Verifying Storage Configuration from Host Once the HP StorageWorks Solution Software has been installed, logical units may be created on the RAID Array and configured. Create these logical units using the Client or the CLI. Be sure the Agent and Client are already installed on the AIX and Windows systems, respectively. New logical units created on the RAID Array must be recognized by the operating system before they can be used. The following steps outline the process: 1.
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 ■ Two single-bus model 4214R disk enclosure shelves ■ PCMCIA cards installed in both controllers A storage subsystem example is shown in Figure 40.
Using CLI for Configuration Port 1 2 3 4 5 6 D0 S1 MI DISK102 00 D0 S1 M1 DISK202 00 D0 S1 M2 DISK302 00 D0 S1 M2 DISK402 00 D2 D101 DISK503 00 D1 M3 DISK502 00 D120 R2 DISK201 00 D120 R2 DISK301 00 D120 R2 DISK401 00 D120 R2 DISK501 00 D102 R1 DISK200 00 D102 R1 DISK300 00 D102 R1 DISK400 00 D102 R1 DISK500 00 Power Supply D120 R2 DISK601 00 Power Supply D102 R1 DISK100 00 Power Supply D1 M3 DISK602 00 Power Supply D120 R2 DISK101 00 Power Supply spareset member DISK603 00 Tar
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 CXO7547B Figure 41: Example, t
Using CLI for Configuration "RED" "GREY" "BLUE" D1 D0 D2 D101 D102 D120 CXO7110B Figure 42: Example, logical or virtual disks comprised of storagesets "PURPLE" "WHITE" "TAN" D0 at LUN 0 D1 at LUN 1 D100 at LUN 0 D120 at LUN 0 CXO7297B Figure 43: Example, virtual system layout from hosts’ point of view 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.
Using CLI for Configuration Plug serial cable from maintenance terminal into top controller. CLEAR CLI SET FAILOVER COPY=THIS CLEAR CLI SET THIS SCSI_VERSION=SCSI-2 SET THIS ALLOCATION_CLASS=0 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 Connection Name Operating System Controller !NEWCON00 WINNT THIS Port 1 Address XXXX XX Unit Offset Status OL this 0 HOST_ID=XXXX-XXXX-XXXX-XX ADAPTER_ID=XXXX-XXXX-XXX XX X-XXXX RENAME !NEWCON00 PURPLE1A1 SET PURPLE1A1 OPERATING_SYSTEM=AIX_CAMBEX SHOW CONNECTIONS Note: Connection table sorts alphabetically.
Using CLI for Configuration Connection Name Operating System Controller Port Address Status Unit Offset !NEWCON0 1 WINNT THIS 2 XXXX XX OL this 100 HOST_ID=XXXX-XXXX-XXXX-XXXX PURPLE1A AIX_CAMBEX 1 OTHER HOST_ID=XXXX-XXXX-XXXX-XXXX ADAPTER_ID=XXXX-XXXX-XXX X-XXXX 1 XXXX XX OL other 0 ADAPTER_ID=XXXX-XXXX-XXX X-XXXX RENAME !NEWCON01 WHITE1B2 SET WHITE1B2 OPERATING_SYSTEM=AIX_CAMBEX SHOW CONNECTIONS Mark or tag both end of Fibre Channel cables.
Using CLI for Configuration Plug in the Fibre Channel cable from the adapter in host “TAN”.
Using CLI for Configuration RENAME !NEWCON02 TAN1B2 SET TAN1B2 OPERATING_SYSTEM=AIX_CAMBEX SET TAN1B2 UNIT_OFFSET=120 SHOW CONNECTIONS HSG80 ACS Solution Software V8.
Using CLI for Configuration Connection Name Operating System PURPLE1A AIX_CAMBEX 1 Controller Port Address Status OTHER 1 XXXX XX OL other HOST_ID=XXXX-XXXX-XXXX-XXXX WHITE1B2 AIX_CAMBEX THIS HOST_ID=XXXX-XXXX-XXXX-XXXX TAN1B2 AIX_CAMBEX THIS HOST_ID=XXXX-XXXX-XXXX-XXXX Unit Offset 0 ADAPTER_ID=XXXX-XXXX-XXX X-XXXX 2 XXXX XX OL this 100 ADAPTER_ID=XXXX-XXXX-XXX X-XXXX 2 XXXX XX OL this 120 ADAPTER_ID=XXXX-XXXX-XXX X-XXXX Mark or tag both end of Fibre Channel cables.
Using CLI for Configuration 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=PURPLE1A1 ADD RAIDSET R2 DISK10100 DISK20100 DISK30100 DISK40100 DISK50100 DISK60100 INITIALIZE R2 ADD UNIT D120 R2 DISABLE_ACCESS_PATH=ALL SET D120 ENABLE_ACCESS_PATH=(TAN1B2) ADD MIRRORSET MI DISK10200 DISK20200 ADD MIRRORSET M2 DISK30200 DISK40200 ADD STRIPESET S1 M1 M2 INITIALIZE S1 ADD UNIT D0 S1 DISABLE_ACC
Using CLI for Configuration 176 HSG80 ACS Solution Software V8.
Backing Up, Cloning, and Moving Data 7 This chapter includes the following topics: ■ "Backing Up Subsystem Configurations", page 178 ■ "Creating Clones for Backup", page 179 ■ "Clone and Snapshot and AIX Environment", page 183 ■ "Moving Storagesets", page 191 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 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. When prompted, enter the unit number of the unit you want to Clone. 4. When prompted, enter a unit number for the Clone unit that Clone creates. 5.
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 . COPY FROM DISK10300 TO DISK20200 IS 100% COMPLETE COPY FROM DISK10000 TO DISK20300 IS 100% COMPLETE PRESS RETURN WHEN YOU WANT THE NEW UNIT TO BE CREATED REDUCE DISK20200 DISK20300 UNMIRROR DISK10300 UNMIRROR DISK10000 ADD MIRRORSET C_MA DISK20200 ADD MIRRORSET C_MB DISK20300 ADD STRIPESET C_ST1 C_MA C_MB INIT C_ST1 NODESTROY ADD UNIT D99 C_ST1 D99 HAS BEEN CREATED. IT IS A CLONE OF D98. CLONE - NORMAL TERMINATION 182 HSG80 ACS Solution Software V8.
Backing Up, Cloning, and Moving Data Clone and Snapshot and AIX Environment The Clone and Snapshot functions permit an HP StorageWorks storage system to make copies of its internal drives. Once these copies become available, applications such as backup can be implemented on the copies, and not affect production work with the original drives. In AIX, volume groups can be copied in this manner, however AIX does not permit the existence of two or more exact volume group copies in same system environment.
Backing Up, Cloning, and Moving Data Snapshot Tools from the AIX Solution Kit The Snapshot tools from the AIX Solution Kit are contained within a fileset called hsg_snapshot.rte. The Snapshot utilities can be accessed through SMIT through the menu items Applications->Compaq HSG80 Snapshots. Following is a description of each of the menu items under StorageWorks HSG80 Snapshots and how to use them. List Snapshot Units The menu item lists all the Snapshot units on a particular HSG80.
Backing Up, Cloning, and Moving Data 2. Name of New Unit—The unit name (Dxx) that you wish to use for the Snapshot unit. Note that the unit must exist on the same controller as the original virtual disk. So, for example, if you have a unit called d5 you wish to Snapshot, it must be within the range of d1–d99 to be on the same controller. 3. Disk Devices for Snapshot—The list of physical disks on the subsystem you wish to use to create the Stripeset for the Snapshot.
Backing Up, Cloning, and Moving Data Manual Snapshot/Clone Creation To Clone or Snapshot drives within an AIX volume group, do the following: 1. Locate all physical volumes (hdisks) within the target volume group using the following command: lsvg -p The response lists the hdisks associated with the target volume group. 2. Get the location codes for the hdisks found with lspv. Refer to the AIX documentation on device locations codes.
Backing Up, Cloning, and Moving Data The following is an example for identifying the RAID set units in a single host configuration using testvg as a hypothetical volume group. # lsvg -p testvg testvg: PV_NAMEPV STATETOTAL PPsFREE PPsFREE DISTRIBUTION hdisk5active54222 00..00..00..00..22 hdisk6active54223 00..00..00..00..
Backing Up, Cloning, and Moving Data Note: Since the S value is not the same as the CCL and L value is 2, the RIAD set unit number for hdisk5 is D102. For dual host connection configuration, the S value for the hdisk location code is zero. However, any hdisks, associated with the D0XX and D1XX series storage system units, is distinguished by their host adapter associations. As a consequence, the CCL, by its host designation, determines the series.
Backing Up, Cloning, and Moving Data From this result, D001 and D102 are the target drives for copy in the storage system. 4. If the copy is to be a Snapshot, skip to Step 5, otherwise follow the Clone procedure described in this guide. Repeat the procedure for each target drive. As mentioned before, the hdisks associated with the storage system drives and targeted for Clone copy can remain available and logical volumes mounted in AIX.
Backing Up, Cloning, and Moving Data hdisk3 and hdisk4 are the copied drives created by the storage system disk copy procedure (Clone or Snapshot) that also became available after the AIX cfgmgr was invoked. These new physical volumes are not associated with a volume group and the PVID of both drives match those respectively in hdisk1 and hdisk2. 9. Change the new hdisks PVIDs.
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 results. 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 194 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 are 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 Reduced Membership Replacement Policy ___Normal (default) __ _No (default) ___Best performance (default) ___Fast ___Yes, missing: ___Best fit ___None Mirrorset Switches: Replacement Policy C
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 D30200 D40200 D50200 Targets D10200 D20200 D60200 Power Supply Power Supply 1 D10100 D20100 D30100 D40100 D50100 D60100 Power Supply Power Supply 0 D10000 D20000 198 D300
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 Third 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 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 Disk30000 Disk30100 Disk30200 Disk30300 Disk30400 Disk30500 Disk30800 Disk30900 Disk31000 Disk31100 Disk31200 Disk31300 Disk31400 Disk31500 Model 4214R Disk Enclosure Shelf 3 (Single-bus) DISK ID 202 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 from previous page Model 4254 Disk Enclosure Shelf 3 (Dual-bus) 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 Disk50100 Disk50200 Disk50300 Disk50400 Disk50500 Disk50800 Disk60000 Disk60100 Disk60200 Disk60300 Disk60400 Disk60500 Disk60800 DISK ID 204 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 4 (Single-bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID Disk41200 9 Disk41100 8 Disk41000 7 Disk40800 6 Disk40500 5 Disk40400 4 Disk40300 3 Disk40200 2 Disk40100 1 Disk40000 Bay 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
Subsystem Profile Templates Model 4310R Disk Enclosure Shelf 3 (Single-bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID HSG80 ACS Solution Software V8.
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 Model 4350R Disk Enclosure Shelf 4 (Single-bus) 10 SCSI ID 00 01 02 03 04 05 08 10 11 12 DISK ID HSG80 ACS Solution Software V8.
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 Model 4314R Disk Enclosure Shelf 4 (Single-bus) 14 SCSI ID 00 01 02 03 04 05 08 09 10 11 12 13 14 15 DISK ID Disk41500 13 Disk41400 12 Disk41300 11 Disk41200 10 Disk41100 9 Disk41000 8 Disk40900 7 Disk40800 6 Disk40500 5 Disk40400 4 Disk40300 3 Disk40200 2 Disk40100 1 Disk40000 Bay 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 1
Subsystem Profile Templates Model 4314R Disk Enclosure Shelf 3 (Single-bus) 14 SCSI ID 00 01 02 03 04 05 08 09 10 11 12 13 14 15 DISK ID 212 Disk31500 13 Disk31400 12 Disk31300 11 Disk31200 10 Disk31100 9 Disk31000 8 Disk30900 7 Disk30800 6 Disk30500 5 Disk30400 4 Disk30300 3 Disk30200 2 Disk30100 1 Disk30000 Bay HSG80 ACS Solution Software V8.
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.
Subsystem Profile Templates Model 4354R Disk Enclosure Shelf 3 (Dual-bus) SCSI Bus A SCSI Bus B 14 SCSI ID 00 01 02 03 04 05 08 00 01 02 03 04 05 08 DISK ID 214 Disk60800 13 Disk60500 12 Disk60400 11 Disk60300 10 Disk60200 9 Disk60100 8 Disk60000 7 Disk50800 6 Disk50500 5 Disk50400 4 Disk50300 3 Disk50200 2 Disk50100 1 Disk50000 Bay HSG80 ACS Solution Software V8.
Installing, Configuring, and Removing the Client B The following information is included in this appendix: ■ "Why Install the Client?", page 216 ■ "Before You Install the Client", page 217 ■ "Installing the Client", page 218 ■ "Installing the Integration Patch", page 219 ■ "Troubleshooting Client Installation", page 222 ■ "Adding Storage Subsystem and its Host to Navigation Tree", page 224 ■ "Removing Command Console Client", page 226 ■ "Where to Find Additional Information", page 228 HSG8
Installing, Configuring, and Removing the Client Why Install the Client? The Client monitors and manages a storage subsystem by performing the following tasks: 216 ■ 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 that 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 fails 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) V4.23. Should I Install the Integration Patch? Install this patch if your HSG80 controller uses ACS 8.6 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 Integrating Controller’s SWCC Storage Window with CIM You can open the controller’s Storage Window from within the Windows-based CIM V4.23 by doing the following: 1. Verify that you have installed the following by looking in Add/Remove Programs in Control Panel: ■ The HSG80 Storage Window for ACS V8.6 or later (Required to open the correct Storage Window for your firmware). ■ The HSG80 Storage Window V2.1 (HP StorageWorks HSG80 V2.
Installing, Configuring, and Removing the Client 2. Highlight the entry for Fibre Array Information and click Add. The Fibre Array Information entry is moved from Inactive Agents to Active Agents. HSG80 ACS Solution Software V8.
Installing, Configuring, and Removing the Client Troubleshooting Client Installation This section provides information on how to resolve some of the problems that may occur when installing the Client software: ■ ■ Invalid Network Port Assignments During Installation “There is no disk in the drive” Message Invalid Network Port Assignments During Installation SWCC Clients and Agents communicate by using sockets.
Installing, Configuring, and Removing the Client ccfabric 4989/tcp #Fibre Channel Interconnect Agent spagent 4999/tcp #HS-Series Client and Agent spagent3 4994/tcp #HSZ22 Client and Agent ccagent 4997/tcp #RA200 Client and Agent spagent2 4995/tcp #RA200 Client and Agent “There is no disk in the drive” Message When you install the Command Console Client, the software checks the shortcuts on the desktop and in the Start menu.
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 46: 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 47: Navigation window showing expanded “Atlanta” host icon 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 V2.5 User Guide. Removing Command Console Client Before you remove the Command Console Client from the computer, remove AES. This prevents 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 Command Console Client.
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. HSG80 ACS Solution Software V8.
Installing, Configuring, and Removing the Client Where to Find Additional Information You can find additional information about SWCC by referring to the online Help and to HP StorageWorks Command Console V2.5 User Guide. About the User Guide HP StorageWorks Command Console V2.5 User Guide contains additional information on how to use SWCC.
HACMP Notes for AIX C Supported Versions of HACMP HACMP is the acronym for High Availability Cluster Multi-Processing. Only HACMP/ES 4.4.1.x and 4.5 are supported with the solution software. Installing Solution Software for AIX V8.8 on HACMP Cluster The installation procedures are the same as those for a standalone node. The solution software must be loaded on each server in the cluster as if it were a standalone node.
HACMP Notes for AIX just meant as guide to you. Consult your HACMP documentation for any changes on creating a shared volume group. Note that using C-SPOC for HACMP does not work for HSG80 RAID Array devices. 1. Show a list of devices on each node in the cluster to see what device you want to create a shared volume group on by issuing the command lshsg on each node.
HACMP Notes for AIX hdisk6 none none There is no PVID for our disk on either node, so we assign a PVID on one node and then get the other node to use the same PVID. From here, you want to pick one node to do the entire configuration on and then use the other node to simply import the needed information. In this case we use node brutus as our main node and miranda as our other node. 3. On node brutus, execute the command chdev -a pv=yes -l hdisk5 4.
HACMP Notes for AIX Output from miranda: 44... You are going to want to use the greater of the two numbers, in this case 45. 7. Create the volume group on node brutus (all commands are on brutus until otherwise specified) using the command: mkvg -f -V 45 -s 32 -y sharedvg hdisk5 Note: The arguments to mkvg can and do vary. Use arguments that are appropriate to the size and purpose of your device. 8. Execute the command lsvg sharedvg to get the number of Free Physical Partitions.
HACMP Notes for AIX Note: The arguments to mklv can and do vary. Use arguments that are appropriate to the purpose of your device. 10. Create a filesystem on the logical volume now. In this case, we are going to create a filesystem that spans the whole disk. This is not mandatory. Use a command similar to: crfs -v jfs -d sharedlv -m /sharedfs Note: The arguments to crfs can and do vary. Use arguments that are appropriate to the purpose of the filesystem. 11.
HACMP Notes for AIX 234 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. 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 is on electronic devices that can only be used in a commercial environment within the United States. FCC Class B This certification label is 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 interface A set of protocols used between components, such as cables, connectors, and signal levels. 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 A physical or virtual device addressable through a target ID number. LUNs use their target bus connection to communicate on the SCSI bus. 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.
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 partition A logical division of a container, represented to the host as a logical unit. 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 HP StorageWorks cabinets.
Glossary private NL_Port An NL_Port which does not attempt login with the fabric and only communicates with NL_Ports on the same loop. program card The PCMCIA card containing the controller operating software. 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.
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 HP StorageWorks enclosures to form storage subsystems. HP 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 256 HSG80 ACS Solution Software V8.
index A B Back up, Clone, Move Data 177 backup cloning data 179 subsystem configuration 178 Index C Index ADD CONNECTIONS multiple-bus failover 48 transparent failover 46 ADD UNIT multiple-bus failover 48 transparent failover 46 adding virtual disks 228 adding a disk drive to the spareset configuration options 160 adding disk drives configuration options 160 Agent functions 124 array of disk drives 77 assigning unit numbers 46 assignment unit numbers fabric topology 159 unit qualifiers fabric topology
Index CHUNKSIZE 93 CLI configuration example 168 CLI configurations 165 CLI prompt changing fabric topology 160 Client removing 226 uninstalling 226 CLONE and SNAPSHOT 183 CLONE utility backup 179 cloning backup 179 command console LUN 39 SCSI-2 mode 49 SCSI-3 mode 49 comparison of container types 77 configuration backup 178 fabric topology devices 152, 153 multiple-bus failover cabling 145 multiple-bus failover using CLI 168 single controller cabling 135 restoring 95 rules 65 configuration options fabric
Index adding fabric topology 160 adding to the spareset fabric topology 160 array 77 corresponding storagesets 98 dividing 88 removing from the spareset fabric topology 161 displaying the current switches fabric topology 163 dividing storagesets 88 document conventions 25 prerequisites 12 related documentation 12 E enabling switches 90 equipment symbols 17 erasing metadata 96 establishing a local connection 134 F fabric topology configuration single controller cabling 135 failover 31 multiple-bus 34 tran
Index installation invalid network port assignments 222 there is no disk in the drive message 223 integrating SWCC 228 invalid network port assignments 222 J JBOD 77 L LOCATE find devices 98 location cache module 28, 29 controller 28, 29 LUN IDs general description 60 LUN presentation 47 N M maintenance port connection establishing a local connection 134 illustrated 134 mapping storagesets 98 messages there is no disk in the drive 223 mirrored caching enabling 39 illustrated 39 mirrorset switches chang
Index assigning a unit number fabric topology 159 defining 89 planning considerations 88 guidelines 89 performance 84 Physical connection, making 108 planning 61 overview 78 striped mirrorsets 87 stripesets 81 Planning a subsystem 27 planning configurations where to start 62 planning considerations 84 planning storage containers 76 planning storagesets characteristics changing switches 90 enabling switches 90 initialization switch 90 storageset switch 90 unit switch 90 switches initialization 93 storageset
Index multiple-bus failover 48 transparent failover 46 SET UNIT multiple-bus failover 48 setting controller configuration handling 95 single disk (JBOD) assigning a unit number fabric topology 159 Single-enclosure subsystem storage map template 1 198 software installation new 110 upgrade 110 storage creating map 98 profile example 196 storage configurations 61 storage map 98 Storage map template 1 198 first enclosure of multiple-enclosure subsystem 198 single enclosure subsystem 198 Storage map template 2
Index online help 228 switches changing 90 changing characteristics 90 CHUNKSIZE 93 enabling 90 mirrorsets 91 NOSAVE_CONFIGURATION 95 RAIDset 91 SAVE_CONFIGURATION 95 switches for storagesets overview 90 symbols in text 25 symbols on equipment 17 T technical support, HP 20 templates subsystem profile 195 terminology other controller 29 this controller 29 text symbols 25 Third enclosure of multiple-enclosure subsystem storage map template 3 200 this controller 29 transparent failover 31 ADD CONNECTIONS 46
Index write-through caching 264 general description 38 HSG80 ACS Solution Software V8.
