1

Installation TrainingEverything you need to know to get up and running

22

• Sales Training Corporate Overview - Why Dot Hill Products Solutions Selling Dot Hill The Dot Hill Process Overcoming Objections Services and Support Storage 101

• Technical Installation

3

Product IntroductionEverything you need to know to get up and running

44

R-Evolution Product Description

• Single-and Dual-controller hardware configurations 2U form factor with either 12 - 3.5” drives or 24 - 2.5”

drives Fully redundant, Hot-swap components

• DAS and SAN connectivity Windows, Linux, Solaris FC and iSCSI host interfaces

• Support from 2 to 96 or 144 disks SAS/SATA drives at many different capacity points

• RAID 0, 1, 3, 5, 6, 10, 50 data protection + NRAID• Hot spare support (Local and Global)• Embedded Management software

55

Assured Family™ of Protection

• AssuredRemote (Snapshot Replication : new ) DR solution or local volume duplication with low cost

storage FC or iSCSI media can be used Point-in-time logical image on both site

• AssuredSnap (Snapshots) Point-in-time logical image of a physical volume Protection against accidental or malicious loss or

corruption

• AssuredCopy (Volume Copy) Complete physical and independent copy of a

volume Additional protection against master volume failure

Protect against local and logical failures

66

Data in Place Upgrades

• Provides the ability to expand capacity, increase performance or switch host connections, speed and protocols with customer data in place! Just replace controller(s)

• From basic Architecture to: More JBODs for additional capacity Faster controllers for performance increase Mixed protocols to meet dynamic environments Advanced method for better data protection

• Any reconfiguration with data intact using single, common architecture

77

Terms Used

• Controller Tray/Chassis – An enclosure with one or two RAID I/O Modules

• Expansion Tray - An enclosure with one or two JBOD I/O Modules

• RAID I/O Module – A FRU containing the RAID controller and Host I/O module. Each controller tray contains one or two RAID I/O Modules.

• Expansion I/O Module / JBOD controller – A FRU with simple disk interface capabilities (no RAID). Each expansion tray contains one or two expansion modules

• WBI / RAIDar – Web Browser Interface• CLI – Command Line Interface

88

Management Interface Options

• Multiple means to manage the storage WBI – GUI interface, standard browser, no host software CLI – Embedded in controller, can be used from serial

connection or telnet/ssh session through Ethernet

• Even more ways to monitor the storage Visual – LED indicators on system, front and rear WBI – monitors event logs for browser display CLI – for prompted or scripted inquiry SNMP – for central monitoring via common software Email – Notification via email to sysadmins, distribution

lists SMI-S – Emerging SNIA common standard for storage FTP – for debug log capture to file or upgrade controller,

drive FW

9

Chassis Tour

12 Drive Sleds12 Drive SledsChassis ID

Chassis ID Status

LEDs

StatusLEDs

Power & Cooling Modules

Power & Cooling Modules

Controller Modules

Controller Modules

24 Drive Slots24 Drive Slots

10

Chassis Tour - Disk Module

Disk Slot Order

0-1-2 23-24

11

Chassis Tour – Status LEDs

Unit Locator

Fault / Service

Power

Temperature Fault

12

Interface Connections

1313

RAID I/O Module

• All controllers have a similar layout• Above shows a Fiber Channel controller

Link Status

Link Speed

SystemLocator

OK to Remove

Fault / Service

FRU Status

Cache Status

Host Activity

Ethernet Link Status

Ethernet Activity

ExpansionPort Status

14

Expansion I/O Module

SystemLocator

SAS InPort Status

OK toRemove

Fault / ServiceRequired

PowerSAS Out

Port Status

SAS In Port SAS Out Port

Service Port

15

Power and Cooling Module

Power Switch

Power Input

Ejection Handle

AC Power Good

DC-Fan Fault/Service Required

Dual Fans in each power supply

16

Array ConfigurationEverything you need to know to get up and running

17

Logs and More Advanced Stuff

Everything you need to know to get up and running

18

Unique FeaturesEverything you need to know to get up and running

1919

SimulCache

• During normal operation:• Host data sent to one controller module is

automatically copied to the other controller module’s write cache using broadcast write technology

• Broadcast write provides simultaneous caching of write data to the cache memory in both controller modules over an internal PCI Express bus

• Improves mirrored cache write operations• 92% as efficient as non-mirrored cache

operations

20

Conventional Cache Mirroring

Disk Interconnect

Cache Processor

Host Interconnect(FC, SAS, etc.)

Processor CacheDisk

Interconnect

Host Interconnect(FC, SAS, etc.)

SAS Drives

Controller 1 Controller 2

PCI PCI

SAN SAN

1) Host initiates write command

1) Host initiates write command

2) Write is mirrored to second controller

2) Write is mirrored to second controller

3) Second controller acknowledges write

3) Second controller acknowledges write

4) Controller acknowledges

successful write

4) Controller acknowledges

successful write

W-ack

W

Traditional Method

21

SimulCache Mirrored Cache

Disk Interconnect

Cache Processor

Host Interconnect(FC, SAS, etc.)

Processor CacheDisk

Interconnect

Host Interconnect(FC, SAS, etc.)

