Optima 1500

User's Guide

REFERENCE 86 A1 61 FA 01

StoreWay Optima

StoreWay Optima Optima 1500

User's Guide

Hardware
February 2010 BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE

REFERENCE 86 A1 61 FA 01

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 2008-2010 Printed in France

Trademarks and Acknowledgements

We acknowledge the rights of the proprietors of the trademarks mentioned in this manual. All brand names and software and hardware product names are subject to trademark and/or patent protection. Quoting of brand and product names is for information purposes only and does not represent trademark misuse.

The information in this document is subject to change without notice. Bull will not be liable for errors contained herein, or for incidental or consequential damages in connection with the use of this material.

Notice
NOTE: Read this manual carefully before using the unit. Keep this manual nearby as a handy reference and refer to the CAUTION and WARNING statements whenever necessary. Trademarks and registered trademarks: UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows, and Windows Vista are trademarks or registered trademarks of Microsoft Corporation in the United States and other countries. Linux is a trademark or registered trademark of Linus Torvalds in the United States and other countries. Java and JRE (Java 2 Runtime Environment) are registered trademarks of Sun Microsystems, Inc. All other trademarks and trade names are the property of their respective owners. Cautions: No part of this manual may be reproduced in any form without prior written consent from Bull. The information in this manual is subject to change without notice. This manual was created with the greatest care, but in the event that any technical or editorial errors or omissions are found, contact your dealer. Bull shall not be liable for any claims of loss or lost profits caused by the use of this disk array unit, regardless of mentioned above. This unit is not intended to be installed in installations or equipment associated with human life, such as medical equipment, atomic installations or equipment, aviation and space equipment, transportation installations or equipment or to be installed in and used to control installations or equipment requiring high reliability. If this unit is used in such installations, equipment, or control systems, Bull shall not be liable for any accident leading to personal injury or death or any property damage that may occur. If you transfer (or sell) the disk array unit to a third party, deliver this manual along with it. Audience: This manual is intended for technical professionals who are experienced with the following: System and storage configurations. Microsoft and Linux-Unix administrative procedures.

About this guide

This guide explains setting up StoreWay Optima1500, installing Storage Manager, and ControlCommand for the sample recommended configuration listed below. StoreWay Optima1500
LAN

Management server

SAN

Fibre Channel
Production server MultiPath ControlCommand

Storage Manager Server

*1

LAN

Client

*1 Included as a product in BaseProduct

Storage Manager Client
*1

Figure i.

Sample of Recommended Configuration

This guide also documents procedures for initial setups of the products based on the sample recommended configuration in the figure. If your configuration differs to Figure i, read the appropriate changes into the procedures. This guide explains functions implemented by the following program products: - Storage Manager Ver5.3 or later - Storage BaseProduct Ver5.3 or later - Storage Manager AccessControl Note. When using old version, please refer to the users guide of corresponding version.

ii

Conventions
The following symbols are used throughout this guide. Display Types Type Description Indicates that failure to follow directions could result in damage to equipment or data. Provides clarifying information or specific instructions. Provides additional information.

WARNING

Indicates that there is a risk of death, serious injury, or burns. Indicates that there is a risk of injury and/or loss of assets. Table i. Symbols of this Guide

CAUTION

The following acronyms are used throughout this guide. Acronym Disk array unit Disk enclosure Disk drive Expanded name StoreWay Optima1500 shown on the front cover Extended SAS/SATA disk enclosure Hard disk drive with an exclusive tray. (SAS drive) (SATA drive) * SATA is referred to as ATA in the software. Exclusive tray (used for an uninstalled hard disk drive) Fibre Channel controller LAN interface Disk array unit Controller in the DAC portion Extended battery backup unit Disk enclosure Power supply (unit) Fibre Channel Cable Fibre Channel Switch Physical Disk Acronyms Used in this Guide

Dummy tray Host bus adapter (HBA) Network Interface Card (NIC) DAC (disk array controller) CONT (controller) Extended BBU DE (disk enclosure) PS (power supply) FC Cable FC Switch PD Table ii.

iii

Note. Shorter terms used throughout the document, but unless otherwise noted, are always referring to Storage Manager Software Products and manuals. The capacity is calculated based on units of 1024 (for example 1 KB = 1024 bytes) unless otherwise specified.

iv

Safety Precautions
Carefully read and understand these Safety Precautions before using this unit in order to use it safely. Risks and necessary actions to reduce risks are indicated individually by the following symbols. Indicates that smoking and/or ignition may occur. Indicates that you may be electrically shocked. Indicates proper procedure for safety. Indicates that the plugs of power cords should be removed for safety. Indicates general prohibitions. Indicates that fire should not be brought near devices for safety. Indicates that devices are prohibited from being disassembled for safety. Table iii. Symbols for Safety

Notes on Safety
Before using the disk array unit, carefully read and understand these Notes on Safety for safe use of the unit.

WARNING
Never use the disk array unit in a location where there is flammable gas or combustible material. Doing so could cause a fire or explosion. Do not use the disk array unit in a location that is unusually damp or a location where water is handled. Doing so could cause failure, electric shock, or fire. Do not install the disk array unit in a dusty location. Remove dust adhering to the unit, outlets, and power cord plugs. Using these with dust on them could cause a fire. Do not perform any disassembly or rebuilding other than that described in this manual. Doing so could cause failure, electric shock, or fire. Do not install the disk array unit in a location where there is direct sunlight or near a heater or other object that generates heat. Doing so could cause failure, fire, or electric shock. Do not handle the disk array unit with wet hands. Doing so could cause electric shock. Do not set up the disk array unit in an unstable location. If it fell, it could cause failure or injury. Install the disk array unit so that vent holes are not blocked. Blocking the vent holes could cause the temperature inside the unit to rise, leading to failure or fire. If abnormalities such as smoking or odors occur, turn off the power to the disk array unit and remove the power plug from the outlet. Immediately request inspection and repair from your sales or maintenance service agent. When moving the disk array unit, do so after removing power cords and cables. Moving it while these are connected could cause failure, electric shock, or fire. Do not put your hands into the disk array unit. If you must put your hands into the unit, do so after turning off the power and removing power plugs from outlets. Be careful not to catch or bump your fingers.

vi

WARNING
Warnings concerning power Do not overload an outlet with the power cords of the disk array unit and extended BBU. Doing so could cause a fire. Do not put heavy objects on the power cords of the disk array unit or extended BBU. If the covering of a power cord is torn, it could cause a fire or electric shock. Although the disk array unit and extended BBU are compatible with AC 100 V-AC 240 V, the accompanying power cords are as follows according to model number. Model numbers NF5111-S*/NF5131-S*: For AC 100 V Model numbers NF5111-N*/NF5131-N*: For AC 200 V When using the accompanying power cord, use it with AC 100 V (50/60 Hz) or AC 200 V (50/60 Hz), depending on the product model number. Using it with a different voltage could cause electric shock, smoke, or fire. Insert the plug of the power cord of the disk array unit or extended BBU in an outlet securely. Provide sufficient slack in the power cord so that excessive force is not placed on the power cord plug or the power cord. If the power cord is disconnected during operation, it could cause data loss or failure. To prevent electric shock, connect the power cords of the disk array unit and extended BBU to outlets that have ground terminals. Grounding to an object such as a gas pipe is hazardous and must never be done. Warnings concerning batteries The batteries of the disk array unit could explode if brought near flames or soaked in water. When lithium batteries (button batteries) and nickel metal hydride batteries no longer operate correctly due to their life spans, do not disassemble, exchange, or charge them yourself, but contact your sales or maintenance service agent.

vii

CAUTION
It is recommended that setup and maintenance of the disk array unit be entrusted to service engineers with specialized knowledge from your maintenance service agent. For details, contact your sales agent. Although installation and maintenance of the disk array unit can be done by customers themselves, they must understand that Bull and its sales agents shall not assume responsibility for any damage to the disk array unit, its components, or connected devices or for any outcome occurring during, before, or after operation when customers do these things themselves. When installing the disk array unit, follow the documentation in the Disk Array Unit Installation Guide. The Disk Array Unit Installation Guide is included in the accompanying CD. Because the disk array unit is precision equipment, do not expose it to strong vibrations or shock, regardless of whether the power is on or off. Do not disconnect a disk drive, cable, or other part while the power is on. If customers themselves change connections of the disk array unit system once it has been configured, there is a risk of operation ceasing or data disappearing. To change connections, it is recommended that you ask your maintenance service agent. To expand the system, turn off the power of the disk array unit and remove power cords from outlets. Not doing so could cause failure or electric shock.

viii

CAUTION
Be sure to perform backup of the data of the disk array unit regularly. It is recommended that particularly important files be backed up on media such as magnetic tape. Reason: The disk array unit, which is available on strictly hard failures, cannot cope with unexpected vibrations or shocks, power cuts due to electrical outages, or soft faults. Damage from soft faults can be kept to a minimum by performing backups. A hard failure is a phenomenon such as a disk drive being damaged or a disk drive being unable to rotate. A soft fault is a phenomenon such as a human error or a host malfunctioning. It is recommended that the latest software and firmware for the disk array unit be used. The disk array unit could be destroyed if you power it off or it becomes powered off while updating its firmware. Be sure that it does not become powered off during a firmware update. Do not power off the disk array unit or the host unit or reset the host unit if the ACTIVE/FAULT LED (green or orange) of a disk drive of the disk array unit is blinking, if the host unit shows that a disk is being accessed, or if it shows that initialization is in progress. If a fault occurs in the disk array unit, the SERVICE LED of the disk array unit and the FAULT LED corresponding to the faulted component illuminate. When faults occur, contact your sales or maintenance service agent. Cautions concerning power If a component of the disk array unit normally is not fully inserted or is loose, or if a cable normally is not fully inserted or is loose, it could cause failure. Always connect all power supplies of the disk array unit and pass current through them. If no current is passed, data is not duplicated and data may be lost. A power supply that is not connected is judged to be abnormal.

ix

CAUTION
Cautions concerning DC power This equipment is designed to permit the connection of the earthed conductor of the d.c. supply circuit to the earthing conductor at the equipment. If this connection is made, all of the following conditions must be met: - This equipment shall be connected to directly to the d.c. supply system earthing electrode conductor or to a bonding jumper from an earthing terminal bar or bus to which the d.c. supply system earthing electrode conductor is connected. - This equipment shall be located in the same immediate area (such as, adjacent cabinets) as any other equipment that has a connection between the earthed conductor of the same d.c. supply circuit and the earthing conductor, and also the point of earthing of the d.c. system. The d.c. system shall not be earthed elsewhere. - The d.c. supply source is to be located within the same premises as the equipment. - Switching or disconnecting devices shall not be in the earthed circuit conductor between the d.c. source and the point of connection of the earthing electrode conductor. Cautions concerning disk drives A disk drive is an electronic device. When handling one, take measures against static electricity, such as using a wrist strap. If you do not have a wrist strap, firmly place one hand on the unpainted metal surface of the disk drive before handling it. Mount three disk drives in the disk array unit at locations 00, 01, and 02 of the unit. If these are not mounted, data may be lost. Do not remove more than one of the drives at locations 00, 01, and 02 of the disk array unit while the power to the unit is off. Moreover, do not turn off the power if more than one of the drives at locations 00, 01, and 02 are removed. If you remove drives, data may be lost. When adding disk drives or changing the locations at which disk drives are mounted, be sure to work on one at a time in powering them on. Install the next disk drive after confirming that the installed disk drive is ready. When installing a disk drive, lock the ejector after it has been inserted fully. Not inserting it fully may cause failure. Do not change the locations at which disk drives are installed if logical disks have been configured. Data may be lost.

CAUTION
Cautions concerning batteries The batteries of the disk array unit have a life span. If batteries are used past their life span, the backup time cannot be guaranteed and user data may be destroyed on a power outage. When replacing batteries due to their life span, a request for battery purchase and maintenance must be made. Ask your sales or maintenance service agent for details. As the life span of this equipments battery, it will be short if there is many times of backup. The life span of battery is set up just for the condition of unexpected power supply cutting like a power failure. For normal use, please cut the power supply according to a regular power supply cutting procedure. (There is an exception partly. For the details, please refer to 5.2 Notes on Turning Off the AC Power.) In addition, the life span of this equipments battery shortens with condition of a high temperature. The life span is for 5 years with condition of 25 degrees Celsius, but with condition of plus 10 degrees Celsius the life span becomes about a half of that (2 years and a half). Performance may deteriorate while charging the battery of the disk array unit. Reason: Fast writing in which a cache is used is not done unless the battery is fully charged, since backup time on a power outage cannot be guaranteed. When disposing of batteries of the disk array unit, do so in accordance with local government regulations. For details, contact your local government. The unit is equipped with batteries as follows. Each controller: Lithium battery (button battery) Each controller: Nickel metal hydride battery Each extended BBU: Nickel metal hydride battery

xi

CAUTION
Cautions concerning cables For the FC cables and SAS cables used in connections in the disk array unit, use cables and cable lengths specified by Bull. If cables other than those specified are used, data can be lost. Check cable specifications and connectors so that there will be no wiring errors. If the unit were operated with wiring errors, data could be lost. When correcting wiring, it may be necessary to erase all disk drive data. When installing, confirm that there is no bending or other damage, dust adhesion, or dirt on connectors or contacts. Do not forcibly insert cable connectors. A connector cannot be connected unless it is inserted with the correct orientation and at the correct angle. When inserted correctly, they go in smoothly without applying excessive force. If you cannot insert one successfully, do not forcibly insert it, but check the orientation and shape of the connector. Handle cable connectors carefully so that they are not dropped on a floor and damaged. Do not place excessive strain on the connector portion or the cable portion of an installed cable. Do not deform a cable by stepping on it or putting heavy objects on it. Treat optical fiber cables with care and respect. Rough treatment of optical fiber cables could cause deterioration of characteristics or mechanical damage (line disconnection). (How to treat optical fiber cables) 1. Ensure a minimum bending radius of 30 mm. 2. Do not drop a cable on the floor or otherwise shock it. 3. If not connecting a cable, place caps on it. When connecting a cable, do not discard the caps but save them (as well as those for connectors on the unit). Optical power may be attenuated by dust or dirt present when inserting an optical fiber cable in a controller of the disk array unit and result in data errors. When inserting a cable, always be sure to clean the optical connector using the following procedure. (Cleaning method) 1. Spray air or another parts cleaning gas on the optical connector for several seconds. 2. Wipe the optical connector lightly several times with a non-fibrous cloth wetted with isopropyl alcohol. 3. Spray parts cleaning gas on the optical connector for several seconds again.

xii

CAUTION
Treat SAS cables with care and respect. Rough treatment of the cables may cause deterioration of characteristics or mechanical damage (line disconnection). (How to treat SAS cables) 1. Make allowance for cable forming. 2. Do not forcibly stretch a cable or otherwise stress it. 3. Ensure a minimum bending radius of 80 mm. Cautions concerning LAN In connecting to the Storage Manager, be sure to connect to a LAN port and not to a MNT port. Assign different addresses for the IP address of the CONT#0 LAN and the IP address of the CONT#1 LAN. This disk array unit does not support several features, including teaming. Set Auto Detect for servers, hubs, and other devices connected to the LAN. Reason: Connecting to a device in full duplex mode could cause abnormal operation. If settings do not match, it may be impossible to connect intermittently even if a connection is established temporarily. To set Speed and Detect settings other than Auto Detect, ask your sales or maintenance service agent. Use a shielded straight cable to connect a LAN cable via a hub or a shielded cross cable to connect it directly. Do not place excessive strain on the cable portion or connector portion of an installed LAN cable. Do not deform the cable by stepping on it or putting heavy objects on it.

xiii

CAUTION
Cautions concerning UPS Constructing a system configuration in which a UPS is used allows the system to operate stably even if an accidental power interruption or momentary AC power outage occurs. Consult your sales or maintenance service agent concerning configuring a system in which a UPS is used. A disk array unit and a directly connected UPS can be linked only if the host is an NX server. Consult your sales or maintenance service agent concerning configuring a system in which a UPS is used. Do not use a UPS other than the ones specified. Operation is not guaranteed if you use one other than one that is specified. Do not connect a UPS to the UPS interface without the AC power turned on. This state is equivalent to a power interruption and mistakenly causes processing for power interruptions to operate.

Perchlorate Material special handling may apply. See www.dtsc.ca.gov/hazardouswaste/perchlorate. This only applies to California, USA.

xiv

Indication on Safety
The warning label is attached to components with possible danger or their vicinity in your disk array unit to inform the user that a hazardous situation may arise when operating the disk array unit. (Do not intentionally remove or damage any of the labels.) If you find any labels totally/partially removed or illegible due to damage, contact your sales representative. Disk Array Unit

xv

AC Power Supply

xvi

DC Power Supply

xvii

Controller

xviii

Battery

xix

Disk Enclosure

xx

Extended Battery Backup Unit

Extended Battery Backup Unit Power Supply

xxi

AC Power Cable

DC Power Cable

xxii

Related Documentation
In addition to this guide, see the following document for more information:

Disk Array Unit Setup Guide Disk Array Unit Installation Guide Storage Manager Installation Guide Storage Manager Users Manual ControlCommand on Windows Installation Guide ControlCommand on Linux Installation Guide Configuration Setting Tool Users Manual (GUI) Data Replication Users Manual (Function Guide) Snapshot Users Manual (Function Guide) StoreWay MultiPath for Windows Installation Guide StoreWay MultiPath for Linux Installation Guide StoreWay MultiPath Users Manual (Windows) StoreWay MultiPath Users Manual (Linux)

xxiii

Contents
1. Overview ............................................................................................................. 1
1.1. Features....................................................................................................................................... 1 1.2. Unit Life Span and Maintenance Period ................................................................................... 2 1.3. Disposing of Equipment ............................................................................................................ 3

2. Install Steps........................................................................................................... 4
2.1. Set up Procedures...................................................................................................................... 4 2.2. Preparation.................................................................................................................................. 5 2.3. Unpacking ................................................................................................................................... 7 2.4. Checking Package Contents ..................................................................................................... 8 2.4.1. Packing Slip ......................................................................................................................... 8 2.5. Appearance and Features........................................................................................................ 10 2.5.1. Disk Array Unit................................................................................................................... 10 2.5.2. Disk Enclosure................................................................................................................... 18 2.5.3. Extended BBU.................................................................................................................... 24 2.6. Installation................................................................................................................................. 26 2.6.1. Mounting Disk Array Unit and Disk Enclosure............................................................... 26 2.6.2. Installation of Disk Drives ................................................................................................ 31 2.6.3. Setting AC Operating Mode.............................................................................................. 39 2.6.4. Installing and Removing Front Mask............................................................................... 40 2.6.5. Mounting an Extended BBU on a Rack ........................................................................... 43 2.7. Cable Connections ................................................................................................................... 49 2.7.1. Notes on Cable Connections ........................................................................................... 49 2.7.2. Connection of Disk Enclosure ......................................................................................... 50 2.7.3. SAS Cable Connection and DE and PD Numbers.......................................................... 52 2.7.4. Connection of Disk Array Unit to Production Server .................................................... 54 2.7.5. Connecting LAN Cables ................................................................................................... 56 2.7.6. Connection of Extended BBU and Controllers .............................................................. 58 2.7.7. Connecting Power Cables ................................................................................................ 59 2.8. Turning On Unit Power............................................................................................................. 61 2.8.1. AC Operating Mode ........................................................................................................... 61 2.8.2. Power-On Procedure......................................................................................................... 61 2.8.3. Notes on Turning On the AC Power ................................................................................ 62 2.8.4. Power Control Methods Beside Power Button............................................................... 63

3. Software Installation........................................................................................... 65
3.1. Software Installation in a Windows Environment ................................................................. 67 3.1.1. Installation and Startup of Storage Manager Server ..................................................... 67 3.1.2. Installation of Volume List Command ............................................................................. 68 3.1.3. Installation of ControlCommand...................................................................................... 69 3.2. Software Installation in a Linux Environment ....................................................................... 71 3.2.1. Installation and Startup of Storage Manager Server ..................................................... 71 3.2.2. Installation of Volume List Command ............................................................................. 74 3.2.3. Installation of ControlCommand...................................................................................... 76 3.3. Installation of the Storage Manager Client ............................................................................ 78 3.3.1. Configurations Offered by the Storage Manager Client ................................................ 78 3.3.2. Installation of Storage Manager Client............................................................................ 79 3.3.3. Starting the Storage Manager Client ............................................................................... 85

xxiv

4. Initialization of Disk Array.................................................................................. 87

4.1. Collection of Host Information on Production Server .......................................................... 88 4.1.1. Automatic Collection in Windows Environment ............................................................ 90 4.1.2. Host Information Collection Using File Output in Windows Environment.................. 90 4.1.3. Host Information Collection Using File Output in Linux Environment ........................ 91 4.2. Initialization Using Initialization Wizard ................................................................................. 92 4.2.1. Initialization Wizard ........................................................................................................... 92 4.2.2. Resetting After Initialization Wizard Suspension ........................................................ 124 4.3. Host Information Confirmation ............................................................................................. 132 4.3.1. Host Information Collection and Storage Using File Output ...................................... 133 4.3.2. Host Information Confirmation Using Storage Manager Client (Web GUI) ............... 135 4.4. Logical Disk Addition and Binding ....................................................................................... 137 4.5. Connection Confirmation from Production Server............................................................. 141 4.5.1. Connection Confirmation in a Windows Environment ................................................ 141 4.5.2. Connection Confirmation in a Linux Environment ...................................................... 144

5. Power-Off Procedure........................................................................................ 148

5.1. Power-Off Procedure.............................................................................................................. 148 5.2. Notes on Turning Off the AC Power ..................................................................................... 149 5.3. Auto-Shutdown Function....................................................................................................... 150

6. Expansion Methods.......................................................................................... 151

6.1. Notes on Expansion ............................................................................................................... 151 6.2. Controller ................................................................................................................................ 152 6.3. Disk Drive ................................................................................................................................ 153 6.4. Disk Enclosure........................................................................................................................ 153 6.5. Extended BBU......................................................................................................................... 154 6.6. Expansion Ports ..................................................................................................................... 155 6.7. Changing DIP Switches ......................................................................................................... 159 6.8. Changing Setting by Storage Manager ................................................................................ 162 6.8.1. Changing Setting by Initialization Wizard..................................................................... 162 6.8.2. Individual Setting by Configuration Setting and Easy Configuration........................ 168

7. Troubleshooting ............................................................................................... 170

7.1. Before You Call ....................................................................................................................... 170 7.2. Contacts for Questions and Consultation ........................................................................... 170 7.3. Troubleshooting According to Device Conditions.............................................................. 171 7.4. Errors on Software Installation ............................................................................................. 176 7.5. Errors on Using Storage Manager Server or Storage Manager Client...................... 177 7.6. Troubleshooting in Initialization Wizard/Easy Configuration ............................................ 178 7.6.1. Changing Network Settings for Monitoring Disk Arrays from Storage Manager ..... 191

Appendix.A. Notes on Using MSCS (Microsoft Cluster Service) in a Windows Server 2003 Environment.............................................. 198 Appendix.B. Notes on Connecting FC Switches in a Fault Tolerant Server Environment ................................................................................... 202 Appendix.C. Initialization of the Disk Array Using Initialization File................ 203 Appendix.D. Technical Specifications ................................................................ 220 Appendix.E. LED Checks ..................................................................................... 223 Index ......................................................................................................... 231

xxv

1.Overview
1.1.Features
The features of this disk array unit are shown below. <High performance, large capacity> Fibre channel (FC-AL/Fabric, 400 MB/s) is employed in the host interface. Disk drives employed are 73 GB (15,000 rpm), 147 GB (15,000 rpm), 300 GB (15,000 rpm), 450 GB (15,000 rpm), or 600GB (15,000 rpm) SAS disk drives, and 500 GB (7200 rpm), 750 GB (7200 rpm), 1TB (7200 rpm), or 2TB (7200 rpm) SATA disk drives, of which a maximum of 144 drives can be implemented. SAS disk drives and SATA disk drives can be mixed in a disk enclosure. Connection as a Windows, Linux, HP-UX, Solaris, or AIX server storage system is possible.

<High reliability, high availability> Controllers, caches, power supplies, fans, and other major components are made redundant. Note. In Single Controller model, the controller and cache are not made redundant. Caches are double-written between controllers so that even if one controller fails, data is preserved in the cache of another controller. Note. In Single Controller model, caches are not double-written. In Single Controller model, the initial value of the write cache function is OFF. Data in a cache is held a standard 24 hours by the battery. By adding an optional extended battery backup unit, the backup time can be extended to a maximum of 72 hours. RAID-1, 3, 3DP, 5, 10, 50, 6, and TM are supported. Even if one disk drive fails, continuous operation is possible and data is not lost. Note. RAID-5/50, RAID-6, and TM are supported for SATA disk drives. Multiple hot spare disks can be established.

<Operation management> - Configuration, status display, and status monitoring can be performed easily using Storage Manager. Note. In order to use this disk array unit, you must purchase the program product Storage BaseProduct separately. Storage Manager is included in BaseProduct.

1.2.Unit Life Span and Maintenance Period

The unit life span and maintenance period after production ends for the disk array unit are as follows. Parts used in the disk array unit include parts that must be exchanged due to their life spans (such as cooling fans and battery backup units). Since life spans may be shorter than five years depending on the environment in which the disk array unit is used, it is recommended that parts be exchanged regularly. Contact your maintenance service agent regarding exchanges and life spans. - Unit life span: - Maintenance period: Caution. 5 years 5 years after production ends

If you continue to use the unit past the unit life span, be sure to perform overhaul (for a fee) in addition to contracted hardware maintenance. Overhaul can be done only once.

Note that repair may not be possible in the cases below. Moreover, a fee may be charged even if within the warranty period. - Stained goods, dropped goods, goods damaged by mishandling - Goods damaged by mishandling in storage or shipping - Items touched by the user - Items whose life spans are over - Goods damaged by reason of earthquake, lightning, fire, or other disaster, and goods damaged due to an accident or other external cause < Parts that have life spans > - Fan (Power supply): - Battery: - Extended BBU: 50,000 hours 5 years 5 years

Caution.

As backup frequency increases, the battery life span of this unit becomes shorter. This life span is calculated considering only accidental power disconnection such as power outage. Be sure to turn of the power according to the proper power-off procedure. The battery life span of this unit also becomes shorter when it is used at high temperatures. The life span is about five years when the unit is used under conditions in which the ambient temperature is 25C (77F), but will be reduced to approximately half (about two years and six months) when the ambient temperature rises by 10C (18F).

1.3.Disposing of Equipment
Lithium batteries and nickel metal hydride batteries are used in the disk array unit. Batteries are implemented as follows. Each controller: Lithium battery (Button battery) Each controller: Nickel metal hydride battery Extended BBU: Nickel metal hydride battery

Consult the sales agent from whom you purchase them or your maintenance service agent concerning disposal of the unit (including battery disposal (and exchange)).

2.Install Steps
2.1.Set up Procedures
Execute setup tasks according to the following procedure. Refer to 2.2 Preparation for details. Refer to 2.3 Unpacking for details. Refer to 2.4 Checking Package Contents for details. Refer to 2.6 Installation for details. Refer to 2.7 Cable Connections for details. Refer to 2.8 Turning On Unit Power for details. Refer to Chapter 3 Software Installation for details. Refer to Chapter 4 Initialization of Disk Array for details.

Preparation Unpacking Checking package contents Installation Connections Turning ON Unit Power Installation of Software Initialization of Disk Array

Finish

2.2.Preparation
For this setup task, the following supplies and tools are required. Since preparation is required at the production server connecting the disk array, also perform that in advance.

1. Prepare the followings:

LAN cable (shielded) - A cross cable to connect the disk array unit to the management server directly. - A straight cable to connect the disk array unit to the management server via a hub. Machines - Management server - production server - client IP Addresses Prepare as many IP addresses to assign to the disk array unit as there are connection ports. Also prepare the subnet mask and gateway address after confirming them with the network administrator. Tools - Phillips screwdriver (No. 1) - installation CD

2. Perform the setup tasks below at the production server connecting the disk array.

Begin preparation

1. Confirm host bus adapter WWPN

2. Install host bus adapter

3. Install host bus adapter driver

Production server

4. Install StoreWay MultiPath

(If installing StoreWay MultiPath)

End preparation

Figure 2.1

Preparation Steps

1. Confirming the WWPN (World Wide Port Name) of the host bus adapter (Fibre Channel controller) This setup is only for WWN mode (using the WWPN of the host bus adapter to allocate LUN to the production server) as the AccessControl setup mode. During the setup task, the WWPN of the host bus adapter installed on the production server is obtained using software. However, it is recommended that you make note of it and provide for a substitute task (confirmation of the server expansion slot location at which the host bus adapter is installed and the WWPN) in case of a host bus adapter fault. The confirmed WWPN of the host bus adapter may have to be input manually if the WWPN of the host bus adapter cannot be obtained by the software.

2. Installing the host bus adapter If a host zbus adapter has already been installed in the production server, this task is not necessary. Install the host bus adapter in the production server according to the host bus adapter and production server users manuals.

3. Installing the host bus adapter driver If a driver for the host bus adapter that is installed in the production server has already been installed and set up, this task is not necessary. Perform the tasks of host bus adapter driver installation and setup according to the manual that came with the host bus adapter product installed in the server.

4. Installing StoreWay MultiPath (Windows/Linux) If StoreWay MultiPath has already been installed and set up for the production server, or if StoreWay MultiPath is not being installed, this task is not necessary. * To perform this task, installation and setup of the host bus adapter driver must be done first. Perform the tasks of StoreWay MultiPath installation and setup according to the StoreWay MultiPath Users Manual that comes with the StoreWay MultiPath product, or the StoreWay MultiPath Installation Guide.

