10400166 102

Transcript

Overland Storage ULTAMUS® RAID 1200 ULTAMUS RAID manager User Guide September 2008 10400166-102 ULTAMUS RAID 1200 User Guide OVERLAND STORAGE END USER LICENSE AGREEMENT (“EULA”) IMPORTANT NOTICE - PLEASE READ THIS END USER SOFTWARE LICENSE AGREEMENT (“EULA”) CAREFULLY BEFORE USING THE SOFTWARE CONTAINED IN THIS EQUIPMENT OR USING THIS EQUIPMENT IN ANY MANNER. BY USING THE EQUIPMENT THAT CONTAINS THIS SOFTWARE, YOU ARE CONSENTING TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS END USER AGREEMENT, PROMPTLY RETURN AND DO NOT USE THE EQUIPMENT AND THE SOFTWARE. 1. Single User License. Subject to the terms and conditions of this EULA, Overland Storage, Inc. (“Overland”) grants to you (“Customer”) a nonexclusive, non-transferable license to use (a) Overland software which provides the basic operating environment for Overland equipment and whether pre-installed on, embedded in or provided with Overland equipment, and (b) the specific Overland program modules or features which have been enabled by security keys supplied by Overland and for which Customer had paid any applicable license fees (collectively, the “Software”), both of the foregoing in object code form only: (i) solely as pre-installed, embedded in or provided with Overland equipment owned or leased by Customer; and (ii) for key-enabled Software corresponding to the security key(s) supplied by Overland and for the license fees paid by Customer. 2. Limitations. Except as otherwise expressly provided under this EULA, Customer will have no right, and Customer will not: (i) make error corrections to or otherwise modify or adapt the Software nor create derivative works based upon the Software, or to permit third parties to do the same; (ii) copy, in whole or in part, decompile, translate, reverse engineer, disassemble or otherwise reduce the Software to human-readable form; or (iii) remove the Software from the equipment in which it is embedded. 3. Upgrades and Additional Copies. For purposes of this EULA, “Software” will also include (and the terms and conditions of this EULA will apply to) any upgrades, updates, bug fixes or modified versions (collectively, “Upgrades”) or backup copies of the Software licensed or provided to Customer by Overland or an authorized distributor for which Customer had paid the applicable license fees and holds the corresponding software keys. Notwithstanding the foregoing, Overland will have no obligation to provide any Upgrades under this EULA. If Upgrades are provided, (i) Customer has no license or right to use any such additional copies or Upgrades unless Customer, at the time of acquiring such copy or Upgrade, already holds a valid license and the corresponding security keys to the original Software; and (ii) use of the Upgrades is limited to Overland equipment for which Customer is the original End-User purchase or lessee. 4. U.S. Government Restriction Rights. The Software was developed at private expense and is provided with “RESTRICTED RIGHTS” as set forth in this License Agreement. Use, duplication or disclosure by the United States government is subject to restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq., or its successors. The use of this Software constitutes acknowledgement of Company’s and its licensors’ rights in the Software. 5. Notices of Proprietary Rights. Customer will maintain and reproduce all trademark, copyright, patent, and notices of other proprietary rights on all copies, in any form, of the Software in the same form and manner that such trademark, copyright, patent, and notices of other rights are included on the Software. Except as expressly authorized in this EULA, Customer will not make any copies or duplicates of any Software without the prior written permission of Overland. 6. Proprietary Rights. The Software is and will remain the sole and exclusive property of Overland. Software is licensed, not sold, by Overland hereunder. Any references to terms in connection with the foregoing, such as “sale”, “purchase” or “sell” will be interpreted as licensed rights granted on a non-exclusive basis hereunder and as otherwise provided in this EULA. Overland’s rights under this Section will include, but not be limited to: (i) all copies of the Software, in whole and in part; and (ii) all intellectual property rights in the Software. 7. Confidential Information. Customer will not disclose or, except as expressly permitted in this EULA, use any Software or other technical information disclosed to Customer by Overland (“Confidential Information”). Customer will take all reasonable measures to maintain the confidentiality of all Confidential Information in Customer’s possession or control, which will in no event be less than the measures Customer uses to maintain the confidentiality of Customer’s own information of equal importance. Confidential Information will not include information that: (i) is in or enters the public domain without breach of this EULA; (ii) Customer receives from a third party without restriction on disclosure and without breach of a nondisclosure obligation; or (iii) Customer develops independently, which Customer can prove with written evidence. The Confidential Information is a trade secret of Overland, the disclosure of which would cause substantial harm to Overland that could not be remedied by the payment of damages alone. Accordingly, Overland will be entitled to preliminary and permanent injunctive relief and other equitable relief for any breach of this Section. 8. Limited Software Warranty. Overland warrants that the Software will substantially conform to its published specifications for a period of 90 days from the later of receipt of the equipment containing the Software or receipt of access to the Software. This limited warranty extends only to Customer as the original licensee. Provided that (a) Customer has notified Overland of such substantial non-conformance during the applicable warranty period, and (b) Overland has confirmed such Software to be substantially non-conforming, as Customer’s sole and exclusive remedy and Overland’s and its suppliers’ entire liability under this limited warranty, Overland will, at its option, repair, replace, or refund the Software pursuant to Overland’s then-current warranty policy. Except as expressly provided in this EULA, the Software is provided “AS IS” without warranty of any kind. Overland does not warrant that the Software is error free or that Customer will be able to operate the Software without problems or interruptions. Overland reserves the right to charge additional fees for repairs or replacements performed outside of the 90-day limited warranty period. This warranty does not apply if the Software or the Overland equipment in which the Software is embedded (i) is licensed for beta, evaluation, testing or demonstration purposes for which Overland does not receive a license fee, (ii) has been altered, except by Overland, (iii) has not been installed, operated, repaired, or maintained in accordance with instructions supplied by Overland, (iv) has been subjected to abnormal physical or electrical stress or to misuse, negligence, or accident, or (v) is used in ultra-hazardous activities. 9. Disclaimer. EXCEPT AS SPECIFIED IN THIS EULA, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, SATISFACTORY QUALITY OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW. IN NO EVENT WILL OVERLAND OR ITS SUPPLIERS BE LIABLE FOR ANY LOST REVENUE, PROFIT, OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR PUNITIVE DAMAGES HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE EVEN IF OVERLAND OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL OVERLAND’S TOTAL LIABILITY TO CUSTOMER, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, EXCEED THE PRICE PAID BY CUSTOMER. THE FOREGOING LIMITATIONS WILL APPLY EVEN IF THE ABOVE-STATED WARRANTY FAILS OF ITS ESSENTIAL PURPOSE. Each party recognizes and agrees that the warranty disclaimers and liability and remedy limitations in this EULA are material bargained for bases of this EULA and that they have been taken into account and reflected in determining the consideration to be given by each party under this EULA and in the decision by each party to enter into this EULA. 10. Term and Termination. This EULA is effective until terminated. Customer’s license rights under this EULA will terminate immediately without notice from Overland if Customer fails to comply with any provision of this EULA. Upon termination, Customer must destroy all copies of Software and the corresponding security keys in its possession or control. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W ii ULTAMUS RAID 1200 User Guide 11. Compliance With Law. Each party will comply with all applicable laws, rules and regulations in connection with its activities under this EULA. Without limiting the foregoing, the Software, including technical data, is subject to United States export control laws, including the United States Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Customer will comply strictly with all such regulations and acknowledges that Customer has the responsibility to obtain licenses to export, re-export, or import the Software. 12. Restricted Rights. The Software will be classified as “commercial computer software” as defined in the applicable provisions of the Federal Acquisition Regulation (the “FAR”) and supplements thereto, including the Department of Defense (DoD) FAR Supplement (the “DFARS”). The parties acknowledge that the Software was developed entirely at private expense and that no part of the Software was first produced in the performance of a Government contract. If the Software is supplied for use by DoD, the Software is delivered subject to the terms of this EULA and either (i) in accordance with DFARS 227.702-1(a) and 227.7202-3(a), or (ii) with restricted rights in accordance with DFARS 252.227-7013(c)(1)(ii) (OCT 1988), as applicable. If the Software is supplied for use by a Federal agency other than DoD, the Software is restricted computer software delivered subject to the terms of this EULA and (i) FAR 12.212(a); (ii) FAR 52.227-19; or (iii) FAR 52.227-14 (ALT III), as applicable. 13. Third Party Software. Third party suppliers of materials integrated with the Overland equipment disclaim all implied warranties, including the implied warranties of merchantability and fitness for a particular purpose. The collective liabilities of the seller/licensor and its third party suppliers are subject to the limitation of liabilities described in this agreement. The third party supplier is an intended beneficiary of this limitation.” Third party suppliers disclaim all liability for consequential or other indirect damages or for loss of or damage to data or records. 14. General. This EULA will bind and inure to the benefit of each party’s successors and assigns, provided that Customer may not assign or transfer this EULA, in whole or in part, without Overland’s written consent. This EULA will be governed by and construed in accordance with the laws of the State of California, United States of America, as if performed wholly within the state and without giving effect to the principles of conflict of law. No failure of either party to exercise or enforce any of its rights under this EULA will act as a waiver of such rights. Any waivers or amendments will be effective only if made in writing by non-preprinted agreements clearly understood by both parties to be an amendment or waiver and signed by a representative of the respective parties authorized to bind the parties. If any portion hereof is found to be void or unenforceable, the remaining provisions of this EULA will remain in full force and effect. This EULA is the complete and exclusive agreement between the parties with respect to the subject matter hereof, superseding and replacing any and all prior agreements, communications, and understandings (both written and oral) regarding such subject matter. Any notice, report, approval or consent required or permitted hereunder will be in writing and will be deemed to have been duly given if delivered personally or mailed by first-class, registered or certified US mail, postage prepaid to the respective addresses of the parties. The prevailing party in any action to enforce this EULA will be entitled to recover costs and expenses including, without limitation, reasonable attorneys’ fees. A material breach of this EULA adversely affecting Overland’s proprietary rights in the Software would cause irreparable injury to Overland for which monetary damages would not be an adequate remedy and that Overland will be entitled to equitable relief in addition to any remedies it may have hereunder or at law. ©2007, 2008 Overland Storage, Inc. All rights reserved. Overland®, Overland Storage®, LoaderXpress®, Multi-SitePAC®, NEO SERIES®, PowerLoader®, Protection OS®, REO®, REO SERIES®, ULTAMUS®, VR2®, WebTLC®, and XchangeNOW® are registered trademarks of Overland Storage, Inc. ARCvault™, NEO™, Simply Protected™, Simply Protected Storage™, SnapWrite™, and ULTAMUS SERIES™ are trademarks of Overland Storage, Inc. All other brand names or trademarks are the property of their respective owners. The names of companies and individuals used in examples are fictitious and intended to illustrate the use of the software. Any resemblance to actual companies or individuals, whether past or present, is coincidental. PROPRIETARY NOTICE All information contained in or disclosed by this document is considered proprietary by Overland Storage. By accepting this material the recipient agrees that this material and the information contained therein are held in confidence and in trust and will not be used, reproduced in whole or in part, nor its contents revealed to others, except to meet the purpose for which it was delivered. It is understood that no right is conveyed to reproduce or have reproduced any item herein disclosed without express permission from Overland Storage. Overland Storage provides this manual as is, without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Overland Storage may make improvements or changes in the product(s) or programs described in this manual at any time. These changes will be incorporated in new editions of this publication. Overland Storage assumes no responsibility for the accuracy, completeness, sufficiency, or usefulness of this manual, nor for any problem that might arise from the use of the information in this manual. Overland Storage, Inc. 4820 Overland Avenue San Diego, CA 92123 U.S.A. Tel: 1.877.654.3429 (toll-free U.S.) Tel: +1.858.571.5555 Option 5 (International) Fax: +1.858.571.0982 (general) Fax: +1.858.571.3664 (sales) www.overlandstorage.com 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W iii Preface This guide explains how to use the ULTAMUS RAID manager software included with the ULTAMUS RAID storage array to perform tasks such as create arrays and logical volumes, modify configuration settings, and take snapshots. For information about how to install and configure the ULTAMUS RAID storage array, see the ULTAMUS RAID 1200 Hardware Setup Guide on your Software and Documentation CD. The setup guide also covers the configuration of the ULTAMUS RAID manager software on the hardware array. This guide assumes that you are familiar with computer hardware, data storage, and network administration terminology and tasks. It also assumes you have basic knowledge of Serial ATA (SATA), Serial-attached SCSI (SAS), Fibre Channel (FC), Storage Area Network (SAN), and Redundant Array of Independent Disks (RAID) technology. How to Use this Document The purpose of this User Guide is to introduce ULTAMUS RAID manager to its users, provide an explanation of the interface, and provide a step-by-step approach to configuring up the network settings when using the ULTAMUS RAID manager. The guide walks you through starting the ULTAMUS RAID manager, configuring e-mail, SYSLOG, and SNMP, and additional monitoring. The remaining chapters deal with the more advanced features such as Snapshot, SAN LUN Mapping, controller environment monitoring and optimization, and modifying controller operational parameters. You will also find information on advanced management of your storage, including event logs and statistical analysis. Product Documentation ULTAMUS RAID Nearline Data Protection product documentation and additional literature are available online at: http://www.overlandstorage.com. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W iv ULTAMUS RAID 1200 User Guide Preface Conventions This user guide exercises several typographical conventions to help explain how to use the ULTAMUS RAID 1200 storage array. Convention Description & Usage Boldface Words in boldface indicate items to select such as menu items or command buttons. Ctrl-Alt-r This type of format details the keys you press simultaneously. In this example, hold down the Ctrl and Alt keys and press the r key. NOTE A Note indicates neutral or positive information that emphasizes or supplements important points of the main text. A note supplies information that may apply only in special cases—for example, memory limitations or details that apply to specific versions of a program. IMPORTANT An Important note is a type of note that provides information essential to the completion of a task or that can impact the product and its function. CAUTION A Caution contains information that the user needs to know to avoid damaging or permanently deleting data or causing physical damage to the hardware or system. WARNING A Warning contains information essential to people’s safety. It advises users that failure to take or avoid a specific action could result in physical harm to the user or hardware. Flow Indicator (>) Words in bold font with a greater than sign between them indicate the flow of actions to accomplish a task. For example, Setup > Passwords > User indicates that you should press the Setup button, then the Passwords button, and finally the User button to accomplish a task. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. Wv Contents Chapter 1 - Introduction and GUI Tour Overview ..................................................................................................................................................... 1-1 Working with ULTAMUS RAID manager GUI ............................................................................................. 1-1 GUI Top Section .......................................................................................................................................... 1-2 GUI Sidebar ................................................................................................................................................. 1-4 Accessing and Navigating the Event Log ......................................................................................... 1-5 Multicast Usage ..................................................................................................................................... 1-6 GUI Configuration Section ......................................................................................................................... 1-7 Toolbar ................................................................................................................................................... 1-7 Array ....................................................................................................................................................... 1-8 Logical Drives Sections ......................................................................................................................... 1-9 Enclosure Subsection .......................................................................................................................... 1-10 Non Fault Tolerant vs. Fault Tolerant Warning State ....................................................................... 1-14 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 whether the array is in a Non Fault Tolerant vs. Fault Tolerant Warning state, identify the number of drive failures for the array. Two drive failures put the RAID 6 array in a non fault tolerant state. Passing the mouse pointer over the status icon (yellow) displays the array’s status, also in the Array Information screen the status is displayed.Locate Option ................................ 1-14 Mixed Drive Types ............................................................................................................................... 1-15 Identifying and Fixing Mismatched Drives .................................................................................. 1-15 Chapter 2 - Getting Started Starting ULTAMUS RAID manager ............................................................................................................. 2-1 Setting Up the ULTAMUS RAID manager .................................................................................................. 2-1 Changing the Password ....................................................................................................................... 2-1 Network Settings ......................................................................................................................................... 2-2 Configuring Network Settings .............................................................................................................. 2-2 E-mail Settings ............................................................................................................................................. 2-3 Configuring E-mail Notices .................................................................................................................. 2-4 Deleting an E-mail Address .................................................................................................................. 2-5 SNMP Settings .............................................................................................................................................. 2-5 Configuring SNMP Traps ....................................................................................................................... 2-5 Deleting an SNMP Server ..................................................................................................................... 2-6 SYSLOG ........................................................................................................................................................ 2-6 Gathering Logs ...................................................................................................................................... 2-7 SYSLOG Daemon .................................................................................................................................. 2-7 Operational View .................................................................................................................................. 2-7 Configuring SYSLOG ............................................................................................................................. 2-8 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W vi ULTAMUS RAID1200 User Guide Contents Deleting a SYSLOG Server .................................................................................................................... 2-8 Monitoring Settings ..................................................................................................................................... 2-9 Additional Monitoring Servers .............................................................................................................. 2-9 Removing an Individually Monitored Server .................................................................................... 2-10 Chapter 3 - Storage Solutions Manually Configuring the Storage Solution ............................................................................................. 3-1 Drive Requirements Based on RAID Level .......................................................................................... 3-1 Optimization and Drive Selection for RAID 5 and 6 .......................................................................... 3-2 Creating and Configuring an Array ......................................................................................................... 3-2 Creating An Array ................................................................................................................................. 3-2 Monitoring Array Initialization .............................................................................................................. 3-5 Configuring Array Write-Back Cache ...................................................................................................... 3-6 Initializing the Array ..................................................................................................................................... 3-7 Monitoring Array Initialization .............................................................................................................. 3-8 Pause/Resume Array Initialization ....................................................................................................... 3-8 Setting Advanced Power Management ........................................................................................... 3-8 Array Power Management (APM Level 2) ................................................................................... 3-8 APM Characteristics ..................................................................................................................... 3-10 Adding Hot Spare Drives .......................................................................................................................... 3-10 Assigning a Global Spare ................................................................................................................... 3-11 Assigning a Dedicated Spare ........................................................................................................... 3-12 Removing a Spare .............................................................................................................................. 3-13 Auto Spare Option .............................................................................................................................. 3-13 Creating the Logical Drive ...................................................................................................................... 3-14 Saving the Configuration ......................................................................................................................... 3-16 Chapter 4 - SAN LUN Mapping Overview ..................................................................................................................................................... 4-1 Terminology ................................................................................................................................................. 4-1 SAN LUN Mapping Access ......................................................................................................................... 4-1 Overview: SAN LUN Mapping Window ............................................................................................... 4-2 SELECT and NAME YOUR HBA PORT Sections .................................................................................... 4-2 ADD MAPPINGS Section ....................................................................................................................... 4-3 MAPPINGS Section ................................................................................................................................ 4-3 Example of Failover Mapping ............................................................................................................. 4-3 Creating a SAN LUN Mapping .................................................................................................................. 4-4 Deleting a SAN LUN Mapping ................................................................................................................... 4-5 Modifying a SAN LUN Mapping ................................................................................................................ 4-6 Chapter 5 - Controller Management Overview ..................................................................................................................................................... 5-1 Controller Information Access ................................................................................................................... 5-1 Status ...................................................................................................................................................... 5-2 Hardware/Firmware .............................................................................................................................. 5-2 Configuration ........................................................................................................................................ 5-2 Operations ............................................................................................................................................. 5-3 Reset or Shut Down a RAID Controller .......................................................................................... 5-3 Log Files and Diagnostic Dumps ................................................................................................... 5-3 Synchronize the Time ...................................................................................................................... 5-3 License Information .............................................................................................................................. 5-4 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W vii ULTAMUS RAID1200 User Guide Contents Update Controller Firmware ...................................................................................................................... 5-4 Advanced Settings ..................................................................................................................................... 5-6 Identity ................................................................................................................................................... 5-7 The Configuration WWN ................................................................................................................. 5-8 Fault Tolerance Settings ....................................................................................................................... 5-9 Host Port Settings ................................................................................................................................. 5-11 Chapter 6 - Daily Operations How ULTAMUS RAID manager Server Failover Works .............................................................................. 6-1 Performance Optimization ....................................................................................................................... 6-1 Execution Throttle .................................................................................................................................. 6-1 Scatter/Gather ...................................................................................................................................... 6-2 Time-Out Issues ............................................................................................................................................ 6-2 Statistics ........................................................................................................................................................ 6-2 Access Statistics .................................................................................................................................... 6-2 Command Size and Alignment Statistics ........................................................................................... 6-4 Using Command Size and Alignment Statistics ................................................................................. 6-5 Read-Ahead Statistics .......................................................................................................................... 6-5 Command Cluster Statistics ................................................................................................................. 6-6 Additional ULTAMUS RAID manager Functions ....................................................................................... 6-8 About ..................................................................................................................................................... 6-8 Take Control Monitoring ....................................................................................................................... 6-8 Rescan ................................................................................................................................................... 6-9 Chapter 7 - Advanced Functions Advanced Drive and Array Functions ...................................................................................................... 7-1 Accessing the Drive Screen ................................................................................................................. 7-1 Locate Drive .......................................................................................................................................... 7-2 Identifying Drive Members of an Array ............................................................................................... 7-3 Modifying an Array ............................................................................................................................... 7-3 Verify Parity ............................................................................................................................................ 7-4 Rebuilding an Array .............................................................................................................................. 7-6 Expanding an Array .............................................................................................................................. 7-7 Deleting an Array .................................................................................................................................. 7-9 Trusting an Array .................................................................................................................................. 7-10 Restoring and Clearing the Configuration ............................................................................................ 7-11 Restoring the Configuration ............................................................................................................... 7-12 Clearing the Configuration ................................................................................................................ 7-13 Advanced Logical Drive Functions ........................................................................................................ 7-13 Expanding a Logical Drive ................................................................................................................. 7-14 Deleting a Logical Drive ..................................................................................................................... 7-15 Advanced Power Management ............................................................................................................ 7-16 Drive Power Management (APM Level 1) ....................................................................................... 7-16 Configuring Drive Power Management (APM Level 1) ............................................................ 7-16 APM Characteristics ........................................................................................................................... 7-18 Advanced Performance Options ........................................................................................................... 7-19 Performance Options Settings ........................................................................................................... 7-20 Synchronize Cache Writes to Disk ............................................................................................... 7-21 Target Command Thread Balance ............................................................................................. 7-22 Sequential Write Optimization ..................................................................................................... 7-23 Overload Management .................................................................................................................... 7-24 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W viii ULTAMUS RAID1200 User Guide Contents Chapter 8 - Using Snapshot Introduction to Snapshots .......................................................................................................................... 8-1 Snapshots and Caching ...................................................................................................................... 8-2 Application Caches ........................................................................................................................ 8-2 Operating System Cache .............................................................................................................. 8-2 RAID Controller Cache ................................................................................................................... 8-2 Overwrite Data Areas ........................................................................................................................... 8-2 ODA Location .................................................................................................................................. 8-3 Selecting the ODA Stripe Size .............................................................................................................. 8-3 ODA Storage Capacity ........................................................................................................................ 8-4 Virtual LUNs ............................................................................................................................................ 8-4 Virtual LUN Numbering ................................................................................................................... 8-4 Example of Virtual LUN Numbering ............................................................................................... 8-5 Enabling Snapshot ...................................................................................................................................... 8-5 Taking a Snapshot ...................................................................................................................................... 8-7 Mapping a Snapshot ............................................................................................................................... 8-10 Deleting a Snapshot ................................................................................................................................. 8-11 Performing a Snapback ........................................................................................................................... 8-14 Disabling Snapshot ................................................................................................................................... 8-16 Chapter 9 - Support and Updates Tech Support ............................................................................................................................................... 9-1 Updating ULTAMUS RAID manager Software .......................................................................................... 9-3 Appendix A - Optimizing Write Performance Introduction .................................................................................................................................................A-1 Sequential Access ......................................................................................................................................A-2 Number of Outstanding Commands .................................................................................................A-2 Access Size ..................................................................................................................................................A-2 Access Alignment .................................................................................................................................A-2 Sub-Array .....................................................................................................................................................A-3 Multiple Drive Failures .................................................................................................................................A-4 Faster Rebuild ........................................................................................................................................A-4 Summary ......................................................................................................................................................A-4 Appendix B - Troubleshooting Problems You May Encounter ................................................................................................................... B-1 Failed Drives Codes .................................................................................................................................... B-5 SAS Fatal Error Codes ................................................................................................................................. B-5 Appendix C - Event Log Lists Controller Events ........................................................................................................................................ C-1 Expansion Module Events ......................................................................................................................... C-7 Alarm Events ............................................................................................................................................... C-8 Drive and Array Events .............................................................................................................................. C-9 Controller Port Events .............................................................................................................................. C-13 Enclosure Events ...................................................................................................................................... C-15 ULTAMUS RAID manager Server Events ................................................................................................. C-19 SnapShot Events ...................................................................................................................................... C-22 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W ix CHAPTER 1 Introduction and GUI Tour Overview ULTAMUS RAID manager (URM) storage management software is a fullfeatured, graphical, HTML-based software suite designed to configure, manage, and monitor storage subsystems. It is installed on each RAID controller and is accessed using a web browser. For storage arrays with two RAID controllers, the data is combined for display in the GUI for that storage array. Working with ULTAMUS RAID manager GUI The ULTAMUS RAID manager GUI consists of four sections (Figure 1-1): Top Section Configuration Section Sidebar Section Enclosure Section Figure 1-1: ULTAMUS RAID manager Main Browser Screen 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-1 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour The ULTAMUS RAID manager work area consists of a Main screen with pop-up dialog windows for performing specific functions. The Main screen sections are: • Top section – title, module tab, and additional support buttons • Sidebar section– network information and links to other ULTAMUS RAID storage arrays • Configuration section – controller links, configuration tools, and enclosure data • Enclosure section – data on the physical status of the arrays Configuration functions 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 and SNMP traps, reviewing event logs, and analyzing system statistics. GUI Top Section Module Tab Additional Help and Support Buttons Top Storage Solution Icon Controller Icon Opens Information Window Figure 1-2: ULTAMUS RAID manager Top Sections The Top section is located at the top of the right side of the screen (Figure 1-2). It provides access to module tabs, support items, and the various installed modules. It consists of these types of icons: 10400166-102 09/2008 • Storage Solution Icons – These icons represent each storage solution configured on the ULTAMUS RAID. You will also see the warning (!), error, and unknown icons for unfocused storage solutions that are being monitored. • Controller Icons – These icons represent RAID Controllers installed in the enclosure. For duplex systems (Active-Active), a dual controller image is displayed. • Module Tab – Loads the module information. ©2007,2008 Overland Storage, Inc. W 1-2 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Table 1-1 provides detailed information for these icons: Table 1-1: Top Section Icons Icon Name Description Storage Solution Icons Normal (Gray) Status is OK. Warning Indicates a component in the storage solution is in (Flashing Yellow & “!”) degraded mode. Error (Flashing Red) Indicates a component in the storage solution has malfunctioned. Missing (Flashing Red “?”) Indicates that the storage solution was there at startup but now cannot be located. Unmonitored This icon indicates that another ULTAMUS RAID manager server is monitoring this storage solution, or if you just performed a rescan, then the ULTAMUS RAID manager servers are still determining which ULTAMUS RAID manager server will take control of the monitoring of the storage solution. Controller Icons Normal (Green) A single green icon represents a normal operating system with one controller card. Normal Duplex (Green) A dual green icon represents a normal operating system with two controller cards (Active-Active). Error (Flashing Red) 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. RAID Module The tab appears at the top of the Main window and when selected, focuses the monitoring and management functions to specific systems types. These tabs flash yellow if a warning condition occurs and red if an error condition occurs. Module Tabs 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-3 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour GUI Sidebar Current ULTAMUS RAID Icon Number of Users Logged In Name & IP Address of Logged-In Host Sidebar Event Logs Main Screen Controls Discovered Remote Icons Figure 1-3: ULTAMUS RAID manager Sidebar Sections The Sidebar section is located along the left side of the screen (Figure 1-3). It provides access to the active storage array, event logs, network settings, and any other remote storage arrays. It consists of these types of icons: • Current ULTAMUS RAID manager Storage Array– This icon appears at the top of the Sidebar section. The icon indicates the status of the storage array by changing its color and state. • Remote ULTAMUS RAID manager Icons (Global License) – These icons appear for each remote storage array discovered during a network scan. The icon indicates the status of the storage array by changing its color and state. • User Icons – Each icon represents a user logged into the active URM. Table 1-2 provides detailed information for these icons: Table 1-2: Sidebar Section Icons Icon Name Description Current ULTAMUS RAID manager Storage Array Icons Normal (Gray) Status is OK. Warning (Flashing Yellow) Indicates a server warning that a device connected is in degraded mode. Error (Flashing Red) Indicates a server error or device malfunction. Remote ULTAMUS RAID manager Icons (Global License) Normal (Gray) 10400166-102 09/2008 Status is OK. ©2007,2008 Overland Storage, Inc. W 1-4 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Table 1-2: Sidebar Section Icons (Continued) Icon Name Description Warning (Flashing Yellow) Indicates a warning that a device connected is in degraded mode. Error (Flashing Red) Indicates an error or device malfunction. Missing (Flashing White) The unit has not responded in at least 40 seconds and is considered missing. If you would like to remove the missing unit from the list, click the Rescan button. This refreshes the screen with a current list of discovered units. Active User Count Represents each user logged into the ULTAMUS RAID manager you are monitoring. Placing the mouse pointer over the icon displays the IP address, host name and the user name. User Icon Accessing and Navigating the Event Log To access the Event Logs, click the LOGS button (Figure 1-4) located under the active (focused) ULTAMUS RAID manager storage array icon on the Main screen. Figure 1-4: Event Logs Button 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-5 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour The Event Log screen appears (Figure 1-5). The following illustration explains the components of the event log. Navigation Buttons Date & Time Event Description * Information Status Icon Device Name & WWN ID Indicates Event Occurred While URM Shut Down Figure 1-5: Event Log Screen Multicast Usage ULTAMUS RAID manager uses multicasting technology to provide inter-server communication with other storage arrays running URM. During initial start-up, a storage array performs a multicast registration using the default multicast IP address of 225.0.0.225 on port 9191. When registration is complete, the unit is able to receive all packets sent to the multicast address. All packets sent to the multicast address remain in the local network, unless an explicit server IP address outside the subnet is added using Settings > Preferences (see “Additional Monitoring Servers” on page 2-9). This provides the focused URM with remote monitoring of up to 10 other installations. Each storage array sends a check-in packet in 10-second intervals. When an initial check-in packet is received, all ULTAMUS RAID manager arrays know the existence of the other units. If a unit fails to send three check-in packets, the other units mark that unit as missing. This is indicated by a white monitor icon displayed on the Main screen in the Sidebar section. When the service that owns the monitored storage solution is down for any reason and three check-in packets are not received, the monitoring is automatically transferred to another ULTAMUS RAID storage array. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-6 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour GUI Configuration Section Figure 1-6: URM GUI Configuration Section The Configuration section is located just under the Top section and contains the Configuration Toolbar, the Arrays subsection, and the Logical Drives subsection. Toolbar The toolbar icon buttons appear at the top of the configuration section (Figure 1-7) and provide one-click access to primary functions. Figure 1-7: Location of Toolbar Icons 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-7 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour NOTE: Throughout the interface, holding the mouse pointer over an icon displays a popup window with information specific to the object. Table 1-3: Toolbar Icons Icon Name Description Create Array This button opens the Create Array window allowing you to create new disk arrays. Create Logical Drive This button opens the Logical Drive window allowing you to create new logical drives. SAN Mapping This button opens the SAN LUN Mapping panel that allows you to further customize logical drive availability. Logical Drive Statistics This button opens the Statistics window. Advanced Settings This button opens a window from which you can change controller parameters. Archive Configuration This button opens a window from which you can choose to save, restore, or clear the configuration. Note that when deleting a configuration, this deletes all arrays and logical drives, including the data on those logical drives. Array The Array subsection is located on the left side of the Configuration section and provides an active view of all the arrays that make up the storage system solution. Number of Disk Arrays Click to Locate Drives Disk Array Status Icon Clicking Array Name Opens Info Window Initializing Status Initializing Controls Figure 1-8: Arrays Subsection Icons 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-8 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Table 1-4: Array Subsection Icons Icon Name Description Normal (Green) Status is OK. Warning (Yellow) Indicates a drive component in a RAID 1, 10, 5, 6 or 50 array has failed and the array is no longer fault tolerant, or the array is in a rebuild cycle. NOTE: For RAID 6 arrays, it indicates 1 or 2 drives have failed. See Drive Status icon Critical state. Error (Red) Indicates an array is invalid or offline due to an error: • RAID 0 – One drive has failed. • RAID 1/10 – Two drives have failed from the same pair. • RAID 5 – Two drives have failed. • RAID 6 – Three drives have failed. • RAID 50 – Two drives have failed within the same sub-array. Logical Drives Sections The Logical Drives subsection is located on the right side of the Configuration section and provides an active view of all the logical drives that make up the storage system solution. Number of Logical Drives Logical Drive Status Icon Camera Indicates Snapshot Enabled Clicking Drive Name Opens Info Window Figure 1-9: Logical Drives Subsection Icons It consists of these types of icons: 10400166-102 09/2008 • Logical Drive Status – These icons appear to the left of each logical drive name and depict the current state of the specific drive. • Snapshot Status – This icon is found in the Logical Drives section, adjacent to the Snapshot enabled logical drive and depict its current state. If a Snapshot operation is underway, a status bar appears beneath the icon displaying the percent complete. ©2007,2008 Overland Storage, Inc. W 1-9 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Table 1-5: Logical Drives Subsection Icons Icon Name Description Logical Drive Status Normal (Green) Status is OK. Warning (Yellow) Indicates the logical drive is part of an array that is degraded. NOTE: For logical drives consisting of RAID 6 arrays, it indicates 1 or 2 drives have failed. See Drive Status icon Critical state. Error (Red) Indicates the logical drive is part of an array that 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 subarray. Snapshot Status Normal (Gray) Snapshot is OK. Warning (Yellow) Snapshot is running out of space. It is OK, just in danger of running out of room if I/O continues. Warning appears if there is approximately less than 3 GB or 90% of the space is used up. Failed (Red) The Overwrite Data Area is full, the Snapshot is invalid, and therefore failed. Enclosure Subsection Number of Enclosures Click Icon to View Information 10400166-102 09/2008 Click to Locate Animated Drive Status Enclosure ID (WWN Name) Temperature Monitor Power Supplies ©2007,2008 Overland Storage, Inc. Cooling Fan Alarm Monitor Blanking Module Expansion RAID I/O Modules Controller W 1-10 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Figure 1-10: Enclosure Section Graphics The Enclosure section is located at the bottom of the Main screen. It provides an active view of all ULTAMUS RAID enclosures (head and expansion units) that make up the active system. It consists of these types of icons: • Drive Status – These icons appear on the front of the enclosure view on the Main screen and provide an instant view of the status of disk drives as well as drive location and an access to the Drive Information pop-up window. • Enclosure Rear Modules – These icons appear on the Main screen in the Enclosure section. They provide an instant view of the operating status of the enclosure modules and open the Controller Information pop-up window. • Alarm Status – Shows if the alarm is active or silent. • Temperature – Icon is displayed just above the rear enclosure icon and indicates the status of the enclosure temperature. • Enclosures – The entire enclosure icon can change shades according to enclosures state. The enclosures are labeled above each front view to aid with identifying them in a multiple enclosure environment. Table 1-6: Enclosure Section Icons Icon Name Description Member Disk drive is a member component of an array. Available Disk drive is online and available for use in an array or as a hot spare. Dedicated Spare Disk drive is marked as a dedicated spare to an array. Empty Disk drive slot is empty. Failed Disk drive has failed. Global Spare Disk drive is a global spare. Missing Indicates that ULTAMUS RAID manager is unable to determine the status of the drive. Initializing Disk drive is a member of an array being initialized. Rebuilding Drive members of an array are in rebuild mode. Locate 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. Critical Drives are members of a fault tolerant array and are in a non-fault tolerant state. See “Non Fault Tolerant vs. Fault Tolerant Warning State” on page 1-14. Updating Firmware Drive’s firmware is being updated. Drive Icons 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-11 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Table 1-6: Enclosure Section Icons (Continued) Icon Name Description Member Failed Array This icon appears on all disk drives that are members of an array that has failed. For example, if you remove a drive from a RAID 0 array or a drive in that array fails, the remaining drive members have this icon displayed indicating that array has failed. If you accidentally remove the wrong drive in a critical redundant array (RAID 5) instead of the failed drive, that array will have failed and its member drives will have this icon displayed. Re-inserting the drive that was accidentally removed puts the drive members back to a critical state in which the array is being rebuilt. Queued to Initialize This icon is displayed on the drive members whose array is to be initialized and is placed in a queue for the process to be started and completed. Expanding This icon is displayed on the drive members whose array is expanding. Verifying This icon is displayed on the drive members whose array’s parity data is being verified. Enclosure Rear Modules Fan Module Normal (Gray) Both fans in the Fan module are operating normally. Fan 1 Failed (Yellow) Fan 1 in the Fan module has failed. Fan 2 is still operating normally. Fan 2 Failed (Yellow) Fan 2 in the Fan module has failed. Fan 1 is still operating normally. Failure (Red) Both fans, front and rear, in the Fan module have failed, or the Fan module has been removed from the enclosure. Power Supply Module Normal (Gray) Power supply is operating normally. Failure (Flashing Red) A red flashing icon with Failure displayed indicates that the subject power supply has failed. Missing (Red) A solid red icon indicates that the power supply is missing. Unknown The power supply information from the SES processor or SAF-TE processes is missing or invalid. RAID Controller Module Normal 10400166-102 09/2008 RAID Controller is operating normally. ©2007,2008 Overland Storage, Inc. W 1-12 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Table 1-6: Enclosure Section Icons (Continued) Icon Name Description Error (Red) RAID Controller has failed in an Active-Active topology or the backup battery has failed. Empty An empty controller slot for future expansion. A blank plate is shown. Disk I/O Module Normal Disk I/O Module is operating normally. Error (Red) A Disk I/O Module has failed. Missing A module is missing from the slot. Empty A module is removed and a blank plate is installed. Alarm Off (Green) Indicates the alarm is Off (Muted). Alarm On (Red) Indicates the alarm is On (Continuous), On (Intermittent), On (Remind), or On. Normal (Green) Indicates that the temperature is normal. Warning (Yellow) Indicates that the enclosure temperature is approaching the established threshold. Failed (Red) Indicates that 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 can be an indication that the temperature sensor is faulty. Missing Indicates that the information from the SES processor or SAF-TE processes regarding the sensors is invalid or missing. Alarm Temperature Rear View (Head Unit) Normal (Full Color) – All components are operating normally. (Expansion) (Head Unit) (Expansion) 10400166-102 09/2008 Communication Error (Grayed Out)– The SES process has lost communication with the enclosure or you have disabled Enclosure Support in the Controller Advanced Settings. ©2007,2008 Overland Storage, Inc. W 1-13 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Table 1-6: Enclosure Section Icons (Continued) Icon Name Description (Head Unit) Normal (Full Color) – All components are operating normally. (Expansion) (Head Unit) (Expansion) Communication Error (Grayed Out)– The SES process has lost communication with the enclosure or you have disabled Enclosure Support in the Controller Advanced Settings. Non Fault Tolerant vs. Fault Tolerant Warning 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 whether the array is in a Non Fault Tolerant vs. Fault Tolerant Warning state, identify the number of drive failures for the array. Two drive failures put the RAID 6 array in a non fault tolerant state. Passing the mouse pointer over the status icon (yellow) displays the array’s status, also in the Array Information screen the status is displayed.Locate Option When you click the Locate highlighted text (just above each storage array front view next to its name), it causes the Blue ID LED on the OPS Panel to flash. This allows for easy identification of the storage array in a rack or a multiple-enclosure installation environment. 1. On the Main screen (Figure 1-11), click the Locate link. The following window appears: Figure 1-11: Locate Start Message Screen 2. Click GO to begin flashing the Blue ID LED or CLOSE to cancel the operation. 3. When the locate function time has expired and you see the completion screen (Figure 1-11), click CLOSE. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-14 ULTAMUS RAID 1200 User Guide Introduction and GUI Tour Figure 1-12: Locate Completion Message Screen Mixed Drive Types You must install drives in each of the four vertical columns of slots using the same drive types; that is all SAS or all SATA types. You will receive the following warning message displayed in the Enclosure section if you have installed a mixture of drive types within a column of drive slots in the enclosure. If the warning message is ignored, an attempt to create an array without rearranging the drives will be stopped with the following subsequent warning message. You will be prevented from proceeding further. Figure 1-13: Mixed Drive Types Warning Message Identifying and Fixing Mismatched Drives Passing the mouse pointer over the drives in the enclosure view displays information about the drive including its type. This makes it easier to locate the group of drives in a column where the mismatch of types exists. Swap the drives with like types to remove the warning message. You can click Rescan to command ULTAMUS RAID manager to detect the correct drives and allow you to proceed. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 1-15 Getting Started CHAPTER 2 Starting ULTAMUS RAID manager 1. Open your web browser. 2. Enter the explicit IP address assigned to the ULTAMUS RAID manager server followed by the port number, for example: http://10.11.48.120:9292. For information on how ULTAMUS RAID manager performs network initialization and how to set the network parameters, see “Network Settings” on page 2-2. When you first start the ULTAMUS RAID manager, you are prompted for a user name and password. The default values are: • User Name: admin • Password: password Setting Up the ULTAMUS RAID manager You must configure the network settings the first time you start ULTAMUS RAID manager. Once the network connections are established, you can then configure URM to send event notifications via e-mail or SNMP traps to recipients with general, error, and warning information. You can also configure the system logging, set passwords, and monitor the system. Changing the Password When you first use the ULTAMUS RAID manager, for security purposes you should change the password using the Password option: 1. From the Sidebar, click SETTINGS > PASSWORD. 2. Enter the appropriate password information (Figure 2-1 on page 2-2): • Type the current password in the Old Password field. • Type the new password in the New Password field. • Retype the new password in the Re-type New Password field. NOTE: Passwords are not displayed as you type them. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-1 ULTAMUS RAID 1200 User Guide Getting Started Figure 2-1: Password Tab on the Settings Screen 3. Click CHANGE. 4. At the successful confirmation message, click CLOSE. 5. Click CLOSE on the SETTINGS screen. NOTE: If you lose or misplace your password, contact technical support for further instructions. Network Settings Upon start-up, the ULTAMUS RAID manager looks for its preestablished IP address and initializes the network interface using that address. NOTE: To identify the new DHCP IP address lease, use the urmsetup.exe program located on your Software and Documentation CD. If an IP address is not defined, ULTAMUS RAID manager queries for a DHCP IP address. If an IP address cannot be determined, the software uses a default IP address of 10.1.1.5 for Controller 0 and 10.1.1.6 for Controller 1. If your network does not have a DHCP server, set the host IP address to 10.1.1.20 and the subnet mask to 255.0.0.0 and run the Setup Wizard. If an error occurs, the ULTAMUS RAID manager server is assigned IP address, 10.1.1.7. Configuring Network Settings The first time you start ULTAMUS RAID manager, you need to configure the network settings: 1. From the Sidebar, click SETTINGS > PREFERENCES. The Host Name field (Figure 2-2 on page 2-3) initially shows a default name of esv0- for Controller 0 (bottom) or esv1- for Controller 1 (top). It is recommended you change this name for easier network identification. IMPORTANT: If the ULTAMUS RAID manager Host Name displays esverr, it indicates a problem with the ULTAMUS RAID manager’s server component. Contact technical support. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-2 ULTAMUS RAID 1200 User Guide Getting Started Figure 2-2: Preferences Tab in the Settings Window 2. To change the Host Name, type a new name in the Host Name field and click Apply. 3. Change the default IP address and network settings: a. Select either Static IP or Dynamic IP (DHCP). b. If Static IP selected, enter the network addresses: • IP Address • Subnet Mask • Default Gateway • DNS Server c. If Dynamic IP selected, you can obtain a new IP address from your DHCP server by checking the Renew box. 4. Click APPLY to make the changes effective. 5. Click CLOSE. E-mail Settings ULTAMUS RAID manager allows you to establish up to ten e-mail addresses where event notices are automatically sent. NOTE: Your e-mail server should be configured to receive on port 25 for the ULTAMUS RAID server to send e-mail messages. For example, to make sure you are always aware of changes to the configuration, you can establish an address where e-mail notification messages are sent when a configuration event occurs. Such notifications enable you to determine when to save your configuration file. NOTE: Enclosure Support is enabled by default. This support option must be enabled for the server to send e-mail notifications of enclosure events. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-3 ULTAMUS RAID 1200 User Guide Getting Started Configuring E-mail Notices 1. From the Sidebar, click SETTINGS. The Settings screen opens at the EMAIL tab (Figure 2-3). Enter signature information here Figure 2-3: Entering E-Mail Settings 2. Enter the appropriate data: a. Enter the name (up to 32 characters) or IP address of your e-mail server. This is the SMTP mail server name. b. To append a signature to the message, check the Put Signature box and type the signature information in the scrollable window. c. Enter the user e-mail addresses in the Email Addresses fields. You can add up to ten (10) e-mail addresses. Click the 6-10 button to enter more than five (5) addresses. d. Check the box under the icon (Table 2-1) for each type of event notification desired for each address: Table 2-1: Event Notification Type Icons Event Icon Event Type Type of Message Information Information notices about the system. Warning Warning events that occur in the system. Error Error events that occur in the system. 3. Click APPLY. 4. At the successful confirmation message, click CLOSE. 5. Click TEST to test the configurations. 6. You receive a pop-up confirmation message that the test was successfully completed, and each addressee receives a test message. Click CLOSE. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-4 ULTAMUS RAID 1200 User Guide Getting Started 7. Click CLOSE on the SETTINGS screen. Deleting an E-mail Address 1. From the Sidebar, click SETTINGS and then EMAIL (if not already selected). 2. Click DELETE next to the e-mail address you want to remove (Figure 2-4). Figure 2-4: EMAIL Tab on the Settings Screen 3. Click APPLY make the changes effective. 4. Click CLOSE on the SETTINGS screen. SNMP Settings ULTAMUS RAID manager 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 ULTAMUS RAID manager are received by the host SNMP Servers designated in the settings window for the specified port and community. Configuring SNMP Traps 1. From the Sidebar, click SETTINGS > SNMP. 2. Enter the appropriate data: a. Enter the SNMP Server name or IP address of the host you want to receive SNMP traps (Figure 2-5). b. Enter the IP port on which the SNMP Server expects to receive traps under SNMP Port. The default is 162. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-5 ULTAMUS RAID 1200 User Guide Getting Started c. Enter the Community to which the traps belongs. SNMP Servers can belong to several different communities or receive packets for different communities. d. Select the events you want to be included in the traps. You can select Informational, Warning and Error trap types (see Table 2-1 on page 2-4). Figure 2-5: SNMP Tab on the Settings Screen 3. Click APPLY. 4. At the successful completion message, click CLOSE. 5. Click TEST to test the configurations. 6. You receive a pop-up confirmation message that the test was successfully completed, and each addressee receives a test message. Click CLOSE. 7. Click CLOSE on the SETTINGS screen. Deleting an SNMP Server To delete an SNMP server: 1. From the Sidebar, click SETTINGS > SNMP. 2. Click DELETE next to the SNMP Server you want to remove. 3. Click APPLY to make the changes effective; a status pop-up notice appears. 4. Click CLOSE on the SETTINGS screen. SYSLOG ULTAMUS RAID manager’s SYSLOG agent is a module that enables sending RAID system event logs to all listening SYSLOG clients on all installed platforms. SYSLOG is designed for greater flexibility in that it supports many-to-many mapping. You may have: • 10400166-102 09/2008 Multiple SYSLOG servers that monitor a single RAID storage system for event logs. ©2007,2008 Overland Storage, Inc. W 2-6 ULTAMUS RAID 1200 User Guide Getting Started • A single SYSLOG server that monitors multiple RAID storage systems for event logs. • Multiple SYSLOG servers that monitor multiple RAID storage systems for event logs. This many-to-many mapping provides data redundancy, which serves as an additional safety net. In this case, a failed SYSLOG server has no impact if another SYSLOG server is functioning normally. SYSLOG daemon supports both Linux and Windows platforms. If you are using a Linux operating system, the SYSLOG daemon is a component of your operating system. If you are using a Windows operating system, you need to install a separate tool (http://syslog-win32.sourceforge.net/) that runs as a Windows service. Gathering Logs With ULTAMUS RAID manager, previously configured listening SYSLOG servers persist even though the controller module is flashed with new software as the file data is stored in NVRAM. Also, the data is not affected by software upgrades. SYSLOG Daemon The SYSLOG daemon listens for incoming event log messages on port 514 and logs them to a message file. SYSLOG messages consist of the elements listed in Table 2-2: Table 2-2: Elements of a SYSLOG Message Element Indicates Facility The type of syslog message. For example, the message can be a kernel, user level, mail system or system daemon message. Priority The sensitivity or type of message, to include Information, Warning, or Error. Timestamp The date and time the event occurred. Originating Device The device that originated the event message. Message Content The plain language contents of the event message. Operational View Whenever a new RAID storage system event is logged, SYSLOG sends the message to all subscribers that match the type of event logged. If the event was an Error message type, and all daemons are configured to receive those type of event messages, then they all receive the event log. If the event was an Information message type, then only those daemons configured to subscribe to Information priority message receive the event log. Security can be a concern because event logs are sent in standard text format and have no encryption. Information is sent in UDP packets, so there is no assurance that the event log arrived at the subscriber (SYSLOG server). 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-7 ULTAMUS RAID 1200 User Guide Getting Started Configuring SYSLOG The SYSLOG information that you enter must be valid, or your entries result in error messages. 1. From the Sidebar, click SETTINGS > SYSLOG. 2. Enter the appropriate data: a. Enter the IP addresses of the host servers designated to be SYSLOG servers in the syslogd server fields (Figure 2-6). b. Enter the port ID of the recipient SYSLOG server in the syslogd port field. The default port is 514, and the range of port IDs is 1 - 65535. c. Select the events you want to be included in the logs. You can select Informational, Warning and Error trap types (see Table 2-1 on page 2-4). Figure 2-6: SYSLOG Screen 3. Click APPLY. 4. At the successful completion message, click CLOSE. 5. Click TEST to test the configurations. 6. You receive a pop-up confirmation message that the test was successfully completed, and each SYSLOG server receives a test message. Click CLOSE. 7. Click CLOSE on the SETTINGS screen. Deleting a SYSLOG Server 1. Click SETTINGS > SYSLOG. 2. Click DELETE next to the syslog you want to remove, which clears the entries for that SYSLOG. 3. Click APPLY to save your settings. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-8 ULTAMUS RAID 1200 User Guide Getting Started Monitoring Settings The following options enable network administrators to make adjustments to the server’s multicast functionality. In the event there is a port conflict with the default multicast port, you have the ability to change this parameter. 1. On the Sidebar, click SETTINGS > PREFERENCES. 2. From the drop-down menu for Select Monitoring Group, choose a group. • Group 1 is Port 9191 • Group 2 is Port 9192 • Group 3 is Port 9193. 3. Click APPLY to make the changes effective. 4. Click CLOSE. Additional Monitoring Servers To specify additional ULTAMUS RAID manager servers on a different subnet to receive ULTAMUS RAID manager server packets, enter the IP addresses of the other servers. You can add up to 10 additional monitored servers (Figure 2-7). Figure 2-7: Monitored Servers on the Preferences Screen 1. From the Sidebar, click SETTINGS > PREFERENCES. 2. In the Individually Monitored Servers field, enter the IP address of a server outside the subnet and click ADD. 3. If necessary, add additional explicit IP addresses of any other server outside the subnet that you want to include by repeating Step 2. 4. Click APPLY. 5. Click CLOSE on the SETTINGS screen. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-9 ULTAMUS RAID 1200 User Guide Getting Started Removing an Individually Monitored Server 1. From the Sidebar, click SETTINGS > PREFERENCES. 2. Select the IP Address from the list of monitored servers and click REMOVE (Figure 2-8). Figure 2-8: Removing a Monitored IP Address 3. Click APPLY. 4. Click CLOSE on the SETTINGS screen. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 2-10 Storage Solutions CHAPTER 3 Configuring a storage solution requires that you plan and define the correct RAID level and array options, Hot Spares, and logical drives required for your solution. This chapter describes two ways to configure the ULTAMUS RAID storage solution: assisted automatic configuration, and manual configuration. This chapter assumes you have a basic understanding of RAID concepts. Manually Configuring the Storage Solution Manual configuration of the ULTAMUS RAID storage solution involves configuring and managing disk arrays, assigning Hot Spares, and creating Logical Drives. Drive requirements are based on the selected RAID level. Drive Requirements Based on RAID Level The drive requirements for each supported RAID level are: 10400166-102 09/2008 RAID Level Minimum Number of Drives Maximum Number of Drives 0 1 16 1 2 16 5 3 16 6 4 16 50 6 16 10 4 16 ©2007,2008 Overland Storage, Inc. W 3-1 ULTAMUS RAID 1200 User Guide Storage Solutions Optimization and Drive Selection for RAID 5 and 6 Typical RAID 5 or 6 implementations require a number of steps to write the data to the drives. If you want to set up a RAID 5 or 6 disk array for optimum performance, you must consider the number of data drives, the number of parity drives, and chunk size. You can optimize system performance based on the type of writes expected in your operation. For information on optimizing the performance using full strip write operations, see “Optimizing Write Performance” on page A-1. Additional information is provided at the appropriate step during configuration. Creating and Configuring an Array Arrays are created and configured using the Create Array screen. To create an array, you select the disk drives for the array, define array parameters, and save the configuration to a file. The configuration file is stored on all disk drives that are members of the array (regardless of whether the drives are in multiple enclosures). No changes are made to the configuration until it is saved. When you make changes to your configuration, make a new backup copy of the configuration file (see “Saving the Configuration” on page 3-16). A backup copy of the configuration allows you to quickly recover from a damaged configuration that was not self-healing, and restore everything to the point in time when the configuration was last saved. This preserves the definition of the arrays, logical drives, Snapshots, SAN LUN Mappings, and controller parameter settings. CAUTION: A damaged configuration can result in data loss. Creating An Array 1. On the Toolbar, click Create Array (Figure 3-1). Figure 3-1: Create Array on URM Toolbar 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-2 ULTAMUS RAID 1200 User Guide Storage Solutions The Create Array Configuration Screen (Figure 3-2) is shown. Figure 3-2: Create Array Screen with Available Drives NOTE: On the screen, the Notes section beneath the Available Drives graphic provides additional information while your mouse pointer is located in that setting row or positioned over a specific drive (Figure 3-2). 2. Select or enter the appropriate array settings: NOTE: The numbers next to each item on the screen suggest sequential steps to follow when creating an array. a. To select drives to include in the array, click any Available drive in the enclosure graphic. The drive icon changes to Selected. As you select drives, the projected size of the array is displayed on the upper right side of the title bar. To deselect a drive, click it a second time. b. In the Name field, enter a name for your array between 1–32 ASCII characters in length. c. Select the RAID Level for the array. RAID levels are based on drive requirements (see “Drive Requirements Based on RAID Level” on page 3-1). For RAID 6, choose 6, 11, or 16 disk drives. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-3 ULTAMUS RAID 1200 User Guide Storage Solutions d. For RAID 50 arrays only, select the number of Sub-Arrays to create. If you select more sub-arrays than allowed for the number of drives in the array, a warning is displayed when you create the array. In this case, reduce the number of sub-arrays. e. Select the appropriate chunk size from the Chunk Size drop-down menu. Available chunk sizes are 64K, 128K, or 256K. • For RAID level 0, 1, or 10 choose the correct size from the table: RAID 0 Number of Drives 1 2 3 4+ Minimum Chunk Size 256K 256K 128K 64K RAID 1 & RAID 10 • RAID 10 (0+1) Number of Drives 2 4 6 8+ Minimum Chunk Size 256K 256K 128K 64K For RAID 5/50, set the chunk sized based on the specific number of drives for a Full Stripe Write for optimum performance. For details, see “Optimizing Write Performance” on page A-1. NOTE: The controller firmware automatically sets the chunk size if a smaller chunk size is selected than the value recommended for the number of drives and specified RAID level. f. Select Initialize from the Initialize Trust drop-down menu (if not already selected). Initialization begins automatically in the background when the array is created. You can stop or pause the initialization from the Main screen. If you stop an initialization, the array will be trusted. NOTE: The Trust Array option should only be used in special circumstances (see “Trusting an Array” on page 7-10). As you create additional arrays, they also begin initializing. The maximum number of arrays that can be initialized in parallel is based on the limit of number of arrays, or 64. g. Select the Back-off Percent (reserved capacity) for the drives. The default is 1%. The Back-off Percent value determines how much drive capacity to reserve for future capacity expansions, or to enable replacement drives of greater capacity. NOTE: The back-off percent option is not applicable to non-redundant array types. A RAID 0 array is a non-redundant type of array and gains no benefit from establishing a reserve capacity. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-4 ULTAMUS RAID 1200 User Guide Storage Solutions h. Set the Read-Ahead Cache threshold. A read-ahead cache stores blocks or tracks of data when the controller satisfies a request. The controller may be able to successfully satisfy further requests using the data that is already in this cache, which improves performance. The Read-Ahead Cache value sets the size of the read-ahead cache, or disables it. Set the cache to: Automatic (Default, recommended) Allows the controller to determine the optimum size. Disabled Turns off the Read-Ahead Cache. 256K, 512K, 1MB, 2MB (Predetermined size) Optimizes the read performance based on your data patterns. i. Set the Write-back Cache options: The Write-back Cache optimizes write performance specific to your data patterns. Larger cache sizes increase the write performance, but may lower simultaneous read performance. The recommended size is 16 MB. The strategy of write operations results in a completion signal being sent to the host operating system as soon as the cache receives the data to be written. The disk drives receive the data at a more appropriate time in order to increase controller performance. See “Configuring Array Write-Back Cache” on page 3-6 for more information. • Select the cache threshold size (1MB, 2MB, 4MB, 8MB, 16MB, 32MB, 64MB, 128MB, 256MB or MAX MB), or Disable it. The default size is 16MB. • Check the box, Mirror Cache (Disable Write-back Cache when partner controller fails or is missing), if appropriate. This box is checked by default for maximum data protection. • Check the box, Disable Write-back Cache if a controller battery is low or fails, if appropriate. This box is checked by default for maximum data protection. • Check the box, Disable Write-back Cache if array becomes critical (N/A for RAID 0), if appropriate (e.g., during a rebuild). This box is checked by default for maximum data protection. 3. Click CREATE to create the array. A confirmation message indicates that the array was successfully created. 4. Click CLOSE to close the confirmation message screen. 5. Click CLOSE at the bottom of the Create Array screen. Monitoring Array Initialization You can monitor array initialization by viewing the progress bar. The progress bar displays the status of the initialization in percentage complete. The enclosure view displays animated icons for the disk drives that are initializing as part of the new array. To stop or pause the initialization process, click the link located to the right of the progress bar. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-5 ULTAMUS RAID 1200 User Guide Storage Solutions Stopping the initialization causes your array to be trusted. If you stop initialization, you should return to it at a later time. Initialization clears the drives of data. See “Initializing the Array” on page 3-7 for more information. Pausing the initialization halts the process until you select Resume. You can change the amount of processor time that is dedicated to the initialization for better initialization performance (see “Fault Tolerance Settings” on page 5-9). Configuring Array Write-Back Cache The write-back cache is an area that the controller uses to collect and store data from the host before writing it to the disk. Before the controller sends the data to the drives, the controller immediately responds to the host confirming the data was received and written to the disk (even though the data may have not been written to the disk). The host may then send more data. Write-back cache operations can significantly increase performance for host systems that only send a low number of commands at a time. The controller caches the data, and if more sequential data is sent from the host, it can cluster the writes together to further increase performance. If sufficient data is sent to fill a stripe in RAID 5, 6, and 50 configurations, the controller can perform a Full Stripe Write, which significantly reduces the write overhead associated with RAID 5, 6, and 50. Disabling write-back cache ensures that the data is sent to the drives before status is returned to the host. With write-back cache enabled, if a short term power failure occurs, the battery back-up unit provides adequate power to ensure that cache is written to disk when the power is restored. In duplex operations, the cache is mirrored to both controllers, which provides further redundancy in the event of a single controller failure. Mirrored cache is designed for absolute data integrity. The cache in each controller contains both primary cached data for the disk groups it owns, and a copy of the primary data of the other controllers. Mirrored cache ensures that two copies of cache exist on both controllers before confirming to the operating system that the write operation has completed. NOTE: A trusted array does not calculate parity across all drives and therefore there is no known state on the drives. As data is received from the host, parity is calculated as normal, but it occurs on a block basis. There is no way to guarantee that parity has been calculated across the entire stripe. The parity data may be inconsistent, so a drive failure within a trusted array may cause data loss. Before you use a trusted array in a live environment, you must initialize it. Normally, write-intensive operations benefit from the higher performance when write-back cache is enabled on an array. Read-intensive operations, such as a streaming server, may not benefit from write-back cache. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-6 ULTAMUS RAID 1200 User Guide Storage Solutions Initializing the Array Initializing an array clears all the data from the drives. This ensures the validity of the data and parity stored on the array drives. When the array is created, initialization automatically begins in the background. While initialization is in progress, logical drives can be created and the disks are made immediately available to the operating system where data can be loaded. As arrays are created and initialization begins, up to 64 arrays can be initialized in parallel (at the same time). As initialization proceeds, you can choose to stop or pause the process and then resume it at a later time. The controls for managing are displayed on the Main screen next to the array name after the initialization has started. If you Stop an initialization, the array will be automatically trusted. The Trust option (accepting an array without initialization) should only be used in testing environments. You should fully understand the consequences of the function before using it. IMPORTANT: The Trust option allows immediate access to an array for testing application purposes only and should NOT be used in a live environment. To initialize an array: 1. In the Main screen Array area, click the name of the array to be initialized. 2. From the Array screen Information tab (Figure 3-3), click INITIALIZE. Figure 3-3: ULTAMUS RAID Main Screen Prior to Initialization 3. Enter your password to confirm the initialization, and click GO. 4. At confirmation messages, click CLOSE. 5. Click CLOSE on the Array screen. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-7 ULTAMUS RAID 1200 User Guide Storage Solutions Monitoring Array Initialization You can monitor array initialization from the main screen. Place the mouse pointer over the progress bar to display the percent complete for the initialization progress. The drive member icons of this array animate to indicate initialization. To stop initialization, click the Stop link located to the right of the progress bar (not recommended). Pause/Resume Array Initialization You can temporarily pause the initialization process, and resume the process at a later time. • To pause initialization: Click the PAUSE link located to the right and below the progress bar. The PAUSE link changes to RESUME and the progress bar stops at its last position. • To resume initialization: Click the RESUME link located to the right and below the progress bar. Initialization continues from the point where it was paused. Setting Advanced Power Management Advanced Power Management brings 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 (see “Drive Power Management (APM Level 1)” on page 7-16) and the second is Array Power Management. 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. IMPORTANT: You cannot enable APM features on logical drives and their arrays that are also being controlled by the Snapshot feature. You must disable Snapshot to utilize APM. The information displayed across the bottom of the page is the time the page loaded, and is designed to help you manage real time data for an 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. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-8 ULTAMUS RAID 1200 User Guide Storage Solutions To configure APM level 2: 1. From the Main screen (Figure 3-4), click the name of the array you wish to set or manage APM policies. Figure 3-4: Select Array from Default Screen 2. From the Array Information window, click the POWER MANAGEMENT tab located at the top of the screen 3. At the configuration screen (Figure 3-5), choose the APM settings: a b c Figure 3-5: Power Management Screen a. If not already enabled, click the check box next to “Advanced Power Management.” b. Use the drop down menus to select: • Idle Time to Array Spin-Down time period • Number of interval days and/or hours before the next APM test c. Click the APPLY button. 4. At the successful configuration message, click CLOSE to return to the Array Information window. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-9 ULTAMUS RAID 1200 User Guide Storage Solutions NOTE: To manually spin up or spin down an array, click the appropriate button located near the bottom of the POWER MANAGEMENT page. APM Characteristics 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, 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. IMPORTANT: 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 reissue the commands once the drives are spun up and back online. Adding Hot Spare Drives Hot-swappable spare disk drives are supported. In the event of a drive failure, the controller uses either a global spare or a dedicated spare to replace a failed drive that is a member of a fault tolerant array. The process of configuring redundant arrays includes assigning drives as global spares and/or as dedicated spares. Global spares are not assigned to a specific array. They can be used by any array as the replacement drive as long as the size is equal to or greater than the drive it is replacing, and the types are the same (for example, all SAS or all SATA). A dedicated spare is assigned to a specific array and can only be used by that array. It should be the same size or greater than the drives that comprise the array, and it must be the same type. NOTE: You cannot mix SAS and SATA disk drives in the same disk array. If you intend to have a Hot Spare disk drive and you have a mixture of SAS and SATA drives in the enclosure, each array of either SATA or SAS drive types must have a dedicated spare of like type. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-10 ULTAMUS RAID 1200 User Guide Storage Solutions Assigning a Global Spare 1. From the Main screen, click an Available drive icon (Figure 3-6) within the enclosure front view for the drive you want to make a global Hot Spare. Figure 3-6: Select an Available Drive NOTE: There must be at least one drive on line and available to be assigned as a Hot Spare, and a configuration must exist (at least one array defined). You must use the same drive type as that used to define the array. 2. From the Drive Information screen, click Make Spare. Figure 3-7: Drive Information Screen 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-11 ULTAMUS RAID 1200 User Guide Storage Solutions 3. Select Global Spare from the drop-down menu on the Make Spare screen (Figure 3-8). Figure 3-8: Make Spare Popup Screen with Global Spare 4. Click CREATE to make the global spare. 5. Click CLOSE on the confirmation screen. 6. Click CLOSE on the Drive Information screen. Assigning a Dedicated Spare 1. From the Main screen, click an Available drive icon within the enclosure front view for the drive you want to make a dedicated Hot Spare. NOTE: There must be at least one drive online and available to be assigned as a Hot Spare, and a configuration must exist (at least one array defined). You must use the same drive type as used to define the array. 2. From the Drive Information window, click Make Spare. 3. From the drop-down menu, select the array to which you want to assign the dedicated spare (Figure 3-9). Figure 3-9: Select an Array for Dedicated Spare 4. Click CREATE to make the dedicated spare. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-12 ULTAMUS RAID 1200 User Guide Storage Solutions 5. Click CLOSE on the confirmation screen. 6. Click CLOSE on the Drive Information screen. NOTE: Only arrays with the spare drive large enough to replace any failed member drive of an array are displayed in the pull down menu. For example, if you have two arrays, one created using 10 GB drives (array 0) and one using 30 GB disk drives (array 1), and you have a 20 GB spare drive that you are attempting to assign to an array, only array 0 will be displayed because the drives in array 1 are greater capacity drives (30 GB) than the spare (20 GB). However, if you have a 40 GB spare drive, both array 0 and array 1 will be displayed since the 40 GB spare size is equal to or greater than the drives in either array. Removing a Spare This operation removes the designation of the drive as a global or dedicated spare. The drive then becomes online and available for other uses. 1. From the Main screen, click on a Dedicated or Global Spare disk drive in the enclosure front view that you want to remove as a spare. 2. In the Drive Information screen, click Remove Spare. 3. Click CLOSE on the confirmation screen. 4. Click CLOSE on the Drive Information screen. Auto Spare Option The Auto Spare option causes a replacement disk drive, when inserted, to be used as a dedicated Hot Spare for the failed drive and its array. When a new drive is inserted in place of the failed drive, a rebuild operation begins automatically using the new drive. This option is useful when a global or dedicated Hot Spare drive is not assigned and you have a fault tolerant array that experiences a drive failure. This option allows you to insert a replacement drive and begin a rebuild, instead of opening the Drive panel for the replacement disk drive and assigning it as a Hot Spare. To enable the Auto Spare option: 1. Click Advanced Settings on the Main screen Toolbar. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-13 ULTAMUS RAID 1200 User Guide Storage Solutions 2. On the Advanced Settings screen (Figure 3-10), check the Auto Spare box. Figure 3-10: Advanced Settings Screen with Auto Spare 3. Click APPLY. 4. When the confirmation screen appears, click CLOSE. 5. On the Advanced Settings screen, click CLOSE. Creating the Logical Drive To complete your storage solution configuration, you must create one or more logical drives. During creation, you assign a LUN (logical unit number) to the logical drive. This identifies the logical drive to the host operating system. Up to 512 logical drives are supported. A logical drive is defined or created from regions of an array, a whole array, or a combination of regions of different arrays that can be made available as a single disk to one or more host systems. IMPORTANT: If you are creating a logical drive greater than 2,198GB (2TB), see your operating and file system documentation to verify that the operating system supports such sizes. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-14 ULTAMUS RAID 1200 User Guide Storage Solutions To create a logical drive: 1. Click Create Logical Drive on the Toolbar (Figure 3-11). Figure 3-11: Creating a Logical Drive 2. Follow the numbered options on the Create Logical Drive screen (Figure 3-12): Figure 3-12: Create Logical Drive Screen a. Select the region or regions you want to use for your logical drive from the list Select which Arrays to use list. Hold down both the or keys to make multiple selections. NOTE: Avoid assigning combinations of regions from different arrays to create your logical drive to reduce data fragmentation. b. Enter a Name for your logical drive from 1–32 characters in length. The default names for logical drives follow the format LDx. Only 12 characters plus an ellipse are displayed when the name is longer. Holding the mouse pointer over the logical drive name on the Main screen shows the complete name in a tool tip. c. Enter the Size in GBs for the logical drive capacity. The maximum size is displayed to the right of the Size field. You can use all or some of these regions for this logical drive. Remember to check the operating system documentation if you create a logical drive greater than 2TB to verify that files that size are supported. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-15 ULTAMUS RAID 1200 User Guide Storage Solutions IMPORTANT: If you intend to make your Snapshots available as logical drives (Virtual LUNs), you must SAN LUN map all logical drives. That includes regular logical drives and snapshot (virtual) logical drives. Any settings made in the Create Logical Drive screen regarding Availability are overridden by the SAN LUN mapping process. d. Choose the desired Block Size. (With this release, only the 512 byte block size selection is available.) e. Select the LUN for the logical drive from the Mapped to drop-down menu. f. Under Availability, check the boxes for the Controller Ports for this drive. If a logical drive is to be seen on all controller ports and to all host HBAs, then check the boxes for both Controller Port 0 and Port 1; otherwise, check the box for the appropriate controller port. It is important to understand the cabling configuration topology you selected during your hardware setup. Refer to the hardware topology for the storage system to ensure you assign your logical drives to the correct port. g. Click Create to finish creating the logical drive. 3. At the confirmation screen, click CLOSE. NOTE: If the command was unsuccessful, review the settings for incorrect parameters and hardware for operational status. 4. To create more logical drives, repeat Steps 2–3. 5. Exit by clicking CLOSE. In most storage system environments, creating the logical drives, assigning them their logical unit number (LUN), and setting the availability is sufficient to meet the requirements for setup. For more advanced and complex systems using storage area networks, you can perform the more advanced SAN LUN mapping (see “SAN LUN Mapping” on page 4-1). Otherwise, access your operating system to make the new drives available for use. Saving the Configuration When you create or make changes to arrays, logical drives, Hot Spares, SAN LUN mappings, or snapshots, or change specific controller setting parameters, a file is written (known as the configuration) to all the disk drives that are members of the array. ULTAMUS RAID manager can capture the configuration and allow you to save it to an external file. IMPORTANT: It is recommended that you periodically save the configuration to an external file. You can use the external file to restore the configuration, if necessary. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-16 ULTAMUS RAID 1200 User Guide Storage Solutions CAUTION: The configuration must be restored exactly as it was. If not, the data and all access to it will be lost. 1. From the Main screen Toolbar, click Archive Configuration. 2. Click SAVE on the Configuration Archival Operations screen. The Save Configuration Operation message dialog appears (Figure 3-13). Figure 3-13: Save Configuration Operation Message Screen 3. Click DOWNLOAD to continue saving the configuration file (or click CLOSE to cancel). The standard File Download screen is displayed. 4. Click Save to continue, or Cancel to quit. 5. On the Save As screen, choose to either: • Save to a default name by selecting the appropriate directory. • Enter the name you want to use and specify the directory. 6. Click Save. 7. At the successful download message, click CLOSE. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 3-17 SAN LUN Mapping CHAPTER 4 Overview When attaching more than one host system to a storage system, it may be necessary to more precisely control which hosts have access to which logical drives. In addition to controlling availability on a controller port by port basis, it is also possible to further restrict access to a specific host system or single adapter in a host system by the use of SAN LUN Mapping. Up to 512 SAN LUN Mappings are supported. Terminology “Used in another Mapping” marks a logical drive that has been mapped to another Host HBA Port, but is available to be mapped to the selected Host HBA Port. It is displayed when the condition above has occurred and appears in the logical drive pull-down menu selections. The logical drives with other mappings have an asterisk (*) next to the name. SAN LUN Mapping Access Click the SAN Mapping icon in the Toolbar to view the SAN LUN Mapping screen. Figure 4-1: SAN Mapping Icon on Toolbar The mapping screen presents a list of the specific host HBA ports and their mapping details. You can view, name, create and remove mappings from this screen. Selecting an HBA Port Name displays its current mappings and parameters (see “Overview: SAN LUN Mapping Window” on page 4-2). The SAN LUN Mapping screen is divided into two primary sections: Topology Information and mapping tools. The Topology Information section displays the list of discovered Host HBAs and the mapping information related to the selected host port or HBA Initiator ID. This information includes the LUN (logical unit number) 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 4-1 ULTAMUS RAID 1200 User Guide SAN LUN Mapping assigned to the logical drive, read/write permissions, the controller port for the connection, and the logical drive’s name. The second section, displayed on the bottom of the screen, provides tools for adding, modifying and deleting SAN LUN Mappings. Overview: SAN LUN Mapping Window Figure 4-2 illustrates the components of the SAN LUN Mapping screen. The blue lines in the diagram represent the physical cable connection from the host HBA port to the enclosure’s RAID Controller I/O ports. HBA WWN / Port WWN of the selected HBA Port Select and Name the HBA Ports in this section Graphical view of the physical connection of the selected host HBA port. Add SAN LUN Mappings in this section View existing mappings and details in this section Figure 4-2. SAN LUN Mapping Screen Sections The SAN LUN Mapping screen is divided into three primary sections. The first section on the left side of the screen, contained in the box titled SELECT YOUR HBA, displays the list of discovered Host HBAs and the current mappings for that selected port name. The second section, displayed beneath the HBA and graphical representation of the enclosure, provides tools for adding and modifying SAN LUN Mappings. The third section, at the bottom of the screen, displays current mappings and provides a method of deleting SAN LUN Mappings. SELECT and NAME YOUR HBA PORT Sections This section of the screen provides a list of the discovered named and unnamed fiber channel HBA Ports. The identity of a selected HBA Port, including its HBA Node WWN and HBA Port WWN, appears above the enclosure graphic. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 4-2 ULTAMUS RAID 1200 User Guide SAN LUN Mapping You must select a port in the SELECT YOUR HBA PORT section and identify it in the area above the enclosure graphic by the Node and Port WNNs. To give the port a name, enter a user-defined name in the Name Your HBA Port field. The new name is entered in the list of HBA Ports as you type it into the field. The name can consist of up to 32 characters, though only 11 are displayed. ADD MAPPINGS Section In this section, you locate the logical drive to which you will be mapping, assign a LUN (logical unit number) to the logical drive, set the permissions of the mapping, and select which ports or channels of the controller you want the logical drive to be seen on. To add the mapping, click the “plus” icon on the right. The Advanced Options include the Host Port selections: C0P0, C0P1, C1P0 and C1P1. C0 represents the lower controller and C1 represents the upper controller, and P0 represents Host 0 and P1 represents Host 1. Choose the ports where you want the logical drive to be seen and to which you have cables connected. NOTE: If you want to modify an existing mapping, you must first delete the mapping, then re-create the mapping with new parameter settings. MAPPINGS Section This section lists existing mappings with their details. The mapping list displays the LUN number assigned, the logical drive name or number, the controller and ports on which it is available, and permissions for each mapping. You can remove a mapping by clicking the minus icon next to the mapping. If a conflict occurs between these mappings, it is possible to disable the Controller LUN by checking the box, Disable Controller LUN. Example of Failover Mapping (This option is not applicable to switch configurations.) In an Active-Active configuration, you could set up a failover mapping where one Host HBA Port is connected to the Host 0 port on the controller and the other Host HBA Port is connected to the Host 1 port on the controller. When a failover condition occurs, the hardware re-routes the connection. To see the results, click the HBA Port that you mapped for the failover condition. You can see that the mapping is now on this port and not on the failed port. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 4-3 ULTAMUS RAID 1200 User Guide SAN LUN Mapping Creating a SAN LUN Mapping The following are the steps to create a SAN LUN Mapping. The process involves identifying the Host Port, creating a user defined name, assigning your mapping a LUN number, establishing the access permissions, and selecting the controller port to make available the mapped logical drive. IMPORTANT: If you intend to make your Snapshots available as logical drives (VLUNs), you must SAN LUN map all logical drives. That includes regular logical drives and the Snapshot logical drives. 1. From the Toolbar, click SAN Mapping. 2. Under Select Your HBA, select an unnamed port. Identify it using the displayed HBA Node WWN and HBA Port WWN displayed above the enclosure graphic. 3. Enter a name for the HBA Port, if needed, in the Name Your HBA Port field. The name displays in the HBA Port list to the left. You may use up to 32 ASCII characters to name the HBA port. Figure 4-3: SAN LUN Mapping Screen 4. In the ADD MAPPINGS section, do the following: a. Select an available Logical Drive Number (LUN) from the pull down menu. The Host sees this LUN as the logical drive. Default logical drive names are LUN 000 through LUN 511. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 4-4 ULTAMUS RAID 1200 User Guide SAN LUN Mapping b. Select the logical drive to which you want to map. Click the pull down menu and choose from the list of logical drives displayed. Default logical drive names are LD1, LD2, LD3, etc. Logical drives marked with an asterisk (*) indicate that another mapping for another Host HBA has been established for this logical drive. You can map it again to additional HBAs but know that all Host HBAs mapped to this logical drive see and have access to this logical drive. c. Select an access permission for the mapping. Choose from the drop-down menu: Read/Write, or Read Only. NOTE: Microsoft Windows does not support Read Only permissions. d. Select the Host Port/Channel. Click the check box(es) for the ports where the mapping is to be available: C0P0, C0P1, C1P0, and/or C1P1. C0 represents the lower controller and C1 represents the upper controller. P0 indicates the port marked Host 0, FC Host 0, or IN 0, and P1 represents the port marked Host 1, FC Host 1, or IN 1 on each controller. Choose the ports you want the logical drive to be seen on and to which you have cables connected. If you select all, the mapping is available to all Host ports connected to the selected connectors. e. Review the settings and click the + icon (plus sign) to add the mapping. Follow Step 4 to add as many mappings as needed. 5. (Optional) If there are drive conflicts, check the Disable Controller LUN box in the MAPPINGS section. 6. Click APPLY to save and use these settings. 7. At the confirmation message, click OK to continue, or click CANCEL to return to the screen. 8. If you click OK, then click CLOSE in the confirmation screen. Deleting a SAN LUN Mapping NOTE: Prior to deleting SAN LUN Mappings, clear your web browser's cache (With Internet Explorer delete the Temporary Internet Files); then, proceed with removing the mappings. 1. From the Toolbar, click SAN Mapping. 2. Select the Host HBA port that contains the mapping to be removed. 3. In the Mappings section, click the – icon (minus sign) to the right of the Mapping to be removed. 4. Click APPLY. 5. At the confirmation screen, click OK to continue, or CANCEL to exit and return to the SAN LUN Mapping window. If you click OK, then click CLOSE in the confirmation screen. 6. You can continue to remove more mappings by repeating Steps 2– 5, or click CLOSE to end the session. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 4-5 ULTAMUS RAID 1200 User Guide SAN LUN Mapping Modifying a SAN LUN Mapping In order to make changes to an existing SAN LUN Mapping, you must first remove the existing SAN LUN Mapping and then re-create it with the changes. CAUTION: Making changes to these mapping parameters may have an adverse affect on other mappings or to the operating system accessing the logical drive. 1. From the Toolbar, click SAN Mapping. 2. Select a Host HBA port under SELECT YOUR HOST HBA that contains the mapping to be modified. 3. Select the mapping to be modified from the MAPPINGS section. NOTE: Make a note of the settings for this mapping to use in step 6. 4. Click the – icon (minus sign) to the right of the mapping to be removed. 5. At the confirmation message, click OK to continue (or CANCEL to exit). 6. Add the new mapping. Follow the procedures to add a new mapping and refer to your notes from the existing mapping to help create the new mapping. For specific details, see “Creating a SAN LUN Mapping” on page 4-4. Use your notes from the previous mapping as a guide. Essentially, you want to re-create the mapping, but with different settings. For example, you may want a different logical drive, a new LUN, different permissions and/or different controller host ports. 7. Click APPLY to save your changes. NOTE: If you want to cancel your changes before you click APPLY, click CANCEL. The changes will be cleared, restoring the previous settings. 8. At the confirmation screen, click OK to continue, or CANCEL to exit and return to the SAN LUN Mapping window. 9. Click CLOSE to exit. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 4-6 CHAPTER 5 Controller Management Overview The Controller information screen provides an instant view of the health status of the RAID Controller components and tool tips with detailed information about the items listed in the Status section. In this screen, you can update the controller firmware, synchronize the date and time, reset or shut down RAID Controllers, and manage event log files. The Advanced Settings allow you to make changes to the controller parameters to optimize the system for your application. Controller Information Access To view and manage controller environmental conditions, click the Controller icon (Figure 5-1) located just above the Toolbar. Figure 5-1: Location of the Controller Icon The Controller icon on the Main screen flashes red when a problem exists with the controller, indicating a status change – either error (failure) or warning. If this occurs, click the icon and investigate the problem from the information provided. You can investigate the Event log to verify the event that changed the controller status. When the Controller Information screen opens (Figure 5-2 on page 5-2), the controller’s status is displayed using status icons and a text message. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-1 ULTAMUS RAID 1200 User Guide Controller Management When the mouse pointer passes over each item in the Status group (controller, battery, temperature, and voltage), a tool tip appears with specific, detailed data. Figure 5-2: Controller Screen Displaying Data in Tooltip Status The Status group of items are specific to the functional status of the RAID Controller. They include general controller status, battery status, temperature of the controller, and voltage status. Placing the mouse pointer over the item displays a pop-up window with more detailed information. In the illustrated example, the mouse pointer is over Voltage so the voltage data is displayed. Status icons appear adjacent to the item in the group along with a text message. Status icon and text message conditions are defined as green – normal, yellow – warning, and red – failed. Hardware/Firmware Hardware/Firmware items display the controller's physical memory and firmware. From this group you can determine the type of processor and onboard memory size, the firmware version, and the CPLD (Complex Programmable Logic Device) firmware version. You can also see each controller’s actual WWN. Configuration The Configuration group identifies the WWN assigned to the entire configuration, the speed of each port and the LUN assigned to the port. The configuration can be assigned the WWN of any controller, preferably one of the controllers installed in the enclosure. For more information on the configuration WWN and port LUN assignment, see “Identity” on page 5-7. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-2 ULTAMUS RAID 1200 User Guide Controller Management Operations The Operations items allow you to reset and shutdown each controller individually, update the controller firmware (see “Update Controller Firmware” on page 5-4), reset both controllers, shutdown both controllers (hard shutdown), export the controller logs, and clear the log files. Reset or Shut Down a RAID Controller • Click Reset to cycle the power, or restart, a controller. The controller is not in service while the power is being cycled, but resumes service when it comes back up. • Click Shutdown to gracefully shut down the controller. The controller will no longer be in service after the shutdown. CAUTION: Before shutting down the RAID Controllers for an extended period of time, verify that the Cache Active LED on the RAID Controller is not illuminated. An illuminated LED indicates that the RAID Controller is holding data in the cache. If the Cache Active LED is illuminated, wait until the controlling application has completed writing the data to the disk before continuing with the shutdown. This ensures that the backup battery is not holding cache data and prevents the battery from being drained. Log Files and Diagnostic Dumps You can export a controller’s log to a Comma Separated Values (.csv) file for later analysis. Click Export Logs to export the logs to your local machine. If you click Clear Logs, all event logs are removed from the controller’s memory. If you need these logs for any reason prior to clearing, export them before clearing them. Diagnostics Dump enables you to dump the controller's diagnostic information into a LOG file for use with technical support when troubleshooting a problem. The LOG file is a standard text file. Synchronize the Time If you want the time on the controller to match the time on your local computer, click Synchronize Time. The controllers quickly synchronize with the local computer. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-3 ULTAMUS RAID 1200 User Guide Controller Management License Information Click License Information to view information about the current license, or to enter a value for the Snapshot license key (Figure 5-3): Figure 5-3: License Information Screen NOTE: A license key cannot be assigned without a valid array. The information screen lists the licensed limits for the number of Overwrite Data Areas and Snapshots per Logical Drive, and lists the configuration WWN. Before you can use the ULTAMUS RAID 4800, you must register it and the Snapshot component. To activate the Snapshot component, you must apply for the activation code, and then register the Snapshot component. The Snapshot component license key is sent to you via e-mail message, following component registration. NOTE: The activation code is sent within 2–3 business days. To submit a license key for the snapshot component, enter the new Snapshot license key in the License Key field and click Submit License Key. When the license key is displayed in “Current License Key,” your Snapshot component is active. Update Controller Firmware In dual controller configurations, a controller can automatically update its partner’s firmware; however, the update process behaves differently under certain conditions. If one controller has a later version of firmware than its partner controller, the later version firmware controller automatically updates the firmware on the lower version controller during the startup process. If a partner controller fails in a dual controller configuration, and the failed controller is replaced, the replacement controller is always updated to match the surviving controller’s firmware, regardless of its firmware version. If you want to downgrade the firmware version, you must shut down one controller and flash the operating controller. Then, shut down the controller that was flashed, bring the second controller up, and flash its firmware to the lower version. Start both controllers again to resume operations. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-4 ULTAMUS RAID 1200 User Guide Controller Management Controller firmware on the enclosure is updated separately from the Disk I/O module firmware on the expansion enclosure. The procedure is the same, except that for the expansion enclosure, you update the Disk I/O Module’s firmware. 1. Click the Controller icon located just above the Toolbar. 2. On the Controller Information screen, click UPDATE CONTROLLER FW (Figure 5-4). If you are updating the Disk I/O Module firmware on the expansion enclosure, click UPDATE EXPANSION FW. Figure 5-4: Update Firmware on Controller Information Screen 3. Locate the appropriate firmware file on your local drive and click Browse (Figure 5-5). The file name resembles: 18-1-98104001.bin. The update file is available from the customer service representative or technical support. Figure 5-5: Update Firmware Controller 4. After you locate the file, click UPLOAD. The confirmation screen appears and indicates the status of the update. When the update completes, the controller automatically restarts. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-5 ULTAMUS RAID 1200 User Guide Controller Management Advanced Settings The Advanced Settings allow you to make changes to the controller parameters to optimize the system for your application. CAUTION: The settings on this screen can significantly alter your system’s configuration. Alter these settings only when necessary. Click the Advanced Settings button in the Toolbar (Figure 5-6). Figure 5-6: Location of the Advanced Settings Icon The Advanced Settings window is displayed (Figure 5-6). Figure 5-7: Advanced Settings Screen The Advanced Settings window is divided into three sections: • Identity • Fault Tolerance • Host Ports From this window you are able to make changes to controller specific parameters, enable or disable Fault Tolerant features, and configure the controller’s host ports. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-6 ULTAMUS RAID 1200 User Guide Controller Management Identity In the Identity section (Figure 5-8), you can change the Configuration Name, assign the configuration the WWN of either controller, and set the controller LUN. Figure 5-8: Identity Section of the Advanced Settings Screen This table describes the settings in the Identity section: Setting Description/Usage Configuration Name The name you assign to the configuration. To change the configuration name, enter the new name in the block provided and click APPLY. Configuration WWN The main RAID Controller's WWN, which is used to uniquely identify the storage solution to the outside world. See ““The Configuration WWN” on page 5-8. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-7 ULTAMUS RAID 1200 User Guide Controller Management Setting Description/Usage Controller LUN The controller’s Logical Unit Number (LUN). You can set or disable the Controller LUN. By default, the Controller LUN is automatically assigned the next number after the last logical drive number. If your operating system is having a problem with the displayed Controller LUN, select Disabled. Different Node Name Allows the controller to report a different Configuration WWN for Port 0 and Port 1 (Host 0 and Host 1 connectors). When this box is not checked (default), a host connected to either port sees the Configuration WWN. When selected, each port displays a slightly different WWN, but the same Configuration name. This option is useful for those who are connecting the storage to a switch employing a fabric topology, where the same WWN is not tolerated. The Configuration WWN The WWN, is the 8-bit unique identifier assigned to a fibre channel controller by its manufacturer. Each RAID controller has a unique WWN. The configuration of your storage solution is also assigned a WWN. This Configuration WWN is the name reported to the outside world for the storage solution, regardless of which port the controller is using. By default, the WWN for the controller used to create the configuration is assigned as the Configuration WWN. If you must swap the controller (most likely because of controller failure), your storage solution still reports the same Configuration WWN. In this case, you must assign the Configuration WWN to the newly installed controller to maintain current mapping assignments To assign the configuration WWN to the installed controller: 1. On the Advanced Settings screen, select Controller 0 or Controller 1 from the Configuration WWN drop-down list. 2. Click APPLY. 3. Restart the ULTAMUS RAID manager. If you reassign the WWN to another controller, you must restart the controllers and any connected hosts for the new setting to take effect. CAUTION: If you are using the Snapshot feature, your feature license key is based on the Configuration WWN, which is based on the RAID Controller’s WWN used at the time of licensing. If you modify the Configuration WWN, the feature license key is no longer valid and the snapshot function is disabled. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-8 ULTAMUS RAID 1200 User Guide Controller Management Fault Tolerance Settings In the Fault Tolerance section, you can enable or disable controller features that improve the controllers abilities to maintain a level of fault tolerance. Figure 5-9: Fault Tolerance Section of Advanced Settings Screen This table describes the settings in the Fault Tolerance section. 10400166-102 09/2008 Setting Description/Usage Auto Spare Check this box to allow data to be rebuilt on a new drive inserted into the same slot from which a failed drive was removed. This is beneficial when a hot spare or global spare is not designated for a fault tolerant array and a drive fails in that array. Auto Rebuild Check this box to start a rebuild operation automatically when a fault-tolerant array loses a drive member and a replacement or hot spare drive is available and online. When you assign a hot spare (dedicated or global) this option is automatically enabled. After creation of the hot spare, the option can be disabled if desired. Single Controller Mode Check this box when operating in the StandAlone mode (single controller configurations), to keep the controller from constantly checking for a partner controller. When operating a duplex ActiveActive configuration, uncheck this box. ©2007,2008 Overland Storage, Inc. W 5-9 ULTAMUS RAID 1200 User Guide Controller Management Setting Description/Usage Background Drive Verification Check this box to automatically verify the media of all drives in the background. If a media error is detected, the controller can automatically re-write the data, providing that the array is in a fault tolerant mode. This process occurs in the background when microprocessor time is available, and is suspended when processor time is not available. Auto Update Drive Firmware Check this box to allow automatic update of the disk drive firmware when a drive has been updated using the VT-100 menu based system. Any time a matching drive identical to the drive you updated in the system is discovered, it automatically updates the firmware for those drives. ULTAMUS RAID manager displays an icon that the firmware is being updated in the enclosure front view graphical display on the Main screen. Enclosure Support Check this box to monitor the enclosure components. If you uncheck the box, ULTAMUS RAID manager does not report the enclosure status or enclosure events, and the image on the Main screen is greyed out. This does not disable the audible alarm. Rebuild Priority Select a value to determines the amount of processor time allocated to the Rebuild operation. The higher the value, the more time the processor spends on the rebuild operation, reducing the time to complete the operation. This priority must be balanced with the initialization priority in the event that a rebuild and an initialization occur simultaneously. Initialization Priority Select a value to determine the amount of processor time allocated to initialization The higher the value, the more time the processor spends on the initialization operation, reducing the time to complete the operation. This priority must be balanced with the rebuild priority in the event that a rebuild and an initialization occur simultaneously. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-10 ULTAMUS RAID 1200 User Guide Controller Management Host Port Settings In the Host Ports section, you can change the LUN (ID) assigned to each of the RAID controller ports, set the data rate, and adjust the type of connection. Figure 5-10: Host Ports Section of the Advanced Settings Screen This table describes the settings in the Host Ports section: Setting Description/Usage Controller Port ID (P0) Set the target ID for both controllers’ port 0. You can set the value to Soft Address, which will assign a value, or to a value in the range 0– 125. The default value is 4. Controller Port ID (P1) Set the target ID for both controllers’ port 1. You can set the value to Soft Address, which will assign a value, or to a value in the range 0– 125. The default value is 5. NOTE: The ports are identified in the software as P0 and P1, they refer to the label on the RAID Controller that indicates Host 0 and Host 1 connectors respectively. Controller 0 is the controller on the left and Controller 1 is the controller on the right as you look at the rear of the enclosure. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 5-11 ULTAMUS RAID 1200 User Guide Setting Controller Management Description/Usage Controller Port Data Use the Automatic setting for most configurations. If you use a Rate specific setting (1GB, 2GB, or 4GB) you override the automatic setting. IMPORTANT: Make sure this software setting matches the hardware switch setting on the HBA ports. NOTE: When using an Active-Active configuration (dual controllers) set the Controller Port Data Rate to a predetermined speed. When the Automatic setting is used with Active-Active, it is possible for the speed to step down to 1GB during a failback operation. For 2GB or 4GB operations, manually setting the speed prevents this from happening. Connection 10400166-102 09/2008 Set the type of connection that is used by the host or switch. Use the Automatic setting for most environments, where the connection attempts to use Loop Only first and then Point to Point. For custom settings: • If you are connecting to a FL_Port switch or NL_Port HBA, then select Loop Only. • If you are connecting F_Port switch or N_Port HBA, then select Point to Point. ©2007,2008 Overland Storage, Inc. W 5-12 Daily Operations CHAPTER 6 This chapter addresses failover, performance, statistics, and additional functions. How ULTAMUS RAID manager Server Failover Works The RAID module failover feature must have dual controllers installed (duplex topology), with ULTAMUS RAID manager software installed on each controller. At startup, each URM server component creates a device list of all the attached storage systems. It then sends the list out on the network as a device list packet. The other URM servers on the network then respond with their device list packets. Since the URM servers are attached to the same storage solution, they will have the same or similar devices in their device list packet. The identical devices in each device list packet are flagged. After analysis, the URM server with the lowest serial number or address will take control of those devices. The other URM servers indicate on their interfaces that another URM server is monitoring the storage solution. During normal operations, the URM servers send check-in packets every 10 seconds. If three consecutive check-in packets for a specific URM server are not received, its devices are flagged and the URM server attached to that storage solution with the lowest serial number or address will take control of those devices. Performance Optimization The HBA Execution Throttle setting and the operating system's Scatter/Gather registry setting can be adjusted on the host HBA and operating system to increase performance. Execution Throttle To improve general I/O performance by allowing more commands on the fibre bus or the SCSI bus, change your host bus adapter’s execution throttle parameter to 256. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-1 ULTAMUS RAID 1200 User Guide Daily Operations Scatter/Gather (Microsoft Windows Only) To increase general I/O performance by allowing larger data transfers, edit the MaximumSGList parameter in the registry. The recommended hexadecimal value is “ff.” The path is: HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/ /Parameters/Device/ See your Microsoft Windows operating system documentation for more information on editing the registry, and your host HBA adapter documentation. Time-Out Issues In many cases, to resolve long time-out issues, you must adjust the SCSI time-out registry values. For the most general cases, a time-out value between 60 and 120 seconds should be fine; however, in the case of heavier workload, a value higher than 240 seconds should be set. For Windows platforms, the default is 60 seconds, and the time-out parameter is: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Disk/TimeO utValue For Linux platforms the default parameters are: 2.6 Kernel = 30 seconds 2.4 Kernel = 60 seconds Statistics ULTAMUS RAID manager and each RAID controller 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. The controller maintains individual access statistics for all logical drives, controllers, and individual or all ports. This information can be used to help balance the load from the host. You can also export the statistical data to a comma delimited file (.csv) for use in third-party software products. Access Statistics Statistics are kept for both reads and writes. You can use the information to tune the operating system for optimum performance. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-2 ULTAMUS RAID 1200 User Guide Daily Operations From the Toolbar, click Logical Drive Statistics. The Statistics screen is displayed defaulted to the Access tab (Figure 6-1). Figure 6-1: Access Statistics Screen 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. 10400166-102 09/2008 Statistic Description Reads 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. Writes 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. No. of Operations The total number of read and write accesses that have occurred since these statistics were reset, or the controller was last powered on. Bytes Transferred The total number of bytes read and written since these statistics were reset, or the controller was last powered on. ©2007,2008 Overland Storage, Inc. W 6-3 ULTAMUS RAID 1200 User Guide Daily Operations Command Size and Alignment Statistics Command size statistics express the percentage of commands whose size is specified for reads and writes. The Alignment statistics express the percentage of commands with addresses aligned on the specified address or chunk boundary (Figure 6-2). Figure 6-2: CMD Size/Alignment Screen with Read/Write Statistics Statistic Description Command Size 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 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. In an optimal system, a write of one chunk of data would reside exactly within a chunk on one disk. If this is not the case, the write is split up into two separate writes to two different data drives. Splitting the write can have a negative effect on performance. To overcome the performance issues, you can set the access size and alignment to optimal values. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-4 ULTAMUS RAID 1200 User Guide Daily Operations Using Command Size and Alignment Statistics To calculate the alignment, check the LBA for the largest number of blocks that evenly divide into it, in powers of 2. In this case, the alignment is 0x10 = 16 blocks, which is 8K. For example, consider a read or write command from a host system with Logical Block Address (LBA) 0x0000070, and access size 0x80, expressed as 128 in decimal. Using 512 byte blocks on the disk drives, the read is 64KB, which is the command size. The alignment and the access size indicate how many drives are involved in an access. In the this example, consider a RAID 5/50 array with a chunk size of 64KB. In this case, the above access involves 2 data drives, since it needs to access 8KB in the first drive (0x80 – 0x70 = 0x10 blocks = 8KB), and the remaining 56KB in the next drive (0x70 blocks = 56KB). This is inefficient, and could be improved by setting the alignment to 64KB on the operating system. If that is not possible, using a larger chunk size can help by reducing the number of accesses that span chunks. Aligning an access on the same value as the access size improves performance because it ensures that there are no multi-chunk accesses for commands that are smaller than a chunk size. Read-Ahead Statistics If sequential read commands are sent to the controller, it assumes that the commands that 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 6-3): Figure 6-3: Read Ahead Statistics Screen 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-5 ULTAMUS RAID 1200 User Guide Daily Operations Statistic Description Sequential Command Interval In determining whether or not to perform a read-ahead, the controller searches 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 multithreaded operating system, commands from one thread may be interspersed with commands from another thread. The controller then checks more than just the immediately previous command, but searches 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 statistics indicate the multithreaded nature of the host. Read-Ahead Command Hit Rate This is the percentage of read command hits versus the total number of read commands that have been issued. These statistics indicate the sequential nature of the data access pattern from the host. Read-Ahead Command Efficiency 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 readahead command is not actually requested by the host. 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 arrays. In cases where the host does not send a sufficient number of outstanding writes, write-back cache can be used to delay the write to disk, increasing the likelihood of clustering more data. Command cluster statistics are also captured by the controller (Figure 6-4 on page 6-7). 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-6 ULTAMUS RAID 1200 User Guide Daily Operations Figure 6-4: The Command Cluster Statistics Screen 10400166-102 09/2008 Statistic Description Write Cluster Rate 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. RAID 5/50/6 Full Stripe Write Rate 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 write-back cache, for RAID 5/50/6 arrays. Command Cluster Count When the controller clusters a write command, it may cluster a large number of them together. These statistics record the average and maximum number of commands the controller clusters, and also the percentage for each one of these values. ©2007,2008 Overland Storage, Inc. W 6-7 ULTAMUS RAID 1200 User Guide Daily Operations Statistic Description Command Cluster Interval In determining whether or not to cluster write commands, the controller searches back in the command queue whenever it receives a new write command. In a multithreaded operating system, commands from each thread may be interspersed with commands from another thread. The controller then checks more than the immediately previous command, but searches back for a number of commands 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 when it finds a sequential command match, and the percentage for each of these values. Additional ULTAMUS RAID manager Functions About The About screen displays software version information and allows for an update of the ULTAMUS RAID manager software. From the Main screen, click the About button, located in the upper right corner of the window under the ULTAMUS RAID manager logo. The About window is displayed. The license type for this installation is indicated below the version number in parenthesis. Figure 6-5: ULTAMUS RAID manager About Screen Take Control Monitoring When multiple host servers are physically attached to the same storage system or the hosts are attached to a fibre switch in which the switch is physically attached to the storage solution, the installed ULTAMUS RAID manager server with the lowest serial number or IP address will take control of those devices. serial number or IP address takes control of those devices. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-8 ULTAMUS RAID 1200 User Guide Daily Operations If you want to take control of the storage solution from another ULTAMUS RAID manager server, click Take Control from the Main screen message displayed on that ULTAMUS RAID manager server (Figure 6-6). Figure 6-6: Take Control Link ULTAMUS RAID manager performs a scan and reloads the configuration for this system. The ULTAMUS RAID manager Server that previously had control now displays the message that the selected storage solution is being monitored by another ULTAMUS RAID manager server. You also see this condition if this ULTAMUS RAID manager server fails to send the required three consecutive check-in packets and it fails over to another ULTAMUS RAID manager server attached to the same storage system. When the problem is resolved on this host ULTAMUS RAID manager server, you can take back control again with that server. Rescan Rescan forces a search of the network to re-discover storage solutions. This action refreshes the display and updates status information. From the Main screen, click RESCAN, located in left panel of the screen. A rescanning message (Figure 6-7) replaces the Main screen. After a few moments, the Main screen is re-displayed with updated information. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-9 ULTAMUS RAID 1200 User Guide Daily Operations Figure 6-7: Rescanning to View All Arrays 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 6-10 Advanced Functions CHAPTER 7 Advanced Drive and Array Functions Using the advanced functions of the ULTAMUS RAID 1200, you can view specific drive information and make changes to drive parameter settings. From the Drive Information screen, you can also locate a drive and execute a rebuild operation. Accessing the Drive Screen To access drive information, click any disk drive icon displayed on the Main Screen in the enclosure front view (Figure 7-1). Figure 7-1: Accessing Drive Information on the Main Screen 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-1 ULTAMUS RAID 1200 User Guide Advanced Functions From the Drive information screen, you can locate a drive, make a spare, or rebuild a disk array (Figure 7-2). Figure 7-2: Drive Information Screen Locate Drive 1. Identify the drive displayed in the enclosure view and click that drive icon. 2. On the Drive information screen, click LOCATE. 3. From the drop-down menu on the Locate Drive screen, select the length of time required (30, 60, 90, or 120 seconds) to blink the Drive’s Activity LED. 4. Click LOCATE. Figure 7-3: Select Time Interval for Drive Activity LED 5. Identify the drive in the enclosure by its blinking Drive Activity LED. See the ULTAMUS RAID 1200 Hardware Setup Guide on your CD for details on drive LEDs. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-2 ULTAMUS RAID 1200 User Guide Advanced Functions Identifying Drive Members of an Array You can quickly identify which drives in the enclosure are members of a specific array. On the right side of any Array name on the Main Screen, there is a Drive Identity icon (that resembles an arrow pointing to the lower left). When you click the Drive Identity icon, all members of that array display the icon (Figure 7-4). The icon also appears next to each logical drive in that array. Drive Identity Icon Member Drives with Drive Identity Icon displayed Figure 7-4: Identifying Drives in an Array To physically locate a drive, see “Locate Drive” on page 7-2. Modifying an Array When an array is created and online, you can change: • The name of the array • The read-ahead and write-back cache parameters Figure 7-5 on page 7-4 shows the modifications you can make on the Array screen under the Information tab. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-3 ULTAMUS RAID 1200 User Guide Advanced Functions Figure 7-5: Make Modifications in the Array Information Tab NOTE: If the array was trusted or never initialized, you can initialize the array from this window by clicking INITIALIZE. If the array has been initialized, RE-INITIALIZE.is displayed. 1. From the Main screen Configuration section, click the array to be modified. 2. When the Array screen opens showing the Information tab, type a new name for the array in the Name field, and/or change the cache parameters. 3. To save and apply the modifications, click APPLY (or to restore the information and start again, click RESTORE). Verify Parity You should perform a parity check as a normal maintenance procedure to ensure data integrity. If a controller in a RAID 5, 6, and 50 disk array is replaced after the controller is powered off with write operations in progress, you may need to verify and correct the parity data on the array. 1. From the Main screen Configuration section, click the array to be modified. 2. When the Array screen opens showing the Information tab, click VERIFY PARITY. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-4 ULTAMUS RAID 1200 User Guide Advanced Functions 3. Select one of the options from the drop-down menu (Figure 7-6) and click VERIFY PARITY again. Figure 7-6: Verifying Parity 10400166-102 09/2008 Option Description Verify Parity Only 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 Reads all the data, calculates the XOR of the data, and writes this out as the new parity. This is the fastest option to complete, since it does not perform a comparison. Verify and Rewrite Parity Reads all the data and parity, calculates the XOR of the data, and compares it to the parity. If there is a discrepancy, it writes this out as the new parity and creates a log entry. This is the slowest option to complete, since it performs both a comparison and a rewrite. ©2007,2008 Overland Storage, Inc. W 7-5 ULTAMUS RAID 1200 User Guide Advanced Functions During verification, the drive members icons in the front enclosure view of the array are animated to indicate verification is in progress. Adjacent to the array name in the Main screen, the progress bar (Figure 7-7) indicates percentage complete. When you run the mouse pointer over the progress bar, a tool tip displays the percent complete value. Figure 7-7: Verification of an Array To stop verification, click the Stop link to the right of the progress bar. Rebuilding an Array Rebuilding an array is necessary if, for example, you pulled the wrong drive from a working array and that drive is now flagged as a failed drive. If you do not have a Hot Spare defined, the array does not automatically begin a rebuild operation. You must change the status of the flagged failed disk drive to a spare drive, which clears the condition and initiates a rebuild. The Rebuild Array option initiates a manual rebuild. NOTE: Only one rebuild can take place at a time. If a rebuild is currently underway, the second array scheduled for rebuild waits until the first array’s rebuild is completed. 1. From the Main screen, identify the failed drive displayed in the enclosure view, and click that drive icon. 2. On the Drive information screen, click REBUILD ARRAY (Figure 7-8). Figure 7-8: Rebuilding the Array 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-6 ULTAMUS RAID 1200 User Guide Advanced Functions 3. From the Rebuild Array pop-up screen (Figure 7-9), select from the drop-down menu the specific array that became critical and click REBUILD. Figure 7-9: Popup Screen for Rebuilding the Array 4. At the confirmation screen, click CLOSE. 5. Click CLOSE to exit the Drive information screen. IMPORTANT: For a RAID 6 rebuild operations, if two (2) drives fail and a rebuild is started after replacing both disk drives, only one drive is rebuilt at a time (e.g., one drive is rebuilt before the second drive rebuild is started). You can monitor the rebuild operation from the Main screen. Expanding an Array IMPORTANT: RAID 6 disk arrays do not support array expansion. Expanding an array increases the capacity of an existing array. An array can be expanded to a maximum of 16 drives. Only one array can be expanded at a time. NOTE: No configuration changes can be made to the arrays, logical drives, or SAN LUN Mapping while an expansion operation is in progress. During expansion, data is re-striped across a new set of data drives, and new parity is calculated and written, if necessary, for fault tolerant arrays. If the array is a fault tolerant array, such as RAID level 1, 10, 5, or 50, it remains fault tolerant during expansion. Should a disk drive fail in a fault tolerant array during expansion, the expand operation continues as normal. The drive is flagged as failed, and the data and parity information is used to create the new data and parity stripe. After the expansion completes, if you designated a Hot Spare, the automatic rebuild operation starts. The rebuild brings the non-fault tolerant expanded array back to a fault tolerant condition. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-7 ULTAMUS RAID 1200 User Guide Advanced Functions IMPORTANT: Before starting an expansion operation, make sure that all critical data is backed up. If a second drive fails during expansion, that condition is not recoverable and you will have a total loss of data. Consider backing up the data prior to expanding an array. Although there is some protection from data loss during this operation, the best insurance is a valid backup. NOTE: After the array expansion process has completed, if you are expanding for the purposes of new drive space, you need to create the appropriate logical drives and define them in your operating system. However, if the expansion is intended to increase the existing logical drive capacity, you need to perform a LUN Expansion. Following expansion, a third-party volume/partition software product is necessary to manipulate any existing partitions. CAUTION: You must stop all host I/O operations prior to deleting or expanding an array. 1. Stop all host I/O operations. 2. On the Main screen, locate and click the array to be expanded. 3. From the default Array screen, click the Expand Array tab. 4. Follow the sequenced steps in the window: a. Click the Array Expansion Type drop-down menu and choose the type of expansion applicable to your array. b. Select the drives to use for expanding the array. c. Examine the Before Expansion and After Expansion analysis to verify the changes to the array. 5. If your settings are correct, click EXPAND (Figure 7-10). Figure 7-10: Expanding an Array 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-8 ULTAMUS RAID 1200 User Guide Advanced Functions 6. At the prompt to confirm the Expand operation (Figure 7-11), type your password and click GO. Figure 7-11: Enter Password and Click Go to Expand Array 7. At the command success prompt, click CLOSE. NOTE: If the command was unsuccessful, review the settings for incorrect parameters and check hardware for operational status. Deleting an Array CAUTION: 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 backup of the data before proceeding. 1. Stop all host I/O operations. 2. In the Main screen Configuration section, click the array you want to delete. The Array Information screen appears (Figure 7-12). Figure 7-12: Delete Array on the Array Information Screen 3. Click DELETE ARRAY. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-9 ULTAMUS RAID 1200 User Guide Advanced Functions 4. At the confirmation screen (Figure 7-13); type your password and click GO. Figure 7-13: Confirmation of Array Deletion NOTE: If you enter a wrong password, you are prompted that the password is incorrect, and the array is not deleted. Click CLOSE to exit the prompt and repeat the process with the correct password. 5. When the array is successfully deleted, click CLOSE. Trusting an Array The trust array option allows immediate access to an array for testing application purposes only. Trust arrays should be used only in environments where you fully understand their function. A trusted array does not calculate parity across all drives; therefore, there is no known drive status. As data is received from the host, parity is calculated as normal, but on a block basis. There is no way to guarantee that parity has been calculated across the entire drive. The parity data is inconsistent, so a drive failure within a trusted array results in data loss. 1. On the Main screen in the Toolbar, click CREATE ARRAY to begin creating a trusted array. 2. Follow the numbered steps to choose your settings: a. Select your drives in the Available Drives section. b. Enter a name for your array. You may use up to 32 characters (ASCII). c. Select the RAID level for the array. d. To enter the desired chunk size, click the pull-down menu and choose from the available values. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-10 ULTAMUS RAID 1200 User Guide Advanced Functions e. At Initialize Trust (item 6 in Figure 7-14), use the pull-down menu and select Trust. Figure 7-14: Creating a Trusted Array f. Choose the Back-off percent (reserved capacity) for the drives. g. The default is 1%. h. Set the Read-Ahead Cache threshold. i. Set the Write-back Cache options. 3. Click CREATE to create the trusted array. 4. At the warning prompt (Figure 7-15), click OK to proceed. Figure 7-15: Warning About Data Loss With Trusted Arrays 5. When the array is successfully built, click CLOSE. Restoring and Clearing the Configuration CAUTION: 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 DATA IS LOST. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-11 ULTAMUS RAID 1200 User Guide Advanced Functions Overland recommends that you periodically save the configuration. See “Saving the Configuration” on page 3-16. Restoring the Configuration 1. On the Toolbar, click Archive Configuration (Figure 7-16). Figure 7-16: Location of Archive Configuration Icon The Configuration Archival Operations screen appears (Figure 7-17). Figure 7-17: Configuration Archival Operations Screen 2. Click RESTORE. 3. At the File upload window (Figure 7-18), click Browse to search for the file. . Figure 7-18: Configuration Restoration Upload Screen 4. Select the appropriate file, and click Open (or Cancel to quit). 5. Click UPLOAD to restore the configuration (or CANCEL to quit). 6. After you complete the configuration restoration, if you had any RAID 5, 6, or 50 arrays defined, verify the parity of each array: a. Click the Array link on the Main screen for each RAID 5, 6, or 50 array. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-12 ULTAMUS RAID 1200 User Guide Advanced Functions b. Perform a Verify Parity operation before using those arrays to ensure that the data and parity data are correct. Clearing the Configuration Some conditions or situations may call for you to clear the entire configuration. CAUTION: This process removes all arrays, logical drives, SAN LUN mappings, snapshots, Snapshot feature licenses, etc. If there is any data on the drives, access to that data is lost. If you are using Snapshot, make a note of which WWN the configuration is based on before you clear the Configuration file (see “Identifying Drive Members of an Array” on page 7-3). The Snapshot feature uses the Configuration WWN that was set when the license key was issued. If you do not use the same WWN, Snapshot will not function. 1. On the Toolbar, click Archive Configuration. The Configuration Archival Operations screen appears (Figure 7-17 on page 7-12). 2. Click CLEAR (or click CLOSE to cancel). 3. At the Clear Configuration Operation pop-up screen (Figure 7-19), type your password and click GO to complete the operation. Figure 7-19: Enter Password to Clear Configuration 4. At the confirmation message, click CLOSE. Advanced Logical Drive Functions Advanced logical drive functions include expanding and deleting logical drives. (To create a logical drive, see “Creating the Logical Drive” on page 3-14.) NOTE: Prior to expanding a logical drive, you can examine the unassigned free space to identify available space for drive creation and expansion. The Create Logical Drive screen displays the available space or free regions. The available free space is displayed in the Select which Arrays to Use field. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-13 ULTAMUS RAID 1200 User Guide Advanced Functions Expanding a Logical Drive CAUTION: You must stop all host I/O operations prior to expanding a logical drive. 1. Stop all host I/O operations. NOTE: After the expansion process is completed you must use a third-party volume/partition software product to manipulate any existing partitions. 2. On the Main screen in the Logical Drives section, click the name of a logical drive that you want to expand. The Logical Drive screen is displayed (Figure 7-20). Figure 7-20: Logical Drive Expansion 3. Choose your settings: a. In the Expand Logical Drive section (lower half) of the window, click the region you want to use in the Select Free Region(s) field. b. In the Add Capacity box, enter the amount of the selected region to use to expand the logical drive. You can use the entire free region space or a portion of it. Enter the value in GB. c. Click EXPAND. 4. At the prompt, enter your password and click GO (or CANCEL to exit). 5. At the successful command message, click CLOSE. NOTE: If the command was unsuccessful, review the settings for incorrect parameters and the hardware for operational status. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-14 ULTAMUS RAID 1200 User Guide Advanced Functions Deleting a Logical Drive CAUTION: You must stop all host I/O operations prior to deleting a logical drive. Deleting a logical drive removes ALL DATA from the drive. Be sure you have backed up any data on the drive before you delete it. Deleting a logical drive removes an existing logical drive that is no longer needed or desired. If the logical drive was previously used, make a backup of any data on the logical drive before beginning this process. After deleting the logical drive, SAN LUN mapping (if used) and operating system mapping must be modified due to the missing drive. 1. Stop all host I/O operations. 2. On the Main screen in the Logical Drives section, click the name of the logical drive you want to delete. The Logical Drive Information screen opens (Figure 7-21). Figure 7-21: Deleting a Logical Drive 3. In the Logical Drive n section (top half), click DELETE. 4. At the prompt, enter your password and click GO (or CANCEL to exit). 5. At the successful command message, click CLOSE. NOTE: If the command was unsuccessful, review the settings for incorrect parameters and the hardware for operational status. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-15 ULTAMUS RAID 1200 User Guide Advanced Functions Advanced Power Management Advanced Power Management offers 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. Drive Power Management (APM Level 1) APM level 1 or Drive Power Management will manage these drive group types: hot spare drives, unused drives and failed drives. The user has the option to set policies for each drive group type managed by APM 1. For each drive group type, the policies are applied universally (see Figure 7-23), 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. IMPORTANT: 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. IMPORTANT: You cannot enable APM features on drives that are also being controlled by the Snapshot feature. Configuring Drive Power Management (APM Level 1) 1. On the toolbar, click the Advanced Settings. Figure 7-22: Location of Advanced Settings Icon 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-16 ULTAMUS RAID 1200 User Guide Advanced Functions The Advanced Settings screen appears (Figure 7-23) Figure 7-23: Advanced Settings screen 2. From the Advanced Settings window click the DRIVE APM button located towards the bottom of the screen. Figure 7-24: Location of the Drive APM button 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-17 ULTAMUS RAID 1200 User Guide Advanced Functions This Advanced Power Management screen appears (Figure 7-25). Figure 7-25: Advanced Power Management screen 3. For each drive type (Unused Drives, Spares and Failed Drives) use the mouse pointer to select the check box adjacent to the type. NOTE: If you wish 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. 4. Once you have enabled “Spin-Up Drives Periodically and Test,” at the lower half of the window choose the policy schedule you wish 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 the CLOSE button on the confirmation window. 6. Click the CLOSE button on the window. APM Characteristics APM level 1 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 level 1 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. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-18 ULTAMUS RAID 1200 User Guide Advanced Functions 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. IMPORTANT: 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 reissue the commands once the drives are spun up and back online. Advanced Performance Options Performance optimization features (Figure 7-26) that include: cache writes to disk, target command thread balancing, and overload management. They provide the end user with the ability to fine tune their configuration. Figure 7-26: Location of the Performance Options button 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-19 ULTAMUS RAID 1200 User Guide Advanced Functions Performance Options Settings The following options will assist you in fine tuning the performance of your system. The Performance Options window is divided into two sections (see Figure 7-27). 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. Figure 7-27: Performance Options Main screen 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-20 ULTAMUS RAID 1200 User Guide Advanced Functions Synchronize Cache Writes to Disk This option (Figure 7-28) will determine whether there is normal processing of the SCSI Cache Synchronize command. Figure 7-28: 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. When you disable this option, these system commands are disregarded and data is not immediately flushed to the arrays. NOTE: If you are operating a duplex system with backup battery units, disabling this option you may improve the system performance. WARNING: When disabled, a loss of power may result in data loss. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-21 ULTAMUS RAID 1200 User Guide Advanced Functions Target Command Thread Balance This option (Figure 7-29) allows the controller to balance response times between multiple initiators. Figure 7-29: Performance Options-Target Command Thread Balance 10400166-102 09/2008 • When enabled, the controller will attempt to reduce the maximum response time by servicing the oldest request first. The default setting is Enabled. • When disabled, the controller will optimize throughput by sorting I/O requests to optimize disk access on any array with write-back cache enabled and write through disabled. This setting should provide optimized performance for typical workloads. ©2007,2008 Overland Storage, Inc. W 7-22 ULTAMUS RAID 1200 User Guide Advanced Functions Sequential Write Optimization This option (Figure 7-30) allows the user to set the amount of optimization the controller should perform for sequential write operations. Figure 7-30: Performance Options-Sequential Write Optimization For best results, select an optimization level that matches the amount of sequential write operations for your workload. If the workload is random or rare write operations, select the OFF setting. Select HIGH for mainly sequential writes, and MEDIUM or LOW for mixed work loads. The default is LOW. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-23 ULTAMUS RAID 1200 User Guide Advanced Functions Overload Management The Overload Management section allows the user 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. This option (Figure 7-31) allows you to enable the response and set the response time out for SCSI Primary Commands. . Figure 7-31: Performance Options-Overland 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 time-out periods are expressed in seconds. The response will be either SCSI TASK SET FULL or SCSI BUSY. Click “Enable” for SCSI TASK SET FULL and “SCSI BUSY” for the SCSI BUSY response. The Queue Full Time-out 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 time-out value is not selectable. Once enabled, you should select a time-out value shorter then the transport layer time-out of your host. Otherwise, the commands will be subject to the normal abort and recovery operations. The default is enabled and a time-out value of 4 seconds. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 7-24 Using Snapshot CHAPTER 8 Introduction to Snapshots A snapshot is the creation of a point-in-time image of a logical drive. The image contains exactly the same data that was on the logical drive at the time of the snapshot. To set up a snapshot, you define a logical drive region as an Overwrite Data Area (ODA). The ODA serves as a storage area for disk data that is protected from any new data overwrites. Figure 8-1: Snapshot and Snapback Operations The snapshot data is transferred to the ODA as new data is written to the logical drive, so the ODA contains an exact image of the logical drive at the time of the snapshot. In the snapback operation, the controller copies the data from the ODA back to the logical drive. A snapback restores the logical drive to the snapshot image. The snapshot image of the logical drive is viewed by the host server as a virtual logical drive (virtual LUN); however, snapshot (virtual) logical drives are read-only. The ODA can only be accessed by the RAID controller for read-write operations, so it is considered an internal drive. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-1 ULTAMUS RAID 1200 User Guide Using Snapshot Snapshots and Caching Disk data caching must be handled properly when taking drive snapshots. For the snapshot function to work, you must be aware of the status of various caches present in the server installation environment. For example. the server might believe a block of data has been committed to the disk when it is actually waiting in the RAID controller cache. An application such as a database might believe its data has been saved on the disk, but the data still resides in the server operating system (OS) cache and has not yet been saved to the disk array. IMPORTANT: The application, operating system, and RAID controller caches must be flushed before you take a snapshot of a logical drive. Application Caches Advanced applications, such as databases, might implement their own data cache to speed up execution. Before you can issue a snapshot, the application’s data cache must be flushed. If the application does not provide a means to flush its cache, close down the application before issuing the snapshot. Operating System Cache The OS dedicates a large percentage of its DRAM space to disk data caching. You must flush the entire OS disk cache just before you issue a snapshot. RAID Controller Cache The RAID Controllers implement large caches for disk data. A large portion of these caches is used as delayed write-back cache space for holding data blocks not yet written to the disk drives. It is very important that the RAID Controllers flush their data caches before you start a snapshot. See the RAID Controller documentation for information on how to flush the disk data cache. Overwrite Data Areas The ODA is a reserved area on the disk array used for storing snapshot data from a logical drive. ODAs are created in a similar fashion as normal disk arrays, but they are for internal controller use only. Before snapshots can be issued on a logical drive, an ODA area must be assigned for its use. The ODA remains assigned as long as it is needed. To unassign an ODA, the snapshots must first be removed. The space can later be reassigned for snapshots of a different logical drive. Up to eight ODAs can be configured within one array. Each ODA can be of any assigned capacity. An ODA can be mapped onto any disk array with any RAID level, chunk size and stripe size. To create an ODA, you enable a snapshot on the Drive Information screen. This action mark one of the previous defined logical drives as internal, and assigns the ODA to the specific logical drive to be snapshot. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-2 ULTAMUS RAID 1200 User Guide Using Snapshot When the ODA is assigned, snapshots can be taken on a logical drive at any time. Each logical drive can be snapshot up to 24 times. Each of these 24 snapshots represents a full virtual copy of the snapshot logical drive at the point in time of the snapshot. ODA initialization is performed automatically by the RAID Controller during configuration. You specify the overall size and the stripe size of the ODA during initialization. The stripe size defines how much data is protected per copy on write operation. When the snapshot engine receives a write command and has determined the underlying data must be protected, the size of the read and write commands is determined by the ODA stripe size. If the ODA stripe size is set to 128K, then the protective read write is performed on 256 disk blocks at a time. ODA Location The overwrite data areas can be configured two ways: on the same disk array as a regular logical drive, or on one or more separate disk arrays dedicated to ODAs. If the ODA area is located on the same physical disk array as the logical drive being snapshot, the performance of both reads and writes to the logical drive is adversely affected. For better performance, the ODA should be located on its own dedicated disk array. For best performance, dedicate one smaller disk array for one or more ODAs, exclusively. Selecting the ODA Stripe Size During ODA initialization, you select a stripe size for the ODAs. In an array with multiple ODAs defined, each ODA can be set up with its own stripe size. The ODA stripe size represents the size of the data area that is always protected during a snapshot copy-on-write operation. Choosing the best ODA stripe size requires some knowledge of the intended write data access pattern on the logical drive to be snapshot. The ODA saves data to be overwritten in multiples of its stripe size. A large stripe size offers a smaller number of data areas, while a smaller stripe size offers more data areas. If the server application issues a high percentage of small writes in a random address pattern, then select a small ODA stripe size, such as 64K. This ODA is striped with many smaller data areas to use for a large amount of small random writes. A disadvantage is that the probability for follow on hits in an already protected area of the logical drive is smaller compared with using a larger ODA stripe size. If the server application issues a high percentage of small random writes clustered together in groups on the logical drive, then select a large ODA stripe size. This increases the probability that other small writes will be addressed to a disk area that is already protected by a larger stripe of data, and minimizes the amount of copy-on-write sequences needed. The impact on performance is minimized. A disadvantage is that the total number of ODA stripes would be reduced if the write access pattern suddenly became very random. For applications that perform a large percentage of sequential writes, select a larger ODA stripe size to minimize the amount of copy-on-write operations needed and maximize performance. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-3 ULTAMUS RAID 1200 User Guide Using Snapshot ODA Storage Capacity The maximum storage capacity of an ODA depends on the ODA stripe size. The space used by each stripe size is shown in Table 8-1: Table 8-1: ODA Stripe Size and Storage Capacity ODA Stripe Size ODA Storage Capacity 64 Kbytes 512 GBs 128 Kbytes 1 Terabyte 256 Kbytes 2 Terabytes 512 Kbytes 4 Terabytes 1 Mbyte 8 Terabytes When you select the size of the ODA, keep in mind the type of data, the ODA stripe size, the number of snapshots you plan to take and the write pattern of the data. Select a size large enough to accommodate the data on the logical drive for the number of possible snapshots. The RAID controller alerts you if ODA storage space is nearly exhausted. If the ODA is filled to its limit and can no longer store copy-on-write data, the Snapshot becomes out of phase with the underlying logical drive, causing the RAID Controller to invalidate all Snapshots for this logical drive. Virtual LUNs Virtual LUNs are also known as snapshot LUNs. They can be made available for access through a dynamically created LUN. Reads issued to a virtual LUN are serviced in a similar way to reads issued to a normal LUN. The data is exactly as it was at the time of the snapshot. This allows an application, such as disk backup software to perform a backup operation of the Virtual LUN. A virtual LUN responds to any type of incoming SCSI command in the same way as the original logical drive. Since this is snapshot data, the host cannot modify the data (i.e., no write commands). Virtual LUN Numbering Each Virtual LUN (logical unit number) is presented to the host side as a regular logical drive. A logical unit number is assigned and used by the accessing host. These LUNs are automatically assigned. Up to eight (8) ODAs can be defined within the array, and are numbered 0-7. Each ODA can store up to 24 Snapshots, so the Snapshot number can range between 0-23. The overall possible range for the Virtual LUNs is 0-192. Because a conflict with a normal LUN is high, virtual LUNs are not automatically made visible to the host system. Through LUN mappings, each Virtual LUN is manually assigned a LUN number that then becomes visible to the host. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-4 ULTAMUS RAID 1200 User Guide Using Snapshot Example of Virtual LUN Numbering A disk array with three normal data LUNs configured as LUN 0-2 and one ODA, will have its first Virtual LUN numbered 0. To avoid a conflict between the original data LUN 0, the Virtual LUN must be LUN mapped to a non-conflicting LUN number, e.g., LUN 10. All accesses to LUN 10 is then translated into Virtual LUN 0 internally by the RAID Controller. Enabling Snapshot This process creates an Overwrite Data Area (ODA) and pairs it to a logical drive for a snapshot. You can create one ODA for the generation of up to four snapshots. IMPORTANT: You cannot enable snapshot support while an array expansion or array initialization is occurring. Wait for the operation to complete before enabling snapshot support. If you intend to make your snapshots available as logical drives (virtual LUNs), you must SAN LUN map all logical drives. That includes regular logical drives and the snapshotted logical drives. 1. From the Main screen Logical Drives area, select a logical drive for the snapshot (Figure 8-2). Figure 8-2: Taking a Snapshot of a Logical Drive IMPORTANT: If you are taking a snapshot for the first time, you can create one ODA and pair it to one logical drive. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-5 ULTAMUS RAID 1200 User Guide Using Snapshot 2. Click ENABLE SNAPSHOT on the Logical Drive screen (Figure 8-3). Figure 8-3: Enabling a Snapshot NOTE: Overland recommends that you create an array specifically for the ODA. Choose an array that is not associated with the logical drive to avoid performance compromises. Figure 8-4: Storing the ODA on an Array By default, the Show arrays used by this logical drive box is not checked (Figure 8-4), and the logical drives associated with the array are not shown. It is strongly recommended that you choose an array that is not associated with the logical drives allocated on it (e.g., do not check the box). When you check this box, the arrays for this logical drive are shown in addition to the other disk arrays; any of the displayed logical drives can be selected. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-6 ULTAMUS RAID 1200 User Guide Using Snapshot 3. Enter the size of the ODA in Gigabytes (GB). Overland recommends that you consider future usage while determining the proper ODA size, based on the number of expected snapshots. If the ODA size is exceeded, all snapshots associated with the logical drive become invalid. See “ODA Storage Capacity” on page 8-4. 4. From the drop-down menu, choose the desired stripe (write buffer) size for the ODA. The choices are: 64KB, 128KB, 256KB, 512KB, or 1MB. NOTE: The maximum ODA size for the data stripe size is shown in Table 8-1 on page 8-4. Stripe size is associated with ODA size. The stripe sizes available in the drop-down menu change dynamically based on ODA size. For example, if you specify an ODA size greater than 549GB, the selection for 64KB is not displayed. If you enter an ODA size greater than 1TB, then both 64KB and 128KB stripe sizes are not displayed. Overland recommends that you choose a stripe size based on your application’s need. If you are making small changes, such as with a database, choose the smallest stripe size. If you are making large changes, such as with video applications, you need a much larger stripe size. For details, see “Selecting the ODA Stripe Size” on page 8-3. 5. Click ENABLE. 6. Click CLOSE in the confirmation screen. Taking a Snapshot This process creates a point-in-time image of the selected logical drive. Snapshots are automatically named, starting with Snap 00, and increment for each additional snapshot (Snap 01, Snap 02, etc.) for the logical drive. You can view them from the Snapshot Information screen. IMPORTANT: Make sure that applications writing to the logical drive are synchronized with the snapshot. This can be performed in a variety of ways depending on the applications using the snapshot logical drive. Flush buffers for a consistent application point-in-time image of the files on the logical drive (see “Snapshots and Caching” on page 8-2). 1. From the Main screen, select the logical drive for the snapshot (Figure 8-5). 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-7 ULTAMUS RAID 1200 User Guide Using Snapshot Figure 8-5: Select the Logical Drive on the ULTAMUS RAID manager Main Screen 2. From the Logical Drive screen, click SNAPSHOT MANAGEMENT (Figure 8-6). Figure 8-6: Snapshot manager on the Logical Drive Information Screen 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-8 ULTAMUS RAID 1200 User Guide Using Snapshot 3. Click TAKE SNAPSHOT to begin the snapshot procedure (Figure 8-7). Figure 8-7: Begin the Snapshot Process You are prompted to ensure that the applications have been synchronized and the logical drive is dismounted. 4. Click Take Snapshot to continue the process (Figure 8-8). Figure 8-8: Taking the Snapshot 5. When the snapshot is complete, click CLOSE on the confirmation screen. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-9 ULTAMUS RAID 1200 User Guide Using Snapshot 6. After the snapshot is complete, the following information is displayed in the Snapshot/ODA Management screen (Figure 8-9): Figure 8-9: List of Snapshots in the Snapshot/ODA Management Screen 7. Click CLOSE on the Snapshot/ODA Management screen. 8. Click CLOSE on the Logical Drive Information screen. Mapping a Snapshot To make the snapshot of the logical drive available to the host, you perform a SAN LUN Mapping of the snapshot. These snapshot logical drives or virtual logical drives have read-only attributes. IMPORTANT: If you intend to make your snapshots available as logical drives (virtual LUNs), you must SAN LUN map all logical drives, including regular logical drives and snapshot logical drives. You map the snapshot on the SAN Mapping screen: 1. From the Toolbar, click SAN MAPPING. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-10 ULTAMUS RAID 1200 User Guide Using Snapshot 2. Select the Snapshot that you want to map from the drop-down Logical Drive menu (Figure 8-10). Logical Drive Snapshot Host Ports Figure 8-10: Selecting the Snapshot to Map 3. Choose the host port check boxes (Figure 8-10) where you want access to the snapshot logical drive, and then click APPLY. 4. Click CLOSE. To backup or retrieve data from the snapshot logical drive, access your host operating system and application software. Deleting a Snapshot You can delete a snapshot taken on a specific logical drive. IMPORTANT: If you delete a snapshot, all snapshots that occurred after the one you are deleting are also deleted. For example, if there are four snapshots (Snap 00 Snap 03), and you delete Snap 01, then Snap 02 and Snap 03 are also deleted. 1. From the Main screen Logical Drive area, select the logical drive with the Snapshot icon next to it (Figure 8-11 on page 8-12). 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-11 ULTAMUS RAID 1200 User Guide Using Snapshot Figure 8-11: Select the Snapshot to Delete 2. At the Logical Drive screen appears, click SNAPSHOT MANAGEMENT (Figure 8-12). Figure 8-12: Select Snapshot Management 3. Select the snapshot you want to delete from the Snapshots list screen 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-12 ULTAMUS RAID 1200 User Guide Using Snapshot 4. Click DELETE SNAPSHOT. Figure 8-13: Deleting the Snapshot 5. At the Delete Snapshot confirmation screen, make sure this is the snapshot you want to delete and click DELETE SNAPSHOT again. Figure 8-14: Confirming Snapshot Deletion 6. At the confirmation message, click CLOSE. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-13 ULTAMUS RAID 1200 User Guide Using Snapshot Performing a Snapback A Snapback restores the logical drive to the state it was in at the point the snapshot was taken. IMPORTANT: Before you perform a snapback operation, be sure to back up the data on the existing logical drive first. When the snapback command is issued, the existing data is overwritten and replaced with an exact copy of the snapshot image. 1. If necessary, perform a backup of the logical drive before performing the Snapback operation. 2. From the Main screen Logical Drive area, select the appropriate logical drive with the Snapshot icon next to it (Figure 8-15). Figure 8-15: Selecting the Snapshots 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-14 ULTAMUS RAID 1200 User Guide Using Snapshot 3. In the Logical Drive screen, click SNAPSHOT MANAGEMENT (Figure 8-16). Figure 8-16: Selecting Snapshot Management 4. Select the snapshot you want to snapback from the Snapshots list screen, and click SNAPBACK (Figure 8-17). Figure 8-17: Initiating the Snapback IMPORTANT: If you perform a snapback, the select snapshot and all snapshots that occurred after the one you are snapping back will be deleted. For example, if there are four snapshots (Snap 00 - Snap 03), and you snapback Snap 01 then Snap 02 and Snap 03 are deleted with Snap 01. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-15 ULTAMUS RAID 1200 User Guide Using Snapshot 5. Click CLOSE on the Snapshot/ODA Management screen. 6. Click CLOSE on the Logical Drive Information screen. A progress bar displays on the Main screen, located under the logical drive icon. The logical drive is now restored to the snapshot point-in-time. Disabling Snapshot This operation unpairs the ODA from the logical drive, which results in deleting an ODA. When you perform this operation, all snapshots for this logical drive are removed. 1. From the Main screen select the logical drive for which you want to disable Snapshot support (Figure 8-18). Figure 8-18: Selecting a Drive to Disable Snapshots 2. In the Logical Drive Information screen, click DISABLE SNAPSHOT. CAUTION: Disabling Snapshot support results in the loss of all snapshots for this logical drive. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-16 ULTAMUS RAID 1200 User Guide Using Snapshot 3. At the Disable Snapshot/Delete ODA confirmation window (Figure 8-19), click DISABLE. Figure 8-19: Confirmation of Snapshot Disablement 4. Enter your password at the prompt and click GO to disable snapshots. 5. On the confirmation screen, click CLOSE. 6. Click CLOSE on the Snapshot/ODA Management screen. 7. Click CLOSE on the Logical Drive Information screen. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 8-17 Support and Updates CHAPTER 9 Tech Support This feature provides technical support personnel with event and configuration information to assist with troubleshooting. 1. From the Main screen, click Tech Support (Figure 9-1). Figure 9-1: Location of the Tech Support Button 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 9-1 ULTAMUS RAID 1200 User Guide Support and Updates 2. Enter the requested information for each field (Figure 9-2). Figure 9-2: Tech Support Information Fields The Your Problem field is scrollable, which allows you to review the information you want to send. NOTE: The gathering of this information may take a few minutes. 3. Click DOWNLOAD. 4. At the prompt to save the file on your local disk, enter a name for the file and click Save. The software creates 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 CLOSE on the Technical Support window. 6. When requested by a technical support representative, e-mail the saved file. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 9-2 ULTAMUS RAID 1200 User Guide Support and Updates Updating ULTAMUS RAID manager Software CAUTION: Ensure there is uninterrupted power during the update. NOTE: You need to update the ULTAMUS RAID manager software on each RAID controller separately. 1. Click About in the main ULTAMUS RAID manager screen to display the About screen (Figure 9-3). Figure 9-3: The Update Button on the About Screen 2. Click the UPDATE button. 3. In the update screen (Figure 9-4), type the name of the firmware file or click the Browse button and locate the file. The file name is similar to “3.05.0001nb-en.bin.” Figure 9-4: The Update ULTAMUS RAID manager Screen 4. Enter your login password and click UPLOAD. When the update is complete, ULTAMUS RAID manager server automatically restarts. This process does not affect I/O activity. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W 9-3 Optimizing Write Performance CHAPTER A Introduction With a typical RAID 5 implementation, there are a number of steps that are performed when data is written to the media. Every write from the host system will typically generate two XOR operations and their associated data transfers, to two drives. If the accesses are sequential, the parity information will be updated a number of times in succession. However, if the host writes sufficient data to cover a complete stripe, the parity data does not need to be updated for each write, but it can be recalculated instead. This operation takes only one XOR operation per host write, compared to two for a standard write. The number of data transfers necessary are also reduced, increasing the available bandwidth. This type of write access is termed a Full Stripe Write. NOTE: This appendix was written for RAID 5. However, with RAID 6, which uses two parity drives, the size of the stripe based on the “number of data drives multiplied by the chunk size” principle is similar. The illustration below displays the distribution of data chunks (denoted by Cx) and their associated parity (denoted by P(y-z)) in a RAID 5 array of five drives. An array is defined as a set of drives, on which data is distributed. An array will have one RAID level. A chunk is the amount of contiguous data stored on one drive before the controller switches over to the next drive. This parameter is adjustable from 64K to 256K, and should be carefully chosen to match the access sizes of the operating system. A Stripe is a set of disk chunks in an array with the same address. In the example below (Figure A-1), Stripe 0 consists of C0, C1, C2, and C3 and their associated parity P(0-3). Figure A-1: RAID 5 Distribution of Data Chunks 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W A-1 ULTAMUS RAID 1200 User Guide Optimizing Write Performance Maximum performance will be achieved when all drives are performing multiple commands in parallel. To take advantage of a Full Stripe Write, the host has to send enough data to the controller. This can be accomplished in two ways. First, if the host sends one command with sufficient data to fill a stripe, then the controller can perform a Full Stripe Write. Alternatively, if the host sends multiple sequential commands, smaller than a stripe size (typically matching the chunk size), the controller can internally combine these commands to get the same effect. In the above example, if a 256K chunk size is used, then the stripe size is 1MB (4 chunks * 256K). So, for maximum performance, the host could either send 5 * 1 MB write commands, or 20 * 256K write commands. The effectiveness of the controller’s ability to perform a Full Stripe Write depends on a number of parameters. Sequential Access If the commands sent from the host are not sequential, the controller will not be able to cluster them together. So, unless each individual access is sufficient to fill a stripe, a Full Stripe Write will not occur. Number of Outstanding Commands For the controller to successfully cluster commands, there must be a number of write commands sent simultaneously. Setting the host to send up to 64 commands should prove adequate. Alternatively, enabling write-back 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. Access Alignment The alignment of a command from a host system is determined by the command’s address. In an optimal system, a write of one chunk of data would reside exactly within a chunk on one disk. However, if this is not the case, this write will be split up into two separate writes to two different data drives. This will have a negative effect on performance. To overcome these problems, you can, with more sophisticated operating systems, set the access size and alignment to an optimal value. As the table below shows (Figure A-2 on page A-3), 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. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W A-2 ULTAMUS RAID 1200 User Guide Optimizing Write Performance Figure A-2: Parallel Striping From the table, 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 can get difficult to achieve maximum performance, as it becomes more difficult to cluster a large number of commands to achieve a Full Stripe Write. 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 the RAID 5 table in Figure A-1 on page A-1). 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: Two RAID 5 Sets Striped 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W A-3 ULTAMUS RAID 1200 User Guide Optimizing Write Performance As you can see, the more sub-arrays used, the more likely it is for a Full Stripe Write to occur, hence the higher the performance. We recommend that you use either four or five drives in a sub-array, for best performance. The following figure (Figure A-4) 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. 15 Drives Using Sub-Arrays Multiple Drive Failures In a configuration with multiple sub-arrays, it is possible for the array to sustain multiple drive failures, provided that there is only one failure in each sub-array. Faster Rebuild A rebuild operation must read data and calculate parity from all the remaining drives in the RAID set. If multiple sub-arrays are used, this means that it is only necessary to read the data from the remaining drives in the sub-array, not all of the drives in the array. This increases both the rebuild speed and the speed of access to missing data, which also has to be recreated from the remaining drives. Summary In summary, for maximum performance, it is recommended to use four or five drives in a sub-array. If there are more than five drives in a sub-array, it is better to use a smaller chunk size, say 64K or 128K, as this will lead to more Full Stripe Writes. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W A-4 Troubleshooting CHAPTER B Problems You May Encounter This appendix provides typical solutions for problems you may encounter while using ULTAMUS RAID manager to control and manage the storage systems. Also refer to the Event chapter, and review the cause and actions for each event listed. Table B-1: Troubleshooting Chart 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. 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 Operating in a StandAlone configuration with the Single Controller Mode setting in the Controller Single Controller Mode Parameters tab. not selected. Password Error Password not accepted at log in. Password is case sensitive, ensure that the password is entered correctly. Password was forgotten Contact technical support for the procedures to recover from a lost or missing password. or lost Lost communication with the RAID Controllers. Service is hung Restart the ULTAMUS RAID manager service. Access the Control Panel and double-click on Services. Locate the ULTAMUS RAID manager Service and click Stop. When the service has stopped, click Start and retry the connection by clicking the Rescan button on the ULTAMUS RAID manager Main screen. On Linux system access the process viewer and stop the ULTAMUS RAID manager Process. Restart the process and click the Rescan button on the ULTAMUS RAID manager Main screen. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W B-1 ULTAMUS RAID 1200 User Guide Troubleshooting Table B-1: Troubleshooting Chart (Continued) Symptom Reason Solution Hot spare not automatically starting when drive failure occurs in a redundant array in which a global or dedicated hot spare is defined. The Auto Rebuild option Open the Controller Information window (click the Controller icon), place a check mark in the box by clicking is not enabled in the Controller Parameters. the check box on the Auto Rebuild parameter. Consistently occurring time out errors when the browser window is open. Host HBA parameter settings are not configured for best performance optimization. Ensure that the disk drive defined as a hot spare is equal Hot spare disk drive is too small to be used for to or greater than the size of the drive members of the the drive replacement. arrays. Auto Rebuild is not selected and no hot spare drive is Waiting for a valid replacement drive to be assigned, but Auto Hot Spare is enabled. The array will begin rebuilding when a valid replacement drive is inserted inserted. in the drive slot of the failed drive Access your Host HBA settings and make the following changes: Execution Throttle: Improve general I/O performance by allowing more commands on the fibre bus. Do this by changing your host bus adapter’s execution throttle parameter to 256. Scatter/Gather: (Microsoft Windows) Increase the general I/O performance by allowing larger data transfers. Do this by editing the MaximumSGList parameter in the register. The recommended hexadecimal value is ff. The path is: HKEY_LOCAL_MACHINE/System/CurrentControlSet/Servi ces//Parameters/Device/. Shared Memory Error is The CGI script manager displayed. may have not released a segment of shared memory. This can occur when heavy I/O is happening at the same time you are accessing ULTAMUS RAID manager. If this occurs you will need to stop and then restart the ULTAMUS RAID manager server service. Multiple Configuration After switching drives and/or controllers from WWNs being used. one storage solution enclosure to another, one of the solutions reports that the storage solution is being monitored by another host. If you have been interchanging configured drives or controllers between storage solutions you may have a situation where multiple solutions are now sharing the same Configuration WWN. This can be corrected by changing the Configuration WWN value found in the Controller Parameters on either of the storage solutions. After making this change, all participating host systems will require a reboot (see “Controller Information Access” on page 5-1). 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W B-2 ULTAMUS RAID 1200 User Guide Troubleshooting Table B-1: Troubleshooting Chart (Continued) Symptom Reason Solution Inadvertently pulled the Possible incorrect drive incorrect drive from the identification and enclosure and the array removal. is dead. If by mistake you remove a working drive member instead of the failed drive, this can cause the array to fail. In most cases you can simply re-insert that drive that was incorrectly removed and the array will return to the same state it was in prior to removing the drive. For RAID 5/50 arrays, a drive failure will put the array in a critical state, if a hot spare was available the array should go into a rebuild mode. If you inadvertently remove one of the known good drives that is in the process of rebuilding, the rebuild operation will stop. When you re-insert the incorrectly removed drive the array will return to the critical state and the rebuild process will start again. If you did not have a hot spare assigned, the array will be in a critical state. If you inadvertently remove a known good drive instead of the failed drive the array will change to a failed array state. Re-inserting that inadvertently removed drive will put the array back into a critical state. Replacing the failed drive will cause the array to begin a rebuild operation provided that you assign it as a hot spare or, if the Auto Hot Spare option was enabled the rebuild will begin automatically as the new replacement drive is installed. For RAID 0 arrays, if you inadvertently remove a known good drive, the array will become dead. When you re-insert the incorrectly removed drive the array will return to its working state. For RAID 1/10 arrays, if you inadvertently remove a known good drive, the array will become failed. When you re-insert the incorrectly removed drive the array will return to its previous state. If the array was critical, you can then replaced the known failed drive with a working drive and assign it as a hot spare and the array will begin rebuilding. NOTE: For all arrays removing a drive as described above will cause all current processing I/O from the controller to stop. Any I/O in progress may have been lost or cause a corrupt file. Be sure to verify all data stored during this type of incidence to ensure data reliability. Expanding Array is displayed as Critical. Known issue and should During an array expansion, the array remains in a fault be corrected in the next tolerant state. Should a drive failure occur during the software release. expansion the operation will continue until it has completed, then if a hot spare was assigned, a rebuild operation will begin automatically. If a hot spare is not assigned, replacing the failed drive with a known good drive after the expansion will cause a rebuild to start, assuming you have the Auto Hot Spare option selected in the Controller Parameters. During the rebuild operation the array will be critical. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W B-3 ULTAMUS RAID 1200 User Guide Troubleshooting Table B-1: Troubleshooting Chart (Continued) Symptom Reason Solution The controller’s IDs and/or Configuration WWN was changed and now there is a communication failure. When you changed the controller IDs, a new nexus is established which requires the operating system and software to establish new communication paths. If you using Microsoft Windows you can use the ULTAMUS RAID manager Rescan feature to relocate the storage solution(s). ULTAMUS RAID manager The host operating displays a message: No system is not able to storage solution found. see the storage solution. Ensure that the Fibre devices appear in your HBA’s BIOS. Ensure that you have the latest driver installed for your HBA. Probe the SCSI enclosure to ensure that you see the solution. Reboot the host and the storage system. I received the following message: Lost communication with server. The server may be down. During heavy host operations and/or data I/O, the system can become too busy to complete CGI requests from the GUI in the time allocated. After several updated attempts have failed you will see this message. At this time you can try to use the Browser’s refresh function to reload the ULTAMUS RAID manager GUI. If that is unsuccessful, you may need to stop and then restart the ULTAMUS RAID manager server service. If you continue to receive that message, close the browser and wait until I/O traffic has settle down before opening the ULTAMUS RAID manager GUI back up. You will still continue to receive e-mail notifications and Event logging. During heavy data I/O, The controller’s onboard Configuration changes during heavy I/O are not recommended. You can either wait until there is less data resources are when I try to make a traffic or keep re-trying the command until it is successful. configuration change I consumed. get a failure saying that the controller is busy Enclosure image on the Enclosure Support Main screen is dimmed option has been or greyed out. disabled. Access the Controller Information window by clicking the Controller icon. Verify the option Enclosure Support is check and click APPLY. Close the window. Fails to set SATA disk Possible mixing of SATA Ensure the MUX Transition cards are all of the same type, drive as a spare. Invalid MUX Transition card either A/A or A/P, specifically on the spare drive attempting field error. types. to be added. Refer to the hardware user guide for illustrated samples of MUX Transition cards. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W B-4 ULTAMUS RAID 1200 User Guide Troubleshooting Failed Drives Codes The controller maintains a list of failed drives. Drives are listed in the following format: Failed Drive:xx SN: yy yy yy yy yy yy The reason code may be one of the following: Reason Code Reason Action Drive Time-out The drive has either timed out or been removed. Re-insert the disk drive. Command: xx Sense Key: yy Ext Sense: zz Replace the disk drive. The drive has failed for the specified Replace the disk drive. command, with the indicated SCSI sense key and extended sense key. SAS Fatal Error Codes The controller maintains a list of internal SAS error codes: 10400166-102 09/2008 Error Code Reason 0x10000000 Controller received a SAS reset Controller is reset to recover. command from the other controller. 0x10000001 Error initializing Target Mode, Controller is reset to recover. controller cannot initialize link. 0x10000002 SAS Discovery Timeout. ©2007,2008 Overland Storage, Inc. Action Controller is reset to recover. W B-5 Event Log Lists CHAPTER C Events in this chapter are categorized and listed in the order of their individual Event Type [ID]. This is a comprehensive list of all events; not every event is applicable to every controller or enclosure model. Controller Events The following table provides a brief description of events which relate to all models of the RAID Controller and Configuration. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. Controller Event Messages Type [ID] Cause There was a fatal xxxx. Where xxxx could be: - Watchdog Error - ECC Error - Host Fibre Channel Interface Error on Loop - Firmware Error 0x. Additional Info: (Advanced hex data for customer service or engineering use.). Error Internal hardware or [0xB01 (2817)] firmware failure. The controller’s internal temperature C has exceeded the maximum limit. The controller will shutdown to prevent damage. Error Blocked fan. [0xB03 (2819)] Failing fan. Action Replace the controller. Contact technical support. Fault SDRAM or damaged internal bus. Internal hardware. Memory or bus error on the indicated channel. Elevated 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. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-1 ULTAMUS RAID 1200 User Guide Controller Event Messages Event Log Lists Type [ID] Warning The controller’s internal [0xB04 (2820)] temperature C is approaching the maximum limit. You should check the cooling system for problems. Cause Action Blocked fan. Check enclosure for sufficient air flow. Failing fan. Elevated ambient temperature. 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. The onboard cache protection Error Battery failure. battery backup unit has failed or [0xB07 (2823)] has been disconnected. Replace battery in the controller. The partner controller has failed Error Failure or removal of one or has been removed. [0xB08 (2824)] controller (partner) in an Active-Active configuration. Re-install the controller. Failure or removal of one This controller has not received a Error [0xB09 (2825)] controller (partner) in an response from the other Active-Active configuration. (partner) controller in the allotted time, and therefore it has been disabled. Replace the controller. or Replace the controller. An error has been detected on the SAS domain or with a SAS device during the discovery process. Error Possible drive or internal [0xB0F (2831)] bus error. Replace drive. The controller’s voltage reading measures V which exceeds the limit. Error Voltage regulator hardware [0xB19 (2841)] failure. Replace the controller. Internal transfer error. Error Hardware problem. [0xB1A (2842)] Replace the controller. The discovery process has completed identifying all SAS devices on the SAS domain. Information Courtesy informational [0xB22 (2850)] message. No action necessary. A discovery process has started to determine all SAS devices on the SAS domain. Information [0xB23; (2851)] No action necessary. Controller mismatch detected. “This” or “The other” controller was shut down. Error RAID Controllers with [0xB1C (2844)] 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. For example all F5402E RAID Controllers or all F5412E RAID Controllers. The other (partner) controller has been inserted. Information Partner controller has been [0xB29 (2857)] inserted. No action necessary. 10400166-102 09/2008 Replace the defective Power Supply or Power Enclosure 5V or 12V problem in the power supply. Supply/Cooling module. Courtesy informational message. ©2007,2008 Overland Storage, Inc. W C-2 ULTAMUS RAID 1200 User Guide Event Log Lists Controller Event Messages Type [ID] Cause Action The other (partner) controller has passed its self-test and is now ready (failback). Information Partner controller is ready to No action necessary. [0xB2A (2858)] fail back. Information A controller fails or is A stripe synchronization of a RAID set has started. This occurs [0xB2C (2860)] powered off during a write operation. when a controller fails, or after a controller is powered off with write commands in progress. No action necessary. A stripe synchronization of a RAID set has completed. Information A controller fails or is [0xB2D (2861)] powered off during a RAID write operation. No action necessary. The configuration has changed. Information A change in the [0xB2F (2863)] configuration has occurred. If you are using the Save Configuration feature, resave your configuration information - it no longer matches, otherwise no action is necessary. The controller is flushing the partner’s mirrored cache to the drives. There are cache entries totalling 512-byte blocks. Information Failure or removal of the [0xB35 (2869)] partner controller. No action necessary. The controller has completed flushing the partner’s mirrored cache to the drives. Information Completion of mirrored [0xB36 (2870)] cache flushing. No action necessary. Battery charging complete. No action necessary. The battery backup unit attached Information [0xB42 (2882)] Special feature mode. to the controller is now functioning correctly. Controller can be operated with battery removed and no Line Power Mode LED indication occurs. The controller has been powered Information Removal of controller or off. [0xB50 (2896)] power. No action necessary. The controller has been powered Information The controller was powered ON. [0xB51 (2897)] ON. No action necessary. The controller self-test was successfully completed. Information Self-test completion on [0xB52 (2898)] startup. No action necessary. The controller self-test has failed. Error Self-test failure on startup. [0xB53 (2899)] Replace the controller. The controller’s NVRAM has been reset. Information Occurs first time after [0xB54 (2900)] production. No action necessary. The controller has an invalid World Wide Name. Error Occurs first time after [0xB55 (2901)] production. Contact technical support. The Event Log has been cleared. Information The user has cleared the [0xB56 (2902)] event log. No action necessary. The controller has been reset. No action necessary. 10400166-102 09/2008 Information User initiated a controller [0xB57 (2903)] reset. ©2007,2008 Overland Storage, Inc. W C-3 ULTAMUS RAID 1200 User Guide Event Log Lists Controller Event Messages Type [ID] Cause The controller has been shutdown. Information User initiated a controller [0xB58 (2904)] shutdown. The controller temperature threshold was exceeded and the controller shut itself down. 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 environment ambient temperature. All identified enclosures have at least two communication paths to their SES devices. Information SES initialization. [0xB5B (2907)] No action necessary. Failover started. Information Failure or removal of the [0xB5C (2908)] partner controller. No action necessary. Failover completed. Information Completion of failover [0xB5D (2909)] process. No action necessary. Failback started. Information Partner controller started [0xB5E (2910)] failback. No action necessary. Failback completed. Information Completion of failback [0xB5F (2911)] process. No action necessary. The controller firmware has been Information User upgraded the controller No action necessary. upgraded to version . [0xB60 (2912)] firmware. The controller battery backup unit is charging. Information Battery charging started. [0xB62 (2914)] No action necessary. Failure of power with writeFlushing of the battery protected Information [0xB63 (2915)] back cache present. cache has started. There are cache entries totalling 512-byte blocks. No action necessary. Flushing of the battery protected Information Completion of cache cache has completed. [0xB64 (2916)] flushing. No action necessary. Failure of power for an The cache data being preserved Error [0xB65 (2917)] extended time with writeby the controller’s battery was back cache present. lost. There were cache entries totalling 512-byte blocks. Check the file system. An SDRAM ECC error - bit at Warning SDRAM error. address has [0xB72 (2930)] been detected and corrected. If it repeats, replace the controller. A configuration parameter has been changed: (Array ) has been trusted due to a cancellation of an initialization. 10400166-102 09/2008 Information A user cancelled an [0xB74 (2932)] initialization. ©2007,2008 Overland Storage, Inc. No action necessary. W C-4 ULTAMUS RAID 1200 User Guide Controller Event Messages Event Log Lists Type [ID] Cause Error [0xB7A (2938)] Additional Info: (Advanced hex data for customer service reps or engineer use.). Hardware Error Running CEMI firmware version: Release , Build . Action The controller will continue Replace the controller. to function, however the SES temperature sensing may not function properly. Information CEMI firmware is current. [0xB89 (2953)] No action necessary. Error Firmware is attempting to “Automatic” or “Manual” CEMI firmware upgrade from : Release , Build to new version: Release , Build , , or . No action necessary. “Automatic” or “Manual”, depending on whether the upgrade attempt was automatic or manual. Error Firmware failed to upgrade CEMI firmware upgrade from [0xB89 (2953)] due to non-responding : controller. Release , Build to new version: Release , Build failed because there is no response from the processor. Occurs when there is a remote request to restart Embedded module. Information [0xB8A (2954)] Embedded module reset was successful. No action necessary. No action necessary. A remote request for a Embedded module reset was successful. Occurs when there is a remote request to restart Embedded module. Error [0xB8A (2954)] Embedded module reset failed. Try again, if no success replace RAID Controller. A remote request for a Embedded module reset failed. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-5 ULTAMUS RAID 1200 User Guide Event Log Lists Controller Event Messages Type [ID] Cause Action When the firmware queries the PMC firmware version, these events are logged: Information Applicable to the [0xB8B (2955)] RS-4835-F4-5404E RAID Controllers only. No action necessary. Error Applicable to the [0xB8B (2955)] RS-4835-F4-5404E RAID Controllers only. No action necessary. 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>.” 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>.” 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-6 ULTAMUS RAID 1200 User Guide Event Log Lists Expansion Module Events These events are related to the expansion modules (Disk I/O or RAID Controller I/O module) reported by the SES processor during updates. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. Expansion Module Event Messages Type [ID] Cause Action Disk I/O FW upgrade started > > from to . Information The firmware upgrade of the No action necessary. [0xB7E (2942)] Disk I/O or RAID Controller I/O module firmware has started. The process uploads the firmware to the buffer on the controller and starts the update on the module. The update will occur on all the Disk I/O or RAID Controller I/O modules connected to the controller. At the end of the update process, if the update process is successful, the RAID Controller I/O and Disk I/O modules will be reset. Disk I/O FW upgrade finished > > from to . Information The firmware upgrade of the No action necessary. [0xB7F (2943)] Disk I/O - RAID Controller I/O module firmware has completed successfully. The RAID Controller and Disk I/O or RAID Controller I/O module will be reset. Disk I/O FW upgrade stopped due to error. Error The firmware upgrade of the No action necessary. [0xB80 (2944)] Disk I/O or RAID Controller I/O module firmware has stopped because the update process has encountered an error. However, the update process will resend the firmware and continue with the process update. At the end of the update process, if the update process is successful, the RAID Controller I/O and Disk I/O modules will be reset. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-7 ULTAMUS RAID 1200 User Guide Event Log Lists Alarm Events These events are related to the audible alarm reported by the SES processor. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. Alarm Event Messages Type [ID] Cause Alarm Mute. Information The user muted the alarm. [0xB8D (2957)] The audible alarm is temporarily muted. Alarm Disable. Information The user disabled the alarm. No action necessary. [0xB8E (2958)] The audible alarm has been disabled and will silence all alarm events. The disabled alarm will be cleared when the Alarm is enabled or the controller is reset. Alarm Enable. The user disabled the alarm. No action necessary. Information [0xB8F (2959)] The audible alarm has been enabled and will allow all alarms to be heard. Information No status condition being [0xC6E (3182)] reported. Where is the alarm number. Alarm silenced. Currently there is only one alarm in the enclosure system, however this is a provision for future expansion. Alarm is Off (Muted). Action No action necessary. No action necessary. User pressed the Alarm Mute button on the front panel. Alarm is Intermittent. Warning A status condition caused Press the Alarm Mute button [0xC6E (3182)] the alarm to sound every two on the front panel and isolate the cause of the minutes until muted. alarm. Alarm is Remind. Warning A status condition that [0xC6E (3182)] 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. Alarm is On Continuous. Error A status condition caused [0xC6E (3182)] the alarm to sound. Press the Alarm Mute button on the front panel and isolate the cause of the alarm. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-8 ULTAMUS RAID 1200 User Guide Event Log Lists Drive and Array Events These events are related to the drives, loops (where applicable) and disk arrays. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. Drive & Array Event Messages Type [ID] Cause Typically due to a nonThe drive w/SN (Slot Error , Enclosure ) ( Drive ) has failed due to an unrecoverable error. Sense Data: //. The drive w/SN (Slot ) (Drive ) has been marked as failed because it was removed. Action Replace the disk drive. Error Drive has been removed or Replace the disk drive. [0xB0B (2827)] bypassed by the user, or has Replace the cables. a serious hardware error. Removal of cables connecting the enclosures. Rebuilding has failed due to an Error Typically due to a nonunrecoverable error on the new [0xB0C (2828)] recoverable media error, or drive w/SN (Slot hardware error. (Drive ) in the array. Replace with a new drive and initiate a rebuild. Rebuilding has failed due to an unrecoverable error on the new drive w/SN (Slot , Enclosure ) ( Drive ). Error Typically due to a non[0xB0D (2829)] recoverable media error or hardware error. Backup all data and restore to a new array. The drive w/SN (Slot , Enclosure ) (Slot ) (Drive ) has failed due to a time-out. Error Drive error. [0xB0E (2830)] Replace the disk drive. Remove the drive in the Disabled Enclosure Slot Error This indicates that the due to excessive errors. [0xB13 (2835)] controller has shutdown the identified slot will re-enable the PHY. slot due to multiple errors from the drive. This may be due to a bad drive or MUX Transition card. SATA Multiplexer switching failure on Enclosure Slot . Error This indicates that the [0xB13 (2835)] controller has tried multiple times to switch Replace the disk drive orþMUX Transition Board (dongle). the Multiplexer (MUX) on a SATA drive and it has not been successful.þ This may be due to a bad drive or MUX Transition card (dongle). Array is in a critical state. 10400166-102 09/2008 Error Drive removal or failure. [0xB1B (2843)] ©2007,2008 Overland Storage, Inc. Replace the disk drive and rebuild the array. W C-9 ULTAMUS RAID 1200 User Guide Event Log Lists Drive & Array Event Messages Type [ID] Cause Action The drive w/SN (Slot ) returned a bad status while completing a command. SCSI Info: Operation , Status . Warning Unknown status returned by Contact technical support [0xB27 (2855)] the disk drive. and provide them with a copy of the event log. The drive w/SN (Slot , Enclosure ) timed out for the SCSI Operation . Warning Drive hardware error or bus [0xB28 (2856)] error. Check cabling and ensure the disk drives are properly seated. A rebuild has started on the drive Information A rebuild has started. w/SN (Slot [0xB30 (2864)] (Drive ). No action necessary. A rebuild has completed on (Array Drive ). No action necessary. Information A rebuild has completed. [0xB31 (2865)] Information A rebuild has started. A rebuild has re-started on the drive w/SN (Slot [0xB32 (2866)] (Drive ). No action necessary. Array has started initializing. Information Initialization has started. [0xB33 (2867)] No action necessary. Array has completed initializing. Information Initialization has completed. No action necessary. [0xB34 (2868)] Aborted command. A SAS command was aborted on Warning [0xB39 (2873)] the drive w/WWN (Slot , Enclosure ) for the SCSI Op Code (hex string). Possible reasons are: faulty disk drive, faulty drive slot, fault enclosure, cable issue, faulty drive firmware, fault in SAS expander, excessive noise, or possible drive interference. Error Bus error. The controller has detected a [0xB3B (2875) data underrun from the drive w/SN (Slot , Enclosure ) for the SCSI Op Code 0x. 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. Check cabling and ensure that the disk drive is properly seated in its slot. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-10 ULTAMUS RAID 1200 User Guide Drive & Array Event Messages Event Log Lists Type [ID] Cause An unrecoverable drive error has Error [0xB40 (2880)] 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 , Host Loop ID , Mapped LUN Requested , Op Code , Sense Data . No action necessary. Typically due to a nonrecoverable media error, hardware error, or loop (bus) error. Parity check started. A RAID parity check has started Information on . Type of parity [0xB43 (2883)] check = . A RAID parity check has completed on . Type of parity check = . Error Count = . Action Information Parity check completed. [0xB44 (2884)] No action necessary. No action necessary. Warning Parity check canceled by the No action necessary. A RAID parity check has been aborted on . Type [0xB45 (2885)] user. of parity check = . Error Count = . A drive w/SN (Slot , Enclosure ) has been inserted. Information Drive was inserted. [0xB61 (2913)] No action necessary. Information The controller has started [0xB66 (2918)] updating a drive’s firmware. Drive w/SN (Slot ID: Firmware Version: or w/wwn , Slot , Enclosure , Firmware Version:. Information The controller has finished [0xB67 (2919)] updating a drive’s firmware. Drive SN: ID: (Slot ) Firmware Version: or WWN , Slot , Enclosure , Firmware Version:. An array expansion has started on Array . Information Expansion has started. [0xB68 (2920)] No action necessary. An array expansion has completed on Array . Information Expansion has completed. [0xB69 (2921)] No action necessary. An array expansion has restarted Information Expansion has restarted. on Array . [0xB6A (2922)] 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. No action necessary. W C-11 ULTAMUS RAID 1200 User Guide Event Log Lists Drive & Array Event Messages Type [ID] Cause The write-back cache on Array has been disabled. Reason(s): (See Cause). Information Disabling of write-back [0xB6F (2927)] cache for the indicated reasons: Action • Replace the failed controller. • The partner controller has • Charge the backup battery failed. or re-install the battery. • The battery is not charging • Resolve the array issue or present. and rebuild the array.] • The array has become critical. • No action necessary. • A “prepare for shutdown” was received by the controller. The write-back cache on Array has been re-enabled. Information Re-enabling of write-back [0xB70 (2928)] cache. Because of a background verify Warning failure, data blocks at LBA [0xB71 (2929)] from drive SN: (SAS: w/ WWN ) (Slot ) have been reallocated. No action necessary. Data Blocks at LBA on No action necessary. Drive w/ SN (SAS: w/ WWN ) (Slot , Enclosure ) have been reallocated. A rebuild was aborted on (Array Drive ). Information A rebuild was canceled by [0xB73 (2931)] the user. No action necessary. SATA Drive Error: (Slot ) Information . Error Drive or SATA link error. [0xB75 (2933)] No action necessary. A drive w/ SN (Slot ) has been removed. Error A drive w/ WWN [0xB76 (2934)] (Slot , Enclosure ) has been removed. No action necessary. There was a bad block during a rebuild on Array , Drive , LBA , Block Count . Replace drive after rebuild. Warning A bad block was detected [0xB78 (2936)] during the rebuild operation. Restore lost data from a Data loss will occur with that know good backup. data stripe. An unsupported drive w/ (WWN Error [0xB7B (2939)] or SN) (Target ID ) has been inserted. is in an unsupported configuration with a mixture of A/P and A/A SATA drives. Replace the SATA drive with A SATA drive with an A/A one that has a A/P MUX MUX Transition card was installed in a system with an Transition card installed. older model controller (RS1220-F4-5402E). Error The array is marked invalid [0xB8C (2956)] because it contains SATA drives with a mix of ActiveActive and Active-Passive MUX Transition cards. A SATA drive with an ActiveActive MUX Transition card is used in a RS-1220-F45402E enclosure. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. Replace the offending drive with one that contains a matching MUX Transition card as the remaining drive members. Replace the SATA drive with the Active-Active MUX Transition card to one with an Active-Passive MUX Transition card. W C-12 ULTAMUS RAID 1200 User Guide Event Log Lists Controller Port Events These events are related to the host side Controller Port. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. Controller Port Event Messages Type [ID] Cause Action Host Loop 0/1 acquired Loop ID Error Address conflict with either Resolve address conflict. because we were not able [0xB17 (2839)] host adapter or other device to get Loop ID (as specified [0xB18 (2840)] on the same loop. in the controller settings). A LIP has occurred on Host loop . Reason: , The LIP was repeated times. A LIP was generated so that No action necessary. Information [0xB24 (2852)] a loop port could acquire a physical address on an arbitrated loop. A LIP was generated by port ID: so that the loop would be re initialized. A LIP was generated because of a loop failure. A LIP was generated by port ID: because of a loop failure. Host Loop is now up. Information Loop is becoming ready. [0xB25 (2853)] SAS Host Port is now up. SAS port is becoming ready. No action necessary. Information [0xB25 (2853)] Host Loop is down. Information Loop is going down. [0xB26 (2854)] Check/replace the cable. SAS Host Port is down. Information SAS port is going down. [0xB26 (2854)] Check/replace the cable. Information A host has accessed a Logical [0xB2E (2862)] Drive for the first time, or for the first time following a reset or LIP. It accessed it through Host Loop (ID ) with the SCSI command . First access by a particular host after a LIP or reset. No action necessary. No action necessary. A host has accessed a Logical Drive for the first time, or for the first time following a reset. ID accessed it through Host Channel with the SCSI command 0x. Host Loop has reported an error status of 0x to a particular command. Error This may indicate a loop [0xB37 (2871)] reset or LIP during a command, or a loop failure. Repeat Count = . Contact technical support. Host Loop has reported an invalid status of 0x to a particular command. Error This indicates a firmware [0xB38 (2872)] error in the host fibre channel chip. Contact technical support. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-13 ULTAMUS RAID 1200 User Guide Controller Port Event Messages Event Log Lists Type [ID] Cause Action Aborted command. A SAS command was aborted on Error the drive w/ WWN (Slot , Enclosure ) for the SCSI Op Code 0x. Possible reasons are: faulty disk drive, fault drive slot, faulty enclosure, cable issue, faulty drive firmware, fault in SAS expander, excessive noise, or possible drive interference. The controller has generated a LIP on Host Loop , due to a loop error. No action necessary. Error Controller initiated a LIP. [0xB3D (2877)] Information Host systems logs into the The host system w/WWN: and [0xB3F (2879)] controller. Loop ID of has logged into the controller through Host Loop . These events will only be listed for HBAs with SAN LUN Mappings. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. No action necessary. W C-14 ULTAMUS RAID 1200 User Guide Event Log Lists Enclosure Events These events are related to the enclosure components reported by the SES processor. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. Enclosure Event Messages Type [ID] Cause No drives installed in slots 1 No SES drives were found which Error [0xB59 (2905)] or 7. means no enclosure status information can be reported. Enclosure ID conflict. This could be due to the SES slot(s) in the enclosure having no drives installed or the drives are malfunctioning. It may also be due to a drive target ID conflict. Check the enclosure(s) drive’s hard target ID setting. Action Insert a disk drive is either or both drive slots 1 and 7. Check the enclosure ID on all enclosure(s). Enclosure (w/ Warning This error is generated when Verify if the system has gone WWN:) timed [0xB79 (2937)] a command to the Enclosure to SES_LEVEL_1. If it has, out on SCSI command 0x02X. processor time-outs. verify the configuration. Faulty cables, drives, RAID Controller I/O, or Disk I/O module malfunction could be the root cause of this error. You may occasionally see this error during drive insertion, failover/failback or drive removal. As long as the system remains at SES_LEVEL_3 the user does not intervene. If this event is periodically posted in the event log the user may have a hard drive, RAID Controller I/O, or Disk I/O module problem. The system should be inspected to isolate the problem to either drives, or RAID Controller I/O or Disk I/O module. NOTE: This event is only valid for daisy chained systems. Power supply is OK. 10400166-102 09/2008 Information Normal condition reported. [0xC6B (3179)] ©2007,2008 Overland Storage, Inc. No action necessary. W C-15 ULTAMUS RAID 1200 User Guide Event Log Lists Enclosure Event Messages Type [ID] Cause Power supply is operating outside of its specification. Warning The specific power supply [0xC6B (3179)] has failed. Action Replace the power supply module. The specific power supply is Ensure that the specific powered off or mains power power supply On/Off switch is in the On position (l) or removed. mains power is applied. Power supply is in a critical Warning The specific power supply state. [0xC6B (3179)] has failed. Replace the power supply. Ensure that the specific The specific power supply is power supply On/Off switch powered off or mains power is in the On position (l) or mains power is applied. removed. The power supply was removed. Power supply is in an unrecoverable state. Error The power supply was [0xC6B (3179)] removed. Re-insert the power supply, connect the power cord. Power supply is not installed. Error The power supply was [0xC6B (3179)] removed. Re-insert the power supply, connect the power cord and power ON, if necessary. Fan is OK. Information Normal condition reported. [0xC6C (3180)] No action necessary. Fan does not support status detection. Information Unknown status. [0xC6C (3180)] No action necessary. Fan is not installed. Information Cooling fan module was [0xC6C (3180)] removed. Re-inset the cooling fan module, connect the power cord and power ON, if necessary. Fan is in a critical state. Error A specific fan failure. [0xC6C (3180)] Total fan module failure. Replace the cooling fan module. 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. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-16 ULTAMUS RAID 1200 User Guide Enclosure Event Messages Event Log Lists Type [ID] Cause Action Temperature sensor is OK. Information Temperature sensors are [0xC6D (3181)] reporting normal temperatures in the enclosure. No action required. Temperature is operating outside of specifications. Ensure that the cooling fan is operating normally. (Replace if needed.) Warning Temperature sensors are [0xC6D (3181)] reporting enclosure temperatures have reached the threshold of 50°C. If the cooling fan is set to automatic speed control, place the jumper on the Cooling Fan module circuit board to force the fans to high speed. If the environment ambient temperature is high, reduce the ambient temperature. Ensure that the airflow is not blocked or restricted on the enclosure. Temperature sensor is in a Error Temperature sensors are critical state. [0xC6D (3181)] reporting enclosure temperatures have reached the threshold of 70°C. Automatic system shutdown will begin. In Active-Active configurations, one controller will shutdown its partner and shutdown the drives, then itself. Ensure that both cooling fans are operating normally. (Replace if needed.) If the fans are set to automatic speed control, place the jumper on the Cooling fan module circuit board to force the fans to high speed. Temperature sensor is in a Error Temperature sensors are critical state. (continued) [0xC6D (3181)] reporting enclosure temperatures have reached the threshold of 70°C. If the environment ambient temperature is high, reduce the ambient temperature. Ensure that the airflow is not blocked or restricted on the enclosure. Alarm is Off (Muted). Information No condition being reported. No action necessary. [0xC6E (3182)] Alarm silenced. User pressed the Alarm Mute button on the ops panel. Alarm is Intermittent. Error A condition caused the [0xC6E (3182)] alarm to sound every two minutes until muted. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. Press the Alarm Mute button on the ops panel and isolate the cause of the alarm. W C-17 ULTAMUS RAID 1200 User Guide Event Log Lists Enclosure Event Messages Type [ID] Cause Alarm is Remind. Error A condition that caused the Press the Alarm Mute button [0xC6E (3182)] alarm to sound is continuing on the ops panel and isolate to remind the user. the cause of the alarm. Alarm is On Continuous. Error A condition caused the [0xC6E (3182)] alarm to sound. Information An enclosure is now SES SES access fault tolerant: Multiple paths are available for [0xCFD (3325)] fault-tolerant. gathering this enclosure’s status information. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. Action Press the Alarm Mute button on the ops panel and isolate the cause of the alarm. No action necessary. W C-18 ULTAMUS RAID 1200 User Guide Event Log Lists ULTAMUS RAID manager Server Events NOTE: These events are applicable to the host-based version only. The following table provides a brief description of the events which relate to the URM server software component. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. URM Server Event Messages Type [ID] Cause Action The server has been started. Information [0x101 (257)] The URM Server started successfully. No action necessary. The server has been shutdown. Information [0x102 (258)] The host is shutting down or No action necessary. a user stopped the URM service. A system rescan has been initiated. Information [0x103 (259)] The system rescan is starting note: a shutdown and start up event will follow. No action necessary. The serial number and key entered are incorrect. Remote features are temporarily disabled. Error [0x104 (260)] The serial number and key specified in the server settings file is not a correct match. Open URM in a browser from the local console, click the Settings button. Re-enter the serial number and key. If you still have problems, contact technical support. All event logs cleared. Information [0x105 (261)] A user cleared the URM event logs. No action required. A user has updated their password. Information [0x106 (262)] A specific user has updated No action required. their password. A user from Host: , IP Address: unsuccessfully attempted to update their password. A specific user tried to change the password but verification failed or old password failed. Ensure the user is authorized or needs assistance. A user has logged into the Server from Host: , IP Address: . Information [0x106 (262)] A specific user has logged into the URM Server from the specified host and IP address location. No action required. A user has logged out the Server from IP address: . Information [0x106 (262)] A specific user has logged out of the URM Server from the specified IP address location. (The host name was not available.) No action required. A user has logged out the Server from Host: , IP Address: . Information [0x107 (264)] A specific user has logged out of the URM Server from the specified host and IP address location. No action required. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-19 ULTAMUS RAID 1200 User Guide Event Log Lists URM Server Event Messages Type [ID] Cause Action The multicast address is not configured. No communication will take place with other servers. Warning [0x201 (513)] The setting “MulticastPort” is not setup in the db/IP.db file. The setting was removed or the file became corrupt. Open the file \db\IP.db in a text editor, and add the following line: MulticastPort=9191. Save the file and start URM and press the Rescan button or restart the URM service. Multicast socket creation failure: Warning [0x202 (514)] URM could not setup the necessary communication paths to talk to other URM Servers. The specific cause will be specified in the appended to the message. Change the multicast port used by URM. Note that all URM servers must communicate with each other on the same multicast port. If the setting is changed on one, they must be changed on all URM Servers. Multicast socket creation failure: Warning (continued) [0x202 (514)] URM could not setup the necessary communication paths to talk to other URM Servers. The specific cause will be specified in the appended to the message. Open the file \db\IP.db in a text editor, and change the following line: MulticastPort=. Save the file and start URM and press the Rescan button or restart the URM service. Error [0x301 (769)] URM tried to create/locate the shared memory used for the Server and Server CGI script to communicate. Quit URM and all connections accessing this URM Server, wait 1 minute and restart them. A CGI request was initiated from Error [0x302 (770)] the GUI but the associated shared memory could not be opened. The Server script creates new shared memory for the Server to access parameter passed from the GUI. This shared memory could not be found. Retry request. The Server script creates new parameter for the Server to access parameter passed from the GUI. This parameters could not be found. Retry request. The request was performed but the Server encountered an error that prevented completion. Retry request. Shared memory used for the Server and the GUI to communicate could not be created nor located. A CGI request was initiated from Error the GUI but the associated [0x303 (771)] parameters could not be located. The Server performed a CGI request but an internal error prevented the Server from returning the results. Error [0x304 (772)] Quit URM and all connections accessing this URM Server, wait 1 minute and restart them. Restart the system. Quit URM and all connections accessing this URM Server, wait 1 minute and restart them. Restart the system. Quit URM and all connections accessing this URM Server, wait 1 minute and restart them. Restart the system. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W C-20 ULTAMUS RAID 1200 User Guide Event Log Lists URM Server Event Messages Type [ID] Cause Action The Server performed a CGI request but the shared memory needed to return the results could not be created. Error [0x305 (773)] The Server completed the request and attempted to create shared memory to send the results back to the Server CGI. The attempt failed. Retry request. The Server completed the request but by the time it was done the Server CGI gave up. Retry request. The Server failed to complete a CGI request before its allowed time expired. Error [0x306 (774)] Quit URM and all connections accessing this URM Server, wait 1 minute and restart them. Restart the system. Quit URM and all connections accessing this URM Server, wait 1 minute and restart them. Restart the system. The Server CGI script was unable Error to return CGI request results to [0x307 (775)] the GUI. Start up is complete. The Server passed the completed request to the Server CGI but for some reason the request wasn’t completed correctly by the Server CGI script. Information The controller module has [0xA01 (2561)] been loaded by the URM Server. Retry request. Quit URM and all connections accessing this URM Server, wait 1 minute and restart them. Restart the system. No action necessary. Several failures encountered Error Several commands have while trying to communicate with [0xA03 (2563)] been sent through a known good path but they have the RAID controller. failed. Ensure that the paths and hardware are operational. Successful communication with controller after several failures. No action necessary. 10400166-102 09/2008 Information A known failed path is now [0xA04 (2564)] functional and passed retest. ©2007,2008 Overland Storage, Inc. W C-21 ULTAMUS RAID 1200 User Guide Event Log Lists SnapShot Events The following table provides a brief description of the events which relate to the Snapshot component. The ID is listed in its hexadecimal value, which appears in the Unix operating system, and its equivalent decimal value in parenthesis, which appears in the Microsoft Windows operating system. Snapshot Event Messages Type [ID] Cause Action Logical Drive ’s Snapshot Warning ODA capacity has reached capacity is at %. [0xB81 (2945)] the indicated threshold. • Delete some snapshots for this snapshotted logical drive. Logical Drive ’s ODA is invalid. Error ODA is no longer valid [0xB81 (2945)] because of a RAID or snapshot error. • Restore from backup. Logical Drive ’s ODA has been overrun. Error ODA is no longer valid. [0xB81 (2945)] Capacity was exceeded during last snapshot. • Restore from backup. Logical Drive ’s had an ODA unassigned from it. Information ODA was unassigned. [0xB82 (2946)] No action necessary. Logical Drive ’s had an ODA assigned from it. Information ODA was assigned. [0xB82 (2946)] No action necessary. Snapshot <#> on Logical Drive has been deleted. Information Snapshot was deleted. [0xB84 (2948)] No action necessary. Snapshot <#> on Logical Drive has been created. Information Snapshot was created. [0xB84 (2948)] No action necessary. • Establish a larger storage area for this snapshotted logical drive. • Establish a larger storage area for this snapshotted logical drive. A snapback operation was A Snapback (based on Snapshot Information ) on Logical Drive has [0xB84 (2948)] started by the operator. been started . No action necessary. A Snapback (based on Snapshot Information A snapback operation has ) on Logical Drive has [0xB84 (2948)] successfully completed. completed . No action necessary. A Snapshot had an error on Logical Drive . Inspect the logical drives and arrays. Error There is a problem with the [0xB85 (2949)] logical drive being snapshotted. License has been modified - the Information A license update/upgrade new level is <#>. [0xB86 (2950)] was performed. Snapshot metadata was left in the controller cache and the power was removed and the battery was drained before the cache was flushed. A flush occurs every two seconds. Metadata is no longer valid. Fatal loss of snapshots will be the result. 10400166-102 09/2008 Error Snapshot metadata was in [0xB88 (2952)] the controller cache when the power was removed before the cache flushed. Followed by the backup battery was drained with a loss of the metadata. ©2007,2008 Overland Storage, Inc. No action necessary. Loss of snapshot, Perform a new snapshot and ensure the power remains constant. W C-22 ULTAMUS RAID 1200 User Guide Event Log Lists Snapshot Event Messages Type [ID] Metadata in the cache is invalid or out of date. Warning A controller was inserted No action necessary. [0xB88 (2952)] that contained old snapshot metadata in its cache. Snapshot metadata recovery was started. Information A snapshot metadata [0xB88 (2952)] recovery from cache was started. No action necessary. Snapshot metadata recovery from cache just completed. Information A snapshot metadata [0xB88 (2952)] recovery from cache was completed. No action necessary. 10400166-102 09/2008 Cause ©2007,2008 Overland Storage, Inc. Action W C-23 Glossary NOTE: This is a general Overland Storage glossary and acronym list. Not all items may be found in this document or be used by this product. 1000BASE-T 1000BASE-T (also known as IEEE 802.3ab) is a standard for gigabit Ethernet over copper wiring. It requires, at a minimum, Category 5 cable (the same as 100BASETX), but Category 5e ("Category 5 enhanced") and Category 6 cable may also be used and are often recommended. 1000BASE-T requires all four pairs to be present and is far less tolerant of poorly installed wiring than 100BASE-TX. Address An address is a data structure or logical convention used to identify a unique entity, such as a particular process or network device. Array A group of disk drives that are combined together to create a single large storage area. Up to 64 arrays are supported, each containing up to 16 drives per array. There is no capacity limit for the arrays. Auto Balance A feature that automatically balances preferred paths evenly among all available host ports and controller ports. Auto balancing spreads I/O load by utilizing as many host ports and controller ports as possible. Back-end Front-end and back-end are terms used to characterize program interfaces and services relative to the initial user, human or program, of these interfaces and services. A "front-end" application is one that application users interact with directly. A "back-end" application or program serves indirectly in support of the front-end services, usually by being closer to the required resource or having the capability to communicate with the required resource. The back-end application may interact directly with the front-end or, perhaps more typically, is a program called from an intermediate program that mediates front-end and back-end activities. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-1 ULTAMUS RAID 1200 User Guide Glossary 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 to 10 percent. This is sometimes known as Reserved Capacity. Bar Code The machine-readable representation of a product code. Bar codes are read by a scanner that passes over the code and registers the product code. The width of black lines and white spaces between varies. Combinations of lines and spaces represent characters. Overland uses 3-of-9 code (Code 39) where each character is represented by 9 bars, 3 of which are wide. Bridging Devices that connect and pass packets between two network segments that use different communications protocol. Bus or Channel A common physical path composed of wires or other media, across which signals are sent from one part of a computer to another. A channel is a means of transferring data between modules and adapters, or between an adapter and SCSI devices. A channel topology network consists of a single cable trunk that connects one workstation to the next in a daisy-chain configuration. All nodes share the same medium, and only one node can broadcast messages at a time. Cache Flush Array This is the array that is used to automatically flush cache data in a situation where power has failed to some of the drives. Cat 5 Cable Short for Category 5, it is network cabling that consists of four twisted pairs of copper wire terminated by 8P8C modular connectors. CAT 5 cabling supports frequencies up to 100 MHz and speeds up to 100 Mbps. (CAT 5e cabling supports frequencies up to 1000 MHz and speeds up to 1000 Mbps.) It can be used for ATM, token ring, 1000BASE-T, 100BASE-T, and 10BASE-T networking. Cat 5 is based on the EIA/TIA 568 Commercial Building Telecommunications Wiring Standard developed by the Electronics Industries Association as requested by the Computer Communications Industry Association in 1985. Cat 6 Cable Short for Category 6, it is network cabling that consists of four twisted pairs of copper wire terminated by 8P8C modular connectors made to higher standards that help reduce noise caused by crosstalk and system noise. The ANSI/TIA-568B.2-1 specification states the cable may be made with 22 to 24 AWG gauge wire, so long as the cable meets the specified testing standards. It is designed for Gigabit Ethernet that is backward compatible with the Category 5/5e and Category 3 cable standards. Cat 6 features more stringent specifications for crosstalk and system noise. The cable standard provides performance of up to 250 MHz and is suitable for 10BASE-T / 100BASE-TX and 1000BASE-T (Gigabit Ethernet). 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-2 ULTAMUS RAID 1200 User Guide Glossary Chunk Size This is the amount of data that is written on a single drive before the controller moves to the next drive in the stripe. DSM Short for Device Specific Module, it is a software module that allows the ULTAMUS RAID storage array hardware to use Microsoft's MPIO. Expansion Slot Area in a computer that accepts additional input/output boards to increase the capability of the computer. F_port A Fabric port within a Fibre Channel switch that provides a point-to-point link attachment to a single N_Port. F_Ports are intermediate ports in virtual point-topoint links between end ports, for example N_Port to F_Port to F_Port to N_Port using a single Fibre Channel fabric switch. FL_port A Fabric Loop port within a Fibre Channel switch that is capable of Fibre Channel Arbitrated Loop operations and is connected to one or more NL_Ports via a Fibre Channel Arbitrated Loop. An FL_Port becomes a shared entry point for public NL_Port devices to a Fibre Channel fabric. FL_Ports are intermediate ports in virtual point-to-point links between end ports that do not reside on the same loop, for example NL_Port to FL_Port to F_Port to N_Port through a single Fibre Channel fabric switch. Failback Failback occurs when a path with a higher priority than the currently active path is restored. In this case, I/O will “fail back” to the higher priority path once it is available again. Failover The ability to automatically substitute a working system or path for one which has failed. Failover/Failback A combination of Failover and Failback. When a preferred path becomes unavailable, another path is used to route I/O until the preferred path is restored. In this case I/O will "fail back" to the preferred path once it is available again. FC-AL Short for Fibre Channel Arbitrated Loop. An FC-AL is a Fibre Channel network in which up to 126 systems and devices are connected in a loop topology, with each transmitter connecting to the receiver of the device on its logical right. The Fibre Channel Arbitrated Loop protocol used for transmission is different from Fibre Channel switched and point-to-point protocols. Multiple FC-AL loops can be connected via a fabric switch to extend the network. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-3 ULTAMUS RAID 1200 User Guide Glossary Firmware Software stored in read-only memory (ROM) or programmable ROM (PROM). Firmware is often responsible for the behavior of a system when it is first switched on. Front-end See Back-end. Gigabit Ethernet Also known as GigE or GbE, this Ethernet standard uses a one Gigahertz (1000 Hz) clock rate to move data. HBA Short for Host Bus Adapter. An HBA is an I/O adapter that sits between the host computer's bus and the Fibre Channel loop and manages the transfer of information between the two channels. In order to minimize the impact on host processor performance, the HBA performs many low-level interface functions automatically or with minimal processor involvement. Hot Swap The action of components being removed and replaced while the unit is running, with power to either the component or a device still connected to the unit. Not all components are hot swappable. Please read installation and maintenance instructions carefully. Internet A global network of networks used to exchange information using the TCP/IP protocol. It allows for electronic mail and the accessing ad retrieval of information from remote sources. Initialization RAID 5, 6, and 50 disk arrays must have consistent parity before they can be used to protect data. Initialization writes a known pattern to all drives in the array. If you choose not to initialize an array, the array will be trusted. Any drive failure results in data corruption in a trusted array. (It is possible to later perform a parity rewrite that recalculates the parity based on the current data, thus ensuring the data and parity are consistent.) Initiator Device A system component that originates an I/O command over an I/O bus or network. An initiator issues the commands; a target receives them. Internal Logical Drive An internal logical drive is identical to a regular logical drive, except it is NOT made visible to a host adapter as a LUN. Instead, internal logical drives are used for setting up snapshot ODAs that are only accessed internally by the RAID controller. IP Short for Internet Protocol. IP specifies the format of packets and the addressing scheme. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-4 ULTAMUS RAID 1200 User Guide Glossary iSCSI Short for Internet SCSI. iSCSI is an IP-based storage networking standard for linking data storage facilities, developed by the Internet Engineering Task Force (IETF). By carrying SCSI commands over IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. The iSCSI protocol is among the key technologies expected to help bring about rapid development of the storage area network (SAN) market, by increasing the capabilities and performance of storage data transmission. Because of the ubiquity of IP networks, iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable locationindependent data storage and retrieval. iSNS Server Short for Internet Storage Name Service Server. This is a server on an iSCSI SAN providing name registration service and query capability to other iSCSI clients per the IETF draft iSNS specification. LAN Short for Local Area Network. A network connecting computers in a relatively small area such as a building. LED Short for Light-Emitting Diode. An LED is a type of diode that emits light when current passes through it. Visible LEDs are used as indicator lights on electronic devices. Logical Drive A drive that is defined or created from regions of an array, a whole array, or a combination of regions of different arrays. The logical drive appears as a single disk to one or more host systems. Logical Drive Availability 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. LUN Short for Logical Unit Number. A SCSI or Fibre Channel device identifier. LUN is a subdivision of a SCSI target. MAC Address Short for Media Access Control address, a hardware address that uniquely identifies each node of a network. 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 reconfigured to maintain access to the logical drive. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-5 ULTAMUS RAID 1200 User Guide Glossary Mapping table A table indexed by sequential LUN values, indicating the selected BUS:TARGET:LUN devices. Mapping tables are used by routers and bridges like the GEOi to perform Ethernet-to-SCSI pathing. MD5 Algorithm MD5 is a way to verify data integrity, and is much more reliable than checksum and many other commonly used methods. MPIO Short for Multipath Input/Output. A multipath solution built into Microsoft server-grade operating systems. It requires the DSM to work with the ULTAMUS RAID storage array hardware. MTU Short for Maximum Transfer Unit. It is the largest size packet or frame, specified in octets (eight-bit bytes), that can be sent in a packet- or frame-based network. N_port A Node port connects via a point-to-point link to either a single N_Port or a single F_Port. N_Ports handle creation, detection, and flow of message units to and from the connected systems. N_Ports are end ports in virtual point-to-point links through a fabric, for example N_Port to F_Port to F_Port to N_Port using a single Fibre Channel fabric switch. Network Interface Card (NIC) A board that provides network communication capabilities to and from a computer. NDMP Short for Network Data Management Protocol. A protocol standard used by some Network Attached Storage systems to provide an industry standard means to do backup and restores of the NAS system without the need for 3rd party agents to be installed on the NAS device. Also see NDMP.org for further details. NL_port A Node Loop port is capable of arbitrated loop functions and protocols. An NL_Port connects via an arbitrated loop to other NL_Port and at most a single FL_Port. NL_Ports handle creation, detection, and flow of message units to and from the connected systems. NL_Ports are end ports in virtual point-to-point links through a fabric, for example NL_Port to F_Port to F_Port to N_Port using a single Fibre Channel fabric switch. In the absence of a fabric switch FL_Port, NL_Ports can communicate with other NL_Ports in virtual point-to-point links through a FC-AL open loop circuit often through FC-AL (Arbitrated Loop) hub or loop switch devices. Node Name This is an eight-byte, 16-character hexadecimal number, uniquely identifying a single fibre device. It incorporates the World Wide Name and two additional bytes that are used to specify the format. In a host system with multiple FC ports, all adapters typically use the same Node Name, but unique Port Names. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-6 ULTAMUS RAID 1200 User Guide Glossary NVRAM Abbreviation of Non-Volatile Random Access Memory, a type of memory that retains its contents when power is turned off. ODA The Overwrite Data Area is an internal storage area on an array that is dedicated to storing data from a snapshot logical drive. The data stored on the ODA is the data from the logical drive that needed to be overwritten after a snapshot was initiated. The ODAs are mapped on top of internal logical drives. An ODA cannot be accessed externally through a host LUN; it is only accessed internally. ODA Stripe Size The read/write block size that the system will use when copying data from the original logical drive to the ODA. Port Name This is an eight-byte hexadecimal number, uniquely identifying a single host HBA port. It incorporates the World Wide Name and two additional bytes that are used to specify the format and indicate the port number. Preferred Path The preferred path is the default path. When the path selection policy is set to Failover/Failback, the preferred path is always used if it is available. If the preferred path fails, I/O switches to another path. If it is later restored, I/O switches back to the preferred path. PTP Short for Point-to-Point. PTP is the common mode of attachment to a single host. PTP is sometimes used to attach to a Fibre Channel switch for SAN connectivity. RAID Level 0 RAID 0 is defined as disk striping where data is striped or spread across one or more drives in parallel. RAID 0 is ideal for environments in which performance (read and write) is more important than fault tolerance, or you need the maximum amount of available drive capacity in one volume. Drive parallelism increases throughput because all disks in the stripe set work together on every I/O operation. For greatest efficiency, all drives in the stripe set must be the same capacity. Because all drives are used in every operation, RAID 0 allows for singlethreaded I/O only (i.e., one I/O operation at a time). Environments with many small simultaneous transactions (e.g., order entry systems) do not get the best possible throughput. RAID Level 1 RAID 1 is defined as disk mirroring where one drive is an exact copy of the other. RAID 1 is useful for building a fault-tolerant system or data volume, providing excellent availability without sacrificing performance. However, you lose 50 percent of the assigned disk capacity. Read performance is somewhat higher than write performance. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-7 ULTAMUS RAID 1200 User Guide Glossary RAID Level 5 RAID 5 is defined as disk striping with parity where the parity data is distributed across all drives in the volume. Normal data and parity data are written to drives in the stripe set in a round-robin algorithm. RAID 5 is multi-threaded for both reads and writes because both normal data and parity data are distributed roundrobin. This is one reason why RAID 5 offers better overall performance in server applications. Random I/O benefits more from RAID 5 than does sequential I/O, and writes take a performance hit because of the parity calculations. RAID 5 is ideal for database applications. RAID Level 6 RAID-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- require more raw capacity than RAID-5 for an equivalent usable storage capacity. RAID Level 10 RAID 10 is defined as mirrored stripe sets or also known as RAID 0+1. You can build RAID 10 either directly through the RAID controller (depending on the controller) or by combining software mirroring and controller striping, or vice versa (called RAID 01). RAID Level 50 This RAID level is a combination of RAID level 5 and RAID level 0. Individual smaller RAID 5 arrays are striped to give a single RAID 50 array. This can increase the performance by allowing the controller to more efficiently cluster commands together. Fault tolerance is also increased, as one drive can fail in each individual array. RETMA Short for Radio-Electronics-Television Manufacturers' Association. It is the common name given for a 19-inch distribution frame rack for mounting components. Round Robin The Round Robin path selection policy causes all healthy paths to be used for I/O. Paths are used in a round-robin order. Router A router is a device that enables connectivity between Ethernet network segments. SAN Short for Storage Area Network. A shared storage architecture connecting computers and storage devices for online data access. Each connected system can directly access any attached storage device. Usually refers to the network behind servers that links one or more servers to one or more storage systems. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-8 ULTAMUS RAID 1200 User Guide Glossary SAS Short for Serial Attached SCSI. It is a point-to-point serial protocol that replaces parallel SCSI bus technology and uses the standard SCSI command set. At present it is slightly slower than the final parallel SCSI implementation, but in 2009 it will double its present speed to 6 Gbit/s, allowing for much higher speed data transfers than previously available, and is "downwards" compatible with second generation SATA drives. SCSI Short for Small Computer System Interface. SCSI is an industry standard for connecting peripheral devices and their controllers to an initiator. Storage devices are daisy-chained together and connected to a host adapter. The host adapter provides a shared bus that attached peripherals use to pass data to and from the host system. Examples of devices attached to the adapter include disk drives, CDROM discs, optical disks, and tape drives. In theory, any SCSI device can be plugged into any SCSI controller. SCSI addressing Each device supported by a SCSI adapter has its own unique SCSI address, which dictates the device’s priority when arbitrating for access to the SCSI bus. A SCSI address of 7 has the highest priority. For a fast/wide SCSI adapter that supports up to 16 devices, the next highest priority address is 6, then 5, 4, 3, 2, 1, 0, 15, 14, 13, 12, 11, 10, 9, and 8. The narrow SCSI adapter supports up to eight devices, including itself. The SCSI address 7 has the highest priority, followed by 6, 5, 4, 3, 2, 1, and 0. SCSI bus A SCSI bus provides a means of transferring data between SCSI devices. A SCSI bus is either an 8- or 16-bit bus that supports up to 8 or 16 devices, including itself. The bus can consist of any mix of initiators and targets, with the requirement that at least one initiator and one target must be present. SCSI device A SCSI device is a single unit on a SCSI bus that originates or services SCSI commands. A SCSI device is identified by a unique SCSI address. SCSI devices can act as initiators or targets. SCSI port A SCSI port is an opening at the back of a router that provides connection between the SCSI adapter and SCSI bus. Snapback The process of restoring a logical drive from a selected snapshot. This process takes place internally in the RAID controller firmware and needs no support from any backup utility. Snapshot A method for producing a point-in-time image of a logical drive. In the process of initiating a snapshot, no data is actually copied from the snapshotted logical drive. However as new writes are made to a snapshotted logical drive, existing data blocks are copied to the ODA before the new data is written to the logical drive. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-9 ULTAMUS RAID 1200 User Guide Glossary Snapshot LUN A special LUN created from a combination of the snapshot logical drives’ data and the data contained in the ODA. Snapshot Number Identifier that references one of several snapshots of the same logical drive. Snapshotted LD A logical drive that has one or more snapshots initiated on it. Storage Area Network See SAN. Stripe The process of separating data for storage on more than one disk. For example, bit striping stores bits 0 and 4 of all bytes on disk 1, bits 1 and 5 on disk 2, etc. Stripe Size This is the number of data drives multiplied by the chunk size. Sub-array In RAID 50 applications, this is the name given to the individual RAID 5 arrays that are striped together. Each sub-array has one parity drive. Target A target is a device (peripheral) that responds to an operation requested by an initiator (host system). Although peripherals are generally targets, a peripheral may be required to act temporarily as an initiator for some commands (for example, SCSI COPY command). Telnet A terminal emulation program for TCP/IP networks such as the Internet. The Telnet program runs on a computer and connects it to a server on the network. You enter commands through the Telnet program and they will be executed as if you were entering them directly on the server console. This enables you to control the server and communicate with other servers on the network. To start a Telnet session, you must log in to a server by entering a valid user name and password. Telnet is a common way to remotely control Web servers. Terminator A terminator refers to the electrical connection at each end of a SCSI bus. The terminator is composed of a set of resisters, or possibly other components. The function of a terminator is to provide a pull-up for open collector drivers on the bus, and also impedance matching to prevent signal reflections at the ends of the cable. SCSI buses require that a terminator be placed on the SCSI connector on the last SCSI peripheral. Data errors may occur in a SCSI bus that is not terminated. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-10 ULTAMUS RAID 1200 User Guide Glossary TOE (TCP Offload Engine) Short for TCP Offload Engine. TOE is a technology used in network interface cards to offload processing of the entire TCP/IP stack to the network controller. It is primarily used with high-speed network interfaces, such as gigabit Ethernet and 10 gigabit Ethernet, where processing overhead of the network stack becomes significant. Topology Logical layout of the parts of a computer system or network and their interconnections. There are two types of topology: physical and logical. The physical topology of a network refers to the configuration of cables, computers, and other peripherals. Logical topology is the method used to pass the information between workstations. 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. USB (Universal Serial Bus) Port A hardware interface for low-speed peripherals such as the keyboard, mouse, joystick, scanner, printer, and telephony devices. Virtual LUN See Snapshot LUN. VLAN Short for Virtual LAN. It consists of a network of computers that behave as if they are connected to the same wire - even though they may actually be physically connected to different segments of a LAN. Write-Back Cache A caching method in which modifications to data in the cache aren't copied to the cache source until absolutely necessary. Write-back caching yields somewhat better performance than write-through caching because it reduces the number of write operations to main memory. With this performance improvement comes a slight risk that data may be lost if the system crashes. 10400166-102 09/2008 ©2007,2008 Overland Storage, Inc. W GL-11 Index Symbols > (Flow Indicator) ............................................ PR-v A About Software Version..................................... 6-8 Access Statistics ........................................................ 6-2 Access Alignment................................................ A-2 Access Size............................................................ A-2 Accessing SAN LUN Mapping ......................... 4-1 Additional Functions.......................................... 6-1 Advanced Functions ........................................... 7-1 Advanced Power Management ............... 3-8, 7-16 Alignment statistic ............................................. 6-4 APM Level 1....................................................... 7-16 APM level 2 .......................................................... 3-8 Array Events ........................................................ C-9 Array Power Management................................ 3-8 Array Rebuild ...................................................... 7-6 Auto Rebuild option............................................ 5-9 Auto Spare option ...................................... 3-13, 5-9 Auto Update option .......................................... 5-10 Automatically Updating Controller Firmware 54 Available Drive Space...................................... 7-13 B Background Drive Verification option ......... 5-10 Back-off Percent ......................................... 3-4, 7-11 Battery Not Charging Write-back Cache Disabled ..................... C-12 Bytes Transferred Statistic .............................. 6-3 C Chunk size ................................................... 3-4, 7-10 Clearing the Configuration............................. 7-13 Command Cluster Statistics ............................ 6-6 10400166-102 09/2008 Command Size statistic...................................... 6-4 Configuration Environment.................................................. 5-2 Name ............................................................... 5-7 Notification .................................................... 2-3 Overview....................................................... 7-11 Restoring ...................................................... 7-12 Configuration WWN ........................................... 5-7 Configuring Additional Monitoring ................. 2-9 Configuring Array Write-back Cache ............. 3-6 Configuring for E-MAIL..................................... 2-4 Configuring Network Settings.......................... 2-2 Connection Host Ports..................................................... 5-12 Controller ........................................................... C-13 Controller Environment..................................... 5-1 Controller Event Battery Failure ............................................ C-2 Battery OK.................................................... C-3 Cache Disabled........................................... C-12 Cached Data Lost ........................................ C-4 Configuration Changed .............................. C-3 Controller Failback Completed ................ C-4 Controller Failback Started ...................... C-4 Controller Failed ......................................... C-2 Controller Failover Completed................. C-4 Controller Failover Started....................... C-4 Controller Firmware Upgraded ............... C-4 Controller Powered On............................... C-3 Controller Present....................................... C-2 Controller Removed .................................... C-2 Controller Reset........................................... C-3 Controller Self-Test Failed........................ C-3 Controller Self-Test Passed....................... C-3 Controller Shutdown .................................. C-4 Controller Time-out .................................... C-2 Controller Timeout...................................... C-2 Controller Valid ........................................... C-3 Ctrl Temp Exceeded............................ C-1, C-2 Event Log Cleared....................................... C-3 Fatal Watchdog Error ................................ C-1 Flush Cache Completed ............................. C-4 ©2007,2008 Overland Storage, Inc. W IX-1 ULTAMUS RAID 1200 User Guide Index Flush Cache Started ................................... C-4 Flush Mirrored Cache................................. C-3 Flush Mirrored Cache Started.................. C-3 Recovered SDRAM ECC Error ................. C-4 Synchronization Completed ........... C-3, C-12 Synchronization Started ............................ C-3 Voltage Error ................................................ C-2 Controller Events................................................ C-1 Controller Firmware Update ........................... 5-4 Controller Information ...................................... 5-1 Controller LUN ................................................... 5-8 Controller Management .................................... 5-1 Controller Port Data Rate............................... 5-12 Controller Port Events..................................... C-13 Controller Port ID............................................. 5-11 Controller Ports................................................. 3-16 Conventions....................................................... PR-v Create SAN LUN Mapping ..................................... 4-4 Creating Array .................................................... 3-2 Creating Arrays................................................... 3-1 D Data Rate............................................................ 5-12 Dedicated Spare ................................................ 3-12 Delete SAN LUN Mapping ..................................... 4-5 Delete a SYSLOG Server .................................. 2-8 Deleting Snapshot ...................................................... 8-11 Deleting a Logical Drive.................................. 7-15 Deleting Addressee............................................. 2-5 Deleting an Array ............................................... 7-3 Deleting an SNMP Server ................................ 2-6 DHCP..................................................................... 2-3 Diagnostic Dump................................................. 5-3 Different Node Name ......................................... 5-8 Disable Write-back Cache................................. 3-5 Disabling Snapshot ...................................................... 8-16 Drive Event Array Critical..................................... C-9, C-11 Array Expansion Complete ..................... C-11 Array Expansion Restarted..................... C-11 Array Initialization Complete................. C-10 Array Initialization Started .................... C-10 Drive Rebuild Failure ................................. C-9 Drive Status ................................................ C-10 Drive Task Full ............................................ C-9 Drive Time-out ........................................... C-10 Drive Time-out Failure............................... C-9 FW Download Complete................ C-11, C-12 10400166-102 09/2008 New Drive Rebuild Failure ....................... C-9 Rebuild Aborted ......................................... C-12 Rebuild Complete ...................................... C-10 Rebuild Restarted...................................... C-10 Rebuild Started.......................................... C-10 SES Initialized ........................................... C-15 Drive Events ........................................................ C-9 Drive Identify Icon .............................................. 7-3 Drive Panel Access ............................................ 7-13 Drive Power Management ............................... 7-16 Drive Selection for RAID 5 and RAID 6 Arrays 3-2 Drive Status Rebuilding .................................................... 1-11 Dynamic IP (DHCP)............................................ 2-3 E E-MAIL Notification ........................................... 2-4 Enabling Snapshot......................................................... 8-5 Enclosure Events .............................................. C-15 Enclosure Support ............................................. 5-10 Event Logs............................................................ C-1 Execution Throttle............................................... 6-1 Expanding an Array............................................ 7-7 Expansion Module Events ................................ C-7 F Failed Drives ....................................................... B-5 Failover .................................................................. 6-1 Failover, Performance and Additional Functions 6-1 Faster Rebuild..................................................... A-4 Fault Tolerance options...................................... 5-9 Fee Drive Space ................................................. 7-13 Firmware Environment.................................................. 5-2 Update............................................................. 5-4 Firmware Environment ..................................... 5-2 G Gateway ................................................................. 2-3 Getting Started .................................................... 2-1 Global Spare ....................................................... 3-11 H Hardware Environment.................................................. 5-2 Host Event ©2007,2008 Overland Storage, Inc. W IX-2 ULTAMUS RAID 1200 User Guide Index CC to Host ID ............................................. C-11 Controller LIP ............................................ C-14 Detected Power-on/Reset ......................... C-13 Host Port Incorrect Address.................... C-13 Logged in at ID........................................... C-14 Loop Down................................................... C-13 Loop Up........................................................ C-13 SAS Host Port Down................................. C-13 SAS Host Port Up ...................................... C-13 Host Ports ........................................................... 5-11 Hot Spare Drives............................................... 3-10 I Identity.................................................................. 5-7 Initialization Pause .............................................................. 3-8 Resume........................................................... 3-8 Initialization Priority....................................... 5-10 Initialize................................................................ 3-4 Initializing Arrays .............................................. 3-7 Internal Logical Drive .................................... GL-4 Inter-server Communication ............................ 1-6 Introduction.......................................................... 1-1 L Logical Drive Delete............................................................ 7-15 Logical Drive Capacity .................................... 3-15 Logical Drive Creation..................................... 3-14 Logs ........................................................................ C-1 LUN Mapping ...................................................... 4-1 LUN Number ..................................................... 3-16 M Many-to-many Mapping .................................... 2-6 Mapping ................................................................ 4-1 Mapping a Snapshot ........................................ 8-10 Mirror Cache........................................................ 3-5 Mixed Drive Types............................................ 1-15 Modifying a SAN LUN Mapping ..................... 4-6 Modifying Arrays ................................................ 7-3 Monitoring initialization ................................... 3-5 Multicast ............................................................... 1-6 N Navigating the Event Log................................. 1-5 Network Settings ................................................ 2-2 Node Name ........................................................ GL-6 10400166-102 09/2008 Notification Tips for Configuration changes ................. 2-3 O ODA .................................................................... GL-7 ODA Assignment ................................................. 8-2 ODA Storage Capacity........................................ 8-4 ODA Stripe Size ................................................... 8-3 Operations Access Statistics............................................ 6-3 Environment.................................................. 5-3 Optimizing Write Performance ....................... A-1 Overview ................................................................ 1-1 SAN LUN Mapping Screen ........................ 4-2 Overwrite Data Area ...................................... GL-7 Overwrite Data Area, ODA ............................... 8-2 P Pause Initialization............................................. 3-8 Performance and Additional Functions.......... 6-1 Performance Optimization ................................ 6-1 Performance, Optimizing.................................. A-1 Performing a Snapback .................................... 8-13 Port Connection Advanced Setting........................................ 5-12 Port Name ......................................................... GL-7 R RAID 5 Sub-Array .............................................. A-3 RAID 5/50 Full Stripe Write Rate ................... 6-7 RAID Controller Status...................................... 5-2 RAID Controller Systems ................................ 5-11 RAID Level 0 .................................................... GL-7 RAID Level 1 .................................................... GL-7 RAID Level 10 .................................................. GL-8 RAID Level 5 .................................................... GL-8 RAID Level 50 .................................................. GL-8 RAID Level 6 .................................................... GL-8 RAID Levels table................................................ 3-1 Read-Ahead Cache .............................................. 3-5 Read-Ahead Command Efficiency ................... 6-6 Read-Ahead Command Hit Rate...................... 6-6 Read-Ahead Statistics ........................................ 6-5 Reads Statistics.................................................... 6-3 Rebuild Array ....................................................... 7-6 Rebuild Priority.................................................. 5-10 Rebuilding an Array............................................ 7-6 Remove an Individually Monitored Server.. 2-10 Removing a Spare.............................................. 3-13 ©2007,2008 Overland Storage, Inc. W IX-3 ULTAMUS RAID 1200 User Guide Index Rescan.................................................................... 6-9 Reserved Capacity ................................. 7-11, GL-2 Reserved capacity ............................................... 3-4 Restoring the Configuration........................... 7-12 Resume Initialization......................................... 3-8 Rewrite Parity ..................................................... 7-5 S SAN LUN Mapping ............................................ 4-1 Creating ......................................................... 4-4 Overview ........................................................ 4-2 Remove ........................................................... 4-5 Scatter/Gather ..................................................... 6-2 Sequential Access ............................................... A-2 Sequential Command Interval......................... 6-6 Server Event All event logs cleared ................................ C-19 Multicast address is not configured ...... C-20 Multicast socket creation failure............ C-20 Serial and key are incorrect .................... C-19 Server has been shutdown....................... C-19 Server has been started ........................... C-19 User has logged in ..................................... C-19 User has logged out ................................... C-19 Server Events .................................................... C-19 Server icon is white ............................................ 1-6 SES Event Alarm Disable............................................... C-8 Alarm Enable................................................ C-8 Alarm is ON ....................................... C-8, C-17 Alarm Mute ................................................... C-8 Encl Alarm is OFF.................. C-8, C-17, C-18 Encl Temp 27C OK.................................... C-17 Encl Temp 50C Warning.......................... C-17 Encl Temp 70C Critical ............................ C-17 Fan Critical ................................................. C-16 Fan OK......................................................... C-16 Power Supply Critical............................... C-16 Power Supply Not found .......................... C-16 Power Supply OK....................................... C-15 SES Events......................................................... C-15 Single Controller Mode...................................... 5-9 SMTP mail server ............................................... 2-4 Snapback.................................................. 8-14, GL-9 Snapshot .................................................... 8-1, GL-9 Delete............................................................ 8-11 Mapping ....................................................... 8-10 Snapshot LUN ................................................ GL-10 SNMP Traps......................................................... 2-5 Software Version................................................. 6-8 Spare Drives....................................................... 3-10 Starting ULTAMUS RAID manager .............. 2-1 10400166-102 09/2008 Static IP ................................................................. 2-3 Statistics Alignment....................................................... 6-4 Command Size .............................................. 6-4 Status Environmental .............................................. 5-2 Storage Area Stripe Size ................................ GL-7 Storage Assistant................................................. 3-1 Stripe ................................................................ GL-10 Support and Updates.......................................... 9-1 SYSLOG Agent..................................................... 2-6 SYSLOG Daemon ................................................ 2-7 T Take Control Monitoring ................................... 6-8 Tech Support......................................................... 9-1 Terminology SAN LUN Mapping...................................... 4-1 Tool Bar Advanced Settings........................................ 1-8 Archive Configuration ................................. 1-8 Create Array.................................................. 1-8 Create Logical ............................................... 1-8 Logical Stats .................................................. 1-8 SAN Mapping ................................................ 1-8 Toolbar ................................................................... 1-7 Troubleshooting .................................................. B-1 Trust Array ......................................................... 7-10 Typographic Conventions .............................. PR-v U ULTAMUS Server Events .............................. C-19 Update Controller Firmware ............................ 5-4 Updates .................................................................. 9-1 Updating Embedded ULTAMUS RAID manager 9-3 Using Snapshot .................................................... 8-1 V Verify Parity ......................................................... 7-4 Virtual LUN Numbering.................................... 8-4 W Write Cluster Rate .............................................. 6-7 Write Performance ............................................. A-1 Write-back Cache................................ 3-5, 3-6, 7-11 Write-back Cache Disabled Battery Not Charging............................... C-12 Writes Statistics................................................... 6-3 ©2007,2008 Overland Storage, Inc. W IX-4