Thecus i8500 User Manual

Download

Thecus i8500

iSCSI RAID SYSTEM

User Manual

- 1 -

Preface

About this manual

This manual is the introduction of i8500 and it aims to help users know the operations of the disk array system easily. Information contained in this manual has been reviewed for accuracy, but not for product warranty because of the various environments/OS/settings, Information and specification will be changed without further notice. For any update information, please visit www.thecus.com and your contact windows.

question, please e-mail to “sales@thecus.com”. We will answer your question

as soon as possible.

The RAM size of i8500 is recommended DDR-333/400 512MB or above (Factory

default DDR-400 1G). Please refer to the certification list in Appendix A.

- 2 -

Table of Contents

1.1 Features........................................................................... 5

1.2 Terminology ..................................................................... 6

1.3 RAID levels ...................................................................... 8

1.4 Volume relationship diagram ........................................... 9

Chapter 2 Getting started.............................................10

2.1 Before starting................................................................ 10

2.2 iSCSI introduction .......................................................... 10

2.3 Management methods ................................................... 12

2.3.1 Web GUI hierarchy...............................................................................12

2.3.2 Remote control – secure shell .............................................................. 13

2.4 Enclosure ....................................................................... 13

2.4.1 LCM...................................................................................................... 13

2.4.2 System buzzer......................................................................................16

2.4.3 LED ......................................................................................................16

Chapter 3 Web GUI guideline.......................................17

3.1 Web GUI hierarchy ........................................................ 17

3.2 Login .............................................................................. 18

3.3 Volume creation wizard.................................................. 19

3.4 System configuration ..................................................... 20

3.4.1 System setting......................................................................................20

3.4.2 IP address ............................................................................................21

3.4.3 Login setting ......................................................................................... 22

3.4.4 Mail setting ...........................................................................................22

3.4.5 Notification setting ................................................................................ 23

3.5 iSCSI configuration ........................................................ 25

3.5.1 Entity property ......................................................................................25

3.5.2 NIC ....................................................................................................... 26

3.5.3 Node.....................................................................................................27

3.5.4 Session.................................................................................................28

3.5.5 CHAP account......................................................................................28

3.6 Volume configuration ..................................................... 29

3.6.1 Volume create wizard...........................................................................29

3.6.2 Physical disk......................................................................................... 32

3.6.3 RAID group........................................................................................... 35

3.6.4 Virtual disk............................................................................................38

3.6.5 Snapshot ..............................................................................................42

3.6.6 Logical unit ...........................................................................................44

3.6.7 Example ...............................................................................................45

3.7 Enclosure management ................................................. 50

3.7.1 SES configuration................................................................................. 50

3.7.2 Hardware monitor.................................................................................51

3.7.3 Hard drive S.M.A.R.T. support .............................................................52

3.7.4 UPS......................................................................................................53

3.8 System maintenance ..................................................... 54

- 3 -

3.8.1 System information............................................................................... 54

3.8.2 Upgrade................................................................................................54

3.8.3 Reset to factory default.........................................................................55

3.8.4 Import and export ................................................................................. 56

3.8.5 Event log ..............................................................................................56

3.8.6 Reboot and shutdown...........................................................................57

3.9 Logout ............................................................................ 57

Chapter 4 Advanced operation....................................58

4.1 Rebuild........................................................................... 58

4.2 RG migration.................................................................. 60

4.3 VD Extension ................................................................. 62

4.4 Snapshot / Rollback ....................................................... 62

4.4.1 Create snapshot volume.......................................................................63

4.4.2 Auto snapshot ......................................................................................65

4.4.3 Rollback................................................................................................66

4.5 Disk roaming .................................................................. 67

4.6 Support Microsoft MPIO and MC/S................................ 67

Appendix............................................................................69

A. Certification list............................................................... 69

Event notifications....................................................................... 71

C. Known issues................................................................. 76

D. Microsoft iSCSI Initiator ................................................. 77

E. Installation steps for large volume (TB).......................... 79

F. MPIO and MC/S setup instructions................................ 82

G. BBM (Battery Backup Module) inspect steps................. 84

G. BBM(Battery Backup Module) inspect steps -(Optional) .. 85

H. M/B Diagram .................................................................. 87

- 4 -

Chapter 1 RAID introduction

1.1 Features

i8500 controller features:

• Front-end 2 GbE NIC ports.

• iSCSI jumbo frame support.

• RAID 6, 60 ready.

• SATA II drives backward-compatible.

• One logic volume can be shared by as many as 8 hosts and 32

connections per system.

• Host access control.

• Configurable N-way mirror for high data protection.

• On-line volume migration with no system down-time.

• HDD S.M.A.R.T. enabled for SATA drives.

With proper configuration, i8500 can provide non-stop service with a high degree of fault tolerance by using i8500 RAID technology and advanced array management features. The controller features are slightly different between the backplane solution and cable solution. For more details, please contact your

direct sales or email to “sales@thecus.com ”.

i8500 connects to the host system in iSCSI interface. It can be configured to any RAID level. i8500 provides reliable data protection for servers and RAID 6. The RAID 6 allows two HDD failures without producing any impact on the existing data. Data can be recovered from the existing data and parity drives. (Data can be recovered from the rest disks/drives.)

Snapshot is a fully usable copy of a defined collection of data that contains an

image of the data as it appeared at the point in time, which means a point-in-time data replication. It provides consistent and instant copies of data volumes without any system downtime. Snapshot can keep up to 32 snapshots for all data

volumes. Rollback feature is provided for restoring the previous-snapshot data

easily while continuously using the volume for further data access. The data access which includes read/ write is working as usual without any impact to end users. The snapshot is taken at target side and done by i8500. It will not consume any host CPU time thus the server is dedicated to the specific or other application. The snapshot copies can be taken manually or by schedule every hour or every day, depends on the modification.

i8500 is the most cost-effective disk array controller with completely integrated high-performance and data-protection capabilities which meet or exceed the

highest industry standards, and the best data solution for small/medium

business (SMB) users.

- 5 -

Caution Snapshot / rollback features need 512MB RAM or more.

Please refer to RAM certification list in Appendix A for more detail.

1.2 Terminology

The document uses the following terms:

RAID

LUN

RAID is the abbreviation of “Redundant Array of Independent Disks”. There are different RAID levels with different degree

of the data protection, data availability, and performance to host environment.

The Physical Disk belongs to the member disk of one specific

RAID group.

Raid Group. A collection of removable media. One RG

consists of a set of VDs and owns one RAID level attribute.

Virtual Disk. Each RD could be divided into several VDs. The

VDs from one RG have the same RAID level, but may have different volume capacity.

Cache Volume. Controller uses onboard memory as cache.

All RAM (except for the part which is occupied by the controller) can be used as cache.

Logical Unit Number. A logical unit number (LUN) is a unique

identifier which enables it to differentiate among separate devices (each one is a logical unit).

GUI

RAID width, RAID copy, RAID row

(RAID cell in

Graphic User Interface.

RAID width, copy and row are used to describe one RG.

E.g.:

1. One 4-disk RAID 0 volume: RAID width= 4; RAID

one row)

2. One 3-way mirroring volume: RAID width=1; RAID

3. One RAID 10 volume over 3 4-disk RAID 1 volume:

copy=1; RAID row=1.

copy=3; RAID row=1.

- 6 -

RAID width=1; RAID copy=4; RAID row=3.

Write-Through cache-write policy. A caching technique in

which the completion of a write request is not signaled until data is safely stored in non-volatile media. Each data is synchronized in both data cache and accessed physical disks.

Write-Back cache-write policy. A caching technique in which

the completion of a write request is signaled as soon as the data is in cache and actual writing to non-volatile media occurs at a later time. It speeds up system write performance but needs to bear the risk where data may be inconsistent between data cache and the physical disks in one short time interval.

Set the volume to be Read-Only.

Dedicated Spare disks. The spare disks are only used by one

specific RG. Others could not use these dedicated spare disks for any rebuilding purpose.

Global Spare disks. GS is shared for rebuilding purpose. If

some RGs need to use the global spare disks for rebuilding, they could get the spare disks out from the common spare disks pool for such requirement.

SCSI

iSCSI

SAS

S.M.A.R.T.

Dedicated Cache.

Global Cache.

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.

Small Computer Systems Interface.

Internet Small Computer Systems Interface.

Serial Advanced Technology Attachment

Fibre Channel.

Self-Monitoring Analysis and Reporting Technology.

- 7 -

WWN

World Wide Name.

HBA

SAF-TE

SES

NIC

LACP

MPIO

MC/S

MTU

CHAP

iSNS

Host Bus Adapter.

SCSI Accessed Fault-Tolerant Enclosures.

SCSI Enclosure Services.

Network Interface Card.

Link Aggregation Control Protocol.

Multi-Path Input/Output.

Multiple Connections per Session

Maximum Transmission Unit.

Challenge Handshake Authentication Protocol. An optional

security mechanism to control access to an iSCSI storage

system over the iSCSI data ports.

Internet Storage Name Service.

1.3 RAID levels

RAID 0

RAID 1

N-way mirror

RAID 3

RAID 5

RAID 6

Disk striping. RAID 0 needs at least one hard drive.

Disk mirroring over two disks. RAID 1 needs at least two hard drives.

Extension to RAID 1 level. It has N copies of the disk.

Striping with parity on the dedicated disk. RAID 3 needs at least three hard drives.

Striping with interspersed parity over the member disks. RAID 3 needs at least three hard drives.

2-dimensional parity protection over the member disks. RAID 6 needs at least four hard drives.

- 8 -

RAID 0+1

Mirroring of the member RAID 0 volumes. RAID 0+1 needs at least four hard drives.

RAID 10

Striping over the member RAID 1 volumes. RAID 10 needs at least four hard drives.

RAID 30

Striping over the member RAID 3 volumes. RAID 30 needs at least six hard drives.

RAID 50

Striping over the member RAID 5 volumes. RAID 50 needs at least six hard drives.

RAID 60

Striping over the member RAID 6 volumes. RAID 60 needs at least eight hard drives.

JBOD

The abbreviation of “Just a Bunch Of Disks”. JBOD needs at

