storview storage management software guide · 2007-11-13 · channel interface, network management,...
TRANSCRIPT
Storview.book Page 1 Tuesday, September 23, 2003 5:11 PM
S t o r a g e M a n a g e m e n t S o f t w a r e
S O F T W A R E G U I D E
Storview.book Page 2 Tuesday, September 23, 2003 5:11 PM
Storview.book Page 3 Tuesday, September 23, 2003 5:11 PM
S t o r a g e M a n a g e m e n t S o f t w a r e
S O F T W A R E G U I D E
Storview.book Page 4 Tuesday, September 23, 2003 5:11 PM
Fujitsu Europe Limited
Restricted Rights and Liability
No part of this manual may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, in whole or part, without prior written permission from Fujitsu Europe Limited.
Fujitsu Europe Limited shall not be liable for any damages or for the loss of any information resulting from the performance or use of the information contained herein. Your rights to the software are governed by the license agreement included with any accompanying software. Fujitsu Europe Limited reserves the right to periodically revise this manual without notice. Product features and specifications described are subject to change without notice.
Copyright
Fujitsu Europe LimitedHayes Park CentralHayes End RoadHayes, Middlesex, England UB4 8FE
Copyright © 2003 Fujitsu Europe Limited. All Rights Reserved.
imageRAID is a trademark of Fujitsu Europe Limited, Fujitsu is a registered trademark of Fujitsu Limited.
Other company and product names herein may be trademarks or registered trademarks of their respective companies.
Storview.book Page 5 Tuesday, September 23, 2003 5:11 PM
The Apache Software License, Version 1.1.
Copyright (c) 2000-2002 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
“This product includes software developed by the Apache Software Foundation (http://www.apache.org/).”
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].
5. Products derived from this software may not be called “Apache”, nor may “Apache” appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see, http://www.apache.org/.
Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.
Storview.book Page 6 Tuesday, September 23, 2003 5:11 PM
Contents
Storview.book Page i Tuesday, September 23, 2003 5:11 PM
About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vWelcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vNumbering Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTypographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . viFeatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Multicast Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
License Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Troubleshooting Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Setup for Microsoft® Windows Platforms . . . . . . . . . . . . . . . . . . 5Hardware Pseudo-Driver for Microsoft® Windows® 2000/2003 . . 11
Removing StorView from Microsoft® Windows Platforms . . . . . . 13
3 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Starting StorView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Navigating the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Components of StorView GUI . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Rescan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Configuring for Email Notices . . . . . . . . . . . . . . . . . . . . . . . . . . 23Deleting an Email Addressee . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Changing the Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Tech Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Pop-Up Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Upgrading the License Manager . . . . . . . . . . . . . . . . . . . . . . . . . 30Modifying the IP.db File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
i
Table of Contents
ii
Storview.book Page ii Tuesday, September 23, 2003 5:11 PM
4 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Optimization and Drive Selection for RAID 5 Arrays . . . . . . . . . 35
Creating Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Configuring Array Writeback Cache . . . . . . . . . . . . . . . . . . . . . . 42
Deleting an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Modifying Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Initializing Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Verify Parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Identifying Drive Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Expanding an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Saving, Restoring and Clearing the Configuration . . . . . . . . . . . . 54Trust an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5 Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Assigning a Global Hot Spare . . . . . . . . . . . . . . . . . . . . . . . . . . 61Assigning a Dedicated Hot Spare . . . . . . . . . . . . . . . . . . . . . . . . 63Removing a Hot Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Auto Hot Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6 LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Viewing Unassigned Free Space . . . . . . . . . . . . . . . . . . . . . . . . 68Creating a LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Tips on Setting LUN Availability . . . . . . . . . . . . . . . . . . . . . . . . 73
Expanding a LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7 LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Viewing Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Viewing LUN Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Creating a LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Deleting a LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Modifying a LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8 Controller Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Modifying Controller Properties . . . . . . . . . . . . . . . . . . . . . . . . . 93Controller Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Controller Environmentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Table of Contents
Storview.book Page iii Tuesday, September 23, 2003 5:11 PM
Controller Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Controller Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Changing the Controller LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . 104StorView Performance Optimization . . . . . . . . . . . . . . . . . . . . . . 105Execution Throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Scatter/Gather . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
9 Drive Panel Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Drive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Locate Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Make Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Rebuild Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10 Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Accessing and Navigating the StorView Event Log . . . . . . . . . . . 113Exporting the StorView Event Log . . . . . . . . . . . . . . . . . . . . . . . 114Clearing the StorView Event Log . . . . . . . . . . . . . . . . . . . . . . . . 116Operating System Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 117List of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118imageRAID Controller Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Drive Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Controller Port Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127SES Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129StorView Server Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Failed Drives Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Access Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Command Size - Alignment Statistics . . . . . . . . . . . . . . . . . . . . . 139Readahead Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Command Cluster Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
A Optimizing RAID 5 Write Performance . . . . . . . . . . . . . . . . . . . . . . 145Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Sequential Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Number of Outstanding Commands . . . . . . . . . . . . . . . . . . . . . . 146Access Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Access Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147RAID 5 Sub-Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Multiple Drive Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Faster Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
iii
Table of Contents
iv
Storview.book Page iv Tuesday, September 23, 2003 5:11 PM
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
B Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Preface
Storview.book Page v Tuesday, September 23, 2003 5:11 PM
About this Manual
Welcome
Congratulations on the purchase of StorView™ Storage Management software
from Fujitsu Europe Limited. StorView is a full-featured GUI-based software suite
designed to configure, manage, and monitor imageRAID Series Storage Systems.
StorView provides a centralized remote management to control primary storage
assets vital to ensuring maximum data reliability, network up-time, and system
serviceability. It allows you to manage the storage system from a host running
StorView locally, and from a web browser across the intranet or internet.
This software guide provides the operational and reference information to
configure and manage the imageRAID Controllers installed in your storage system
when using StorView Storage Management software. Although the target
audience is experienced system administrators who are familiar with the
principles and conventions of Small Computer System Interface (SCSI), Fibre
Channel Interface, network management, and Redundant Array of Independent
Disk (RAID) technology, you will find step-by-step procedures to perform
configurations, management and enclosure monitoring of your storage solution.
v
About this Manual
vi
Storview.book Page vi Tuesday, September 23, 2003 5:11 PM
Numbering Convention
The capacity of most disk drives is reported from the Controller using base-10
decimal system expressed in GB (1 GB = 1,000,000,000 bytes). Many operating
systems use base-2 binary system to define the same space in GB (1 GB =
1,073,741,824 bytes. This can cause a visual discrepancy of approximately 7%
between what the controller reports and what the operating system reports.
For example, an array of six drives may be reported as 733 GB by StorView, and
Microsoft® Windows NT reports it as 699282 MB and Microsoft® Windows® 2000
reports it as 682.89 GB.
The volume size is the same amount whether it is reported in base-10 or base-2,
or MB vs. GB.
NOTE: The RAID Controller also reserves some capacity for configuration data.
Typographical Conventions
The following typographical conventions are used in the user’s guide:
� Menu and button selections are displayed in the format: “From the Main
screen click on the Settings button.”
� Code font will indicate literal text used in examples.
� Italic code font indicates a replaceable or variable item in code.
� Italic text indicates the item that is selected or chosen.
� Key strokes are enclosed in brackets, e.g., <Esc>, <Y>, or <Enter>.
Numbering Convention
About this Manual
Storview.book Page vii Tuesday, September 23, 2003 5:11 PM
Features
The following are some of the major features of StorView Storage Management
software.
� Highly visual and intuitive user interface, making it easy to learn and use.
� HTML-based interface allows it to work with nearly any web browser
software.
� Local or network-based management and fault reporting.
� Automatic detection of servers on the network minimizes setup and support.
� Redundant server operation for continuous management and monitoring.
� Graphically displayed LUN management and LUN Mapping capabilities.
� Server-based service runs in the background and requires no user input.
� User name and password protection eliminates unwanted access to your
storage.
� Add on modules for expandability and increased functionality.
Features vii
About this Manual
viii
Storview.book Page viii Tuesday, September 23, 2003 5:11 PM
Features
Chapter 1
Storview.book Page 1 Tuesday, September 23, 2003 5:11 PM
Introduction
Overview
StorView is a utility software designed to provide local and remote storage
management and monitoring of imageRAID storage systems. Currently available,
the imageRAID Controller module provides support for the imageRAID Storage
Systems which utilize the 2Gb FC-to-FC RAID Controller(s).
The StorView Server is comprised of two parts, the Server and the GUI. The
Server component runs as a background service and is responsible for managing
the installed components. The Server discovers system devices, manages and
distributes message logs, and communicates with other StorView Servers installed
on the same local network or if configured, external network subnets. The GUI
component provides the interface in an HTML based front end which is accessed
through a standard web browser.
A HTTP web server is required which provides the interface between the Server
and GUI. Web Server software is included with StorView and it is the open source
release of Apache 2.0 web server. During installation it is automatically installed
and configured through the installation process. It allows the Server CGI scripts
to acquire web pages from the Server thus providing the interaction between the
Server and the GUI. The installation of the HTTP web server software is self
contained and will not conflict with other web server software currently installed
on your system, unless it is listening on Port 9292.
1
Chapter 1 - Introduction
2
Storview.book Page 2 Tuesday, September 23, 2003 5:11 PM
Multicast Communication
The StorView Server uses multicasting technology to provide the inter-
communications with other StorView Servers when the Global Access license is
installed. During the Server’s initial start-up, it performs a multicast registration
using the default multicast IP address 225.0.0.225 on port 9191. Once the
connection is established, the Server is able to receive all packets sent to the
multicast address from other StorView Servers, as well as packets sent directly to
the host’s IP address on the specified port listed in the file “IP.db.” All packets
sent to the multicast address remain in the local network, unless a specific host IP
address outside the subnet is appended to the list in the file IP.db. (Refer to
“Modifying the IP.db File” on page 31.) This inter-communication capability
provides the StorView Servers with the ability to remotely monitor each other on
the same local network.
Each Server sends a “check-in” packet at 10 second intervals. Once an initial
check-in packet is received, all StorView Servers will know the existence of the
other StorView Servers. If a Server fails to send two check-in packets, the other
Servers will mark that Server as “missing.” This is indicated by a white Server icon
displayed on the Main screen under the “Other Servers” section.
When the StorView Server service is down for any reason that owns the
monitored solution and two check-in packets are not received, the monitoring/
control will be transferred to another StorView Server.
If a StorView Server is down and the controller is operational and functioning it
continues to process events. When the StorView Server comes back online it will
automatically synchronize its logs to those on the controller. Those synchronized
logs have a date and time in parenthesis displayed in the Message field of the
Event log window. That time-date stamp indicates when the event actually took
place.
The StorView Server has the ability to communicate with any StorView Server on
the local network. These other Server’s are displayed on the Main screen and are
listed under the “Other Servers” section. They display the IP address, name, and a
overall status of that Server’s monitored storage solution. To indicate status of a
monitored Server storage solution, the icon of the specific Server changes to one
of four states, refer to “Components of StorView GUI” on page 16.
Multicast Communication
Chapter 1 - Introduction
Storview.book Page 3 Tuesday, September 23, 2003 5:11 PM
License Managers
The StorView license managers are defined as StorView Local Access and StorView
Global Access. The Local manager is included with the purchase of the Fujitsu
Europe Limited imageRAID-based storage system and provides the basic control,
management, and monitoring of the local attached storage solution. The Global
manager is offered through a purchasable licensing program and provides the
capabilities of the Local manager features plus remote login, configuration, and
monitoring, and it provides alert notifications via Email. With remote login and
management the user can focus or log into a different storage solution discovered
and displayed under the Other Servers section on the Main screen.
NOTE: Only the following topologies will support monitoring failover when the
Global Access manager is installed. Each manager requires a unique serial
number and activation code, and a minimum of two are required.
� Simplex:
• Dual Port Multi-Host Single Connection
• Dual Port Multi-Host Dual Connection
� Duplex:
• Multi-Port Mirrored Dual Host System Single Connection
• Multi-Port Mirrored Dual Host System Quad Connection
• Multi-Port Mirrored SAN Attach Single Switch Connection
• Multi-Port Mirrored SAN Attach Dual Switch Connection
During installation you will be prompted to select the type of license manager you
wish to install. If you choose Global Access, you will be prompted to enter a
unique serial number and activation code which is provided with the purchase of
the of a Global Access license.
Installing StorView with global access on each host that will be attached to a
storage solution either directly or indirectly through a switch, will provide
monitoring failover. During the initial startup of the host systems, the StorView
Server that identifies the storage solution first, assumes ownership of the devices.
The other StorView Server will display a message in its browser Main screen that
another host is monitoring the storage solution.
License Managers 3
Chapter 1 - Introduction
4
Storview.book Page 4 Tuesday, September 23, 2003 5:11 PM
Should the StorView Server service with ownership of the storage solution fail, that
is the service is stopped, the remote StorView Server will take over ownership and
control of the storage solution. You will notice a change in the GUI, you will see a
message that another host is monitoring, thus transferring ownership to the remote
StorView Server. The user can expedite the process if they know that the system
with the StorView Server which had ownership of the storage is down for some
reason by clicking the Rescan button. The key to the monitoring failover is whether
or not the owning StorView Server service is running. Once the service stops the
StorView Server can no longer send “Check-In” packets. A fault in the host loop
will not cause a monitor failover is due to the fact that the owning Server service is
still operational. However, neither StorView Server will be able to communicate
with the storage solution during a loop failure.
Troubleshooting Assistance
To assist you when troubleshooting problems with your system, the Events
chapter and on-line help provides a list of all the events that can occur, along
with a suggested cause and action to take. When a warning or error event occurs,
you can review the event log and locate the suspect event and refer to the Events
chapter or help section to determine the possible cause or causes and the
suggested action to take. Also, refer to “Troubleshooting” on page 151.
Troubleshooting Assistance
Chapter 2
Storview.book Page 5 Tuesday, September 23, 2003 5:11 PM
Installation
System Requirements
The following are the minimum system requirements to install and use StorView™:
� A PC with an Intel Pentium III type processor or compatible.
� 64 MB RAM.
� CD-ROM.
� 256 color video adapter (Display settings should be set to 1024x768 and Font Size=Small).
� Operating systems - Microsoft® Windows NT® 4.0 (SP6), Microsoft® Windows® 2000 (SP2 or greater), or Microsoft® Windows® 2003.
� Web browser software (HTTP 1.1 compliant) such as: Microsoft® Internet Explorer 5.5 or greater, Netscape 7.0 or greater, Mozilla 1.1 or greater, or Opera 7.11 or greater.
� 60 MB hard disk space.
� Network adapter or a Microsoft® Loop Back Adapter software for local attachments when an HBA is not installed.
� imageRAID Storage System.
Setup for Microsoft® Windows Platforms
After you have completed the hardware installation and setup, you should be
ready to begin the software installation. Ensure that your host system meets the
system requirements listed above.
1 Insert the Software/Documentation Disc into your CD-ROM drive.
5
Chapter 2 - Installation
6
Storview.book Page 6 Tuesday, September 23, 2003 5:11 PM
The autorun program will automatically start the navigation menu, click on
the StorView button.
Disc Navigation Screen
2 The StorView navigation tree menu will open. You may choose to review the
StorView READMe file, open the Software Manual, or Install the software.
To continue with installation, click the Install button.
3 The Welcome screen appears, click the Next button.
Welcome Screen
Setup for Microsoft® Windows Platforms
Chapter 2 - Installation
Storview.book Page 7 Tuesday, September 23, 2003 5:11 PM
4 Read the license agreement and click the Yes button to accept the software
license and continue. Click No if you do not wish to license the software
which will cancel the installation.
License Agreement Screen
5 Choose the license manager to install, and click the Next button.
The Local manager is provided free without the requirement of a serial
number or activation code. It allows you to configure, manage, and monitor
your storage system that is attached to your local host system. The Global
manager requires a serial number and activation code. The Global manager
allows you to perform remote login, management and monitoring, and
monitoring failover capabilities plus Email alert notifications.
Select Version Package Screen
Setup for Microsoft® Windows Platforms 7
Chapter 2 - Installation
8
Storview.book Page 8 Tuesday, September 23, 2003 5:11 PM
6 If you selected the Global manager, enter your serial number and activation
code, then click the Next button.
Serial Number and Activation Code Screen
7 Enter the user name and password, then click the Next button.
This is the user name and password that will be established for the web
server software that is installed as a component of StorView. You may use up
to 258 characters for the user name or password, and it is case sensitive. Be
sure to write down the user name and password, as it will be required to log
into StorView. In this example, we used “admin.”
User Name and Password Screen
8 Select the directory for the software installation, then click the Next button.
Setup for Microsoft® Windows Platforms
Chapter 2 - Installation
Storview.book Page 9 Tuesday, September 23, 2003 5:11 PM
The default directory is \Program Files\StorView.
Installation Destination Directory Screen
9 Select the Start Menu folder and click the Next button.
You may accept the default name, “StorView” or enter your own custom Start
Menu folder name by typing in the desired name.
Start Menu Folder Screen
10 The installation will begin. You may cancel the installation process by
clicking the Cancel button at any time.
Setup for Microsoft® Windows Platforms 9
Chapter 2 - Installation
10
Storview.book Page 10 Tuesday, September 23, 2003 5:11 PM
Installation Destination Directory Screen
During the installation you will see several screens appear while the installer
completes the StorView installation, followed by the installation and
configuration of the HTTP web server software.
11 Once the installation is complete a screen is displayed indicating the
installation was successful. Click the Finish button.
Installation Complete Screen
Setup for Microsoft® Windows Platforms
Chapter 2 - Installation
Storview.book Page 11 Tuesday, September 23, 2003 5:11 PM
Hardware Pseudo-Driver for Microsoft® Windows® 2000/2003
A .inf pseudo-driver file should be installed on all Microsoft® Windows®
2000/2003 based systems that will have an imageRAID storage system attached.
Manual Installation
1 Click on the Start button, choose Settings and select Control Panel.
2 Double-click on the Add/Remove Hardware icon.
The Add/Remove Hardware Wizard will appear, click the Next button.
3 From the “Choose a Hardware Task” window, select “Add/Troubleshoot a
Device” and click the Next button.
4 In the “Choose a Hardware Device” window, select the option “Add a new
device” and click the Next button.
You should now be in the “Find New Hardware” window.
5 Choose the option “No I want to select the hardware from a list” and click
the Next button.
6 The “Hardware Type” window appears, scroll down and select System
Devices then click the Next button.
Now you will choose a driver. Click the Have Disk button.
7 Ensure that your Software/Documentation Disc is in the CD-ROM drive. Click
the Browse button. Locate the CD-ROM and locate the “Drivers” folder and
select the “fujitsu.inf” file. Click the Open button.
8 The “Install from Disk” window appears, click the OK button.
9 The “Select a Device Driver” window appears, select under Manufacturer
column “Fujitsu” and under Models “imageRAID Storage System Processor
Device” and click the Next button.
The “Start Hardware Installation” window will appear.
10 Click the Next button.
The window “Complete the Add/Remove Hardware” Wizard will appear.
11 Click on the Finish button.
Hardware Pseudo-Driver for Microsoft® Windows® 2000/2003 11
Chapter 2 - Installation
12
Storview.book Page 12 Tuesday, September 23, 2003 5:11 PM
New Hardware Found at Startup - Installation
1 At startup, if the “Found New Hardware” Wizard appears, click the Next
button.
The “Install Hardware Device Drivers” window appears.
2 Choose the option that reads “Display a list of the known drivers for this
device so that I can choose a specific driver” and click the Next button.
The “Hardware Type” menu will appear.
3 Scroll down and select System Devices, then click the Next button.
Now you must choose a driver.
4 Ensure that your Software/Documentation Disc is in the CD-ROM drive. Click
the Browse button. Locate the CD-ROM and locate the “Drivers” folder and
select the “fujitsu.inf” file. Click the Open button.
5 The “Install from Disk” window appears, click the OK button.
6 The “Select a Device Driver” window appears, select under Manufacturer
column “Fujitsu” and under Models “imageRAID Storage System Processor
Device” and click the Next button.
NOTE: If the “Update Driver Warning” appears, click the Yes button.
The “Start Hardware Installation” window will appear.
7 Click the Next button.
The “Completing the Found New Hardware” Wizard will appear.
8 Click on the Finish button.
New Hardware Found at Startup - Installation
Chapter 2 - Installation
Storview.book Page 13 Tuesday, September 23, 2003 5:11 PM
Removing StorView from Microsoft® Windows Platforms
1 Insert the Software/Documentation Disc into your CD-ROM drive.
The autorun program will automatically start the navigation menu, click on
the StorView button.
Disc Navigation Screen
2 The StorView navigation tree menu will open. Click the Install button.
3 The InstallShield Wizard will open, click the radio button for Remove and
click the Next button.
InstallShield Wizard Screen
4 Follow the on-screen instructions to complete the uninstall process.
Removing StorView from Microsoft® Windows Platforms 13
Chapter 2 - Installation
14
Storview.book Page 14 Tuesday, September 23, 2003 5:11 PM
Removing StorView from Microsoft® Windows Platforms
Chapter 3
Storview.book Page 15 Tuesday, September 23, 2003 5:11 PM
Getting Started
Starting StorView
When you start the StorView software, it will automatically start your default web
browser and you are presented with the graphical HTML interface. There are
several ways to start StorView. From Microsoft® Windows®, you may choose to
access it from the Start Menu, by clicking the Start button and selecting Programs,
followed by choosing StorView and then selecting “StorView Manager Console.”
Or you may open a new page in your web browser and enter either of the
following URL addresses: “HTTP://localhost:9292” or “HTTP://127.0.0.1:9292” and
press <Enter>. (For remote access, substitute your networked Host IP address in
place of localhost or 127.0.0.1.)
Navigating the GUI
The GUI component provides the user with an interface from which they can
create logical arrays, sub-arrays, and LUNs, and perform LUN mapping along
with monitoring enclosure components and array status.
There are many components to the StorView GUI. This chapter is designed to
provide a description of the StorView interface components. It provides details
explaining how to interpret specific icons, and how they assist you with
monitoring the status of your enclosure(s) and arrays. The remainder of the
chapter describes basic settings and license manager upgrades.
15
Chapter 3 - Getting Started
16
Storview.book Page 16 Tuesday, September 23, 2003 5:11 PM
Components of StorView GUI
The following provides the identification and description of the different icon
components that comprise the StorView GUI. Familiarize yourself with the
interface and refer to this section for questions about each icon. Holding the
mouse pointer over an icon will display pop-up information specific to the item.
StorView Main Screen GUI
Icon Description and Condition
StorView Server Icon(located in the dark yellow area)
Depicts the current StorView Server that you are logged into. The icon will indicate the status of its’ components by changes in the color and state:
• Normal Gray - Status is ok.
• Flashing Yellow - Indicates a server warning that a device connected is in degraded mode. (Warning)
• Flashing Red - Indicates a server error where a device has malfunctioned. (Error)
StorView Servercurently logged in
Opens the Event Log, rescans the bus,
and configuresE-mail/Password settings
Displays the number ofusers logged in (mouse
rollover displays address,host, and user name)
Installed module
Attached StorageSolution (focused)
Save/Restore/ClearConfiguration buttons
Attached Storage Solution(not focused)
Displays the software versionand installed license manager
Indicates another StorViewServer is monitoring this storage
Opens a windowdisplaying online help
Allows the user to capturethe event log and configuration information and save it to a file
Installed RAID Controllers(number of icons representsnumber of controllers installed)
LUN management andavailability, displays currentLUNs and their status
LUN Mappings
Enclosure WWN &SES firmware version
Enclosure temperaturemonitor and notice that theaudible alarm is sounding
Storage Enclosure frontview depicts the disk
drives and their status
Storage Enclosurerear view depictsPower Supplies, Fans,Disk I/O, SES Controller,Host I/O Cards, and theRAID Controllers
Defined arrays withstatus information
and operation controls
Status of drive loopsand displays the loopspeed setting
Enclosure Number
Locates the disk drivemembers of the array
Dark AreaEncompasses Current
Server Logged Into
Embedded URL linkto Fujitsu's website
Displays the Status, IPAddress and Name ofthe discovered Server
(Global manager accessrequired to be installed.)
Components of StorView GUI
Chapter 3 - Getting Started
Storview.book Page 17 Tuesday, September 23, 2003 5:11 PM
Remote StorView Servers Icon(located in the light yellow area, requires Global manager access)
Depicts the discovered StorView Server’s that you are not logged into. The icon will indicate the status of its’ components by changes in the color and state:
• Normal Gray - Status is ok.
• Flashing Yellow - Indicates a server warning that a device connected is in degraded mode. (Warning)
• Flashing Red - Indicates a server error where a device has malfunctioned. (Error)
• Flashing White - The server has not responded in at least 40 seconds and is considered missing. If you would like to remove the missing server from the list, click the Rescan button. This will refresh the screen with a current list of discovered Servers..
User Icon(located adjacent to Server icon)
Represents the number of user’s logged into the current StorView Server you are focused on. Placing the mouse pointer over the icon will display the IP address, host name and the user name.
Storage Solution Icon(displayed for each storage solution)
When selected, it displays the focused configuration and its’ associated arrays, controllers, LUNs, LUN mappings, and enclosures.
• Normal Gray - Status is ok.
• Flash Yellow with red “!” - Indicates a component in the storage enclosure(s) is in degraded mode. (Warning)
• Flashing Red - Indicates a component in the storage enclosure(s) has malfunctioned. (Error)
• Flashing Red with “?”- Indicates that the storage enclosure was there at startup but cannot be now located.
Unmonitored Icon This icon indicates that another StorView Server is monitoring this device, or if you just performed a rescan then the StorView Servers are still determining which Server will monitor the storage solution (it takes about 5 seconds from the point that the rescan is completed).
Controller Icon The number of controller icons displayed indicates the number of RAID Controllers installed in the enclosure.
• Single icon represents a Stand-Alone topology.
• Dual icon represents an Active-Active topology.
• The icon will flash red if the controller’s backup battery unit has failed, or in Active-Active topologies when the partner controller has failed.
Icon Description and Condition
Normal
Normal
Error
Components of StorView GUI 17
Chapter 3 - Getting Started
18
Storview.book Page 18 Tuesday, September 23, 2003 5:11 PM
Array Status Icon This icon appears adjacent to the Array name and gives a overall status of the array.
• Green - Status is ok.
• Yellow - Indicates a drive component in a RAID 5 or 50 array has failed and the array is not fault tolerant, or the array is in a rebuild cycle. (Warning)
• Red - Indicates an array is invalidated/offline due to (Error):RAID 0 = One drive has failed.RAID 1/10 = Two drives have failed from the same pair.RAID 5 = Two drives have failed.RAID 50 = Two drives have failed within the same sub-array.
LUN Status Icon This icon appears adjacent to a LUN name and gives an overall status of the LUN.
• Green - Status is ok.
• Yellow - Indicates the LUN is part of an array that is degraded. (Warning)
• Red - Indicates the LUN is part of an array which is invalidated (offline),RAID 0 = One drive has failedRAID 1/10 = Two drives have failed from the same pairRAID 5 = Two drives have failedRAID 50 = Two drives have failed within the same sub-array
Drive Loop Status Icon These icons appears adjacent to the Drive Loop name and presents an overall status view of the Loop.
• Green - Indicates the Drive Loop is up.
• Red - Indicates the Drive Loop is down. (Warning)
Drive Status Icon Animated drive status icons which are displayed in the front view of the enclosure and will indicate the status and condition of the specific disk drive.
• Member - Drive is a member component of an array.
• Available - Drive is online and available for use in an array or as a hot spare.
• Dedicated Spare - Drive is marked as a dedicated spare to an array.
• Empty - Drive slot is empty.
• Failed - Drive is marked as failed.
• Hot Spare - Drive is a global spare.
• Missing - Indicates that StorView is unable to determine the status of the drive.
• Initializing - Drive is a member of an array being initialized. (Also see Critical below.)
Icon Description and Condition
Green
Yellow
Red
Green
Yellow
Red
Green
Red
Member
Available
Dedicated Spare
Empty
Failed
Hot Spare
Initializing
Missing
Components of StorView GUI
Chapter 3 - Getting Started
Storview.book Page 19 Tuesday, September 23, 2003 5:11 PM
Drive Status Icon (continued)
• Rebuilding - Drive members or an array is in rebuild mode.
• Locate - Clicking the “arrow” icon next to the “specific array” in the Arrays section will display the “arrow” icon on the drive members of this array displayed in the front enclosure view.
• Critical - Drive(s) are members of a fault tolerant array and are in a non-fault tolerant state during a rebuild cycle.
• Updating Firmware - This icon will appear when the subject drive’s firmware is being updated.
• Failed Array Member - This icon will appear on all disk drives that are members of an array that has failed. For example if you remove a drive from a RAID 0 array or a drive in that array fails, the remaining drive members will have this icon displayed indicating that array has failed. If you accidentally remove the wrong drive in a critical redundant array (RAID 5) instead of the failed drive, that array will have failed and its member drives will have this icon displayed. Re-inserting the drive that was accidentally removed will put the drive members back to a critical state in which the array is being rebuilt.
• Queued to Initialize - This icon is displayed on the drive members whose array is to be initialized and is placed in a queue for the process to be started and completed. Only one array can be initialized at one time.
• Expanding - This icon is displayed on the drive members whose array is expanding.
• Verifying - This icon is displayed on the drive members whose array’s parity data is being verified.
Fan Icon Animated fan icons are displayed in the rear view of the enclosure and will change colors and text animation according to the state of one or both cooling fans.
• Normal - Both fans are operating normally.
• Critical- One fan in the fan module has failed.
• Failure - Both fans in the fan module have failed or the cooling fan module has been removed.
Icon Description and Condition
Rebuilding
Locate
Critical
Updating Firmware
Member Failed Array
Queued to Initialize
Expanding
Verifying
Normal (gray)
Critical (yellow)
Failure (red)
Components of StorView GUI 19
Chapter 3 - Getting Started
20
Storview.book Page 20 Tuesday, September 23, 2003 5:11 PM
Power Supply Icon Animated Power Supply icons are displayed in the rear view of the enclosure and will change according to the state of the specific power supply.
• Normal gray icon indicates that the power supply is operating normally.
• A red flashing icon with “Power Supply Failure” displayed indicates that the subject power supply has failed.
• A flashing solid red icon indicates that the power supply is missing.
Disk I/O Card Icon Animated Disk I/O Card icons are displayed in the rear view of the enclosure and will change colors according to their state.
• Normal - Each Disk I/O Card is operating normally. Each corresponding Drive Loop Status icon will be green.
• Failed - A Disk I/O Card has failed, and the icon will change to flashing red. The corresponding Drive Loop Status icon will change to flashing red.
• Missing - A Disk I/O Card is missing.
Host I/O Card Icon Host I/O Card icons are displayed in the rear view of the enclosure and will change according to their state.
• Normal - Each Host I/O Card is operating normally.
• Missing - A Host I/O Card is missing or was removed.
RAID Controller Icon Animated RAID Controller icons are displayed in the rear view of the enclosure will change colors according to their state.
• Normal - RAID Controller is operating normally.
• Failed - RAID Controller has failed, applicable to Active-Active topologies. The icon will flash red indicating it has failed or the backup battery has failed.
• Missing - A RAID Controller is missing or removed.
Audible Alarm Icon This animated icon will appear any time the front bezel alarm is sounding.
Icon Description and Condition
Normal
Failure
Missing
Normal
Fail
Missing
Normal
Missing
Normal
Failed
Missing
Alarm
Components of StorView GUI
Chapter 3 - Getting Started
Storview.book Page 21 Tuesday, September 23, 2003 5:11 PM
Enclosure Icon Enclosure icons are displayed at the bottom of the main screen and will change shades according to its’ state, as well as its’ individual component icons.
• Normal - All components are operating normally.
NOTE: The enclosures are labeled above each front view to aid with identifying a specific enclosure in a multiple enclosure environment.
• Lost SES - The enclosure has lost communication with the SES processor. The icon will grey or dim.
NOTE: The order of the enclosures displayed in the GUI when multiple enclosures are daisy-chained together, is based on the ID range setting of the enclosure’s SES Controller card. For example, if you have three enclosures (IRF-1S plus two IRF-JBODs) the IRF-1S is set to IDs 0 - 11, the first IRF-JBOD enclosure is set to IDs 16-27, and the second IRF-JBOD enclosure is set to IDS 32-43, then they will appear in the GUI as the top enclosure being the IRF-1S (0 - 11), followed by the first IRF-JBOD (16 - 27), and finally the last or lowest display is the second IRF-JBOD (32 - 43).
Status Icon These icons are displayed in the Email setup and Event logs. They depict the type of events that can be selected or isolated for email notices or the type of event in the event log.
• Information - This icon represents the information type of events.
• Warning - This icon represents a warning type of event.
• Error - This icon represents an error type of event.
Enclosure Temperature Icon Enclosure temperature icon is displayed just above the rear enclosure and indicates the status of the enclosure temperature.
• Normal - This icon indicates that the temperature is normal. It appears green.
• Warning - This yellow icon indicates that the enclosure temperature is approaching the established threshold.
• Failed - This red icon indicates that the enclosure temperature has reached or exceeded the enclosure temperature threshold. (If the fans are operating normally and the enclosure air flow temperature seems normal it may be an indication that the temperature sensor has failed.
• Missing - This icon indicates that the information from the SES processor regarding the sensors is invalid or missing.
Icon Description and Condition
Normal
Lost SES
Information
Warning
Error
Normal
Warning
Failed
Missing
Components of StorView GUI 21
Chapter 3 - Getting Started
22
Storview.book Page 22 Tuesday, September 23, 2003 5:11 PM
Configuration Icons These icons are located in the “light yellow” area directly above the “Arrays” section next to the “Configuration” label in the Main screen.
• Save - This icon when clicked will save the current configuration to an external file. Refer to “Saving the Configuration” on page 55.
• Restore - This icon when clicked will restore the configuration from the saved file. Refer to “Restoring the Configuration” on page 57.
• Clear - This icon when clicked will clear the configuration. This will delete all information pertaining to and defining arrays, LUNs, mappings, email settings, etc. Data will be lost on the array's if you clear the configuration.
Icon Description and Condition
Save Configuration
Restore Configuration
Clear Configuration
Components of StorView GUI
Chapter 3 - Getting Started
Storview.book Page 23 Tuesday, September 23, 2003 5:11 PM
Rescan
This button allows the user to force a system rescan to refresh the display.
From the Main screen, click the Rescan button located in the dark yellow
area just below the focused server icon. The screen will be updated.
Main Screen
During this process the StorView Server will query the host, HBA and SCSI
devices, examine installed modules, and create a log entry. Any new devices
or changes in devices/modules discovered will result in an updated display.
Settings
Configuring for Email Notices
With the Global manager installed, StorView provides you with the ability to
establish up to ten email addresses where notices of events can be automatically
mailed to the selected user(s).
To configure the Email notifications perform the following:
1 From the Main screen click the Settings button.
The Settings window will open with the Email tab selected.
Rescan 23
Chapter 3 - Getting Started
24
Storview.book Page 24 Tuesday, September 23, 2003 5:11 PM
2 Enter the name or address of your Email server.
This will be the SMTP mail server name. It is designed to listen on port 25 in
accordance with SMTP 1.0 protocol.
Settings Screen - Email Tab
3 If you would like a signature appended to the message, click the check box
and type in the signature information in the scrollable window provided.
4 Enter the user email addresses as desired.
You may add up to ten (10) email addresses. Type the full email address and
click one or more of the check boxes next to the specific name. This
determines which levels of events are included as notifications for that user.
The types of events are: Informational, Warning, and/or Errors.
If you have more than five email recipients, you will need to click the button
“6 - 10” to access the next five address blocks.
5 Click the Apply button.
You will receive a confirmation message that the changes were successfully
completed. Click the Close button.
6 Test the configurations by clicking the Test button.
You will receive a confirmation message that the test was successfully
completed, and each addressee will receive a “Test Message” from the mail
server. Click the Close button.
7 Click the Close button on the Settings window.
Configuring for Email Notices
Chapter 3 - Getting Started
Storview.book Page 25 Tuesday, September 23, 2003 5:11 PM
Deleting an Email Addressee
1 From the Main screen click on the Settings button. The Settings window will
open with the Email tab selected.
2 Click the Delete button next to the address name you wish to remove.
Settings Screen - Email Tab
3 Click the Apply button make the changes effective, then click the Close
button on the Settings window.
Deleting an Email Addressee 25
Chapter 3 - Getting Started
26
Storview.book Page 26 Tuesday, September 23, 2003 5:11 PM
Changing the Password
This option provides the ability to change the access password used at log in.
1 From the Main screen click on the Settings button.
The Settings window will open with the Email tab selected.
2 Click the Password tab at the top of the window.
Settings Screen - Password Tab
NOTE: Passwords will not be displayed as you type them.
3 Type in the Old Password and press the <Tab> key or click in the next text
box.
4 Type in the New Password and press the <Tab> key or click in the next text
box.
5 Re-type the New Password.
6 Click the Change button.
If you do not enter the old password correctly, or the new password and its
re-type is not an exact match, the “Change” button will not become active.
You will receive a confirmation message that the changes were successful.
Click the Close button.
7 Click the Close button on the Settings window.
NOTE: If you loose or misplace your password, contact technical support for
instructions.
Changing the Password
Chapter 3 - Getting Started
Storview.book Page 27 Tuesday, September 23, 2003 5:11 PM
Tech Support
This feature allows the user to provide technical support with event and
configuration information to assist with troubleshooting.
1 From the Main screen, click the Tech Support button, located in the upper
right corner of the window under the StorView logo.
Main Screen
The following screen is displayed.
Tech Support Screen
Tech Support 27
Chapter 3 - Getting Started
28
Storview.book Page 28 Tuesday, September 23, 2003 5:11 PM
2 Enter the requested information for each field.
The Problem field is scrollable allowing you to review the information you
will be sending.
3 Click the Download button.
You will receive a screen prompt to save the file on your local disk. Enter a
name for the file and click Save. The software will create a file with your user
data, a capture of the event log files, and a capture of all configuration
information that technical support representatives will be able to work with
to assist with solving your problem.
4 Click the Close button on the Technical Support window.
5 When requested by a technical support representative, email the saved file to
the address specified by the technical support representative.
Help
This button opens the HTML-based online help.
Pop-Up Assistance
Details on specific components in the StorView interface is available by placing
the mouse pointer over an object and holding it stationary. Sometimes known as
Tooltips or pop-up text, it will assist the user in identifying a component or text
link enabling the user to better understand its function. Also, during some
processes, a Notes window is provided that is context sensitive to entries made
and it will make suggestions, offer guidance, or explain a limitation or restriction
based on known settings.
Help
Chapter 3 - Getting Started
Storview.book Page 29 Tuesday, September 23, 2003 5:11 PM
About
This button provides the user with access to the StorView software version
information and displays the type of license manager installed.
1 From the Main screen, click the About button, located in the upper right
corner of the window under the StorView logo.
Main Screen
The following screen is displayed. The License Manager type for this
installation is indicated below the version number in parenthesis.
2 Click the Close button on the Help window.
About Screen
About 29
Chapter 3 - Getting Started
30
Storview.book Page 30 Tuesday, September 23, 2003 5:11 PM
Upgrading the License Manager
Some capabilities of StorView are dependent on which license manager is
installed. If you have the Local Manager installed, provided free with the storage
system, you are limited to local management and monitoring of the storage
solution attached to the host system. If a remote login is attempted from another
host system on the same network, you will see a message displayed with the
option to upgrade your license manager by entering your serial number and
activation code. You can also upgrade your license manager from the local
console by clicking on the link provided in the notice displayed in the “Other
Servers” section or clicking the Settings button.
Contact your sales representative to obtain a serial number and activation code.
1 With your serial number and activation code, click on the “link” provided
under the “Other Servers.” The Settings window will open with Email tab
selected. There you will enter the required information and click the Activate
button.
This will remove the limitations of the Local manager and you will now have
the full capabilities of the Global manager.
License Upgrade Screen
2 Once you have completed the upgrade, click on the Close button in the
confirmation window.
Upgrading the License Manager
Chapter 3 - Getting Started
Storview.book Page 31 Tuesday, September 23, 2003 5:11 PM
3 Click the Close button on the Settings window.
4 You can verify the change by clicking the About button and verify it now
displays (Global).
Also the notice displayed under the “Other Servers” section has been
removed and any remote discovered StorView Servers will be displayed.
Modifying the IP.db File
Making changes to the IP.db file, allows you to specify additional host outside the
subnet to be included in the inter-communications between StorView Servers for
monitoring and monitorig failover abilities. (Refer to “Multicast Communication”
on page 2.)
Using a text editor, open the file: <install directory>/db/IP.db
The IP.db file default entries are:
--------------------------
| MulticastPort = 9191 |
| IP0 = 225.0.0.225 |
| 'IP1 = 199.199.199.41 |
| 'IP2 = 199.199.199.42 |
--------------------------
Lines that contain comments begin with a “'” character. This file has two sample
entries IP1 and IP2.
The format of an entry follows: IPx = IP Address. The value of x is an
enumeration starting at 0 and incrementing by 1 with each additional entry.
NOTE: IP0 is the multicast address.
Adding an Entry
1 Start a new entry after the last entry in your list.
On a new line type:
IP<next number in sequence> = <IP Address of StorView Server>
Example: IP1 = 45.89.6.88
If you skip a number in the enumeration sequence the IP address will not be
used because the Server will stop scanning after the first out of sequence
number.
Modifying the IP.db File 31
Chapter 3 - Getting Started
32
Storview.book Page 32 Tuesday, September 23, 2003 5:11 PM
NOTE: Since IP1 and IP2 are comment lines, they are not included in the
sequence. The next valid entry would be IP1 followed by IP2
followed by IP3 etc.
2 Save the file.
3 Click the Rescan button.
Deleting an Entry
1 Locate the entry you wish to remove.
2 Select the line and delete it.
NOTE: IP0 is the multicast address, do not delete this entry.
3 Re-number any following entries so the sequence remains consistent and
correct.
Example: Suppose you want to delete IP2 in the following sequence:
IP0 = 225.0.0.225
IP1 = 45.5.7.88
IP2 = 45.5.7.89
IP3 = 45.5.7.90
After you delete IP2 the sequence would be:
IP0 = 225.0.0.225
IP1 = 45.5.7.88
IP2 = 45.5.7.90
4 Save the file.
5 Click the Rescan button.
Altering an Entry
1 Find the entry you wish to modify.
2 Make corrections as needed.
The MulticastPort and IP0 entry can be changed, but if you wish for it to
communicate with the other StorView Server, all Servers must have like
settings, that is the MulticastPort and IP0 entries must be the same.
3 Save the file.
4 Click the Rescan button.
Deleting an Entry
Chapter 4
Storview.book Page 33 Tuesday, September 23, 2003 5:11 PM
Disk Arrays
Configuring a RAID system requires some planning to ensure that you define the
correct RAID level and array options. It may be helpful to refer to the “Topologies
and Operating Modes” chapter in the imageRAID User’s Guide for specific
information on supported topologies and LUN information.
This chapter will step you through the process to configure and manage your
disk arrays. After you have created the arrays you will be directed to the next
chapter for the procedures to define and manage your LUNs which are the logical
drive(s) available to the operating system.
This manual assumes you have a basic understanding of RAID concepts.
RAID Levels
The table below describes the drive requirements for each RAID level.
Drive Requirements by RAID Level
RAID Level Minimum No. of Drives Maximum No. of Drives
0 1 16
1 2 16
5 3 16
50 6 16
10 (Mirrored) 4 16
33
Chapter 4 - Disk Arrays
34
Storview.book Page 34 Tuesday, September 23, 2003 5:11 PM
Terminology
The following describes the terminology used when creating and managing array’s.
Term Description
Array A group of disk drives that are combined together to create a single large storage area. Up to 64 arrays are supported, each containing up to 16 drives per array. There is no capacity limit for the arrays.
Backoff Percent In order to allow drives from a different family or manufacturer to be used as a replacement for a drive in an array, it is recommended that a small percentage of the drive’s capacity be reserved when creating the array. This is user selectable, from 0 to 10 percent. This is sometimes known as Reserved Capacity.
Cache Flush Array This is the array that is used to automatically flush cache data in the situation where power has failed to some of the drives.
Chunk Size This is the amount of data that is written on a single drive before the controller moves to the next drive in the stripe.
Initialization RAID 5/50 arrays must have consistent parity before they can be used to protect data. Initialization writes a known pattern to all drives in the array. If the user chooses not to initialize an array, this is known as a “trusted array” and any drive failure will result in data corruption. It is possible to later perform a parity rewrite, which recalculates the parity based on the current data, thus ensuring the data and parity are consistent.
RAID Level 0 RAID 0 is defined as disk striping where data is striped or spread across one or more drives in parallel. RAID 0 is ideal for environments in which performance (read and write) is more important than fault tolerance or you need the maximum amount of available drive capacity in one volume. Drive parallelism increases throughput because all disks in the stripe set work together on every I/O operation. For greatest efficiency, all drives in the stripe set must be the same capacity. Because all drives are used in every operation, RAID 0 allows for single-threaded I/O only (i.e., one I/O operation at a time). Environments with many small simultaneous transactions (e.g., order entry systems) will not get the best possible throughput.
RAID Level 1 RAID 1 is defined as disk mirroring where one drive is an exact copy of the other. RAID 1 is useful for building a fault-tolerant system or data volume, providing excellent availability without sacrificing performance. However, you lose 50 percent of the assigned disk capacity. Read performance is somewhat higher than write performance.
Terminology
Chapter 4 - Disk Arrays
Storview.book Page 35 Tuesday, September 23, 2003 5:11 PM
Optimization and Drive Selection for RAID 5 Arrays
Typical RAID 5 implementations require a number of steps to write the data to
the drives. In order to optimize your system performance based on the type of
writes you expect in your operation, we have provided detailed information on
optimizing the performance using full strip write operations in an appendix.
If you intend to setup a RAID 5 array and wish to consider optimum
performance, you will need to consider the number of data drives, parity drives,
chunk size, and therefore should review the information provided in “Optimizing
RAID 5 Write Performance” on page 145. Additional information is provided at
the appropriate step during configuration.
RAID Level 5 RAID 5 is defined as disk striping with parity where the parity data is distributed across all drives in the volume. Normal data and parity data are written to drives in the stripe set in a round-robin algorithm. RAID 5 is multi-threaded for both reads and writes because both normal data and parity data are distributed round-robin. This is one reason why RAID 5 offers better overall performance in server applications. Random I/O benefits more from RAID 5 than does sequential I/O, and writes take a performance hit because of the parity calculations. RAID 5 is ideal for database applications.
RAID Level 10 RAID 10 is defined as mirrored stripe sets or also known as RAID 0+1. You can build RAID 10 either directly through the RAID controller (depending on the controller) or by combining software mirroring and controller striping, or vice versa (called RAID 01).
RAID Level 50 This RAID level is a combination of RAID level 5 and RAID level 0. Individual smaller RAID 5 arrays are striped, to give a single RAID 50 array. This can increase the performance by allowing the controller to more efficiently cluster commands together. Fault tolerance is also increased, as one drive can fail in each individual array.
Stripe The process of separating data for storage on more than one disk. For example, bit striping stores bits 0 and 4 of all bytes on disk 1, bits 1 and 5 on disk 2, etc.
Stripe Size This is the number of data drives multiplied by the chunk size.
Sub-array In RAID 50 applications, this is the name given to the individual RAID 5 arrays that are striped together. Each sub-array has one parity drive.
Optimization and Drive Selection for RAID 5 Arrays 35
Chapter 4 - Disk Arrays
36
Storview.book Page 36 Tuesday, September 23, 2003 5:11 PM
Creating Arrays
Configuring the arrays involves a few steps from one panel. From the Create
Array screen drives are selected, and the parameters of the array are established
through drop-down menu selections or check boxes. The settings information
that defines all the arrays, spares, and controller specific parameters is contained
in a configuration file.
This configuration file is stored on all disk drives that are attached to the
controller(s) and are members of the array (regardless if the drives are in multiple
enclosures). This makes it possible to remove and replace the controllers or
drives without requiring any configuration changes.
No changes are made to the configuration until the current process is saved, so it
is possible to quit at any time without affecting the current configuration. After
making changes to your configuration, be sure to make a backup copy. See
“Saving, Restoring and Clearing the Configuration” on page 54. This ability of
making a backup copy of the configuration allows you to quickly recover from a
damaged configuration that was not self healing, and restore everything to the
point in time when the configuration was saved which preserves the array’s,
LUNs, LUN mapping and the data. A damaged configuration could result in loss
of data.
To create an array follow the procedures listed below:
1 Locate the Configuration section and next to Arrays click the Create button.
Main Screen
Creating Arrays
Chapter 4 - Disk Arrays
Storview.book Page 37 Tuesday, September 23, 2003 5:11 PM
2 Select the drives you wish to include in the array. You can use the <Ctrl> or
<Shift> keys to select multiple drives at one time.
As you select drives, the projected size of the array is displayed in the upper
right corner of the window.
You will notice numbers next to each item. These are the suggested
sequential order to follow when creating an array.
3 Enter a name for your array. You may use up to 32 characters (ASCII).
NOTE: Passing the mouse pointer over components of the Create Array
screen will display detailed information in the Notes box.
Create Array Screen
4 Select the RAID level for the array.
Click the pull-down menu and choose from the available levels. These are
based on the number of drives selected, refer to the “Drive Requirements”
table at the beginning of this chapter.
a (For RAID 50 arrays.) Create the sub-arrays. From the pull-down menu
select the number of sub-arrays you wish to create for this array.
If you choose more sub-arrays than allowed for the number of drives
selected, when you click the “Create” button you will get a warning to
correct the situation. Choose a smaller number of sub-arrays.
Creating Arrays 37
Chapter 4 - Disk Arrays
38
Storview.book Page 38 Tuesday, September 23, 2003 5:11 PM
5 Enter the desired chunk size. Click the pull-down menu and choose from the
available values.
The available chunk sizes are 64K, 128K, and 256K. This is the amount of
data that is written on a single drive before the controller moves to the next
drive in the stripe.
To achieve optimum RAID 5 write performance you should consider setting
the chunk size based on the specified number of drives for a full stripe write
when configuring RAID 5/50 arrays. Refer to “Optimizing RAID 5 Write
Performance” on page 145 for detailed information.
For RAID 5/50, the primary aim of setting a chunk size is to try to set a stripe
size that allows for full stripe writes. The stripe size is determined by the
number of data drives multiplied by the chunk size, (8 data drives * 64K
chunk size = 512 stripe size).
For maximum performance with RAID 5/50 arrays, you want to do as many
full stripe writes as possible. Typically, Windows NT/2000/2003 accesses at
64K, therefore a stripe size of up to 1 MB would mean the controller has to
cluster 16 commands to perform a full stripe write (sometimes 17 because of
alignment). If you were to use a larger stripe size, then you run the risk of
not being able to cluster sufficiently for the application.
In cases where you are performing larger writes to the controller, then you
could go up to 2 MB for a stripe size, since you have more data to cluster.
Never exceed 2 MB for a stripe size, since the controller cannot cluster over
this size.
It is recommended to keep the stripe size to 1 MB or less for general use,
perhaps increasing it for specific applications. This stripe size is actually the
substripe size in RAID 50 cases. A 4+1 array (4 data and 1 parity drives) with
a 256K chunk has a 1 MB stripe size, as does an 8+1 array with 128K stripe
size, and an 8+2 RAID 50 array with 256K chunk size.
Although 8+1 gives an even stripe size, this does not really matter for an
operating system (OS) that writes in significantly smaller chunks. So, 8+1,
10+1, or 11+1 with a chunk size of 64K would be fine for an OS that does
64K writes. If the operating system can do much larger writes, then you may
want to increase the chunk size. With writeback cache enabled, the
controller can cache data and perform full stripe writes.
Creating Arrays
Chapter 4 - Disk Arrays
Storview.book Page 39 Tuesday, September 23, 2003 5:11 PM
For a single enclosure example - best all around performance:
11+1 with 64K chunk size would yield a 704K stripe (11*64=704)
10+2 with 128K chunk size would yield a 640K stripe (5*128=640)
When using more drives, 14+2 (64K), or 12+3 (128K) should be as good
as 12+4. However, it is recommended that subarray be kept to a
minimum of four data drives.
For most sequential accesses, the difference may not be too noticeable for
different configurations. However, for large block random writes, it can help
if the stripe size is similar to the I/O size. This allows the controller to
perform a partial full stripe write, where it has most of the data for a full
stripe, and can just read some from the drives to complete the stripe.
While Microsoft® Windows NT/Microsoft® Windows® 2000/Microsoft®
Windows® 2003 does 64K accesses, these are not aligned. If the chunk size
is 64K, most accesses crosses a chunk boundary and therefore involves two
read/modify/write commands instead of one. However, because the
controller can cluster, this problem is somewhat offset since the controller
can usually cluster sufficiently to do full stripe writes. If it is completely
random 64K access on Microsoft® Windows NT/Microsoft® Windows®
2000/Microsoft® Windows® 2003, then a 64K chunk is not the best. In this
case 128K or 256K is better to minimize the number of commands that cross
chunk.
Larger chunk sizes should be used if the operating system is writing large
blocks, or with large sequential writes where the controller can cluster
sufficiently. Always keep the stripe size below 2 MB.
6 Select to Initialize the array.
You must initialize your array before data is written to the array.
The Trust Array function is also used in very special circumstances, refer to
“Trust an Array” on page 60 for more information.
7 Choose the “Back-off Percent” (reserved capacity) for the drives.
This determines how much drive capacity to reserve for future capacity
expansions or replacement drives. This is not applicable to RAID 0 arrays.
The default is 1%.
NOTE: The Writeback Cache and Read-Ahead Cache thresholds work together to
allow fine tuning of the I/O performance.
Creating Arrays 39
Chapter 4 - Disk Arrays
40
Storview.book Page 40 Tuesday, September 23, 2003 5:11 PM
8 Set the Read-Ahead Cache threshold.
The choices are automatic, disabled, and four pre-determined sizes. Select
Automatic, which is the recommended setting and the default. This allows
the controller to determine the optimum setting. Disabled will turn off the
Read-Ahead Cache. Choose one of the pre-determined sizes to optimize the
read performance based on your data patterns.
The Read-Ahead function improves the data retrieval performance by
allowing the controller to read into cache a full stripe of data at one time,
which greatly improves the cache hits. For smaller transfers the Read-Ahead
algorithm can improve performance. If, for example, the stripe size is 256KB
(chunk size multiplied by the number of data drives) and the host request
64KB of data, when Read-Ahead is enabled the controller will read in
advance a full 256KB. When the host request the next 64KB block, the data
will already be in the cache. Depending on the data patterns for your
application, disabling the Read-Ahead Cache can help load balance the reads
and write operations, which can increase performance.
9 Set the Writeback Cache options.
Click the pull-down menu to select from Disabled, or choose one of the
pre-determined cache threshold sizes (1MB, 2MB, 4MB, 8MB, 16MB, 32MB,
64MB, 128MB, 256MB or 512MB). (Refer to “Configuring Array Writeback
Cache” on page 42.)
There are three additional options to an active Write Back Cache: Disable if a
partner controller fails or is missing, Disable if a controller battery fails,
and/or Disable if the array is in a critical state, (e.g., during a rebuild). Enable
the options for your application. For maximum data protection, it is
recommended to enable all three options.
The Writeback Cache is used to optimize the write performance specific to
your data patterns. In general, larger cache sizes will increase the write
performance but may lower simultaneous read performance. The
recommended size is 16 MB. The strategy of write operations results in a
completion signal being sent to the host operating system as soon as the
cache receives the data to be written. The disk drives will receive the data at
a more appropriate time in order to increase controller performance.
Creating Arrays
Chapter 4 - Disk Arrays
Storview.book Page 41 Tuesday, September 23, 2003 5:11 PM
10 Click the Create Array button to complete this operation.
11 You will see a confirmation that the array was successfully created, click the
Close button.
12 Click the Close button at the bottom of the Create Array window.
While monitoring the array initialization, you will note that under the Array name
a progress bar appears displaying the percent complete for the initialization. Also,
in the Enclosure front view, the disk drives being initialized display an animated
icon during the initialization.
Monitoring the Initialization Process at the Main Screen
You can stop the Initialization process if you wish by clicking on the Stop link
located to the right of the progress bar. Stopping the initialization will cause your
array to be trusted.
NOTE: You can only initialize one array at a time, therefore during an
initialization you will not be able to initialize another array until this one
is complete.
Creating Arrays 41
Chapter 4 - Disk Arrays
42
Storview.book Page 42 Tuesday, September 23, 2003 5:11 PM
Configuring Array Writeback Cache
In a writeback cache operation, data is sent to the controller from the host and
before actually sending the data to the drives, the controller immediately
responds to the host confirming the data was received and written to the disk
(even though the data may have not been written to the disk). The host may
then send more data. This can significantly increase performance for host
systems that only send a low number of commands at a time. The controller
caches the data, and if more sequential data is sent from the host, it can cluster
the writes together to increase performance further. If sufficient data is sent to fill
a stripe in RAID 5/50 configurations, the controller can perform a Full Stripe
Write, which significantly reduces the write overhead associated with RAID 5/50.
Disabling writeback cache ensures that the data is sent to the drives before status
is returned to the host. With writeback cache enabled, if a short term power
failure occurs, the battery back-up unit provides adequate power to ensure that
cache is written to disk when the power is restored. In duplex operations, the
cache is mirrored to both controllers which provides further redundancy in the
event of a single controller failure.
Mirrored cache is designed for absolute data integrity. The cache in each
controller contains both primary cached data for the disk groups it owns, and a
copy of the primary data of the other controllers. Mirrored cache ensures that two
copies of cache exist on both controllers before confirming to the operating
system that the write has completed.
Refer to the imageRAID User’s Guide for battery hold-up times for data retention.
Normally, write-intensive operations will benefit from the higher performance
when writeback cache is enabled on that array. Read-intensive operations, such
as a streaming server, may not benefit from writeback cache.
Configuring Array Writeback Cache
Chapter 4 - Disk Arrays
Storview.book Page 43 Tuesday, September 23, 2003 5:11 PM
Deleting an Array
This operation will remove or delete an array. Deleting an array will delete all
data on the LUNs and the LUNs associated with that array, thus causing data loss.
Be sure you have a back up of the data before proceeding.
1 Locate the Configuration section and next to the Arrays section, click the
“Array_Name” you wish to delete.
Main Screen
2 In the Array screen, click the Delete Array button.
Array Screen
Deleting an Array 43
Chapter 4 - Disk Arrays
44
Storview.book Page 44 Tuesday, September 23, 2003 5:11 PM
3 A confirmation screen will appear, type your Password and click the Go
button.
Confirmation Screen
If the wrong password is entered, you will be prompted and the array will
not be deleted.
If the password is correct, you will see the following screen.
4 Once the array has been successfully deleted, click the Close button.
Confirmation Screen
Deleting an Array
Chapter 4 - Disk Arrays
Storview.book Page 45 Tuesday, September 23, 2003 5:11 PM
Modifying Arrays
Once the array has been created and is online you can make changes to the
following:
� Change the name of the array.
� Change the Read-Ahead and Writeback cache parameters.
NOTE: To restore the original settings click the Restore button. This option is only
effective if you have not clicked the Apply button. Once you have applied
the changes, you cannot restore the settings.
To change the name of the array:
Type a new name for the array in the Name field and click the Apply button.
Array Screen
NOTE: If the array was trusted or never initialized, you can initialize the array
from this panel by clicking the “Initialize” button. The button will not be
active if the array is already initialized
Modifying Arrays 45
Chapter 4 - Disk Arrays
46
Storview.book Page 46 Tuesday, September 23, 2003 5:11 PM
Initializing Array
Initializing an array clears all the data from the drives and writes data chunks to
the drives. To ensure the validity of the data stored on the arrays you must
initialize the array. For whatever reason, you may wish to initialize the array at a
later time. You can stop the automatic initialization from the Main screen by
clicking the Stop link on the progress bar. A button is provided in the Array
Information screen to manually start an initialization.
1 Locate and click on the array name you wish to initialize. This will open the
Array screen.
Main Screen
2 From the Array screen, click the Initialize button.
Array Screen
Initializing Array
Chapter 4 - Disk Arrays
Storview.book Page 47 Tuesday, September 23, 2003 5:11 PM
3 You will be prompted to enter your password to confirm you wish to
initialize the array. Type your password and click Go. A confirmation appears
indicating the success of the operation, click the Close button.
4 Click the Close button on the Array screen.
From the Main screen you can monitor the initialization.
Monitoring the Initialization Progress
Placing the mouse pointer over the progress bar will display the percent
complete for the initialization progress in a pop-up window. The drive
member icons of this array will change to an animated icon indicating the
array is initializing.
You can stop the Initialization process if you wish by clicking on the Stop link
located to the right of the progress bar.
Once the initialization is complete you are ready to create the disk LUNs.
NOTE: You can only initialize one array at a time, therefore during an
initialization you will not be able to initialize another array until this one
is complete.
Initializing Array 47
Chapter 4 - Disk Arrays
48
Storview.book Page 48 Tuesday, September 23, 2003 5:11 PM
Verify Parity
If a RAID 5/50 array experiences a situation where both controllers are replaced
after the array is powered off with write operations in progress or you see parity
errors reported in the event log, it may be necessary to verify and correct the
parity data on the array. It is also desirable to perform this check as a normal
maintenance procedure from time to time.
1 Locate and click on the array name you wish to verify parity data on. This
will open the Array screen.
Main Screen
2 From the Array screen, click the Verify Parity button.
Array Screen
Verify Parity
Chapter 4 - Disk Arrays
Storview.book Page 49 Tuesday, September 23, 2003 5:11 PM
3 Select a verify option from the list presented.
Verify Options Screen
The table below provides a description of each option:
During the verification, the drive members icons in the front enclosure view of
that array will display an animated icon indicating a verification is in progress.
Also, adjacent to the array name in the Main screen, a progress bar will indicate
the percent complete. When you place the mouse pointer over the progress bar a
pop-up will display the value of the percent complete.
Option Description
Check Parity This option reads all the data and parity, calculates the XOR of the data, and compares it to the parity. If there is an error, it is displayed in the event log.
Rewrite Parity This option reads all the data, calculates the XOR of the data, and writes this out as the new parity. This is the fastest to complete, since it does not have the overhead of a comparison.
Check and Rewrite Parity This option reads all the data and parity, calculates the XOR of the data, and compares it to the parity. Then, if there is a discrepancy, it writes this out as the new parity. This is the slowest to complete, since it has the overhead of a comparison as well as a rewrite.
Verify Parity 49
Chapter 4 - Disk Arrays
50
Storview.book Page 50 Tuesday, September 23, 2003 5:11 PM
Monitoring Progress of Parity Verification
You can stop the Verification process if you wish by clicking on the Stop link
located to the right of the progress bar.
Identifying Drive Members
Should the need arise, you can quickly identify which drives in the enclosure are
members of a specific array. (Refer to the illustration on the following page.)
Located on the right side of an Array name is an icon (Drive Identity icon), whose
appearance is like an arrow pointing to the lower left corner. This is used to turn
on the identify function.
Clicking on the Drive Identity icon will cause all drive members of that array in
the graphical representation of the enclosure front view to have the “Drive
Identity (arrow)” icon displayed on those drives.
Identifying Drive Members
Chapter 4 - Disk Arrays
Storview.book Page 51 Tuesday, September 23, 2003 5:11 PM
Identifying Member Drives Screen
You can also identify specific drives in an array by flashing its Drive Status LED,
see “Locate Drive” on page 108.
Expanding an Array
The Expand Array feature is used to increase the capacity of an existing array. An
array can be expanded to a maximum of 16 drives. Only one array can be
expanded at a time, and no configuration changes can be made to the arrays,
disk LUNs, or LUN Mapping while an expansion operation is in progress.
During the expansion process, data is re-striped across a new set of data drives,
and new parity is calculated and written if necessary for fault tolerant arrays. If the
array is a fault tolerant array, such as RAID level 1, 10, 5, or 50, it will remain fault
tolerant during the expansion. Should a disk drive fail in a fault tolerant array
during the expansion, the expand operation will continue as normal at which time
it will flag the drive as failed and use the data and parity information to create the
new data and parity stripe. After the expansion is complete, and if you had a hot
spare designated, the automatic rebuild operation will commence bringing the
non-fault tolerant expanded array back to a fault tolerant condition.
Drive Identity Icon
Member Drives withDrive Identity icon
displayed.
Expanding an Array 51
Chapter 4 - Disk Arrays
52
Storview.book Page 52 Tuesday, September 23, 2003 5:11 PM
If a second drive failure occurs during expansion, that condition is not recoverable
and you will have a total loss of data. You may wish to consider backing up the
data prior to expanding an array. Although there is a level of protection during
this operation without the backup, the best insurance is a valid backup.
NOTE: After the array expansion process has completed, if you are expanding for
the purposes of new drive space you will need to create the appropriate
LUN(s) and define them in your operating system. However, if the
expansion is intended to increase the existing LUN capacity you will need
to perform a LUN Expansion. Afterwards a third-party volume/partition
software product will be necessary to manipulate any existing partitions.
1 Locate and click on the array name you wish to expand. This will open the
Array screen.
Main Screen
2 From the Array screen, click the Expand Array tab.
(Refer to the illustration on the following page.)
3 Following the sequenced steps, click the Array Expansion Type pull-down
menu, choose the type of expansion applicable to your array.
4 Select the drives that will be used to expand the array.
Expanding an Array
Chapter 4 - Disk Arrays
Storview.book Page 53 Tuesday, September 23, 2003 5:11 PM
Array Screen - Expand Array Tab Selected
5 Verify the changes you are about to make by examining the “Before
Expansion” and “After Expansion” analysis.
6 If your settings are correct, click the Expand button.
7 You will be prompted to confirm the Expand operation. Type your password
and click the GO button.
Expand Array Confirmation Screen
8 Once the expansion begins click the Close button on the Array window. You
can monitor the status of the expansion from the Main screen.
Expanding an Array 53
Chapter 4 - Disk Arrays
54
Storview.book Page 54 Tuesday, September 23, 2003 5:11 PM
Saving, Restoring and Clearing the Configuration
The option of saving and restoring the configuration information is a very
valuable feature of StorView. When you create arrays, create disk LUNs, establish
hot spare drives, define LUN Mapping, and change the parameters of specific
settings a file is written that contains all this important information to all the
configured disk drives. StorView has the ability to capture that file and enable
you to save it to an external file. This can be a figurative lifesaver should the
situation occur where a configuration has become corrupt or damaged. With this
ability to reload the settings from a file you are instantly able to re-establish your
settings, otherwise you would be required to rely on your memory or notes you
may have taken when you set up the system which may not be complete. If you
cannot restore the configuration you will not be able to restore access to the data
and it will be lost. This is also demonstrated in the discussion on Trusting arrays.
Because some day to day changes to your system will cause changes to the
configuration file, the configuration should be periodically updated. An example
of a change would be a drive failure, a hot spare drive automatically replacing
the failed drive and the data rebuilding on the new drive with new parity. That
indicates a significant change in the configuration because the failed drive
member has been removed and a new drive has taken its place. Restoring a
configuration with a missing drive would not be possible and would cause the
existing data to be lost.
Therefore it is vitally important that when configuration changes occur, you save
the configuration again with a new file name.
The user controls for saving and restoring the configuration are located on the
Main screen adjacent to the labeled “Configuration” section. The controls are a
Disk icon for saving and a Folder icon for restoring.
Refer to “Saving the Configuration” on page 55 and “Restoring the Configuration”
on page 57 for specific instructions.
Saving, Restoring and Clearing the Configuration
Chapter 4 - Disk Arrays
Storview.book Page 55 Tuesday, September 23, 2003 5:11 PM
Saving the Configuration
This option allows you to save your configuration information into an external
file and to be able to restore the configuration.
1 From the Main screen and adjacent to the Configuration section, click the
Disk icon to save the configuration file.
Main Screen
2 Click the Download button to continue with saving the configuration file, or
click the Close button to cancel.
Save Configuration Download Screen
3 You are presented with the browser’s standard “File Download” screen. Click
the Save button to continue, or Cancel to quit.
Saving the Configuration 55
Chapter 4 - Disk Arrays
56
Storview.book Page 56 Tuesday, September 23, 2003 5:11 PM
Save Configuration File Screen
4 Next, you are presented with the “Save As” screen. If you wish to use the
default file name, select the directory and click the Save button, otherwise
enter the name you wish to use and specify the directory, and then click
Save. Click the Cancel button to exit.
File Name Screen
5 After successful download, you will see a confirmation window. Click the
Close button.
Saving the Configuration
Chapter 4 - Disk Arrays
Storview.book Page 57 Tuesday, September 23, 2003 5:11 PM
Restoring the Configuration
Before you restore the configuration, be sure to read the information on “Saving,
Restoring and Clearing the Configuration” on page 54.
1 From the Main screen and adjacent to the Configuration section, click the
Folder icon to restore the configuration file.
Main Screen
2 The File upload screen appears, click the Browse button.
Restore Configuration Upload Screen
You are presented with the browser’s “Choose File” screen. Select the
appropriate file and click the Open button to continue, or Cancel to quit.
Restoring the Configuration 57
Chapter 4 - Disk Arrays
58
Storview.book Page 58 Tuesday, September 23, 2003 5:11 PM
Restore Choose File Screen
3 Click the Upload button to continue to restore the configuration, or click the
Cancel button to quit.
Restore Configuration Upload Screen
4 After you have completed the configuration restoration, and if you had any
RAID 5/50 arrays defined click the Array link on the Main screen for each
RAID 5/50 array. Perform a Verify Parity operation before using those arrays.
This will ensure that the data and parity data are correct.
Clearing the Configuration
Some conditions or situations may call for you to clear the entire configuration.
This process removes all arrays, LUNs, LUN mappings, etc. If there is any data on
the drives, that data be lost when the configuration is cleared.
1 From the Main screen and adjacent to the Configuration section, click the
Trash icon to clear the configuration file.
Clearing the Configuration
Chapter 4 - Disk Arrays
Storview.book Page 59 Tuesday, September 23, 2003 5:11 PM
Main Screen
2 A pop-up screen appears, type your password and click the Go button.
Clear Configuration Confirmation Pop-up Screen
You will receive a confirmation of the operation. Click the Close button.
Notification
To ensure that you are made aware of changes to the configuration, you can
set up an Email account that sends you a message when an event of this type
has occurred. This may serve as a notification that you should save the
configuration file again. Refer to “Configuring for Email Notices” on page 23.
Notification 59
Chapter 4 - Disk Arrays
60
Storview.book Page 60 Tuesday, September 23, 2003 5:11 PM
Trust an Array
This option is used to make an array ready to use for testing purposes. Trusting
the array makes it available immediately rather than the time involved to fully
initialize it. You should be aware that the parity data will be inconsistent when the
array is trusted. Using a trusted array in a live data environment may result in data
corruption and potential data loss.
1 Locate the Configuration section and next to Arrays click the “Create” button.
Create Array Screen
2 At Item 6, use the pull-down menu and select “Trust.”
3 Click the “Create Array” button to complete this operation.
Trust an Array
Chapter 5
Storview.book Page 61 Tuesday, September 23, 2003 5:11 PM
Spares
The imageRAID Controller supports hot spare drives. The process of configuring
some arrays includes assigning drives for global hot spares and/or dedicated hot
spares. In the event of a drive failure, the controller will use either a global hot
spare or if defined, a dedicated hot spare for that array, to replace the failed drive.
Global spares are not assigned to a specific array and when created can be used by
any array as the replacement member drive. A dedicated spare is assigned to a
specific array and can only be used by that array as the replacement drive member.
Assigning a Global Hot Spare
1 From the Main screen, select a disk drive that you wish to make a global hot
spare from those drives with icons indicating “Available” in the enclosure
front view by clicking the drives’ icon.
Main Screen
61
Chapter 5 - Spares
62
Storview.book Page 62 Tuesday, September 23, 2003 5:11 PM
NOTE: There must be at least one drive available and online to be assigned
as a hot spare.
2 In the Drive window, click the Make Spare button.
Drive Screen
3 A small window will appear, click Make Global Hot Spare.
Make Spare Screen
4 A progress window will open indicating the status of the process. Once
completed, click the Close button.
Assigning a Global Hot Spare
Chapter 5 - Spares
Storview.book Page 63 Tuesday, September 23, 2003 5:11 PM
Assigning a Dedicated Hot Spare
1 From the Main screen, select a disk drive that you wish to make a dedicated
hot spare from those drives with icons indicating “Available” in the enclosure
front view by clicking the drives’ icon.
Main Screen
NOTE: There must be at least one drive online and available to be assigned
as a hot spare.
2 In the Drive window, click the Make Spare button.
Drive Screen
Assigning a Dedicated Hot Spare 63
Chapter 5 - Spares
64
Storview.book Page 64 Tuesday, September 23, 2003 5:11 PM
3 A small window will appear, click the pull-down menu and select the array
to which you wish to assign the dedicated spare.
Dedicated Spare Screen
4 A progress window will open indicating the status of the operation. Once
completed, click the Close button.
NOTE: An additional spare option, “Auto Hot Spare” is available and can be
accessed from the Controller panel – Parameters tab. Refer to “Controller
Parameters” on page 98 for more details.
Assigning a Dedicated Hot Spare
Chapter 5 - Spares
Storview.book Page 65 Tuesday, September 23, 2003 5:11 PM
Removing a Hot Spare
This operation will remove the designation of the disk drive as a global or
dedicated spare. The drive will be online and available for other uses afterwards.
1 From the Main screen, click on a disk drive labeled “Dedicated” or “Hot
Spare” in the enclosure front view that you wish to remove as a global or
dedicated hot spare.
The drive window will open.
Drive Screen
2 Click the Remove Spare button.
3 A progress window will open indicating the status of the operation. Once
complete, click the Close button.
Removing a Hot Spare 65
Chapter 5 - Spares
66
Storview.book Page 66 Tuesday, September 23, 2003 5:11 PM
Auto Hot Spare
The Auto Hot Spare option when enabled, will automatically mark a replacement
disk drive as a dedicated hot spare drive. When the replacement drive is inserted
in place of the failed drive, a rebuild operation will begin automatically using the
new drive. This option is useful when a global or dedicated hot spare drive is not
assigned and you have a fault tolerant array that experiences a drive failure.
Instead of inserting a replacement drive, opening the Drive panel for the
replacement disk drive and assigning it as a hot spare, you simply remove the
failed drive and insert the replacement drive.
1 To enable this feature, click the Controller icon on the Main screen and select
the Parameters tab.
2 Place the mouse pointer on the check box next to the Auto Hot Spare
parameter and click to place a check mark enabling the feature.
3 Click the Apply button, and click the Close button on the confirmation
window when it appears. Then click the Close button on the Controller
screen.
Controller Screen - Parameters Tab Selected
Auto Hot Spare
Chapter 6
Storview.book Page 67 Tuesday, September 23, 2003 5:11 PM
LUNs
A LUN is defined as a region or combination of regions of storage that can be
made available to one or more host systems. Up to 512 LUNs are supported. After
an array has been created, this region is first marked as unassigned. One or more
LUNs can be created in this region or existing LUNs can be expanded using this
region. A LUN can be created or expanded in 1 GB increments with a maximum
total size per LUN of 2,198 GBs. This corresponds to the 32 bit addressing
limitation of 2 TB.
NOTE: For Microsoft® Windows NT there is a limitation of 231 LUNs. A hot fix is
available, refer to Microsoft® Knowledge Base Article - 245637.
Terminology
The following table describes the terminology relating to LUNs.
Term Description
LUN Segmentation Any LUN can be expanded into any free region, so it is possible to easily add capacity at any time. There is no requirement that any additional space be contiguous. LUN Segmentation is completely transparent to the host systems.
LUN Availability To accommodate hosts with multiple ports and multiple host systems, it is possible to restrict a LUN’s availability to a particular controller or port. Access can be enabled or disabled for each host port of each controller.
67
Chapter 6 - LUNs
68
Storview.book Page 68 Tuesday, September 23, 2003 5:11 PM
Viewing Unassigned Free Space
Prior to assigning a LUN, you may wish to review the unassigned free space. This
will help you to identify the unused regions or segments that can be used for
LUN creation. Normally with a first time configuration this step is not necessary
since all of the space is unassigned.
1 From the Main screen in the LUNs section, click on the Create button.
Main Screen
The available free space is displayed in the “Select which Array(s) to Use”
scrollable window.
2 Click the Close button after you have reviewed the available free space
segments.
Mapped LUN Number Each LUN is presented to the host systems with a unique LUN Number. In certain cases (such as after deleting another LUN) it may be desirable to change the number that a LUN is presented as. This can be done at any time, bearing in mind that any attached host systems may need to be rebooted or re configured to maintain access.
Unassigned Free Space The controller keeps a map of all the space that is not assigned to any LUN. This space is available for LUN creation or expansion. Each unassigned region is individually listed.
Viewing Unassigned Free Space
Chapter 6 - LUNs
Storview.book Page 69 Tuesday, September 23, 2003 5:11 PM
Create LUN Screen
Viewing Unassigned Free Space 69
Chapter 6 - LUNs
70
Storview.book Page 70 Tuesday, September 23, 2003 5:11 PM
Creating a LUN
To complete the process of configuring your arrays, you will need to create and
assign one or more LUNs. This presents the logical drive to the host operating
system. Refer to the example below.
Sample Array and LUN Layout
1 From the Main screen in the LUNs section, click on the Create button.
Main Screen
2 Select the segment or segments you wish to use for your LUN from the
scrollable “Select Which Array(s) to use” window.
You may hold the <Shift> or <Ctrl> key down to make multiple selections.
Array 1RAID 50
2400 GB
LUN 3:0 700 GB
LUN 2:0 400 GB
LUN 1:0 1000 GB
LUN 0:0 300 GB
Creating a LUN
Chapter 6 - LUNs
Storview.book Page 71 Tuesday, September 23, 2003 5:11 PM
Create LUN Screen
3 Type the name for your LUN, you may use up to 32 characters.
4 Enter the size in GB’s for the LUN Capacity.
The maximum of the segments you have selected are displayed to the right
of the size block field. You may use all or some of the capacity for this LUN.
The maximum capacity for any LUN is 2198 GBs (32-bit addressing limit). If
the total amount selected exceeds the limit only the maximum allowable size
is displayed.
Defining the LUN Capacity Screen
Creating a LUN 71
Chapter 6 - LUNs
72
Storview.book Page 72 Tuesday, September 23, 2003 5:11 PM
5 Select the LUN number that the LUN will be presented as. It will default
beginning at LUN 1.
StorView communicates with the controllers through LUN 0. If you are
required to have your disk LUN set to LUN 0 for reasons such as a bootable
array, then you will need to change the Controller LUN found under the
Controller Parameters tab. For more information on Controller LUNs refer to
“Controller Parameters” on page 98 and “Changing the Controller LUN” on
page 104.
6 Select the Controller Ports you wish to make available to the LUN.
If a LUN is to be seen on all controller ports to all host HBAs, then set the
availability (place check marks for both Controller’s Port 0 (C0/C1) and
Controller’s Port 1 (C0/C1)). Otherwise, select the Controller’s port you wish
the LUN to be available on.
NOTE: If you intend to perform a LUN Mapping, a LUN Mapping will
override any availability settings you make here.
It is important to understand the cabling configuration topology you selected
during your hardware setup. If for example, you have a host connected to
the left Host I/O card Port 0 and another host connected to the right Host I/O
card Port 0, and you select to make the LUN available to Controller’s Port 1,
no LUN will be seen by either host because you have set it to be seen only
on a host connection to C0P1 and C1P1, when in fact it should have been
Controller’s Port 0 indicating C0P0 and C1P0. Refer to “Tips on Setting LUN
Availability” on page 73.
7 Click the Create button to create the LUN.
You will see a progress display.
8 Once it has completed, you can continue to create more LUNs or exit by
clicking the Close button.
Creating a LUN
Chapter 6 - LUNs
Storview.book Page 73 Tuesday, September 23, 2003 5:11 PM
Tips on Setting LUN Availability
The following information will assist you when creating LUNs and setting their
availability for each of the supported imageRAID storage system topologies. You
may wish to have the imageRAID User’s Guide and this manual available for
reference. Locate the topology you configured listed below and on the following
pages, then review the information on its LUN presentation. A notation of “LUN”
appearing in the block indicates one or more LUNs appear available on the port.
imageRAID IRF-1Sxx-xx/IRF-1Dxx-xx (Simplex: Dual Port One Host)
Because of the specific Host I/O card switch settings for this configuration, all
LUNs are visible on all Host Ports, if they are available to either controller port.
� LUN Availability should be set to only one controller port for each LUN and
the user should balance the load between the two controller ports (C0P0 &
C0P1) for best performance.
NOTE: If the LUN Availability is set to both ports the host will see a given
array twice unless it does special processing to detect duplicate paths
to the array, which would result in potential data overwrites. A host
device driver may provide this functionality.
Product Identification
Storage Enclosure Number of Controllers Model of Controller
IRF-JBOD 0 JBOD
IRF-1Sxx-xx 1 imageRAID
IRF-2Sxx-xx 2 imageRAID
IRF-1Dxx-xx 1 imageRAIDXP
IRF-2Dxx-xx 2 imageRAIDXP
LEFT H0Host I/O Card
Controller Ports
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
LUN LUN LUN LUN
LUN LUN LUN LUN
LUN LUN LUN LUN
Tips on Setting LUN Availability 73
Chapter 6 - LUNs
74
Storview.book Page 74 Tuesday, September 23, 2003 5:11 PM
imageRAID IRF-1Sxx-xx/IRF-1Dxx-xx (Simplex: Dual Port One Host with Dual Connection)
The user should balance the load between the two controller ports for best
performance. This can be accomplished using one of two methods.
� LUN Availability can be set to both controller ports and the user can then
map LUNs to the different HBA WWN.
� LUN Availability can be set to one port for each LUN and alternate
controller ports to balance the load.
If setup requires Upstream Failover, LUN Availability should be set to both ports.
A host device driver or third party software which provides upstream failover
functionality will do special processing to detect duplicate paths to array.
imageRAID IRF-1Sxx-xx/IRF-1Dxx-xx (Simplex: Dual Port Multi Host Connection)
When this configuration is set up, you will have the option for dedicated LUNs
for each host, or clustered servers.
� For dedicated LUNs with two host systems, set LUN Availability to the
controller port to which the respective host is attached.
� For dedicated LUNs with more than two host, set LUN Availability to both
ports and the user can use LUN Mapping to a specific HBA WWN to restrict
access between hosts.
� For clustered servers, enable LUN Availability to both ports which will
cause the same LUN to be reported to all attached Hosts.
NOTE: Protected LUN sharing between two host systems is not supported
without third party software which will provide the necessary file
share/file lock capabilities.
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
N/A N/A LUN LUN
LUN LUN N/A N/A
LUN LUN LUN LUN
Host I/O Card
Controller Ports
imageRAID IRF-1Sxx-xx/IRF-1Dxx-xx (Simplex: Dual Port One Host with Dual Connection)
Chapter 6 - LUNs
Storview.book Page 75 Tuesday, September 23, 2003 5:11 PM
imageRAID IRF-1Sxx-xx/IRF-1Dxx-xx (Simplex: Dual Port Dual Host with a Quad Connection)
When this configuration is set up, you will have the option for dedicated LUNs
for each host, or clustered servers.
� Set LUN Availability to both controller ports.
NOTE: Protected LUN sharing between two host systems is not supported
without third party software which will provide the necessary file
share/file lock capabilities.
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored One Host)
When this configuration is set up, the user should balance the load between the
two controller ports for best performance.
� Set LUN Availability to only one controller port for each LUN.
� If LUN Availability is set to both ports the host will see a given array twice
unless it does special processing to detect duplicate paths to the array. This
may result in potential data overwrites. A host device driver may provide
this functionality.
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
N/A N/A LUN LUN
LUN LUN N/A N/A
LUN LUN LUN LUN
Host I/O Card
Controller Ports
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
N/A N/A LUN LUN
LUN LUN N/A N/A
LUN LUN LUN LUN
Host I/O Card
Controller Ports
imageRAID IRF-1Sxx-xx/IRF-1Dxx-xx (Simplex: Dual Port Dual Host with a Quad Connection) 75
Chapter 6 - LUNs
76
Storview.book Page 76 Tuesday, September 23, 2003 5:11 PM
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored One Host Dual Connection)
When this configuration is set up, the user should balance the load between the
two controller ports for best performance. This can be accomplished in one of
two ways:
� Set LUN Availability to both controller ports. Use LUN Mapping to restrict
access to different HBA WWNs.
� Set LUN AVailability to one port for each LUN and alternate controller ports
availability between LUNs.
NOTE: Set the LUN Availability and Mapping for Upstream Failover
functionality to both ports. A host device driver or third party
software which provides the upstream failover will do special
processing to detect duplicate paths to the array.
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored Multi Host Connection)
When this configuration is set up, you can choose from dedicated LUNs for each
host, or clustered servers.
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
LUN N/A LUN LUN
LUN LUN N/A LUN
LUN x2 LUN LUN LUN x2
Host I/O Card
Controller Ports
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
N/A N/A LUN LUN
LUN LUN N/A N/A
LUN LUN LUN LUN
Host I/O Card
Controller Ports
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored One Host Dual Connection)
Chapter 6 - LUNs
Storview.book Page 77 Tuesday, September 23, 2003 5:11 PM
� For two host systems with dedicated LUNs, set LUN Availability to the
controller port to which the respective host is attached.
� For more than two host systems with dedicated LUNs, set the LUN
Availability to both ports and the user can use LUN Mapping to a specific
HBA WWN to restrict access between hosts.
� For clustered servers set the LUN Availability to both ports. This will cause
the same LUN to be reported to all attached hosts.
NOTE: Protected LUN sharing between two host systems is not supported
without third party software which will provide the necessary file
share/file lock capabilities.
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored Dual Host with Quad Connections)
When this configuration is set up, you are creating a system level fault-tolerant,
high-performance shared storage with clustering.
� Set LUN Availability to both controller ports.
NOTE: Protected LUN sharing between two host systems is not supported
without third party software which will provide the necessary file
share/file lock capabilities.
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
N/A N/A LUN LUN
LUN LUN N/A N/A
LUN LUN LUN LUN
Host I/O Card
Controller Ports
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
LUN LUN N/A N/A
N/A N/A LUN LUN
LUN LUN LUN LUN
Host I/O Card
Controller Ports
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored Dual Host with Quad Connections) 77
Chapter 6 - LUNs
78
Storview.book Page 78 Tuesday, September 23, 2003 5:11 PM
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored SAN Single Switch Connection)
When this configuration is set up, you can choose from dedicated LUNs for each
host, or clustered servers.
� For dedicated LUNs, set LUN Availability to only one controller port for
each LUN and the user should balance the load between the two controller
ports for best performance.
� Use LUN Mapping to a specific HBA WWN to restrict access between hosts
attached to the same controller port.
� For clustered servers set the LUN Availability to both ports. This will cause
the same LUN to be reported to all attached hosts.
NOTE: Protected LUN sharing between two host systems is not supported
without third party software which will provide the necessary file
share/file lock capabilities.
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored SAN Dual Switches Connection)
When this configuration is set up, you set the LUN Availability for clustered
servers.
� Set LUN Availability to both controller ports.
NOTE: Protected LUN sharing between two host systems is not supported
without third party software which will provide the necessary file
share/file lock capabilities.
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
N/A N/A LUN LUN
LUN LUN N/A N/A
LUN LUN LUN LUN
Host I/O Card
Controller Ports
LEFT H0
Port 0
Port 1
Ports 0 & 1
LEFT H1 RIGHT H0 RIGHT H1
N/A N/A LUN LUN
LUN LUN N/A N/A
LUN LUN LUN LUN
Host I/O Card
Controller Ports
imageRAID IRF-2Sxx-xx/IRF-2Dxx-xx (Duplex: Multi Port Mirrored SAN Single Switch Connection)
Chapter 6 - LUNs
Storview.book Page 79 Tuesday, September 23, 2003 5:11 PM
Expanding a LUN
Expanding a LUN is a utility that allows you to take an existing LUN and expand
its’ capacity using unused free segment space of an array.
NOTE: After the LUN expansion process has completed you will need to use a
third-party volume/partition software product to manipulate any existing
partitions.
1 From the Main screen in the LUNs section, click on a LUN name that you
wish to expand.
Main Screen
2 Locate the Expand portion of the window (lower half), and follow the
sequenced steps beginning at step 1 where you will choose a free space
segment to be used for the expansion.
3 In the Add Capacity box, enter the amount of the selected region to expand
the LUN. You may use the entire free region space or a portion of it.
4 Click the Expand button.
Expanding a LUN 79
Chapter 6 - LUNs
80
Storview.book Page 80 Tuesday, September 23, 2003 5:11 PM
LUN Screen
5 You will prompted to enter your password to confirm the expansion. Type in
your password and click the Go button.
6 Click the Close button on the LUN screen.
You can monitor the status of the LUN expansion from the Main screen.
Expanding a LUN
Chapter 7
Storview.book Page 81 Tuesday, September 23, 2003 5:11 PM
LUN Mapping
When attaching many host systems in a network environment, it may be
necessary to more precisely control which hosts have access to which LUNs. In
addition to controlling LUN availability on a controller port by port basis, it is also
possible to further restrict access to a specific host system or single adapter in a
host system. Up to 512 LUN Mappings are supported.
NOTE: If you attempt to map a LUN to a Controller LUN, you will receive a
warning prompting you that you will lose communication with this setting.
Terminology
The following table describes the terminology relating to LUNs.
Term Description
Node Name This is an eight byte hexadecimal number, uniquely identifying a single host system. It incorporates the World Wide Name and two additional bytes which are used to specify the format. In a system with multiple FC ports, all adapters will typically use the same Node Name, but unique Port Names.
Port Name This is an eight byte hexadecimal number, uniquely identifying a single host port. It incorporates the World Wide Name and two additional bytes which are used to specify the format and indicate the port number.
Mapping Name A 28 character name that can be used to help identify the host system.
Read/Write Access A host may read and write to the LUN.
Read Only Access A host may only read from a LUN.
Presented As This is the LUN number that a specific LUN responds to when accessed by a host. It is not necessary for this to bear any relation to the LUN number.
81
Chapter 7 - LUN Mapping
82
Storview.book Page 82 Tuesday, September 23, 2003 5:11 PM
Viewing Hosts
In the LUN Mapping section of the Main screen, a list of the specific host HBA
ports will appear. They will be identified either by the WWN or a plain language
name that you defined. Clicking on one of those HBA ports will open the LUN
Mapping screen and display the specific mapping configuration for that HBA
port.
The list displayed in this section can include a list of hosts that are logged into
the controller and a list of hosts from previous mappings that are not logged into
the controller.
These list of hosts that exists from previous mappings will appear even if a LUN
was mapped to a host but is no longer online.
Main Screen
You may wish to create a table of the specific host HBA’s with their WWNs and
each HBA’s port WWN, as well as their associated logical names. This will
become a valuable reference map when you begin performing the LUN Mapping.
Viewing Hosts
Chapter 7 - LUN Mapping
Storview.book Page 83 Tuesday, September 23, 2003 5:11 PM
Viewing LUN Mappings
Prior to performing LUN Mapping, you may wish to review the current mappings,
if any exists. Normally with a first time configuration this is not necessary since
there will be no current mappings.
From the Main screen in the LUNs Mapping section, click on the WWN/Port
name listed under “LUN Mapping.”
Main Screen
The LUN Mapping window will open. The illustration below provides an
explanation of each component of the LUN Mapping window.
LUN Mapping Screen
Name of the LUNcreated by the user
(default is LUN x)
Presence of a Check Boxindicates the LUN is mappedto another HBA or HBA Port
LUN number presented to the OS,Not Seen indicates the mapping isdisabled or not mapped to an HBA
Sets the access characteristicsto the LUN
WWN of the Host HBAThe name created by the
user for the HBA Portand appears on the Main
screen (default is the WWN)
Number of LUN in theorder they were created
WWN of the specificHost HBA Port
Option to Map to eitherthe HBA or the HBA Port
This option sets the hostaccess to the controller's ports,either both or a specific port
These are the controller ports,P0 = 0, P1=1, for both controllers,if applicable. For example, "0" isC0P0 and C1P0.
Viewing LUN Mappings 83
Chapter 7 - LUN Mapping
84
Storview.book Page 84 Tuesday, September 23, 2003 5:11 PM
Creating a LUN Mapping
This is where you map your LUNs to HBAs or HBA Ports, and then to either both
controller ports or the individual controller ports. The controller uses the World
Wide Name (WWN) to uniquely identify each host HBA and specific HBA port
that has logged into the controller. The HBA WWN and the HBA Port WWN are
displayed in the LUN Mapping section at the top of the LUN Mapping window.
1 In the “LUN Mapping” segment, click on the HBA WWN or HBA Port WWN to
which you wish to create a LUN Map. Only one is displayed in the example.
Main Screen
2 In the name field, enter a name you wish to identify the LUN Mapping. You
are limited to 28 characters. (We recommend that the name relate to the host
or host name for clarity.)
The HBA WWN and HBA Port WWN of the specific port (a single node can
have multiple ports) are displayed across the top of the LUN Mapping window.
LUN Mapping Screen
Creating a LUN Mapping
Chapter 7 - LUN Mapping
Storview.book Page 85 Tuesday, September 23, 2003 5:11 PM
The user definable name directly below the “HBA WWN” will be used on the
Main screen to identify the host HBA or HBA Port from this point forward.
3 In the “Map to” field, use the pull-down menu to choose from HBA or Port.
If you select to map to the HBA, then all ports on the HBA will see the LUN
that is being mapped. If you map to a specific HBA port, then only the port
of the HBA identified at the top of the screen will see the LUN.
LUN Mapping Screen - Name Entered
4 Under the “Controllers (C0/C1) Port” section located in the dark green bar,
click the pull-down menu and select either Both Ports or Individual.
This is the controller port or ports to which the host will have access. If you
select “Both Ports,” both radio buttons will be greyed out indicating the LUN
is presented on all ports. If you select “Individual” it will allow you to specify
which of the controllers port the LUN will be seen by the HBAs. The radio
button appears selected (solid dot) when chosen. The “0” selection is the
Controller 0 Port 0 and if installed Controller 1 Port 0, the “1” selection is the
Controller 0 Port 1 and again if installed Controller 1 Port 1. Refer to the
hardware user’s guide Topology chapter for the specific connection on the
Host I/O card for the specific Controller’s port.
LUN Mapping Screen - Host Access
Creating a LUN Mapping 85
Chapter 7 - LUN Mapping
86
Storview.book Page 86 Tuesday, September 23, 2003 5:11 PM
5 Assign a LUN number that will be presented to the host operating system for
the LUN in the list you are working with.
The default setting is “Not Seen.” This indicates that the LUN is not mapped.
You may choose from 0 - 511 for the LUN number presented. Note that some
HBA and OS settings inhibit the OS from being able to detect 512 LUN
possibilities.
NOTE: The setting “Not Seen” is also used to delete the LUN Map. Refer to
“Deleting a LUN Mapping” on page 88.
LUN Mapping Screen - Presented As
6 Set the Data Access privileges for the LUN. Click on the pull-down menu and
choose from Read/Write or Read Only. Read Only is not supported by
Microsoft® Windows NT, Microsoft® Windows® 2000 or Microsoft®
Windows® 2003.
LUN Mapping Screen - Access Privileges
7 If you selected “Individual” access for the Controller’s Port, you will need to
specify which port the LUN will be presented to. Do this by selecting the
appropriate radio button. Refer to the hardware user’s guide, Topology
chapter for details on the Host I/O card port connectivity.
Creating a LUN Mapping
Chapter 7 - LUN Mapping
Storview.book Page 87 Tuesday, September 23, 2003 5:11 PM
LUN Mapping Screen - Host I/O Card Port Availability
8 Continue setting the options for the remaining LUNs that you wish to map.
9 Once you are finished, click the Apply button in the upper right corner of the
LUN Mapping window.
You will see a status window appear indicating that changes to the LUN
Mapping was successful.
LUN Mapping Screen - Completed
10 Click the Close button.
Creating a LUN Mapping 87
Chapter 7 - LUN Mapping
88
Storview.book Page 88 Tuesday, September 23, 2003 5:11 PM
Deleting a LUN Mapping
1 In the “LUN Mapping” segment of the Main screen, click on the node name
WWN or Port you wish to delete its LUN Map.
Main Screen
2 From the pull-down menu under “Present As” change the LUN number to Not
Seen.
LUN Mapping Screen - Presented As
3 Click the Apply button in the upper right corner of the LUN Mapping screen.
Deleting a LUN Mapping
Chapter 7 - LUN Mapping
Storview.book Page 89 Tuesday, September 23, 2003 5:11 PM
You will see a status window appear indicating that changes to the LUN
Mapping was successful.
LUN Mapping Screen - Completed
4 Click the Close button.
Deleting a LUN Mapping 89
Chapter 7 - LUN Mapping
90
Storview.book Page 90 Tuesday, September 23, 2003 5:11 PM
Modifying a LUN Mapping
You can make changes to the following parameters of a LUN Mapping:
� Map Name
� LUN Number presented to the operating system
� Data Access privileges (Read/Write or Read Only)
� Host Access (Host I/O card port availability)
� Map To parameter (HBA or Port)
NOTE: Making changes to the Map To parameter may have adverse
reactions to another map to a specific port.
1 Access the “LUN Mapping” segment of the Main screen, and click on the
node WWN or Port of the host you wish to make LUN Mapping changes.
LUN Mapping Screen
� If you wish to change the LUN Map name, enter a new name (up to 28
characters) and click the Apply button.
� If you wish to change LUN number presented to the operating system,
locate the “LUN #” you wish to modify and click the pull-down menu
under “Present As” and select a new LUN number (0-511). Setting the
property “Not Seen” will effectively delete the LUN Map. Click Apply to
make the changes effective. (Some changes may require that the host
system to which the LUN was mapped to be rebooted.)
Modifying a LUN Mapping
Chapter 7 - LUN Mapping
Storview.book Page 91 Tuesday, September 23, 2003 5:11 PM
� If you wish to make changes to the Data Access privileges of a specific
LUN, locate the “LUN #” and click the pull-down menu changing the
parameter to either Read/Write or Read Only. Note that Microsoft®
Windows NT does not support Read Only. Click the Apply button to make
the changes effective.
� If you wish to make changes to the Host Access parameter, if “Both Ports”
are selected all LUNs will have both Host I/O card ports selected (0 & 1). If
you change the parameter to “Individual”, you must select which LUN you
wish to have access on either Port H0 or Port H1. You cannot mix the LUNs
of a LUN Mapping where some have both ports and some have a single
port mapping. Click the Apply button to make your changes effective.
� If you wish to make changes to the “Map To” parameter, there are some
considerations to be aware of: for example, if there are three maps, one to
each Port of the same HBA, then a “Map To” is changed to HBA, all two
maps will be deleted and a single map will be created to the HBA.
If there is a mapping to the HBA and a map is created to a specific Port,
the map to the HBA will be deleted.
This means that the other Port could see the internal LUNs, because the
LUN Mapping was to the HBA and now will not be able to see any LUNs
until you open the other host port and map LUNs to the port. The Port to
which the map is now configured will see the internal LUNs.
Modifying a LUN Mapping 91
Chapter 7 - LUN Mapping
92
Storview.book Page 92 Tuesday, September 23, 2003 5:11 PM
Modifying a LUN Mapping
Chapter 8
Storview.book Page 93 Tuesday, September 23, 2003 5:11 PM
Controller Settings
Modifying Controller Properties
The Controller window allows you to view and make changes to the controller
settings. Each controller is shipped from the factory with default settings which
have been found to work well in a majority of applications and environments.
Since your environment may be different, you may want to make changes to
optimize the controllers for your application.
1 To view or modify a controller setting, click the Controller icon on the Main
screen for the storage system you are logged into.
Main Screen
2 The Controller window will open with the Information tab selected.
93
Chapter 8 - Controller Settings
94
Storview.book Page 94 Tuesday, September 23, 2003 5:11 PM
Controller Information
When the Controller window opens, the Information tab is selected and presents
the user with a view of one or both controllers depending on the number of
controllers installed.
Controller Screen - Information Tab
From this window you can view:
� Status - This item will indicate whether or not the controller is detected in
the slot.
� WWN - Displays the world wide name assigned to the controller.
� Firmware Version - Displays the current firmware level of the controller.
� CPLD Revision - Displays the current version of the complex
programmable logic device.
� Processor - Displays the speed of the main processor expressed in MHz.
Controller Information
Chapter 8 - Controller Settings
Storview.book Page 95 Tuesday, September 23, 2003 5:11 PM
� Co-Processor - If displayed, it indicates that the co-processor board is
installed and shows the speed of the co-processor expressed in MHz.
� Total SDRAM - Displays the total amount of memory. Generally, there is
512 MBs of RAM for each processor.
� Resets/Power Cycles - Displays the number of resets and power cycles the
controller has experienced.
� Controller Port (P0) - This displays the operating status of the Controller
Port of the specific controller. It displays the speed and ID of the port.
Refer to the logical diagrams in the imageRAID User’s Guide. These ports
are identified as C0P0 and C0P1 for Controller 0, and C1P0 and C1P1 for
Controller 1.
� Controller Port (P1) - This displays the operating status of the Controller
Port of the specific controller. It displays the speed and ID of the port.
Refer to the logical diagrams in the imageRAID User’s Guide, these ports
are identified as C0P0 and C0P1 for Controller 0, and C1P0 and C1P1 for
Controller 1.
� Configuration: Name - This is the name of the configuration you entered
during initial setup or as defined later.
� Configuration: WWN - This is the world wide name of the configuration,
derived from either Controller 0 or Controller 1's WWN. If the controller
whose WWN is being used fails, the failed controller's WWN is still used
even though the partner controller is the primary controller and the
replacement controller has a different WWN.
� Configuration: Cache will be flushed to Array - This is the array which the
controllers cache will be flushed to during a power failure.
� Configuration: Arrays - This indicates the number of arrays created for this
configuration.
� Configuration: LUNs - This indicates the number of LUNs assigned to the
configuration.
NOTE: If the controller status changes from “Present” to “Missing or Failed”
and/or the FC Host Loop is down, you will see the Information tab begin
flashing red until the condition is corrected.
Controller Information 95
Chapter 8 - Controller Settings
96
Storview.book Page 96 Tuesday, September 23, 2003 5:11 PM
Controller Environmentals
To view the controller(s) status, click the Controllers icon on the Main screen for
the storage system you are logged into.
The Controller window will open with the Information tab selected. Click the
Environmentals tab.
Controller Screen - Environmental Tab
From this window you can view the following:
� Component Status:
• Controller - Displays the presence of a controller in the slot.
• Battery - Displays the life status of the backup battery unit on the
controller. This status is expressed in hours remaining to hold the data
preserved in cache during a power failure. If the life percentage is 79%
or below, the cache parameter will be temporarily disabled. Also, the
Environmentals tab will change to red as the life percentage drops
below 80%.
Controller Environmentals
Chapter 8 - Controller Settings
Storview.book Page 97 Tuesday, September 23, 2003 5:11 PM
• UPS - Displays whether an external uninterruptable power source
(UPS) is present and/or if it has failed.
• Temperature - Displays the temperature results of the thermal-sensors
on the controller board in both Celsius and Fahrenheit.
� Voltage:
• 12V Input - Displays 12V DC power supply input to the controller.
• 5V Input - Displays the 5V DC power supply input to the controller.
• 5V Protected - Displays the current limited version of 5V input.
• 3.3V - Displays the controller onboard main 3.3V DC regulator output.
• 3.3V SDRAM - Displays the isolated 3.3V DC to power SDRAM DIMM.
• 2.5V - Displays the controller onboard main 2.5V DC regulator output.
• 1.5V Processor Core - Displays the 1.5V DC regulator output to power
the CPU chip.
• Battery - Displays the battery voltage measured directly at the output
of the battery.
� Co-Processor Status:
NOTE: Co-Processor status information is only applicable to systems
which use the imageRAIDXP model controller.
• Status - Displays the presence of the co-processor board, or if it is
failed.
• 3.3V SDRAM - Displays the isolated 3.3V DC to power SDRAM DIMM.
• 1.5V Core - Displays the 1.5V DC regulator output to power the CPU
chip.
NOTE: If the controller battery status changes, the Environmental tab will begin
flashing red until the condition has been corrected.
Controller Environmentals 97
Chapter 8 - Controller Settings
98
Storview.book Page 98 Tuesday, September 23, 2003 5:11 PM
Controller Parameters
Selecting the Parameters tab allows you to make changes to controller settings
such as the configuration name, the configuration WWN, controller port settings,
single controller mode, auto spare settings, and rebuild options.
Click the Controller icon on the Main screen for the storage system you are
logged into.
Controller Screen - Parameters Tab
From this window you can view and change the following:
� Configuration Name - This is the name you will assign to the configuration.
If you wish to change the configuration name, enter the new name here.
� Configuration WWN - Determines which controllers’ WWN to report to the
outside world.
� Controller LUN - This option sets the logical unit number (LUN) that
StorView uses to communicate with the RAID Controller(s). Changing this
parameter can alleviate a potential performance issue which is seen as a
significant degradation in performance when relatively high I/O activity is
ongoing, and a “Disk” LUN and Controller LUN are using the same logical
unit number. The values are: Not Mapped, and 0 - 511, with LUN 0 being
the default.
Controller Parameters
Chapter 8 - Controller Settings
Storview.book Page 99 Tuesday, September 23, 2003 5:11 PM
Normally, the first “Disk” LUN you create will automatically be assigned
LUN 1, because the controller processor, by default, is 0 for the Controller
logical unit number. If your “Disk” LUN needs to be at LUN 0, then you
would change the Controller LUN parameter to another LUN that is not
being used by another “Disk” LUN. The “Not Mapped” selection is used
when the controller is not required to be addressed as an independent
device. When set to “Not Mapped,” StorView will use the first available LUN
which should be at LUN 0. See “Changing the Controller LUN” on page 104.
If you need to change this parameter, make the change after you have
created your arrays, otherwise you will not be able to save the change nor
see the LUN 0 selection in the Create LUN window. This performance issue
could also occur if you perform a LUN Map to your HBA or HBA Port and
assign the mapping to the Controller LUN.
� Controller Port ID (P0) - This is the target ID for both controller(s) port 0. It
can range from: Soft Address, or 0 - 125.
� Controller Port ID (P1) - This is the target ID for both controller(s) port 1. It
can range from: Soft address, or 0 - 125.
NOTE: You must have a configuration established to make changes to the
Controller Port IDs.
� Controller Port Connection Options - This option sets the type of
connection that is being used from the host or switch. Use the Automatic
setting for most environments where it will attempt to use Loop Only first
then Point to Point. For custom settings, if you are connecting to a FL_Port
switch or NL_Port HBA then select Loop Only, and if you are connecting
F_Port switch or N_Port HBA then select Point to Point.
� Controller Port Data Rate - Use the Automatic setting for most
configurations. If you choose to use a specific setting (1GB or 2GB) and
override the automatic setting be sure the software setting here matches
the hardware switch setting on the Host I/O card.
� Different Node Name - Selecting this option allows the controller to report
a different Configuration WWN for Port 0 and Port 1 (H0 and H1
connectors on the Host I/O cards respectively). Normally, when
deselected, a host connected to either port will see the same Configuration
WWN. When enabled (selected) you will see a slightly different WWN for
each port but the same Configuration name. This option is useful to users
who are connecting the storage to a switch employing a fabric topology
where the same WWN is not tolerated.
Controller Parameters 99
Chapter 8 - Controller Settings
100
Storview.book Page 100 Tuesday, September 23, 2003 5:11 PM
� Controller Log SES Events - Selecting this option will cause all enclosure
events (SES Events) to be added to the events that the controller logs. SES
events are those events that pertain to the enclosure components such as
cooling fan status, power supply status, I/O card status, etc. The controller
will log all events relative to the RAID Controllers and events for SES
Events when this option is selected. It does not log events specific to
StorView events such as a server log in or log out, password change, email
setting, etc. Within StorView note that you must export the controller logs
to view them, refer to “Controller Operations” on page 102 for controller
log buttons. The Logs button on the Main screen is the user access to the
StorView log of events. The control button for the controller log is found in
the Controller window when the Operations tab is selected.
� Single Controller Mode - When operating in the StandAlone mode (single
controller configurations) selecting this option stops the controller from
constantly checking for a partner controller. When operating a duplex
Active-Active configuration, deselect this option.
� Background Verification - This option when selected is used to
automatically verify the media of all drives in the background. If a media
error is detected, the controller can automatically re-write the data,
providing that the array is in a fault tolerant mode.
� Auto Update Drive Firmware - Selecting this option allows the disk drive
firmware to be automatically updated when a drive has been updated
using the VT-100 menu based system. Any time an exact matching drive
identical to the drive you updated in the system is discovered, it will
automatically update those drives firmware. StorView will display an icon
that the firmware is being updated in the enclosure front view graphical
display on the Main screen.
� Auto Hot Spare - This option when selected allows the data to be rebuilt
on the drive that is inserted into the slot from which the failed drive was
removed. This is beneficial when a hot spare or global spare is not
designated for a fault tolerant array.
� Auto Rebuild - Selecting this option will automatically start a rebuild
operation when a fault-tolerant array looses a drive member and a
replacement or hot spare drive is available and online. When you assign a
hot spare (dedicated or global) this option is automatically enabled. After
creation of the hot spare, the option can be disabled if desired.
Controller Parameters
Chapter 8 - Controller Settings
Storview.book Page 101 Tuesday, September 23, 2003 5:11 PM
� Rebuild Priority - This determines the amount of processor time allocated
to the rebuild operation. The higher the value entered here, the more time
the processor will spend expediting the rebuild operation, thus reducing
the time of slow I/O operations. Choose the desired percent from the
pull-down menu.
NOTE: If you are making changes to items marked with an asterik, you must
reboot both the storage system and the host system connected to the
storage in order for the changes to take effect in the host operating
system.
Controller Parameters 101
Chapter 8 - Controller Settings
102
Storview.book Page 102 Tuesday, September 23, 2003 5:11 PM
Controller Operations
Clicking the Operations tab in the Controller window will allow the user to
manage their controllers with functions such as reset and shutdown, as well as
perform other controller operations.
Controller Screen - Operations Tab
From this window you can control or manage the following:
� Status - Directly under each controller is a status line that presents the
current status of each controller.
� Reset - This option provides the user with the ability to reset a specific
controller.
� Shutdown - This option provides the user with the ability to gracefully
shutdown the specific controller.
� Update Controller F/W - This option provides the user with the ability to
flash the controller’s firmware by reprogramming the EEPROM. (See note
on the following page.)
� Synchronize Time - This option allows the user to synchronize the
controllers time with that of the host system.
Controller Operations
Chapter 8 - Controller Settings
Storview.book Page 103 Tuesday, September 23, 2003 5:11 PM
� Reset Both Controllers - This option provides the user with the ability to
reset both controllers at the same time.
� Shutdown Both Controllers - This option provides the user with the ability
to gracefully shutdown both controllers.
� Export Controller Logs - This options allows the user to export to a file the
controller log entries that are maintained on the controller and is limited to
4096 log entries. Note that these logs are different from the Main screen
StorView Logs button, where they contain only controller events and if
selected SES Events, but they do not contain StorView specific events.
� Clear Controller Logs - This option allows the user to clear the event logs
maintained in the controller and is not the same log files retained by
StorView which is located on the Main screen under the Logs button. These
logs are limited to 4096 entries and is also limited by the amount of free
disk space.
NOTE: The RAID Controllers will automatically update their firmware,
however the update process behaves differently under certain
conditions. If one controller has a later version of firmware then its
partner controller, during the startup process the later version
firmware controller will automatically update the firmware on the
lower revision controller to match the later version. If a partner
controller fails in a Duplex (dual controller) configuration, when the
failed controller is replaced, regardless of its firmware version it will
always be updated to match the surviving controllers firmware.
Controller Operations 103
Chapter 8 - Controller Settings
104
Storview.book Page 104 Tuesday, September 23, 2003 5:11 PM
Changing the Controller LUN
This Parameter option sets the logical unit number (LUN) that StorView uses to
communicate with the RAID Controller(s).
1 From the Main screen, click on the Controller icon.
2 When the Controller window opens, click on the Parameters tab.
Controller Window - Parameters Tab Screen
3 Locate the option “Controller LUN” and select the desired LUN number from
the pull-down menu.
By default the Controller LUN is assigned LUN 0. Some configuration may
require a data LUN or a mapped LUN to reside at LUN 0, in those cases you
will probably want to change the Controller LUN to one not being used.
Otherwise, performance degradation will occur because it will share the LUN
with a “Disk” LUN.
NOTE: To optimize the performance abilities of StorView, see Execution
Throttle and Scatter/Gather settings on the following page.
4 Click the Apply button and close the window.
Changing the Controller LUN
Chapter 8 - Controller Settings
Storview.book Page 105 Tuesday, September 23, 2003 5:11 PM
StorView Performance Optimization
There are a few HBA and operating system parameters that can be adjusted to
increase the performance of StorView. They are the HBA Execution Throttle
setting and the operating system Scatter/Gather registry setting.
Execution Throttle
To improve general I/O performance by allowing more commands on the fibre
bus, we recommend changing your host bus adapter’s execution throttle
parameter to 256. Refer to your host HBA documentation for more information.
Scatter/Gather
(Microsoft® Windows NT, Microsoft® Windows® 2000, or Microsoft® Windows®
2003 Only) To increase general I/O performance by allowing larger data transfers
we recommend editing the “MaximumSGList” parameter in the registry. The
recommended hexadecimal value is “ff.” The path is:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/<name of HBA
driver>/Parameters/Device/
Refer to your operating system documentation for more information on editing
the registry.
StorView Performance Optimization 105
Chapter 8 - Controller Settings
106
Storview.book Page 106 Tuesday, September 23, 2003 5:11 PM
Scatter/Gather
Chapter 9
Storview.book Page 107 Tuesday, September 23, 2003 5:11 PM
Drive Panel Settings
Drive Information
From the Drive window the user can view specific drive inquiry information and
make changes to drive parameter settings. You will also find functional controls
that allow you to locate a drive, make hot spares, and execute a rebuild
operation.
1 From the Main screen, click on a disk drive icon displayed in the enclosure
front view which will open the Drive window.
Drive Window
107
Chapter 9 - Drive Panel Settings
108
Storview.book Page 108 Tuesday, September 23, 2003 5:11 PM
Locate Drive
1 To locate a drive, identify the drive displayed in the enclosure front view and
click that drive. The Drive Panel will open.
2 Click the Locate button.
Locate Drive Screen
3 A sub menu will open in the Drive Panel screen, from which you will select
the time interval to blink the Drive’s Activity LED. Select the time period you
wish to use.
4 Identify the drive in the enclosure by its blinking Drive Activity LED.
Make Spare
Refer to “Spares” on page 61 for information on dedicated and global spares.
Locate Drive
Chapter 9 - Drive Panel Settings
Storview.book Page 109 Tuesday, September 23, 2003 5:11 PM
Rebuild Array
This option is designed for situations where the user wants to manually start a
rebuild operation. One situation where this option would become useful is if you
inadvertently pulled the wrong drive from a working array. That drive is now
flagged as a failed drive, regardless of whether or not you re-insert the drive
quickly. If for example you do not have a hot spare defined, the array will not
begin a rebuild operation, and by re-inserting the drive it is still flagged as a
failed drive. Even if you had selected the Auto Hot Spare option in the Controller
Panel, the drive is required to be a new different drive for that option to
automatically begin a rebuild. So now you can force the rebuild using the now
flagged failed drive to rebuild the array. Normal operations will be resumed once
the array is returned to a fault tolerant state.
1 To initiate a manual rebuild operation using the specific disk drive, identify
the drive displayed in the enclosure front view and click that drive. The Drive
Panel screen will open.
2 Click the Rebuild button.
Drive Panel Screen
3 A small window will appear where you will select the “critical” array to
which you wish to rebuild using the selected disk drive.
Click the scroll button to locate the correct array and click that array name.
Rebuild Array 109
Chapter 9 - Drive Panel Settings
110
Storview.book Page 110 Tuesday, September 23, 2003 5:11 PM
Drive Panel Screen - Rebuild Array
4 A confirmation window will appear indicating the successful execution of the
command, click the Close button.
5 Click the Close button on the Drive Panel window.
6 You can monitor the rebuild operation from the Main screen.
Rebuild Array
Chapter 10
Storview.book Page 111 Tuesday, September 23, 2003 5:11 PM
Event Logs
StorView has the ability to manage the events generated from the RAID Controllers,
SES processor’s and the software’s unique events in a comprehensive set of event
logs. They can be used for monitoring and managing enclosure events and/or error
conditions, and controller events and errors. The following event types are logged:
� Enclosure, Drive, Array, and Controller events and errors
� Network communication events and errors
� Temperature and Voltage events and errors
� Fibre Loop events and errors (Drive and Host)
� SES Enclosure Component events and errors
� StorView Modules and StorView Servers events and errors
There are two event logs maintained that will be referred to below: one set of log
entries the controller maintains and one set StorView maintains. There are some
differences and limitations between the controller set of event logs and StorView’s
event logs. This includes the type of events logged and in some cases the ease of
interpretation.
The controller’s maximum event log size is 4096 entries, and oldest events are
overwritten as the log reaches the size limit. Some repetitive events such as LIPs
are appended to previous events, so entries are not used up unnecessarily. The
controller logs are managed by clicking the Controller icon and accessing the
specific Operation tab. From here you can export the controller logs to an
external file or clear the log entries. You can add SES Events to the controller log
by selecting this option in the Controller - Parameters tab settings, see “Controller
Parameters” on page 98.
111
Chapter 10 - Event Logs
112
Storview.book Page 112 Tuesday, September 23, 2003 5:11 PM
StorView’s event log will maintain the controller’s compilation of events and the
software’s specific events. The controller’s compilation of events include those
unique to the imageRAID Controller events (known as controller events), drive
events and host events, and if the Controller Log SES Events option is selected it
will include the SES events.
NOTE: If “Controller Log SES Events” option is not selected, Email notifications
setup for those events will not occur.
The StorView Server will also perform a synchronization of its event log to the
controller log when the StorView Server starts. Since the controller(s) can
continue to operate when StorView Server is shut down, the StorView log would
have missing events during this down period. The event synchronization feature
of StorView will append the log with the controller events that occurred while the
StorView Server was shutdown.
The time stamp for each event in the StorView log is the exact time the event was
received by StorView, and can be slightly off for the actual time it occurred in the
controller log. After synchronization, events that occurred while the StorView
Server was down are marked with an additional string in the event description
which displays the actual time stamp that event occurred. The string will be in
the form of an asterisk followed by the time and date in parenthesis. At the
bottom of the Event Log window you will find the footnote “* Indicates event
occurred while Server module was down.” This indicates that those events with
this extra time stamp in the description are the results of a synchronization and
displays the exact time the event actually occurred.
StorView’s event log has a maximum size limited only by the available disk
space, therefore the log events in StorView will require regular maintenance to
ensure the list is manageable and doesn’t fill to capacity. You can export the log
files to a comma delimited file prior to clearing them for later use.
Chapter 10 - Event Logs
Storview.book Page 113 Tuesday, September 23, 2003 5:11 PM
Accessing and Navigating the StorView Event LogTo access the Event Logs, click on the Logs button located below the focused
server in the Main screen.
Main Screen with Event Log Screen
Below you will find an illustration that depicts the components of the event log.
Event Log Description
Navigation Buttons(moves one screen
forward or backwards).Note that these buttons
will also appear at thebottom of the window.
Information Status Icon
Error Status Icon
Warning Status Icon
Export button providesthe user with a file of theevents that can be usedwith third-party softwareproducts.
Clears the Event Log
Indicates the eventoccurred while the StorView Serverwas shut down.
Plain languagedescriptionof the event.
Allows the user to jumpquickly to a specific Eventbased on its Log Number.
Event Log Number
Date and Timethe Event was
received by theStorView Server
Device Nameand WWN ID
Accessing and Navigating the StorView Event Log 113
Chapter 10 - Event Logs
114
Storview.book Page 114 Tuesday, September 23, 2003 5:11 PM
Exporting the StorView Event Log
The event logs can be exported into a file for use in third-party software
products. Some web browsers provide more options for the format of the file.
Refer to your browser software for specific details.
1 To export the log file, click the Logs button on the Main screen for the
storage system you are logged into.
Main Screen
2 Click the Export button in the Event Logs window.
Event Log Screen
Exporting the StorView Event Log
Chapter 10 - Event Logs
Storview.book Page 115 Tuesday, September 23, 2003 5:11 PM
� If you are using Internet Explorer as your web browser, you will see the
following screen. Choose to save the file or open it. The saved file format
will be a comma-delimited format.
Example of Export Log Event Options - Netscape
� If you are using Netscape as your web browser, you will see the following
screen. This product provides you with a few more options through the
“Advanced” button.
Click the Advanced button and select the file format type, creator
application, and other options available, as desired.
Example of Export Log Event Options - Netscape
3 Click the Close button on the Event Logs window.
Exporting the StorView Event Log 115
Chapter 10 - Event Logs
116
Storview.book Page 116 Tuesday, September 23, 2003 5:11 PM
Clearing the StorView Event Log
1 To clear the log file, click the Logs button on the Main screen for the storage
system you are logged into.
Main Screen
2 Click the Clear button in the Event Logs window.
Event Log Screen
3 Click the Close button on the Event Logs window.
Clearing the StorView Event Log
Chapter 10 - Event Logs
Storview.book Page 117 Tuesday, September 23, 2003 5:11 PM
Operating System Event Log
StorView is capable of passing all the events to the host operating system event
log. Accessing the operating system event logs will display events generated from
StorView. Each event is identified by an event ID. In the tables for the events you
will see the Event type followed by its ID. The ID is given in the format of its
hexadecimal value and its equivalent decimal value in parenthesis. The Event
number is how the events are displayed in the operating system event log. The
decimal value is the is how the OS event log will display the event ID.
You can double-click the specific event in the operating system log and it will
display a window with a plain english description of the event.
Also, you can use the tables to locate the event ID and determine the possible
cause of that event and suggested actions to take if necessary.
There are three types of events logs. StorView events are placed into the
application event logs.
To shutoff OS event logging, edit the following file using a text editor:
<install directory>/db/server.ini
1 Change the field “UseOsEventLog” from “true” to “false.”
UseOsEventLog = true enables event logs to be sent to the Windows
Event log, and,
UseOsEventLog = false disables event logs being sent to the Windows
Event log
2 At the Main screen click the Rescan button. After the rescan is complete
events will no longer be sent to the Windows operating system event log.
Operating System Event Log 117
Chapter 10 - Event Logs
118
Storview.book Page 118 Tuesday, September 23, 2003 5:11 PM
List of Events
imageRAID Controller Events
The following table provides a brief description of the events which relates to the
imageRAID Controllers and the configuration. The Type [ID] format is: Event type
name with its associated ID expressed in [hexadecimal (decimal (displayed in the
OS))].
imageRAID Event Messages Type [ID] Cause Action
The onboard cache protection battery backup unit has failed or has been disconnected.
Error [0xB07 (2823)]
Battery failure. Replace battery in the controller.
The battery backup unit attached to the controller is now functioning correctly.
Information[0xB42 (2882)]
Battery charging complete.
No action necessary.
The controller battery backup unit is charging.
Information[0xB62 (2914)]
Battery charging started.
No action necessary.
The cache data being preserved by the controller’s battery was lost. There were <xx> cache entries totalling <yy> 512-byte blocks.
Error[0xB65 (2917)]
Failure of power for an extended time with writeback cache present.
Check the file system.
The controller’s internal temperature <aa>C is approaching the maximum limit. You should check the cooling system for problems.
Warning[0xB04 (2820)]
Blocked fan.
Failing fan.
Elevated ambient temperature.
Check enclosure for sufficient air flow.
Check for a failed fan, if found replace cooling fan module.
Check the ambient temperature of the environment, decrease the local ambient temperature.
The controller’s internal temperature <aa>C has exceeded the maximum limit. The controller will shutdown to prevent damage.
Error[0xB03 {2819)]
Blocked fan.
Failing fan.
Elevated ambient temperature.
Check enclosure for sufficient air flow.
Check for a failed fan, if found replace cooling fan module.
Check the ambient temperature of the environment, decrease the local ambient temperature.
List of Events
Chapter 10 - Event Logs
Storview.book Page 119 Tuesday, September 23, 2003 5:11 PM
The partner controller has failed or has been removed.
Error[0xB08 (2824)]
Failure or removal of one controller (partner) in an Active-Active configuration.
Replace the controller.
Re-install the controller.
This controller has not received a response from the other (partner) controller in the allotted time, and therefore it has been disabled.
Error[0xB09 (2825)]
Failure or removal of one controller (partner) in an Active-Active configuration.
Replace the controller.
The other (partner) controller has been inserted.
Information[0xB29 (2857)]
Partner controller has been inserted.
No action necessary.
The other (partner) controller has passed its self-test and is now ready (failback).
Information[0xB2a (2858)]
Partner controller is ready to fail back.
No action necessary.
Failover started. Information[0xB5C (2908)]
Failure or removal of the partner controller.
No action necessary.
Failover completed. Information[0xB5D (2909)]
Completion of failover process.
No action necessary.
Failback started. Information[0xB5E (2910)]
Partner controller started failback.
No action necessary.
Failback completed. Information[0xB5F (2911)]
Completion of failback process.
No action necessary.
The controller has been powered on.
Information[0xB51 (2897)]
The controller was powered on.
No action necessary.
The controller has been powered off.
Information[0xB50 (2896)]
Removal of controller or power.
No action necessary.
The controller has been reset. Information[0xB57 (2903)]
User initiated a controller reset.
No action necessary.
The controller has been shutdown. Information[0xB58 (2904)]
User initiated a controller shutdown.
The controller temperature was exceeded and the controller shut itself down.
No action necessary.
Check for a failed fan, replace as needed. Check for blocked air flow, correct as needed. Check for high ambient temperature, reduce the environments ambient temperature.
A configuration parameter has been changed: <array name> (Array <array number>) has been trusted due to a cancellation of an initialization.
Information[0xB74 (2932)]
A user cancelled an initialization.
No action necessary.
imageRAID Event Messages Type [ID] Cause Action
imageRAID Controller Events 119
Chapter 10 - Event Logs
120
Storview.book Page 120 Tuesday, September 23, 2003 5:11 PM
The controller self-test was successfully completed.
Information[0xB52 (2898)]
Self-test completion on startup.
No action necessary.
The controller self-test has failed. Error[0xB53 (2899)]
Self-test failure on startup.
Replace the controller.
The controller firmware has been upgraded to version <x.xx.xxxx>.
Information[0xB60 (2912)]
User upgraded the controller firmware.
No action necessary.
The configuration has changed. Information[0xB2F (2863)]
A change in the configuration has occurred.
If you are using the Save Configuration feature, re-save your configuration information - it no longer matches, otherwise no action is necessary.
The Event Log has been cleared. Information[0xB56 (2902)]
The user has cleared the event log.
No action necessary.
There was a fatal controller error. Kernel trace: xx,xx,xx,xx.
Error[0xB01 (2817)]
Internal hardware or firmware failure.
Replace the controller. Contact Technical Support.
There was a fatal controller error. Kernel trace: xx,xx,xx,xx.
Error[0xB01 (2817)]
Fault SDRAM or damaged internal bus.
Replace the controller.
There was a fatal controller error. Kernel trace: xx,xx,xx,xx.
Error[0xB01 (2817)]
Internal hardware or firmware failure on the coprocessor.
Replace the controller. Contact Technical Support.
There was a fatal controller error. Kernel trace: xx,xx,xx,xx.
Error[0xB01 (2817)]
Memory or bus error on the indicated channel.
Replace the controller.
There was a fatal controller error. Kernel trace: xx,xx,xx,xx.
Error[0xB01 (2817)]
Memory or bus error on the indicated channel.
Replace the controller.
The controller is flushing the partner’s mirrored cache to the drives. There are <xx> cache entries totalling <yy> 512-byte blocks.
Information[0xB35 (2869)]
Failure or removal of the partner controller.
No action necessary.
The controller has completed flushing the partner’s mirrored cache to the drives.
Information[0xB36 (2870)]
Completion of mirrored cache flushing.
No action necessary.
Flushing of the battery protected cache has started. There are <xx> cache entries totalling <yy> 512-byte blocks.
Information[0xB63 (2915)]
Failure of power with writeback cache present.
No action necessary.
imageRAID Event Messages Type [ID] Cause Action
imageRAID Controller Events
Chapter 10 - Event Logs
Storview.book Page 121 Tuesday, September 23, 2003 5:11 PM
Flushing of the battery protected cache has completed.
Information[0xB64 (2916)]
Completion of cache flushing.
No action necessary.
An SDRAM ECC error - bit <xx> at address <xx,xx,xx,xx.xx> has been detected and corrected.
Warning[0xB72 (2930)]
SDRAM error. If it repeats, replace the controller.
A stripe synchronization of a RAID 5/50 set has started. This occurs when a controller fails, or after a controller is powered off with RAID 5/50 write commands in progress.
Information[0xB2C (2860)]
A controller fails or is powered off during a RAID 5/50 write operation.
No action necessary.
A stripe synchronization of a RAID 5/50 set has completed.
Information[0xB2D (2861)]
A controller fails or is powered off during a RAID 5/50 write operation.
No action necessary.
The attached UPS has failed or been disconnected.
Error[0xB06 (2822)]
UPS has been disconnected or communications with the UPS has failed.
Check the UPS monitoring connections. Check the UPS, if necessary replace it.
The UPS attached to this controller is now functioning correctly.
Information[0xB41 (2881)]
UPS is connected. No action necessary.
The controller’s <x> voltage reading measures <aa>V which exceeds the limit.
Error[0xB19 (2841)]
Voltage regulator hardware failure.
Enclosure 5V or 12V problem in the power supply.
Replace the controller.
Replace the defective power supply.
Controller mismatch detected: Controller 0 is a <type> version, whereas Controller 1 is a <type> version.
Error[0xB1C (2844)]
The cause is that both controllers have different Drive or Host I/O Card parameters. The controllers need to be individually checked by looking at the Controller information on the respective Controller. (i.e., check Controller 0, look on the VT-100 connected to Controller 0). Only the enabled Drive or Host I/O Card will have information.
Insert matching Controllers.
Upgrade the Host I/O Card to dual Host I/O Card mode.
If the user plugs a single Disk I/O card mode or Host I/O Card mode Controller into a standard dual system, then purchase a licence or key to upgrade both Disk I/O Card and Host I/O Card operations.
imageRAID Event Messages Type [ID] Cause Action
imageRAID Controller Events 121
Chapter 10 - Event Logs
122
Storview.book Page 122 Tuesday, September 23, 2003 5:11 PM
Drive Events
These events are related to the drive loops and disk arrays. The Type [ID] format
is: Event type name with its associated ID expressed in [hexadecimal (decimal
(displayed in the OS))].
Drive Event Messages Type [ID] Cause Action
Array <name> is in a critical state. Error[0xB1B (2843)]
Drive removal or failure.
Replace the disk drive and rebuild the array.
An array expansion has started on Array <name>.
Information[0xB68 (2920)]
Expansion has started.
No action necessary.
An array expansion has restarted on Array <name>.
Information[0xB6A (2922)]
Expansion has restarted.
No action necessary.
An array expansion has completed on Array <name>.
Information[0xB69 (2921)]
Expansion has completed.
No action necessary.
Array <name> has started initializing.
Information[0xB33 (2867)]
Initialization has started.
No action necessary.
Array <name> has completed initializing.
Information[0xB34 (2868)]
Initialization has completed.
No action necessary.
A RAID 5/50 parity check has started on Array <name>. Type of parity check <paritytype>.
Error[0xB43 (2883)]
Parity check started. No action necessary.
A RAID 5/50 parity check has completed on Array <name>. Type of parity check is <paritytype>. Error count <zz>.
Error[0xB44 (2884)]
Parity check completed.
No action necessary.
A RAIS 5/50 parity check has been aborted on Array <name>. Type of parity check is <paritytype>. Error Count <zz>.
Error[0xB45 (2885)]
Parity check canceled by the user.
No action necessary.
The controller has generated a LIP on Drive Loop <xx>, due to a loop error.
Error[0xB3C (2876)]
Controller initiated a LIP.
No action necessary.
The controller has detected a data underrun from the drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) on drive loop <nn> for the SCSI Op Code xxx. This is caused by the controller detecting a bad CRC in a frame and usually indicates a link problem, either with cabling or an enclosure.
Error[0xB3B (2875)
Loop error. Check cabling, Disk I/O card, and ensure that the disk drive is properly seated.
Drive Events
Chapter 10 - Event Logs
Storview.book Page 123 Tuesday, September 23, 2003 5:11 PM
The drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) on Drive Loop <yy> returned a bad status while completing a command. SCSI Info: Operation <type>, Status <type>.
Error[0xB27 (2855)]
Drive is busy and cannot accept any more commands.
No action necessary.
An unrecoverable drive error has occurred as a result of a command being issued. This may be due to a drive error in a non-fault tolerant array, such as RAID 0, or when the array is already in a degraded mode. The controller will pass the status from the drive back to the host system, to allow the host recovery mechanisms to be used. Details: Host Loop <x>, Host Loop ID <y>, Mapped LUN Requested <z>, Op Code <zz>, Sense Data <uu>.
Error[0xB40 (2880)]
Typically due to a non-recoverable media error, hardware error, or loop error.
No action necessary.
The drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) (Array <Name> Drive <number>) has failed due to an unrecoverable error. Sense Data: <yy>.
Error[0xB0A (2826)]
Typically due to a non-recoverable media error or hardware error.
Replace the disk drive.
The drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) has been inserted.
Information[0xB61 (2913)]
Drive was inserted. No action necessary.
The controller has determined that the disk drive w/WWN <xx xx xx xx xx xx> on <yy> has an invalid block size of <uuu>. This drive should be low level formatted to change the block size.
Error[0xB3E (2878)]
The drive has an invalid block size.
Replace the disk drive.
The drive w/WWN <xx xx xx xx xx xx> (Array <Name> Drive <number>) has been marked as failed because it was removed.
Error[0xB0B (2827)]
Drive has been removed or bypassed by the user, or has a serious hardware error.
Removal of cables connecting the enclosures.
Removal of power to daisy-chained enclosure(s).
Replace the disk drive.
Replace the cables.
Restore power to the daisy-chained enclosure(s).
Drive Event Messages Type [ID] Cause Action
Drive Events 123
Chapter 10 - Event Logs
124
Storview.book Page 124 Tuesday, September 23, 2003 5:11 PM
Rebuilding has failed due to an unrecoverable error on another drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) (Array <Name> Drive <number>) in the array.
Error[0xB0D (2829)]
Typically due to a non-recoverable media error or hardware error.
Backup all data and restore to a new array.
The drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) on Drive Loop <w> returned a bad status while completing a command. SCSI Info: Operation <type>, Status <type>.
Error[0xB27 (2855)]
Unknown status returned by the disk drive.
Contact Technical Support and provide them with a copy of the event log.
The drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) on Drive Loop <w> returned a bad status while completing a command. SCSI Info: Operation <type>, Status <type>.
Error[0xB27 (2855)]
Drive is busy and cannot accept any more commands.
No action necessary.
The drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) on Drive Loop <w> timed out for the SCSI Operation <type>.
Error[0xB28 (2856)]
Drive hardware error or loop error.
Check cabling, Disk I/O cards, and ensure the disk drives are properly seated.
The drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) (Array <Name> Drive <number>) has failed due to a time-out.
Error[0xB0E (2830)]
Drive error. Replace the disk drive.
Drive Loop 0/1 has exceeded the allowable error count. The controller will not use this loop for data transfers. After two hours have elapsed, the loop will be re-enabled.
Error[0xB13 (2835)][0xB14 (2836)]
Damaged cable.
Faulty Disk I/O card (LRC failure).
Check/replace cable.
Check/replace Disk I/O card.
Drive Loop <x> is now up. Information[0xB22 (2850)]
Loop becoming ready.
No action necessary.
Drive Loop <x> is down. Error[0xB23 (2851)]
Loop has gone down.
Check/replace cable.
Check/Replace Disk I/O card.
Drive Loop 0/1 is not initializing correctly.
Error[0xB0F (2831)][0xB10 (2832)]
Loop is going down. Check/replace cable.
Check/Replace Disk I/O card.
Drive Event Messages Type [ID] Cause Action
Drive Events
Chapter 10 - Event Logs
Storview.book Page 125 Tuesday, September 23, 2003 5:11 PM
A LIP has occurred on Drive Loop <x>. Reason: <type>, The LIP was repeated <yy> times.
Information[0xB21 (2849)]
A LIP was generated so that a loop port could acquire a physical address on an arbitrated loop.
A LIP was generated by port ID: <xx> so that the loop would be re initialized.
A LIP was generated because a loop failure has been detected.
A LIP was generated by port ID: <xx> because a loop failure has been detected.
No action necessary.
Rebuilding has failed due to an unrecoverable error on the new drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) (Array <Name> Drive <number>).
Error[0xB0C (2828)]
Typically due to a non-recoverable media error, or hardware error.
Replace new drive and initiate a rebuild.
A rebuild was aborted on (Array <yy> Drive <ww>).
Information[0xB73 (2931)]
A rebuild was canceled by the user.
No action necessary.
A rebuild has started on the drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) (Array <Name> Drive <number>).
Information[0xB30 (2864)]
A rebuild has started. No action necessary.
A rebuild has re-started on the drive w/WWN <xx xx xx xx xx xx> (Target ID <zz>) (Array <Name> Drive <number>).
Information[0xB32 (2866)]
A rebuild has started. No action necessary.
A rebuild has completed on (Array <Name> Drive <number>).
Information[0xB31 (2865)]
A rebuild has completed.
No action necessary.
There is at least one enclosure’s SES device that has only one communication path rendering SES access NON-fault tolerant.
Warning[0xB5A (2906)]
No drives installed in slots 1 or 7.
Insert a disk drive is either or both drive slots 1 and 7.
All identified enclosures have at least two communication paths to their SES devices.
Information[0xB5B (2907)]
Drives are installed in slots 1 or 7.
No action necessary.
Drive Event Messages Type [ID] Cause Action
Drive Events 125
Chapter 10 - Event Logs
126
Storview.book Page 126 Tuesday, September 23, 2003 5:11 PM
There is a problem with some drives on the Drive Loop 0/1, but the loop is still up and functional. This usually indicates one cable or connection has a problem between enclosures.
Error[0xB11 (2833)][0xB12 (2834)]
Disk I/O card removal or failure.
Cable disconnected or failed.
Check/replace Disk I/O card.
Check/replace data cable.
The controller has started updating a drive’s firmware. Drive WWN:<xx xx xx xx xx xx> ID:<zz> Firmware Version: <y.yy.yyyy)
Information[0xB66 (2918)]
A firmware upgrade has started.
No action necessary.
The controller has finished updating a drive’s firmware. Drive WWN:<xx xx xx xx xx xx> ID:<zz> Firmware Version: <y.yy.yyyy)
Information[0xB67 (2919)]
The firmware upgrade is complete.
No action necessary.
The writeback cache on Array <name> has been disabled. Reason(s): <see causes>.
Warning[0xB6F (2927)]
Disabling of writeback cache for the indicated reasons:
• The partner controller has failed.
• The battery is not charged or present.
• The array has become critical.
• The UPS has failed.
• A “prepare for shutdown” command has been received by the controller.
• Replace the failed controller.
• Charge the backup battery or re-install the battery.
• Resolve the array issue and rebuild the array.
• Replace the failed UPS.
• No action necessary.
The writeback cache on Array <name> has been re-enabled.
Information[0xB70 (2928)]
Re-enabling of writeback cache.
No action necessary.
Because of a background verify failure, data blocks at LBA <yyy> from drive WWN:<xx xx xx xx xx xx> (Target ID <zz>) have been reallocated.
Warning[0xB71 (2929)]
Disk scrubbing detected an error.
No action necessary.
Drive Event Messages Type [ID] Cause Action
Drive Events
Chapter 10 - Event Logs
Storview.book Page 127 Tuesday, September 23, 2003 5:11 PM
Controller Port Events
These events are related to the host side Controller Port loops and Host I/O
cards. The Type [ID] format is: Event type name with its associated ID expressed
in [hexadecimal (decimal (displayed in the OS))].
Controller Port Event Messages Type [ID] Cause Action
The controller has generated a LIP on Host Loop <xx>, due to a loop error.
Error[0xB3D (2877)]
Controller initiated a LIP. No action necessary.
A host has accessed LUN <yy> for the first time, or for the first time following a reset or LIP. It accessed it through Host Loop <xx> (ID <zz>) with the SCSI command <check condition, busy, or task set full>.
Information[0xB2E (2862)]
First access by a particular host after a LIP or reset.
No action necessary.
Host Loop 0/1 acquired Loop ID <xx> because we were not able to get Loop ID <xx> (as specified in the controller settings).
Error[0xB17 (2839)][0xB18 (2840)]
Address conflict with either host adapter or other device on the same loop.
Resolve address conflict.
The host system w/WWN:<xx xx xx xx xx xx> and Loop ID of <xx> has logged into the controller through Host Loop <xx>. These events will only be listed from hosts that have SAN mappings created.
Information[0xB3F (2879)]
Host systems logs into the controller.
No action necessary.
A LIP has occurred on Host loop <xx>. Reason: <type>, The LIP was repeated <yy> times.
Information[0xB24 (2852)]
A LIP was generated so that a loop port could acquire a physical address on an arbitrated loop.
A LIP was generated by port ID: <xx> so that the loop would be re initialized.
A LIP was generated because a loop failure has been detected.
A LIP was generated by port ID: <xx> because a loop failure has been detected.
No action necessary.
Controller Port Events 127
Chapter 10 - Event Logs
128
Storview.book Page 128 Tuesday, September 23, 2003 5:11 PM
Host Loop <xx> is down. Information[0xB36 (2870)]
Loop is going down. Check/replace cable.
Check/Replace Host I/O card.
Host Loop <xx> is now up. Information[0xB25 (2853)]
Loop is becoming ready. No action necessary.
An unrecoverable drive error has occurred as a result of a command being issued. This may be due to a drive error in a non-fault tolerant array, such as RAID 0, or when the array is already in a degraded mode. The controller will pass the status from the drive back to the host system, to allow the host recovery mechanisms to be used. Details: Host Loop <x>, Host Loop ID <y>, Mapped LUN Requested <z>, Op Code <zz>, Sense Data <uu>.
Error[0xB40 (2880)]
Data is not recoverable. Backup all data, and restore to a new array.
Controller Port Event Messages Type [ID] Cause Action
Controller Port Events
Chapter 10 - Event Logs
Storview.book Page 129 Tuesday, September 23, 2003 5:11 PM
SES Events
These events are related to the SES enclosure components. The Type [ID] format
is: Event type name with its associated ID expressed in [hexadecimal (decimal
(displayed in the OS))].
SES Event Messages Type [ID] Cause Action
No SES drives were found which means no enclosure status information can be reported. This could be due to the SES slot(s) in the enclosure having no drives installed or the drives are malfunctioning. It may also be due to a drive target ID conflict. Check the enclosure(s) drive’s hard target ID setting.
Error[0xB59 (2905)]
No drives installed in slots 1 or 7.
Enclosure ID conflict.
Insert a disk drive is either or both drive slots 1 and 7.
Check the enclosure ID on all enclosure(s).
Power supply <zz> is OK. Information[0xC6B (3179)]
Normal condition reported.
No action necessary.
Power supply <zz> is in a critical state.
Warning[0xC6B (3179)]
The specific power supply has failed.
The specific power supply is powered off.
Replace the power supply.
Ensure that the specific power supply On/Off button is in the On position ( l ).
Power supply <zz> is not installed.
Error[0xC6B (3179)]
The power supply was removed.
Re-insert the power supply, connect the AC power cord and power on the power supply.
Fan <zz> is OK. Information[0xC6C (3180)]
Normal condition reported.
No action necessary.
Fan <zz> is in a critical state. Error[0xC6C (3180)]
A specific fan failure.
Total fan failure.
Cooling fan module was removed.
Replace the cooling fan module.
Replace the cooling fan module.
Re-inset the cooling fan module.
SES Events 129
Chapter 10 - Event Logs
130
Storview.book Page 130 Tuesday, September 23, 2003 5:11 PM
Temperature sensor <zz> is OK.
Information[0xC6D (3181)]
Temperature sensors are reporting normal temperatures in the enclosure.
No action required.
Temperature <zz> is operating outside of specifications.
Warning[0xC6D (3181)]
Temperature sensors are reporting enclosure temperatures have reached the threshold of 50°C.
Ensure that both cooling fans are operating normally. (Replace if needed.)
If the fans are set to automatic speed control, place the jumper on the Cooling fan module circuit board to force the fans to high speed.
If the environment ambient temperature is high, reduce the ambient temperature.
Ensure that the airflow is not blocked or restricted on the enclosure.
Temperature sensor <zz> is in a critical state.
Error[0xC6D (3181)]
Temperature sensors are reporting enclosure temperatures have reached the threshold of 70°C.
Automatic system shutdown will begin. In Active-Active controller configurations, one controller will shutdown its partner and shutdown the drives, then itself.
Ensure that both cooling fans are operating normally. (Replace if needed.)
If the fans are set to automatic speed control, place the jumper on the Cooling fan module circuit board to force the fans to high speed.
SES Event Messages Type [ID] Cause Action
SES Events
Chapter 10 - Event Logs
Storview.book Page 131 Tuesday, September 23, 2003 5:11 PM
Temperature sensor <zz> is in a critical state. (continued)
Error[0xC6D (3181)]
Temperature sensors are reporting enclosure temperatures have reached the threshold of 70°C.
If the environment ambient temperature is high, reduce the ambient temperature.
Ensure that the airflow is not blocked or restricted on the enclosure.
Alarm is Off. Information[0xC6E (3182)]
No condition being reported.
Alarm silenced.
No action necessary.
User pressed the Alarm Silence button on the front panel.
Alarm is On. Error[0xC6E (3182)]
A condition caused the alarm to sound.
Press the Alarm Silence button on the front panel and isolate the cause of the alarm.
SES access not fault tolerant: If this enclosure’s SES enabled drive fails then no information about the status of this enclosure will be available.
Warning[0xCFE (3326)]
An enclosure was found to have only one available SES drive.
Press the Alarm Silence button on the front panel.
Ensure that both slot 1 and 7 have SES compatible drives installed.
Ensure that the SES drives installed in slots 1 and 7 are operational.
SES access fault tolerant: Multiple paths are available for gathering this enclosure’s status information.
Information[0xCFD (3325)]
An enclosure is now SES fault-tolerant.
No action necessary.
SES Event Messages Type [ID] Cause Action
SES Events 131
Chapter 10 - Event Logs
132
Storview.book Page 132 Tuesday, September 23, 2003 5:11 PM
StorView Server Events
The following table provides a brief description of the events which relate to the
StorView Server software component. The Type [ID] format is: Event type name
with its associated ID expressed in [hexadecimal (decimal (displayed in the OS))].
StorView Server Event Messages Type [ID] Cause Action
The server has been started. Information[0x101 (257)]
The StorView Server started successfully.
No action necessary.
The server has been shutdown. Information[0x102 (258)]
The host is shutting down or a user stopped the StorView service.
No action necessary.
The multicast address is not configured. No communication will take place with other servers.
Error[0x201 (513)]
The setting “MulticastPort” is not setup in the db/IP.db file. The setting was removed or the file became corrupt.
Open the file <StorViewfolder>\db\IP.db in a text editor, and add the following line: MulticastPort=9191. Save the file and start StorView and press the Rescan button or restart the StorView service.
Multicast socket creation failure: <reason>
Error[0x202 (514)]
StorView could not setup the necessary communication paths to talk to other StorView Servers. The specific cause will be specified in the <reason> appended to the message.
Change the multicast port used by StorView. Note that all StorView servers must communicate with each other on the same multicast port. If the setting is changed on one, they must be changed on all StorView Servers.
Open the file <StorViewfolder>\db\IP.db in a text editor, and change the following line: MulticastPort=<port number>. Save the file and start StorView and press the Rescan button or restart the StorView service.
StorView Server Events
Chapter 10 - Event Logs
Storview.book Page 133 Tuesday, September 23, 2003 5:11 PM
A system rescan has been initiated.
Information[0x103 (259)]
The system rescan is starting note: a shutdown and start up event will follow.
No action necessary.
The serial number and key entered are incorrect. Remote features are temporarily disabled.
Error[0x104 (260)]
The serial number and key specified in the server settings file is not a correct match.
Open StorView in a browser from the local console, click the Settings button. Re-enter the serial number and key. If you still have problems, contact Technical Support.
All event logs cleared. Information[0x105 (261)]
A user cleared the StorView event logs.
No action required.
A user <name> has logged into the Server from Host: <host name>, IP Address: <IP_address>.
Information[0x106 (263)]
A specific user has logged into the StorView Server from the specified host and IP address location.
No action required.
A user <name> has logged into the Server from IP address: <IP_address>.
Information[0x106 (263)]
A specific user has logged into the StorView Server from the specified IP address location. (The host name was not available.)
No action required.
A user <name> has logged out the Server from Host: <host name>, IP Address: <IP_address>.
Information[0x107 (264)]
A specific user has logged out of the StorView Server from the specified host and IP address location.
No action required.
A user <name> has logged out the Server from IP address: <IP_address>.
Information[0x106 (263)]
A specific user has logged out of the StorView Server from the specified IP address location. (The host name was not available.)
No action required.
The server has been shutdown. Information[0x102 (258)]
The host is shutting down or a user stopped the StorView service.
No action necessary.
StorView Server Event Messages Type [ID] Cause Action
StorView Server Events 133
Chapter 10 - Event Logs
134
Storview.book Page 134 Tuesday, September 23, 2003 5:11 PM
A user <name> has updated their password.
Information[0x106 (262)]
A specific user has updated their password.
No action required.
A user <name> from Host: <host name>, IP Address: <IP_address> unsuccessfully attempted to update their password.
Information[0x106 (262)]
A specific user tried to change the password but verification failed or old password failed.
Ensure the user is authorized or needs assistance.
Shared memory used for the Server and the GUI to communicate could not be created nor located.
Error[0x301 (769)]
StorView tried to create/locate the shared memory used for the Server and Server CGI script to communicate.
Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them.
A CGI request was initiated from the GUI but the associated shared memory could not be opened.
Error[0x302 (770)]
The Server script creates new shared memory for the Server to access parameter passed from the GUI. This shared memory could not be found.
Retry request.
Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them.
Restart the system.
A CGI request was initiated from the GUI but the associated parameters could not be located.
Error[0x303 (771)]
The Server script creates new parameter for the Server to access parameter passed from the GUI. This parameters could not be found.
Retry request.
Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them.
Restart the system.
The Server performed a CGI request but an internal error prevented the Server from returning the results.
Error[0x304 (772)]
The request was performed but the Server encountered an error that prevented completion.
Retry request.
Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them.
Restart the system.
The Server performed a CGI request but the shared memory needed to return the results could not be created.
Error[0x305 (773)]
The Server completed the request and attempted to create shared memory to send the results back to the Server CGI. The attempt failed.
Retry request.
Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them.
Restart the system.
StorView Server Event Messages Type [ID] Cause Action
StorView Server Events
Chapter 10 - Event Logs
Storview.book Page 135 Tuesday, September 23, 2003 5:11 PM
The Server failed to complete a CGI request before its allowed time expired.
Error[0x306 (774)]
The Server completed the request but by the time it was done the Server CGI gave up.
Retry request.
Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them.
Restart the system.
The Server CGI script was unable to return CGI request results to the GUI.
Error[0x307 (775)]
The Server passed the completed request to the Server CGI but for some reason the request wasn’t completed correctly by the Server CGI script.
Retry request.
Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them.
Restart the system.
Start up is complete. Information[0xA01 (2561)]
The imageRAID module has been loaded by the StorView Server.
No action necessary.
Several failures encountered while trying to communicate with the RAID controller.
Error[0xA03 (2563)]
Several commands have been sent through a known good path but they have failed.
Ensure that the paths and hardware are operational.
Successful communication with controller after several failures.
Information[0xA04 (2564)]
A known failed path is now functional and passed retest.
No action necessary.
StorView Server Event Messages Type [ID] Cause Action
StorView Server Events 135
Chapter 10 - Event Logs
136
Storview.book Page 136 Tuesday, September 23, 2003 5:11 PM
Failed Drives Codes
The controller maintains a list of failed drives. Drives are listed in the following
format:
Failed Drive:xx WWN: yy yy yy yy yy yy
Reason Code
The reason code may be one of the following:
Reason Code Reason Action
Drive Timeout The drive has either timed out or been removed.
Re-insert the disk drive.
Replace the disk drive.
Command: xx Sense Key: yy Ext Sense: zz
The drive has failed for the specified command, with the indicated SCSI sense key and extended sense key.
Replace the disk drive.
Failed Drives Codes
Chapter 11
Storview.book Page 137 Tuesday, September 23, 2003 5:11 PM
Statistics
StorView and the imageRAID Controller monitor all incoming commands, and
calculate various statistics. The statistics monitored include:
� Command Count
� Command Alignment
� Command Size
� Readahead Statistics
� Write Clustering Statistics
� RAID 5/50 Write Statistics
The controller maintains individual access statistics for individual LUNs or all
LUNs, individual controllers, and individual or all ports. These can be used to
help balance the load from the host.
You may also export the statistical data to a comma delimited file for use in
third-party software products.
137
Chapter 11 - Statistics
138
Storview.book Page 138 Tuesday, September 23, 2003 5:11 PM
Access Statistics
These statistics are for both reads and writes, and can be used to tune the
operating system for optimum performance.
Statistics Screen - Access Tab
Every time statistics are viewed, the controller first outputs the current time and
the time since it was last reset. The statistics can be cleared at any time. This is
useful in determining the access pattern for a particular test or period of time.
Statistic Description
Reads This is a count of the total read accesses (for all or specific ports and LUNs) that are occurring. This value is expressed in MB/seconds.
Writes This is a count of the total write accesses (for all or specific ports and LUNs) that are occurring. This value is expressed in MB/seconds.
Read Commands Since Reset This is a count of the total number of read accesses that have occurred since these statistics were reset, or the controller was last powered on.
Write Commands Since Reset This is a count of the total number of write accesses that have occurred since these statistics were reset, or the controller was last powered on.
Access Statistics
Chapter 11 - Statistics
Storview.book Page 139 Tuesday, September 23, 2003 5:11 PM
Command Size - Alignment Statistics
Command size statistics express the percentage of commands whose size is as
specified. The Alignment statistics is the percentage of commands whose address
aligned on the specified address boundary.
Statistics Screen - Command Size/Alignments Tab
Statistic Description
Command Size Expressed in the percentage of commands whose size is specified for reads and writes. The valid values are: 1-100 = percentage of commands with this size, 255 = less that 1% of commands with this size.For example, consider a read or write command from a host system with Logical Block Address (LBA) 0x0000070, and access size 0x80. Using 512 byte blocks on the disk drives, it can be seen that this is a read of 64 Kbytes, which is the command size. To calculate the alignment, we check the LBA for the largest number of blocks that will evenly divide into it, in powers of 2. So, we can see that in this case, the alignment is 0x10 = 16 blocks. This equates to 8K.
Command Size - Alignment Statistics 139
Chapter 11 - Statistics
140
Storview.book Page 140 Tuesday, September 23, 2003 5:11 PM
Command Size (continued) The alignment, in conjunction with the access size, gives an indication of how many drives are involved in an access. In the above example, consider a RAID 5/50 array with a chunk size of 64K. In this case, the above access will actually involve 2 data drives, since it needs to access 8K in the first drive (0x80 – 0x70 = 0x10 blocks = 8K), and the remaining 56K in the next drive (0x70 blocks = 56K). This is clearly inefficient, and could be improved by setting the alignment to 64K on the operating system. If that is not possible, using a larger chunk size can help, as this reduces the number of accesses that span chunks. Aligning an access on the same value as the access size will improve performance, as it will ensure that there are no multi-chunk accesses for commands that are smaller than a chunk size.
Alignment This is the percentage of commands whose address is aligned on the specified address boundary. The alignment of a command from a host system is determined by the command’s address. In an optimal system, a write of one chunk of data would reside exactly within a chunk on one disk. However, if this is not the case, this write will be split up into two separate writes to two different data drives. This of course will have a negative effect on performance. To overcome these problems, the user can, with more sophisticated operating systems, set the access size and alignment to an optimal value. These statistics can help the user to tune the operating system.
Statistic Description
Command Size - Alignment Statistics
Chapter 11 - Statistics
Storview.book Page 141 Tuesday, September 23, 2003 5:11 PM
Readahead Statistics
If sequential read commands are sent to the controller, it assumes that the
commands which follow may also be sequential. It can then go and perform a
read of the data, before the host requests it. This improves performance,
particularly for smaller reads. The size of the readahead is calculated based on
the original command size, so the controller does not read too much data. The
controller maintains statistics for all readahead commands performed.
Statistics Screen - ReadAhead Tab
Statistic Description
Sequential Command Interval In determining whether to perform a readahead or not, the controller will search back in the command queue whenever it receives a new read command that is not satisfied by an existing readahead cache buffer. In a multi threaded operating system, commands from one thread may be interspersed with commands from another thread.
Readahead Statistics 141
Chapter 11 - Statistics
142
Storview.book Page 142 Tuesday, September 23, 2003 5:11 PM
Sequential Command Interval (continued)
This requires that the controller not just check the immediately previous command. The controller will search back for a number of commands, to see if the new command is exactly sequential to any one of these previous commands. If it is, then the controller determines that the data access pattern is sequential, and so performs a readahead. These statistics record the average number of commands the controller must search back for when it finds a sequential command match, the maximum number, and also the percentage for each one of these values. These give an indication of the multi threaded nature of the host.
Readahead Command Hit Rate This is the percentage of read command hits versus the total number of read commands that have been issued. This gives an indication of the sequential nature of the data access pattern from the host.
Readahead Command Efficiency
This is the percentage of the number of read command hits versus the projected number of readahead command hits. This is a measure of the efficiency of the readahead algorithm. A low value means that much of the data that the controller reads in the readahead command is not actually requested by the host.
Statistic Description
Readahead Statistics
Chapter 11 - Statistics
Storview.book Page 143 Tuesday, September 23, 2003 5:11 PM
Command Cluster Statistics
To increase performance, the controller can cluster sequential write commands
together to create a larger write command. This results in less commands being
sent to the disk drives. Additionally, if sufficient data is clustered by the controller,
then it can perform a a full stripe write for RAID5/50 arrays. This significantly
improves performance. In cases where the host does not send a sufficient number
of outstanding writes, writeback cache can be used to delay the write to disk,
increasing the likelihood of clustering more data.
Statistics Screen - Command Cluster Tab
Statistic Description
Write Cluster Rate This is the percentage of the number of write commands that are part of a cluster versus the total number of write commands that have been issued. This gives an indication of the sequential nature of the data access pattern from the host, and of the performance of the writeback cache.
Command Cluster Statistics 143
Chapter 11 - Statistics
144
Storview.book Page 144 Tuesday, September 23, 2003 5:11 PM
RAID 5/50 Full Stripe Write Rate This is the percentage of the amount of data that is written as a full stripe write versus the total amount of data written. This gives an indication of the sequential nature of the data access pattern from the host, and of the performance of the writeback cache, for RAID 5/50 drive ranks.
Command Cluster Interval In determining whether to cluster write commands or not, the controller will search back in the command queue whenever it receives a new write command. In a multi threaded operating system, commands from each thread may be interspersed with commands from another thread. This requires that the controller not just check the immediately previous command. The controller will search back for a number of commands, to try to determine if the new command is exactly sequential to any one of these previous commands. If it is, then the controller determines that it can cluster these commands.
These statistics record the average and maximum number of commands the controller must search back for when it finds a sequential command match, and also the percentage for each one of these values.
Command Cluster Count When the controller clusters a write command, it may cluster a large number of them together. These statistics record the average and maximum number of commands the controller clusters, and also the percentage for each one of these values.
Statistic Description
Command Cluster Statistics
Appendix A
Storview.book Page 145 Tuesday, September 23, 2003 5:11 PM
Optimizing RAID 5 Write Performance
Introduction
With a typical RAID 5 implementation, there are a number of steps that are
performed when data is written to the media. Every write from the host system
will typically generate two XOR operations and their associated data transfers, to
two drives. If the accesses are sequential, the parity information will be updated
a number of times in succession. However, if the host writes sufficient data to
cover a complete stripe, the parity data does not need to be updated for each
write, but it can be recalculated instead. This operation takes only one XOR
operation per host write, compared to two for a standard RAID 5 write. The
number of data transfers necessary are also reduced, increasing the available
bandwidth. This type of write access is termed a “Full Stripe Write.”
Distribution of Data and Parity in a RAID 5 with Five Drives
P (20-23) C20 C21 C22 C23 Stripe 5
P (16-19)C17 C18 C19 Stripe 4
P (12-15)C13 C14 C15 Stripe 3
P (8-11)C9 C10 C11 Stripe 2
P (4-7)
C16
C12
C8
C4 C5 C6 C7 Stripe 1
P (0-3) C0 C1 C2 C3 Stripe 0
145
Appendix A - Optimizing RAID 5 Write Performance
146
Storview.book Page 146 Tuesday, September 23, 2003 5:11 PM
The illustration on the previous page displays the distribution of data chunks
(denoted by Cx) and their associated parity (denoted by P(y-z)) in a RAID 5 array
of five drives. An “array” is defined as a set of drives, on which data is
distributed. An array will have one RAID level. A “chunk” is the amount of
contiguous data stored on one drive before the controller switches over to the
next drive. This parameter is adjustable from 64K to 256K, and should be
carefully chosen to match the access sizes of the operating system. A Stripe is a
set of disk chunks in an array with the same address. In the above example,
Stripe 0 consists of C0, C1, C2, and C3 and their associated parity P(0-3).
Maximum performance will be achieved when all drives are performing multiple
commands in parallel. To take advantage of a Full Stripe Write, the host has to
send enough data to the controller. This can be accomplished in two ways. First,
if the host sends one command with sufficient data to fill a stripe, then the
controller can perform a Full Stripe Write. Alternatively, if the host sends
multiple sequential commands, smaller than a stripe size (typically matching the
chunk size), the controller can internally combine these commands to get the
same effect. In the above example, if a 256K chunk size is used, then the stripe
size is 1MB (4 chunks * 256K). So, for maximum performance, the host could
either send 5 * 1 MB write commands, or 20 * 256K write commands.
The effectiveness of the controller’s ability to perform a Full Stripe Write depends
on a number of parameters:
Sequential Access
If the commands sent from the host are not sequential, the controller will not be
able to cluster them together. So, unless each individual access is sufficient to fill
a stripe, a Full Stripe Write will not occur.
Number of Outstanding Commands
For the controller to successfully cluster commands, there has to be a number of
write commands sent simultaneously. Setting the host to send up to 64
commands should prove adequate. Alternatively, enabling writeback cache will
have a similar effect, as the controller can then cluster sequential commands even
if the host only sends a small number of commands at a time.
Sequential Access
Appendix A - Optimizing RAID 5 Write Performance
Storview.book Page 147 Tuesday, September 23, 2003 5:11 PM
Access Size
With very small accesses, it is necessary to have a large number of commands to
cluster together to fill up a full stripe. So, the larger the access size the better. It
is best to use an access size that will fill a chunk. Of course, even if a stripe is
not filled up, small sequential writes will still benefit from command clustering.
Access Alignment
The alignment of a command from a host system is determined by the
command’s address. In an optimal system, a write of one chunk of data would
reside exactly within a chunk on one disk. However, if this is not the case, this
write will be split up into two separate writes to two different data drives. This
will have a negative effect on performance. To overcome these problems, the
user can, with more sophisticated operating systems, set the access size and
alignment to an optimal value.
As can be seen from the figure below, to get the highest performance from this
system, it is necessary to have a number of stripes being written in parallel. As
the array expands, with more and more drives, the number of commands (and
amount of sequential data) necessary to do this increases.
Distribution of Data and Parity in a RAID 5 with Eight Drives
P (56-62) C56 C57 C58 C59 C60 C61 C62 Stripe 8
C53 C54 C55 Stripe 7
C46 C47 C48 Stripe 6
C39 C61 C62 Stripe 5
C32 C33 C34 Stripe 4
C24 C25 C26 C27 Stripe 3
P (49-55)C50 C51 C52
P (42-48)C43 C44 C45
P (20-23)C36 C37 C38
P (28-34)C29 C30 C31
P (21-27)C22 C23
C17 C18 C19 C20 Stripe 2P (14-20)C15 C16
C10 C11 C12 C13 Stripe 1
C3 C4 C5 C6 Stripe 0
P (7-13)
C49
C42
C35
C28
C21
C14
C7 C8 C9
P (0-6) C0 C1 C2
Access Size 147
Appendix A - Optimizing RAID 5 Write Performance
148
Storview.book Page 148 Tuesday, September 23, 2003 5:11 PM
In the figure on the previous page, we can see that seven chunks of sequential
data are necessary to fill a stripe. To have multiple commands active for all disk
drives, this requires more data than for the case with five drives. As can be seen,
this number will increase as the number of drives increases. If a large number of
drives are used, it may get difficult to achieve maximum performance, as it
becomes more difficult to cluster a large number of commands to achieve a Full
Stripe Write.
RAID 5 Sub-Array
The difficulty in realizing the maximum performance possible introduces the
concept of a Sub-Array. Suppose an array consisted of two RAID 5 sets, as
described in the figure on page 145. If these are then striped, the resulting array
would appear as shown below. In this case, in order for a Full Stripe Write to be
performed, it is still only necessary to cluster four write commands together, as
opposed to the seven necessary as indicated below. The array of drives appears
as two separate sub-arrays, each with it’s own rotating parity.
Distribution of Data and Parity in a RAID 5 with Ten Drives and Two Sub-Arrays
It can be seen that the more sub-arrays used, the more likely it is for a Full Stripe
Write to occur, and hence the higher the performance. It is recommended to use
either four or five drives in a sub-array, for best performance. On the following
page the figure shows that even with 15 drives, it is still possible to perform Full
Stripe Writes, by clustering together 4 chunks of data.
P (40-43) P (44-47)C40 C41 C42 C43 C44 C45 Stripe 5
C36 C37 Stripe 4
C27 C28 C30
C38
Stripe 3
C19 C21 P (20-23) Stripe 2
C12 P (12-15) C13 Stripe 1
C3 P (4-7) C4 C5 Stripe 0
P (32-35)C33 C34 C35
C29C25 C26 P (24-27)
C20C17 P (16-19) C18
C11P (8-11) C9 C10
C2C0 C1
C46
P (28-31)
C22
C14
C6
C39
C47
C31
C23
C15
C7
P (36-39)C32
C24
C16
C8
P (0-3)
RAID 5 Sub-Array
Appendix A - Optimizing RAID 5 Write Performance
Storview.book Page 149 Tuesday, September 23, 2003 5:11 PM
Distribution of Data and Parity in a RAID 5 with Fifteen Drives and Three Sub-Arrays
As well as the performance advantage gained from using multiple sub-arrays,
there are a number of other advantages:
Multiple Drive Failures
In a configuration with multiple sub-arrays, it is possible for the array to sustain
multiple drive failures, provided that there is only one failure in each sub-array.
Faster Rebuild
A rebuild operation must read data and calculate parity from all the remaining
drives in the RAID set. If multiple sub-arrays are used, this means that it is only
necessary to read the data from the remaining drives in the sub-array, not all of
the drives in the array. This increases both the rebuild speed and the speed of
access to missing data, which also has to be recreated from the remaining drives.
Summary
In summary, for maximum performance using RAID 5, it is recommended to use
four or five drives in a sub-array. If there are more than five drives in a sub-array,
it is better to use a smaller chunk size, say 64K or 128K, as this will lead to more
Full Stripe Writes.
P PC60 C61 C62 C63 C64 C65
C52 C53
C39 C40 C42
C54
C27 C29 P
C16 P C17
C3 P C4 C5
PC49 C50 C51
C41C37 C38 P
C28C25 P C26
C15P C13 C14
C2C0 C1
C66
P
C30
C18
C6
C55
C67
C43
C31
C19
C7
P
P C68
C56
C45
C57
C32 C33
C20 P
P C8
C44
C69
C46
P
C21
C9
C58
C70
P
C34
C22
C10
C59
Stripe 5
Stripe 4
Stripe 3
Stripe 2
Stripe 1
Stripe 0
C71
C47
C35
C23
C11
PC48
C36
C24
C12
P
Multiple Drive Failures 149
Appendix A - Optimizing RAID 5 Write Performance
150
Storview.book Page 150 Tuesday, September 23, 2003 5:11 PM
Summary
Appendix B
Storview.book Page 151 Tuesday, September 23, 2003 5:11 PM
Troubleshooting
This chapter provides typical solutions for problems you may encounter while
using StorView to control and manage the imageRAID Storage Systems. Also refer
to the Event chapter and review the cause and actions for each event listed.
Symptom Reason Solution
Continuous indications that the partner controller has failed or is missing.
A partner controller in an Active-Active configuration has failed or was removed.
Operating in a Stand-Alone configuration with Single Controller Mode not selected.
Until the partner controller is replaced, temporarily enable Single Controller Mode in the Controller Parameters tab. Be sure to disable this option when the partner controller is to be replaced.
If you are operating in a Stand-Alone configuration, enable the Single Controller Mode setting in the Controller Parameters tab.
Password Error Password not accepted at log in.
Password was forgotten or lost.
Password is case sensitive, ensure that the password is entered correctly.
Contact Technical Support for the procedures to recover from a lost or missing password.
Lost communication with the RAID Controllers.
Service is hung. Restart the StorView service. Access the Control Panel and double-click on Services. Locate the StorView Service and click Stop. Once the service has stopped, click Start and retry the connection by clicking the Rescan button on the StorView Main screen.
151
Appendix B - Troubleshooting
152
Storview.book Page 152 Tuesday, September 23, 2003 5:11 PM
Hot spare not automatically starting when drive failure occurs in a redundant array in which a global or dedicated hot spare is defined.
The Auto Rebuild option is not enabled in the Controller Parameters.
Hot spare disk drive is too small to be used for the drive replacement.
Waiting for a valid replacement drive to be inserted.
Open the Controller settings and select the Parameters tab, place a check mark in the box by clicking the check box on the Auto Rebuild parameter.
Ensure that the disk drive defined as a hot spare is equal to or greater than the size of the drive members of the arrays.
Auto Rebuild is not selected and no hot spare drive is assigned, but Auto Hot Spare is enabled. The array will begin rebuilding once a valid replacement drive is inserted in the drive slot of the failed drive.
Consistently occurring time out errors when the browser window is open.
Host HBA parameter settings are not configured for best performance optimization.
Access your Host HBA settings and make the following changes:
Execution Throttle
Improve general I/O performance by allowing more commands on the fibre bus. Do this by changing your host bus adapter’s execution throttle parameter to 256.
Scatter/Gather
(Microsoft® Windows NT, Microsoft® Windows® 2000, or Microsoft® Windows® 2003) Increase the general I/O performance by allowing larger data transfers. Do this by editing the “MaximumSGList” parameter in the registry. The recommended hexadecimal value is “ff.” The path is: HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/<name of HBA driver>/Parameters/Device/.
Shared Memory Error is displayed.
The CGI script manager may have not released a segment of shared memory.
This may occur when heavy I/O is happening at the same time you are accessing StorView. If this occurs you will need to stop and then restart the StorView Server service.
Symptom Reason Solution
Appendix B - Troubleshooting
Storview.book Page 153 Tuesday, September 23, 2003 5:11 PM
After switching drives and/or controllers from one storage solution enclosure to another, one of the solutions reports that the storage solution is being monitored by another host.
Multiple Configuration WWNs being used.
If you have been interchanging configured drives or controllers between storage solutions you may have a situation where multiple solutions are now sharing the same Configuration WWN. This can be corrected by changing the Configuration WWN value found in the Controller Parameters on either of the storage solutions. After making this change, all participating host systems will require a reboot. Refer to “Controller Parameters” on page 98.
Inadvertently pulled the incorrect drive from the enclosure and the array is dead.
Possible incorrect drive identification and removal.
If by mistake you remove a working drive member instead of the failed drive, this can cause the array to fail. In most cases you can simply re-insert that drive that was incorrectly removed and the array will return to the same state it was in prior to removing the drive.
For RAID 5/50 arrays, a drive failure will put the array in a critical state, if a hot spare was available the array should go into a rebuild mode. If you inadvertently remove one of the known good drives that is in the process of rebuilding, the rebuild operation will stop. Once you re-insert the incorrectly removed drive the array will return to the critical state and the rebuild process will start again. If you did not have a hot spare assigned, the array will be in a critical state. If you inadvertently remove a known good drive instead of the failed drive the array will change to a failed array state. Re-inserting that inadvertently removed drive will put the array back into a critical state. Replacing the failed drive will cause the array to begin a rebuild operation provided that you assign it as a hot spare or, if the Auto Hot Spare option was enabled the rebuild will begin automatically as the new replacement drive is installed.
Symptom Reason Solution
153
Appendix B - Troubleshooting
154
Storview.book Page 154 Tuesday, September 23, 2003 5:11 PM
(continued)
Inadvertently pulled the incorrect drive from the enclosure and the array is dead.
(continued)
Possible incorrect drive identification and removal.
For RAID 0 arrays, if you inadvertently remove a known good drive, the array will become dead. Once you re-insert the incorrectly removed drive the array will return to its working state.
For RAID 1/10 arrays, if you inadvertently remove a known good drive, the array will become failed. Once you re-insert the incorrectly removed drive the array will return to its previous state. If the array was critical, you can then replaced the known failed drive with a working drive and assign it as a hot spare and the array will begin rebuilding.
NOTE: For all arrays removing a drive as described above will cause all current processing I/O from the controller to stop. Any I/O in progress may have been lost or cause a corrupt file. Be sure to verify all data stored during this type of incidence to ensure data reliability.
Expanding Array is displayed as “Critical.”
Known issue and should be corrected in the next software release.
During an array expansion, the array remains in a fault tolerant state. Should a drive failure occur during the expansion the operation will continue until it has completed, then if a hot spare was assigned, a rebuild operation will begin automatically. If a hot spare is not assigned, replacing the failed drive with a known good drive after the expansion will cause a rebuild to start, assuming you have the Auto Hot Spare option selected in the Controller Parameters.
During the rebuild operation the array will be critical.
StorView displays a message: “No storage solution found.”
The host operating system is not able to see the storage solution.
Ensure that the Fibre devices appear in your HBA’s BIOS.
Ensure that you have the latest driver installed for your HBA.
Probe the SCSI enclosure to ensure that you see the solution.
Reboot the host and the storage system.
Symptom Reason Solution
Appendix B - Troubleshooting
Storview.book Page 155 Tuesday, September 23, 2003 5:11 PM
Password was changed, but cannot remember it.
Not applicable. Contact Technical Support for procedures to recover from this situation.
The controller’s IDs and/or Configuration WWN was changed and now there is a communication failure.
When you changed the controller IDs, a new nexus is established which requires the operating system and software to establish new communication paths.
If you are on Microsoft® Windows® 2000 or 2003, you can simply use the StorView “Rescan” feature to relocate the storage solution(s).
If you are running Microsoft® Windows NT® you will be required to reboot the host system.
During heavy data I/O, when I try to make a configuration change I get a failure saying that the controller is busy
The controller’s onboard resources are consumed.
Configuration changes during heavy I/O are not recommended. You can either wait until there is less data traffic or keep re-trying the command until it is successful.
I received the following message: “Lost communication with server. The server maybe down.”
During heavy host operations and/or data I/O, the system may become too busy to complete CGI requests from the GUI in the time allocated.
After several updated attempts have failed you will see this message. At this time you can try to use the Browsers’ refresh function to reload the StorView GUI. If that is unsuccessful, you may need to stop and then restart the StorView Server service. If you continue to receive that message, close the browser and wait until I/O traffic has settle down before opening the StorView GUI back up. You will still continue to receive email notifications and Event logging.
Symptom Reason Solution
155
Appendix B - Troubleshooting
156
Storview.book Page 156 Tuesday, September 23, 2003 5:11 PM
Index
Storview.book Page 157 Tuesday, September 23, 2003 5:11 PM
AAbout software version 29
Access Alignment 147
Access Size 147
Access Statistics 138
Activation code 8
Alignment 140
Alignment Statistics 139
Array 34
Array Status Icon 18
Audible Alarm Icon 20
Auto Hot Spare 66, 100
Auto Rebuild 100
Auto Update 100
Automatically UpdateController Firmware 103
BBackground Verification 100
Back-off Percent 39
Backoff Percent 34
Battery 96
Both PortsController Port 85
CCache Flush Array 34
Capacity of disk drives vi
Changing Password 26
Changing the Controller LUN 104
Check Parity 49
Chunk Size 34
Chunk size 38
Clear Controller Logs 103
Clearing the Configuration 58
Clearing the Event Log 116
Command Cluster Count 144
Command Cluster Interval 144
Command Cluster Statistics 143
Command Size 139
Components of GUI 16
ConfigurationCache 95Notification 59Restoring 57Saving 55Saving/Restoring/Clearing Overview 54
Configuration Icons 22
Configuration Name 95, 98
Configuration WWN 95, 98
Configuring Array Writeback Cache 42
Configuring for Email 23
Controller 127
Controller Environmentals 96
Controller EventBattery Failure 118Battery OK 118Cache Disabled 126Cached Data Lost 118Cntrl Temp Exceeded 118Configuration Changed 120Controller Failback Completed 119Controller Failback Started 119Controller Failed 119Controller Failover Completed 119Controller Failover Started 119Controller Firmware Upgraded 120Controller Powered On 119Controller Present 119Controller Removed 119Controller Reset 119Controller Selftest Failed 120Controller Selftest Passed 120Controller Shutdown 119
157
158
Storview.book Page 158 Tuesday, September 23, 2003 5:11 PM
Controller Timeout 119Controller Valid 119Event Log Cleared 120Fatal Coprocessor Error 120Fatal Drive FC Channel Error 120Fatal Host FC Channel Error 120Fatal SDRAM ECC 120Fatal Watchdog Error 120Flush Cache Completed 121Flush Cache Started 120Flush Mirrored Cache 120Flush Mirrored Cache Started 120Recovered SDRAM ECC Error 121Synchronization Completed 121Synchronization Started 121UPS Failure 121UPS OK 121Voltage Error 121
Controller Events 118
Controller Icon 17
Controller Information 94
Controller Log SES Events 100
Controller LUN 98
Controller Operations 102
Controller Parameters 98
Controller Port 95
Controller Port Connection 99
Controller Port Data Rate 99
Controller Port Events 127
Controller Port ID 99
Controller Ports 72
Controller Properties 93
Controller Settings 93
Controllers (C0/C1) Port 85
Co-Processor Status 97
CPLD Revision 94
Creating a LUN 70
Creating a LUN Mapping 84
Creating Arrays 33, 36
DData Access privileges 86
Data Rate 99
Dedicated Hot Spare 63
Deleting a LUN Mapping 88
Deleting Addressee 25
Deleting an Array 43
Different Node Name 99
Disk Arrays 33
Disk I/O Card Icon 20
Drive EventArray Critical 122Array Expansion Complete 122Array Expansion Restarted 122Array Initialization Complete 122Array Initialization Started 122Array Parity Check Canceled 122Array Parity Check Completed 122Array Parity Check Started 122Controller LIP 122Data Underrun 122Drive Busy 123Drive CC Failure 123Drive Inserted 123Drive Rebuild Failure 124Drive Status 124Drive Task Full 123, 124Drive Timeout 124Drive Timeout Failure 124Excessive Errors on Drive Loop 124FW Download Complete 126LIP-Drive Loop 125Loop Down 124Loop Error 124Loop Up 124New Drive Rebuild Failure 125Rebuild Aborted 125Rebuild Complete 125Rebuild Restarted 125Rebuild Started 125SES Initialized 129SES Initialized Level 1 125
Drive Events 122Not Available On Loop 126
Drive Identity icon 50
Drive Loop Status Icon 18
Drive Panel Settings 107
Drive Selection for RAID 5 Arrays 35
Drive StatusAvailable 18Critical 19Dedicated Spare 18Empty 18Failed 18Failed Array Member 19Hot Spare 18Initializing 18Locate 19Member 18Queued to Initialize 19Rebuilding 19Updating Firmware 19
Drive Status Icon 18, 19
Index
Storview.book Page 159 Tuesday, September 23, 2003 5:11 PM
EEmail Notification 23
Enclosure Icon 21
Enclosure Temperature Icon 21
Error Status 21
Event Logs 111
Execution Throttle 105
Expanding a LUN 79
Expanding an Array 51
Export Controller Logs 103
Exporting Logs 114
FFailed Drives 136
Fan Icon 19
Faster Rebuild 149
Features vii
Firmware Version 94
FlashController firmware 102
Free Space 68
GGlobal Access 2, 3
Global Hot Spare 61
Global Manager 3, 30
Global version 7
GUI 16
HHardware Pseudo-Driver 11
HBA Port WWN 84
HBA WWN 84
Help 28
Host EventCC to Host ID 123, 128Controller LIP 127Detected Power-on/Reset 127Host Port Incorrect Address 127Logged in at ID 127Loop Down 128Loop Up 128
Host I/O Card Icon 20
IIdentifying Drive Members 50
imageRAID Events 118
IndividualController Port 85
Information Status 21
Initialization 34
Initialize 39
Initializing Arrays 46
Installation 5
IP.db File 31
LLicense Managers 3
Local Manager 3
Local version 7
LUNExpansion 79
LUN Availability 67
LUN Capacity 71
LUN Mapping 81
LUN number 72, 86
LUN Segmentation 67
LUN Status Icon 18
LUNs 67
MMake Spare 108
Map to 85
Mapping Name 81
Missing 18
Modifying a LUN Mapping 90
Modifying Arrays 45
Modifying IP.db File 31
Monitoring initialization 41
Multicast 2
NNavigating 15
Navigating the Event Log 113
Node Name 81
Notes window 28
NotificationTips for Configuration changes 59
Numbering Convention vi
OOnline help 28
Operating System Event Log 117
Overview 1
PPassword 8
Performance Optimization 105
Index 159
160
Storview.book Page 160 Tuesday, September 23, 2003 5:11 PM
Pop-Up Assistance 28
Port Connection 99
Port Name 81
Power Supply Icon 20
RRAID 5 Sub-Array 148
RAID 5 Write Performance 145
RAID 5/50 Full Stripe Write Rate 144
RAID Controller Icon 20
RAID Level 0 34
RAID Level 1 34
RAID Level 10 35
RAID Level 5 35
RAID Level 50 35
RAID Levels 33
Read Commands Since Reset 138
Read Only Access 81
Read/Write Access 81
Read-Ahead Cache 40
Readahead Command Efficiency 142
Readahead Command Hit Rate 142
Readahead Statistics 141
Reads Statistics 138
Rebuild Priority 101
Remote login 3
Remote monitor 2
Remote StorView Servers Icon 17
Removing a Hot Spare 65
Removing StorView 13
Rescan 23
Reserve capacity vi
Reserved Capacity 34
Reserved capacity 39
Reset Controller 102
Resets/Power Cycles 95
Restoring the Configuration 57
Rewrite Parity 49
SSaving the Configuration 55
Scatter/Gather 105
segment 70
Sequential Access 146
Sequential Command Interval 141
Serial number 8
Server EventAll event logs cleared 133
Multicast address is not configured 132Multicast socket creation failure 132Serial and key are incorrect 133Server has been shutdown 132, 133Server has been started 132User has logged in 133User has logged out 133
Server icon is white 2
Server is missing 2
Server module 1
SES EventAlarm is ON 131Encl Alarm is OFF 131Encl Temp 27C OK 130Encl Temp 50C Warning 130Encl Temp 70C Critical 130, 131Fan Critical 129Fan OK 129Power Supply Critical 129Power Supply Not found 129Power Supply OK 129
SES Events 100, 129
Settings 23
Setup 5
Shutdown Controllers 103
Single Controller Mode 100
SMTP mail server 24
Software version 29
Spares 61
Starting StorView 15
Statistics 137
Status Icon 21
Storage Solution Icon 17
StorView Manager Console 15
StorView Server Events 132
StorView Server Icon 16
Stripe 35
Stripe Size 35
Sub-array 35
Synchronize Time 102
Synchronized logs 2
System Requirements 5
System rescan 23
TTech Support 27
Temperature 97
TerminologyArrays 34
Index
Storview.book Page 161 Tuesday, September 23, 2003 5:11 PM
LUNs 67SAN LUNs 81
Tips on Setting LUN Availability 73
Total SDRAM 95
Troubleshooting Assistance 4
Trust Array 60
UUnassigned Free Space 68
Unmonitored Icon 17
Upgrading License Managers 30
UPS 97
User Icon 17
User name 8
User Name and Password Screen 8
VVerify Parity 48
Viewing Hosts 82
Viewing LUN Mappings 83
Voltage 97
WWarning Status 21
Web server 1
Windows NT limitation 67
Write Cluster Rate 143
Write Commands Since Reset 138
Writeback Cache 40
Writes Statistics 138
Index 161
162
Storview.book Page 162 Tuesday, September 23, 2003 5:11 PM
Index
Storview.book Page 163 Tuesday, September 23, 2003 5:11 PM
Storview.book Page 164 Tuesday, September 23, 2003 5:11 PM
www.fel.fujitsu.com 91-9-94628001 (A)August 2003
Fujitsu Europe LimitedHayes Park CentralHayes End RoadHayes, Middlesex, England UB4 8FE44.208.573.4444