JanusRAID II Generic Software Manual U320 SCSI to SATAII 4G Fibre to SAS SAS to SAS iSCSI to SAS Disk Array Systems Version 1.
U320 SCSI to SATA II 4G Fibre to SAS SAS to SAS iSCSI to SAS Model: SA-8850S, SA-4551S, SA-6651S, SA-6651E, SS-4551E, SS-4552E, SS-6651E, SS-6652E, SS-4501E/R, SS-6601E/R, SS-8801E/R, TS-4801R, SS-4502E/R, SS-6602E/R, SS-8802E/R, SS-4503E/R, SS-6603E/R JanusRAID II Generic Software Manual
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.
Contents 2.7.12 Array roaming .............................................................................................................. 2-51 2.7.13 Array recovery ............................................................................................................. 2-52 2.7.14 Schedule task .............................................................................................................. 2-54 2.7.15 Cache Configurations ................................................................
Contents 4.1.1 Embedded CLI ................................................................................................................. 4-1 4.1.2 Conventions Overview ..................................................................................................... 4-6 4.2 Basic RAID Management ......................................................................................................... 4-7 4.2.1 Hard disks ................................................................................
Contents 4.9.1 Configurations management .......................................................................................... 4-34 4.9.2 Time management ......................................................................................................... 4-35 4.9.3 Administration security control ....................................................................................... 4-36 4.9.4 System information ......................................................................................
Contents 5.6.7 RAID System Registration ............................................................................................. 5-67 5.6.8 RAID System Monitoring ............................................................................................... 5-71 5.6.9 Configuring MSN Event Notification .............................................................................. 5-72 5.7 VDS Provider .....................................................................................................
Contents C.4 (S) Update System ROM ........................................................................................................ C-4 C.5 (H) Utility menu ....................................................................................................................... C-5 C.6 (P) Set password .................................................................................................................... C-5 C.7 (R) Restart system ..........................................................
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 xv 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) ....................................................
Contents Figure 5-7 Redundant Single MPIO host (quad channel) .................................................... 5-27 Figure 5-8 Redundant Dual Independent MPIO hosts ......................................................... 5-29 Figure 5-9 Dual clustering MPIO hosts ................................................................................ 5-31 Figure 5-10 Active-Passive Redundant Single MPIO host ....................................................
Contents Figure A-7 RAID 30 disk array ...............................................................................................A-9 Figure A-8 RAID 50 disk array .............................................................................................A-10 Figure A-9 RAID 60 disk array .............................................................................................A-11 Figure A-10 JBOD disk array ...................................................................................
Preface About this manual Congratulations on your purchase of the product. This controller allows you to control your RAID system through a userfriendly 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.
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 1.2 Key Features • Basic RAID Construction • Multiple RAID levels: 0, 1, 3, 5, 6, 10, 30, 50, 60, JBOD, and NRAID • Multiple stripe sizes (KB): 4, 8, 16, 32, 64, 128, 256, and 512.
Introduction • Online simultaneous disk group expansion and defragmentation • Online logical disk capacity expansion • Online logical disk capacity shrink • Support rebuild-first policy for early recovery from RAID degradation • Data Integrity Maintenance Utilities • Online logical disk parity regeneration • Online disk scrubbing (a.k.a.
Introduction • Host Interface Functions (model-dependent) • Support 4Gb/s Fibre Channel host interfaces (FC-SAS/SATA controller) • Support 3Gb SAS host interfaces (SAS-SAS controller) • Support Ultra320 SCSI host interfaces (SCSI-SATA controller) • Support T11 SM-HBA attributes statistics • Support multiple-path IO (MPIO) solutions • 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 AP
Introduction • Support password reminding email • Time management by RTC and Network Time Protocol (NTP) with DST • Support controller firmware upgrade (boot code and system code) • Support dual flash chips for protecting and recovering system code • Support object naming and creation-time logging Note The features may differ for different RAID system models and firmware version. You may need to contact your RAID system supplier to get the updates. 1.
Introduction 1.4 RAID Structure Overview The storage resources are managed as storage objects in a hierarchical structure. The hard disks, the only physical storage objects in the structure, are the essence of all other storage objects. A hard disk can be a JBOD disk, a data disk of a disk group, or a local spare disk of a disk group. It can also be an unused disk or a global spare disk.
Introduction 1.5 User Interfaces to Manage the RAID System A variety of user interfaces and utilities are offered for managing the RAID systems, and you may choose to use one or multiple of them that suit your management purposes. Introduction to these interfaces and utilities is described as below: • Web-based GUI (chapter 2) Web-based GUI is accessed by web browsers after proper setup of the network interfaces.
Introduction • Configuring the hardware settings and doing health check After installing your RAID systems with necessary components, like hard disks and transceivers, to your environment, enabling the user interfaces is a prerequisite if you want to do anything useful to your RAID systems. The only user interface that you can use without any tools is the LCD console, by which the settings of the RS232 port and the management network interface can be done to allow you to use the GUI and CLI (see 3.
Introduction Data integrity assurance For better system reliability, you are advised to set policies for handling exceptions, like to start disk cloning when SMART warning is detected or too many bad sectors of a hard disk are discovered (see 2.8.1 Hard disks on page 2-38), or to turn off write cache when something wrong happens (see 2.9.5 Miscellaneous on page 2-47). You may also schedule periodic maintenance tasks to do disk scrubbing(see 2.7.
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 • Firefox language settings Here is an example of how to change the GUI language settings in Firefox. 1. Open the Firefox browser and select Tools > Options > Advanced > General tab. 2. Click the Choose... button to specify your preferred language for the GUI to display. Figure 2-2 Setting the language in Firefox 3. The following Languages dialog displays. To add a language, click Select a language to add..., choose the language, and click the Add button.
Using the RAID GUI 2.1.2 Multiple System Viewer The RAID GUI features a side button for a quick on-line system view. The side button is always on the left side of the screen so that you can click to view all the other on-line systems at anytime. Move the cursor over the side button and the multiple system viewer appears (see Figure 2-5).
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 Button Description 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. 2.2.1 HDD state Through the front panel of the RAID console displayed in the GUI, you can easily identify the status of each hard disk by its color and status code.
Using the RAID GUI 2.2.2 Information icons When components are working normally, their icons are shown in green. When components are uninstall, not norms or, failed, the icons are shown in red. Click on each icon for detailed information. Icon Name Detailed Information Event log view • Seq. No. • Severity • Type • Time • Description Beeper See 6.2 Beeper on page 6-1 for the possible beeper reasons.
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, 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 Redundant and Upgradable RAID system A A A Controller B Controller A C B B D D 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-8
Using the RAID GUI A A A C Controller A B D B ispa4 (left)/ispa3/ispa2/ispa1 (right) A A A C Controller A 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 Ethernet port • IP Address • Network Mask • Gateway • DNS Server • MAC Address C Table 2-5 Components at the rear side
Using the RAID GUI 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 iSCSI ports • iSCSI ID • IP address • Network Mask • Gateway • MAC Address • Jumbo Frame • Link Status G Table 2-5 Components at the rear side of the system 2.2.4 Login Figure 2-12 Login section The RAID GUI provides two sets of default login members.
Using the RAID GUI 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. Each redundant / upgradable system provides two SAS expansion ports to connect with one or more SAS JBOD chassis.
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 2.3.3 Monitor mode When SAS JBOD chassis are connected, the enclosure tabs will appear in the Monitor Mode (see Figure 2-16). 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 Voltage • Sensor • Current • High Limit • Low Limit Fan module • BP_FAN1 • BP_FAN2 • BP_FAN3 • BP_FAN4 Power supply • POW1 • POW2 Table 2-8 Information icons (in SAS monitor mode) 2.3.5 SAS/SATA HDD information Through the hard disk codes and tray color shown on the screen, you can easily identify the status of each connected SAS/SATA hard disk. Click on each SAS/SATA hard disk to display detailed information.
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 • Redundant-controller RAID configuration Two volumes (for raid30, raid50, or raid60) or two logical disks (for other RAID levels) will be created with all capacity of all disks in the RAID enclosure. One volume will be based on two disk groups, so totally there will be four disk groups. The preferred controller of one volume or logical disk is assgined to controller A and the other is assigned to controller B. They will be mapped to LUN 0 and LUN 1 of all host ports on both controllers.
Using the RAID GUI 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. If a hard disk belongs to a disk group, you cannot change its disk cache. To modify it, refer to 2.6.3 Disk groups. 3.
Using the RAID GUI • Modify JBOD disks To modify a setting, select a JBOD and click Modify. Specify the following options for configuration. Name Type a name for the JBOD ID. Preferred Controller This option is only available when the redundant-controller system is in use. Select the preferred controller to be in charge of managing and accessing the JBOD disk. However, the controller ownership will not change unless you check the ‘Change owner controller immediately’ box.
Using the RAID GUI Capacity to Truncate (GB) LD Initialization Mode Specifies the capacity to be truncated for the smallest disk of this disk group. This option is useful when the replacement disk that is slightly smaller than the original disk. Without this option, the capacity to truncate is 0GB. The initialization mode defines how logical disks of a disk group are initialized. Different disk groups can have different initialization modes.
Using the RAID GUI Note 1. Progress rates increase in proportion to priority (i.e. A high priority task runs faster than a low priority one.) 2. When there is no host access, all tasks (regardless of priority) run at their fastest possible speed. 3. When host access exists, tasks run at their minimum possible speed. • Detailed disk group information Click to display a complete list of disk group information. You will see the following details.
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 • Detailed logical disk information Click to display a complete list of logical disk information. You will see the following details. • DG ID • Write Cache Setting • LD ID • Write Sorting • UUID • Read Ahead Policy • Created Time and Date • Read Ahead Multiplier • LD Read Algorithm • Read Logs • Alignment Offset (sector) • Member State • Write Cache Status 2.6.5 Volumes This feature allows you to create, delete, and modify your volume settings.
Using the RAID GUI • 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 redundant-controller system is in use. Select the preferred controller to be in charge of managing and accessing the volume. However, the controller ownership will not change unless you check the ‘Change owner controller immediately’ box.
Using the RAID GUI • Delete snapshot volume pairs Select the snapshot volume pair(s) you want to delete and click Remove. • 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.
Using the RAID GUI SVOL ID Select a snapshot volume ID from the drop-down menu. PV ID Select a primary volume ID from the drop-down menu. Name Use the system default name as svolx. ‘x’ is the VOL identifier. OR Uncheck the ‘Use system default name’ box and enter the name in the Name field. The maximum name length is 63 bytes. • Delete snapshot volumes Select the snapshot volume(s) you want to delete and click Delete. To delete all LUNs of svolx, check the ‘Force to delete LUN mapping(s)’ box.
Using the RAID GUI Add LUNs in a storage port In the simple storage main screen, click Add to add a LUN to the default storage group of an FC port/ SAS port/SCSI port/iSCSI port, fcpx/sasy/scpz/isp, with a virtual disk. 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.
Using the RAID GUI Add hosts In the symmetric storage main screen, click Host > Add. Host ID Select a Host ID from the drop-down menu. A maximum of 32 hosts can be added to the controller. WWPN Each FC port needs a WWPN for communicating with other devices in an FC domain. Users can choose each WWPN of Fiber HBA from the ‘Choose from detected hosts’ box or directly enter the WWPN in this field.
Using the RAID GUI • Selective method Selective storage is used in complicated SAN environments, where there are multiple hosts accessing the controller through an FC switch. This method provides the most flexibility for you to manage the logical 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.
Using the RAID GUI Mapping Virtual Disk Select a virtual disk from the drop-down menu for LUN mapping. Mask Status Unmask / Mask This option makes a LUN available to some hosts and unavailable to other hosts. Access Right Read-only / Read-writable The access right is applied to individual LUNs in a storage group. Sector Size 512Byte / 1KB / 2KB / 4KB Select a sector size from the drop-down menu as the basic unit of data transfer in a host.
Using the RAID GUI 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.2 Defragmenting disk groups Except defragmenting disk groups during expansion, there is another way to perform the task. 1.
Using the RAID GUI * Where “Nn” means the number of member disks in the new RAID level, “No” means the number of member disks in the original/old RAID level, “OK” means the migration is always possible, and “N/A” means the migration is disallowed. Stripe Size (KB) This option must be specified when migrating from a non-striping-based RAID level to a striping-based RAID level. Schedule Immediately: The task will start immediately. Once: The task will start on the specified date and time.
Using the RAID GUI Note It is advised that the file systems on the host be shrunk before shrinking the logical disks; otherwise shrinking might cause data loss or file system corruption. 3. Click Apply to view the current settings. 4. Click Confirm. The task starts. 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.
Using the RAID GUI 2.7.8 Cloning hard disks When a hard disk is likely to become faulty or develop errors, for example, when the number of reported errors or bad sectors of a physical disk increases over a certain threshold, or a disk reports SMART warning, you can copy all the data on the disk to another disk. To clone a hard disk, do the following: 1. Select Maintenance Utilities > HDD Clone from the main menu. 2. Click Clone and specify the following disk cloning options.
Using the RAID GUI Schedule Immediately: The task will start immediately. Once: The task will start on the specified date and time. Weekly: The task will start on the specified day and time every week. Monthly: The task will start on the specified date and time every month. 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.
Using the RAID GUI To stop the DST of a hard disk, select it and click Stop. A confirmation prompt displays. Click Confirm to end the DST. Note 1. 2. 3. 4. 5. 6. 7. Hard disks must support DST. Hard disks must not be executing DST. For ATA disks, the SMART must be turned on. For ATA disks, if SMART is turned off during DST execution, DST will be aborted. During DST execution, accessing the hard disks may lead to performance degradation.
Using the RAID GUI • Partition state transition The corresponding events and state transitions of a partition are shown in the table below: From To Disk is failed or removed. OPTIMAL FAULTY: for faulty logical disk BANISH: for degraded logical disk REBUILD BANISH UNTRUST BANISH Lost member disk is replaced by a new disk for disk rebuilding. FAULTY UNTRUST (The logical disk is not recoverable.) BANISH UNTRUST (and later to REBUILD) Lost member disk is restored to a disk group by the ARU.
Using the RAID GUI 2.7.14 Schedule task The DG reconfiguration, LD reconfiguration, disk cloning, disk scrubbing, and DST scheduled tasks are listed in the Schedule Task section. When the scheduled date and time is met, the controller will start the specified tasks. Note The controller will try to launch commands according to the schedule. However, if the command cannot be executed at that moment, the controller will not retry. To cancel a scheduled task, select it and click Delete.
Using the RAID GUI Note Hard disks with configurations that conflict with controller configurations are not imported and enter conflict state. On-line Array Roaming Control: On / Off (default) On: The controller will try to keep the disk in the foreign state if hard disk contains valid meta-data. However, if the disk fails to import successfully, it will enter the conflict state. Off: All on-line installed disks are perceived as new disks and enter unused state. Meta-data on the disk is cleared and reset.
Using the RAID GUI This option specifies the transfer speed of a hard disk. When Auto is specified, the transfer speed is determined by the controller according to the best transfer mode supported by the installed hard disks.The option is available only for RAID controller with SATA disk interface. Bad Block Alert: On / Off (default) This option enables or disables event alerts for bad block reallocation.
Using the RAID GUI 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. For SCSI ports including each port’s ID, name, default SCSI ID and data rate.
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 • Create an iSCSI target 1. Click Create to open the configurations window, specify the following options: IST ID Specifies an iSCSI target identification. The maximum number is 8. Name Specifies an IQN name. The maximum length of the name is 223. Alias Specifies an Alias name. The maximum length of the alias name is 63. Auth.Method None / CHAP Target Binding Port Select the ISP ports bound to target. 2.
Using the RAID GUI • 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.9 Event Management Event Management enables or disables event notifications. When an event is detected, the controller will alert you by the specified notification methods. All the events will be recorded in the controller. You are allowed to erase and download the log, and send a test email of events. 2.9.1 Setting up the SMTP The controller can notify you when an event occurs by sending a mail to the specified user account. Specify the following options for event configurations.
Using the RAID GUI 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. Server Address: IP Address / Domain Name Set up the IP address or the domain name of the SNMP server.
Using the RAID GUI 4. Set Agent's Charset to IS0-8859-1 (Choose Tools > Options > General). Note Before the manager application accesses the RAID controller, user needs to integrate the MIB into the management application’s database of events and status indicator codes. This process is known as compiling the MIB into the application. This process is highly vendor-specific and should be well-covered in the User’s Guide of your SNMP application.
Using the RAID GUI 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. Send a Test Mail Click Configure and specify the Severity of testing event option to send a test mail. A testing event record will be generated according to the selected severity level.
Using the RAID GUI This option enables or disables the auto write-through function for the following four types of events. 1. Controller Failure 2. Battery Backup Module Failure 3. Power Supply Unit Failure 4. Fan Failure 5. UPS Failure When events are detected with a specified type, both the cache on the controller and disk will be automatically set as write-through. After the failure or warning condition is removed, the cache settings will be restored to your original configuration.
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 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. (For the redundant-controller system only) From the Controller drop-down menu, select the desired controller for the following network settings to apply. 3.
Using the RAID GUI 2.10.4 System Time • Setting up the Time Time is required for the controller to record events and to schedule maintenance tasks. There are two time modes for selection, static and NTP settings. For network settings, do the following: 1. Select System Management > Time from the main menu. 2. From the Time Mode drop-down menu, select either static or NTP. • If you select the static mode, specify the date and time. The data and time is set in form as MM/DD/YY and hh/mm.
Using the RAID GUI 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 Note 3. For external enclosure firmware option, you can check the ‘Apply’ to all external enclosure' option to apply the updating to all external enclosure at the same times. 3. After updating the firmware for external enclosures, it requires to restart both the controllers for the RAID system and all external enclosures. 4. The RAID controller supports redundant flash chip for system firmware. Primary chips will be updated first and the secondary chips later.
Using the RAID GUI 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.3 LUN This feature allows you to enable, disable, or reset LUN IO logging. When LUN IO logging is enabled, the following IO statistics of a LUN (depending on the storage presentation method selected) will be displayed. You can press the Reset button to clear all statistics except outstanding IO to zero.
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 • Second since last reset • NOS Count • TX/RX Frame • Error Frame • Dumped 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 Status Info Message Note Controller voltage +3.3V [A] 3.3V: xx.xx Controller voltage +5V [A] 5.0V: xx.xx 3.3V, 5V, and 12V status on controller A or B Controller voltage +12V [A] 12.0: xx.xx * [A] denotes controller A; [B] denotes controller B. BP voltage +3.3V [BP] 3.3V: xx.xx 3.3V, 5V, and 12V status on backplane BP voltage +5V [BP] 5.0V: xx.xx BP voltage +12V [BP] 12.0: xx.xx Expansion voltage sensor[x] VOLT#x: xx.
Using the LCD Console 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 Consolel 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 Console 3.3.4 Terminal Port Settings To configure the settings of terminal port, enter the Terminal Port menu. Specify the following items one by one. Baud Rate 2400, 4800, 9600, 19200, 38400, 57600, 115200 (default) Stop Bit 1 (default), 2 Data Bit 7, 8 (default) Parity NONE (default), ODD, EVEN Flow control OFF (default), H/W Use the UP and DOWN buttons to scroll through the options. Press the ENT button to select it.
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 Controller modifier In a dual-controller system, hardware such as the host interface ports is exactly the same on the two controllers. To specify which controller the hardware to be selected in CLI, a controller modifier is added. For example, to refer to the first FC port in controller A, the identifier is °ßfcpa1°®. Without the modifier, all identifiers are referring to local controller (the controller that user logs in currently).
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 [-i par/seq]: logical disk initialization mode (parallel or sequential) Parameters [-z]: write-zero immediately [-s hddz,hdda, ...
Using the CLI Commands Command autospare Synopsis autospare [on/off] Description Review or set the auto spare settings. Parameters [on/off]: turn on or off the auto spare option Command restorespare Synopsis restorespare [on/off] Description Review or set the restore spare settings. Parameters [on/off]: turn on or off the restore spare option 4.2.
Using the CLI Commands Command checkonread Synopsis checkonread dgxldy/all on/off Description Enable or disable check-on-read for all RAID 3/5/6 logical disks. Command writelog Synopsis writelog [on/off] Description Review or set the write logging. Parameters [on/off]: enable or disable write logging 4.2.7 Volumes Command volcreate Synopsis volcreate volx dgxldy dgildj ...[-s stripesize] [-o sector] [-n name] [-c ctlx] Description Create 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 Command ldexpand Synopsis ldexpand dgildx newcapacity [-i initopt] [-f x,y] Description Expand the capacity of one or more logical disks in a disk group. newcapacity: new capacity of a logical disk Parameters [-i initopt]: initialization method [-f x,y]: free chunks Command ldshrink Synopsis ldshrink dgildx newcapacity Description Shrink the capacity of a logical disk.
Using the CLI Commands Command regparity Synopsis regparity dgx/dgxldy Description Regenerate the parity of a logical disk or the logical disks of disk group with parity-based RAID level. Command regparitystop Synopsis regparitystop dgxldy/dgx Description Stop regenerating parity of a logical disk or the logical disks of disk group with parity-based RAID level. 4.3.
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 4.3.7 Array recovery utilities Command dgrecover Synopsis dgrecover dgx hddx hddy ... [-f member_id] Description Recover a faulty disk group. Parameters [-f member_id]: force to recover disk Command ldrecover Synopsis ldrecover dgxldy partition_id Description Recover a faulty logical disk. Command volrecover Synopsis volrecover volx dgildj dgxldy ... Description Recover a faulty volume. 4.4 Storage Presentation 4.4.
Using the CLI Commands Command hgname Synopsis hgname hgx name Description Name a host group. Command hglist Synopsis hglist hgx/all Description List one or all host groups. 4.4.3 Storage groups Command sgaddlun Synopsis sgaddlun sgx/fcpx/sasx/scpx jbdy/dgyldz/voly/vvoly [-l lunz] [-s 512b/1kb/2kb/4kb] [-g cylinder head sector] [-w wt/wb] Description Add a LUN in a storage group or a default storage group.
Using the CLI Commands Command sglistlun Synopsis sglistlun sgxluny/fcpxluny/sasxluny/scpxluny/sgx/fcpx/sasx/scpx/all Description List LUN information in one or all storage groups / default storage groups. 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.
Using the CLI Commands 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 Command Synopsis Description hddsmart hddsmart on [-p period] [-a clone/alert] hddsmart off Change the SMART warning settings of all hard disks. on/off: SMART control Parameters [-p period]: period of SMART polling [-a clone/alert]: SMART actions Command hddsmartlist Synopsis hddsmartlist all/hddx hddy hddz … Description List SMART information and current status of the specified or all hard disks.
Using the CLI Commands Command hddretry Synopsis hddretry xx Description Specify the number of retries when a disk IO command fails. Command hddxfermode Synopsis hddxfermode mode Description Specify the transfer mode of hard disks in the enclosure. The possible values of mode are Auto(default), 1.5Gb,and 3Gb. Command hddqueue Synopsis hddqueue on/off Description Enable or disable the IO queuing of hard 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 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. Command fcplistusrconf Synopsis fcplistcurconf fcpx/all Description List the current configurations of an FC port or all FC ports. 4.5.
Using the CLI Commands Command ethssh Synopsis ethssh on/off Description Enables or disables the SSH service on all management network interface ports. Command ethweb Synopsis ethweb on/off Description Enables or disables the web service on all management network interface ports. Command ethapi Synopsis ethapi on/off Description Enables or disables the network based out-band API service on all management network interface ports.
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 Command chapusr Synopsis chapusr add/remove/update user_name[-s secret][-t all/x,y,...] Description Add, remove, or update an incomming CHAP user name and secret. The maximum chap user number is 8.
Using the CLI Commands Command iscsiaggregport Synopsis iscsiaggregport create method [-a ip_addr] [-s net_mask] [-g gw_addr][-m MTU_size][p all/x,y,...] iscsiaggregport delete iscsiaggregport update method [-a ip_addr] [-s net_mask] [-g gw_addr] [-m MTU_size] Description Create, deletes or updates an iSCSI aggregation target port with IP address and other network related setting.
Using the CLI Commands Command lunliststat Synopsis lunliststat sgxluny/fcpxluny/sasxluny/scpxidylunz/hgxluny/istxluny Description List LUN IO statistics. 4.6.4 Storage ports 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. Command sasstat Synopsis sasstat on/off/reset Description Enable or clear SAS port statistics.
Using the CLI Commands 4.7.3 Path failover alert delay Command foalertdelay Synopsis foalertdelay [xxmin] Description Set the delay period before the controller generates a warning event to notify users of the critical condition that virtual disks transferred to the non-preferred controller. 4.7.4 Controller fallover mode Command Failovermode Synopsis Failovermode mpio / mtid Description Sets the failover mode to Mutipath IO (mpio) or Multiple-ID (mtid).
Using the CLI Commands Command notifylist Synopsis notifylist smtp/snmp/all Description List the current settings of all or the selected notification method. Command eventmailrcv Synopsis Description eventmailrcv set rcvx receiver severity eventmailrcv reset rcvx Enable or disable the specified mail account for mail notification receiver.
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 confighdd Synopsis confighdd [frequency] Description Show or update the progress of background tasks except reconfiguration task. Parameters [frequency]: high, medium, or low 4.9.2 Time management Command dateset Synopsis dateset static/ntp [-t YYYY/MM/DD/hh/mm]/[-n xxx.yyy.zzz] Description Set the current date and time on the controller. Parameters Command Synopsis Description [-t YYYY/MM/DD/hh/mm]: date and time. This is valid only when static is specified.
Using the CLI Commands Command passwdchk Synopsis passwdchk user/admin [on/off] Description Review or set password checking for an account. Show or change the setting of password check for an account. Parameters [on/off]: enable or disable the password check 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.
Using the CLI Commands 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. • DRAM R/W test: The test will be conducted only once when controller is restarted. • FC loopback test: The test will be conducted immediately stops it or the controller restarts.
Using the CLI Commands Command ctldst Synopsis ctldst on/off Description Enable or disable the detailed self test of controller during start-up. Command diagdump Synopsis diagdump diag.bin [-p] Description Export extensive diagnostics information from the controller to a file. This command only works on local CLI run on the host computer and dosen’t work on remote CLI via telnet, SSH, or RS232.
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 Command svolcreate Synopsis svolcreate pdevice svolx [-n name] Description Create a snapshot volume. Parameters [-n name]:The name of a snapshot volume. Primary and secondary volume of snapshot volume pair must not be in faulty state. Restrictions All snapshot volume of the same primary volume must not be in the restoring state. There must be no existed svolx. 4-31 Command svoldelete Synopsis svoldelete svolx [-f] Description Delete 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 multipath IO software of the operating systems.
Advanced Functions If directly attaching the host-interface ports to the HBAs, you can easily know the number of paths for single virtual disk by counting the physical links. But if a switch is used to build a fabric, you need to multiply the number of HBA ports and the number of host-interface ports of the controller to derive the number of paths.
Advanced Functions 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 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 sys
Advanced Functions 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 • Check the MPIO disk status on the host computer After the MPIO driver has been installed, you can find the new multi-path disk device(s) (eg. ACS82410 Multi-Path Disk Device) and the Multi-Path Support displayed in the following screen: Computer Management > Device Manager.
Advanced Functions Category Display Device Name MPIO Disk name Available Path The available number of paths on the MPIO disk Host Name The host name or IP address of host where the MPIO device is located Serial Number The RAID controller model name and serial number Path Policy The path policy of the selected MPIO Disk Table 5-1 MPIO device information • Detailed MPIO device information Click • • to display a complete list of MPIO disk information. You will see the following details.
Advanced Functions 5.1.5 Linux Multi-Path Solution Native Linux multi-path I/O support has been added to the Linux 2.6 kernel tree since the release of 2.6.13, and has been back-ported into Red Hat Enterprise Linux 4 in Update 2 and into Novell SUSE Linux Enterprise Server 9 in Service Pack 2.
Advanced Functions 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. This not only installs the driver but also starts the multipathd service like the procedures described for the single-controller system. 2. To build a driver binary, follow the steps below: 2.1 Type rpm -ivh mpath-xxx-x.src-xxxx.rpm to install the source code package 2.2 Change working directory to /usr/src/packages/SPECS and type rpmbuild -bb mpath.spec 2.
Advanced Functions 4. You may also use multipath command to configure, list, and remove multi-path devices. 5. To add or remove LUNS, after completing the changes to the RAID system configurations, restart the service by typing service multipathd restart. Modifying the configuration needs also to restart the service to make the modifications effective. 6. If you’re running Linux cluster and need to have consistent multi-path device names, you need to use the alias option in multipath.
Advanced Functions 5.2 Multiple ID solutions 5.2.1 Overview The multiple ID mechanism provides host transparent controller failover/failback solution. That is, no particular software or driver is required to be installed at the host side. Howerver, a fiber switch is required. Through the connection of fiber switch, the fiber host chanel ports can provide backup for each other. ‘Fcpa1’ and ‘fcpb1’ can backup each other, so do ‘fcpa2’ and ‘fcpb2’.
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 preferr
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 • Failback State Update When the backup controller’s firmware version is different with the survival controller, the survival controller will automatically synchronize the firmware to the backup controller to make the two controllers with the same firmware version. The user needs to confirm the firmware update by pressing the button on the LCD panel to continue the automatic synchronization. • Normal State Update The normal state indicates that two controllers are normally in use.
Advanced Functions 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. The Configuration Tasks table shown below details each configuration task according to the example given in Figure 5-6.
Advanced Functions 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. The redundant paths of all LUNs are also established by mapping them across four fibre ports.
Advanced Functions • Active-Active Redundant Dual Independent MPIO Hosts As Figure 5-8 shows, the redundant RAID system is operating in a dual independent MPIO hosts environment using the selective storage method. All LUNs are formed into storage groups, used to bind the host groups across four fibre ports.
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 DG0LD1 > Specify the preferred controller as ctlb RAID Management > Logical Disks > Create DG1LD0 > Specify the preferred controller as ctla RAID Management > Logical Disks > Create DG1LD1 > Specify the prefe
Advanced Functions In this configuration, for DG0LD0, the two green solid path is the active path by controller A while the two red dotted path is the standby path by controller B; for DG1LD0, the condition is reversed. 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 The steps to set up the active-passive and active-active connections are almost the same. You simply need to specify all the LUNs to the same preferred controller in the RAID GUI. The Configuration Tasks table shown below details each configuration task according to the example given in Figure 510.
Advanced Functions Path Failback Across Controllers When any active path is restored, the MPIO driver routes the traffic back to the active path automatically. No user intervention is needed for the path failback process. • Controller Failover and Failback Scenarios When doing the controller failover and failback in the redundant-controller 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.
Advanced Functions Controller Failback If a system is in the controller failover mode, the survival controller will take over the failed controller’s job and process its own job. When a healthy replacement controller is installed, the system will proceed the failback process. The survival controller will return the failed controller’s job and sync all states and configuration to the failback controller. When the redundant mode is established, the heartbeat LED of the failback controller flashes.
Advanced Functions 5.4 Snapshot 5.4.1 Introduction Snapshot allows you to create instantaneous data images of a volume at designated points in time. Unlike traditional data copy, which takes hours or even days for data replication, depending on the size of the volume, the snapshot function can create a copy of a volume of any size within seconds.
Advanced Functions • Spare COW Volume When running out of the space of a secondary volume and there are spare COW volumes, the copied data of COW operations will be automatically redirected to an unused spare COW volume for the primary volume. The spare COW volume serves as a buffer to accommodate written data of size larger than planned and allows you to expand size of the secondary volume later.
Advanced Functions 5.4.3 How to Use Snapshots • Overview To make the most use of the snapshot function, proper planning and configuration is of essence. Below is a list of related tasks grouped into three phases: Phase 1: Planning 1. Identify the source volumes that need to have snapshots. 2. Define how many snapshots will be taken and how long they will exist. 3. Allocate the disk space and RAID attributes of the secondary volumes. 4. Allocate the disk space and RAID attributes of the spare COW volume.
Advanced Functions • Creating Snapshots using GUI or CLI After secondary volumes are chosen for the volumes need to have snapshots, you may create snapshots by the Web GUI or CLI commands. Detailed information about GUI and CLI can be found in 2.6.6 Snapshot Volumes on page 2-23 and 4.2 Basic RAID Management on page 4-2, respectively. On Windows, you may also use the host-side CLI utility, acs_snap.exe.
Advanced Functions • Snapshot Roaming The snapshot configurations are stored in the disks of the secondary volume. If “Auto Array Roaming Control” option is enabled please see 2.7.16 Miscellaneous on page 2-37, foreign hard disks with snapshot configurations can be automatically restored during the controller boo-up.
Advanced Functions • 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. You may use file system check utilities after the resizing for ensuring data integrity. Below list the software that offers solutions to support partition resizing: • Symantec Partition Magic : http://www.
Advanced Functions • Disk group expansion to expand the last existing free chunk All existing free chunks except the one at the end of the disk group are deleted, and the last free chunk is expanded.
Advanced Functions • 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 allocating an adjacent free chunk and moving logical disks If the free chunk right after the selected logical disk is not sufficient for expansion, the controller will allocate the free chunk and also start a background task to move logical disks. LD 0 LD 1 free chunk 0 LD 0 expand LD 1 LD 1 LD 2 free chunk 1 free chunk 1 DG DG Figure 5-23 Logical disk capacity expansion by allocating an adjacent free chunk and moving logical disks 5.5.
Advanced Functions • Disk group expansion to consolidate free chunks When disk group expansion is executed in a disk group where free chunks between logical disks exist, the free chunks are consolidated and placed in the end space of the disk group after expansion.
Advanced Functions Concatenated striping: A volume formed by concatenating set of striping member volumes. VU 3:1 (striping) VU 3:2 (striping) MV 3:1 MV 3:2 MV 3:3 MV 3:4 MV 3:5 MV 3:6 MV 3:7 VOL 3 (concatenating two sets: VU3:1 & VU 3:2) Figure 5-29 Concatenated striping member volumes 5.5.6 Windows DiskPart Utility The Microsoft Diskpart utility is a command line program for managing the disk partitions or volumes on Windows systems.
Advanced Functions On Windows Vista, you can also use Computer Management ÑŠ Disk Management GUI to do partition expansion and shrinking. Please follow the links below and enter “diskpart” to find more information: Microsoft Web Site Links: Search link: http://search.microsoft.com/?mkt=en-US Download diskpart utility link: http://www.microsoft.com/downloads/details.aspx?FamilyID=0fd9788a-5d64-4f57-949fef62de7ab1ae&displaylang=en 5.6 RAIDGuard Central 5.6.
Advanced Functions 5.6.2 Deployment Overview RAIDGuard Central consists of the following three software components: RAIDGuard Central Server (RGC Server), RAIDGuard Central Agent (RGC Agent), and RAIDGuard Central GUI (RGC GUI). RGC Server is the main software component of RAIDGuard Central, responsible for RAID system monitoring, event consolidation, and event notification.
Advanced Functions 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. Running RGC components requires Java Runtime Environment (JRE) version 1.
Advanced Functions Note If you want the RAIDGuard Central loading at startup each time the host computer is turned on, refer to your operating system documentation to find out how to add the startup programs. • 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.
Advanced Functions 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. Language Specify the desired GUI language. * The language options will differ according to the language support on your operating system. Help Help Contents: Open the online help web page. About: Display the program version.
Advanced Functions After logging into the RGC GUI, the following screen displays: Figure 5-33 RGC GUI main screen The following table describes each menu bar item, tool bar button, left panel and system panel contents in this screen. Menu Bar System Exit: Exit the program. Security Change Password: Change the password of the current user. Logout: Log out the current user. Language Specify the desired GUI language.
Advanced Functions 5.6.7 RAID System Registration You need to register RAID systems to RGC using the RGC GUI to build network connections to the RAID systems. Because the RGC Server communicates with RAID systems using RGC Agents, you also need to have one RGC Agent for each network of the RAID systems.
Advanced Functions 3. For scanning RAID systems, the RGC Agent sends out broadcast packets on its subnet. If IP address range is specified, only the RAID 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.
Advanced Functions 2. After the registration is completed successfully, a RAID system icon together with the IP address of the RAID system will be added to the RGC Agent branch in the Structure tree section. Figure 5-37 shows the updated screen after the registration of two RAID systems is complete. Figure 5-37 Registering a RAID system to an agent Remove a RGC Agent To remove an agent from the RGC Server, do the following: 1. Select the agent you want to remove from the structure tree. 2.
Advanced Functions 5.6.8 RAID System Monitoring After the RAID systems are registered, the RAIDGuard Central will download the event logs from the RAID controller to local database. RAIDGuard Central will also start sending out query packets every ten seconds to check the status of the RAID systems. You may now do the following tasks by the RGC GUI: 1. View the event logs of a RAID system 2. Save the event logs of a RAID system to a file 3.
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 2. Choose a management host system connected to the same LAN 3. Install the VDS Provider on the management host system. 4. Use VDS Provider Configuration Utility to locate the RAID systems and complete the registration for the VDS Provider You may now start using VDS-compliant manage software to manage the registered RAID systems. 5.7.2 Installing the VDS Provider Follow the steps below to install the VDS Provider onto the management host. 1. Copy the software file (VDSProvider_SW_1.00.
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 • 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. From the list of components, in the Windows Components Wizard dialog box, select Management and Monitoring Tools, and click Details. 3.
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 6.3 Performance Tuning Performance tuning is always not an easy job because it requires in-depth knowledge of hardware and software. This section offers a few guidelines for you to identify performance problem sources and to do improvements. However, the system performance depends on not only the RAID system but also the capability of all software and hardware components along the I/O path. Please contact your solution providers to choose field-proven configurations. 1.
Troubleshooting 9. Add memory at host computer or RAID controller Adding more memory to your motherboard or RAID controller helps to cache more data at memory to so as to reduce the number I/O access to hard disks, especially helpful for data being accessed frequently. Bigger memory also helps to avoid the performance glitch because more data can be buffered for write commands or pre-fetched for read commands, especially helpful for multiple video streams. 10.
Troubleshooting 3. Verify hard disk health status To know exactly if a hard disk fails or not, using SMART check or DST (Device Self-Test) to test the hard disks in question is a good choice. It’s also advised to check the number of bad blocks and warning events reported by the RAID controller (see 2.8.1 Hard disks on page 2-38).
Troubleshooting 4. It takes very long time for the web GUI to respond my commands The web GUI is presented by browser but its contents are generated by the storage processor, which need also process I/O request as well as other maintenance tasks. You might experience slow GUI when the I/O access is very heavy. Please reduce the workload or stop some background tasks.
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-37) and restart the system to accommodate the logical disk.
Troubleshooting on page 5-11). 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 3. Host computer reports I/O errors during path/controller failover If you use MPIO against path or controller failure, it is essential to check if your MPIO driver is installed properly. Below are the checking items you need to do: • A virtual disk has been mapped to LUNs of all host-interface ports in simple storage presentation configuration. Or, a virtual disk has been mapped to a host or host group in symmetric storage presentation configuration.
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 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 blockinterleaved.
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 sub-arrays 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 B.3 Flexible Storage Provisioning Storage provisioning is the process to organize the physical disks with appropriate RAID configurations, which determine the level of performance and reliability of LUNs. The more RAID configurations a storage system can provide the more types of applications that the system can serve.
Appendix • Flexible hot spare policy Hot spare disks are standby disks that are used for replacing faulty disks by rebuilding the data of the faulty disks. Spare disks can be configured as local spare dedicated to specific disk group or global spare shared by all disk groups. Users can also enable the auto-spare option to force the spare disk returns to standby after the faulty disks are replaced by newer disks. This helps to control the physical organization of hard disks in the chassis. B.
Appendix • Autonomous free space management The free space on a disk group is managed as free chunks. A free chunk is created when an administrator deletes a logical disk or shrinks its capacity. Free chunks are for creating new logical disks or for expanding a logical disk. By visualizing the free space with easy management utilities, an administrator can easily manage the free space and avoid waste.
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 B.9 Fortified Reliability and Robustness The mission of a RAID controller is not only to protect user data from disk drive failure but also any hazards that might cause data loss or system downtime. Both hardware and firmware of RAID controller has incorporated advanced mechanisms to fortify the data reliability and to ensure the system robustness.
Appendix • Timely event notification In addition to the audible alarm on the controller to alert the administrators, the firmware can also send out event notification email and SNMP traps. To make sure that the events are delivered to the recipients, redundant servers are used to pass the events. The administrator can also manually generate test events to see how events are logged and alerts are sent.
Appendix B.12 Extensive Supportive Tools In addition to the fundamental storage functions, the RAID controller firmware also provides extensive supportive tools that help the administrator to do a better job when managing the storage resources. These tools are aimed to offer full control to the storage devices so as to make the most of the storage system as well as to simplify the management tasks.
Appendix • 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. The system operators, like the staff in a security control center, can also easily communicate with the administrators by reporting the messages shown on the LCD panel.
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 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. Press [Y] to save the settings. If your system supports redundant controller, press [N] and you are required to set the following IP addresses. 1. Set the Server IP address and press [Enter]. 2.
Appendix 2. Press [L] in the Boot Utility and enter the file name of boot code of firmware. 3. The TFTP server starts loading. When the loading is complete, you can proceed to update the Boot ROM or System ROM. 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.
Appendix 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. You can see the process percentages on the screen. 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.
Appendix Appendix D: Event Log Messages D.1 RAID • • D-1 Disk operations Event ID 0x0800 Type RAID Message HDDx added Description hddx was added to the system from the user interface. Advice None Event ID 0x0801 Type RAID Message HDDx removed Description hddx was removed from the system from the user interface. Advice None Event ID 0x0802 Type RAID Message HDDx plugged Description hddx was added to the system by manual installation.
Appendix Event ID 0x0c01 Type RAID Message JBODx deleted Description jbdx was deleted. Advice None Event ID 0x1000 Type RAID Message DGx created Description dgx was created. Advice None Event ID 0x1001 Type RAID Message DGx deleted Description dgx was deleted. Advice None Event ID 0x1800 Type RAID Message DGxLDy created Description dgxldy was created. Advice None Event ID 0x1801 Type RAID Message DGxLDy deleted Description dgxldy was deleted.
Appendix • D-3 Event ID 0x1c01 Type RAID Message VOLx deleted Description volx was deleted. Advice None Severity INFO Parameters VOL ID Severity INFO Parameters DG ID Parameters DG ID, LD ID Parameters DG ID Parameters DG ID, LD ID Parameters DG ID Initialization Event ID 0x204c Type RAID Message Write-zero init on DGx started Description Disk group zeroing task on dgx was started.
Appendix • Event ID 0x2051 Type RAID Message Logical disk init on DGxLDy aborted 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. Event ID 0x2064 Type RAID Message Write zero progress(y%) on DGx reach to the notify percent(z%) Description The progress of zeroing DG has reached the notify threshold.
Appendix • • D-5 Event ID 0x1003 Type RAID Message Local spare HDDx of DGy removed Description dgy’s local spare, hddx, was removed. Advice None Severity INFO Parameters Disk ID, DG ID NOTICE Parameters DG ID NOTICE Parameters DG ID WARNING Parameters DG ID NOTICE Parameters Rebuild progress, DG ID, Notify threshold Rebuild Event ID 0x2000 Type RAID Message Rebuilding on DGx started Description Disk rebuilding on dgx was started.
Appendix • • Event ID 0x1004 Type RAID Message DGx is imported Description Foreign disk group has been imported to be dgx. Advice None Event ID 0x1c02 Type RAID Message VOLx is imported Description Foreign volume has been imported to be volx.
Appendix • D-7 Write Cache Event ID 0x0c02 Type RAID Message JBDx write cache is enabled Description Write cache of jbdx was enabled by user. Advice None Event ID 0x0c03 Type RAID Message JBDx write cache is disabled Description Write cache of jbdx was enabled by user. Advice None Event ID 0x1c03 Type RAID Message VOLx write cache is enabled Description Write cache of volx was disabled by user.
Appendix D.2 Task • Disk group expansion Event ID 0x2009 Type TASK Message Expansion on DGx started Description Disk group expansion on dgx was started manually. Advice None Event ID 0x202d Type TASK Message Expansion on DGx started by schedule Description Scheduled disk group expansion on dgx was started. Advice None Event ID 0x2043 Type TASK Message Expansion on DGx failed to start by schedule Description Scheduled disk group expansion on dgx failed to start.
Appendix • D-9 Event ID 0x205f Type TASK Message DG expand progress(y%) on DGx reach to the notify percent(z%) Description The progress of dg expanding has reached the pre-define threshold. Advice None Severity NOTICE Parameters Expand progress, DG ID, Notify threshold Logical disk migration Event ID 0x2004 Type TASK Message Migration on DGxLDy started Description Migration on dgxldy was started manually.
Appendix • Event ID 0x2006 Type TASK Message Migration on DGxLDy aborted Description Migration on dgxldy was aborted. Advice Check if the logical disk is faulty. Event ID 0x2005 Type TASK Message Migration on DGxLDy completed Description Migration on dgxldy was completed. Advice None Event ID 0x2061 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 D-11 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. Event ID 0x2031 Type TASK Message Expansion on DGxLDy paused Description Logical disk capacity expansion on dgxldy was paused. Advice Check if a member disk in the disk group failed during the task.
Appendix • • Logical disk shrink Event ID 0x200e Type TASK Message DGxLDy shrinked Description DGxLDy shrinked Advice Make sure partitions or file systems on the logical disk have been shrunk before conducting the logical disk capacity shrink. After finishing, hosts might need to rescan the LUN of the logical disk to get the updated capacity.
Appendix • • D-13 Event ID 0x2011 Type TASK Message Defragment on DGx completed Description Disk group defragment on dgx was completed. Advice None Event ID 0x205e 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.
Appendix Event ID 0x2048 Type TASK Message Clone from HDDx to HDDy failed to auto start 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 Description Disk cloning from hddx to hddy was paused. Advice Check if the source disk group is busy or non-optimal during the task.
Appendix • D-15 Event ID 0x2056 Type TASK Message Clone from HDDx to HDDy auto-resumed Description Disk cloning from hddx to hddy was auto-resumed. Advice None Event ID 0x206f Severity Severity NOTICE Parameters DISK ID, DISK ID Parameters Clone progress, DISK ID, DISK ID, Notify threshold Type TASK Message Clone progress(w%) from HDDx to HDDy reach to the notify percent(z%) Description The progress of disk cloning has reached the pre-define threshold.
Appendix • 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. Advice If the number of bad sectors grows exceptionally fast or beyond a reasonable number, consider to conduct diagnostics and replace with new disks.
Appendix D-17 Event ID 0x2036 Type TASK Message Scrub on DGx started by schedule Description Scheduled disk scrubbing on dgx was started. Advice None Event ID 0x2049 Type TASK Message Scrub on DGx failed to start by schedule Description Scheduled disk scrubbing on dgx failed to start. Advice Check if the disk group is busy or non-optimal.
Appendix Event ID 0x205d 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 Severity NOTICE Parameters Scrub. Progress, DG ID, Notify threshold 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 • D-19 Event ID 0x2042 Type TASK Message Scrub on DGvLDw aborted with x bad sectors detected, y inconsistent rows found, and z rows recovered Description Disk scrubbing on dgvldw was aborted, and there were x bad sectors detected, y inconsistent rows found, and z rows recovered. Advice Check if the logical disk is busy or non-optimal.
Appendix • Event ID 0x2027 Type TASK Message Reg. parity on DGx stopped Description Reg. parity on dgx was stopped manually. Advice None Event ID 0x2025 Type TASK Message Reg. parity on DGx completed Description Reg. parity on dgx was completed. Advice None Event ID 0x205c 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.
Appendix D-21 Event ID 0x203e Type TASK Message Reg. parity on DGxLDy aborted Description Reg. parity on dgxldy was aborted. Advice Check if the logic disk is busy or non-optimal. Event ID 0x203f Type TASK Message Reg. parity on DGxLDy stopped Description Reg. parity on dgxldy was stopped manually. Advice None Event ID 0x203d Type TASK Message Reg. parity on DGxLDy completed Description Reg. parity on dgxldy was completed.
Appendix D.3 Disk • • Disk status Event ID 0x0811 Type DISK Message HDDx powered on/off Description hddx was powered on or off. Advice None Event ID 0x0817 Type DISK Message HDDx failed Description hddx failed to respond to the controller. Advice Check if the disk is corrupt or the disk interface connection is unstable. Event ID 0x0810 Type DISK Message HDDx issued SMART warning Description Controller detects that hddx is signaling SMART warning.
Appendix D-23 Event ID 0x0819 Type DISK Message Controller x detected aborted task on HDDy Description The controller x aborted the command that hddy failed to respond to controller in time. This could be a transient error due to unstable channel, heavy traffic, or malfunctioning hard disks. The controller will retry the command to complete the IO; however, this could result in performance drop of the disk.
Appendix • Disk port and chip Event ID 0x081b Type DISK Message Reset disk port x in controller y Description The controller y resets disk port x that failed to execute commands properly. This could be a transient error due to unstable channel, heavy traffic, or malfunctioning hard disks. The controller will resume normal operations after reset; however, this could result in performance drop of the disks attached to the disk port.
Appendix • D-25 SMART disk self tests Event ID 0x0807 Type DISK Message SHT DST on HDDx started Description hddx started SMART short device self test routine. Advice None Event ID 0x0806 Type DISK Message EXT DST on HDDx started 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 0x080c Type DISK Message DST on HDDx completed with servo error Description DST on hddx completed with servo error. Advice The disk failed or will fail soon, replace the hard disk. Event ID 0x080d Type DISK Message DST on HDDx completed with electrical error Description DST on hddx completed with electrical error. Advice The disk failed or will fail soon, replace the hard disk.
Appendix D-27 Event ID 0x1400 Type DISK 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 0x140d Type DISK Message BBR exceeds clone threshold on HDDx Description The number of bad block reallocation table entries on hddx has exceeded the pre-defined threshold level to trigger disk cloning. 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 D-29 Event ID 0x0815 Type DISK Message Write secondary metadata on HDDx failed Description The controller failed to access the secondary RAID metadata stored on hddx and the metadata was invalid. However, the primary RAID metadata still works. Advice Start to monitor more carefully the status of the primary RAID metadata on this disk.
Appendix • Event ID 0x1405 Type DISK Message Primary BBR table on HDDx is corrupt Description The controller failed to access the primary BBR table on hddx 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. Event ID 0x1406 Type DISK Message Secondary BBR table on HDDx is corrupt Description The controller failed to access the secondary BBR table on hddx and the table was non-trustable.
Appendix D.4 Host ports FC • • D-31 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 Description Host x quitted from host port y.
Appendix • • IO exceptions handling Event ID 0x3004 Type HOST Message LIP issued on host port x Description The controller issued LIP (Loop Initialization Packet) on host port x. This is to ask host to rescan the connection and get updated of LUN information, such as capacity change or LUN mapping change. Advice None Event ID 0x3005 Type HOST Message LIP detected on host port x Description The controller detected LIP (Loop Initialization Packet) on host port x.
Appendix Event ID 0x3009 Type HOST Message Reset host i/f chip x in controller y Description The controller resets chip x that failed to execute commands properly. This could be to recover from a transient error due to 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 • • • 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. Advice None Event ID 0x300e Type HOST Message Host port x phy y link down Description The link on the host port x phy y had been turned down by the controller, and data transferring was posed.
Appendix Event ID 0x3011 Type HOST Message Reset host i/f chip x in controller y Description The controller y resets chip x that failed to execute commands properly. This could be to recover from transient error due to a 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 Event ID 0x3016 Type HOST Message Host port x detected parity error during Command phase Description Parity error was detected during command phase. Advice None Event ID 0x3017 Type HOST Message Host port x detected parity error during Message Out phase Description Parity error was detected during message out phase.
Appendix D-37 Event ID 0x301c Type HOST Message Host port x transfer count mismatch Description The amount of data that the target actually transferred does not match the DataLength. The amount of data was specified in the TargetAssist request message. Advice None Event ID 0x301d Type HOST Message Host port x data offset error Description Data was received with a data offset that was not expected.
Appendix • • Event ID 0x3022 Type HOST Message Host port x EEDP Application Tag Error Description The logical block application tag in the data protection information block of an end-to-end data protection I/O did not match the expected value. Advice None Severity WARNING Parameters Host Port ID Port and chip Event ID 0x3023 Type HOST Message IOC Bus Reset on port x Description A bus reset has occurred on port x that was initiated by the IOC.
Appendix Event ID 0x302b Type HOST Message iSCSI listen port change to x Description iSCSI listen port will be changed to x Advice None Event ID 0x302c Type HOST Message iSNS server x port y added Description iSNS server x port y was added Severity Severity INFO Parameters Port Number INFO Parameters IP Address, Port Number INFO Parameters IP Address, Port Number INFO Parameters Bond Port ID INFO Parameters Bond Port ID INFO Parameters Initiator Name, Target ID Advice
Appendix Event ID 0x3031 Type HOST 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. Severity INFO Parameters Initiator Name, Target ID D.
Appendix D-41 Event ID 0x242b Type CONTROLLER Message Bootrom in controller x is corrupt Description Bootrom on controller x is corrupt and cannot be used. Because the bootcode is stored on the bootrom, the controller cannot work. Advice Check if the power supply is stable. Replace with a new controller. Contact local sales or support office.
Appendix • Controller (In Dual-Controller Configuration) Event ID 0x242e Type CONTROLLER Message Controller x failed Description One of the controllers failed, was removed, or powered off, while the other controller remains working. This happens only in dual-controller configuration. Advice Check if the power supply is stable. Replace with a new controller. Event ID 0x242f Type CONTROLLER Message Controller x returned Description The failed controller has been replaced and back to work.
Appendix • • D-43 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 0x280a Type ENCLOSURE Message Abnormal +3.3V voltage source in backplane (z V) Abnormal +3.3V voltage source in controller (z V) Description The current voltage of the +3.3V voltage source in backplane or controller was out of normal range, right now is zV. Advice Check the power supply system, or contact local sales or support office.
Appendix • • D-45 Power supply Event ID 0x280d Type ENCLOSURE Message Power supply x in enclosure y detected Description Power supply unit (PSU) x was installed and present. Advice None Event ID 0x280e Type ENCLOSURE Message Power supply x in enclosure y failed Description The controller cannot get status from power supply unit (PSU) x in enclosure y, which might have failed or removal. Advice Replace the power supply, or contact local sales or support office.
Appendix Event ID 0x2812 Type ENCLOSURE Message BBM in controller x is charging Description BBM in controller x was not fully charged, and it started charging. Advice Start host access or operations after the BBM at fully-charged state. Event ID 0x2813 Type ENCLOSURE Message BBM in controller x charging completed Description BBM in controller x charging was done and BBM was fully charged.
Appendix • D-47 Event ID 0x2828 Type ENCLOSURE Message Remaining capacity of BBM in Controller x under threshold Description The current capacity of BBM in Controller x under threshold Advice Let BBM in charging Severity WARNING Parameters Controller ID UPS Event ID 0x2817 Type ENCLOSURE Message UPS connection detected Description UPS detected by the controller.
Appendix Event ID 0x281c Type ENCLOSURE Message UPS battery back to normal Description UPS battery charge back to normal range. Advice None Event ID 0x281d Type ENCLOSURE Message UPS battery will fail Description The UPS has a battery that will fail. Advice Replace the UPS battery as soon as possible. Event ID 0x281e Type ENCLOSURE Message UPS battery replace back to non-failure status Description The UPS is replaced and back to non-failure status.
Appendix • SAS Link Event ID 0x2825 Type ENCLOSURE Message SAS link is up Description SAS link detected by the controller Advice None Event ID 0x2826 Type ENCLOSURE Message SAS Link is down Description The controller find the SAS link is lost Advice Make sure that the proper communications cable is securely connected Severity Severity INFO Parameters WARNING Parameters D.
Appendix • Event ID 0x2416 Type SYSTEM Message NVRAM configurations restored from HDDx Description The NVRAM configurations were restored from hddx. Advice None Event ID 0x2417 Type SYSTEM Message NVRAM configurations restored from file Description The configurations were restored from a file uploaded to the controller. Advice None Event ID 0x2409 Type SYSTEM Message NVRAM configuration checksum error Description The checksum stored on NVRAM do not match the contents on NVRAM.
Appendix • D-51 Event ID 0x2410 Type SYSTEM Message Admin login failed Description Administrator failed to login to the controller. Advice Check if there is any unauthorized trial access to the controller or there are multiple administrator logins. Event ID 0x2427 Type SYSTEM Message User login Description User login to the controller. Advice None Event ID 0x2428 Type SYSTEM Message User login failed Description User failed to login to the controller.
Appendix Event ID 0x0401 Type SYSTEM Message Event test with severity: error Description Users have generated a simulated event to test the event handling/notification mechanisms. The severity level of this event is error. Advice None Event ID 0x0402 Type SYSTEM Message Event test with severity: warn Description Users have generated a simulated event to test the event handling/notification mechanisms. The severity level of this event is warn.
Appendix • D-53 Event ID 0x2414 Type SYSTEM Message Auto-write-through de-activated Description The pre-defined triggering events for auto-write-through have gone, and the controller restored the original cache setting. Advice None Event ID 0x2418 Type SYSTEM Message Auto-shutdown activated Description The pre-defined triggering events for auto-shutdown occurred, and the controller was going to shutdown itself.
Appendix • Event ID 0x2429 Type SYSTEM Message Boot code in controller x updated Description Boot code in controller x was updated successfully. Advice Restart the controller so that the new code can be effective. Event ID 0x242a Type SYSTEM Message Controller x failed to update boot code Description The controller x cannot update the boot code. Advice Check the firmware file is not corrupt and has the correct version.
Appendix • • D-55 System start-up and shutdown Event ID 0x2402 Type SYSTEM Message System to be restarted or halted Description The RAID system is going to get restarted or halted. Advice None Event ID 0x2403 Type SYSTEM Message RAID system started Description The RAID system was started.
Appendix • Event ID 0x2432 Type SYSTEM Message System Date or Time has been changed Description The system date or time has been changed by user Advice None 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 option
Appendix D-57 Event ID 0x2438 Type SYSTEM Message Enclosure serial number in controller x updated by controller y Description During fail-back, if enclosure serial number of returning controller x is not the same as controller y.
Appendix Event ID 0x243f Type SYSTEM Message Connected expansion or disk numbers of the returning controller is not the same. Description During fail-back, detected expansion or disk numbers of the returning controller is not the same. Advice Make sure the links between controllers and expansions are installed properly. If the controller still can’t startup successfully, please contact local sales or support office.
Appendix • D-59 Event ID 0x3401 Type NETWORK Message Link down on network interface ethx Description The network link on network interface of ethx had been turned down. This happens when the network configuration is incorrect, or cable were removed, or during abnormal network activity. Advice If the network link unexpectedly disconnects, or it happens repeatedly, check the network configuration and hardware. If it is still unable to work, contact local sales or support office.
Appendix Event ID 0x3406 Type NETWORK Message MAC address conflicted on iSCSI port ispx Description The MAC address of network adapter iSCSI port ispx conflicted with another one in the same network. Advice Try to configuration of network adaptor with different MAC address. Event ID 0x3407 Type NETWORK Message IP address conflicted on network interface ethx Description The IP address of network adapter iSCSI port ispx conflicted with another one in the same network.
Appendix D-61 Event ID 0x3C01 Type SNAPSHOT Message Snapshot volume pair x/y deleted Description Snapshot volume pair x/y was deleted. Advice None Event ID 0x3C02 Type SNAPSHOT Message VVOLx created Description Snapshot volume vvox was created. Advice None Event ID 0x3C03 Type SNAPSHOT Message VVOLx deleted Description Snapshot volume vvox was deleted.
Appendix Event ID 0x3C08 Type SNAPSHOT Message Spare COW volume x is added. Description Spare COW volume x was added. Advice None Event ID 0x3C09 Type SNAPSHOT Message Spare COW volume x is removed. Description Snapshot volume pair x was removed. Advice None Event ID 0x3C0B Type SNAPSHOT Message Primary volume x is restoring to SVOL y. Description Primay volume x was restoring to SVOL y.