least one hard drive.

1.4 Volume relationship diagram

This is the volume structure of i8500 designed. It describes the relationship of RAID components. One RG (RAID group) consists of a set of VDs (Virtual disk) and owns one RAID level attribute. Each RG can be divided into several VDs. The VDs in one RG share the same RAID level, but may have different volume capacity. Each VD will be associated with one specific CV (Cache Volume) to

LUN 1 LUN 2 LUN

VD 1 VD 2

Snap

PD 2 PD 3 DS PD 1

Figure 1.4.1

Global CV

Dedicated

RAM

- 9 -

execute the data transaction. Each CV can have different cache memory size by user’s modification/setting. LUN (Logical Unit Number) is a unique identifier, in which users can access through SCSI commands.

Chapter 2 Getting started

2.1 Before starting

Before starting, prepare the following items.

1. Check “Certification list” in Appendix A to confirm the hardware

setting is fully supported.

2. Read the latest release note before upgrading. Release note accompany with release firmware.

3. A server with a NIC or iSCSI HBA.

4. CAT 5e, or CAT 6 network cables for management port and iSCSI data ports. Recommend CAT 6 cables for best performance.

5. Prepare storage system configuration plan.

6. Management and iSCSI data ports network information. When using static IP, please prepare static IP addresses, subnet mask, and default gateway.

7. Gigabit LAN switches. (recommended) Or Gigabit LAN switches with VLAN/LCAP. (optional)

8. CHAP security information, including CHAP username and secret. (optional)

9. Setup the hardware connection before power on servers and i8500. Connect console cable, management port cable, and iSCSI data port cables in advance.

2.2 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.

IP SANs are true SANs (Storage Area Networks) which allow few servers to attach to an infinite number of storage volumes by using iSCSI over TCP/IP networks. IP SANs can scale the storage capacity with any type and brand of storage system. In addition, it can be used by any type of network (Ethernet, Fast Ethernet, and Gigabit Ethernet) and combination of operating systems (Microsoft Windows, Linux, Solaris, etc.) within the SAN network. IP-SANs also include mechanisms for security, data replication, multi-path and high availability.

- 10 -

Storage protocol, such as iSCSI, has “two ends” in the connection. These ends are initiator and target. In iSCSI, we call them iSCSI initiator and iSCSI target. The iSCSI initiator requests or initiates any iSCSI communication. It requests all SCSI operations like read or write. An initiator is usually located on the host/server side (either an iSCSI HBA or iSCSI SW initiator).

The target is the storage device itself or an appliance which controls and serves volumes or virtual volumes. The target is the device which performs SCSI command or bridge to an attached storage device.

Host 1

(initiator)

NIC

Host 2

(initiator)

iSCSI

HBA

IP SAN

iSCSI device 1

(target)

iSCSI device 2

(target)

Figure 2.2.1

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 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) provide its own initiator tool. Please refer to the vendors’ HBA user manual. Microsoft, Linux and Mac provide iSCSI initiator driver. Below are the available links:

1. Link to download the Microsoft iSCSI software initiator:

http://www.microsoft.com/downloads/details.aspx?FamilyID=12cb3c1a15d6-4585-b385-befd1319f825&DisplayLang=en

Please refer to Appendix D for Microsoft iSCSI initiator installation procedure.

- 11 -

2. Linux iSCSI initiator is also available. For different kernels, there are different iSCSI drivers. Please check Appendix A for iSCSI initiator certification list. If user needs the latest Linux iSCSI initiator, please visit Open-iSCSI project for most update information. Linux-iSCSI (sfnet) and Open-iSCSI projects merged in April 11, 2005.

Open-iSCSI website: http://www.open-iscsi.org/ Open-iSCSI README: http://www.open-iscsi.org/docs/README Features: http://www.open-iscsi.org/cgi-bin/wiki.pl/Roadmap Support Kernels:

http://www.open-iscsi.org/cgi-bin/wiki.pl/Supported_Kernels

Google groups:

http://groups.google.com/group/open-iscsi/threads?gvc=2 http://groups.google.com/group/open-iscsi/topics

Open-iSCSI Wiki: http://www.open-iscsi.org/cgi-bin/wiki.pl

3. ATTO iSCSI initiator is available for Mac.

Website: http://www.attotech.com/xtend.html

2.3 Management methods

There are two management methods to manage i8500, describe in the following:

2.3.1 Web GUI hierarchy

i8500 support graphic user interface to manage the system. Be sure to connect LAN cable. The default setting of management port IP is Static IP and Static IP address displays on LCM; user can inspect LCM for IP first, then open the browser and type the Static IP address:

Take an example on LCM:

192.168.1.100 i8500

http://192.168.1.100

Click any function at the first time; it will pop up a dialog to authenticate current user.

- 12 -

Or login with read-only account which only allows reading the configuration and cannot change setting.

2.3.2 Remote control – secure shell

SSH (secure shell) is required for controllers to 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.1.100 (Please check your DHCP address for this field.) Login name: admin Default password: 1234

Tips i8500 controllers only support SSH for remote control. For

using SSH, the IP address and password are required for login.

2.4 Enclosure

2.4.1 LCM

There are four buttons to control LCM (LCD Control Module), including:

c (up), d (down), ESC (Escape), and ENT (Enter).

After booting up the system, the following screen shows management port IP and model name:

192.168.1.100 i8500 ←

Press “ENT”, the LCM functions “System Info.”, “Alarm Mute”,

“Reset/Shutdown”, “Quick Install”, “Volume Wizard”, “View IP Setting”, “Change IP Config” and “Reset to Default” will rotate by pressing c (up) and d (down).

- 13 -

When there is WARNING or ERROR occurred (LCM default filter), the LCM shows the event log to give users more detail from front panel.

The following table is function description.

System Info.

Alarm Mute

Reset/Shutdown

Quick Install

Volume Wizard

View IP Setting

Change IP Config

Reset to Default

Display system information.

Mute alarm when error occurs.

Reset or shutdown controller.

Quick steps to create a volume. Please refer to next chapter for operation in web UI.

Smart steps to create a volume. Please refer to next chapter for operation in web UI.

Display current IP address, subnet mask, and gateway.

Set IP address, subnet mask, and gateway. There are 2 options: DHCP (Get IP address from DHCP server) or static IP.

Reset to default will set password to default: admin, and

set IP address to default as DHCP setting.

Default IP address: 192.168.1.100 Default subnet mask: 255.255.255.0 Default gateway: 192.168.1.1

The following is LCM menu hierarchy.

[System Info.]

[Alarm Mute] [cYes Nod]

[Reset/Shutdown]

[Firmware

Version

x.x.x]

[RAM Size

xxx MB]

[Reset]

[Shutdown]

[cYes

Nod]

[cYes

Nod]

- 14 -

RAID 0 RAID 1 RAID 3

[Quick Install]

[Volume Wizard]

[View IP Setting]

[Change IP

Config]

[Reset to Default] [cYes Nod]

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.001.100]

[IP Subnet Mask]

[255.255.255.0]

[IP Gateway]

[192.168.001.001]

[DHCP]

[Static IP]

[Apply The

Config]

[Use default

algorithm]

[new x disk]

xxx BG

[cYes

Nod]

[IP Address]

[IP Subnet

Mask]

[IP

Gateway]

[Apply IP

Setting]

[cYes

Nod]

[Apply

[Volume

Size]

xxx GB

Adjust

Volume Size

Adjust IP

address

Adjust

Submask IP

Adjust

Gateway IP

[cYes

Nod]

The

Config]

[cYes

Nod]

[Apply

The

Config]

[cYes

Nod]

Caution Before power off, it is better to execute “Shutdown” to flush

the data from cache to physical disks.

- 15 -

2.4.2 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., when RAID 5 is degraded and alarm rings immediately, user changes/adds one physical disk for rebuilding. When the rebuilding is done, the alarm will be muted automatically.

2.4.3 LED

The LED features are listed below:

1. Marquee / Disk Status / Disk Rebuilding LED: The Marquee / Disk

Status / Disk Rebuilding LEDs are displayed in the same LEDs. The LEDs indicates different functions in different stages.

I. Marquee LEDs: When system powers on and successfully boots

up, the Marquee LED is on until the system boots successful.

II. Disk status LEDs: the LEDs reflect the disk status for the tray.

Only On/Off situation.

III. Disk rebuilding LEDs: the LEDs are blinking when the disks are

under rebuilding.

2. Disk Access LED: Hardware activated LED when accessing disks (IO).

3. Disk Power LED: Hardware activated LED when the disks are plugged

in and powered on.

4. System status LED: Used to reflect the system status by turning on

the LED when error occurs or RAID malfunction happens.

5. Management LAN port LED: GREEN LED is for LAN transmit/receive

indication. ORANGE LED is for LAN port 10/100 LINK indication.

6. BUSY LED: Hardware activated LED when the front-end channel is

busy.

7. POWER LED: Hardware activated LED when system is powered on.

- 16 -

Chapter 3 Web GUI guideline

3.1 Web GUI hierarchy

The below table is the hierarchy of web GUI.

Quick installation System configuration

System setting

IP address

Mail setting Notification

iSCSI configuration

Entity property

CHAP account

Session

Volume configuration

Volume create

Physical disk

RAID group

Virtual disk

Snapshot

Logical unit

Enclosure management

configuration

Hardware

monitor

S.M.A.R.T.

Maintenance

information

setting

NIC

Node

wizard

SES

UPS

System

Step 1 / Step 2 / Confirm

System name / Date and time

MAC address / Address / DNS / port

password Mail

SNMP / Messenger / System log server / Event log

filter

Entity name / iSNS IP

IP settings for iSCSI ports / Become default gateway /

Enable jumbo frame Create

Session information / Delete

Create / Delete

Step 1 / Step 2 / Step 3 / Step 4 / Confirm

Set Free disk / Set Global spare / Set Dedicated

spare / More information Create / Migrate / Activate / Deactivate / Scrub /

Delete / Set disk property / More information Create / Extend / Scrub / Delete / Set property /

ttach LUN / Detach LUN / List LUN / Set snapshot space / Cleanup snapshot / Take snapshot / Auto snapshot / List snapshot / More information Cleanup snapshot / Auto snapshot / Take snapshot /

