Académique Documents
Professionnel Documents
Culture Documents
Notices
The information in this document is subject to change without notice.
While every effort has been made to ensure that all information in this document is accurate, the Authors
accept no liability for any errors that may arise.
No part of this document may be transmitted or copied in any form, or by any means, for any purpose,
without the written permission of the Authors.
Issue 1.0
Acknowledgments
Microsoft Windows 2003 is a registered trademark of Microsoft Corporation
StorView is a registered trademark of Xyratex.
ii
Contents
Contents
Preface ................................................................................................................................................. vii
License Agreement ............................................................................................................................... vii
Related Documentation ....................................................................................................................... viii
Revision History ................................................................................................................................... viii
1
Introduction ..................................................................................................................................... 1
1.1 Overview ..................................................................................................................................... 1
1.2 Inter-Server Communication ....................................................................................................... 1
1.2.1
Multicast ............................................................................................................................. 1
1.3 License Manager ......................................................................................................................... 2
1.3.1
Access License Limits ........................................................................................................ 2
1.3.2
Feature License .................................................................................................................. 3
iii
iv
45
45
45
46
48
48
54
55
56
57
57
58
60
61
62
65
65
69
69
69
70
72
72
73
73
74
77
78
81
81
81
83
83
83
83
91
91
91
92
94
96
Contents
149
150
151
151
157
158
159
164
166
169
173
175
175
15 Statistics ......................................................................................................................................
15.1 Overview .................................................................................................................................
15.2 Access Statistics .....................................................................................................................
15.3 Command Size - Alignment Statistics .....................................................................................
15.4 Read-Ahead Statistics .............................................................................................................
15.5 Command Cluster Statistics ....................................................................................................
177
177
178
179
181
183
185
185
186
186
186
186
187
188
188
188
195
195
195
196
197
197
197
198
198
198
199
199
199
199
vi
Preface
Preface
What is in this guide
This user guide gives you the step-by-step instructions on how to setup and use the StorView Storage
Management RAID Module software.
Who should use this guide
This user guide assumes that you have a working knowledge of storage appliance products. If you do not
have these skills, or are not confident with the instructions in this guide, do not proceed with the
installation.
License Agreement
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 apache@apache.org.
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
vii
Related Documentation
StorView Storage Management Software Installation Guide (P/N 90377-01A)
RS-4835-F4-5404E Quick Start Guide (P/N 80449-01A)
RS-4835-F4-5404E & RS-4835-E3-XPN Installation and User Guide (P/N 80448-01A)
RS-1220-F4-5412E Quick Start Guide (P/N 90506-01A)
RS-1220-F4-5412E & RS-1220-E3-XPN Installation and User Guide (P/N 90505-01A)
RS-1220-F4-5402E Quick Start Guide (P/N 78603-03A)
RS-1220-F4-5402E & RS-1220-E3-XPN Installation and User Guide (P/N 72814-04A)
RS-1220-E3-5412E Quick Start Guide (P/N 90509-01A)
RS-1220-E3-5412E & RS-1220-E3-XPN Installation and User Guide (P/N 90508-01A)
RS-1220-E3-5402E Quick Start Guide (P/N 82903-02A)
RS-1220-E3-5402E & RS-1220-E3-XPN Installation and User Guide (P/N 82904-02A)
F5404E VT-100 RAID Configuration Utility User Guide (P/N 90255-01A)
F5412E VT-100 RAID Configuration Utility User Guide (P/N 90507-01A)
F5402E VT-100 RAID Configuration Utility User Guide (P/N 80226-03A)
E5412E VT-100 RAID Configuration Utility User Guide (P/N 90510-01A)
E5402E VT-100 RAID Configuration Utility User Guide (P/N 83249-02A)
Revision History
viii
Version
Date
Description of Change
1.0
March, 2007
New Release.
Introduction
Chapter 1
Introduction
1.1 Overview
StorView Storage Management software is a full-featured graphical HTML-based software suite
designed to configure, manage, and monitor storage subsystems. StorView is built on a modular design
and currently supports the RAID Module. Other modules available in the future are separately
documented.
The RAID Module provides an extensive set of configuration and management tools. StorViews RAID
Module is available in two versions: host-based and embedded. The host-based version is installed on
the host computer system, while the embedded version is installed on the RAID Controller.
StorViews server component discovers storage solutions, manages and distributes message logs, and
communicates with other server components installed on the same local network and external subnet
networks. StorView has an HTML-based front end, accessed with a web browser, and provides the
interface to the end user.
StorView incorporates web server software as part of the installation, Apache 2.0, which provides the
interface between the server component and HTML interface. During installation the web server is
automatically configured and requires no further management.The installation of the web server software
is self contained and will not conflict with other web server software currently installed on your system.
All packets sent to the multicast address remain in the local network, unless an explicit server IP address
outside the subnet is added in the Inter-Server Communication Explicit StorView Server IPs >
Preference Settings, see 4.7 Monitoring Settings beginning on page 37. The inter-server
communication abilities provide StorView with remote monitoring of other installations of StorView and
their monitored storage solutions.
StorView has the ability to communicate with any StorView installation on the local network. These other
StorView servers 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 servers monitored storage solution. They
indicate the status of a monitored server storage solution, by the server icon changing to one of a few
different states, see 2.1.4 Server Sidebar and Top Section beginning on page 17.
Each server sends a check-in packet in 10 second intervals. Once an initial check-in packet is received,
all StorView servers will know the existence of the other servers. If a server fails to send three 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 server service that owns the monitored storage solution is down for any reason and three
check-in packets are not received, the monitoring will automatically be transferred to another StorView
server.
Introduction
Figure 1-1
A limited free license is included with the system that allows for one (1) Overwrite Data Area (ODA) to be
created. Or you can purchase a full license which provides for up to eight (8) Overwrite Data Area (ODA)
to be created. With the limited free license, you can have up to four Snapshots for the single ODA. With
the maximum full license you can have up to twenty-four Snapshots for each of the eight ODAs. Each
ODA is paired to a physical Logical Drive allowing the user to create up to 4 or 24 Snapshots of their
logical drives, depending on the license.
Figure 1-2
A licensing upgrade path to the maximum full feature license is provided from the License Information
screen. To upgrade, you will need to provide your Configuration WWN and Serial Number for the specific
feature to obtain a license key. The serial number is found on the label affixed to the license certificate.
You will find the Configuration WWN displayed in the License Information window.
Below is an explanation of the fields of the licensing information window.
Figure 1-3
Once your license key is entered, click the Submit License Key button and the current licensing
information is displayed (Figure 1-4).
Figure 1-4
License Upgraded
If you attempt to exceed the limited license you will receive a message. You will have the option to
upgrade the Limited Free license from that screen. Click the UPGRADE LICENSE button and enter a
new license key to enable the maximum license. Or you may upgrade any time by clicking the Controller
icon and then the LICENSE INFORMATION button. (Figure 1-5)
Figure 1-5
Quick Tour
Chapter 2
Figure 21
Note
Throughout the interface, holding the mouse pointer over an icon will display a pop-up window with
information specific to the object.
Tool Bar Button
Description
Storage Assistant
This button will start the Storage Assistant wizard which will
automatically configure your storage system based on user inquiries.
Create Array
This button will open the Create Array window allowing the user to
create new disk arrays.
Create Logical
This button will open the Logical Drive window allowing the user to
create new logical drives.
SAN Mapping
This button will open the SAN LUN Mapping panel which allows the
user to further customize logical drive availability.
Quick Tour
Description
Advanced Settings
This button opens a window from which you may change controller
parameters.
Archive Configuration
This button will open a window from which you may choose to save,
restore, or clear the configuration. Note when deleting a
configuration, this will delete all arrays and logical drives as well as
the data on those logical drives.
Figure 22
Figure 23
Enclosure Section
These icons appear on the front of the enclosure on the Main screen
and provide an instant view of the status of disk drives as well as drive
location and clicking the icon will open the Drive Information window.
Member
Available
Dedicated Spare
Empty
Missing
Initializing
Quick Tour
Enclosure Section
Locate
Critical
Updating Firmware
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
Expanding
Verifying
Unsupported
Enclosure Section
Fan Icon
(RS-1220 Enclosures Only)
Normal
Fan 1 Failed
Fan 1 Failed - One fan in the fan module has failed. The fan
which failed will be indicated on the icon.
Fan 2 Failed
Fan 2 Failed - One fan in the fan module has failed. The fan
which failed will be indicated on the icon.
Failure
Failure - Both fans in the fan module have failed or the cooling
fan module has been removed.
Failure
Missing
Unknown
Warning - To be determined.
Warning
Failure - To be determined.
Failure
Unknown
Missing
10
Quick Tour
Enclosure Section
Error
Empty
Empty - This icon represents the empty controller slot for future
expansion. A blank plate is shown.
Error
Empty
Empty - This icon represents the empty controller slot for future
expansion. A blank plate is shown.
Error
Empty
Empty - This icon represents the empty controller slot for future
expansion. A blank plate is shown.
E5402E/E5412E RAID
Controller
Normal - RAID Controller is operating normally.
Normal
Error
Empty
Error
Missing
Empty
11
Enclosure Section
Missing
Empty
On
Mute
Disabled
Warning
Failed
Missing
Missing - This icon indicates that the information from the SES
regarding the sensors is invalid or missing.
Rear view enclosure icons are displayed at the bottom of the main
screen and will change shades according to enclosures state, as well
as the state of the individual components. The enclosures are labeled
above each front view to aid with identifying them in a multiple
enclosure environment.
Normal - All components are operating normally.
12
Quick Tour
Enclosure Section
13
Enclosure Section
14
Quick Tour
Figure 24
Red (Error)
These icons are found in the Array section and depict the current
state of the specific component.
Green - Status is ok.
Yellow - Indicates a drive component in a RAID 1, 10, 5, 6 or
50 array has failed and the array is no longer fault tolerant, or
the array is in a rebuild cycle.
For RAID 6 arrays, it indicates 1 or 2 drives have failed. See
Drive Status Icon Critical state.
Red - Indicates an array is invalid or offline due to an 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 6 = Three drives have failed.
RAID 50 = Two drives have failed within the same sub-array.
15
Green (Normal)
Yellow (Warning)
Red (Error)
16
These icons are found in the Logical Drive section and depict the
current state of the specific component.
Normal
ODA is OK.
Warning
Failed
The ODA has run out of space. All snapshots are invalid. In
order to resume operations, delete all snapshots.
Quick Tour
Figure 25
Server Section
These icons will appear on the Server Sidebar section on the Main
screen. They depict the current server and discovered servers. The
icon will indicated the status of the server components by changing
its color and state.
Normal
Normal
Warning
Error
17
Server Section
You will also see the warning !, error, and unknown icons for
unfocused storage solutions that are being monitored as well.
Normal Gray - Status is ok.
Flash Yellow with red ! - Indicates a component in the storage
solution is in degraded mode.
Error
Unknown
Normal
Normal
Error
Module Tabs
RAID Module
18
The tab appears at the top of the Main window and when selected will
focus the monitoring and management functions to specific systems
types. This tab will flash yellow if a warning condition occurs and red
if an error condition occurs.
Quick Tour
19
20
Chapter 3
Embedded StorView
Setup
3.1 Embedded Network Settings
Note
If you are using the host-based version of StorView, you may skip this chapter.
After completing your hardware set up, ensure you have a shielded Cat 5 or better Ethernet cable
connected to the controllers networking port (StorView Embedded Module port (RJ-45)) and your
network hub or host computer Ethernet port. If your connecting to the network hub use a standard
Ethernet cable, if your connecting to your host port use a cross-over Ethernet cable. The first time you
start embedded StorView, you must configure the network settings.
Upon start-up, embedded StorView looks at the user Preferences Settings to determine if an IP address
exists. If one is defined it will initialize the network interface using that IP address.
In the event an IP address is not defined, it attempts to get a DHCP IP address. You will need to contact
your network administrator for the IP address assigned by the DHCP server. To identify the new IP
address lease, one can look for esv0 or esv1 in your DHCP Manager software.
If an IP address cannot be determined, the software will use a default IP address of 10.1.1.5 for
Controller 0 and 10.1.1.6 for Controller 1. If your network does not have a DHCP server, then set the
host IP address to 10.1.1.20 and the subnet mask to 255.0.0.0 and run the wizard again. If an error is
encountered, the embedded StorView Server will have the IP address of 10.1.1.7 assigned to it.
A tool is provided to configure new embedded StorView modules. From a Windows platform, it is
accessed via the Embedded StorView Setup Wizard link on the disc navigation menu and on Linux it is
accessed via a command line executable.
21
Even if a configuration is created with arrays and logical drives but the login name and password have
not been changed, it will still be considered an uninitialized system. During the process of configuring an
embedded module, you will be required to enter a new password and confirm that password. The
default password is the word password.
The embedded module is identified by its MAC and IP address. It may be more helpful during setup to
configure one embedded module at a time. You will find the MAC and IP address by accessing the VT100 RAID Configuration Utility, selecting Diagnostics then choosing StorView Embedded Module
Support. Select Enter StorView Embedded Module Menu Mode and choose View Network Settings.
1
Insert the Software and Manuals Disc into your CD drive. The autorun program will automatically start
the navigation menu.
Click the Embedded StorView Setup Wizard link to begin the configuration.
You are presented with a Welcome screen and instructions to proceed. Review the information and click
the Next button.
Figure 31
4
Welcome Screen
Figure 32
Searching Screen
Those embedded modules with their default password intact will be displayed with their MAC address in
an Uninitialized list window. If all discovered embedded modules have had their default passwords
changed, then you will be taken to the Initialized screen.
22
From the Uninitialized screen, select the MAC address of the embedded module you wish to configure.
If you wish to use a DHCP server to assign your IP address, click the check box Use DHCP.
If you wish to manually configure your network setting, enter the correction information in the appropriate
fields.
Enter a new password and confirm the new password. Click the Configure button.
Figure 33
7
Configuration Screen
If you have additional uninitialized embedded modules, select the next MAC address and choose the
appropriate settings from the previous steps.
Once you have completed configuring all the uninitialized embedded modules and have clicked the
Configure button, the wizard will display a pop-up message indicating all systems have been configured.
It will then re-scan for uninitialized systems and if none are found, you will be taken to the Initialized
screen. If someone plugs in a uninitialized system to the network (same subnet mask) during the time of
the rescan or resets a systems password back to the defaults, you will be taken to the Uninitialized
screen again.
Select the MAC address of the embedded module you wish to start and click the Launch StorView button.
StorView will start up.
Figure 34
9
Launch Screen
Your web browser will open with a login screen. Enter the login name and new password then click OK.
The StorView Main screen will open.
23
Log in as root.
Follow the on screen prompts. At the conclusion of the setup you will be instructed on how to proceed.
StorView will start within your web browser.
Note
Host-based StorView is started by launching your web browser and entering the IP address of the local
host followed by :9292. For more information, refer to the StorView Storage Management Software
RAID Module Users Guide.
Click the SETTINGS button on the Main screen and select the PREFERENCES tab.
The StorView Server Name field will have a default name, esv0 for Controller 0 and esv1 for
Controller 1. If you wish to change this name, enter the desired name for this embedded StorView server.
Note
If the StorView server name displays esverr, this indicates a problem with the embedded StorView
server module. Contact technical support.
Figure 35
24
3.1.3.1
Note
3.1.3.2
Using Static IP
To manually configure the network interface setting:
Enter the desired IP address in the IP Address field and press the <Tab> key or click in the Subnet Mask
field.
Enter the desired Subnet Mask in the Subnet Mask field and press the <Tab> key or click in the Default
Gateway field.
Enter the desired gateway or router address and press the <Tab> key or click in the DNS Server field.
25
26
Getting Started
Chapter 4
Getting Started
4.1 Starting StorView
Host-based StorView is started by opening your web browser software and entering the IP address of
the host attached to the storage system followed by the port number. The URL format will be either
HTTP://<your_IP_address>:9292, HTTP://127.0.0.1:9292 or HTTP://localhost:9292.
Note
For Microsoft Windows users, you may also launch StorView via the Start Menu. Click the Start button
and select Programs, then choose StorView and select StorView Manager Console. Your web browser
will open with a login screen.
To use Secure Web Proxy (Secure Mode) enter the following URL: HTTPS://127.0.0.1:9393, HTTPS:/
/localhost:9393, or HTTPS://<your_IP_address>:9393. A secure browsing lock icon will appear on the
web browser window.
Note: For Microsoft Windows Internet Explorer, be sure you have checked the box for Use SSL
2.0 under the Internet Options > Advanced > Security settings.
Embedded StorView is started by opening your web browser and entering the explicit IP address
assigned to the embedded StorView server followed by the port number (e.g., HTTP://10.11.48.120:
9292). For more information on how embedded StorView performs its network initialization and how to
set the network parameters, see 3.1 Embedded Network Settings beginning on page 21.
For specific information on the Feature License and upgrades, refer to section 1.3.2.
27
If a remote login is attempted from another host system on the same network and you do not have a
global license, you will see a message displayed regarding this. You will have the option to upgrade your
license by entering your serial number and activation code. You can also upgrade your license from the
Other Servers section by clicking on the link in the notice displayed or the upgrade can be accessed by
clicking the Settings button (E-MAIL tab, default, presents an upgrade option when using a local or
remote access license).
Note
1
License
Features
Version
Local Access
Host-based
Remote Access
Embedded
Global Access
Refer to your disc envelope to obtain the serial number and activation code.
Click on the link provided under Other Servers. The Settings window will open with the E-MAIL tab
selected. There you will enter the required information and click the Activate button.
Figure 41
Once you have completed the upgrade, the window will reload with the E-MAIL, SYSLOG, and SNMP
tabs active. Click on the CLOSE button in the confirmation window.
You can verify the change by clicking the About button and noting that it now displays (Global), see
12.5.1 About beginning on page 135.
Also the notice displayed under the Other Servers section will now be removed and any remote
discovered StorView Servers will be displayed.
28
Getting Started
4.3 E-MAIL
4.3.1 Configuring E-Mail Notices
With a Global license installed, StorView provides you with the ability to establish up to ten E-Mail
addresses where notices of events can be automatically sent.
To configure the E-Mail notifications perform the following:
1
Figure 42
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.
Enter the user E-Mail addresses. You may add up to ten (10) E-Mail addresses.
Type the full E-Mail address, and click one or more of the check boxes for the type of event to which the
user is to be notified. The types of events are: Information, Warning, and/or Error.
Information
Warning
Error
29
If you have more than five E-Mail recipients, you will need to click the button 6 - 10 to access the next
five address blocks.
5
From the Main screen click on the SETTINGS button. The SETTINGS window will open with the E-MAIL
tab selected.
Figure 43
30
Click the DELETE button next to the E-Mail Address name you wish to remove. The address is
immediately removed.
Click the APPLY button to make the changes effective and a status pop-up notice will appear. Click the
CLOSE button. Then click the CLOSE button on the SETTINGS window.
Getting Started
4.4 SNMP
4.4.1 Configuring SNMP Traps
StorView can be configured to send SNMP traps to any network management system. These traps carry
all the information that appears in the log entries for each level of severity.
Note
If your system requires a MIB file, it is located in the following directory C:\Program Files\StorView\alertssnmp.mib.
All SNMP traps sent from StorView will be received by the host SNMP Servers designated in the settings
window for the specified port and community.
Enter the SNMP Server name or IP address of the host you wish to receive SNMP traps.
Enter the IP port on which the SNMP Server expects to receive traps. The default is 162.
Enter the Community to which the traps belongs. The default is public.
SNMP Servers may belong to several different communities or receive packets for different communities.
Select the level of events you wish to be included in the traps. You can select from Information, Warning
and Error types. For more information, see Event Logs beginning on page 143.
Figure 44
31
You will receive a confirmation message that the test was successfully completed, and each addressee
will receive a Test Message. Click the CLOSE button.
9
32
Click the DELETE button next to the SNMP Server you wish to remove. The server is immediately
removed.
Click the APPLY button to make the changes effective and a status pop-up notice will appear. Click the
CLOSE button. Then click the CLOSE button on the SETTINGS window.
Getting Started
4.5 SYSLOG
StorViews SYSLOG agent is a module designed for StorView that enables sending RAID system event
logs to all listening SYSLOG clients on all installed platforms.
SYSLOG requires that the Global Access license be enabled before the feature is activated. Once
activated on each installation of StorView, the locally monitored storage system events are then sent to
the SYSLOG daemon running on the host system.
StorView SYSLOG is designed for greater flexibility in that it supports many-to-many mapping. You may
have:
Multiple SYSLOG servers that monitor a single RAID storage system for event logs.
A single SYSLOG server that monitors multiple RAID storage systems for event logs.
Multiple SYSLOG servers that monitor multiple RAID storage systems for event logs.
This many-to-many mapping provides an additional safety net in that it offers data redundancy. In this
instance a failed SYSLOG server will not have any impact if another SYSLOG server is functioning
normally.
If you are using a Linux operating system, the syslogd daemon is a component of your operating system.
If you are using a Windows operating system you will need to install a separate tool (http://syslogwin32.sourceforge.net/) which runs as a Windows service.
33
If you have not yet enabled the Global Access license please do so at this time, see 4.2 Upgrading the
Access License beginning on page 27.
After activating the Access license, you will see the following screen when the SYSLOG tab is selected.
The following fields are described:
34
Field
Description
SYSLOG Server
SYSLOGD Port
Allows the user to enter a specified SYSLOG port. The default port
is 514. An error message will appear if the enter is invalid or left
blank. The range of port IDs are: 1 - 65535.
Information (I)
Warning (W)
Error (E)
Delete Button
Clicking this button clears the previously entered IP address for the
selected line and resets the check boxes to their default state.
Test Button
Enter the port ID of the recipient SYSLOG server. You must enter a correct value otherwise you will
receive an error message.
Getting Started
Figure 45
If you are finished completing the setup, click the CLOSE button on the SETTINGS window.
Click the DELETE button next to the syslogd server you wish to remove. The server name is
immediately removed.
Click the APPLY button to make the changes effective and a status pop-up notice will appear. Click the
CLOSE button. Then click the CLOSE button on the SETTINGS window.
35
Figure 46
Note
Type in the Old Password and press the <Tab> key or click in the next text box.
Type in the New Password and press the <Tab> key or click in the next text box.
6
Note
36
Getting Started
The Monitoring Settings are disabled with the Remote license, you must upgrade to a Global license to
enable these features.
From the Main screen click on the SETTINGS button, then click the PREFERENCES tab.
Click the pull-down menu for Select Monitoring Group and choose Group 1, Group 2, or Group 3. Group
1 is port 9191, Group 2 is port 9192, and Group 3 is port 9193.
Figure 47
Figure 48
Click the APPLY button to make the changes effective, then click the CLOSE button. Click the CLOSE
button on the SETTINGS window.
37
Enter the IP address in the Individually Monitored Servers field of another StorView server outside the
subnet and click the ADD button.
Add additional explicit IP addresses of any other StorView server you wish to include to receive packets
that is outside the subnet and click ADD button. Otherwise, skip to step 5.
Under the Individually Monitored Servers section, select the Server IP Address you wish to delete and
click the REMOVE button.
Figure 49
38
Click the APPLY button. A confirmation window will appear, click the CLOSE button.
Storage Assistance
Chapter 5
Storage Assistant
5.1 Assisted Automatic Configuration
Note
If you will be manually configuring your disk array, hot spare drives and logical drives, skip this chapter.
The StorView Storage Assistant is a wizard like feature that will automatically configure your storage
system after it has obtained some brief information from the user.
To begin, click the Storage Assistant icon on the Tool Bar located on the Main screen.
Figure 51
2
39
The name is used to identify this storage solution. You may use up to 64 characters, although only the
first 25 characters are displayed.
Figure 52
3
Note
At any point you can click the PREVIOUS button to move back one screen and make any necessary
changes.
Select a host server connection for this storage from the list of detected connections. Enter a name for
this server connection and click NEXT. Enter a name for the logical drive or use the default name.
Figure 53
40
Storage Assistance
Figure 54
5
Figure 55
41
After you have selected a specific drive type and created the logical drive(s) with those disks, you can
then click the PREVIOUS button to create another logical drive using the drive type not yet selected.
Or, you can alternate back and forth between selecting a disk type and creating logical drive(s).
Figure 56
6
Enter the capacity for the logical drive (GBs), or you may use the default capacity. The value is expressed
in GBs.
Click the check box next to the named server connection(s) displayed in the Server Connection(s) pane.
Click the ADD button. The Logical Drive is added to the summary window at the lower section of the
window.
Figure 57
Note
42
Repeat steps 4 - 6 for each additional Logical Drive you wish to create and assign to a server.
Storage Assistance
Figure 58
If you decide that a Logical Drive you added is not desired, you may remove it from the list by clicking the
REMOVE button next to the Logical Drive name in the Configuration Summary window.
If you have used up all the available capacity, the fields will gray out and the available capacity will display
0 GB in red.
8
You are presented with a summary of your selections. Click the APPLY button.
The Storage Assistant will begin configuring the storage solution.
Figure 59
43
This completes the configuration of your storage solution. Before you bring the storage system online and
into service, we recommend that a backup copy of the configuration be made, see 6.6 Saving the
Configuration beginning on page 65.
44
Chapter 6
Configuring a Storage
Solution
6.1 Creating Disk Arrays
Configuring a storage solution requires some planning to ensure that you define the correct RAID level
and array options, hot spares and logical drives for your solution requirements.
This chapter will step you through the process to configure and manage your disk arrays, assign hot
spares and create the logical drives. You should have a basic understanding of RAID concepts.
16
16
16
6*
16
50
16
10
16
RAID 6 supports only the following drive configurations: 6 (4 data drives + 2 parity drives), 11
(9 data drives + 2 parity drives), 12 (10 data drives + 2 parity drives), and 16 (14 data drives
+ 2 parity drives).
45
6.1.2 Terminology
The following describes some of the terminology used when creating disk arrays and logical drives.
Term
Description
Array
Back-off Percent
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, 6, and 50 disk arrays must have consistent parity before they
can be used to protect data. However, StorView will initialize all array
RAID types regardless. If the user chooses the Trust option during
array creation or stops the initialization, the array will be trusted. Note
that any drive failure in a trusted array will result in data corruption.
It is possible to perform the initialization later. This recalculates the
parity based on current data, ensuring data and parity are consistent.
46
Each logical drive is presented to the host system with a unique LUN.
In certain cases (such as after deleting another logical drive) it may be
desirable to change the number that a logical drive 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
to the logical drive.
RAID Level 0
Term
Description
RAID Level 1
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 6
RAID Level 10
RAID Level 50
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
Sub-array
The controller keeps a map of all the space that is not assigned to any
logical drive. This space is available for creation or expansion. Each
unassigned region is individually listed.
47
Figure 61
48
Figure 62
The Create Array window will open, see Figure 63 Create Array Window (RS-4835-F4-5404E Shown)
beginning on page 49.
2
Select drives to include in your array. Click on each drive that has the Available icon displayed. The icon
will change to Selected.
As you select drives, the projected size of the array is displayed in the upper right corner of the window.
Note
You will notice numbers next to each item on the screen. These are the suggested sequential steps to
follow when creating an array.
Figure 63
49
Figure 64
Enter a name for your array. You may use up to 32 characters (ASCII).
Note
The Notes section under the Available Drives section will display information to help you with drive
selection. (Figure 66)
Note
If you choose RAID Level 6 but the incorrect number of drives, you will see the following warning
message when you click the CREATE button. Click OK and choose the correct number of disk for the
particular RAID level.
Figure 65
50
Figure 66
5
Choose the chunk size. Click the pull-down menu and select a chunk size (64K, 128K, or 256K).
Chunk size is the amount of data that is written on a single drive before the controller moves to the next
drive in the stripe.
For RAID level 0, 1, or 10, choose the correct size from the tables below. For RAID 5/50/6, refer to the
note below.
Note
To achieve optimum RAID 5/50/6 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/6 arrays, for detailed
information see Optimizing Write Performance beginning on page 185. For optimum performance, you
want to do as many full stripe writes as possible.
Note
The controller firmware will automatically set the chunk size if a smaller chunk size is selected than the
value recommended for the number of drives and specified RAID level.
RAID 0
Number of Drives
4+
256K
256K
128K
64K
RAID 10 (0+1)
Number of Drives
8+
256K
256K
128K
64K
Select to Initialize the array. The default setting is to initialize, so you will just verify this setting. If it is not
set, click the pull-down menu and choose Initialize.
51
Initialization will begin automatically in the background once the array is created. You will have an option
to stop or pause the initialization from the Main screen. If you Stop an initialization, the array will be
trusted, see note below. As you create additional arrays, they too will begin initializing. The maximum
number of arrays that can be initialized in parallel is sixty-four (64).
Note
The Trust Array option should only be used in very special circumstances, see 10.2.7 Trust an Array
beginning on page 108.
Choose the Back-off Percent (reserved capacity) for the drives. The default is 1%.
This determines how much drive capacity to reserve for future capacity expansions or to enable
replacement drives of greater capacity sizes to be used.
Note
The back-off percent option is not applicable to non-redundant array types. A RAID 0 array is a nonredundant type of array and gains no benefit from establishing a reserve capacity.
Set the Read-Ahead Cache threshold.
The choices are automatic, disabled, and four pre-determined sizes (256KB, 512KB, 1 MB, and 2 MB).
Selecting Automatic, which is the recommended and default setting, allows the controller to determine
the optimum size. Selecting Disabled will turn off the Read-Ahead Cache. Select from one of the predetermined sizes to optimize the read performance based on your data patterns.
52
10
11
You will see a confirmation message that the array was successfully created, click the CLOSE button.
12
Click the CLOSE button at the bottom of the Create Array window.
Figure 67
While monitoring the array initialization, under the Array name a progress bar appears displaying the
percent complete. Also, in the enclosure front view, the disk drives being initialized display an animated
icon indicating their present status.
You can stop or pause the Initialization process if you wish by clicking on the link located to the right of
the progress bar.
Stopping the initialization will cause your array to be trusted. If you stop the initialization, you want to
return at a later time, but before you being to use the array in a live environment and initialize the array,
see 6.3 Initializing the Array beginning on page 55.
Pausing the initialization will halt the process until the resume option is selected. You can change the
amount of processor time that is dedicated to the initialization for better initialization performance, see
9.2.2 Fault Tolerance beginning on page 94.
53
54
A trusted array does not calculate parity across all drives and therefore there is no known state on the
drives. As data is received from the host parity is calculated as normal, but it occurs on a block basis.
There is no way to guarantee that parity has been calculated across the entire stripe. The parity data will
be inconsistent and so a drive failure within a trusted array will cause data loss. Before you use a trusted
array in a live environment, you must initialize it.
Locate and click on the <Array_Name> in the Array section on the Main screen you wish to initialize. This
will open the Array Information window.
Figure 68
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 message appears indicating the success of the operation, click
the CLOSE button.
55
Figure 69
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 the Stop link located to the right of the
progress bar.
6.3.1.1
1
Pause Initialization
Click the PAUSE link located just to the right and below the progress bar.
The Pause link will change to Resume and the progress bar will stop its forward motion.
6.3.1.2
1
Resume Initialization
Click the RESUME link located just to the right and below the progress bar.
The initialization will continue from the point where it was paused.
56
From the Main screen, click a drive icon within the enclosure front view indicating Available that you
wish to make a global hot spare.
Figure 610
Note: There must be at least one drive online and available that meets the rules from above to be
assigned as a hot spare, and a configuration must exist (at least one array defined).
57
From the Drive Information window, click the MAKE SPARE button.
Figure 611
3
A pop-up window will appear, select Global Spare from the drop down menu.
Figure 612
Click the CREATE button. You will see a confirmation window indicating the process was successful,
click the CLOSE button.
58
From the Main screen, click a drive icon in the enclosure front view indicating Available that you wish
to make a dedicated hot spare.
Note: There must be at least one drive online and available that meets the rules for spare drives
on page 57 to be assigned as a hot spare, and a configuration must exists (at least one array
defined).
2
From the Drive Information window, click the Make Spare button.
Figure 613
3
A pop-up window will appear, click the drop-down menu and select the array to which you wish to assign
the dedicated spare.
Figure 614
Click the CREATE button. A confirmation window will appear indicating success, click the CLOSE button.
Note
Only arrays that the spare drive is large enough to replace any member drive of that array or of the same
drive type will be displayed in the pull down menu. For example, if you have two arrays one created using
500 GB drives (array 0) and one using 750 GB disk drives (array 1). If you have a 500 GB spare drive
that you attempting to assign to an array, only Array 0 will be displayed because the drives in array 1 are
of equal or lesser capacity drives then the spare. However, if you have a 750 GB spare drive both Array
0 and Array 1 will be displayed since the 750 GB spare is equal to or greater than any drive in either array.
59
From the Main screen, click on a disk drive labeled Dedicated or Global in the enclosure front view
that you wish to remove as a spare. The Drive Information window will open.
Figure 615
60
Click the REMOVE SPARE button. A confirmation window will appear indicating success, click the
CLOSE button.
To enable this feature, click the Advanced Settings icon on the Main screen Tool Bar. The Advanced
Settings window will open.
Place the mouse pointer on the check box next to the Auto Spare parameter and click to place a check
mark enabling the feature.
Figure 616
Click the APPLY button and click the CLOSE button on the confirmation window when it appears.
61
From the Main screen click on the Create Logical icon in the Tool Bar.
Figure 617
62
Select the region or regions you wish to use for your logical drive from the list Select Which Array(s) to
use window. You may hold the <Shift> or <Ctrl> key down to make multiple selections.
Enter a name for your logical drive, you may use up to 32 characters. The default names for logical drives
follow the format LDx. Only 12 characters plus an ellipse is displayed when the name is longer. Holding
the mouse pointer over the logical drive name on the Main screen will show the complete name in a
popup.
Figure 618
4
Figure 619
Important
If you intend to make your Snapshots available as logical drives (Virtual LUNs (VLUN)), you must
SAN LUN Map all logical drives. That includes regular logical drives and the snapshot logical
drives. Any settings made in the Create Logical Drive screen regarding Availability will be
overridden by the SAN LUN Mapping process.
Choose the desired Block Size. (With this release only the 512 byte block size selection is available. No
change is required here.)
Select the LUN number for the logical drive from the Mapped to drop down menu.
63
Select the Controller Ports you wish to make the logical drive available through. Place a check mark next
to the desired controller ports displayed.
The choices are: C0P0, C0P1, C1P0, and/or C1P1. Where C0 represents the left or lower controller and
C1 represents the right or upper controller, and P0 indicates the port marked Host 0, FC Host 0, or IN 0,
and P1 represents the port marked Host 1, FC Host 1, or IN 1 on each controller. There is a one-to-one
relationship between the controller port selected and a data cable connected to that port. Ensure that the
ports you select are properly cabled.
You may continue to create more logical drives or exit by clicking the CLOSE button.
In most storage system environments, creating the logical drives, assigning them their logical unit number
(LUN) and setting the availability is sufficient to meet the requirements for setup. For more advanced and
complex systems using storage area networks you may wish to perform the more advanced SAN LUN
Mapping, see SAN LUN Mapping beginning on page 69. Otherwise access your operating system to
make the new drives available for use.
64
If you cannot restore the configuration exactly as it was, you will not be able to restore access to the data
and it will be lost.
From the Main screen Tool Bar click the Archive Configuration icon.
Figure 620
Click the SAVE button. You may click the CLOSE button to cancel and return to the Main screen.
65
Figure 621
3
Click the DOWNLOAD button to continue with saving the configuration file, or click the CANCEL button
to cancel.
Figure 622
4
66
You are presented with the browsers standard File Download screen. Click the SAVE button to
continue, or CANCEL to quit.
Figure 623
5
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.
Figure 624
6
After a successful download, you will see a confirmation window. Click the CLOSE button.
67
68
Chapter 7
7.2 Terminology
The following table describes the terminology relating to StorViews SAN LUN Mapping.
Term
Description
Node Name
HBA Port Name (Port Name) This is an eight byte hexadecimal number, uniquely identifying a single
host HBA 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
Read/Write Access
This notation marks a logical drive that has been mapped to another
Host HBA Port, but is available to be mapped to the selected Host HBA
Port. It will be displayed when the condition above has occurred and
appears in the Logical Drive pull-down menu selections. The logical
drives with other mappings will have an asterisk next to the name.
69
Figure 71
70
Figure 72
71
Figure 73
The SAN LUN Mapping window is basically divided into two primary sections. The first section on the left
side of the window encompassed in the box titled Topology Information displays the list of discovered
Host HBAs and the current mappings for that selected port name. The second section displayed on the
right hand side of the window provides tools for adding, modifying and deleting SAN LUN Mappings.
72
73
If you intend to make your Snapshots available as logical drives (VLUNs), you must SAN LUN Map
all logical drives. That includes regular logical drives and the snapshot logical drives.
From the Main screen click the SAN Mapping icon in the Tool Bar.
Figure 74
2
Select and name the Host HBA port or Host HBA Initiator ID.
In the HBA Ports Name section, select an unnamed port and identify it using the displayed HBA Node
WWN and HBA Port WWN in the NAME HOST section.
In the NAME HOST section, enter a user defined name for the HBA Port and click the ASSIGN NAME
button. Refer to the illustrations on the following page.
You may use up to 32 ASCII characters, however only 11 characters are displayed in the HBA Ports
Name field.
74
Figure 75
4
Add a mapping.
In the ADD NEW MAP section, do the following:
a Select the logical drive to which you wish to map. Click the pull down menu and choose from the
list of logical drives displayed. Default logical drive names are LD1, LD2, LD3, etc.
Note: Logical drives marked with an asterisk * indicate that another mapping for another Host
HBA has been established for this logical drive. You can map it again to additional HBAs but
know that all Host HBAs mapped to this logical drive will see and have access to this logical
drive.
b Choose the LUN (logical unit number) to present the mapped logical drive to the Host system.
Click the drop-down menu and choose the desired number.
c Select an access permission for the mapping. Choose from the drop-down menu: Read/Write or
Read Only.
Note: Microsoft Windows does not support Read Only permissions.
d Select the Host Port/Channel.
Click the check box(es) for the port that you wish the mapping to be available: C0P0, C0P1,
C1P0, and/or C1P1. Where C0 represents the left or lower controller and C1 represents the right
or upper controller, and P0 indicates the port marked Host 0, FC Host 0, or IN 0, and P1
represents the port marked Host 1, FC Host 1, or IN 1 on each controller. Ensure that the ports
you select are properly cabled.
e Click the ADD MAPPING button.
75
76
You will receive a confirmation, click the OK button to continue, or CANCEL to exit and return to the SAN
LUN Mapping window.
You may continue to create more mappings by repeating the above procedures or end this session by
clicking the CLOSE button.
Prior to deleting SAN LUN Mappings, clear your web browsers cache (With Internet Explorer the function
is known as deleting Temporary Internet Files). Then proceed with removing the mappings
From the Main screen click the SAN Mapping icon in the Tool Bar.
Select a Host HBA port or the user name you gave the port under the HBA Ports Name section that
contains the mapping to be removed.
Figure 76
Select the Mapping to remove from the MAPPINGS section. If there are multiple mappings for this Host
Port, and you want to remove them all, you can shift-click to select all the mappings.
You will receive a confirmation, click the OK button to continue, or CANCEL to exit and return to the SAN
LUN Mapping window.
You may continue to remove more mappings by repeating steps 2 through 5, or end this session by
clicking the CLOSE button.
77
Making changes to these mapping parameters may have an adverse affect on other mappings or to the
operating system accessing the logical drive.
From the Main screen click the SAN Mapping icon in the Tool Bar.
Select a Host HBA port under the HBA Ports Name section that contains the mapping to be modified.
Note
4
Figure 77
You will receive a confirmation, click the OK button to continue, or Cancel to exit and return to the SAN
LUN Mapping window.
Add the new mapping. Follow the procedures to add a new mapping and refer to your notes from the
existing mapping to help create the new mapping. For specific details, see 7.5 Creating a SAN LUN
Mapping beginning on page 74.
Essentially you want to re-create the mapping except using the new settings you want for example a
different logical drive, a new LUN, different permissions and/or different controller host ports.
78
Note
If you wish to cancel your changes before you click the APPLY button, click the RESTORE button and
the changes will be cleared restoring the previous settings.
If you are making multiple changes in multiple sessions, clicking Restore will reset the parameters to the
last time the APPLY button was clicked. For example, if you create a new mapping and click APPLY then
change the name of the Host Port and decide you dont want that change, clicking the RESTORE button
will cancel the name change and the new mapping remains as it was when you clicked the APPLY button
previously.
You will receive a confirmation, click the OK button to continue, or CANCEL to exit and return to the SAN
LUN Mapping window.
79
80
Controller Environmentals
Chapter 8
Controller
Environmentals
8.1 Overview
The Controller Information window provides you with a instant view of the health status of the RAID
Controller components and a mouse over function for detailed information of the items listed in the Status
section. User controllable functions include updating RAID Controller firmware, updating the Expansion
module firmware (Disk I/O or EBOD I/O modules), synchronizing the date and time, resetting or shutting
down RAID Controllers, and managing event log files.
Figure 81
81
The Controller icon on the Main screen will flash red when a problem exists with the controller, indicating
a status change either error or warning. If this occurs, click the icon and investigate the problem from
the information provided. You may wish to investigate the Event log to verify the event that changed the
controller status, see 14.6.5 Controller Port Events beginning on page 164.
When the Controller Information window opens the controllers status is displayed using status icons and
a text message.
By passing the mouse pointer over each item in the Status group (controller, battery, temperature and
voltage), a pop-up window will appear with specific detailed data.
82
Figure 82
Figure 83
Controller Environmentals
8.2.1 Status
This group of items are applicable to the functional status of the RAID Controller. They include general
controller status, battery status, temperature of the controller, and voltage status. Placing the mouse
pointer over the item will display a pop-up window with more detailed information. In the illustrated
example, the mouse pointer is over Voltage so the voltage data is displayed. Status icons appear
adjacent to the item in the group along with a text message. Status icon and text message conditions are
defined as green - normal, yellow - warning, and red - failed.
When the mouse pointer is rolled over the Battery status icon, the pop-up display provides the remaining
charge on the battery expressed as a percentage and the length of time the battery will hold the cache
data. A warning icon indicates a below 80% charge (battery is low but most likely charging). An error
indicates below 80% charge and the controller has been powered up for over 24 hours.
8.2.2 Hardware/Firmware
This group of items are applicable to the controllers physical memory and firmware. From this group you
can determine the type of processor, onboard memory size, the firmware version, and the CPLD
(Complex Programmable Logic Device) firmware version. The controllers WWN (world wide name) is
presented in this group.
8.2.3 Configuration
This group identifies the WWN (world wide name) assigned to the configuration, the speed of each port
and the LUN assigned to the port. The configuration can be assigned the WWN of any controller
preferably one of the controllers installed in the enclosure. For more information on the configuration
WWN and port LUN assignment, see 9.2.1 Identity beginning on page 92.
8.2.4 Operations
These items include a group of buttons that allow the user to reset and shutdown each controller
individually, update the controller firmware (see 8.2.4.1 on page 83), update the expansion module
(Disk I/O or EBOD I/O module) firmware (see 8.2.4.2 on page 85), export the controller logs (see 8.2.4.4
on page 88) and clear the log files (see 8.2.4.3 on page 87).
Note
When choosing to shutdown the RAID Controller(s) for an extended period of time, be sure to verify that
the Cache Active LED on each RAID Controller is NOT illuminated. If it is, wait until the controlling
application has completed writing the data to the disk before continuing with the shutdown. This will
ensure that the backup battery is not holding cache data and will prevent the battery from being drained.
The user can dump the controllers diagnostic information into a file for use with technical support when
troubleshooting a problem by clicking the DIAGNOSTIC DUMP button.
8.2.4.1
83
If you want to downgrade the firmware version you must shut down one controller and flash the operating
controller. Then shut down the controller which was downgraded, bring the second controller up and flash
its firmware to the lower version. Then start both controllers and resume operations.
1
Click the Controller icon located just above the Tool Bar.
Figure 84
Figure 85
84
Controller Environmentals
Locate the firmware file, click the Browse button. The file will be named similar to I_320_0179.bin.
The file will be made available from the customer service representative or technical support.
Figure 86
4
Note
8.2.4.2
Note
For more information on License Information, see 1.3.2 Feature License beginning on page 3.
Figure 87
85
Figure 88
3
Locate the firmware file, click the Browse button. The file will be named similar to
fw_1220_SAS10_0105.bin.
The file will be made available from the customer service representative or technical support.
Figure 89
4
86
Controller Environmentals
8.2.4.3
1
Figure 810
Figure 811
2
87
A window opens prompting to confirm clearing the logs. Click the OK button.
Figure 812
4
8.2.4.4
1
Confirmation WIndow
Click the CLOSE button at the bottom of the Controller Information window.
Figure 813
88
Controller Environmentals
Figure 814
Choose Save to Disk, enter a name and location for the file, then click the OK button.
Figure 815
Confirmation WIndow
Click the CLOSE button at the bottom of the Controller Information window.
89
90
Chapter 9
Controller Advanced
Settings
9.1 Overview
In the Controller Information window you can view the status of the controller and perform certain
controller operational functions. Since your storage solution may be different from another, you may want
to make changes to the controller parameters to optimize the system for your application. This is
accomplished through the Advanced Settings window.
Figure 91
91
The Advanced Settings window will appear. From this window you are able to make changes to controller
parameters, enable or disable Fault Tolerant features, and configure the controllers host ports.
The Advanced Settings window is divided into three sections; Identity, Fault Tolerance and Host Ports.
Figure 92
9.2.1 Identity
In the Identity section, you can make changes to the Configuration Name, assign the configuration the
WWN of either controller, and set the LUN (logical unit number) for the controller.
Figure 93
92
93
Figure 94
Auto 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 and a drive fails in that array.
Auto Rebuild - Selecting this option will automatically start a rebuild operation when a fault-tolerant
array loses 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.
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 Drive 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. As stated this process occurs in the
background when microprocessor time is available and is suspended when processor time is not
available.
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 a
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.
94
Enclosure Support - Selecting this option will cause the enclosure components to be monitored by
StorView. If you deselect this option StorView will not report the enclosure status, will not report
enclosure events, and the image on the Main screen will be dimmed. This does not disable the
audible alarm on the front panel.
Rebuild Priority - This option determines the amount of processor time allocated to the Rebuild
operation. The higher the value, the more time the processor will spend on the rebuild operation,
reducing the time to complete the operation. It is recommended to balance the two priority
parameters in the event a rebuild and initialization were to occur simultaneously.
Initialization Priority - This option determines the amount of processor time allocated to the
operation. The higher the value, the more time the processor will spend on the initialization
operation, reducing the time to complete the operation. It is recommended to balance the two priority
parameters in the event a rebuild and initialization were to occur simultaneously.
95
Figure 95
Controller Port ID (P0) - This is the target ID for both controller(s) port 0. It can range from: Soft
Address, or 0 - 125. The default is ID 4.
Controller Port ID (P1) - This is the target ID for both controller(s) port 1. It can range from: Soft
address, or 0 - 125. The default is ID 5.
Note: The ports are identified in the software as P0 and P1, they refer to the label on the RAID
Controller which indicates FC Host 1 and FC Host 2 connectors respectively. Controller 0
refers to the left controller and Controller 1 is the right controller.
Controller Port Data Rate - Use the Automatic setting for most configurations. If you choose to use
a specific setting (1 Gb, 2 Gb, or 4 Gb) you override the automatic setting. Be sure the software
setting here matches the hardware switch setting on the HBA ports.
Note: When using an Active-Active configuration (dual controllers) set the Controller Port Data
Rate to a predetermined speed. When the Automatic setting is used with Active-Active it is
possible for the speed to step down to 1Gb during a fail-back operation. For 2 Gb or 4 Gb
operations, manually setting the speed will prevent this from happening.
96
Connection - 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.
9.2.3.2
Figure 96
Controller Port ID (P0 = Host 0) - This is the target ID for both controller(s) port 0. It can range from:
Soft Address, or 0 - 125. The default is ID 4.
Controller Port ID (P1 = Host 1) - This is the target ID for both controller(s) port 1. It can range from:
Soft address, or 0 - 125. The default is ID 5.
Note: The ports are identified in the software as P0 and P1, they refer to the label on the RAID
Controller which indicates Host 0 and Host 1 connectors respectively. Controller 0 refers to
the lower controller and Controller 1 is the upper controller.
Controller Port Data Rate - Use the Automatic setting for most configurations. If you choose to use
a specific setting (1 Gb, 2 Gb, or 4 Gb) you override the automatic setting. Be sure the software
setting here matches the hardware switch setting on the HBA ports.
Note: When using an Active-Active configuration (dual controllers) set the Controller Port Data
Rate to a predetermined speed. When the Automatic setting is used with Active-Active it is
possible for the speed to step down to 1Gb during a fail-back operation. For 2 Gb or 4 Gb
operations, manually setting the speed will prevent this from happening.
97
Connection - 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.
9.2.3.3
Figure 97
Data Rate - Use the Automatic setting for most configurations. If you choose to use a specific setting
(1.5 Gbits/sec. or 3 Gbits/sec.) you override the automatic setting. Be sure the software setting here
matches the hardware switch setting on the HBA ports.
98
Chapter 10
99
You must stop all host I/O operations prior to deleting an array.
Caution
Deleting an array will delete all data on the logical drives and those associated with that array. Be sure
you have a back up of the data before proceeding.
From the Main screen Configuration section, click the <Array_Name> you wish to delete.
The Array Information screen will appear, click the DELETE ARRAY button.
Figure 101
4
A confirmation screen will appear, type your password and click the GO button. If the wrong password
is entered, you will be prompted and the array will not be deleted.
Figure 102
5
100
Confirmation Window
Once the array has been successfully deleted, click the CLOSE button.
You can restore the original settings by clicking the RESTORE button which will cancel any changes you
have made as long as you have not clicked the APPLY button.
From the Main screen Configuration section, click the <Array_Name> you wish to modify.
The Array Information window will open, type a new name for the array in the Name field and click the
APPLY button.
Figure 103
Note
If the array was trusted or never initialized, you can also initialize the array from this window by clicking
the INITIALIZE button.
Note
From the Main screen Configuration section, click the <Array_Name> you wish to verify parity data.
The Array Information window will open, click the VERIFY PARITY button.
101
Figure 104
3
Select a verify method from the drop-down list and click the VERIFY PARITY button.
Figure 105
102
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.
Option
Description
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.
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 and creates a log entry. This is the slowest to
complete, since it has the overhead of a comparison as well as a rewrite.
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.
Figure 106
You can stop the Verification process if you wish by clicking on the Stop link located to the right of the
progress bar.
103
Figure 107
You can also identify specific drives in an array by flashing its Drive Status LED, see 10.4.2 Locate
Drive beginning on page 114.
104
Only one rebuild can take place at a time. If a rebuild is currently underway, the second array scheduled
for rebuild will be on-hold until the first array has completed the rebuild.
One scenario where this option would be useful is if you inadvertently pulled the wrong drive from a
working array and that drive is now flagged as a failed drive, regardless of whether or not you re-insert
the drive quickly. If you do not have a hot spare defined, the array will not automatically begin a rebuild
operation. You must change the status of the flagged failed disk drive to a spare drive which will clear the
condition and initiate a rebuild.
From the Main screen, identify the failed drive displayed in the enclosure front view and click that drive
icon. The Drive Information window will open.
Figure 108
2
Figure 109
Rebuild Options
105
Scroll down and choose the specific array that became critical from the removed/failed drive.
A confirmation window will appear indicating the successful execution of the command, click the CLOSE
button.
Important
For a RAID 6 rebuild operations, if two (2) drives fail, and a rebuild is started after replacing both
disk drives, only one drive rebuild is performed at a time. This means one drive will be rebuilt then
the second drive rebuild will be started.
You can monitor the rebuild operation from the Main screen
You must stop all host I/O operations prior to deleting an array.
RAID 6 disk arrays do not support array expansion.
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.
Note
No configuration changes can be made to the arrays, logical drives, or SAN 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.
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
106
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 logical drive(s) and define them in your operating system.
However, if the expansion is intended to increase the existing logical drive 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.
On the Main screen locate and click on the <Array_Name> you wish to expand. This will open the Array
Information window.
From the Array Information window, click the Expand Array tab, see Figure 1010 Expand Array Tab
Selected beginning on page 107.
Following the sequenced steps, click the Array Expansion Type pull-down menu, choose the type of
expansion applicable to your array.
Verify the changes you are about to make by examining the Before Expansion and After Expansion
analysis.
You will be prompted to confirm the Expand operation. Type your password and click the GO button.
You will receive a screen prompt that the command was successful, click the CLOSE button. If the
command was unsuccessful, review the settings for incorrect parameters and hardware for operational
status.
107
On the Main screen in the Tool Bar, click the Create Array icon.
The Create Array window will appear, select your drives in the Available Drives section.
Enter a name for your array. You may use up to 32 characters (ASCII).
Enter the desired chunk size. Click the pull-down menu and choose from the available values.
Choose the Back-off Percent (reserved capacity) for the drives. The default is 1%.
10
108
If your configuration is cleared accidentally and you cannot restore the configuration exactly as it was,
you will not be able to restore access to the data. This will result in data loss.
It is recommended to periodically save the configuration so that it is up to date, see 6.6.1 Saving the
Configuration beginning on page 65.
From the Main screen Tool Bar click the Archive Configuration icon. The Configuration Archival
Operations screen appears.
Click the RESTORE button. You may click the CLOSE button to cancel and return to the Main screen.
109
Click the UPLOAD button to continue to restore the configuration, or click the CANCEL button to quit.
After you have completed the configuration restoration, and if you had any RAID 5, 6, or 50 arrays
defined, click the Array link on the Main screen for each RAID 5, 6, or 50 array. Perform a Verify Parity
operation before using those arrays. This will ensure that the data and parity data are correct.
110
This process removes all arrays, logical drives, SAN LUN Mappings, Snapshots, Snapshot Feature
License, etc. If there is any data on the drives, access to that data will be lost when the configuration is
cleared.
From the Main screen Tool Bar click the Archive Configuration icon.
Before you clear the configuration file, if you are using the Snapshot feature, ensure that you
make a note of which WWN the configuration is based on, see 9.2.1 Identity beginning on
page 92. When you start your new configuration and if you intend to use the Snapshot feature, it
will be necessary to set the Configuration WWN based to the same WWN as when the snapshot
license key was issued. This is because the snapshot license key is generated so that it works
only with an array using the configuration WWN as it was in the previous configuration.
Click the CLEAR button.
You may click the CLOSE button to cancel and return to the Main screen.
A pop-up window appears, type your password and click the GO button.
111
112
From the Main screen, click on any disk drive icon displayed in the enclosure front view.
113
To locate a disk drive, select a drive icon in the enclosure front view and click that drive icon.
114
A sub menu will open in the Drive Information window, from which you will select the time interval to blink
the Drives Activity LED. Select the time period you desire.
Identify the drive in the enclosure by its blinking Drive Activity LED. Refer to the hardware users guide
for details on Drive LEDs.
From the Main screen in the Tool Bar click on the Create Logical Drive icon.
The available free space is displayed in the Select which Array(s) to Use scrollable window. You will
see each array and how much space is available.
If you were just interested in the available free space, click the CLOSE button. Otherwise to continue with
creating a logical drive, see 6.5 Create the Logical Drive beginning on page 62.
You must stop all host I/O operations prior to deleting an array.
Expanding a logical drive is a utility that allows you to take an existing logical drive and expand its
capacity using free regions.
Note
After the expansion process has completed you will need to use a third-party volume/partition software
product to manipulate any existing partitions.
From the Main screen in the Logical Drives section, click on a <logical_drive_name> that you wish to
expand. The Logical Drive Information window will open.
115
Locate the Expand section of the window (lower half), and follow the sequenced steps beginning at Step
1 where you will choose a free space region to be used for the expansion.
116
In the Add Capacity box, enter the amount of the selected region to expand the logical drive. You may
use the entire free region space or a portion of it, specify by entering the number of GBs to use.
You will be prompted to enter your password to confirm the expansion. Type in your password and click
the GO button.
You will receive a screen prompt that the command was successful, click the CLOSE button. If the
command was unsuccessful, review the settings for incorrect parameters and hardware for operational
status.
You must stop all host I/O operations prior to deleting an array.
Deleting a logical drive is an option that allows the user to remove an existing logical drive that is no
longer needed or desired. If the logical drive was previously used be sure to make a backup of any data
on the logical drive. After deleting the logical drive, SAN LUN Mapping (if used) and the operating system
will need to be modified due to the missing drive.
From the Main screen in the Logical Drives section, click on a <logical_drive_name> that you wish to
delete.
In the Logical Drive section at the top, click the DELETE button.
117
118
You will be prompted to enter your password to confirm the deletion. Type in your password and click the
GO button. Click the CANCEL button to exit without making any changes.
You will receive a screen prompt that the command was successful, click the CLOSE button. If the
command was unsuccessful, review the settings for incorrect parameters and hardware for operational
status.
Using Snapshot
Chapter 11
Using Snapshot
11.1 Introduction
StorViews Snapshot feature has been designed to give the user considerable flexibility when setting up
and performing snapshot and snapback operations.
A snapshot allows the user to create a point-in-time image of a logical drive that contains exactly the
same data at the point the Snapshot was taken.
Snapback allows the user to restore the logical drive to that point in time when the snapshot was taken.
For more detailed information on snapshot, see More on Snapshot beginning on page 195.
You cannot enable Snapshot support while an array expansion or array initialization is occurring.
Please wait for the operation to complete before attempting to enable Snapshot.
Important
If you intend to make your Snapshots available as logical drives (Virtual LUNs (VLUNs)), you must
SAN LUN Map all logical drives. This includes regular logical drives and the snapshotted logical
drives.
Ensure you have an array created to hold the ODA. This should be a different array not comprised of the
logical drives intended to be snapshotted. If not, stop the process and create an array for the ODA. It is
not recommended to use the same array as the logical drive for performance reasons.
From the Main screen select a logical drive that will be snapshotted.
Important
If this is the first time enabling Snapshot you will have the ability to create one ODA and pairing
it to one logical drive. If you attempt to exceed the Limited Free License, you be prompted to enter
a license key. To obtain a feature license key, contact your sales representative.
119
Figure 111
Figure 112
3
120
Using Snapshot
Figure 113
4
Enter your license key and click the Submit License Key button.
You will receive confirmation that it was successful. If the procedure is unsuccessful ensure the key has
been entered correctly and repeat. If it still remains unsuccessful contact customer support. For more
information, see 1.3.2 Feature License beginning on page 3.
Select the array you wish to use for the Overwrite Data Area (ODA). This is where all the snapshots will
be stored for this logical drive. You should see the array you created for the ODA from step 1. For more
information, see C.2 Overwrite Data Area beginning on page 196.
Figure 114
Note
It is recommended that you have an array created specifically for the Overwrite Data Area (ODA).
Choosing a different array then the array the logical drive uses will avoid any performance compromises.
If necessary, return to the Main screen and create a new array for the ODA. (You will need to wait until
the new array completes initializing and refresh the Logical Drive window for the new array to appear.)
121
By default the Show arrays used by this logical drive is not selected. This is to deter the user from
selecting an array that comprise the logical drives arrays, as it is not the recommended choice. The
preferred method is to choose an array not associated with the logical drive. When the check box is
selected in addition to the other disk arrays, the arrays for this logical drive are shown as well and can be
selected.
6
From the drop-down menu, choose the desired stripe size (or write buffer size) for the Overwrite Data
Area (ODA). The choices are: 64KB, 128KB, 256KB, 512KB, or 1MB.
It is recommended that you choose a stripe size based on your applications need. If you are making small
changes, such as with a database, then you will want the smallest stripe size. If you are making large
changes, such as with video application, then you will want a much larger stripe size.
Table 111
Note
Stripe Size
64 Kbytes
549 GBs
128 Kbytes
1 Terabyte
256 Kbytes
2 Terabytes
512 Kbytes
4 Terabytes
1 Mbyte
8 Terabytes
The stripe sizes available in the drop-down menu will change dynamically based on the size of the ODA
entered. For example if you specify an ODA greater than 549 GBs, the selection for 64 Kb will not be
displayed. If you enter an ODA size greater than 1 terabyte, then both 64 Kb and 128 Kb stripe sizes will
not be displayed in the drop-down menu.
122
You must ensure that applications writing to the logical drive are synchronized with the snapshot.
This can be performed in a variety of ways depending on the applications using the logical drive
where the snapshot is being initiated. Buffers may need to be flushed for a consistent point-intime image of the files on the logical drive.
From the Main screen select the logical drive to which you wish to take a snapshot.
Using Snapshot
From the Logical Drive window, click the SNAPSHOT MANAGEMENT button.
Figure 115
3
Figure 116
Taking a Snapshot
You will receive a notice, prompting you to ensure the applications have been synchronized and the
logical drive is dismounted to ensure a valid snapshot is taken.
You will see a confirmation window once it is complete. Click the CLOSE button.
123
Figure 117
4
After the snapshot is complete, you will see the following in the Snapshot/ODA Management window.
Figure 118
5
124
Figure 119
6
Snapshot Message
Using Snapshot
If you intend to make your Snapshots available as logical drives (Virtual LUNs (VLUN)), you must
SAN LUN Map all logical drives. That includes regular logical drives and the snapshotted logical
drives.
From the Main screen click the SAN Mapping icon in the Tool Bar.
Select the Snapshot from the drop-down Logical Drive menu that you wish to map.
125
In the example on the previous page, the LD0-S0 entry represents Snapshot 0 of Logical Drive 0.
126
Choose the host port check boxes you wish the snapshot logical drive to be available, then click the
APPLY button.
Access your host operating system and application software to backup or retrieve data from the snapshot
logical drive.
Using Snapshot
If you delete a snapshot, all snapshots that occurred after the one you are deleting will also be
deleted. For example, if there are four snapshots (Snap 00 - Snap 03), and you delete Snap
01 then Snap 02 and Snap 03 will also be deleted.
From the Main screen select the logical drive with the Snapshot icon adjacent to it.
127
Select the snapshot you wish to delete from the Snapshots list window, then click the DELETE
SNAPSHOT button.
128
You will see a message that the execution was successful, click the CLOSE button.
Using Snapshot
Before you perform a snapback operation, be sure to back up the data on the existing logical drive
first. When the snapback command is issued, the existing data will be overwritten and replaced
with an exact copy of the Snapshot image.
If necessary, perform a backup of the logical drive before performing the Snapback operation.
From the Main screen select the logical drive with the Snapshot icon adjacent to it.
129
Select the snapshot you wish to snapback from the Snapshots list window, then click the SNAPBACK
button.
Important
If you perform a snapback, the select snapshot and all snapshots that occurred after the one you
are snapping back will be deleted. For example, if there are four snapshots (Snap 00 - Snap
03), and you snapback Snap 01 then Snap 02 and Snap 03 will also be deleted, as well as
Snap 01.
You will see a progress display on the Main screen, located under the logical drive icon.
130
Using Snapshot
From the Main screen select the logical drive to which you wish to disable Snapshot support.
131
3
Caution
4
You will be prompted to enter your password. Enter the password and click the GO button.
Disabling Snapshot support will result in the loss of all Snapshots for this logical drive.
Click the DISABLE button.
132
Chapter 12
Failover, Performance
and Additional Functions
12.1 Overview
In this chapter you will find more information on the following:
How StorView failover operates
Performance optimization processes
Additional Functions
About
Take Control Monitoring
Rescan
Alarm Mute and Enable/Disable
133
During normal operations, the StorView server(s) send check-in packets every 10 seconds. If three
consecutive check-in packets for a specific StorView server are not received, its devices are flagged and
the StorView server with the lowest serial number or address will take control of those devices.
12.3.2 Scatter/Gather
(Microsoft Windows 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 Microsoft Windows operating system documentation for more information on editing the
registry and your host HBA adapter documentation.
134
From the Main screen, click the ABOUT button, located in the upper right corner of the window under the
StorView logo.
Figure 121
The About window is displayed. The license type for this installation is indicated below the version
number in parenthesis.
2
Figure 122
135
Figure 123
After clicking the Take Control link on the Main screen, StorView will perform a scan and reload the
configuration for this system. The StorView Server which previously had control will now display the
message that the selected storage solution is being monitored by another StorView server.
You would also see this condition if this StorView server failed to send the required three consecutive
check-in packets and it fails over to another StorView server attached to the same storage system. Once
the problem is resolved on this host StorView Server, you can take back control again with that StorView
server.
136
12.5.3 Rescan
This Rescan function will force a search to re-discover storage solutions in order to refresh the display
and update status information.
From the Main screen, click the RESCAN button located on the far left side of the screen. After a few
moments the Main screen is re-displayed with updated information.
Figure 124
137
Figure 125
This feature works whether the alarm is sounding or is currently silent. The Mute and Disable features
are only applicable to the RS1220-F4-5402E& RS-1220-F4-5412E and RS-1220-E3-5402E & RS-1220E3-5412E systems.
Silent
Figure 126
Sounding
Muted
Disabled
From the popup window choose to mute the alarm for the enclosure(s) or you may choose to disable that
alarm for all future events and notifications. The alarm must be enabled to restore normal alarm
notifications.
To mute the alarm, click the Speaker Monitor icon again and click the MUTE button.
To disable the alarm, click the Speaker Monitor icon again and click the DISABLE button.
To enable, click the Speaker Monitor icon again and click the ENABLE button.
Figure 127
138
Chapter 13
From the Main screen, click the TECH SUPPORT button, located in the upper right corner of the window
under the StorView logo.
Figure 131
2
139
The Problem field is scrollable allowing you to review the information you will be sending.
Note
Figure 132
3
140
Figure 133
Caution
Type the name of the firmware file or click the Browse button and locate the file. The file name will be
similar to storview-3.06.xxxx-nb-en.bin.
Figure 134
4
141
142
Event Logs
Chapter 14
Event Logs
14.1 Overview
StorView has the ability to manage the events generated by the controller, SES processors. StorView
also has its own unique events that are related to the StorView server component of the software. Events
can be used to assist with troubleshooting, monitoring components, and determining the status of
hardware components, logical drives and arrays. The following event types are logged:
There are two event logs maintained: 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
StorViews set of event logs. The differences include the type of events logged and in some cases the
ease of interpretation. StorView event logs provide a more user friendly language approach to describing
the event.
The controllers maximum event log size is 4096 entries with the oldest events being overwritten as the
log reaches the size limit. Some repetitive events 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 Operation tab. From there you can export the controller logs to an external file or clear the log entries.
Enclosure event monitoring can be disabled which reduces the polling that StorView performs thereby
increasing the performance that may be necessary in certain applications. This is accomplished by deselecting the Enclosure Support option in the Advanced Settings window. Disabling this option will stop
enclosure component monitoring, which can be noted on the Main screen by the dimming of the
enclosure rear view graphics and a notation above the graphic stating Enclosure Information Not
Available see 8.2 Controller Environmentals beginning on page 81.
143
StorViews event log will maintain the controllers compilation of events and the softwares specific
events. The controllers compilation of events include Controller Events (those unique to the RAID
Controller), Drive Events and Host Events, and if the Enclosure Support option is enabled, enclosure
component events.
Note
If the Enclosure Support option is disabled, E-Mail notifications established for those enclosure 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.
StorViews 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 doesnt fill to
disk capacity. You can export the log files to a comma delimited file prior to clearing them for later use.
StorView also supports the SYSLOG feature. Refer to Section 4.5, SYSLOG, on page 33.
144
Event Logs
Figure 141
145
Below you will find an explanation of the components of the event log.
Figure 142
The embedded version of StorView does not support some components of Event Log window. The
unsupported components include the Log # column, Log # window, Jump To button, Export button, and
the Clear Log button. Clear log is now handled by the clear controller log function found in the
Environmentals section.
Event Type Icons
Information
Warning
Error
146
Event Logs
To export the log file, click the LOGS button on the Main screen for the storage system you are logged
into.
Figure 143
2
Figure 144
147
The following are examples of some web browser file export options, your browser may be slightly
different.
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.
Figure 145
If you are using a Mozilla type 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, as
desired.
Figure 146
3
148
Event Logs
To clear the log file, click the LOGS button on the Main screen for the storage system you are logged into.
Figure 147
Figure 148
149
Click the CLEAR button on the upper right corner of the Event Logs window. The following window
appears.
Figure 149
Confirmation Window
Click the CLOSE button at the bottom of the Event Logs window.
150
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.
Event Logs
Cause
Action
Internal hardware or
firmware failure.
Fault SDRAM or
damaged internal bus.
Internal hardware.
Memory or bus error on
the indicated channel.
Warning
Blocked fan.
[0xB04 (2820)]
Failing fan.
Elevated ambient
temperature.
151
Cause
Action
Replace battery in the
controller.
Error
Failure or removal of one Re-install the controller.
[0xB08 (2824)] controller (partner) in an
or
Active-Active
configuration.
Replace the controller.
Error
Voltage regulator
[0xB19 (2841)] hardware failure.
Enclosure 5V or 12V
problem in the power
supply.
Error
Hardware problem.
[0xB1A (2842)]
Information
Partner controller has
[0xB29 (2857)] been inserted.
No action necessary.
Information
Partner controller is ready No action necessary.
[0xB2A (2858)] to fail back.
A stripe synchronization of a
Information
A controller fails or is
No action necessary.
RAID set has started. This
[0xB2C (2860)] powered off during a write
occurs when a controller fails,
operation.
or after a controller is powered
off with write commands in
progress.
152
Event Logs
Cause
Action
A stripe synchronization of a
RAID set has completed.
Information
A controller fails or is
[0xB2D (2861)] powered off during a
RAID write operation.
No action necessary.
Information
A change in the
[0xB2F (2863)] configuration has
occurred.
No action necessary.
No action necessary.
Information
Battery charging
[0xB42 (2882)] complete.
No action necessary.
Information
Removal of controller or
[0xB50 (2896)] power.
No action necessary.
Information
The controller was
[0xB51 (2897)] powered on.
No action necessary.
Information
Self-test completion on
[0xB52 (2898)] startup.
No action necessary.
Error
Self-test failure on
[0xB53 (2899)] startup.
Information
Occurs first time after
[0xB54 (2900)] production.
No action necessary.
Error
Occurs first time after
[0xB55 (2901)] production.
Contact technical
support.
Information
The user has cleared the No action necessary.
[0xB56 (2902)] event log.
153
Cause
Action
Information
User initiated a controller No action necessary.
[0xB58 (2904)] shutdown.
The controller
temperature threshold
was exceeded and the
controller shut itself
down.
Information
SES initialization.
[0xB5B (2907)]
No action necessary.
Failover started.
Information
Failure or removal of the
[0xB5C (2908)] partner controller.
No action necessary.
Failover completed.
Information
Completion of failover
[0xB5D (2909)] process.
No action necessary.
Failback started.
Information
Partner controller started No action necessary.
[0xB5E (2910)] failback.
Failback completed.
Information
Completion of failback
[0xB5F (2911)] process.
No action necessary.
No action necessary.
No action necessary.
Information
Battery charging started.
[0xB62 (2914)]
154
No action necessary.
Error
Failure of power for an
Check the file system.
[0xB65 (2917)] extended time with
writeback cache present.
Event Logs
Cause
Warning
SDRAM error.
[0xB72 (2930)]
Action
If it repeats, replace the
controller.
No action necessary.
Hardware Error
Error
The controller will
Replace the controller.
[0xB7A (2938)] continue to function,
Additional Info: (Advanced hex
however the SES
data for customer service reps
temperature sensing may
or engineer use.).
not function properly.
Running <version_number>
Information
CEMI firmware is current. No action necessary.
CEMI firmware version:
[0xB89 (2953)]
Release <num>, Build <num>.
Automatic or Manual CEMI Error
Firmware is attempting to No action necessary.
firmware upgrade from
[0xB89 (2953)] upgrade.
<original CEMI FW version>:
Release <num>, Build <num>
to new version: Release
<num>, Build <num>
<completed successfully>, <is
underway>, or <failed>.
Automatic or Manual,
depending on whether the
upgrade attempt was
automatic or manual.
CEMI firmware upgrade from Error
Firmware failed to
<original CEMI FW version>: [0xB89 (2953)] upgrade due to nonRelease <num>, Build <num>
responding controller.
to new version: Release
<num>, Build <num> failed
because there is no response
from the processor.
No action necessary.
No action necessary.
155
Cause
Action
No action necessary.
156
No action necessary.
Event Logs
Type [ID]
Cause
Action
Information
The firmware upgrade of the No action necessary.
[0xB7E (2942)] Disk I/O or EBOD I/O module
firmware has started. The
process uploads the firmware
to the buffer on the controller
and starts the update on the
module. The update will
occur on all the Disk I/O or
EBOD I/O modules
connected to the controller.
At the end of the update
process, if the update
process is successful, the
RAID Controller and Disk I/O
or EBOD I/O module will be
reset.
Information
The firmware upgrade of the
[0xB7F (2943)] Disk I/O - EBOD I/O module
firmware has completed
successfully. The RAID
Controller and Disk I/O or
EBOD I/O module will be
reset.
Error
The firmware upgrade of the No action necessary.
[0xB80 (2944)] Disk I/O EBOD I/O module
firmware has stopped
because the update process
has encountered an error.
However, the update process
will resend the firmware and
continue with the process
update. At the end of the
update process, if the update
process is successful, the
RAID Controller and Disk I/O
EBOD I/O module will be
reset.
No action necessary.
157
Type [ID]
Alarm Mute.
Information
The user muted the alarm.
[0xB8D (2957)]
The audible alarm is
temporarily muted.
Alarm Disable.
Information
The user disabled the alarm. No action necessary.
[0xB8E (2958)]
The audible alarm has been
disabled and will silence all
alarm events. The disabled
alarm will be cleared when
the Alarm is enabled or the
controller is reset.
Alarm Enable.
Information
The user disabled the alarm. No action necessary.
[0xB8F (2959)]
The audible alarm has been
enabled and will allow all
alarms to be heard.
Information
No status condition being
[0xC6E (3182)] reported.
158
Cause
Alarm silenced.
Action
No action necessary.
No action necessary.
User pressed the
Alarm Mute button on
the front panel.
Warning
A status condition caused the Press the Alarm Mute
[0xC6E (3182)] alarm to sound every two
button on the front
minutes until muted.
panel and isolate the
cause of the alarm.
Warning
A status condition that
Press the Alarm Mute
[0xC6E (3182)] caused the alarm to sound is button on the front
continuing to remind the user. panel and isolate the
cause of the alarm.
Error
A status condition caused the Press the Alarm Mute
[0xC6E (3182)] alarm to sound.
button on the front
panel and isolate the
cause of the alarm.
Event Logs
Type [ID]
Cause
Error
Typically due to a nonThe drive w/SN <xxxxxxx>
(Slot <nn>, Enclosure <nn>)
[0xB0A (2826)] recoverable media error
(<Array Name> Drive
or hardware error.
<member index>) has failed
due to an unrecoverable error.
Sense Data: <xx>/<xx>/<xx>.
The drive w/SN <xxxxxxx>
(Slot <number>) (Drive
<number>) has been marked
as failed because it was
removed.
Action
Error
Drive has been removed Replace the disk drive.
[0xB0B (2827)] or bypassed by the user,
or has a serious
hardware error.
Removal of cables
connecting the
enclosures.
Error
This indicates that the
Remove the drive in the
[0xB13 (2835)] controller has shutdown identified slot will rethe slot due to multiple
enable the PHY.
errors from the drive.
This may be due to a bad
drive or MUX Transition
card.
159
Type [ID]
Cause
Error
This indicates that the
Replace the disk drive
[0xB13 (2835)] controller has tried
or MUX Transition Board
multiple times to switch
(dongle).
the Multiplexer (MUX) on
a SATA drive and it has
not been successful.
This may be due to a bad
drive or MUX Transition
card (dongle).
Error
Drive removal or failure.
[0xB1B (2843)]
Warning
Unknown status returned Contact technical support
[0xB27 (2855)] by the disk drive.
and provide them with a
copy of the event log.
Warning
Drive hardware error or
[0xB28 (2856)] bus error.
Information
A rebuild has started.
[0xB30 (2864)]
No action necessary.
Information
A rebuild has completed. No action necessary.
[0xB31 (2865)]
No action necessary.
Information
Initialization has started.
[0xB33 (2867)]
No action necessary.
Information
Initialization has
[0xB34 (2868)] completed.
No action necessary.
160
Action
Event Logs
Type [ID]
Cause
Action
Bus error.
No action necessary.
Information
Parity check started.
[0xB43 (2883)]
No action necessary.
Information
Parity check completed.
[0xB44 (2884)]
No action necessary.
Information
Drive was inserted.
[0xB61 (2913)]
No action necessary.
161
Type [ID]
Cause
Information
The controller has finished No action necessary.
[0xB67 (2919)] updating a drives
firmware. Drive w/SN
<xxxxxxx> or WWN
<xxxxxxxxxxxxxxxx>, Slot
<nn>, Enclosure <nn>,
Firmware Version:<xxxx>.
Information
Expansion has started.
[0xB68 (2920)]
No action necessary.
Information
Expansion has
[0xB69 (2921)] completed.
No action necessary.
Information
Expansion has restarted. No action necessary.
[0xB6A (2922)]
Action
162
Warning
Data Blocks at LBA <yyy> No action necessary.
[0xB71 (2929)] on Drive w/ SN <xxxxxxx>
(SAS: w/ WWN
<xxxxxxxxxxxxxxxx>)
(Slot <nn>, Enclosure
<nn>) have been
reallocated.
Event Logs
Type [ID]
Cause
Action
Information
A rebuild was canceled
[0xB73 (2931)] by the user.
No action necessary.
Error
Drive or SATA link error.
[0xB75 (2933)]
No action necessary.
Error
A drive w/ WWN
No action necessary.
[0xB76 (2934)] <xxxxxxxxxxxxxxxx> (Slot
<nn>, Enclosure <nn>)
has been removed.
Error
An unsupported drive w/
(WWN <xxxxxxxxxxxxxxxx> or [0xB7B (2939)]
SN) <xxxxxxx> (Target ID
<num>) has been inserted.
<Array Name> is in an
Error
unsupported configuration with [0xB8C (2956)]
a mixture of A/P and A/A SATA
drives.
163
Type [ID]
Cause
Action
Error
[0xB17 (2839)]
[0xB18 (2840)]
Information
[0xB24 (2852)]
No action necessary.
Information
[0xB25 (2853)]
No action necessary.
No action necessary.
Information
[0xB26 (2854)]
Information
[0xB26 (2854)]
164
First access by a
No action necessary.
particular host after a LIP
or reset.
A host has accessed a
Logical Drive <yy> for the
first time, or for the first
time following a reset. ID
<zz> accessed it through
Host Channel <nn> with
the SCSI command
0x<zz>.
Event Logs
Type [ID]
Cause
Action
Error
This may indicate a loop
[0xB37 (2871)] reset or LIP during a
command, or a loop
failure. Repeat Count =
<count>.
Error
This indicates a firmware Contact technical
[0xB38 (2872)] error in the host fibre
support.
channel chip.
Contact technical
support.
No action necessary.
165
Type [ID]
Cause
Enclosure<xx> (w/
WWN:<xxxxxxxxxxxxxxxx>)
timed out on SCSI
command 0x02X.
Warning
This error is generated
[0xB79 (2937)] when a command to the
Enclosure processor
time-outs.
Action
Verify if the system has
gone to SES_LEVEL_1.
If it has, verify the
configuration.
Faulty cables, drives or
EBOD I/O or Disk I/O
module malfunction
could be the root cause
of this error.
You may occasionally
see this error during drive
insertion, failover/
failback or drive removal.
As long as the system
remains at
SES_LEVEL_3 the user
does not intervene. If this
event is periodically
posted in the event log
the user may have a hard
drive or EBOD I/O or Disk
I/O module problem. The
system should be
inspected to isolate the
problem to either drives
or EBOD I/O or Disk I/O
module.
NOTE: This event is only
valid for daisy chained
systems.
166
Information
Normal condition
[0xC6B (3179)] reported.
No action necessary.
Warning
The specific power
[0xC6B (3179)] supply has failed.
Event Logs
Type [ID]
Cause
Warning
The specific power
[0xC6B (3179)] supply has failed.
The specific power
supply is powered off or
mains power removed.
The power supply was
removed.
Action
Replace the power
supply.
Ensure that the specific
power supply On/Off
switch is in the On
position (l) or mains
power is applied.
Error
The power supply was
[0xC6B (3179)] removed.
Error
The power supply was
[0xC6B (3179)] removed.
Information
Normal condition
[0xC6C (3180)] reported.
No action necessary.
Information
Unknown status.
[0xC6C (3180)]
No action necessary.
Information
Cooling fan module was
[0xC6C (3180)] removed.
Error
A specific fan failure.
[0xC6C (3180)]
Total fan module failure.
Information
Temperature sensors are No action required.
[0xC6D (3181)] reporting normal
temperatures in the
enclosure.
167
Type [ID]
Cause
Action
Ensure that the cooling
fan is operating normally.
(Replace if needed.)
If the cooling fan is 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.
Automatic system
shutdown will begin. In
Active-Active
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.
168
If the environment
ambient temperature is
high, reduce the ambient
temperature.
Ensure that the airflow is
not blocked or restricted
on the enclosure.
Event Logs
Type [ID]
Cause
Action
Information
[0x101 (257)]
No action necessary.
Information
[0x102 (258)]
Information
[0x103 (259)]
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.
Information
[0x105 (261)]
No action required.
Information
[0x106 (262)]
No action required.
Information
[0x106 (262)]
Information
[0x106 (262)]
169
170
Type [ID]
Cause
Action
The setting
MulticastPort is not
setup in the db/IP.db file.
The setting was removed
or the file became
corrupt.
Warning
[0x202 (514)]
Warning
[0x202 (514)]
Event Logs
Type [ID]
Cause
Action
Error
[0x301 (769)]
Error
[0x302 (770)]
Retry request.
Error
[0x303 (771)]
Error
[0x304 (772)]
Error
[0x305 (773)]
Error
[0x306 (774)]
Retry request.
Quit StorView and all
connections accessing
this StorView Server, wait
1 minute and restart them.
Restart the system.
Retry request.
Quit StorView and all
connections accessing
this StorView Server, wait
1 minute and restart them.
Restart the system.
171
172
Type [ID]
Cause
Action
Error
[0x307 (775)]
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
The controller module
[0xA01 (2561)] has been loaded by the
StorView Server.
No action necessary.
Error
Several commands have Ensure that the paths and
[0xA03 (2563)] been sent through a
hardware are operational.
known good path but they
have failed.
Successful communication
with controller after several
failures.
Information
A known failed path is
[0xA04 (2564)] now functional and
passed retest.
No action necessary.
Event Logs
Type [ID]
Cause
Action
Error
ODA is no longer valid.
[0xB81 (2945)] Capacity was exceeded
during last snapshot.
Information
ODA was unassigned.
[0xB82 (2946)]
No action necessary.
Information
ODA was assigned.
[0xB82 (2946)]
No action necessary.
No action necessary.
No action necessary.
A Snapback (based on
Information
A snapback operation
Snapshot <x>) on Logical
[0xB84 (2948)] was started by the
Drive <ID #> has been started
operator.
<x,y>.
No action necessary.
A Snapback (based on
Snapshot <x>) on Logical
Drive <ID #> has completed
<x,y>.
Information
A snapback operation
[0xB84 (2948)] has successfully
completed.
No action necessary.
Error
There is a problem with
[0xB85 (2949)] the logical drive being
snapshotted.
Information
A license update/upgrade No action necessary.
[0xB86 (2950)] was performed.
173
Type [ID]
174
Cause
Action
Loss of snapshot,
Perform a new snapshot
and ensure the power
remains constant.
Warning
A controller was inserted No action necessary.
[0xB88 (2952)] that contained old
snapshot metadata in its
cache.
Information
A snapshot metadata
No action necessary.
[0xB88 (2952)] recovery from cache was
started.
Information
A snapshot metadata
No action necessary.
[0xB88 (2952)] recovery from cache was
completed.
Event Logs
Reason Code
Reason
Action
Drive Time-out
Reason
Action
0x10000000
0x10000001
0x10000002
175
176
Statistics
Chapter 15
Statistics
15.1 Overview
StorView and the RAID Controller will monitor all incoming commands and calculate various statistics.
The statistics monitored include:
Command Count
Command Alignment
Command Size
Read-Ahead Statistics
Write Clustering Statistics
RAID 5/50/6 Write Statistics
From the Main screen click the Logical Drive Statistics icon in the Tool Bar.
The controller maintains individual access statistics for all logical drives, 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.
177
Figure 151
Every time statistics are viewed, the controller first outputs the time since the statistics were last reset.
However, the statistics can be cleared at any time. This is useful in determining the access pattern for a
particular test or period of time.
178
Statistic
Description
Reads
Writes
No. of Operations
This is the total number of read and write accesses that have
occurred since these statistics were reset, or the controller
was last powered on.
Bytes Transferred
This is the total number of bytes read and written since these
statistics were reset, or the controller was last powered on.
Statistics
Figure 152
Statistic
Description
Command Size
Alignment
179
Statistic
Description
180
Statistics
Figure 153
Statistic
Description
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 read-ahead. 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.
181
182
Statistic
Description
Statistics
Figure 154
Statistic
Description
183
Statistic
Description
184
Appendix A
Optimizing Write
Performance
A.1 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 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.
Note
This appendix was written for RAID 5. However, with RAID 6 which uses two parity drives, the size of the
stripe based on the number of data drives multiplied by the chunk size principle is the similar.
The illustration below 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 example below, Stripe 0 consists of C0, C1,
C2, and C3 and their associated parity P(0-3).
Figure A1
185
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 controllers ability to perform a Full Stripe Write depends on a number of
parameters:
186
Figure A2
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.
A.4 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, see Figure A1 Distribution of Data and Parity in a RAID
5 with Five Drives beginning on page 185. 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 its own rotating parity.
Figure A3
Distribution of Data and Parity in a RAID 5 with Ten Drives and Two Sub-Arrays
187
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.
Figure A4
Distribution of Data and Parity in a RAID 5 with Fifteen Drives and Three Sub-Arrays
A.6 Summary
In summary, for maximum performance, 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.
188
Troubleshooting
Appendix B
Troubleshooting
B.1 Problems You May Encounter
This appendix provides typical solutions for problems you may encounter while using StorView to control
and manage the 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.
Password Error
Lost communication
with the RAID
Controllers.
Service is hung.
189
Symptom
Reason
Solution
Lost communication
Service is hung.
with the RAID
Controllers.(continued)
Consistently occurring
time out errors when
the browser window is
open.
190
The CGI script manager may have not This may occur when heavy I/O is
released a segment of shared
happening at the same time you are
memory.
accessing StorView. If this occurs you
will need to stop and then restart the
StorView Server service.
Troubleshooting
Symptom
Reason
Solution
191
Symptom
Reason
(continued)
(continued)
Inadvertently pulled the Possible incorrect drive identification
incorrect drive from the and removal.
enclosure and the
array is dead.
Solution
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 During an array expansion, the array
in the next software release.
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.
192
Troubleshooting
Symptom
Reason
Solution
StorView displays a
message: No storage
solution found.
The host operating system is not able Ensure that the Fibre devices appear
to see the storage solution.
in your HBAs 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.
Enclosure image on
Enclosure Support option has been
the Main screen is
disabled.
dimmed or greyed out.
193
194
More on Snapshot
Appendix C
More on Snapshot
C.1 Overview
This appendix is provided to give a more in depth look at Snapshot, in order to provide a better
understanding of the technology used.
The Snapshot engine has been designed to give the user considerable flexibility when setting up and
performing snapshot and snapback operations. A snapshot allows the user to recreate a point in time
image of a logical drive that contains exactly the same data at the point the it was taken.
To recreate the data of the snapshot, a snapback is initiated. This will cause the controller to copy data
from the Overwrite Data Area (ODA) back to the snapshotted logical drive. Once completed, the logical
drive will now contain exactly the same data as it did at the time of the snapshot.
A snapshot image can also be presented back to the host server as a snapshot (virtual) logical drive, in
which the server will see this virtual LUN and its data just like any other logical drive. However, there is
one exception to snapshot (virtual) logical drives, it is only possible to read from the snapshot logical
drive. Any write commands issued to it will result in a error or check condition.
One of the most important components of Snapshot is the Overwrite Data Area or ODA. The ODA serves
as a storage area for disk data that needs to be protected from being overwritten by new data after a
snapshot was issued.
C.1.1 Terminology
The following describes some of the terminology used when working with Snapshot.
Term
Description
195
Term
Description
Snapback
Snapshot
Snapshot Number
Snapshotted LD
ODA Size
The read/write block size that the system will use when copying data
from the original logical drive to the ODA.
Virtual LUN or Snapshot LUN A special LUN created from a combination of the snapshotted logical
drives data and the data contained in the ODA.
196
More on Snapshot
197
Table C1
64 Kbytes
512 GBs
128 Kbytes
1 Terabyte
256 Kbytes
2 Terabytes
512 Kbytes
4 Terabytes
1 Mbyte
8 Terabytes
If the Overwrite Data Area storage space gets close to running out of storage space, it will alert the user.
If the Overwrite Data Area does get filled to its limit and can no longer store copy-on-write data, the
Snapshot will become out of phase with the underlying snapshotted logical drive resulting in all
Snapshots for this logical drive being invalidated by the RAID Controller.
198
More on Snapshot
199
200
Index
Index
a
About software version 135
Access
License 2
Access Alignment 186
Access Size 186
Access Statistics 178
Accessing SAN LUN Mapping 70
Accessing the Drive Information
Window 113
Advanced Settings 91
Alarm
Enable/Disable 138
Alarm Icon
Disabled 12
Muted 12
Off (Silent) 12
On 12
Alarm Monitor Icon 12, 138
Alarm Mute 138
Alignment 179
Alignment Statistics 179
Array Events 159
Array Status Icon 15
Auto Rebuild 94
Auto Spare 61, 94
Auto Update 94
Automatically Update
Controller Firmware 83
b
Background Drive Verification 94
Back-off Percent 46, 52, 108
Battery error 83
Battery Not Charging
Writeback Cache Disabled 162
Battery status 83
Battery warning 83
Bytes Transferred 178
c
Cache Flush Array 46
Caching
Snapshot 198
Changing Password 36
Check Parity 102
Chunk Size 46
Chunk size 51, 108
Clearing the Configuration 110
Clearing the Controller Logs 87
Clearing the Event Log 149
Command Cluster Count 183
Command Cluster Interval 184
Command Cluster Statistics 183
Command Size 179
Configuration
Environmental 83
Restoring 109
Saving 65
Saving/Restoring/Clearing
Overview 109
Configuration Name 93
Configuration WWN 93
Configuring Additional Monitoring 38
Configuring Array Writeback Cache 54
Configuring for E-MAIL 29
Configuring Network Settings 21, 24
Connection
Host Ports 97, 98
Controller 164
Reset 83
Shutdown 83
Controller Environmentals 81
Controller Event
Battery Failure 152
Battery OK 153
Cache Disabled 162
Cached Data Lost 154
Cntrl Temp Exceeded 151
Configuration Changed 153
Controller Failback Completed 154
Controller Failback Started 154
Controller Failed 152
Controller Failover Completed 154
Controller Failover Started 154
Controller Firmware Upgraded 154
Controller Powered On 153
Controller Present 152
Controller Removed 152
Controller Reset 153
Controller Selftest Failed 153
201
d
Data Rate 96, 97, 98
Dedicated Spare 58
Delete
SAN LUN Mapping 77
Delete a SYSLOG Server 35
Deleting
Snapshot 127
Deleting a Logical Drive 117
Deleting Addressee 30
Deleting an Array 100
Deleting an SNMP Server 32
DHCP Manager 21
DHCP Server 25
Diagnostic Dump 83
Different Node Name 93
Disable Writeback Cache 52
Disabling
Snapshot 131
Disk I/O Module 12
Drive Event
Array Critical 160, 162
202
e
E5402E RAID Controller
Host Port Settings 98
E5412E RAID Controller
Host Port Settings 98
EBOD I/O Module 11
E-MAIL Notification 29
Embedded StorView Upgrade 141
Enabling
Snapshot 119
Enclosure Events 166
Enclosure Icons 12
Enclosure Support 95
Enclosure Temperature Icon 12
Index
i
Identifying Drive Members 104
Identity 92
Initialization 46
Pause 56
Resume 56
Initialization Priority 95
Initialize 51
Initializing Arrays 55
Internal Logical Drive 195
Internet Options
Security Settings 27
InterServer Communication 1
f
F5402E & F5412E RAID Controller
Host Port Settings 97
F5404E RAID Controller
Host Port Settings 96
Failed Drives 175
Failover 133
Fan Icon 10
Faster Rebuild 188
Fault Tolerance 94
Feature License 3
Firmware
Environmental 83
Update 83
Free Space 115
Full Stripe Write Rate 183
g
Gateway 25
Getting a New IP Address
Global Access 1, 2, 28
Global Spare 57
25
h
Hardware
Environmental 83
HBA Port Name 69
Host Event
CC to Host ID 161
Controller LIP 165
Detected Power-on/Reset 164
Host Port Incorrect Address 164
Logged in at ID 165
Loop Down 164
Loop Up 164
SAS Host Port Down 164
l
License
Access 2
Feature 3
License Exceeded 4
License Managers 2
Licensing Information window 4
Local Access 2, 28
Locate Drive 114
Logical Drive
Delete 117
Expanding 115
Logical Drive Availability 46
Logical drive capacity 63
Logical Drive Status Icon 16
LUN Mapping 69
LUN number 63
m
Many-to-many mapping 33
Mapping a Snapshot 125
Mapping Name 69
MIB file 31
Mirror Cache 52
Missing 8
Modifying a SAN LUN Mapping
Modifying Arrays 101
Module Tabs 18
Monitoring initialization 53
Multicast 1
78
203
n
Navigating the Event Log
Network Settings 21
New IP Address 25
Node Name 69
Read/Write Access 69
Read-Ahead Cache 52
Read-Ahead Command Efficiency 182
Read-Ahead Command Hit Rate 182
Read-Ahead Statistics 181
Reads Statistics 178
Rebuild Priority 95
Rebuilding an Array 105
Related Documentation viii
Remote Access 28
Remote login 2
Remote StorView Servers Icon 17, 18
Remove an Individually Monitored
Server 38
Removing a Spare 60
Rescan 137
Reserved Capacity 46
Reserved capacity 52, 108
Reset
RAID Controller 83
Restore
Mapping changes 79
Restore button 79
Restoring the Configuration 109
Resume Initialization 56
Revision History viii
Rewrite Parity 103
RS-1220-E3-5402E & RS-1220-E35412E Enclosure 13
RS-1220-E3-XPN Enclosure 13
RS-1220-F4-5402E Enclosure 13
RS-1220-F4-5412E Enclosure 13
RS-4835-E3-XPN Enclosure 13
RS-4835-F4-5404E Enclosure 12
145
o
ODA 196
ODA Assignment 198
ODA Size 196
ODA Status Icon 16
ODA Storage Capacity 197
ODA Stripe Size 196, 197
ODA Stripe Sizes 198
Operating System Event Log 150
Operations
Access Statistics 178
Environmental 83
Overview 1
SAN LUN Mapping Screen 72
Overwrite Data Area 196
Overwrite Data Area Stripe Sizes 122
p
Pause Initialization 56
Performance Optimization 134
Performing a Snapback 129
Port Connection
Advanced Setting 97, 98
Port Name 69
Power Supply Icon 10
r
RAID 5 Sub-Array 187
RAID Controller Icon
E5402E & E5412E 11
F5402E 11
F5404E 11
F5412E 11
RAID Level 0 46
RAID Level 1 47
RAID Level 10 47
RAID Level 5 47
RAID Level 50 47
RAID Level 6 47
RAID Levels 45
Read Only Access 69
204
s
SAN LUN Mapping 69
Creating 74
Overview 72
Remove 77
SAS-SATA Channel Card Icons 14
Saving the Configuration 65
Scatter/Gather 134
Secure Mode 27
Secure Web Proxy 27
Sequential Access 186
Sequential Command Interval 181
Server Event
All event logs cleared 169
Index
t
Take Control Monitoring 136
Tech Support 139
Terminology
Arrays 46
SAN LUN Mapping 69
Tool Bar 6
Advanced Settings 7
Archive Configuration 7
Create Array 6
Create Logical 6
Logical Stats 6
SAN Mapping 6
Storage Assistant 6
Trust Array 108
u
Unassigned Free Space 115
Update Controller Firmware 83
Update Expansion Module Firmware 85
Updating Embedded StorView 141
Upgrading Access License 27
User Icon 18
v
Verify Parity 101
Virtual LUN Numbering
Virtual LUNs 199
199
w
Web server 1
Work Area 5
Write Cluster Rate 183
Write Performance 185
Writeback Cache 52, 108
Writeback Cache Disabled
Battery Not Charging 162
Writes Statistics 178
205
206