2.3.Unpacking
This is the task of unpacking a delivered disk array unit and removing the materials used to protect the unit for transportation. In order to prevent condensation, unpack them after acclimating the disk array unit to the ambient temperature sufficiently (approximately nine hours). In unpacking, take the disk array unit itself and the accessories out of the carton in such a way that they are not exposed to excessive shocks. The disk array unit is extremely heavy. If only one or two persons lift it when taking it out of the carton, they may hurt their backs. At least three people should take the disk array unit out of the carton by supporting the bottom of the unit and not holding on to projections such as power supplies and controllers. The carton is designed to transport precision equipment. Do not discard the carton because it will be needed when returning the unit to the factory for repair.

2.4.Checking Package Contents

Remove the contents, making sure you have everything listed below. If anything is missing, contact your sales representative For the necessary program product, such as ControlCommand and StoreWay MultiPath, refer to the list of included items which is attached to each product.

2.4.1.Packing Slip
< Disk Array > Rack mount kit Front Mask Dx-xx microprogram (CD-R) Installation Guide Setup Guide Users Guide Cable Label T&D Program (CD-R) List of Included Items

(*) (*) (*) (*) (*) (*)

(*) Non-attached depending on a model < Disk Enclosure > (Optional parts) Rack mount kit Front Mask SAS cable (2) (1 m) Cable Label Location Label List of Included Items (*) Non-attached depending on a model Note. SAS/SATA disk enclosure (NF5021-xE60E) is not an accessory of the disk array unit itself. When purchasing disk enclosure as an optional part, it will be packed separately. (*)

< Extended Battery Backup Unit > (Optional parts) Extended battery backup unit (2) Rack mount kit Front Mask BBU-CONT connection cable(2) (1 m) List of Included Items

Note. Extended battery backup unit (NF5021-xZ021E) is not an accessory of the disk array unit itself. When purchasing this as an optional part, it will be packed separately.

Listed Accessory - For use with Disk Array Unit Model DAS04xUy (where x=0-9, A-Z, y=A-Z or blank) only.

2.5.Appearance and Features

2.5.1.Disk Array Unit
This section describes the names and functions of each portion of the disk array unit.

2.5.1.1.Front View
2. SERVICE LED
1. POWER LED

Figure 2.2

Front View of the Disk Array Unit

Note. Refer to 2.6.4 Installing and Removing Front Mask for a description of how to remove the front mask.

2.5.1.2.Front View (viewed when front mask is removed)

2. SERVICE LED 1. POWER LED

4. ACTIVE/FAULT LED 3. Disk drive/Dummy tray

Figure 2.3 1. POWER LED (green)

Front View of the Disk Array Unit Without Front Mask

The POWER LED illuminates to indicate normal operation.

10

2.

SERVICE LED (orange) The SERVICE LED illuminates to indicate that the entire unit containing the disk enclosure requires maintenance. The LED blinks to indicate that the power-on sequence is in progress. The LED turns off to indicate that the power-on or power-off sequence is completed.

POWER LED ON ON

ON

ON ON Blinking OFF Table 2.1 3.

Description Normal operation Requesting maintenance or processing a maintenance task ON (such as during recovery) It is one of the following. Check the controller LEDs. - Power-on sequence in progress - Online download sequence in progress Blinking - Automatic download sequence in progress Note. Do not turn off power while a sequence is in progress. ON for 5 sec. and Requesting maintenance (battery backup failure; write OFF for 7 sec. data may have been lost) ON for 0.5 sec. and Storage Manager client instructs by blinking of the OFF for 0.5 sec. Service LED. Shutdown sequence complete OFF Auto shutdown sequence complete AC power can be turned off. OFF Powered off ON/OFF Status of POWER and SERVICE LED of Disk Array Unit

SERVICE LED OFF

Disk drive/Dummy carrier A single disk enclosure is equipped with 12 disk drives/dummy carriers. Disk drive: Dummy carrier: Hard disk drive (HDD) with exclusive carrier Dummy carrier that fills the hole of HDD

< Locations and disk drive numbers > 00 04 08 01 05 09 02 06 0A 03 07 0B

4.

ACTIVE/FAULT LED (green/orange) A single ACTIVE/FAULT LED is installed on each disk drive/dummy carrier. The LEDs indicate the states of the respective disk drives.

11

<Status display> Indicates the status of the disk drive located to the right. Indicates the status of the disk drive located to the left.

ACTIVE/FAULT LED Green : ON Green : Blinking Green/orange : Blinking in turn Orange only : Blinking Orange : ON Table 2.2

Status Normal status (ready) Normal status (accessing) Rebuilding HDD low power state Abnormal status

ON/OFF Status of ACTIVE/FAULT LED of Disk Array Unit

2.5.1.3.Rear View
1. Power supply (PS1) 1. Power supply (PS0)

2. Controller (CONT1)

2. Controller (CONT0)

Figure 2.4 1. Power supplies (PS0/PS1)

Rear View of the Disk Array Unit

A single disk array unit is equipped with two power supplies. Supply AC power to both of the power supplies. 2. Controllers (CONT0/CONT1) A single disk array unit can be equipped with up to two controllers.

12

2.5.1.4.Power Supply
AC Power Supply
1. Receptacle 5. Ejector

2. POWER GOOD LED 6. Power cable clamp

4. FAN FAULT LED

3. POWER FAULT LED

DC Power Supply
1. Receptacle 5. Ejector

2.POWER GOOD LED

4.FAN FAULT LED

3.POWER FAULT LED

Figure 2.5

Power Supply

1.

Receptacle Connect the power cable unit to the receptacle to supply power.

2.

POWER GOOD LED (green) The LED illuminates to indicate that power is being supplied to the unit.

3.

POWER FAULT LED (orange) The POWER FAULT LED illuminates to indicate that the power supply (excluding the fan) is faulted. Blinking indicates a temperature abnormality inside the power supply or that a controller has not been installed to the chassis. This LED is effective when power is being supplied to either PS0 or PS1.

13

4.

FAN FAULT LED (orange) The FAN FAULT LED illuminates to indicate that the fan is faulted. The power supply FAN operates when power is being supplied to either PS0 or PS1. This LED is effective when power is being supplied to either PS0 or PS1.

5.

Ejector The ejector is used in installing or removing the power supply.

6.

Power cable clamp The power cable clamp is a mechanism that prevents the power cable from being disconnected unintentionally.

14

2.5.1.5.Controller
11. Ejector 10. Modem connector 12. HPE FAULT LED 13. HPE 15. MC Slot. 11. Ejector 1. Power button

14. BBU FAULT LED

8. SAS connector 2. MNT connector 9. Extended BBU connector 6. BACKUP LED 4. READY LED 3. LAN connector 5. FAULT LED 7. HP connector

Figure 2.6 1. Power button

Controller

The power button is used to turn the power on or off. 2. MNT connector The MNT connector is used to connect the controller to a maintenance PC. (This is not used.) 3. LAN connector The LAN connector is used to connect the controller to Storage Manager or a LAN for SNMP. There is a LINK LED (left) and an ACTIVE LED (right) on the connector. - LINK LED (LNK) (green) The LINK LED indicates that a LAN is physically connected. Depending on the type of hub, it may not illuminate or it may blink. - ACTIVE LED (orange) The ACTIVE LED illuminates during a TCP protocol connection from a host. It illuminates if monitoring is being done by Storage Manager. 4. READY LED (green) The READY LED illuminates during the power-on sequence. The READY LED blinks during normal operation. Rapid blinking indicates that power was disrupted.

15

5.

FAULT LED (orange) The FAULT LED illuminates to indicate that a fault occurred in the controller. READY LED FAULT LED State Blinking OFF Normal operation ON OFF Starting Blinking rapidly OFF Shutdown sequence in progress (2 times/second) Auto shutdown*1 sequence is running Blinking asynchronously Online/automatic download sequence in progress Blinking synchronously In download mode ON ON Occurrence of fault ON Blinking Waiting for disk enclosure power-on Blinking ON Disk interface is disable OFF OFF Powered off Table 2.3 READY LED and FAULT LED of Controller *1 It shifts automatically to this mode when the cutting condition of the host connection port continues for five minutes, and it prepares for the power supply cutting. Moreover, it usually returns to the state when the host connection port recovers.

6.

BACKUP LED (orange) The BACKUP LED blinks to indicate the battery backup state.

7.

HP connector A host connection port is for connecting the disk array unit to a host. Without an expansion port, there are two ports per controller. With an expansion port, there are six ports per controller. There is an ACTIVE LED (left) and a LINK LED (right) below each connector. Descriptions of HP LINK LED and ACTIVE LED are as follows - Illumination of the HP Link LED indicates that the corresponding FC link is in an Up state. - Illumination of HP Active indicates that I/O processing is in progress. - Both LEDs blinking simultaneously (1-second intervals) indicates that the port is offline. - Both LEDs blinking rapid simultaneously (500 ms intervals) indicates that power-off processing is in progress. - Simultaneous blinking other than the above indicates that port setup was not done correctly. < Locations and port numbers of HP connector > HP5 HP4 HP1 HP3 HP0 HP2

16

8.

SAS connectors The SAS connectors are for connecting the disk array unit to disk enclosures. There are two connectors per controller. There is a FAULT LED (left) and LINK LED (right) below each connector. - LINK LED (LNK) (green) The LINK LED illuminates to indicate link-up. The LED is off to indicate link-down. - FAULT LED (FLT) (orange) The FAULT LED illuminates to indicate that an error is detected. < Locations and port numbers of SAS connector > DP1 DP0

9.

Extended BBU connector The extended BBU connector is for connecting the disk array unit to an extended BBU.

10. Modem connector The modem connector is for connecting the disk array unit to a modem for (optional) remote maintenance. (This is not used.) 11. Ejector The ejectors are used to install or remove the controller. 12. HPE FAULT LED (orange) The HPE FAULT LED illuminates to indicate that there is an abnormality in the host port extension. 13. HPE (Host Port Extension) The optional HPE is for extending the HP connector. 14. Battery FAULT LED (orange) The BBU FAULT LED illuminates to indicate that an error occurs in the battery backup unit. The LED blinks to indicate the battery backup unit must be replaced due to its life. 15. MC Slot MC Slot is a maintenance SD memory card slot for collecting failure log.

17

2.5.2.Disk Enclosure
This section describes the names and functions of each portion of the disk enclosure (DE).

2.5.2.1.Front View
2. SERVICE LED
1. POWER LED

Figure 2.7 Note.

Front View of the Disk Enclosure

Refer to 2.6.4 Installing and Removing Front Mask for a description of how to remove the front mask.

2.5.2.2.Front View (viewed when front mask is removed)

2. SERVICE LED 1. POWER LED

4. ACTIVE/FAULT LED 3. Disk drive/Dummy carrier

Figure 2.8 1. POWER LED (green)

Front View of the Disk Enclosure Without Front Mask

The POWER LED illuminates to indicate normal operation. 2. SERVICE LED (orange) The SERVICE LED illuminates to indicate that the entire unit containing the disk enclosure requires maintenance. The LED blinks to indicate that the power-on or power-off sequence is in progress.

18

Condition Operating

Description Normal operation Requesting maintenance or processing a maintenance task (such as system recovery) Power-off OFF OFF Powered off The LED is off to indicate that the power-on or power-off sequence is completed. Table 2.4 ON/OFF Status of POWER and SERVICE LED of Disk Enclosure

POWER LED ON ON

SERVICE LED OFF ON

3.

Disk drive/Dummy carrier A single disk enclosure is equipped with 12 disk drives/dummy carriers. Disk drive: Dummy carrier: Hard disk drive (HDD) with exclusive carrier Dummy carrier that fills the hole of HDD

<Locations and disk drive numbers> x0 x4 x8 x1 x5 x9 x2 x6 xA x3 x7 xB

The symbol x in the table indicates the disk enclosure number (x: 1 to F (hexadecimal)). 4. ACTIVE/FAULT LED (green/orange) A single ACTIVE/FAULT LED is installed for each disk drive/dummy carrier. The LEDs indicate the states of the respective disk drives. <Status display> Indicates the status of the disk drive located to the right. Indicates the status of the disk drive located to the left. ACTIVE/FAULT LED Green : ON Green : Blinking Green/orange : Blinking in turn Orange only : Blinking Orange : ON Table 2.5 Status Normal status (ready) Normal status (accessing) Rebuilding HDD low power state Abnormal status

ON/OFF Status of ACTIVE/FAULT LED of Disk Enclosure

19

2.5.2.3.Rear View
1. Power supply (PS1) 4. Power supply (PS0)

2. Adapter (ADP1)

2. Adapter (ADP0)

Figure 2.9 1. Power supplies (PS0/PS1)

Rear View of the Disk Enclosure

A single disk enclosure is equipped with two power supplies. Supply AC power to both of the power supplies. 2. Adapters (ADP0/ADP1) A single disk enclosure is equipped with two adapters.

2.5.2.4.Power Supply
AC Power Supply
1. Receptacle 5. Ejector

2. POWER GOOD LED 6. Power cable clamp

4. FAN FAULT LED

3. POWER FAULT LED

DC Power Supply
1. Receptacle 5. Ejector

2.POWER GOOD LED

4.FAN FAULT LED

3.POWER FAULT LED

Figure 2.10

Power Supply

20

1.

Receptacle Connect the power cable unit to the receptacle to supply power.

2.

POWER GOOD LED (green) The LED illuminates to indicate that power is being supplied to the unit.

3.

POWER FAULT LED (orange) The POWER FAULT LED illuminates to indicate that the power supply (excluding the fan) is faulted.

4.

FAN FAULT LED (orange) The FAN FAULT LED illuminates to indicate that the fan is faulted.

5.

Ejector The ejector is used in installing or removing the power supply.

6.

Power cable clamp The power cable clamp is a mechanism for preventing the power cable from being disconnected unintentionally.

2.5.2.5.Adapter

5. Ejector

5. Ejector

4. PS FAULT CLEAR

3. SAS connector

2. FAULT LED

1. READY LED

Adapter REV. Axx or Bxx (where xx is version number) 5. Ejector 5. Ejector

4. PS FAULT CLEAR

3. SAS connector

1. READY LED

2. FAULT LED

Adapter REV. Cxx (where xx is version number)

NOTE: Adapter REV is written in UNIT LABEL. Figure 2.11 Adapter

21

1.

READY LED The READY LED illuminates to indicate normal operation.

2.

FAULT LED The FAULT LED illuminates to indicate that an error occurred in the adapter. <(A) READY LED and FAULT LED before DE FW Rev.040D> READY LED OFF ON Blinking ON Status No connection or powered off Normal operation FW Copying Fault inside adapter Exchange adapter (Refer to the following notice). ON Blinking None Table 2.6(a) READY LED and FAULT LED of Adapter FAULT LED OFF OFF OFF ON

When DE FW is before Rev.040D, there is the following case; One ADP becomes READY LED ON and FAULT LED ON, another ADP becomes READY LED ON and FAULT LED OFF. In this case, confirm Condition View, then if CONT is Fault, exchange the ADP of the CONT side. If CONT is not Fault, exchange the ADP which is Fault on Condition View. If both ADPs are Fault together, request the analysis to the technology section because fault point identification is difficult. Collect Log of the DE by delogsave command after having collected usual Log information then. <(B) READY LED and FAULT LED of DE FW Rev.050C> READY LED OFF ON Blinking ON Status No connection or powered off Normal operation FW Copying Fault inside adapter Exchange adapter. ON Blinking Communication failure between the ADP is detected. Fault inside adapter (Refer to the following notice). Table 2.6(b) READY LED and FAULT LED of Adapter FAULT LED OFF OFF OFF ON

When DE FW is Rev.050C, there is the following case; One ADP becomes READY LED ON and FAULT LED Blinking, another ADP becomes READY LED ON and FAULT LED OFF. In this case, confirm Condition View, then if CONT is Fault, exchange the ADP of the CONT side. If CONT is not Fault, exchange the ADP which is Fault on Condition View. If both ADPs are Fault together, request the analysis to the technology section because fault point identification is difficult. Collect Log of the DE by delogsave command after having collected usual Log information then.

22

<(C) READY LED and FAULT LED after DE FW Rev.070D> READY LED OFF ON FAULT LED Status OFF No connection or powered off OFF Normal operation Fault inside adapter (Refer to the following notice). Blinking OFF FW Copying ON ON Fault inside adapter Exchange adapter. ON Blinking Communication failure between the ADP is detected. Table 2.6(b) READY LED and FAULT LED of Adapter

When DE FW is after Rev.070D, there is the case that ADP is fault at READY LED ON and FAULT LED OFF. In this case, if CONT is Fault, exchange the ADP which is Fault on Condition View. If both ADPs are Fault together, request the analysis to the technology section because fault point identification is difficult. Collect Log of the DE by delogsave command after having collected usual Log information then. 3. SAS connector The SAS connector is for connecting the adapter to a disk array device or disk enclosure. There are two ports per adapter. In adapter REV.Axx/Bxx, there is a FAULT LED (left) and a LINK LED (right) below each connector. In adapter REV.Cxx, there is a FAULT LED (left) and a LINK LED (right) on both sides of the connector respectively. - LINK LED (LNK) (green) The LINK LED illuminates to indicate link-up. The LED is off to indicate link-down. - FAULT LED (FLT) (orange) Lighting or blinking indicates that an abnormality was detected. < Locations and names of SAS connectors > DP-OUT 4. DP-IN

DP-IN (Connector on right): Connection to controller or adapter on side near controller. DP-OUT (Connector on left): Connection to adapter of next connection stage.

PS FAULT CLEAR The switch can be used to clear the fault status of the corresponding power supply.

5.

Ejectors The ejectors are used to install or remove the adapter.

23

2.5.3.Extended BBU
This section describes the names and functions of each portion of the extended BBU.

2.5.3.1.Front View

Figure 2.12

Front View of the Extended BBU

2.5.3.2.Rear View
1. Receptacle 6. BBU OUT connector 7. Set screw 7. Set screw

4. CHARGE LED 5. BBU FAULT LED

2. AC switch 3. Cooling fan

Figure 2.13 1. Receptacle

Rear View of the Extended BBU

Connect the power cable unit to the receptacle to supply AC power. 2. AC switch The AC switch is the switch for turning AC power to the extended BBU on or off. - indicates ON and indicates OFF. 3. Cooling fan The cooling fan is a fan for cooling the extended BBU. 4. CHARGE LED ON: Blinking: Indicates that AC power to the extended BBU is turned on. Indicates that the battery is charging.

24

5.

BBU FAULT LED ON: 1) Indicates that a fault has occurred in the extended BBU. 2) The BBU FAULT LED also illuminates when the BBU cable described in 6. is not connected normally to the body of the DAC unit. Blinking: The BBU FAULT LED blinks when the battery exchange period is up. (Please exchange the BBU within the prescribed interval.)

6.

BBU OUT connector The BBU OUT connector is the output connector of the BBU. Connect the accompanying BBU cable between the BBU-IN pin on the DAC unit and this terminal.

25

2.6.Installation
2.6.1.Mounting Disk Array Unit and Disk Enclosure
This section describes how to mount the disk array unit and disk enclosure on a rack. - The disk array unit weighs up to 31 kg and a disk enclosure up to 29 kg. At least three people should perform the tasks of mounting the units on a rack. - Mount disk enclosures, disk array unit, and extended BBU in that order from the top. - If adding an extended BBU, reserve space to mount the extended BBU (1 unit) below the disk array unit. How to attach the rack mount kit that is shipped with the disk array unit to a rack is described below. < Rack mount kit > Rail (L) Rail (R) M5 screw (12) Cable clamp (4) Releasable tie(5)

Rail (L)

Rear Inner

Front

Rail (R)

M5 screw

Cable clamp Figure 2.14 Rack Mount Kit

Releasable tie

26

1. Check the rail (L). The rear is the side that has an inner rail. The rail (L) is the rail whose cross section when viewed from the front forms the letter L. Install this rail on the leftmost when viewed from the front of the rack.

Rear Rail (L)

Front

Figure 2.15

Rail

2. Connect the bottom of the rail to a 1U delimiting mark on the rear support of the rack and insert the two inner rail projections.

Inner rail tabs 1U delimiting mark Figure 2.16 Attachment to Rear Support

27

3. Connect the bottom of the rail to a 1U delimiting mark on the front support of the rack and insert the two rail projections. Racks may be square-holed racks or round-holed racks and their respective rail projections differ. Affix the rail by inserting M5 screws in the two center screw holes in the front support of the rack.

Rail front Relative positions of projections

Installation in front support (Square-holed rack)

Installation in front support (Round-holed rack)

1U delimiting mark

Rail projections 1U delimiting mark

Rail projections

Figure 2.17

Installing Rail to the Front Support of the Rack

28

4. Draw the inner rail to the rear support of the rack and insert the two projections.

Rail front Relative positions of projections

Installation in rear support (Square-holed rack)

Installation in rear support (Round-holed rack)

Projection (round hole) Projection (square hole)

Projection (round hole) Projection (square hole)

Inner rail projections Figure 2.18

Inner rail projections

Installing Rail to the Rear Support of the Rack

5. Attach the inner rail by inserting M5 screws in the cable clamps in two center screw holes in the rear support of the rack. Make the cable clamp installation direction as shown in the figure to the right.

Right side when installed

Figure 2.19

Installing Inner Rails with Cable Clamp

29

6. Also install rail (R) on the rightmost of the rack by the same procedure. Installation of the rack mount kit is complete. 7. Mount units from the front of the rack. Raise a unit, place the rear of it on the rail, and slide it in.

- At least three people should perform the tasks of mounting a unit in a rack. - Because the units are heavy, watch out for pinched fingers or other injuries. - Do not drop a unit.
8. From the front of the rack, affix the unit. Affix the unit using M5 screws in two places each on the left and right of the front of the unit. Mounting in the rack is complete.

M5 Screw

Figure 2.20

Mounting the Unit

30

2.6.2.Installation of Disk Drives

1. Remove the front mask if installed. 2. Remove the dummy carrier from where the additional disk drive will be installed. 3. Install the disk drive. (See the next page for details.) 4. Repeat steps 2. and 3. for each additional disk drive. - Disk drive has a plug-in structure. Please insert slowly. - Install the disk drives one by one. At powered on state, insert next disk drive after the first disk drive becomes ready state. - Use newly purchased SAS/SATA disk drive. Operations of diverted or reused disk drives are not guaranteed. Do not divert or reuse disk drives. - Refer to 2.6.4 Installing and Removing Front Mask for a description of how to remove the front mask. - When handling a disk drive, take measures against static electricity, such as using a wrist strap. If you do not have a wrist strap, firmly place one hand on the unpainted metal surface of the disk drive before handling it. - You must mount three disk drives in locations 00, 01, and 02. These three of them function as a system disk. - Paste a system disk label bundled with a disk drive on a system disk for prevention of operational error. - Do not take out more than one of the disk drives inserted in locations 00, 01, and 02 at one time. - Do not expose the disk array unit to excessive vibration or shock. - When replacing the disk drive, confirm that the model number of a new one is the same as the one being replaced. - In the location that does not mount a disk drive, mount a dummy carrier necessarily. It is necessary for the cooling of this unit. System disks

Location label pasting position Paste a system disk label Figure 2.21 Disk Drives

31

<Dummy Carrier removing procedure> Please do not insert the finger up to the interior of the hook hole at the time of taking out the dummy carrier. Please insert your forefinger slightly on the Hook of the Dummy Carrier, and draw it out in an arrow direction.

Hook

Dummy Carrier Figure 2.22 Removing Dummy Carrier (1)

Figure 2.23

Removing Dummy Carrier (2)

Please keep the removed dummy carrier carefully.

32

Disk drives come in 2 types. SAS drives and SATA drives. Type of the disk drive is printed on the front label.

Figure 2.24

Disk Drive (SAS drive)

Figure 2.25 < Disk drive installation procedure >

Disk Drive (SATA drive)

1. Open the disk drive lever. When shipped, the disk drive lever is closed. Push the circled portion in the direction of the arrow and open the lever 40 degrees while it is pushed.

Figure 2.26

Opening the Lever

33

2. Support the part which a label of CARRIER is attached, and support CARRIER by other hand from the bottom. Insert the disk drive slowly till a screw out of sight, and stop insert once.

CARRIER

Label

* Support CARRIER from the bottom.

Screw

Disk Drive Figure 2.27 Inserting the Unit (1)

34

3. Support the lever, and insert the disk drive to the position which CARRIER just stops slowly.

CARRIER

Lever

Figure 2.28

Inserting the Unit (2)

35

4. Push the lever. The lever is locked.

Figure 2.29

Closing the Lever

Figure 2.30

Installation Complete

36

< Disk drive removal procedure > 1. Open the liver. (Pull the lever while pressing the blue part of the lever.) Wait in this state (figure below) for about 30 seconds till the disk drive stops if the disk drive is operating.

Lever

* Wait in this state for 30 about 30 seconds

Figure 2.31

Opening the Lever

2. Support the lever, and pull the disk drive slowly till the screw appears. If the screw appears, stop pulling it once.

Screw

Disk Drive

Figure 2.32

Removing the Disk Drive (1)

37

3. Support the part which the label of CARRIER is attached, and support CARRIER by other hand from the bottom. Pull the disk drive slowly.

CARRIER

Label

* Support CARRIER from the bottom.

Figure 2.33

Removing the Disk Drive (2)

38

2.6.3.Setting AC Operating Mode

This disk array unit is equipped with an AC operating mode. When AC operation mode is enabled, the disk array powers on when the AC power is turned on. The AC operating mode is enabled when the unit is shipped. It can be disabled by changing DIP switch settings in the controller of the disk array unit. When the AC operating mode is disabled, power is controlled by the power button of the disk array unit.

When The AC operating mode is disabled, the facility to control power using ESMPRO/AC cannot be used since power to the control circuits on the controller is not on. To use the facility for power control by ESMPRO/AC and NX coordination mechanisms (UPS), be sure to enable The AC operating mode.

<How to change mode> To disable AC operating mode by changing shipped state Change the DIP switch by referring to 6.7 Changing DIP Switches. The first switch (Bit1) of the DIP switch OFF disables The AC operating mode. ON enables the AC operating mode.

Make the settings of CONT0 and CONT1 the same.

39

2.6.4.Installing and Removing Front Mask

<State of mask key> The figure below shows the key unlocked when the key is in a horizontal state.

Figure 2.34 -

Key in Unlocked State

The figure below shows the key locked when the key is in a vertical state.

Figure 2.35

Key in Locked State

40

<Front mask installation procedure>

1. 2.

To install the mask, first unlock it by turning the key to the horizontal position. Connect the mask to the top and bottom, left and right of the unit and push it straight in until it clicks. Note. If it clicks, it has been installed accurately. After installing the mask, lock it by turning the key counterclockwise and mask installation is complete.

3.

Figure 2.36

Installing Front Mask

41

<Front mask removal procedure> 1. 2. Release the lock by turning the key clockwise. Pull the right side toward you by pivoting the left end, detach the left side, and pull the entire mask toward you.

Figure 2.37

Removing Front Mask (1)

Figure 2.38

Removing Front Mask (2)

42

2.6.5.Mounting an Extended BBU on a Rack

Rack Mount Instructions - The following or similar rack-mount instructions are included with the installation instructions: A) Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly, the operating ambient temperature of the rack environment may be greater than room ambient. Therefore, consideration should be given to installing the equipment in an environment compatible with the maximum ambient temperature (Tma) specified by the manufacturer. B) Reduced Air Flow - Installation of the equipment in a rack should be such that the amount of air flow required for safe operation of the equipment is not compromised. C) Mechanical Loading - Mounting of the equipment in the rack should be such that a hazardous condition is not achieved due to uneven mechanical loading. D) Circuit Overloading - Consideration should be given to the connection of the equipment to the supply circuit and the effect that overloading of the circuits might have on overcurrent protection and supply wiring. Appropriate consideration of equipment nameplate ratings should be used when addressing this concern. E) Reliable Earthing - Reliable earthing of rack-mounted equipment should be maintained. Particular attention should be given to supply connections other than direct connections to the branch circuit (e.g. use of power strips).

43

<List of included items for extended BBU> Extended battery backup unit Rack mount kit Enclosure Rear rail (2) Core nut (6) Screw (6) Front Mask BBU-CONT connection cable (2) Warranty List of Included Items

Rear rail (common to left and right)

Front mask

Extended battery backup unit Enclosure Cage nut (6) Mounting screw (6) Rear rail (common to left and right)

Figure 2.39

Extended BBU

44

1. For safety, remove the extended BBU from the chassis. Loosen the set screws (2 per extended BBU) of the extended BBU and pull out and remove the extended BBU.

Extended BBU

Set screws (2 locations)

Figure 2.40

Removing Extended BBU Cage nut

2. Install cage nuts in the rack support. Determine the position for installing cage nuts by looking at 1U delimiting marks on the rack. The figure to the right shows the position in which to install a cage nut in the support on the front left side of the rack. Install cage nuts on the left and right sides by inserting a nut in the center hole between 1U delimiting marks and catching the sheet metal in the hole. Figure 2.41 Rack Front (left side)

Front cage nut installation position 1U delimiting marks

The figure to the right shows the positions in which to install cage nuts in the support in the rear left side of the rack. Install cage nuts on the left and right sides by inserting two of them in holes above and below 1U delimiting marks and catching the sheet metal in the holes.

Rear cage nut installation positions

1U delimiting marks Figure 2.42 Rack Rear (left side)

45

3. Rack mounting chassis and rear rails Work in order of the numbers in the figure below. Rear Rail Rack rear (d) (c)

(d) (c) (b)

(b) Figure 2.43 a. b. Mounting Enclosure and Rack

(a)

Rack front

Slowly insert the enclosure from the front of the rack. Affix the enclosure to the attached cage nuts on the left and right using two mounting screws.

Cage nut

Affix using mounting screws (2 locations, left and right)

Figure 2.44

Affixing Enclosure

46

c.

From the rear of the rack, insert a rear rail in the gutters along the side of the enclosure and slide it forward

Gutter

Rear rail

Figure 2.45 d.

Rear Rail and Gutter

Affix the rear rail to the rack using two mounting screws. Also affix a rear rail on the right side of the enclosure by the same method.

Affix using mounting screws (Total of 4 places on left and right) Cage nut Figure 2.46 Affixing Rear Rail

4.

Mounting battery units Return battery units to the enclosure and fasten them with set screws. (2 per extended BBU) Rack mounting of the extended BBU is complete.