Export / Rollback / Delete Attach / Detach

Enable / Disable

Auto shutdown

S.M.A.R.T. information

UPS Type / Shutdown battery level / Shutdown delay /

Shutdown UPS

System information

- 17 -

Browse the firmware to upgrade / Export configuration

Logout

Upgrade

Reset to default

Import and

export

Event log

Reboot and

shutdown

Sure to reset to factory default?

Import/Export / Import file

Download / Mute / Clear

Reboot / Shutdown

Sure to logout?

3.2 Login

i8500 supports graphic user interface (GUI) to operate the system. Be sure to

connect the LAN cable. The default IP address is 192.168.1.100; open the

browser and enter:

http://192.168.1.100 (Please check the IP address first on LCM.)

Click any function at the first time; it will pop up a dialog for authentication.

After login, you can choose the functions which lists on the left side of window to make configuration.

There are six indicators at the top-right corner for backplane solutions, and cabling solutions have three indicators at the top-right corner.

Figure 3.2.1

- 18 -

Figure 3.2.2

1. RAID light: Green means RAID works well. Red represents RAID

failure.

2. Temperature light: Green means normal temperature. Red

represents abnormal temperature.

3. Voltage light: Green means normal voltage. Red represents

abnormal voltage.

4. UPS light: Green means UPS works well. Red represents UPS

failure.

3.3 Volume creation wizard

It is easy to use “Volume creation wizard” to create a volume. It uses whole

physical disks to create a RG; the system will calculate maximum spaces on

RAID levels 0/1/3/5/6/0+1. “Volume creation wizard” 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 by manual, and refer to section 4.4 for more

detail. If some physical disks are used in other RGs, “Volume creation wizard”

can not be run because the operation is valid only when all physical disks in this system are free.

Step 1: Click “Volume creation wizard”, then choose the RAID level. After

choosing the RAID level, then click “ ”. It will link to another

page.

Figure 3.3.1

- 19 -

Step 2: Confirm page. Click “ ” if all setups are correct. Then

a VD will be created.

Done. You can start to use the system now.

Figure 3.3.2

(Figure 3.3.2: A RAID 0 Virtual disk with the VD name “QUICK53360”, named by system itself, with the total available volume size 1191GB.)

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 set system name and date. Default “System name”

composed of model name and serial number of this system.

Figure 3.4.1

- 20 -

Figure 3.4.1.1

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 change IP address for remote administration usage. There are

2 options, DHCP (Get IP address from DHCP server) or static IP. The default setting is Static IP(192.168.1.100). User can change the HTTP, and SSH port number when the default port number is not allowed on host/server.

Figure 3.4.2.1

- 21 -

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. When the login lock is enabled, the

system allows only one user to login or modify system settings.

Check “Change admin password” or “Change user password” to change

admin or user password. The maximum length of password is 12 characters.

3.4.4 Mail setting

“Mail setting” can enter at most 3 mail addresses 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. 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.

Figure 3.4.3.1

- 22 -

Figure 3.4.4.1

3.4.5 Notification setting

“Notification setting” can set up SNMP trap for alerting via SNMP, pop-up

message via Windows messenger (not MSN), alert via system log server protocol, and event log filter.

- 23 -

“SNMP” allows up to 3 SNMP trap addresses. Default community setting is

“public”. User can choose the event log levels and default setting only enables INFO event log in SNMP. There are many SNMP tools. The following web sites are for your reference:

SNMPc: http://www.snmpc.com/ Net-SNMP:

http://net-snmp.sourceforge.net/

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.

Figure 3.4.5.1

- 24 -

Using “System log server”, user can choose the facility and the event log level.

The default port of syslog is 514. The default setting enables event level: INFO, WARNING and ERROR event logs.

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 build in syslog daemon.

“Event log filter” setting can enable event level on “Pop up events” and “LCM”.

3.5 iSCSI configuration

“iSCSI configuration” is designed for setting up the “Entity Property”, “NIC”, “Node”, “Session”, and “CHAP account”.

Figure 3.5.1

3.5.1 Entity property

“Entity property” can view the entity name of the controller, and setup “iSNS IP” for iSNS (Internet Storage Name Service). iSNS protocol allows automated

discovery, management and configuration of Using iSNS, it needs to install a 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’t be changed.

Figure 3.5.1.1

- 25 -

iSCSI devices on a TCP/IP network.

3.5.2 NIC

“NIC” can change IP addresses of iSCSI data ports.

Figure 3.5.2.1

(Figure 3.5.2.1: there are 2 iSCSI data ports.)

IP settings:

User can change IP address by moving 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.

Figure 3.5.2.2

Default gateway:

Default gateway can be changed by moving mouse to the gray button of LAN

port, click “Become default gateway”. There is only one default gateway.

MTU / Jumbo frame: MTU (Maximum Transmission Unit) size can be enabled by moving mouse to the

gray button of LAN port, click “Enable jumbo frame”.

- 26 -

Caution

The MTU size of switching hub and HBA on host must be enabled. Otherwise, the LAN connection can not work properly.

3.5.3 Node

“Node” can view the target name for iSCSI initiator. The node name of i8500

exists by default and can not be changed.

Figure 3.5.3.1

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. CHAP enables the username and password to transmitting in an encrypted form for protection.

To use CHAP authentication, please follow the procedures.

1. Click “

”.

2. Select “CHAP”.

Figure 3.5.3.2

3. Click “

”.

Figure 3.5.3.3

- 27 -

4. Go to “/ iSCSI configuration / CHAP account” page to create CHAP

account. Please refer to next section for more detail.

5. In “Authenticate” page, select “None” to disable CHAP.

Tips

After setting CHAP, the initiator in host/server should be set the same CHAP account. Otherwise, user cannot login.

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.

Figure 3.5.4.1

(Figure 3.5.4.1: iSCSI Session.)

Mouse moves to the gray button of session number, click “List connection”. It

will list all connection(s) of the session.

Figure 3.5.4.2

(Figure 3.5.4.2: iSCSI Connection.)

3.5.5 CHAP account

“CHAP account” can manage a CHAP account for authentication.

To setup CHAP account, please follow the procedures.

1. Click “ ”.

- 28 -

2. Enter “User”, “Secret”, and “Confirm” secret again.

Figure 3.5.5.3

3. Click “ ”.

Figure 3.5.5.1

(Figure 3.5.5.4: create a CHAP account named “chap1”.)

4. Click “Delete” to delete CHAP account.

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”.

3.6.1 Volume create 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

Figure 3.6.1

- 29 -

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. After user chooses RAID level, user may find that some HDDs are available (free

status). The result is using smarter policy designed by Thecus. It gives user:

1. Biggest capacity of RAID level for user to choose and,

2. The fewest disk number for RAID level / volume size.

E.g., user chooses RAID 5 and the controller has 6*200G + 2*80G HDDs inserted. If we use all 16 HDDs for a RAID 5, and then the maximum size of volume is 560G (80G*7). By the wizard, we do smarter check and find out the most efficient way of using HDDs. The wizard only uses 200G HDDs (Volume size is 200G*5=1000G), the volume size is bigger and fully uses HDD capacity.

Step 1: Select “Volume create wizard” and then choose the RAID level. After

the RAID level is chosen, click “ ”. Then it will link to next

page.

Step 2: Please select the combination of the RG capacity, or “Use default algorithm” for maximum RG capacity. After RG size is chosen, click

“ ”.

Figure 3.6.1.1

- 30 -

Figure 3.6.1.2

Step 3: Decide VD size. User can enter a number less or equal to the default

number. Then click “ ”.

Figure 3.6.1.3

Step 4: Confirm page. Click “ ” if all setups are correct. Then

a VD will be created.

Done. You can start to use the system now.

Figure 3.6.1.4

(Figure 3.6.1.4: A RAID 0 Virtual disk with the VD name “QUICK13573”, named by system itself, with the total available volume size 1862GB.)

- 31 -

3.6.2 Physical disk

“Physical disk” can view the status of hard drives in the system. The followings

are operational tips:

1. Mouse moves to the gray button next to the number of slot, 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 11 to dedicated spare disk.

Step 1: Mouse moves to the gray button of PD 11, select “Set Dedicated spare”, it will link to next page.

Figure 3.6.2.1

Step 2: Maybe it has some RGs which can be set dedicate spare disk, select which one will be added, then click “ ”.

Figure 3.6.2.2

Done. View “Physical disk” page.

- 32 -

Figure 3.6.2.3

(Figure 3.6.2.3: Physical disks of slot 1,2,3 are created for a RG named “RG-R5”. Slot 4 is set as dedicated spare disk of RG named “RG-R5”. The others are free disks.)

• PD column description:

Slot

Size (GB)

RG Name

Status

Health

The position of hard drives. The button next to the number of slot shows the functions which can be executed.

Capacity of hard drive.

Related RAID group name.

The status of hard drive.

“Online” Æ the hard drive is online. “Rebuilding” Æ the hard drive is being rebuilt. “Transition” Æ the hard drive is being migrated or is

replaced by another disk when rebuilding occurs.

“Missing” Æ the hard drive has already joined a RG

but not plugged into the disk tray of current system.

The health of hard drive.

- 33 -

“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

Vendor

Serial

Type

“RD” Æ RAID Disk. This hard drive has been set to

RAID.

“FR” Æ FRee disk. This hard drive is free for use. “DS” Æ Dedicated Spare. This hard drive has been

set to the dedicated spare of the RG.

“GS” Æ Global Spare. This hard drive has been set to

a global spare of all RGs.

“RS” Æ ReServe. The hard drive contains the RG

information but cannot be used. It may be caused by an uncompleted 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.

Hard drive vendor.

Hard drive serial number.

Hard drive type.

Write cache

Standby

• PD operations description:

Set Free disk

Set Global spare

“SATA” Æ SATA disk. “SATA2” Æ SATA II disk.

Hard drive write cache is enabled or disabled.

HDD auto spindown to save power. The default value is disabled.

Make the selected hard drive to be free for use.

Set the selected hard drive to global spare of all RGs.

- 34 -

