Imagine Communications NX2212 Nexio Farad User Guide
Reklama
Reklama
User Guide
Nexio® Farad™
NX2212
April 2014
175-100274-01
Publication Information
© 2014 Imagine Communications Corp. Proprietary and Confidential.
Imagine Communications considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine Communications. All others uses are illegal.
This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine
Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product.
Trademarks
6800+™, ADC™, CCS Navigator™, Channel ONE™, ChannelView™, ClipSync™, Delay™, D-Series™, D-Series DSX™,
Deliver the Moment™, Delivering the Moment™, FAME™, Farad™, G8™, G-Scribe™, HView™, IconMaster™,
IconLogo™, IconStation™, IconKey™, InfoCaster™, InfoCaster Creator™, InfoCaster Manager™, InfoCaster Player™,
InstantOnline™, Invenio®, Live-Update™, mCAPTURE™, Magellan™, Magellan CCS Navigator™, Magellan Q-SEE™,
MultiService SDN™, NetPlus™, NetVX™, NewsForce™, Nexio® G8™, Nexio AMP® ChannelView™, Nexio® Channel
ONE™, Nexio® ClipSync™, Nexio® Delay™, Nexio® Digital Turnaround Processor™, Nexio® Farad™, Nexio® G-
Scribe™, Nexio® IconKey™, Nexio® IconLogo™, Nexio® IconMaster™, Nexio® IconStation™, Nexio® InfoCaster™,
Nexio® InfoCaster Creator™, Nexio® InfoCaster Manager™, Nexio® InfoCaster Player™, Nexio® InfoCaster Traffic™,
Nexio® InstantOnline™, Nexio® mCAPTURE™, Nexio® NewsForce™, Nexio® NXIQ™, Nexio® Playlist™, Nexio®
Remote™, Nexio®RTX Net™, Nexio® TitleMotion™, Nexio® TitleOne™, Nexio® Velocity ESX™, Nexio® Velocity
PRX™, Nexio® Velocity XNG™, Nexio® Volt™, OPTO+™, Panacea™, Platinum™, Playlist™, Predator II-GRF™, Predator
II-GX™, Punctuate™, Remote™, RTX Net™, QuiC™, Q-SEE™, SD-STAR™, Selenio™, Selenio 6800+™, SelenioNext™,
Selenio X50™, Selenio X85™, Selenio X100™, TitleMotion™, TitleOne™, Velocity ESX™, Velocity PRX™, Velocity
XNG™, Versio™, Videotek® SD-STAR™, X50™, and X85™ are trademarks of Imagine Communications or its subsidiaries.
Altitude Express®, Connectus®, Enabling PersonalizedTV®, ICE® Broadcast System, ICE Illustrate®, ICE-Q® algorithms, ICEPAC®, Imagine ICE®, Inscriber®, Inscriber® Connectus®, Invenio®, NEO®, Nexio®, Nexio AMP®,
PersonalizedTV®, RouterWorks®, Videotek®, Videotek® ASI-STAR®, Videotek® GEN-STAR®, and Videotek® HD-
STAR® are registered trademarks of Imagine Communications or its subsidiaries.
Microsoft® and Windows® are registered trademarks of Microsoft Corporation. HD-BNC is a trademark of
Amphenol Corporation. Some products are manufactured under license from Dolby Laboratories. Dolby and the double-D symbol are registered trademarks of Dolby Laboratories. DTS Neural audio products are manufactured under license from DTS Licensing Limited. DTS and the Symbol are registered trademarks & the DTS Logos are trademarks of DTS, Inc. © 2008-2010 DTS, Inc. All other trademarks and trade names are the property of their respective companies.
Contact Information
Imagine Communications has office locations around the world. For locations and contact information see:
http://www.imaginecommunications.com/contact-us/
Support Contact Information
For support contact information see:
Support Contacts:
http://www.imaginecommunications.com/services/technical-support/
eCustomer Portal:
http://support.imaginecommunications.com
© 2014 Imagine Communications Corp. Proprietary and Confidential
Contents
About This Guide
...................................................................................... 1
Finding Specific Information in This Guide ................................................... 1
....................................................................................... 2
................................................................................. 3
............................................................................. 3
Unpacking/Shipping Information
.................................................................. 4
Unpacking a Harris Product ................................................................... 4
Returning a Harris Product .................................................................... 4
............................................................................................ 5
Chapter 1 Quick Tour
................................................................................................ 8
Enclosure Section — Descriptions and Conditions
..................................... 10
Enclosure Component Icons ...................................................................... 13
NXS2200SRC RAID Controller ............................................................. 13
NXS2200SSC SAS Disk I/O Module on Expansion chassis ..................... 14
NXS2200SPS Power Cooling Module Icons ......................................... 14
Enclosure Temperature Icons ..................................................................... 15
©2011 Harris Corporation. All rights reserved.
iii
iv
Contents
Array and Logical Drive — Descriptions and Conditions
...........................17
Server Sidebar and Top Section — Descriptions and Conditions
Remote StorView Servers Icon ...................................................................21
Storage System: Unmonitored ...................................................................22
Module Tabs (RAID Module) ......................................................................22
Chapter 2 Initial Setup
.............................................................................................23
Accessing and Configuring Network Settings using Ethernet
..................24
Configuring Network Settings using StorView
..........................................25
............................................................................26
Chapter 3 Getting Started
........................................................................................27
.........................................................................................28
......................................................................30
..............................................................................................................31
Configuring SNMP Traps ...........................................................................31
..........................................................................................................32
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
v
............................................................................... 35
..................................................................................... 36
Monitoring Stacks on a Different Subnet ................................................... 37
Remove Monitored Stack IP ...................................................................... 38
Chapter 4 Configuring a Storage System
......................................................... 39
..................................................................................... 40
Pause/Resume the Initialization ................................................................. 42
Resume Initialization ........................................................................... 42
Adding and Removing Global Spare Drives
............................................... 42
............................................................................... 48
............................................................................. 50
Chapter 5 Controller Advanced Settings
.......................................................... 55
........................................................................................ 56
Advanced Power Management (APM)
........................................................ 62
Drive Power Management ......................................................................... 63
.................................................................. 66
Overload Management ............................................................................. 69
Chapter 6 Environments
........................................................................................... 71
........................................................................... 72
©2011 Harris Corporation. All rights reserved.
vi
Contents
Updating the Firmware (UID) ...............................................................75
Determining the Version of Firmware on Expansion Modules ..............78
Clearing the Controller Logs ...............................................................79
Exporting the Controller Logs ..............................................................81
Enclosure Environmental Information
.........................................................83
Chapter 7 Managing the Storage System
.........................................................87
...........................................................................88
Identifying and Replacing a Failed Drive .....................................................97
Slot Empty Mode ..............................................................................100
.................................................................108
Array Power Management (APM Level 2) .................................................108
Restoring and Clearing the Configuration
................................................114
Restoring the Configuration ....................................................................114
Clearing the Configuration ......................................................................117
............................................................................120
Accessing the Drive Information Window ................................................120
Advanced Logical Drive Functions
.............................................................123
Viewing Unassigned Free Space ...............................................................123
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
vii
S.M.A.R.T Alert and Proxy Mode
............................................................... 127
Chapter 8 Additional Functions
......................................................................... 131
................................................................................ 132
................................................................. 132
Chapter 9 Support and Updates
......................................................................... 135
Accessing Tech Support Through StorView
.............................................. 135
.................................................................. 136
Chapter 10 Statistics
.................................................................................................. 137
.......................................................................................... 138
Command Size — Alignment Statistics
..................................................... 139
................................................................................. 141
....................................................................... 143
Appendix A
................................................................... 145
................................................................................................ 146
....................................................................................... 147
Number of Outstanding Commands ....................................................... 147
.................................................................................................. 147
............................................................................... 150
..................................................................................................... 150
©2011 Harris Corporation. All rights reserved.
viii
Contents
Appendix B
...........................................................................................151
..................................................................................158
....................................................................................160
Navigating the Event Logs .......................................................................161
Clearing the StorView Event Log
...............................................................167
...............................................................................................168
Advanced Power Management Events .....................................................183
Persistent Reservation Events ...................................................................206
SAS Discovery Error Codes .......................................................................207
Chapter C Inter-Stack Communication Method
..........................................233
Glossary
.....................................................................................................235
©2011 Harris Corporation. All rights reserved.
List of Procedures
To verify if the Array is in a Non-Fault Tolerant vs. Fault Tolerant Warning state 11
To configure network settings using StorView ................................................. 25
To use the DHCP Server network interface setting ........................................... 26
To manually configure the network interface setting ........................................ 26
To obtain a new IP address from the DHCP server ............................................ 26
To configure the E-Mail notifications perform the following ............................. 28
To change the access password used at log in. ................................................ 35
To specify additional StorView server(s) on a different subnet .......................... 37
To remove a monitored stack IP address .......................................................... 38
To view and manage controller environmental conditions and functions .......... 72
©2011 Harris Corporation. All rights reserved.
ix
x
Contents
To determine the Firmware version on expansion modules ...............................78
To view status and version from the Enclosure Information window .................83
To verify and correct the parity data on the Array .............................................94
To find and replace a drive that has entered Failure mode ................................98
To find and replace a drive that has entered Slot Empty mode .......................100
To manually spin up or spin down an array ....................................................111
To locate the physical location of a disk drive .................................................121
To view how much available space is left on StorView ....................................124
To update the Embedded StorView software .................................................136
To have multiple commands active for all disk drives ......................................148
To export the log file from Internet Explorer ...................................................162
©2011 Harris Corporation. All rights reserved.
About This Guide
About This Guide
provides an overview of this guide, describes guide conventions, and tells you where to look for specific information. This section also contains important information on unpacking and shipping your Harris product.
What’s in
This Guide
This user guide gives you step-by-step instructions on how to setup and use the
StorView Storage Management RAID Module software. This manual supports the
RAID and Expansion enclosure storage systems listed in the
If the information in the release notes shipped with your product differs from the information in this guide, follow the instructions in the release notes.
Intended
Audience
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.
Finding Specific Information in This Guide
This table shows the location of specific information in this guide.
If you are looking for
Starting StorView and configuring E-Mail, SYSLOG, SNMP, and additional monitoring
Configuring the storage system from defining disk arrays, assigning spares, and configuring the logical drives
Go to
©2011 Harris Corporation. All rights reserved.
1
2
About This Guide
Writing Conventions
This guide uses the following writing conventions.
Table 1-1
Writing Conventions
Convention
Bold
Italics
CAPS
Code
>
hyperlink
Internet address
Step_heading
Definition
Indicates dialog box, property sheet, field, button, check box, list box, combo box, menu, submenu, window, list, and selection names.
Indicates e-mail addresses, names of books and publications, and first instances of new terms and specialized words that need emphasis.
Indicates a specific key on the keyboard, such as ENTER,
TAB, CTRL, ALT, DELETE.
Indicates variables or command-line entries, such as a
DOS entry or something you type into a field.
Indicates the direction of navigation through a hierarchy of menus and windows.
Indicates a jump to another location within the electronic document or elsewhere.
Indicates a jump to a Web site or URL.
Indicates an introduction to a procedure or series of procedural steps.
Tip
Note text
Indicates important information that helps to avoid and troubleshoot problems.
Caution text Indicates important information that if not followed could cause system problems.
Indicates information that may be helpful, including related topics, shortcut keys, or ways to improve smooth operation of hardware and software.
Danger text Indicates information that conditions or practices that can result in personal injury or loss of life.
Warning text
Indicates information that if not followed could prevent system operation or cause it damage.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
3
Related Documentation
Farad Hardware and Commissioning Guide
Farad Customer Care Card and Installation Check list
Farad Troubleshooting Guide
Obtaining Documentation
Manuals, User Guides and other documents can be viewed or downloaded from the Harris website at http://ecustomer.broadcast.harris.com
.
1
In the
Customer Login
area, enter your
User
and
Password
, and click
Submit
.
OR
Click
New User
to register with Harris.
The
Harris Welcome
page displays.
2
Under
Self Service
, select
Review Documentation
.
3
Under the
Table of Contents
, click
Servers > Storage Systems > Farad
.
4
Click on the title of the document, and click
Open
to view it.
OR
Click
Save
to download the document.
Alternatively, contact your Harris customer service representative to request a document.
Purchasing
Manuals
Alternatively, you can purchase product documentation on our
Harris E-commerce site , or contact your Harris customer service representative to request a document.
©2011 Harris Corporation. All rights reserved.
4
About This Guide
Unpacking/Shipping Information
Unpacking a Harris Product
All Harris NEXIO products have been carefully inspected, tested, and calibrated before shipment to ensure stable and trouble-free service.
1
Check the equipment for any visible damage that may have occurred during transit.
2
Confirm that you have received all items listed on the packing list.
3
Contact your Harris NEXIO dealer if any item on the packing list is missing.
4
Contact the carrier if any item is damaged.
5
Remove all packaging material from the product and its associated components before you install the unit.
Returning a Harris Product
In the unlikely event that a Harris product fails to operate properly, contact the
Harris Customer Service Department to obtain a Return Material Authorization
(RMA) number, then send the unit back for servicing. Include the RMA number on the outside of the return box.
Keep at least one set of original packaging in the event that a product needs to be returned for service. If the original package is not available, you can purchase replacement packaging from Harris Corporation. Otherwise, you can supply your own packaging as long as it meets the following criteria:
The packaging must be able to withstand the product’s weight.
The product must be held rigid within the package.
There must be at least 2 in. (5 cm) of space between the product and the container.
The corners of the product must be protected.
If the product is still within the warranty period, Harris Corporation will return it to you by prepaid ground shipping after servicing.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
5
Technical Support
Technical support is available 24 hours a day, 7 days a week. You can contact technical support by phone or e-mail.
Harris Broadcast Division Support:
Call:
1-416-445-4032
Toll Free:
+1 (888) 534-8246
Email:
website:
http://support.broadcast.harris.com
Video Server Division
website:
http://www.broadcast.harris.com/products/servers
Email:
U.S., Canada, Central America, and Latin America (CALA)
Video Processing, Distribution, Servers, Storage, News, Inscriber and Videotek
Call:
1-888-534-8246
Fax:
1-416-445-9020
Email:
Europe, Middle East, and Africa
24 hours a day, 7 days a week
Regular Business Hours (9am to 5pm, Monday to Friday)
24/7 Support line: +44-118-964-8100
Fax:
+44-118-964-8054
Email:
Infrastructure products:
RMA’s:
DAM Support:
ADC Automation:
D Series Support:
Transmitters:
©2011 Harris Corporation. All rights reserved.
6
About This Guide
Asia, Pacific Rim
24 hours a day, 7 days a week
Regular Business Hours (9am to 5pm HKT Monday to Friday)
Call:
+852-2776-0628
After-Hour Hotline:
1-888-534-8246
Fax:
+852-2776-0227
Email:
©2011 Harris Corporation. All rights reserved.
1
Quick Tour
StorView® is a full-featured graphical HTML-based software suite designed to configure, manage, and monitor NEXIO Farad Storage Systems on a facility wide basis.
StorView’s Hypertext Transfer Protocol Daemon (httpd) server hardware is embedded in the RAID Controller module and is upgradeable via firmware load.
The following topics are included:
Enclosure Section — Descriptions and Conditions
Array and Logical Drive — Descriptions and Conditions
Server Sidebar and Top Section — Descriptions and Conditions
7
©2011 Harris Corporation. All rights reserved.
8
Chapter 1
Quick Tour
The Work Area
The StorView work area consists of the Main screen and its dialog windows for performing specific functions. On the Main screen you will find the Toolbar, sections for Arrays and Logical Drives, an Enclosure section and a Server section.
Through the use of interactive components, animated icons, and mouse over information an intuitive, easy-to-use approach is provided to manage your storage system.
There are also primary configuration functions which include creating disk arrays, logical drives, LUN mapping and assignment of spare drives.
You also have access to advanced features that allow for array and logical drive expansion, optimizing controller parameters, rebuilding arrays, managing E-Mail notices of events, SYSLOG, and SNMP traps, reviewing event logs, and analyzing system statistics.
Tool Bar
These icon buttons displays at the top of the work area and define the tool bar section of the work area. They provide a one click access to primary functions.
Create
Array
Create
Logical Drive
Not
Used
Figure 1-1
StorView Tool Bar
©2011 Harris Corporation. All rights reserved.
Logical Drive
Statistics
Advanced
Settings
Archive
Configuration
NEXIO Farad
User Guide
9
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
Create Array
Use this to open the Create Array window and create new disk arrays.
Create Logical
Drive
Use this to open the Create Logical Drive window and configure new logical drives.
This button opens the Statistics window.
Logical Drive
Statistics
Advanced
Settings
Use this to change controller parameters.
Archive
Configuration
Use this to save, restore, or clear the configuration.
NOTE:
When clearing a configuration this will delete all arrays and logical drives, as well as the data on those logical drives.
©2011 Harris Corporation. All rights reserved.
10
Chapter 1
Quick Tour
Enclosure Section — Descriptions and Conditions
This section displays the front and rear views of the RAID enclosure and expansion enclosures.
Click to Locate
Enclosures
Enclosure ID
(WWN)
Temperature
Monitor Icon
Indicates the number of
Enclosures found
Click a drive icon to open the Drive
Information window
Alarm
Monitor Icon
RAID
Controller
Icons
Animated
Drive Status
Icons
Power Cooling
Module Icons
Figure 1-2
Enclosure Section
Drive Status
Icons
These icons display 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. Clicking the icon opens the
Drive Information
window.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
11
Drive Status Icons
Icon Name
Array Member
Array Member
(Spun-Down)
Available
Condition
Disk drive is a member of an array.
Disk drive is a member of an array but is spun down under APM.
This should never appear on NEXIO Farad storage.
Disk drive is online and must be either selected for use in an array or assigned as a global spare. It is not good practice to leave a drive in available status.
Available
(Spun-Down)
Critical
Disk drive is online and available for use in an array or as a global spare but is spun down under
APM.
Not normally used on NEXIO Farad storage systems.
Drive(s) are members of a fault tolerant array and are in a non-fault tolerant state.
With RAID 6 disk arrays, the loss of a single drive does not place the array in a non-fault tolerant state. The drive status icon is the same for single or dual drive failures.
To verify if the Array is in a Non-Fault Tolerant vs. Fault Tolerant Warning state
1
Identify the number of drive failures for the array. Two drive failures will put the RAID 6 array in a non fault tolerant state.
2
Passing the mouse pointer over the status icon (yellow) will display the array’s status, also in the Array Information screen the status is displayed.
Dedicated Spare
Dedicated Spare
(Spun-Down)
Empty
Disk drive is marked as a dedicated spare to an array.
Not normally used on NEXIO Farad storage systems.
Disk drive is marked as a dedicated “cold” spare to an array but is spun down under APM.
Not normally used on NEXIO Farad storage systems.
No disk drive was detected. Empty slots compromise the cooling airflow. Drive slots should not be left empty for more than 10 minutes.
©2011 Harris Corporation. All rights reserved.
12
Chapter 1
Quick Tour
Drive Status Icons
Icon Name
Expanding
Failed
Failed Array
Member
Failed Array
Member (Spun
Down)
Global Hot Spare
Global Spare
(Spun-Down)
Initializing
Locate
Proxy Mode
Missing
Rebuilding
Condition
This icon is displayed on the drive members whose array is expanding.
Not normally used on NEXIO Farad storage systems.
Disk drive has failed.
This icon will appear on all disk drives that are members of an array that has failed. This will occur if more than 2 drives fail in a RAID-6 array.
This disk drive is a member of an array. It has failed and was spun down under APM.
Disk drive is a global spare.
Disk drive is a global “cold” spare but is spun down under APM.
Disk drive is a member of an array being initialized.
Clicking the “arrow” icon next to the “specific array” in the Arrays section displays an “arrow” icon on all the drive members of that array in the front enclosure view.
Indicates the drive is in a state that is only accessible via one controller. Reasons include accidental disconnection of one of the peripheral frame interconnect cables, or a drive that has failed on one of the two SAS data ports. This condition will clear within 6 minutes after the root cause has been corrected.
Indicates that StorView is unable to determine the status of the drive.
Drive members of an array are in rebuild mode.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
13
Drive Status Icons
Icon Name
SMART Alert
Verifying
Updating
Firmware
Unsupported
Condition
Indicates the drive’s monitoring system has detected a number of errors, indicating a possible impending failure. Drives that enter this state should be scheduled for replacement at a convenient time. The drive may enter the "failed" state within a few days after entering the SMART
Alert state.
This icon is displayed on the drive members whose array’s parity data is being verified.
This icon will appear when the subject drive’s firmware is being updated.
This icon is displayed when a drive does not match the other drives for the array. There are two images, one is for when the drive is a member of an array and the last one is when it is not a member of an array.
Enclosure Component Icons
The following icons appear on the Main screen in the Enclosure section. They provide an instant view of the operating status of the enclosure components, and clicking the icons will open the Controller Information window.
NXS2200SRC RAID Controller
Normal
Error
Empty
RAID Controller is operating normally.
A RAID Controller has failed in an
Active-Active topology or the backup battery has failed.
This icon represents the empty controller slot for future expansion. A blank plate is shown.
©2011 Harris Corporation. All rights reserved.
14
Chapter 1
Quick Tour
NXS2200SSC SAS Disk I/O Module on Expansion chassis
Normal
Error
Missing
Empty
Communication Error
Disk I/O Module is operating normally.
Disk I/O Module has failed.
Disk I/O is missing from the slot.
Disk I/O is removed and a blank plate is installed.
The process has lost communication with the enclosure, indicated by the icon becoming grey or dim. Or you have disabled “Enclosure Support” in the Controller Advanced Settings.
NXS2200SPS Power Cooling Module Icons
Normal
Warning
Failure
Unknown
Missing
Communication Error
The Power Cooling Module is operating normally.
Indicates either the fan or the power supply is critical, or both are critical.
Indicates either the fan or the power supply has failed, or both have failed.
The Power Cooling Module status cannot be determined.
The Power Cooling Module cannot be located.
The process has lost communication with the enclosure, indicated by the icon becoming grey or dim. Or you have disabled “Enclosure
Support” in the Controller Advanced Settings.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
15
Alarm Monitor Icons
OFF
ON
This icon indicates the alarm is silent.
This icon indicates the alarm is On (Continuous), On
(Intermittent), or On (Remind).
This icon indicates the alarm is muted.
Mute
Disabled
This icon indicates the alarm is disabled.
Clicking the icon will open a window to manage the alarm policies. If you mute the alarm in a multiple enclosure systems, all enclosure alarms will be muted.
Enclosure Temperature Icons
These icons are displayed just above the rear enclosure icon and indicate enclosure temperature status.
Normal
Warning
Failure
Missing
When green, the temperature is normal.
When yellow, the enclosure temperature is approaching the established threshold.
When red, the enclosure temperature has reached or exceeded the enclosure temperature threshold. (If the fans are operating normally and the air flow temperature seems normal it may be an indication that the temperature sensor is faulty.)
This icon indicates that the information from the SES regarding the sensors is invalid or missing.
Temperature
Sensors
Passing the mouse pointer over the Enclosure Temperature Icon will display either 8 or 10 temperature sensors. There are 8 for the NXS2212x7EXP Expansion enclosure and 10 sensors for NXS2212x7CORE RAID Controller enclosure. Exceeding the limits of these “Critical” values will cause a notification to occur.
©2011 Harris Corporation. All rights reserved.
16
Chapter 1
Quick Tour
Table 1-1
Temperature Sensor Identification and Threshold Values
6
7
8
4
5
2
3
Sensor
#
Location and Type
1 Enclosure Ambient.
Enclosure Midplane.
PCM 0* Inlet.
PCM 0* Hotspot.
9
10
PCM 1* Inlet.
PCM 1* Hotspot.
Critical
Cold
Warning
Cold
0°C/32°F 5°C/41°F
Warning
Hot
Critical
Hot
40°C/104°F 42°C/107°F
5°C/41°F 10°C/50°F 50°C/122°F 55°C/131°F
5°C/41°F 10°C/50°F 50°C/122°F 55°C/131°F
5°C/41°F 10°C/50°F 65°C/149°F 70°C/158°F
5°C/41°F 10°C/50°F 50°C/122°F 55°C/131°F
5°C/41°F 10°C/50°F 65°C/149°F 70°C/158°F
Bay 0* (Upper I/O Bay) Ambient.
5°C/41°F 10°C/50°F 68°C/154°F 73°C/163°F
Bay 0* (Upper I/O Bay) RAID
Controller Processor.
1°C/34°F 5°C/41°F 90°C/194°F 100°C/
212°F
Bay 1* (Lower I/O Bay) Ambient.
5°C/41°F 10°C/50°F 68°C/154°F 73°C/163°F
Bay 1* (Lower I/O Bay) RAID
Controller Processor.
1°C/34°F 5°C/41°F 90°C/194°F 100°C/
212°F
Sensor numbers 8 and 10 are exclusively for the RAID Controller modules and are not present in the expansion enclosures. An oddity exist in the software presentation of sensors related only to the Expansion enclosure enclosures. Sensor number 9 is reported as sensor number 8. So you see the sensors listed as 1-8 for each Expansion enclosure. The value presented for sensor number 8 is actually the
I/O Bay 1 ambient temperature sensor number 9.
©2011 Harris Corporation. All rights reserved.
Array and Logical Drive — Descriptions and Conditions
NEXIO Farad
User Guide
17
Figure 1-3
Array and Logical Drive Section
©2011 Harris Corporation. All rights reserved.
18
Chapter 1
Quick Tour
Array Status
Icon
These icons are found in the Array section and depict the current state of the specific component.
Green
(Normal)
Status is okay.
Yellow
(Warning)
Red
(Error)
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.
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.
Logical Drive
Status Icon
These icons are found in the Logical Drive section and depict the current state of the specific component.
Green
(Normal)
Status is okay.
Yellow
(Warning)
Red
(Error)
Indicates the logical drive is part of an array that is degraded. For logical drives consisting of RAID 6 arrays, it indicates 1 or 2 drives have failed. See Drive Status Icon
“Critical” state.
Indicates the logical drive is part of an array which is invalid or offline:
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 in the same sub-array.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
19
ODA Status
Icon
NOT USED ON NEXIO Farad Storage System.
This icon is found in the Logical Drive section adjacent to the logical drive and depicts it’s current state.
Normal
Warning
Failed
ODA is okay.
ODA is reaching capacity. Free up ODA space by deleting unneeded snapshots. A warning will appear when a minimum amount of space remains on the ODA. The specific amount is dependant on the size of the ODA.
The ODA has run out of space. All snapshots are invalid. In order to resume operations, delete all snapshots.
Trusted Array
Icon
Trusted
Array
This icon is found in the Array section, adjacent to a disk array.
It indicates that the array has been created bypassing the parity check.
This must not be used for NEXIO Farad storage.
At the top of the Arrays and Logical Drives section are values displayed in parenthesis next to each title. The value indicates the total number of Arrays for the storage system, Logical Drives for the storage system.
©2011 Harris Corporation. All rights reserved.
20
Chapter 1
Quick Tour
Server Sidebar and Top Section — Descriptions and Conditions
Module tab indicates general status of entire module. Red indicates error. Yellow is warning.
Gray is normal
Controller Icon (dual active-active shown)
Clicking the controller name opens Controller
Information
Tech Support.
Help and
About buttons
Storage system Icon
(an icon is displayed for each system attached to this host)
Number of users logged into this
StorView Server
Logged in StorView
Server Icon
Remote StorView
Server Icons
(Discovered) Also displays the Host
Logs, Rescan and settings buttons
Figure 1-4
Server Sidebar Section
Name and IP Address of the logged in host
StorView
Server Icon
These icons display on the Server Sidebar section on the Main screen. They depict the current server and discovered servers. The icon indicates the status of the server components by changing its color and state.
Normal (Gray)
Warning
(Flashing Yellow)
Failed
(Flashing Red
Status is okay.
Indicates a server warning that a device connected is in degraded mode.
Indicates a server error or device malfunction.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
21
Warnings and errors should be investigated by clicking on the flashing icon. This will redirect your browser to the GUI for the complaining controller.
Remote StorView Servers Icon
Flashing
White
The server has not responded in at least 40 seconds and is considered missing. If you would like to remove the missing server from the list, click the Rescan button. This will refresh the screen with a current list of discovered servers.
User Icon
Located adjacent to Server icon
Represents each user logged into the StorView server you are monitoring.
Placing the mouse pointer over the icon will display the IP address, host name and the user name.
Storage System Icon
This icon is displayed for each storage system.
You will also see the warning “
!
”, error, and unknown icons for unfocused storage systems that are being monitored as well.
Normal (Gray)
Status is okay.
Warning (Flash
Yellow with red “!”)
Error (Flashing Red)
Unknown (Flashing
Red with “?”)
Indicates a component in the storage system is in degraded mode.
Indicates a component in the storage system has malfunctioned.
Indicates that the storage system was there at startup but now cannot be located.
©2011 Harris Corporation. All rights reserved.
22
Chapter 1
Quick Tour
Storage System: Unmonitored
Storage
System:
Unmonitored
This icon indicates that the StorView server, located in the other controller module, is monitoring this storage system, or if you just performed a rescan then the two modules are still determining which one will take control of the monitoring of the storage system.
Controller
Icon
This icon represents the RAID Controller installed in the enclosure. For duplex systems (Active-Active), a dual controller image is displayed.
Normal
A green icon represents a normal operating system.
Error
A flashing red icon appears if the controller’s backup battery unit has failed, or in Active-Active topologies when the partner controller has failed.
Module Tabs (RAID Module)
The tab displays 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.
©2011 Harris Corporation. All rights reserved.
2
Initial Setup
After completing your hardware set up, ensure you have a shielded Cat 5 or better
Ethernet cable connected to the controller’s networking port (StorView Embedded
Module port (RJ-45)) and your network hub or host computer Ethernet port. If you are connecting to the network hub, use a standard Ethernet cable. If you are connecting to your host port, use a cross-over Ethernet cable. The first time you start Embedded StorView, you must configure the network settings.
The following topics are included:
Accessing and Configuring Network Settings using Ethernet
Configuring Network Settings using StorView
23
©2011 Harris Corporation. All rights reserved.
24
Chapter 2
Initial Setup
Accessing and Configuring Network Settings using Ethernet
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. This is not normally the case during initial setup.
Tip
If the IP address is not defined and a DHCP server is configured, 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
Do one of the following:
Look for
esv0
or
esv1
in your
DHCP Manager
software.
StorView can then be accessed via a web browser pointed to
http://<cname or IP address>:9292
If neither of the conditions above exists, the software assigns a default
IP address of
10.1.1.5
for Controller 0 (the top module) and
10.1.1.6
for Controller 1.
Set your host IP address to
10.1.1.20
with subnet mask
255.0.0.0
.
Storview can then be accessed via a web browser pointed to
http://10.1.1.5:9292
or
http://10.1.1.6:9292
.
When Storview has been successfully accessed via one of these two methods, the final IP addresses can be set using the dialog found by clicking the “Settings” button.
A tool is provided to configure new embedded StorView modules. You can download it from the
Harris Support Portal
at: http://support.broadcast.harris.com
.
Click
Download Software Updates
, then click
Servers > Storage Systems >
Farad.
For details on using this tool, see
To use the GUI-based embedded
StorView setup tool
on page 76 of the
NEXIO Farad Hardware Guide
.
StorView is started by launching your web browser and entering the IP address of
the embedded controller followed by “:9292.” For more information, see
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
25
Configuring Network Settings using StorView
To configure network settings using StorView
1
Click the SETTINGS button on the Main screen and select the PREFERENCES tab.
The StorView Host Name field will have a default name, “esv0” for Controller 0 and “esv1” for Controller 1.
2
(Optional) If you don’t want to use the default name, you may enter different name for this Embedded StorView server.
If the StorView Host name displays esverr , this indicates a problem with the
Embedded StorView server module. Contact technical support.
Figure 2-1
Settings Screen – Preference Tab (Dynamic IP Selected)
©2011 Harris Corporation. All rights reserved.
26
Chapter 2
Initial Setup
Using Dynamic IP (DHCP)
StorView does not display the TCP/IP information when Dynamic IP (DHCP) is selected. You must use a third-party network administration program to obtain this information.
To use the DHCP Server network interface setting
1
Click the option button next to
Dynamic IP (DHCP)
.
2
Click
APPLY
to make the changes effective.
3
Click
CLOSE
.
Using Static IP
To manually configure the network interface setting
1
Click the option button next to
Static IP.
2
In the
IP Address
field, enter the IP address and press the
TAB
key, or click in the
Subnet Mask
field.
3
In the
Subnet Mask
field, enter a Subnet Mask and press the
TAB
key, or click in the
Default Gateway
field.
4
Enter the gateway or router address and press the
TAB
key, or click in the
DNS
Server
field.
5
Enter the DNS Server IP address.
6
Click
APPLY
to make the changes effective.
7
Click
CLOSE
.
Getting a New IP Address
If you are set up to receive your IP address using Dynamic IP (DHCP), you can force the Embedded StorView server to obtain a new IP address from your DHCP server.
To obtain a new IP address from the DHCP server
1
Click
SETTINGS
and select the
PREFERENCES
tab.
2
Click the
Renew
check box.
3
Click
APPLY
to make the changes effective.
4
Click
CLOSE
.
©2011 Harris Corporation. All rights reserved.
3
Getting Started
The following topics are included:
Monitoring Stacks on a Different Subnet
©2011 Harris Corporation. All rights reserved.
27
28
Chapter 3
Getting Started
Starting StorView
Embedded
StorView
Embedded StorView is started by opening your web browser software and entering the IP address assigned to the controller’s embedded module followed by the port number. The format is “HTTP://10.1.1.5:9292.” For the first startup of the embedded version you will need to perform some network configuration of the module, refer to
Configuring Network Settings using StorView
Some browsers will require the "http://" to be entered due to the non-standard port used.
To log into StorView
1
Open your web browser and entering the explicit IP address assigned to the
Embedded StorView
server followed by the port number
(e.g., HTTP://10.1.1.5:9292).
2
Upon startup, you will be prompted for a user name and password. The default user name is
admin
and password is the word
password
.
Configuring E-Mail Notices
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
From the Main screen click the SETTINGS button.
The Settings window will open with the E-MAIL tab selected.
All fields have a limit of 127 ASCII characters.
2
Enter the “name” or “IP address” of your E-Mail server.
This will be the SMTP mail server name. E-Mail messages are sent to the E-Mail server using port 25.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
29
If your E-Mail server is not configured to receive on port 25, then E-Mail will not function properly.
3
The “From” field should be pre-configured using the software name followed by your fully qualified domain name. If you change this setting be sure it is compliant with your IS policy.
4
The “Reply-To” field should be completed using a desired e-mail address that recipients could respond to when they receive these automatically sent e-mails. This field by default will be blank.
5
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.
6
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
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.
7
Once complete, click the APPLY button.
©2011 Harris Corporation. All rights reserved.
30
Chapter 3
Getting Started
You will receive a confirmation message that the changes were successfully completed. Click the CLOSE button.
8
Test the configurations by clicking the TEST button.
You will receive a confirmation message that the test was successfully completed, and each addressee will receive a “Test Message” from the mail server. Click the
CLOSE button.
9
Click the CLOSE button on the SETTINGS window.
Deleting an E-Mail Addressee
To delete an email addressee
1
From the Main screen click on the SETTINGS button. The SETTINGS window will open with the E-MAIL tab selected.
2
Click the DELETE button next to the E-Mail Address name you want to remove. The address is immediately removed.
3
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.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
31
SNMP
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.
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.
To configure SNMP traps
1
From the Main screen click on the SETTINGS button.
2
Click the SNMP tab.
If your system requires a MIB file, download it by clicking the link in this window.
3
Enter the SNMP Server name or IP address of the host you want to receive SNMP traps.
4
Enter the IP port on which the SNMP Server expects to receive traps. The default is
162.
5
Enter the Community to which the trap belongs. The default is public. SNMP
Servers may belong to several different communities or receive packets for different communities.
6
Select the level of events you want to be included in the traps. You can select from
Information, Warning and Error types.
Figure 3-1
Settings Screen – SNMP Tab
©2011 Harris Corporation. All rights reserved.
32
Chapter 3
Getting Started
7
Click the APPLY button.
8
Test the configurations by clicking the TEST button.
You will receive a confirmation message that the test was successfully completed, and each addressee will receive a “Test Message.” Click the CLOSE button.
9
Click the CLOSE button on the SETTINGS window.
Deleting an SNMP Server
To delete an SNMP server
1
From the Main screen click on the SETTINGS button.
2
Click the SNMP tab.
3
Click the DELETE button next to the SNMP Server you want to remove. The server is immediately removed.
4
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.
SYSLOG
StorView’s Syslogd agent is a module designed for StorView that enables sending
RAID system event logs to all listening syslogd clients on all installed platforms.
StorView syslogd is designed for greater flexibility in that it supports
“many-to-many” mapping.
You may have:
Multiple syslogd servers that monitor a single RAID storage system for event logs.
A single syslogd server that monitors multiple RAID storage systems for event logs.
Multiple syslogd 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 syslogd server will not have any impact if another syslogd server is functioning normally.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
33
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://syslog-win32.sourceforge.net/) which runs as a
Windows service.
Syslog
Daemon
The daemon listens for incoming event log messages on port 514. It logs them to a messages file.
The syslogd messages consist of:
Facility - indicates the type of syslog message. For example they can be kernel, user level, mail system and system daemon messages.
Priority - indicates the sensitivity of the message, to include: Information,
Warning, or Error.
Timestamp - indicates the date and time of the event.
Originating Device - specifies which device originated the event message.
Message Content - provides a plain language content of the event message.
Syslogd daemon supports both Linux and Windows platforms.
Operational
View
Whenever a new event is logged, based on the type of event, StorView syslogd will send the message out to all of its subscribers that match the type of event involved.
If the event was an Error type, and all daemons are configured to receive that type, then they will all receive the event. If the event was an Information type, only those daemons configured to receive Information type will receive the event.
Event logs are sent in standard text format and have no encryption, in such security can be a concern. Additionally UDP packets are involved so there is no assurance that the event log arrived at the subscriber (syslogd server).
Configuring Syslogd Server
You will see the following screen when the SYSLOG tab is selected.
The following fields are described:
syslogd Server.
Allows the user to enter the IP address of the syslogd servers.
An error message is displayed if an invalid server name is entered.
©2011 Harris Corporation. All rights reserved.
34
Chapter 3
Getting Started
syslogd Port.
Allows the user to enter a specified syslogd 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).
If checked the recipient would receive Informational type of event logs.
Warning (W).
If checked the recipient would receive Warning type of event logs.
Error (E).
If checked the recipient would receive Error type of event logs.
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.
Send out a dummy test message to the specified recipient servers.
To configure Syslogd servers
1
Enter the IP addresses of the host servers designated to be syslogd servers.
2
Enter the port ID of the recipient syslogd server. You must enter a correct value otherwise you will receive an error message.
3
Select the check boxes under the severity/priority icons.
4
Click the APPLY button to save your settings.
5
If you are finished completing the setup, click the CLOSE button on the SETTINGS window.
6
(Optional) Test the settings by clicking the TEST button.
You will receive a confirmation message that the test was successfully completed, and each syslogd server will receive a “Test Message.” Click the CLOSE button.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
35
Delete a Syslogd Server
To delete a Systlogd server
1
Access the Settings window and select the SYSLOG tab.
2
Click the DELETE button next to the “syslogd server” you want to remove. The server name is immediately removed.
3
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.
Changing the Password
To change the access password used at log in.
1
From the Main screen click on the SETTINGS button.
2
Click the PASSWORD tab at the top of the window.
Figure 3-2
Settings Screen – Password Tab
Passwords will not be displayed as you type them.
3
Type in the Old Password and press the <Tab> key or click in the next text box.
4
Type in the New Password and press the <Tab> key or click in the next text box.
5
Re-type the New Password and click the CHANGE button.
©2011 Harris Corporation. All rights reserved.
36
Chapter 3
Getting Started
You will receive a confirmation message that the changes were successful. Click the
CLOSE button.
6
Click the CLOSE button on the SETTINGS window.
If you lose or misplace your password, contact technical support for further instructions.
Monitoring
Settings
The following options enable network administrators to make adjustments to the
StorView server’s multicast functionality. In the event there is a port conflict with the default multicast port, you have the ability change the parameters.
To change this parameter
1
From the
Main
screen click
SETTINGS
>
PREFERENCES
tab.
2
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 3-3
Monitoring Settings Screen – Preferences Tab
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
37
Figure 3-4
Monitoring Settings Screen – Preferences Tab (Embedded Version)
3
Click the APPLY button to make the changes effective, then click the CLOSE button. Click the CLOSE button on the SETTINGS window.
Monitoring Stacks on a Different Subnet
You can add one or more stacks on a different subnet to be included in the receipt of StorView server packets.
To specify additional StorView server(s) on a different subnet
1
Enter the IP addresses of both controllers in the other stacks. You may add up to 10 additional monitored controllers.
2
From the Main screen click on the SETTINGS button.
3
Click the PREFERENCES tab at the top of the window.
4
Enter the IP address in the “Individually Monitored Servers” field of another stack controller outside the subnet and click the ADD button.
5
Add additional explicit IP addresses of any other stacks you want to include to receive packets that is outside the subnet and click ADD button. Otherwise, skip to step 6.
6
Click the APPLY button.
7
Click the CLOSE button on the SETTINGS window.
©2011 Harris Corporation. All rights reserved.
38
Chapter 3
Getting Started
Remove Monitored Stack IP
To remove a monitored stack IP address
1
From the Main screen click on the SETTINGS button.
2
Click the PREFERENCES tab at the top of the window.
3
Under the Individually Monitored Servers section, select the controller IP Address you want to delete and click the REMOVE button.
Figure 3-5
Settings Screen – Preferences Tab (Embedded Shown for Example
Purposes)
4
Click the APPLY button. A confirmation window will appear, click the CLOSE button.
5
Click the CLOSE button on the SETTINGS window.
©2011 Harris Corporation. All rights reserved.
4
Configuring a Storage
System
The following topics are included:
Pause/Resume the Initialization
Adding and Removing Global Spare Drives
39
©2011 Harris Corporation. All rights reserved.
40
Chapter 4
Configuring a Storage System
Creating Disk Arrays
To create the Arrays
1
Click on “Create Array” in the “Configuration” group.
The “CREATE ARRAY” applet pops up.
2
Check mark and enter the parameters as shown below. Arrays are created using
RAID level 6, six drives selected in each group, Name GRP xxx, where xxx starts at
001 for stack 0, 017 for stack 1, etc.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
41
3
Select drives by clicking on that drive, using the two left or two right columns in a chassis. The blue “Available” status will change to green “Selected” as you select the drives.
Figure 4-1
Create Array window
4
At the bottom of the window, click “CREATE”.
5
Repeat this process until all arrays have been created. When you’re done, the
StorView GUI will look like below, showing all arrays in initializing state. The initializing process will take 18 hours or more. The rest of the system can be setup, tested, and if necessary put to air while the arrays are initializing. Note that in the stack shown below, the last 6 drives were not used. They will be setup as cold spares later in the commissioning process.
Figure 4-2
Arrays Initializing
©2011 Harris Corporation. All rights reserved.
42
Chapter 4
Configuring a Storage System
Pause/Resume the Initialization
You can temporarily pause the initialization process, and resume the process at a later time.
Pause Initialization
To pause the Disk Array 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.
Resume Initialization
To resume the Disk Array 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.
Adding and Removing Global Spare Drives
Adding a
Spare
Global spare disk drives are supported. In the event of a drive failure, the controller will use a configured global spare to replace a failed drive that is a member of a fault tolerant array within the stack. The process of configuring your redundant arrays includes assigning global spares if you desire.
Global spares are not assigned to a specific array. They will be used by any array as the replacement drive provided that the capacity of the configured spare drive is equal to or greater than the capacity of the drive it is replacing.
Although it is possible to configure dedicated spares that can only be used by a specific array, this is not recommended practice for Farad storage.
©2011 Harris Corporation. All rights reserved.
To add a Spare
1
From the
Main
screen, click on a disk drive labeled
AVAILABLE
.
NEXIO Farad
User Guide
43
©2011 Harris Corporation. All rights reserved.
44
Chapter 4
Configuring a Storage System
The Drive Information window will open.
Figure 4-3
Drive Information window
2
Click the MAKE SPARE button. The Spares Submenu will appear.
3
Select Global Spare, then click Create
4
A confirmation window will appear indicating success, click the CLOSE button.
5
Click the CLOSE button on the Drive Information window.
Removing a
Spare
This operation will remove the designation of the drive as a global spare. The drive will then enter AVAILABLE status.
To remove a Spare
1
From the
Main
screen, click on a disk drive labeled
GLOBAL SPARE
in the enclosure drive view that you want to remove as a spare.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
45
The Drive Information window will open.
Figure 4-4
Drive Information window
©2011 Harris Corporation. All rights reserved.
46
Chapter 4
Configuring a Storage System
2
Click the REMOVE SPARE button. A confirmation window will appear indicating success, click the CLOSE button.
3
Click the CLOSE button on the Drive Information window.
Auto Spare
When Auto Spare is enabled, a freshly inserted replacement disk drive is used as the rebuild target for the failed drive and its array. When a new drive is inserted in place of the failed drive, a rebuild operation will begin automatically using the new drive. This option is useful when a global spares are not configured. This option allows the user to just insert a replacement drive and the rebuild will begin, instead of opening the Drive Information window for the replacement disk drive and assigning it as a spare.
To enable this feature
1
Click the Advanced Settings icon on the Main screen Tool Bar.
The Advanced Settings window displays.
2
Place the mouse pointer on the check box next to the Auto Spare parameter and click to place a check mark enabling the feature.
3
Click the APPLY button and click the CLOSE button on the confirmation window when it appears.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
47
Figure 4-5
Advanced Settings Window
4
Then click the CLOSE button on the Advanced Settings window.
©2011 Harris Corporation. All rights reserved.
48
Chapter 4
Configuring a Storage System
Create the Logical Drive
To create Logical Disks
1
Click on “Create Logical Drive”
2
Select the Grp 001 array (names shown in figure are different)
3
Name the logical drive. Naming convention is “Disk xxx”, where xxx is the same as the array number.
4
Leave the Size field blank. This will use the entire array capacity to create the logical drive.
5
Select “Mapped to” and use the LUN numbers as shown in Table 1. Array number, Disk number, and LUN number should all match each other for ease of troubleshooting.
6
Check all four boxes in the “Availability” section.
©2011 Harris Corporation. All rights reserved.
7
Click the “CREATE” button.
NEXIO Farad
User Guide
49
8
Click “OK” when the “Warning” message appears.
©2011 Harris Corporation. All rights reserved.
50
Chapter 4
Configuring a Storage System
9
Continue to create Logical Disks until all the arrays are used. The display will look similar to below when you have completed this task.
Saving the Configuration
Saving the configuration information should only be done just prior to replacing a
RAID controller module. The configuration will be downloaded to your computer as protection against the unlikely event that the replacement process wipes out the stack's configuration information.
If any changes other than a controller swap have been done since the previous save, then do not restore the configuration, as it can cause loss of content. Restore should only be attempted as a last ditch measure to recover from either of the following conditions after replacing a controller:
Arrays and/or logical drives disappear from StorView
Physical drives enter the "Available" state.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
51
Should the above situation occur you can instantly re-establish your storage system by restoring the configuration from the external file.
To save the configuration
1
From the
Main
screen in the
Configuration
area, select
Archive Configuration
icon.
The
Configuration Archival Operations
window displays.
2
Click
Save
. You may click the CLOSE button to cancel and return to the Main screen.
3
Click
Download
to continue with saving the configuration file.
The
File Download
window displays.
4
Click
Save
. You can either save the file using the default file name and/or location provided or enter your own preferences.
©2011 Harris Corporation. All rights reserved.
52
Chapter 4
Configuring a Storage System
The file is now saved and is available in case you need it.
To restore the configuration
1
From the
Main
screen in the
Configuration
area, select
Archive Configuration
icon.
The
Configuration Archival Operations
window displays.
2
Click
RESTORE
.
3
The File upload window appears, click the
Browse
button.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
53
4
You are presented with the browser’s “Choose File” window. Select the appropriate file and click the
Open
button to continue, or
Cancel
to quit.
5
Click the
UPLOAD
button to continue to restore the configuration, or click the
CANCEL
button to quit.
©2011 Harris Corporation. All rights reserved.
54
Chapter 4
Configuring a Storage System
©2011 Harris Corporation. All rights reserved.
5
Controller Advanced
Settings
In order to customize your storage system, you may want to make changes to the storage systems configuration parameters to optimize it for your application. This is accomplished through the Advanced Settings window. These functions include managing the identity, fault tolerance, host port settings, drive advanced power management and array performance tuning.
The following topics are included:
Advanced Power Management (APM)
55
©2011 Harris Corporation. All rights reserved.
56
Chapter 5
Controller Advanced Settings
Advanced Settings
To access the advance settings
1
On the
Main
screen, click the
Advanced Settings
icon.
The
Advanced Settings
window displays.
Identity
Fault
Tolerance
Host Posts
From this window you are able to make changes to controller parameters, enable or disable Fault Tolerant features, and configure the controller’s host ports.
2
Review each of the three sections below to make the changes your system requires.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
57
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 5-1
Advanced Settings Window
The following list describes the components of the Identity section:
Configuration Name
Default.
This is set to
Default Configuration Name
. The name should be changed to make it easy to identify the stack, e.g.
Farad Stack 1 Config
.
This is the name you will assign to the configuration. The configuration contains all the information that defines the disk arrays, logical drives, SAN
LUN Mapping, spare drives and controller specific settings.
Click the APPLY button followed by the CLOSE button.
Configuration WWN
Default.
This is set to
Controller 1
at time of install. When the system is new, the only options in the drop-down are
Controller 0
and
Controller 1
.
This is the RAID Controller’s WWN reported to the outside world over the
FC link. The configured WWN is also used as a key to generate the Logical
Disk serial numbers. The WWN and serial numbers need to stay the same while the rest of the server system is running.
If the configuration WWN is set to an actual number instead, then the controller that was being used as the reference WWN has been replaced. The system remembers the old WWN and uses it anyway, since the Configuration
WWN is what is reported to the outside world. This way, if you swap controllers (most likely because of a failure) your Configuration WWN still reports the same WWN as it did before so you do not have to change any mappings on your host or fibre channel switch.
©2011 Harris Corporation. All rights reserved.
58
Chapter 5
Controller Advanced Settings
Do not change this selection unless you also intend to restart all attached
FC switches and hosts.
Controller LUN
This option allows the user to set a specific LUN number or disable the
Controller LUN. By default the Controller LUN is automatically assigned the next LUN number after the last logical drive.
In the event you have an operating system that is having a problem with the Controller LUN being displayed, click the pull-down selection and choose “Disabled.”
Default is set to 0. Check this setting both before and after setting up all logical drive LUN mappings.
Different Node Name
Selecting this option allows the controller to report a different
Configuration WWN for Port 0 and Port 1 (FC Host 0 and FC Host 1 connectors). Normally, when deselected, a host connected to either port will see the same Configuration WWN.
When enabled (selected) you will see a slightly different WWN for each port but the same Configuration name. This option is useful to users who are connecting the storage to a switch employing a fabric topology where the same WWN is not tolerated.
Default is checked (enabled).
Fault
Tolerance
In the Fault Tolerance section, you can enable or disable controller features that improve its abilities to maintain a level of fault tolerance.
Figure 5-2
Advanced Settings Window
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
59
The following list explains the Fault Tolerance settings:
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 global spares are not configured.
Default is checked (enabled).
Auto Rebuild
Selecting this option will automatically start a rebuild operation when a fault-tolerant array loses a drive member and a spare drive is available and online. When you assign a global spare this option is automatically enabled. The option can be disabled if desired.
Default is checked (enabled)
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.
Default is unchecked (disabled)
Background Drive Verification
This option is used to automatically verify the media on all drives in arrays in the background. If a media error is detected, the controller can automatically re-write the data, providing that the array is in fault tolerant mode.
System performance may be impacted by Background Drive Verification, depending on the workload.
Default is unchecked (disabled).
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.
Default is enabled (checked).
©2011 Harris Corporation. All rights reserved.
60
Chapter 5
Controller Advanced Settings
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.
Default is set to 50%.
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.
This has no effect in current code versions. Rebuild operations back off automatically to protect air operations.
Default is set to 10%
Network Idle Timeout
This option is only displayed for Embedded StorView, and sets the maximum amount of time that the embedded software will run without any HTTP activity. If the time period is exceeded the software will assume the HTTP interface is not responding and will reboot the Embedded module in an attempt to recover. This will not impact RAID operations.
Default 1 Week
Host Ports
In the Host Ports section, you can change the ALPA ID assigned to each of the controller ports, set the type of connection, and set the data rate.
Figure 5-3
Advanced Settings Window
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
61
Controller Port ID (P0)
This is the target ALPA for both controller(s) port 0. It can range from: Soft
Address, or 0 - 125. The default is ID 4. This setting applies to Loop topology only.
Default is set to 4.
Controller Port ID (P1)
This is the target ALPA for both controller(s) port 1. It can range from: Soft
Address, or 0 - 125. The default is ID 5. This setting applies to Loop topology only.
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 upper controller and Controller 1 is the lower controller.
Default is set to 5.
Controller Port Data Rate
Use the Automatic setting for most configurations. If you choose to use a specific setting (1 Gb, 2 Gb, 4 Gb, or 8 Gb), then you override the automatic setting. Be sure the software setting here matches the hardware switch setting on the HBA ports.
When using an Active-Active configuration (dual controllers) set the
Controller Port Data Rate to one of the established settings. 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. Set the speed to either 2
Gb, 4 Gb, or 8 Gb to prevent this from happening.
Default is set to automatic.
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.
Default is set to Automatic.
©2011 Harris Corporation. All rights reserved.
62
Chapter 5
Controller Advanced Settings
Refresh Rate
This control adjusts the elapsed time between StorView updates. When viewing StorView in a browser, the refresh cycle returns the view to the top every 10 seconds. This can interfere with operations that require the user to scroll down the list of frames. The refresh cycle is adjustable in 10 seconds increments through the drop down list available in this section.
Default is set to 10 seconds.
Figure 5-4
Advanced Settings – Drive APM Screen
Advanced Power Management
(APM)
Advanced Power Management brings to StorView and the storage systems two new levels of power management. These new power management features will help you extend the life of your disk drives, reduce power consumption, reduce noise levels, and excess heat, helping you save on energy costs. The first level is
Drive Power Management
and the second level is
Array Power Management
. Refer
Array Power Management (APM Level 2)
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
63
Drive Power Management
Drive Power Management is accessed via the Advanced Settings button and the
Drive APM button located at the lower position of the Advanced Settings window.
If you have made changes to any of the settings in this view, select the “Apply” button before selecting “Drive APM”.
Figure 5-5
Advanced Settings – Drive APM Screen
APM or Drive Power Management will manage these drive group types: spare drives, unused drives and failed drives. The user has the option to set policies for each drive group type managed by APM. For each drive group type, the policies are applied universally. Referring to Figure 1–6, you can choose to enable or disable each drive group type and also enable periodic spin-up and test of the drives managed by APM. Below the drive group types section you will be able to customize your drives spin-up and test policies.
©2011 Harris Corporation. All rights reserved.
64
Chapter 5
Controller Advanced Settings
The power management feature will only spin down eight (8) unused or spare disk drives at a time. If there are more than eight unused or spare drives, APM will spin them down in groups of 8 or less. For example, if you have 10 unused drives, APM will spin down the first 8, then the remaining 2.
The time the page loaded, displayed across the bottom of the page, is designed to help you manage real time data for the opened window. It is a reminder to the user that you must manually refresh the page to ensure accurate data is presented. Be sure to reload the page when correct and current information is needed.
To configure APM
1
From the Main screen, click the Advanced Settings button on the tool bar.
2
From the Advanced Settings window click the DRIVE APM button located towards the bottom of the screen. This will open the Power Management window.
3
Set check boxes as shown below. For each drive type (Unused Drives, Spares and
Failed Drives) use the mouse pointer to select the check box adjacent to the type.
If you want to have the drive type perform a periodic spin-up and self test, place a check mark in the box for each type, Unused and Spare drives only.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
65
4
Once you have enabled “Spin-Up Drives Periodically and Test,” at the lower half of the window choose the policy schedule you want to use to manage your disks.
Use the mouse to select whether the drives should spin up and complete a test.
You will choose whether the policy will be daily, weekly or monthly, and the time to perform the test.
5
Click the APPLY button. Then click CLOSE twice more.
APM Characteristics
APM controlled drives will stay spun down after a configuration has been cleared.
Since APM settings are written to meta-data and the user clears the configuration, then the APM level 1 settings will also be cleared. APM level 1 drives will not change their state as they are not updated.
The standard behavior is such that APM drives will stay spun down if they are currently spun down even during configuration updates. They will be spun up only if the user will require use of those drives, like creating an array.
If a drive is configured as a spare, it is known as a hot spare if it is spun up and a cold spare if it is spun down.
©2011 Harris Corporation. All rights reserved.
66
Chapter 5
Controller Advanced Settings
Advanced Performance Options
These features are accessed from the Advanced Settings window by clicking the
“PERFORMANCE OPTIONS” button.
Figure 5-6
Advanced Settings – Performance Options Screen
The Performance Options window is divided into two sections. The top portion contains the options to configure the system for stripe access in parallel, execute
SCSI cache flush commands, balance the response times for servicing commands, and customize the amount of sequential write operations for your workload.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
67
Use the Overload Management section to enable the ability to return TASK SET
FULL responses when the controller believes it cannot currently handled the I/O request. This is preferred rather than responding with a return and reject status because the host did not receive a status in sufficient time. You can set the time in seconds for the response, which should be much lower than the host setting.
Performance Options
The following options will assist you in fine tuning the performance of your system.
For specific details on the tuning process and applied metrics, refer to your supplier for subject related white papers.
The following options are available in Performances Options
Synchronize Cache Writes to Disk
This option will determine whether there is normal processing of the SCSI
Cache Synchronize command.
Figure 5-7
Performance Options – Synchronize Cache
By placing a check mark in the box, the option is enabled. When enabled, a specific system command will cause the controller to flush the cache contents to the arrays.
©2011 Harris Corporation. All rights reserved.
68
Chapter 5
Controller Advanced Settings
The Farad hosts have no need for the flush command, so this option is not used.
Default is set to disabled (unchecked).
Target Command Thread Balance and Sequential Write Optimization
Use this option to balance response times between multiple initiators.
Figure 5-8
Performance Options – Target Command Thread Balance and Write
Optimization
When enabled (checked), the controller will attempt to reduce the maximum response time by servicing the oldest request first.
When disabled (unchecked), the controller will optimize throughput by sorting I/O requests to optimize disk access on any array with writeback cache enabled and write through disabled. This setting should provide optimized performance for typical workloads.
Streaming file systems such as Farad are obligated to equalize response times among hosts, therefore this feature is used.
Default is enabled (checked).
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
69
Sequential Write Optimization
Use this to set the amount of optimization the controller should perform for sequential write operations. Since Farad writes are mostly random, this is set to Low.
Default is set to Low.
Overload Management
Disabled
Use this to enable the response and set the response time out for SCSI
Primary Commands.
Figure 5-9
Overload Management
Choose to enable this option when you want a response sent to the host within a specified amount of time because the target queue is full. The timeout periods are expressed in seconds.
©2011 Harris Corporation. All rights reserved.
70
Chapter 5
Controller Advanced Settings
SCSI Busy status
The response will be either SCSI TASK SET FULL or SCSI BUSY. Click
“Enabled” for SCSI TASK SET FULL and “SCSI BUSY” for the SCSI BUSY response.
Queue Full Timeout
Specifies the delay in seconds that commands will wait for space in the target queue before failing with the Target Queue Full response selected above. If a response of “Disabled” is selected, then the timeout value is not selectable.
Enabled
Select a timeout value shorter then the transport layer timeout of your host. Otherwise, the commands will be subject to the normal abort and recovery operations.
Default is Disabled
©2011 Harris Corporation. All rights reserved.
6
Environments
Use the Controller Information window to instantly view the health status of the
RAID Controller components and a mouse over function for detailed information of the items listed in the top Status section. User controllable functions include updating firmware, synchronizing the date and time, performing a diagnostic dump, resetting or shutting down the RAID Controller(s), licensing features, and managing event log files.
The following topics are included:
Determining the Version of Firmware on Expansion Modules
Enclosure Environmental Information
©2011 Harris Corporation. All rights reserved.
71
72
Chapter 6
Environments
Controller Environmentals
To view and manage controller environmental conditions and functions
1
Click the Controller icon located just above the Tool Bar on the Main screen.
Figure 6-1
Main Screen – Arrays, Logical Drives, and Enclosure Sections
The Controller icon on the Main screen will flash red for a failure condition and yellow for an abnormal condition. If this occurs, click the icon and investigate the problem from the information provided in the Controller Information window. You may want to further investigate the Event log to verify whether one or more event(s) changed the controller status, see
When the Controller Information window opens, the controller’s status is displayed via status icons and a text message.
By passing the mouse pointer over each item in the Status group (controller and battery), a pop-up window will appear with specific detailed data.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
73
Figure 6-2
Controller Window with Pop-Up on Battery Status
Status
This group of items are applicable to the functional status of the RAID Controller.
They include general controller status and battery status. Placing the mouse pointer over the item will display a pop-up window with more detailed information.
Status icons appear adjacent to each 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.
©2011 Harris Corporation. All rights reserved.
74
Chapter 6
Environments
When the mouse pointer is rolled over the Battery status icon, the pop-up display provides general information about the battery, that is whether it is charged, charging in process, or has a fault. A warning (yellow) icon indicates the battery is low but is charging. An error (red) icon indicates the battery is low but has charging for over 24 hours and is most likely defective.
Hardware/
Firmware
This group of items are applicable to the controller’s physical memory and firmware. From this group you can determine the type of processor, onboard memory size, the firmware versions, and the CPLD (Complex Programmable Logic
Device) version. The controller’s WWN (world wide name) is presented in this group.
Configuration
This particular group identifies the WWN (world wide name) assigned to the configuration and the speed of each 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
Be careful when changing the Configuration WWN, as you can inadvertently cause a duplication in names that will result in some devices not being seen by the FC switch, the FC driver, or the LLM.
Operations
These items include buttons that allow the user to reset each controller individually,
controller logs (see
diagnostic dump, synchronize date and time, and clear the log files (see
The user can dump the controller’s diagnostic information into a file for use with technical support when troubleshooting a problem by clicking the DIAGNOSTICS
DUMP button.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
75
Updating the Firmware (UID)
This option provides the means to update the firmware of all affected internal components via a unified image download (UID) file. There are basically three major groups of the UID, the controller firmware, the GEM firmware and Embedded
StorView.
The controller firmware consists of the firmware, boot primary and boot failsafe.
The GEM (Genesis Enclosure Management) consists of enclosure midplane VPD and CPLD, RAID canister firmware, bootloader, VPD, flash configuration CRC,
CPLD, and expansion module canister firmware, bootloader, Disk I/O module VPD,
Disk I/O module flash configuration CRC, Disk I/O module CPLD, also included is the PCM firmware and PCM VPD. And the last group is Embedded StorView application primary and boot monitor primary.
It is vitally important that an uninterruptible power source is used during the update.
During the update process, the primary controller and GEM will manage updating the components in the RAID enclosure and in the Expansion enclosure(s).
The PCM updates are performed serially in the enclosure, that is PCM 1 then PCM
2, but all enclosures (RAID and Expansion(s)) are updated in parallel. That is all PCM
1’s in all enclosure are updated then all PCM 2’s. While this is occurring the PCM fans will be elevated to the highest RPM.
Once the updates are completed successfully, a reboot command is issued and the components are restarted. This process does not affect I/O operations, other than a minor degradation during controller failover and fail back while a controller is restarted.
If any errors are encountered, refer to the Event log and contact Harris Customer
Support.
©2011 Harris Corporation. All rights reserved.
76
Chapter 6
Environments
To update the Firmwave (UID)
1
Click the Controller icon located just above the Tool Bar.
Figure 6-3
Main Screen – Arrays, Logical Drives, and Enclosure Sections
The Controller Information window will open.
2
Click the “UPDATE FIRMWARE” button.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
77
Figure 6-4
Controller Information Window
3
Locate the firmware file, click the Browse button. The file will be named similar to
“XUIM-Rxxx-IADN-A6500F-xxxx.bin.” Firmware update files, if available, will be posted on the Harris Support Portal.
©2011 Harris Corporation. All rights reserved.
78
Chapter 6
Environments
Figure 6-5
Firmware Upload Window
4
After locating the file, click the UPLOAD button.
The firmware update process may take as long as 90 minutes to run to completion. During this time the PCM fans may run at full speed, which will be noisy. DO NOT interrupt the update process by removing power or pulling any modules during this time.
You will see an acknowledgement window display indicating the status of the update, followed by the system components automatically restarting.
Replaced Component Firmware Management
If a failed component (including a controller module) is replaced while the stack is powered, the new component will be updated to match the firmware database managed in the system. If a controller module with later firmware version is inserted while the stack is unpowered, then all system components will update to the latest firmware version when power is restored.
Determining the Version of Firmware on Expansion
Modules
To determine the Firmware version on expansion modules
1
Click the Controller icon located just above the Tool Bar for the storage system you want to examine. The Controller Information window will open.
2
Click the DIAGNOSTIC DUMP button.
3
Once complete, open the “DiagnosticsDump.log” file using a text editor.
4
Scroll down through the file and look for “List of Enclosures and Firmware Version” section and view the firmware version of each Disk I/O module.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
79
The firmware on the Disk I/O modules must be the same version on ALL
Disk I/O modules installed in ALL expansion enclosures in that storage system.
Clearing the Controller Logs
To clear the controller logs
1
Click the Controller icon located just above the Tool Bar.
p
Figure 6-6
Main Screen – Arrays, Logical Drives, and Enclosure Sections
The Controller Information window will open.
©2011 Harris Corporation. All rights reserved.
80
Chapter 6
Environments
Figure 6-7
Controller Information Window
2
Click the CLEAR LOGS button.
3
A window opens prompting to confirm clearing the logs. Click the OK button.
Figure 6-8
Confirmation WIndow
4
Click the CLOSE button at the bottom of the Controller Information window.
©2011 Harris Corporation. All rights reserved.
Exporting the Controller Logs
To export the controller logs
1
Click the Controller icon located just above the Tool Bar.
NEXIO Farad
User Guide
81
Figure 6-9
Main Screen – Arrays, Logical Drives, and Enclosure Sections
The Controller Information window will open.
©2011 Harris Corporation. All rights reserved.
82
Chapter 6
Environments
Figure 6-10
Controller Information Window
2
Click the EXPORT LOGS button.
3
Choose Save to Disk, enter a name and location for the file, then click the OK button.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
83
Figure 6-11
Confirmation WIndow
4
Click the CLOSE button at the bottom of the Controller Information window.
5
Open the event log with a text editor program.
Enclosure Environmental Information
The user can view enclosure status, RAID Controller status, PCM status and firmware version data from the Enclosure Information window. This window displays the version information about firmware programs of the individual modules and examines each of the power cooling modules (PCM) via a tab selection process.
To view status and version from the Enclosure Information window
1
From the Main screen, click the Enclosure “x” link located just above the drive view of the enclosure.
Figure 6-12
Main Screen – Enclosure Sections
©2011 Harris Corporation. All rights reserved.
84
Chapter 6
Environments
The Enclosure Information window will open.
2
Enclosure Information Window - General Tab Selected
General Tab
When the Enclosure link is clicked, the Enclosure Information windows opens with this General tab selected. The page displays information and data about the overall status of enclosure and the RAID Controllers. It includes data such as overall status, serial number, vendor, alarm state, temperatures, product ID and chassis type. It further provides a general status and specific data for each of the RAID
Controller(s), refer to the example provided above.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
85
PCM Tabs
Each of these tabs will display information about the specific Power Cooling
Module (PCM) which includes the status of the overall status of the power supply, status of each of the cooling fans, and the inlet and hotspot temperature to determine the state of the thermal state of the module, plus firmware version information and the field replaceable unit (FRU) number. The FRU is helpful when ordering a replacement part.
If a problem occurs with a Power Cooling Module, its tab will flash red.
Figure 6-13
Enclosure Information Window - PCM 1 Tab Selected
©2011 Harris Corporation. All rights reserved.
86
Chapter 6
Environments
Version Info
Tab
The Version Info tab will display information about all firmware program versions including CPLD and VPD for the enclosure and then specific firmware version for each of the RAID Controllers.
Figure 6-14
Enclosure Information Window - Version Info Tab Selected
©2011 Harris Corporation. All rights reserved.
7
Managing the Storage
System
This chapter contains all management features, but many are not performed due to the specific application of the NEXIO Farad storage system.
The following topics are included:
Array Power Management (APM Level 2)
Restoring and Clearing the Configuration
Accessing the Drive Information Window
Advanced Logical Drive Functions
S.M.A.R.T Alert and Proxy Mode
©2011 Harris Corporation. All rights reserved.
87
88
Chapter 7
Managing the Storage System
Advanced Array Functions
Deleting an Array
You must stop all host I/O operations prior to deleting an array.
Deleting an array deletes all data on the logical drives and those associated with that array. Be sure you have a back up of the data before proceeding.
You cannot delete any array in the storage system while any of the following background operations are occurring: Expansion, Rebuild,
Initialization, or Parity Check.
To delete an Array
1
Stop all host I/O operations.
2
From the
Main
screen in the
Configuration
section, click an
Array
to delete.
The
Array Information
screen displays.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
89
3
Click
DELETE ARRAY
.
If the array contains logical drives, a message displays requesting a confirmation to continue or to cancel the operation.
©2011 Harris Corporation. All rights reserved.
90
Chapter 7
Managing the Storage System
4
Click
OK
to continue.
The
Confirmation Password Screen
displays.
5
Type your
Password
and click
GO
.
If the incorrect password is entered, you receive an error message and the array is not deleted.
6
Once the array has been successfully deleted, click
CLOSE
.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
91
Modifying
Arrays
Once the array has been created and is online you can make changes to the following:
The name of the array. See page 92.
The Read-Ahead and Writeback cache parameters. Do not deviate from the default settings.
To restore the original array settings
You can restore the original settings by clicking
RESTORE
. This cancels any changes you have made prior to clicking
APPLY
. Once you click
APPLY
, the new settings become the current baseline.
©2011 Harris Corporation. All rights reserved.
92
Chapter 7
Managing the Storage System
To rename an Array
1
From the
Main
screen
Configuration
section, click on the
Array
from the list to be renamed.
The
Array Information
screen displays.
2
In the
Name
field, type a new name for the array and click
APPLY
.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
93
To initialize a trusted array
You can initialize the array from this window by clicking
INITIALIZE
(or
RE-INITIALIZE
if the array was initialized before).
Initializing a trusted array deletes all data on the logical drives associated with that array. Be sure you have a back up of the data before proceeding.
Verifying
Parity
This is not normally necessary on Farad arrays. This performs a parity check as a normal maintenance procedure to ensure data integrity. Also, if a RAID 5, 6, and 50 disk array experiences a situation where a controller is replaced after the controller is powered off with write operations in progress, it may be necessary to verify and correct the parity data on the array.
©2011 Harris Corporation. All rights reserved.
94
Chapter 7
Managing the Storage System
To verify and correct the parity data on the Array
1
From the
Main
screen
Configuration
section, click the
Array
to verify parity data.
The
Array Information
screen displays.
2
Click
VERIFY PARITY
.
The
Verify Party
window displays.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
95
3
Select one of the following verify methods from the drop-down list and click
VERIFY PARITY
.
Verify Parity Only.
This option reads all the data and parity, calculates the
XOR of the data, and compares it to the parity. If there is an error, it is displayed in the event log.
Rewrite Parity Only.
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.
Verify and Rewrite Parity.
This option reads all the data and parity, calculates the XOR of the data, and compares it to the parity. Then, if there is a discrepancy, it writes this out as the new parity 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 on the Main screen, the drive indicates that verification is in progress. Adjacent to the array name, a progress bar indicates the percent completed. When you place the mouse pointer over the progress bar a pop-up will display the value of the percent complete. Under Enclosures, the drives being verified are also indicated.
Figure 7-1
Monitoring Progress of Parity Verification
©2011 Harris Corporation. All rights reserved.
96
Chapter 7
Managing the Storage System
To stop verification
1
On the Main screen, click
Stop
located to the right of the progress bar.
The
Confirmation Screen
displays.
2
Click
GO
to stop the verification process.
If you clicked
GO
, a window displays to confirm that the verification was successfully cancelled.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
97
Identifying Drive Members
When the need arises, you can identify which drives in the
Enclosure
are members of a specific array.
To identify array drives
1
On the
Main
screen to the right side of an
Array
, press the
Drive Identify
icon.
2
Each logical drive created from the drives of the array also display the
Drive Identify
icon.
Tip
Figure 7-2
Identifying Member Drives Screen
You can also identify specific drives in an array by flashing its
Drive Status LED
, see
Identifying and Replacing a Failed Drive
Failed Drives
Upon a drive failure, the following notifications occur:
Physical Indicators.
The yellow identification LED on the remaining members of the affected array will flash.
The yellow identification LED on the failed drive will be on (most cases).
Local StorView GUI.
The faulted drive’s icon will either enter the fail state, or
less commonly the empty state . The storage system tab will begin to flash red. The affected array and logical disk icons will exit the green “good” status and enter the yellow “fault” status.
Remote StorView GUI.
The controller icon for the affected stack will begin to flash red.
SNMP.
An SNMP trap will be issued at ERROR level
E-Mail.
An ERROR level message will be sent to those configured to receive such messages
©2011 Harris Corporation. All rights reserved.
98
Chapter 7
Managing the Storage System
To find and replace a drive that has entered Failure mode
1
Identify the failed drive.
Verify on the StorView GUI that a drive is in the failure state.
shows the expected indication on the StorView GUI. In this example the failed drive is in the slot 9 position of enclosure 3.
Figure 7-3
Failed Drive Identification
2
Replace the failed drive.
Once identified, go to the stack and find the failing drive. The enclosure ID number is displayed on the left trim panel. Examine the drives in that frame and verify that the yellow LED on the expected drive is steadily lit. Operate the release lever and pull the failing drive from the enclosure. Replace immediately with a new drive.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
99
3
Verify that the affected array successfully rebuilds (Global Spares configured).
shows a stack configured with global spares. The Farad controller has
already started a rebuild using one of the configured cold spares. If you find that the affected array is instead in critical mode, then start the rebuild manually by selecting a drive in either “Available” or “Global Spare” status to bring up the
Drive Information window, then click the “Rebuild Array” button.
4
Assign the replaced drive as a global spare (Global Spares configured).
a
In most cases the replaced drive will indicate “Available” status on the
StorView GUI. The replaced drive must be assigned as a global spare so that is can be used as the rebuild target in the future.
b
Select the available drive to bring up the Drive Information window, then click the “Make Spare” button. Select the “Global Spare” option in the Make Spare popup, click “Create”, click OK on the warning message, then close the Drive
Information window.
Figure 7-4
Drive information window on an Available drive
5
Verify that the affected array successfully rebuilds (Global Spares not configured).
The Farad controller will start the rebuild within 5 minutes after the failed disk is replaced. If this does not occur, then verify that the replaced drive shows
“Available” status. Start the rebuild manually by selecting the “available” drive, and then click the “Rebuild Array” button on the Drive Information window.
©2011 Harris Corporation. All rights reserved.
100
Chapter 7
Managing the Storage System
Slot Empty Mode
To find and replace a drive that has entered Slot Empty mode
Occasionally, a drive will fail in a manner that causes the controller to determine
Upon a drive failure, the following notifications occur:
on page 97 for an explanation of the error messages.
1
Identify the failed drive.
Verify on the StorView GUI that a drive is in the
Empty
state.
shows the expected indication on the StorView GUI. In this example the failed drive is in the slot 9 position of enclosure 3.
Figure 7-5
Identifying a failed drive
2
Replace the failed drive.
Once identified, go to the stack and find the failing drive. The enclosure ID number is displayed on the left trim panel. Examine the drives in that frame and verify that the expected drive has the green light steadily lit, even when other members of the array are blinking. Operate the release lever and pull the failing drive from the enclosure. Replace immediately with a new drive.
3
After replacement, follow the procedures in the previous section concerning verification of rebuild activity and assigning the replaced drive as a global spare.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
101
Rebuilding an Array
This option is designed for situations where you want to manually start a rebuild operation.
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 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 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.
To rebuild an Array
If the stack is configured with global spares, the rebuild process will start automatically. If the system is not configured with spares, the rebuild process will start when the failed drive is physically replaced. The manual process described in this section should only be used if the automatic process fails to start.
1
From the
Main
screen, click on the
Available
drive displayed in the
Enclosures
view.
The
Drive Information
window displays.
2
Click
REBUILD ARRAY
.
©2011 Harris Corporation. All rights reserved.
102
Chapter 7
Managing the Storage System
A
Warning
window displays.
3
Click
OK
to continue.
A
Rebuild Array
window displays.
4
Scroll down and choose the specific array that became critical from the removed/ failed drive.
5
Click
REBUILD
.
©2011 Harris Corporation. All rights reserved.
A confirmation window displays indicating the successful execution.
NEXIO Farad
User Guide
103
6
Click
CLOSE
to exit the window.
7
Click
CLOSE
again to exit the
Drive Information
window.
©2011 Harris Corporation. All rights reserved.
104
Chapter 7
Managing the Storage System
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 the array is first rebuilt using one drive, then the rebuild repeats using the second drive.
You can monitor the rebuild operation from the Main screen.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
105
Expanding an Array
NOT DONE ON NEXIO Farad.
NEXIO Farad Storage expansion on the fly is implemented at the application layer.
You can configure physical storage, create new arrays and logical disks, then select the Expand feature on the LLM. The storage subsystem array expansion should not be used because it will not be seen as additional storage by the hosts.
You must stop all host I/O operations prior to expanding an array. After the expansion has reached 1%, then you can resume your host I/O operations.
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.
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, 6, 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 continues as normal, 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 spare designated, the automatic rebuild operation commences 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. Harris recommends that you back 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.
After the array expansion process is complete, 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.
©2011 Harris Corporation. All rights reserved.
106
Chapter 7
Managing the Storage System
To expand an Array
1
Stop all host I/O operations.
2
On the
Main
screen, click on the
Array
to expand.
The
Array Information
window displays.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
107
3
From the
Array Information
window, select the
EXPAND ARRAY
tab.
4
Click the
1. Array Expansion Type
pull-down menu, choose the type of expansion applicable to your array.
5
From
2. Select Drives
, click on the drives used to expand the array.
6
For
3. Verify Configuration,
review the changes you are about to make by examining the
Before Expansion
and
After Expansion
analysis.
7
If your settings are correct, click
EXPAND
.
You are prompted to confirm the Expand operation.
8
Type your
Password
and click
GO
.
A screen prompt displays indicating that the command was successful.
9
Click
CLOSE
.
©2011 Harris Corporation. All rights reserved.
108
Chapter 7
Managing the Storage System
Tip
If the command was unsuccessful, review the settings for incorrect parameters and hardware for operational status.
Figure 7-6
Expand Array Confirmation
Once the expansion progress has reached 1% complete, you may resume normal host I/O operations.
Advanced Power Management
Although this section is included for completeness, this function must not be enabled on active drives or arrays. The time required to spin up drives is not compatible with the time-critical mission of the NEXIO Farad streaming storage system. Harris cannot be responsible for data access issues caused by enabling APM level 2.
Advanced Power Management brings to StorView and the storage systems two new levels of power management. Use these new power management features to extend the life of your disk drives, reduce power consumption, reduce noise levels, and reduce excess heat. This will help you to save on energy costs. The first level is
Drive Power Management
and the second is
Array Power Management
. Also
Array Power Management (APM Level 2)
APM level 2 or Array Power Management, will individually manage the array’s disk drives through a set of policies that establishes when the drives should be spun up and spun down. APM level 2 is implemented on a per array basis. Since APM level
2 deals with the arrays, each of the respective logical drives will be affected as well.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
109
To configure APM level 2
1
From the
Main
screen, click the
Array
to set or manage APM policies.
The
Array Information
window displays.
2
From the
Array Information
window, click the
POWER MANAGEMENT
tab.
©2011 Harris Corporation. All rights reserved.
110
Chapter 7
Managing the Storage System
3
If not already enabled, click the check box next to
Advanced Power
Management
.
4
From the drop-down menu, select the
Idle Time to Array Spin-Down
time period for
Hours
and
Minutes
.
5
From the
Periodically Spin-Up Array Members for APM Test
section, select the
Number of Days
(Interval) and/or
Number of Hours
.
©2011 Harris Corporation. All rights reserved.
6
Click
APPLY
to accept the changes.
A message for success completion displays.
NEXIO Farad
User Guide
111
7
Click
CLOSE
twice to exit the
Confirmation of Success
and
Array Information
windows.
To manually spin up or spin down an array
1
From the
Main
screen, click on an
Array
.
The
Array Information
window displays.
©2011 Harris Corporation. All rights reserved.
112
Chapter 7
Managing the Storage System
2
From the
Array Information
window, click the
POWER MANAGEMENT
tab.
3
Click either
SPIN DOWN
or
SPIN UP
located near the bottom of the page. Only one of the buttons will be available at time.
4
Click
APPLY
and then
CLOSE
on the confirmation window.
5
Click the
CLOSE
again to exit the
Array Information
window.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
113
APM Characteristics
APM level 1 controlled drives stay spun down after a configuration has been cleared. Since APM settings are written to meta-data and you are able to clear the configuration, the APM level 1 settings will also be cleared. APM level 1 drives do not change their state because they are not updated.
The standard behavior is that APM level 1 drives stay spun down if they are currently spun down even during configuration updates. They are spun up only if you require use of those drives; for example, if you are creating an array.
If a drive is configured as a spare, it is known as a hot spare if it is spun up and a cold spare if it is spun down.
If an APM level 2 policy is set on an array, that array will be spun down immediately if it has already been idle for that specified amount of time. APM uses controller statistics to determine the length of time the array has been idle and those statistics are tracked from the controller boot time. Even though APM level 2 is not enabled on a particular array, its status is still tracked.
Other characteristics are the drive icon changes to indicate a spun down drive. If a drive is unused, or a spare, or part of an array and has been spun down it will have a normal icon except with a blue tint overlay and a small
moon
icon to the left side of the icon. Refer to
Enclosure Section — Descriptions and Conditions
on page 10 for a list of all drive icons.
When drives are spun down and depending upon the number of drives spun down, it could take longer than 1 and 1/2 minutes to spin the drives back up. If commands are issued to the drives before they are spun up, the commands will fail. You will need to re-issue the commands once the drives are spun up and back online.
©2011 Harris Corporation. All rights reserved.
114
Chapter 7
Managing the Storage System
Restoring and Clearing the Configuration
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.
Restoring the Configuration
Use this to recover your configuration from a previously saved file.
To restore the StorView configuration
1
From the
Main
screen in the
Configuration
area, select
Archive Configuration
icon.
The
Configuration Archival Operations
screen displays.
2
Select
Restore
.
You are about to overwrite the controller’s configuration. This is an irreversible process. After restore, it is your responsibility to ensure that all redundant data is valid. To proceed, locate the file and click upload.
The
File
upload window displays.
©2011 Harris Corporation. All rights reserved.
3
Click
Browse
.
The
Choose File to Upload
window displays.
4
Select the appropriate file and click
Open
to continue.
NEXIO Farad
User Guide
115
©2011 Harris Corporation. All rights reserved.
116
Chapter 7
Managing the Storage System
5
Click
Upload
to continue to restore the configuration.
Once the configuration file has been restored, a confirmation message displays.
6
After you have completed the configuration restoration, 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. See
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
117
Clearing the Configuration
Some conditions or situations may call for you to clear the entire configuration.
This process takes you offline and removes all arrays, logical drives, LUN
Mappings, and configuration settings. If there is any data on the drives, access to that data will be lost when the configuration is cleared.
To clear StorView configuration
1
From the
Main
screen in the
Configuration
area, select
Archive Configuration
icon.
The
Configuration Archival Operations
screen displays.
2
Select
Clear
.
This is an irreversible process. Data will be lost. You may click Close to cancel and return to the Main screen.
The
Clear Configuration Operation
window displays.
©2011 Harris Corporation. All rights reserved.
118
Chapter 7
Managing the Storage System
3
Enter your
Password
and click
GO
.
Once the configuration has been cleared, a confirmation message displays and the
Main
window is updated.
©2011 Harris Corporation. All rights reserved.
4
Click
CLOSE
.
The
Main
window is available to reconfigure.
NEXIO Farad
User Guide
119
Figure 7-7
Main window after the configuration has been cleared
©2011 Harris Corporation. All rights reserved.
120
Chapter 7
Managing the Storage System
Advanced Drive Options
Use the Drive Information window to view specific drive inquiry information and make changes to drive parameter settings. From the Drive Information window you will also find functional controls that allow you to locate a drive and execute a rebuild operation.
Accessing the Drive Information Window
To view Drive Information window
From the
Main
screen in the
Enclosures
area, click on any of the
Disk Drive
icons.
Click on any of these drives to bring up the
Drive Information window
The
Drive Information
window displays.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
121
Locating a
Disk Drive
Use this feature to locate a drive installed in the enclosure using the
Drive Activity
LED
.
To locate the physical location of a disk drive
1
Open the
Drive Information
To view Drive Information window
The
Drive Information
window displays.
2
Click
Locate
.
The
Locate Drive
window displays.
3
Select the time interval from the drop-down menu to blink the
Drive’s Activity
LED
. The farther away the drive is from you physical, the more time you should allow.
4
Identify the drive in the enclosure by its blinking
Drive Activity LED
. Refer to the
Hardware User Guide
for details on Drive LEDs.
©2011 Harris Corporation. All rights reserved.
122
Chapter 7
Managing the Storage System
Failing a
Disk Drive
Use this feature to fail a drive that is a member of a redundant array. This provides a safe way to fail a drive that needs inspection that or may be failing.
This feature should be used as a last resort to terminate access to a drive that has been identified as failing through inspection of log data. Failing drives will be automatically failed by the controller before the problem is noticeable by the administrator.
To fail a member disk drive
1
From the
Main
screen in the
Enclosures
area, click on any of the
Disk Drive
to fail.
The
Drive Information
window displays.
2
Click
Fail Drive
.
The
Confirmation Screen
displays.
©2011 Harris Corporation. All rights reserved.
3
Enter the
Password
in the text field and press
GO
.
NEXIO Farad
User Guide
123
The drive is taken offline and marked as a failed drive. For RAID level 1/10 and 5, one drive can be failed, and for RAID level 6, two drives can be failed. Drives cannot be failed as members of a RAID 0 array.
Advanced Logical Drive Functions
Viewing Unassigned Free Space
Prior to creating or expanding a logical drive, examine the unassigned free space to identify the available free space that can be used to create and expand logical drives. The
Create Logical Drive
window is designed to display all available unused space or free regions.
©2011 Harris Corporation. All rights reserved.
124
Chapter 7
Managing the Storage System
To view how much available space is left on StorView
1
From the
Main
screen in the
Configuration
area, select
Archive Configuration
icon.
The available free space is displayed in the
Select which Array(s) to Use
area. You will see each array and how much space is available.
2
If you only wanted to view the available free space, click
Close
. Otherwise to continue with creating a logical drive, see
Figure 7-8
Create Logical Drive window
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
125
Expanding a Logical Disk
NOT USED ON NEXIO Farad.
NEXIO Farad Storage expansion on the fly is implemented at the application layer.
You can configure more physical storage, create new arrays and logical disks, then select the
Expand
feature on the LLM. The storage subsystem logical disk expansion should not be used; it
does not
register as additional storage.
You must stop all host I/O operations prior to expanding a logical disk.
You can use expand a logical disk to take an existing logical drive and expand its capacity using free regions.
After the expansion process is complete, you will need to use a third-party volume/ partition software product to manipulate any existing partitions.
To expand a Logical Disk
1
From the
Main
screen in the
Logical Drives
section, click on a Logical Drive to expand.
The
Logical Drive Information
window displays.
2
In the
Expand Logical Drive
section
Step 1
, choose a free space region for the expansion.
©2011 Harris Corporation. All rights reserved.
126
Chapter 7
Managing the Storage System
3
In the
Add Capacity
box, enter the amount of the selected region to expand the logical disk. You may use the entire free region space or a portion of it. Specify the amount by entering the number of GBs to use.
You cannot exceed the maximum number of 16 regions when expanding a logical disk. Before attempting to expand the logical disk, observe the current number of regions used to comprise the logical disk to ensure you can safely execute the expansion. The current number of regions used is displayed in the top section of the Logical Drive window.
4
Click
Expand
and enter your
Password
and press
GO
to confirm and execute the expansion.
5
You will receive a screen prompt that the command was successful, click
Close
. If the command was unsuccessful, review the settings for incorrect parameters and hardware for operational status.
Deleting a Logical Disk
You must stop all host I/O operations prior to deleting a logical drive.
Deleting a logical drive is an option that allows the user to remove an existing logical disk that is no longer needed or desired. If the logical disk was previously used be sure to make a backup of any data on the logical disk.
To delete a Logical Disk
1
Stop all host I/O operations.
2
From the
Main
screen in the
Logical Drives
section, click on a
Logical Drive
to delete.
The
Logical Drive Information
window displays.
3
In the
Logical Drive
section at the top, click
Delete
.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
127
4
Enter your
Password
and press
GO
to confirm and execute the deletion.
5
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.
S.M.A.R.T Alert and Proxy Mode
S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) is a monitoring system for disk drives to detect and report on various indicators of reliability, designed to anticipate a failure. A disk drive with a displayed
SMART Alert
icon indicates the monitoring system has detected a number of errors that exceed the parameters to trigger the alert. This warning indicates an impending failure.
In a dual controller configuration, Proxy mode is only accessible via one controller.
I/O’s coming into the controller that can't access the drive must be transferred over the inter-controller link to the other controller. This can adversely affect throughput of the affected stack. When portions of a stack are in Proxy mode, the number of volume recoverable errors may increase.
If a drive is in Proxy mode, its status is presented in the
Current Status
block of the
Drive Information
window, with a flashing drive icon in the
Enclosure
front view.
©2011 Harris Corporation. All rights reserved.
128
Chapter 7
Managing the Storage System
Proxy mode can occur due to a drive fault (a single drive in proxy mode) or due to cable or controller fault. In the latter situation multiple drives will show up as proxy mode.
If a drive is displaying either SMART Alert or Proxy icons, you can view a specific drive’s status from its Drive Information window and in the windows’ Extended
Drive Info list view error counts.
You can use
Fail Drive
to safely shutdown a drive that is in
SMART
or
PROXY
mode.
If a spare is defined, a rebuild will begin replacing the drive targeted by the fail command. If multiple drives are in PROXY state, then the fault lies in either a controller module or a cable. Careful examination of activity lights adjacent to each
SAS interconnect cable at the back of the stack will usually point to the offending connection or hardware module. Restore the connection or replace the faulty module. PROXY mode will take up to 6 minutes to clear after the fault is corrected.
Figure 7-9
Drive Information with SMART and Proxy Indicators
In the
Drive Information
), the subject drive is displaying both a
SMART Alert and Proxy in the Current Status - Status field. This indicates both warnings are active. In the Extended Drive Info list, the type and number of errors are reported and displayed.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
129
Likely causes of the
Proxy Mode
alert can range from SAS link errors, internal drive errors, cabling, controller or enclosure errors.
If either of these conditions are present, the drive icon label will flash the condition on for 1 second and off for 2 seconds. If both conditions are present then they will alternate PROXY on for 1 second and off for 2 seconds followed by SMART Alert on for 1 second and off for 2 seconds, in which the entire animation sequence will last a total of 6 seconds. During the off state, the normal drive status image is displayed: array member, rebuilding, etc.
If you experience an error, open the specific disk drive's
Drive Information
window by clicking on the drive icon, and review the path, timeout, hardware, media and recovered errors in the Extended Drive Info list. This list is located in the lower section of the
Drive Information
window.
©2011 Harris Corporation. All rights reserved.
130
Chapter 7
Managing the Storage System
©2011 Harris Corporation. All rights reserved.
8
Additional Functions
The following topics are included:
131
©2011 Harris Corporation. All rights reserved.
132
Chapter 8
Additional Functions
StorView Redundancy
There are two control paths to each Farad stack, one through each controller. If the
StorView monitoring operations should fail on one controller, the stack can still be managed by pointing your browser to the other controller's IP address.
Additional StorView Functions
About
Clicking this button displays the software version information and the type of license installed. The About window also provides the control button to update the software, see
1
From the Main screen, click the ABOUT button, located in the upper right corner of the window under the StorView logo.
The About window is displayed. The license type for this installation is indicated below the version number in parenthesis.
©2011 Harris Corporation. All rights reserved.
2
Click the CLOSE button on the About window.
NEXIO Farad
User Guide
133
Take Control Monitoring
There are two control paths to each Farad stack, one through each controller. If the stack was being monitored through the top controller and you browse to the bottom controller, you will receive a message stating that the other controller is monitoring the storage. Click the “Take Control” link to transfer monitoring to the new control path.
Figure 8-1
Main Screen Take Control - Monitoring Screen
©2011 Harris Corporation. All rights reserved.
134
Chapter 8
Additional Functions
After clicking the “Take Control” link, StorView will perform a scan and reload the configuration for this system. The browser which previously had control will now display the message that the selected storage system is being monitored by another StorView server.
You would also see this condition if this controller failed to send the required three consecutive check-in packets and it fails over to the other controller. Once the problem is resolved, you can take back control again through the other control path.
Rescan
This Rescan function will force a search to re-discover storage systems 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 screen will refresh and displays updated information.
Figure 8-2
Main Screen in Rescan Mode
©2011 Harris Corporation. All rights reserved.
9
Support and Updates
The following topics are included:
Accessing Tech Support Through StorView
Accessing Tech Support Through StorView
Use this feature to provide technical support personnel with event and configuration information to assist with troubleshooting.
To access tech support from Farad
1
From the Main screen, click the TECH SUPPORT button, located in the upper right corner of the window under the StorView logo.
Figure 9-1
Main Screen
2
Enter the requested information for each field.
3
Review the information you will be sending in the
Problem
field, which is scrollable.
©2011 Harris Corporation. All rights reserved.
135
136
Chapter 9
Support and Updates
Gathering this information may take a few minutes.
Figure 9-2
Tech Support Screen
4
Click the DOWNLOAD button.
You will receive a screen prompt to save the file on your local disk. Enter a name for the file and click Save. The software will create a file with your user data, a capture of the event log files, and a capture of all configuration information. Technical support representatives will be able to work with this information to assist with solving your problem.
5
Click the CLOSE button on the Technical Support window.
6
When requested by a technical support representative, E-mail the saved file.
Updating Embedded StorView
To update the Embedded StorView software
Refer to
©2011 Harris Corporation. All rights reserved.
10
Statistics
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.
You may also export the statistical data to a comma delimited file for use in third-party software products.
The following topics are included:
Command Size — Alignment Statistics
©2011 Harris Corporation. All rights reserved.
137
138
Chapter 10
Statistics
Access
Statistics
These statistics are for both reads and writes, and can be used to tune the operating system for optimum performance.
Figure 10-1
Statistics Screen – Access Tab
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.
Statistic
Reads
Writes
No. of
Operations
Bytes
Transferred
Description
This is the average number of MBs transferred in the last few seconds from the logical drives, controllers or ports. This value is expressed in MB/seconds.
This is the average number of MBs transferred in the last few seconds to the logical drives, controllers or ports. This value is expressed in MB/seconds.
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.
This is the total number of bytes read and written since these statistics were reset, or the controller was last powered on.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
139
Command Size — Alignment Statistics
Command size statistics express the percentage of commands whose size is as specified. The Alignment statistics is the percentage of commands whose address aligned on the specified address boundary.
Figure 10-2
Statistics Screen – Command Size/Alignments Tab
©2011 Harris Corporation. All rights reserved.
140
Chapter 10
Statistics
Table 10-1
Statistical Information
Statistic
Command Size
Description
Expressed in the percentage of commands whose size is specified for reads and writes. The values are displayed with a horizontal bar for each value. The lack of a bar displayed for a specific value indicates it is 0% (or less than 1%).
Alignment
For example, consider a read or write command from a host system with
Logical Block Address (LBA) 0x0000070, and access size 0x80, expressed in decimal 128. Using 512 byte blocks on the disk drives, it can be seen that this is a read of 64 Kbytes, which is the command size.
This is the percentage of commands whose address is aligned on the specified chunk boundary. The alignment of a command from a host system is determined by the command’s address.
How to Use Command
Size and Alignment
In an optimal system, a write of one chunk of data would reside exactly within a chunk on one disk. However, if this is not the case, this write will be split up into two separate writes to two different data drives. This of course will have a negative effect on performance.
The NEXIO Farad storage access algorithms are optimized for transfer size and are aligned to stripe boundaries.
To calculate the alignment
Check the LBA for the largest number of blocks that will evenly divide into it, in powers of 2. So, we can see that in this case, the alignment is 0x10 =
16 blocks. This equates to 8K.
The alignment, in conjunction with the access size, gives an indication of how many drives are involved in an access. In the above example, consider a RAID 5/50/6 array with a chunk size of 64K. In this case, the above access will actually involve 2 data drives, since it needs to access 8K in the first drive (0x80 – 0x70 = 0x10 blocks = 8K), and the remaining 56K in the next drive (0x70 blocks = 56K). This is clearly inefficient, and could be improved by setting the alignment to 64K on the operating system. If that is not possible, using a larger chunk size can help, as this reduces the number of accesses that span chunks. Aligning an access on the same value as the access size will improve performance, as it will ensure that there are no multi-chunk accesses for commands that are smaller than a chunk size. The NEXIO Farad storage access algorithms are optimized for transfer size and are aligned to stripe boundaries.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
141
Read-Ahead Statistics
If sequential read commands are sent to the controller, it assumes that the commands which follow may also be sequential. It can then go and perform a read of the data, before the host requests it. This improves performance, particularly for smaller reads. The size of the read-ahead is calculated based on the original command size, so the controller does not read too much data. The controller maintains statistics for all read-ahead commands performed.
Figure 10-3
Statistics Screen – Read-Ahead Tab
©2011 Harris Corporation. All rights reserved.
142
Chapter 10
Statistics
Statistic
Sequential
Command Interval
Description
In determining whether to perform a read-ahead or not, the controller will search back in the command queue whenever it receives a new read command that is not satisfied by an existing read-ahead cache buffer. In a multi threaded operating system, commands from one thread may be interspersed with commands from another thread.
Read-Ahead
Command Hit Rate
Read-Ahead
Command
Efficiency
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.
This is the percentage of read command hits versus the total number of read commands that have been issued.
This gives an indication of the sequential nature of the data access pattern from the host.
This is the percentage of the number of read command hits versus the projected number of read-ahead command hits. This is a measure of the efficiency of the read-ahead algorithm. A low value means that much of the data that the controller reads in the read-ahead command is not actually requested by the host.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
143
Command Cluster Statistics
To increase performance, the controller can cluster sequential write commands together to create a larger write command. This results in less commands being sent to the disk drives. Additionally, if sufficient data is clustered by the controller, then it can perform a full stripe write for RAID5/50/6 arrays. This significantly improves performance. In cases where the host does not send a sufficient number of outstanding writes, writeback cache can be used to delay the write to disk, increasing the likelihood of clustering more data.
Figure 10-4
Statistics Screen – Command Cluster Tab
©2011 Harris Corporation. All rights reserved.
144
Chapter 10
Statistics
Statistic
Write Cluster Rate
RAID 5/50/6 Full
Stripe Write Rate
Command Cluster
Count
Command Cluster
Interval
Description
This is the percentage of the number of write commands that are part of a cluster versus the total number of write commands that have been issued. This gives an indication of the sequential nature of the data access pattern from the host, and of the performance of the writeback cache.
This is the percentage of the amount of data that is written as a full stripe write versus the total amount of data written. This gives an indication of the sequential nature of the data access pattern from the host, and of the performance of the writeback cache, for RAID 5/50/6 arrays. Since the NEXIO Farad storage access algorithms are optimized for transfer size and are aligned to stripe boundaries, this indicator should show 100% at all times unless the stack is busy doing drive initialize or drive rebuild operations.
When the controller clusters a write command, it may cluster a large number of them together. These statistics record the average and maximum number of commands the controller clusters, and also the percentage for each one of these values.
In determining whether to cluster write commands or not, the controller will search back in the command queue whenever it receives a new write command. In a multi threaded operating system, commands from each thread may be interspersed with commands from another thread. This requires that the controller not just check the immediately previous command. The controller will search back for a number of commands, to try to determine if the new command is exactly sequential to any one of these previous commands. If it is, then the controller determines that it can cluster these commands.
These statistics record the average and maximum number of commands the controller must search back for when it finds a sequential command match, and also the percentage for each one of these values.
©2011 Harris Corporation. All rights reserved.
A
Optimizing Write
Performance
This appendix is included for completeness. You should not change the default
Farad settings, or the array types or size. The optimized settings have been applied and tested at the Harris factory.
The following topics are included:
Number of Outstanding Commands
145
©2011 Harris Corporation. All rights reserved.
146
Appendix A
Optimizing Write Performance
Introduction
With a typical RAID 5 implementation, there are a number of steps that are performed when data is written to the media. Every write from the host system will typically generate two XOR operations and their associated data transfers, to two drives. If the accesses are sequential, the parity information will be updated a number of times in succession. However, if the host writes sufficient data to cover a complete stripe, the parity data does not need to be updated for each write, but it can be recalculated instead. This operation takes only one XOR operation per host write, compared to two for a standard RAID 5 write. The number of data transfers necessary are also reduced, increasing the available bandwidth. This type of write access is termed a “Full Stripe Write.”
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 on the following page displays the distribution of data chunks
(denoted by Cx) and their associated parity (denoted by P(y-z)) in a RAID 5 array of five drives. An “array” is defined as a set of drives, on which data is distributed. An array will have one RAID level. A “chunk” is the amount of contiguous data stored on one drive before the controller switches over to the next drive. This parameter is adjustable from 64K to 256K, and should be carefully chosen to match the access sizes of the operating system. A Stripe is a set of disk chunks in an array with the same address. In the example below, Stripe 0 consists of C0, C1, C2, and C3 and their associated parity P(0-3).
Figure A-1
Distribution of Data and Parity in a RAID 5 with Five Drives
Maximum performance will be achieved when all drives are performing multiple commands in parallel.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
147
To take advantage of a Full Stripe Write
The host has to send enough data to the controller. This can be accomplished in two ways. First, if the host sends one command with sufficient data to fill a stripe, then the controller can perform a Full Stripe Write. Alternatively, if the host sends multiple sequential commands, smaller than a stripe size (typically matching the chunk size), the controller can internally combine these commands to get the same effect. In the above example, if a 256K chunk size is used, then the stripe size is
1MB (4 chunks * 256K). So, for maximum performance, the host could either send
5 * 1 MB write commands, or 20 * 256K write commands.
The effectiveness of the controller’s ability to perform a Full Stripe Write depends on a number of parameters:
Sequential Access
If the commands sent from the host are not sequential, the controller will not be able to cluster them together. So, unless each individual access is sufficient to fill a stripe, a Full Stripe Write will not occur.
Number of Outstanding Commands
For the controller to successfully cluster commands, there has to be a number of write commands sent simultaneously. Setting the host to send up to 64 commands should prove adequate. Alternatively, enabling writeback cache will have a similar effect, as the controller can then cluster sequential commands even if the host only sends a small number of commands at a time.
Access Size
With very small accesses, it is necessary to have a large number of commands to cluster together to fill up a full stripe. So, the larger the access size the better. It is best to use an access size that will fill a chunk. Of course, even if a stripe is not filled up, small sequential writes will still benefit from command clustering.
©2011 Harris Corporation. All rights reserved.
148
Appendix A
Optimizing Write Performance
Access
Alignment
Tip
The alignment of a command from a host system is determined by the command’s address. In an optimal system, a write of one chunk of data would reside exactly within a chunk on one disk. However, if this is not the case, this write will be split up into two separate writes to two different data drives. This will have a negative effect on performance.
To overcome these problems, the user can, with more sophisticated operating systems, set the access size and alignment to an optimal value.
As can be seen from the figure below, to get the highest performance from this system, it is necessary to have a number of stripes being written in parallel. As the array expands, with more and more drives, the number of commands (and amount of sequential data) necessary to do this increases.
Figure A-2
Distribution of Data and Parity in a RAID 5 with Eight Drives
In the figure above, 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.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
149
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
on page 146. 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 A-3
Distribution of Data and Parity in a RAID 5 with Ten Drives and Two
Sub-Arrays
It can be seen that the more sub-arrays used, the more likely it is for a Full Stripe
Write to occur, and hence the higher the performance. It is recommended to use either four or five drives in a sub-array, for best performance. On the following page the figure shows that even with 15 drives, it is still possible to perform Full
Stripe Writes, by clustering together 4 chunks of data.
Figure A-4
Distribution of Data and Parity in a RAID 5 with Fifteen Drives and
Three Sub-Arrays
©2011 Harris Corporation. All rights reserved.
150
Appendix A
Optimizing Write Performance
Multiple Drive Failures
In a configuration with multiple sub-arrays, it is possible for the array to sustain multiple drive failures, provided that there is only one failure in each sub-array.
Faster
Rebuild
A rebuild operation must read data and calculate parity from all the remaining drives in the array. If multiple sub-arrays are used, this means that it is only necessary to read the data from the remaining drives in the sub-array, not all of the drives in the array. This increases both the rebuild speed and the speed of access to missing data, which also has to be recreated from the remaining drives.
Summary
In summary, for maximum performance, NEXIO Farad storage systems use six drives per array, Four data and two parity. Chunk size is set to 256K, which means that each stripe is 1024K. The NEXIO file system writes data in precise multiples of this stripe size, with all write operations starting at byte 0 of the stripe.
©2011 Harris Corporation. All rights reserved.
B
Troubleshooting
This appendix provides typical solutions for problems you may encounter while using StorView to control and manage the storage systems. Also refer to
on page 160 and review the cause and actions for each event listed.
Topics including the following:
Clearing the StorView Event Log
Advanced Power Management Events
©2011 Harris Corporation. All rights reserved.
151
152
Appendix B
Troubleshooting
Symptoms
Failure Indicators
Symptom Reason Solution
Continuous indications that the partner controller has failed or is missing.
A partner controller in an
Active-Active configuration has failed or was removed.
Operating in a
Stand-Alone configuration with Single Controller
Mode not selected.
Until the partner controller is replaced, temporarily enable Single Controller Mode in the Controller Parameters tab. Be sure to disable this option when the partner controller is to be replaced.
If you are operating in a Stand-Alone configuration, enable the Single Controller
Mode setting in the Controller Parameters tab.
Rebuild Problems
Symptom Reason Solution
Spare not automatically starting when drive failure occurs in a redundant array in which a global spares are configured.
The Auto
Rebuild option is not enabled in the Controller
Parameters.
Spare disk drive is too small to be used for the drive replacement.
Waiting for a valid replacement drive to be inserted.
Open the Controller Information window (click the
Controller icon), place a check mark in the box by clicking the check box on the Auto Rebuild parameter.
Ensure that the disk drive defined as a spare is equal to or greater than the size of the drive members of the arrays.
If Auto Rebuild is not selected and no global spare drives are assigned, but Auto Spare is enabled. The array will begin rebuilding once a valid replacement drive is inserted in the drive slot of the failed drive.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
153
Rebuild Problems
(Continued)
Symptom Reason
After switching drives and/or controllers from one storage system enclosure to another, one of the solutions reports that the storage system is being monitored by another host.
Multiple
Configuration
WWNs being used.
Inadvertently pulled the incorrect drive from the enclosure during rebuild
(with spares).
Possible incorrect drive identification and removal.
Inadvertently pulled the incorrect drive from the enclosure during rebuild
(no spares).
Possible incorrect drive identification and removal.
Solution
If you have been interchanging configured drives or controllers between storage systems you may have a situation where multiple systems are now sharing the same Configuration WWN. This can be corrected by changing the Configuration WWN value found in the
Controller Parameters on either of the storage systems.
Duplicate WWNs will also cause drive discovery issues at all host computers. This can be diagnosed by searching for duplicate WWNs of target ports in the FC switch nameserver. After making this change, all participating FC switches and host systems will require a reboot.
1
The set will enter critical state. The rebuild operation will stop.
2
A new rebuild operation will begin using one of the spare drives.
3
The inadvertently pulled drive may be re-inserted into the set after the rebuild begins. Use StorView to assign
the re-inserted drive as a global spare (see
1
The set will enter critical state.
2
The inadvertently pulled drive may be re-inserted into the set at any time. A rebuild operation will begin using the inadvertently pulled drive if the Auto Spare option is enabled (default setting). If Auto Spare is not enabled, then start the rebuild manually using the StorView
©2011 Harris Corporation. All rights reserved.
154
Appendix B
Troubleshooting
Rebuild Problems
(Continued)
Symptom Reason
Inadvertently pulled the incorrect drive from the enclosure while rebuilding 2 failed drives.
Possible incorrect drive identification and removal.
Solution
1
The set will enter the “Failed Array” state.
2
Re-inserting the drive will return the set to critical state.
3
A new rebuild operation will start automatically if a spare is available and Auto Spare is enabled. If Auto
Spare is not enabled, then start the rebuild manually using the StorView interface (see
NOTE:
For all arrays, removing a drive as described above will cause all current processing I/O from the controller to stop. I/O in progress will be lost. This will be covered by the intrinsically mirrored copy. The number of Volume
Recoverable errors shown in IM Monitor will increase until the set is restored to critical state.
Login/Management Problems
Symptom Reason
Password Error Password not accepted at log in.
Password was forgotten or lost.
Lost communication with the RAID Controllers.
Connectivity
Solution
Password is case sensitive, ensure that the password is entered correctly.
Contact technical support for the procedures to recover from a lost or missing password.
Ping the target IP address to make sure it responds.
Lost communication with the RAID Controllers.
(
continued
)
StorView controller is hung.
Try connecting to StorView through the other controller’s Ethernet port. A watchdog timer will reset a hung StorView controller after a few minutes.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
155
Login/Management Problems
(Continued)
Symptom Reason Solution
After switching drives and/or controllers from one storage system enclosure to another, one of the solutions reports that the storage system is being monitored by another host.
Multiple
Configuration WWNs being used.
If you have been interchanging configured drives or controllers between storage systems you may have a situation where multiple systems are now sharing the same Configuration WWN. This can be corrected by changing the Configuration WWN value found in the Controller Parameters on either of the storage systems. After making this change, all participating FC switches and host systems will require a reboot.
I received the following message: “Lost communication with server. The server maybe down.”
During heavy host operations and/or data I/O, the system may become too busy to complete requests from the web browser in the time allocated.
After several updated attempts have failed you will see this message. At this time you can try to use the
Browsers’ refresh function to reload the StorView
GUI. If you continue to receive that message, close the browser and wait until I/O traffic has settle down before opening the StorView GUI back up.
You will still continue to receive email notifications and Event logging.
During heavy data I/O, when I try to make a configuration change I get a failure saying that the controller is busy
The controller’s onboard resources are consumed.
Configuration changes during heavy
I/O are not recommended. You can either wait until there is less data traffic or keep re-trying the command until it is successful.
Enclosure image on the
Main screen is dimmed or greyed out.
Cannot start SSL
StorView while using a
Microsoft Proxy Server.
Enclosure Support option has been disabled.
Access the Controller Information window by clicking the Advanced Settings icon. Verify the option “Enclosure Support” is checked and click
APPLY. Close the window.
Issue with allowing the secure port on the proxy.
Refer to
for details on issues with a proxy server.
©2011 Harris Corporation. All rights reserved.
156
Appendix B
Troubleshooting
Login/Management Problems
(Continued)
Symptom Reason Solution
I received the following message: “Lost communication with server. The server maybe down.”
During heavy host operations and/or data I/O, the system may become too busy to complete requests from the web browser in the time allocated.
After several updated attempts have failed you will see this message. At this time you can try to use the
Browsers’ refresh function to reload the StorView
GUI. If you continue to receive that message, close the browser and wait until I/O traffic has settle down before opening the StorView GUI back up.
You will still continue to receive email notifications and Event logging.
Trust an Array
When you create an array, you have the option to trust the array. This option should only be used in environments where you fully understand the consequences of the function. The trust array option is provided to allow immediate access to an array for testing application purposes only.
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 drive. The parity data is inconsistent and so a drive failure within a trusted array will cause data loss.
Trusted arrays should not be used on NEXIO Farad systems and in no circumstances can they be used on a system committed to air.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
157
To verify an Array’s trustworthiness
1
On the
Main
screen under
Configuration
, click the
Create Array
icon.
The
Create Array
window displays.
2
Select your drives in the
Available Drives
section.
3
Enter a name for your array. You may use up to 32 characters (ASCII).
4
Select the
RAID level
for the array.
5
Enter the chunk size by clicking the pull-down menu and choose from the available values.
6
At
Item 7
, use the pull-down menu and select
Trust Array
.
7
Choose the
Back-off Percent
(reserved capacity) for the drives. The default is 1%.
8
Set the
Read-Ahead Cache
threshold.
9
Set the
Writeback Cache
options.
10
Click
CREATE
to create and trust the array.
©2011 Harris Corporation. All rights reserved.
158
Appendix B
Troubleshooting
Figure B-1
Main Screen - Trusted Array Example
A trusted array is indicated on the Main screen with the following icon, which appears adjacent to the array name.
Event Logs
Overview
StorView has the ability to manage the events generated by the controller and enclosure components. StorView also has its own unique set of 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:
Advanced Power Management
Alarms
Controller, UID, Controller Ports, and Expansion modules
Drive and Array
Enclosure components
Fibre Loop and SAS/SATA Bus (Drive and Host)
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
159
Network communication (applicable to the host-based version only)
Persistent Reservations
StorView server (applicable to the host-based version only)
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 StorView’s 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 user friendly language to describe the event.
The controller’s 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 de-selecting 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
DO NOT Disable this option on NEXIO Farad.
StorView’s event log will maintain the controller’s compilation of events and the software’s specific events. The controller’s compilation of events include Controller
Events (those unique to the RAID Controller), Drive Events and Host Events, and if the Enclosure Support option is enabled, enclosure component events.
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.
©2011 Harris Corporation. All rights reserved.
160
Appendix B
Troubleshooting
The time stamp for each event in the StorView log is the exact time the event was received by StorView, and can be slightly off for the actual time it occurred in the controller log. After synchronization, events that occurred while the StorView server was down are marked with an additional string in the event description which displays the actual time stamp that event occurred. The string will be in the form of an asterisk followed by the time and date in parenthesis. At the bottom of the Event Log window you will find the footnote “* Indicates event occurred while
Server module was down.” This indicates that those events with this extra time stamp in the description are the results of a synchronization and displays the exact time the event actually occurred.
StorView’s event log has a maximum size limited only by the available disk space, therefore the log events in StorView will require regular maintenance to ensure the list is manageable and doesn’t fill to 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
.
StorView Event Log
Viewing the
Event Log
To access the Event Log
On the
Main
screen, click on the
LOGS
button located under the
Harris Logo
.
Figure B-2
Main Screen with Event Log Screen
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
161
Event Type
Icons
The following icons display under the status column in the Events Log:
Information
Warning
Error
Figure B-3
Event Log Status Icons
Navigating the
Event Logs
You can use the
Next
and
Previous
buttons located at the top and bottom of the
Events Log window
to scroll through the logs.
To scroll through the Event Logs
1
Press either the
Previous
or
Next
buttons.
2
Observe the
Status Bar
located on the bottom of the Event Logs window.
It may take up to a minute to refresh the page.
©2011 Harris Corporation. All rights reserved.
162
Appendix B
Troubleshooting
To close the Event Logs window
Do one of the following:
Click on the red
X
in the upper right corner of the window.
Press the
Close
button located at the bottom of the window.
Exporting the
Event Logs
The event logs can be exported to a comma delimited file for use in third-party software products. Some web browsers provide more options for the format of the file. Refer to your browser software for specific details.
To export the log file from Internet Explorer
1
On the
Main
screen, click on
Controller 0 & 1
.
The
Controller
window displays.
©2011 Harris Corporation. All rights reserved.
2
Click on
EXPORT LOGS
.
NEXIO Farad
User Guide
163
The
File download
window displays.
©2011 Harris Corporation. All rights reserved.
164
Appendix B
Troubleshooting
3
Select one of the following options from the
File Download
window:
Open.
Select this option if you want to view the document. The
ControllerLogs.csv
window displays. Once the file opens, you can change the formatting before saving it.
Save.
Select this option if you want to save the file without making formatting changes. Once the
Save As
window displays, navigate to a location and save the file. The default name for the file is
ControllerLogs.csv
. You can change the name of the file, but keep the .csv file extension.
Cancel.
Select this if you want to cancel exporting the file.
©2011 Harris Corporation. All rights reserved.
To export the log file from Mozilla Firefox
1
On the
Main
screen, click on
Controller 0 & 1
.
NEXIO Farad
User Guide
165
The
Controller
window displays.
2
Click on
EXPORT LOGS
.
©2011 Harris Corporation. All rights reserved.
166
Appendix B
Troubleshooting
The
Opening ControllerLogs.csv
window displays.
3
Select one of the following options from the
Opening ControllerLogs.csv
window:
Open.
Select this option if you want to view the document. You can open the file using the Microsoft Office Excel default option. Or you can select another program. Once the file opens, you can change the formatting before saving it.
Save File.
Select this to download and save the file to your local machine.
The
Download
window displays and provides a status bar.
4
Click
OK
to close the
Opening ControllerLogs.csv
window.
©2011 Harris Corporation. All rights reserved.
Clearing the StorView Event Log
You can clear the StorView event log retained on the server from the
Controller Information
window.
To clear the log file
1
On the
Main
screen, click on
Controller 0 & 1
.
NEXIO Farad
User Guide
167
The
Controller
window displays.
2
Click
Clear Logs
.
©2011 Harris Corporation. All rights reserved.
168
Appendix B
Troubleshooting
3
Click
Yes
to confirm or
Cancel
to abort the request.
4
Click
Close
at the bottom of the
Controller
window.
List of Events
Events here are categorized and listed in the order of their individual Event Type
[ID]. As this is a comprehensive list of all events, not every event is applicable to every controller or enclosure model.
Drive and Array Events
These events are related to the drives, loops (where applicable) and disk arrays. The
ID is given in the format of its hexadecimal value.
On SATA disk drives the event message displays the drive’s serial number and on
SAS drives the world wide name is displayed.
Failed Drives Codes
The controller maintains a list of failed drives.
Drives are listed in the following format:
Failed Drive:xx SN: <xxxxxxx>
Reason Code
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
169
The reason code may be one of the following:
Reason Code
Drive Time-out
Reason
The drive has either timed out or been removed.
Command: xx Sense
Key:
yy
Ext Sense:
zz
The drive has failed for the specified command, with the indicated SCSI sense key and extended sense key.
Action
Re-insert the disk drive.
or
Replace the disk drive.
Replace the disk drive.
Drive & Array Event Messages
The drive w/(SN/WWN) <
xxxxxxx
>
(Slot <
nn
>, Enclosure <
nn
>) (<
Array
Name
> Drive <
member index
>) has failed due to an unrecoverable error.
Sense Data: <
xx
>/<
xx
>/<
xx
>.
The drive w/(SN/WWN) <
xxxxxxx
>
(Slot <
number
>) (Drive <
number
>) has been marked as failed because it was removed.
Type [ID]
Error
[0xB0A
(2826)]
Error
[0xB0B (2827)]
Cause Action
Typically due to a non-recoverable media error or hardware error.
Replace the disk drive.
Drive has been removed or bypassed by the user, or has a serious hardware error.
Removal of cables connecting the enclosures.
Replace the disk drive.
Replace the cables.
Rebuilding has failed due to an unrecoverable error on the new drive w/(SN/WWN) <
xxxxxxx
> (Slot
<
number
>) (Drive <
number
>) in the array.
Error
[0xB0C
(2828)]
Rebuilding has failed due to an unrecoverable error on the new drive w/(SN/WWN) <
xxxxxxx
> (Slot <
nn
>,
Enclosure <
nn
>) (<
array name
> Drive
<
num
>).
Error
[0xB0D
(2829)]
Error
[0xB0E (2830)]
The drive w/(SN/WWN) <
xxxxxxx
>
(Slot <
nn
>, Enclosure <
nn
>) (
Slot
<number
>) (Drive <
number
>) has failed due to a time-out.
Drive Loop 1 is not initializing correctly.
Error
[0xB10 (2832)]
Typically due to a non-recoverable media error, or hardware error.
Typically due to a non-recoverable media error or hardware error.
Drive error.
Loop error.
Replace with a new drive and initiate a rebuild.
Backup all data and restore to a new array.
Replace the disk drive.
Check the cables.
©2011 Harris Corporation. All rights reserved.
170
Appendix B
Troubleshooting
Drive & Array Event Messages
Disabled Enclosure <
name
> Slot
<
nn
> due to excessive errors.
Type [ID]
Error
[0xB13 (2835)]
Cause
This indicates that the controller has shutdown the slot due to multiple errors from the drive.
Action
Remove the drive in the identified slot will re-enable the PHY.
Replace the disk drive or MUX Transition
Board.
SATA Multiplexer switching failure on
Enclosure <
xxxxxx
> Slot <
nn
>.
Error
[0xB13 (2835)]
This indicates that the controller has tried multiple times to switch 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.
Drive Loop 1 has exceeded the allowable error count. The controller will not use this loop for data transfers. After two hours have elapsed, the loop will be re-enabled.
Array <
name
> is in a critical state.
Error
[0xB14 (2836)]
Too many errors on the loop.
Error
[0xB1B (2843)]
Drive removal or failure.
The drive w/(SN/WWN) <
xxxxxxx
>
(Slot <
number
>) returned a bad status while completing a command.
SCSI Info: Operation <
type
>, Status
<
type
>.
Error
[0xB27 (2855)]
Unknown status returned by the disk drive.
Wait two hours and try again.
Replace the disk drive and rebuild the array.
Contact technical support and provide them with a copy of the event log.
No action necessary.
The drive w/(SN/WWN) <
xxxxxx
>
(Slot <
number
>) returned a bad status while completing a command.
SCSI Info: Operation <
type
>, Status
<
type
>.
Information
[0xB27 (2855)]
Disk drive returned a check condition.
The drive w/(SN/WWN) <
xxxxxx
>
(Slot <
number
>) returned a bad status while completing a command.
SCSI Info: Operation <
type
>, Status
<
type
>.
Error
[0xB27 (2855)]
SCSI status command was terminated.
Contact Technical
Support and provide them with a copy of the event log.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
171
Drive & Array Event Messages
The drive w/ (SN/WWN) <
xxxxxxx
>
(Slot
n
, Enclosure
n
) returned a bad status while completing a command.
SCSI Info: Operation =
a
, Status =
b
(c/d/e)
.
Type [ID]
Information
[0xB27 (2855)]
Cause
Drive is busy and cannot accept any more commands.
The drive w/(SN/WWN) <
xxxxxxx
>
(Slot
n
, Enclosure
n
) returned a bad status while completing a command.
SCSI Info: Operation =
a
, Status =
b
(c/d/e)
.
Information
[0xB27 (2855)]
Drive is busy and cannot accept any more commands.
See ([0xBAA (2986)]) below.
Action
No action necessary.
No action necessary.
The drive w/(SN/WWN) <
xxxxxxx
>
(Slot <
nn
>, Enclosure <
nn
>) timed out for the SCSI Operation <
type
>.
A rebuild has started on the drive w/
(SN/WWN) <
xxxxxxx
> (Slot <
nn
>
(Drive <
number
>).
A rebuild has completed on (Array
<
Name
> Drive <
number
>).
Warning
[0xB28 (2856)]
Information
[0xB30 (2864)]
Drive hardware error or bus error.
A rebuild has started.
Check cabling and ensure the disk drives are properly seated.
No action necessary.
A rebuild has re-started on the drive w/(SN/WWN) <
xxxxxxx
> (Slot <
nn
>
(Drive <
number
>).
Information
[0xB31 (2865)]
Information
[0xB32 (2866)]
A rebuild has completed.
Array <
name>
has started initializing. Information
[0xB33 (2867)]
Initialization has started.
No action necessary.
A rebuild has started.
No action necessary.
No action necessary.
Array <
name>
has completed initializing.
The controller has detected a data underrun from the drive w/(SN/
WWN) <
xxxxxxx
> (Slot <
nn
>,
Enclosure <
nn
>) for the SCSI Op
Code 0x<
xx
>. This is caused by the controller detecting a bad CRC in a frame, and usually indicates a link problem, either with cabling or an enclosure.
Information
[0xB34 (2868)]
Error
[0xB3B (2875)
Initialization has completed.
Bus error.
No action necessary.
Check cabling and ensure that the disk drive is properly seated in its slot.
©2011 Harris Corporation. All rights reserved.
172
Appendix B
Troubleshooting
Drive & Array Event Messages
An unrecoverable drive error has occurred as a result of a command being issued. This may be due to a drive error in a non-fault tolerant array, such as RAID 0, or when the array is already in a degraded mode.
The controller will pass the status from the drive back to the host system, to allow the host recovery mechanisms to be used. Details: Host
Loop <
x
>, Host Loop ID <
y
>, Mapped
LUN Requested <
z
>, Op Code <
zz
>,
Sense Data <
uu
>.
Type [ID]
Error
[0xB40 (2880)]
Cause
Typically due to a non-recoverable media error, hardware error, or loop (bus) error.
Action
No action necessary.
No action necessary.
A RAID parity check has started on
<
Array Name
>. Type of parity check
= <
paritytype
>.
A RAID parity check has completed on <
Array Name
>. Type of parity check = <
paritytype
>. Error Count =
<
zz
>.
A RAID parity check has been aborted on <
Array Name
>. Type of parity check = <
paritytype
>. Error
Count = <
zz
>.
A drive w/(SN/WWN) (Slot <
nn
>,
Enclosure <
nn
>) has been inserted.
Information
[0xB43 (2883)]
Information
[0xB44 (2884)]
Information
[0xB45 (2885)]
Parity check started.
Parity check completed.
Parity check canceled by the user.
Information
[0xB61 (2913)]
Drive was inserted.
The controller has started updating a drive’s firmware. Drive w/(SN/WWN)
<
xxxxxx
> (Slot <
nn
> ID:<
zz>
Firmware Version: <
yy.yy.yyyy
).
Information
[0xB66 (2918)]
The controller has started updating a drive’s firmware. Drive
<w/sn <xxxxxxx> or w/ wwn
<
xxxxxxxxxxxxxxxx
>,
Slot <
nn
>, Enclosure
<
nn
>, Firmware
Version:<
xxxx
>.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
173
Drive & Array Event Messages
The controller has finished updating a drive’s firmware. Drive (SN/WWN):
<xxxxxxx>
ID:<
zz>
(Slot <
number
>)
Firmware Version: <
yy.yy.yyyy
).
Type [ID]
Information
[0xB67 (2919)]
Cause
The controller has finished updating a drive’s firmware. Drive w/SN <xxxxxxx> or
WWN
<
xxxxxxxxxxxxxxxx
>,
Slot <
nn
>, Enclosure
<
nn
>, Firmware
Version:<
xxxx
>.
Action
No action necessary.
An array expansion has started on
Array <
name
>.
An array expansion has completed on
Array <
name
>.
Information
[0xB69 (2921)]
An array expansion has restarted on
Array <
name
>.
The writeback cache on Array
<
name
> has been disabled.
Reason(s): (S
ee reasons
).
Information
[0xB68 (2920)]
Information
[0xB6A
(2922)]
Warning
[0xB6F (2927)]
Expansion has started.
No action necessary.
Expansion has completed.
Expansion has restarted.
No action necessary.
No action necessary.
Disabling of writeback cache for the indicated reasons:
• The partner controller has failed.
• The battery is not charging or present.
• The array has become critical.
• A “prepare for shutdown” was received by the controller.
• Replace the failed controller.
• Charge the backup battery or re-install the battery.
• Resolve the array issue and rebuild the array.
• No action necessary.
The writeback cache on Array
<
name
> has been re-enabled.
Because of a background verify failure, data blocks at LBA <yyy> from drive (SN/WWN):
<xxxxxxx>
(Slot <
number
>) (Consecutive
Number of Allocations <
zz
>) have been reallocated.
Information
[0xB70 (2928)]
Warning
[0xB71 (2929)]
Re-enabling of writeback cache.
Data Blocks at this location have media errors. The data is being reallocated to different blocks.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
174
Appendix B
Troubleshooting
Drive & Array Event Messages Type [ID]
A rebuild was aborted on (Array <
yy
>
Drive <
ww
>).
Information
[0xB73 (2931)]
SATA Drive Error: (Slot <
number
Information <description>.
>)
A drive w/(SN/WWN)
<xxxxxxx>
(Slot
<
nn
>) has been removed.
Error
[0xB75 (2933)]
Error
[0xB76 (2934)]
Cause
A rebuild was canceled by the user.
Action
No action necessary.
Drive or SATA link error.
A drive w/ SN
<xxxxxxx>
(Slot <
nn
>,
Enclosure <
nn
>) has been removed.
No action necessary.
No action necessary.
There was a bad block during a rebuild on Array <
nn
>, Drive <
mm
>,
LBA <
xx xx xx xx xx xx
>, Block Count
<xx>.
Error
[0xB78 (2936)]
A bad block was detected during the rebuild operation. Data loss will occur with that data stripe.
Replace drive after rebuild. Restore lost data from a known good backup.
An unsupported drive w/(SN/WWN)
<xxxxxxx> (Target ID <num>) has been inserted.
<Array Name> is in an unsupported configuration with a mixture of A/P and A/A SATA drives.
<
Array Name
> is in an unsupported
A/P SATA drive mutiplexer configuration.
Error
[0xB7B (2939)]
Error
[0xB8C
(2956)]
Error
[0xB8C
(2956)]
A SATA drive with an
A/A MUX Transition card was installed in a system with an older model controller.
The array is marked invalid because it contains SATA drives with a mixture of
Active-Active and
Active-Passive MUX
Transition cards.
A SATA drive with an
Active-Active MUX
Transition card is not supported in older 12 drive enclosures.
The array is marked invalid because it contains a SATA drive with an unsupported
Active-Passive MUX
Transition card.
Replace the SATA drive with one that has a A/P MUX
Transition card installed.
Replace the offending drive with one that contains a matching
MUX Transition card as the remaining drive members.
Replace the offending drive with one that contains a matching
MUX Transition card.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
175
Drive & Array Event Messages
<
Array Name
> is in an unsupported
A/A SATA drive mutiplexer configuration.
Extended Sense: Information =
0x%.2X %.2X %.2X %.2X
,
Command Specific=
0x%.2X %.2X
%.2X %.2X
, FRU Code =
0x%.2X
,
Sense Data =
%.2X %.2X %.2X
.
Information
[0xBAA
(2986)]
The drive w/
%s
(Slot
%s
, Enclosure
%s
) (
%s
Drive
%d
) is no longer in proxy mode.
Information
[0xBAD
(2989)]
The drive w/
%s
(Slot
%s
, Enclosure
%s
) (
%s
Drive
%d
) has entered proxy mode.
Information
[0xBAD
(2989)]
The drive w/
%s
) (
%s
%s
Drive count exceeded.
(Slot
%d
%s
, Enclosure
) drive path error
Type [ID]
Error
[0xB8C
(2956)]
Warning
[0xBAD
(2989)]
Cause
The array is marked invalid because it contains a SATA drive with an unsupported
Active-Active MUX
Transition card.
Action
Replace the offending drive with one that contains a matching
MUX Transition card.
Due to size constraints on event log entries, it is necessary to add another event that is an extension of the previous drive check condition event (see
[0xB27 (2855)]). To facilitate drive vendors in warranty claims, these fields are logged in a new event log entry.
Error conditions cleared.
Contact Technical
Support and provide them with a copy of the event log.
No action necessary.
Drive errors are reported and the path
I/O is being handled by the other controller.
Check the host cabling.
Replace the disk drive.
Replace the RAID
Controller.
Possible SAS link or drive internal error.
Check the host cabling.
Replace the disk drive.
Replace the RAID
Controller.
©2011 Harris Corporation. All rights reserved.
176
Appendix B
Troubleshooting
Controller Port Events
These events are related to the host side Controller Port or Loop. The ID is given in the format of its hexadecimal value.
Controller Port Event
Messages
Host Loop 0 is not initializing correctly.
SAS Port 0 will not initialize.
Host Loop 1 is not initializing correctly.
SAS Port 1 will not initialize.
Type [ID]
Error
[0xB15
(2837)]
Error
[0xB15
(2837)]
Error
[0xB16
(2838)]
Error
[0xB16
(2838)]
Cause
The loop is not initializing.
The port is not initializing.
The loop is not initializing.
The port is not initializing.
Action
Check/replace the cable.
Replace the
Controller.
Check/replace the cable.
Replace the
Controller.
Check/replace the cable.
Replace the
Controller.
Check/replace the cable.
Replace the
Controller.
Resolve address conflict.
Host Loop 0/1 acquired Loop
ID <
xx
> because we were not able to get Loop ID <
xx
> (as specified in the controller settings).
A LIP has occurred on Drive
Loop <
xx
>.
Error
[0xB17 (2839)]
[0xB18 (2840)]
Address conflict with either host adapter or other device on the same loop.
The loop is disrupted or the host is booting.
The Drive Loop (
The Drive Loop (
xx xx
) is up.
) is down.
Information
[0xB21
(2849)]
Information
[0xB22
(2850)]
Information
[0xB23
(2851)]
Loop is up.
Loop is down.
No action necessary.
No action necessary.
Check/replace the cable.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
177
Controller Port Event
Messages
A LIP has occurred on Host loop < times.
xx
>. Reason: <
type
The LIP was repeated <
yy
>,
>
Type [ID] Cause Action
Information
[0xB24 (2852)]
A LIP was generated so that a loop port could acquire a physical address on an arbitrated loop.
A LIP was generated by port
ID: <
xx
> so that the loop would be re-initialized.
A LIP was generated because of a loop failure.
No action necessary.
No action necessary.
Information
[0xB24 (2852)]
A LIP was generated by port
ID: <
xx
> because of a loop failure.
A LIP has occurred on Host loop <
xx
>. Reason: <
type
>,
The LIP was repeated <
yy
> times.
Host Loop <
xx
> is now up.
Information
[0xB25 (2853)]
Loop is becoming ready.
No action necessary.
SAS Host Port <
xx
> is now up.
Information
[0xB25 (2853)]
Host Loop <
xx
> is down.
Information
[0xB26 (2854)]
SAS port is becoming ready.
No action necessary.
Loop is going down.
Check/replace the cable.
SAS Host Port <
Host Loop <
num
> has reported an error status of
0x<
xx
> to a particular command.
xx
> is down.
A host has accessed a Logical
Drive <
yy
> for the first time, or for the first time following a reset or LIP. It accessed it through Host Loop <
xx
> (ID
<
zz
>) with the SCSI command
<
check condition, busy, or task set full
>.
Information
[0xB26 (2854)]
Information
[0xB2E (2862)]
Error
[0xB37
(2871)]
SAS port is going down.
Check/replace the cable.
No action necessary.
First access by a 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
>.
This may indicate a loop reset or LIP during a command, or a loop failure. Repeat Count =
<
count
>.
No action necessary.
However, this event is usually followed by another event that indicates the real problem.
©2011 Harris Corporation. All rights reserved.
178
Appendix B
Troubleshooting
Controller Port Event
Messages
SAS Host Port < was repeated < times.
num
reported an error <
> has
port
>. It
number of times the error happened
>
Type [ID]
Error
[0xB37
(2871)]
Drive Loop <
num
> has reported an error status of
<
error status
> to a particular command. This may indicate a loop reset or LIP during a command, or a loop failure.
Repeat Count = <
number of times the error happened
>.
Host Loop <
num
> has reported an invalid status of
0x<
xx
> to a particular command.
Error
[0xB38
(2872)]
Error
[0xB39
(2873)]
The controller has generated a
LIP on Drive Loop <
xx
>, due to a loop error.
Error
[0xB3C
(2876)]
Cause Action
This may indicate a reset or LIP during a command. Repeat
Count = <
count
>.
No action necessary.
However, this event is usually followed by another event that indicates the real problem.
The drive loop encountered a loop reset or LIP during a command or a loop failure has occurred.
This indicates a firmware error in the host fibre channel chip.
No action necessary.
Contact technical support.
The controller has generated a
LIP on Host Loop <
xx
>, due to a loop error.
Error
[0xB3D
(2877)]
The host system w/
WWN:<
xxxxxxxxxxxxxxxx
> and
Loop ID of <
xx
> has logged into the controller through
Host Loop <
xx
>. These events will only be listed for HBAs with SAN LUN Mappings.
Information
[0xB3F (2879)]
Controller initiated a LIP on
Drive Loop 1 due to a loop error. Could be caused by a disk drive being pulled or any drive side loop LIP.
Controller initiated a LIP.
No action necessary.
However, this event is usually followed by another event that indicates the real problem.
No action necessary.
Host systems logs into the controller.
No action necessary.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
179
Controller Port Event
Messages
SAS Host System
<xxxxxxxxxxxxxxxx>
has logged into
<y>
. (ID:
<z>
).
SAS Host System
<xxxxxxxxxxxxxxxx>
has logged out of
<y>
. (ID:
<z>
).
Type [ID]
Information
[0xB7C
(2940)]
Information
[0xB7D
(2941)]
Cause
Host system has logged into the controller port
<y>
.
Action
No action necessary.
Host system has logged out of the controller port
<y>
.
No action necessary.
Enclosure Events
These events are related to the enclosure components reported by the SES processor. The ID is given in the format of its hexadecimal value.
Enclosure Event Messages Type [ID] Cause
Information
[0xB6B (2923)]
Normal condition reported.
Action
Enclosure<
xx
> (w/
WWN:<
xxxxxxxxxxxxxxxx
>) timed out on SCSI command
0x02X.
Warning
[0xB79 (2937)]
NOTE
: This event is only valid for the expansion enclosure or daisy-chained systems.
This error is generated when a command to the Enclosure processor time-outs.
Faulty cable or drive malfunctions could be the cause of this error.
Verify if the system has gone to
SES_LEVEL_1. If it has, verify the configuration.
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 need to intervene. If this event is periodically posted in the event log the user may have a hard drive or EBOD I/O module problem. The system should be inspected to isolate the problem to either drives or
EBOD
I/O module.
Power supply <
zz>
is OK.
No action necessary.
©2011 Harris Corporation. All rights reserved.
180
Appendix B
Troubleshooting
Enclosure Event Messages Type [ID]
Power supply <
zz>
is operating outside of its specification.
Warning
[0xB6B (2923)]
Cause
The specific power supply has failed.
The specific power supply has the mains power removed.
Power supply <
zz>
is in a critical state.
Action
Replace the power supply module.
Ensure that the specific power supply mains power is applied.
Warning
[0xB6B (2923)]
The specific power supply has failed.
The specific power supply has the mains power removed.
The power supply was removed.
Replace the power supply.
Ensure that the specific power supply mains power is applied.
Insert the power supply.
Power supply <
zz>
is not installed.
Error
[0xB6B (2923)]
The power supply was removed.
An Expansion enclosure was connected to Enclosure
ax
.
The enclosure count increased from
yy
to
zz
.
Information
[0xB98 (2968)]
Expansion cable was connected.
Re-insert the power supply, connect the power cord.
No action necessary.
An Expansion enclosure was removed from Enclosure
xx
.
The enclosure count decrease from yy to
zz
.
Warning
[0xB98 (2968)]
Expansion cable was disconnected.
Re-connect the SAS patch cable.
The expansion cable was removed from Enclosure
<
xz
> or failed for more than
10 times in an hour.
Warning
[0xB99 (2969)]
The user disconnected an expansion cable greater than 10 times or the cable failed for more than 10 times in an hour.
Replace cable.
The expansion cable was removed from Enclosure
<
xx
> or failed for more than
10 times in a hour.
Information
[0xB99 (2969)]
The firmware image was not corrupt.
No action necessary.
The expander SPIMEM image is valid. Current version:
xxxxx
, new version:
xxxxx
.
Information
[0xB99 (2969)]
Firmware was updated successfully.
No action necessary.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
181
Enclosure Event Messages Type [ID] Cause
The expander SPIMEM was updated successfully.
Current version:
xxxxx
, new version:
xxxxx
.
Error
[0xB99 (2969)]
Corrupt file.
The header of the expander
SPIMEM download image is invalid. Current version:
xxxxx
, new version:
xxxxx
.
Error
[0xB99 (2969)]
Corrupt file.
The ID of the expander
SPIMEM download image does not match. Current version:
xxxxx
, new version
xxxxx
.
Error
[0xB99 (2969)]
Corrupt file.
Action
Obtain a new copy of the file.
Obtain a new copy of the file.
Obtain a new copy of the file.
The CRC of the expander
SPIMEM download image does not match. Current version:
xxxxx
, new version:
xxxxx
.
Error
[0xB99 (2969)]
Failed to update.
Power supply <
zz>
is in an unrecoverable state.
Power supply <
zz>
is not installed.
Fan <
zz>
is OK.
Fan <
zz>
does not support status detection.
Error
[0xC6B (3179)]
Error
[0xC6B (3179)]
The power supply was removed.
The power supply was removed.
Information
[0xC6C (3180)]
Normal condition reported.
Information
[0xC6C (3180)]
Unknown status.
Obtain a new copy of the file.
Re-insert the power supply, connect the power cord.
Re-insert the power supply, connect the power cord.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
182
Appendix B
Troubleshooting
Enclosure Event Messages Type [ID] Cause
Fan <
zz>
is in a critical state.
Additional information may appear:
The fan is stopped.
The fan is running at its lowest speed.
The fan is running at its second lowest speed.
The fan is running at its third speed level.
The fan is running at its forth speed level.
The fan is running at its fifth speed level.
The fan is running at its intermediate speed.
The fan is running at its highest speed.
Error
[0xC6C (3180)]
A specific fan failure.
Action
Replace the cooling fan module.
Temperature sensor <
zz
> is
OK.
Information
[0xC6D (3181)]
Temperature sensors are reporting normal temperatures in the enclosure.
Temperature <
zz>
is operating outside of specifications.
No action required.
Warning
[0xC6D (3181)]
Temperature sensors are reporting enclosure temperatures have reached the threshold of 50°C (122°F).
Ensure that both cooling fans are operating normally.
(Replace if needed.)
If the environment ambient temperature is high, reduce the ambient temperature.
Ensure that the airflow is not blocked or restricted on the enclosure.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
183
Enclosure Event Messages Type [ID] Cause Action
Temperature sensor <
zz>
is in a critical state.
Error
[0xC6D (3181)]
Temperature sensors are reporting enclosure temperatures have reached the threshold of 70°C (158°F).
Automatic system shutdown will begin. In Active-Active controller configurations, one controller will shutdown its partner and shutdown the drives, then itself.
Ensure that the cooling fans are operating normally. (Replace if needed.)
If the environment ambient temperature is high, reduce the ambient temperature.
Ensure that the airflow is not blocked or restricted on the enclosure.
Advanced Power Management Events
These events are related to Advanced Power Management, APM level 1 and APM level 2. The ID is given in the format of its hexadecimal value.
Advanced Power Management Event
Messages
Type [ID]
APM drive test failed (test result:
w
) on drive w/
xxxxxxxxxx
(Slot
y
, Enclosure
z
).
Sense Data
aa/bb/cc
.
Error
[0xB1D]
Drive w/ SN <
Serial number
> (Slot <
Slot number
>, Enclosure <
Enclosure number
>) executes a spin up cycle.
Information
[0xB93]
Drive w/ SN <
Serial number
> (Slot <
Slot number
>, Enclosure <
Enclosure number
>) executes a spin down cycle.
Information
[0xB93]
These drives execute a spin down cycle
(unused drives: <
Unused drive count
>, spares: <
Spare count
>, failed drives:
<
failed drive count
>).
Information
[0xB94]
Cause
Unrecoverable problem on
APM level 1 drive.
Action
Check the drive.
User or software commanded a drive spin up.
No action necessary.
User or software commanded a drive spin down.
User or software commanded spin down on the identified drive(s).
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
184
Appendix B
Troubleshooting
Advanced Power Management Event
Messages
Type [ID]
These drives execute a spin up cycle
(unused drives: <
Unused drive count
spares: <
Spare count
>, failed drives:
<
failed drive count
>).
>,
<
Array drive count
> drives from array with ID <
Array number
> execute a spin down cycle.
Information
[0xB94]
Information
[0xB95]
<
Array drive count
> drives from array with ID <
Array number
> execute a spin up cycle.
Information
[0xB95]
APM drive test started on <
Drive count
> drives.
Information
[0xB96]
APM drive test started on <
Drive count
> drives from array with ID <
Array number
>.
Information
[0xB96]
APM drive test completed on <
Drive count
> drives.
Information
[0xB97]
APM drive test completed on <
Drive count
> drives from array with ID <
Array number
>.
Information
[0xB97]
The expansion cable was connected to
Enclosure <
Enclosure number
>.
Information
[0xB98]
The expansion cable was removed from
Enclosure <
Enclosure number
>.
Information
[0xB98]
The expansion cable was removed from
Enclosure <
Enclosure number
> or failed for more than 10 times in an hour.
Warning
[0xB98]
Cause Action
User or software commanded spin up on the identified drive(s).
No action necessary.
User or software commanded spin down on the drives in the identified array.
No action necessary.
User or software commanded spin up on the drives in the identified array.
No action necessary.
User or software executed a drive test.
No action necessary.
User or software executed a drive test on the drives in the selected array.
No action necessary.
User or software executed drive test is complete.
User or software executed drive test on the drives in the selected array is complete.
No action necessary.
No action necessary.
The user connected an expansion cable.
The user disconnected an expansion cable.
The user disconnected an expansion cable greater than 10 times or the cable failed for more than 10 times in an hour.
No action necessary.
No action necessary.
Replace cable.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
185
Alarm Events
These events are related to the audible alarm reported by the SES processor. The ID is given in the format of its hexadecimal value.
Alarm Event Messages
The audible alarm is temporarily muted.
Alarm Disable.
Alarm Enable.
Type [ID]
Information
[0xB8D
(2957)]
Information
[0xB8E (2958)]
Information
[0xB8F (2959)]
Cause
The user muted the alarm.
The audible alarm is temporarily muted.
Action
No action necessary.
The user disabled the alarm.
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.
No action necessary.
The user disabled the alarm.
The audible alarm has been enabled and will allow all alarms to be heard.
No action necessary.
Alarm <
x
> is Off (Muted).
Where <
x
> is the alarm number.
Currently there is only one alarm in the enclosure system, however this is a provision for future expansion.
Information
[0xC6E (3182)]
No status condition being reported.
Alarm silenced.
Alarm <
x
> is Intermittent. Warning
[0xC6E (3182)]
A status condition caused the alarm to sound every two minutes until muted.
Alarm <
x
> is Remind.
No action necessary.
User pressed the
Alarm Mute button on the front panel.
Press the Alarm
Mute button on the front panel and isolate the cause of the alarm.
Warning
[0xC6E (3182)]
A status condition that caused the alarm to sound is continuing to remind the user.
Press the Alarm
Mute button on the front panel and isolate the cause of the alarm.
©2011 Harris Corporation. All rights reserved.
186
Appendix B
Troubleshooting
Alarm Event Messages
Alarm <
x
> is On Continuous.
Type [ID]
Error
[0xC6E (3182)]
Cause
A status condition caused the alarm to sound.
Action
Press the Alarm
Mute button on the front panel and isolate the cause of the alarm.
Controller
Events
The following table provides a brief description of the events that relate to all models of the RAID Controller and the Configuration. The ID is given in the format of its hexadecimal value.
Table B-1
Events and Configuration for the RAID Controller
Controller Events Messages Type [ID] Cause
There was a fatal Watchdog
Error.
Additional Info:
(Advanced hex data for customer service or engineering use.)
.
Error
[0xB01 (2817)]
Internal hardware or firmware failure.
There was a fatal ECC Error.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Fault SDRAM or damaged internal bus.
There was a fatal Host Fibre
Channel Interface Error on
Loop <
xx
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Internal hardware or firmware failure on the coprocessor.
There was a fatal
Coprocessor Error.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Internal hardware or firmware failure on the coprocessor.
Action
Replace the controller.
Replace the controller.
Replace the controller. Contact technical support.
Replace the controller.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
187
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
There was a fatal Data
Abort: <
yyyyyyyy
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
This fatal controller event log error indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
There was a fatal Prefetch
Abort: <
yyyyyyyy
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
There was a fatal Software
Interrupt: <
yyyyyyyy
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
There was a fatal Bad
Instruction: <
yyyyyyyy
Additional Info:
(Advanced hex data for customer service or engineering use.).
There was a fatal IRQ
INTERRUPT: <
yyyyyyyy
>.
>.
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
Additional Info:
(Advanced hex data for customer service or engineering use.).
There was a fatal ATU Error:
<
yyyyyyyy
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
There was a fatal PBI Error:
<
yyyyyyyy
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
Action
No action necessary.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
188
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
There was a fatal AAU
Error: <
yyyyyyyy
Additional Info:
>.
(Advanced hex data for customer service or engineering use.).
There was a fatal Internal
Error Log Continuation:
<
yyyyyyyy
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
There was a fatal F/W Error:
<
xx
><
yyyyyyyy
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
There was a fatal Firmware
Error 0xB<
xx
>.
Additional Info:
(Advanced hex data for customer service or engineering use.).
A fatal PCIe Interface Error:
Link Training Error.
Error
[0xB01 (2817)]
Error
[0xB01 (2817)]
Indicates an unexpected interrupt, exception, or error status internal to the policy processor or a related coprocessor.
Indicates the PCIe bus of the policy processor is not fully operational.
A fatal PCIe Interface Error:
Bad Link Width.
There was a fatal PCIe
Interface Error: Correctable
Error.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates the protocol processor was unable to negotiate for the proper link width resulting in degraded controller performance.
Error
[0xB01 (2817)]
Cannot clear PCIe correctable errors.
Action
No action necessary.
No action necessary
No action necessary.
No action necessary.
Replace the controller.
Replace the controller.
Replace the controller.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
189
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
There was a fatal PCIe
Interface Error: Presence
Mismatch.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates a connection problem between the two controllers.
Action
Replace the controller.
There was a fatal PCIe
Interface Error: Fault
Detected on Other (Partner)
Controller.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates a connection problem between the two controllers.
Error
[0xB01 (2817)]
Indicates a connection problem between the two controllers.
There was a fatal PCIe
Interface Error: No
Initialization Information from Other (Partner)
Controller.
Additional Info:
(Advanced hex data for customer service or engineering use.).
There was a fatal PCIe
Interface Error: Information
Mismatch on Other
(Partner) Controller.
Additional Info:
(Advanced hex data for customer service or engineering use.).
Error
[0xB01 (2817)]
Indicates a compatibility problem between the two controllers.
Replace the controller.
Replace the controller.
Replace the controller.
©2011 Harris Corporation. All rights reserved.
190
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The controller’s internal temperature <
aa
>C has exceeded the maximum limit. The controller will shutdown to prevent damage.
Error
[0xB03 (2819)]
Blocked fan.
Failing fan.
Elevated ambient temperature.
The Temperature Sensor
x
from Controller
y
reported a reading of
z
degrees Celsius and it has exceeded the maximum limit (
n
degrees
Celsius). The controller will shutdown to prevent damage.
Error
[0xB03 (2819)]
Blocked fan.
Failing fan.
Elevated ambient temperature.
The controller’s internal temperature <
aa
>C is approaching the maximum limit. You should check the cooling system for problems.
Warning
[0xB04 (2820)]
Blocked fan.
Failing fan.
Elevated ambient temperature.
Action
Check enclosure for sufficient air flow.
Check for a failed
Power Supply/Cooling module or Cooling
Fan module, if found replace module.
Check the ambient temperature of the environment, decrease the local ambient temperature.
Check enclosure for sufficient air flow.
Check for a failed
Power Supply/Cooling module or Cooling
Fan module, if found replace module.
Check the ambient temperature of the environment, decrease the local ambient temperature.
Check enclosure for sufficient air flow.
Check for a failed
Power Supply/Cooling module or Cooling
Fan module, if found replace module.
Check the ambient temperature of the environment, decrease the local ambient temperature.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
191
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The Temperature Sensor
x
from Controller
y
reported a reading of
z
degrees Celsius and is approaching the maximum limit (
n
degrees
Celsius). You should check the cooling system for problems.
Warning
[0xB04 (2820)]
Blocked fan.
Failing fan.
Elevated ambient temperature.
Action
Check enclosure for sufficient air flow.
Check for a failed
Power Supply/Cooling module or Cooling
Fan module, if found replace module.
Check the ambient temperature of the environment, decrease the local ambient temperature.
Replace battery in the controller or the RAID
Controller.
The onboard cache protection battery backup unit has failed, due to charger disabled, charge current not zero.
The onboard cache protection battery backup unit has failed or has been disconnected.
Error
[0xB07 (2823)]
Battery failure or charging failure.
Error
[0xB07 (2823)]
Battery failure or charging failure.
Replace battery in the controller, replace the
RAID Controller, or re-connect the battery.
Replace battery in the controller or the RAID
Controller.
The onboard cache protection battery backup unit has failed, due to voltage out of range.
The onboard cache protection battery backup unit has failed, due to fast charge under current.
The onboard cache protection battery backup unit has failed, due to trickle charge under current.
Error
[0xB07 (2823)]
Battery failure or charging failure.
Error
[0xB07 (2823)]
Battery failure or charging failure.
Error
[0xB07 (2823)]
Battery failure or charging failure.
Replace battery in the controller or the RAID
Controller.
Replace battery in the controller or the RAID
Controller.
©2011 Harris Corporation. All rights reserved.
192
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The onboard cache protection battery backup unit has failed, due to fast charge over current.
The onboard cache protection battery backup unit has failed, due to trickle charge over current.
Error
[0xB07 (2823)]
Battery failure or charging failure.
Error
[0xB07 (2823)]
Battery failure or charging failure.
The onboard cache protection battery backup unit has failed, due to failure in detecting full charge within the allotted time.
The onboard cache protection battery backup unit has failed, due to battery not present.
Error
[0xB07 (2823)]
Battery failure due to inability to completely charge.
Error
[0xB07 (2823)]
Battery removed or failed.
The onboard cache protection battery backup unit has failed or has been disconnected.
Error
[0xB07 (2823)]
Error
[0xB07 (2823)]
Battery failure or has been disconnected.
Failed to communicate to the monitoring system.
Action
Replace battery in the controller or the RAID
Controller.
Replace battery in the controller or the RAID
Controller.
Replace battery in the controller or the RAID
Controller.
Replace battery in the controller, replace the
RAID Controller, or re-connect the battery.
Replace battery in the controller, replace the
RAID Controller, or re-connect the battery.
Replace battery in the controller or the RAID
Controller.
The onboard cache protection battery backup unit has failed or has been disconnected, due to communication problem.
The onboard cache protection battery backup unit has failed or has been disconnected. The battery charger circuit is disabled.
Error
[0xB07 (2823)]
Battery was disconnected or failed.
Replace battery in the controller or re-connect the battery.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
193
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The onboard cache protection battery backup unit has failed or has been disconnected. The battery charger circuit is enabled.
The onboard cache protection battery backup unit has failed or has been disconnected. The battery charger circuit is disabled because the temperature is less than 5 degrees Celsius.
Error
[0xB07 (2823)]
Battery was disconnected or failed.
Error
[0xB07 (2823)]
Excessive cool or faulty battery.
Action
Replace battery in the controller or re-connect the battery.
Replace battery in the controller.
Error
[0xB07 (2823)]
Excessive hot or faulty battery.
Replace battery in the controller.
The onboard cache protection battery backup unit has failed or has been disconnected. The battery charger circuit is disabled because the temperature is greater than 70 degrees
Celsius.
The onboard cache protection battery backup unit has failed or has been disconnected. Hardware fault:
0x%.2X%.2X
.
The onboard cache protection battery backup unit has failed or has been disconnected. The battery charger is disabled.
Error
[0xB07 (2823)]
Error
[0xB07 (2823)]
Battery disconnected or failed.
Charger is disabled.
Replace battery in the controller.
Replace battery in the controller.
The onboard cache protection battery backup unit has started charging unexpectedly.
The onboard cache protection battery backup unit has been removed.
Error
[0xB07 (2823)]
Charging has started.
Information
[0xB07 (2823)]
Battery removed.
Replace battery in the controller.
Install a battery in the controller.
©2011 Harris Corporation. All rights reserved.
194
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The onboard cache protection battery backup unit has been inserted.
The partner controller has failed or has been removed.
Information
[0xB07 (2823)]
Battery installed.
Error
[0xB08 (2824)]
Failure or removal of one controller (partner) in an
Active-Active configuration.
The discovery process has started to determine all SAS devices on the SAS domain.
Information
[0xB23 (2851)]
A SAS discovery was initiated.
The other (partner) controller has been inserted.
Information
[0xB29 (2857)]
Partner controller has been inserted.
Action
No action necessary.
Re-install the controller.
or
Replace the controller.
Replace the controller.
This controller has not received a response from the other (partner) controller in the allotted time, and therefore it has been disabled.
Error
[0xB09 (2825)]
Failure or removal of one controller (partner) in an
Active-Active configuration.
The controller’s <
x
> voltage reading measures <
aa
>V which exceeds the limit.
Internal transfer error.
Controller mismatch detected. “This” or “The other” controller was shut down.
The discovery process has completed identifying all
SAS devices on the SAS domain.
Error
[0xB19 (2841)]
Voltage regulator hardware failure.
Enclosure 5V or 12V problem in the power supply.
Replace the controller.
Replace the defective
Power Supply or
Power Supply/Cooling module.
Replace the controller.
Error
[0xB1A
(2842)]
Error
[0xB1C
(2844)]
Hardware problem.
RAID Controllers with different
SAS controller chips have been installed. This is not a supported configuration.
Replace one of the controllers so that both controllers are of the same type.
Information
[0xB22 (2850)]
A SAS discovery was completed.
No action necessary.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
195
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The other (partner) controller has passed its self-test and is now ready
(failback).
The other controller has shut itself down, either because of a failure or user request.
Information
[0xB2A
(2858)]
Warning
[0xB2B (2859)]
Partner controller is ready to fail back.
A controller failure.
User request to shutdown.
A stripe synchronization of a RAID set has started. This occurs when a controller fails, or after a controller is powered off with write commands in progress.
A stripe synchronization of a RAID set has completed.
Information
[0xB2C
(2860)]
A controller fails or is powered off during a write operation.
The configuration has changed.
Action
No action necessary.
Replace Controller.
No action necessary.
No action necessary.
Information
[0xB2D
(2861)]
Information
[0xB2F (2863)]
A controller fails or is powered off during a RAID write operation.
A change in the configuration has occurred.
Information
[0xB35 (2869)]
Failure or removal of the partner controller.
No action necessary.
If you are using the
Save Configuration feature, re-save your configuration information - it no longer matches, otherwise no action is necessary.
No action necessary.
The controller is flushing the partner’s mirrored cache to the drives. There are <
xx
> cache entries totalling <
yy
> 512-byte blocks.
The controller has completed flushing the partner’s mirrored cache to the drives.
Information
[0xB36 (2870)]
Completion of mirrored cache flushing.
No action necessary.
©2011 Harris Corporation. All rights reserved.
196
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
Line Power Mode is now active, the battery is not required.
Information
[0xB42 (2882)]
Battery charging complete.
Special feature mode. Controller can be operated with battery removed and no LED status indication occurs.
Action
No action necessary.
The backup battery unit attached to this controller is now functioning correctly.
Information
[0xB42 (2882)]
Battery OK. Charged for <
x
> seconds.
The controller has been powered off.
The controller has been powered on.
Information
[0xB50 (2896)]
Information
[0xB51 (2897)]
Removal of controller or power.
The controller was powered on.
No action necessary.
No action necessary.
No action necessary.
The controller self-test was successfully completed.
The controller self-test has failed.
The controller’s NVRAM has been reset.
Information
[0xB52 (2898)]
Self-test completion on startup.
No action necessary.
Error
[0xB53 (2899)]
Self-test failure on startup.
Information
[0xB54 (2900)]
Occurs first time after production.
Replace the controller.
No action necessary.
The controller has an invalid
World Wide Name.
The Event Log has been cleared.
The controller has been reset.
Error
[0xB55 (2901)]
Information
[0xB56 (2902)]
Information
[0xB57 (2903)]
Occurs first time after production.
The user has cleared the event log.
User initiated a reset to the controller.
Contact technical support.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
197
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The controller has been shutdown gracefully.
Information
[0xB58 (2904)]
User initiated a controller shutdown.
The controller temperature threshold was exceeded and the controller shut itself down.
All identified enclosures have at least two communication paths to their SES devices.
Failover started.
Information
[0xB5B (2907)]
SES initialization.
Failure or removal of the partner controller.
Action
No action necessary.
Check for a failed
Cooling Fan or Power
Supply/Cooling module, replace as needed. Check for blocked air flow, correct as needed.
Check for high ambient temperature, reduce the environments ambient temperature.
No action necessary.
No action necessary.
Failover completed.
Information
[0xB5C
(2908)]
Information
[0xB5D
(2909)]
Completion of failover process.
No action necessary.
Failback started.
Failback completed.
Information
[0xB5E (2910)]
Information
[0xB5F (2911)]
Partner controller started failback.
No action necessary.
Completion of failback process.
No action necessary.
The controller firmware has been upgraded to version
<
xxxx
>.
Information
[0xB60 (2912)]
User upgraded the controller firmware.
No action necessary.
©2011 Harris Corporation. All rights reserved.
198
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The controller battery backup unit is charging.
Information
[0xB62 (2914)]
Battery charging started.
The controller battery backup unit has been charging for
x
minutes.
The controller battery backup unit has been charging for
x
minutes.
The battery backup unit is charging in forced trickle mode.
This is due to a missing or failed power supply.
The battery backup unit top-off cycle has begun.
Flushing of the battery protected cache has started.
There are <
xx
> cache entries totalling <
yy
>
512-byte blocks.
Information
[0xB63 (2915)]
Failure of power with writeback cache present.
Flushing of the battery protected cache has completed.
Information
[0xB64 (2916)]
Completion of cache flushing.
Action
No action necessary.
No action necessary.
No action necessary.
The cache data being preserved by the controller’s battery was lost. There were
<xx>
cache entries totalling
<yy>
512-byte blocks.
Error
[0xB65 (2917)]
Failure of power for an extended time with writeback cache present.
Check the file system.
The cached data was lost.
There were entries, totalling
<xx>
MBs.
The cached data was lost.
There were <
xx
> MBs lost in
Array <
yy
>.
<xx>
cache
The controller has been shudown either locally or remotely. The controller temperature was exceeded and the controller shut itself down.
Error
[0xB65 (2917)]
Failure of power for an extended time with writeback cache present.
Check the file system.
Error
[0xB65 (2917)]
Failure of power for an extended time with writeback cache present.
Check the file system.
Information
[0xB65 (2917)]
Internal hardware or firmware failure.
Replace the controller.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
199
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
An SDRAM ECC error - bit
<
xx
> at address
<
xx,xx,xx,xx
.
xx
> has been detected and corrected.
A configuration parameter has been changed: <
array name
> (Array <
number
>) has been trusted due to a cancellation of an initialization.
Hardware Error
Additional Info: (
Advanced hex data for customer service reps or engineer use.
).
Warning
[0xB72 (2930)]
SDRAM error.
Information
[0xB74 (2932)]
Error
[0xB7A
(2938)]
A user cancelled an initialization.
The controller will continue to function, however the SES temperature sensing may not function properly.
Action
If it repeats, replace the controller.
No action necessary.
Replace the controller.
Running <
version_number
>
CEMI firmware version:
Release <
num
>, Build
<
num
>.
Information
[0xB89 (2953)]
CEMI firmware is current.
No action necessary.
CEMI firmware upgrade from <
original CEMI FW version
>: Release <
num
>,
Build <
num
> to new version: Release <
num
>,
Build <
num
> failed because there is no response from the processor.
Error
[0xB89 (2953)]
Firmware failed to upgrade due to non-responding controller.
No action necessary.
©2011 Harris Corporation. All rights reserved.
200
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
“Automatic” or “Manual”
CEMI firmware upgrade from <
original CEMI FW version
>: Release <
num
>,
Build <
num
> to new version: Release <
num
>,
Build <
num
> <
completed successfully>, <i
s
underway
>, or <
failed
>.
“Automatic” or “Manual,” depending on whether the upgrade attempt was automatic or manual.
Error
[0xB89 (2953)]
Firmware is attempting to upgrade.
Information
[0xB8A
(2954)]
Embedded module reset was successful.
Occurs when there is a remote request to restart
Embedded module.
A remote request for a
Embedded module reset was successful.
Occurs when there is a remote request to restart
Embedded module.
A remote request for a
Embedded module reset failed.
Occurs when there is a remote request to restart
Embedded module.
A remote request for an
Embedded module reset was blocked, CEMI is updating.
Embedded module reset generated an unknown log entry.
Error
[0xB8A
(2954)]
Error
[0xB8A
(2954)]
Error
[0xB8A
(2954)]
Embedded module reset failed.
Embedded module reset was unsuccessful because the CEMI is being currently programmed.
Embedded module reset was unsuccessful because of unknown reasons.
Action
No action necessary.
No action necessary.
Try again, if no success replace RAID
Controller.
Retry sending the request for a reset.
Try again, if no success replace RAID
Controller.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
201
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
When the firmware queries the PMC firmware version, these events are logged:
PMC images are up to date.
CRC: <
16 digit hex CRC code
>.
PMC firmware image of type <
%s
> <
%s
>.
Where the first <
%s
> is one of: “bootrom” or
“initstring” or
“application” and the second <
%s
> is one of: “is up to date, current image’s
CRC:<
16 digit hex CRC code
>,” or “was updated successfully from old image
CRC: <
16 digit hex CRC code
> to new image CRC:
<
16 digit hex CRC code
>.”
Information
[0xB8B (2955)]
When the firmware queries the PMC firmware version, these events are logged:
PMC firmware image of type <
%s
> <
%s
>.
Where the first <
%s
> is one of: “bootrom” or
“initstring” or
“application” and the second <
%s
> is “failed to update from old image
CRC: <
16 digit hex CRC code
> to new image CRC:
<
16 digit hex CRC code
>.”
Error
[0xB8B (2955)]
Invalid SAS Disk I/O or EBOD
I/O module found in
Enclosure: <
xxx
>.
Error
[0xB90 (2960)]
An unsupported EBOD
I/O module was detected in the expansion enclosure.
Action
No action necessary.
No action necessary.
Replace the subject
EBOD I/O module with a correct supported module.
©2011 Harris Corporation. All rights reserved.
202
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
Drive power down/up maintenance is carried out on the drive (Slot <
x
>,
Enclosure <
y
>).
Drive maintenance is forcing the drive (Slot <
x
>,
Enclosure <
y
>) to fail.
Information
[0xB91 (2961)]
Drive maintenance.
Error
[0xB91 (2961)]
Drive failure unknown.
There is a mismatch of controller cache size causing the shutting down of this controller. This controller (version:
<This
Controller Version>
, cache size:
<This Controller Cache
Size>
) versus partner controller (version:
<Partner
Controller Version>
, cache size:
<Partner Controller
Cache Size>
).
Error
[0xB92 (2962)]
A mismatch was detected between Controller 0 and 1
SDRAM Memory module sizes.
Both SDRAM Memory modules in a dual controller
(Active-Active) configuration must be the same size.
Action
No action necessary.
Replace disk drive.
When this unsupported configuration occurs,
Controller 1 is always shutdown and
Controller 0 is always kept running, regardless of either controller's memory size.
With Controller 1 shutdown, remove and install the same size SDRAM Memory module as what is installed in Controller
0.
After the memory module is replaced, re-insert Controller 1.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
203
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
There is a mismatch of controller cache size causing the shutting down of the partner controller.
This controller (version:
<This Controller Version>
, cache size:
<This Controller
Cache Size>
) versus partner controller (version:
<Partner
Controller Version>
, cache size:
<Partner Controller
Cache Size>
).versus partner controller (
version: %.2X, cache size: %s
).
Error
[0xB92 (2962)]
A mismatch was detected between Controller 0 and 1
SDRAM Memory module sizes.
Both SDRAM Memory modules in a dual controller
(Active-Active) configuration must be the same size.
Action
When this unsupported configuration occurs,
Controller 1 is always shutdown and
Controller 0 is always kept running, regardless of either controller's memory size.
With Controller 1 shutdown, remove and install the same size SDRAM Memory module as what is installed in Controller
0.
After the memory module is replaced, re-insert Controller 1.
Obtain a new copy of the file.
The header of the expander
SPIMEM downloaded image is invalid.
Error
[0xB99 (2969)]
Corrupt file.
The expander SPIMEM was updated successfully.
The ID of the expander
SPIMEM download image does not match.
Information
[0xB99 (2969)]
Error
[0xB99 (2969)]
Firmware was updated successfully.
Corrupt file.
The CRC of the expander
SPIMEM download image does not match.
Failed to read from the expander EEPROM I2C.
Error
[0xB99 (2969)]
Failed to verify the expander
BOOTROM flash.
Error
[0xB9A
(2970)]
Corrupt file.
File failed to verify.
Error
[0xB9B (2971)]
Internal communication error.
No action necessary.
Obtain a new copy of the file.
Obtain a new copy of the file.
Replace the controller.
Replace the controller.
©2011 Harris Corporation. All rights reserved.
204
Appendix B
Troubleshooting
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
The expander EEPROM was updated successfully.
The controller watchdog interrupt warning was repeated <
xx
> times.
Recoverable instruction cache parity error detected.
Unable to delete any array while an array expansion background operation is in progress.
Information
[0xB9B (2971)]
Firmware was updated successfully.
Warning
[0xB9C
(2972)]
Warning
[0xB9C
(2972)]
Information
[0xB9E (2974)]
Internal errors are being reported.
Internal errors are being reported.
Indicates the user attempted to delete any array while an array expansion background operation is in progress.
Action
No action necessary.
Replace the controller.
Replace the controller.
Wait for the background process has completed and try the array deletion again.
Unable to delete any array while an array rebuild background operation is in progress.
Unable to delete any array while an array initialization background operation is in progress.
Information
[0xB9E (2974)]
Information
[0xB9E (2974)]
Indicates the user attempted to delete any array while an array rebuild background operation is in progress.
Indicates the user attempted to delete any array while an array initialization background operation is in progress.
Wait for the background process has completed and try the array deletion again.
Wait for the background process has completed and try the array deletion again.
Unable to delete any array while an array parity check background operation is in progress.
The data rate on Host Port
<
x
> has been limited to <
n
>
Gbps instead of the <
n
>
Gbps supported by the controller.
Information
[0xB9E (2974)]
Warning
[0xB9F] (2975)
Indicates the user attempted to delete any array while an array parity check background operation is in progress.
The SFP inserted in the host port does not support the data rate set for that port.
Wait for the background process has completed and try the array deletion again.
User should be aware with the current SFP the port is speed limited, otherwise replace with a higher speed SFP more compatible with the data rate set for the host port.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
205
Table B-1
Events and Configuration for the RAID Controller
(Continued)
Controller Events Messages Type [ID] Cause
This controller has temporarily paused its bootup process because its
NVRAM timestamp <
xxxx
> is different from the partner controller <
xxxx
>. The partner controller's state:
<value>.
Information
[0xBA0]
(2976)
Action
The controller initialization is on hold due to differences between this controller and the other controller's NVRAM timestamp.
No action necessary.
This controller continues its bootup process.
This controller's NVRAM timestamp is not valid.
The other controller's
NVRAM timestamp is valid.
SAN LUN Mapping trial period has expired.
Information
[0xBA1]
(2977)
Warning
[0xBA2]
(2978)
Information
[0xBA3]
(2979)
Information
[0xBA8]
(2984)
The controller has exited the state of paused initialization and is continuing the boot process.
No action necessary.
The other controller has a valid timestamp which will be used or the configuration is not valid.
No action necessary.
The other controller's NVRAM valid timestamp will be used and will be given control.
The SAN LUN Mapping licensed trial period or 15 day grace period has ended.
No action necessary.
Purchase a valid SAN
LUN Mapping license to reinstate functionality.
SAN LUN Mapping trial period expires in <
xx
> days.
Information
[0xBA8]
(2984)
This is a daily reminder that the
SAN LUN Mapping is in its licensed trial period or 15 day grace period and will expire in the specified number of days.
Contact technical support.
Purchase a valid SAN
LUN Mapping license to reinstate functionality.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
206
Appendix B
Troubleshooting
Persistent Reservation Events
These events are related to persistent reservation. The ID is given in the format of its hexadecimal value.
Persistent Reservation
Event Messages
Incorrect Reservation Key.
(Controller: <
num
>, Port
<
num
>, Logical Drive
<
num
>).
Incorrect Reservation Type.
(Controller: <
num
>, Port
<
num
>, Logical Drive
<
num
>).
I_T Nexus is not Reserved.
(Controller: <
num
>, Port
<
num
>, Logical Drive
<
num
>).
I_T Nexus is not Registered.
(Controller: <
num
>, Port
<
num
>, Logical Drive
<
num
>).
Reservation Conflict
Detected. (Controller:
<
num
>, Port <
num
>, Logical
Drive <
num
>).
Persistent Reservation Check
Condition Detected.
(Controller: <
num
>, Port
<
num
>, Logical Drive
<
num
>).
Invalid Service Action
Reservation Key.
(Controller: <
num
>, Port
<
num
>, Logical Drive
<
num
>).
Type [ID] Cause
Information
[0xB87 (2951)]
A Persistent
Reservation issue has occurred.
Information
[0xB87 (2951)]
A Persistent
Reservation issue has occurred.
Information
[0xB87 (2951)]
A Persistent
Reservation issue has occurred.
Information
[0xB87 (2951)]
A Persistent
Reservation issue has occurred.
Information
[0xB87 (2951)]
A Persistent
Reservation issue has occurred.
Information
[0xB87 (2951)]
A Persistent
Reservation issue has occurred.
Information
[0xB87 (2951)]
A Persistent
Reservation issue has occurred.
Action
No action necessary.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
207
SAS Interface Error Codes
The controller maintains a list of internal SAS Interface error codes. For these error codes the RAID Controller will automatically recover either by a reset or re initialization.
Error Code Message
There was an Inter-Controller Link Error.
There was an Inter-Controller Link Initialization Error.
There was a SAS Discovery Timeout.
There was a SAS Discovery Error.
There was a SAS Controller Reinitialization Error.
There was a SAS Interface Error
xxxxxxxx
*
SAS Discovery Error Codes
The controller maintains a list of internal SAS Discovery error codes. There is no action necessary with these error codes.
Error Code Message
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Max SATA Targets.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Multiple Paths.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Table to Table.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Multiple Subtractive.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: SMP CRC Error.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: SMP Function Failed.
©2011 Harris Corporation. All rights reserved.
208
Appendix B
Troubleshooting
Error Code Message
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Route Table Index Missing.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Expander Out of Entries.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: SMP Timeout.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Expander Error.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Ports With Same Address.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Unaddressable Device Found.
An error has been detected on port 0/1 of the SAS domain or with a SAS device during the discovery process: Loop Detected.
A single event may contain multiple errors, in those situations the error is appended to the base message separated by a semicolon.
Example:
An error has been detected on port 0 of the SAS domain or with a SAS device during the discovery process: Max SATA Targets; SMP Function Failed; Loop
Detected.
UID Events
The following table provides a brief description of the events that relate to the unified image download and system firmware updates. The ID is given in the format of its hexadecimal value.
The 0xBAE events will be handled a little differently than most of the other events, where two sets of conditional text inserts are provided along with the main text string. Refer to the two sub-tables for the conditional text and add them to the main text string to complete the event provided in the event log.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
209
Table B-2
UID Event Descriptions
UID Events Messages
UID image downloaded, Build
Number:
xxxxxxxxxxxxx
.
UID image downloaded, OEM
String:
xxxxxxxxxxxxx
UID Timestamp:
.
xxxxxx
.
UID Number of Included Images:
xxx
.
UID Checksum:
xxxxxx
.
UID Full Release Flag:
UID Utility Revision:
xx
.
xx.xx
.
The UID failsafe image downloaded, Version:
xxxxxxxxxxxxx
.
The UID failsafe image installed,
Version:
xxxxxxxxxxxxx
.
The UID failsafe image is invalid,
Version:
xxxxxxxxxxxxx
.
Type [ID]
Information
[0xBA5] (2981)
Information
[0xBA5] (2981)
Information
[0xBA5] (2981)
Information
[0xBA5] (2981)
Information
[0xBA5] (2981)
Information
[0xBA5] (2981)
Information
[0xBA5] (2981)
Information
[0xBA6] (2982)
Cause Action
User upgraded the firmware using a UID image or a controller migration happened with a UID image.
No action necessary.
User upgraded the firmware using a UID image or a controller migration happened with a UID image.
No action necessary.
User upgraded the controller firmware using a UID image or a controller migration happened with a UID image.
No action necessary.
UID image contains these numbers of images.
No action necessary.
UID image checksum is xxxxxx.
No action necessary.
Indicates version checking is enabled.
No action necessary.
UID image update utility version number.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
210
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID IOP boot image downloaded, Version:
xxxxxxxxxxxxx
.
The UID IOP boot image installed,
Version:
xxxxxxxxxxxxx
.
The UID IOP boot image is invalid,
Version:
xxxxxxxxxxxxx
.
The UID IOP primary image downloaded, Version:
xxxxxxxxxxxxx
.
The UID IOP primary image installed, Version:
xxxxxxxxxxxxx
.
The UID IOP primary image is invalid, Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot monitor failsafe image downloaded, Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot monitor failsafe image installed,
Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot monitor failsafe image is invalid,
Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot monitor primary image downloaded, Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot monitor primary image installed,
Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot monitor primary image is invalid,
Version:
xxxxxxxxxxxxx
.
Type [ID]
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
Action
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
211
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID embedded module’s boot configuration image downloaded,
Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot configuration image installed,
Version:
xxxxxxxxxxxxx
.
The UID embedded module’s boot configuration image is invalid,
Version:
xxxxxxxxxxxxx
.
Type [ID]
Information
[0xBA6] (2982)
The UID embedded module’s application configuration image downloaded, Version:
xxxxxxxxxxxxx
.
The UID embedded module’s application configuration image installed, Version:
xxxxxxxxxxxxx
.
The UID embedded module’s application configuration image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID embedded module’s application failsafe image downloaded, Version:
xxxxxxxxxxxxx
.
The UID embedded module’s application failsafe image installed,
Version:
xxxxxxxxxxxxx
.
The UID embedded module’s application failsafe image is invalid,
Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID embedded module’s application primary image downloaded, Version:
xxxxxxxxxxxxx
.
The UID embedded module’s application primary image installed,
Version:
xxxxxxxxxxxxx
.
The UID embedded module’s application primary image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
Action
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
212
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID GEM image downloaded,
Version:
xxxxxxxxxxxxx
.
The UID GEM image installed,
Version:
xxxxxxxxxxxxx
.
The UID GEM image is invalid,
Version:
xxxxxxxxxxxxx
.
Type [ID]
Information
[0xBA6] (2982)
The UID GEM bootloader image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM bootloader image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM bootloader image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID GEM Midplane VPD image for 4U/24 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane VPD image for 4U/24 installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane VPD image for 4U/24 is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID GEM Midplane VPD image for 2U/24 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane VPD image for 2U/24 installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane VPD image for 2U/24 is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
Action
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
213
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages Type [ID]
The UID GEM Midplane VPD image for 2U/12 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane VPD image for 2U/12 installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane VPD image for 2U/12 is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
The UID GEM Power Cooling
Module image for slot 1 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 1 installed,
Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 1 is invalid,
Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 2 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 2 installed,
Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 2 is invalid,
Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID GEM Power Cooling
Module image for slot 3 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 3 installed,
Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 3 is invalid,
Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
Action
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
214
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID GEM Power Cooling
Module image for slot 4 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 4 installed,
Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module image for slot 4 is invalid,
Version:
xxxxxxxxxxxxx
.
Type [ID]
Information
[0xBA6] (2982)
The UID GEM RAID Controller VPD image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM RAID Controller VPD image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM RAID Controller VPD image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID GEM RAID Controller configuration CRC image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM RAID Controller configuration CRC image installed,
Version:
xxxxxxxxxxxx
.
The UID GEM RAID Controller configuration CRC image is invalid,
Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID GEM Disk IO Module VPD image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Disk IO Module VPD image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Disk IO Module VPD image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
Action
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
215
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages Type [ID]
The UID GEM Disk IO Module configuration CRC image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Disk IO Module configuration CRC image installed,
Version:
xxxxxxxxxxxx
.
The UID GEM Disk IO Module configuration CRC image is invalid,
Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
The UID GEM Power Cooling
Module VPD image for slot 1 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 1 installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 1 is invalid, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 2 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 2 installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 2 is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
Action
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
216
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID GEM Power Cooling
Module VPD image for slot 3 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 3 installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 3 is invalid, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 4 downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 4 installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module VPD image for slot 4 is invalid, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane CPLD image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane CPLD image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Midplane CPLD image is invalid, Version:
xxxxxxxxxxxxx
.
Type [ID]
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
The UID GEM RAID Controller
CPLD image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM RAID Controller
CPLD image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM RAID Controller
CPLD image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
Action
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
217
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages Type [ID]
The UID GEM Disk IO Module CPLD image downloaded, Version: xxxxxxxxxxxxx.
The UID GEM Disk IO Module CPLD image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM Disk IO Module CPLD image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
Information
[0xBA6] (2982)
The UID GEM Power Cooling
Module CPLD image downloaded,
Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module CPLD image installed,
Version:
xxxxxxxxxxxxx
.
The UID GEM Power Cooling
Module CPLD image is invalid,
Version:
xxxxxxxxxxxxx
.
The UID GEM RebootAll image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM RebootAll image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM RebootAll image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID GEM RebootOne image downloaded, Version:
xxxxxxxxxxxxx
.
The UID GEM RebootOne image installed, Version:
xxxxxxxxxxxxx
.
The UID GEM RebootOne image is invalid, Version:
xxxxxxxxxxxxx
.
Information
[0xBA6] (2982)
The UID image is being sent to the other (partner) controller.
Information
[0xBA7] (2983)
The UID image is being received from the other (partner) controller.
Information
[0xBA7] (2983)
Cause
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
No action necessary.
No action necessary.
Contact technical support.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
The image was downloaded and the version is listed.
The image was installed and the version is listed.
The image is invalid.
UID image is being sent to the partner controller.
The UID image was received from the partner controller.
Action
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
218
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID image is being read from the other (partner) controller.
Type [ID]
Information
[0xBA7] (2983)
The UID image migration requested from the other (partner) controller.
Status: invalid image was detected.
Information
[0xBA7] (2983)
The UID image migration requested from the other (partner) controller.
Status: older timestamp was detected.
Information
[0xBA7] (2983)
The UID image migration requested from the other (partner) controller.
Status: non-UID image was detected.
Information
[0xBA7] (2983)
The UID image migration requested from the other (partner) controller.
Status: memory buffer allocation failure.
Information
[0xBA7] (2983)
The UID image migration requested from the other (partner) controller.
Status: non-specific failure.
Information
[0xBA7] (2983)
The UID image migration requested from the other (partner) controller.
Status:prior attempt had failed.
Information
[0xBA7] (2983)
The UID image migration requested from the other (partner) controller.
Status: other (partner) controller already running.
Information
[0xBA7] (2983)
The UID image migration failed.
Status: invalid image was detected.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID image migration failed.
Status: older timestamp was detected.
The UID image migration failed.
Status: non-UID image was detected.
Information
[0xBA7] (2983)
©2011 Harris Corporation. All rights reserved.
Cause
The UID image was read from the partner controller.
Two controllers have different versions.
Action
No action necessary.
Contact technical support.
Two controllers have different time stamps.
Contact technical support.
Anon-UID image was detected.
A memory buffer allocation failure occurred.
Unspecified failure.
Contact technical support.
Contact technical support.
Contact technical support.
Repeated attempts have failed.
Contact technical support.
Possibly due to a repeated attempt to update when it is already occurring.
Contact technical support.
Image is invalid.
Mismatch on time stamps.
Corrupt file detected.
Contact technical support.
Contact technical support.
Contact technical support.
NEXIO Farad
User Guide
219
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID image migration failed.
Status: memory buffer allocation failure.
The UID image migration failed.
Status: non-specific failure.
The UID image migration failed.
Status:prior attempt had failed.
Type [ID]
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID image migration failed.
Status: other (partner) controller already running.
The UID image migration was terminated. Status: invalid image was detected.
Information
[0xBA7] (2983)
The UID image migration was terminated. Status: older timestamp was detected.
Information
[0xBA7] (2983)
The UID image migration was terminated. Status: non-UID image was detected.
Information
[0xBA7] (2983)
The UID image migration was terminated. Status: memory buffer allocation failure.
Information
[0xBA7] (2983)
The UID image migration was terminated. Status: non-specific failure.
The UID image migration was terminated. Status:prior attempt had failed.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID image migration was terminated. Status: other (partner) controller already running.
There is no UID image in flash.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Cause
Buffer failure.
Non-specific failure.
Previous attempts or retries have failed.
Contact technical support.
Contact technical support.
Possibly due to a repeated attempt to update when it is already occurring.
Contact technical support.
Corrupt file.
Contact technical support.
Invalid time stamps.
Action
Contact technical support.
Corrupt file detected.
Contact technical support.
Contact technical support.
Buffer failure.
Non-specific failure.
Contact technical support.
Contact technical support.
Previous attempts have failed.
Contact technical support.
Possibly due to a repeated attempt to update when it is already occurring.
Contact technical support.
File header does not exist. Contact technical support.
©2011 Harris Corporation. All rights reserved.
220
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID update failed. Status: sending image to other (partner) controller failed.
Type [ID]
Information
[0xBA7] (2983)
The UID update failed. Status: could not send image to other
(partner) controller.
Information
[0xBA7] (2983)
The UID update failed. Status: GEM error detected.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update failed. Status: embedded module's application error detected.
The UID update failed. Status: signaling update failure to other
(partner) controller, Flash State:
xx
.
Information
[0xBA7] (2983)
The UID update failed. Status: Flash
State set to non-UID, Flash State:
xx
.
Information
[0xBA7] (2983)
The UID update failed. Status: embedded module's application global timeout.
The UID update failed. Status: embedded module's application image timeout.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update failed. Status: Flash
State set to unknown, Flash State:
xx
.
Information
[0xBA7] (2983)
The UID update failed. Status: download failed - update is in progress.
The UID update failed. Status: download failed - the global header size is incorrect.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update failed. Status: download failed - the build number preservation failed.
Information
[0xBA7] (2983)
Cause
Communication error.
Communication error.
Action
Contact technical support.
Contact technical support.
Failure detected in the
GEM code.
Application error was detected.
Contact technical support.
Contact technical support.
Communications error.
Contact technical support.
Updated corrupted.
Application time out occurred.
Contact technical support.
Contact technical support.
Application image time out occurred.
Contact technical support.
Unknown error.
Download failed.
Contact technical support.
Contact technical support.
File header is corrupt.
File header is corrupt.
Contact technical support.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
221
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID update failed. Status: download failed - the SES information is not available.
The UID update failed. Status: invalid controller configuration detected.
The UID update failed. Status: update from flash failed.
Type [ID]
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
[0xBA7] (2983)
The UID update failed. Status: update from flash failed - memory buffer allocation failed.
The UID update failed. Status: update from flash failed - the UID flash image is not valid.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update failed. Status: update from flash failed - the flash image is not idle.
Information
[0xBA7] (2983)
The UID update failed. Status: post-update verification failed,
Flash State:
xx
.
The UID update failed. Status: pending update invalidated, Flash
State:
xx
, UID State:
xx
.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update failed. Status: enclosure detection error, Error
Code:
xx
.
The UID update failed. Status: GEM counter error, Completions:
xx
,
Send Diagnostic Commands:
xx
.
Information
[0xBA7] (2983)
The UID update failed. Status: update unsuccessful, download failed.
The UID update general status: nothing done, no reboot required.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Cause Action
SES communication error. Contact technical support.
Hardware error.
Contact technical support.
Failed to update.
Buffer failure.
Image is not valid.
Update process busy.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Verification failed.
Update status failed.
Enclosure error.
Status error.
Status error.
Status condition.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
No action necessary.
©2011 Harris Corporation. All rights reserved.
222
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages Type [ID]
The UID update general status: an image was modified, controller will be reset.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update general status: no valid embedded module images detected.
The UID update general status: valid embedded module images detected:
xx
.
Information
[0xBA7] (2983)
The UID update general status: all
GEM updates completed without error.
The UID update general status: resending GEM image - Image:
xx
,
Enclosure:
xx
, Retry Count:
xx
.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update general status: begin update of UID components from flash.
Information
[0xBA7] (2983)
The UID update general status: retrying update of UID components from flash.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update general status: post update validation - IOP firmware revisions match.
The UID update general status: post update validation - IOP firmware revisions differ.
Information
[0xBA7] (2983)
The UID update general status: post update validation - IOP boot revisions match.
The UID update general status: post update validation - IOP boot revisions differ.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID update general status: UID being restarted.
Information
[0xBA7] (2983)
Cause
Status condition.
Status condition.
Status condition.
Action
No action necessary.
No action necessary.
No action necessary.
Status condition.
Status condition.
Status condition.
Status condition. Update always attempt three retries before failure.
Status condition.
No action necessary.
No action necessary.
Status condition.
No action necessary.
Status condition.
No action necessary.
No action necessary.
Status condition.
Status condition.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
223
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID update general status: sending extended information to other (partner) controller.
Type [ID]
Information
[0xBA7] (2983)
The UID update general status: received extended information from other (partner) controller.
The UID flash access status: UID header - flash erase failed.
The UID flash access status: UID header - invalid erase status.
The UID flash access status: UID header - programming failed.
The UID flash access status: UID sector - erase failed.
The UID flash access status: UID sector - invalid erase status.
The UID flash access status: UID sector - programming failed.
The UID flash access status: UID copied from flash to RAM.
The UID flash access status: UID header erase failed.
The UID flash access status: UID
OEM string - erase failed.
The UID flash access status: UID
OEM string - programming failed.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID validation status: enclosure information check - retrying GEM,
Retry Count:
xx
.
Information
[0xBA7] (2983)
The UID validation status: enclosure information check - GEM information not available.
Information
[0xBA7] (2983)
Cause
Status condition.
Status condition.
Status condition.
Hardware condition.
Hardware condition.
Hardware condition.
Hardware condition.
Hardware condition.
Hardware condition.
Hardware condition.
Hardware condition.
Hardware condition.
Hardware condition.
Status condition.
Action
No action necessary.
No action necessary.
Replace controller.
Replace controller.
Replace controller.
Replace controller.
Replace controller.
Replace controller.
Replace controller.
Replace controller.
Replace controller.
Replace controller.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
224
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages Type [ID]
The UID validation status: enclosure information check - retrying embedded module's application,
Retry Count:
xx
.
Information
[0xBA7] (2983)
The UID validation status: enclosure information check - embedded module's application information not available.
Information
[0xBA7] (2983)
The UID validation status: invalid controller name.
The UID validation status: single image checksum error.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID validation status: post update validation - disabled.
The UID validation status: post update validation - delayed.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID validation status: post update validation - revision mismatch detected, updates required.
The UID validation status: post update validation - success.
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
The UID validation status: enclosure information check - retrying
COMPONENT, Retry Count:
xx
.
Information
[0xBA7] (2983)
The UID validation status: enclosure information check - COMPONENT information not available.
Information
[0xBA7] (2983)
The UID state status: UID State:
xx
.
Information
[0xBA7] (2983)
The UID state status: UID Flash
State:
xx
.
Information
[0xBA7] (2983)
The UID reset status: GEM reset error.
Information
[0xBA7] (2983)
Cause
Status condition.
Status condition.
Status condition.
Status condition.
Status error.
Status error.
Status error.
Status error.
Status error.
Status error.
Status error.
Status error.
Status error.
©2011 Harris Corporation. All rights reserved.
Action
No action necessary.
No action necessary.
No action necessary.
No action necessary.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
NEXIO Farad
User Guide
225
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID reset status: all GEM
RebootAll images sent.
The UID reset status: all GEM
RebootOne images sent.
The UID reset status: all GEM
RebootAll images sent. Resetting all controllers.
The UID reset status: all GEM
RebootOne images sent. Resetting controller.
The UID reset status: reset error -
GEM reboot timeout, resetting controller.
The UID reset status: reset error -
GEM reboot timeout, resetting all controllers.
The UID reset status: reset error -
GEM RebootAll, Enclosure:
xx
.
The UID reset status: reset error -
GEM RebootOne, Enclosure:
xx
.
Failed to flash the UID IOP boot image.
Failed to flash the UID IOP primary image.
Failed to flash the UID embedded module’s boot monitor failsafe image.
Failed to flash the UID embedded module’s boot monitor primary image.
Failed to flash the UID embedded module’s boot configuration image.
Type [ID]
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA7] (2983)
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
Cause
Status error.
Status error.
Status condition.
Status condition.
Status condition.
Status condition.
Status condition.
Status condition.
Flash errors.
Flash errors.
Flash errors.
Flash errors.
Flash errors.
©2011 Harris Corporation. All rights reserved.
Action
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
226
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages Type [ID]
Failed to flash the UID embedded module’s application configuration image.
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
Failed to flash the UID embedded module’s application failsafe image.
Failed to flash the UID embedded module’s application primary image.
Information
[0xBA9] (2985)
Failed to flash the UID GEM image. Information
[0xBA9] (2985)
Failed to flash the UID GEM RAID
Controller VPD image.
Information
[0xBA9] (2985)
Failed to flash the UID GEM Disk IO
Module VPD image.
Information
[0xBA9] (2985)
The UID IOP boot image was flashed successfully.
The UID IOP primary image was flashed successfully.
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
The UID embedded module’s boot monitor failsafe image was flashed successfully.
Information
[0xBA9] (2985)
The UID embedded module’s boot monitor primary image was flashed successfully.
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
The UID embedded module’s boot configuration image was flashed successfully.
The UID embedded module’s application configuration image was flashed successfully.
Information
[0xBA9] (2985)
The UID embedded module’s application failsafe image was flashed successfully.
Information
[0xBA9] (2985)
Cause
Flash errors.
Flash errors.
Flash errors.
Flash errors.
Flash errors.
Flash errors.
Normal operation.
Normal operation.
Normal operation.
Normal operation.
Normal operation.
Normal operation.
Normal operation.
©2011 Harris Corporation. All rights reserved.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
Action
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
No action necessary.
No action necessary.
No action necessary.
NEXIO Farad
User Guide
227
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
The UID embedded module’s application primary image was flashed successfully.
The UID GEM image was flashed successfully.
Type [ID]
Information
[0xBA9] (2985)
Information
[0xBA9] (2985)
The UID GEM RAID Controller VPD image was flashed successfully.
Information
[0xBA9] (2985)
The UID GEM Disk IO Module VPD image was flashed successfully.
These validation types are to be used for all 0xBAE events.
Information
[0xBA9] (2985)
Information
[0xBAE] (2990)
Where <
ValidationType
> is 1 of the following:
01 = expected revision
02 = POST update
03 = OEM string
04 = build number
05 = checksum
06 = overall expected revision
07 = overall POST update
08 = download to target status
Cause
Normal operation.
Normal operation.
Normal operation.
Normal operation.
Validation types.
Action
No action necessary.
No action necessary.
No action necessary.
No action necessary.
Used to replace each condition of
<ValidationType> in the following
0xBAE events.
©2011 Harris Corporation. All rights reserved.
228
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
These UID Imagetypes are to be used for all 0xBAE events.
Type [ID]
Information
[0xBAE] (2990)
Where <
UID_ImageType
> is 1 of the following:
00 = UID failsafe image
01 = UID IOP boot image
02 = UID IOP primary image
03 = UID embedded module’s boot monitor failsafe image
04 = UID embedded module’s boot monitor primary image
05 = UID embedded module’s boot configuration image
06 = UID embedded module’s application configuration image
07 = UID embedded module’s application failsafe image
08 = UID embedded module’s application primary image
09 = UID GEM image
0A = UID GEM bootloader image
0B = UID GEM Midplane VPD image for 4U/24
0C = UID GEM Midplane VPD image for 2U/24
0D = UID GEM Midplane VPD image for 2U/12
0E = UID GEM Power Cooling
Module image for slot 1
0F = UID GEM Power Cooling
Module image for slot 2
10 = UID GEM Power Cooling
Module image for slot 3
11 = UID GEM Power Cooling
Module image for slot 4
12 = UID GEM RAID Controller VPD image
Cause
Image types.
©2011 Harris Corporation. All rights reserved.
Action
Used to replace each condition of
<UID_ImageType> in the following
0xBAE events.
NEXIO Farad
User Guide
229
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
These UID Imagetypes are to be used for all 0xBAE events.
(continued)
Type [ID]
Information
[0xBAE] (2990)
Where <
UID_ImageType
> is 1 of the following:
13 = UID GEM RAID Controller configuration CRC image
14 = UID GEM Disk IO Module VPD image
15 = UID GEM Disk IO Module configuration CRC image
16 = UID GEM Power Cooling
Module VPD image for slot 1
17 = UID GEM Power Cooling
Module VPD image for slot 2
18 = UID GEM Power Cooling
Module VPD image for slot 3
19 = UID GEM Power Cooling
Module VPD image for slot 4
1A = UID GEM Midplane CPLD image
1B = UID GEM RAID Controller
CPLD image
1C = UID GEM Disk IO Module
CPLD image
1D = UID GEM Power Cooling
Module CPLD image
1E = UID GEM RebootAll image
1F = UID GEM RebootOne image
Validation type: <
ValidationType
>.
Successful in validating the
<
UID_ImageType
> on Enclosure
xx
.
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
Failed to validate the
<
UID_ImageType
> on Enclosure
xx
.
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
The <
UID_ImageType
> is accepted on Enclosure
xx
.
Information
[0xBAE] (2990)
Cause
Image types.
Normal operation.
Status error.
Normal operation.
Action
Used to replace each condition of
<UID_ImageType> in the following
0xBAE events.
No action necessary.
Contact technical support.
No action necessary.
©2011 Harris Corporation. All rights reserved.
230
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
Validation type: <
ValidationType
>.
The controller is not ready to validate the <
UID_ImageType
> on
Enclosure
xx
.
Type [ID]
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Status detection is not implemented for this element.
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Element is installed and no error conditions are known.
Information
[0xBAE] (2990)
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Critical condition is detected.
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Noncritical condition is detected.
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Unrecoverable condition is detected.
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Element is not installed in the enclosure.
Information
[0xBAE] (2990)
Information
[0xBAE] (2990)
Cause
Normal operation.
Normal operation.
Normal operation.
Error is detected.
Normal operation.
Status error.
Status error.
Action
No action necessary.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
Contact technical support.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
NEXIO Farad
User Guide
231
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Sensor has failed or element status is not available.
Type [ID]
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. Element installed, no known errors, but the element has not been turned on or set into operation.
Information
[0xBAE] (2990)
Information
[0xBAE] (2990)
Validation type: <
ValidationType
>.
The target is not installed to validate the <
UID_ImageType
> on
Enclosure
xx
. No status available because the initiator port from which the RECEIVE DIAGNOSTIC
RESULT command was received does not have access to this element.
Validation type: <
ValidationType
>.
The UID download of the<
UID_ImageType
> s on
Enclosure
xx
is not supported.
Information
[0xBAE] (2990)
Validation type: expected revision.
Expected Version:
xxxxxxxxxxxxx
.
Validation type: POST update.
Expected Version:
xxxxxxxxxxxxx
.
Validation type: OEM string.
Expected Version:
xxxxxxxxxxxxx
.
Validation type: build number.
Expected Version:
xxxxxxxxxxxxx
.
Validation type: checksum.
Expected Version:
xxxxxxxxxxxxx
.
Information
[0xBAF] (2991)
Information
[0xBAF] (2991)
Information
[0xBAF] (2991)
Information
[0xBAF] (2991)
Information
[0xBAF] (2991)
Cause
Status error.
Normal operation.
Status error.
Status error.
Status error.
Status error.
Status error.
Status error.
Status error.
Action
Contact technical support.
No action necessary.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
Contact technical support.
©2011 Harris Corporation. All rights reserved.
232
Appendix B
Troubleshooting
Table B-2
UID Event Descriptions
(Continued)
UID Events Messages
Validation type: overall expected revision. Expected Version:
xxxxxxxxxxxxx
.
Validation type: overall POST update. Expected Version:
xxxxxxxxxxxxx
.
Validation type: download to target status. Expected Version:
xxxxxxxxxxxxx
.
Type [ID]
Information
[0xBAF] (2991)
Information
[0xBAF] (2991)
Information
[0xBAF] (2991)
Validation type: expected revision.
Actual Version:
xxxxxxxxxxxxx
.
Validation type: POST update.
Actual Version:
xxxxxxxxxxxxx
.
Information
[0xBB0] (2992)
Information
[0xBB0] (2992)
Validation type: OEM string. Actual
Version:
xxxxxxxxxxxxx
.
Information
[0xBB0] (2992)
Validation type: build number.
Actual Version:
Validation type: checksum. Actual
Version:
xxxxxxxxxxxxx xxxxxxxxxxxxx
.
Validation type: download to target status. Actual Version:
xxxxxxxxxxxxx
.
.
Validation type: overall expected revision. Actual Version:
xxxxxxxxxxxxx
.
Validation type: overall POST update. Actual Version:
xxxxxxxxxxxxx
.
Information
[0xBB0] (2992)
Information
[0xBB0] (2992)
Information
[0xBB0] (2992)
Information
[0xBB0] (2992)
Information
[0xBB0] (2992)
Cause
Status error.
Status error.
Status error.
Normal operation.
Normal operation.
Normal operation.
Normal operation.
Normal operation.
Status error.
Normal operation.
Normal operation.
Action
Contact technical support.
Contact technical support.
Contact technical support.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
No action necessary.
Contact technical support.
No action necessary.
No action necessary.
©2011 Harris Corporation. All rights reserved.
C
Inter-Stack
Communication Method
233
StorView’s server component uses multicasting technology to provide inter-stack communication. During the server’s initial start-up, it performs a multicast registration using the default multicast IP address of 225.0.0.225 on port 9191.
Once registration is complete, the server is able to receive all packets sent to the multicast address.
All packets sent to the multicast address will remain in the local network unless an explicit server IP address outside the subnet is added in the
Individually Monitored
Servers
field in the
Monitoring Settings
section of the Preferences tab located in the
Settings window. The inter-stack communication abilities provide each StorView
GUI with remote monitoring of other stacks.
These other stacks are displayed on the Main screen and are listed under the “Other
Servers” section. They display the IP address, name, and an overall status of both controllers in that stack. Status of the remote stacks is indicated by the color of the
Server Sidebar and Top Section — Descriptions and
Each stack 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 stacks. 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
©2011 Harris Corporation. All rights reserved.
234
Appendix
Figure C-1
Other Servers Section
©2011 Harris Corporation. All rights reserved.
Glossary
A
Array
C
Chunk Size
A group of disk drives that are combined together to create a single large storage area. Up to 64 arrays are supported, each containing up to 16 drives per array. There is no capacity limit for the arrays.
B
Back-off Percent In order to allow drives from a different family or manufacturer to be used as a replacement for a drive in an array, it is recommended that a small percentage of the drive’s capacity be reserved when creating the array. This is user selectable, from
0, 0.1, 1-10, and 90 percent. This is sometimes known as Reserved Capacity.
This is the amount of data that is written on a single drive before the controller moves to the next drive in the stripe.
235
©2011 Harris Corporation. All rights reserved.
236
Glossary
I
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.
L
Logical Drive
Availability
R
RAID Level 0
To accommodate hosts with multiple ports and multiple host systems, it is possible to restrict a logical drive’s availability to a particular HBA or controller port. Access can be enabled or disabled for each host port of each controller.
M
Mapped LUN
Number
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 0 is defined as disk striping where data is striped or spread across one or more drives in parallel. RAID 0 is ideal for environments in which performance (read and write) is more important than fault tolerance or you need the maximum amount of available drive capacity in one volume. Drive parallelism increases throughput because all disks in the stripe set work together on every I/O operation. For greatest efficiency, all drives in the stripe set must be the same capacity. Because all drives are used in every operation, RAID 0 allows for single-threaded I/O only (i.e., one I/O operation at a time). Environments with many small simultaneous transactions
(e.g., order entry systems) will not get the best possible throughput.
©2011 Harris Corporation. All rights reserved.
RAID Level 1
RAID Level 5
RAID Level 6
RAID Level 10
RAID Level 50
NEXIO Farad
User Guide
237
RAID 1 is defined as disk mirroring where one drive is an exact copy of the other.
RAID 1 is useful for building a fault-tolerant system or data volume, providing excellent availability without sacrificing performance. However, you lose 50 percent of the assigned disk capacity. Read performance is somewhat higher than write performance.
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 6 is the same as RAID 5 except that it uses a second level of independently calculated and distributed parity information for additional fault tolerance. This extra fault tolerance provides data security in the event two drives fail before a drive can be replaced. RAID 6 provides greater fault tolerance than RAID 5. There is a loss in write performance with RAID 6 when compared to RAID 5 due to the requirement for storing parity twice for each write operation. A RAID 6 configuration also requires N+2 drives to accommodate the additional parity data, which makes RAID 6 require more raw capacity than RAID 5 for an equivalent usable storage capacity.
RAID 10 is defined as mirrored stripe set.
This RAID level is a combination of RAID level 5 and RAID level 0. Individual smaller
RAID 5 arrays are striped, to give a single RAID 50 array. This can increase the performance by allowing the controller to more efficiently cluster commands together. Fault tolerance is also increased, as one drive can fail in each individual array.
S
Stripe
Stripe Size
Sub-array
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.
This is the number of data drives multiplied by the chunk size.
In RAID 50 applications, this is the name given when individual RAID 5 arrays that are striped together. Each sub-array has one parity drive.
©2011 Harris Corporation. All rights reserved.
238
Glossary
U
Unassigned Free
Space
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.
©2011 Harris Corporation. All rights reserved.
Index
A
access alignment 147 access size 147
Advanced Logical Drive Functions 123
Advanced Power Management (APM) 62
Array Power Management (APM Level 2) 108
arrays
B
Battery Not Charging
C
configuration
Controller Event
Controller Failback Completed 197
Controller Failback Started 197
Controller Failover Completed 197
Controller Failover Started 197
Controller Firmware Upgraded 197
Controller Selftest Failed 196
Controller Selftest Passed 196
Flush Mirrored Cache Started 195
controller logs
D
239
240
Index disk arrays
disk drive
Drive Event
Array Initialization Complete 171
Array Initialization Started 171
Drive Loop 1 is not initalizing 169
drive members
E
F
Failure Prediction Threshold Exceeded
G
H
Host Event
Host Port Incorrect Address 176
I
L
Logical Disk
M
monitor
monitoring
N
network settings
O
Operations
P
parity
password
R
Read-Ahead Command Efficiency 142
Read-Ahead Command Hit Rate 142
S
SAN LUN Mapping trial period 205
Sequential Command Interval 142
SES Event
,
settings
SNMP
StorView
T
U
Updating the Firmware (UID) 75
V
W
Writeback Cache Disabled
NEXIO Farad
User Guide
241
Pobierz
Publiczny link zaktualizowany
Publiczny link do Twojego czatu został zaktualizowany. You may view and manage your chat links after registration here.
Publiczny link do dokumentu
Reklama
