iSCSI GbE to SAS/SATA II RAID Subsystem User Manual Revision 1.
iSCSI GbE to SAS/SATA II RAID Subsystem Table of Contents Preface ................................................................................................................................ 6 Before You Begin ............................................................................................................. 7 Safety Guidelines ............................................................................................................................................................
iSCSI GbE to SAS/SATA II RAID Subsystem 4.1 Management Interfaces...................................................................................................................................... 37 4.1.1 Serial Console Port ....................................................................................................................................... 37 4.1.2 Remote Control – Secure Shell ......................................................................................................
iSCSI GbE to SAS/SATA II RAID Subsystem 5.5.4 5.6 Hard Drive S.M.A.R.T. Support ................................................................................................................. 89 System Maintenance ........................................................................................................................................... 91 5.6.1 System Information ...........................................................................................................................
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 7 Troubleshooting .................................................................................... 135 7.1 System Buzzer ......................................................................................................................................................135 7.2 Event Notifications .............................................................................................................................................
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 The shipping package contains the following: iSCSI RAID Subsystem Unit Two (2) power cords Five (5) Ethernet LAN cables for single controller Note: Ten (10) Ethernet LAN cables for dual controller One (1) External null modem cable Note: Two (2) External null modem cables for dual controller User Manual NOTE: If any damage is found, contact the dealer or vendor for assistance.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 1 Introduction The iSCSI RAID Subsystem The EP-2124 series RAID subsystem features four Gigabit ports on each controller to increase system efficiency and performance. It features high capacity expansion, with 12 hot-swappable SAS/SATA II hard disk drive bays in a 19-inch 2U rackmount unit, scaling to a maximum storage capacity in the terabyte range.
iSCSI GbE to SAS/SATA II RAID Subsystem Features Front-end 4/8 x 1Gb ports support independent access, fail-over and loadbalancing (802.
iSCSI GbE to SAS/SATA II RAID Subsystem 1.
iSCSI GbE to SAS/SATA II RAID Subsystem Snapshot rollback mechanism support Yes Platform Rackmount Form Factor 2U # of Hot Swap Trays 12 Tray Lock Yes Disk Status Indicator Access / Fail LED Backplane SAS2 / SATA3 Single BP # of PS/Fan Modules 460W x 2 w/PFC # of Fans 2 Power requirements AC 90V ~ 264V Full Range, 10A ~ 5A, 47Hz ~ 63Hz Relative Humidity 10% ~ 85% Non-condensing Operating Temperature 10°C ~ 40°C (50°F ~ 104°F) Physical Dimension 555(L) x 482(W) x 88(H) mm Weight (W
iSCSI GbE to SAS/SATA II RAID Subsystem 1.2 Terminology The document uses the following terms: RAID Redundant Array of Independent Disks. There are different RAID levels with different degree of data protection, data availability, and performance to host environment. PD The Physical Disk belongs to the member disk of one specific RAID group. RG Raid Group. A collection of removable media. One RG consists of a set of VDs and owns one RAID level attribute. VD Virtual Disk.
iSCSI GbE to SAS/SATA II RAID Subsystem DG DeGraded mode. Not all of the array’s member disks are functioning, but the array is able to respond to application read and write requests to its virtual disks. SCSI Small Computer Systems Interface. SAS Serial Attached SCSI. S.M.A.R.T. Self-Monitoring Analysis and Reporting Technology. WWN World Wide Name. HBA Host Bus Adapter. SES SCSI Enclosure Services. NIC Network Interface Card.
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 Level 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 Identifying Parts of the RAID Subsystem The illustrations below identify the various parts of the subsystem. 2.1 Main Components 2.1.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.1.2.1 Disk Trays HDD Status Indicator Part Function HDD Activity LED This LED will blink blue when the hard drive is being accessed. HDD Fault LED Green LED indicates power is on and hard drive status is good for this slot. If hard drive is defective or failed, the LED is Red. LED is off when there is no hard drive.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.1.2.2 LCD Front Panel Smart Function Front Panel The smart LCD panel is an option to configure the RAID subsystem. If you are configuring the subsystem using the LCD panel, press the Select button to login and configure the RAID subsystem. Parts Function Up and Down Arrow buttons Use the Up or Down arrow keys to go through the information on the LCD screen. This is also used to move between each menu when you configure the subsystem.
iSCSI GbE to SAS/SATA II RAID Subsystem Environment Status LEDs Parts Function Power LED Green LED indicates power is ON. Power Fail LED If a redundant power supply unit fails, this LED will turn to RED and alarm will sound. Fan Fail LED When a fan fails or the fan’s rotational speed is below 1500RPM, this LED will turn red and an alarm will sound.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.1.
iSCSI GbE to SAS/SATA II RAID Subsystem 1. Controller Module The subsystem has one or two controller modules. 2. Power Supply Unit 1 ~ 2 Two power supplies (power supply 1 and power supply 2) are located at the rear of the subsystem. Each PSFM has one Power Supply and one Fan. The PSFM 1 has Power#1, Fan#1. The PSFM 2 has Power#2, Fan#2. Turn on the power of these power supplies to power-on the subsystem. The “power” LED at the front panel will turn green.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.2.1 Controller Module Panel 1. 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. 2.
iSCSI GbE to SAS/SATA II RAID Subsystem 7. BBM Status LED Green BBM installed and powered Off No BBM 8. BBM Status Button When the system power is off, press the BBM status button, if the BBM LED is Green, then the BBM still has power to keep data on the cache. If not, then the BBM power is ran out and cannot keep the data on the cache anymore. 2.3 Power Supply / Fan Module (PSFM) The RAID subsystem contains two 460W Power Supply / Fan Modules.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.3.1 PSFM Panel The panel of the Power Supply/Fan Module contains: the Power On/Off Switch, the AC Inlet Plug, FAN fail Indicator, and a Power On/Fail Indicator showing the Power Status LED, indicating ready or fail. Each fan within a PSFM is powered independently of the power supply within the same PSFM. So if the power supply of a PSFM fails, the fan associated with that PSFM will continue to operate and cool the enclosure.
iSCSI GbE to SAS/SATA II RAID Subsystem 2.4 Checklist before Starting Before starting, check or prepare the following items. Check “Certification list” in Appendix A to confirm the hardware setting is fully supported. Read the latest release note before upgrading. Release note accompany with release firmware. A server with a NIC or iSCSI HBA. CAT 5e, or CAT 6 network cables for management port and iSCSI data ports. Recommend CAT 6 cables for best performance.
iSCSI GbE to SAS/SATA II RAID Subsystem User Manual 27
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 3 Getting Started with the Subsystem 3.1 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.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.3 Disk Drive Installation 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. 3.3.1 Installing a SAS Disk Drive in a Disk Tray 1. Unlock the Disk Trays using a flat-head screw driver by rotating the Lock Groove. 2.
iSCSI GbE to SAS/SATA II RAID Subsystem 4. Place the hard drive in the disk tray. Turn the disk tray upside down. Align the four screw holes of the SAS disk drive in the four Hole A of the disk tray. To secure the disk drive into the disk tray, tighten four screws on these holes of the disk tray. Note in the picture below where the screws should be placed in the disk tray holes. Tray Hole A NOTE: All the disk tray holes are labelled accordingly.
iSCSI GbE to SAS/SATA II RAID Subsystem 5. Slide the tray into a slot. 6. Press the lever in until you hear the latch click into place. The HDD Fault LED will turn green when the subsystem is powered on and HDD is good. 7. If necessary, lock the Disk Tray by turning the Lock Groove.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.3.2 Installing a SATA Disk Drive (Dual Controller Mode) in a Disk Tray 1. Remove an empty disk tray from the subsystem. 2. Prepare the dongle board and two screws. 3. Place the dongle board in the disk tray. Turn the tray upside down. Align the two screw hole of the dongle board in the two Hole D of the disk tray. Tighten two screws to secure the dongle board into the disk tray.
iSCSI GbE to SAS/SATA II RAID Subsystem Tray Hole D NOTE: All the disk tray holes are labelled accordingly. 4. Place the SATA disk drive into the disk tray. Slide the disk drive towards the dongle board.
iSCSI GbE to SAS/SATA II RAID Subsystem 5. Turn the disk tray upside down. Align the four screw holes of the SATA disk drive in the four Hole C of the disk tray. To secure the disk drive into the disk tray, tighten four screws on these holes of the disk tray. Note in the picture below where the screws should be placed in the disk tray holes. Tray Hole C NOTE: All the disk tray holes are labelled accordingly. 6. Insert the disk tray into the subsystem.
iSCSI GbE to SAS/SATA II RAID Subsystem 3.4 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 Chapter 4 Quick Setup 4.1 Management Interfaces There are three management methods to manage the iSCSI RAID subsystem described as follows: 4.1.1 Serial Console Port Use NULL modem cable to connect console port. The console settings are on the following: Baud rate: 115200, 8 bits, 1 stop bit, and no parity. Terminal type: vt100 Login name: admin Default password: 00000000 4.1.2 Remote Control – Secure Shell SSH (secure shell) is required for remote login.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.1.3 LCD Control Module (LCM) 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 (up) and (down).
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] [Yes No] [Reset] [Reset/Shutdown] [Shutdown] [Quick Install] [Volume Wizard] proIPS [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] 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. 4.1.4 Web GUI 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.50 (Please check the DHCP address first on LCM) Click any function at the first time; it will pop up a dialog window for authentication.
iSCSI GbE to SAS/SATA II RAID Subsystem There are seven indicators at the top-right corner. RAID light: Green RAID works well. Red RAID fails. Temperature light: Green Temperature is normal. Red Temperature is abnormal. Voltage light: Green voltage is normal. Red voltage is abnormal. UPS light: Green UPS works well. Red UPS fails. Fan light: Green Fan works well. Red Fan fails. Power light: Green Power works well. Red Power fails.
iSCSI GbE to SAS/SATA II RAID Subsystem 4.2 How to Use the System Quickly 4.2.1 Quick Installation Please make sure that there are some free drives installed in this system. SAS drivers are recommended. Please check the hard drive details in “/ Volume configuration / Physical disk”. Step 1: Click “Quick installation” menu item. Follow the steps to set up system name and date/time.
iSCSI GbE to SAS/SATA II RAID Subsystem Step2: Confirm the management port IP address and DNS, and then click “Next”. Step 3: Set up the data port IP and click “Next”.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 4: Set up the RAID level and volume size and click “Next”. Step 5: Check all items, and click “Finish”.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 6: Done. 4.2.2 Volume Creation Wizard “Volume create wizard” has a smarter policy. When the system is inserted with some HDDs. “Volume create wizard” lists all possibilities and sizes in different RAID levels, it will use all available HDDs for RAID level depends 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 1: Select “Volume create wizard” and then choose the RAID level. After the RAID level is chosen, click “Next”. Step 2: Please select the combination of the RG capacity, or “Use default algorithm” for maximum RG capacity. After RG size is chosen, click “Next”.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 3: Decide VD size. User can enter a number less or equal to the default number. Then click “Next”. Step 4: Confirmation page. Click “Finish” if all setups are correct. Then a VD will be created. Step 5: Done. The system is available now. NOTE: A virtual disk of RAID 0 is created and is named by system itself.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 5 Configuration 5.1 Web GUI Management Interface Hierarchy The below table is the hierarchy of the management GUI.
iSCSI GbE to SAS/SATA II RAID Subsystem Maintenance System information Event log Upgrade Firmware sync hronization Reset to factor y default Import and export Reboot and shu tdown Quick installation Volume creation wizard System information Download / Mute / Clear Browse the firmware to upgrade Synchronize the slave controller’s firmware version with the master’s Sure to reset to factory default? Import/Export / Import file Reboot / Shutdown Step 1 / Step 2 / Step 3 / Step 4 / Confirm Step 1 /
iSCSI GbE to SAS/SATA II RAID Subsystem 5.2 System Configuration “System configuration” is designed for setting up the “System setting”, “Network setting”, “Login setting”, “Mail setting”, and “Notification setting”. 5.2.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.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.2.2 Network Setting “Network setting” is for changing IP address for remote administration usage. There are 2 options, DHCP (Get IP address from DHCP server) and 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 5.2.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 5.2.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 5.2.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 Configuration The following configuration is a sample for target and log server setting: Target side Go to \System configuration\Notification setting\System log server. Fill the fields Server IP/hostname: enter the IP address or hostname of system log server. UDP Port: enter the UDP port number on which system log server is listening to. The default port number is 514. 5. Facility: select the facility for event log. 6. Event level: Select the event log options. 7.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.3 iSCSI Configuration “iSCSI configuration” is designed for setting up the “Entity Property”, “NIC”, “Node”, “Session”, and “CHAP account”. 5.3.1 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.
iSCSI GbE to SAS/SATA II RAID Subsystem IP settings: User can change IP address by moving the mouse to the gray button of LAN port, click “IP settings for iSCSI ports”. There are 2 selections, DHCP (Get IP address from DHCP server) or static IP. Default gateway: Default gateway can be changed by moving the mouse to the gray button of LAN port, click “Become default gateway”. There is only one default gateway.
iSCSI GbE to SAS/SATA II RAID Subsystem 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. LACP: The Link Aggregation Control Protocol (LACP) is part of IEEE specification 802.3ad that allows bundling several physical ports together to form a single logical channel. LACP allows a network switch to negotiate an automatic bundle by sending LACP packets to the peer.
iSCSI GbE to SAS/SATA II RAID Subsystem Ping host: User can ping the corresponding host data port from the target, click “Ping host”. A user can ping host from the target to make sure the data port connection is well.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.3.2 Entity Property “Entity property” can view the entity name of the system, 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. Using iSNS, it needs to install an iSNS server in SAN. Add an iSNS server IP address into iSNS server lists in order that iSCSI initiator service can send queries. The entity name can be changed.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.3.3 Node “Node” can be used to view the target name for iSCSI initiator. There are 32 default nodes created for each controller. CHAP: CHAP is the abbreviation of Challenge Handshake Authorization Protocol. CHAP is a strong authentication method used in point-to-point for user login. It’s a type of authentication in which the authentication server sends the client a key to be used for encrypting the username and password.
iSCSI GbE to SAS/SATA II RAID Subsystem 4. Click “OK”. 5. Go to “/ iSCSI configuration / CHAP account” page to create CHAP account. Please refer to next section for more detail. Check the gray button of “OP.” column, click “User”. Select CHAP user(s) which will be used. It’s a multi option; it can be one or more. If choosing none, CHAP cannot work. 6. 7. 8. 9. Click “OK”. In “Authenticate” of “OP” page, select “None” to disable CHAP.
iSCSI GbE to SAS/SATA II RAID Subsystem Change portal: Users can change the portals belonging to the device node of each controller. 1. 2. 3. 4. Check the gray button of “OP.” column next to one device node. Select “Change portal”. Choose the portals for the controller. Click “OK” to confirm. Rename alias: User can create an alias to one device node. 1. 2. 3. 4. 5. Check the gray button of “OP.” column next to one device node. Select “Rename alias”. Create an alias for that device node.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.3.4 Session “Session” can display iSCSI session and connection information, including the following items: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. TSIH (target session identifying handle) Host (Initiator Name) Controller (Target Name) InitialR2T(Initial Ready to Transfer) Immed.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.3.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. 2. Click “Create”. Enter “User”, “Secret”, and “Confirm” secret again. “Node” can be selected here or later. If selecting none, it can be enabled later in “/ iSCSI configuration / Node / User”. 3. Click “OK”. 4. Click “Delete” to delete CHAP account.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.4 Volume Configuration “Volume configuration” is designed for setting up the volume configuration which includes “Physical disk”, “RAID group”, “Virtual disk”, “Snapshot”, and “Logical unit”. 5.4.1 Physical Disk “Physical disk” can be used to view the status of hard drives in the system. The following are operational tips: 1. 2. Check the gray button next to the number of slot, it will show the functions which can be executed.
iSCSI GbE to SAS/SATA II RAID Subsystem Physical Disk: Physical disks in slot 1, 2, 3 are created for a RG named “RG-R5”. Slot 4 is set as dedicated spare disk of the RG named “RG-R5”. The others are free disks.) Step 4: The unit of size can be changed from (GB) to (MB). It will display the capacity of hard drive in MB. 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.
iSCSI GbE to SAS/SATA II RAID Subsystem “Good” the hard drive is good. “Failed” the hard drive is failed. “Error Alert” S.M.A.R.T. error alert. “Read Errors” the hard drive has unrecoverable read errors. Usage The usage of hard drive: “RAID disk” This hard drive has been set to a RAID group. “Free disk” This hard drive is free for use. “Dedicated spare” This hard drive has been set as dedicated spare of a RG.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.4.2 RAID Group “RAID group” can view the status of each RAID group, create, and modify RAID groups. The following is an example to create a RG. Step 1: Click “Create”, enter “Name”, choose “RAID level”, click “Select PD” to select PD, assign the RG’s “Preferred owner”. Then click “OK”. The “Write Cache” option is to enable or disable the hard drives’ write cache option.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 2: Confirm page. Click “OK” if all setups are correct. There is a RAID 0 with 4 physical disks, named “RG-R0”. The second RAID group is a RAID 5 with 3 physical disks, named “RG-R5” Step 3: Done. View “RAID group” page. RG column description: The button includes the functions which can be excuted. Name RAID group name. Total(GB)(MB) Total capacity of this RAID group. The unit can be displayed in GB or MB. Free(GB) (MB) Free capacity of this RAID group.
iSCSI GbE to SAS/SATA II RAID Subsystem RAID The RAID level of the RAID group. Current owner The owner of the RAID group. Please refer to next chapter for details. Preferred owner The preferred owner of the RAID group. The default owner is controller 1. RG operations description: Create Create a RAID group. Migrate Change the RAID level of a RAID group. Please refer to next chapter for details. Activate Activate a RAID group; it can be executed when RG status is offline.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.4.3 Virtual Disk “Virtual disk” can view the status of each Virtual disk, create, and modify virtual disks. The following is an example to create a VD. Step 1: Click “Create”, enter “Name”, select RAID group from “RG name”, enter required “Capacity (GB)/(MB)”, change “Stripe height (KB)”, change “Block size (B)”, change “Read/Write” mode, set virtual disk “Priority”, select “Bg rate” (Background task priority), and change “Readahead” option if necessary.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 2: Confirm page. Click “OK” if all setups are correct. Create a VD named “VD-01”, from “RG-R0”. The second VD is named “VD-02”, it’s initializing. Step 3: Done. View “Virtual disk” page. VD column description: The button includes the functions which can be executed. Name Virtual disk name. Size (GB) (MB) Total capacity of the virtual disk. The unit can be displayed in GB or MB. Right The right of virtual disk: Priority Bg rate “WT” Write Through.
iSCSI GbE to SAS/SATA II RAID Subsystem Type Health “Migrate” The virtual disk is being migrated. “Rollback” The virtual disk is being rolled back. “Scrubbing” The virtual disk is being scrubbed. “Parity checking” The virtual disk is being parity check. The type of virtual disk: “RAID” the virtual disk is normal. “BACKUP” the virtual disk is for clone usage.
iSCSI GbE to SAS/SATA II RAID Subsystem Delete Delete a Virtual disk. Set property Change the VD name, right, priority, bg rate and read ahead. Right: “WT” Write Through. “WB” Write Back. (Default) “RO” Read Only. Priority: “HI” HIgh priority. (Default) “MD” MiDdle priority. “LO” LOw priority. Bg rate: “4 / 3 / 2 / 1 / 0” Default value is 4. The higher number the background priority of a VD is, the more background I/O will be scheduled to execute.
iSCSI GbE to SAS/SATA II RAID Subsystem Cleanup snapshot Clean all snapshot VD related to the Virtual disk and release snapshot space. Take snapshot Take a snapshot on the Virtual disk. Auto snapshot Set auto snapshot on the Virtual disk. List snapshot List all snapshot VD related to the Virtual disk. More information Show Virtual disk detail information. 5.4.4 Snapshot “Snapshot” can view the status of snapshot, create and modify snapshots.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 3: Take a snapshot. In “/ Volume configuration / Snapshot”, click “Take snapshot”. It will link to next page. Enter a snapshot name. Step 4: Expose the snapshot VD. Move the mouse pointer to the gray button next to the Snapshot VD number; click “Expose”. Enter a capacity for snapshot VD. If size is zero, the exported snapshot VD will be read only. Otherwise, the exported snapshot VD can be read / written, and the size will be the maximum capacity to read/write.
iSCSI GbE to SAS/SATA II RAID Subsystem Snapshot column description: The button includes the functions which can be executed. Name Snapshot VD name. Used (GB) (MB) The amount of snapshot space that has been used. The unit can be displayed in GB or MB. Status The status of snapshot: Health “N/A” The snapshot is normal. “Replicated” The snapshot is for clone or QReplica usage. “Abort” The snapshot is over space and abort. The health of snapshot: “Good” The snapshot is good.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.4.5 Logical Unit “Logical unit” can view, create, and modify the status of attached logical unit number(s) of each VD. User can attach LUN by clicking the “Attach”. “Host” must enter with an iSCSI node name for access control, or fill-in wildcard “*”, which means every host can access the volume. Choose LUN number and permission, and then click “OK”. VD-01 is attached to LUN 0 and every host can access.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.4.6 Example The following is an example for creating volumes. Example 1 is to create two VDs and set a global spare disk. Example 1 Example 1 is to create two VDs in one RG, each VD uses global cache volume. Global cache volume is created after system boots up automatically. So, no action is needed to set CV. Then set a global spare disk. Eventually, 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 5. Done. RG has been created. A RAID 5 RG named “RG-R5” with 3 physical disks is created. Step 2: Create VD (Virtual disk). To create a data user volume, please follow these steps. 1. Select “/ Volume configuration / Virtual disk”. 2. Click “Create”. 3. Input a VD name, choose the RG when VD will be created, enter the VD capacity, select the stripe height, block size, read/write mode, set priority, modify Bg rate if necessary, and finally click “OK”. 4.
iSCSI GbE to SAS/SATA II RAID Subsystem Two VDs, “VD-R5-1” and “VD-R5-2”, were created from RG “RG-R5”. The size of “VDR5-1” is 50GB, and the size of “VD-R5-2” is 64GB. There is no LUN attached. Step 3: Attach LUN to VD. There are 2 methods to attach LUN to VD. 1. In “/ Volume configuration / Virtual disk”, move the mouse pointer to the gray button next to the VD number; click “Attach LUN”. 2. In “/ Volume configuration / Logical unit”, click “Attach”. The steps are as follows: 1. Select a VD. 2.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 4: Set global spare disk. To set global spare disks, please follow the procedures. 1. 2. 3. Select “/ Volume configuration / Physical disk”. Check the gray button next to the PD slot; click “Set global space”. “Global spare” status is shown in “Usage” column. 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.
iSCSI GbE to SAS/SATA II RAID Subsystem Step 7: Delete VD (Virtual disk). To delete the Virtual disk, 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 “Delete”. There will pop up a confirmation page, click “OK”. 3. Done. Then, the VDs are deleted. NOTE: When deleting VD, the attached LUN(s) related to this VD will be detached automatically. Step 8: Delete RG (RAID group).
iSCSI GbE to SAS/SATA II RAID Subsystem 5.5 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 5.5.1 Hardware Monitor “Hardware monitor” can be used to view the information of current voltage, temperature levels, and fan speed.
iSCSI GbE to SAS/SATA II RAID Subsystem 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”. For better protection and avoiding single short period of high temperature triggering auto shutdown, the RAID controller evaluates multiple conditions for triggering auto shutdown. Below are the details of when the Auto shutdown will be triggered. 1.
iSCSI GbE to SAS/SATA II RAID Subsystem UPS Type Select UPS Type. Choose Smart-UPS for APC, None for other vendors or no UPS. Shutdown Battery Level (%) When below the setting level, system will shutdown. Setting level to “0” will disable UPS. Shutdown Delay (s) If power failure occurred, and system can not return to value setting status, the system will shutdown. Setting delay to “0” will disable the function.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.5.3 SES SES represents SCSI Enclosure Services, one of the enclosure management standards. “SES configuration” can enable or disable the management of SES. Enable SES in LUN 0, and can be accessed from every host The SES client software is available at the following web site: SANtools: http://www.santools.com/ 5.5.4 Hard Drive S.M.A.R.T. Support S.M.A.R.T.
iSCSI GbE to SAS/SATA II RAID Subsystem 90 User Manual
iSCSI GbE to SAS/SATA II RAID Subsystem 5.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.6.2 Event Log “Event log” can view the event messages. Check the checkbox of INFO, WARNING, and ERROR to choose the level of event log display. Click “Download” button to save the whole event log as a text file with file name “log-ModelName-SerialNumber-DateTime.txt”. Click “Clear” button to clear all event logs. Click “Mute” button to stop alarm if system alerts. The event log is displayed in reverse order which means the latest event log is on the first page.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.6.3 Upgrade “Upgrade” can upgrade firmware. Please prepare new firmware file named “xxxx.bin” in local hard drive, then click “Browse” to select the file. Click “Confirm”, 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 5.6.4 Firmware Synchronization “Firmware synchronization” can synchronize the firmware version when controller 1 and controller 2’s firmware are different. In normal status, the firmware versions in controller 1 and 2 are the same as below figure. 5.6.5 Reset to Factory Default “Reset to factory default” allows user to reset controller to factory default setting. Reset to default value, the password is: 00000000, and IP address to default DHCP.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.6.6 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 which mean if one system already has valuable volumes in the disks and user may forget and overwrite it. Use import could return to original configuration.
iSCSI GbE to SAS/SATA II RAID Subsystem 5.7 Home/Logout/Mute In the right-upper corner of web UI, there are 3 individual icons, “Home”, “Logout”, and “Mute”. 5.7.1 Home Click “Home” to return to home page 5.7.2 Logout For security reason, please use “Logout” to exit the web UI. To re-login the system, please enter username and password again. 5.7.3 Mute Click “Mute” to stop the alarm when error occurs.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 6 Advanced Operations 6.1 Volume 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 6.2 RG Migration To migrate the RAID level, please follow the steps below. 1. Select “/ Volume configuration / RAID group”. 2. Check 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 RAID level, click “Select PD” to increase hard drives, then click “OK “ 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 6.3 VD Extension To extend VD size, please follow the procedures. 1. Select “/ Volume configuration / Virtual disk”. 2. Check 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 “OK” 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 6.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 6.4.1 Create Snapshot Volume To take a snapshot of the data, please follow the procedures. 1. Select “/ Volume configuration / Virtual disk”. 2. Check 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 “OK“. It will go back to the VD page and the size will show in snapshot column.
iSCSI GbE to SAS/SATA II RAID Subsystem 1. 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 “Cleanup”. 2. “Cleanup snapshot” 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 6.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 “Auto snapshot”. 2. The auto snapshot can be set monthly, weekly, daily, or hourly. 3. Done.
iSCSI GbE to SAS/SATA II RAID Subsystem 6.4.3 Rollback The data in snapshot VD can rollback to original VD. Please follow the steps. 1. Select “/ Volume configuration / Snapshot”. 2. Check 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 6.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. Check 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 2. Create two virtual disks (VD) “SourceVD_R5” and “TargetVD_R6”. The raid type of backup target needs to be set as “BACKUP”. 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 “Configuration”. 4. There are three clone configurations, describe on the following.
iSCSI GbE to SAS/SATA II RAID Subsystem Snapshot space: This setting is the ratio of source VD and snapshot space. The default ratio is 2 to 1. It means when the clone process is starting, the system will automatically use the free RG space to create a snapshot space which capacity is double the source VD. Threshold: (The setting will be effective after enabling schedule clone) The threshold setting will monitor the usage amount of snapshot space.
iSCSI GbE to SAS/SATA II RAID Subsystem When running out of snapshot space, the VD clone process will be stopped because there is no more available snapshot space. If this option has been checked, system will clear the snapshots of clone in order to release snapshot space automatically, and the VD clone will restart the task after an hour. This task will start a full copy. 5. After deploying the VD clone rule, the VD clone process can be started now.
iSCSI GbE to SAS/SATA II RAID Subsystem 8. Click “Start clone”, the clone process will start. 9. The default setting will create a snapshot space automatically which the capacity is double size of the VD space. Before starting clone, system will initiate the snapshot space. 10. After initiating the snapshot space, it will start cloning.
iSCSI GbE to SAS/SATA II RAID Subsystem 11. Click “Schedule clone” to set up the clone by 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 in 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 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. Next time, when trying to start clone, it will get a warning message “This is not enough of snapshot space for the operation”. At this time, the user needs to clean up the snapshot space in order to operate the clone process.
iSCSI GbE to SAS/SATA II RAID Subsystem 6.7 SAS JBOD Expansion 6.7.1 Connecting JBOD iSCSI RAID controller suports SAS JBOD expansion to connect extra SAS dual JBOD controller. When connecting a dual JBOD controller which can be detected in RAID Subsystem management GUI, it will be displayed in “Show PD for:” under “/ Volume configuration / Physical disk” menu. For example, Local, JBOD 1, JBOD 2, …etc.
iSCSI GbE to SAS/SATA II RAID Subsystem “/ Enclosure management / Hardware monitor” can display the hardware status of SAS JBODs.
iSCSI GbE to SAS/SATA II RAID Subsystem 116 User Manual
iSCSI GbE to SAS/SATA II RAID Subsystem “/ Enclosure management / S.M.A.R.T.” can display S.M.A.R.T. information of all PDs, including Local and all SAS JBODs. SAS JBOD expansion has some constraints as described in the followings: 1 2 3 User can create RAID group among multiple chassis/enclosures; the maximum number of disks in a single RAID group is 32. Global spare disk can support all RAID groups which can be located in the different chassis/enclosure.
iSCSI GbE to SAS/SATA II RAID Subsystem 6.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 6.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. The iSCSI subsystem implements link aggregation as LACP and Trunking. 1.
iSCSI GbE to SAS/SATA II RAID Subsystem IMPORTANT! Before using trunking or LACP, he gigabit switch must support trunking or LACP and enabled. Otherwise, host cannot connect the link with storage device.
iSCSI GbE to SAS/SATA II RAID Subsystem 6.10 Dual Controllers 6.10.1 Perform I/O Please refer to the following topology and have all the connections ready. To perform I/O on dual controllers, server/host should setup MPIO. MPIO policy will keep I/O running and prevent fail connection with single controller failure.
iSCSI GbE to SAS/SATA II RAID Subsystem 6.10.2 Ownership When creating RG, it will be assigned with a prefered owner, the default owner is controller 1. To change the RG ownership, please follow the procedures. 1. Select “/ Volume configuration / RAID group”. 2. Check the gray button next to the RG name; click “Set preferred owner”. 3. The ownership of the RG will be switched to the other controller. The RG ownership is changed to the other controller. 6.10.
iSCSI GbE to SAS/SATA II RAID Subsystem 4. Single: Single controller mode. In the stage, the controller must stay in slot A. Boards for SATA drives are not necessary. The differences between single and degraded are described on the following. There is no error message for inserted one controller only. I/O will not force to write through. And there is no ownership of RG. Single controller mode can be upgraded to dual controller mode, please contact the distributor for upgradable.
iSCSI GbE to SAS/SATA II RAID Subsystem 6.11 QReplica (Optional) QReplica function will help users to replicate data easily through LAN or WAN from one subsystem to another. The procedures of QReplica are on the following: 1. Copy all data from source VD to target VD at the beginning (full copy). 2. Use 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 2. The setting can be reverted by select “Disable QReplica” in the operation menu. Create backup VD on the target subsystem 1. Before creating the replication job on the source subsystem, user has to create a virtual disk on the target subsystem and set the type of the VD as “Backup”.
iSCSI GbE to SAS/SATA II RAID Subsystem 2. The backup VD needs to be attached to a LUN ID first before creating replication job. Create replication job on the source subsystem 1. If the license key is activated on the subsystem correctly, a new QReplica tab will be added on the Web UI. Click “Create” to create a new replication job.
iSCSI GbE to SAS/SATA II RAID Subsystem 2. Select the source VD which will be replicated to the target subsystem and click “Next”. NOTE: If the message displays that there is not enough space for creation, please refer to the section of Configure the snapshot space below for solution. 3. Enter the IP address of iSCSI port on controller 1 of the target subsystem. Click “Next” to continue.
iSCSI GbE to SAS/SATA II RAID Subsystem 4. The QReplica uses standard iSCSI protocol for data replication. User has to log on the iSCSI node to create the iSCSI connection for the data transmission. Enter the CHAP information if necessary and select the target node to log no. Click “Next” to continue. 5. Choose the backup VD and click “Next”.
iSCSI GbE to SAS/SATA II RAID Subsystem 6. A new replication job is created and listed on the QReplica page. Run the replication job 1. Click the “OP” button on the replication job to open operation menu. Click “Start” to run the replication job. 2. Click “Start” again to confirm the execution of the replication job.
iSCSI GbE to SAS/SATA II RAID Subsystem 3. User can monitor the replication job from the “Status” information and the progress is expressed by percentage. Create multi-path on the replication job 1. Click the “Create multi-path” in the operation menu of the replication job. 2. Enter the IP of iSCSI port on controller 2 of the target subsystem.
iSCSI GbE to SAS/SATA II RAID Subsystem 3. Select the iSCSI node to log on and click “Next”. 4. Choose the same target VD and click “Next”. 5. A new target will be added in this replication job as a redundancy path.
iSCSI GbE to SAS/SATA II RAID Subsystem Configure the replication job to run by schedule 1. Click “Schedule” in the operation menu of the replication job. 2. The replication job can be scheduled to run by day, by week or by month. The execution time can be configurable per user’s need. Configure the snapshot space The QReplica uses Snapshot. The snapshot technique helps user to replicate the data without stop accessing to the source VD.
iSCSI GbE to SAS/SATA II RAID Subsystem 1. To configure the snapshot space settings of QReplica, click the “configuration” button. There are three settings in the QReplica configuration menu, The Snapshot space specifies the ratio of snapshot space allocated to the source VD automatically when the snapshot space is not configured in advance. The default ratio is 2 to 1.
iSCSI GbE to SAS/SATA II RAID Subsystem Chapter 7 Troubleshooting 7.1 System Buzzer The system buzzer features are listed below: 1. The system buzzer alarms 1 second when system boots up successfully. 2. The system buzzer alarms continuously when there is error occurred. The alarm will be stopped after error resolved or be muted. 3. The alarm will be muted automatically when the error is resolved. E.g.
iSCSI GbE to SAS/SATA II RAID Subsystem ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR INFO INFO INFO INFO Failed to allocate memory for SATA EDMA Failed to remap SATA memory io spcae Failed to init SATA PRD memory manager Failed to get SATA revision id Failed to set SATA register Core failed to initialize the SATA adapter SATA Adapter diagnostics failed SATA Mode ID failed SATA Chip count error SAS HBA port reply terminated abnormally SAS frontend reply terminated abnormally FC HBA por
iSCSI GbE to SAS/SATA II RAID Subsystem ERROR WARNING Voltage level 2 shutdown Voltage level 2 CTR shutdown UPS OK UPS fail UPS AC loss UPS power low SMART T.E.C.
iSCSI GbE to SAS/SATA II RAID Subsystem INFO INFO INFO INFO INFO WARNING INFO INFO WARNING INFO INFO ERROR INFO INFO INFO INFO INFO INFO INFO INFO INFO ERROR INFO INFO INFO INFO WARNING WARNING WARNING ERROR ERROR 138 User Manual OK VD attach LUN fail VD detach LUN OK VD detach LUN fail VD init started VD init finished VD init failed VD rebuild started VD rebuild finished VD rebuild failed VD migrate started VD migrate finished VD migrate failed VD scrub started VD scrub finished VD scrub aborted RG mig
iSCSI GbE to SAS/SATA II RAID Subsystem ERROR VD IO fault WARNING WARNING Recoverable read error Recoverable write error Unrecoverable read error Unrecoverable write error Config read fail Config write fail CV boot error adjust global CV boot global CV boot error create global PD dedicated spare PD global spare PD read error WARNING PD write error WARNING Scrub wrong parity WARNING Scrub data recovered WARNING Scrub recovered data Scrub parity recovered WARNING ERROR ERROR ERROR ERROR ERROR IN
iSCSI GbE to SAS/SATA II RAID Subsystem INFO WARNING INFO VD erase finished VD erase failed VD erase started Snap mem WARNING Snap space overflow Snap threshold Snap delete Snap auto delete Snap take Snap set space Snap rollback started Snap rollback finished Snap quota reached Snap clear space INFO INFO INFO INFO INFO INFO WARNING INFO VD starts erasing process. Description Failed to allocate snapshot memory for VD . Failed to allocate snapshot space for VD .
iSCSI GbE to SAS/SATA II RAID Subsystem INFO WARNING INFO INFO INFO BBM status charging BBM status fail BBM enabled BBM inserted BBM removed Battery backup module is charging Battery backup module is failed Battery backup feature is .
iSCSI GbE to SAS/SATA II RAID Subsystem INFO PS normal WARNING FAN fail INFO FAN normal WARNING Volt warn OV WARNING Volt warn UV WARNING Volt crit OV WARNING Volt crit UV INFO Volt recovery WARNING WARNING Therm warn OT Therm warn UT Therm fail OT WARNING Therm fail UT INFO Therm recovery WARNING System maintenance events Level INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO WARNING 142 FAIL Power Supply of in JBOD is NORMAL Cooling fan of in JB
iSCSI GbE to SAS/SATA II RAID Subsystem ERROR INFO failure IPC FW upgrade timeout Config imported config imported HAC events Level INFO INFO INFO INFO INFO INFO ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR INFO System firmware upgrade timeout on another controller Type Description RG owner changed Force CTR write through Restore CTR cache mode Failover complete Failback complete CTR inserted CTR removed CTR timeout CTR lockdown CTR memory NG CTR firmware NG CTR lowspeed NG CT
iSCSI GbE to SAS/SATA II RAID Subsystem WARNING WARNING Auto clone task: . Auto clone task: Snapshot is not found for VD .
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 4GB, 64-bit data bus width (and also 32-bit memory), 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 GbE iSCSI HBA card Vendor HP QLogic QLogic QLogic Model NC380T (PCI-Express, Gigabit, 2 ports, TCP/IP offload, iSCSI offload) QLA4010C (PCI-X, Gigabit, 1 port, TCP/IP offload, iSCSI offload) QLA4052C (PCI-X, Gigabit, 2 ports, TCP/IP offload, iSCSI offload) QLE4062C (PCI-Express, Gigabit, 2 ports, TCP/IP offload, iSCSI offload) GbE NIC Vendor HP HP IBM Intel Model NC7170 (PCI-X, Gigabit, 2 ports) NC360T (PCI-Express, Gigabit, 2 ports, TCP/IP offload) NetXt
iSCSI GbE to SAS/SATA II RAID Subsystem Seagate Seagate Seagate Seagate Seagate Seagate 16M (F/W: 003) Cheetah NS, ST3400755SS, 400GB, 10000RPM, SAS 3.0Gb/s, 16M Barracuda ES.2, ST31000640SS, 1TB, 7200RPM, SAS 3.0Gb/s, 16M (F/W: 0002) Cheetah NS.2, ST3600002SS, 600GB, 10000RPM, SAS 2.0, 6.0Gb/s, 16M (F/W: 0004) Cheetah 15K.7, ST3600057SS, 600GB, 15000RPM, SAS 2.0, 6.0Gb/s, 16MB (F/W: 0004) Constellation ES, ST31000424SS, 1TB, 7200RPM, SAS 2.0 6.
iSCSI GbE to SAS/SATA II RAID Subsystem Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Westem Digital Westem Digital Westem Digital Westem Digital Westem Westem Westem Westem Digital Digital Digital Digital Westem Digital Westem Digital Westem Digital Westem Digital Westem Digital Westem Digital Westem Digital Barracuda 7200.11, ST3500320AS, 500GB, 7200RPM, SATA 3.0Gb/s, 32M, NCQ Barracuda 7200.11, ST31000340AS, 1TB, 7200RPM, SATA 3.0Gb/s, 32M, NCQ Barracuda 7200.
iSCSI GbE to SAS/SATA II RAID Subsystem B. Microsoft iSCSI initiator Here is the step by step to setup Microsoft iSCSI Initiator. Please visit Microsoft website for latest iSCSI initiator. This example is based on Microsoft Windows Server 2008 R2. 1. 2. Connect Run Microsoft iSCSI Initiator. Input IP address or DNS name of the target. And then click “Quick Connect”.
iSCSI GbE to SAS/SATA II RAID Subsystem 3. Click “Done”. 4. It can connect to an iSCSI disk now.
iSCSI GbE to SAS/SATA II RAID Subsystem 5. MPIO Service Please run “Server Manager” with below path: Control Panel\System and Security\Administrative Tools 6. Click “Feature” and select Add Features. 7.
iSCSI GbE to SAS/SATA II RAID Subsystem 8. Install: 9. Installation succeeded.
iSCSI GbE to SAS/SATA II RAID Subsystem Starting iSCSI Initiator 10. Please run “iSCSI initiator” with below path: Control Panel\System and Security\Administrative Tools 11. Click Discovery tab Discover Portal 12.
iSCSI GbE to SAS/SATA II RAID Subsystem 13. Click Discover Portal 14.
iSCSI GbE to SAS/SATA II RAID Subsystem 15. Please connect ctrl1 16.
iSCSI GbE to SAS/SATA II RAID Subsystem 17. Please select the IP address for Initiator & Target of controller1 18. Please connect ctrl2.
iSCSI GbE to SAS/SATA II RAID Subsystem 19. Choose checkbox of “Enable multipath-path”. 20. Please select the IP address for Initiator & Target of controller2.
iSCSI GbE to SAS/SATA II RAID Subsystem 21. iSCSI initiator install finish. Setup MPIO 22.
iSCSI GbE to SAS/SATA II RAID Subsystem 23. Click tab of “Discover Multi-Paths” 24. Choose checkbox of “Add support for iSCSI devices 25.
iSCSI GbE to SAS/SATA II RAID Subsystem MC/S 26. If running MC/S, please continue. 27. Select one target name, click “Properties…”. 28. Click “MCS…” to add additional connections.
iSCSI GbE to SAS/SATA II RAID Subsystem 29. Click “Add…”. 30. Click “Advanced…”. 31. Select Initiator IP and Target portal IP, and then click “OK”. 32. Click “Connect”. 33. Click “OK”.
iSCSI GbE to SAS/SATA II RAID Subsystem 34. Done.
iSCSI GbE to SAS/SATA II RAID Subsystem Disconnect 35. Select the target name, click “Disconnect”, and then click “Yes”. 36. Done, the iSCSI device disconnect successfully.
