USER’S GUIDE Global Array Manager Transition Tool Client Software May 2003 First Edition ® DB15-000278-00
This document contains proprietary information of LSI Logic Corporation. The information contained herein is not to be used by or disclosed to third parties without the express written permission of an officer of LSI Logic Corporation. Document DB15-000278-00, First Edition (May 2003) This document describes version 5.20 of LSI Logic Corporation’s Global Array Management Client software.
This warranty will not apply to, and LSI provides no warranty for any BIOS, software, ROM-based firmware or other product developed or manufactured by any third party whether including with this Product or not. Such warranty or warranties are provided by third parties and, to the extent permitted thereby, shall be made available and are hereby assigned by LSI to Customer.
Software License Subject to the terms and conditions of this Agreement, LSI grants Customer a non-exclusive, worldwide, non-transferable, revocable, royalty-free license to use, perform and display the LSI software that is a part of the Product (“LSI Software”) solely as part of the Product incorporated into the OEM Products that and not on a standalone basis.
Preface This User’s Guide covers the steps involved to install and use the client component of Mylex’s Global Array Manager® Transition Tool with MegaRAID Ultra 320 and Mylex PCI Disk Array Controllers. For information on installing and running the server component of Global Array Manager Transition Tool, consult the Global Array Manager Transition Tool Server Software Installation Guide and User Manual DB15-000279-00.
• Chapter 3, Startup and Navigation, describes how to start and navigate through the GAM TT Client. • Chapter 4, Configuration, describes how to use the RAIDAssist configuration wizard to configure or re-configure your disk array system. • Chapter 5, Monitoring, explains the monitoring functions available to gather information about the status of your disk array system. • Chapter 6, Maintenance Processes, describes maintenance functions available for individual disk arrays and drives.
Contents Chapter 1 Introduction 1.1 1.2 Overview 1.1.1 Global Array Manager Transition Tool Components 1.1.2 Configuration Functions 1.1.3 Monitoring Functions 1.1.4 Maintenance Functions Requirements 1.2.1 Client Hardware and Software 1-1 1-1 1-2 1-2 1-2 1-2 1-3 Chapter 2 Installation 2.1 2.2 2.3 Installation Overview 2-1 Installation of the Global Array Manager Transition Tool Client 2-1 2.2.
3.3 3.4 3.5 3.6 3.7 3.8 3.2.2 Components of the GAM TT Client Opening Screen 3-3 3.2.3 Components of the Controller View Window 3-6 Status Icons 3-8 3.3.1 Menu Bar and Menus 3-9 3.3.2 Toolbar and Toolbar Icons 3-14 Exiting Global Array Manager Transition Tool 3-15 3.4.1 Exiting GAM TT Server 3-16 Setting Up Server Groups and Servers 3-17 3.5.1 Adding a Server Group to the Server Group List 3-17 3.5.2 Adding a Server to the Server Groups List 3-18 Signing On to a Server 3-19 3.6.
4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.8.2 Expanding an Array on MegaRAID Controllers Deleting a Logical Drive Migrating a RAID Level Transporting a Disk Array (Mylex Controllers Only) Clustering (Mylex Controllers Only) Managing Channels Spanning in Global Array Manager Transition Tool Enable Spanning in GAM TT Configuring a Spanned Disk Array 4.16.
5.7.1 5.7.2 5.7.3 Chapter 6 Maintenance Processes 6.1 6.2 6.3 6.4 6.5 6.6 6.7 Power Levels Battery Status Actions (Mylex Controllers Only) Introduction Running a Logical Drive Initialization Running a Logical Drive Consistency Check Running a Device Rebuild Using the Flash Utility Defragmenting an Array (Mylex Controllers Only) Clearing a Configuration 5-28 5-28 5-29 6-1 6-1 6-3 6-4 6-5 6-9 6-10 Appendix A Event Information A.1 Overview A-1 Glossary Index Customer Feedback x Contents Version 1.
Chapter 1 Introduction 1.1 Overview Global Array Manager® Transition Tool (GAM TT) Client software manages selected MegaRAID Ultra320 and the AcceleRAID and eXtremeRAID families of PCI RAID controllers. This manual provides information on GAM TT Client that supports new server features for the following controllers: • MegaRAID Ultra320 -1, -2, 2x, 4x • eXtremeRAID 2000/3000 • AcceleRAID 160/170/170LP/352 GAM TT Client software is used to: 1.1.1 • Monitor and manage server and disk array groups.
1.1.2 Configuration Functions Configuration functions are easily performed using RAID AssistTM, an intuitive, wizard-like utility in the GAM TT Client component that simplifies the process of setting up or reconfiguring a disk array. Just answer a few brief questions, and RAID Assist automatically does the rest. Use Manual Configuration for more control over drive group setup or individual configuration parameters. 1.1.
1.2.1 1.2.1.
1-4 Introduction Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Chapter 2 Installation 2.1 Installation Overview Installation of the Global Array Manager Transition Tool Client component requires one of the following operating systems: • Windows 2000/2003/XP 32-bit/98/95/Me • Linux (using Wine) This chapter assumes that the network administrator for this site will be performing these installation procedures. If you are installing GAM TT Client, you may also choose to install GAM TT Server and its subcomponents at the same time on the same system.
1. Double-click Setup.exe. 2. After a few moments, the Welcome dialog box will display (Figure 2.1). Click Next to proceed with the installation, or click Cancel to end the installation procedure and return to the menu. Figure 2.1 Welcome Dialog Box 3. When the LSI Logic Software License Agreement screen displays, click Yes to accept the terms of the agreement and continue. If you click No, you will not be allowed to continue GAM TT Client installation.
Figure 2.2 Select Components to Install 4. To select Global Array Manager Transition Tool Client for installation, click the box (if necessary) to check the Global Array Manager Transition Tool Client option. Note: If installing the Global Array Manager Transition Tool Client, you may also choose to install Global Array Manager Transition Tool Server at this time.
2.3.1 Install Wine Go to the following web site to download Wine: http://www.rpmfind.net It is highly recommended that you use the following Windows 16/32-bit emulator rpm file: wine-20010131-3.i386.rpm Refer to the following web sites for further information on Wine. http://www.winehq.com http://www.codeweavers.com 2.3.2 Install GAM TT Client Global Array Manager Transition Tool software Global Array Manager Transition Tool software can be downloaded from http://www.lsilogic.com/GAMTT.
Chapter 3 Startup and Navigation 3.1 Starting Global Array Manager Transition Tool Starting the Global Array Manager Transition Tool Client requires both the Server and Client components. It is required that you install and start GAM TT Server before you attempt to run the Global Array Manager Client. 3.1.1 Server Component Installation and startup of the Global Array Manager Server component is covered in the Global Array Manager Server Software Installation Guide and User Manual.
At startup, the GAM TT Client will display the following message dialog box (Figure 3.1). Figure 3.1 GAM TT Client Opening Message This dialog box is to notify you that the event definition has been changed from default after clicking OK from the Settings option. If you do not want this dialog box to open each time you start the GAM TT Client, select the “Don’t display this dialog again” check box. Click OK to close the dialog box.
Click this button to confirm the action identified in the dialog box. Click this button to cancel the action identified in the dialog box. Click this button to close the active dialog box. Click this button to apply your configuration changes. 3.2.
3.2.2.1 Components of the GAM TT Client Windows The major components of the GAM TT Client windows (Figure 3.2) are described below. 1. Item #1 is the menu bar. There are five menus with several selections each. The contents of the menus and the functionality of several of the most important selections will be described throughout this guide. 2. Item #2 is the toolbar. There are seven toolbar icons representing eight of the most useful functions available in GAM TT Client.
– the number of DAC (PCI/SCSI) controllers connected on the server, with a controller operational status light (green = functioning, yellow = critical, red ‘X’ = down or nonfunctional) 6. Item #6 is an icon that represents a currently unselected file server running the GAM TT Server component. The icon identifies the same information described above. 3.2.2.3 Components of the Log Information Viewer 7. Item #7 in Figure 3.2 is the GAM TT Client Log Information Viewer.
3.2.3 Components of the Controller View Window Open the Controller View window by double-clicking any server icon in the Global Status View, or as shown in Figure 3.3: Figure 3.3 Select “Controller View” The Controller View window (Figure 3.
• Item #4: The enclosure device present on each channel, specifying the device inquiry data (vendor, bus width, etc...), and the device state. • Item #5: The host device present on each channel, specifying the device inquiry data (vendor, bus width, etc...), and the device state. Figure 3.4 Controller View Window – “Non-Fibre” RAID Controller #1 #4 3.2.3.1 #2 #3 #5 eXtremeRAID 3000 The Controller View window for the eXtremeRAID 3000 (Figure 3.
Figure 3.5 3.
3.3.1 Menu Bar and Menus GAM TT Client contains a menu bar (Figure 3.6) in the Global Array Manager Transition Tool window. Figure 3.6 3.3.1.1 Menu Bar File Menu The File menu (Figure 3.7) contains the following options: • Open Configuration (Ctrl+O): Loads a configuration from disk and saves it to the controller. (See Section 3.5, “Setting Up Server Groups and Servers,” page 3-17.) • Save Configuration (Ctrl+S): Saves a configuration file to a new filename, disk, and/or directory.
3.3.1.2 View Menu The View menu (Figure 3.8) contains the following options: • Global Status View: Toggles the Global Status View window. The Global Status View window opens by default when Global Array Manager Transition Tool Client starts. • Controller View: Toggles the Controller View window showing channel/ID/target information and physical device/logical drive configurations for the controller selected in the controller selection box.
3.3.1.3 • Consistency Check Status: Displays the progress (percent complete) of an ongoing logical drive consistency check. • Expand Capacity Status: Displays the progress (percent complete) of an ongoing data restriping process across the target RAID group. • Patrol Read Status: Enables GAM TT Client to poll every 1 minute to get new status data from the controller.
Figure 3.9 • Initialize Logical Drives: Offers the ability to run a full initialization of logical drives at a time of your choice, not just immediately following a new configuration. If it’s inconvenient to follow a configuration immediately with a logical drive initialization, you can decline the initialization and use this menu item to start the process at a later time.
– Monitor the power remaining in the Intelligent BBU (Mylex Controllers Only). – Set the low power threshold (Mylex Controllers Only). The Intelligent BBU features and functionality are described in detail elsewhere. GAM TT simply offers a way of keeping up-to-date as to the condition and charge in the battery. • Scan Devices: Scans for new devices that have recently been added and which are not currently identified within GAM TT Client.
Figure 3.10 Window Menu 3.3.1.5 Help Menu The Help menu (Figure 3.11) identifies the on-line help options available within the Global Array Manager Transition Tool Client. • Contents (F1): Displays a list of available help topics. • About Global Array Manager: Displays the Windows standard “About” box. Figure 3.11 Help Menu 3.3.2 Toolbar and Toolbar Icons GAM TT Client contains a toolbar (Figure 3.12) in the Global Array Manager Transition Tool window. Figure 3.
Each toolbar button corresponds to a function available from the menu bar. Disk Configuration Wizard: Brings up the RAID Assist dialog box for RAID controller configuration. Scan Devices: Scans for new, recently added devices which are not yet identified within GAM TT. Displays Controller Information: Displays key information about the currently-selected RAID Controller or HBA. Error Table: Displays a table of “request sense” data.
unless you restart GAM TT Client and reconnect to the server(s). 3.4.1 Exiting GAM TT Server Refer to the Global Array Manager Transition Tool Server Software Installation Guide and User Manual for details on how to exit GAM TT Server. 3-16 Startup and Navigation Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
3.5 3.5.1 Setting Up Server Groups and Servers Adding a Server Group to the Server Group List Open Define Server Groups as shown in Figure 3.14. (This is not necessary if you are starting GAM TT and no Server Groups are defined. The Define Server Groups dialog box will display automatically.) Figure 3.14 Select “Define Server Groups” In the Define Server Groups dialog box (Figure 3.15), do the following: 1. Click the Add button under the Server Groups section of the dialog box. Figure 3.
2. In the Adding Item dialog box, type the name of the server group that you are adding. 3. Click OK. The Define Server Groups dialog box will reappear with the newly-defined server group added. Note: 3.5.2 The Discovered group contains a list of all server hosts that are sending events to the client. Adding a Server to the Server Groups List With the Define Server Groups dialog box open (Figure 3.15), do the following: 1. Click the Add button under the Servers section of the dialog box. 2.
3.6 Signing On to a Server This section describes the different server access levels and the methods of signing onto the Global Array Manager Transition Tool Client. 3.6.1 Security Access Levels The ability to perform certain actions within the GAM TT Client depends on your security access level. There are three levels of security access, Guest (no sign-on), User, and Administrator. Note: 3.6.1.
3.6.1.3 Administrator Administrator access level is achieved by signing on to a server host using the username “gamroot”; use of a password is highly recommended. Administrators have the capabilities of Guests and Users plus the full privilege to view and change the status and settings of the selected controller and other internal GAM TT settings. 3.6.2 Signing On To gain access to capabilities beyond Guest access level, you must sign on to a server host.
Figure 3.17 Select “Sign On” GAM’s internal operation during Sign On is to: 1. Encrypt the username and password and send them to the GAM TT Server running on the selected server host. 2. The GAM TT Server receives and decrypts the username and password and makes an operating system specific call to validate them per the server host’s operating system’s user accounts. 3. After the username and password are validated by the operating system the username is compared to the string “gamroot”.
Uncheck the box if you want to retain the option of signing on to each server you wish to access individually. 3. Click the Sign-On button (see Figure 3.16). 3.7 Setting and Modifying User Preferences Open Settings by clicking Administration->Settings on the menu bar or the Preferences icon as shown in Figure 3.18. Figure 3.18 Select “Settings” 3-22 Startup and Navigation Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
3.7.1 Alert Preferences Figure 3.19 Settings Dialog Box – Alert Preferences In the Settings dialog box, under the Alert Preferences tab (Figure 3.19), you have several options: 3.7.1.1 3.7.1.
Events are numbered from 0 for most severe to 4 for least severe, and can be edited by the user. Finish by doing one of the following: 3.7.2 • Click OK to accept the global alert settings and exit the Settings dialog box, or • Click Cancel to leave original settings unchanged, or • Click another Settings tab to set additional user preferences. Alarm Setup The top half of the Alarm Setup dialog box lists the types of alarms that can be used (Pager, Fax, E-mail, Launch Application).
3.7.2.1 Add a Pager 1. Select the Pager alarm type in the upper window. 2. Click Add. The Pager setup box is displayed as shown in Figure 3.21. Figure 3.21 Pager Setup Dialog Box 3. In the Pager box: – Enable or disable this Pager entry using the Enabled check box. – Type the Modem Setup String, or keep the default. – Type a Pager Prefix, or keep the default. – Type the phone number of someone who will receive a page. – Type a Pager Suffix if needed. – Type a Pager Delay interval.
4. If you need to enter a Message Prefix, Suffix, or Delay interval, click Advanced. Type the desired information and click OK to return to the Pager setup box. 5. To test the pager using the settings you’ve input, click Test. 6. When you are satisfied with the Pager you’ve set up, click OK. Your new Pager entry displays in the lower window of the Alarm Setup dialog box. (Refer to Figure 3.20 for an example.) 3.7.2.2 Remove a Pager 1. Select the Pager alarm type in the upper window of Alarm Setup. 2.
Figure 3.23 Fax Alarm Setup 2. Click Add. The Fax setup box is displayed as shown in Figure 3.24. Figure 3.24 Fax Setup Dialog Box 3. In the Fax box: – Enable or disable this Fax entry using the Enabled check box. – Type the fax phone number of someone who will receive a fax. – Type a fax header, if desired. 4. To test the fax using the settings you have input, click Test. 5. When you are satisfied with the Fax you have set up, click OK.
3.7.2.4 Remove a Fax 1. Select the Fax alarm type in the upper window of Alarm Setup. 2. Select the Fax entry to remove in the lower window of Alarm Setup. 3. Click Remove. 4. At the confirmation message, click Yes to remove the Fax entry, or click No to keep the entry. 3.7.2.5 Add a Fax Using Linux When using Linux, the behavior of the Fax Alert function is defined in gam2cl.ini file as follows, which is located under “~User/.gam/”.
Figure 3.25 Email Alarm Setup 2. Click Add. The E-mail setup box is displayed as shown in Figure 3.26. Figure 3.26 Email Setup Dialog Box 3. In the Email box: – Enable or disable this Email entry using the Enabled check box. – Type the email address of someone who will receive an email. – Type the subject of the email. 4. To test the email using the settings you’ve input, click Test. 5. When you are satisfied with the Email you’ve set up, click OK.
3.7.2.7 Remove Email 1. Select the Email alarm type in the upper window of Alarm Setup. 2. Select the Email entry to remove in the lower window of Alarm Setup. 3. Click Remove. 4. At the confirmation message, click Yes to remove the Email entry, or click No to keep the entry. 3.7.2.8 Add an Email Using Linux When using Linux, the behavior of the E-mail Alert function is defined in gam2cl.ini file as follows, which is located under “~User/.gam/”. [COMM_SECTION] ...
Figure 3.27 Launch Application Alarm Setup 2. Click Add. The Launch Application setup box is displayed as shown in Figure 3.28. Figure 3.28 Launch Application Setup Dialog Box 3. In the Launch Application box: – Enable or disable this Application entry using the Enabled check box. – Enable Launch Only Once if you want to prevent the application from launching again if GAM TT detects that it is already running. – Type the name of an application to launch should certain events or messages require it.
– If you don’t remember the name or path of the application, click the Browse button. 4. To test the application launch using the settings you’ve input, click Test. 5. When you are satisfied with the application you’ve set up, click OK. Your new application entry displays in the lower window of the Alarm Setup dialog box (refer back to Figure 3.27 for an example.) 3.7.2.10 Remove an Application to Launch 1. Select the Launch Application alarm type in the upper window of Alarm Setup. 2.
Figure 3.29 Settings Dialog Box – Communication 3.7.3.1 Baud Rate Select the baud rate appropriate to your communication hardware. 3.7.3.2 Port Select the COM port at which your communication hardware resides. 3.7.3.3 Parity Select the type of parity for communication sessions: None, Even, Odd, Mark, Space. 3.7.3.4 Stop Bits Select the number of stop bits required for communication sessions: 1, 1.5, 2. 3.7.3.
Finish by doing one of the following: 3.7.4 • Click OK to accept the communication settings and exit the Settings dialog box, or • Click Cancel to leave original settings unchanged, or • Click another Settings tab to set additional user preferences. Event Editor Figure 3.30 Settings Dialog Box – Event Editor In the Settings dialog box, under the Event Editor tab (Figure 3.30), you have several options. 3.7.4.1 Event ID/User Event ID/Severity/Default 1.
3.7.4.2 Alarm for the Event When all Global boxes are checked, you can view the alarms that will activate when this particular event occurs (these are based on the settings in Alert Preferences). Check or uncheck specific boxes if you wish to override these defaults and change the alarms for this event. 3.7.4.3 Event Message Text Type new text for this event, or keep the default text (set by LSI Logic). After modifying the event definitions, a data file called “gam2cl.
3.8 For More Information... This concludes the Startup & Navigation chapter. For additional information on Global Array Manager Transition Tool options and functionality, refer to other chapters in this installation guide, and to the context-sensitive online help file available from the Help menu, by pressing F1, or by right-mouse-clicking an item on which you require help. 3-36 Startup and Navigation Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Chapter 4 Configuration 4.1 Introduction Configuration activities involve the following: 4.
Once the user with the lock has completed the critical activity, the controller system will be automatically unlocked. 4.3 Setting and Modifying Controller Options Open Controller Options as shown in Figure 4.2. Figure 4.2 Select “Controller Options” To configure options for a controller, complete the following property pages. 4.3.1 Controller Options To configure Controller Options, follow these steps: 1. Select the Controller Options tab (Figure 4.3). 4-2 Configuration Version 1.
Figure 4.3 Controller Options Dialog Box for new PCI DAC 2. Enable or disable (by checking or unchecking) any of the following global parameters: – Automatic Rebuild Management. Works in conjunction with SAF-TE disk array enclosures to detect removal of a failed drive and perform an automatic rebuild after installation of a replacement drive. Change the default Rate Controls to less than or equal to 50. Do this by using the slide bar or typing the rate in the edit box.
– – Consistency Check Rate. – – – MegaRAID Controllers: Enable Background initialization and initialization rate are not available. MegaRAID controllers perform background initialization on the first write or after 5 minutes. Change the default Rate Controls to less than or equal to 50. Do this by using the slide bar or typing the rate in the edit box. A rate of 50 dedicates the maximum allowable resources to a Consistency Check allowing it to proceed at its fastest.
– Devices Between Spins. Number of devices to spin up at one time. A low number lessens the likelihood of a power drain. – Initial Delay. Number of seconds between physical device startups. – Delay Between Spins. Number of seconds between consecutive device spin-up cycles. Clustering. Under Windows 2000/2003/XP 32-bit/95/98/Me with clustering support, allows redundancy among controllers in various servers.
Figure 4.4 Advanced Controller Options Dialog Box Enable or disable (by checking or unchecking) the following parameters: – Temporarily Offline RAID Array. Prevents a second physical drive associated with a currently critical system drive from being permanently marked offline. The disk drive is marked temporarily unavailable or dead. – Device Health Monitoring (S.M.A.R.T). S.M.A.R.T.
You can set the Patrol Read Iterations from four hours to 1016 hours in multiples of four hours. – Fibre Channel Speed (Mylex eXtremeRAID 3000 Controllers Only): Manages three speeds of the fibre channel. – Auto - Sets an Auto Negotiate speed for the host port(s) selected. – 1Gb - Sets a 1 Gigabits/second speed for the host port(s) selected. – 1Gb - Sets a 2 Gigabits/second speed for the host port(s) selected. Click the OK button to accept the changes, or the Cancel button to discard them. 4.
Figure 4.
4.5 Running RAID Assist RAID Assist is the Global Array Manager Transition Tool Client’s “wizard” for the setup and configuration of new logical drives and disk arrays. In its simplest form, RAID Assist provides an Auto Configuration option which immediately configures all available drives into an optimal configuration. RAID Assist’s Assisted Configuration sets up a new array according to predefined parameters, and asks the user questions to gather the key information necessary to build the array.
Figure 4.8 RAID Assist “Welcome” Dialog Box In the RAID Assist “Welcome” dialog box (Figure 4.8), do one of the following: 4.5.
• Expand Array. Restripes data in your array across additional, unconfigured drives to expand the capacity of the array. For example, open New Configuration as shown in Figure 4.9. Figure 4.9 Select “New Configuration” The new configuration created is based on the total number of drives discovered by the Global Array Manager Transition Tool.
Figure 4.10 Automatic Configuration->New Configuration->Finish Do the following: 1. Examine the Configuration Summary for details about the configuration that RAID Assist will set up. 2. If you want to start over, click the Back or Cancel button, or the Welcome tab, OR If you want to view the configuration before it is applied to the controller, click the Details button.
Figure 4.11 WARNING Before Applying the Configuration 4. Type YES and click OK if you are sure you want to apply the new configuration and overwrite the old. If you’re not sure, click Cancel. 4.5.3 Assisted Configuration Assisted Configuration provides three options: • New Configuration. Sets up a new configuration on the controller, deleting the previous configuration and data (if any). • Add Logical Drive. Sets up additional arrays (logical drives) leaving the existing array(s) intact.
Figure 4.12 Select “New Configuration” Assisted Configuration walks you step by step through a new configuration (Figure 4.13). Each “tab” in the Assisted Configuration dialog box collects information about an important aspect of the configuration you wish to set up. During this process, you provide answers to several questions. 4.5.3.1 Fault Tolerance Tab Configure the following options (Figure 4.13) for fault tolerance. 1. Do you want Fault Tolerance? [Yes/No] 2.
Figure 4.13 Assisted Configuration – Fault Tolerance RAID Level Tab If Fault Tolerance Was Yes (Figure 4.14), choose between: – Parity error correction (RAID 5, RAID 3), or – Fully redundant drives (RAID 1, RAID 0+1) Running RAID Assist Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Figure 4.14 Assisted Configuration – RAID Level With Fault Tolerance RAID Level Tab If Fault Tolerance Was No (Figure 4.15), choose between: Mylex RAID Levels: – Striping (RAID 0), or – Stand-alone drive (JBOD) MegaRAID RAID Levels: – 4-16 Striping (RAID 0) Configuration Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Figure 4.15 Assisted Configuration – RAID Level With No Fault Tolerance 4.5.3.2 Logical Drives Tab Configure the following options (Figure 4.16) for a logical drive. 1. How many logical drives do you want to create? – Mylex 1–32 supported – MegaRAID 1–40 supported 2. How much capacity do you want to use? [default=100% available space, or equivalent in Mbytes] 3. Do you want to initialize logical drives? [Yes/No] This is done after the configuration has been applied. Running RAID Assist Version 1.
Figure 4.16 Assisted Configuration –Logical Drives Certain Mylex PCI RAID Controllers allow Immediate RAID Availability of logical drives after configuration. For these controllers, initialization can take place in the background without the need to wait for full foreground initialization. If you selected Yes to the question above and the controller supports background initialization, the following screen will display (Figure 4.17): Figure 4.17 Background Initialization is Supported 4.
4.5.3.3 Optimization Tab Configure the following options (Figure 4.18) for optimization. 1. Choose between: – Write cache enabled (write back) – Write cache disabled (write through) 2. Select a Stripe Size from the valid drop-down list. 3. Select Cache line size (Mylex Controllers Only). Valid cache line size values depend on the stripe size settings.
4.5.3.4 Finish Tab When you get to the Finish screen (Figure 4.19), do the following: Figure 4.19 Assisted Configuration ->New Configuration ->Finish 1. Examine the Configuration Summary for details about the configuration that RAID Assist will set up. 2.
Figure 4.20 WARNING Before Applying the Configuration 4. Type YES and click OK if you are sure you want to apply the new configuration and overwrite the old. If you are not sure, click Cancel. Note: 4.5.4 In Assisted Configuration, Add Logical Drive and Expand Array function very similarly to the New Configuration option. In each case RAID Assist leads you step-by-step through the relevant questions for the task. Manual Configuration Manual Configuration provides four options: • Edit Configuration.
For example, open New Configuration as shown in Figure 4.21. Figure 4.21 Select “New Configuration” The Disk Arrays tab in Manual Configuration is where you begin to configure your unused disk drives (lower left, Figure 4.22). Figure 4.22 Manual Configuration – Disk Arrays 4-22 Configuration Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Each disk array is represented by two lines in the Disk Arrays area of the screen (upper left, Figure 4.22). Logical drives (if any have already been configured) display on the right side. Do the following: 1. Select an unused drive and drag it to the Disk Array A0 section. The drive will be part of a disk array referred to as “A0.” 2. Select other unused drives and drag them to Disk Array A0, or click the Add Array button to create a row for Disk Array A1 (then A2, A3, etc.
Do the following: 1. If you want to randomly create a logical drive, select the desired disk array from the Disk Array drop down menu (Mylex Controllers Only). 2. Select a RAID level for your first logical drive. Only RAID levels compatible with the current configuration will be available in the list. – Mylex supported RAID levels are RAID 0, RAID 1, RAID 3, RAID 5, RAID 0+1, and stand-alone drive (JBOD). – MegaRAID supported RAID levels are RAID 0, RAID 1, RAID 5. 3.
Figure 4.24 Stripe Size Selection Warning If you select Yes, the new configuration will be applied and an 8 KB cache line size will be active. If you select No, the Logical Drives page of the Manual Configuration Wizard will open. You can change the stripe size in order to obtain the desired cache line size. 7. Select a cache line size (Mylex Controllers Only), if enabled. Available settings will depend on the selected stripe size. 8. Click the Add Drive button to register your new logical drive. 9.
Note: 4.6 In Manual Configuration, Add Logical Drive and Expand Array function very similarly to what was shown above. In each of these two cases, however, RAID Assist shows you the disk arrays and logical drives and allows you to add to the configuration without risking existing data.
4. Click Add Drive to add a logical drive(s). If there are a few available segmented spaces, the largest space is used for the creation of a new logical drive. Figure 4.27 Add Logical Drive(s) 5. Select a RAID level for your new logical drive. 6. Type the desired amount of available logical or physical capacity for this logical drive. 7. Check the Write Cache box if you want this logical drive to use Write Back caching. This improves performance but puts data at risk.
Figure 4.28 WARNING Before Applying the Configuration 12. Type YES and click OK if you are sure you want to apply the new configuration and overwrite the old. 4.7 Global Hot Spares vs. Dedicated Hot Spares A hot spare is classified as two types: 1) a Dedicated Hot Spare and 2) a Global Hot Spare. Dedicated Hot Spares belong to a single disk array or spanned disk array.
Figure 4.29 Creating a Global Hot Spare 8. If you want the Global Hot Spare to be a Dedicated Hot Spare drag and drop it to the disk array that the Global Hot Spare belongs (see Figure 4.30). Figure 4.30 Creating a Dedicated Hot Spare A Dedicated Hot Spare is created, and a green plus sign indicates the physical disk drive has changed to a Dedicated Hot Spare (see Figure 4.30). Global Hot Spares vs. Dedicated Hot Spares Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
4.8 Expanding Capacity GAM TT provides an advanced configuration mode known as MORE2 (Mylex Online RAID Expansion 2) which provides two features, Online Capacity Expansion and Extension (OCE), and RAID Level Migration (RLM). These features allow you to increase the capacity of a RAID array in a variety of ways. All of the following operations are available while the controller is online. The operations are performed in the background while normal data operations occur.
Caution:It is highly recommended that you backup your data and current configuration before making modifications. To perform an Array Expansion, follow these steps: 1. Select Administration->RAID Assist on the menu bar or the RAID Assist icon (see Figure 4.7). 2. Click the Manual Configuration button. 3. Click Expand Array. The Manual Configuration Disk Array tab (see Figure 4.31) will open. This is where you can add available disk drive capacity. 4.
Figure 4.32 Logical Drives Tab 6. From the Physical Capacity drop-down list, check the maximum amount of capacity. 7. Add the maximum capacity to the logical drive or a portion of it. – To add a portion of the capacity: type the desired capacity amount in the Logical Drive Capacity field. – To add the entire amount of capacity: select the amount from the Physical capacity drop-down list. 8. Change the RAID level or leave it as is. 9. Click the Apply button to save your new configuration.
Figure 4.34 WARNING Before Applying the Configuration 10. Type YES and click OK if you are sure you want to apply the new configuration and overwrite the old. WARNING: Expand Capacity cannot be cancelled. The Expand Capacity Status box (Figure 4.41) opens and displays the progress of a disk array capacity expansion. Figure 4.35 Expand Capacity Status Box 11. Click Close to close the Expand Capacity Status box at any time. Click View-> Expand Capacity Status to open the status box at any time. 4.8.
1. Select Administration->RAID Assist on the menu bar or the RAID Assist icon (see Figure 4.7). 2. Click the Manual Configuration button. 3. Click Expand Array, the Reconstruct a Logical Drive dialog box (see Figure 4.36) opens. Select the logical drive that you want to expand and click OK. The Disk Array tab opens (see Figure 4.37). Figure 4.36 Select a Logical Drive 4. Select the physical drive(s) that you want to add to the array and drag and drop them to the desired array (see Figure 4.37). Figure 4.
Figure 4.38 Logical Drives Tab 6. Add logical drives to utilize the new capacity. 7. Click the Apply button to save your new configuration. A message box appears as shown in Figure 4.39. Click Yes to proceed: Figure 4.39 Message Before Applying the Configuration A warning confirmation box appears as shown in Figure 4.40 Expanding Capacity Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Figure 4.40 WARNING Before Applying the Configuration 8. Type YES and click OK if you are sure you want to apply the new configuration and overwrite the old. WARNING: Expand Capacity cannot be cancelled. The Expand Capacity Status box (Figure 4.41) opens and displays the progress of a disk array capacity expansion. Figure 4.41 Expand Capacity Status Box 9. Click Close to close the Expand Capacity Status box at any time. Click View-> Expand Capacity Status to open the status box at any time. 4.
Figure 4.42 Deleting a Logical Drive 5. To delete a logical drive: – For Mylex Controllers, you must first right-click the logical drive that you want to delete. This will activate the Delete Drive button. – For MegaRAID Controllers, the last logical drive created will be the first deleted and so on. 6. Click Delete Drive. The logical drive will be deleted from the configuration. 7. Repeat Step 5 and Step 6 to delete more logical drives. 8. Click the Apply button to save your new configuration. 9.
Table 4.1 and Table 4.2 describes the allowed migrations. Table 4.1 Mylex Controller RAID Level Migration Options Starting RAID Level 0 0, 3, 5, 0+1 1 3, 5, 0+1 3 3, 5, 0+1 5 3, 5, 0+1 0+1 3, 5, 0+1 JBOD Table 4.2 0, 1, 3, 5, 0+1 MegaRAID Controller RAID Level Migration Options Starting RAID Level 4-38 Destination RAID Level Destination RAID Level 0 0, 1, 5 1 0, 5 5 0, 5 Configuration Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
To migrate a RAID level, follow these steps: 1. Select Administration->RAID Assist on the menu bar or the RAID Assist icon (see Figure 4.7). 2. Click Manual Configuration/Edit Configuration. 3. Click the Logical Drives tab, this is where you can edit a RAID level. 4. Follow Step 5 through Step 12 of Section 4.8.1, “Expanding an Array on Mylex Controllers,” page 4-30 or Section 4.8.2, “Expanding an Array on MegaRAID Controllers,” page 4-33. Migrating a RAID Level Version 1.
4.11 Transporting a Disk Array (Mylex Controllers Only) You can transport a disk array group between any single controller to any dual controllers and vice versa. However, it may not be easy for you to know which disk drives in an enclosure belongs to which specific disk array. To help you, the locate function is expanded to indicate visually all disk drives (dedicated hot spares and global hot spares are not included) that belong to a specific disk array by using LEDs.
Figure 4.44 Disk Array Transport Information Window All of the physical drives including the global and dedicated spares associated with the selected logical drive and all of the logical drives that belong to the same disk array are displayed. Click the Locate Transport button to turn on LEDs on all of the physical drives including the global hot and dedicated hot spares that belong to the disk array for visual indication. You are now ready to transport your physical drives. 4.
physical disk belongs will be specifically indicated. The following colors combinations will be used per channel: • Channel 0: Orange • Channel 1: Violet • Channel 2: Cyan • Channel 3: Lavender Note: The use of color combinations is being researched. The channel colors listed are subject to change. A channel that is not shared with any other controller is called a Private channel. A channel that is shared with cluster nodes is called a Shared Channel.
Figure 4.46 Controller View – Four Channels Displayed When an attempt is made to create a disk array across channels, the caution message in Figure 4.47 opens. The message does not inhibit this operation, click the OK button to continue or click Cancel to end the operation. When GAM TT Client is running, this message will display once at the first attempt. Figure 4.
4.14 Spanning in Global Array Manager Transition Tool Spanning allows you to configure multiple drive packs or parts of multiple drive packs as one system drive. This means that space is used from the first array to the last identical array. A drive pack is a group of individual disk drives (preferably identical) that are logically tied to each other and are addressed as a single unit. In some cases this may be called a drive “pack” when referring to just the physical devices.
After physical disk drive packs are defined, one or more system drives may be created from drive packs. System drives have the following properties: • In GAM TT more than one system drive can be defined on a single drive pack; a system drive can also span 16 packs. • The minimum size of a system drive is 8 Mbytes. The maximum is 2 Terabytes. • Up to 32 system drives can be created. Each system drive has its own write policy (write-back or write-through).
3. Click the Manual Configuration button. 4. Click the Edit Configuration button. Note: Automatic and Assisted configuration options do not allow spanning. 5. To create a a Spanned Disk Array: – For a RAID 1 or RAID0 connect at least four drives of the same size to a controller. To create a RAID 3, RAID 5, or RAID 0+1, connect at least six drives of the same size to a controller. Select physical drives from the drive packs to create a spanned array.
Figure 4.49 Creating a Spanned Array You can now configure the desired number of logical drives. Select the Logical Drives tab to configure your disk arrays into logical drives. It works the same as Manual/New (see Section 4.5.4, “Manual Configuration,” page 4-21). Note that the only logical drives that will be spanned are those whose capacity is taken from more than 1 array. If the logical drive size created uses less that the capacity available on the channel, the spanning will not take place. 4.
Figure 4.51 Open Configuration Dialog Box 2. Click Open to access the configuration file. Changing the configuration is data destructive. A warning message appears (Figure 4.52): Figure 4.52 Open Configuration Warning Message 3. To confirm your decision to overwrite the existing configuration, type YES then click OK, or Click Cancel to stop without applying the saved configuration. 4.18 Saving a Configuration to Disk Saves a configuration file to a new filename, disk, and/or directory.
Figure 4.53 Select “Save Configuration” 1. In the Save Configuration dialog box (Figure 4.54), type a name for the configuration file you wish to save. Figure 4.54 Save Configuration Dialog Box 2. Click Save to save the configuration file. The configuration file (.gcf) will be saved. Saving a Configuration to Disk Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
4-50 Configuration Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Chapter 5 Monitoring 5.1 Introduction Monitoring activities involve the following: 5.2 • Monitoring events (messages) sent by various servers to the client workstation(s). • Monitoring controller activity; reviewing controller configuration and other information. • Reviewing physical device and logical drive information. • Viewing Bad Block Data (Mylex Controllers Only), Request Sense Data, and NVRAM Log Data. • Monitoring and managing SCSI and Fibre enclosure information.
such as assignment of a drive to hot spare status), the event is sent to selected workstations running GAM TT Client. Events are displayed in the Log Information Viewer. An “event” can be any of the following: • Server attach and detach (Guest, User, and Administrator) • Error or warning condition in a RAID subsystem (such as a power, fan, or drive failure) • Any administrative activity (taking a drive off-line, killing, or rebuilding a drive) Note: 5.2.
Figure 5.1 Event Information Window A variety of information about the event is displayed to aid in troubleshooting. The Event ID and Severity Level are displayed in the window’s title bar. SOURCE, DEVICE ADDRESS, and DESCRIPTION redisplay information from the original event line. The most useful fields are: – CAUSE. Possible reasons that the event occurred, and – REQUIRED ACTION. What you should do in response to this message. Informational messages will most likely have no required actions.
5.3.1 Displaying Controller Information Open Controller Information by clicking Administration->Controller Information on the menu bar or the Controller Information icon as shown in Figure 5.2: Figure 5.2 Select “Controller Information” Figure 5.3 shows the Controller Information window for a PCI RAID Controller. Figure 5.3 5-4 Controller Information Monitoring Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
The following information is displayed: • The controller model • Whether an Intelligent Battery Backup Unit is installed (N/A for not supported on the current controller) • The firmware and BIOS versions residing on the controller • The cache size and Flash ROM size • The bus type and number of channels on the controller • The number of physical devices detected, and the maximum number of physical devices that this controller can hold • The number of logical drives configured on this controlle
Figure 5.4 Host Device Information – RAID Controller Figure 5.5 Disk Device Information Device Information (Figure 5.4, Figure 5.5) displays the following about the currently-selected physical device. 5.4.1.1 5-6 Device Information: RAID Controller • The vendor or source of the controller • The controller’s product identification • The revision level of the hardware • The back-end bus width (in bits) Monitoring Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
5.4.1.
need to go to RAID Assist to configure the device disk (see Section 4.5, “Running RAID Assist,” page 4-9). If the disk drive’s status is dead, you will see a failure indicator display on the Device Information page in the Device State section. Make Online and Make Offline buttons should be used with great caution. Refer to the online help file, or call LSI Logic for support on these options. The Locate button allows you to locate this physical device visually: 1. Click the Locate button.
Figure 5.7 PFA Information Window Click the Close button to close the window. 5.4.2 Viewing the Request Sense Data and NVRAM Error Log Open the Error Table by clicking View->Error Table on the menu bar or the Error Table icon as shown in Figure 5.8. Figure 5.8 Select “Error Table” If you click the Request Sense Data tab, the following type of information displays (Figure 5.9): Physical Device and Logical Drive Monitoring Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation.
Figure 5.9 Request Sense Data This information may be useful for troubleshooting or later analysis. 1. Click Save File to record the request sense data for later use. The .rsd file can be saved to a floppy disk or your hard drive. 2. Click Read File to open and view a .rsd file that was previously saved. 3. Click Close to close the Error Table. For MegaRAID and Mylex controllers, a tab for NVRAM Error Log is also available (Figure 5.10): 5-10 Monitoring Version 1.
Figure 5.10 NVRAM Error Log Similar to the event log in the controller memory, the error event logged in the NVRAM has the following types: • Generic event: it records all activity changes, i.e. disk drive offline, logical created/deleted, etc. • Request Sense: Also referred to as 'Error Events', this records only error activity in the form of vendor unique SCSI request sense format for Mylex errors or actual SCSI request sense from physical device, i.e.
• The time information is displayed differently for MegaRAID and Mylex controllers. – MegaRAID controllers: displays date and time as m/d/h:m:ss/yyyy. – Mylex controllers: displays date and time as #h;#m:#ss since system started. The following describes the button functions for the NVRAM Error Log: 5.4.3 • To save data for failure analysis that can be used for troubleshooting, click the Save File button to record the NVRAM Error data for later use.
Figure 5.
If write back cache is disabled, click the Enable Write Cache button to enable the cache. If write back cache is enabled, click the Disable Write Cache button to disable the cache (and use write through caching). If the Consistency Check button is enabled, you may manually run a consistency check on this logical drive (as discussed in the next chapter). Click Show Bad Data Blocks to display a window of all bad data blocks found on this logical drive.
The Transport button (for Mylex Controllers Only) opens the Disk Array Transport Information window that shows all of the physical drives, including the spares associated with the selected logical drive, and all of the logical drives that belong to the same disk array. See Section 4.11, “Transporting a Disk Array (Mylex Controllers Only),” page 4-40 for details. 5.5 Enclosure Monitoring and Management The Controller View window contains an Enclosure button with a status light.
Figure 5.14 SES Enclosure Information Page 5.5.1 Information Page Enclosure Information displays the following about the currently-available enclosures: • The status of each enclosure, identified by an icon and an enclosure number (1–32)1, as well as one of the following expressed in text: – OK – All components are optimal. – Critical – Some component has failed; one more failure may result in data loss. – Failed – A failure has occurred that may result in data loss. • The enclosure type.
• The number of drive slots in the enclosure cabinet. Highlight an enclosure and the Locate button will become available (for Mylex Controllers Only). Click the Locate button to “blink” the LEDs of all of the physical drives in the enclosure to reveal its location. A locate enclosure dialog box will open, click OK or press the Enter key to end the locate operation. Click the Close button or press the Enter key to close the dialog box. 5.5.
The access status of each enclosure, which indicates the controller’s ability to communicate with the enclosure. The status values are: • OK – Access is optimal. • Critical – Only one access path remains of the several that were detected previously. If the last access path is lost, the controller will take steps to protect the data. • Lost – The enclosure is unreachable by the controller. Any failures in the enclosure while this state exists will not be sensed by the controller.
The status of the alarms in the enclosure. Each alarm is designated with a number, the status values are: • Absent – The alarm is not installed, or has failed in an undetectable way. • OK – The alarm is optimal. One additional item is displayed with this state: ON – the alarm is currently on or sounding. • Failed – The alarm is installed, but has failed. The status of the enclosure’s connection to one or more Uninterruptible Power Supplies (UPS). Each UPS is designated with a number.
enclosure to reveal its location. A locate enclosure dialog box will open, click OK or press the Enter key to end the locate operation and return to normal status. Click the Close button or press the Enter key to close the dialog box. 5.5.3 SCSI Enclosures Among the stack of drives displayed in a channel tower of the Controller View window, you will find an enclosure depicted.
5.6 Process Status Monitoring This section describes the various ways to monitor long operation tasks. 5.6.1 Background and Foreground Initialization Status While background or foreground initialization is performed, open the Background or Foreground Initialization Status box as shown in Figure 5.17 to monitor the progress of or cancel the process. Figure 5.17 Foreground Initialization Status Shown Figure 5.18 Foreground Initialization Status Box Shown The Initialize Status box (Figure 5.
To cancel individual drive initializations... Check the box(es) of the drive(s) to cancel, then click Cancel to stop only those initializations. If all drives are selected for cancellation and you wish to reverse that... 1. Click the Clear All button, which deselects all drives for cancellation. 2. Click Close to close the Initialize Status box at any time. 5.6.2 Rebuild Status If a rebuild process is currently underway, open the Rebuild Status box as shown in Figure 5.
Figure 5.20 Rebuild Status Box Mylex controllers MegaRAID controllers To stop a rebuild: – Mylex controllers: click Cancel to stop the rebuild. – MegaRAID controllers: check the box(es) of the drive(s) to cancel, then click Cancel to stop the rebuild. You may need to check the Views menu to see if Rebuild Status is still enabled. If so, you may need to cancel other rebuilds as well. Click Close to close the Rebuild Status box at any time. 5.6.
Figure 5.21 Select “Consistency Check Status” The Consistency Check Status box (Figure 5.22) displays the progress of a logical drive consistency check. Figure 5.22 Consistency Check Status Box Mylex controllers MegaRAID controllers To stop a consistency check: 5-24 – Mylex controllers: click Cancel to stop the consistency check. – MegaRAID controllers: check the box(es) of the drive(s) to cancel, then click Cancel to stop the consistency check Monitoring Version 1.
You may need to check the Views menu to see if Consistency Check Status is still enabled. If so, you may need to cancel other consistency checks as well. Click Close to close the Consistency Check Status box at any time. 5.6.4 Expand Capacity Status If an expand array (also called “MORE2”) process is currently underway, open the Expand Capacity Status box as shown in Figure 5.23 to monitor the progress of this process. This status box is also used to monitor a defragmentation. Figure 5.
5.6.5 Patrol Status To monitor the Patrol Read Status, open the Patrol Status box as shown in Figure 5.25. Figure 5.25 Select “Patrol Read Status” The Patrol Read Status dialog box displays (Figure 5.26). You can start the Patrol Read operation from the point it was stopped. If it was never enabled, the Patrol Read operation will start from the beginning. This feature will enable the GAM TT Client to poll every 1 minute to get new status data from the controller.
5.7 Battery Backup Unit Monitoring and Maintenance If your controller is equipped with an Intelligent Battery Backup Unit (BBU), you will be able to open the BBU dialog box as shown in Figure 5.27: Figure 5.27 Select “Intelligent BBU” Figure 5.28 shows the Intelligent BBU window for new Mylex PCI RAID Controllers. Figure 5.28 Intelligent BBU – New PCI Controllers The Intelligent Battery Backup Unit (BBU) dialog box is used to monitor and charge or recharge the backup battery pack on the controller.
lost to the disk storage system. When a new battery is needed, the BBU dialog indicates this by showing the battery can no longer take or hold a charge. This dialog box is also used after an old battery pack is replaced with a new one. The new battery must be fully discharged before it can be charged up. Prior to beginning normal operations, LSI Logic recommends that you condition the battery for maximum longevity. See page 5-29. 5.7.
• • Battery Type. The battery pack type. Available options: – Mylex controllers: Ni-Cad, Lithium ion, or Unknown – MegaRAID controllers: NiMH Version. Version number for the controller. Version selection numbers are from 0 to 255. The version number used for the first release is 1 for the controller production release. The following are read-only checkbox items which indicate the battery status for Mylex Controllers Only: 5.7.3 • Low Power Alarm.
5-30 Monitoring Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Chapter 6 Maintenance Processes 6.1 Introduction Maintenance processes include the following activities which you may need to perform from time to time on arrays that use redundancy and/or fault tolerance, or to maintain the most up-to-date firmware maintenance releases: 6.2 • Running a logical drive initialization. • Running a consistency check on a logical drive to examine (and optionally restore) consistency (parity). Encountered errors will be written to the Error Table.
Figure 6.1 Select “Initialize Logical Drives” An Initialize Logical Drives dialog box opens (Figure 6.2). Figure 6.2 Initialize Logical Drives Dialog Box To select logical drives to initialize, check the desired checkboxes next to the appropriate logical drive. Click The OK button or press the Enter key to begin the initialization. A Warning message dialog box will open for confirmation. Figure 6.3 6-2 Initialization Confirmation Dialog Box Maintenance Processes Version 1.
Type YES to confirm the initialization and click the OK button or press the Enter key. The Initialize Status Dialog box opens. See Section 5.6, “Process Status Monitoring,” page 5-21 for more information. 6.3 Running a Logical Drive Consistency Check From time to time run a consistency check on each of your fault tolerant logical drives. This check scans the logical drive to determine whether consistency data has become corrupted and needs to be restored.
Caution: If consistency data is badly corrupted on a logical drive, attempting to restore consistency may result in corrupted real data. Use the Yes option with caution. 2. Click No if you just want to carry out the consistency check. There is no risk of data loss. Errors will still be reported to the Error Table but no attempt will be made to correct them. 3. Consistency Check runs and the Consistency Check Status box appears (see Section 5.6.3, “Consistency Check Status,” page 5-23).
The Disk Device Information dialog box will open, and the Rebuild button should be available (Figure 6.5). Figure 6.5 Rebuild Button Available for This Disk Device 3. Click the Rebuild button in the Disk Device Information dialog box. Rebuild runs and the Rebuild Status box appears (see the previous chapter). Close the box and continue or leave the box open until Rebuild has completed. With MegaRAID controllers you can run multiple rebuilds, however only one rebuild per array can be performed.
board BIOS of the Mylex or MegaRAID Controller. As maintenance releases of this code become available, this utility allows you to keep your controller current using GAM TT. Caution: If Expand Array (Expand Capacity) is running or was stopped, you must allow the process to run to completion BEFORE replacing controllers and flashing new firmware. Otherwise, data corruption may result! Open the Flash Utility as shown in Figure 6.6: Figure 6.
purposes as well as to determine whether you need to upgrade some aspect of the firmware, BIOS, etc. To perform a flash upgrade: 1. Type the name of the appropriate firmware file (.IMG or .ROM) in the Flash file selection box, or click the Browse button to locate the file. If you select Browse, the Open Image file dialog box is displayed as shown in Figure 6.8: Figure 6.8 Note: Open Image File Dialog Box To search for files other than the .img or .rom file name, choose All Files (*.
Figure 6.9 Additional Flash File Information Mylex controllers MegaRAID controllers 4. Compare the information for the new .IMG (Mylex) or .ROM (MegaRAID) with the current information to confirm that a flash is warranted (for example, that the .IMG or .ROM contains a newer version of firmware code). 5. Click Start Flash. Because flashing new firmware code to the controller erases what was there previously, two levels of confirmation are required to proceed with the flash. 6.
The controller will be updated with the new firmware code contained in the .IMG (Mylex) or .ROM (MegaRAID) file. 6.6 Defragmenting an Array (Mylex Controllers Only) Randomly deleting a logical drive(s) will result in unused spaces in an array. Use this feature to unify space. You will need the following information before beginning a defragmentation: • The location of unused space for the creation of a new logical drive. • Capacity expansion through MORE2 with an unused physical disk(s).
The Logical Drives in the selected array pane shows the RAID level and size of the logical drives. The Array Space pane shows the following information: – unused disk space – total number of unused space (Mbytes) in the array – the largest unused space (Mbytes) in the array Click the Apply button to begin defragmenting. A warning message box opens (Figure 6.11): Figure 6.11 Defragmentation Warning Message 4. To confirm your decision to defragment, type YES then click OK, or click Cancel to stop. 5.
Figure 6.12 Mylex Only - Clear Configuration Dialog Box 1. Select the disk array(s) that you want to delete. 2. Click OK to clear the configuration. A caution message box will open (see Figure 6.13). Figure 6.13 Clear Configuration Caution Message – For MegaRAID controllers: A caution message box will open (see Figure 6.13). 2. Click the Yes button to continue. A warning message box will open (see Figure 6.14). Figure 6.14 Clear Configuration Warning Message 3.
6-12 Maintenance Processes Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Appendix A Event Information A.1 Overview Global Array Manager Transition Tool provides information about drive and controller failures, as well as maintaining an event log. Global Array Manager Transition Tool classifies the events it records into five severity levels described in Table A.1. All event information can also be found in the text file EventDef.txt in the GAM TT Files folder of the GAM TT directory. Table A.
Table A.2 GAM TT Events for PCI Controllers ID Severity Description Details 1 Actions 4 A physical disk has been placed online. Rebuild completed. Physical disk was None. configured. Manual on-line was done. 2 4 A physical disk has been added as hot spare. Device was configured. Manual hot spare was done. Automatic hot spare was done. 'Raidbld' made it hot spare. None 5 4 An automatic rebuild has started. A physical device failed and spare was available.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 14 4 A physical disk User removed an unconfigured phys- Replace the device if has been removed ical disk. An unconfigured physical needed. disk failed. A controller was removed. A controller powered off. 15 4 A previously configured physical disk is now available. User set the physical device to unconfigured. 16 4 Expand Capacity Started. User started the RAID Expansion None. operation.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 23 3 Soft error found. An error was detected by physical device and data was recovered. Run consistency check. If problem occurs frequently, replace the physical device. 24 3 Misc error found. A physical device reported some error which does not fit in any category. Read/Write command time out. Data over run. Physical device was busy when host attempted to send command.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 32 1 Initialization cancelled. User cancelled the operation. Physical disk must be initialized again or the Physical disk cannot be used. 33 1 A physical disk failed because write recovery failed. Write recovery process failed. Replace physical disk and rebuild it. 34 1 A physical disk failed because SCSI bus reset failed. SCSI bus reset failed. Replace physical disk and rebuild it.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 41 1 A physical disk The device returned busy status. The failed because of SCSI transaction with the device met busy status or par- with parity error. ity error. Replace physical disk and rebuild it. 42 1 A physical disk set to failed state by host. Command from host set the Physical disk to failed state. Replace physical disk and rebuild it. 43 1 Device disconnected or powered off.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 49 1 A Physical disk failed because write operation of 'Bad Data Table' failed. Bad Physical disk. Device write protected. Replace Physical disk and rebuild it. Check the startup option parameters on the system. 57 1 Physical disk missing on startup. Physical disk missing. Replace the Physical disk or power-on all enclosures. 58 3 Rebuild startup failed due to lower disk capacity.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 65 3 A storage access PathPilot is unable to access storage path has shifted to on the original path but is able to use the alternate path. the alternate path. A PathPilot failover has occurred. 66 0 A storage access path has shifted to the primary path. PathPilot is again able to access cer- None. This indicates tain storage on the original path. that the primary path A PathPilot failback has occurred.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 137 4 An automatic rebuild has started on logical drive. A physical disk failed and a spare device was available. A spare physical disk was found and replaced the failed device. None. 138 4 A manual rebuild has started on logical drive. Client started the rebuild on user's request. User replaced the failed device and 'Raidbld' started the rebuild. None. 139 4 Rebuild on logical drive is over.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 148 4 A logical drive has been found. A new configuration has been added. MORE completed. A new controller has been plugged in. Controller has been powered on. System has rebooted. None. 149 4 A logical drive has been deleted. A new configuration has been added. A new logical device has been deleted. Controller has been removed. Controller has been powered off. None. 150 4 Expand capacity started.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 159 2 Data for Disk Block has been lost due to Logical Drive problem. Data retained in RAID Cache for a Write-back Logical Drive cannot be stored to the physical medium because of Logical Drive problem. The Logical Drive problem could be because of multiple physical medium error or multiple physical devices offline or other reasons.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 272 1 Power supply failure. Cable connection is broken. Power supply failure. Reconnect cable or replace the power supply as required. 273 4 Power supply has been restored. Faulty power supply has been replaced. None. 274 2 Power supply failure. Cable connection broken. Power sup- Replace power supply. ply failure. 275 4 Storage cabinet power supply is not present.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 306 4 Storage Works enclosure reported normal state. Problem has been rectified. None. 320 1 Fan failure. Cable connection broken. Fan failure. Replace fan. 321 4 Fan has been restored. Faulty fan has been replaced. Cable is connected properly. 322 4 Fan is not present. Enclosure Management Connection Refer to the enclosure is broken. Management hardware fail- manufacturer's service ure.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details 331 Actions 4 Enclosure access has been restored. Enclosure has been fixed or replaced. None. 332 2 Enclosure access is offline. Enclosure management connection is broken. Management hardware failure. 384 4 Array management server software started successfully. The server system (or array manage- If you did not expect a ment utility server) started. system reboot, investigate. 385 2 Write back error.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 392 4 Battery Present A battery module has been detected and is now operational. None. 393 3 Battery Power Low. Battery power is low. If this message occurs without power failure, replace the Battery. 394 4 Battery Power OK. Battery does not have enough power to enable the write data cache. None. 395 0 Controller is gone. System is disconnecting from this controller.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 418 2 BBU out of service. BBU will not be able to power the cache if AC power fails. Firmware will switch WriteBack logical drives to WriteThrough. Replace BBU. 427 2 Mirror Race recov- Some physical devices may have ery failed. failed. Run consistency check and restore consistency. 428 0 Mirror Race on critical logical drive. Logical device is critical. Replace failed physical disk and rebuild.
Table A.2 GAM TT Events for PCI Controllers (Cont.) ID Severity Description Details Actions 517 2 Lost connection to server, or server is down. Lost network connection to server. Server shutdown. None. 640 3 Channel Failed. Cable disconnected. Plug in cable. 641 3 Channel Online. Cable reconnected. None. 896 2 Internal Controller is in the hung state. Internal Controller is in the hung state. Controller has to be powered off and on. 897 2 Internal Controller hung.
A-18 Event Information Version 1.0 Copyright © 2001-2003 by LSI Logic Corporation. All rights reserved.
Glossary ANSI American National Standards Institute, a standards organization that promotes and facilitates understanding among qualified members for the implementation of agreed upon code and signaling standards and conformity. ANSI represents the U.S. in the ISO (International Standards Organization). Applet Small application programs that are usually built into an operating system or a larger application program and designed to run from within another application.
• All system drives that are dependent on the failed disk drive are configured as a redundant array: RAID 1, RAID 3, RAID 5, or RAID 0+1. During the automatic rebuild process, system activity continues; however, system performance may degrade slightly. Automatic Switchover See Failover Background Initialization Where the initialization process of a disk array takes place in the background, allowing use of a disk array within seconds instead of several hours. Also known as Immediate RAID Availability.
Cache A temporary storage area for frequently accessed or recently accessed data. Cache is used to speed up data transfer to and from a disk. See also Caching. Cache Flush Refers to an operation where all unwritten blocks in a Write-Back Cache are written to the target disk. This operation is necessary before powering down the system. Cache Line Size Represents the size of the data “chunk” that will be read or written at one time, and is set in conjunction with stripe size.
DACCF Disk Array Controller Configuration File (utility), a diskette-based configuration utility for RAID configuration. Data Transfer Rate The amount of data per unit of time moved through a channel or I/O bus in the course of execution of an I/O load, usually expressed in Mbytes/s. Degraded Mode A RAID mode used when a component drive has failed.
Drivers A software routine that receives I/O requests from higher levels within the operating system and converts those requests to the protocol required by a specific hardware device. ECC Error Correcting Code, a method of generating redundant information which can be used to detect and correct errors in stored or transmitted data. EEPROM Electrically Erasable PROM, see EPROM. EPROM Erasable Programmable Read Only Memory, memory which can be erased and re-used.
Global Array Manager (GAM)™ A Mylex RAID management utility that allows a system administrator to configure, monitor, and manage network RAID storage from anywhere in the world. GAM can communicate critical information via e-mail, fax, pager, SNMP, or the launching of an application. GAM is everything needed to manage Mylex PCI RAID Controllers, SCSI Host Adapters, and External RAID Controllers.
Java A programming language expressly designed for use in the distributed environment of the Internet and enforces a completely object-oriented view of programming. Java can be used to create complete application programs that may run on a single computer or be distributed among servers and clients in a network. It can also be used to build small application modules, or applets, for use as part of a Web page. Kilobyte 210 (1,024). Abbreviated as KB or Kbyte.
single-ended devices on the bus and revert to single-ended signaling. Devices need to be Ultra2 SCSI LVD drives in order to take advantage of the LVD signaling. Mylex AcceleRAID, eXtremeRAID, and DAC FL controllers are LVD controllers. Megabit A million bits; used as a common unit of measure, relative to time in seconds, as an expression of a transmission technology's bandwidth or data transfer rates (abbreviated as Mbit).
NOS Network Operating System, an operating system that has special features for connecting computers and peripheral devices into a LAN. NVRAM Non-Volatile Random Access Memory, a memory unit equipped with a battery so that the data stays intact even after the main power had been switched off. Offline A Logical Drive is in an “offline” state if no data can be read from it or written to it. Offline does not apply to physical disk drives.
computer that performs logic operations and manages data movement in the computer. Plug and Play The ability to install peripheral cards or other devices without requiring manual configuration by the user. PROM Programmable Read-Only Memory, memory that users with appropriate instructions can reprogram. Protocol A special set of rules for transmitting data between two devices in a telecommunication connection.
Level 0: Provides block “striping” across multiple drives, yielding higher performance than is possible with individual drives. This level does not provide any redundancy. Level 1: Drives are paired and mirrored. All data is 100 percent duplicated on a drive of equivalent size. Level 3: Data is “striped” across several physical drives. Maintains parity information which can be used for data recovery. Level 5: Data is “striped” across several physical drives.
Read-Ahead Cache A caching strategy whereby the computer anticipates data and holds it in cache until requested. Recovery The process of reconstructing data from a failed disk using data from other drives. Redundancy The inclusion of extra components of a given type in a system (beyond those the system requires to carry out its functions). Replacement Table A table that contains information regarding which SCSI devices have been replaced by others through standby replacement.
to obtain base-level fault-tolerant alert notification and status information. All Mylex RAID controllers feature SAF-TE. SAN See Storage Area Network SANArray™ Server-independent External RAID Controllers that provide fibre channel interface connections to loop or fabric topologies and dual redundant loops for continuous access to large data pools. These controllers are designed for homogeneous and heterogeneous operating system setups in Storage Area Network environments.
SMB Server Message Block protocol, a method for client applications in a computer to read and write to files on, and to request services from server programs in, a computer network. A client application can read, create, and update files on the remote server. It can also communicate with any server program that is set up to receive an SMB client request. SNMP Simple Network Management Protocol, the protocol governing network management: for monitoring network devices and their functions.
Synchronous Data Transfer Data transmission synchronized to a defined time interval, and is faster than asynchronous SCSI because there is no wait for acknowledgment of each byte from the receiving device (up to 20MHz). Compare with Asynchronous Data Transfer. System Disk The disk on which a system’s operating software is stored. System Drives See Logical Drives TCP/IP Transmission Control Protocol/Internet Protocol, the basic communication language or protocol of the Internet.
disk drive) receives the data to be written. The target disk drive will receive the data at a more appropriate time in order to increase controller performance. An optional cache battery backup can be used to protect against data loss as a result of a power failure or system crash. Write-Through Cache A caching strategy whereby data is written to the SCSI drive before a completion status is returned to the host operating system.
Index A C Add Logical Drive 4-10, 4-13, 4-21 Adding a Server Group to the Server Group List 3-17 Adding a Server to the Servers List 3-18 Alarm Setup add a fax using Linux 3-28 add a fax using Windows 3-26 add a pager 3-25 add an application to launch 3-30 add an email using Linux 3-30 add an email using Windows 3-28 remove a fax 3-28 remove a pager 3-26 remove an application to launch 3-32 remove email 3-30 Alarms 3-24 ANSI 1-1 Applet 1-1 Application Program 1-1 Array 1-1 Assisted Configuration 4-9 faul
Device Driver 1-4 Device Errors 5-7 Device Information 5-6 Device Inquiry Data 5-6, 5-7 Disk Array defragmenting 6-9 spanning 4-44 transporting 4-40 Disk Device Information 6-5 Disk Failure Detection 1-4 Disk Media Error Management 1-4 Disk Spin-up 4-4 Display Controller Information 3-15 Drive Groups, Drive Packs 1-4 Drivers 1-5 E ECC 1-5 Edit Configuration 4-21 EEPROM 1-5 Enclosure details page 5-17 information page 5-16 Enclosure Information 3-12, 5-17 Enclosure Monitoring and Management 5-15 EPROM 1-5 E
M P M.O.R.E.
guest 3-19 Security Access Levels administrator 3-20 guest 3-19 user 3-19 Segment Size 1-13 Selected File Server 3-4 Sequential I/O 1-13 Server 1-13 Server Groups setting up 3-17 Server Selection Box 3-4 Servers setting up 3-17 SES Enclosure Information details page 5-17 information page 5-16 Session 1-13 Settings 3-13, 3-15 Severity Levels A-1 Sign On 3-11, 3-15, 3-20 Signing On to a Server 3-19 security access levels 3-19 sign on 3-20 SMART 1-13 SMB 1-14 SNMP 1-14 Software Driver 1-14 Software Requirement
Customer Feedback We would appreciate your feedback on this document. Please copy the following page, add your comments, and fax it to us at the number shown. If appropriate, please also fax copies of any marked-up pages from this document. Important: Please include your name, phone number, fax number, and company address so that we may contact you directly for clarification or additional information. Thank you for your help in improving the quality of our documents.
Reader’s Comments Fax your comments to: LSI Logic Corporation Technical Publications M/S E-198 Fax: 408.433.4333 Please tell us how you rate this document: Global Array Manager Transition Tool Client Software User’s Guide. Place a check mark in the appropriate blank for each category.