47

5.

Installation and removal of front mask To install the front mask, push in the springs on back of the front mask to the edges of the enclosure cutouts. To remove the front mask, press the top and bottom or left and right sides of the front mask and pull it toward you.

Front mask

Figure 2.47
6.

Installation and Removal of Front Mask

Mount the extended BBU to the enclosure. Affix the extended BBU with set screws. (2 per extended BBU)

Extended BBU

Fix screw (2 screws)

Figure 2.48

Mounting Extended BBU to the Enclosure

48

2.7.Cable Connections
2.7.1.Notes on Cable Connections
Check followings for each cable connection of the disk array unit. 1. Cables used for connections Use the power cables that ones specified by Bull to connect to power supplies. To connect the disk array unit to the host bus adapter or FC switch in the host, always use the FC cables specified by Bull. To connect the disk array unit and disk enclosures, always use the SAS cables that come with the disk enclosures.

2. Maximum length of FC cable Host Interface 1 Gbps 2 Gbps 4 Gbps Table 2.7 Maximum Cable Length 500 m 300 m 150 m

Maximum Length of FC Cable

Paste a cable label bundled with disk array unit and disk enclosure on each cable for prevention of miss connection.

49

2.7.2.Connection of Disk Enclosure

When connecting a disk enclosure, connect DP-IN on the disk enclosure to DP0 or DP1 on the disk array unit. To connect more than one disk enclosure, connect DP-IN on the next disk enclosure to DP-OUT on a previously connected disk enclosure.
DP-IN

Disk enclosure Disk enclosure Disk array DP-OUT DP-IN

DP0

Figure 2.49

Connection of SAS Cables

- Insert the SAS cable in each connector surely (till a click is heard). - SAS cables are also used for power control of the Disk Enclosure. - If both SAS cables are pulled out, the power supply of the Disk Enclosure is not turned on.

50

SAS Cable

Connector

Diamond

Circle

DP0/DP1 DP-OUT

DP-IN

Figure 2.50

Cable and Connector

- SAS cable has ditch to prevent the wrong insertion in the connector part. - Choose the connector to suit the destination port.

51

2.7.3.SAS Cable Connection and DE and PD Numbers

This disk array unit has two models: A maximum of eleven DE can be connected. Functions equivalent to DE 00 are implemented in the DAC. The figure below shows how to connect disk enclosures and the DE numbers and PD numbers.

DE 0D PD D0 to DB DE 0C PD C0 to CB DE 0B PD B0 to BB DE 0A PD A0 to AB DE 09 PD 90 to 9B DE 08 PD 80 to 8B

DE 05 PD 50 to 5B DE 04 PD 40 to 4B DE 03 PD 30 to 3B DE 02 PD 20 to 2B DE 01 PD 10 to 1B DAC PD 00 to 0B

Figure 2.51

SAS Cable Connection and DE and PD Numbers

52

Recommendation: configuration in order of the numbers below is recommended. Example: In a configuration with 3 DE, connect DE in the order (1)(DE 08), (2)(DE 01), (3)(DE 09). The order of DE configuration is shown below.
DE 0D PD D0 to DB DE 0C PD C0 to CB DE 0B PD B0 to BB DE 0A PD A0 to AB DE 09 PD 90 to 9B DE 08 PD 80 to 8B

11. 9. 7. 5. 3. 1. Figure 2.52 DE Configuration

10. 8. 6. 4. 2.

DE 05 PD 50 to 5B DE 04 PD 40 to 4B DE 03 PD 30 to 3B DE 02 PD 20 to 2B DE 01 PD 10 to 1B DAC PD 00 to 0B

- For prevention of false connection, paste a DE location label bundled with a disk enclosure after having connected SAS cable. - Match the location number with a said DE number.

DE Location label pasting position

53

2.7.4.Connection of Disk Array Unit to Production Server

Connect a FC cable between a disk array host connection port (HP connector) and the production server.
Host connection port (HP connector)

Host connection port (HP connector)

Host connection port (HP connector)

Host connection port (HP connector)

Figure 2.53

Rear View of Disk Array Unit

The sample recommendation requires the followings: - Two host adapters installed in the host. - Two LC-LC cables to connect the disk array unit and host bus adapters. * A one-controller unit requires a single host bus adapter and a single cable.
Production server

Host bus adapter Host bus adapter

FC cable (LC-LC cable)

Figure 2.54

Configuration Sample

Note. The dust-proof cover put on the host connection port of the controller is required when the controller is moved. Keep it in a safe place.

54

Connect the disk array unit to the production server with FC cables by the following procedure:

1. Checking power supplies Make sure that the plug of each power cable is disconnected from the outlet. 2. Connecting disk array unit to production server Push a separately purchased FC cable (LC-LC cable) into a host connection port (HPx) of a disk array unit controller (CONT0 or CONT1) until a click is heard. The connectors at both ends of the FC cable are the same. Connect the other connector of the FC cable to the connector of a host bus adapter installed in the production server. Connect the connector of the other host bus adapter to the other controller in the same way.

Pushing the connectors excessively may damage their ends, which may decrease optical output and cause inferior operation.

55

2.7.5.Connecting LAN Cables

Connect each servers and clients to the disk array unit with LAN cables. The disk array unit, management server, and client must be connected in order to perform initial setup and monitoring of the disk array. Configuration change and fault occurrence of the disk array unit can be monitored through LAN by using management software Storage Manager. Storage Manager is required for using the disk array. Connect separately purchased shielded LAN cables to the LAN ports (LAN connectors) for Storage Manager on the controllers.
LAN

Optima1500

Production server

Storage Manager server

*1

Storage Manager client

*1

Management server

Client

*1 Included as a product in BaseProduct

Figure 2.55

Sample LAN Cable Connection Configuration

56

Although the Storage Manager server can be connected to CONT0 or CONT1, connect it on the CONT0 side if only connecting one. Recommendation: Set IP addresses for the CONT0 and CONT1 LAN ports for Storage Manager individually to make them redundant and use them via Ether-HUB.

LAN port for Storage Manager (LAN connector)

CONT1

CONT0

LAN port for Storage Manager (LAN connector)

CONT1 Figure 2.56

CONT0
LAN port for Storage Manager (LAN connector)

Rear View of Controller Board

When using initialization wizard from Storage Manager to perform disk array initial settings, disk array unit, management server, and client must be connected with LAN cables.

LAN cables used to connect to management server - Use a shielded cross cable to connect a terminal to the unit directly. - Use a shielded straight cable to connect a terminal to the unit via a hub.

57

2.7.6.Connection of Extended BBU and Controllers

Connect an extended BBU to the disk array unit using the BBU cable shipped with the unit. 1. Mount the extended BBU directly below the disk array unit. Disk array unit

Extended BBU1 BBU input connector Controller

Extended BBU0

CHARGE BBU

BBU output connecter BBU Cable Figure 2.57 Extended BBU Connection of Extended BBU and Controllers

2.

Connect BBU IN of the controller to BBU OUT of the extended BBU using BBU cable.

58

2.7.7.Connecting Power Cables

WARNING

- Do not put too many loads on a single outlet. Failure to follow this warning may cause fire to occur. - Do not insert the plug of a power cord into an outlet with wet hands. Failure to follow this warning may cause electric shock to occur. - Do not put heavy objects on power cords. The coverings of power cords may be damaged and cause fire or electric shock to occur.

- Since the AC operating mode is functioning in the shipped state, connect the AC cable of the disk array unit last. - The disk array unit and disk array enclosures have dual power supply configurations so that they do not halt even if one power supply breaks down. When using this disk array unit, connect two power cables to the disk array unit and each disk enclosure. 1. 2. Before turning on the power, push mounted disk drives to make sure that they are not loosened. Connect disk enclosure power cables as in P.60 <Connection procedure>. Be sure to connect power supply PS0 and power supply PS1. Check power connections of all installed disk enclosures. Turn off the AC switches of extended BBU. Connect the power cables of extended BBU. Turn on the AC switches of extended BBU. Be sure to connect extended BBU BBU0 and extended BBU BBU1. Connect the power cable of the disk array unit. Since the AC operating mode is functioning in the shipped state, it will be powered on when you connect the power cable if electricity is being supplied. Note. 5. AC operating mode can be changed by setting a DIP switch in the controller.

3.

4.

Supply power after 4. if power is not supplied.

- Until the RDY LEDs blink, do not perform any operations using Storage Manager. - If one or more disk enclosures are connected to the disk array unit, always turn on the AC power of the disk enclosures before turning on the power of the disk array unit.

59

<Connection procedure>

Figure 2.58

Rear Side of Disk Array Unit and Extended BBU

Figure 2.59 1. 2.

Rear Side of Disk Enclosure

Spread the AC cable clamp, connect the power cable, and loosely lock the clamp. Move the clamp in the direction of the arrows and fix the clamp securely at a point close to the base of the plug.
AC cable Put-on Spread

Clamp

Figure 2.60 Note.

AC Cable

AC Cable : If the clamp is locked loosely, the power cable may come out. Fix the AC cable clamp securely at a point close to the base of the power cable.

DC Cable : The connector has lock mechanism. Insert a cable properly till it is locked.

60

2.8.Turning On Unit Power

2.8.1.AC Operating Mode
This disk array unit is equipped with an AC operating mode. When AC operation mode is enabled, the disk array powers on when the AC power is turned on. The AC operating mode is enabled when the unit is shipped. When the AC operating mode is disabled, power supply will be controlled by the power button of the disk array unit. Change AC operating mode by changing the DIP switch. Refer to 6.7 Changing DIP Switches.

2.8.2.Power-On Procedure
1. Supply power to the expanded BBU and the disk array unit. Turn on the expanded BBU first or turn on them simultaneously.

Note. When AC Operating Mode is enabled, AC power will turn on automatically. Go to step 3. If AC operating mode is disabled, go to step 2. AC power of disk enclosure part will turn on sequentially, corresponding with the disk array unit.
2. When AC operating mode is disabled, push the power button on the rear side of the disk array for about one second. Push until the fan on the power supply part rotates. Go to step 3. FAN FAN

Power button

Power button

Figure 2.61

Rear Side of the Disk Array

Perform this procedure on either CONT 0 or CONT1.

Note. If the unit is 2 controller model, push power button of either CONT 0 or CONT1. It is unnecessary to push both buttons. AC power of disk enclosure part will turn on sequentially, corresponding with the disk array unit.

61

3. Wait until the POWER LED (green) on the front side turns on and SERVICE LED (orange) LED turns off. Note. After turning the power on, SERVICE LED (orange) blinks while initializing and performing a self-test. If SERVICE LED (orange) doesnt turn off or POWER LED (green) doesnt illuminate after ten minutes, there is a possibility of failure. Refer to Chapter 7 Troubleshooting. When using snapshot function or data replication function, initializing time and self-test times will differ from referred to above. 4. Turn on the production server. Note. Turn on the production server after the disk array unit starts normally.

2.8.3.Notes on Turning On the AC Power

1. Notes on Turning ON from the Battery Backup State It takes up to 8 hours from the battery being discharged until it is fully charged. When it is not fully charged, fast writing that uses the cache (Cache Fast Write) is not done, which lowers performance. Since the cache cannot be retained at power-off, data is written to the disk without using the cache. The retention time of a battery that is not fully charged cannot be guaranteed. 2. Startup Procedure when losing the user data Follow the procedures below when failed to perform backup operation. <Startup when data in the cache has been lost> (1) After you turn on the unit, the service LED repeats blinking for 5 seconds ON and 7 seconds OFF. The unit does not start normally. (2) Turn off the unit by following 5.1 Power-Off Procedure. (3) Turn on the unit by following 2.8.2 Power-On Procedure. Note. Charging the battery takes up to 8 hours. If the unit does not start normally, there is a possibility of a failure. 3. Instructions for the use of snapshot function With the snapshot function, the management information for an update difference will be copied from a disk drive to the cache memory when the disk array device starts. Therefore, for starting disk array, it delays about 10seconds per 1TB of update difference data.

62

2.8.4.Power Control Methods Beside Power Button

1. Control Method Table 2.8 lists the control method besides using power button. Control Method ESMPRO/AC (UPS coordination) Host OS Windows Linux Features Coordination with the host is possible by using power control server. For details, check ESMPRO/AC. Automatic operation using power control server. For details, check ESMPRO/AC.

ESMPRO/AC Windows (automatic operation) Linux NX UPS coordination HP-UX This is an NX exclusive power control method. Windows (NQH-55/07 series UPS For details, check with your sales agent. Linux coordination) UPS Unspecified This is for countering momentary power interruption. (No UPS coordination) Table 2.8 Power Control Methods Note. Coordination refers to a mechanism that notifies the unit that AC input to the UPS was disconnected and begins shutdown processing.

When using UPS, duplex the UPS by connecting them to each power supply of the unit. Do this so that CONT0 and CONT1 are not simultaneously disconnected from AC power on a fault on one UPS.

63

2. Notes on UPS Coordination and Automatic Running Pay attention to the AC power-off sequence when using NX UPS.

< AC power-off sequence > 1. Production server 2. FC switch 3. Disk array unit (including extended BBU) 4. Disk enclosure 5. Management server (only ESMPRO/AC) There is no designated AC power-off sequence for multiple disk enclosures. (1)
Production server
UPS (with SNMP card)

ESMPRO/ACE

(2)

FC Switch

UPS (with SNMP card)

UPS (with SNMP card)

(3)

Disk array unit

UPS (with SNMP card)

UPS (with SNMP card)

Extended BBU

(4)

Disk Enclosure

UPS (with SNMP card)

UPS (with SNMP card)

(5)

Control server (AC Server)

UPS (with SNMP card)

ESMPRO/AC

Figure 2.62

AC Power-Off Sequence

64

3.Software Installation
This chapter explains the installation of Storage Manager and ControlCommand software. Since Storage Manager consists of Storage Manager server and Storage Manager client, each must be installed. Moreover, installation tasks are also necessary for a production server that connects the disk array. Software installation is performed by the procedure below. Storage Manager server installation

Installs Storage Manager server on a management server

iSM volume list command or ControlCommand installation

Installs the iSM volume list command or ControlCommand on a production server

Storage Manager Client installation

Installs Storage Manager client on a client

Perform software installation using the sample recommended configuration below as a reference.
Optima1500
Management server LAN

SAN FC Production server

iSM volume list command ControlCommand

Storage Manager Server LAN Client

Storage Manager Client

Figure 3.1

Sample of Recommended Configuration

65

* When using a Windows environment, the Storage Manager client can also be used on a management server. Refer to 3.1 Software Installation in a Windows Environment and 3.3 Installation of the Storage Manager Client if using a Windows environment.

Refer to 3.2 Software Installation in a Linux Environment and 3.3 Installation of the Storage Manager Client if using a Linux environment.

66

3.1.Software Installation in a Windows Environment

Install the Storage Manager server software on the management server, and the volume list command or ControlCommand on the production server. If you apply quota management*1 or file screening*2 to a disk or folder that is an installation destination, be sure to use it appropriately. When these are used erroneously, there can be problems during installation or during operation. *1 This is a facility for setting a limit on used capacity and making it impossible to use more than the set limit. *2 This is a facility for making it impossible to save a file of a specific file name (extension).

3.1.1.Installation and Startup of Storage Manager Server

Storage Manager server installation is done from Storage Manager Setup. Storage Manager Setup, which starts up when you insert the CD, makes it easy to install Storage Manager server by following the instructions in the screens. Refer to the Storage Manager Installation Guide attached to BaseProduct for details. You will also find the manual on the Storage Manager CD. The procedure for using Storage Manager Setup is the following. (1) Login as a user with administrator privileges. (2) Insert the Storage Manager CD on the management server. (3) Storage Manager Setup starts automatically. Install the Storage Manager server by following the screen instructions. Depending on the environment in which it is used, the program may not start automatically. In that case, directly start the following on the CD. \INSTALL\WINDOWS\ISMSETUP.EXE Set a user for connecting to Storage Manager server from Storage Manager client at installation. A user consists of a user name, password, and user level, and to ensure security, the range in which a user can operate from the Storage Manager client is limited according to the user level. A system administrator (L3) capable of all operations must be set at the time of initial installation or to change settings.

After installing Storage Manager server, the system must be restarted in order to start Storage Manager server.

67

When performing installation from Setup for the server of managing the disk array of easy installation, all of the Storage Manager server, the iSM volume list command, and JRE that is necessary for using Storage Manager client (Web GUI) are installed in Storage Manager Setup.

3.1.2.Installation of Volume List Command

This section explains installation of the iSM volume list command. If you are installing ControlCommand, perform the tasks of 3.1.3 Installation of ControlCommand without performing the tasks of this section. (1) Prior to Installation

Before beginning the volume list command (iSMvollist command) installation, be sure of the following. - By installing the volume list command, the functions of the host information collection command (iSMcc_hostinfo) and iSM Host Agent Service become available. - Refer to the Storage Manager Installation Guide accompanying BaseProduct for details about OS environments in which the host information collection command (iSMcc_hostinfo) and iSM Host Agent Service can be used. (2) Installation

Install the volume list command by following the procedure below. Refer to the Storage Manager Installation Guide accompanying BaseProduct for details. You will also find the manual on the Storage Manager CD. (a) Login as a user with administrator privileges. (b) Insert the Storage Manager CD on the production server. (c) Storage Manager Setup starts automatically. Install the volume list command by following the screen instructions. Depending on the environment in which it is used, the program may not start automatically. In that case, directly start the following on the CD. \INSTALL\WINDOWS\ISMSETUP.EXE

After installing the iSM volume list command, the system must be restarted in order to start iSM Host Agent Service.

68

3.1.3.Installation of ControlCommand
This section explains installation of ControlCommand. If not installing ControlCommand, the tasks of this section are unnecessary. (1) Prior to Installation Before beginning ControlCommand installation, be sure of the following. - By installing ControlCommand, functions of the host information collection command (iSMcc_hostinfo) and iSM Host Agent Service become available. - Refer to the ControlCommand on Windows Installation Guide for details about OS environments in which the host information collection command (iSMcc_hostinfo) and iSM Host Agent Service can be used. (2) Installation Install ControlCommand according to the procedure below. Refer to the ControlCommand on Windows Installation Guide for details. You will also find the manual on ControlCommand on Windows CD. By installing ControlCommand, the functions below become available. ReplicationControl ReplicationControl/ConsistencyOption SnapControl ProtectControl PowerControl iSM volume list command (iSMvollist) (a) Login as a user with administrator privileges. (b) Insert the ControlCommand CD on the production server and execute the following installation program on the CD drive. \iSMCCS\SETUP.EXE (c) Follow the instructions displayed on the screen.

After installing ControlCommand, the system must be restarted in order to start iSM Host Agent Service.

69

If any of the software below has already been installed, uninstall all of it before you install ControlCommand. If ReplicationControl/ConsistencyOption has been installed, you must uninstall ReplicationControl/ConsistencyOption before you uninstall ReplicationControl. ReplicationControl ReplicationControl/ConsistencyOption SnapControl Storage Manager volume list command * ControlCommandSet or ControlCommand * If the Storage Manager volume list command that is installed is Ver5.1 or later and coincides exactly with the version of ControlCommand, you can install ControlCommand by overwriting with the Storage Manager volume list command installed.

The version of the software that you install must support disk arrays that are connected to the server. Moreover, if a disk array has RemoteDataReplication configured, the remote disk array to which it connects must also be supported.

70

3.2.Software Installation in a Linux Environment

Install the Storage Manager server software on the management server, and the volume list command or ControlCommand on the production server.

3.2.1.Installation and Startup of Storage Manager Server

(1) Installation Install the Storage Manager server by following the procedure below. Refer to the Storage Manager Installation Guide accompanying BaseProduct for details. You will also find the manual on the Storage Manager CD.

(a) Login as a user with root privileges. (b) Insert the Storage Manager CD on the management server. * For servers on which the CD cannot be used, file transfer iSMsvr.rpm from another server. (c) Mount the CD. - Create the mount directory (For example, /cdrom) - Mount using the mount command mount -r /dev/cdrom /cdrom

(d) Install using the rpm command. rpm -ivh /cdrom/SERVER/LINUX/iSMsvr.rpm

(e) Installation is complete when the message below is output. Installation of iSMsvr was successful. (f) Unmount the CD. - Unmount using the umount command umount /cdrom

71

(2) Startup of Storage Manager server In order to start the Storage Manager server, environment setting is needed. The Storage Manager server is supplied with a sample environment definition file (/etc/iSMsvr/iSMsvr.conf). A sample file for the minimum possible environment setting for the Optima1500/2000/3000 (iSMsvr.easy-D.sample) is shown in the references here. Refer to the Storage Manager Installation Guide attached to the BaseProduct for other sample files. Explanations of each parameter are also given in comments in the sample files.

(a) Copy iSMsvr.easy-D.sample to create an environment definition file. # cp iSMsvr.easy-D.sample iSMsvr.conf (b) Edit the copied iSMsvr.conf and make the following settings. 1. Disk array IP settings Set the IP address for the disk array unit to be monitored. When using the initialization wizard to perform initialization after the Storage Manager server is started, disk array IP settings are not needed. 2. Set the user Set the user for when connecting to Storage Manager server from Storage Manager client. A user consists of a user name, password, and user level, and to ensure security, the range in which a user can operate from the Storage Manager client is limited according to the user level. A system administrator (L3) capable of all operations must be set at the time of initial installation or to change settings. login1 = (iSM , iSM , L1) login2 = (username, password , L3)