Set Dedicated spares

Set hard drive to dedicated spare of selected RGs.

Set property

Change the 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.

Show hard drive detail information.

information

3.6.3 RAID group

“RAID group” can view the status of each RAID group. The following is an

example to create a RG.

Step 1: Click “ ”, enter “Name”, choose “RAID level”, click

“ ” to select PD. Then click “ ”.

Figure 3.6.3.1

- 35 -

Step 2: Confirm page. Click “ ” if all setups are correct.

Figure 3.6.3.2

(Figure 3.6.3.2: There is a RAID 0 with 4 physical disks, named “RG-R0”, total size is 135GB. Another is a RAID 5 with 3 physical disks, named “RG-R5”.)

Done. View “RAID group” page.

• RG column description:

No.

Number of RAID group. The button next to the No. shows the functions which can be executed.

Name

Total(GB)

RAID group name.

Total capacity of this RAID group.

Free(GB)

#PD

#VD

Status

Free capacity of this RAID group.

The number of physical disks in RAID group.

The number of virtual disks in RAID group.

The status of RAID group.

“Online” Æ the RAID group is online. “Offline” Æ the RAID group is offline. “Rebuild” Æ the RAID group is being rebuilt.

- 36 -

“Migrate” Æ the RAID group is being migrated. “Scrub” Æ the RAID group is being scrubbed.

Health

The health of RAID group. “Good” Æ the RAID group is good. “Failed” Æ the hard drive is failed. “Degraded” Æ the RAID group is not completed. The

reason could be lack of one disk or disk failure.

RAID

Enclosure

• RG operations description:

Create

Migrate

The RAID level of the RAID group.

RG locates on local or JBOD enclosure.

Create a RAID group.

Migrate a RAID group. Please refer to next chapter for more detail.

Activate

Activate a RAID group; it can be executed when RG status is offline. This is for online roaming purpose.

Deactivate

Scrub

Delete

Set disk property

Deactivate a RAID group; it can be executed when RG status is online. This is for online roaming purpose.

Scrub a RAID group. It’s a parity regeneration. It supports RAID 3 / 5 / 6 / 30 / 50 / 60 only.

Delete a RAID group.

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.

Show RAID group detail information.

- 37 -

information

3.6.4 Virtual disk

“Virtual disk” can view the status of each Virtual disk. The following is an

example to create a VD.

Step 1: Click “

”, enter “Name”, choose “RG name”,

“Stripe height (KB)”, “Block size (B)”, “Read/Write” mode, “Priority”, “Bg rate” , change “Capacity (GB)” if necessary. Then click “ ”.

Step 2: Confirm page. Click “ ” if all setups are correct.

Figure 3.6.4.1

- 38 -

Figure 3.6.4.2

(Figure 3.6.4.2: Create a VD named “VD-01”, related to “RG-R0”, size is 30GB. The other VD is named “VD-02”, initializing to 12%.)

Done. View “Virtual disk” page.

• VD column description:

No.

Name

Size(GB)

Right

Priority

Number of this Virtual disk. The button next to the VD No. shows the functions which can be executed.

Virtual disk name.

Total capacity of the Virtual disk.

“WT” Æ Write Through. “WB” Æ Write Back. “RO” Æ Read Only.

“HI” Æ HIgh priority. “MD” Æ MiD priority. “LO” Æ LOw priority.

- 39 -

Bg rate

Background task priority.

“4 / 3 / 2 / 1 / 0” Æ Default value is 4. The higher

number the background priority of a VD has, the more background I/O will be scheduled to execute.

Status

Health

The status of Virtual disk. “Online” Æ the Virtual disk is online. “Offline” Æ the Virtual disk is offline. “Initiating” Æ the Virtual disk is being initialized. “Rebuild” Æ the Virtual disk is being rebuilt. “Migrate” Æ the Virtual disk is being migrated. “Rollback” Æ the Virtual disk is being rolled back. “Scrub” Æ the Virtual disk is being scrubbed.

The health of Virtual disk. “Optimal” Æ the Virtual disk is operating and has

experienced no failures of the disks that comprise

the RG.

“Degraded” Æ At least one disk which comprises

space of the Virtual disk has been marked as failed or has been plugged.

“Missing” Æ the Virtual disk has been marked as

missing by the system.

R %

RAID

#LUN

Snapshot (MB)

“Failed” Æ the Virtual disk has experienced enough

failures of the disks that comprise the VD for

unrecoverable data loss to occur.

“Part optimal” Æ the Virtual disk has experienced

disk failures.

Ratio of initializing or rebuilding.

The levels of RAID that Virtual disk is using.

Number of LUN(s) that Virtual disk is attaching.

The Virtual disk size that used for snapshot. The

number means “Used snapshot space” / “Total snapshot space”. The unit is in megabytes (MB).

- 40 -

#Snapshot

Number of snapshot(s) that Virtual disk is taken.

RG name

Readahead

• VD operations description:

Extend

Scrub

The Virtual disk is related to the RG name

This feature makes data be loaded to disk's buffer in advance for further use. Default is "Enabled".

Extend a Virtual disk capacity.

Scrub a Virtual disk. It’s a parity regeneration. It supports RAID 3 / 5 / 6 / 30 / 50 / 60 only.

Delete

Set property

Delete a Virtual disk.

Change the VD name, right, priority and bg rate.

Right options:

“WT” Æ Write Through. “WB” Æ Write Back. “RO” Æ Read Only.

Attach LUN

Detach LUN

List LUN

Set snapshot space

Priority options:

“HI” Æ HIgh priority. “MD” Æ MiD priority. “LO” Æ LOw priority.

Bg rate options:

“4 / 3 / 2 / 1 / 0” Æ Default value is 4. The higher

number the background priority of a VD has, the more background I/O will be scheduled to execute.

Attach to a LUN.

Detach to a LUN.

List attached LUN(s).

Set snapshot space for executing snapshot. Please refer to next chapter for more detail.

- 41 -

Cleanup snapshot

Clean all snapshot VD related to the Virtual disk and release snapshot space.

Take

Take a snapshot on the Virtual disk.

snapshot

Auto

Set auto snapshot on the Virtual disk.

snapshot

List snapshot

List all snapshot VD related to the Virtual disk.

Show Virtual disk detail information.

information

3.6.5 Snapshot

“Snapshot” can view the status of snapshot. Please refer to next chapter for

more detail about snapshot concept. The following is an example to take a snapshot.

Step 1: Create snapshot space. In “/ Volume configuration / Virtual disk”, Mouse moves to the gray button next to the VD number; click “Set snapshot

space”.

Step 2: Set snapshot space. Then click “ ”. The snapshot

space is created.

Figure 3.6.5.1

Figure 3.6.5.2

(Figure 3.6.5.2: “VD-01” snapshot space has been created, snapshot space is 15360MB, and used 263MB for saving snapshot index.)

- 42 -

Step 3: Take a snapshot. In “/ Volume configuration / Snapshot”, click

“ ”. It will link to next page. Enter a snapshot name.

Figure 3.6.5.3

Step 4: Export the snapshot VD. Mouse moves 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. Otherwise, the exported snapshot VD can be read/written, and the size will be the maximum capacity to read/write.

Figure 3.6.5.4

(Figure 3.6.5.5: This is the list of “VD-01”. There are two snapshots in “VD-01”. Snapshot VD “SnapVD-01” is exported to read only, “SnapVD-02” is exported to read/write.)

Step 5: Attach a LUN for snapshot VD. Please refer to the next section for

attaching a LUN.

Done. Snapshot VD can be used.

Figure 3.6.5.5

- 43 -

• 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

Used (MB)

Exported

Right

Snapshot VD name.

The amount of snapshot space that has been used.

Snapshot VD is exported or not.

“RW” Æ Read / Write. The snapshot VD can be read /

write.

“RO” Æ Read Only. The snapshot VD can be read

only.

#LUN

Created time

• Snapshot operations description:

Number of LUN(s) that snapshot VD is attaching.

Snapshot VD created time.

Export /

Export / unexport the snapshot VD.

Unexport

Rollback

Delete

Attach

Detach

List LUN

Rollback the snapshot VD to the original.

Delete the snapshot VD.

Attach to a LUN.

Detach to a LUN.

List attached LUN(s).

3.6.6 Logical unit

“Logical unit” can view the status of attached logical unit number of each VD.

- 44 -

User can attach LUN by clicking the “ ”. “Host” 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 “ ”.

Figure 3.6.6.1

• LUN operations description:

Attach

Detach

Attach a logical unit number to a Virtual disk.

Detach a logical unit number from a Virtual disk.

The matching rules of access control are inspected from top to bottom in sequence. For example: there are 2 rules for the same VD, one is “*”, LUN 0; and the other is “iqn.host1”, LUN 1. The other host “iqn.host2” can login successfully because it matches the rule 1.

The access will be denied when there is no matching rule.

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

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.

- 45 -

Step 1: Create RG (RAID group).

To create the RAID group, please follow the procedures:

Figure 3.6.7.1

1. Select “/ Volume configuration / RAID group”.

2. Click “ “.

3. Input a RG Name, choose a RAID level from the list, click

“ “ to choose the RAID PD slot(s), then click

“ “.

4. Check the outcome. Click “ “ if all setups are correct.

5. Done. A RG has been created.

Figure 3.6.7.2

(Figure 3.6.7.2: Creating a RAID 5 with 3 physical disks, named “RG-R5”. The total size is 931GB. Because there is no related VD, free size still remains 931GB.)

Step 2: Create VD (Virtual disk).

To create a data user volume, please follow the procedures.

- 46 -

Figure 3.6.7.3

5. Select “/ Volume configuration / Virtual disk”.

6. Click “ ”.

7. Input a VD name, choose a RG Name and enter a size of VD; decide the stripe high, block size, read/write mode and set priority, finally click

“ “.

8. Done. A VD has been created.

9. Do one more time to create another VD.

Figure 3.6.7.4

