iSCSI GbE to SAS/SATA II RAID Subsystem User Manual Revision 1.
iSCSI GbE to SAS/SATA II RAID Subsystem Table of Contents Preface ................................................................................................................................ 5 Before You Begin ............................................................................................................. 6 Safety Guidelines ............................................................................................................................................................
iSCSI GbE to SAS/SATA II RAID Subsystem 3.1 The GUI Hierarchy ................................................................................................................................................ 28 3.2 Login........................................................................................................................................................................... 29 3.2.1 Language .................................................................................................
iSCSI GbE to SAS/SATA II RAID Subsystem 3.8.3 Reset to Factory Default ............................................................................................................................ 72 3.8.4 Import and Export ........................................................................................................................................ 73 3.8.5 Event Log................................................................................................................................
iSCSI GbE to SAS/SATA II RAID Subsystem Preface About this manual This manual provides information regarding the quick installation and hardware features of the RAID subsystem. This document also describes how to use the storage management software. Information contained in the manual has been reviewed for accuracy, but not for product warranty because of the various environment/OS/settings. Information and specifications will be changed without further notice.
iSCSI GbE to SAS/SATA II RAID Subsystem Before You Begin Before going through with this manual, you should read and focus to the following safety guidelines. Notes about the subsystem’s controller configuration and the product packaging and delivery are also included.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 1 Introduction The iSCSI RAID Subsystem Host systems can connect to the iSCSI RAID subsystem using iSCSI protocol. The iSCSI RAID subsystem can be configured to any RAID level. The iSCSI RAID subsystem provides reliable data protection for servers and the RAID 6 function is available. The RAID 6 function allows two HDD failures without any impact on the existing data. Data can be recovered from the remaining data and parity drives.
iSCSI GbE to SAS/SATA II RAID Subsystem 1.1 Key Features 4 x 1Gigabit Ethernet ports support independent access, fail-over or load- balancing (802.3ad port trunking, LACP) Supports iSCSI jumbo frame Supports Microsoft Multipath I/O (MPIO) Supports RAID levels 0, 1, 0+1, 3, 5, 6, 10, 30, 50, 60 and JBOD Local N-way mirror: Extension to RAID 1 level, N copies of the disk.
iSCSI GbE to SAS/SATA II RAID Subsystem 1.2 Terminology The document uses the following terms: RAID RAID is the abbreviation of “Redundant Array of Independent Disks”. There are different RAID levels with different degree of the data protection, data availability, performance to host environment. PD The Physical Disk belongs to the member disk of one specific volume group. RG Raid Group. A collection of removable media or physical disks.
iSCSI GbE to SAS/SATA II RAID Subsystem GC Global Cache. DG DeGraded mode. Not all of the RG’s member disks are functioning, but the RG is able to respond to application read and write requests to its virtual disks. S.M.A.R.T. Self-Monitoring Analysis and Reporting Technology. SAS Serial Attached SCSI. WWN World Wide Name. HBA Host Bus Adapter. SAF-TE SCSI Accessed Fault-Tolerant Enclosures. MPIO Multi-Path Input/Output. MC/S Multiple Connections per Session SES SCSI Enclosure Services.
iSCSI GbE to SAS/SATA II RAID Subsystem 1.3 RAID Levels The subsystem can implement several different levels of RAID technology. RAID levels supported by the subsystem are shown below. RAID Description Min. Drives 0 Block striping is provide, which yields higher performance than with individual drives. There is no redundancy. 1 1 Drives are paired and mirrored. All data is 100% duplicated on an equivalent drive. Fully redundant. 2 N-way mirror Extension to RAID 1 level.
iSCSI GbE to SAS/SATA II RAID Subsystem 1.4 Volume Relationship Diagram This is the design of volume structure of the iSCSI RAID subsystem. It describes the relationship of RAID components. One RG (RAID Group) is composed of several PDs (Physical Disks). One RG owns one RAID level attribute. Each RG can be divided into several VDs (Virtual Disks). The VDs in one RG share the same RAID level, but may have different volume capacity.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 2 Getting Started 2.1 Packaging, Shipment, and Delivery Before removing the subsystem from the shipping carton, you should visually inspect the physical condition of the shipping carton. Unpack the subsystem and verify that the contents of the shipping carton are all there and in good condition. Exterior damage to the shipping carton may indicate that the contents of the carton are damaged.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.3 Identifying Parts of the Subsystem The illustrations below identify the various parts of the subsystem. 2.3.1 Front View Reserve for other model 1. HDD Status Indicator Parts Function HDD Status LEDs Green LED indicates power is on and hard drive status is good for this slot. If hard drive defected in this slot or the hard drive is failure, the LED is orange.
iSCSI GbE to SAS/SATA II RAID Subsystem 2. 3. HDD Trays 1 ~ 16 (From left to right) Access LED The LED will be blinking blue when subsystem is busy or data is being accessed. 4. LCD Display Panel 5. LCM (LCD Control Module) - Smart Front Panel Function Buttons The LCM provides menu options to configure the iSCSI RAID subsystem. If you are configuring the subsystem using the Front Panel, please press the controller button to configure your RAID subsystem.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.3.2 Rear View Uninterrupted Power Supply (UPS) Port (APC Smart UPS only) The subsystem may come with an optional UPS port allowing you to connect an APC Smart UPS device. Connect the cable from the UPS device to the UPS port located at the rear of the subsystem. This will automatically allow the subsystem to use the functions and features of the UPS.
iSCSI GbE to SAS/SATA II RAID Subsystem Cooling Fan module Two blower fans are located at the rear of the subsystem. They provide sufficient airflow and heat dispersion inside the chassis. In case a fan fails to function, the “ ” Fan fail LED will turn red and an alarm will sound. Power Supply Power On Indicator Green LED indicates power is on. System Power On Indicator Green LED indicates power is on.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.5 Connecting the iSCSI RAID Subsystem to the Network To connect the iSCSI unit to the network, insert the network cable that came with the unit into the network port (LAN1) at the back of iSCSI unit. Insert the other end into a Gigabit BASE-T Ethernet connection on your network hub or switch. You may connect the other network ports if needed. For remote management of iSCSI RAID subsystem, use another network cable to connect the R-Link port to your network. 2.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.7 Installing Hard Drives This section describes the physical locations of the hard drives supported by the subsystem and give instructions on installing a hard drive. The subsystem supports hot-swapping allowing you to install or replace a hard drive while the subsystem is running. a. Pull out an empty disk tray. Pull the handle outwards to remove the carrier from the enclosure. b. Take off the bracket before installing hard drive. c.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.8 iSCSI Introduction iSCSI (Internet SCSI) is a protocol which encapsulates SCSI (Small Computer System Interface) commands and data in TCP/IP packets for linking storage devices with servers over common IP infrastructures. iSCSI provides high performance SANs over standard IP networks like LAN, WAN or the Internet.
iSCSI GbE to SAS/SATA II RAID Subsystem The host side needs an iSCSI initiator. The initiator is a driver which handles the SCSI traffic over iSCSI. The initiator can be software or hardware (HBA). Please refer to the certification list of iSCSI HBA(s) in Appendix A. OS native initiators or other software initiators use the standard TCP/IP stack and Ethernet hardware, while iSCSI HBA(s) use their own iSCSI and TCP/IP stacks on board. Hardware iSCSI HBA(s) would provide its initiator tool.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.9 Management Methods There are three management methods to manage the iSCSI RAID subsystem described as follows: 2.9.1 Web GUI The iSCSI RAID subsystem supports graphical user interface to manage the system. Be sure to connect LAN cable to your R-Link port.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.9.2 Console Serial Port Use NULL modem cable to connect console port. The console setting is baud rate: 115200, 8 bits, 1 stop bit, and no parity. Terminal type: vt100 Login name: admin Default password: 00000000 2.9.3 Remote Control – Secure Shell SSH (secure shell) is required for remote login. The SSH client software is available at the following web site: SSHWinClient WWW: http://www.ssh.com/ Putty WWW: http://www.chiark.greenend.org.uk/ Host name: 192.168.10.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.10 Enclosure 2.10.1 LCD Control Module (LCM) There are four buttons to control the LCM. These are: c(Up) d(Down) (Escape) (Enter) After booting up the system, the following screen shows management port IP and model name: 192.168.10.50 iSCSI-Model Press “ ”, the LCM functions “Alarm Mute”, “Reset/Shutdown”, “Quick Install”, “View IP Setting”, “Change IP Config” and “Reset to Default” will rotate by pressing c (up) and d (down).
iSCSI GbE to SAS/SATA II RAID Subsystem The following table is the function description of LCM menus. System Info Displays System information. Alarm Mute Mute alarm when error occurs. Reset/Shutdown Reset or shutdown controller. Quick Install Quick three steps to create a volume. Please refer to next chapter for operation in web UI. Volume Wizard Smart steps to create a volume. Please refer to next chapter for operation in web UI.
iSCSI GbE to SAS/SATA II RAID Subsystem The following is LCM menu hierarchy. [System Info.] [Alarm Mute] [Firmware Version x.x.x] [RAM Size xxx MB] [cYes Nod] [Reset] [Reset/Shutdown] [Shutdown] [Quick Install] [Volume Wizard] proIPS cd [View IP Setting] RAID 0 RAID 1 RAID 3 RAID 5 RAID 6 RAID 0+1 xxx GB [Local] RAID 0 RAID 1 RAID 3 RAID 5 RAID 6 RAID 0+1 [JBOD x] cd RAID 0 RAID 1 RAID 3 RAID 5 RAID 6 RAID 0+1 [IP Config] [Static IP] [IP Address] [192.168.010.050] [IP Subnet Mask] [255.255.255.
iSCSI GbE to SAS/SATA II RAID Subsystem CAUTION! Before power off, it is better to execute “Shutdown” to flush the data from cache to physical disks. 2.10.2 System Buzzer The system buzzer features are described in the following: 1. The system buzzer alarms 1 second when system boots up successfully. 2. The system buzzer alarms continuously when an error level event happens. The alarm will be stopped after mute. 3. The alarm will be muted automatically when the error situation is resolved. E.g.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 3 Web GUI Guideline 3.1 The GUI Hierarchy The below table is the hierarchy of the management GUI.
iSCSI GbE to SAS/SATA II RAID Subsystem Reset to default Import and export Event log Reboot and shutdown Logout Æ Sure to reset to factory default? Æ Import/Export / Import file Æ Download / Mute / Clear Æ Reboot / Shutdown Sure to logout? 3.2 Login The iSCSI RAID subsystem supports graphical user interface (GUI) to operate the system. Be sure to connect the LAN cable. The default IP setting is DHCP; open the browser and enter: http://192.168.10.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.2.1 Language Before clicking the Login button, you can change the GUI language if needed. There are 4 options to select: English, Simplified Chinese, German, and French. 3.2.2 Status Indicators There are six indicators at the top-right corner. 1. RAID light: Green means RAID is working well. Red represents RAID failure. 2. Temperature temperature. 3. light: Green is normal. Red represents abnormal Voltage light: Green is normal.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.3 Quick Install It is easy to use “Quick install” to create a volume. It uses all available physical disks to create a RG; the system will calculate maximum spaces on RAID levels 0/1/3/5/6/0+1. “Quick install” will occupy all residual RG space for one VD, and it has no space for snapshot and spare. If snapshot is needed, please create volumes manually, and refer to Section 4.4 for more detail.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.4 System Configuration “System configuration” is designed for setting up the “System setting”, “IP address”, “Login setting”, “Mail setting”, and “Notification setting”. 3.4.1 System Setting “System setting” can be used to set system name and date. Default “System name” is composed of model name and serial number of this system, e.g.: iSCSIModel-A6D299.
iSCSI GbE to SAS/SATA II RAID Subsystem Check “Change date and time” to set up the current date, time, and time zone before using or synchronize time from NTP (Network Time Protocol) server. 3.4.2 IP Address “IP address” can be used to change IP address remote administration usage. There are 2 options, DHCP (Get IP address from DHCP server) or static IP. The default setting is DHCP. User can change the HTTP, HTTPS, and SSH port number when the default port number is not allowed on host/server.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.4.3 Login Setting “Login setting” can set single admin, auto logout time and Admin/User password. The single admin can prevent multiple users access the same controller at the same time. 1. Auto logout: The options are (1) Disable; (2) 5 minutes; (3) 30 minutes; (4) 1 hour. The system will log out automatically when user is inactive for a period of time. 2. Login lock: Disable/Enable.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.4.4 Mail Setting “Mail setting” can accept at most 3 mail-to address entries for receiving the event notification. Some mail servers would check “Mail-from address” and need authentication for anti-spam. Please fill the necessary fields and click “Send test mail” to test whether email functions are available or working. User can also select which levels of event logs are needed to be sent via Mail. Default setting only enables ERROR and WARNING event logs.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.4.5 Notification Setting “Notification setting” can be used to set up SNMP trap for alerting via SNMP, pop-up message via Windows messenger (not MSN), alert via syslog protocol, and event log filter. “SNMP” allows up to 3 SNMP trap addresses. Default community name is set as “public”. User can choose the event log levels and default setting only enables INFO event log in SNMP. There are many SNMP tools.
iSCSI GbE to SAS/SATA II RAID Subsystem Using “Messenger”, user must enable the service “Messenger” in Windows (Start Æ Control Panel Æ Administrative Tools Æ Services Æ Messenger), and then event logs can be received. It allows up to 3 messenger addresses. User can choose the event log levels and default setting enables the WARNING and ERROR event logs. Using “System log server”, user can choose the facility and the event log level. The default port of syslog is 514.
iSCSI GbE to SAS/SATA II RAID Subsystem There are some syslog server tools. The following web sites are for your reference: WinSyslog: http://www.winsyslog.com/ Kiwi Syslog Daemon: http://www.kiwisyslog.com/ Most UNIX systems have built-in syslog daemon. “Event log filter” setting can enable event level on “Pop up events” and “LCM”.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.5 iSCSI Configuration “iSCSI configuration” is designed for setting up the “Entity Property”, “NIC”, “Node”, “Session”, and “CHAP account”. 3.5.1 Entity Property “Entity property” is used to view the entity name of the iSCSI RAID subsystem, and setup “iSNS IP” for iSNS (Internet Storage Name Service). iSNS protocol allows automated discovery, management and configuration of iSCSI devices on a TCP/IP network.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.5.2 NIC “NIC” function is used to change the IP addresses of iSCSI data ports. The iSCSI RAID subsystem has four gigabit LAN ports to transmit data. Each of them must be assigned to one IP address in multi-homed mode unless the link aggregation or trunking mode has been selected. If any two or more ports are set in link aggregation or trunking mode, they will display the same IP.
iSCSI GbE to SAS/SATA II RAID Subsystem Multi-homed / Trunking / LACP: The following is the description of multi-homed/trunking/LACP. 1. Multi-homed: Default mode. Each of iSCSI data port is connected by itself and is not set to link aggregation and trunking. Selecting this mode can also remove the setting of Trunking/LACP at the same time. 2. Trunking: defines the use of multiple iSCSI data ports in parallel to increase the link speed beyond the limits of any single port. 3.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.5.3 Node “Node” can be used to view the target name for iSCSI initiator. This iSCSI RAID model supports multi-node. There is no default node name, i.e. it is empty. It must be created first, and then the iSCSI RAID system can be used. When using “Quick install”, a node name like “iqn.1997-05.com.vendor:iSCSI-Modelxxxxxxxxx:target0” will be created automatically. Click “Create” to create a node name.
iSCSI GbE to SAS/SATA II RAID Subsystem 3. Click “ ”. 4. Go to “/ iSCSI configuration / CHAP account” page to create CHAP account. Please refer to next section for more detail. 5. Move the mouse pointer to the gray button of “Auth” column, click “User”. 6. Select CHAP user(s) which will be used. It’s a multiple option selection; it can be one or more. If none is chosen, CHAP can not work. 7. Click “ ”. 8. In “Change Authenticate” page, select “None” to disable CHAP.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.5.4 Session “Session” can display iSCSI session and connection information, including the following items: 1. Host (Initiator Name) 2. Error Recovery Level 3. Error Recovery Count 4. Detail of Authentication status and Source IP: port number. Move the mouse pointer to the gray button of session number, click “List connection”. It will list all connection(s) of the session.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.5.5 CHAP Account “CHAP account” is used to manage CHAP accounts for authentication. This iSCSI RAID subsystem allows creation of many CHAP accounts. To setup CHAP account, please follow these steps: 1. Click “ ”. 2. Enter “User”, “Secret”, and “Confirm” secret again. “Node” can be selected here or later. If selecting none, it can be enabled in “/ iSCSI configuration / Node / User”. 3. Click “ ”.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.6 Volume Configuration “Volume configuration” is designed for setting up the volume configuration which includes “Volume create wizard”, “Physical disk”, “RAID group”, “Virtual disk”, “Snapshot”, and “Logical unit”.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.6.1 Volume Create Wizard “Volume create wizard” has smart policy. When the system is inserted with several HDDs, “Volume create wizard” will list all possibilities and sizes in different RAID levels. It will use all available HDDs for RAID level depending on which user chooses. When system has different sizes of HDDs, e.g., 8*200G and 8*80G, it lists all possibilities and combination in different RAID level and different sizes.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 2: Please select the combination of the RG capacity, or “Use default algorithm” for maximum RG capacity. After RG size is chosen, click ”. “ Step 3: Decide VD size. User can enter a number less or equal to the default number. Then click “ ”. Step 4: Confirm page. Click “ VD will be created. ” if all setups are correct. Then a Done. You can start to use the system now.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.6.2 Physical Disk “Physical disk” can be used to view the status of hard drives in the system. The following are operational tips: 1. Move the mouse pointer to the gray button next to the PD slot number; it will show the functions which can be executed. 2. Active function can be selected, but inactive function will show in gray color. For example, set PD slot number 4 to dedicated spare disk.
iSCSI GbE to SAS/SATA II RAID Subsystem Physical disks of slot 1, 2, and 3 are RAID members (RAID disk) of RG named “RG-R5”. Slot 4 is set as global hot spare. The others are Free disks. PD column description: Slot The position of hard drives. The button next to the number of slot shows the functions which can be executed. Size (GB) Capacity of hard drive. RG Name Related RAID group name. Status The status of hard drive. “Online” Æ the hard drive is online.
iSCSI GbE to SAS/SATA II RAID Subsystem RG set, or hot-plug of this disk in the running time. In order to protect the data in the disk, the status changes to reserve. It can be reused after setting it to “FR” manually. Vendor Hard drive vendor. Serial Hard drive serial number. Type Hard drive type. “SATA” Æ SATA disk. “SATA2” Æ SATA II disk. “SAS” Æ SAS disk. Write cache Hard drive write cache is enabled or disabled. Standby HDD auto spindown function to save power.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.6.3 RAID Group “RAID group” is used to create RAID group or view the status of each RAID group. The following is an example to create a RG. ”, enter “Name”, choose “RAID level”, click Step 1: Click “ ” to select PD. Then click “ “ Step 2: Confirm page. Click “ ”. ” if all setups are correct. There are two RGs. One RG, named “RG-R0” with 4 physical disks, is RAID 0 and has total size of 135GB. Another RG is “RG-R5”, a RAID 5 RG with 3 physical disks. Done.
iSCSI GbE to SAS/SATA II RAID Subsystem RG column description: No. Number of RAID group. The button next to the No. shows the functions which can be executed. Name RAID group name. Total(GB) Total capacity of this RAID group. Free(GB) Free capacity of this RAID group. #PD The number of physical disks in RAID group. #VD The number of virtual disks in RAID group. Status The status of RAID group. “Online” Æ the RAID group is online. “Offline” Æ the RAID group is offline.
iSCSI GbE to SAS/SATA II RAID Subsystem Delete Delete a RAID group. Set disk property Change the disk status of write cache and standby. Write Cache options: “Enabled” Æ Enable disk write cache. “Disabled” Æ Disable disk write cache. Standby options: “Disabled” Æ Disable spindown. “30 sec / 1 min / 5 min / 30 min” Æ Enable hard drive auto spindown to save power in the period of time. More information Show RAID group detail information. 3.6.
iSCSI GbE to SAS/SATA II RAID Subsystem WARNING! If shutdown or reboot the system when creating VD, the erase process will stop. Step 2: Confirm page. Click “ ” if all setups are correct. A VD named “VD-01” has been created from “RG-R0”. The other VD is named “VD-02” and is initializing. Done. View “Virtual disk” page. VD column description: No. Virtual disk number. The button includes the functions which can be executed. Name Virtual disk name.
iSCSI GbE to SAS/SATA II RAID Subsystem Bg rate x “MD” Æ MiDdle priority. x “LO” Æ LOw priority. Background task priority: x Status The status of virtual disk: x “Online” Æ The virtual disk is online. x “Offline” Æ The virtual disk is offline. x “Initiating” Æ The virtual disk is being initialized. x “Rebuild” Æ The virtual disk is being rebuilt. x “Migrate” Æ The virtual disk is being migrated. x “Rollback” Æ The virtual disk is being rolled back.
iSCSI GbE to SAS/SATA II RAID Subsystem (GB) (MB) means “Used snapshot space” / “Total snapshot space”. The unit can be displayed in GB or MB. #Snapshot Number of snapshot(s) that have been taken. RG name The RG name of the virtual disk VD operations description: Create Create a virtual disk. Extend Extend the virtual disk capacity. Parity check Execute parity check for the virtual disk. It supports RAID 3 / 5 / 6 / 30 / 50 / 60. Regenerate parity: x “Yes” Æ Regenerate RAID parity and write.
iSCSI GbE to SAS/SATA II RAID Subsystem Attach LUN Attach to a LUN. Detach LUN Detach to a LUN. List LUN List attached LUN(s). Set snapshot space Set snapshot space for taking snapshot. Please refer to next chapter for more detail. Set clone Set the target virtual disk for clone. Clear clone Clear clone function. Start clone Start clone function. Stop clone Stop clone function. Schedule clone Set clone function by schedule. Take snapshot Take a snapshot on the virtual disk.
iSCSI GbE to SAS/SATA II RAID Subsystem “VD-01” snapshot space has been created, snapshot space is 15360MB, and used 263MB for saving snapshot index. Step 3: Take a snapshot. In “/ Volume configuration / Snapshot”, click “ ”. It will link to next page. Enter a snapshot name. Step 4: Export the snapshot VD. Move the mouse pointer to the gray button next to the Snapshot VD number; click “Export”. Enter a capacity for snapshot VD. If size is zero, the exported snapshot VD will be read only.
iSCSI GbE to SAS/SATA II RAID Subsystem Done. Snapshot VD can be used. Snapshot column description: No. Number of this snapshot VD. The button next to the snapshot VD No. shows the functions which can be executed. Name Snapshot VD name. Used (MB) The amount of snapshot space that has been used. Exported Snapshot VD is exported or not. Right “RW” Æ Read / Write. The snapshot VD can be read / write. “RO” Æ Read Only. The snapshot VD can be read only.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.6.6 Logical Unit “Logical unit” can be used to view the status of attached logical unit number of each VD, or can be used to attach or detach a LUN. User can attach LUN by clicking the “ ”. In the “Host” field, user must enter an iSCSI node name for access control, or fill-in wildcard “*”, which means every host can access the volume. Choose LUN number and permission, then click ”. “ VD-01 is attached to LUN 0 and every host can access.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.6.7 Example The following is an example for creating volumes. Example 1 is to create two VDs and set a global spare disk. Example 1 This example is to create two VDs in one RG, each VD shares the cache volume. The cache volume is created after system boots up automatically. Then set a global spare disk. Last, delete all of them. Step 1: Create RG (RAID group). To create the RAID group, please follow these steps: 1.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 2: Create VD (Virtual disk). To create a data user volume, please follow these steps. 1. Select “/ Volume configuration / Virtual disk”. 2. Click “ 3. Input a VD name, choose a RG Name and enter a size for this VD; decide the stripe height, block size, read / write mode, bg rate, and set priority, finally click “ ”. ”. 4. Done. A VD has been created. 5. Repeat steps 1 to 4 to create another VD.
iSCSI GbE to SAS/SATA II RAID Subsystem The steps are as follows: 1. Select a VD. 2. Input “Host” IQN, which is an iSCSI node name for access control, or fill-in wildcard “*”, which means every host can access to this volume. Choose LUN 3. and permission, and then click “ Done. ”. VD-R5-1 is attached to LUN 0. VD-R5-2 is attached LUN 1. NOTE: The matching rules of access control are from the LUNs’ created time, the earlier created LUN is prior to the matching rules. Step 4: Set global spare disk.
iSCSI GbE to SAS/SATA II RAID Subsystem Slot 4 is set as global spare disk (GS). Step 5: Done. LUNs can be used as disks. To delete VDs, RG, please follow the steps listed below. Step 6: Detach LUN from VD. In “/ Volume configuration / Logical unit”, 1. Move the mouse pointer to the gray button next to the LUN; click “Detach”. There will pop up a confirmation page. 2. Choose “OK”. 3. Done. Step 7: Delete VD (Virtual disk). To delete the Virtual disk, please follow the procedures: 1.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 8: Delete RG (RAID group). To delete the RAID group, please follow the procedures: 1. Select “/ Volume configuration / RAID group”. 2. Select a RG which is no VD related on this RG, otherwise the VD(s) on this RG must be deleted first. 3. Check the gray button next to the RG number click “Delete”. 4. There will pop up a confirmation page, click “OK”. 5. Done. The RG has been deleted.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.7 Enclosure Management “Enclosure management” allows managing enclosure information including “SES configuration”, “Hardware monitor”, “S.M.A.R.T.” and “UPS”. For the enclosure management, there are many sensors for different purposes, such as temperature sensors, voltage sensors, hard disks, fan sensors, power sensors, and LED status. Due to the different hardware characteristics among these sensors, they have different polling intervals.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.7.2 Hardware Monitor “Hardware monitor” can be used to view the information of current voltage, temperature levels, and fan speed. If “Auto shutdown” has been checked, the system will shutdown automatically when voltage or temperature is out of the normal range. For better data protection, please check “Auto Shutdown”.
iSCSI GbE to SAS/SATA II RAID Subsystem 1. There are 3 sensors placed on controller for temperature checking, they are on core processor, PCI-X bridge, and daughter board. Controller will check each sensor for every 30 seconds. When one of these sensors is over high temperature value continuously for 3 minutes, auto shutdown will be triggered immediately. 2. The core processor temperature limit is 85°C. The PCI-X bridge temperature limit is 80°C. The daughter board temperature limit is 80°C. 3.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.7.4 UPS “UPS” is used to set up UPS (Uninterruptible Power Supply). Currently, the system only supports and communicates with APC (American Power Conversion Corp.) smart UPS. Please review the details from the website: http://www.apc.com/. First, connect the system and APC UPS via RS-232 for communication. Then set up the shutdown values when power is failed. UPS in other companies can work well, but they have no such communication feature.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.8 System Maintenance “Maintenance” allows the operation of system functions which include “System information” to show the system version, “Upgrade” to the latest firmware, “Reset to factory default” to reset all controller configuration values to factory settings, “Import and export” to import and export all controller configuration, “Event log” to view system event log to record critical events, and “Reboot and shutdown” to either reboot or shutdown the system.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.8.2 Upgrade “Upgrade” is used to upgrade firmware. Please prepare new firmware file named “xxxx.bin” in local hard drive, then click “ ” to select the file. Click ”, it will pop up a message “Upgrade system now? If you want “ to downgrade to the previous FW later (not recommend), please export your system configuration in advance”, click “Cancel” to export system configuration in advance, then click “OK” to start to upgrade firmware.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.8.4 Import and Export “Import and export” allows user to save system configuration values: export, and apply all configuration: import. For the volume configuration setting, the values are available in export and not available in import which can avoid confliction/date-deleting between two controllers. That says if one controller already exists valuable data in the disks and user may forget to overwrite it. Use import could return to original configuration.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.8.5 Event Log “Event log” can be used to view the event messages. Check the checkbox of INFO, WARNING, and ERROR to choose the level of display event log. Clicking ” button will save the whole event log as a text file with file “ name “log-ModelName-SerialNumber-Date-Time.txt” (e.g., log-iSCSI-Model-a0000120080501-120000.txt). Click ” ” button will clear event log. Click ” button will stop alarm if system alerts.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.9 Logout For security reason, “Logout” allows users to logout when user does not need to operate the system. To re-login, enter username and password again. Click “Confirm” to proceed with logout.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 4 Advanced Operation 4.1 Rebuild If one physical disk from a RG, which is set to a protected RAID level (e.g. RAID 3, RAID 5, or RAID 6), failed or has been unplugged/removed, the status of RG is changed to degraded mode. The system will search/detect spare disk to rebuild the degraded RG to become normal/complete. It will detect dedicated spare disk as rebuild disk first, then global spare disk. The iSCSI RAID subsystem supports Auto-Rebuild.
iSCSI GbE to SAS/SATA II RAID Subsystem NOTE: “Set dedicated spare” is not available if there is no RG, or if RG is set to RAID 0 or JBOD, because user can not set dedicated spare disk to RAID 0 & JBOD. Sometimes, rebuild is called recover; they are the same meaning. The following table is the relationship between RAID levels and rebuild. RAID 0 Disk striping. No protection for data. RG fails if any hard drive fails or unplugs. RAID 1 Disk mirroring over 2 disks.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.2 RG Migration To migrate the RAID level, please follow the steps below. 1. Select “/ Volume configuration / RAID group”. 2. Move the mouse pointer to the gray button next to the RG number; click “Migrate”. 3. Change the RAID level by clicking the down arrow to “RAID 5”. There will be a pup-up which indicates that HDD is not enough to support the new setting of ” to increase hard drives, then click RAID level, click “ “ “ to go back to setup page.
iSCSI GbE to SAS/SATA II RAID Subsystem To do migration, the total size of RG must be larger or equal to the original RG. It does not allow expanding the same RAID level with the same hard disks of original RG. The operation is not allowed when RG is being migrated. System would reject following operations: 1. Add dedicated spare. 2. Remove a dedicated spare. 3. Create a new VD. 4. Delete a VD. 5. Extend a VD. 6. Scrub a VD. 7. Perform yet another migration operation. 8. Scrub entire RG. 9.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.3 VD Extension To extend VD size, please follow the procedures. 1. Select “/ Volume configuration / Virtual disk”. 2. Move the mouse pointer to the gray button next to the VD number; click “Extend”. 3. Change the size. The size must be larger than the original, and then click ” to start extension. “ 4. Extension starts. If VD needs initialization, it will display “Initiating” in “Status” and the completed percentage of initialization in “R%” column.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.4 Snapshot / Rollback Snapshot-on-the-box captures the instant state of data in the target volume in a logical sense. The underlying logic is Copy-on-Write -- moving out the data which would be written to certain location where a write action occurs since the time of data capture. The certain location, named as “Snap VD”, is essentially a new VD.which can be attached to a LUN provisioned to a host as a disk like other ordinary VDs in the system.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.4.1 Create Snapshot Volume To take a snapshot of the data, please follow the procedures. 1. Select “/ Volume configuration / Virtual disk”. 2. Move the mouse pointer to the gray button next to the VD number; click “Set snapshot space”. 3. Set up the size for snapshot. The minimum size is suggested to be 20% of VD size, then click “ “. It will go back to the VD page and the size will show in snapshot column.
iSCSI GbE to SAS/SATA II RAID Subsystem 10. There are two methods to clean all snapshots. In “/ Volume configuration / Virtual disk”, move the mouse pointer to the gray button next to the VD number; click “Cleanup snapshot”. Or in “/ Volume configuration / ”. Snapshot”, click “ 11. Cleanup will delete all snapshots related to the VD and release snapshot space. Snapshot has some constraints such as the following: 1. Minimum RAM size for enabling snapshot is 1GB. 2.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.4.2 Auto Snapshot The snapshot copies can be taken manually or by schedule such as hourly or daily. Please follow the procedures. 1. There are two methods to set auto snapshot. In “/ Volume configuration / Virtual disk”, move the mouse pointer to the gray button next to the VD number; click “Auto snapshot”. Or in “/ Volume configuration / Snapshot”, click “ ”. 2. The auto snapshot can be set monthly, weekly, daily, or hourly. 3. Done.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.4.3 Rollback The data in snapshot VD can rollback to original VD. Please follow the steps. 1. Select “/ Volume configuration / Snapshot”. 2. Mouse moves to the gray button next to the Snap VD number which user wants to rollback the data; click “Rollback”. 3. Done, the data in snapshot VD will rollback to original VD. Rollback has some constraints as described in the following: 1. 2. Minimum RAM size required for enabling rollback is 1GB.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.5 Disk Roaming Physical disks can be re-sequenced in the same system or move all physical disks from system-1 to system-2. This is called disk roaming. System can execute disk roaming online. Please follow these steps: 1. Select “/ Volume configuration / RAID group”. 2. Move the mouse pointer to the gray button next to the RG number; click “Deactivate”. 3. Move all PDs related to the RG to another system. 4.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.6 VD Clone The user could use VD clone to backup data from source VD to target VD, set up backup schedule, and deploy the clone rules. The procedures of VD clone are on the following: 1. Fully copy data from source VD to target VD at the beginning. 2. Using Snapshot technology to perform the incremental copy afterwards. Please be fully aware that the incremental copy needs to use snapshot to compare the data difference.
iSCSI GbE to SAS/SATA II RAID Subsystem 3. Here are the objects, a Source VD and a Target VD. Before starting clone process, it needs to deploy the VD Clone rule first. Click the “Configuration” button. 4. There are three clone configurations, describe on the following. x Snapshot space: This setting is the ratio of source VD and snapshot space. The default ratio is 2 to 1.
iSCSI GbE to SAS/SATA II RAID Subsystem x Restart the task an hour later if failed: (Become effective after enabling schedule clone) When running out of snapshot space, the VD clone process will stop because there is no more available snapshot space. If this option has been check, system will automatically clear the snapshots of clone in order to release snapshot space, and the VD clone will restart the task after an hour. This task will start a fully copy. 5.
iSCSI GbE to SAS/SATA II RAID Subsystem 7. Now, the clone target “TargetVD_Raid6” has been set. 8. Click “Start clone”, the clone process will start. 9. The default setting will automatically create a snapshot space which capacity is double size of VD space. Before starting clone, system will initiate the snapshot space. 10. Start cloning. System will issue an Info level event “VD SourceVD_Raid5 starts cloning process.
iSCSI GbE to SAS/SATA II RAID Subsystem 11. Click “Schedule clone “to set up schedule. 12. There are “Set Clone schedule” and “Clear Clone schedule” in this page. (Please remember that ”Threshold“ and “Restart the task an hour later if failed” options from VD configuration will take effect after clone schedule has been set.
iSCSI GbE to SAS/SATA II RAID Subsystem Run out of snapshot space while VD clone 1. User can set up snapshot space by themselves for VD clone. 2. For example, set up 5GB snapshot space and start clone process.
iSCSI GbE to SAS/SATA II RAID Subsystem 3. While the clone is processing, the increment data of this VD is over the snapshot space. The clone will complete, but the clone snapshot will fail. 4. Next time, when user tries to start clone will get a “This is not enough of snapshot space for the operation” message. 5. User needs to clean up the snapshot space in order to operate the clone process next time.
iSCSI GbE to SAS/SATA II RAID Subsystem 6. Each time the clone snapshot failed, it means system loses the reference value of incremental data. So the next clone process will start a fully copy. 7. When running out of snapshot space, the VD clone procedure will like the flow diagram below.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.7 SAS JBOD Expansion 4.7.1 Connecting JBOD This iSCSI RAID subsystem has SAS expansion port to connect to SAS JBOD Expansion chassis. When a SAS JBOD Expansion chassis is connected and detected, it displays tabs on the top in “/ Volume configuration / Physical disk”. For example: Local, JBOD 1 (vendor model), JBOD 2 (vendor model), …etc. Local means disks in local controller, and so on. The disks in JBOD can be used as local disks. “/ Enclosure management / S.M.A.
iSCSI GbE to SAS/SATA II RAID Subsystem Figure shows Disk S.M.A.R.T. information of Local and JBOD 1; S.M.A.R.T. is supported in SATA disks only. SAS JBOD expansion has some constraints as described in the following: 1. Up to 4 SAS JBODs can be cascaded. 2. When creating RG, member PDs must be located within the same enclosure. RG cannot use PDs which are located in different enclosure. It means that RG can be composed of PDs which are all in same Local enclosure or one SAS JBOD enclosure. 3.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.8 MPIO and MC/S These features come from iSCSi initiator. They can be setup from iSCSI initiator to establish redundant paths for sending I/O from the initiator to the target. 1. MPIO: In Microsoft Windows server base system, Microsoft MPIO driver allows initiators to login multiple sessions to the same target and aggregate the duplicate devices into a single device.
iSCSI GbE to SAS/SATA II RAID Subsystem Difference: MC/S is implemented on iSCSI level, while MPIO is implemented on the higher level. Hence, all MPIO infrastructures are shared among all SCSI transports, including Fiber Channel, SAS, etc. MPIO is the most common usage across all OS vendors. The primary difference between these two is which level the redundancy is maintained. MPIO creates multiple iSCSI sessions with the target storage. Load balance and failover occurs between the multiple sessions.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.9 Trunking and LACP Link aggregation is the technique of taking several distinct Ethernet links to let them appear as a single link. It has a larger bandwidth and provides the fault tolerance ability. Beside the advantage of wide bandwidth, the I/O traffic remains operating until all physical links fail. If any link is restored, it will be added to the link group automatically. iSCSI subsystem implements link aggregation as LACP and Trunking. 1. LACP (IEEE 802.
iSCSI GbE to SAS/SATA II RAID Subsystem 2. Trunking (Non-protocol): Defines the usage of multiple iSCSI data ports in parallel to increase the link speed beyond the limits of any single port. The usage occasion of Trunking: A. This is a simple SAN environment. There is only one switch to connect the server and storage. And there is no extra server to be added in the future. B. There is no idea of using LACP or Trunking, uses Trunking first. C.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 6 Troubleshooting 6.1 System Buzzer The system buzzer features are listed below: 1. 2. The system buzzer alarms 1 second when system boots up successfully. The system buzzer alarms continuously when there is error occurred. The alarm will be stopped after error resolved or be muted. The alarm will be muted automatically when the error is resolved. E.g.
iSCSI GbE to SAS/SATA II RAID Subsystem INFO ERROR WARNIN G INFO ERROR INFO ERROR WARNIN G ERROR ERROR WARNIN G WARNIN G ERROR ERROR INFO WARNIN G ERROR ERROR WARNIN G WARNIN G Power work Power warning Power detect Power - function is restored. Power
- is not functioning. PSU signal detection
- . Fan work Fan warning Fan installed Fan not present Thermal warning Fan
- function is restored. Fan
- is not functioning. Fan
- is installed. Fan
- is not present.
iSCSI GbE to SAS/SATA II RAID Subsystem INFO INFO INFO INFO INFO INFO WARNIN G INFO INFO WARNIN G INFO INFO ERROR INFO INFO INFO INFO INFO INFO INFO INFO WARNIN G WARNIN G WARNIN G ERROR ERROR WARNIN G WARNIN G ERROR Read-only caching enabled Writeback caching enabled Write-through caching enabled VD extended VD initialization started VD initialization finished VD initialization failed VD rebuild started VD rebuild finished VD rebuild failed . Cache policy of VD has been set as read only.
iSCSI GbE to SAS/SATA II RAID Subsystem ERROR WARNIN G WARNIN G WARNIN G WARNIN G INFO Unrecoverable write error occurred Dedicated spare configured Global spare configured PD read error occurred PD write error occurred Parity wrong when scrubbing Data recovered when scrubbing PD freed INFO RG imported INFO RG restored INFO VD restored INFO INFO RG owner changed Disk scrubbing started Disk scrubbing finished RG created INFO RG created INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO WAR
iSCSI GbE to SAS/SATA II RAID Subsystem INFO INFO INFO iSCSI login succeeds iSCSI login rejected iSCSI logout iSCSI login from was rejected, reason [] iSCSI logout from was received, reason []. Battery backup events Level iSCSI login from succeeds.
iSCSI GbE to SAS/SATA II RAID Subsystem INFO WARNIN G INFO PS normal WARNIN G INFO FAN failure WARNIN G WARNIN G WARNIN G WARNIN G INFO Volt warn OV WARNIN G WARNIN G WARNIN G WARNIN G INFO Therm warn OT FAN normal Volt warn UV Volt crit OV Volt crit UV Volt recovery Therm warn UT Therm fail OT Therm fail UT Therm recovery JBOD PD completed disk scrubbing process.
iSCSI GbE to SAS/SATA II RAID Subsystem Appendix A. Certification list RAM RAM Spec: 240-pin, DDR2-533(PC4300), Reg.(register) or UB(Unbufferred), ECC, up to 2GB, 64-bit data bus width (and also 32-bit memory support), x8 or x16 devices, 36-bit addressable, up to 14-bit row address and 10-bit column address.
iSCSI GbE to SAS/SATA II RAID Subsystem 3. Mac build-in iSCSI initiator iscsi-initiator-utils-4.0.3.0-4 in kernel 2.6.9 For Red Hat Enterprise Linux 5 (Kernel 2.6), use the build-in iSCSI initiator iscsi-initiator-utils-6.2.0.7420.5.el5 in kernel 2.6.18 ATTO Xtend SAN iSCSI initiator v3.10 System Requirements: 1. Mac OS X v10.5 or later For ATTO Xtend SAN iSCSI initiator, it is not free. Please contact your local distributor.
iSCSI GbE to SAS/SATA II RAID Subsystem Hitachi Hitachi Hitachi Maxtor Maxtor Samsung Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Westem Westem Westem Westem Digital Digital Digital Digital Westem Digital Westem Digital Westem Digital Deskstar 7K80, HDS728040PLA320, 40GB, 7200RPM, SATA II, 2M Deskstar T7K500, HDT725032VLA360, 320GB, 7200RPM, SATA II, 16M Deskstar P7K500, HDP725050GLA360, 500GB, 7200RPM, SATA II, 16M DiamondMax Plus 9, 6Y080M0, 80GB, 7200RPM, SATA, 8M
iSCSI GbE to SAS/SATA II RAID Subsystem B. Known issues 1. Microsoft MPIO driver is not supported on Windows XP and Windows 2000 Professional. Workaround solution: Use Windows Server 2008/2003 or Windows 2000 Server to run MPIO. 2. When two controllers (with SAS JBOD expansion ports) connect to JBOD expansion chassis (SAS JBOD), they can not detect all PDs of JBOD. Workaround solution: It’s a JBOD limitation. C. Microsoft iSCSI Initiator Here is the step by step to setup Microsoft iSCSI Initiator.
iSCSI GbE to SAS/SATA II RAID Subsystem 5. Click “Targets”. 6. Click “Log On”. Check “Enable multi-path” if running MPIO. 7. Click “Advance…” if CHAP information is needed. 8. Click “OK”. The status would be “Connected”. 9. Done, it can connect to an iSCSI disk. The following procedure is to log off iSCSI device. 1. Click “Details” in “Targets”. 2. Check the Identifier, which will be deleted. 3. Click “Log off”. 4. Done, the iSCSI device is logged off successfully.
iSCSI GbE to SAS/SATA II RAID Subsystem D. Installation steps for large volume (over 2TB) Introduction: This iSCSI RAID subsystem is capable of supporting large volumes (>2TB). When connecting the iSCSI RAID system to host/server with 64bit OS installed, the host/server is inherently capable for large volumes from the 64bit address.
iSCSI GbE to SAS/SATA II RAID Subsystem In the figure above, choose “OK” for 64bit OS, choose “Cancel” for 32bit OS, this step will change block size to 4K automatically. 2. Move the mouse pointer to the gray button next to the VD number; click “More information”. Look at the block size; 512B for 64bit OS setting, 4K for 32bit OS setting. Step 2: Configure host/server 1. Follow the installation guide provided by HBA vendor, install HBA driver properly.
iSCSI GbE to SAS/SATA II RAID Subsystem 2. Initialize the disk. 3. Convert to GPT disk for over 2TB capacity. For more detail information about GPT, please visit http://www.microsoft.com/whdc/device/storage/GPT_FAQ.mspx 4. Format the disk. 5. Done.
iSCSI GbE to SAS/SATA II RAID Subsystem 6. The new disk is ready to be used, with available size = 2.72TB. WARNING! If VD is setup using 512B block size and the host/server OS is 32bit, in the last step of formatting disk, the OS cannot format the disk sector after 2048GB (2TB). 7. Wrong setting result: OS can not format disk sector after 2048GB(2TB).