Remove the commenting out (#) of the line above and input the login2 user name and password. The password value can be encrypted.

3. Setting of Web browser destination port number Set the port number to use when connecting from a Web browser. Normally, this need not be changed. # web_port_no = 8070

If the default port number above conflicts with another application, remove the commenting out (#) of the above line and change the port number.

72

4. Setting of operation log file Set the directory in which to store the operation log file. Normally, this need not be changed. # file_directory = /opt/iSMsvr/etc/log/

To change the directory storing the operation log from the above default value, remove the commenting out (#) of the above line and change the path.

(c) Check the syntax of the environment definition file #iSMsvr check Verifying syntax(/etc/iSMsvr/iSMsvr.conf)...success Verifying disk free space(/opt/iSMsvr/etc/log/)...success iSM01419:Unencrypted object was found. You can make password m encrypted by executing with -p option. The iSMsvr check command checks in advance for syntax errors in the environment definition file and for insufficient disk capacity where the Storage Manager server operation log is stored. If there is not sufficient free capacity, change the directory for storing the operation log (default value: /opt/iSMsvr/etc/log). Message number iSM01419 indicates that the user password was not encrypted (which has no effect on Storage Manager server operation). Specify the -p option to encrypt the user password value specified. #iSMsvr check -p Verifying syntax(/etc/iSMsvr/iSMsvr.conf)...success Verifying disk free space(/opt/iSMsvr/etc/log/)...success Encrypting passwordsuccess

(d) Starting the Storage Manager server #iSMsvr start Enter the start command (iSMsvr start) or restart the system to start the Storage Manager server.

73

3.2.2.Installation of Volume List Command

This section explains installation of the iSM volume list command. If you are installing ControlCommand, perform the tasks of 3.2.3 Installation of ControlCommand without performing the tasks of this section.

(1) Prior to Installation Before beginning volume list command (iSMvollist command) installation, be sure to confirm the following. - By installing the volume list command, the functions of the host information collection command (iSMcc_hostinfo) becomes available. - Refer to the Storage Manager Installation Guide accompanying BaseProduct for details about OS environments in which the host information collection command (iSMcc_hostinfo) can be used.

(2) Installation Install the volume list command by following the procedure below. Refer to the Storage Manager Installation Guide accompanying BaseProduct for details. You will also find the manual on the Storage Manager CD.

(a) Login with root privileges. (b) Confirm that none of the following software is installed. iSMrpl (ReplicationControl) iSMrcd (ReplicationControl/ConsistencyOption) iSMsc (SnapControl) iSMvol (Storage Manager volume list command) iSMccs (ControlCommandSet or ControlCommand) Execute the following commands for confirmation. rpm -q rpm -q rpm -q rpm -q rpm -q iSMrpl iSMrcd iSMsc iSMvol iSMccs

If any of these are installed, uninstall them. (c) Insert the Storage Manager CD on the production server. For servers on which the CD cannot be used, file transfer iSMvol.rpm from another server.

74

(d) Mount the CD. - Create the mount directory (For example, /cdrom) - Mount using the mount command mount -r /dev/cdrom /cdrom

(e) Install using the rpm command. rpm -ivh /cdrom/VOLLIST/LINUX/iSMVOL/iSMvol.rpm (f) Installation is complete when the message below is output. Installation completed. (g) Unmount the CD. - Unmount using the umount command umount /cdrom

75

3.2.3.Installation of ControlCommand
This section explains installation of ControlCommand. If not installing ControlCommand, the tasks of this section are unnecessary.

(1) Prior to Installation Before beginning ControlCommand installation, be sure of the following. - By installing ControlCommand, the functions of the host information collection command (iSMcc_hostinfo) become available. - Refer to the ControlCommand on Linux Installation Guide for details about OS environments in which the host information collection command (iSMcc_hostinfo) can be used.

(2) Installation Install ControlCommand by using the Linux rpm command and following the procedure below. Refer to the ControlCommand on Linux Installation Guide for details. You will also find the manual on ControlCommand on Linux CD. By installing ControlCommand, the functions below become available. ReplicationControl ReplicationControl/ConsistencyOption SnapControl ProtectControl PowerControl Storage Manager volume list command (iSMvollist) (a) Login with root privileges. (b) Confirm that none of the following software is installed. iSMrpl (ReplicationControl) iSMrcd (ReplicationControl/ConsistencyOption) iSMsc (SnapControl) iSMvol (Storage Manager volume list command) iSMccs (ControlCommandSet or ControlCommand) Execute the following commands for confirmation. rpm -q rpm -q rpm -q rpm -q rpm -q iSMrpl iSMrcd iSMsc iSMvol iSMccs

If any of these are installed, uninstall them.

76

(c) Insert the CD on the production server. For servers on which the CD cannot be used, file transfer iSMccs.rpm from another server. (d) Mount the CD. - Create the mount directory (For example, /cdrom) - Mount using the mount command mount -r /dev/cdrom /cdrom

(e) Install using the rpm command. rpm -ivh /cdrom/LINUX/iSMCCS/iSMccs.rpm (f) Installation is complete when the message below is output. Installation completed. (g) Unmount the CD. - Unmount using the umount command umount /cdrom

If any of the software below has already been installed, uninstall all of it before you install ControlCommand. If ReplicationControl/ConsistencyOption has been installed, you must uninstall ReplicationControl/ConsistencyOption before you uninstall ReplicationControl. ReplicationControl ReplicationControl/ConsistencyOption SnapControl Storage Manager volume list command ControlCommandSet or ControlCommand

The version of the software that you install must support disk arrays that are connected to the server. Moreover, if a disk array has RemoteDataReplication configured, the remote disk array to which it connects must also be supported. ControlCommand is 32-bit software. If it will be used in an IA64 server environment, a 32-bit emulator, 32-bit compatible library, or other package offered by the OS must be installed in advance in order for the 32-bit software to run. Refer to the ControlCommand on Linux Installation Guide for details.

77

3.3.Installation of the Storage Manager Client

3.3.1.Configurations Offered by the Storage Manager Client
The Storage Manager client, which runs on a PC connected by a LAN to a management server, offers users monitoring and operating procedures through graphical user interfaces (GUI). The Storage Manager client offers the following two types of GUI. Web-based GUI Windows-based GUI

This manual documents installation methods for the Web-based GUI. If it is necessary to distinguish them specifically in the text, the term Storage Manager client (Web GUI) is used to indicate just the former and the term Storage Manager client (Win GUI) is used to indicate just the latter. The Storage Manager client runs only in a Windows environment. For details, refer to the Storage Manager Installation Guide accompanying BaseProduct. In an environment in which the Storage Manager client (Web GUI) is running, if a product that runs using a Java Runtime Environment (JRE) has already been installed, they can coexist and operate only if the environment conforms to the condition below. - The latest versions of everything within the JRE that is installed in the environment in question must be supported by both the Storage Manager client (Web GUI) and the other product. If this condition is not met, the Storage Manager client (Web GUI) or the other product must be operated on another machine.

At initial installation, use the JRE that is stored on the Storage Manager CD. Supported JREs may include versions for which security vulnerabilities have been reported. Therefore, it is recommended that the latest version among these JREs be used after installation. Refer to the pages below for details about security vulnerabilities. US-CERT (http://www.us-cert.gov) SunSolve Online (http://sunsolve.sun.com/show.do?target=home)

78

3.3.2.Installation of Storage Manager Client

This section describes the use of Storage Manager client (Web GUI). Storage Manager client (Web GUI) connects to Storage Manager server by starting a Web browser. Use Storage Manager client (Web GUI) when using a Optima1500/2000/3000. Moreover, in order to use Storage Manager client (Web GUI), JRE must be installed in advance. For details, refer to the Storage Manager Installation Guide accompanying BaseProduct. You will also find the manual on the Storage Manager CD.

Perform the following setup in advance for the Web browser to be used with the Storage Manager client (Web GUI).

(1) Set the Storage Manager server to connect in [Trusted sites]. Set this as follows. (a) From [Control Panel], select [Internet Options] and then select the [Security] tab. (b) Select [Trusted sites] and click the [Sites] button.

Figure 3.2

Internet Properties Screen

79

(c) Input the URL of the Storage Manager server to connect (for example: http://IP address (host name) of Storage Manager server to connect) in [Add this Web site to the zone:] and click the [Add] button. * Uncheck [Require server verification (https:) for all sites in this zone].

Figure 3.3

Trusted Site Setting Screen

(d) Click the [OK] button to close the screen.

80

(2) Set the security level of [Trusted Sites]. Set this as follows. (a) From [Control Panel], select [Internet Options] and then select the [Security] tab. (b) Select [Trusted sites] and click the [Custom Level] button.

Figure 3.4

Internet Options Screen

81

(c) Under [ActiveX controls and plug-ins], set [Run ActiveX controls and plug-ins] to [Enable].

Figure 3.5

Security Settings Screen

(d) Click the [OK] button to close the screen. * When Internet Explorer Version7 is used, invalidate the protection mode of trusted sites.

82

1. If the Storage Manager server is connected without making trusted sites settings and security level settings for the Web browser, the message below may be displayed and the connection fail. Change the settings by following the above procedure and connect again.

Figure 3.6

Web Browser Screen (When setup is not performed)

When using the Storage Manager client (Web GUI), set it up to allow ActiveX controls and plug-ins to run in the Web browser. This can be set in the [Security] tab of the screen displayed by selecting [Internet Options] from [Control Panel]. 2. When connecting to the Storage Manager server, a Warning Security screen may be displayed. If so, confirm that the issuer is Bull SAS and click the [Run] button. 3. When connecting to the Storage Manager server, a message showing that a function of Internet Explorer (or program name of Web browser used) is being blocked may be displayed in a Windows Security Alert screen. If so, release blocking through the screen in question or release the blocking of Internet Explorer (or program name of Web browser used) in firewall setup beforehand. 4. If use via a proxy server has been specified in setup of the Web browser being used, connection may fail. In that case, specify a proxy exception in Web browser setup to make connection to the Storage Manager server not be via the proxy server. Note that no change is needed if using the Storage Manager client (Web GUI) on the same computer as the Storage Manager server. Make changes by the following procedure. (1) From [Control Panel], select [Internet Options] and display the local area network settings screen by clicking on [LAN settings] in the [Connections] tab. (2) If [Use a proxy server for your LAN] is not checked, you need not perform the following. If it is checked, display the proxy settings screen by clicking on [Advanced]. (3) Add the host name or IP address of the server to connect to [Do not use proxy for addresses beginning with:]. (4) Check JRE proxy settings by the following procedure. - JRE 1.4.2 From [Control Panel], select [Java Plug-in] and the [Proxies] tab and look at whether [Use browser settings] is checked. If it is not checked, add the host name or IP address of the server to connect to [No Proxy Host].

83

- JRE 6 or 5.0 From [Control Panel], select [Java] and [Network Settings] and look at whether [Use browser settings] is checked. If it is not checked, select [Advanced] and add the host name or IP address of the server to connect to [Exceptions]. (5) Exit all Web browsers under use, and restart it. 5. If you newly installed the Storage Manager client (Win GUI) by downloading the installer from the Storage Manager client (Web GUI), a shortcut to start the Storage Manager client is not created in the start menu or on the desktop. For an overwritten installation or if the Storage Manager client (Win GUI) was installed previously on the same PC, a shortcut to start the Storage Manager client is created in the start menu and on the desktop, but since it is not needed in order to use the Storage Manager client (Web GUI), it may be deleted. 6. After JRE installation, it is recommended that you disable automatic updating of JRE. From [Control Panel], select the [Java] or [Java Plug-in] icon and change it in the Java Control Panel that is displayed. 7. The Storage Manager client (Web GUI) can be operated only by a user having administrator privileges. 8. When connecting to Storage Manager server, sometimes nothing is displayed in the Web browsers window and only Page displayed is shown in the status bar in the lower part of the window. If this is so, the following are possible causes. - JRE has not been installed Check whether JRE has been installed on the machine in question and if not, install it according to the procedure in the Storage Manager Installation Guide accompanying BaseProduct. - Web browser security settings have not been made Make Web browser security settings according to the procedure in 3.3.2 Installation of Storage Manager Client. - The network load is high Storage Manager client (Web GUI) downloads files that it needs to operate from Storage Manager server at startup and it sometimes takes time to download these depending on network conditions. When this occurs, wait awhile (up to several minutes) until downloading finishes.

84

3.3.3.Starting the Storage Manager Client

Input the name and port number of the host on which the Storage Manager server to connect is running in the Web browser URL field to start the client. Example: http://hostname:8070 If connection to the Storage Manager server succeeded, a login screen is displayed.

Figure 3.7 (a) User Name

Login Screen

Input a user name registered at setup on the Storage Manager server. To perform initial setup or to change settings, the user level must be a system administrator (L3). (b) Password Input a password registered at setup on the Storage Manager server. Although the user name and password each can be saved, care is needed since this makes it possible for anyone to connect.

85

Clicking the [Options>>] button extends the login screen as shown in Figure 3.8 and makes it possible to change the settings for operations following login. Refer to the Users Manual for details.

Figure 3.8

Login Screen (Detail)

When you click the [OK] button, the main window starts up.

Figure 3.9

Main Window Screen

86

4.Initialization of Disk Array

Initialization of a disk array is performed by the procedure below. Performs host information collection from the production server. For details, refer to 4.1 Collection of Host Information on Production Server. Performs initialization of the disk array. For details, refer to 4.2 Initialization Using Initialization Wizard. Confirms registration of host information. For details, refer to 4.3 Host Information Confirmation.

Collection of host information

Initialization using initialization wizard

Host information registration confirmation

Logical disk addition and binding

Carried out when adding and binding a logical disk. For details, refer to 4.4 Logical Disk Addition and Binding. Confirms that a bound logical disk can be recognized by the production server. For details, refer to 4.5 Connection Confiramtion from Production Server.

Connection confirmation from production server

87

4.1.Collection of Host Information on Production Server

This chapter describes the collection of host information from a production server. If production servers use only Windows OS and all servers are new systems (servers that have not begun operating), automatic collection of host information can be done. If you are setting up a disk array in a system that has already been in operation, or if a production server contains a Linux OS, collect host information using the methods shown in 4.1.2 Host Information Collection Using File Output in Windows Environment and 4.1.3 Host Information Collection Using File Output in Linux Environment. 1. Configuration for which automatic collection of host information is possible This method can be used if all production server OS of a new installation connected by FC cable are Windows and the disk array unit is also newly installed. It is set in 4.2.1 Initialization Wizard 2. Setting (e) Selection method of host information collection. New disk array New Windows server

SAN New Windows server

88

2.

Host information collection using file output from host information collection command If setting up a disk array unit in a system that has already begun operation, or if a production server connected by FC cable contains a Linux OS, the host information collection command can be used to output a file. By reading this output file in 4.2.1 Initialization Wizard 2. Setting (j) LD Binding, a logical disk that was created can be assigned to the production server. New disk array SAN New Linux server New Linux server New disk array SAN New Linux server New Windows server

New disk array SAN

New server

New disk array SAN

Existing server

Existing server

Existing server

89

4.1.1.Automatic Collection in Windows Environment

The tasks of this section are not needed to perform automatic collection of host information, since this is set by 4.2.1 Initialization Wizard 2. Setting (e) Selection method of host information collection.

4.1.2.Host Information Collection Using File Output in Windows Environment

Perform the procedure below. 1. Execute the host information collection command (iSMcc_hostinfo command). Execute the host information collection command (iSMcc_hostinfo command) from the command prompt. In the -export option, specify the file that is the output destination of the host information (host information file). Execute the host information collection command (iSMcc_hostinfo command) as a user with administrator privileges. D:\> iSMcc_hostinfo -export \ServerName iSMcc_hostinfo: Info: iSM11700: Please wait a minute. iSMcc_hostinfo: Info: iSM11770: Host Information was exported successfully. (code=aaaa-bbbb-bbbb-bbbb) iSMcc_hostinfo: Info: iSM11100: Command has completed successfully.

2.

Confirm the command execution result. After executing the host information collection command (iSMcc_hostinfo command), confirm that message number iSM11770 is output and that host information collection succeeded. The process number is output in aaaa in the message and an internal code for maintenance is output in bbbb. Transfer the host information file. Transfer the host information file that is output by executing the host information collection command (iSMcc_hostinfo command) to the client by using file transfer or USB memory. The host information file transferred to the client can be read and used when selecting the host in 4.2.1 Initialization Wizard 2. Setting (j) LD Binding.

3.

90

4.1.3.Host Information Collection Using File Output in Linux Environment

Perform the procedure below. 1. Execute the host information collection command (iSMcc_hostinfo command). Execute the host information collection command (iSMcc_hostinfo command) from the command line. In the -export option, specify the file that is the output destination of the host information (host information file). Execute the host information collection command (iSMcc_hostinfo command) as a user with root privileges. # iSMcc_hostinfo -export /tmp/ServerName iSMcc_hostinfo: Info: iSM11700: Please wait a minute. iSMcc_hostinfo: Info: iSM11770: Host Information was exported successfully. (code=aaaa-bbbb-bbbb-bbbb) iSMcc_hostinfo: Info: iSM11100: Command has completed successfully.

2.

Confirm the command execution result. After executing the host information collection command (iSMcc_hostinfo command), confirm that message number iSM11770 is output and that host information collection succeeded. The process number is output in aaaa in the message and an internal code for maintenance is output in bbbb. Transfer the host information file. Transfer the host information file that is output by executing the host information collection command (iSMcc_hostinfo command) to the client by using file transfer or USB memory. The host information file transferred to the client can be read and used when selecting the host in 4.2.1 Initialization Wizard 2. Setting (j) LD Binding.

3.

91

4.2.Initialization Using Initialization Wizard

4.2.1.Initialization Wizard
1. Overview The iSM initialization wizard can be used when installing a new disk array. The setup that is offered by the initialization wizard is as follows.
Start screen Selection of disk array Confirmation of disk array connection state

Start the initialization wizard. Refer to 2. Setting (a) Start screen. Specify the disk array to set up. Refer to 2. Setting (b) Selection of disk array. Confirm the disk array connections. Refer to 2. Setting (c) Confirmation of disk array connection state. Specify the method of setting the disk array. The following two setting methods are available. - Set by wizard form (standard) - Batch setting with initialization file This section explains the [Set by wizard form (standard)] method. Refer to 2. Setting (d) Selection of setting method. Refer to Appendix C Initialization of the Disk Array Using Initialization File concerning [Batch setting with initialization file]. Specify the host information collection method. Refer to 2. Setting (e) Selection method of host information collection. Set the network address for monitoring the disk array from Storage Manager. Refer to 2. Setting (f) Network parameters setting. Set the disk arrays host connection port. Refer to 2. Setting (g) Setting of host connection port. Unlock the licenses of the program products. Refer to 2. Setting (h) License Unlock. Specify whether to do LD binding in the initialization wizard. Refer to 2. Setting (i) Selection of LD binding. By binding a logical disk, the logical disk that is bound can be assigned to the production server obtained by collecting host information. Refer to 2. Setting (j) LD Binding and (k) Settings confirmation. Finish the initialization wizard. Refer to 2. Setting (l) Initialization Complete.

Selection of setting method

Selection method of host information collection

Network parameters setting Setting of host connection port License Unlock Selection of LD binding

LD Binding

Finish

92

If the initialization wizard is cancelled during operation, refer to 4.2.2 Resetting After Initialization Wizard Suspension and to 6.8 Changing Setting by Storage Manager to change initial settings. To execute the initialization wizard, the disk array, management server, and client must be connected by a LAN. Pay attention to the following in connecting a disk array for which a network is not set. - Only a disk array that is connected to the same network as the management server (for example, a network connected by IP addresses 192.168.1.xxx for different xxx) can be retrieved. - In disk array retrieval, which uses the User Datagram Protocol (UDP), port number 2730 is used. If a firewall has been installed, set it so that packets used for retrieval are passed to the management server and disk array network.

93

2. Setting Select [File] [Initialization Wizard] from the menu bar and start the initialization wizard.

Figure 4.1

Starting the Initialization Wizard

After the initialization wizard starts, make settings by following the screens.

94

(a) Start screen The start screen of the initialization wizard is displayed.

Figure 4.2

Start of initialization wizard Screen

Check what is displayed in the screen and begin retrieval of the subject disk array by clicking the [Next] button.

The [Cancel] button of an initialization wizard screen suspends the initialization wizard. The [Help] button displays a Storage Manager client help screen.

95

(b) Selection of disk array Selection of disk array specifies the disk array to be initialized.

Figure 4.3

Selection of disk array Screen

The disk arrays that are found by retrieval are displayed in a list. For a disk array that will be initialized for the first time, [Initialization] displays [not execute]. Select the disk array to set up from the list and click the [Next] button.

96

If Optima1500 is already installed and is being monitored from Storage Manager, [suspended] or [finished] is displayed. Display Contents not execute Disk Array Status Status immediately following disk array installation. Since initialization wizard network setting has not been performed, it is not subject to Storage Manager monitoring. Initialization by the initialization wizard or maintenance personnel is necessary. Processing through Network parameters setting or Setting of host connection port has been performed by the initialization wizard but the BaseProduct license has not been unlocked. The disk array is subject to Storage Manager monitoring. (*) Status in which unlocking has been done up to and including the BaseProduct license. The disk array is subject to Storage Manager monitoring. (*) Initialization Status of Disk Array

suspended

finished

Table 4.1

(*) Being subject to Storage Monitor monitoring means that the subject disk array is displayed in the main screen of Storage Manager client. The initialization wizard performs initialization for the one unit that is selected. If multiple units are displayed, start the initialization wizard again to perform initialization for another disk array.

97

(c) Confirmation of disk array connection state Confirm the disk array connections.

Figure 4.4

Confirmation of disk array connection state Screen

The Confirmation of disk array connection state screen is displayed. The displayed connection image shows the maximum configuration for each series. Confirm that the respective connection lines are correct. Check its contents and click the [Next] button.

In this screen, the [Back] button cannot be used to return to the previous screen. If you wish to change the subject disk array, click the [Cancel] button and start the initialization wizard again.

When reconnecting a connected SAS cable, refer to 7.3 Trouble Shooting According to Device Conditions 6. Trouble in SAS cable connection. Removal of an extended BBU that has been set up should be entrusted to your maintenance service agent. Removing it without changing internal settings reports an abnormality.

98

(d) Selection of setting method Select the setting method (initialization method).

Figure 4.5

Selection of setting method Screen

The initialization wizard provides the following two methods. - Set by wizard form (standard) Do not use the initialization file but make settings by following the wizard hereafter. - Batch setting with initialization file Batch initialization can be performed by using an initialization file prepared in advance. For a disk array being initialized for the first time, specify [Set by wizard form (standard)] and click the [Next] button. Refer to Appendix C Initialization of the Disk Array Using Initialization File concerning [Batch setting with initialization file].

99

(e) Selection method of host information collection If [Set by wizard form (standard)] was selected in (d) Selection of setting method, specify the host information collection method.

Figure 4.6

Selection method of host information collection Screen

Select [Automatic collection] for the configuration shown in 4.1 Collection of Host Information on Production server, in which the entire system is a completely new installation and the production server is a Windows platform. Do not check [Automatic collection] for a system configuration that does not correspond to the conditions for performing automatic collection of host information when a host information file is output by the host information collection command.

Host information that is automatically collected or output to a file can be used in disk array initialization and configuration setting. When binding logical disks from the initialization wizard or Easy Configuration, it is possible to perform logical disk allocation by specifying a host obtained in host information. When making Access Control settings from [Configuration Setting], host information can be used.

100

Configurations for which automatic collection of host information is possible are those in which all production server OS of a new installation connected by FC cable are Windows and the disk array is also newly installed. By making this setting, the host recognize volume becomes available (ON). Using the host recognize volume when there is a server on which work is already being performed has effects such as volumes that cannot be used for work unexpectedly appearing and becoming unavailable (OFF) due to completion or cancellation of the initialization wizard and volumes disappearing. Do not use it except for the configuration below.

Following specification, click the [Next] button. Checking [Automatic collection] and clicking the [Next] button displays a warning dialog.

Figure 4.7

Host Information Collection Method Warning Screen

If you are satisfied with the specification to perform automatic collection of host information, click the [OK] button. If you performed file output using the collection command, click the [Cancel] button, uncheck [Automatic collection] in the Selection method of host information collection screen, and click the [Next] button.

101

(f) Network parameters setting Set network addresses so that the disk array can be monitored from Storage Manager.

Figure 4.8

Network parameters setting Screen

Set a network address for monitoring for each controller of the disk array and also register that address in Storage Manager server environment setting. Set to both controllers (recommended) Set network addresses for monitoring for controller 0 and controller 1. Monitoring by Storage Manager from a controller connected to the management server by a LAN cable becomes effective. For a controller to which a LAN cable is not connected, the setting is made but monitoring is unavailable. Only set to Controller0 Set a network address for monitoring for controller 0 only. Controller 0 must be connected to the management server by a LAN cable. First, confirm that the management server and controller are connected by a LAN. Next, specify an IP address, subnet mask, and gateway address for each controller. Performing this setup makes it possible to monitor the disk array from the Storage Manager server by specifying an IP address that is set. For the IP address of a controller, specify a valid value that can be communicated with the network address of the management server, excluding 10.1.0.0 through 10.1.0.255 or 0.0.0.0. To not specify a gateway address, input 0.0.0.0.

102

Following specification, click the [Next] button. This displays the confirmation dialog.

Figure 4.9

Confirmation Dialog

Click the [Execute] button to set the specified value to the disk array. Click the [Cancel] button when returning to the Network parameters setting screen.

If an IP address, subnet mask, or gateway address has not been set correctly, network setting failed and monitoring by Storage Manager is not possible. If error message [05068] Failed to set network parameter. is displayed, refer to the Help.

103

(g) Setting of host connection port Set the host connection port of the disk array.

Figure 4.10

Setting of host connection port Screen

Default values are displayed in the list. To change settings, select the port to edit from the list and click the [Edit] button.

104

Figure 4.11

Setting of host connection port Edit Screen

Refer to explanations and modify settings. After modifying, click the [OK] button. To return change the selected display to the default value, click [Back to default value] button. Clicking the [Cancel] button cancels modified settings and returns to the Setting of host connection port screen. To modify settings for another port, select the port to edit from the list in the Setting of host connection port screen and click the [Edit] button. Platform Select the platform of the production server to connect. Windows (WN) Select this if the production server to connect from the subject port is a Windows environment. Linux (LX) Select this if the production server to connect from the subject port is a Linux environment.

When connecting to Windows environment and Linux environment production servers from one host connection port by way of a FC switch, this need not be changed from the default value (Windows). However, you must perform access control license unlocking and operate in WWN mode. Data rate Select the data rate (transfer rate) of the host connection port. - 4Gbps - 2Gbps - 1Gbps Match the data rate to the data rate of the host bus adapter of the production server to connect.

105

 Server connection type Select the type of connection with the production server to connect. - Direct Connection/FC-AL Select this to connect the production server to the host connection port directly by FC cable or using a loop topology FC switch (ex. N8190-119) that supports 1 Gbps or 2 Gbps. - FC switch connection (Fabric) Select this when the FC switch except the Loop topology FC switch is connected (WB series, MDS series). Switch ID Set the Loop Switch ID. When connecting multiple disk array units in a loop topology FC switch configuration that supports 1 Gbps or 2 Gbps, set this so that the same value is not repeated. If you select [Direct Connection/FC-AL] in [Server connection type], normally use it at 10h.

106

After finished editing, clicking the [Next] button in the Setting of host connection port screen displays the confirmation screen.

Figure 4.12

Host Connection Port Setup Confirmation Screen

The host connection port setup confirmation screen displays the host connection port settings. Port Number Displays the subject port number. Platform Displays the platform to set. Data rate Displays the data rate to set. Server connection type Displays the server connection type to set. Switch ID Displays the Loop Switch ID to set.

Confirm that the specified settings are correct. After checking, click the [Execute] button. This sets the specified values for the disk array. When returning to the Setting of host connection port screen, click the [Cancel] button.

107

When connected to production servers in Windows and Linux environments through a FC switch from one host connection port, the default value (Windows) need not be changed. However, you must perform Access Control license unlocking and operate in WWN mode. - Access Control is set to WWN mode automatically if you perform Access Control license unlocking and you bind logical disks by specifying a host in subsequent screens. If you do not unlock the Access Control license and you bind logical disks without specifying a host, set Access Control to WWN mode from [Configuration Setting] after terminating the initialization wizard.

The host connection port of the disk array must be set to the same data rate as the host bus adapter it connects. If the data rate is set different from the host bus adapter, it may not be possible to recognize the logical disk from the production server to which it is connected. If volumes cannot be recognized, recheck the connection between the host connection port and the host bus adapter and the settings. For a Microsoft Cluster Service (MSCS) configuration, or if connecting to a fault tolerant server, set the Switch IDs of ports to connect to the same value. (Setting the Switch IDs to the same value makes the IDs (AL_PA) of the ports the same value.) For details, refer to Appendix A and Appendix B.

108

(h) License Unlock Unlock the license of the program product.

Figure 4.13

License Unlock Screen

Input a license key that is entered in the Program Product License Sheet for disk array software. Then click the [Enter] button. A license key and program product are displayed in the list of input keys. If you wish to clear an input key from the list, select it from the list and click the [Clear] button.

Be sure to input the program product license of the BaseProduct. When connecting a disk array to multiple servers, except for a single cluster configuration, the Access Control license must be unlocked and restrictions are needed so that a logical disk always is accessed from one OS.

109

Installing Access Control (unlocking the license), makes it possible to allocate accessible logical disks by server when configuring a multiple server connection. In [LD Binding] of [Initialization Wizard] and [LD Bind Easy Configuration] of [Easy Configuration], it is possible to specify production servers obtained in host information and allocate bound logical disks. The above automatically sets up the following to execute in Access Control setup. (1) Set access mode of port (2) Create LD Set (3) Link path to LD Set (4) Allocate logical disk Furthermore, if you unlocked the Access Control license from the initialization wizard, it automatically starts Access Control. If Access Control has not been installed (or Access Control is stopped), bound logical disks become accessible from all servers connected to the disk array. When you have input all of the license keys, click the [Next] button.

110

(i) Selection of LD binding Selection of LD binding specifies whether to bind a logical disk in the initialization wizard.

Figure 4.14

Selection of LD binding Screen

Specify whether to [LD binding] or [Not LD binding]. - If [LD binding (RAID-1/RAID-6) ] is selected The LD binding screen ((j) LD Binding) is displayed by clicking the [Next] button. RAID types that can be bound are as follows. When binding a spare, another physical disk is required. RAID1 (Basic Pool): Configured on 2 physical disks RAID6 (4+PQ) (Dynamic Pool): Configured on 6 physical disks RAID6 (8+PQ) (Dynamic Pool): Configured on 10 physical disks

- If [Not LD binding (Individually executes later)] is selected The settings confirmation screen ((k) Settings confirmation) is displayed by clicking the [Next] button.

111

- When binding logical disks using the initialization wizard, it is possible to bind multiple logical disks of the same capacity in one RAID type. However, they cannot be bound successively. To add more logical disks, use [Easy Configuration] or [Configuration Setting] after the initialization wizard is complete. - In cases such as the following, using [Configuration Setting] without binding logical disks in the initialization wizard is recommended. When configuration is other than RAID-1 or RAID-6 When binding logical disks by specifying the physical disks in RAID-6 When binding logical disks by specifying implementation locations of physical disks in a disk enclosure When binding logical disks of different capacities in one RAID When binding logical disks when aware of replication or snapshot operation

112

(j) LD Binding If [LD binding] was selected in (i) Selection of LD binding, next bind the logical disk and assign it to the host (production server).

Figure 4.15

LD Binding Screen

Specify [RAID Type/PD Type], [LD Capacity], and [Number of LDs]. If the AccessControl license has been unlocked in advance, logical disk assignment can be performed by specifying a production server. Specify this by referring to the following. RAID Type/PD Type Select one of the RAID types/PD (physical disk) types displayed in a pull-down. LD Capacity Specify the capacity of the logical disk to bind. The capacity that is displayed by default shows the maximum capacity of a logical disk that can be bound if Selection host1 and Selection host2 are specified, excluding the 0.2 GB capacity of each control volume that is bound. The maximum capacity shown in the pull-down varies depending on whether a host is specified.

113

 Number of LDs Specify the number of logical disks to bind. Selection host1/Selection host2 Check this to assign a bound logical disk to a specified host (production server). When configuring a cluster, checking both [Selection host1] and [Selection host2] makes the logical disk shared. If not configuring a cluster, check only Selection host 1. Only one host can be specified for each of [Selection host1] and [Selection host2]. If multiple hosts are connected and more logical disks will be added and allocated, add them after the initialization wizard finishes by referring to 4.4 Logical Disk Addition and Binding. - If checked A logical disk to be bound is assigned to a specified production server. If [Automatic collection] was selected in (e) Selection method of host information collection, production servers connected to the disk array are shown in the pull-down. Select the host to which to assign the logical disk. - If not checked The logical disk is not assigned to a production server. To allocate a created logical disk to a production server, execute Access Control setup from Configuration Setting. Refer to the Configuration Setting Tool Users Manual (GUI) for details. [Refresh] button If the name of the host to assign to the logical disk is not displayed in the [Selection host1/Selection host2] specification, click the [Refresh] button. The following screen is displayed.

Figure 4.16

List Update Screen

Select the method of getting host information.

114

- Update with info from iSM server. Get the host information currently recognized by the Storage Manager server. If host information is not displayed by this operation, refer to 7.6 Trouble Shooting in Initialization Wizard/Easy Configuration 3. Host information is not displayed.

- Update with info file. Read the host information file that was output using the host information collection command. The host information file must be stored in advance on the client.

Clicking the [OK] button acquires the specified host information. Clicking [Close] returns to the LD Binding screen without performing any processing. LD Set Name Use this to set and name a grouping of logical disks (LD Set) accessible to the specified host. The default value of the LD Set name is the name of the assigned host. To edit the LD Set name, check the checkbox displayed ahead of [LD Set Name]. Name To specify an arbitrary name for the logical disk, check the checkbox and change the name. A four-digit logical disk number is added to the specified name. Quick Format By performing only the minimum necessary processing and omitting data area initialization (clearing), this formats in a short time. This is available only for RAID types and platforms supported by quick formatting in a basic pool. The disk array provides basic pools and dynamic pools. Refer to the Configuration Setting Tool Users Manual (GUI) for details. GPT Disk Type This makes the OS type of the logical disk to bind a GPT disk type (WG). Select [GPT Disk Type] in the following cases. - Platform is Windows - To use as GPT disk type by host * When using a logical disk of 2 TB or more, it may not be possible to use it unless it is a GPT disk type. For details, refer to your Windows platform documentation.

115

If [GPT Disk Type] is not selected for a Windows platform, it is set up in the normal format (WN). This item can be selected only when host specification is performed. This format can also be changed later. (Change it from nickname setting of the relevant disk in the client main screen) Spare Binding Use this to automatically bind a spare physical disk that has the same PD type as that selected in [RAID Type/PDP Type (capacity)]. This does not bind a spare disk if there is no physical disk of the same PD type to bind to a physical disk as a spare. Following specification, click the [Next] button. Clicking the [Back] button returns to the Selection of LD binding screen.

- If a logical disk was bound without making an assignment to a production server, assignment to a production server can be made separately in [Setting Access Control] in [Configuration Setting]. Refer to the Configuration Setting Tool Users Manual (GUI) for details. - Making a host specification binds a 0.2 GB control volume besides the logical disk being bound in the LD Set (it binds two if host 1 and host 2 both are specified). Refer to the Data Replication Users Manual (Function Guide) and the Snapshot Users Manual (Function Guide) concerning control volumes. - If the Access Control license has not been unlocked, the following options cannot be specified. - Selection host1/Selection host2 and each LD Set Name - Name (prefix) In addition, the following options can be specified by performing host specification if the Access Control license has been unlocked. - Quick Format - GPT Disk Type

When no host name is displayed after executing [Update with info from iSM server], refer to the following and take appropriate action. 7.6 Trouble Shooting in Initialization Wizard/Easy Configuration (3) Host information is not displayed

116

(k) Settings confirmation Check the license unlocking and LD binding parameters. If [Not LD binding] was specified in the Selection of LD binding screen, only the license unlocking specifications are displayed.

Figure 4.17

Settings Confirmation Screen (for individual setting)

Check the settings of each parameter. License Unlock The specifications for setting license unlocking are displayed. - Product The program product of which license is to be unlocked is displayed. - License key The license key of the license to unlock is displayed. - AccessControl This displays ON if the Access Control license was unlocked and indicates that Access Control was started. * The start of Access Control is the same as when the [Start Access Control] button is clicked from [Setting Access Control] in [Configuration Setting].

117

[Example]
--- License Unlock --Product :BaseProduct License key :ABCDEF-GHIJKL-MNOPQR-STUVWX-YZABCD Product :AccessControl License key :GHIJKL-MNOPQR-STUVWX-YZABCD-EFGHIJ AccessControl :ON

Spare Binding The specifications for spare binding are displayed. This is displayed if [LD binding] was selected in the Selection of LD binding screen and the [Spare Binding] checkbox was checked in the LD Binding screen. - Physical Disk A list of the physical disks that make up the spare to bind is displayed in xxh-xxh format (hexadecimal).

[Example]
--- Spare Binding --Physical Disk : 00h-0dh

Pool Binding The contents of a pool bound from the specified RAID type and PD type are displayed. This is displayed only if [LD binding] was selected in the Selection of LD binding screen. - Pool Number The pool number to bind is displayed. - RAID Type/PD Type The specified RAID type and PD type are displayed. - Physical Disk A list of the physical disks that make up the pool to bind is displayed in xxh-xxh format (hexadecimal).

118

[Example]
--- Pool Binding --Pool Number : 0000h RAID Type/PD Type: RAID1(Basic)/SAS Physical Disk : 00h-02h 00h-03h

LD Binding The specifications for logical disk to bind are displayed. - Capacity The capacity of the logical disk to bind is displayed. - Number of LDs The number of logical disks to bind is displayed. If hosts were specified, as many control volumes (0.2 GB) as the number of hosts specified are included in the number. - Bind Mode The Bind Mode of the logical disk to bind is displayed. normal quick Normal format Quick format

- Number/OS type/LD Name/Purpose Number: OS type: The logical disk number is displayed in hexadecimal notation. The OS type of the logical disk is displayed. LX WG WN Logical disk used by Linux system Logical disk used by Windows GPT system Logical disk used by Windows system

LD Name: The logical disk name assigned by default is displayed. Purpose: The purpose of the logical disk to bind is displayed. Control Volume None Logical disk used for control volume Logical disk for general use

119

[Example]
--- LD Binding --Capacity: 132.0GB(141,733,920,768bytes) Number of LDs: 3(Include Control Volume) Bind Mode : normal Number/OS type/LD Name/Purpose 0000h/WN/20000030138414870000/Control Volume 0001h/WN/20000030138414870001/Control Volume 0002h/WN/20000030138414870002/

Access Control Setting Specifications set for Access Control are displayed. - Platform The platform of the LD Set is displayed. - LD Set Name The name of the LD Set is displayed. - Host Name The name of the production server to which to assign the bound logical disk is displayed. - Path Info WWPN (World Wide Port Name) information to set for the LD Set is displayed. - Logical Disk Assigned to Host The logical disks to assign to the specified production server are displayed. LUN: Number: OS type: The LUN (Logical Unit Number) is displayed in hexadecimal notation. The logical disk number is displayed in hexadecimal notation. The OS type of the logical disk is displayed. LX WG WN LD Name: Capacity Logical disk used by Linux system Logical disk used by Windows GPT system Logical disk used by Windows system

The logical disk name is displayed. The capacity of the logical disk is displayed.

RAID Type: The specified RAID type is displayed. PD Type: The specified PD type is displayed.

[Example]

120

--- Access Control Setting (Host1) --Platform : WN LD Set Name : EXP12DV1 Host Name : EXP12DV1 Path Info : 1000-0000-aaaa-bbbb 1000-0000-cccc-dddd --- Logical Disk Assigned to Host --LUN/Number/OS type/LD Name/Capacity/RAID Type/PD Type 0000h/0000h/WN/WG0000/0.2GB/RAID1(Basic)/SAS 0001h/0002h/WN/WG0002/2.0GB/RAID1(Basic)/SAS --- Access Control Setting (Host2) --Platform : WN LD Set Name : EXP12DV2 Host Name : EXP12DV2 Path Info : 1000-0000-eeee-ffff 1000-0000-gggg-hhhh --- Logical Disk Assigned to Host --LUN/Number/OS type/LD Name/Capacity/RAID Type/PD Type 0000h/0001h/WN/WG0001/0.2GB/RAID1(Basic)/SAS 0001h/0002h/WN/WG0002/2.0GB/RAID1(Basic)/SAS

After checking, click the [Execute] button. This makes settings to the disk array. Clicking [Cancel] returns to the LD Binding screen or the Selection of LD binding screen.

121

(l) Initialization Complete The following screen is displayed if the disk array was initialized correctly.

Figure 4.18 Check Description.

Initialization Complete Screen

Click the [Save Param] button to use the settings made in the initialization wizard when initializing another disk array. The settings made in the initialization wizard (except for IP address and license information) are saved in text format. The saved file can be used as the file used for batch setting in (d) Selection of setting method when initializing another disk array. For the contents of the file, refer to Appendix C Initialization of the Disk Array Using Initialization File. To use the saved initialization file for another disk array, it is necessary to edit the IP address and license key in advance. After confirming Description, click the [Finish] button to terminate the initialization wizard. This returns you to the Storage Manager main window screen.

122

(m) If setup fails If initializing the disk array fails in the initialization wizard, the following screen is displayed.

Figure 4.19

Initialization Failure Screen

The following contents are displayed when initialization fails in license unlocking or LD binding. License Unlock Spare Binding Pool Binding LD Binding LD Set Setting Time Setting Host information collection Setting * The display is also as shown above on a quick format error. After checking the displayed error content, click the [Finish] button to terminate the initialization wizard and return to the main window of Storage Manager client. Execute the initialization wizard again. If the method for coping with each error is unknown, refer to 7.6 Troubleshooting in Initialization Wizard/Easy Configuration.

123

4.2.2.Resetting After Initialization Wizard Suspension

After cancelling the initialization wizard, look up the contents of each screen in Table 4.2 when you perform initialization by the initialization wizard again. Initialization Wizard Screen Start screen Selection of disk array Setting Status of Disk Array Afer Suspension & How to Re-execute Nothing has been set in the disk array. In re-execution, the initialization wizard can be executed the same as when first performing initialization for the disk array. Nothing has been set in the disk array. When reconnecting a connected SAS cable, refer to 7.3 Troubleshooting according to Device Conditions 6. Trouble in SAS cable connection. In re-execution, the initialization wizard can be executed the same as when first performing initialization for the disk array. Nothing has been set in the disk array. In re-execution, the initialization wizard can be executed the same as when first performing initialization for the disk array. If this displayed an error message and terminated, a network address is set in the disk array and environment setting. Refer to the error message contents in the help for Storage Manager client and restore the network. After retoration, execute the initialization wizard again. Only network settings are set in the disk array. Host connection port setup Execute the initialization wizard again. Network settings and host connection port settings are set in the disk array. License Unlock Execute the initialization wizard again. Table 4.2 Resetting After Initialization Wizard Suspension (1/2)

Confirmation of disk array connection state

Selection of setting method Selection method of host information collection Network parameters setting

Network confirmation screen

124

Initialization Wizard Screen Selection of LD binding

Setting Status of Disk Array Afer Suspension & How to Re-execute Network settings and host connection port settings have been made in the disk array. License unlocking has not been done.

LD Binding

Table 4.2

Execute the initialization wizard again. Also re-enter the license key that was input before suspension. Resetting After Initialization Wizard Suspension (2/2)

125

(a) Start screen The start screen of the initialization wizard is displayed. Check the contents and proceed to the next screen. For details, refer to 4.2.1 Initialization Wizard 2. Setting (a) Start screen. (b) Selection of disk array Selection of disk array specifies the disk array to be initialized.

Figure 4.20

Selection of disk array Screen

The disk arrays that are found by retrieval are displayed in a list. The display in Initialization differs depending on where the initialization wizard was cancelled the previous time. For details, refer to Table 4.3. Select the disk array to set up from the list and click the [Next] button.

126

Display Contents

Disk Array Status Status immediately following disk array installation. Since network setting was not performed in the initialization wizard, it is not subject to Storage Manager monitoring. Initialization by the initialization wizard or maintenance personnel is needed. Processing through Network parameters setting or Setting of host connection port has been performed by the initialization wizard, but the BaseProduct license has not been unlocked. The disk array is subject to Storage Manager monitoring. (*)

not execute

suspended

finished

Status in which unlocking has been done up to and including the BaseProduct license. The disk array is subject to Storage Manager monitoring. (*) Table 4.3 Initialization Status of Disk Array

(*) Being subject to Storage Monitor monitoring means that the subject disk array is displayed in the main screen of Storage Manager client. If the initialization status of a disk array is [suspended] or [finished], the message box shown below is displayed to stop disk array monitoring and put the subject disk array in a Configuration Setting state.

Figure 4.21

Monitoring Stop Confirmation Message Box

Although the display in [Initialization] is [suspended] after cancelling the initialization wizard before it finishes, the disk array status in the main screen of Storage Manager client displays [Normal].

127

(c) Confirmation of disk array connection state Confirm the disk array connections. For details, refer to 4.2.1 Initialization Wizard 2. Setting (c) Confirmation of disk array connection state.

(d) Selection of setting method This specifies the setting method (initialization method). Specify [Set by wizard form (standard)] and click the [Next] button. For details, refer to 4.2.1 Initialization Wizard 2. Setting (d) Selection of setting method.

(e) Selection method of host information collection This specifies the host information collection method. Check what is displayed in the screen, specify whether or not to perform automatic collection of host information, and click the [Next] button. For details, refer to 4.2.1 Initialization Wizard 2. Setting (e) Selection method of host information collection.

(f) Network parameters setting Network parameters setting sets network addresses so that the disk array can be monitored from Storage Manager. For a disk array for which a network is already set, the addresses set in the disk array are displayed. To change an address, perform setup again. For the IP address of a controller, specify a valid value other than 10.1.0.0 through 10.1.0.255 or 0.0.0.0. To not specify a gateway address, input 0.0.0.0. For details, refer to 4.2.1 Initialization Wizard 2. Setting (f) Network parameters setting.

128

- If settings have been made to both controllers, only [Set to both controllers] can be specified, and if settings have been made only to controller 0, only [Only set to controller0] can be specified. If settings have been made only to controller 0, to also make monitoring from controller 1 available, connect the management server to controller 1 by a LAN cable and make changes to disk array settings and environment settings, respectively. Disk array: [Configuration Setting] [Disk array setting] [Network] tab For details, refer to the Configuration Setting Tool Users Manual (GUI). Environment setting: Storage Manager server Setting Utility program For details, refer to the Storage Manager Installation Guide accompanying BaseProduct. - If [Set to both controllers] is performed when only one controller is connected by a LAN cable, the disk array changes the addresses of both controllers, but Storage Manager server environment setting changes only an address for which monitoring is available. To make monitoring from both controllers available, connect the management server to controller 1 by a LAN cable and make changes to Storage Manager server environment settings to match the IP address of the disk array to monitor. Refer to the Storage Manager Installation Guide accompanying BaseProduct concerning changing environment settings. Disk array Controller Controller Disk Array Controller 0 Controller 1 Address A C (Change) Address B D (Change) Setting Utility Address A C (Change) Address B (Not change) Monitoring Available Not available LAN
Management server

If an IP address, subnet mask, or gateway address has not been set correctly, monitoring by Storage Manager is not possible. If error message [05068] Failed to set network parameter. is displayed, refer to the Help.

129

(g) Setting of host connection port Setting of host connection port sets up the host connection port of the disk array. Default values or settings from the last time are displayed in a list. To change settings, select the port to edit from the list and click the [Edit] button. After editing is finished, confirm that the edited contents are correct in the confirmation screen and click the [Execute] button. For details, refer to 4.2.1 Initialization Wizard 2. Setting (g) Setting of host connection port.

If a platform value other than WN or LX is set, editing is not possible. Edit in [Host connecting port] of [Configuration Setting]. If the port configuration change is locked, the setting of host connection port cannot be changed.

(h) License Unlock Unlock the license of the program product that you have purchased. For details, refer to 4.2.1 Initialization Wizard 2. Setting (h) License Unlock.

A license that is already unlocked need not be input again. Unlocked licenses are not displayed. To check licenses that have been unlocked, select the subject disk array from the main screen of Storage Manager client and refer to [Product status] in [Properties]. (i) Selection of LD binding Specify [LD binding] or [Not LD binding]. For details, refer to 4.2.1 Initialization Wizard 2. Setting (i) Selection of LD binding. - If logical disks have already been bound, a logical disk is bound using unused physical disks. If logical disks are already bound and you do not have the unused physical disks needed for the RAID type that you wish to bind, specify [Not LD binding]. The unused physical disks needed for RAID types are as follows. RAID1 (Basic Pool): Configured on 2 physical disks RAID6 (4+PQ) (Dynamic Pool): Configured on 6 physical disks RAID6 (8+PQ) (Dynamic Pool): Configured on 10 physical disks - To unbind a logical disk that is already bound, use [Configuration Setting] [LD Bind/Unbind].

130

(j) LD Binding If [LD binding] was selected in (i) Selection of LD binding, next bind the logical disk and assign it to the production server. For details, refer to 4.2.1 Initialization Wizard 2. Setting (j) LD Binding.

(k) Settings confirmation If [Set by wizard form (standard)] was selected in (d) Selection of setting method, what was set from (h) License Unlock on is displayed. For details, refer to 4.2.1 Initialization Wizard 2. Setting (k) Settings confirmation.

(l) Initialization Complete The Initialization Complete screen of the initialization wizard is displayed. The screen display differs if setup failed from if it was done correctly. For details, refer to 4.2.1 Initialization Wizard 2. Setting (l) Initialization Complete or (m) If setup fails.

131

4.3.Host Information Confirmation

Perform the procedures below to confirm that production server host information has been stored.

- For Windows Refer to 4.3.2 Host Information Confirmation Using Storage Manager Client (Web GUI) and confirm that host information has been stored. If host information has not been stored, refer to 4.3.1 Host Information Collection and Storage Using File Output and after performing host information collection and storage using file output, refer to 4.3.2 Host Information Confirmation Using Storage Manager Client (Web GUI) and confirm that host information has been stored. - For Linux Refer to 4.3.1 Host Information Collection and Storage Using File Output and perform host information collection and storage using file output. Afterwards, refer to 4.3.2 Host Information Confirmation Using Storage Manager Client (Web GUI) and confirm that host information has been stored.

132

4.3.1.Host Information Collection and Storage Using File Output

Perform the procedure below. 1. Output host information file Refer to 4.1.2 Host Information Collection Using File Output in Windows Environment or 4.1.3 Host Information Collection Using File Output in Linux Environment and output a host information file. 2. Transfer host information file to management server Transfer the host information file to the management server on which Storage Manager server is running. 3. Store host information using host information storage command (iSMhoststore) Execute the host information storage command (iSMhoststore command) from the command prompt (in a windows environment) or the command line (in a Linux environment) on the management server on which the Storage Manager server is operating. In the -import option, specify the host information file that was transferred from the production server. And in the -arrayname option, specify the nickname of the disk array to which the operation applies. Execute the host information collection command (iSMcc_hostinfo command) as a user with administrator privileges in a Windows environment or as a user with root privileges in a Linux environment. Moreover, when performing host information storage, the target disk array that is the storage destination must be being monitored normally from the Storage Manager server. Execution example when the Storage Manager server is operating in a Windows environment
D:\> iSMhoststore -import \ServerName -arrayname StorageName iSMhoststore: 002 Host Information was imported successfully. (Disk Array=StorageName) iSMhoststore: 001 Command completed successfully.

Execution example when the Storage Manager server is operating in a Linux environment
# iSMhoststore -import /tmp/ServerName -arrayname StorageName iSMhoststore: 002 Host Information was imported successfully. (Disk Array=StorageName) iSMhoststore: 001 Command completed successfully.

133

After you execute the host information storage command (iSMhoststore command), message number 002 is output. Check this to confirm that host information storage succeeded.

If another disk array is already installed and you execute the host information storage command (iSMhoststore) in a configuration in which logical disks of an existing disk array are assigned to the production server, even if you correctly specify the disk array name in the -arrayname option, the error message below may be output and host information storage may not be possible. iSMhoststore: 103 Specified Disk Array does not exist. In this case, use the procedure below to correct the host information file and then store the host information again. 1. Open the host information file in a text editor. 2. Delete all iSM_ArrayInfo table descriptions (portions enclosed by <class name=iSM_ArrayInfo> and </class>) except those corresponding to the disk array specified in the -arrayname option. 3. Save the corrected host information file. 4. Re-execute the host information storage command (iSMhoststore) with the -arrayname option specified.

134

4.3.2.Host Information Confirmation Using Storage Manager Client (Web GUI)

Perform the procedure below. 1. Confirmation of connected host list screen Select the target disk array in the main window of the Storage Manager client (Web GUI) and select [Connected Host] to display a list of connected hosts. Confirm that this contains host information that has the host name of the relevant production server.

Figure 4.22

Example of Confirmation of Connected Host List Screen

135

2. Confirmation of connected host detail information screen (HBA list) Right-click the host information that you confirmed in the connected host list screen and select [Properties] to open the connected host properties screen. In the connected host detail information screen, confirm that HBA information (WWNN, WWPN) of the relevant production server is displayed in [HBA List].

Figure 4.23

Example of Confirmation of Connected Host Detail Information Screen

3. Confirmation of connected host detail information screen (disk array port) Confirm that port information of the connected disk array is displayed in [Diskarray Port] when a FC port of the host adapter connected to the disk array is selected in [HBA List] of the connected host detail information screen. If the procedure in 4.3.1 Host Information Collection and Storage Using File Output was performed when the production server did not recognize the logical disks, since disk array port information was not collected and stored, the information is not displayed in [Diskarray Port] in the connected host detail information screen. In this case, performing 4.3.1 Host Information Collection and Storage Using File Output after 4.5 Connection Confirmation from Production Server is finished and store host information again so that disk array port information will be displayed in the connected host detail information screen. Stored host information can be used in LD Bind Easy Configuration or when setting Access Control. Refer to the Configuration Setting Tool Users Manual (GUI) regarding LD Bind Easy Configuration and Access Control.

136

4.4.Logical Disk Addition and Binding

If you did not bind logical disks in the initialization wizard or to add and bind logical disks, logical disk addition and binding can be performed from Easy Configuration LD Bind Easy Configuration or Configuration Setting LD Bind/Unbind. What is manipulated (in double frames below) differs depending on License Unlock and Selection of LD binding in the initialization wizard. Check the flow shown below and perform LD binding.
Host information collection Initialization wizard License unlocking BaseProductAccess Control BaseProduct only

LD binding specification

Bind

Do not bind

Bind

Host information registration confirmation Add and bind LD No Yes

Bind using same RAID configuration as logical disk binding in initialization wizard (Bind in separate pool)

Add and bind LD Yes No

Bind using same RAID configuration as logical disk binding in initialization wizard (Bind in separate pool)

Yes

No
Configuration Setting LD binding Configuration Setting Access Control Setting LD Set creation LD Set/path link LD assignment

No

Yes

Easy Configuration LD Bind Easy Configuration (Host specified)

Easy Configuration LD Bind Easy Configuration (Host not specified)

Connection confirmation from production server Figure 4.24 Flow of Setup After Initialization Wizard Termination

137

How to start Easy Configuration and how to start Configuration Setting are explained below. 1. Starting Easy Configuration After selecting the target disk array from the main window screen of the Storage Manager client, start Easy Configuration by selecting [File] [Configuration Settings/Reference] [Easy Configuration] from the menu bar or by clicking the [Configuration Settings/Reference] icon from the tool bar and selecting [Easy Configuration].

Figure 4.25

Main Window Screen of the Storage Manager Client

Figure 4.26

Selecting Easy Configuration

Select [LD Bind Easy Configuration] from the Easy Configuration menu screen. For details of Easy Configuration, refer to the Configuration Setting Tool Users Manual (GUI).

Figure 4.27

Easy Configuration Menu Screen

138

- Easy Configuration can be performed only at the system administrator level (L3). - In [Batch License Unlock], license unlocking is performed in the same way as in the initialization wizard. 2. Starting Configuration Setting After selecting the target disk array from the main window screen of the Storage Manager client, start Configuration Setting by selecting [File] [Configuration Settings/Reference] [Configuration Setting] from the menu bar in the Storage Manager client (Web GUI) main screen or click the [Configuration Settings/Reference] icon in the tool bar and select [Configuration Setting].

Figure 4.28

Main Window Screen of the Storage Manager Client

Figure 4.29

Starting Configuration Setting

139

To perform binding of logical disks, select [Individual Setting/Reference] [LD Bind/Unbind] from the Configuration Setting menu screen. To perform Access Control Setting, select [Individual Setting/Reference] [Setting Access Control] from the Configuration Setting menu screen. For details of Configuration Setting, refer to the Configuration Setting Tool Users Manual (GUI).

Figure 4.30

Configuration Setting Menu Screen

Configuration Setting can be performed only at the system administrator level (L3).

140

4.5.Connection Confirmation from Production Server

4.5.1.Connection Confirmation in a Windows Environment
1. Confirmation procedure from Windows OS After confirming that a FC cable is connected between the server and the disk array, restart the server and perform confirmation tasks by following the procedure below. (a) Start [Administrative Tools] [Computer Management] [Device Manager]. (b) Click Disk drives and check the number of logical disks (as many as the number of logical disks assigned to the server times the number of access paths from the server to each logical disk are displayed) and the respective disk drives (disk array 1000 SCSI Disk Device). * If none are displayed, the logical disks in the disk array that are assigned to the server are not being recognized by the OS. Check connections between the server and the disk array, AccessControl settings, and the host bus adapter driver setup. <Sample display> When three logical disks are assigned to the server and there are two access paths for each logical disk

Check the total number of devices

Figure 4.31

Device Manager

141

(c) Open [Disk Management] and check the number of logical disks (Number of logical disks assigned to the server are displayed).

Check the total number of disks

Figure 4.32

Disk Management

142

2. StoreWay MultiPath setup and status confirmation If you have not installed StoreWay MultiPath, this task is unnecessary. After confirming that a FC cable is connected between the server and the disk array, restart the server and execute the commands below from the command prompt. Refer to the StoreWay MultiPath Users Manual (Windows) or the StoreWay MultiPath for Windows Installation Guide for details. (a) For a MSCS (Microsoft Cluster Service) environment Execute the following commands from the command prompt. spscmd -avail ::: spscmd -setmscsmode E (b) If not a MSCS environment Execute the following command from the command prompt. spscmd -avail ::: (c) StoreWay MultiPath status confirmation Execute the following command from the command prompt. spscmd -getlun

Look at the messages displayed on command execution (Figure 4.33 Sample spscmd -getlun Output) and confirm the number of logical disks assigned to the server, the number of access paths to each logical disk, and the path status. <Sample display> When two logical disks are assigned to the server and there are two access paths for each logical disk
C:\>spscmd -getlun +++ LogicalUnit #0 +++ <least_size> > 0: Priority=2, PathNumber=4:0:0:0 1: Priority=1, PathNumber=5:0:1:0 +++ LogicalUnit #1 +++ <least_size> > 0: Priority=2, PathNumber=4:0:0:1 1: Priority=1, PathNumber=5:0:1:1

Figure 4.33

Sample spscmd -getlun Output

Note. If nothing is displayed, the logical disks in the disk array that are assigned to the server are not being recognized on any access path. Check the connection between the server and the disk array, AccessControl settings, and host bus adapter driver setup.

143

4.5.2.Connection Confirmation in a Linux Environment

1. Confirmation procedure from Linux OS After confirming that a FC cable is connected between the server and the disk array, restart the server and execute the command below to check the number of logical disks (as many as the number of logical disks assigned to the server times the number of access paths from the server to each logical disk are displayed) and the vendor and model (Bull, FDA1000) of each. Note. If none are displayed, the logical disks in the disk array that are assigned to the server are not being recognized by the OS. Check connections between the server and the disk array, AccessControl settings, and the host bus adapter driver setup. <Sample display> When two logical disks are assigned to the server and there are two access paths for each logical disk
# cat /proc/scsi/scsi Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: xxxxxxx Model: xxxxxxx Type: Direct-Access Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: xxxxxxx Model: xxxxxxx Type: Processor Host: scsi2 Channel: 00 Id: 00 Lun: 00 Rev: xxxx ANSI SCSI revision: 02 Model: NEC Storage 1000 Rev: xxxx Rev: xxxx ANSI SCSI revision: 03

Host bus adapter #1

Vendor: NEC Type:

Direct-Access

ANSI SCSI revision: 04 Rev: xxxx

Host: scsi2 Channel: 00 Id: 00 Lun: 01 Vendor: NEC Type: Model: NEC Storage 1000 Direct-Access ANSI SCSI revision: 04 Rev: xxxx

Host: scsi3 Channel: 00 Id: 00 Lun: 00

Check the number of these

Host bus adapter #2

Vendor: NEC Type:

Model: NEC Storage 1000

Direct-Access

ANSI SCSI revision: 04 Rev: xxxx

Host: scsi3 Channel: 00 Id: 00 Lun: 01 Vendor: NEC Type: Model: NEC Storage 1000 Direct-Access ANSI SCSI revision: 04 Rev: xxxx

Host: scsi4 Channel: 00 Id: 00 Lun: 00 Vendor: NEC Type: Model: NEC Storage 1000 Direct-Access ANSI SCSI revision: 04 Rev: xxxx

Host: scsi4 Channel: 00 Id: 00 Lun: 01 Vendor: NEC Type: Model: NEC Storage 1000 Direct-Access ANSI SCSI revision: 04

(*)

Figure 4.34

Confirmation of Number of LDs in a Linux OS Environment

144

Note.

In an environment in which StoreWay MultiPath is installed, logical disks that are controlled by StoreWay MultiPath control may be displayed. They are displayed after the logical disks recognized by the OS via host bus adapters (host adapter #1 and host bus adapter #2 sections of the above sample display). It depends on the Linux kernel version.

2. StoreWay MultiPath setup and status confirmation If you have not installed StoreWay MultiPath, this task is unnecessary. After confirming that a FC cable is connected between the server and the disk array, restart the server and perform the checks below from the command prompt. Refer to the StoreWay MultiPath Users Manual (Linux) or the StoreWay MultiPath for Linux Installation Guide for details. (a) Confirmation of kernel version Confirm that StoreWay MultiPath supported by the kernel being used is installed. Confirm that kernel version (A) displayed by uname -r and kernel version (B) displayed by rpm -qi are the same.
# uname -r 2.4.X-XX # rpm -qa | grep sps sps-xxx-yyyy # rpm -qi sps-xxx-yyyy Name : sps-X-XXX Relocations: (not relocatable) Version : 2.X.X Vendor: NEC Corporation Release : 2.X.XX.XX Build Date: 200y MM DD hh mm ss Install date: 200y MM DD hh mm ss Build Host: nec.co.jp Group : Utilities/System Source RPM: sps-X-XX.X.src.rpm Size : XXXXXX License: commercial Summary : SCSI dual-path driver and utilities for NEC Storage Description : This package contains a driver, daemon and some utilities. The driver (dd_mod,dd) provides the redundant SCSI-path for NEC Storage Disk Array System. The daemon (dd_daemon) supervises the driver. And, some utilities work for the maintenance. It runs on 2.4.X.XX kernel.

Kernel version (A)

Kernel version (B) in which StoreWay MultiPath is supported

Figure 4.35

Confirmation of Kernel Version

Note. This may differ somewhat if the OS is a 2.6 series kernel.

145

(b) StoreWay MultiPath status confirmation - For a 2.4 series kernel Check /proc/dualpath/ddX (where X is a, b, c as many as number of logical disks assigned to server). If the partition-info field is NML, the paths have been multiplexed normally. Note. If nothing is displayed, the logical disks in the disk array that are assigned to the server are not being recognized on any access path. Check connections between the server and the disk array, AccessControl settings, and the host bus adapter driver setup. <Sample display> When two logical disks are assigned to the server and there are two access paths for each logical disk
# cat /proc/dualpath/dda disk-info: NEC , NEC Storage 1000 , xxxxxxxxxxxxxxxx, xxxxx path-info: 0: 2, 0, 0, ACT, 1 path-info: 2: 3, 0, 0, HOT, 2 lb-info: S partition-info: 0, NML # cat /proc/dualpath/ddb disk-info: NEC , NEC Storage 1000 , xxxxxxxxxxxxxxxx, xxxxx path-info: 1: 2, 0, 0, ACT, 1 path-info: 3: 3, 0, 0, HOT, 2 lb-info: S partition-info: 0, NML

# Figure 4.36 StoreWay MultiPath Status Confirmation (for 2.4 series)

- For a 2.6 series kernel Check /proc/scsi/sps/ddX (where X is a, b, c as many as number of logical disks assigned to server). If a path-info line exists only for multiplexed portions of each device and the device-info: Status fields all are NML, the paths have been multiplexed normally. Note. If nothing is displayed, the logical disks in the disk array that are assigned to the server are not being recognized on any access path. Check connections between the server and the disk array, AccessControl settings, and the host bus adapter driver setup.

146

<Sample display> When two logical disks are assigned to the server and there are two access paths for each logical disk
# cat /proc/scsi/sps/dda device:/dev/dda disk-info:NEC ,NEC Storage 1000 ,xxxxxxxxxxxxxxxx,xxxxx device-info:Host:scsi:4 Channel:0 Id:0 Lun:0 Status:NML LoadBalance:D2 path-info:0 Host:scsi:2 Channel:0 Id:0 Lun:0 Priority:1 Watch:Enable Status:ACT path-info:2 Host:scsi:3 Channel:0 Id:0 Lun:0 Priority:2 Watch:Enable Status:ACT # cat /proc/scsi/sps/ddb device:/dev/dda disk-info:NEC ,NEC Storage 1000 ,xxxxxxxxxxxxxxxx,xxxxx device-info:Host:scsi:4 Channel:0 Id:0 Lun:1 Status:NML LoadBalance:D2 path-info:1 Host:scsi:2 Channel:0 Id:0 Lun:1 Priority:1 Watch:Enable Status:ACT path-info:3 Host:scsi:3 Channel:0 Id:0 Lun:1 Priority:2 Watch:Enable Status:ACT

# Figure 4.37 StoreWay MultiPath Status Confirmation (for 2.6 series)

(c) Confirmation of path patrol daemon Confirm that the path patrol daemon is running. If the path patrol daemon is running, the message shown below is displayed.
# /etc/rc.d/init.d/dd_daemon status dd_daemon (pid XXX) is running ... #

Figure 4.38

Confirmation of Path Patrol Daemon

147

5.Power-Off Procedure
5.1.Power-Off Procedure
1. When powering off, first turn off the power of the production server. 2. Press the power button at the right end of the rear face of the disk array unit for at least five seconds. The READY LED blinks rapidly if power is disrupted. Note. If two controllers are installed, press the power button on either of the controllers. You need not press both buttons. Pressing the power button for 10 seconds or longer continuously forcibly turns off the power, which may be bad for the disk array unit. Accordingly, stop pressing the button as soon as possible after power-off is accepted. 3. The power of the disk array unit and of disk enclosures is turned off within ten minutes. (All LEDs other than those on the power supplies go off and the fans stop rotating.) 4. Turn off the AC power of the disk array unit, extended BBU, and disk enclosures. Disconnect the AC power of the disk array unit and disk enclosures by unplugging the AC input receptacle or disconnecting it at a breaker. Start power-off for the disk array unit and disk enclosures after power-off of the production server is completed. Turn off the AC power only after the RDY LEDs go off. If one or more disk enclosures are connected to the disk array unit, always turn off the AC power of the disk enclosures after power-off of the disk array unit is completed.

148

5.2.Notes on Turning Off the AC Power

1. User data backup If you disconnect the AC power without performing the procedures in 5.1 Power-Off Procedure or 2.8.4 Power Control Methods Beside Power Button, the disk array unit saves the cache by battery. Product Name Optima1500 Without Extended BBU 24 hours With Extended BBU 72 hours (3 days)

Table 5.1 2.

Battery Backup Retention Time

User data cant be retained over battery backup retention time. When passing the retention time, user data may loss. When cases more than the prescribed battery backup retention time exceed 4 times a year, life of the battery shortens. (guarantees of the battery are not had.) The extended BBU varies by product name.

Instruction when using Data Replication Function

Update difference Information* managed by data replication function is built on the storage system volume or cache memory. When that storage system volume is not built, the information of update will be built on cache memory. So the device changes in a battery backup state when it stops however the power supply of a disk array unit is cut exactly according to procedure in 5.1 Power-Off Procedure. In this state, when it is over battery backup time limit of a disk array device, storage system information on a cache memory disappears, and it will be in condition as follows. * Information of storage system Activity State Separate State Synchronous State Separated (separated) Separate Execution (sep/exec) Synchronous Execution (rpl/exec) Synchronous State (rpl/sync) Restore Execution (rst/exec) Synchronous State (rst/sync) Table 5.2 State of Pair A difference becomes all domains. The state becomes fault and copy is stopped. A difference becomes all domains, replication starts again from the beginning automatically. The state becomes fault and copy is stopped. A difference becomes all domains, replication starts again from the beginning automatically.

Replicate State

Restore State

Data Replication Function

149

For restoration of the pair which became fault, please perform the following replication work. 1. Perform Forced Separate operation in RV object. 2. Perform restoring operation again. ( Replicate Separate or Restore ) Caution. Copying will be started again, all domains of an ethic disk become objective, it will be full copy.

In the case of using replication function, we recommend firmly to use a storage system information saving function and build storage system volume from the Storage Manager. Capacity of storage system volume is 8.9 GB. Turning off the power supply in a normal procedure, storage system information will be saved in the storage system volume. In the condition of not being built storage system volume, turning off the power make the life span of battery short, although storage system information is saved on cache memory within time of backup. When you dont use storage system volume, we recommend turning it on within 24 hours. Note. Storage system information saving function means the function to save storage system information like a map for a difference of the duties volume (MV) and the reproduction volume (RV) on the disk drive.

5.3.Auto-Shutdown Function
The auto-shutdown is a function to save user data, difference map, and composition information in a cache to a disk drive automatically when host IO are not issued for five minutes. When the power is disconnected without following the normal shutdown procedure with the unwritten data remained on the cache, battery backup function operates to protect the data on the cache. But if the battery remains at this status for a long time, the battery will be discharged and the data on the cache may be lost.

As the auto-shutdown function guarantees the data on the cache to be written to the disk drive, data will be protected although the unit is powered off without following the shutdown procedures.

Completion of the automatic shutdown can be judged by the rapid blinking of the POWER LED. Even if power-off / powerfail occur in the automatic shutdown sequence completed, they are not notified of for five minutes (the SNMP trap does not occur). This is not to notify you of a fault to occur by the gap of the timing of the power-off of the both system in the manual power-down. But they are notified you of when power-off / powerfail continued in single system in automatic shutdown sequence completed more than five minutes.

150

6.Expansion Methods
6.1.Notes on Expansion
Check the precautions and working methods below when performing installation tasks for options installed in the disk array unit. Options and cables should be parts that Bull specifies. There is a charge for repairs associated with malfunction, failure, or damage to the unit that occurs as a result of using parts other than those specified.

About electrostatic countermeasures The internal parts of the disk array unit are electronic parts that are weak against static electricity. Be careful of component failure due to static electricity when working. Wearing a wrist strap (arm band, antistatic glove, or other) Wrap a wrist grounding strap around your wrist. If you do not have one, touching an uncoated metal surface of the cabinet before touching a part discharges static electricity stored in your body. Also periodically touch a metal surface while working so that you discharge static electricity. Workplace checks Work on a floor for which measures to prevent static electricity have been taken or on concrete. If working on carpet or another location in which static electricity readily occurs, do the work after taking measures to prevent static electricity.

Use of work stands Place the disk array unit on an antistatic mat and do the work on that as well.

Clothing Do not work wearing clothing made of wool and synthetic fibers. Work wearing antistatic shoes. Remove precious metals (such as rings, bracelets, or watches) before working.

Parts handling Put parts to install in antistatic bags until inserting them in the disk array unit. Hold the edges of each part and do not touch pins or mounting parts. When storing or transporting parts, put them in antistatic bags.

151

6.2.Controller
< Removing a controller from the chassis >
1. Confirm that the power is turned off. 2. Confirm that the power cable of the unit and the cable of the controller are not connected. 3. Take an ejector of the controller in each hand and open them to the left and right. The ejectors are locked at bottom. The controller comes out by freeing it on the left and right.

Ejector

Figure 6.1

Removing Controller

4. Holding the ejectors in both hands, pull horizontally approximately 10 cm. 5. Hold the controller firmly in both hands and pull it all the way out.

152

< Installing a controller in the chassis > 1. Insert the controller in the chassis. Firmly push it all the way in. 2. Close the ejectors and firmly press the protruding portions of the ejectors. Confirm that both ejectors are locked.

If the controller is not fully inserted, it could lead to malfunction.

6.3.Disk Drive
For installing and removing disk drives, Refer to the sections below. 2.6 Installation 2.6.2 2.6.4 Installation of Disk Drives Installing and Removing Front Mask

When removing a disk drive that has been set up, contact your maintenance service agent. If it is removed without changing settings inside the unit, a service LED on the controller will turn on and the status on the Storage Manager will be fault.

6.4.Disk Enclosure
For installing and removing disk enclosures, see the sections below. 2.6 Installation 2.6.1 2.6.4 2.7 Moving Disk Array Unit and Disk Enclosures Installing and Removing Front Mask

Cable Connections 2.7.3 2.7.7 SAS Cable Connection and DE and PD Numbers Connecting Power Cables

When removing a disk enclosure that has been set up, contact your maintenance service agent. If it is removed without changing settings inside the unit, a service LED on the controller will turn on and the status on the Storage Manager will be fault.

153

6.5.Extended BBU
For installing and removing the extended BBU, see the sections below. 2.6 2.7 Installation 2.6.5 2.7.6 Mounting an Extended BBU on a Rack Connection of Extended BBU and Controllers Cable Connections

Turn on the power by following procedures.

1. 2. 3.

Turn on the AC switch of extended BBU. Turn on the power supply of extended BBU. Turn on the power supply of the disk array unit. When removing an extended BBU that has been set up, contact your maintenance service agent. If it is removed without changing settings inside the unit, a service LED on the controller will turn on and the status on the Storage Manager will be fault.

154

6.6.Expansion Ports
The procedure for installing expansion ports is as follows. 1. Remove the controller from the chassis. Refer to 6.2 Controller.

2.

Remove the cover of the controller. Remove the cover by sliding it while pressing the lock (indicated in red in figure below).

Figure 6.2 3.

Removing the Cover of the Controller

The following shows the surface of the controller and the location of the expansion port spacer. Confirm the location of the expansion port spacer.

Magnification of Spacer

Figure 6.3

Expansion Port Spacer

155

4.

Confirm the locations of the respective connectors of the controller and the expansion port rear surface (red rectangles in figures below).

Guard panel

Figure 6.4

Controller

Figure 6.5 5.

Expansion Port

Remove the guard panel on the front view of the controller (blue rectangle in figure above). Next, insert the expansion port by matching the connector locations. (Insert by matching the expansion port front view panel location to the reference.)

Figure 6.6

Connector Location of Expansion Port

156

6.

Confirm that it is firmly inserted and there is no play in the expansion port. Screw in at the two places in the figure above.

7.

Install the cover of the controller. Match the end of the cover to the grove in the controller. Put it on so that the location of the side lock of the cover (figure below) meets it.

Figure 6.7 8.

Installing the Cover (1)

Close the cover by sliding it as shown in the figure below.

Figure 6.8 9. Install the controller. Refer to 6.2 Controller.

Installing the Cover (2)

157

10. Check the operation of the unit after expansion port installation. Power-on and confirm normal startup. Confirm that the LEDs (LINK and ACTIVE) in the places in the figure below are blinking.

Figure 6.9

LINK and ACTIVE LED

The expansion port installation task is finished.

158

6.7.Changing DIP Switches

This section describes the procedure for changing the DIP switches on the surface of a controller. Have a toothpick or other fine-tipped tool available. 1. Remove the controller from the chassis. Refer to 6.2 Controller. 2. Remove the cover of the controller. Remove the cover by sliding it while pressing the lock (indicated in red in figure below).

Figure 6.10

Removing the Cover

159

3.

The following shows the location of the DIP switches on the surface of the controller.

Figure 6.11 4.

DIP Switches

Change the DIP switches on the surface of the controller. Operate the switches using a fine-tipped tool such as a toothpick.

160

5.

Install the cover of the controller. Match the end of the cover to the groove in the controller. Put it on so that the location of the side lock of the cover (figure below) meets it.

Figure 6.12

Installing the Cover (1)

6.

Close the cover by sliding it as shown in the figure below.

Figure 6.13 7. Install the controller. Refer to 6.2 Controller.

Installing the Cover (2)

161

6.8.Changing Setting by Storage Manager

Disk array setting change can be done by re-executing the initialization wizard or in Easy Configuration or Configuration Setting. To make individual settings, use Easy Configuration or Configuration Setting.

6.8.1.Changing Setting by Initialization Wizard

This section explains performing setting change by re-executing the initialization wizard.

(a) Start screen The start screen of the initialization wizard is displayed. Manipulated contents are the same as when set the first time. Check the contents and proceed to the next screen. For details, refer to 4.2.1 Initialization Wizard 2. Setting (a) Start screen. (b) Selection of disk array Selection of disk array specifies the disk array to be initialized.

Figure 6.14

Selection of disk array Screen

162

The disk arrays that are found by retrieval are displayed in a list. What is displayed in [Initialization] varies according to where the initialization wizard was cancelled the previous time. For details, refer to Table 6.1. Select the disk array to set up from the list and click the [Next] button. Display Contents Disk Array Status Status immediately following disk array installation. Since initialization wizard network setting has not been performed, it is not subject to Storage Manager monitoring. not execute Initialization by the initialization wizard or maintenance personnel is necessary. Processing through Network parameters setting or Setting of host connection port has been performed by the initialization suspended wizard but the BaseProduct license has not been unlocked. The disk array is subject to Storage Manager monitoring. (*) Status in which unlocking has been done up to and including the BaseProduct license. The disk array is subject to Storage finished Manager monitoring. (*) Table 6.1 Initialization Status of Disk Array

(*) Being subject to Storage Monitor monitoring means that the subject disk array is displayed in the main screen of Storage Manager client. If the initialization status of a disk array is [suspended] or [finished], the message box shown below is displayed to stop disk array monitoring and put the subject disk array in a Configuration Setting state.

Figure 6.15

Monitoring Stop Confirmation Message Box

163

(c) Confirmation of disk array connection state Confirm the disk array connections. Manipulated contents are the same as when set the first time. For details, refer to 4.2.1 Initialization Wizard 2. Setting (c) Confirmation of disk array connection state.

(d) Selection of setting method Selection of setting method selects the initialization method. Manipulated contents are the same as when set the first time. Specify [Set by wizard form (standard)] and click the [Next] button. For details, refer to 4.2.1 Initialization Wizard 2. Setting (d) Selection of setting method.

(e) Selection method of host information collection This specifies the host information collection method. Manipulated contents are the same as when set the first time. Check what is displayed in the screen, specify whether or not to perform automatic collection of host information, and click the [Next] button. For details, refer to 4.2.1 Initialization Wizard 2. Setting (e) Selection method of host information collection.

(f) Network parameters setting Network parameters setting sets network addresses so that the disk array can be monitored from Storage Manager. For a disk array for which a network is already set, the addresses set for the disk array are displayed. To change an address, perform setup again. For the IP address of a controller, specify a valid value other than 10.1.0.0 through 10.1.0.255 or 0.0.0.0. To not specify a gateway address, input 0.0.0.0. For details, refer to 4.2.1 Initialization Wizard 2. Setting (f) Network parameters setting.

164

If settings have been made to both controllers, only Set to both controllers can be specified, and if settings have been made only to controller 0, only Only set to controller 0 can be specified. If settings have been made only to controller 0, to also make monitoring from controller 1 available, connect the management server to controller 1 by a LAN cable and make changes to disk array settings and environment settings, respectively. Disk array: [Configuration Setting] [Disk array setting] [Network] tab For details, refer to the Configuration Setting Tool Users Manual (GUI). Environment setting: Storage Manager server Setting Utility program For details, refer to the Storage Manager Installation Guide accompanying BaseProduct. If disk array setup alone is performed without having changed the Storage Manager server environment settings, a warning dialog is displayed.

Figure 6.16 -

Warning Dialog

If [Set to both controllers] is performed when only one controller is connected by LAN cable, the disk array changes the addresses of both controllers, but Storage Manager server environment setting changes only an address for which monitoring is available. To make monitoring from both controllers available, connect the management server to controller 1 by a LAN cable and make changes to Storage Manager server environment settings to match the IP address of the disk array to monitor. Refer to the Storage Manager Installation Guide accompanying BaseProduct concerning changing environment settings. Disk array Controller Controller Disk Array Address A C (Change) Address B D (Change) Setting Utility Address A C (Change) Address B (Not change) Monitoring Available Not available LAN cable
Management server

Controller 0 Controller 1

165

If an IP address, subnet mask, or gateway address has not been set correctly, monitoring by Storage Manager is not possible. If error message [05068] Failed to set network parameter. is displayed, refer to the Help.

(g) Setting of host connection port Setting of host connection port sets up the host connection port of the disk array. Default values or settings from the last time are displayed in a list. To change settings, select the port to edit from the list and click the [Edit] button. Manipulated contents of the edit screen are the same as when set the first time. After editing is finished, confirm that the edited contents are correct in the confirmation screen and click the [Execute] button. For details, refer to 4.2.1 Initialization Wizard 2. Setting (g) Setting of host connection port.

If a platform value other than WN or LX is set, editing is not possible. Edit in [Host connecting port] of [Configuration Setting].

(h) License Unlock Unlock the license of the program product that you have purchased. For details, refer to 4.2.1 Initialization Wizard 2. Setting (h) License Unlock.

A license that is already unlocked need not be input again.

166

(i) Selection of LD binding Specify [LD binding] or [Not LD binding]. For details, refer to 4.2.1 Initialization Wizard 2. Setting (i) Selection of LD binding.

If logical disks have already been bound, a logical disk is bound using unused physical disks. If logical disks are already bound and you do not have the unused physical disks needed for the RAID type that you wish to bind, specify [Not LD binding]. The unused physical disks needed for RAID types are as follows. RAID1 (Basic Pool): Configured on 2 physical disks RAID6 (4+PQ) (Dynamic Pool): Configured on 6 physical disks RAID6 (8+PQ) (Dynamic Pool): Configured on 10 physical disks To unbind a logical disk that is already bound, use [Configuration Setting] [LD Bind/Unbind].

(j) LD Binding If [LD binding] was selected in (i) Selection of LD binding, next bind the logical disk and assign it to the production server. For details, refer to 4.2.1 Initialization Wizard 2. Setting (j) LD Binding.

(k) Settings confirmation If [Set by wizard form (standard)] was selected in (d) Selection of setting method, settings from (h) License Unlock is displayed. For details, refer to 4.2.1 Initialization Wizard 2. Setting (k) Settings confirmation.

(l) Initialization Complete The Initialization Complete screen of the initialization wizard is displayed. The screen display differs if setup failed from if it was done correctly. For details, refer to 4.2.1 Initialization Wizard 2. Setting (l) Initialization Complete or (m) If setup fails.

167

6.8.2.Individual Setting by Configuration Setting and Easy Configuration

Individual settings can be made from Configuration Setting or Easy Configuration. Refer to 4.4 Logical Disk Addition and Binding concerning how to start Configuration Setting and Easy Configuration. Configuration Setting (1) Host recognize volume (Selection method of host information collection (2) Network (Network parameters setting) (3) Host connection port (Setting of host connection port) (4) License Unlock (License unlocking) (5) LD Binding (LD binding) Table 6.3 Setting Host Recognize Volume mode Easy Configuration

Network Host connecting port Licenses

Batch License Unlock

LD Bind/Unbind LD Bind Easy Configuration Setting Access Control Configuration Setting and Easy Configuration

168

Functions provided by the initialization wizard are in parentheses. [Setting Host Recognize Volume mode] of [Configuration Setting], which is the same as [Selection method of host information collection] of the initialization wizard, is set when automatically collecting host information and used when binding a logical disk using [LD Bind Easy Configuration] of [Easy Configuration]. It need not be set if host information has already been obtained in initialization. After making the setting effective and binding a logical disk, be sure to make the setting ineffective (uncheck it).

To make the host recognize volume setting effective, the conditions below must be satisfied. 1. Production servers connected to the disk array must be Windows only and systems all must be new servers (servers that have not begun operation). If an operating host is connected, the file system may be affected due to the host recognize volume. iSM volume list command or ControlCommand must be installed on a host that is to be connected.

2.

Do not make the host recognize volume setting effective if host information has already been obtained in initialization.

169

7.Troubleshooting
This chapter describes trouble conditions and actions of the disk array controller.

7.1.Before You Call

When trouble other than the following is detected, or when you could not recover the disk array unit from the trouble by taking the corresponding action, please call to ask questions or consult on a failure or abnormality of the disk array unit. Please have the following items ready. - The warranty and this manual - Conditions of the fault or abnormality, notes on content of questions - Notes on the configuration of the disk array unit and software used with the disk array unit - Notes on the configuration of the connection of the host unit to the disk array unit and the configuration of peripheral equipment connected to the host unit - Manuals of the host unit and peripheral equipment connected to the host unit and manuals of software used

7.2.Contacts for Questions and Consultation

For questions and consultation about the disk array unit, contact Bull sales, the sales agent from whom you purchased it, or your maintenance service agent.

170

7.3.Troubleshooting According to Device Conditions

This section is organized by location. 1. Trouble in disk array unit (front panel LED status) 2. Trouble in disk array unit (rear panel controller LED status) 3. Trouble in disk array unit or disk enclosure (rear panel power LED status) 4. Trouble in disk enclosure 5. Trouble in extended BBU 6. Trouble in SAS cable connection

1.

Trouble in disk array unit (front panel LED status) Condition Action This is not a fault. This indicates that the disk array unit is in normal operation after turning on. This indicates the disk array unit power-on sequence has not been completed. It takes several minutes until POWER LED illuminates after turning on the unit. * If POWER LED does not illuminate in 10 minutes, check the following. Confirm that AC power is being supplied to the unit. Confirm that POWER GOOD LED on the back of the unit illuminates. If this LED is out, check cable connection and power source.

POWER LED (green) illuminates, but SERVICE LED is out POWER LED (green) is out

SERVICE LED (orange) illuminates

This indicates that the disk array unit, connected disk enclosure, or extended BBU requires maintenance. Since there are two or more maintenance requests at the same time, check all of the following. - Confirm that AC power is being supplied to both PS0 and PS1 in the disk array unit, connected disk enclosure, or extended BBU. To ensure that AC power is being supplied, confirm that POWER LEDs of the disk array unit and disk enclosure illuminate and CHARGE LED of the extended BBU is not out. - When SERVICE LED of the connected disk enclosure illuminates, refer to the description of SERVICE LED illuminates in 4. Trouble in disk enclosure. - When either of the FUALT LEDs of the extended BBU illuminates, refer to the description of BBU FAULT LED blinks in 5. Trouble in extended BBU. - When the last operation is maintenance, processing such as disk recovery may take time. Ask the maintenance personnel for the estimated time of completion. If the disk is not recovered beyond the estimated time, ask the maintenance personnel to investigate.

171

Condition SERVICE LED (orange) blinks

Action This indicates that the power-on sequence or download sequence of the disk array unit is in progress. It takes several minutes from start to finish of the sequence. When SERVICE LED still blinks in 10 minutes, there may be a failure. Caution. Do not turn off the power or AC power while SERVICE LED blinks.

SERVICE LED (orange) iterates turning on and off at intervals (illuminating for 5 seconds and going out for 7 seconds)

This indicates that battery backup failed in the last power-off status. Files may be destroyed. Restore those files using backup files. This may occur because of the following causes. Remove the appropriate cause. 1. The power-off status continued exceeding the battery backup retention time when disconnecting the AC power without performing the power-off procedure. 2. Battery backup was performed past the battery or extended BBU life spans. 3. The disk array unit or extended BBU was continuously used or has been used at the temperature higher than the predetermined temperature. 4. Battery backup was or has been performed more than the predetermined backup frequency. Caution. In the cases other than 1, the battery backup retention time of the battery or extended BBU cannot be guaranteed. It is necessary to replace the battery or extended BBU due to its life span. Contact your sales or maintenance service agent. (There is a charge for battery exchange due to life span.)

172

2.

Trouble in disk array unit (rear panel controller LED status) Condition Action This indicates that the power-on sequence is in progress. It takes several minutes from start to finish of the sequence. When READY LED still illuminates in 10 minutes, there may be a failure. This is not a fault. This indicates that the controller is in normal operation. This indicates that power is disrupted. It takes several minutes from start to finish of the sequence. When READY LED still blinks rapidly in 10 minutes, there may be a failure. This is not a fault. This indicates that data is retained by the battery. This is not a fault. It is one year before the end of the life span of the battery installed in the disk array unit. A battery purchase and maintenance request must be made. Contact your sales or maintenance service agent. (There is a charge for battery exchange due to life span.) When connecting a cable to the LAN connector, LINK LED (green) may not turn on because of the following causes. - The power of HUB, switch, or server to connect has not been turned on. - The power supply of HUB, switch, or server to connect is at fault. - The cable type is wrong. A cross cable and straight cable are not recognized automatically. Use a cable following the predetermined connection method. - The Speed and Duplex settings do not match. Auto Detect is set as default. Since connecting to a device in full duplex mode could cause abnormal operation, set Auto Detect or Half Duplex to the device to connect. (To set Full Duplex, ask your sales or maintenance service agent.) - Depending on the type of hub, it may not illuminate or it may blink. This is not a fault. ACTIVE LED (orange) illuminates when connection is established via the disk array unit monitoring protocol with a cable connected to the LAN connector. If the cable is removed from the unit, ACTIVE LED still illuminates for a while.

READY LED (green) illuminates

READY LED (green) blinks READY LED (green) blinks rapidly

BACK UP LED (orange) blinks while AC power is disconnected The battery FAULT LED (orange) blinks

LINK LED (green) of the LAN connector is out, or blinks

ACTIVE LED (orange) of the LAN connector illuminates, or blinks

173

3.

Trouble in disk array unit or disk enclosure (rear panel power LED status) Condition Action This is not a fault. This indicates that AC power is being supplied to the unit and the power supply is in normal operation. Caution. The unit has dual power supply configuration. Therefore, SERVICE LED illuminates when neither PS0 nor PS1 illuminates.

POWER GOOD LED (green) illuminates

4.

Trouble in disk enclosure Condition Action This is not a fault. This indicates that the disk enclosure is in normal operation after turning on. This indicates that starting the disk enclosure has not been complete. The power of the disk enclosure is turned on in conjunction with the power of the connected disk enclosure or disk array unit. It takes several minutes until POWER LED of the disk enclosure turns on after turning on the unit power. If POWER LED does not illuminate in 10 minutes, check the following. - Check whether POWER GOOD LED of the disk enclosure power supply illuminates, indicating that the power is supplied to the disk enclosure. - Check cable connection status to confirm whether this disk enclosure is normally connected to other disk enclosures or the disk array unit. - Check POWER LED of the disk array unit to confirm whether the power of the disk array unit was turned on. If this LED is out, check whether the power source is normal. This indicates that the disk enclosure is out of order or maintenance has not been complete. - When the last operation is maintenance, processing such as disk recovery may take time. Ask the maintenance personnel for the estimated time of completion. If the disk is not recovered beyond the estimated time, ask the maintenance personnel to investigate.

POWER LED (green) illuminates, but SERVICE LED (orange) is out POWER LED (green) is out

SERVICE LED (orange) illuminates

174

5.

Trouble in extended BBU Condition Action CHARGE LED does not illuminate when the power of the extended BBU is not turned on. - Confirm that the AC switch of the extended BBU is ON. - Check whether cable connection and power source are normal. This indicates that AC power is being supplied to the extended BBU. This is not a fault. It is one year before the end of the life span of the extended BBU connected to the disk array unit. An extended BBU purchase and maintenance request must be made. Contact your sales or maintenance service agent. (There is a charge for battery exchange due to life span.) The extended BBU may be out of order or may not connect to the disk array unit, or the power of the disk array unit may not be turned on. This LED turns on five minutes after the extended BBU detected an abnormality. - Check the cable connection between the disk enclosure and the disk array unit. - Confirm that the power of the disk array unit has been turned on. Caution. When only the power of the extended BBU has been turned on, it is assumed that connection has not been established.

CHARGE LED (green) does not illuminate

CHARGE LED (green) blinks BBU FAULT LED (orange) blinks

BBU FAULT LED (orange) illuminates

6.

Trouble in SAS cable connection Action When the pool / logical disk / spare are already bounded, they must be released before changing the connection. After turning off the power of the unit and changing the connection of the SAS cable, disconnect PD80 to 83 and turn on the power of the unit again. Wait until it becomes ready. If the unit became ready, insert PD80 to 83 and wait until it becomes ready. If the PD80 to 83 become ready state, the procedure is completed. When the pool / logical disk / spare are already bounded, they must be released before changing the connection. After turning off the power of the unit, change the connection of the SAS cable. Turn on the power supply again and wait until it becomes ready. If the unit becomes ready state, the procedure is completed.

Condition Changing the connection of DE (including DE08)

Changing the connection of the DE (excluding DE08)

175

7.4.Errors on Software Installation

Condition Installation terminated abnormally Action The following are possible causes. Eliminate the cause and perform setup again. The user that logged in has insufficient privileges Perform installation by logging in as a user having administrator privileges for Windows or root privileges for Linux. An unsupported OS is being used Refer to the installation guide for the software being installed and check the supported OS. Disk has insufficient free capacity Refer to the installation guide for the software being installed and check the disk capacity needed to install it. There is a problem with quota management or file screening setup If you apply quota management*1 or file screening*2 to an installation destination disk or folder, use it appropriately. Misusing these may become a problem during installation or during operation. *1 This function puts a limit on used capacity and makes it impossible to use more than the set limit. *2 This function makes it impossible to save files of specific file names (or extensions). After JRE installation, news of the latest edition of Java came. If you update JRE, it is possible that it will be changed into an unsupported JRE. Therefore, after JRE installation, it is recommended that automatic updating of JRE be made ineffective.

176

7.5.Errors on Using Storage Manager Server or Storage Manager Client

Condition The screen being operated on disappeared Action The following is a possible cause. Eliminate the cause and perform the operation again. When connecting to Storage Manager server from Storage Manager client (Web GUI), nothing is displayed in the Web browsers window and only Page displayed is displayed in the status bar in the lower part of the window. The following message is output when Storage Manager client (Win GUI) is executed from Storage Manager client (Web GUI). 01094 An error occurred while downloading (197) Check whether it has been set to go through a proxy server. After terminating the initialization wizard, [01286-00] Configuration Setting screen display failed was displayed when I tried to start Configuration Setting and it did not start. It is possible that it is hidden by another screen. Switch screens using ALT+TAB. The following are possible causes. - JRE has not been installed - Web browser security settings have not been made - The network load is high For details, refer to the Storage Manager Installation Guide accompanying BaseProduct.

This error occurs when going through a proxy server is specified in Web browser setup. Specify a proxy exception in Web browser setup and set it so that connection to Storage Manager server does not go through the proxy server. For details, refer to Caution in 3.3.2 Installation of Storage Manager Client.

The following is a possible cause. Eliminate the cause and perform the operation again. An unsupported JRE (Java Runtime Environment) may have been installed. Refer to the Storage Manager Installation Guide accompanying BaseProduct and change to a JRE that is supported.

177

7.6.Troubleshooting in Initialization Wizard/Easy Configuration

In this section, troubles are classified as follows, according to the location where the trouble occurs. 1. Disk array to be set up by initialization wizard was not found 2. Network setting failed 3. Host information is not displayed 4. Logical disk cannot be bound 5. Error is displayed in setup completion screen (When setting method is [Set by wizard form (standard)]) 6. Batch setting with initialization file failed 1. Disk array to be set up by initialization wizard was not found Condition Target disk array is not displayed in Selection of disk array screen Action The following are possible causes. Eliminate the cause and perform setup again. - Target disk array is not properly connected to management server by a LAN. The initialization wizard applies to the Optima1500. The management server and disk array must be in the same network environment (for example, a network connected by IP addresses 192.168.1.xxx for different xxx) and connected by a LAN. - Port number 2730 is being used elsewhere. For disk arrays for which initialization was never performed, the User Datagram Protocol (UDP is used to retrieve disk arrays on the same network (for example, a network connected by IP addresses 192.168.1.xxx for different xxx) using port number 2730. If a firewall is installed, set it up so that packets used for retrieval is passed for the management server and disk array. - Network address is invalid. When disk array network setting was performed, a different network address from the management server may have been set. Refer to 7.6.1 Changing Network Settings for Monitoring Disk Arrays from Storage Manager to change the setting.

178

2. Network setting failed Condition [05068] Failed to set network parameter is displayed Action The following is a possible cause. Eliminate the cause and perform setup again. - The management server network address differs from the address input in the Network parameters setting screen. Refer to 7.6.1 Changing Network Settings for Monitoring Disk Arrays from Storage Manager.

3. Host information is not displayed Condition Nothing is displayed in Selection host in the LD Binding screen of the initialization wizard or the LD Bind Easy Configuration screen of Easy Configuration Action The following are possible causes. Eliminate the cause and perform setup again. - Automatic collection of host information failed. ([Automatic collection] was specified in the Selection method of host information collection screen of the initialization wizard.) Check as follows. * Refer to Chapter 6 Volume List Installation (Windows)of the Storage Manager Installation Guide for OS in which automatic collection of host information is possible. 1. Confirm that the production server is a Windows OS. 2. Confirm that the iSMvollist command or ControlCommand has been installed on the production server. (This can be checked from [Add or Remove Programs] in [Control Panel].) 3. Since it is possible that the host recognize volume is not being recognized by the production server (OS), restart iSM Host Agent Service (Disk Array Manager Host Agent). (Execute from [Services] in [Administrative Tools].) Three minutes later, click the [Refresh] button in the LD binding screen of the Storage Manager client (Web GUI) initialization wizard, select [Update with info from iSM server], click [OK], and perform host specification again. 4. If host information is not displayed in the LD binding screen even after executing procedure 3 above, refer to 4.1.2 Host Information Collection Using File Output in Windows Environment. Output the host information file and transfer it to the client. Afterwards, click the [Refresh] button in the LD binding screen, select [Update with info file], click [OK], and then perform host specification in the LD binding screen again. 5. If host information is not displayed in the LD binding screen even after executing procedure 4 above, it is possible that necessary information failed to be fetched in initialization. Contact your maintenance service agent. *Continue to next page

179

Condition (* Continued)

Action A file was output by the host information collection command but not transferred. Check as follows. 1. The host information file that is output must be manually transferred (saved) to the host on which Storage Manager client was started. If it was not transferred, transfer it using file transfer or USB memory. 2. Get host information from the host information file that was output by clicking the [Refresh] button in the LD binding screen and then selecting [Update with info file.]. [Automatic collection] is not specified in the Selection method of host information collection screen. File output is also not performed by the host information collection command. Refer to 4.1.2 Host Information Collection Using File Output in Windows Environment and 4.1.3 Collecting Host Information Using File Output in Linux Environment and perform host information collection by file output. After the host information file is output, perform the operations in the procedure below. 1. The host information file that is output must be manually transferred (saved) to the host on which Storage Manager client was started. If it was not transferred, transfer it using file transfer or USB memory. Get host information from the host information file that was output by clicking the [Refresh] button in the LD binding screen and then selecting [Update with info file.].

2.

180

4. Logical disk cannot be bound

Condition Action

The message [25957] LD binding would not execute with selected parameters(RAID type, PD type, number, capacity. Please confirm the parameters. is displayed over and over

The following are possible causes. Eliminate the cause and perform setup again. There are too few physical disks for the specified [RAID Type/PD Type]. If [Spare Binding] is selected, one more physical disk is needed in the RAID configurations below. Specify [RAID Type/PD Type] again after confirming the number of physical disks that are implemented. RAID1 (Basic Pool): Configured on 2 physical disks RAID6(4+PQ) (Dynamic Pool): Configured on 6 physical disks RAID6(8+PQ) (Dynamic Pool): Configured on 10 physical disks The specified logical disk capacity or number of logical disks is too great. The capacity from multiplying the specified number of disks and capacity exceeds the maximum logical capacity that can be bound in the selected [RAID Type/PD Type]. If the logical disk capacity is important, reduce the number of logical disks, and if the number of logical disks is important, reduce the logical disk capacity. Note that the maximum logical disk capacity differs depending on the presence of [Selection host]. If [Selection host] is selected, a control volume (capacity: 0.2 GB) is bound automatically for each host. Do not specify more than the capacity that is displayed by default. The capacity that is displayed by default is for one logical disk. Specify up to 511 for the number of logical disks. * The number of logical disks allocated to one LD Set is at most 512. If [Selection host] is not selected, the maximum value for logical disk capacity that is displayed in the pull-down can be specified. The capacity that is displayed by the maximum value is the capacity for one logical disk. Although the number of disks that can be bound is at most 1024, note that if a LD Set is made separately by Access Control, the number of logical disks allocated to one LD Set is at most 512.

Unable to change the LD Set name in the LD binding screen

The following is a possible cause. Eliminate the cause and perform setup again. An identical LD Set has already been registered. Only new RAID can be added for the same host.

181

5. Error is displayed in setup completion screen (When setting method is Individual setting) Condition License unlocking failed Action The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, select the subject disk array from the main screen of Storage Manager client and reference [Properties] to check for unlocked licenses. Execute the initialization wizard again to unlock only licenses that have not been unlocked. Spare binding failed The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, before executing the initialization wizard again, check whether the subject physical disk has been set as a spare from Storage Manager client. The method of checking is as follows. - Select the subject disk array from the configuration display (tree display on left side) in the main screen of Storage Manager client. - Select a physical disk that is subordinate in the tree of the subject disk array. - From [Type] of the list of physical disks displayed in the information list display (right side) of the main screen, check whether there is a physical disk of the same PD type as that specified in [LD Binding] that is set as a spare. If it is already set as a spare, uncheck [Spare Binding] in the LD binding screen of the initialization wizard or unbind the spare of the subject physical disk from [LD Bind/Unbind] of [Configuration Setting] when you perform LD binding by using the initialization wizard again.

182

Condition Pool binding failed

Action The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, before executing the initialization wizard again, check the status of the pool from Storage Manager client. The method of checking is as follows. - Select the subject disk array from the configuration display (tree display on left side) in the main screen of Storage Manager client. - Select a pool that is subordinate in the tree of the subject disk array. - From the list of pools displayed in the information list display (right side) of the main screen, check whether there is a pool that was newly bound. If the pool is already bound, unbind the subject pool from [LD Bind/Unbind] of [Configuration Setting] when you perform LD binding by using the initialization wizard again.

LD binding failed

The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, before executing the initialization wizard again, check the status of the logical disk from Storage Manager client. The method of checking is as follows. - Select the subject disk array from the configuration display (tree display on left side) in the main screen of Storage Manager client. - Select a logical disk that is subordinate in the tree of the subject disk array. - Use the list of logical disks displayed in the information list display (right side) of the main screen to check whether there is a logical disk that was newly bound. If the logical disk is already bound, unbind the subject pool from [LD Bind/Unbind] of [Configuration Setting] (the logical disk is also unbound at the same time) when you perform LD binding by using the initialization wizard again.

183

Condition LD Set setting failed

Action The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, before executing the initialization wizard again, check whether the LD Set is bound from the main screen of Storage Manager client. If it is bound, since it may have timed out waiting for setup completion, it is not necessary to bind it again. The method of checking is as follows. - Select the subject disk array from the configuration display (tree display on left side) in the main screen of Storage Manager client. - Select a logical disk that is subordinate in the tree of the subject disk array. - Pull down the access control displayed in the upper part of the information list display (right side) in the main screen and check whether the subject LD Set is displayed and whether a bound logical disk is displayed in the information list display. When you retry LD binding by using the initialization wizard again, since it is possible that the subject pool and spare are already bound, perform unbinding of the subject pool and spare from [LD Bind/Unbind] of [Configuration Setting].

Time setting failed

The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, restart the management server. Restarting the management server makes the disk arrays time match the management servers time. Be careful if another disk array is being monitored, since all disk array monitoring stops due to restarting the management server.

Host information collection method setting failed

The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, select the [Special 2] tab from [Setting Disk Array] of [Configuration Setting] and turn off [Setting Host Recognize Volume mode]. Execute the initialization wizard again.

184

6. Batch setting with initialization file failed Condition An IP address setting error is displayed in the Initialization Complete screen Action The following are possible causes. Eliminate the cause and perform setup again. - Configuration is not the same as disk array used in file save. [Batch setting with initialization file] cannot be executed. Make the configuration the same or start the initialization wizard again and perform setup by selecting [Set by wizard form (standard)] from the Selection of setting method screen. - Configuration is the same as disk array used in file save. There is no entry in the network setting section of the initialization file. Check whether there is a description of the address that is used in the network setting section of the initialization file. * This can be used after editing it so that it does not duplicate network settings of a disk array already being used. After editing, perform [Batch setting with initialization file] from the initialization wizard again or perform [Set by wizard form (standard)]. There is an address description in the network setting section of the initialization file. Setup may have failed because it is a different network address from the management server. Check the network settings of the management server that is connected to the disk array by a LAN and modify the description in the network setting section of the initialization file. Initialize disk array network settings by referencing (3) Disk Array Network Setting Initialization in 7.6.1 Changing Network Settings for Monitoring Disk Arrays from Storage Manager. Perform [Batch setting with initialization file] from the initialization wizard again or perform [Set by wizard form (standard)]. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, select the [Network] tab from [Setting Disk Array] of [Configuration Setting] and check whether an IP address, subnet mask, and gateway address have been set for controller 0 (service processor number 00h) and controller 1 (service processor number 01h). If they are set, they are set normally on the disk array. Perform [Batch setting with initialization file] from the initialization wizard again or perform [Set by wizard form (standard)].

185

Condition A license unlocking error is displayed in the Initialization Complete screen

Action The following are possible causes. Eliminate the cause and perform setup again. Configuration is not the same as disk array used in file save. [Batch setting with initialization file] cannot be executed. Make the configuration the same or start the initialization wizard again and perform setup by selecting [Set by wizard form (standard)] from the Selection of setting method screen. Configuration is the same as disk array used in file save. There is no entry in the license unlocking section of the initialization file. Check whether there is a description of the license that is used in the license unlocking section of the initialization file. * This can be used after editing it so that it does not duplicate a license of a disk array already being used. After editing, perform [Batch setting with initialization file] from the initialization wizard again or perform [Set by wizard form (standard)]. There is an entry in the license unlocking section of the initialization file. The license key may be in error or a license that is already being used elsewhere may be described. Confirm that it is the license for the subject disk array and that the license key that is entered in the license sheet is described correctly. Perform [Batch setting with initialization file] from the initialization wizard again or perform [Set by wizard form (standard)]. Disk array faults or communication abnormalities between the disk array and a management server or client are occurring or a license is already unlocked Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, select the subject disk array from the main screen of Storage Manager client and reference [Properties] to check whether there are unlocked licenses. Execute the initialization wizard again and unlock only licenses that are not unlocked.

186

Condition A host connection port setting error is displayed in Initialization Complete.

Action The following are possible causes. Eliminate the cause and perform setup again. - If configuration differs from disk array used in saving file [Batch setting with initialization file] cannot be executed in a different configuration. Start the initialization wizard again and perform setup by selecting [Set by wizard form (standard)] from the Selection of setting method screen. Since the initialization file is a file used to execute batch setup of a disk array of the same configuration as the disk array used to save it, it cannot be used for a disk array of a different configuration. The only editing of the file is of network settings and license descriptions. - For same configuration as disk array used in saving file Disk array faults or communication abnormalities between the disk array and a management server or client may be occurring. Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, perform [Batch setting with initialization file] from the initialization wizard again or perform [Set by wizard form (standard)].

187

Condition Setting errors below are displayed in the Initialization Complete screen - Spare Binding - Pool Binding - LD Binding

Action The following is a possible cause. Eliminate the cause and perform setup again. If configuration differs from disk array used in saving file [Batch setting with initialization file] cannot be executed in a different configuration. Start the initialization wizard again and perform setup by selecting [Set by wizard form (standard)] from the Selection of setting method screen. Since the initialization file is a file used to execute batch setup of a disk array of the same configuration as the disk array used to save it, it cannot be used for a disk array of a different configuration. The only editing of the file is of network settings and license descriptions. For same configuration as disk array used in saving file Disk array faults or communication abnormalities between the disk array and a management server or client may be occurring or spare binding, pool binding, and LD binding may have already been done. Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, check whether binding has already been done.

The method of checking is as follows. - Select the subject disk array from the configuration display (tree display on left side) in the main screen of Storage Manager client. - Check each subordinate item in the tree of the subject disk array. <Checking spares> Select a physical disk and from [Type] of the list of physical disks displayed in the information list display (right side) of the main screen, check whether there is a physical disk of the same PD type as that specified in [LD binding] that is set as a spare. <Checking pools> Select a pool and use the list of pools displayed in the information list display (right side) of the main screen to check whether there is a pool that was newly bound. <Checking logical disks> Select a logical disk and use the list of logical disks displayed in the information list display (right side) of the main screen to check whether there is a logical disk that was newly bound. If it is already bound, unbind the subject spare or pool from [LD Bind/Unbind] of [Configuration Setting] (the logical disk is also unbound at the same time) in order to execute the initialization wizard again.

188

Condition An LD Set setting error is displayed in Initialization Complete.

Action The following are possible causes. Eliminate the cause and perform setup again. If configuration differs from disk array used in saving file [Batch setting with initialization file] cannot be executed if the configuration is not the same. Start the initialization wizard again and perform setup by selecting [Set by wizard form (standard)] from the Selection of setting method screen. Since the initialization file is a file used to execute batch setup of a disk array of the same configuration as the disk array used to save it, it cannot be used for a disk array of a different configuration. The only editing of the file is of network settings and license descriptions. For same configuration as disk array used in saving file Disk array faults or communication abnormalities between the disk array and a management server or client may be occurring or LD Set setting may already have been done. Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, check whether it has already been set up. If it is set up, it may have timed out waiting for setup completion, and it need not be set up again.

The method of checking is as follows. - Select the subject disk array from the configuration display (tree display on left side) in the main screen of Storage Manager client. - Select a logical disk that is subordinate in the tree of the subject disk array. - Pull down the access control displayed in the upper part of the information list display (right side) in the main screen and check whether the subject LD Set is displayed and whether a bound logical disk is displayed in the information list display. When you retry LD binding by using the initialization wizard again, since it is possible that the subject pool and spare are already bound, perform unbinding of the subject pool and spare from [LD Bind/Unbind] of [Configuration Setting].

189

Condition A time setting error is displayed in the Setup completion screen

Action The following is a possible cause. Disk array faults or communication abnormalities between the disk array and a management server or client may be occurring. Check whether there are abnormalities in the disk array, management server, or client. If there are no abnormalities, restart the management server. Restarting the management server makes the disk arrays time match the management servers time. Be careful if another disk array is being monitored, since all disk array monitoring stops due to restarting the management server.

190

7.6.1.Changing Network Settings for Monitoring Disk Arrays from Storage Manager
If a disk array cannot be monitored correctly from Storage Manager due to faults occurring in performing initialization or erroneous settings, network settings must be changed. Change disk array network settings using any of the following four procedures. Whether the disk array or management server must be changed is noted in the summary of each setting. Make changes after taking into account their effect on business. Yes (1) Changing Network Settings from Storage Manager 1 <Summary> - If changing only the IP address of the disk array to an address in the same network without changing the address of the management server, it can be done by changing only the disk array. - If changing the network itself, the management server also requires address changes from the OS after disk array setting change.

Currently, there is LAN monitoring by Storage Manager No

There is a logical disk that can be recognized by the production server No

Yes

(2) Changing Network Settings from Storage Manager 2 < Summary> - Only disk array addresses can be changed to fit with management server addresses (3) Changing again due to management server setting change < Summary> - Temporarily making the management server match the setting environment of the disk array, subsequent disk array changes in Storage Manager, and changing management server addresses again from the OS (4) Resetting due to network setting initialization < Summary> - After a disk array power cut, network settings can be initialized using DIP switches and the disk array can be reset later to match management server network addresses.

(Mistakenly) set information is known * Setting information can also be checked from log No

Yes

191

(1) Changing Network Setting from Storage Manager 1 If the disk array is monitored from Storage Manager, the disk array unit network settings can be changed from Storage Manager. Make changes using [Disk Array Setting] [Network] from the menu [File] [Configuration Settings/Reference] [Configuration Setting] [Individual Setting/Reference]. For details, refer to the Configuration Setting Tool Users Manual (GUI).

(2) Changing Network Setting from Storage Manager 2 If there is a host connected by FC to the disk array, changes can also be made using the network relief setting command (iSMnetconf) from the host. For details, refer to the Configuration Setting Tool Users Manual (GUI).

192

(3) Re-setting by Changing Management Server Setting Network setting can also be changed by executing the initialization wizard or Configuration Setting after temporarily making network settings of the current disk array unit coincide with management server network settings and changing them to make monitoring from Storage Manager possible. Confirmation of IP address that was set Provide the IP address, subnet mask, and gateway address noted in the Network parameters setting screen of the initialization wizard. (*1) Check the settings of the IP address, subnet mask, and gateway address in each controller of the disk array and of the IP address, subnet mask, and gateway address of the Network Interface Card (NIC) in the host on which the Storage Manager server is installed (hereafter, management server), as well as the physical connection configuration. (*2) (*3) Temporarily change the IP address, subnet mask, and gateway address of the management server NIC so that the IP address of the management server NIC is in the same subnet as the IP address of each controller. (*4) (*5) Referring to the installation guide, perform environment setting so that disk array monitoring is performed through a LAN connection from the Storage Manager server and restart the Storage Manager server. Confirm that the target disk array can be monitored from the Storage Manager client. Referring to the Configuration Setting Tool Users Manual (GUI), set the IP address, subnet mask, and gateway address of the disk array via the network setting of the Configuration Setting. (*6) (*7) (*8) After restoring the temporary IP address, subnet mask, and gateway address of the management server NIC, restart the Storage Manager server. Confirm that disk array monitoring is being performed by the Storage Manager client.

Connection configuration check

Change host IP address

Start of disk array unit monitoring

Disk array unit network setup

Host IP address restoration Confirmation of disk array connection state

If disk array unit initialization is not complete, host connection port setup, license unlocking, LD binding, and other initializations must be performed separately. *1: If an IP address is not provided, refer to SVP Number (controller number), IP Address, Subnet mask, and Gateway, which are output in message number iSM14483 in the message display of the Storage Manager client (Web GUI). Once you have restarted (reconnected) the Storage Manager client (Web GUI), since messages are output only from that time, refer to SVP Number (00h: LAN connector for controller 0, 01h: LAN connector for controller 1), IP Address, Subnet mask, and Gateway, which are output in message number iSM14483 in the log file of the Storage Manager server. For the Storage Manager server log file output destination, refer to Log Output in the Users Manual of the OS being used.

193

Fry Jan 12 14:32:46 2007 0000004380 Info iSMconfig iSM14483:Set IP Address(Product ID=xxxxx ,Serial Number=xxxxxxxxxxxxxxxx) : SVP number=xxh, IP Address=x.x.x.x, Subnetmask=x.x.x.x, Gateway=x.x.x.x, status=failed

Message Display Area

Figure 7.1

Storage Manager Client (Web GUI) Message

*2: If disk array unit network settings and server connections are correct, contact your sales agent. *3: If there are multiple Network Interface Cards (NIC) in the management server, refer to the manual for each server and OS for the correspondence between IP addresses and Network Interface Card (NIC). *4: Since changes to disk array network settings cannot be made until monitoring can be performed from the Storage Manager server, it is necessary to temporarily change the management server IP address, subnet mask, and gateway address to configure the disk array so that it can be monitored. *5: Change the IP address to that of the Network Interface Card (NIC) that is physically connected to the disk array. *6: Since the IP addresses of controller 0 and controller 1 cannot be made the same, another IP address must be set temporarily when switching IP addresses. *7: To change multiple IP addresses, view device properties in the main screen of the Storage Manager client and make changes from the side that is not the control path (1). *8: Since the Storage Manager server environment settings are not changed if the disk array IP address is changed to an IP address that cannot be monitored after the change, the Storage Manager server environment settings must be changed manually after making the change.

194

(4) Resetting by Network Setting Initialization It is possible to initialize the disk array unit network settings in order to perform operations described in Chapter 4. Initialization of Disk Array from the beginning. However, only perform this initialization if network setting by the initialization wizard failed. 1. Change DIP switches of the disk array Change DIP switches by referring to 6.7 Changing DIP Switches. Changing the second switch (Bit2) of the DIP switches initializes network settings at startup.

Figure 7.2

DIP Switches

If the disk array detects a mismatch between DIP switch memory at the time of unit startup and when the network was set, it initializes network settings. Accordingly, it is not necessary to restore changed values (DIP switches).

195

2. Confirmation of Storage Manager server environment setting If disk array network addresses initialized as mentioned above are registered in the Storage Manager server Setting Utility program, perform deletion and restart the management server on which Storage Manager server is installed. If another disk array is already being monitored, monitoring stops during this interval. For details about environment setting, refer to the attached Storage Manager Installation Guide. - When Storage Manager server is a Windows environment Select the relevant disk array and click the [Delete] button.

Figure 7.3

Storage Manager Server Setting Utility Program (Windows)

196

- When Storage Manager server is a Linux environment Delete the portion of the entry shown below for the relevant disk array. [agent] : : Diskarray1 = ( ip = ( 192.168.0.1 ,192.168.0.2 ) ) : :

Delete

3. Execution of initialization wizard from Storage Manager Execute the initialization wizard again. For disk array DIP switches, controller 0 and controller 1settings need not be the same. For initialization, however, change both controller 0 and controller 1. Make changes to network settings from Configuration Setting for a disk array for which initialization has already finished and monitoring is being done from Storage Manager. If network settings have already been initialized by mistake due to DIP switches, perform the following minimum necessary setup using the initialization wizard. 1. Initialization wizard startup Click [Next]. 2. Selection of disk array Select the disk array unit for which to perform setup and click [Next] 3. Confirmation of disk array connection state Click [Next]. 4. Selection of setting method Select [Set by wizard form (standard)] and click [Next]. 5. Selection method of host information collection Uncheck [Automatic collection] and click [Next]. 6. Network parameters setting Input valid values, click the [Next] button, and click [Execute] after confirming that there are no errors in the confirmation screen. 7. Setting of host connection port When the screen is displayed, click [Cancel] to exit it.

197

Appendix.A.Notes on Using MSCS (Microsoft Cluster Service) in a Windows Server 2003 Environment
When using MSCS in a Windows Server 2003 environment, according to MSCS specifications, Target ID and LUN (number) of the disk array that each server recognizes must be set to the same values. A cluster cannot be set up if they are set to different values. For details, refer to the URL below. <KB331801> Cluster setup may not work when you add nodes. http://support.microsoft.com/kb/331801/en-us

1. Target ID How to set the Target IDs of controllers of a disk array unit that are recognized by servers to the same value is described below for each connection configuration.

< Connecting disk array unit to server (HBA) directly >

Set the Loop Switch IDs of disk array unit controllers to the same value. The Switch ID that is set becomes the Target ID recognized by the server. Also set the Loop Switch IDs of all connected controller ports to the same value in the same way when the disk array unit is connected to the server by multiple paths. Server A Server B Server A
SPS
HBA1 HBA0

Server B

Cluster
HBA0 HBA1 HBA0

Cluster
HBA1 HBA0

SPS
HBA1

Set the same value.

10h
HF0

10h
HF0

Set the same value.

10h
HF0

10h
HF1

10h
HF0

10h
HF1

Basic port
Controller 0

Basic port
Controller 1

Basic port
Controller 0

Basic port
Controller 1

Optima disk array

Optima disk array

Single-path configuration

Dual-path configuration

SPS: MultiPath Figure A.1 Direct Connection < Connecting to Loop Topology FC Switch >

198

For controllers of the same disk array unit, set the Loop Switch ID to the same value. The Switch ID that is set becomes the Target ID recognized by the server. When connecting multiple disk array units to a FC Switch, be sure to set the Loop Switch ID for each disk array unit to a different value. If set to the same value, the units will not start normally. Note. For Loop Topology FC Switches, binding with one FC Switch is not possible since different Loop Switch IDs must be set within a FC Switch.
Server A SPS
HBA0 HBA1

Server B

Cluster
HBA0

SPS
HBA1
Port2 Port11

Port1

Port2

Port1

Set different values.

FC Switch0
Port12 Port11

FC Switch1
Port12

Set the same value.

11h 11h

Set the same value.

10h 10h

HF0

HF0

HF0

HF0

Basic port
Controller 0

Basic port
Controller 1

Basic port
Controller 0

Basic port
Controller 1

Optima disk array 0

Optima disk array 1

Figure A.2

Connecting to Loop Topology FC Switch

199

< Connecting to Fabric Switch (Such as NF9320-xSxx/SS11x, NF9330-xSxx, and N8406-019/020) > Connect the connections from a server and a disk array unit to the same port number of each switch by Fabric Switch or by zoning group, as shown in the figure below. Target IDs starting from 0 are assigned to Targets recognized by the server in order from the lower numbered N_Port ID (lower numbered Port of Switch). Server A
SPS
HBA0
Port2

Server B Cluster
SPS
HBA1
Port3

HBA1
Port3

HBA0

Port2

Fabric Switch0
Port0 Port1

Fabric Switch1
Port0

Port1

HF0 Basic port

Controller 0

HF0 Basic port

Controller 1

HF0 Basic port

Controller 0

HF0 Basic port

Controller 1

Optima disk array 0

Optima disk array 1

Figure A.3 Switch No. Port No. Switch0 - Port0 Switch0 - Port1 Switch0 - Port2 Switch0 - Port3 Switch1 - Port0 Switch1 - Port1 Switch1 - Port2 Switch1 - Port3

Connecting to Fabric Switch Switch ID 10h 12h 11h 13h Target ID 0 1 0 1 Recognizes Targets connected to Fabric Switch as Target ID 0, 1, in order detected starting from lower numbered Port of Switch.

Connection Device Storage 0 - Cont0 Storage 1 - Cont0 Server A - HBA0 Server B - HBA0 Storage 0 - Cont1 Storage 1 - Cont1 Server A - HBA1 Server B - HBA1

Table A.1

Connection of Switch

200

Note.

If you connect wrong disk array to Ports of Switch0 and Switch1, you can not perform cluster setup since Target IDs differ between controller 0 and controller 1. Target IDs at CONT0 and CONT1 differ.

Swtich0 - Port0 : Storage 0 - Cont0 Target ID 0 Swtich0 - Port1 : Storage 1 - Cont0 Target ID 1 Swtich1 - Port0 : Storage 1 - Cont1 Target ID 0 Swtich1 - Port1 : Storage 0 - Cont1 Target ID 1

2. LUN (number) How to set disk array unit LUN (numbers) recognized by the server to the same value is described below. The disk array unit offers the Access Control function that maps logical disk masking and LDN starting from LUN 0. If this Access Control has not been installed, the logical disks (LDN) bound in the disk array unit will be the logical disks (LUN) that can be accessed from the server. Installing Access Control may change the accessible logical disks (LUN) from the server. For example, if LDN00 to 03 are in the disk array unit, Access Control makes it possible to set them so that LDN00=LUN00, LDN01=LUN01, LDN02=LUN02 are recognized by Server A and also to set them so that LDN00=LUN01, LDN01=LUN02, LDN03=LUN00 are recognized by Server B. In this case, the LUN being recognized by Server A and the LUN being recognized by Server B are different LDN. If you do not install Access Control Special setting is unnecessary. If you install Access Control When setting up Access Control, be sure to set it so that an LDN in the disk array unit is recognized as the same LUN (number) by each server.

201

Appendix.B.Notes on Connecting FC Switches in a Fault Tolerant Server Environment

Please make the port number of the switch same in each ZONE and Switch.

Fault Tolerant Server

FC HBA FC HBA

Fault Tolerant Server

FC HBA FC HBA

FC Switch Zone 0 Port 0 - 7 Zone 1 Port 8 - 15

FC Switch 1

FC Switch 2

Cont0-0 (ID=10h) Cont1-0 (ID=10h) Cont0-0 (ID=11h) Cont1-0 (ID=11h)

Cont0-0 (ID=10h) Cont1-0 (ID=10h) Cont0-0 (ID=11h)

Cont1-0 (ID=11h)

Storage 1

Storage 2

Storage 1

Storage 2

Zone 0
Switch Port No. Zone 1 Port 0 Port 1 Port 2 Zone 2 Port 8 Port 9 Port 10 Connection Device Fault tolerant server Storage 1 Cont0-0 Storage 2 Cont0-0 Fault tolerant server Storage 1 Cont1-0 Storage 2 Cont1-0 10h 11h 10h 11h Loop ID Switch No. Port No. Switch 1 - Port 0 Switch 1 - Port 1 Switch 1 - Port 2 Switch 2 - Port 0 Switch 2 - Port 1 Switch 2 - Port 2 Connection Device Fault tolerant server Storage 1 Cont0-0 Storage 2 Cont0-0 Fault tolerant server Storage 1 Cont1-0 Storage 2 Cont1-0 10h 11h 10h 11h Loop ID

Zone 1

- Controllers have a same Loop ID number - Different Loop ID numbers for each unit

202

Appendix.C.Initialization of the Disk Array Using Initialization File

1. Overview An initialization file is available to create disk arrays with the same configuration. Batch initialization of disk arrays can be performed by using an initialization file. This file is created by saving the settings on the Initialization Complete screen of the initialization wizard.

Start screen

Selection of disk array

Confirmation of disk array connection state Selection of setting method Selection method of host information collection Network parameters setting Setting of host connection port License Unlock Selection of LD binding

LD Binding Finish

203

Pay attention to the following when using an initialization file.

-

Use it for disk arrays of the same configuration. To perform setup in a different configuration, select [Set by wizard form]. Use it after editing IP addresses and license keys. Do not edit items other than these. To modify a disk array for which Batch setting with initialization file was performed, start the initialization wizard again and make changes after selecting [Set by wizard form] or make changes individually from [Configuration Setting] after the initialization wizard finishes. Since path information in a LD set is information about the server used when the initialization file was saved, if the server being used is different, check and make changes to the information in the [Configuration Setting] Access Control after initialization ends. To use an initialization file, the disk array must satisfy all of the following conditions. - There are no pools or spares. - The platform of the host connection port is WN or LX. - Host connection port configuration change is not locked. If conditions are not satisfied, file reading cannot be selected.

204

2. Editing initialization file

To prevent the same IP address and license from being used for other disk arrays, they are described as xxx in the saved file. Initialization file becomes available by editing the IP address and license. Be careful not to edit other items. The format and sample settings of the initialization file are shown below. The format to perform batch settings from a user-defined file is explained. a. The file is an ASCII character format text file (*.txt). b. From a # (sharp) to the end of a line is treated as a comment. c. A section must be enclosed in [ ] and start from the beginning of a line. d. A section description action is in effect until the next section description appears. e. A sentence within a section in the syntax for settings by section is complete in one line. f. The syntax for settings by section is the format below. - Key=Value The setting for Key is described by Value. - KeyValue.Subkey=Value This specifies a subkey of the value set above it and describes its setting in Value. Key and Subkey names vary by section. g. If a section name begins with *, it is not used in setting. h. Since uppercase and lowercase characters are distinguished, take care in description.

205

<Format of initialization file> # Comment line Initialization wizard ................... (1) [SVPConf] ................................ (2) 00h.GateWay=x.x.x.x 00h.IP=x.x.x.x 00h.Mask=x.x.x.x SVPNO=00h [License] .................................. (3) License=XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX [*DiskArray] .............................. (4) : [FCPort] ........................................ (5) : [LD]............... ................................ (6) : [LDSET]......................................... (7) : [*LDSET_ASS]............................... (8) : [Pool] ..............................................(9) : [Spare] ............................................(10)
:

(1) Key information This has the description Initialization wizard as key information to show that the parameters to follow are a setup file. (2) Section (Network) This describes the network (IP address, etc.) to set in the disk array. <Explanation of syntax> Section: Key: Subkeys: Syntax: [SVPConf] SVPNO IP, GateWay, Mask SVPNO=xx xx.IP=aaa.bbb.ccc.ddd xx.GateWay= aaa.bbb.ccc.ddd xx.Mask= aaa.bbb.ccc.ddd

206

SVPNO: Describes the SVP (service processor) number in 2 hexadecimal digits. 00h: LAN connector number on controller 0 side 01h: LAN connector number on controller 1 side IP: Represents an IP address in . delimited decimal notation.

GateWay: Describes a gateway in the same format as an IP address. Mask: Example: Describes a subnet mask in the same format as an IP address.

SVPNO=00h 00h.IP=192.168.1.1 00h.GateWay=255.255.255.0 00h.Mask=0.0.0.0 SVPNO=01h 00h.IP=192.168.1.2 00h.GateWay=255.255.255.0 00h.Mask=0.0.0.0

(3) Section (License) This describes a license key used for the disk array. <Explanation of syntax> Section: Key: Syntax: [License] License License=xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx When unlocking multiple license keys, describe them on multiple lines. License=123456-123456-123456-123456-123456 License=ABCDEF-ABCDEF-ABCDEF-ABCDEF-ABCDEF (4) Section (Disk array) This is key information for displaying the disk array type being set. The section name begins with [*DiskArray] and is not used in initialization. (5) Section (Host connection port) This describes the host connection port settings. The section name is displayed as [FCPort]. Example:

207

(6) Section (Logical disk) This describes the binding of logical disks. The section name is displayed as [LD].

(7) Section (LD Set) This describes the binding of an LD Set. The section name is displayed as [LDSET].

(8) Section (Assignment of logical disks to LD Set) This describes the logical disks assigned to an LD Set. This section is ignored at re-initialization because it exists as a result of execution. The section name is displayed as [*LDSET_ASS].

(9) Section (Pool) This describes the binding of a pool. The section name is displayed as [Pool].

(10) Section (Spare) This describes the binding of the spare disk.

208

3. Settings

Select [File] [Initialization Wizard] from the menu bar starts the initialization wizard. After initialization wizard startup, follow the screens that are displayed to make settings. (a) Start screen The start screen of the initialization wizard is displayed. Operation procedure is same with the first setting. Confirm the displayed message and click [Next]. For details, refer to 4.2.1 Initialization Wizard 2. Setting (a) Start screen. (b) Selection of disk array Selection of disk array specifies the disk array to be initialized.

Figure C.1

Selection of disk array Screen

The disk arrays found by the searching are displayed. Display of the initialization differs in the point where last initialization wizard was cancelled. Refer to Table C.1 for details. Select the target display from the list and click [Next].

209

Display Contents not execute

suspended

finished

Disk Array Status Status immediately following disk array installation. Since network setting was not performed in the initialization wizard, it is not subject to Storage Manager monitoring. Initialization by the initialization wizard or maintenance personnel is needed. Processing through Network parameters setting or Setting of host connection port has been performed by the initialization wizard, but the BaseProduct license has not been unlocked. The disk array is subject to Storage Manager monitoring. (*) Status in which unlocking has been done up to and including the BaseProduct license. The disk array is subject to Storage Manager monitoring. (*) Table C.1 Initialization of Disk Array

(*) When a disk array is monitored by the Storage Manager, the disk array will be displayed in the main screen of the Storage Manager client. If the initialization status of a disk array is [suspended] or [finished], the message box shown below is displayed to stop disk array monitoring and put the subject disk array in a Configuration Setting state.

Figure C.2

Monitoring Stop Confirmation Message Box

(c) Confirmation of disk array connection state Next, confirm the disk array connections. Operation procedure will be the same with the first setting. For details, refer to 4.2.1 Initialization Wizard 2. Setting (c) Confirmation of disk array connection state.

210

(d) Selection of setting method Select the initialization method.

Figure C.3

Selection of setting method Screen

Select [Batch setting with initialization file]. After reading the file, click [Next].

211

(e) Confirmation of setting parameters Setting parameters are displayed.

Figure C.4

Confirmation of setting parameters Screen (When Using Initialization File)

Confirm the setting parameters. After confirmation, click [Next]. Perform settings of the disk array.

<IP address Setting> Disk array IP address settings are displayed. - Controller The target controller is displayed. - IP Address The IP address to set is displayed. - Subnet Mask The subnet mask to set is displayed. - Gateway Address The gateway address to set is displayed.

212

<Example> --- IP address setting --Controller0 IP Address : 192.168.2.176 Subnet Mask : 255.255.255.0 Gateway Address : 0.0.0.0

<Host connecting port> The settings for the host connection port are displayed. - Port Number The target port number is displayed. - Platform The platform to set is displayed. - Data rate The data rate to set is displayed. - Host connection type The host connection type to set is displayed. - Switch ID The Loop Switch ID to set is displayed. <Example> --- Host connecting port --Port Number : 00h-00h Platform : Windows(WN) Data rate : 4Gbps Host connection type : Direct Connection(FC-AL) Switch ID :10h

<License Unlock> The specifications for setting license unlocking are displayed. - License key The license key to be unlocked is displayed. <Example> --- License Unlock --Product :BaseProduct License key :ABCDEF-GHIJKL-MNOPQR-STUVWX-YZABCD AccessControl :ON

213

<Spare Binding> Spare binding specifications are displayed. - Physical Disk A list of the physical disks set for spare are displayed in xxh-xxh format (hexadecimal). <Example> --- Spare Binding --Physical Disk : 00h-0dh

<Pool Binding> Pool binding specifications are displayed. This is displayed only if [LD binding] was selected in Selection of LD binding. - Pool Number The pool number to bind is displayed. - RAID Type/PD Type The RAID type and PD type of the pool to bind are displayed. - Physical Disk A list of the physical disks that make up the pool to bind is displayed in xxh-xxh format (hexadecimal). <Example> --- Pool Binding --Pool Number : 0000h RAID Type/PD Type: RAID1(Basic)/FC Physical Disk : 00h-01h 00h-0ch

<LD Binding> The specifications for LD binding are displayed. - Start Number The starting logical disk number (hexadecimal) of logical disks to bind is displayed. - Capacity The capacity of the logical disk to bind is displayed. - Number of LDs Number of logical disks to bind is displayed.

214

- OS type The OS type of the logical disk to bind is displayed. LX WG WN - Name (prefix) The name (prefix) of the logical disk to bind is displayed. - Purpose The purpose of the logical disk to bind is displayed. Control Volume None - Binding type Displayed when a quick format is used. <Example> --- LD Binding --Start Number: 0000h Capacity: 0.2GB Number of LDs: 2 OS type: WN Name(prefix): 2000003013841487 Purpose: Control Volume Binding type:Quick --- LD Binding --Start Number: 0002h Capacity: 132.0GB Number of LDs: 1 OS type: WN Name(prefix): 2000003013841487 Binding type:Quick Logical disk for control volume. Logical disk for general use. Operation logical disk by Linux system. Operation logical diks by Windows GPT system. Operation logical disk by Windows system.

215

<Access Control Setting> Specifications set for Access Control are displayed. - Platform The platform of the LD Set is displayed. - LD Set Name The name of the LD Set is displayed. - Host Name The production server name to which bound logical disks are assigned is displayed. - Path Info WWPN (World Wide Port Name) information set for the LD Set is displayed. <Example> --- Access Control Setting (Host1) --Platform : WN LD Set Name : EXP12DV1 Host Name : EXP12DV1 Path Info : 1000-0000-aaaa-bbbb 1000-0000-cccc-dddd --- Access Control Setting (Host2) --Platform : WN LD Set Name : EXP12DV2 Host Name : EXP12DV2 Path Info : 1000-0000-eeee-ffff 1000-0000-gggg-hhhh

216

(f) Initialization Complete The setup completion screen of the initialization wizard is displayed. Displayed screen will differ when setup failed. For details, refer to 4.2.1 Initialization Wizard 2. Setting (l) Initialization Complete or (m) If setup fails. If the setting failed when selecting [Batch setting with initialization file] at 4 Selection of setting method, any of the following will be displayed. IP address setting Setting of host connection port License Unlock Spare Binding Pool Binding LD Binding LD Set Setting Time Setting

* Display above will also be used at quick format error. After confirming the displayed error content, click [Finish] to terminate the initialization wizard. Itll return to the Storage Manager client (Web GUI) main window screen. For details, refer to Table C.2 Failure Setting of Initialization File.

217

Failure Setting IP address setting

Disk Array Setting State IP address setting failed. The network address may have been set in disk array or Storage Manager server environment setting. Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

Host connection port setup

Host connection port setup failed. It is possible that network setting completed and the host connection port setting has been made in the disk array. Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

License Unlock

License unlocking failed. Network setting and host connection port setup have been performed in the disk array. Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

Spare Binding

Spare binding failed. The following settings have been made in the disk array. - Network - Host connection port setup - License Unlock Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

Pool Binding

Pool binding failed. The following settings have been made in the disk array. - Network - Host connection port setup - License Unlock - Spare Binding Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

Table C.2

Failure Setting of Initialization File (1/2)

218

Failure Setting LD Binding

Disk Array Setting State LD binding failed. The following settings have been made in the disk array. - Network - Host connection port setup - License Unlock - Spare Binding - Pool Binding Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

LD Set Setting

Access control setting or quick format failed. The following settings have been made in the disk array. - Network - Host connection port setup - License Unlock - Spare Binding - Pool Binding - LD Binding Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

Time Setting

Time setting failed. The following settings have been made in the disk array. - Network - Host connection port setup - License Unlock - Spare Binding - Pool Binding - LD Binding - LD Set Settings Refer to 7.6 Initialization Wizard and Easy Configuration Errors.

Table C.2

Failure Setting of Initialization File (1/2)

219

Appendix.D.Technical Specifications
Table D.1 lists the technical specifications for the disk array units. Optima1500 (Single Controller Model)

Optima1500 Host interface Controllers per unit Host ports per unit Cache memory capacity per unit Cache memory battery backup time Disk enclosures per unit Number of disk drives Disk drives

Fibre channel (FC-AL, Fabric), max. transmission speed 400 MB/s 2 4 With extended Host Port: 8 12 4 GB 24 hours With extended BBU added: 72 hours Up to 11 Up to 144 SAS: 73GB (15,000 rpm), 147 GB (15,000 rpm), 300 GB (15,000 rpm) , 450 GB (15,000 rpm) , 600 GB (15,000 rpm) SATA: 500 GB (7,200 rpm), 750 GB (7,200 rpm), 1TB (7,200 rpm) , 2TB (7,200 rpm) SAS: Max. transmission speed 300 MB/s SATA: Max. transmission speed 300 MB/s SAS: RAID-1, 3, 3DP, 5, 10, 50, 6,TM SATA: RAID-5/50, RAID-6, TM Table D-1 Disk Array Units 1 2

2 GB

Disk drive interface RAID types

220

TableD.2 lists the RAID configuration specifications. RAID Type RAID-1 RAID-3 RAID-3DP RAID Configuration Units 1D+1D 4D+P 8D+P 4D+PQ 8D+PQ 2D+P RAID-5 4D+P 8D+P (1D+1D)2 (1D+1D)3 (1D+1D)4 RAID-10 (1D+1D)5 (1D+1D)6 (1D+1D)7 (1D+1D)8 RAID-50 (4D+P)2 (4D+P)4 4D+PQ RAID-6 8D+PQ 1D+1D+1D Table D-2 Number of Disk Drives 2 5 9 6 10 3 to 4 5 to 8 9 to 12 4 6 8 10 12 14 16 10 20 6 to 144 10 to 144 3 RAID Configuration Capacity Utilization 50% 80% 88% 66% 80% 66% 80% 88% 50% 50% 50% 50% 50% 50% 50% 80% 80% 66% 80% 33%

RAID-TM

Note. A RAID consists of a combination of disk drives of the same capacity and same rotation speed. D, P, and Q have the meanings D: Data disk, P, Q: Parity disk.

221

Table D.3 lists the optional components of this disk array unit. Part Name Remarks Option Controller Extended Host Port (4Ports 8Ports) UPS Interface Extended Host Port (4 ports 12 ports) Extended battery backup unit SAS/SATA disk enclosure SAS disk drive (15krpm/73GB) SAS disk drive (15krpm/147GB) SAS disk drive (15krpm/300GB) SAS disk drive (15krpm/450GB) SAS disk drive (15krpm/600GB) SATA disk drive (7200rpm/500GB) SATA disk drive (7200rpm/750GB) SATA disk drive (7200rpm/1TB) SATA disk drive (7200rpm/2TB) Extended controller For 2 controllers For 2 controllers Extends battery backup time to 72 hrs. 12 SAS/SATA disk drives can be implemented 15k rpm/73 GB SAS disk drive for disk array extension 15k rpm/147 GB SAS disk drive for disk array extension 15k rpm/300 GB SAS disk drive for disk array extension 15k rpm/450 GB SAS disk drive for disk array extension 15k rpm/600 GB SAS disk drive for disk array extension 7200 rpm/500 GB SATA disk drive for disk array extension 7200 rpm/750 GB SATA disk drive for disk array extension 7200 rpm/1TB SATA disk drive for disk array extension 7200 rpm/2TB SATA disk drive for disk array extension Table D.3 Optional Components

(*1) can be used only by the Storage Manager Ver.6.1 or later / Storage basic control software Ver.061A or later. (*2) can be used only by the Storage Manager Ver.6.1 or later / Storage basic control software Ver.061B or later.

222

Appendix.E.LED Checks
In the case which state monitoring is not done by Storage Manager, states can be checked at LEDs on devices. When an abnormality is detected, please check the LED that differs from the underlined status below. Identification of the location of the abnormality and arrangement for the recovery can be done more rapidly. Disk Array Unit < Disk array unit (front face) > 1 2 3 POWER LED (green) SERVICE LED (orange) ACTIVE/FAULT (orange / green) ON / Blinking / OFF ON / Blinking / ON for 5 sec. and OFF for 7 sec. / ON for 0.5 sec. and OFF for 0.5 sec. / OFF Alternate blinking orange and green / Only orange ON Location ( Alternate blinking orange and green / Only orange ON Location ( Alternate blinking orange and green / Only orange ON Location (

) ) )

< Disk array unit (rear face) > PS0 1 2 3 1 2 3 4 5 6 7 8 9 4 5 6 7 8 9 POWER GOOD LED (green) POWER FAULT LED (orange) FAN FAULT LED (orange) POWER GOOD LED (green) POWER FAULT LED (orange) FAN FAULT LED (orange) HPE GOOD LED (orange) Battery FAULT (orange) BACKUP LED (orange) FAULT LED (orange) READY LED (green) SAS connector FAUTL LED (FLT) (orange) HPE GOOD LED (orange) Battery FAULT (orange) BACKUP LED (orange) FAULT LED (orange) READY LED (green) SAS connector FAUTL LED (FLT) (orange) ON / OFF ON / OFF ON / OFF ON / OFF ON / OFF ON / OFF ON / OFF ON / Blinking / OFF ON / Blinking / OFF ON / Blinking / Blinking slowly / OFF ON / Blinking / OFF ON / OFF Location ( ) ON / OFF ON / Blinking / OFF ON / Blinking / OFF ON / Blinking / Blinking slowly / OFF ON / Blinking / OFF ON / OFF Location ( )

PS1

CONT0

CONT1

223

< Extended BBU (rear face) > Extended BBU0 Extended BBU1 1 2 3 1 2 3 CHARGE LED (green) BBU FAULT LED (orange) AC switch (orange) CHARGE LED (green) BBU FAULT LED (orange) AC switch (orange) ON / Blinking / OFF ON / Blinking / OFF ON (-) / OFF (O) ON / Blinking / OFF ON / Blinking / OFF ON (-) / OFF (O)

Disk enclosure < Disk enclosure (front face) > 1 2 3 POWER LED (green) SERVICE LED (orange) ACTIVE/FAULT (orange / green) ON / Blinking / OFF ON / Blinking / ON for 5 sec. and OFF for 7 sec. / OFF Alternate blinking orange and green / Only orange ON Alternate blinking orange and green / Only orange ON Alternate blinking orange and green / Only orange ON Location ( Location ( Location ( ) ) )

< Disk enclosure (rear face) > PS0 1 2 3 1 2 3 4 5 6 4 5 6 POWER GOOD LED (green) POWER FAULT LED (orange) FAN FAULT LED (orange) POWER GOOD LED (green) POWER FAULT LED (orange) FAN FAULT LED (orange) SAS connector FAUTL LED (FLT) (orange) FAULT LED (orange) READY LED (green) SAS connector FAUTL LED (FLT) (orange) FAULT LED (orange) READY LED (green) ON / OFF ON / OFF ON / OFF ON / OFF ON / OFF ON / OFF ON / OFF Location ( ON / Blinking / OFF ON / Blinking / OFF ON / OFF Location ( ON / Blinking / OFF ON / Blinking / OFF

PS1

ADP0

ADP1

224

Disk array unit front view (viewed when front mask is removed)
2. SERVICE 1. POWER

Location 00 04 08

01 05 09

02 06 0A

03 07 0B

3. ACTIVE/FAULT

1. 2.

POWER LED (green) SERVICE LED (orange) POWER LED ON ON SERVICE LED OFF ON

Right drive disk Left drive disk

STATUS Operating

Power-on

ON ON

Blinking ON for 5 sec. and OFF for 7 sec. ON for 0.5 sec. and OFF for 0.5 sec. OFF OFF

ON Power-off Blinking OFF

3.

Description Normal operation Requesting maintenance or processing a maintenance task (such as during recovery) Power-on sequence in progress Requesting maintenance (battery backup failure; write data may have been lost) Storage Manager client instructs by blinking of the Service LED. Shutdown sequence complete Auto shutdown sequence complete Powered off

ACTIVE/FAULT LED (green/orange) for each disk drive ACTIVE/FAULT LED Green : ON Green : Blinking Green/orange : Alternate blinking Orange only : Blinking Orange : ON Status Normal status (ready) Normal status (accessing) Rebuilding HDD low power state Abnormal status

225

Disk enclosure front view (viewed when front mask is removed)

2. SERVICE 1. POWER

Location x0 x4 x8

x1 x5 x9

x2 x6 xA

x3 x7 xB

1. POWER LED (green) 2. SERVICE LED (orange) STATUS Operating POWER LED ON ON

3. ACTIVE/FAULT Right drive disk Left drive disk

SERVICE LED OFF ON

Power-off

OFF

OFF

Description Normal operation Requesting maintenance or processing a maintenance task (such as during recovery) Powered off

3. ACTIVE/FAULT LED (green/orange) for each disk drive ACTIVE/FAULT LED Green : ON Green : Blinking Green/orange : Alternate blinking Orange only : Blinking Orange : ON Status Normal status (ready) Normal status (accessing) Rebuilding HDD low power state Abnormal status

226

Disk array unit rear view

1. POWER GOOD 2. POWER FAULT 3. FAN FAULT

Location PS1 CONT1

4. HPE FAULT 5. Battery FAULT 10. HP Connector

PS0 CONT0

6. BACKUP

7. FAULT

8. READY

9.SAS Connector

11. LAN Connector

1 2 3 4 5

6
7. 8.

LED ON / Blinking POWER GOOD LED (green) Normal POWER FAULT LED (orange) Power supply fault (excluding the fan) FAN FAULT LED (orange) Fan fault HPE FAULT LED (orange) HPE fault Battery FAULT (orange) Battery backup unit status ON: Fault Blinking: To be replaced due to its life BACKUP LED (orange) Blinking: Battery backup state FAULT LED (orange) READY LED (green)

OFF AC power is not being supplied Normal Normal Normal Normal

Normal

READY LED OFF ON ON Blinking Rapidly ON Blinking Blinking

FAULT LED OFF ON OFF OFF Blinking slowly ON OFF

State Powered off Occurrence of fault Power-on sequence in progress Shutdown sequence is running Auto shutdown sequence is running Waiting for disk enclosure power-on Disk interface is disable Normal operation

227

9.

SAS connector ON: Link-up, OFF: Link-down ON: Error detection, OFF: Normal

LINK LED (LNK) (green) FAULT LED (FLT) (orange) < Location and port numbers > DP1 DP0

10. HP connector

LINK LED (L) (green) ACTIVE LED (A) (green) Concurrent blinking both LINK and ACTIVE LEDs

ON: Link-up, OFF: Link-down ON, blinking: I/O access Once in 2 seconds: Offline Twice in 2 seconds: Waiting setup

< Location and port numbers > HP5 HP4 HP3 HP2 HP1 HP0

228

Disk enclosure rear view

Adapter REV. Axx or Bxx (where xx is version number) 1. POWER GOOD 2. POWER FAULT 3. FAN FAULT

Location PS1 PS0 ADP1 ADP0

4. SAS connector 5. FAULT 6. READY 1. POWER GOOD 2. POWER FAULT 3. FAN FAULT

Adapter REV. Cxx (where xx is version number)

Location PS1 PS0 ADP1 ADP0

5. FAULT

4. SAS connector

6. READY

NOTE: Adapter REV is written in UNIT LABEL. ON / Blinking POWER GOOD LED (green) Normal POWER FAULT LED (orange) Power supply fault (excluding the fan) FAN FAULT LED (orange) Fan fault OFF AC power is not being supplied Normal Normal

1 2 3

4. SAS connector LINK LED (LNK) (green) FAULT LED (FLT) (orange) < Location and port numbers > DP1 DP0 5. FAULT LED (orange) 6. READY LED (green) READY LED OFF ON Blinking ON ON FAULT LED OFF OFF OFF ON Blinking Status No connection or powered off Normal operation Starting Fault inside Adapter Communication failure between the ADP was detected. ON: Link-up, OFF: Link-down ON: Error detection, OFF: Normal

229

Extended BBU rear view

Location PS1
2. BBU FAULT 1. CHARGE 3. AC Switch

PS0

1 2

CHARGE LED (green) BBU FAULT LED (orange)

ON / Blinking ON: Normal, Blinking: Recharging ON: Fault Blinking: To be replaced due to its life

OFF AC power is not being supplied Normal

230

Index
1
1U delimiting mark .................................27, 45 Dynamic Pool ......................111, 130, 167, 181

E
ejector ......................................... 14, 17, 21, 23 environment setting .................... 129, 165, 196 ESMPRO/AC.......................................... 39, 63 Ether-HUB.................................................... 57

A
Access Control ............................ 117, 201, 216 Access Control Setting ................................120 ACTIVE LED .................................15, 16, 173 adapter .............................................20, 21, 229 ADP.......................................................20, 224 AIX..................................................................1 arrayname ............................................133, 134 automatic collection of host information.......88 Auto-Shutdown function .............................150

F
FAN FAULT LED... 14, 21, 223, 224, 227, 229 fault tolerant server ............................. 108, 202 FC cable........................................................ 49 FC link .......................................................... 16 FC switch.............................. 64, 106, 198, 202 FC-AL..................................... 1, 106, 213, 220 FCPort......................................................... 207 Fibre channel .......................................... 1, 220 file screening......................................... 67, 176 Forced Separate .......................................... 150

B
BaseProduct...................97, 109, 127, 163, 210 Basic Pool.................... 111, 115, 130, 167, 181 Batch License Unlock .........................139, 168 battery purchase...................................173, 175 BBU FAULT LED.................25, 175, 224, 230 BBU-CONT connection cable...................9, 44

G
GateWay ............................................. 207, 212 GPT disk type ......................................115, 116 GUI ....................................... 78, 135, 177, 194

C
capacity................................119, 120, 181, 214 changing setting...................................162, 192 Configuration Setting ..129, 130, 139, 165, 168 Configuration Setting state..........127, 163, 210 Confirmation of disk array connection state 98, 124, 128, 164, 210 connection confirmation......................141, 144 connection type ...........................106, 107, 213 control path..................................................194 Control Volume ...................................119, 215 ControlCommand ....................................69, 76 controller .....3, 12, 15, 152, 154, 171, 173, 220

H
HBA............................................ 136, 198, 200 host connection port... 107, 124, 130, 166, 168, 187, 207, 213, 217, 218 host information collection ................... 88, 133 host information confirmation .................... 132 host information file ................90, 91, 115, 133 host name............................................ 120, 216 Host Port Extension ...................................... 17 host recognize volume ................ 101, 168, 179 HP-UX ...................................................... 1, 63

D
DAC ........................................................52, 53 data rate .......................................................213 data replication function........................62, 149 DE..................................................................52 direct connection .........................................106 disk array .....................................133, 134, 145 disk drive ... 11, 19, 31, 153, 220, 222, 225, 226 duties volume ..............................................150

I
initialization file.................................. 203, 205 initialization of disk array............... 87, 97, 210 installation .........67, 68, 69, 71, 74, 76, 78, 176 IP address .......................... 185, 212, 217, 218 iSMcc_hostinfo....................................... 90, 91 iSMhoststore............................................... 133

231

K
Key information ..........................................206

O
operation log file........................................... 73 Optima1500 ........................................ 149, 220 Optima1500/2000/3000 ................................ 79 Optima1500/2000/3000 ................................ 72 overhaul .......................................................... 2

L
LAN.....................................................102, 178 LAN cable .................................................5, 56 LAN connection ..........................................193 LAN connector..............................15, 173, 207 LD................................................................208 LD Bind Easy Configuration.......................168 LD Bind/Unbind..........................................168 LD Binding. 113, 119, 125, 131, 167, 168, 178, 179, 181, 183, 188, 214, 217, 219 LD capacity ................. 113, 119, 120, 181, 214 LD Set .................................................110, 208 LD Set name................ 115, 116, 120, 181, 216 LD Set Setting .....................184, 189, 217, 219 LED .............................................................223 license..................................................145, 207 License Unlock... 117, 130, 166, 168, 182, 186, 213, 217 license unlocking.........................................139 LINK LED.................15, 17, 23, 173, 227, 229 Linux1, 7, 63, 71, 76, 77, 91, 105, 132, 144, 197 log file ...................................................73, 193 log file output destination............................193 log output.....................................................193 logical disk number ..................... 115, 119, 120 Loop Switch ID ...........106, 107, 198, 199, 213 LUN.....................................................120, 201 LX........................ 105, 119, 120, 130, 166, 215

P
password ................................................. 72, 73 path information ......................... 120, 204, 216 PD type ........................113, 118, 120, 181, 214 physical disk ........ 111, 118, 130, 167, 181, 214 platform ...................... 105, 107, 120, 213, 216 Pool Binding ................118, 188, 214, 217, 218 pool number.........................................118, 214 port...............................................110, 136, 155 port number........16, 17, 72, 107, 213, 227, 229 power cable............................... 14, 21, 59, 153 POWER FAULT LED ... 13, 21, 223, 224, 227, 229 POWER GOOD LED .... 13, 21, 223, 224, 227, 229 POWER LED ..10, 18, 171, 174, 223, 224, 226 production server ............ 5, 54, 55, 64, 88, 141 program product ..........1, 8, 109, 117, 130, 166 Program Product License Sheet.................. 109 PS.................................................................. 23 purpose.................................................119, 215 purpose of logical disk.........................119, 215

Q
quick format.........................................115, 119 quota management ................................ 67, 176

M
management server....................5, 57, 133, 193 MNT connector .............................................15 modem connector ..........................................17 MV ..............................................................150

R
RAID ...............................1, 111, 112, 220, 221 RAID type............113, 118, 120, 214, 220, 221 READY LED...15, 16, 173, 223, 224, 227, 229 ready state ..................................................... 31 retention time ................................ 62, 149, 172

N
Network.......................................................168 Network Interface Card (NIC) ............193, 194 Network parameters setting.102, 124, 128, 164 network relief setting command ..................192 network setting ..............................83, 191, 195 new server .............................................88, 101 nickname .............................................116, 133 number of LDs .................... 114, 119, 181, 214 NX coordination mechanism.........................39

S
SAS cable ................................. 9, 52, 171, 175 SAS connector ........ 17, 23, 223, 224, 227, 229 Section ................................................ 206, 208 Selection method of host information collection ................................ 100, 124, 128, 164, 168 Selection of LD binding.......111, 125, 130, 167 Selection of setting method . 99, 124, 128, 164,

232

211 SERVICE LED 11, 18, 171, 174, 223, 224, 226 Setting of host connection port....................104 Solaris..............................................................1 spare ............................................................116 Spare............................................................208 Spare Binding ...... 118, 182, 188, 214, 217, 218 start number.........................................214, 215 status display .......................................1, 12, 19 Storage Manager client......78, 79, 85, 135, 177 Storage Manager server67, 71, 72, 73, 115, 129, 165, 177, 196, 197 subnet mask .................................................212 SVP Number................................................193 Switch ID.............................106, 107, 200, 213 system administrator (L3) .67, 72, 85, 139, 140 system disk ....................................................31

U
unlocking the license .................................. 110 UPS coordination.................................... 63, 64 User Datagram Protocol (UDP)............ 93, 178 user level........................... 67, 72, 85, 139, 140

V
volume ............................ 68, 69, 70, 74, 76, 77

W
Web GUI..................................... 135, 177, 194 WG...............................................119, 120, 215 Win GUI ......................................... 78, 83, 177 Windows1, 7, 63, 67, 78, 90, 105, 132, 141, 196, 198 WN.......................................105, 119, 120, 215 WWN mode.................................... 6, 105, 108 WWNN....................................................... 136 WWPN............................................ 6, 120, 136

T
Target ID..............................................198, 200 text format ...................................................122 Time Setting ........................................217, 219

233

BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE

REFERENCE

86 A2 61FA 01