(Figure 3.6.7.4: Create VDs named “VD-R5-1” and “VD-R5-2”. Regarding to “RG-R5”, the size of “VD-R5-1” is 50GB, the size of “VD-R5-2” is 64GB. “VD-R5-1” is initialing about 86%. 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”, mouse moves to the gray

button next to the VD number; click “Attach LUN”.

2. In “/ Volume configuration / Logical unit”, click

“

”.

The procedures are as follows:

1. Select a VD.

- 47 -

2. Input “Host” name, which is a FC node name for access control, or fill- in wildcard “*”, which means every host can access to this volume.

Choose LUN and permission, then click “ ”.

3. Done.

Tips

The matching rules of access control are from top to bottom in sequence.

Step 4: Set global spare disk.

To set global spare disks, please follow the procedures.

1. Select “/ Volume configuration / Physical disk”.

2. Mouse moves to the gray button next to the PD slot; click “Set Global space”.

3. “GS” icon is shown in “Usage” column.

(Figure 3.5.8.7: Slot 4 is set as global spare disk.)

Step 5: Done. They can be used as disks.

Delete VDs, RG, please follow the steps listed below.

Step 6: Detach LUN from VD.

Figure 3.6.7.5

- 48 -

In “/ Volume configuration / Logical unit”,

1. Mouse moves 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. Select “/ Volume configuration / Virtual disk”.

2. Mouse moves 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.

Tips

When deleting VD, the attached LUN(s) related to this VD will be detached automatically.

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. Mouse moves to 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.

Tips

The action of deleting one RG will succeed only when all of the related VD(s) are deleted in this RG. Otherwise, it will have an error when deleting this RG.

Step 9: Free global spare disk.

To free global spare disks, please follow the procedures.

- 49 -

1. Select “/ Volume configuration / Physical disk”.

2. Mouse moves to the gray button next to the PD slot; click “Set Free

disk”.

Step 10: Done, all volumes have been deleted.

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. Below are the details of polling time intervals:

1. Temperature sensors: 1 minute.

2. Voltage sensors: 1 minute.

3. Hard disk sensors: 10 minutes.

4. Fan sensors: 10 seconds . When there are 3 errors consecutively, controller sends ERROR event log.

5. Power sensors: 10 seconds, when there are 3 errors consecutively, controller sends ERROR event log.

6. LED status: 10 seconds.

3.7.1 SES configuration

SES represents SCSI Enclosure Services, one of the enclosure management

standards. “SES configuration” can enable or disable the management of SES.

The SES client software is available at the following web site:

SANtools:

http://www.santools.com/

Figure 3.7.1

- 50 -

3.7.2 Hardware monitor

“Hardware monitor” can view the information of current voltage and

temperature.

Figure 3.7.2.1

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, controllers use multiple condition judgments for auto shutdown, below are the details of when the Auto shutdown will be triggered.

1. There are 3 sensors placed on controllers for temperature checking, one is on core processor, another two are on controller board. Controller will check each sensor for every 30 seconds. When one of these sensors is over high temperature value for continuous 3 minutes,

auto shutdown will be triggered immediately.

2. The core processor temperature limit is 85 ℃ . The PCI-X bridge temperature limit is 80℃. The daughter board temperature limit is 80℃.

- 51 -

3. If the high temperature situation doesn’t last for 3 minutes, controller will not do auto shutdown.

3.7.3 Hard drive S.M.A.R.T. support

S.M.A.R.T. (Self-Monitoring Analysis and Reporting Technology) is a diagnostic

tool for hard drives to deliver warning of drive failures in advance. S.M.A.R.T. provides users chances to take actions before possible drive failure.

S.M.A.R.T. measures many attributes of the hard drive all the time and inspects the properties of hard drives which are close to be out of tolerance. The advanced notice of possible hard drive failure can allow users to back up hard drive or replace the hard drive. This is much better than hard drive crash when it is writing data or rebuilding a failed hard drive.

“S.M.A.R.T.” can display S.M.A.R.T. information of hard drives. The number is

the current value; the number in parenthesis is the threshold value. The threshold values of hard drive vendors are different; please refer to vendors’ specification for details.

Figure 3.7.3.1

- 52 -

3.7.4 UPS

“UPS” can set up UPS (Uninterruptible Power Supply).

Figure 3.7.4.1

Currently, the system only supports and communicates with smart-UPS of APC (American Power Conversion Corp.) 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.

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.

Shutdown UPS

Status

Select ON, when power is gone, UPS will shutdown by itself after the system shutdown successfully. After power comes back, UPS will start working and notify system to boot up. OFF will not.

The status of UPS.

“Detecting…” “Running” “Unable to detect UPS” “Communication lost” “UPS reboot in progress”

- 53 -

“UPS shutdown in progress” “Batteries failed. Please change them NOW!”

Battery Level (%)

Current percentage of battery level.

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.

Figure 3.8.1

3.8.1 System information

“System information” can display system information (including firmware

version), CPU type, installed system memory, and controller serial number.

3.8.2 Upgrade

“Upgrade” can upgrade firmware. Please prepare new firmware file named “xxxx.bin” in local hard drive, then click “

“ 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.

”, it will pop up a message “Upgrade system now? If you

” to select the file. Click

- 54 -

Figure 3.8.2.1

Figure 3.8.2.2

When upgrading, there is a progress bar running. After finished upgrading, the system must reboot manually to make the new firmware took effect.

Tips Please contact with www.thecus.com for latest firmware.

3.8.3 Reset to factory default

“Reset to factory default” allows user to reset controller to factory default

setting.

Figure 3.8.3.1

Reset to default value, the password is: admin, and IP address to default Static

IP.

Default IP address: 192.168.1.100 Default subnet mask: 255.255.255.0 Default gateway: 192.168.1.1

- 55 -

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. If the volume setting was also imported, user’s current data will be overwritten.

Figure 3.8.4.1

1. Import: Import all system configurations excluding volume

configuration.

2. Export: Export all configurations to a file.

Caution “Import” will import all system configurations excluding

volume configuration; the current configurations will be replaced.

3.8.5 Event log

“Event log” can view the event messages. Check the checkbox of INFO,

WARNING, and ERROR to choose the level of display event log. Clicking

“ name “log-ModelName-SerialNumber-Date-Time.txt”.

” button will save the whole event log as a text file with file

Click ”

“ ” button will stop alarm if system alerts.

” button will clear event log. Click

- 56 -

Figure 3.8.5.1

The event log is displayed in reverse order which means the latest event log is on the first page. The event logs are actually saved in the first four hard drives; each hard drive has one copy of event log. For one controller, there are four copies of event logs to make sure users can check event log any time when there is/are failed disk(s).

Tips

Please plug-in any of the first four hard drives, then event logs can be saved and displayed in next system boot up. Otherwise, the event logs would be disappeared.

3.8.6 Reboot and shutdown

“Reboot and shutdown” displays “Reboot” and “Shutdown” buttons. Before

power off, it’s better to execute “Shutdown” to flush the data from cache to

physical disks. The step is necessary for data protection.

3.9 Logout

For security reason, “Logout” allows users logout when no user is operating the

system. Re-login the system; please enter username and password again.

Figure 3.8.6.1

- 57 -

Chapter 4 Advanced operation

4.1 Rebuild

If one physical disk of the RG which is set as protected RAID level (e.g.: RAID 3, RAID 5, or RAID 6) is FAILED or has been unplugged/removed, then the status of RG is changed to degraded mode, the system will search/detect spare disk to

rebuild the degraded RG to a complete one. It will detect dedicated spare disk as

rebuild disk first, then global spare disk.

i8500 support Auto-Rebuild. The following is the scenario:

Take RAID 6 for example:

1. When there is no global spare disk or dedicated spare disk in the system, controller will be in degraded mode and wait until (A) there is one disk assigned as spare disk, or (B) the failed disk is removed and replaced with new clean disk, then the Auto-Rebuild starts. The new disk will be a spare disk to the original RG automatically.

If the new added disk is not clean (with other RG information), it would be marked as RS (reserved) and the system will not start "auto-rebuild".

If this disk is not belonging to any existing RG, it would be FR (Free) disk and the system will start Auto-Rebuild.

If user only removes the failed disk and plugs the same failed disk in the same slot again, the auto-rebuild will start running. But rebuilding in the same failed disk may impact customer data if the status of disk is

unstable. Thecus suggests all customers not to rebuild in the failed

disk for better data protection.

2. When there is enough global spare disk(s) or dedicated spare disk(s) for the degraded array, controller starts Auto-Rebuild immediately. And in RAID 6, if there is another disk failure occurs during rebuilding, controller will start the above Auto-Rebuild process as well. Auto-

Rebuild feature only works at that the status of RG is "Online". It will not work at “Offline”. Thus, it will not conflict with the “Roaming”.

3. In degraded mode, the status of RG is “Degraded”. When rebuilding, the status of RG/VD will be “Rebuild”, the column “R%” in VD will

display the ratio in percentage. After complete rebuilding, the status will become “Online”. RG will become completely one.

- 58 -

Tips “Set dedicated spare” is not available if there is no RG or

only RG of RAID 0, 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

RAID 1

N-way mirror

RAID 3

RAID 5

RAID 6

Disk striping. No protection for data. RG fails if any hard drive fails or unplugs.

Disk mirroring over 2 disks. RAID 1 allows one hard drive fails or unplugging. Need one new hard drive to insert to the system and rebuild to be completed.

Extension to RAID 1 level. It has N copies of the disk. N-way mirror allows N-1 hard drives failure or unplugging.

Striping with parity on the dedicated disk. RAID 3 allows one hard drive failure or unplugging.

Striping with interspersed parity over the member disks. RAID 5 allows one hard drive failure or unplugging.

2-dimensional parity protection over the member disks. RAID 6 allows two hard drives failure or unplugging. If it needs to rebuild two hard drives at the same time, it will rebuild the first one, then the other in sequence.

RAID 0+1

Mirroring of RAID 0 volumes. RAID 0+1 allows two hard drive failures or unplugging, but at the same array.

RAID 10

Striping over the member of RAID 1 volumes. RAID 10 allows two hard drive failure or unplugging, but in different arrays.

RAID 30

Striping over the member of RAID 3 volumes. RAID 30 allows two hard drive failure or unplugging, but in different arrays.

RAID 50

Striping over the member of RAID 5 volumes. RAID 50 allows two hard drive failures or unplugging, but in different arrays.

RAID 60

Striping over the member of RAID 6 volumes. RAID 40 allows four hard drive failures or unplugging, every two in different

- 59 -

arrays.

JBOD

The abbreviation of “Just a Bunch Of Disks”. No data

protection. RG fails if any hard drive failures or unplugs.

4.2 RG migration

To migrate the RAID level, please follow below procedures.

1. Select “/ Volume configuration / RAID group”.

2. Mouse moves 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 RAID level, click “ ” to increase hard

drives, then click “ “ to go back to setup page. When doing migration to lower RAID level, such as the original RAID level is RAID 6 and user wants to migrate to RAID 0, system will evaluate whether this operation is safe or not, and appear a message

of "Sure to migrate to a lower protection array?” to give user

warning.

4. Double check the setting of RAID level and RAID PD slot. If there is no problem, click “

5. Finally a confirmation page shows the detail of RAID information. If

there is no problem, click “

System also pops up a message of “Warning: power lost during migration may cause damage of data!” to give user warning. When

the power is abnormally off during the migration, the data is in high risk.

6. Migration starts and it can be seen from the “status” of a RG with

“Migrating”. In “/ Volume configuration / Virtual disk”, it displays a “Migrating” in “Status” and complete percentage of migration in “R%”.

Figure 4.2.1

“.

“ to start migration.

- 60 -

Figure 4.2.2

(Figure 4.2.2: A RAID 0 with 4 physical disks migrates to RAID 5 with 5 physical disks.)

Figure 4.2.3

(Figure 4.2.3: A RAID 0 migrates to RAID 5, the complete percentage is 14%.)

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. Take a new snapshot.

10. Delete an existing snapshot.

11. Export a snapshot.

12. Rollback to a snapshot.

Caution

RG Migration cannot be executed during rebuild or VD extension.

- 61 -

4.3 VD Extension

To extend VD size, please follow the procedures.

1. Select “/ Volume configuration / Virtual disk”.

2. Mouse moves 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.

Figure 4.3.1

4. Extension starts. If VD needs initialization, it will display an “Initiating” in “Status” and complete percentage of initialization in “R%”.

Figure 4.3.2

(Figure 4.3.2: Extend VD-R5 from 20GB to 40GB.)

Tips

The size of VD extension must be larger than original.

Caution

VD Extension cannot be executed during rebuild or migration.

4.4 Snapshot / Rollback

Snapshot 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

- 62 -

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. Rollback restores the data back to the state of any time which was previously captured in case for any unfortunate reason it might be (e.g. virus attack, data corruption, human errors and so on). Snap VD is allocated within the same RG in which the snapshot is taken, we suggest to reserve 20% of RG size or more for snapshot space.

Caution Snapshot / rollback features need 512MB RAM at least. Please

also refer to RAM certification list in Appendix A.

4.4.1 Create snapshot volume

To take a snapshot of the data, please follow the procedures.

1. Select “/ Volume configuration / Virtual disk”.

2. Mouse moves 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. It may not be the same as the number entered because some size is reserved for

snapshot internal usage. There will be 2 numbers in “Snapshot (MB)” column. These numbers mean “Used snapshot space” and “Total snapshot space”.

4. There are two methods to take snapshot. In “/ Volume configuration / Virtual disk”, mouse moves to the gray button next to the VD number; click “Take snapshot”. Or in “/ Volume configuration / Snapshot”,

click “

”.

5. Enter a snapshot name, then click “ ”. A snapshot VD is created.

6. Select “/ Volume configuration / Snapshot” to display all snapshot

VDs related to the VD.

- 63 -

Figure 4.4.1.1

(Figure 4.4.1.1: This is Snap VD, but it is not exported.)

7. Mouse moves 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. Otherwise, the exported snapshot VD can be read/written, and the size will be the maximum capacity to read/write.

8. Attach a LUN for snapshot VD. Please refer to the previous chapter for attaching a LUN.

9. Done. It can be used as a disk.

(Figure 4.4.1.2: This is the list of “VD-01”. There are two snapshots in “VD-01”. Snapshot VD “SnapVD-01” is exported to read only, “SnapVD-02” is exported to read/write.)

10. There are two methods to clean all snapshots. In “/ Volume configuration / Virtual disk”, mouse moves 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 as followings:

1. Minimum RAM size of enabling snapshot is 512MB.

Figure 4.4.1.2

”.

- 64 -

2. For performance and future rollback, system saves snapshot with names in sequences. For example, three snapshots has been taken and named “SnapVD-01”(first), “SnapVD-02” and “SnapVD-03”(last). When deleting “SnapVD-02”, both of “SnapVD-02” and “SnapVD-03” will be deleted because “SnapVD-03” is related to “SnapVD-02”.

3. For resource management, maximum number of snapshots in VD is 32.

4. If the snapshot space is full, system will send a warning message of space full and the new taken snapshot will replace the oldest snapshot in rotational sequence by executing auto snapshot, but new snapshot can not be taken by manual because system does not know which snapshot VDs can be deleted.

z No. of Snapshot: There are three constraints related to snapshot volume.

1. Up to 16 VD could be taken snapshot volume.

2. Each VD supports up to 32 snapshot volumes.

3. i8500 supports up to 256 logical volumes.

i8500 allows 256 VD/snapshot volume. It depends when the logical volumes (VD number + snapshot config + snapshot number) reaches the max number of the controller. In i8500, it is 256. We leave the flexibility to users, so users can have their own RG/VD/Snapshot plan.

Let take 2 examples to describe it.

Example 1.

We assume user wants to create 32 snapshots for each VD. By all the constraints, i8500 could support 7 VD to take 32 snapshots. The formula listed as below: 256/(1+1+32) (VD itself+ Snapshot config+ 32 Snapshots)=7.52

Example 2.

We assume user want to have 16 VD with snapshot. By all the constraints, i8500 could support each VD to take 14 snapshots. The formula listed as below: 256/16=16 (Each VD could consumes 16 logical volumes, one is for VD itself and one is for Snapshot config. There remains 14 logical volumes for snapshot).

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”, mouse moves 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.

”.

- 65 -

3. Done. It will take snapshots automatically.

Figure 4.4.2.1

(Figure 4.4.2.1: It will take snapshots every month, and keep the last 32 snapshot copies.)

Tips

Daily snapshot will be taken at every 00:00. Weekly snapshot will be taken every Sunday 00:00. Monthly snapshot will be taken every first day of month 00:00.

4.4.3 Rollback

The data in snapshot VD can rollback to original VD. Please follow the procedures.

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 followings:

1. Minimum RAM size of enabling rollback is 512MB.

- 66 -

2. When making rollback, the original VD cannot be accessed for a while. At the same time, the system connects to original VD and snaps VD, and then starts rollback.

3. During rollback, data from snap VD to original VD, the original VD can be accessed and the data in VD just like it has finished rollback. At the same time, the other related snap VD(s) can not be accessed.

4. After rollback, the other snapshot VD(s) after the VD which is doing rollback will be deleted.

Caution

Before executing rollback, it is better to dismount file system for flushing data from cache to disks in OS first. System sends

pop-up message when user executes rollback function.

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 the procedures.

1. Select “/ Volume configuration / RAID group”.

2. Mouse moves to the gray button next to the RG number; click

“Deactivate”.

3. Move all PDs related to the RG to another system.

4. Mouse moves to the gray button next to the RG number; click

“Activate”.

5. Done.

Disk roaming has some constraints as described in the followings:

1. Check the firmware of two systems first. It is better that both systems have the same firmware version or newer.

2. All physical disks of related RG should be moved from system-1 to system-2 together. The configuration of both RG and VD will be kept but LUN configuration will be cleared in order to avoid conflict with system-2.

4.6 Support Microsoft MPIO and MC/S

MPIO (Multi-Path Input/Output) and MC/S (Multiple Connections per Session)

- 67 -

use multiple physical paths to create logical "paths" between the server and the storage device. In the case which one or more of these components fails, causing the path to fail, multi-path logic uses an alternate path for I/O. So applications can still access their data.

Microsoft iSCSI initiator supports multi-path. Please follow the procedures to use MPIO feature.

1. A host with dual LAN ports connects cables to controller.

2. Create a RG/VD and attach this VD to the host.

3. When installing “Microsoft iSCSI initiator”, please install MPIO driver

at the same time.

4. Logon to target separately on each port. When logon to target, check

“Enable multi-path”.

5. MPIO mode can be selected on Targets Æ Details Æ Devices Æ Advanced in Microsoft iSCSI initiator.

6. Rescan disk.

7. There will be one disk running MPIO.

- 68 -

Appendix

A. Certification list

• RAM

i8500 RAM Spec: 184pins, DDR333(PC2700), Reg.(register) or

UB(Unbufferred), ECC or Non-ECC, from 64MB to 1GB, 32-bit or 64-bit data bus width, x8 or x16 devices, 9 to 11 bits column address.

Vendor Model

ATP AG64L72T8SQC4S, 512MB DDR-400 (ECC) with Samsung ATP AG28L64T8SHC4S, 1GB DDR-400 with Samsung ATP AG28L72T8SHC4S, 1GB DDR-400 (ECC) with Samsung ATP AB28L72Q8SHC4S, 1GB DDR-400 (ECC, Reg.) with Samsung Unigen UG732D6688KN-DH, 256MB DDR-333 (Unbufferred) with Hynix Unigen UG732D7588KZ-DH, 256MB DDR-333 (ECC, Reg.) with Elpida Unigen UG764D7588KZ-DH, 512MB DDR-333 (ECC, Reg.) with Elpida Unigen UG7128D7588LZ-DH, 1GB DDR-333 (ECC, Reg.) with Hynix Unigen UG7128D7488LN-GJF, 1GB DDR-400 (ECC) with Hynix Unigen UG7128D7588LZ-GJF, 1GB DDR-400 (ECC, Reg.) with Hynix Unigen UG7128D7588LZ-GJF, 1GB DDR-400 (ECC, Reg.) with Elpida Unigen UG732D6688KS-DH, 256MB DDR-333 (Unbufferred, Low profile)

with Hynix

Unigen UG764D6688LS-DH, 512MB DDR-333 (Unbufferred, Low profile)

with Hynix Unigen UG718D6688LN-GJF, 1GB DDR-400 with Hynix Unigen UG718D6688LN-GJF, 1GB DDR-400 with Elpida

• iSCSI Initiator (Software)

OS Software/Release Number

Microsoft Windows

Linux

Microsoft iSCSI Software Initiator Release v2.07

System Requirements:

1. Windows 2000 Server with SP4

2. Windows Server 2003 with SP2

3. Windows Server 2003 R2 with SP2

4. Windows Server 2008

The iSCSI Initiators are different for different Linux Kernels.

1. For Red Hat Enterprise Linux 3 (Kernel 2.4), install linux-iscsi-

3.6.3.tar

2. For Red Hat Enterprise Linux 4 (Kernel 2.6), use the build-in

- 69 -

iSCSI initiator iscsi-initiator-utils-4.0.3.0-4 in kernel 2.6.9

3. For Red Hat Enterprise Linux 5 (Kernel 2.6), use the build-in iSCSI initiator iscsi-initiator-utils-6.2.0.742-0.5.el5 in kernel

2.6.18

Mac

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 HBA card

Vendor Model

HP NC380T (PCI-Express, Gigabit, 2 ports, TCP/IP offload, iSCSI

offload) QLogic QLA4010C (PCI-X, Gigabit, 1 port, TCP/IP offload, iSCSI offload) QLogic QLA4052C (PCI-X, Gigabit, 2 ports, TCP/IP offload, iSCSI offload)

• NIC

Vendor Model

HP NC7170 (PCI-X, Gigabit, 2 ports) HP NC360T (PCI-Express, Gigabit, 2 ports, TCP/IP offload) IBM NetXtreme 1000 T (73P4201) (PCI-X, Gigabit, 2 ports, TCP/IP

offload) Intel PWLA8492MT (PCI-X, Gigabit, 2 ports, TCP/IP offload)

• GbE Switch

Vendor Model

Dell PowerConnect 5324 Dell PowerConnect 2724 Dell PowerConnect 2708 HP ProCurve 1800-24G

• Hard drive

i8500 support SATA I, II disks.

Vendor Model

Hitachi Deskstar 7K250, HDS722580VLSA80, 80GB, 7200RPM, SATA, 8M Hitachi Deskstar E7K500, HDS725050KLA360, 500GB, 7200RPM, SATA II,

16M

- 70 -

Hitachi Deskstar 7K80, HDS728040PLA320, 40GB, 7200RPM, SATA II, 2M Hitachi Deskstar T7K500, HDT725032VLA360, 320GB, 7200RPM, SATA II,

16M Hitachi Deskstar P7K500, HDP725050GLA360, 500GB, 7200RPM, SATA II,

16M Maxtor DiamondMax Plus 9, 6Y080M0, 80GB, 7200RPM, SATA, 8M Maxtor DiamondMax 11, 6H500F0, 500GB, 7200RPM, SATA 3.0Gb/s, 16M Samsung

Seagate Barracuda 7200.7, ST380013AS, 80GB, 7200RPM, SATA 1.5Gb/s, 8M Seagate Barracuda 7200.7, ST380817AS, 80GB, 7200RPM, SATA 1.5Gb/s, 8M,

Seagate Barracuda 7200.8, ST3400832AS, 400GB, 7200RPM, SATA 1.5Gb/s,

Seagate Barracuda 7200.9, ST3500641AS, 500GB, 7200RPM, SATA 3.0Gb/s,

Seagate Barracuda 7200.11, ST31000340AS, 1000GB, 7200RPM, SATA

Seagate NL35, ST3400633NS, 400GB, 7200RPM, SATA 3.0Gb/s, 16M Seagate NL35, ST3500641NS, 500GB, 7200RPM, SATA 3.0Gb/s, 16M Seagate Barracuda ES, ST3500630NS, 500GB, 7200RPM, SATA 3.0Gb/s, 16M Seagate Barracuda ES, ST3750640NS, 750GB, 7200RPM, SATA 3.0Gb/s, 16M Seagate Barracuda ES.2, ST31000340NS, 1000GB, 7200RPM, SATA 3.0Gb/s,

Westem Digital Caviar SE, WD800JD, 80GB, 7200RPM, SATA 3.0Gb/s, 8M Westem Digital Caviar SE, WD1600JD, 160GB, 7200RPM, SATA 1.5G/s , 8M Westem Digital Raptor, WD360GD, 36.7GB, 10000RPM, SATA 1.5Gb/s, 8M Westem Digital Caviar RE2, WD4000YR, 400GB, 7200RPM, SATA 1.5Gb/s, 16M, NCQ Westem Digital RE2, WD4000YS, 400GB, 7200RPM, SATA 3.0Gb/s, 16M Westem Digital Caviar RE16, WD5000AAKS, 500GB, 7200RPM, SATA 3.0Gb/s, 16M Westem Digital RE2, WD5000ABYS, 500GB, 7200RPM, SATA 3.0Gb/s, 16M, NCQ

SpinPoint P80, HDSASP0812C, 80GB，7200RPM, SATA, 8M

NCQ

8M, NCQ

16M, NCQ

3.0Gb/s, 32M, NCQ

32M

Event notifications

• PD events

Level Type Description

INFO WARNING ERROR

• HW events

Level Type Description

WARNING ERROR INFO INFO

Disk inserted Disk <slot> is inserted into system. Disk removed Disk <slot> is removed from system. HDD failure Disk <slot> is disabled.

ECC error Single-bit ECC error is detected. ECC error Multi-bit ECC error is detected. ECC info ECC memory is installed. ECC info Non-ECC memory is installed.

- 71 -

INFO

• EMS events

Level Type Description

INFO ERROR INFO ERROR WARNING INFO ERROR INFO ERROR WARNING

ERROR ERROR

WARNING WARNING ERROR

ERROR INFO

WARNING ERROR ERROR

WARNING WARNING

SCSI info Received SCSI Bus Reset event at the SCSI

Bus <number>.

Power installed Power <number> is installed. Power absent Power <number> is absent. Power work Power <number> is restored to work. Power warning Power <number> is out of work. Power detect PSU signal detection <number>. Fan work Fan <number> is restored to work. Fan warning Fan <number> is out of work. Fan installed Fan <number> is installed. Fan not present Fan <number> is not present. Thermal warning System temperature <location> is a little bit

higher. Thermal critical System Overheated <location>!!! Thermal critical shutdown Thermal ignore

System Overheated <location>!!! The system

will do the auto shutdown immediately.

Unable to update thermal value on <location>. value Voltage warning System voltage <location> is a little bit

higher/lower. Voltage critical System voltages <location> failed!!! Voltage critical shutdown

System voltages <location> failed!!! The system

will do the auto shutdown immediately. UPS info UPS detection succeeded. UPS error UPS detection failed. UPS error AC loss for the system is detected. UPS error UPS Power Low!!! The system will do the auto

shutdown immediately. SMART T.E.C. Disk <slot> S.M.A.R.T. Threshold Exceed

Condition occurred for attribute <item>. SMART failure Disk <slot>: Failure to get S.M.A.R.T

information.

• RMS events

Level Type Description

INFO INFO INFO

INFO

Console Login <username> login from <IP or serial console>

Console Logout <username> logout from <IP or serial console>

Web Login <username> login from <IP> via Web UI. Web Logout <username> logout from <IP> via Web UI.

• LVM3 events

Level Type Description

via Console UI.

- 72 -

INFO INFO INFO INFO INFO INFO INFO

INFO INFO INFO INFO

INFO INFO WARNING INFO

INFO WARNING INFO

INFO ERROR

INFO INFO INFO INFO INFO

INFO INFO INFO WARNING WARNING WARNING ERROR ERROR WARNING

WARNING ERROR ERROR

RG created RG <name> has been created. RG creation failed Failed to create RG <name>. RG deleted RG <name> has been deleted. VD created VD <name> has been created. VD creation failed Failed to create VD <name>. VD deleted VD <name> has been deleted. VD renamed Name of VD <name> has been renamed to

<name>. Read-only caching enabled Writeback caching enabled Write-through caching enabled

Cache policy of VD <name> has been set as

read only.

Cache policy of VD <name> has been set as

write-back.

Cache policy of VD <name> has been set as

write-through. VD extended Size of VD <name> extends. VD initialization

VD <name> starts initialization. started VD initialization

VD <name> completes the initialization. finished VD initialization

Failed to complete initialization of VD <name>. failed VD rebuild started VD <name> starts rebuilding. VD rebuild finished VD <name> completes rebuilding. VD rebuild failed Failed to complete rebuild of VD <name>. VD migration

VD <name> starts migration. started VD migration

VD <name> completes migration. finished VD migration failed Failed to complete migration of VD <name>. VD scrubbing

VD <name> starts scrubbing. started VD scrubbing

VD <name> completes scrubbing. finished RG migration

RG <name> starts migration. started RG migration

RG <name> completes migration. finished RG activated RG <name> has been manually activated. RG deactivated RG <name> has been manually deactivated. VD rewrite started Rewrite at LBA <address> of VD %s starts. VD rewrite finished Rewrite at LBA <address> of VD %s completes. VD rewrite failed Rewrite at LBA <address> of VD %s failed. RG degraded RG <name> is under degraded mode. VD degraded VD <name> is under degraded mode. RG failed RG <name> is failed. VD failed VD <name> is failed. Recoverable read error occurred Recoverable write error occurred Unrecoverable read error occurred

Recoverable read error occurred at LBA

<address>-<address> of VD <name>.

Recoverable write error occurred at LBA

<address>-<address> of VD <name>.

Unrecoverable read error occurred at LBA

<address>-<address> of VD <name>. Unrecoverable Unrecoverable write error occurred at LBA

- 73 -

write error occurred <address>-<address> of VD <name>.

INFO

Dedicated spare configured

INFO

Global spare configured

WARNING

PD read error occurred

WARNING

PD write error occurred

WARNING

Parity wrong when scrubbing

WARNING

Data recovered when scrubbing

INFO INFO INFO INFO

PD freed PD <slot> has been removed from RG <name>. RG imported Configuration of RG<name> has been imported. RG restored Configuration of RG <name> has been restored. VD restored Configuration of VD <name> has been restored.

• Snapshot events

Level Type Description

INFO INFO

Snapshot deleted The snapshot VD <name> has been deleted. Snapshot auto deleted

INFO INFO

Snapshot taken A snapshot on VD <name> has been taken. Snapshot space configured

INFO

Snapshot rollback started

INFO

Snapshot rollback finished

WARNING

Snapshot quota reached

PD <slot> has been configured to RG <name>

as a dedicated spare disk.

PD <slot> has been configured as a global

spare disk.

Read error occurred at LBA <address>-

<address> of PD <slot>.

Write error occurred at LBA <address>-

<address> of PD <slot>.

The parity data is wrong at LBA <address>-

<address> when scrubbing VD <name>.

Data at LBA <address>-<address> has been

recovered when scrubbing VD <name>.

The oldest snapshot VD <name> has been

deleted to obtain extra snapshot space.

Set the snapshot space of VD <name> to

<number> MB.

Snapshot rollback of VD <name> has been

started.

Snapshot rollback of VD <name> has been

finished.

The quota assigned to snapshot <name> is

reached.

• iSCSI events

Level Type Description

INFO

iSCSI login succeeds

INFO INFO

iSCSI login rejected iSCSI login from <IP> was rejected, reason

iSCSI logout iSCSI logout from <IP> was received, reason

• Battery backup events

Level Type Description

INFO INFO

BBM sync data Abnormal shutdown detected, start flushing

BBM sync data Abnormal shutdown detected, flushing battery-

iSCSI login from <IP> succeeds.

[<string>]

[<string>].

battery-backuped data (<number> KB).

- 74 -

INFO INFO INFO WARNING INFO

• JBOD events

Level Type Description

INFO Warning ERROR

INFO WARNING WARNING

WARNING INFO

INFO WARNING WARNING INFO

BBM detected Battery backup module is detected. BBM is good Battery backup module is good. BBM is charging Battery backup module is charging. BBM is failed Battery backup module is failed. BBM Battery backup feature is <item>.

Disk inserted JBOD <number> disk <slot> is inserted into

Disk removed JBOD <number> disk <slot> is removed from

HDD failure JBOD <number> disk <slot> is disabled. JBOD inserted JBOD <number> is inserted into system JBOD removed JBOD <number> is removed from system SMART T.E.C JBOD <number> disk <slot>: S.M.A.R.T.

SMART Failure JBOD <number> disk <slot>: Failure to get

Dedicated spare configured

Global spare configured PD read error occurred PD write error occurred PD freed JBOD <number> PD <slot> has been removed

backuped data finishes.

system.

Threshold Exceed Condition occurred for

attribute %s

S.M.A.R.T information

JBOD <number> PD <slot> has been

configured to RG <name> as a dedicated spare

disk.

JBOD <number> PD <slot>d has been

configured as a global spare disk.

Read error occurred at LBA <address>-

<address> of JBOD <number> PD <slot>.

Write error occurred at LBA <address>-

<address> of JBOD <number> PD <slot>.

from RG <name>.

• System maintenance events

Level Type Description

INFO INFO INFO INFO

WARNING

System shutdown System shutdown. System reboot System reboot. FW upgrade start Firmware upgrade start. FW upgrade success FW upgrade failure Firmware upgrade failure.

Firmware upgrade success.

- 75 -

C. Known issues

1. Microsoft MPIO driver is not supported on Windows XP and Windows 2000 Professional.

Workaround solution: Using Windows Server 2008/2003, Windows

2000 server to run MPIO.

Workaround solution: It’s a JBOD limitation.

- 76 -

D. Microsoft iSCSI Initiator

Here is the step by step to setup Microsoft iSCSI Initiator. Please visit Microsoft website for latest iSCSI initiator. The following setup may not use the latest Microsoft iSCSI initiator.

1. Run Microsoft iSCSI Initiator.

2. Click “Discovery”.

3. Click “Add”. Input IP address or DNS name of iSCSI storage device.

4. Click “OK”.

5. Click “Targets”.

Figure D.2

6. Click “Log On”. Check “Enable multi-path” if running MPIO.

Figure D.3

- 77 -

Figure D.4

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 log off successfully.

Figure D.5

- 78 -

E. Installation steps for large volume (TB)

Introduction:

i8500 capable of supporting large volumes (>2TB). When connecting controllers to 64bit OS installed host/server, the host/server is inherently capable for large volumes from the 64bit address. On the other side, if the host/server is installed with 32bit OS, user has to change the block size to 1KB, 2KB or 4KB to support volumes up to 4TB, 8TB or 16TB, for the 32bit host/server is not LBA (Logical Block Addressing) 64bit supported. For detail installation steps, please refer to following steps below.

Step 1: Configure target

1. Prepare the hard drivers which capacity is over 2TB totally. Follow the example in chapter 3 to create a RG/VD. Then attach LUN.

Tips

If the OS is 64bit, user can set the block size to any available value. If the OS is 32bit, user must change the block size to larger values than 512B. There will be a confirmation pop-up message when VD size is over 2TB.

(Figure G.1: choose “OK” for 64bit OS, choose “Cancel” for 32bit OS, this step will change block size to 4K automatically.)

2. Mouse moves to the gray button next to the VD number; click “More information”. Look at block size is 512B for 64bit OS setting, 4K for

32bit OS setting.

Step 2: Configure host/server

Figure E.1:

- 79 -

1. Follow the installation guild provided by HBA vendor, install HBA driver properly. For iSCSI models, please install the latest Microsoft iSCSI initiator from the link below.

http://www.microsoft.com/downloads/details.aspx?FamilyID=12cb3c1a15d6-4585-b385-befd1319f825&DisplayLang=en

Step 3: Initialize/Format/Mount the disk

1. Go to Start Æ Control Panel Æ Computer Management Æ Disk Management, it displays a new disk.

Figure E.2

2. Initialize the disk.

Figure E.3

3. Convert to GPT disk for over 2TB capacity. For more detail information about GPT, please visit

- 80 -

http://www.microsoft.com/whdc/device/storage/GPT_FAQ.mspx

4. Format the disk.

5. Done.

Figure E.4

Figure E.5

6. The new disk is ready to use, the available size = 2.72TB.

Figure E.6

- 81 -

Figure E.7

Caution

If user setups 512B block size for VD and the host/server OS is 32bit, in the last step of formatting disk, user will find OS cannot format the disk sector after 2048GB (2TB).

7. Wrong setting result: OS can not format disk sector after 2048GB(2TB).

F. MPIO and MC/S setup instructions

Here is the instruction to setup MPIO or MC/S. The following network diagrams are the examples. Please follow them to setup the environment. Remind that host must have multi NICs which are set up as different IPs.

Figure E.8

- 82 -

Figure F.1

The MPIO setup instructions are in the following:

1. Create RG/VD, and then attach LUN.

2. Add the first “Target Portal” on Microsoft iSCSI initiator.

3. Add the second “Target Portal” on Microsoft iSCSI initiator.

4. Logon.

5. Enable “Enable multi-path” checkbox. Then click “Advanced…”.

6. Select the first “Source IP” and “Target Portal” to iSCSI data port 1.

Then click “OK”.

7. Logon again.

8. Enable “Enable multi-path” checkbox. Then click “Advanced…”.

9. Select the second “Source IP” and “Target Portal” to iSCSI data port 2.

Then click “OK”.

10. iSCSI device is connected. Click “Details”.

- 83 -

11. Click “Device” tab, then click “Advanced”.

12. Click “MPIO” tab, select “Load Balance Policy” to “Round Robin”.

13. Click “Apply”.

14. Run “Device Manage” in Windows. Make sure MPIO device is

available.

15. Done.

The MC/S setup instructions are in the following:

1. Create RG/VD, and then attach LUN.

2. Add the first “Target Portal” on Microsoft iSCSI initiator, For MC/S,

there is only ONE “Target Portals” in the “Discovery” tab.

3. Logon.

4. Then click “Advanced…”.

5. Select the first “Source IP” and “Target Portal” to iSCSI data port 1.

Then click “OK”.

6. After connected, click “Details”, then in the “Session” tab, click “Connections”.

7. Choose “Round Robin” in “Load Balance Policy”.

8. “Add” Source Portal for the iSCSI data port 2.

9. Select the second “Source IP” and “Target Portal” to iSCSI data port 2.

Then select “OK”.

10. Done.

G. BBM (Battery Backup Module) inspect steps

i8500 BBMs (battery backup module) protect the integrity of the cache data when user uses “write-back” cache policy.

Write-back cache policy means i8500 reply to the host that write access is complete when data is written into memory. Then i8500 writes the cached data to the disk device when system activity is low or when the cache is getting full. Another cache policy is “write through” which means i8500 reply to the host that write access is complete only when the data is written into disks.

Writing a block of data to cache memory is much faster than write it to a disk device, but there is risk for “write-back” cache policy. The risk of using write-back cache policy is that the cached data can be lost if the AC power fails or power outage before it has been written to the storage device. The risk factor could be eliminated when i8500 has an onboard BBM. i8500 monitor the power supply if BBM is installed. When power supply fail, then BBM mechanism switches the memory power source from AC power to BBM and retain the data in memory. When power supply recover, all data retain in memory will be flushed to storage device without data lost.

PS. If the i8500 face power outage or abnormal shutdown, you will see following log when restart the system.

- 84 -

z INFO: Abnormal shutdown detected, start flushing battery-backed data (xxx

KB).

z INFO: Abnormal shutdown detected, flushing battery-backed data finished

BBM inspect steps

1. Connect BBM cable into i8500 controller.

2. Initial controller, then BBM will start to charge automatically.

3. Wait and watch the value of “Battery Backup Module”, please reference the attached screen shot from console, Once the value is over 70%, the BBM can backup 1GB DDR-II cach over 72hr.

Note : The BBM is use for P2x0/S5x0/F2x0/S12x/P15x

- 85 -

■H■ M/B Diagram

- 86 -

Thecus i8500 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual