MAXDATA SR1202 M1 StorView® RAID User Guide
Contents
Contents 1 Preface 9 Notices ....................................................................................................................................................... 9 Acknowledgments ..................................................................................................................................... 9 What is in this guide ...................................................................................................................................
Initializing the Array .................................................................................................................................. 49 Pause/Resume the Initialization ............................................................................................................... 51 Pause Initialization ............................................................................................................................... 51 Resume Initialization ..................................
Advanced Logical Drive Functions ........................................................................................................... 96 Viewing Unassigned Free Space......................................................................................................... 96 Expanding a Logical Drive ................................................................................................................... 96 Deleting a Logical Drive ............................................................
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 6 StorView Main Screen - Tool Bar .................................................................................................... 13 StorView Main Screen - Enclosure Section .....................................................................................
57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99. 100. 101. 102. 103. 104. 105. 106. 107. 108. 109. 110. 111. 112. 113. Main Screen .................................................................................................................................... 75 Advanced Settings Window ................................................................................................
1 Preface Notices The information in this document is subject to change without notice. While every effort has been made to ensure that all information in this document is accurate, the Authors accept no liability for any errors that may arise. No part of this document may be transmitted or copied in any form, or by any means, for any purpose, without the written permission of the Authors. Acknowledgments Microsoft Windows 2003 is a registered trademark of Microsoft Corporation.
THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
2 Introduction Overview StorView® Storage Management software is a full-featured graphical HTML-based software suite designed to configure, manage, and monitor storage subsystems. StorView is built on a modular design and currently supports the RAID Module. However, other modules will become available in the future. The RAID Module provides the support for the SR1202 Enclosure Platform (SR1202 M1 RAID Storage Solution) with an extensive set of configuration and management options.
License Manager The StorView licenses have different limits for the two RAID Module versions of StorView. The hostbased version has Local Access and Global Access, and the embedded version has Remote Access and Global Access. License Access Limits The Local Access is the default license of the host-based software. It provides the basic control, management and monitoring of the locally attached storage solution. The Remote Access is the default license included with the embedded version.
3 StorView Quick Tour Learning the Interface StorView’s HTML interface provides the user with a means to interact with the software and storage solutions. Primary configuration functions include creating disk arrays, logical drives, SAN LUN mapping and assignment of hot spare drives.
Tool Bar Button Description Storage Assistant This button will start the Storage Assistant wizard which will automatically configure your storage system based on user inquiries. Create Array This button will open the Create Array panel allowing the user to create new disk arrays. Create Logical Drive This button will open the Logical Drive panel allowing the user to create new logical drives.
Enclosure Section Description and Condition Drive Status Icon Animated drive status icons which are displayed in the front view of the enclosure, and will indicate the status and condition of the specific disk drive. Member • Member - Disk drive is a member component of an array. Available • Available - Disk drive is online and available for use in an array or as a hot spare. Dedicated Spare • Dedicated Spare - Disk drive is marked as a dedicated spare to an array.
Enclosure Section Description and Condition Fan Icon (continued) Fan 2 Failed (yellow) • Fan 2 Failed - One fan in the fan module has failed. The fan which failed will be indicated on the icon. Failure (red) • Failure - Both fans in the fan module have failed or the cooling fan module has been removed. Power Supply Icon Power Supply icons are displayed on the Main screen rear view image of the enclosure and will change according to the state of the specific power supply.
Enclosure Section Description and Condition Enclosure Icon - SR1202 RAID Enclosure icons are displayed at the bottom of the main screen and Storage Solution will change shades according to enclosures state, as well as the state of the individual components. The enclosures are labeled above each front view to aid with identifying them in a multiple enclosure environment. • Normal - All components are operating normally.
Mixed Drive 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. Figure 5. Mixed Drive Warning Message 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.
Array and Logical Drive Section Figure 7.
Array and Logical Drive Section Description and Condition Array Status Icon This icon appears adjacent to the Array name and gives a overall status of the array. Green (Normal) • Green - Status is ok. Yellow (Warning) • Yellow - Indicates a drive component in a RAID 1, 10, 5 or 50 array has failed and the array is no longer fault tolerant, or the array is in a rebuild cycle. Red (Error) • Red - Indicates an array is invalid or offline due to an error: RAID 0 = One drive has failed.
Server Sidebar Section Figure 8. StorView Main Screen - Server Sidebar Section Server Section Description and Condition StorView Server Icon Depicts the current StorView server that you are logged into. The icon will indicate the status of its’ components by changes in the color and state: Normal • 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.
Server Section Description and Condition Remote StorView Servers Icon Depicts the discovered StorView servers that you are not logged into. The icon will indicate the status of its components by changes in the color and state: • Flashing White - The server has not responded in at least 40 seconds and is considered missing. If you would like to remove the missing server from the list, click the Rescan button. This will refresh the screen with a current list of discovered servers.
How to Use this Document The design of this user guide is to introduce StorVIew to its users, provide an explanation of the interface through this quick tour section and provide a step-by-step approach to configuring up the network settings when using the embedded version. If you are using the host-based version you may skip Chapter 4. The Getting Started chapter will walk you through starting StorView, upgrading the license if necessary, and configuring E-mail, SNMP, and additional monitoring.
4 Embedded StorView Setup Embedded Network Settings NOTE If you are using the host-based version of StorView, you may skip this chapter. Upon start-up, embedded StorView looks at the user Preferences Settings to determine if an IP address exists. If one is defined it will initialize the network interface using that IP address. In the event an IP address is not defined, it attempts to get a DHCP IP address. You will need to contact your network administrator for the IP address assigned by the DHCP server.
Using Dynamic IP (DHCP) NOTE StorView does not display the TCP/IP information when Dynamic IP (DHCP) is selected. You must use a third-party network administration program to obtain this information. To use the DHCP Server network interface settings: 1. Click the “radio button” next to Dynamic IP (DHCP). 2. Click the APPLY button to make the changes effective. 3. Click the CLOSE button. Using Static IP To manually configure the network interface settings: 1. Click the “radio button” next to Static IP.
5 Getting Started Starting StorView Host-based StorView is started by opening your web browser software and entering the IP address of the host attached to the storage system followed by the port number. The URL format will be either “HTTP://:9292”, “HTTP://127.0.0.1:9292” or “HTTP://localhost:9292”. NOTE For Microsoft Windows users, you may also launch StorView via the Start Menu. Click the Start button and select Programs, then choose StorView and select “StorView Manager Console”.
Figure 10. License Upgrade Screen 2. Once you have completed the upgrade, the window will reload with the E-MAIL and SNMP tabs active. Click on the Close button in the confirmation window. 3. Click the Close button on the Settings window. 4. You can verify the change by clicking the About button and noting that it now displays (Global), see ”About” beginning on page 102.
E-MAIL Configuring E-MAIL Notices With a Global license installed, StorView provides you with the ability to establish up to ten E-MAIL addresses where notices of events can be automatically sent. Event Type Icons These icons are displayed in the E-MAIL setup. They depict the type of events that can be selected or isolated for E-MAIL notices. Information • Information - This icon represents the information type of events. Warning • Warning - This icon represents a warning type of event.
5. Click the APPLY button. You will receive a confirmation message that the changes were successfully completed. Click the CLOSE button. 6. Test the configurations by clicking the TEST button. You will receive a confirmation message that the test was successfully completed, and each addressee will receive a “Test Message” from the mail server. Click the CLOSE button. 7. Click the CLOSE button on the SETTINGS window. Deleting an E-MAIL Addressee 1. From the Main screen click on the SETTINGS button.
SNMP Configuring SNMP Traps StorView can be configured to send SNMP traps to any network management system. These traps carry all the information that appears in the log entries for each level of severity. All SNMP traps sent from StorView are received by the host SNMP Servers designated in the settings window for the specified port and community. 1. From the Main screen click on the SETTINGS button. 2. Click the SNMP tab. 3.
Deleting an SNMP Server 1. From the Main screen click on the SETTINGS button. 2. Click the SNMP tab. 3. Click the DELETE button next to the SNMP Server you wish to remove. 4. Click the APPLY button to make the changes effective, a status pop-up notice will appear. Then click the CLOSE button on the SETTINGS window. Changing the Password This option provides the ability to change the access password used at log in. 1. From the Main screen click on the SETTINGS button. 2.
Monitoring Setting The following options enable network administrators to make adjustments to the StorView server’s multicast functionality. In the event there is a port conflict with the default multicast port, you have the ability to change this parameter. NOTE The Monitoring Settings are disabled with the Remote license, you must upgrade to a Global license to enable these features. 1. From the Main screen click on the SETTINGS button, then click the PREFERENCES tab at the top of the window. 2.
Additional Monitoring Servers To specify additional StorView server(s) on a different subnet to be included in the receipt of StorView server packets, enter the IP addresses of those other StorView servers. You may add up to 10 additional monitored servers. 1. From the Main screen click on the SETTINGS button. 2. Click the PREFERENCES tab at the top of the window. 3. Enter the IP address in the “Individually Monitored Servers” field of another StorView server outside the subnet and click the ADD button. 4.
6 Storage Assistant Assisted Automatic Configuration NOTE If you will be manually configuring your disk array, hot spare drives and logical drives, skip this chapter. The StorView Storage Assistant is a wizard like feature that will automatically configure your storage system after it has obtained some brief information from the user. 1. To begin, click the Storage Assistant button on the Tool Bar located on the Main screen. Figure 18. Main Screen - Starting Storage Assistant 2.
The name is used to identify this storage solution. You may use up to 64 characters, although only the first 25 characters are displayed. Figure 19. Storage Assistant - Introduction 3. Click the NEXT button. NOTE At any point you can click the “PREVIOUS” button to move back one screen and make any necessary changes. 4. Select a host server connection for this storage from the list of detected connections. Enter a name for this server connection and click NEXT.
Figure 20. Storage Assistant - Server Screen 5. Click the NEXT button. If you have mixed SAS and SATA disk drives in your enclosure, the following screen will appear. If you do not have mixed drives proceed to the Server page, skip to step 6. NOTE You cannot mix SAS and SATA drive types. You must create the logical drives from arrays comprised of the same type of drives then return back to this page and select the other drive type and create additional logical drive.
Figure 21. Storage Assistant - Physical Disk Type Screen After you have selected a specific drive type and created the logical drive(s) with those disks, you can then click the PREVIOUS button to create another logical drive using the drive type not yet selected. Or, you can alternate back and forth between selecting a disk type and creating logical drive(s). 6. Enter a name for the logical drive or use the default name. Figure 22.
7. Enter the capacity for the logical drive (GB), or you may use the default capacity. The value is expressed in GB. 8. Click the check box next to the named server connection(s) displayed in the Server Connection(s) pane. Click the ADD button. The Logical Drive is added to the summary window at the lower section of the window. Figure 23. Storage Assistant - Logical Drive Screen NOTE Repeat steps 4–8 for each additional Logical Drive you wish to create and assign to a server.
Figure 24. Storage Assistant - Logical Drive Screen If you decide that a Logical Drive you added is not desired, you may remove it from the list by clicking the REMOVE button next to the Logical Drive name in the summary window. If you have used up all the available capacity, the fields will gray out and the available capacity will display “0 GB” in red. 9. You are presented with a summary of your selections. Click the APPLY button. The Storage Assistant will begin configuring the storage solution.
Figure 25. Storage Assistant - Finished Screen This completes the configuration of your storage solution. Before you begin using it, we recommend that a backup copy of the configuration be made, see ”Saving the Configuration” beginning on page 59.
7 Configuring a Storage Solution Creating Disk Arrays Configuring a storage solution requires some planning to ensure that you define the correct RAID level and array options, hot spares and logical drives for your solution requirements. This chapter will step you through the process to configure and manage your disk arrays, assign hot spares and create the logical drives. This manual assumes you have a basic understanding of RAID concepts.
Mapped LUN Number Each logical drive is presented to the host system with a unique LUN. In certain cases (such as after deleting another logical drive) it may be desirable to change the number that a logical drive is presented as. This can be done at any time, bearing in mind that any attached host systems may need to be rebooted or re-configured to maintain access to the logical drive.
Optimization and Drive Selection for RAID 5 Arrays Typical RAID 5 implementations require a number of steps to write the data to the drives. In order to optimize your system performance based on the type of writes you expect in your operation, we have provided detailed information on optimizing the performance using full strip write operations in an appendix.
The Create Array window will open, see Figure 27 ”Create Array Screen”. 2. Select drives to include in your array. Click on each drive that has the “Available” icon displayed. The icon will change to “Selected”. NOTE You will notice numbers next to each item on the screen. These are the suggested sequential order to follow when creating an array. As you select drives, the projected size of the array is displayed in the upper right corner of the window.
5. Choose the chunk size. Click the pull-down menu and select a chunk size (64K, 128K, or 256K). For RAID level 0, 1, or 10 choose the correct size from the tables on this page. For RAID 5/50 applications, refer to the note below.
9. Set the Writeback Cache options. Click the pull-down menu to select from Disabled, or choose one of the pre-determined cache threshold sizes (1 MB, 2 MB, 4 MB, 8 MB, 16 MB, 32 MB, 64 MB, 128 MB, 256 MB or MAX “MB”), see ”Configuring Array Writeback Cache” beginning on page 49.
While monitoring the array initialization, under the Array name a progress bar appears displaying the percent complete for the initialization. Also, in the Enclosure front view, the disk drives being initialized display an animated icon during the initialization. You can stop or pause the Initialization process if you wish by clicking on the link located to the right of the progress bar. Stopping the initialization will cause your array to be trusted.
1. Locate and click on the in the Array section on the Main screen you wish to initialize. This will open the Array Information window. 2. From the Array Information screen, click the INITIALIZE button. Figure 29. Array Information Screen 3. You will be prompted to enter your password to confirm you wish to initialize the array. Type your password and click GO. A confirmation message appears indicating the success of the operation, click the CLOSE button. 4.
Figure 30. Monitoring the Initialization Progress Placing the mouse pointer over the progress bar will display the percent complete for the initialization progress in a pop-up window. The drive member icons of this array will change to an animated icon indicating the array is initializing. You can stop the initialization process, if you wish, by clicking the Stop link located to the right of the progress bar.
NOTE You cannot mix SAS and SATA disk drives in the same disk array. If you have a mix of SATA and SAS drives in the enclosure, each array comprised of either SATA or SAS drive types must have a dedicated spare assigned of like type. Assigning a Global Spare 1. From the Main screen, click a drive icon within the enclosure front view indicating “Available” that you wish to make a global hot spare. Figure 31.
Figure 32. Drive Panel Screen 3. A pop-up window will appear, select Global Spare from the drop down menu. Figure 33. Make Spare Screen 4. Click the CREATE button. You will see a confirmation window indicating the process was successful, click the CLOSE button. 5. Click the CLOSE button on the Drive panel window.
Assigning a Dedicated Spare 1. From the Main screen, click a drive icon in the enclosure front view indicating “Available” that you wish to make a dedicated hot spare. NOTE There must be at least one drive online and available to be assigned as a hot spare, and a configuration must exist (at least one array defined). 2. From the Drive panel screen, click the Make Spare button. Figure 34. Drive Panel Screen 3.
4. Click the CREATE button. You will see a confirmation window indicating the process was successful, click the CLOSE button. 5. Click the CLOSE button on the Drive panel window. NOTE Only arrays that the spare drive is large enough to replace any member drive of will be 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).
NOTE You cannot mix SAS and SATA disk drives in the same disk array. If you have a mix of SATA and SAS drives in the enclosure, each array comprised of either SATA or SAS drive types must have a dedicated spare assigned of like type. For example, if you have an array with SAS drives and one with SATA drives you must have two hot spares one assigned for SAS and one for SATA for the hot spare feature to work and to have complete fault tolerance. 1.
1. From the Main screen click on the Create Logical Drive button in the Tool Bar. Figure 38. Main Screen 2. Select the region or regions you wish to use for your logical drive from the list “Select Which Array(s) to use” window. You may hold the or key down to make multiple selections. 3. Enter a name for your logical drive, you may use up to 32 characters. The default names for logical drives follow the format “LDx”. Only 12 characters plus an ellipse is displayed when the name is longer.
Figure 39. Create Logical Drive Screen 4. Enter the size in GB for the logical drive capacity. As you select your regions, the maximum size is displayed to the right of the “Size:” field. You may use all or some of these regions for this logical drive. If you are creating a logical drive greater than 2,198 GB (2 TB), please refer to your operating and file system documentation to verify it supports such sizes. Figure 40.
5. Select the LUN number for the logical drive from the “Mapped to” drop down menu. 6. Select the Controller Ports you wish to make the logical drive available through. Place a check mark next to the controller ports displayed. If a logical drive is to be seen on all controller ports and to all host HBAs, then set the availability by placing check marks for both Controller’s Port 0 and Port 1. Otherwise, place a check mark on the appropriate controller port you wish the logical drive to be seen.
Saving the Configuration 1. From the Main screen Tool Bar click the Archive Configuration button. Figure 41. Main Screen The Configuration Archival Operations screen appears. 2. Click the SAVE button. You may click the CLOSE button to cancel and return to the Main screen. Figure 42. Configuration Archival Operations Screen 3. Click the DOWNLOAD button to continue with saving the configuration file, or click the CANCEL button to cancel. Figure 43.
4. You are presented with the browser’s standard “File Download” screen. Click the SAVE button to continue, or CANCEL to quit. Figure 44. Save Configuration File Screen 5. Next, you are presented with the “Save As” screen. If you wish to use the default file name, select the directory and click the Save button, otherwise enter the name you wish to use and specify the directory, and then click Save. Click the Cancel button to exit. Figure 45. File Name Screen 6.
8 SAN LUN Mapping 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.
Figure 46. SAN LUN Mapping Screen Overview of SAN LUN Mapping Screen The illustration below provides an explanation of each component of the SAN LUN Mapping window. A graphical illustration of the physical connection from the Host HBA Port to the storage enclosure is provided to help you visualize the topology being mapped.
Figure 47. SAN LUN Mapping Example The SAN LUN Mapping screen is basically divided into two primary sections. The first section on the left side of the screen encompassed in the box titled “Topology Information” displays the list of discovered Host HBAs and the current mappings. The second section displayed on the right hand side of the screen is for adding, modifying and deleting SAN LUN Mappings. HBA PORTS Name Section A list of discovered named and unnamed HBA Ports are displayed.
1. From the Main screen click the SAN Mapping button in the Tool Bar. Figure 48. Main Screen 2. Select and name the host HBA port. In the “HBA Ports Name” section, select an unnamed port and identify it using the displayed HBA Node WWN and HBA Port WWN under the NAME HOST section. 3. In the “NAME HOST” section, enter a user friendly name for the HBA Port. You may use up to 32 ASCII characters, however only 11 characters are displayed in the HBA Ports Name field. 4. Click the Assign Name button.
Figure 49. SAN LUN Mapping Screen 5 Add a mapping. In the “ADD NEW MAP” section, do the following: (A) Select the logical drive you wish to map to. Click the pull down menu and choose from the list of logical drives displayed. Default logical drive names are LD1, LD2, LD3, etc. NOTE Logical drives marked with an asterisk “*” indicate that another mapping for another Host HBA has been established for this logical drive.
Deleting a SAN LUN Mapping 1. From the Main screen click the SAN Mapping button in the Tool Bar. 2. Select a Host HBA port under the “HBA Ports Name” section that contains the mapping to be removed. Figure 50. SAN LUN Mapping Screen 3. Select a Mapping to remove from the “Mappings” section. 4. Click the REMOVE MAPPING button and click APPLY. 5. You will receive a confirmation, click the OK button to continue, or CANCEL to exit and return to the SAN LUN Mapping window. 6.
1. From the Main screen click the SAN Mapping button in the Tool Bar. 2. Select a Host HBA port under the “HBA Port Name” section 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 REMOVE MAPPING button. Figure 51. SAN LUN Mapping Screen 5. You will receive a confirmation, click the OK button to continue, or Cancel to exit and return to the SAN LUN Mapping window.
If you are making multiple changes in multiple sessions, clicking Restore will reset the parameters to the last time the APPLY button was clicked. For example, if you create a new mapping and click APPLY then change the name of the Host and decide you don’t want that change, clicking the RESTORE button will cancel the name change but the new mapping remains valid since the APPLY button had already been clicked. 8.
9 Controller Environmentals Overview The Controller Information window provides you with options to view the status of the a controller and makes changes to some of its environmental parameters. User controllable functions include updating controller firmware, synchronizing the time and date, as well as resetting controllers and managing log files.
Figure 53. Controller Window with Pop-Up Status This group of items are specific to the functional status of the controller. It includes general controller status, battery status, temperature of the controller, and voltage status. Placing the mouse pointer over the item will display a pop-up window with detailed information. In the previous examples, the mouse pointer was over “Voltage.” Status icons appear adjacent to the item in the group.
Update Controller Firmware This option provides the means for the user to update the controller firmware. The controllers have the ability to automatically update their partner’s firmware, however the update process behaves differently under certain conditions.
Figure 55. Controller Information Screen 3. Locate the firmware file, click the Browse button. The file will be named similar to “18-1-98104001.bin.” The file will be made available from the customer service representative. Figure 56. Firmware Upload Screen 4. After locating the file, click the UPLOAD button.
10 Controller Advanced Settings Overview The Controller Information window allows you to view and make changes to the controller operational settings. Since your environment may be different, you may want to make changes to the controller parameters to optimize the system for your application. This is accomplished through the Advanced Settings window, activated from the Tool Bar.
The Advanced Settings window is divided into three sections; Identity, Fault Tolerance and Host Ports. Figure 58. Advanced Settings Window Identity In the Identity section, you can make changes to the Configuration Name, assign the configuration the WWN of either controller, and set the LUN for the controller. Figure 59.
• Configuration Name - This is the name you will assign to the configuration. The configuration contains all the information that defines the disk arrays, logical drives, SAN LUN Mapping, hot spare drives and controller specific settings. If you wish to change the configuration name, enter the new name in the block provided. Click the APPLY button followed by the CLOSE button. • Configuration WWN - This is the RAID Controller’s WWN reported to the outside world to identify the configuration.
• Auto Spare - This option when selected allows the data to be rebuilt on the drive that is inserted into the slot from which the failed drive was removed. This is beneficial when a hot spare or global spare is not designated for a fault tolerant array and a drive fails in that array. • Auto Rebuild - Selecting this option will automatically start a rebuild operation when a faulttolerant array loses a drive member and a replacement or hot spare drive is available and online.
Host Ports In the Host Ports section, you can change the ID assigned to each of the controller ports and set the data rate. Figure 61. Advanced Settings Window • Controller Port ID (P0) - This is the target ID for both controller(s) port 0. It can range from: Soft Address, or 0 - 125. The default is ID 4. • Controller Port ID (P1) - This is the target ID for both controller(s) port 1. It can range from: Soft address, or 0 - 125. The default is ID 5.
11 Managing the Storage Solution Advanced Array Functions Deleting an Array ! Caution You must stop all host I/O operations prior to deleting an array. ! Caution Deleting an array will delete all data on the logical drives and those associated with that array. Be sure you have a backup of the data before proceeding. 1. Stop all host I/O operations. 2. In the Configuration section next to the Arrays section, click the you wish to delete. 3.
Figure 63. Confirmation Screen If the wrong password is entered, you will be prompted and the array will not be deleted. 5. Once the array has been successfully deleted, click the CLOSE button. Modifying Arrays Once the array has been created and is online you can make changes to the following: • The name of the array. • The Read-Ahead and Writeback cache parameters.
NOTE If the array was trusted or never initialized, you can initialize the array from this panel by clicking the INITIALIZE button. NOTE Arrays can be re-initialized, if an array has been initialized the button will be renamed to “ReInitialize”. Verify Parity It is desirable to perform a parity check as a normal maintenance procedure to ensure data integrity.
Figure 66. Verify Options Screen The following table provides a description of each option. Option Description Check Parity This option reads all the data and parity, calculates the XOR of the data, and compares it to the parity. If there is an error, it is displayed in the event log. Rewrite Parity This option reads all the data, calculates the XOR of the data, and writes this out as the new parity. This is the fastest to complete, since it does not have the overhead of a comparison.
Figure 67. Monitoring Progress of Parity Verification You can stop the Verification process if you wish by clicking on the Stop link located to the right of the progress bar. Identifying Drive Members Should the need arise, you can quickly identify which drives in the enclosure are members of a specific array. Located on the right side of an Array name is an icon (Drive Identify icon), whose appearance is like an arrow pointing to the lower left corner. This is used to turn on the identify function.
Figure 68. Identifying Member Drives Screen You can also identify specific drives in an array by flashing its Drive Status LED, see ”Locate Drive” beginning on page 95. Rebuilding an Array This option is designed for situations where the user wants to manually start a rebuild operation. One scenario where this option would be used is if you inadvertently pulled the wrong drive from a working array and that drive is now flagged as a failed drive, regardless of whether or not you reinsert the drive quickly.
Figure 69. Drive Panel Screen 2. Click the MAKE SPARE button. A small window will appear. Figure 70. Drive Panel Screen - Rebuild Options 3. Scroll down and choose the specific array that became critical from the removed drive. 4. A confirmation window will appear indicating the successful execution of the command, click the CLOSE button. 5. Click the CLOSE button on the Drive Panel window. 6. You can monitor the rebuild operation from the Main screen.
Expanding an Array ! Caution You must stop all host I/O operations prior to deleting an array. The Expand Array feature is used to increase the capacity of an existing array. An array can be expanded to a maximum of 16 drives. Only one array can be expanded at a time. NOTE No configuration changes can be made to the arrays, logical drives, or SAN LUN Mapping while an expansion operation is in progress. NOTE You cannot mix SAS and SATA disk drives in the same disk array.
Figure 71. Array Screen - Expand Array Tab Selected 8. You will be prompted to confirm the Expand operation. Type your password and click the GO button. 9. You will receive a screen prompt that the command was successful, click the CLOSE button. If the command was unsuccessful, review the settings for incorrect parameters and hardware for operational status. Figure 72. Expand Array Confirmation Screen Trust an Array When you create an array, you have the option to trust the array.
1. On the Main screen in the Tool Bar, click the CREATE ARRAY button. Figure 73. Create Array Screen 2. Select your drives. 3. Enter a name for your array. You may use up to 32 characters (ASCII). 4. Select the RAID level for the array. 5. Enter the desired chunk size. Click the pull-down menu and choose from the available values. 6. At Item 6, use the pull-down menu and select “Trust.” 7. Choose the “Back-off Percent” (reserved capacity) for the drives. The default is 1%. 8.
Restoring and Clearing the Configuration ! Caution If you cannot restore the configuration exactly as it was, you will not be able to restore access to the data and it will be lost. Because of day to day changes to your system which will cause differences between the configuration file and the actual configuration, the configuration should be periodically updated using the Save function.
Figure 75. Configuration Archival Operations Screen 3. The File upload screen appears, click the Browse button. Figure 76. Restore Configuration Upload Screen You are presented with the browser’s “Choose File” screen. Select the appropriate file and click the Open button to continue, or Cancel to quit. Figure 77. Restore Choose File Screen 4. Click the UPLOAD button to continue to restore the configuration, or click the CANCEL button to quit. 5.
Clearing the Configuration Some conditions or situations may call for you to clear the entire configuration. This process removes all arrays, logical drives, SAN LUN Mappings, etc. If there is any data on the drives, access to that data be lost when the configuration is cleared. 1. From the Main screen Tool Bar click the Archive Configuration button. Figure 78. Main Screen The Configuration Archival Operations screen appears. 2. Click the CLEAR button.
Figure 80. Clear Configuration Confirmation Pop-up Screen You will receive a confirmation of the operation. Click the CLOSE button. Notification To ensure that you are made aware of changes to the configuration, you can set up an E-mail account that sends you a message when an event of this type has occurred. This may serve as a notification that you should save the configuration file again, see ”Configuring E-MAIL Notices” beginning on page 29.
The Drive Panel screen will open. Figure 82. Drive Panel Screen Locate Drive 1. To locate a disk drive, identify the drive displayed in the enclosure front view and click that drive icon. The Drive Information window will open. 2. Click the LOCATE button. Figure 83. Locate Drive Screen 3. A sub menu will open in the Drive Information window, from which you will select the time interval to blink the Drive’s Activity LED. Select the time period you desire. 4.
Advanced Logical Drive Functions Viewing Unassigned Free Space Prior to creating or expanding a logical drive, you may wish to examine the unassigned free space. This will help you identify the available free space that can be used to create and expand logical drives. The Create Logical Drive window is designed to display all available unused space. 1. From the Main screen in the Tool Bar click on the Create Logical Drive button.
Figure 85. Main Screen 3. Locate the Expand section of the window (lower half), and follow the sequenced steps beginning at “Step 1” where you will choose a free space region to be used for the expansion. Figure 86.
4. In the “Add Capacity” box, enter the amount of the selected region to expand the logical drive. You may use the entire free region space or a portion of it. 5. Click the EXPAND button. 6. You will be prompted to enter your password to confirm the expansion. Type in your password and click the GO button. 7. You will receive a screen prompt that the command was successful, click the CLOSE button.
Figure 88. Logical Drive Information Screen 4. You will be prompted to enter your password to confirm the deletion. Type in your password and click the GO button. 5. You will receive a screen prompt that the command was successful, click the CLOSE button. If the command was unsuccessful, review the settings for incorrect parameters and hardware for operational status.
12 Failover, Performance and Additional Functions How StorView Server Failover Works The failover feature of the StorView RAID Module must have one of the following setups. If you are using the host-based version of StorView, two or more host servers must be directly connected to the SR1202 RAID Storage Solution enclosure and each host must have a copy of StorView installed with a Global Access license.
Additional StorView Functions About Clicking this button displays the software version information and the type of license installed. When using the embedded StorView the About window also provides the control button to update the software. 1. From the Main screen, click the About button, located in the upper right corner of the window under the StorView logo. Figure 89. Main Screen The following screen is displayed.
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 StorView server with the lowest serial number or IP address will take control of those devices. If you wish to take control of the storage solution from another StorView server, click the “Take Control” link from the Main screen message displayed on that StorView server. Figure 91.
Rescan This Rescan function will force a search to re-discover storage solutions in order to refresh the display and update status information. From the Main screen, click the RESCAN button located on the far left side of the screen. After a few moments the Main screen is re-displayed with updated information. Figure 92.
13 Support and Updates Tech Support This feature allows the user to provide technical support personnel with event and configuration information to assist with troubleshooting. 1. From the Main screen, click the Tech Support button, located in the upper right corner of the window under the StorView logo. Figure 93. Main Screen 2. Enter the requested information for each field. The Problem field is scrollable allowing you to review the information you will be sending.
Figure 94. Tech Support Screen 3. Click the DOWNLOAD button. You will receive a screen prompt to save the file on your local disk. Enter a name for the file and click Save. The software will create a file with your user data, a capture of the event log files, and a capture of all configuration information. Technical support representatives will be able to work with this information to assist with solving your problem. 4. Click the CLOSE button on the Technical Support window. 5.
! Caution Ensure there is uninterrupted power during the update. 2. Click the UPDATE button. 3. Type the name of the firmware file or click the Browse button and locate the file. The file name will be similar to storview-3.04.T014-XXX-nb-en.bin. Figure 96. About Update Screen (Embedded StorView) 4. Enter your login password and click the UPLOAD button. Once the update is complete, StorView Server will automatically restart. This process will not affect I/O activity.
14 Event Logs Overview StorView has the ability to manage the events generated by the controller, SES processor’s or SAF-TE processes. StorView also has its own unique events that are related to the StorView server component of the software. Events can be used to assist with troubleshooting, monitoring components, and determining the status of hardware components, logical drives and arrays.
The time stamp for each event in the StorView log is the exact time the event was received by StorView, and can be slightly off for the actual time it occurred in the controller log. After synchronization, events that occurred while the StorView server was down are marked with an additional string in the event description which displays the actual time stamp that event occurred. The string will be in the form of an asterisk followed by the time and date in parenthesis.
Figure 98.
Below you will find an explanation of the components of the event log. Figure 99. Event Log Description The embedded version of StorView does not support some components of Event Log window. The unsupported components include the Log # column, Log # window, Jump To button, Export button, and the Clear Log button. Clear log is now handled by the clear controller log function found in the Environmentals section.
Figure 100. Main Screen 2. Click the EXPORT button in the Event Logs window. Figure 101. Event Log Screen The following are examples of some web browser file export options, your browser may be slightly different. • If you are using Internet Explorer as your web browser, you will see the following screen. Choose to save the file or open it. The saved file format will be a comma delimited format.
Figure 102. Example of Export Log Event Options - Internet Explorer • If you are using a Mozilla type web browser, you will see the following screen. This product provides you with a few more options through the “Advanced” button. Click the Advanced button and select the file format type, creator application, and other options, as desired. Figure 103. Example of Export Log Event Options - Mozilla 3. Click the CLOSE button on the Event Logs window.
Clearing the StorView Event Log You can clear the event log from this window when using the host-based version of StorView. 1. To clear the log file, click the LOGS button on the Main screen for the storage system you are logged into. Figure 104. Main Screen 2. Click the CLEAR button in the Event Logs window. This will purge the event logs maintained by StorView for the logged in storage system’s RAID Controller. This will not clear the log of events maintained by the RAID Controller itself. Figure 105.
Operating System Event Log StorView is capable of passing all the events to the host operating system event log. Accessing the operating system event logs will display events generated by StorView. Each event is identified by an Event ID. In the tables for the events you will see the Event type followed by its ID. The ID is given in the format of its hexadecimal value and its equivalent decimal value in parenthesis.
Controller Events Messages Type [ID] The controller’s internal Error temperature C has [0xB03 (2819)] exceeded the maximum limit. The controller will shutdown to prevent damage. Cause Action Blocked fan. Check enclosure for sufficient air flow. Failing fan. Check for a failed fan, if found replace cooling fan module. Elevated ambient temperature. Check the ambient temperature of the environment, decrease the local ambient temperature. Blocked fan. Check enclosure for sufficient air flow.
Controller Events Messages Type [ID] Cause Action A discovery process has started to determine all SAS devices on the SAS domain. Information [0xB23 (2851)] Courtesy informational message. No action necessary. The other (partner) controller has been inserted. Information [0xB29 (2857)] Partner controller has been inserted. No action necessary. The other (partner) controller has passed its self-test and is now ready (failback).
Controller Events Messages Type [ID] Cause Action The controller has an invalid World Wide Name. Error [0xB55 (2901)] Occurs first time after production. Contact technical support. The Event Log has been Information cleared. [0xB56 (2902)] The user has cleared the event log. No action necessary. The controller has been reset. Information [0xB57 (2903)] User initiated a controller reset. No action necessary. The controller has been shut down.
Controller Events Messages Type [ID] Cause Action An SDRAM ECC error - bit at address has been detected and corrected. Warning [0xB72 (2930)] SDRAM error. If it repeats, replace the controller. A configuration parameter has been changed: (Array ) has been trusted due to a cancellation of an initialization. Information [0xB74 (2932)] A user cancelled an initialization No action necessary.
Drive & Array Event Messages Type [ID] Cause Action Rebuilding has failed due to an unrecoverable error on the new drive w/SN (SAS: w/ WWN) (Slot , Enclosure ) ( Drive ). Error [0xB0D (2829)] Typically due to a non-recoverable media error or hardware error. Backup all data and restore to a new array. The drive w/SN (SAS: w/ WWN) (Slot , Enclosure ) (Slot ) (Drive ) has failed due to a time-out. Error [0xB0E (2830)] Drive error.
Drive & Array Event Messages Type [ID] Cause Action A rebuild has started on Information the drive w/SN (SAS: w/ [0xB30 (2864)] WWN) (Slot (Drive ). A rebuild has started. No action necessary. A rebuild has completed on (Array Drive ) Information [0xB31 (2865)] A rebuild has completed. No action necessary. A rebuild has restarted on the drive w/SN (SAS: w/WWN (Slot (Drive ). Information [0xB32 (2866)] A rebuild has started.
Drive & Array Event Messages Type [ID] Cause Action A RAID 5/50 parity check has started on . Type of parity check = . Error [0xB43 (2883)] Parity check started. No action necessary. A RAID 5/50 parity Error check has completed on [0xB44 (2884)] . Type of parity check = . Error Count = . Parity check completed. No action necessary. A RAID 5/50 parity check has been aborted on . Type of parity check = .
Drive & Array Event Messages Type [ID] Cause Action An array expansion has started on Array . Information [0xB68 (2920)] Expansion has started. No action necessary. An array expansion has completed on Array . Information [0xB69 (2921)] Expansion has completed. No action necessary. An array expansion has restarted on Array . Information [0xB6A (2922)] Expansion has restarted. No action necessary. The writeback cache on Warning Array has been [0xB6F (2927)] disabled.
Drive & Array Event Messages Type [ID] Cause Action (SATA Drives Only) SATA Drive Error: (Slot ) Information . Error [0xB75 (2933)] Drive or SATA link error. No action necessary. (SATA Drives Only) A drive w/ SN (SAS: w/ WWN) (Slot ) has been removed. Error [0xB76 (2934)] A drive w/ WWN (Slot , Enclosure ) has been removed. No action necessary.
Controller Port Event Messages Type [ID] Cause Action A host has accessed a Logical 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 . Information [0xB2E (2862)] First access by a particular host after a LIP or reset. A host has accessed a Logical Drive for the first time, or for the first time following a reset.
Enclosure Events These events are related to the enclosure components reported by the SES processor or SAF-TE processes (SCSI). The type [ID] format is: Event type name with its associated ID expressed in [hexadecimal (decimal (displayed in the OS))]. Enclosure Event Messages Type [ID] Cause Action No SES drives were found which means no enclosure status information can be reported. This could be due to the SES slot(s) in the enclosure having no drives installed or the drives are malfunctioning.
Enclosure Event Messages Type [ID] Cause Action Power supply is OK. Information [0xC6B (3179)] Normal condition reported. No action necessary. Power supply is in a critical state. Warning [0xC6B (3179)] The specific power supply has failed. Replace the power supply. The specific power supply is powered off. Ensure that the specific power supply On/Off button is in the On position ( l ). Power supply is not installed. Error [0xC6B (3179)] The power supply was removed.
Enclosure Event Messages Type [ID] Cause Action Temperature sensor Error is in a critical state. [0xC6D (3181)] Temperature sensors are 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.
StorView 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 StorView server software component. The type [ID] format is: Event type name with its associated ID expressed in [hexadecimal (decimal (displayed in the OS))]. 130 StorView Server Event Messages Type [ID] Cause Action The server has been started. Information [0x101 (257)] The StorView Server started successfully.
StorView Server Event Messages Type [ID] Cause Action A user has logged out the Server from IP address: . Information [0x106 (263)] A specific user has logged out of the StorView Server from the specified IP address location. (The host name was not available.) No action required. A user has logged out the Server from Host: , IP Address: .
StorView Server Event Messages Type [ID] Cause Action Shared memory used for the Server and the GUI to communicate could not be created nor located. Error [0x301 (769)] StorView tried to create/locate the shared memory used for the Server and Server CGI script to communicate. Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them. A CGI request was initiated from the GUI but the associated shared memory could not be opened.
StorView Server Event Messages Type [ID] Cause Action The Server CGI script was unable to return CGI request results to the GUI. Error [0x307 (775)] The Server passed the completed request to the Server CGI but for some reason the request wasn’t completed correctly by the Server CGI script. Retry request. Quit StorView and all connections accessing this StorView Server, wait 1 minute and restart them. Restart the system. Start up is complete.
15 Statistics Overview StorView and the SR1202 RAID Controller will monitor all incoming commands, and calculate various statistics. The statistics monitored include: • Command Count • Command Alignment • Command Size • Read-Ahead Statistics • Write Clustering Statistics • RAID 5/50 Write Statistics From the Main screen click the Logical Stats button in the Tool Bar.
Statistic Description Reads This is the average number of MBs transferred in the last few seconds from the logical drives, controllers or ports. This value is expressed in MB/seconds. Writes This is the average number of MBs transferred in the last few seconds to the logical drives, controllers or ports. This value is expressed in MB/seconds. No.
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%). For example, consider a read or write command from a host system with Logical Block Address (LBA) 0x0000070, and access size 0x80, expressed in decimal 128.
Read-Ahead Statistics If sequential read commands are sent to the controller, it assumes that the commands which follow may also be sequential. It can then go and perform a read of the data, before the host requests it. This improves performance, particularly for smaller reads. The size of the read-ahead is calculated based on the original command size, so the controller does not read too much data. The controller maintains statistics for all read-ahead commands performed. Figure 108.
Statistic Description Read-Ahead Command Hit Rate This is the percentage of read command hits versus the total number of read commands that have been issued. This gives an indication of the sequential nature of the data access pattern from the host. 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.
Statistic Description Write Cluster Rate This is the percentage of the number of write commands that are part of a cluster versus the total number of write commands that have been issued. This gives an indication of the sequential nature of the data access pattern from the host, and of the performance of the writeback cache. RAID 5/50 Full Stripe Write Rate This is the percentage of the amount of data that is written as a full stripe write versus the total amount of data written.
16 Optimizing RAID 5 Write Performance Introduction With a typical RAID 5 implementation, there are a number of steps that are performed when data is written to the media. Every write from the host system will typically generate two XOR operations and their associated data transfers, to two drives. If the accesses are sequential, the parity information will be updated a number of times in succession.
Sequential Access If the commands sent from the host are not sequential, the controller will not be able to cluster them together. So, unless each individual access is sufficient to fill a stripe, a Full Stripe Write will not occur. Number of Outstanding Commands For the controller to successfully cluster commands, there has to be a number of write commands sent simultaneously. Setting the host to send up to 64 commands should prove adequate.
RAID 5 Sub-Array The difficulty in realizing the maximum performance possible introduces the concept of a sub-array. Suppose an array consisted of two RAID 5 sets, see Figure 110 ”Distribution of Data and Parity in a RAID 5 with Five Drives”. 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.
17 Troubleshooting Problems You May Encounter This chapter provides typical solutions for problems you may encounter while using StorView to control and manage the storage systems. Also refer to the Event chapter, and review the cause and actions for each event listed. Symptom Reason Solution Continuous indications that the partner controller has failed or is missing. A partner controller in an Active-Active configuration has failed or was removed.
Symptom Reason Solution Consistently occurring time out errors when the browser window is open. Host HBA parameter settings are not configured for best performance optimization. Access your Host HBA settings and make the following changes: Execution Throttle Improve general I/O performance by allowing more commands on the fibre bus. Do this by changing your host bus adapter’s execution throttle parameter to 256.
Symptom Reason Solution Inadvertently pulled the incorrect drive from the enclosure and the array is dead. Possible incorrect drive identification and removal. If by mistake you remove a working drive member instead of the failed drive, this can cause the array to fail. In most cases you can simply re-insert that drive that was incorrectly removed and the array will return to the same state it was in prior to removing the drive.
Symptom Reason Solution Expanding Array is displayed as “Critical.” Known issue and should be corrected in the next software release. During an array expansion, the array remains in a fault tolerant state. Should a drive failure occur during the expansion the operation will continue until it has completed, then if a hot spare was assigned, a rebuild operation will begin automatically.
Index A About Software Version ............................... 102 Access Alignment......................................... 142 Access Size .................................................. 142 Access Statistics .......................................... 135 Accessing SAN LUN Mapping ........................ 63 Accessing the Drive Panel .............................. 94 Advanced Settings.......................................... 75 Alignment .....................................................
Deleting a Logical Drive .................................. 98 DHCP Manager............................................... 25 DHCP Server .................................................. 25 Diagnostic Dump ............................................ 72 Different Node Name ..................................... 77 Disable Writeback Cache................................ 48 Drive Event Array Critical ............................................ 121 Array Expansion Complete ......................
M Mapping Name ............................................... 63 Mirror Cache ................................................... 48 Missing ........................................................... 15 Mixed Drive Types.......................................... 18 Mixed Drive Warning Message ...................... 18 Modifying Arrays ............................................ 82 Modifying a SAN LUN Mapping ..................... 68 Module Tabs ...................................................
Statistics ....................................................... 135 Status Environmental ..................................... 72 Storage Assistant ........................................... 35 Storage Solution Icon ..................................... 22 StorView Manager Console ............................ 27 StorView Server Events................................ 130 StorView Server Icon ...................................... 21 Stripe ..............................................................
