Accusys RAID GUI User's Manual
Accusys RAID GUI User's Manual Version:1.
Appendix Notice Product features and specifications described in this manual are subject to change without notice. The manufacturer shall not be liable for any damage or loss of information resulting from the performance or use of the information contained herein. Trademarks Accusys and the names of Accusys products and logos referenced herein are either trademarks and/or service marks or registered trademarks and/or service marks of Accusys, Inc.
Preface About this manual Congratulations on your purchase of the product. This controller allows you to control your RAID system through a user-friendly GUI, which is accessed through your web browser. This manual is designed and written for users installing and using the RAID controller. The user should have a good working knowledge of RAID planning and data storage.
Preface Company Contact Accusys, Inc. • • • • • 5F., No.38, Taiyuan St., Jhubei City, Hsinchu County 30265, Taiwan(R.O.C) Tel: +886-3-560-0288 Fax: +886-3-560-0299 http://www.accusys.com.tw/ E-mail: sales@accusys.com.tw Accusys U.S.A., Inc. • 1321 W. Foothill Blvd. Azusa, CA91702 • Tel: +1-510-661-0800 • Fax: +1-510-661-9800 • http://www.accusys.com.tw • E-mail: Maggie@accusys.com.tw Accusys Korea, Inc.
Contents Table of Contents Chapter 1: Introduction 1.1 Overview ........................................................................................................1-1 1.2 Key Features ..................................................................................................1-2 1.3 How to Use This Manual ................................................................................1-7 1.4 RAID Structure Overview ...............................................................................
Contents 2.7.2 Defragmenting disk groups ...................................................................2-43 2.7.3 Changing RAID level / stripe size for logical disks ................................2-44 2.7.4 Expanding the capacity of logical disks in a disk group ........................2-45 2.7.5 Shrinking logical disks ..........................................................................2-46 2.7.6 Expanding volumes ..............................................................................
Contents Chapter 3: Using the LCD Console 3.1 Starting LCD Manipulation .............................................................................3-1 3.1.1 Confirm password ...................................................................................3-1 3.2 LCD Messages ..............................................................................................3-2 3.2.1 LCD layout ..............................................................................................3-2 3.2.
Contents 4.4.3 Storage groups .....................................................................................4-19 4.4.4 Presentation planning ...........................................................................4-20 4.4.5 Selective storage presentation .............................................................4-20 4.4.6 Simple storage presentation .................................................................4-21 4.4.7 Symmetric-LUN storage presentation ....................................
Contents Chapter 5: Advanced Functions 5.1 Multi-Path IO Solutions ..................................................................................5-1 5.1.1 Overview .................................................................................................5-1 5.1.2 Benefits ...................................................................................................5-1 5.1.3 Configuring MPIO Hosts and RAID Controller ........................................5-2 5.1.
Contents 5.7.2 Installing the VDS Provider ...................................................................5-74 5.7.3 Uninstalling the VDS Provider ..............................................................5-74 5.7.4 Using the VDS Provider Configuration Utility ........................................5-74 5.7.5 VDS-Based RAID Management Software ............................................5-76 Chapter 6: Troubleshooting 6.1 General Guidelines .........................................................
Contents Appendix C: Boot Utility C.1 (N) Set IP address ........................................................................................ C-2 C.2 (L) Load Image by TFTP .............................................................................. C-3 C.3 (B) Update Boot ROM .................................................................................. C-4 C.4 (S) Update System ROM .............................................................................. C-4 C.5 (H) Utility menu ..........
Contents List of Tables Table 2-1 Buttons in monitor and config mode .................................................2-6 Table 2-2 Hard disk code .................................................................................2-6 Table 2-4 Information icons ..............................................................................2-7 Table 2-3 Hard disks tray color .........................................................................
Contents List of Figures Figure 1-1 Layered storage objects .................................................................1-8 Figure 2-1 GUI login screen .............................................................................2-1 Figure 2-2 Setting the language in Firefox .......................................................2-2 Figure 2-3 Languages dialog (Firefox) .............................................................2-3 Figure 2-4 Multiple system viewer (side button) ...........
Contents Figure 3-2 Menu tree ........................................................................................3-6 Figure 4-1 Interfaces to Access CLI .................................................................4-1 Figure 5-1 Dual independent MPIO hosts ........................................................5-4 Figure 5-2 Clustered server environment .........................................................5-6 Figure 5-3 Computer Management screen: Device Manager ......................
Contents Figure 5-31 Deployment example of RAIDGuard Central components ...........5-60 Figure 5-32 RGC Server monitor screen .........................................................5-63 Figure 5-33 RGC Agent monitor screen ...........................................................5-64 Figure 5-34 RGC GUI main screen ..................................................................5-65 Figure 5-35 Adding the IP address of an agent ...............................................
Contents Revision History Version xviii Description Release Date 1.0 Initial release 2006/09/22 1.01 2.2.2 Added detailed information of information icons shown in Monitor Mode. 2.2.3 Added detailed information of components shown in Monitor Mode. 2.4.2 Removed the restrictions on the number of spare disks for quick setup. 2.5.1 Added a note for the Disk Cache field shown in [RAID Management] > [Hard Disks]. 2.6.1/ 2.6.2/ 2.6.3/ 2.6.4/ 2.6.6 Modified the contents for the Schedule option. 2.6.
Contents Version 1.1 Description 2.4 Added Figure 2-10 (Overview screen) and modified the related descriptions. 2.5.2 Modified the hard disk state for quick setup. 2.6.1 Added one category, mode, and its definition. Added a note for the Modify button. 2.6.4 Added options to LD read algorithm. 2.6.6 Updated the Figure 2-11. 2.7.5 Modified the note for LD shrink. 2.7.6 Added expanding volumes. 2.7.7 Added shrinking volumes. 2.7.11 Added the contents for the Schedule option. 2.7.
Contents Version xx Description Release Date 1.1 2.11 Modified the descriptions related to the Reset button. 2.11.4 Added a note to explain the displayed information in the list. 3.2.3 Added UPS off emergent info. 3.2.5 Added hotkeys. Chapter 4 Updated CLI commands. Appendix C Updated event log messages. 2007/02/26 1.2 1.3 2007/07/15 Modified descriptions related to the logical disk expansion and logical disk shrink. 2.2.2 Modified descriptions related to the information icons. 2.2.
Contents Version Description Release Date 1.3 • Modified Company Address 2.2.3 Modified the descriptions related to the rear side of the RAID system and picture, include added SCSI controller picture. added component of Table 2-5. 2.6.6 Added a SCSI ID setting for simple method. 2.8.2 Added a Default SCSI ID setting for SCSI ports and provider setting data rate of SCSI on SCSI ports. Appendix F Added RAIDGuard Central. Appendix G Added VDS Provider. 2007/10/29 1.4 Chapter 1 Updated contents. 2.1.
Contents Version xxii Description Release Date 1.4 2.9.2 Added the new option ‘Port’ for the SNMP setting, and a note for the OIDs used for each SNMP version. 2.9.5 Added the new option ‘Path Failover Alert Delay” and a new check item ‘Controller Failure’ for Auto Write-Through Cache option. 2.10.6/2.10.7/2.10.9/2.11.1/2.11.2/ 2.11.3 Added a note to for the screen difference in the redundantcontroller system. Chapter 4 Updated CLI commands. Appendix B Added Features and Benefits.
Contents Version 1.4.2 Description Chapter 1 Added CLI In-band API Features. Added Snapshot function note. Chapter 4 Added support CLI In-band API. Modified 4.12 snapshot commands. Chapter 5 Added 5.1.8 Multi-path IO solution on SUN Solaris. Modified 5.3 Snapshot contents. Appendix D Modified D.10 snapshot events.
Contents Version 1.5 xxiv Description Chapter 6 Modified content of all. Chapter 5 Modified section 5.2. Move 5.2.2 Monitor Mode to 2.2. Move 5.2.2 SAS JBOD to 2.3. 2.9.2 Added SNMP agent functions. Added descriptions related SNMP MIB. 5.3.5 Removed. 5.3.6 Removed. 5.3.7 Removed. 2.6.6 Added descriptions related spare COW volumes functions. Added descriptions related Restore functions. Appendix C Revised the subtitles. 2.10.4 Added a Note. Chapter 1 Modified snapshot functions content.
Contents Version Description Release Date 1.6 Chapter 5 Modified section 5.2. Inserted Multiple ID solutions in section 5.2 2.2.3 Modified redundant controller RAID pictures 2.3.1 Modified redundant controller RAID pictures. Added RAID model names 2.8.2 Modified description. Added Controller Failover mode description. 2008/11/14 1.
Introduction Chapter 1: Introduction Congratulations on your purchase of our RAID controller. Aiming at serving versatile applications, the RAID controller ensures not only data reliability but also improves system availability.
Introduction Comprehensive online reconfiguration utilities are available for migration of RAID level and stripe size, volume management, capacity resizing, and free space management. • Outstanding Performance The RAID controller delivers outstanding performance for both transaction-oriented and bandwidth-hungry applications. Its superscalar CPU architecture with L2 cache enables efficient IO command processing, while its low-latency system bus streamlines large-block data transfer.
Introduction • Support up to 32 disk groups and 32 logical disk per disk group (Redundant/Upgradable controller) • Support up to 24 disks in one chassis and totally 64 drives with expansion units (Single controller) • Support up to 24 disks in one chassis and totally 120 drives with expansion units (Redundant/Upgradable controller) • Volume management • Support striping volume for performance enhancement • Support concatenating volume for large-capacity LUN • Support concatenated striping volume • Online v
Introduction • Support intelligent disk I/O scheduling • Selective performance profile: AV streaming, Max IOPS, and Max throughput • RAID Reconfiguration Utilities • Online disk group expansion • Online RAID level migration • Online stripe size migration • Online simultaneous execution of the operations above • Online disk group defragmentation for free space consolidation • Online simultaneous disk group expansion and defragmentation • Online logical disk capacity expansion • Online logical disk capacity
Introduction • Online array recovery for logical disks, disk groups, and volumes • Storage Presentation • Support multiple storage presentations: simple, symmetric, and selective • Support dynamic LUN masking • Independently-selectable access control for each host and LUN • Independently-selectable CHS geometry and sector size for each LUN • Support host grouping management • Support up to 32 hosts, 16 host groups, and 32 storage groups • Support up 1024 LUNs and 128 LUNs per storage group • Hard Disk Man
Introduction • Management Interfaces • Local management via RS-232 port and LCD panel • Remote management via Ethernet and TCP/IP • Support network address settings by static, DHCP, and APIPA • Support web-based GUI via embedded web server (HTTP) • Support multiple languages and on-line help on web GUI • Web-based multiple RAID system viewer with auto system discovery • Embedded Command Line Interface (CLI) via RS232 port, SSH, and telnet • Host-side Command Line Interface (CLI) via FC/SAS/SCSI and TCP/IP
Introduction • Snapshot Functions (model-dependent) • Support copy-on-write compact snapshot • Instant online copy image creation and export • Instant online data restore/rollback from snapshot • Support multiple active snapshots for single LUN • Support read/writable snapshot • Support spare volume for overflow • Support online snapshot volume expansion • Support snapshot configuration roaming • Miscellaneous Supporting Functions • Support configurations download and restore • Support configurations savi
Introduction or definitions of parameters between GUI and CLI, you can study the GUI chapter to know how a CLI command works. • Chapter 5 (Advanced Functions) provides in-depth information about the advanced functions of the RAID system to enrich your knowledge and elaborate your management tasks. • Chapter 6 (TroubleShooting) provides extensive information about how you can help yourself when encoutering any troubles. • Appendices describe supporting information for your references.
Introduction logical disks can be put together to create volumes using striping, concatenation, or both. The JBOD disks, logical disks, and volumes, are virtual disks, which can be exported to host interfaces as SCSI logical units (LUN) and serve I/O access from the host systems. Below are more descriptions about each storage objects. • JBOD disk A JBOD (Just a Bunch Of Disks) disk is formed by single hard disk that can be accessed by hosts as a LUN exported by the controller.
Introduction • Virtual disk A virtual disk is an storage entity that can service I/O access from LUNs or from other virtual disks. It could be JBOD disk, logical disk, or volume. If a virtual disk is part of other virtual disk, then it cannot be exported to LUNs. • LUN mapping A LUN mapping is a set of mapping relationships between LUNs and virtual disks in the controller. Computer systems can access the LUNs presented by the controller after inquiring host ports of the controller. 1.
Introduction • RAIDGuard Central (chapter 5) RAIDGuard Central is a software suite that helps you to manage multiple RAID systems installed in multiple networks. It locates these systems by broadcasting and will be constantly monitoring them. It receives events from the systems, and stores all the events to single database. It also provides event notification by MSN messages. • Microsoft VDS (chapter 5) VDS is a standard of RAID management interface for Windows systems.
Introduction largely depend on the information you collect. It is advised to write down the information of users’ needs and environments as well as the configurations in your mind, which can be very helpful guidance through the all the lifetime of the RAID systems.
Introduction such that capacity overhead can be minimized while performance and reliability can still be guaranteed. You might need to pay attentions to a few options when doing the tasks above, like initialization modes, cache settings, alignment offset rebuilding mode, and etc. Please read the GUI chapter to know their meanings and choose the most appropriate settings, because they are directly or indirectly related to how well the RAID system can perform (see 2.6 RAID Management on page 2-22 and 2.7.
Introduction (see 2.9.5 Miscellaneous on page 2-71). You may also schedule periodic maintenance tasks to do disk scrubbing(see 2.7.9 Scrubbing on page 250) for defected sectors recovery or to do disk self-tests (see 2.7.11 Performing disk self test on page 2-51). Miscellaneous settings There are also minor settings that you might need to do, like checking UPS (see 2.9.4 UPS on page 2-70), time setup (see 2.10.4 System Time on page 2-76), changing password (strongly suggested) and etc.
Introduction Capacity resource reallocation If you’d like to add more disks for capacity expansion, you can use disk group expansion (see 2.7.1 Expanding disk groups on page 2-44). Resizing logical disks and volumes ( 2.7.4 Expanding the capacity of logical disks in a disk group on page 2-46 to 2.7.6 Expanding volumes on page 2-47) can also help you to transfer the unused capacity of a LUN to others that are desperate for more space without any impact to other LUNs.
Using the RAID GUI Chapter 2: Using the RAID GUI 2.1 Accessing the RAID GUI 1. Open a browser and enter the IP address in the address field. (The default IP address is 192.168.0.1. You can use the FW customization tool to set another IP address as the default.) The supported browsers are listed as below: • IE 6.x (Windows) • IE 7.x (Windows) • FireFox 1.x (Windows, Linux, and Mac) • Safari 1.x and 2.x (Mac) 2. The following webpage appears when the connection is made.
Using the RAID GUI 2. In the Add Language window, find the language you want to use, and click OK. 3. In the Language Preference window, select the language you want to use, and use the Move Up and Move Down buttons to move it up to the top of the list. Click OK. 4. Click OK again to confirm the settings. Note If the GUI does not support the selected language, the webpage will still appear in English. • Firefox language settings Here is an example of how to change the GUI language settings in Firefox. 1.
Using the RAID GUI 3. The following Languages dialog displays. To add a language, click Select a language to add..., choose the language, and click the Add button. Use the Move Up and Move Down buttons to arrange the languages in order of priority, and the Remove button if you need to remove a language. Click OK. Figure 2-3 Languages dialog (Firefox) 4. Click OK again to confirm the settings. 2.1.2 Multiple System Viewer The RAID GUI features a side button for a quick on-line system view.
Using the RAID GUI Figure 2-5 Opening the multiple system viewer Move the cursor to a system, and the following system information will appear: IP address, System name, Model name, Firmware version, and Status. Click on a system to open its GUI, and you can login to view the complete system information. If there are too many on-line systems displayed in the viewer at one time, you can use the arrow buttons to scroll up and down. Click the to refresh the viewer.
Using the RAID GUI 2.2 Monitor Mode RAID GUI monitors the status of your RAID controller(s) through your Ethernet connection. The RAID GUI window first displays the Monitor Mode. This mode is also the login to enter Config Mode. The GUI components shown are introduced in the following sections. Figure 2-6 Single controller GUI monitor mode At the front view panel, there are 16 or 24 HDD trays displayed in the redundant-controller system.
Using the RAID GUI There are four buttons at the top right of the page. See the following table for each button’s function. Button Description Switches between Monitor Mode and Config Mode. Switch Mode Logs out the user. Logout Opens the Help file. Help Displays the GUI version, firmware version, and boot code version. About Table 2-1 Buttons in monitor and config mode System name, controller name, firmware version, and boot code version information are also displayed at the bottom left of the page.
Using the RAID GUI Code Hard Disk Status D0-D7 D0-Dv Disk group (The redundant-controller system supports up to 32 DGs, which are encoding from D0 to Dv) L0-L7 Local spare G Global spare T Clone Table 2-2 Hard disk code Color Hard Disk Status Color Green Online Adding (flashing green) Purple Red Orange Blue Faulty Silver Conflict Gray Foreign Hard Disk Status Unknown Permanently removed Removed Empty Table 2-3 Hard disks tray color 2.2.
Using the RAID GUI Fan module (This icon will be shown when the fan is installed on the controller.) • Controller Fan BBM (This icon will be shown when the BBM control is on.) • State • Remaining Capacity • Voltage (V) • Temperature (ºC/ºF) • Non-critical Temperature (ºC/ºF)* • Critical Temperature (ºC/ºF)* UPS (This icon will be shown when the UPS control is on.
Using the RAID GUI 2.2.3 Rear side view On the rear side of the RAID system, you can see the fan modules, power supplies, host ports (fibre, SAS, SCSI or iSCSI), one Ethernet port, and SAS expansion port (for SAS expansion controller solution). Click on the components for detailed information.
Using the RAID GUI • For RAID system For Redundant and upgradable RAID system A A A Controller B Controller A C B B G G ispa4 (left)/ispa3/ispa2/ispa1 (right) ispb4 (left)/ispb3/ispb2/ispb1 (right) A A A Controller B Controller A C B B D D fcpa2 (left)/fcpa1 (right) fcpb2 (left)/fcpb1 (right) A A A Controller B Controller A C B E sasa2 (left)/sasa1 (right) E B sasb2 (left)/sasb1 (right) Figure 2-10 Rear side of the redundant RAID system 2-10
Using the RAID GUI A A A Controller A C B G B ispa4 (left)/ispa3/ispa2/ispa1 (right) A A A Controller A C B D B fcpa2 (left)/fcpa1 (right) A A A C Controller A B E B sasa2 (left)/sasa1 (right) Figure 2-11 Rear side of upgradable RAID system Component Detailed Information A Fan module • BP_FAN1 • BP_FAN2 • BP_FAN3 • BP_FAN4 B Power supply • POW1 • POW2 • POW3 Table 2-5 Components at the rear side of the system 2-11
Using the RAID GUI C Ethernet port • IP Address • Network Mask • Gateway • DNS Server • MAC Address D Fiber ports • FCP ID • WWN • Connection Mode • Date Rate • Hard Loop ID E SAS ports • SAS ID • SAS Address F SCSI ports • SCSI ID • Data Rate • Default SCSI ID G iSCSI ports • iSCSI ID • IP address • Network Mask • Gateway • MAC Address • Jumbo Frame • Link Status Table 2-5 Components at the rear side of the system 2.2.
Using the RAID GUI option is set to On (see 2.10.5 Security control on page 2-76), and the mail server has been configured in System Management > Network. Note You can use the FW customization tool to set a new password as the default. 2.3 SAS JBOD Enclosure Display (for SAS expansion controller only) The single controller RAID subsystem provides a SAS expansion port which allows users to connect a SAS JBOD.The single controller support 64 hard disks.
Using the RAID GUI 2.3.1 Rear side monitor of the SAS JBOD chassis On the rear side of the SAS JBOD chassis, there are three ports (for single SAS JBOD) or six ports (for redundant SAS JBOD) available for SAS JBOD expansion. See the port identifiers as shown in Figure 2-13.
Using the RAID GUI 2.3.2 SAS JBOD Installation with RAID subsystem • For single controller with single JBODs: Use the down and up stream ports to connect the RAID subsystem with up to three SAS JBODs. Figure 2-14 shows a serial construction for expanded JBOD disks. Connect the RAID subsystem’s SAS port to the up stream port of a SAS JBOD using a Mini SAS cable. For more expanded JBOD chassis, connect the down stream port on the previously connected SAS JBOD to the up stream port on the other SAS JBOD.
Using the RAID GUI • For redundant controller with redundant JBODs To ensure the system can continue its operation without any interruption in the event of any SAS JBOD failure, a loop construction is suggested. Figure 2-15 shows an example of the loop implementation with a redundant RAID system and SAS JBODs.
Using the RAID GUI 2.3.3 Monitor mode When SAS JBOD chassis are connected, the enclosure tabs will appear in the Monitor Mode (see Figure 216). Each tab view displays different information for each connected enclosure. Click the Enclosure 0 tab to view the information of the local RAID subsystem. Click the Enclosure 1, Enclosure 2, or Enclosure 3 tabs for a brief view of the connected SAS JBOD.
Using the RAID GUI 2.3.4 Information icons In Monitor Mode, the following information icons are displayed on the screen. When components are working normally, their icons are shown in green. When components fail to work, the icons are shown in red. Click on each icon for detailed information.
Using the RAID GUI 2.4 Config Mode To configure any settings under Config Mode, log in with admin and its password. The Overview screen displays as below. Figure 2-18 Overview screen The RAID GUI Config Mode provides the following configuration settings. Quick Setup Allows you to configure your array quickly. RAID Management Allows you to plan your array. Maintenance Utilities Allows you to perform maintenance tasks on your arrays.
Using the RAID GUI 2.5 Quick Setup 2.5.1 Performance profile The RAID GUI provides three performance profiles for you to apply the preset settings to the RAID configuration. This allows users to achieve the optimal performance for a specified application. When using a profile for the RAID configuration, any attempt to change the settings is rejected. See the following table for the values of each profile. Select Off if you want to configure the settings manually.
Using the RAID GUI 2.5.2 RAID setup To perform quick setup, all hard disks must be on-line and unused. Users can specify the RAID level, number of spare disks, and initiation method for an easy RAID configuration. See the following for details of each option. HDD Information This shows the number and the minimum size of hard disks. RAID Level RAID 0 / RAID 3 / RAID 5 / RAID 6 / RAID 10 / RAID 30 / RAID 50 / RAID 60 Spare Disks Select the required number of global spare disks.
Using the RAID GUI 2.6 RAID Management 2.6.1 Hard disks This feature allows you to add or remove hard disks and set any online disk as global spare drive. The hard disk information included is listed as follows. Table 2-10 Hard disk information Category Display HDD ID Hard disk identifier Model Hard disk model name Capacity (GB) Hard disk capacity State On-line, Foreign, Conflict, Removed, PRemoved, Faulty, Initializing, Unknown.
Using the RAID GUI • Buttons Add: To add hard disks, select a hard disk and click this button. Remove: To remove hard disks, select a hard disk and click this button. To remove hard disks permanently, check the Permanent remove box when removing them. Modify: Select a hard disk and click this button to enter the settings screen to enable or disable the disk cache and the disk identify function. Note 1. When the selected hard disk is not in the on-line state, the Disk Cache field will not be displayed. 2.
Using the RAID GUI 2.6.2 JBOD This feature allows you to create, delete, and modify your JBOD settings. • Create JBOD disks Click Create to add a new JBOD disk, where up to a maximum of 16 JBOD disks can be created. Specify the following options for the configuration. JBOD ID Select a JBOD ID from the drop-down menu. Name Use the system default name as jbdx. ‘x’ is the JBOD identifier. OR Uncheck the ‘Use system default name’ box and enter the name in the Name field.
Using the RAID GUI Write Sorting This option enables or disables the sorting in the write cache. To improve writing performance, it is recommended to turn this option on for random access. This option is available only if the write cache is on. Read Ahead Policy Always: The controller performs pre-fetching data for every read command from hosts. Adaptive: The controller performs pre-fetching only for host read commands that are detected as sequential reads. The detection is done by read logs.
Using the RAID GUI 2.6.3 Disk groups This feature allows you to create, delete, and modify your disk group settings. • Create disk groups Click Create to add a new disk group, where up to a maximum of 8 (single controller) / 32 (redundant controller model) disk groups can be created. Specify the following options for configuration. DG ID Select a DG ID from the drop-down menu. Name Use the system default name as dgx. ‘x’ is the DG identifier.
Using the RAID GUI • Delete disk groups Select the disk group(s) you want to delete and click Delete. • Modify disk groups To modify a setting, select a DG and click Modify. Specify the following options for configuration. Name Type a name associated for the DG ID. Spare Disks Assign disks to be used as local spares. Disk Cache This option enables or disables the on-disk cache of hard disks in a disk group.
Using the RAID GUI Initialization Task Priority Low / Medium / High Utilities Task Priority Low / Medium / High This option sets the priority of the background tasks for utilities of disk groups. These include RAID reconfiguration utilities and data integrity maintenance utilities. This option sets the priority of the background tasks for logical disk initialization of disk groups. Note 1. Progress rates increase in proportion to priority (i.e. A high priority task runs faster than a low priority one.
Using the RAID GUI Name Use the system default name as dgxldy. ‘x’ is the DG identifier and ‘y’ is the LD identifier. OR Uncheck the ‘Use system default name’ box and enter the name in the Name field. The maximum name length is 63 bytes. RAID Level Select a RAID level for the logical disk. Different logical disks in a disk group can have different RAID levels. However, when NRAID is selected, there must be no non-NRAID logical disks in the same disk group.
Using the RAID GUI Alignment Offset (sector) Set the alignment offset for the logical disk starting sector to enhance the controller’s performance. For Windows OS, it is suggested to set the alignment offset at sector 63. Note Make sure the disk group to be created for a new logical disk is in OPTIMAL or LD_INIT state, otherwise the new logical disk will not be created. • Delete logical disks Select the logical disk(s) you want to delete and click Delete.
Using the RAID GUI Read Ahead Multiplier This option specifies the read ahead multiplier for the Always and Adaptive read ahead policies. Select how much additional sequential data will be pre-fetched. The default value is 8. Read Logs This option specifies the number of concurrent sequential-read streams for the Adaptive read ahead policy, and the range is between 1 and 128. The default value is 32. LD Read Algorithm This option is only available for logical disks with parity-based RAID level, i.e.
Using the RAID GUI 2.6.5 Volumes This feature allows you to create, delete, and modify your volume settings. RAID 30/50/60 are supported by creating striping volumes over RAID 3/5/6 logical disks. • Create volumes Click Create to add a new volume, where up to a maximum of 32 volumes can be created. Specify the following options for the configuration. VOL ID Select a VOL ID from the drop-down menu. Name Use the system default name as volx. ‘x’ is the VOL identifier.
Using the RAID GUI • Delete volumes Select the volume(s) you want to delete and click Delete. To delete all LUNs of volx, check the ‘Force to delete LUN mapping(s)’ box. All access to the volume will be stopped. • Modify volumes To modify a setting, select a volume and click Modify. Specify the following options for configuration. Name Type a name for the volume ID. Preferred Controller This option is only available when the redundantcontroller system is in use.
Using the RAID GUI • Create volume (VOL) snapshot volume pair Instead of creating volume pairs in the Snapshot Volumes page, you can directly create volume pair to a specified volume by clicking the S.VOL button. Specify a virtual disk as the secondary volume from the SV ID drop-down menu, then click the Apply button to confirm. • Detailed volume information Click to display a complete list of volume information. You will see the following details.
Using the RAID GUI • Modify snapshot volume pairs To modify a setting, select a snapshot volume and click Modify. Specify the following options for configuration. Overflow Alert (%) Specify an overflow alert threshold for a secondary volume. The range is from 50 to 99. When the allocated space exceeds the specified threshold, an alert notification is generated. If not specified, the default threshold is 80.
Using the RAID GUI • Create Spare COW volumes (S.COW.VOL) Click Add to add a new spare COW volume, where up to a maximum of 128 volume pairs can be created. Specify the following options for the configuration. COW VOL ID From the drop-down menu, specify an LD as the spare COW volume. • Delete snapshot volume pairs Select the spare COW volume you want to delete and click Remove.
Using the RAID GUI • Detailed snapshot volume information Click to display a complete list of snapshot volume information. You will see the following details. • VOL ID • UUID • Allocated Space on SV (MB) 2.6.7 Storage provisioning The RAID GUI provides three storage provision methods; simple, symmetric, and selective. Whenever you change the method, the following confirmation message is displayed.
Using the RAID GUI HTP ID Each FC/SAS/SCSI port has a unique ID, which is determined according to the physical location of the port on the controller. Select one from the drop-down menu. For iSCSI port, at least an iSCSI target node is necessary for LUN pressented. SCSI ID (For SCSI port) Select a SCSI ID from the drop-down menu. A maximum of 16 SCSI IDs can be added to the controller. LUN ID Select a LUN ID from the drop-down menu, where up to a maximum of 128 LUNs can be selected.
Using the RAID GUI In this case, the controller’s performance is highly elevated. You need not consider different host ports because the bindings between hosts and storage groups are applied to all host ports. HOST FCP1 (Port1) FCP2 (Port2) LUN0 (DG0LD0) As the illustration shows, LUNs are assigned according to each host’s WWPN (World Wide Port Name). Therefore, you need to set the host WWPN first. Each host can recognize LUNs as paths to virtual disks, instead of individual disks.
Using the RAID GUI Remove hosts Select the host(s) you want to delete and click Remove. Check the ‘Only remove from host group’ box if you want to remove the host(s) from the host group only. Modify hosts/host group Select a host you want to change for its host name, host group ID, or host group name, and click Modify to enter the settings screen. Add LUNs in Host Group After setting the host(s), click Back to return to the symmetric storage main screen. Then click Add to add LUNs in the HG(s).
Using the RAID GUI connectivity between host and storage resources exported by the controller. As the illustration shows, the HG (Host Group) can be a host or a group of hosts that share the same access control settings in the controller. SG represents the LUNs as a storage group. Bind the host/ host group and storage group to the same host port.
Using the RAID GUI Remove hosts Select the host(s) you want to delete and click Remove. Check the ‘Only remove from host group’ box if you want to remove the host(s) from the host group only. Modify hosts/host groups Select a host you want to change for its host name, host group ID, or host group name, and click Modify to enter the settings screen. Add LUNs in storage group In the selective storage main screen, click SG > Add. SG ID Select a SG ID from the drop-down menu.
Using the RAID GUI Remove LUNs in storage group Select the LUN(s) you want to delete and click Remove. To remove all LUNs of a virtual disk from all storage groups, check the ‘Remove mapping virtual disk from all storage group’ box. Modify LUN/storage group Select a LUN/ storage group you want to change for its mask status, access right, or storage group name, and click Modify to enter the settings screen.
Using the RAID GUI 3. Click Apply to review the current settings. 4. Click Confirm. The task is created. Note 1. The disk group to be expanded must be in the optimal state. 2. You may only select to increase the number of hard disks but not to change the disk group setting. 3. Once confirmed, please wait until the expansion process is complete. Do not change or select any functions during the expansion process. 2.7.
Using the RAID GUI Expanding HDDs The controller performs disk group expansion with specified hard disks. RAID Level The controller performs the specified RAID level migration. The feasibility of migration is limited to the original and final RAID level and the number of member disks in the disk group. The following table defines the rules of the number disks during the RAID migration.
Using the RAID GUI Note 1. The new capacity must be bigger than the current capacity. 2. The sum of increased capacity of all logical disks on the disk group must be less than or equal to the sum of capacity of all selected free chunks. Schedule Immediately: The task will start immediately. Once: The task will start on the specified date and time. Starting Free Chunk / Ending Free Chunk This option specifies the start and end of free chunks to be used for the expansion.
Using the RAID GUI 2.7.6 Expanding volumes To expand the capacity of a volume, do the following: 1. Select Maintenance Utilities > VOL Reconfiguration from the main menu. 2. Select Expand and specify the following options for a VOL expansion task. The expansion volume is formed by concatenating new logical disks. VOL ID Select a VOL ID from the drop-down menu for expansion. LD Level Select a RAID level to filter a list of expanding LDs.
Using the RAID GUI Note 1. The volume must be in optimal state. 2. There must be at least two concatenating volume units in a volume. 3. All selected volume units must be the last concatenating volume units in the volume. 3. Click Apply to view the current settings. 4. Click Confirm to continue the shrink. 2.7.
Using the RAID GUI Note 1. If there is disk scrubbing task or parity regeneration task in the disk group of the source disk, the task is aborted and cloning is started. 2. If the disk group of the source disk contains faulty disks, cloning is suspended until the disk group completely rebuilds its disks. 3. Click Apply. The task will start according to the specified time. To cancel hard disk cloning, do the following: 1. Select the task(s) and click Stop to abort disk cloning.
Using the RAID GUI 3. Click Apply. The task will start according to the specified time. Note 1. The hard disk must not be a member disk of a disk group. 2. The disk group and logical disk(s) for scrubbing must be in the optimal state. 3. The scrubbing task will be aborted if the disk group enters degraded mode, starts rebuilding disk, or starts disk cloning. 4. If the disk group of the source disk contains faulty disks, scrubbing is aborted until the disk group completely rebuilds its disks.
Using the RAID GUI this function, make sure the SMART warning has been turned on. (See 2.8.1 Hard disks on page 2-57) Follow the steps below to start a disk self test: 1. Select Maintenance Utilities > Disk Self Test from the main menu. 2. Select the hard disks you want to perform the disk self test and click DST. Specify the following options. Schedule Immediately: The task will start immediately. Once: The task will start on the specified date and time.
Using the RAID GUI 2.7.12 Array roaming Array roaming will be activated when hard disks are moved from one slot to another or from one controller to a new controller. This ensures that the new controller can be working at all times. You can determine the way of array roaming through the Auto Array Roaming Control (See 2.7.16 Miscellaneous on page 2-55).
Using the RAID GUI • BANISH: The partition is lost (the member disk is removed or faulty) and it results in a degraded logical disk. The data on the banish partition will be out of sync with data on other partitions. The data on the banish partition can’t be used after recovery. • REBUILD: The member disk of the partition has been added to the logical disk, and the partition is rebuilding the data.
Using the RAID GUI • No reconfiguration tasks are performed by the faulty logical disk. • Start a recovery When there are any hard disk conflicts, there might be faulty disk groups, logical disks, or volumes on your controller. You can perform DG recovery to restore lost member disks to a disk group. The faulty logical disks on the disk group are recovered automatically when the disk group is recovered. To perform a disk group recovery, do the following: 1.
Using the RAID GUI 2.7.15 Cache Configurations In this section, you can configure the following settings to the controller. The settings of Cache Unit Size, Auto Array Roaming Control, and Write Log Control will take effect after you restart the RAID subsystem. Cache Unit Size (KB): 4 / 8/ 16 / 32 / 64 / 128 (default) The cache unit size must be smaller or equal to the minimum stripe size of existing logical disks.
Using the RAID GUI Auto Array Roaming Control: On / Off (default) On: Enable imported foreign hard disks when the controller is started. Foreign hard disk configurations are also restored. Off: Disable imported foreign hard disks when the controller is started. Note Hard disks with configurations that conflict with controller configurations are not imported and enter conflict state.
Using the RAID GUI 2.8 Hardware Configurations 2.8.1 Hard disks In this section, you can configure the following settings to all hard disks. Utilities Task Priority: Low (default) / Medium / High This option determines the priority of the background tasks for utilities of all hard disks not belonging to any disk group, such as scrubbing and cloning. SMART Warning: On / Off (default) This option is only for SMART function supported hard disks. The SMART function serves as a device status monitor.
Using the RAID GUI Figure 2-23 Specify the percentage for Bad Block Alert Note 1. Latter percentages must be larger than the former percentages. 2. Percentages must be integers between 1 and 100. Bad Block Clone: On / Off (default) This option enables or disables disk cloning for bad block reallocation. After selecting On, a blank field is displayed for you to specify the percentage of reserved bad block reallocation space. When the specified space is reached, disk cloning will be started.
Using the RAID GUI Caution The boot-up delay time must be longer than the disk access delay time plus 5 seconds. 2.8.2 Ports 2.8.2.1 FC / SAS / SCSI ports This shows information about FC/SAS/SCSI ports. For FC ports including Controller Failover Mode (for redundant controller only), each port’s ID, name, WWN, Hard loop ID, connection mode (private loop, public loop, or point-to-point), and data rate. For SAS ports including each port’s ID, name and SAS address.
Using the RAID GUI Connection Mode Auto: The controller will determine the connection mode automatically. Arbitration loop: This is a link that connects all the storages with the host, which enables data transferring. Fabric: This is a point to point connection mode without a switch. Default SCSI ID (For SCSI port) Select a fixed SCSI ID for each SCSI port from the drop-down menu. The ID range is from 0 to 15.
Using the RAID GUI 2.8.2.2 iSCSI ports This shows information about iSCSI ports, including Assignment (DHCP/ Static), IP address, Subnet Mask, Gateway, Jumbo, MAC address, Aggregation and Link Status. Note • The default iSCSI listening port is 3260. • ispa1~4 belong to Controller A; ispb1~4 belong to Controller B (only appear in redundant controller model). In addition, following buttons are provided to configure iSCSI ports. Entity Configure iSCSI Entity for IQN header usage. Sess.
Using the RAID GUI as below. 2.8.2.2.3 Target-iSCSI Target Node iSCSI storage device been seen as a “iSCSI Target” and the host is called “iSCSI Initiator”. At least an iSCSI target node MUST be created for getting communication with host iSCSI HBA or software iSCSI initiator. Click Target icon to open the configurations window and click Back if you want return to the page of iSCSI ports. • Create an iSCSI target 1.
Using the RAID GUI CHAP User name and Secret (password) at both iSCSI initiator and target side, or the connection fail. Click CHAP User icon to open the configurations window and click Back if you want return to the page of iSCSI ports. • Create a CHAP User 1. Click Add to open the configurations window, specify the following CHAP User Name Specifies the CHAP User name. The maximum length of the name is 16. CHAP Secret Specifies the CHAP Secret.
Using the RAID GUI 2. After setting done, click Apply to make it available Note • Support Primary and Secondary iSNS server. Delete a CHAP User • Select the iSNS server you want to delete and click Remove. 2.8.2.2.6 Aggregate, RM-Aggr The Aggregation function is following 802.3ad specification, which supports combining multiple physical iSCSI links into one logical link. That is, increasing bandwidth, path redundancy and avoids single points of failure. • Create Aggregation port 1.
Using the RAID GUI 2.8.3 COM port In this section, you can configure the terminal settings on the COM port as instructed below. Select Terminal port, and click Modify to open the configurations window. • Terminal port The terminal port serves as one of the mechanisms to manage the controller on-site. The configurations for the terminal ports are baud rate, stop bit, data bit, parity check, and flow control.
Using the RAID GUI Mail Retry Period (minute): 10 (default) Specify the period of time in minutes to retry sending event notification mail. The range is from 10 to 60. Mail Delay Time (second): 10 (default) Specify the delay time in seconds to send out multiple events in one mail. This helps to reduce the number of mails. The range is from 5 to 60. Add Event Receivers You can add a maximum of three mail recipients.
Using the RAID GUI Set up the community name as the authentication string between the SNMP Agent and SNMP applications. Add SNMP Event Receivers Servers You can have up to three SNMP servers to receive SNMP event notification packets. Click Add to choose a Server ID, and set its SNMP server address, port, and the corresponding protocol version, community name, and severity level. Server ID: 0 / 1 / 2 Select a server ID from the drop-down menu.
Using the RAID GUI Send a Test SNMP Trap Select the SNMP server(s) to which a test SNMP trap will be sent, and click SNMP. The test SNMP trap will contain message “This trap is for testing purpose only.” Note In a redundant-controller system, both controllers send out SNMP event notification packets for one event. • SNMP MIB Definition A Management Information Base (MIB) is a collection of information that is organized hierarchically.MIBs are accessed using a networkmanagement protocol such as SNMP.
Using the RAID GUI 2.9.3 Event logs When the state of a logical or physical component in the controller changes, such as failure of hard disks or completion of a background task, an event occurs. Events are classified into different severity levels. You can view the events according to the different categories. Specify the severity level at the top of the page. Events are listed in the event log from newer to older. The events contain the following information: 1. Sequence number 2.
Using the RAID GUI Click Close to close the window. Note The event log file stores details of controller activity. In the case of malfunction, this data can be analysed by the user to determine the cause(s). Record Event Log Click Configure and specify the Lowest severity of events option for the events you want to record on NVRAM. The events with severity levels higher than the specified one will be recorded. The default severity level is info, which means events of all severity levels will be recorded.
Using the RAID GUI Low Battery Threshold (seconds) Change Restart Percentage 120 / 300 / 480 / 660 / 840 / 1020 / 1200 / 1380 This option notifies the user that the UPS battery is low, with the specified remaining seconds. 0 / 15 / 30 / 45 / 60 / 75 / 90 After the AC power returns, the UPS does not power on until the battery charge reaches the specified capacity. 3. Click Apply to confirm the current settings. Note 1. The values from each drop-down menu may be different according to the UPS connected.
Using the RAID GUI When a path failover occurs, the controller will send out warning events to notify users after the specified delay time (in minutes). The range is between 0 and 60. To make the settings effective, click Apply. 2.10 System Management 2.10.1 Restoring to factory settings To clear the NVRAM or hard disk configurations, do the following: 1. Select the “Erase configurations on NVRAM” or the “Erase configurations on HDD(s)” option to clear all configurations made on NVRAM or hard disks. 2.
Using the RAID GUI Read the NVRAM configuration on hard disks and save to NVRAM Specify this option to read the NVRAM configuration data on the specified hard disk and save to NVRAM. Figure 2-27 Options in the Configurations screen-2 (System Management menu) Note This option will be available when on-line hard disks exist. Therefore, only on-line hard disks will be displayed in the list box. Get main configurations Specify this option to save the NVRAM configuration data to a file.
Using the RAID GUI Upload a file and store it as the controller’s main configurations Specify this option to upload a configuration file and store it on NVRAM. Figure 2-29 Options in the Configurations screen-4 (System Management menu) 2.10.3 Setting up the network The network interface serves as one of the methods to manage the controller. There are two network types, static and DHCP. To set up the network, do the following: 1. Select System Management > Network from the main menu. 2.
Using the RAID GUI Configure or Modify SMTP server Select a server you want to configure and click Modify. The configurations window opens. Enter the information for the following options. Server Address Set the SMTP server address. Port Enter the SMTP port for the outgoing mails. Check with your ISP provider for the port number to use. By default, the port is set to 0. SSL Setting Enable or disable the SMTP server to use secure connection.
Using the RAID GUI • If you select the NTP mode, specify the IP address or the domain name of the NTP server. The NTP server automatically synchronizes the controller clock at 23:59 every day. 3. Click Apply, and the settings are effective immediately. • Setting up the Time-Zone 1. Select System Management > Time from the main menu. 2. From the Time-Zone Mode drop-down menu, select location of country. 3. From the DST(Daylight saving time) Status Mode drop-down menu, select On/Off(default). 4.
Using the RAID GUI To disable forced SSL encryption, select either On or Off from the SSL Forced drop-down menu. When all the settings are complete, click Apply to make them effective immediately. 2.10.6 System information To view system information and controller information, select System Management > System Information from the main menu. You will see the following details.
Using the RAID GUI 2.10.8 Update system firmware, boot code and external enclosure F/W To update the system’s firmware, boot code and external enclosure firmware, do the following: 1. Select System Management > Firmware Update from the main menu. 2. Specify the firmware type; the current firmware, boot code version and external enclosure amount will be also displayed on-screen. • For firmware update, click on the System firmware radio button. • For boot code update, click on the Boot Code radio button.
Using the RAID GUI 2.10.9 Restart or halt the controller When you want to turn the RAID system off, you must go through a regular shutdown procedure. Always follow the steps below to instruct the controller restart or halt before powering off the RAID system. 1. Select System Management > Restart/Halt from the main menu. 2. (For redundant-controller system only) From the Controller ID dropdown menu, specify whether you want to restart or halt ctla, ctlb, or Both Controllers. 3.
Using the RAID GUI Note Faster GUI refresh rates may degrade the performance of controller. To make the settings effective, click Apply. 2.11 Performance Management 2.11.1 Hard disks This feature allows you to enable, disable, or reset disk IO logging for all hard disks. When hard disk IO logging is enabled, the following data will be displayed. You can press the Reset button to clear all statistics except outstanding IO and disk utilization to zero.
Using the RAID GUI 2.11.2 Cache This feature allows you to enable, disable, or reset buffer cache IO logging. When cache IO logging is enabled, select the cache type (volume, logical disk, or JBOD disk) to be displayed from the drop-down menu. The following IO statistics will be displayed. You can press the Reset button to clear all statistics except dirty buffer and clean buffer to zero.
Using the RAID GUI Response Time (ms) Outstanding IO The average command response time since the disk was powered on The maximum command response time since the disk was powered on The number of current outstanding IO Note When the redundant-controller system is in use, all the LUN statistics information in both controllers (Controller A and B) will be displayed on the screen. Click to see a complete list of LUN information.
Using the RAID GUI Click to see a complete list of storage port information. You will see the following details. • HTP ID • TX/RX Word • Primitives Sequence Protocol Error Count • LIP Count • NOS Count • Error Frame • Dumped Frame • Second since last reset • TX/RX Frame Note The information displayed is dependent on the installed FC chip. Some chips do not support the provision of all storage port information.
Using the LCD Consolel Chapter 3: Using the LCD Console 3.1 Starting LCD Manipulation The RAID system has a front LCD panel which supports a quick configuration and RAID monitoring. You can use the four buttons on the LCD panel to manipulate the LCD configuration utility. Each state and display sequence is illustrated as below: 1. Boot up info system fail system ready 3. Error info 4. Status info Empty Press ENT (Clear) emergent events 2.
Using the LCD Console 3.2 LCD Messages 3.2.1 LCD layout Line 1 {INFO1} Line 2 {INFO2/DISK} * Where: ∗ : Heart Plus. The heart plus icon flashes when the controller is working normally. When not flashing, this indicates a controller failure has occurred. INFO1: Information (including status info, emergent info, and background task messages) display area at line 1, the maximum string length is 15. INFO2: Information display area at line 2, the maximum string length is 16.
Using the LCD Consolel 3.2.2 Status info When the system is ready, the system information and background task messages are displayed sequentially every two seconds. See the button functions as below. UP/DOWN: Scroll up/down the message. ESC: Clear the message and enter the menu (password may be required). ENT: Enter the password (if required). UP+DOWN: Clear all status info and restart to display all the status messages. Line 1 shows messages, and Line 2 shows the disk status.
Using the LCD Console 3.2.3 Emergent info When an emergent event occurs, you can read the message on the LCD. This state is held until every event is confirmed. See the function buttons as below. UP/DOWN: Scroll up/down the message. ENT: Confirm (clear) the message. (not supported in current version.) ESC: Enter the menu (password may be required). Line 1 shows messages, and Line 2 shows the disk status.
Using the LCD Consolel Background Task Message Format LD Expand xx.yy Exp xx.x% LD Migrate xx.yy Mig xx.x% DG Defragment dgx Defrg xx.x% DG Expanding dgx Exp xx.x% Disk Cloning Clone zz xx.x% Disk Initializing xx.yy Ini xx.x% Disk Rebuilding Reb xx xx.x% Disk (HDD) Scrubbing Scrub zz xx.x% LD Scrubbing xx.yy Scr xx.x% DG Scrubbing dgx Scr xx.x% Regenerate LD Parity xx.yy Par xx.x% Regenerate DG Parity dgx Par xx.x% Table 3-3 List of background task messages 3.2.
Using the LCD Console 3.3 Menu 3.3.1 Menu Tree Use the UP or DOWN arrow buttons to scroll through the menu. Press the ENT button to enter the selected setting. To exit the menu, press ESC. The menu tree hierarchy is as shown below: Level 0 Level 1 Level 2 Level 3 Quick Setup RAID Level Spare Disk # Init.
Using the LCD Consolel 3.3.3 Network Settings In Ethernet Setup menu, users can view the network status and configure the server settings. Use the UP and DOWN buttons to scroll through the following items, and press the ENT button to select. Select CTL ID (For redundant-controller system only) Selects the controller you want to configure. Status Displays the connection status.
Using the LCD Console 3.3.5 System Settings In the System Setup menu, users are allowed to change the password settings, save or restore the configurations to NVRAM, reboot and power off the system. See the following table for details of each option. Password Passwd ENABLE: YES (default) / NO Enable or disable the password check when logging in menu. Change Passwd Key in the new password. The maximum length of password is eight characters.
Using the CLI Commands Chapter 4: Using the CLI Commands 4.1 Overview The Command Line Interface (CLI) is a set of commands which allows users to configure or monitor the RAID system by entering lines of text through a variety of the terminal consoles. The Figure 4-1 depicts how the CLI can be accessed: Figure 4-1 Interfaces to Access CLI With the embedded CLI, you can get full-function management capabilities without the need to install any software on your hosts.
Using the CLI Commands • Hard disk: hddx • JBOD disk: jbdx • Disk group: dgx • Logical disk: dgxldy • Volume: volx • Host: hostx • Storage group: sgx • Host group: hgx • Logical unit: lunx • Fiber port: fcpx • Serial SCSI port: sasx • Controller: ctlx • Management network port: ethx • Enclosure: encx Options Options are expressed in the form of [-x ... ], where -x is the identifier of the option. Selectable arguments When more than one value can be used in an argument, they are listed with “/” in between.
Using the CLI Commands Command hddremove Synopsis hddremove hddx hddy ...[-p] Remove one or more hard disks. To gain control over the Description removed hard disks, users can use hddadd to add the hard disks. The hard disks being removed will be managed again when the controller restarts. Parameters [-p]: permanent remove Command hddlist Synopsis hddlist hddx/all [-h] Description List the status of one or all hard disks. Parameters [-h]: show hardware status 4.2.
Using the CLI Commands 4.2.3 Disk groups Command dgcreate Synopsis dgcreate dgi hddx hddy ... [-n name] [-i par/seq] [-z] [-s hddz,hdda, ...] [-t capacity] Description Create a disk group with member disks. [-n name]: the name of a disk group Parameters [-i par/seq]: logical disk initialization mode (parallel or sequential) [-z]: write-zero immediately [-s hddz,hdda, ...
Using the CLI Commands Command dgrebseq Synopsis dgrebseq dgi par/seq/pri [-l ldx,ldy, ...] Description Set rebuild mode of a disk group. Parameters par/seq/pri: parallel, sequential, or priority [-l ldx,ldy, ...]: priority of logical disks to rebuild Command globalspare Synopsis globalspare add/remove hddx hddy ... Description Add or remove one or more hard disks as global spare disks. Command autospare Synopsis autospare [on/off] Description Review or set the auto spare settings.
Using the CLI Commands Command lddelete Synopsis lddelete dgxldy [-f] Description Delete a logical disk. Parameters [-f]: force to delete LUN mapping Command ldname Synopsis ldname dgxldy name Description Name a logical disk. Command ldlist Synopsis ldlist dgxldy/dgx/all Description List the status of one logical disk, all logical disks on a disk group, or al logical disks on the controller. 4.2.
Using the CLI Commands 4.2.7 Volumes Command volcreate Synopsis volcreate volx dgxldy dgildj ...[-s stripesize] [-o sector] [-n name] [-c ctlx] Description Create a volume. [-s stripesize]: stripe size [-o sector]: alignment offset Parameters [-n name]: the name of a volume [-c ctlx] (for redundant controller only): the preferred controller of a volume Command voldelete Synopsis voldelete volx [-f] Description Delete a volume.
Using the CLI Commands Command cachepflush Synopsis cachepflush [periodsec] Description Review or set the current cache flush period. Parameters [periodsec]: the cache flush period Command cacheunit Synopsis cacheunit [4kb/8kb/16kb/32kb/64kb/128kb] Description Review or set the cache unit size.
Using the CLI Commands 4.3 RAID Maintenance Utilities 4.3.1 RAID attributes reconfiguration utilities Command dgexpand Synopsis dgexpand dgi [-d] hddx hddy ... Description Expand a disk group by adding one or more disks. Parameters [-d]: defragment during expanding Command ldmigrate Synopsis ldmigrate dgxldy [-s newstripesize] [-r newraidlevel] [-d] [-l hddx,hddy,...] Description Perform RAID level and/or stripe size migration for a logical disk on a disk group.
Using the CLI Commands Command volshrink Synopsis volshrink volx Description Shrink the capacity of a volume by removing the concatenating logical disks. 4.3.2 Data integrity maintenance utilities Command hddclone Synopsis hddclone hddx hddy [-a] Description Perform disk cloning (clone from hddx to hddy). Parameters [-a]: automatic resume Command hddclonestop Synopsis hddclonestop hddx Description Stop disk cloning.
Using the CLI Commands 4.3.3 Task priority control Command hddutilpri Synopsis hddutilpri [priority] Description Show or set the utilities task priority of non-DG hard disks. Parameters [priority]: low, medium, or high Command dgrebpri Synopsis dgrebpri dgx priority Description Set the rebuild task priority of a disk group. Parameters priority: low, medium, or high Command dginitpri Synopsis dginitpri dgx priority Description Set the initialization task priority of a disk group.
Using the CLI Commands Command schedulelist Synopsis schedulelist command/all Description List one or all types of scheduled commands. 4.3.5 On-going task monitoring Command tasklist Synopsis tasklist command/all Description List one or all types of background tasks. Command tasknotify Synopsis tasknotify on/off [-p percentage] Description Enable or disable the event notification of the background task completion. Parameters [-p percentage]: completion percentage to notify 4.3.
Using the CLI Commands Command volimport Synopsis volimport [-f][-t volx] dgxldy dgildj ... Description import a volume from logical disks specified. Parameters [-f]: force to import a faulty volume [-t volx]: target volume Command volimportlist Synopsis volimportlist Description List volume configurations on all or specified logical disks. 4.3.7 Array recovery utilities Command dgrecover Synopsis dgrecover dgx hddx hddy ... [-f member_id] Description Recover a faulty disk group.
Using the CLI Commands Command hostname Synopsis hostname hostx name Description Name a host. Command hostlist Synopsis hostlist all/hostx Description List all hosts or one host. 4.4.2 Host groups Command hgaddhost Synopsis hgaddhost hgx hostx hosty ... Description Add hosts to a host group. Command hgremovehost Synopsis hgremovehost hgx hostx hosty ... Description Remove hosts from a host group. Command hgname Synopsis hgname hgx name Description Name a host group.
Using the CLI Commands 4-15 Command sgremovelun Synopsis sgremovelun sgx/fcpx/sasx/scpx luny/all Description Remove one or all LUNs in a storage group or a default storage group. Command sgremovedisk Synopsis sgremovedisk sgx/fcpx/sasx/scpx/all jbdy/dgyldz/voly/ vvoly Description Remove LUNs of a virtual disk from one storage groups, a default storage group, or all storage groups.
Using the CLI Commands 4.4.4 Presentation planning Command sgsetmethod Synopsis sgsetmethod sim/sym/sel [-a on/off] Description Select storage presentation method. Parameters sim/sym/sel: simple, symmetric-LUN, or selective storage presentation by default, the method is sim. [-a on/off]: enable or disable automatic LUN mapping Command sgmgmtdevice Synopsis sgmgmtdevice on/off [-l lunx] Description Enable or disable management device support of in-band API.
Using the CLI Commands Command Synopsis htpremovelun htpremovelun fcpx/sasx luny/all htpremovelun scpx idx/idxluny/all Description Remove one or all LUNs in a host port. Command htpremovedisk Synopsis htpremovedisk fcpx/sasx/scpx/all jbdy/dgyldz/voly/vvoly Description Remove all LUNs of a virtual disk from one or all host ports. Command htplistlun Synopsis htplistlun fcpx/sasx/scpx/all Description List LUN information in one or all host ports. 4.4.
Using the CLI Commands 4.5 Hardware Configurations and Utilities 4.5.1 Generic hard disk Command hddst Synopsis hdddst short/extended all/hddx hddy hddz … Description Perform short or extended disk self test (DST). Command hdddststop Synopsis hdddststop all/hddx hddy hddz … Description Stop DST immediately. Command hdddstlist Synopsis hdddstlist all/hddx hddy hddz … Description List disk self test information and status.
Using the CLI Commands Command hddbbrclone Synopsis hddbbrclone on/off [-p percentage] Description Enable or disable disk cloning for bad block reallocation. Parameters [-p percentage]: thresholds to start cloning Command hddbbrretry Synopsis hddbbrretry on/off Description Enable or disable retrying IO in bad block reallocation.
Using the CLI Commands Command hddqueue Synopsis hddqueue on/off Description Enable or disable the IO queuing of hard disks. Command hdddelayaccess Synopsis hdddelayaccess [-b] xxsec Description Specify the delay time before the controller tries to access the hard disks after power-on. Parameters [-b]: boot-up delay access time Command hddverify Synopsis hddverify on/off Description Enable or disable the write commands for initialization or rebuilding data on logical disks.
Using the CLI Commands Command scprate Synopsis scprate scpx/all async/fast/fastwide/ultra/ultrawide/ultra2/ ultra2wide/ultra3/ultra320 Description You can sets the preferred data rate of a SCSI port (scpx) or all SCSI ports (all), as Asynchrous SCSI (async), Fast SCSI (fast), Fast-Wide SCSI (fastwide), Ultra SCSI(ultra), Ultra Wide SCSI (ultrawide), Ultra2 SCSI (ultra2), Ultra2 Wide SCSI(ultra2wide), Ultra3 SCSI (ultra3), or Ultra-320 SCSI (ultra320),The default is ultra320.
Using the CLI Commands Command fcpwwnn Synopsis fcpwwnn identical/distinct Description Set the World-Wide Node Name of FC port to be identical or distinct. Without option, this command shows the current setting. Command fcplisthost Synopsis fcplisthost fcpx/all Description List the detected hosts of an FC port or all FC ports. Command fcplistusrconf Synopsis fcplistusrconf fcpx/all Description List the user’s configurations of an FC port or all FC ports.
Using the CLI Commands Command smtpconfig Synopsis smtpconfig set primary/secondary server sender [-p password] [-n name] smtpconfig reset primary/secondary Description Configure or clear the primary or secondary SMTP servers.
Using the CLI Commands Command ethlist Synopsis ethlist Displays the control setting of all management network interface ports, including the following information: • TELNET service status: on/off • SSH service status: on/off Description • Web service status: on/off • Out-band API status: on/off • Out-band API with SSL status: on/off • Broadcast status: on/off 4.5.
Using the CLI Commands Command enclist conf Synopsis enclistconf Description List enclosure configurations. Command encidentify Synopsis encidentify on/off encx Description Enable or disable identifying the enclosure with a visual indication. This command is applicable only when enclosure visual indication hardware is available. Command encfwupdate Synopsis enfwupdate encx firmware.
Using the CLI Commands 4.5.9 iSCSI target / ports Command iscsitarglist Synopsis iscsitarglist istx/all Display the setting of one or all iSCSI targets, including the following information: Description • Target name • Target alias • CHAP authentication and incomming CHAP users, if any. Command iscsientityname Synopsis iscsientityname iscsi_entity_name Description Set the entity name of this system Command chapusr Synopsis chapusr add/remove/update user_name[-s secret][-t all/ x,y,...
Using the CLI Commands Command isnsconfig Synopsis isnsconfig add/remove server[:port] Description Configure the iSNS servers for iSCSI target automated discovery by iSCSI initiators. At most two iSNS servers can be added. The first added one will be the primary server and the latter one is the secondary server. If iSNS server is configured, the controller shall automatically register iSCSI target information.
Using the CLI Commands Command iscsiaggregportlist Synopsis iscsiaggregportlist agx Description Display the IP address setting and MAC of an iSCSI aggregation port, including the following information: MAC address, IP address, network mask, gateway, MTU size, link status and bind members Command ispliststat Synopsis ispliststat ispx Description Display the statistics of a iSCSI port (ispx), including the following information: iSCSI port identifier, MAC layer statistisc. 4.
Using the CLI Commands 4.6.3 LUN Command lunstat Synopsis lunstat on/off/reset Description Change the setting of LUN IO logging. Command lunliststat Synopsis lunliststat sgxluny/fcpxluny/sasxluny/scpxidylunz/hgxluny/ istxluny Description List LUN IO statistics. 4.6.4 Storage ports 4-29 Command fcpstat Synopsis fcpstat on/off/reset Description Enable or clear FC port statistics. Command fcpliststat Synopsis fcpliststat fcpx Description List FC port IO statistics.
Using the CLI Commands 4.7 Redundant Controller Configurations 4.7.1 Mirrored write cache control Command cachemirror Synopsis cachemirror [on/off] Description Show or change the setting of mirrored write cache control. Parameters [on/off]: enable or disable mirrored write cache 4.7.2 Change preferred controller Command prefctlchg Synopsis prefeclchg [-o] jbdx/dgxldy/volx ctlx Description Change the preferred controller of a virtual disk.
Using the CLI Commands Command eventget Synopsis eventget log.txt/log.csv Description Download all event records to a file, log.txt or log.csv. Command eventconfig Synopsis enentconfig [-s severity] Description List or configure the lowest severity level of events to be recorded. Parameters [-s severity]: severity level of events to record Command eventerase Synopsis eventerase Description Erase all records in the event log.
Using the CLI Commands Command eventmailconfig Synopsis eventmailconfig [-j subject] [-r xmin] [-d xsec] [-c content] Description Display or set the event mail configurations.
Using the CLI Commands Command autoshutdown Synopsis autoshutdown [on/off] [-e upsac/fan/temp] [-t xxmin] Description Review or set the auto shutdown function. [on/off]: enable or disable the auto shoutdown function Parameters [-e upsac/fan/temp]: event to trigger auto shutdown. (UPS AC power loss and then low battery or UPS connection loss, all fan failure, or over temperature) [-t xxmin]: shutdown delay time 4.9 System Management 4.9.
Using the CLI Commands Command configset Synopsis configset config.bin Description Store a file, config.bin, as the controller’s main configurations on NVRAM. Command configtext Synopsis configtext config.html Description Get the main configurations and save to a html file. Command configtextmail Synopsis configtextmail account Description Get the main configurations and save to a text file, which is then sent to the specified mail receiver.
Using the CLI Commands Command ntpsync Synopsis ntpsync Description Immediately synchronize controller’s time with network time server. Command datelist Synopsis datelist Description List current date, time, time zone, and DST (Daylight Saving Time) setting on the controller. If the controller time is synchronized with a NTP server, it also shows the IP address of the NTP server and whether the controller can connect to the NTP server. 4.9.
Using the CLI Commands Command paswdmail Synopsis passwdmail [-s account]/[send]/[off] Description When enabled, the email account to which the password reminder should be sent to is displayed. When disabled, off is displayed. Only one of the three options can be specified at a time.
Using the CLI Commands Command ctllist Synopsis ctllist ctlx [-r] Description List the controller-related information. Parameters [-r] (for redundant controller only): Show internal controller status Command sysdiag Synopsis sysdiag start/stop nvram/dram/fcloopback/led/disk all/ hdds Starts or stops one of the following self tests: • NVRAM R/W test: The test will be conducted only once when controller is restarted.
Using the CLI Commands Command beeper Synopsis beeper on/off/mute Description Review or set the beeper. Command fwupdate Synopsis fwupdate image.bin [-b] [-c ctlx] Description Upload the firmware image or update the boot code with the file, image.bin. [-b]: update boot code Parameters [-c ctlx] (for redundant controller only): target controller to update Command fwupdateprog Synopsis fwupdateprog [-c ctlx] Description List the current firmware update progress.
Using the CLI Commands Command bbmcontrol Synopsis bbmcontrol on/off Description Enable or disable battery backup support. Command memtest Synopsis memtest on/off Description Enable or disable memory testing during system boot-up. 4.10 Miscellaneous Utilities 4.10.
Using the CLI Commands 4.11 Configuration shortcuts 4.11.1 RAID quick setup Command raidquick Synopsis raidquick [-r raidlevel] [-i initopt] [-s spare_no] Initialize RAID configurations and LUN mapping according to the specified. [For single controller model] A volume (for raid30, raid50, or raid60) or a logical disk (for other RAID levels) will be created with all capacity of all local data member disks and it will be mapped to the LUN 0 of the default storage group of all host ports.
Using the CLI Commands 4.12 Snapshot Command svpcreate Synopsis svpcreate pdevice sdevice Description Create a snapshot volume pair. pdevice and sdevice must not be a private virtual disk. sdevice must not be used by any LUN. Restrictions pdevice and sdevice must not be in faulty and regular initialization state. The capacity of sdevice must be greater than 10% of the capacity of pdevice. Command svpdelete Synopsis svpdelete pdevice Description Delete a snapshot volume pair.
Using the CLI Commands Command svolname Synopsis svolname svolx name Description Set snapshot volume name. Command svpimport Synopsis svpimport pdevice sdevice Description Import snapshot volumes. Command svimportlist Synopsis svimportlist Description List snapshot volume pairs on virtual disks. Command svlist Synopsis svlist pdevice/all Description List snapshot volume pairs Command svrestore Synopsis svrestore svolx Description Restores a primary volume to a snapshot volume.
Advanced Functions Chapter 5: Advanced Functions 5.1 Multi-Path IO Solutions 5.1.1 Overview Multi-path IO allows a host computer to access a RAID system over multiple paths for enhancing system availability and performance. The RAID system supports multi-path IO either with the bundled proprietary software or by the native multi-path IO software of the operating systems.
Advanced Functions side software RAID0 because RAID0 forces I/O to be truncated into data stripes, resulting in overhead and limited size of per-transaction data transfer. • Higher bandwidth utilization With statically assigning paths to logical devices on a controller, the bandwidth of all connections cannot be fully utilized if the loading on different logical devices is uneven. By transferring data over all paths, bandwidth utilization is more efficient, and ROI is improved.
Advanced Functions 1. Create virtual disks, like JBOD disks, logical disks, and volumes 2. Choose symmetric storage presentation method 3. Add all HBA ports (with WWPN or SAS address) to the hosts in the controller 4. Selectively add hosts (HBA ports) to a host group (HG) 5. Export virtual disks to LUNs for the host group (HG) 6.
Advanced Functions Bellow is the guideline and example to set up the hosts and host groups when using multi-path IO solutions: • Independent MPIO Hosts Computers For independent (non-clustered) host computers sharing single RAID system, the storage should be partitioned and accessed independently by the host computers. One host group should be created for each host computer, and the host group should include all HBA ports on the host computer.
Advanced Functions Add WWPN of HBAs to hosts HBA0 WWPN -> Host 0 HBA1 WWPN -> Host 1 HBA2 WWPN -> Host 2 HBA3 WWPN -> Host 3 Add hosts to each host group Host 0 and Host 1 -> Host Group 0 Host 2 and Host 3 -> Host Group 1 Map LUNs to host groups DG0LD0 and DG0LD1 -> Host Group 0 DG1LD0 and DG1LD1 -> Host Group 1 • Clustered MPIO Host Computers For clustered host computers sharing single RAID system, the storage is to be accessed simultaneously by all host computers.
Advanced Functions The table below shows the configuration steps for Figure 5-27. Tasks Instructions Select Storage Provisioning method RAID Management > Storage Provisioning > Symmetric Add WWPN of HBAs to hosts HBA0 WWPN -> Host 0 HBA1 WWPN -> Host 1 HBA2 WWPN -> Host 2 HBA3 WWPN -> Host 3 Add hosts to one host group Host 0 and Host 1 -> Host Group 0 Host 2 and Host 3 -> Host Group 0 Map LUNs to host groups DG0LD0 and DG0LD1 -> Host Group 0 DG1LD0 and DG1LD1 -> Host Group 0 5.1.
Advanced Functions Management > Storage > Disk Management) When multi-path disks are not properly detected. • Install and Uninstall PathGuard To install the PathGuard, double click the installation file on a host computer (choose the 32-bit or 64-bit installation file according to your host system). And follow the on-screen instructions to start the installation. After the installation, you can install MPIO driver or use PathGuard GUI.
Advanced Functions Figure 5-3 Computer Management screen: Device Manager • Use the PathGuard GUI for managing MPIO disks You can launch the PathGuard GUI by clicking Start > Programs > PathGuard > PathGuard GUI. As PathGuard GUI allows you to manage multiple hosts running PathGuard MPIO drivers (either the local one or remote ones), you need to connect and login to a host before monitoring or managing its MPIO. Please follow the steps below: 1. Click the Connect button 2.
Advanced Functions • MPIO Device Information When logged in, the PathGuard MPIO Utility GUI shows all connected MPIO disks.
Advanced Functions 1. From the Path Policy drop-down menu, select either Fail-over or Dynamic balance. • If you select Fail-over mode, specify the preferred working path. • If you select Dynamic balance mode, specify a weight mode and switch counter. 2. Each option is described as below. Specify the settings for the selected MPIO disk. Path Policy Fail-over: The Read/Write IOs are transferred on the designated Primary (Active) path.
Advanced Functions Command Queue: Given path1 has x IOs in queue, path2 has y IOs in queue and switch counter has been set to z IOs. Whenever z Read/ Write IOs have been transferred, the transferred Read/Write IO Queues on each path will be checked. If x > y and the primary (active) path is on path1, the primary path will be switched to path2 at next IO. Vice versa, if x < y and current path is path2; the primary path will be switched back to path1 at next IO.
Advanced Functions • Install and start the multipathd service (Single-Controller System) 1. Check /etc/multipath.conf, and if it is not there, you need to build it (see the example under /usr/share/doc/packages/multipath-tools/ multipath.conf.synthetic). 2. To install multipathd into your Linux service scripts, type insserv /etc/ init.d/multipathd. 3.
Advanced Functions RHEL5 Xen/64bit:mpath-xxx-x.x86_64xen-rhel5.rpm SuSe10/32bit: mpath-xxx-x.i586-sles10.rpm SuSe10/64bit: mpath-xxx-x.x86_64-sles10.rpm If your Linux kernel cannot match the pre-built driver binaries, you may also build the binary on your own. Below are the source RPM packages: RHEL5: mpath-xxx-x.src-rhel5.rpm SuSe10: mpath-xxx-x.src-sles10.rpm 1. Install the RPM by typing rpm -ivh mpath-xxx-x.xxx-xxxx.rpm.
Advanced Functions 1. To view the LUNs of the attached RAID systems, type cat /proc/scsi/ scsi, and similar outputs are displayed as below: 2. To check if multipathd service has been activated or not, type chkconfig --list multipathd. 3. To check if service has been running or not, type serivce -- statusall.The multipathd provides several commands for configuring the paths as well as showing path and device information. Type multipathd -k to enter its interactive mode. 4.
Advanced Functions 5.1.6 MAC Multi-Path Solution Mac OS X provides multi-path support on a basis since OS X 10.3.5, providing both path redundancy and load balancing. Mac OS X implements miltipathing at the target device level, and it requires that the RAID controller presents the same World Wide Node Name (WWNN) to all the host interfaces connected to the MAC systems. Please refer to • Setting FC Worldwide Node Name on page 2-61 to select identical WWNN.
Advanced Functions 5.1.8 Sun Solaris 10 OS Multi-Path Solution The latest Sun Solaris OS 10 has integrated Storage Multipahting software, which offers path failover and a path management utility. The singlecontroller RAID system is fully compliant with the software.
Advanced Functions As Figure 5-5 shows, the green and the red dotted paths are both active paths. When the green path link fails, the red dotted path will continue to access all the storage devices without interruption.
Advanced Functions Configuration Tasks Tasks Create Virtual volumes and specify the preferred controller Instructions RAID Management > Disk Groups > Create DG0 and DG1 RAID Management > Logical Disks > Create DG0LD0 > Specify the preferred controller as ctla RAID Management > Logical Disks > Create DG0LD1 > Specify the preferred controller as ctla RAID Management > Logical Disks > Create DG1LD0 > Specify the preferred controller as ctlb RAID Management > Logical Disks > Create DG1LD1 > Specify the prefer
Advanced Functions • Mirrored write cache A controller caches data in the memory for performance when the delay-write option is turned on. To ensure that the cached data can be retained, data written to one controller is also forwarded to the peer controller. The RCC also serves as the path of data forwarding for mirroring write cache. You may also disable the write cache mirroring by the UI (see Mirrored Write Cache Control option on Section 2.7.15).
Advanced Functions • Owner controller and preferred controller The controller implements the ALUA (Asymmetric Logical Unit Access) algorithm to ensure that only one controller is allowed to access a virtual disk. The controller that controls a virtual disk is the owner controller of the virtual disk. When both controllers are healthy and all paths are online, the owner controller is the same as the preferred controller.
Advanced Functions • Configuration data The controller’s configurations and states are synchronized between two controllers. There are two copies of one identical configuration data in the two controller. Updating the two copies of configuration data should be considered as an atomic operation. • Event logs The event logs are mirrored between controllers. Users can view the event logs even one of controllers is failed.
Advanced Functions For example, once the firmware update is executed on controller A, all the LUN mappings will be shifted from controller B to controller A. Then the controller B restarts automatically. When the controller B is completed with the firmware update, all the LUN mappings will be shifted from controller A to controller B. The controller A then restarts automatically.
Advanced Functions • Specify the storage provisioning method • Assign the WWPN for the HBAs in the server hosts, and group them into a host group • Bind the two logical disks to the host group In this configuration, for DG0LD0, the green path is the active path while the red path is the standby path, when the green path fails, the link transfroms and access will be continued by the red dotted path; for DG1LD0, the condition is reversed. Please check other similar description in section 5.3.
Advanced Functions Select Storage Provisioning method RAID Management > Storage Provisioning > Simple Specify the LUN ID and map LUNs to fiber ports fcpa2 -> DG0LD0 fcpa2 -> DG1LD0 fcpb2 -> DG0LD0 fcpb2 -> DG1LD0 • Active-Active Redundant Single MPIO Host (Quad Channel) As Figure 5-7 shows, the redundant RAID system is operating in a single MPIO host environment using the symmetric storage method. The access channel is established via four fibre ports, fcpa1, fcpa2, fcpb1, and fcpb2.
Advanced Functions Configuration Tasks Tasks Instructions Create Virtual volumes and specify the preferred controller RAID Management > Disk Groups > Create DG0 and DG1 RAID Management > Logical Disks > Create DG0LD0 > Specify the preferred controller as ctla RAID Management > Logical Disks > Create DG1LD0 > Specify the preferred controller as ctlb Select Storage Provisioning method RAID Management > Storage Provisioning > Symmetric Add WWPN of HBAs to hosts HBA0 WWPN -> Host 0 -> Host Group 0 HBA1
Advanced Functions To set up the connection, perform these tasks in the RAID GUI: • Specify the storage provisioning method • Assign the WWPN for the HBAs in the server hosts • Define the host group to which the server host belongs to • Create storage groups for LUNs • Bind storage groups to each host group across four fibre ports In this configuration, for DG0LD0 and DG0LD1, the green path is the active path while the red path is the standby path, when the green path fails, the link transfroms and access w
Advanced Functions Assign LUNs to storage groups DG0LD0 and DG0LD1 -> Storage Group 0 DG1LD0 and DG1LD1 -> Storage Group 1 Bind host groups and storage groups to the fibre ports Storage Group 0 bound to Host Group 0 -> fcpa2 and fcpb2 Storage Group 1 bound to Host Group 1 -> fcpa1 and fcpb1 • Active-Active Redundant Dual MPIO Clustering Hosts (With Fibre/SAS switch) As Figure 5-9 shows, the redundant RAID system is operating in a clustering environment with dual MPIO hosts and two FC/SAS switches.
Advanced Functions Before proceeding with the following configuration tasks, ensure the FC/ SAS switches are used to establish the connections between the hosts and the redundant RAID system. Then perform the GUI configuration tasks as described in the following Configuration Tasks table.
Advanced Functions ports, fcpa2 and fcpb2. For all LUNs, the green path is the active path to the controller A, and the red path is the standby path to the controller B. Host Group 0 Host HBA1 WWP FCPa1 FCP1 FCPb2 FCP2 N WW PN HBA0 FCPa2 FCP2 FCPb1 FCP1 Controller A Controller B DG0LD0 DG1LD0 Figure 5-10 Active-Passive Redundant Single MPIO host The steps to set up the active-passive and active-active connections are almost the same.
Advanced Functions Add WWPN of HBAs to hosts HBA0 WWPN -> Host 0 -> Host Group 0 HBA1 WWPN -> Host 1 -> Host Group 0 Map LUNs to host groups DG0LD0 and DG1LD0 -> Host Group 0 5.3.4 Controller and Path Failover/Failback Scenarios By incorporating with the MPIO driver, the access to any virtual disk can be continued when one of the controller is failed. Two principles should be cared for proper operation: 1. MPIO driver must be installed in the hosts. 2.
Advanced Functions • Controller Failover and Failback Scenarios When doing the controller failover and failback in the redundantcontroller systems, the two controllers must meet the following hardware and software requirements: Hardware: 1. Both controllers are of the same model and PLD version 2. Same number and model of daughter boards installed on both controllers 3. Same BBM (battery backup module) number and state 4.
Advanced Functions Normally, the heartbeat LED on each controller board is flashing periodically and the system keeps syncing state messages shown on the GUI to identify the controller is alive. When a heartbeat LED does not flash anymore, or the state message cannot be synced, the controller will be regarded as failed. Note When the heartbeat LED of both controllers are flashing, users are allowed to hot remove any one controller.
Advanced Functions Figure 5-14 Controller failback message If both controllers are down, the following pop-up dialog box will be displayed to notify the user. Figure 5-15 Error message indicates both controller failures 5.4 Snapshot 5.4.1 Introduction Snapshot allows you to create instantaneous data images of a volume at designated points in time.
Advanced Functions • Reducing Data-freezing Time for Backup or Replication When doing backup or data replication, the data of a volume has to be frozen to maintain the data consistency by pausing the I/O access of the applications. With the snapshot function, a copy of a volume can be created instantaneously, and the backup or replication operations can be performed on the snapshot volume, so the time to freeze a volume for backup can be largely reduced.
Advanced Functions in the secondary volume for the RAID controller to know where the differential data is stored. Because the secondary volume stores only the differential data, you can choose a secondary volume of capacity less than the primary volume. However, to ensure minimum operations, the capacity of the secondary volume has to be at least 10 percent of the primary volume.
Advanced Functions • Restoring by Snapshots Users can online restore a primary volume to one of its snapshot volumes. After the restore, the contents of the primary volume immediately become the current image of data of the selected snapshot volume, and the primary volume is accessible. A backward synchronization task is started in the background to copy data of segments from the secondary volume and spare COW volume to overwrite the differential data on the primary volume.
Advanced Functions Phase 2: Configuration 5. Create volumes of the secondary volumes. 6. Select a secondary volume for each source volume (primary volume). 7. Set up snapshot options, like overflow alert. 8. Build snapshot automation scripts and conduct trail runs (optionally). Phase 3: Creating and Utilizing Snapshots (Manually or Scripted) When taking a snapshot for a source volume, the tasks below are required: 9. Stop all the write access to the LUN of the primary volume. 10.
Advanced Functions Another consideration in estimate reserved capacity is that because the COW operations are done by chunks, consisting of multiple consecutive sectors, more space is required than the actual data being modified. If the space of a secondary volume is fully occupied, the data on the snapshot volumes will be corrupted. Be aware of applications that would change huge amount of data on a source volume, like video recording and file system defragmentation.
Advanced Functions In contrary to stopping the applications manually, you may use the utility offered by your applications to force the applications to enter “quiescent” state, in which there is no ongoing transaction and all completed transactions have been made effective permanently. In some systems, you may try to un-mount the LUN to force the operating systems to flush cached data and to avoid I/O access when the snapshot is taken.
Advanced Functions (6) Mount the LUN of the primary volume at the host computers Note 1. 1.Restoring data with a snapshot volume destroys the data on the primary volume. 2. If selecting a snapshot volume with LUN accessed by host computer, flush the system cache before unmouting the LUN of the snapshot volume. • Deleting Snapshots It is advised to delete any snapshot volume once you do not need it.
Advanced Functions • Delete unused logical disks to release free space (Section 2.6.4 Logical disks) • Delete unused volumes to release free logical disks (Section 2.6.5 Volumes) • Expand a disk group by adding hard disks to it (Section 2.7.1 Expanding disk groups) • Shrink under-utilized logical disks to release free space (Section 2.7.5 Shrinking logical disks) • Shrink under-utilized volumes to release free logical disks (Section 2.7.
Advanced Functions (3) Shrink the partition on the LUN by your partition editor (4) Shrink the corresponding logical disk or volume by the firmware utility (5) Rescan the physical drives by your operating system utility • Capabilities at host to support LUN resizing Proper LUN resizing depends on the capabilities of your operating system, partition editor, and file system utilities. It is advised to check the related manuals and do some trial runs before doing LUN resizing for your production site.
Advanced Functions • File system defragmentation might be needed before resizing Note The software listed above is only for your information; no warranty should be assumed. Please contact the software vendors to learn how to use the software to support LUN resizing.
Advanced Functions LD 0 free chunk 0 LD 0 LD 1 LD 2 disk group defragment LD 1 free chunk 1 LD 2 free chunk 2 free chunk 0 DG DG Figure 5-17 Defragment a disk group to expand the last free chunk • Defragment a disk group to consolidate free chunks All existing free chunks are deleted, and a single free chunk at the end of the disk group is created.
Advanced Functions LD 0 LD 0 shrink LD 1 LD 1 LD 1 free chunk 0 free chunk 0 LD 2 LD 2 DG DG Figure 5-19 Logical disk capacity shrink and expanding an adjacent free chunk • Shrink a logical disk without an adjacent free chunk After a logical disk is shrunk, a free chunk is created next to the logical disk. LD 0 LD 0 shrink LD 1 LD 1 LD 1 free chunk 1 LD 2 LD 2 free chunk 0 free chunk 0 DG DG Figure 5-20 Logical disk capacity shrink and creating a new free chunk 5.5.
Advanced Functions • Expand a logical disk by moving logical disks to a free chunk If there is no free chunk right after the selected logical disk, the controller will start a background task to move nearby logical disks to fill the requested capacity.
Advanced Functions Disk group (before) Disk group (after) LD 0 LD 0 LD 1 LD 1 LD 2 LD 2 Free chunk Free chunk MD 0 MD 1 MD 2 MD 0 MD 1 MD 2 MD 3 MD 4 Figure 5-24 Disk group expansion by adding new member disks and enlarging the last free • Disk group expansion to create a free chunk If the disk group has no free chunks in the end space before expansion, a new free chunk will be created.
Advanced Functions 5.5.5 Volume expansion and shrink The capacity of a volume can be online expanded by adding the logical disks to the volume, which concatenates the space of each logical disk to form a larger capacity. Because the expansion is done instantly without incurring any background tasks, you can quickly start using the added capacity without waiting. Users can also reduce the capacity of a volume by removing the concatenated logical disks.
Advanced Functions Windows Server XP, 2003, and Vista operating system. It can also support Windows 2000, but you need to download it from Microsoft web site. For a list of commands that you can use within the Diskpart console you can type help to get some information. For the help instructions for a particular command you can type the name of the command followed by help, such as select help.
Advanced Functions Step4: At the DISKPART prompt, type: shrink desired=2000 (If you do not set a size, such as the above example for 2 GB, it will shrink the partition by the maximum amount possible. You may use shrink querymax command to know the maximum space that you can shrink.) When the shrink command is done, you should receive a message stating that Diskpart had successfully shrunk the volume.
Advanced Functions • Consolidating event logs of multiple RAID systems RAIDGuard Central keeps monitoring the RAID systems and stores the event log from the RAID systems to local files. You can browse the event logs of the RAID systems registered in RAIDGuard Central to know the complete event history or to export the event log to files.
Advanced Functions • Support multiple languages RAIDGuard Central currently supports three languages: English, Traditional Chinese, and Simplified Chinese. The default language will be automatically selected according to the default locale of the computers running RAIDGuard Central, and you may also set the language manually. RAIDGuard Central allows adding more languages. Please contact your RAID system supplier if you want to use other languages. 5.6.
Advanced Functions You may follow the steps below to deploy the RGC components: 1. Install RAID systems and connect them to the networks. 2. Install one RGC Server and conduct the necessary configurations (you need to start web server if you would like to use RGC GUI). 3. Install RGC Agents (one for each network segment). 4. Launch RGC GUI (you will need to enter a password). 5. Use RGC GUI to add RGC Agents by keying the IP address of the RGC Agents. 6.
Advanced Functions systems. The monitoring tasks can still continue when one of the RGC Servers is down. Note 1. The RGC components communicate with each other by the TCP connections at the following ports: 8060~8070, 8077, and 8088. Make sure the network connection and these ports are not blocked by your firewall equipments and software before deploying RGC components. Please also make sure these TCP ports are not used by other applications running on the computer of RGC Server and Agents. 2.
Advanced Functions • Mac/ Linux OS platform To uninstall the RAIDGuard Central from your Mac or Linux operating system, simply delete the folder where the RAIDGuard Central program files are located. 5.6.5 Launching the RAIDGuard Central When the installation is finished, launch the RGC Server and RGC Agent monitor screens as described below: In Windows OS: Go to Start > Programs > RAIDGuard Central > RAIDGuard Central or RAIDGuard Agent. In Mac OS: Go to Application > RAIDGuard Central > RGC.
Advanced Functions • RGC Server and RGC Agent Monitor Screens The RGC Server monitor screen (based on Windows platform) is displayed as below: Figure 5-31 RGC Server monitor screen The following table describes the function of each menu bar item, buttons, and listed information in this screen. Menu Bar System Exit: Exit the program. Specify the desired GUI language. Language Help * The language options will differ according to the language support on your operating system.
Advanced Functions Connecting Users Display the number of users logged into the RGC GUI. Note RAIDGuard Central supports only login with the admin account. The RGC Agent monitor screen (based on Windows platform) is displayed as below: Figure 5-32 RGC Agent monitor screen The following table describes the function of each menu bar item and listed information in this screen. Menu Bar System Exit: Exit the program. Specify the desired GUI language.
Advanced Functions 5.6.6 RGC GUI Overview • Login To launch RGC GUI, you may click the Launch RGC GUI button on the RGC Server monitor screen. You can also access the GUI remotely with a web browser by entering the URL: http://RGC-IP:xxxx/RGCG, where RGCIP is the IP address of the computer running RGC Server, and xxxx is the port of the RGC web server is listening to. Note 1. The RGC GUI is a java-based software utility.
Advanced Functions Security Change Password: Change the password of the current user. Logout: Log out the current user. Specify the desired GUI language. Language Help * The language options will differ according to the language support on your operating system. Help Contents: Open the help web page. About: Display the program version. Tool Bar MSN tool button Open the MSN Login and Configure screen. This icon also indicates the MSN status (Green: MSN account is online; Red: MSN account is offline).
Advanced Functions 2. An Agent icon ( ) with IP address will be displayed in the Structure tree section if the Agent has been successfully added. Figure 5-34 Adding the IP address of an agent Note 1. If the RGC Agent is installed onto the local host server, you can also add it as one of the agents. 2. Each agent can only be controlled by a RGC Server. 3. The color of an agent icon ( ) will fade away when it goes offline. Scan RAID systems 1. Click the Agent icon ( Agent.
Advanced Functions systems within the IP address range will respond to the Agent. Up to 256 RAID systems can be displayed per scan. If you have more RAID systems on single subnetwork, you need to carry out multiple scans using different IP ranges. Figure 5-36 Scanning the online RAID systems in the selected agent’s domain Figure 5-36 shows the RAID system scan screen. The System Panel contains the following columns to display the information of each RAID system discovered.
Advanced Functions Register a RAID system 1. Login to RAID systems with admin is required for the registration. RAIDGuard Central will attempt to use the default admin password '0000' to login the selected RAID system. If the password is incorrect, it will pop up a window to request for your input. Note 1. If you register the selected RAID system three times with the wrong password, the pop-up password request window will close.
Advanced Functions 2. Click the Remove this agent button in the system panel, and the selected agent is removed from the RGC Server. Note To clear the records of all RAID systems registered to a removed agent, you need to remove all RAID systems registered to this agent first before removing a RGC Agent. See the next section “Unregister a RAID system” for more information.
Advanced Functions Click a registered RAID system on the structure tree. The retrieved system information and existing event logs are displayed in the system panel. Figure 5-38 RGC GUI - System Panel Click the Severity drop-down menu to display the event logs according to the specified severity level. You can view the event logs in different pages by either using the and buttons or entering the required page number in the page number field.
Advanced Functions 5.6.9 Configuring MSN Event Notification The RAIDGuard Central integrates with the MSN service to notify users of system status changes by sending instant messages. Follow the steps below to configure this function: 1. From the Tool bar in RGC GUI, click the MSN tool button ( or ) to open the MSN Login and Configure screen. 2. Select the Login tab to enter the MSN account and password to be used by RAIDGuard Central to login to MSN server and send out messages. 3.
Advanced Functions The architecture of VDS is illustrated as below: Figure 5-39 VDS Provider illustration VDS is supported on Windows server 2003 SP-1(VDS1.0), Windows server 2003 R2 (VDS1.1). Microsoft provides both command-line and GUI tool based on VDS: DiskRAID and Microsoft Storage Manager for SAN. VDScompliant storage management software from other vendors is also available. Please see Section G.5 for more information. You may follow the steps below to build VDS-based management environment. 5.
Advanced Functions 5.7.3 Uninstalling the VDS Provider Follow the steps below to uninstall the VDS Provider GUI from the management host. 1. Click Start > Settings > Control Panel > Add or Remove Programs. 2. Locate VDS Provider and click on it to start the un-installation. Click No to quit or Yes to confirm the un-installation. 5.7.
Advanced Functions Figure 5-40 VDS Provider Configure screen • Register RAID systems 1. Click the Scan RAID systems in the LAN button to locate RAID systems on the LAN. 2. Check the checkbox in the Ctrl column of the RAID system you want to register. 3. For each checked RAID system, a window pops up for you to enter the password. 4. If all setting are done, choose ‘Exit’ to exit this program. Note 1. At most 16 RAID systems are managed by single VDS Provider. 2.
Advanced Functions Please follow the links below and enter “diskraid” to find more information: Microsoft Web Site Links: Search link: http://search.microsoft.com/?mkt=en-US • Microsoft Storage Manager for SANs The Storage Manager for SANs (SMfS) is RAID management GUI introduced in Windows Server 2003 R2 by Microsoft. You may follow the steps below to install it: 1. In Control Panel, click Add or Remove Programs. Then click Add/ Remove Windows Components. 2.
Advanced Functions SAN environment, graphically displaying all supported servers, HBAs, switches and storage. For more information, please contact Emulex or follow the link below: Web Site Links: http://www.emulex.
Troubleshooting Chapter 6: Troubleshooting 6.1 General Guidelines When you encounter issues, the most essential troubleshooting is to check the event log of your RAID system and carry out the suggested actions offered in the Appendix D. In addition, you may need to check the system log of the operating system at your host computers.
Troubleshooting • Voltage failure or error • Power supply failure or error • Fan failure or error • Temperature failure or error • BBM failure or error (when BBM is connected) • Disk SMART warning • Disk bad block over threshold warning • Disk group with degraded logical disk and no disk for rebuilding • Disk group with faulty logical disks • UPS failure or error (when UPS control is on, see 2.9.
Troubleshooting 3. Use large I/O size at host Aggregating multiple contiguous I/O into single I/O of big size significantly improves the sequential-I/O performance because of better bandwidth utilization and reduced CPU loading. You can use larger allocation size (a.k.a. block size) when creating a file system (for example, 64KB for NTFS and Apple Xsan, and 4KB for ext3).
Troubleshooting 7. Check I/O path connections You have to make sure the bandwidth of I/O path can deliver the performance you need. For example, if you install a quad-port 4Gbps Fibre Channel HBA to a 4-lane PCIe 1.0 slot, your bandwidth will be limited to 1GB/s bandwidth of the PCIe slot. You need also to check the data rate of I/O paths is configured properly without degradation.
Troubleshooting 12. Close the web GUI during I/O access Sometimes, the web GUI or RAID monitoring software could be an influential factor to the performance unstableness, because it needs to retrieve RAID system status periodically, and consumes CPU cycles of the storage processor. Close the web GUI when you run time-sensitive applications. 13.
Troubleshooting 2. Hard disks are offline unexpected The RAID controller takes a hard disk offline when the hard disk cannot respond to the RAID controller after the full-cycle error recovery procedure has been done. This could happen when the hard disk is permanently dead because of its internal component failure, and you lose all your data on the hard disk.
Troubleshooting causing corrupted logical disks, you may try to use array recovery utility to the RAID configurations (see 2.7.13 Array recovery on page 2-53). 6. Ensure proper power on/off sequence of RAID and JBOD You have to make sure the expansion chassis has been ready before powering on the RAID system, such that the RAID system can properly recognize the expansion chassis and the hard disks.
Troubleshooting • To avoid confusing operations, some settings cannot be modified when a related state happens. For example, rebuilding-related settings cannot be modified when there is rebuilding disk. 3. The web GUI does not show updated information The web browser displays the cached the web pages such that you cannot see the updated web pages. For example, the percentage of firmware upload progress isn’t updated.
Troubleshooting For Windows above to work around the 2TB limitation, choose bigger sector size of a LUN (see 2.6.7 Storage provisioning on page 2-37). However, you cannot use dynamic disk in Windows for the LUN with non512B sector size, and your data will be lost if you change the sector size of a LUN. The table below shows the capacity correlated with sector size.
Troubleshooting 5. Hard disk shows Conflict state The Conflict state indicates that the hard disk contains valid RAID configurations but the controller cannot work with such configurations. If the conflict is because the cache unit size of the controller is bigger than the stripe size of the logical disk on the hard disks, you can change the cache unit size (see 2.7.16 Miscellaneous on page 2-56) and restart the system to accommodate the logical disk.
Troubleshooting (F) DISK NR UNEQ: The detected disk numbers are not same of both controller. (G) EXPAN NR UNEQ WILL BE RETEST: The detected expansion numbers are not same of both controller. Below list the resolutions for the configuration conflict. (A/B/C/F) Contact your RAID system supplier to get the correct controller (D/E) Install proper memory module and BBM (G) Check connection is properly between expansions and controllers. Wait boot agent to re-test.
Troubleshooting Controller on page 5-21). The controllers will stop boot-up to show messages on the LCD. The messages and corresponding resolutions are the same as failure of replacement controller. If the two controllers have different versions of boot code or firmware, you need to choose between the versions. If the two controllers have different BBM option, you need to choose to enable or disable it.
Troubleshooting 5. It takes too much time for path or controller failover with MPIO driver The MPIO driver detects path failure by checking the HBA driver to get the link status. The setting of HBA determines how much time it takes for the MPIO driver to detect path failure and to do path failover. If your controller failover/failback is supported by MPIO drivers, it also determines how much time it takes for controller failover.
Appendix A: Understanding RAID A.1 RAID Overview The controller supports eleven types of RAID: RAID 0, 1, 3, 5, 6, 10, 30, 50, 60, JBOD and NRAID. The application(s) you are using will determine which RAID setup is best for you. • RAID Level 0 This level offers high transfer rates and is ideal for large blocks of data where speed is of the essence. Computer Aided Design, graphics, scientific computing, image, and multimedia applications are all good examples.
Appendix • NRAID ("None RAID") This level allows you to combine the capacity of all drives and does not suffer from data redundancy. • RAID Level 10 This level offers a compromise between the reliability and tolerance of level 1 and the high transfer rates provided by level 0. • RAID Level 30/50/60 RAID 30/50/60 performs striping over RAID 3/5/6 groups. With multiple independent RAID groups, performance and reliability can be improved.
Appendix A.2 RAID 0 RAID 0 links each drive in the array to form one large drive. Storage capacity is determined by the smallest drive in the array. This capacity is then applied to format all other drives in the array. When using a 40GB, 50GB and a 60GB drive in a RAID 0 array, your system will effectively have a single 120GB drive (40GB x 3).
Appendix A.3 RAID 1 RAID 1 is commonly referred to as disk mirroring as all data is duplicated on two or more disks. This provides a high access rate and very high data availability. RAID 1 has low performance for write operations but very high performance for intensive read operations. RAID 1: Mirroring Characteristics • • • • • • • Storage capacity = the capacity of the smallest disk A minimum of two disks are required. Fault tolerance: Very good Read transaction rate: Good.
Appendix A.4 RAID 3 In RAID 3, all data is divided into pieces, after which the system calculates the parity of these pieces. The pieces are written to separate disks in parallel with the writing of the parity data. In the event of disk failure, the parity data can be used to rebuild the lost data. If two or more disks fail, data will be lost.
Appendix A.5 RAID 5 With RAID 5, the system calculates parity from data on three drives. If one of the drives fails, parity data can be used to rebuild the lost data. Under RAID 5, parity data is stored across all disks in the array. This maximizes the amount of storage capacity available from all drives in the array while still providing data redundancy. Data under RAID 5 is block-interleaved.
Appendix A.6 RAID 6 RAID 6 stripes data and parity data across an array of drives, as with RAID 5, and calculates two sets of parity information for each stripe to improve fault tolerance. Performance-wise, RAID 6 is generally slightly worse than RAID 5 in terms of writes, due to the extra parity calculations. It may, however, be slightly faster in terms of random reads, due to the spreading of data over one more disk. As with RAID 3 and RAID 5, performance can be adjusted by changing stripe size.
Appendix A.7 RAID 10 RAID 10 arrays are formed by striping data across RAID 1 sub-arrays. This offers better performance than RAID 1 alone but does not have the speed of a pure RAID 0 array. Storage efficiency and fault tolerance vary depending on the number and size of sub-arrays compared to the array as a whole.
Appendix A.8 RAID 30 RAID 30 arrays are formed by striping data across RAID 3 sub-arrays. This offers better performance than RAID 3 alone but does not have the speed of a pure RAID 0 array. Storage efficiency and fault tolerance vary depending on the number and size of sub-arrays compared to the array as a whole. RAID 30 resembles RAID 50 in terms of characteristics but is more suitable for handling large files.
Appendix A.9 RAID 50 RAID 50 arrays are formed by striping data across RAID 5 sub-arrays. Striping helps increase capacity and performance without adding disks to each RAID 5 array (which will decrease data availability and affect performance when running in a degraded mode). Storage efficiency and fault tolerance vary, depending on the number and size of the subarrays compared to the array as a whole.
Appendix A.10 RAID 60 RAID 60 arrays are formed by striping data across RAID 6 sub-arrays. Striping increases the system capacity and performance without adding disks to the array. It features dual parity, which allows for a possible failure of two disks in each array. RAID 60: Striping with dual parity Characteristics • • • • • Storage capacity = [(number of disks in each subarray) -1] x (number of subarrays) x (capacity of the smallest disk) A minimum of eight disks are required.
Appendix A.11 JBOD JBOD (“Just a Bunch of Disks”) focuses on individual drives. The operating system sees each drive as an individual drive in JBOD mode. Therefore, the total capacity of JBOD is the sum of the capacities of each disk. This allows the user to add disks until the desired total capacity is reached. However, there is no RAID protection in this mode.
Appendix A.12 NRAID NRAID (“None RAID”) combines all drives as one simple logical volume. The capacity of this volume is the total capacity of the physical member disks. NRAID does not have data redundancy.
Appendix Appendix B: Features and Benefits B.1 Overview With the comprehensive features and utilities of the firmware, the system administrators can easily build solutions that meet business requirements as well as conduct management tasks effortlessly. The firmware offers not only performance and reliability but also capabilities to effectively maximize storage resources. It is a well-balanced mix of powerful functionalities and user-friendly management interfaces.
Appendix Selective presentation for sophisticated storage area network (SAN) environments The administrators can choose an appropriate presentation method according to the environment to quickly complete the presentation at the deployment stage and effectively manage the presentation at the maintenance stage. • Host and LUN management The host HBA ports are managed by groups and the internal storage resources are exported as LUNs managed in distinct storage groups.
Appendix stripe sizes can coexist in single disk group. This largely improves the utilization of disk space as well as simplifies the configuration planning. • Online volume management The firmware provides online volume management to build LUNs of multilevel RAID by striping over two or more logical disks for higher performance (aggregating horsepower of more disks), better reliability (multiple independent parity), and larger capacity (distributing data over more disks).
Appendix • Selective initialization method and mode To initialize a logical disk, either data zeroing or background parity regeneration can be used. The administrator can choose to execute the background initialization for all logical disks simultaneously or one by one sequentially. To avoid confusing the operating systems, the background initialization will also clean up the data on the first few sectors to erase the file system super blocks.
Appendix controller will start a background task to perform the data re-layout operations; during the migration, RAID operations are still available to protect data and serve requests from host computers. Unlike other implementations where only specific RAID levels or stripe sizes can be migrated, the RAID controller firmware can do the migration virtually from all RAID levels and stripe sizes to others as long as the disk space is sufficient.
Appendix capacity change, RAID operations are still available to protect data and serve requests from host computers. • Concurrent logical disk capacity and disk group expansion The logical disk capacity expansion can also be done simultaneously with disk group expansion, and as a result, users can expand the capacity of a LUN by adding more drives to its disk group. Without logical disk capacity expansion, the administrator is forced to create a new LUN after the disk group expansion is done.
Appendix algorithms that can intelligently self-monitor and self-adjust the performance parameters. • Adaptive read-ahead (pre-read, pre-fetch) optimization Read-ahead operation improves the performance of sequential reads by pre-fetching data from disk drives according to current hosts’ read commands. The firmware can further identify multiple sequential read streams in random access and perform pre-read for the streams. The administrator can also specify the pre-read depth for dynamical tuning.
Appendix B.8 Proactive Data Protection The most fundamental requirement for a storage system is to protect the data from all kinds of failures. The RAID controller firmware supports versatile RAID configurations for different levels of reliability requirement, including RAID 6 to tolerate double-drive failure, and Triple Parity for extreme data availability. It provides online utilities for proactive data protection to monitor disk health, minimize the risk of data loss, and avoid RAID degradation.
Appendix • Online SMART disk cloning When a hard disk fails in a disk group, RAID enters the degradation state, which means lower performance, higher risk of data loss or RAID corruption. When a hard disk is likely to become faulty or unhealthy, such as bad sectors of a physical disk increases over a threshold, or a disk reports SMART warning, the controller will online copy all data of the disk to a spare disk.
Appendix • Seasoned redundancy design The storage system availability is achieved by the redundancy design to eliminate single point of failure. The controller is equipped with redundant flash chips with advanced algorithms for error checking and bad block reallocation in the firmware to protect the controller from defect flash blocks and ensure longer life time of the controller.
Appendix environmental conditions, like bad air conditioning or vibrations, or because of failures of hardware components, like connectors or cables. When any of these happens, the data and RAID configurations are gone forever for most storage systems. With the online array recovery, the firmware can online recognize and recover the RAID configurations stored on disk drives and get the data back as long as the disk drives can be running again. B.
Appendix B.11 Convenient Task Management The RAID controllers are equipped with extensive utilities to support the system administrator to conduct maintenance tasks, which may be to fortify the RAID protection by disk scrubbing, to reconfigure RAID attributes by migrating RAID level or stripe size, or to expand LUN capacity. There are also other tasks like disk rebuilding or disk cloning that are started by the firmware automatically.
Appendix unwanted performance impact. When the rebuilding is done, the paused tasks will be automatically resumed. • Task priority control Executing the background tasks needs to occupy system resources, like CPU time, memory bandwidth, or access to disk drive. The administrator can choose the priority of the background tasks to speed up the task execution or to prevent the task from disturbing the host accesses.
Appendix configurations and save it as a file on his desktops, and he can restore the configurations later, if needed for system recovery or apply the configuration files to other systems. The configurations can also be saved to disk drives such that the configurations can be restored from the disk drives after the array roaming. • Hardware parameters Extensive user-configurable parameters are provided for configuring the system.
Appendix line interface to deploy single configuration over multiple storage systems by replaying the CLI scripts predefined by the administrator. • Support LCD panel The LCD panel provides a quick overview of the system status as well as a simple way for setting basic configurations. It is very convenient for people who don’t have or don’t want to have the knowledge about the detailed operations of a storage system.
Appendix Appendix C: Boot Utility Follow the steps below to enter the Boot Utility menu: 1. Run HyperTerminal (or the terminal program used to establish an RS232 connection with your RAID system) and open the connection established with your RAID system. RS232 COM Port Setting Bits per second: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow Control: None 2. Turn on the RAID system, the terminal shows the version, CPU and memory information. 3.
Appendix There are eight items in the Boot Utility menu. (N) Set IP address (H) Utility menu (L) Load Image by TFTP (P) Set Password (B) Update Boot ROM (R) Restart system (S) Update System ROM (Q) Quit & Boot RAID system C.1 (N) Set IP address The Boot Utility allows you to update the Boot ROM and System ROM. First you need to set the controller and server IP addresses. Press [N] to enter the settings. 1. Set the Board IP address and press [Enter]. 2. Set the Server IP address and press [Enter]. 3.
Appendix C.2 (L) Load Image by TFTP Before a Boot ROM or System ROM update, you need to set up the TFTP server for loading a new firmware image. Follow the steps below to load an image: 1. Open the TFTP Server, click the Browse button to set the boot code or firmware image directory. You can use the Show Dir button to see the files in the directory. 2. Press [L] in the Boot Utility and enter the file name of boot code of firmware. 3. The TFTP server starts loading.
Appendix C.3 (B) Update Boot ROM Press [B] to update the Boot ROM. The firmware versions and the Update download boot firmware message are displayed. Press [Y] to start the Boot ROM update. You can see the process percentage on the screen. C.4 (S) Update System ROM Press [S] to update the System ROM. The firmware versions and the Update New System firmware message are displayed. Press [Y] and the system starts to update the System ROM with the primary flash and backup flash.
Appendix Note Before a Boot ROM or System ROM update, make sure you have loaded the image by TFTP server. If not, the following message displays: Invalid image size, load firmware first! C.5 (H) Utility menu Press [H] to clear the Utility screen, and recall the Boot Utility menu. C.6 (P) Set password Press [P] to set or change the password for the Boot Utility login. C.7 (R) Restart system Press [R] to exit the Boot Utility and restart the RAID system. C.
Appendix Appendix D: Event Log Messages D.1 RAID • Disk operations Event ID 0x0800 Type RAID Message HDDx added Severity INFO Parameters Disk ID Description hddx was added to the system from the user interface. Advice None Event ID 0x0801 Type RAID Message HDDx removed Severity NOTICE Parameters Disk ID Description hddx was removed from the system from the user interface.
Appendix Event ID 0x0c01 Type RAID Message JBODx deleted Severity INFO Parameters JBOD ID Description jbdx was deleted. Advice None Event ID 0x1000 Type RAID Message DGx created Severity INFO Parameters DG ID Description dgx was created. Advice None Event ID 0x1001 Type RAID Message DGx deleted Severity INFO Parameters DG ID Description dgx was deleted.
Appendix Event ID 0x1c01 Type RAID Message VOLx deleted Severity INFO Parameters VOL ID Description volx was deleted. Advice None • Initialization Event ID 0x204c Type RAID Message Write-zero init on DGx started Severity INFO Parameters DG ID Description Disk group zeroing task on dgx was started.
Appendix Event ID 0x2051 Type RAID Message Logical disk init on DGxLDy aborted Severity WARNING Parameters DG ID, LD ID Description Logical disk initialization task on dgxldy was aborted. Advice Check if any disks in the disk group failed, and then re-create the logical disk.
Appendix Event ID 0x0805 Type RAID Message Global spare HDDx removed Severity INFO Parameters Disk ID Description Global spare hddx was changed to be an unused disk. Advice None Event ID 0x1002 Type RAID Message Local spare HDDx of DGy added Severity INFO Parameters Disk ID, DG ID Description hddx was selected as local spare of dgy.
Appendix Event ID 0x2063 Severity NOTICE Rebuild progress, Parameters DG ID, Notify threshold Type RAID Message Rebuild progress(y%) on DGx reach to the notify percent(z%) Description The progress of rebuilding has reached the pre-define threshold. Advice None • Roaming Event ID 0x0820 Type RAID Message Disks changed during power-off Severity INFO Parameters The number of disks installed is different when the controller was Description powered off.
Appendix Event ID 0x2053 Type RAID Message DGxLDy is recovered Severity INFO Parameters DG ID, LD ID Description Logical disk dgxldy has been recovered. Advice None Event ID 0x2054 Type RAID Message VOLx is recovered Severity INFO Parameters VOL ID Description Volume volx has been recovered.
Appendix Event ID 0x1c03 Type RAID Message VOLx write cache is enabled Severity INFO Parameters VOL ID Description Write cache of volx was disabled by user. Advice None Event ID 0x1c04 Type RAID Message VOLx write cache is disabled Severity INFO Parameters VOL ID Description Write cache of volx was disabled by user.
Appendix Event ID 0x2043 Type TASK Message Expansion on DGx failed to start by schedule Severity WARNING Parameters DG ID Description Scheduled disk group expansion on dgx failed to start. Advice Check if the disk group is busy or non-optimal when starting the task. Event ID 0x200c Type TASK Message Expansion on DGx paused Severity NOTICE Parameters DG ID Description Disk group expansion on dgx was paused. Advice Check if there is failed member disk in the disk group during the task.
Appendix • Logical disk migration Event ID 0x2004 Type TASK Message Migration on DGxLDy started Severity INFO Parameters DG ID, LD ID Description Migration on dgxldy was started manually. Advice None Event ID 0x202c Type TASK Message Migration on DGxLDy started by schedule Severity NOTICE Parameters DG ID, LD ID Description Scheduled migration on dgxldy was started.
Appendix Advice Check if the logical disk is faulty. Event ID 0x2005 Type TASK Message Migration on DGxLDy completed Severity NOTICE Parameters DG ID, LD ID Description Migration on dgxldy was completed. Advice None Event ID 0x2061 Severity NOTICE Migrate progress, Parameters DG ID, Notify threshold Type TASK Message LD migrate progress(y%) on DGx reach to the notify percent(z%) Description The progress of LD migration has reached the pre-define threshold.
Appendix Event ID 0x202e Type TASK Message Expansion on DGxLDy started by schedule Description Scheduled logical disk capacity expansion on dgxldy was started. Advice None Event ID 0x2045 Type TASK Message Expansion on DGxLDy failed to start by schedule Description Scheduled logical disk capacity expansion on dgxldy failed to start. Advice Check if the logical disk or the disk group is busy or non-optimal when starting the task.
Appendix Event ID 0x202f Type TASK Message Expansion on DGxLDy completed Severity NOTICE Parameters DG ID, LD ID Description Logical disk capacity expansion on dgxldy is complete. Advice Hosts might need to rescan the LUN of the logical disk to get the updated capacity. The partitions or file systems on the logical disk has to be grown to access the newly created space.
Appendix Event ID 0x2033 Type TASK Message Defragment on DGx started by schedule Severity NOTICE Parameters DG ID Description Scheduled disk group defragment on dgx was started. Advice None Event ID 0x2047 Type TASK Message Defragment on DGx failed to start by schedule Severity WARNING Parameters DG ID Description Scheduled disk group defragment on dgx failed to start. Advice Check if the disk group is busy or non-optimal when starting the task.
Appendix Event ID 0x205e Severity NOTICE Defrag progress, Parameters DG ID, Notify threshold Type TASK Message Defrag progress(y%) on DGx reach to the notify percent(z%) Description The progress of defragmentation has reached the pre-define threshold. Advice None • Volume expansion Event ID 0x202a Type TASK Message VOLx expanded Severity NOTICE Parameters VOL ID Description Volume capacity expansion on volx was completed.
Appendix Event ID 0x2048 Type TASK Message Clone from HDDx to HDDy failed to auto start Severity WARNING Parameters DISK ID, DISK ID Description Auto disk cloning from hddx to hddy failed to start. Advice Check if the disk failed or the source disk group is non-optimal when starting the task. Event ID 0x2018 Type TASK Message Clone from HDDx to HDDy paused Severity NOTICE Parameters DISK ID, DISK ID Description Disk cloning from hddx to hddy was paused.
Appendix Event ID 0x2016 Type TASK Message Clone from HDDx to HDDy completed Severity NOTICE Parameters DISK ID, DISK ID Description Disk cloning from hddx to hddy is complete. Advice None Event ID 0x2056 Type TASK Message Clone from HDDx to HDDy auto-resumed Severity NOTICE Parameters DISK ID, DISK ID Description Disk cloning from hddx to hddy was auto-resumed.
Appendix Event ID 0x204a Type TASK Message Scrub on HDDx failed to start by schedule Severity WARNING Parameters DISK ID Description Scheduled disk scrubbing on hddx failed to start. Advice Check if the disk is off-line or busy. Event ID 0x2020 Type TASK Message Scrub on HDDx stopped with y bad sectors detected Description Disk scrubbing on hddx was stopped manually, and y bad sectors were detected.
Appendix Event ID 0x2065 Severity NOTICE Scrub. Progress, DISK ID, Parameters Notify threshold Type TASK Message Scrub progress(y%) on HDDx reach to the notify percent(z%) Description The progress of scrubbing disk has reached the pre-define threshold. Advice None • Disk scrubbing of disk groups Event ID 0x201d Type TASK Message Scrub on DGx started Severity INFO Parameters DG ID Description Disk scrubbing on dgx was started manually.
Appendix Event ID 0x2021 Severity INFO DG ID, Parameters Sector Num, Row Num, Row Num Type TASK Message Scrub on DGw stopped with x bad sectors detected, y inconsistent rows found, and z rows recovered Disk scrubbing on dgw was stopped manually, and there were x Description bad sectors detected, y inconsistent rows found, and z rows recovered.
Appendix Event ID 0x205d Severity NOTICE Scrub. Progress, Parameters DG ID, Notify threshold Type TASK Message Scrub progress(y%) on DGx reach to the notify percent(z%) Description The progress of scrubbing on dgx has reached the pre-define threshold. Advice None Note: Because one disk group can have only one logical disk executing disk scrubbing, the events do not record ID of the logical disk to execute disk scrubbing.
Appendix Event ID 0x2041 Severity INFO DG ID, LD_ID, Parameters Sector Num, Row Num, Row Num Type TASK Message Scrub on DGvLDw stopped with x bad sectors detected, y inconsistent rows found, and z rows recovered Disk scrubbing on dgvldw was stopped manually, and there Description were x bad sectors detected, y inconsistent rows found, and z rows recovered.
Appendix Event ID 0x206d Severity NOTICE Scrub. Progress, Parameters DG ID, LD_ID, Notify threshold Type TASK Message Scrub progress(w%) on DGxLDy reach to the notify percent(z%) Description The progress of scrubbing on dgxldy has reached the pre-define threshold. Advice None • Disk group parity regeneration Event ID 0x2024 Type TASK Message Reg. parity on DGx started Severity INFO Parameters DG ID Description Reg. parity on dgx was started manually.
Appendix Event ID 0x205c Severity NOTICE Reg. Progress, Parameters DG ID, Notify threshold Type TASK Message Reg. progress(y%) on DGx reach to the notify percent(z%) Description The progress of Reg. parity on dgx has reached the pre-define threshold. Advice None Event ID 0x2058 Type TASK Message Reg. parity on DGx started by schedule Severity NOTICE Parameters DG ID Description Scheduled Reg. parity on dgx was started Advice None Event ID 0x205a Type TASK Message Reg.
Appendix Event ID 0x203f Type TASK Message Reg. parity on DGxLDy stopped Severity INFO Parameters DG ID, LD_ID Description Reg. parity on dgxldy was stopped manually. Advice None Event ID 0x203d Type TASK Message Reg. parity on DGxLDy completed Severity NOTICE Parameters DG ID, LD_ID Description Reg. parity on dgxldy was completed. Advice None Event ID 0x206d Severity NOTICE Reg. Progress, Parameters DG ID, LD_ID, Notify threshold Type TASK Message Reg.
Appendix D.3 Disk • Disk status Event ID 0x0811 Type DISK Message HDDx powered on/off Severity INFO Parameters Disk ID Description hddx was powered on or off. Advice None Event ID 0x0817 Type DISK Message HDDx failed Severity ERROR Parameters Disk ID Description hddx failed to respond to the controller. Advice Check if the disk is corrupt or the disk interface connection is unstable.
Appendix • Disk IO exception handling Event ID 0x0818 Type DISK Message Controller x detected CRC error on HDDy Severity NOTICE Parameters Controller ID, Disk ID The controller x detected a CRC error when transferring data with hddy. This could be a transient error due to unstable chanDescription nel, electronic interference, heavy traffic, or malfunctioning hard disks. The controller will invalidate the data and retry the command.
Appendix Event ID 0x081e Severity NOTICE DISK ID, Parameters opcode, sense key, ASC, ASCQ Type DISK Message Check condition on HDDv: SCSI opcode=w, Sense Key=x, ASC=y, ASCQ=z Description This presents the SCSI status number when error happens such as CRC error and it will have some field (Sense Key, ASC, ASCQ). Advice If this event occurs often, check the disk connectivity, check power supply to disks, or replace with a new disk.
Appendix Event ID 0x081c Type DISK Message Reset disk i/f chip x in controller y Severity WARNING Parameters Chip ID, Controller ID The controller y resets chip x that failed to execute commands properly. This could be a transient error due to unstable channel, Description heavy traffic, or malfunctioning hard disks. The controller will resume normal operations of the chip after reset; however, this could result in performance drop of the disks attached to the disk ports of this chip.
Appendix Event ID 0x0806 Type DISK Message EXT DST on HDDx started Severity INFO Parameters Disk ID Description hddx started SMART extended device self test routine. Advice None Event ID 0x0808 Type DISK Message DST on HDDx stopped Description DST on hddx was stopped by the controller or from the user interface.
Appendix Event ID 0x080d Type DISK Message DST on HDDx completed with electrical error Severity WARNING Parameters Disk ID Description DST on hddx completed with electrical error. Advice The disk failed or will fail soon, replace the hard disk. Event ID 0x080e Type DISK Message DST on HDDx completed with unknown test element error Description DST on hddx completed with error but the failed elements are unknown. Advice The disk failed or will fail soon, replace the hard disk.
Appendix Event ID 0x1400 Type DISK Sector NO, Severity WARNING Parameters Sector NO, Disk ID Message A BBR entry added for mapping sector x to sector y on HDDz Description An entry of bad block reallocation table at was allocated for mapping sector x to sector y on hddz. Advice If the number of BBR table entries or spare blocks being reallocated grows exceptionally fast or beyond a reasonable number, consider to conduct diagnostics and replace with new disks.
Appendix Event ID 0x1409 Type DISK Threshold Severity NOTICE Parameters value, Disk ID Message BBR exceeds notice threshold x% on HDDy The number of bad block reallocation table entries on hddy has exceeded the pre-defined threshold level. The severity of this Description event depends on the threshold being exceed. Over threshold 1/ 2/3 leads to notice events.
Appendix Event ID 0x1403 Type DISK Message Out of BBR spare blocks on HDDx Severity WARNING Parameters Disk ID On-disk reserved space for bad block reallocation was occuDescription pied, reallocation cannot proceed if new bad sectors are detected. Advice Replace with new disks to prevent from data loss.
Appendix Event ID 0x0816 Type DISK Message Write both metadata on HDDx failed Severity WARNING Parameters Disk ID The controller failed to access both primary and secondary RAID metadata on hddx, and the RAID metadata was invalid. In this Description case, hddx will be set to faulty, and disk rebuilding will be started, if needed.
Appendix Event ID 0x1405 Type DISK Message Primary BBR table on HDDx is corrupt Severity WARNING Parameters Disk ID The controller failed to access the primary BBR table on hddx Description and the table was invalid. However, the secondary BBR table still works. Advice Start to monitor the status of the secondary BBR table on this disk.
Appendix D.4 Host ports FC • Hosts Event ID 0x3000 Type HOST Message Host x detected on host port y Description The controller detected host x on host port y. The host can start access the controller over the host port. Advice None Event ID 0x3001 Type HOST Message Host x removed on host port y Severity INFO Severity INFO Parameters Parameters Host WWPN, Host Port ID Host WWPN, Host Port ID Description Host x quitted from host port y.
Appendix Event ID 0x3003 Type HOST Message Host port x link down Severity NOTICE Parameters Host Port ID The link on the host port x had been turned down by the controller, and data transferring was posed. This happens when the host Description port was disconnected from host HBA or switch because of removing/powering down/resetting the host or switch, or removing the cables.
Appendix Event ID 0x3006 Type HOST Host Port ID, Severity WARNING Parameters Host WWPN, LUN ID Message Task abort on host port x from host y to LUN z The controller received task abort on host port x from host y to LUN z. This could be to recover from a transient error due to Description unstable channel, command time-out, or unexpected host behaviors. The controller will drop the command specified by the host, and the host will retry the command; however, this could result in LUN performance drop.
Appendix Event ID 0x3009 Type HOST Message Reset host i/f chip x in controller y Severity WARNING Parameters Chip ID, Controller ID The controller resets chip x that failed to execute commands properly. This could be to recover from a transient error due to Description unstable channel or heavy traffic. The controller will resume normal operations of the chip after reset; however, this could result in performance drop of the LUNs exported to the host ports of this chip.
Appendix SAS • Hosts Event ID 0x300c Type HOST Message Host x detected on host port y Description The controller detected host x on host port y. The host can start access the controller over the host port. Advice None Severity INFO Parameters Host WWPN, Host Port ID • Link Event ID 0x300d Type HOST Message Host port x phy y link up Description The link on the host port x phy y had been built by the controller successfully, and data transferring can be started.
Appendix • IO exceptions handling Event ID 0x300f Severity Host Port ID, WARNING Parameters Host WWPN, LUN ID Type HOST Message Task abort on host port x from host y to LUN z The controller received task abort on host port x from host y to LUN z. This could be to recover from a transient error due to Description unstable channel, command time-out, or unexpected host behaviors.
Appendix Event ID 0x3012 Severity ERROR Host ChanParameters nel ID, Controller ID, Error Code Type HOST Message Host channel x in controller y PCI Error: z Description The controller y has detected error in the host channel. Advice Check if the power supply is stable. Contact local sales or support office. Event ID 0x3013 Type HOST Message IOC Bus Reset on port x Severity WARNING Parameters Host Port ID Description A bus reset has occurred on port x that was initiated by the IOC.
Appendix SCSI • IO exceptions handling Event ID 0x3015 Type HOST Host Port ID, Severity WARNING Parameters Host SCSI ID, LUN ID Message Task abort on host port x from host y to LUN z The controller received task abort on host port x from host y to LUN z. This could be to recover from a transient error due to Description unstable channel, command time-out, or unexpected host behaviors.
Appendix Event ID 0x3019 Type HOST Message Host port x detected parity error during Command phase Severity WARNING Parameters Host Port ID Description Parity error was detected during command phase. Advice None Event ID 0x301a Type HOST Message Host port x detected parity error during Data Out phase Severity WARNING Parameters Host Port ID Description Parity error was detected during data out phase.
Appendix Event ID 0x301e Type HOST Message Host port x too much write data Description More than the expected amount of write data was received from the initiator. Advice None Event ID 0x301f Type HOST Message Host port x IU too short Description A received information unit was shorter than the value allowed by the protocol specification.
Appendix • Port and chip Event ID 0x3023 Type HOST Message IOC Bus Reset on port x Severity WARNING Parameters Host Port ID Description A bus reset has occurred on port x that was initiated by the IOC. Advice None Event ID 0x3024 Type HOST Message Ext Bus Reset on port x Description A bus reset has occurred on port x that was initiated by an external entity.
Appendix Event ID 0x302c Type HOST Message iSNS server x port y added Severity INFO Parameters IP Address, Port Number Parameters IP Address, Port Number Description iSNS server x port y was added Advice Event ID 0x302d Type HOST Message iSNS server x port y removed Severity INFO Description iSNS server x port y was removed Advice Event ID 0x302e Type HOST Message Bond port x created Severity INFO Parameters Bond Port ID Description Bond port x was created Advice Event ID 0x302f
Appendix Event ID 0x3031 Type HOST Initiator Severity INFO Parameters Name, Target ID Message Initiator x log off target y Description The controller detected Initiator x log off target y. Advice If initiator quitted unexpectedly, or it happens continuously during host access, check the host connectivity, or contact local sales or support office. D.
Appendix Event ID 0x2422 Type CONTROLLER Message Secondary system flash in controller x is corrupt Description The secondary system flash chip on controller x is corrupt and cannot be used. But the primary flash still works. Advice Check if there are any hardware hazards that lead to abnormal flash corruption. Watch the secondary flash chip.
Appendix Event ID 0x2425 Type CONTROLLER Message Bad block on primary system flash over 70% in controller y Description The amount of bad blocks is over 70% of the table that is used to remap bad blocks. Advice Check if there are any hardware hazards that lead to bad blocks. This flash chip is close to fail.
Appendix D.6 Enclosure • Temperature Event ID 0x2800 Severity NOTICE Sensor ID, Enclosure ID, Parameters Temperature Type ENCLOSURE Message Temperature at sensor x in enclosure y back to normal (z c) Temperature at sensor x in controller back to normal (z c) Description The temperature at sensor x in enclosure y or controller returned to normal working temperature range, right now is z ºC. Advice If the temperature is very unstable, contact local sales or support office.
Appendix • Fan Event ID 0x2804 Type ENCLOSURE Message Rotation speed of fan x in enclosure y back to normal Description The rotation speed of fan x in enclosure y returned to normal range. Advice If the rotation speed is very unstable, replace the fan, or contact local sales or support office. Event ID 0x2805 Type ENCLOSURE Message Abnormal rotation speed of fan x in enclosure y detected or the fan have remove.
Appendix Event ID 0x2809 Type ENCLOSURE Message +12V voltage source in backplane back to normal (z V) +12V voltage source in controller back to normal (z V) Description +12V voltage source in backplane or controller returned to normal range, right now is zV. Advice If the voltage is very unstable, contact local sales or support office. Event ID 0x280a Type ENCLOSURE Message Abnormal +3.3V voltage source in backplane (z V) Abnormal +3.
Appendix Event ID 0x2821 Type ENCLOSURE Message Voltage source x in enclosure y back to normal Severity NOTICE Parameters Voltage, Enclosure ID Description Voltage source x in enclosure y returned to normal range. Advice If the voltage is very unstable, contact local sales or support office.
Appendix • BBM Event ID 0x280f Type ENCLOSURE Message BBM disabled Severity INFO Parameters Description The battery backup function was disabled. Advice None Event ID 0x2810 Type ENCLOSURE Message Dirty boot and flush data Description The controller was not properly shutdown and it will flush cached data in memory protected by BBM.
Appendix Event ID 0x2814 Type ENCLOSURE Message BBM in controller x absent Severity WARNING Parameters Controller ID Description The controller x cannot detect BBM. Advice Check if the BBM is properly installed or replace with a new BBM. Event ID 0x2815 Type ENCLOSURE Message Temperature of BBM in controller x back to normal Description The temperature of BBM in controller x returned to normal working temperature range.
Appendix • UPS Event ID 0x2817 Type ENCLOSURE Message UPS connection detected Severity INFO Parameters Description UPS detected by the controller. Advice None Event ID 0x2818 Type ENCLOSURE Message UPS connection loss Severity WARNING Parameters Description The controller cannot detect UPS. Advice Make sure that the proper communication cable is securely connected to the UPS.
Appendix Event ID 0x281c Type ENCLOSURE Message UPS battery back to normal Severity INFO Parameters Description UPS battery charge back to normal range. Advice None Event ID 0x281d Type ENCLOSURE Message UPS battery will fail Severity WARNING Parameters Description The UPS has a battery that will fail. Advice Replace the UPS battery as soon as possible.
Appendix Event ID 0x2820 Type ENCLOSURE Message UPS overload solved Severity INFO Parameters Description The UPS overload solved.
Appendix Event ID 0x2401 Type SYSTEM Message RAID configurations on all disks erased Description RAID configurations stored on all disks were erased. All RAID configurations are lost. Advice Restart the controller so that all disks can be re-initialized all together. Event ID 0x2415 Type SYSTEM Message NVRAM configurations restore to default Description The controller configurations stored on NVRAM were erased and restored to factory default.
Appendix Event ID 0x2431 Type SYSTEM Message NVRAM mapping table on controller x checksum error Severity FATAL Parameters Controller ID The checksum stored on NVRAM cannot match the contents on the NVRAM. This could happen during the controller is not propDescription erly shutdown. System will restore default the default mapping table automatically Advice Start to monitor more carefully the status of the NVRAM.
Appendix Event ID 0x240e Type SYSTEM Message Service login Severity INFO Parameters Description Service login to the controller. Advice None Event ID 0x2411 Type SYSTEM Message Service login failed Severity INFO Parameters Description Service failed to login to the controller. Advice Check if there is any unauthorized trial access to the controller. Event ID 0x240f Type SYSTEM Message Accusys login Severity INFO Parameters Description Accusys login to the controller.
Appendix Event ID 0x0401 Type SYSTEM Message Event test with severity: error Severity ERROR Parameters Users have generated a simulated event to test the event han- Description dling/notification mechanisms. The severity level of this event is error. Advice None Event ID 0x0402 Type SYSTEM Message Event test with severity: warn Severity WARNING Parameters Users have generated a simulated event to test the event hanDescription dling/notification mechanisms.
Appendix Event ID 0x2413 Type SYSTEM Message Auto-write-through activated Severity NOTICE Parameters The pre-defined triggering events for auto-write-through Description occurred, and the controller has set the buffer cache as writethrough. Advice Check the event logs, and remove the causes of events that trigger auto-write-through.
Appendix • Firmware update Event ID 0x2407 Type SYSTEM Message System firmware in controller x updated Severity INFO Parameters Controller ID Description System firmware in controller x was updated successfully. Advice Restart the controller so that the new firmware can be effective. Event ID 0x2408 Type SYSTEM Message Controller x failed to update system firmware Severity INFO Parameters Controller ID Description The controller x cannot update the system firmware.
Appendix Event ID 0x2450 Type SYSTEM Message Firmware version are not the same Description Firmware version are not the same, only one controller will be startup Advice Check firmware version of both controller, and update the wanted firmware to another controller Severity WARNING Parameters • Email (SMTP) server status Event ID 0x240b Type SYSTEM Message Controller x failed to send mail Description The controller failed to send mail.
Appendix Event ID 0x2433 Type SYSTEM Message The RAID system was started in non HA mode Description If single controller boot at booting phase, the system will be non high availability mode Advice None Event ID 0x2434 Type SYSTEM Message The RAID system was started in HA mode Description If dual controller boot at booting phase, the system will be high availability mode Advice None Severity INFO Severity INFO Parameters Parameters • Miscellaneous Event ID 0x240c Type SYSTEM Mess
Appendix Event ID 0x2451 Type SYSTEM Message Enclosure serial number are not the same Description Enclosure serial number are not the same, only one controller will be startup Advice Check Enclosure serial number of both controller, and update the wanted serial number to another controller Event ID 0x2829 Type SYSTEM Message BBM optional are not the same Severity WARNING Parameters Severity WARNING Parameters Description BBM optional are not the same, only one controller will be startup A
Appendix Event ID 0x2438 Type SYSTEM Message Enclosure serial number in controller x updated by controller y Severity INFO Parameters During fail-back, if enclosure serial number of returning controller Description x is not the same as controller y.
Appendix Event ID 0x243d Type SYSTEM Message The PLD version of the returning controller is not the same. Severity WARNING Parameters Description The PLD version of the returning controller is not the same. Advice Contact local sales or support office. Event ID 0x243f Type SYSTEM Message Connected expansion or disk numbers of the returning controller. Description During fail-back, detected expansion or disk numbers of the returning controller is not the same.
Appendix D.8 Network • Network Event ID 0x3400 Type NETWORK Message Link up on network interface ethx Description The network link on network interface ethx had been built successfully. Advice None Event ID 0x3401 Type NETWORK Message Link down on network interface ethx Severity INFO Severity NOTICE Parameters Ethernet ID Parameters Ethernet ID The network link on network interface of ethx had been turned Description down.
Appendix • iSCSI port Event ID 0x3404 Type NETWORK Message Link up on iSCSI port ispx Severity INFO Parameters iSCSI port ID Description The network link on iSCSI port ispx had been built successfully Advice None Event ID 0x3405 Type NETWORK Message Link down on iSCSI port ispx Severity NOTICE Parameters iSCSI port ID The network link on iSCSI port of ispx had been turned down.
Appendix D.9 Miscellaneous • Event subscribe Event ID 0x3800 Type MISC Message Send message to x port y failed Severity NOTICE Parameters IP Address, Port Number Description Send a message a specify registrant is failed. Advice None Event ID 0x3801 Type MISC Message Registrant x port y is kicked Severity NOTICE Parameters IP Address, Port Number Description The registrant is kicked. Advice None D.
Appendix Event ID 0x3C02 Type SNAPSHOT Message VVOLx created Severity INFO Parameters VVOL ID Description Snapshot volume vvox was created. Advice None Event ID 0x3C03 Type SNAPSHOT Message VVOLx deleted Severity INFO Parameters VVOL ID Description Snapshot volume vvox was deleted. Advice None Event ID 0x3C04 Type SNAPSHOT Message Secondary volume x is out of free space Severity ERROR Parameters Secondary volume All space of the secondary volume was occupied.
Appendix Event ID 0x3C08 Type SNAPSHOT Message Spare COW volume x is added. Severity INFO Parameters Spare COW volume Parameters Spare COW volume Description Spare COW volume x was added. Advice None Event ID 0x3C09 Type SNAPSHOT Message Spare COW volume x is removed. Severity INFO Description Snapshot volume pair x was removed. Advice None Event ID 0x3C0B Type SNAPSHOT Primary vol- Severity INFO Parameters ume, Snapshot volume Message Primary volume x is restoring to SVOL y.
Index Index A accessing the RAID GUI 2-1 add LUNs in host 2-39 add LUNs in storage group 2-41 array recovery 2-52 faulty 2-52 optimal 2-52 partition state transition 2-53 array roaming 2-51 auto logout setting 2-72 auto spare 2-55 auto write-through cache 2-67 automatic resume 2-48 AV streaming 2-19 B background task messages 3-4 bad block alert setting 2-57 bad block clone setting 2-58 beeper alarm 6-1 beeper control 2-67 bind host/host group and storage group 2-42 boot utility C-1 set IP address C-2 set
Index telnet, and SSH B-15 web-based GUI B-14 web-based GUI over PPP B-15 IO queue, NCQ 2-58 J JBOD creating 2-23 creating volume pair 2-24 deleting 2-23 JBOD, defined A-12 spanned disk array without fault tolerance A-12 L language 2-1 LCD console background task messages 3-4 creating a RAID array 3-6 emergent info 3-4 ethernet setting 3-7 hotkeys 3-5 status info 3-3 terminal port setting 3-7 LCD manipulation procedure 3-1 LD read algorithm check on read 2-30 fast read response 2-30 intelligent data compu
Index R RAID 0, defined A-3 striped disk array without fault tolerance A-3 RAID 1, defined A-4 mirroring A-4 RAID 10, defined A-8 high reliability setup combined with high performance A-8 RAID 3, defined A-5 parallel transfer with parity A-5 RAID 30, defined A-9 byte striping with parity combined with block striping A-9 RAID 5, defined A-6 independent data disks with distributed parity blocks A-6 RAID 50, defined A-10 block striping with distributed parity combined with block striping A-10 RAID 6, defined
Index SSL forced setting 2-73 status info 3-3 storage provisioning 2-36 selective storage add hosts 2-41 add LUNs in storage group 2-41 bind host/host group and storage group 2-42 remove hosts 2-41 remove LUNs in storage group 242 unbind hosts/ host groups and storage groups 2-42 simple storage add LUNs in a storage port 2-36 remove LUNs in storage port 2-38 symmetric storage add hosts 2-38 add LUNs in host 2-39 remove hosts 2-39 remove LUNs from host 2-40 Symmetric MPIO (multi-path IO) 2-38 restrictions 2