SAS Drives

Controller 1 Controller 2

PCI PCI

SAN SAN

Broadcast WriteCircuitry

Broadcast WriteCircuitry

W

W

SimulCache

1) Host initiates write command

1) Host initiates write command

W-ack

2) Controller acknowledges

successful write

2) Controller acknowledges

successful write

The Dot Hill Advantage

2222

EcoStor Technology

• Battery-free alternative for cache backup• Ensures cache data is stored safely when

power fails• System enters write-back mode in minutes vs.

hours with batteries• Up to 10 year life span – eliminates periodic

battery replacement down time• Environmentally friendly – corresponds with

our global responsibility spirit

23

EcoStor Technology

23

zzPrimaryPower

RAIDController

DDR-SDRAMCache Memory

Compact Flash-IISocket

(CF card or uDrive)

DDRInterface

IDEInterface

PWR_STATE[1:0]Power

Monitor andBackup

Logic

PowerRegulators

ClockSource

Storage ControllerCPU Subsystem

CPCI

On-boardFlash

Store signature forcache validity ofremovable NV memory

FLUSH_STATUS[1:0]

Reset

Remain Powered during Flush Operation

Powered-down during Flush Operation

EcoStorEcoStor

BackupPower

Super Caps provide enough power to flush cache data to the compact flash card, then refresh memory

24

Unbox and RackEverything you need to know to get up and running

25

Array Installation

2626

Installation Overview

• Unpack the array• Obtain the necessary accessories and equipment• Mount the controller and expansion trays in a rack or

cabinet• Connect the power to the two power modules• Perform initial power-up• Connect the management hosts to the controller tray• Connect the data hosts to the controller tray• Use WBI or the CLI to set the

Ethernet, netmask, and gateway addresses, for each controller module

Array date and time; change the management password

• Set the basic array configuration parameters• Plan and implement your storage configuration

27

Assemble Rail Kits

Attach side brackets12-drive enclosure show below

Install hanger fasteners

28

Install Rails1 2

43 5

29

Install and secure the enclosure

30

Connecting the ArrayEverything you need to know to get up and running

3131

Connect storage and power up

• Connect power• Connect to host network

Fiber Channel Ethernet

• Set management IP address

3232

Connecting to a terminal emulator

• Start and configure a terminal emulator, such as HyperTerminal using the following settings: Terminal Emulator Display Settings

Terminal Emulation Mode ANSI (for color support) Font Terminal Translations None Columns 80

Terminal Emulator Connection Settings Connector COM1 (typically) Baud rate (bits/sec) 115,200 Data bits 8 Parity None Stop bits 1 Flow control None

Connect to the storage array to set the management IP address

3333

Applying the IP Address

• At the prompt (#), type the following command to set the IP address for controller A set network-parameters ip <address> netmask

<netmask> gateway <gateway> controller <a|b>

• Verify Ethernet connectivity by pinging the IP addresses

• Optional At the prompt (#), use the same command to set the

IP address for controller B except b Type the following command to verify the new IP

addresses: show network-parametersYou can now manage the storage through the web interface

34

Changing the IP Address

• After you have established the initial address you can change the address from the web based interface

35

Connecting Expansion Units

36

Expansion Trays

Controller A SAS ‘Out’ portController A SAS ‘Out’ port

Controller B SAS ‘Out’ portController B SAS ‘Out’ port

A

B

A

B

SAS ‘In’ portsSAS ‘In’ ports SAS ‘Out’ portsSAS ‘Out’ ports

• You can add additional storage on the fly by cabling in JBOD systems

37

Cabling Expansion Trays (cont.)

• Cable from top RM-A to top IOM-A, and bottom RM-B to bottom IOM-B• Still have path

to surviving JBODs on one chassis power lost

• Repeat for each JBODs:• up 7 for 2U12

(max 96 drives)• Up to 5 for

2U24 (max 144 drives)

00 0RAID A0RAID B

SASExpansionChannel 0

11 IOM AIn Out

IOM BIn Out

22 IOM AIn Out

IOM BIn Out

33 IOM AIn Out

IOM BIn Out

44 IOM AIn Out

IOM BIn Out

38

Connecting Host Systems

39

Non-Redundant Single Host DAS

A

B

PO P1

PO P1

• Utilizes a single HBA • Can access all A and B volumes

• with ALUA (Asymmetric LUN Access)• volume on B has penalty for this

• Is a non-redundant configuration

Host Port Connection – Single Connection

40

A

B

PO P1

PO P1

• Utilizes two HBA’s • Has access to all A and B volumes• Is a redundant configuration

• Host should use MPIO driver for HA purpose• Has more bandwidth in total

Host Port Connection – Two connections

Redundant Single Host DAS

41

A

B

PO P1

PO P1

1 2

Host Port Connection – Two nodes DAS and MPIO

Redundant Dual Host DAS

Okay with MS Cluster or Linux based Cluster and other HA configuration

42

A

B

PO P1

PO P1

1 2

Host Port Connection – Applicable for all R/Evo gen.

Redundant Multi Host SAN

For ALUA or ULP systems (All but 2730, 2330), 2nd connection from server 1 to B-P1 can be go to B-P0 (More intrinsic and simple).