Dot Hill II 200 FC User Manual

SANnet II 200 FC, SATA, and SATA SE

Array Installation, Operation, and

Service Manual

March 2005 83-00003261, Revision C

Copyright  2001-2005 Dot Hill Systems Corp. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, translated, transcribed, or transmitted, in any form or by any means – manual, electric, electronic, electromechanical, chemical, optical, or otherwise – without prior explicit written permission of Dot Hill Systems Corp., 6305 El Camino Real, P.O. Box 9000, Carlsbad, CA., 92009-1606.

Trademarks

Dot Hill Systems, the Dot Hill logo, SANscape, SANnet, and SANpath are registered trademarks of Dot Hill Systems Corp. All other trademarks and registered trademarks are proprietary to their respective owners.

Changes

The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, Dot Hill Systems Corp., assumes no liability resulting from errors or omissions in this document, or from the use of the information contained herein. Dot Hill Systems Corp., reserves the right to make changes in the product design without reservation and without notification to its users.

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

1. Product and Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

1.1 Comparison of FC, SATA, and SATA SE Arrays . . . . . . . . . . . . . . . . . . . . . . . .1–2

1.1.1 Fibre Channel and SATA Array Architectures . . . . . . . . . . . . . . . . . . 1–3

1.1.1.1 SANnet II 200 FC Array Features . . . . . . . . . . . . . . . . . . . 1–3

1.1.1.2 SANnet II 200 SATA and SATA SE Array Features . . . . . . 1–4

1.1.2 Differences Between SANnet II 200 FC Arrays and SANnet II 200

SATA Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–4

1.1.3 SANnet II 200 FC, SATA, and SATA SE Array Configurations . . . . . . 1–6

1.2 Field-Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–8

1.2.1 RAID I/O Controller Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8

1.2.2 I/O Expansion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–9

1.2.3 Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9

1.2.3.1 SANnet II 200 FC Array Disk Drives . . . . . . . . . . . . . . . . 1–10

1.2.3.2 SANnet II 200 SATA and SATA SE Array Disk Drives . . . 1–10

1.2.4 Battery Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–10

1.2.5 Power and Fan Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11

1.3 Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–11

1.4 Fibre Channel Technology Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–11

1.4.1 FC Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12

1.4.2 FC Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–12

1.4.3 Fibre Hubs and Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12

1.4.4 Data Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13

1.4.5 Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–13

iii

1.5 Fibre Channel Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–14

1.5.1 Redundant Configuration Considerations . . . . . . . . . . . . . . . . . . . .1–14

1.5.1.1 Host Bus Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–14

1.5.1.2 Active-to-Active Redundant Controller . . . . . . . . . . . . . . .1–15

1.5.1.3 Host Redundant Paths . . . . . . . . . . . . . . . . . . . . . . . . . .1–15

1.6 Additional Software Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–15

2. Site Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–1

2.1 Customer Obligations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–1

2.2 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–2

2.3 Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–3

2.3.1 Electromagnetic Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–3

2.4 Electrical and Power Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–3

2.5 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–4

2.6 Layout Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–4

2.6.1 Rack Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–4

2.6.2 Tabletop Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–5

2.7 Console and Other Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–5

2.8 Preinstallation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–6

3. Unpacking Your Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–1

3.1 Opening Your Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–1

3.2 Checking the Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–2

3.2.1 Standard Array Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–2

3.3 Field-Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–3

3.4 Customer-Provided Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–3

3.5 Mounting Your Array in a Rack or Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–3

4. Connecting Your Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–1

4.1 Converting Your Front Bezel Locks So the Keys Cannot Be Removed . . . . . .4–2

4.2 RAID Array Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–4

4.2.1 SANnet II 200 FC Array Connections . . . . . . . . . . . . . . . . . . . . . . . .4–4

4.2.2 SANnet II 200 SATA Array Connections . . . . . . . . . . . . . . . . . . . . . . .4–5

4.2.3 SANnet II 200 SATA SE Array Connections . . . . . . . . . . . . . . . . . . . .4–7

4.3 Connecting the Chassis to AC Power Outlets . . . . . . . . . . . . . . . . . . . . . . . . .4–7

iv SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

4.4 Connecting the Chassis to DC Power Outlets . . . . . . . . . . . . . . . . . . . . . . . . .4–9

4.5 Cabling to Expansion Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11

4.6 Setting Loop IDs on Expansion Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–13

4.7 Powering Up and Checking LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16

4.8 Reviewing Channels, Ports, and SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16

4.8.1 Drive Port Connectivity in a Dual-Controller Array . . . . . . . . . . . . . . 4–17

4.8.1.1 SANnet II 200 FC Array Drive Ports . . . . . . . . . . . . . . . . 4–18

4.8.1.2 SANnet II 200 SATA Array Drive Ports . . . . . . . . . . . . . .4–18

4.8.2 Host Port Connectivity in a Dual-Controller Array . . . . . . . . . . . . . . 4–19

4.8.2.1 SANnet II 200 FC Array . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19

4.8.2.2 SANnet II 200 SATA and SATA SE Arrays . . . . . . . . . . . . 4–20

4.8.3 Default SFP Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21

4.8.4 Changing Your SFP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24

4.9 Establishing Communications With An Array . . . . . . . . . . . . . . . . . . . . . . . . .4–25

4.10 Configuring a Host COM Port to Connect to a RAID Array . . . . . . . . . . . . . . 4–26

4.11 Manually Setting a Static IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–27

4.12 Setting Up Out-of-Band Management Over Ethernet . . . . . . . . . . . . . . . . . . 4–28

4.13 Scaling a SANnet II 200 Fibre Channel Array Into a High-Capacity

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29

4.14 Adding an Expansion Unit to an Existing RAID Array . . . . . . . . . . . . . . . . . . 4–30

4.15 Connecting Ports to Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31

4.16 Power-On Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–32

4.17 Powering Off the Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33

5. Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–1

5.1 Summary of Array Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–1

5.1.1 Point-to-Point Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . 5–3

5.1.2 A Sample SAN Point-to-Point Configuration . . . . . . . . . . . . . . . . . . . 5–5

5.1.3 A Sample DAS Loop Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 5–10

5.1.4 Connecting Two Hosts to One Host Channel (SATA Only) . . . . . . . . 5–14

5.2 Larger Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14

6. Checking LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–1

6.1 LEDs When The Array Is First Powered On . . . . . . . . . . . . . . . . . . . . . . . . . .6–1

6.2 Front-Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2

Contents v

6.2.1 Drive LED Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–4

6.2.2 Correcting SES or PLD Firmware Version Conflicts . . . . . . . . . . . . . .6–4

6.3 Back-Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–5

6.3.1 I/O Controller Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–5

6.3.2 I/O Expansion Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–8

6.3.3 Power Supply and Fan Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . .6–9

7. Maintaining Your Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–1

7.1 Using Software to Monitor and Manage the Array . . . . . . . . . . . . . . . . . . . . . .7–1

7.1.1 Out-of-Band Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–2

7.1.2 In-Band Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–2

7.1.3 Other Supported Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–2

7.1.4 Enabling VERITAS DMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–3

7.1.5 The VERITAS Volume Manager ASL . . . . . . . . . . . . . . . . . . . . . . . . .7–4

7.2 Battery Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–4

7.2.1 Battery Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–4

7.3 Viewing Event Logs on the Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–5

7.4 Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–7

7.4.1 Installing Firmware Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–7

7.4.2 Controller Firmware Upgrade Features . . . . . . . . . . . . . . . . . . . . . . .7–7

7.4.3 Upgrading SES and PLD Firmware . . . . . . . . . . . . . . . . . . . . . . . . . .7–8

7.5 Replacing the Front Bezel and Ear Caps . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–8

7.5.1 Removing the Front Bezel and Ear Caps . . . . . . . . . . . . . . . . . . . . . .7–9

7.5.2 Placing the Bezel and Ear Caps Back Onto the Chassis . . . . . . . . . .7–9

8. Troubleshooting Your Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–1

8.1 Sensor Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–1

8.1.1 Cooling Element Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–2

8.1.2 Temperature Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–3

8.1.3 Voltage Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–4

8.1.4 Power Supply Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–5

8.2 Silencing Audible Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–5

8.3 RAID LUNs Not Visible to the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–7

8.4 Controller Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–7

vi SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

8.5 Recovering From Fatal Drive Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8

8.6 Using the Reset Push Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10

8.7 Troubleshooting Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–11

8.7.1 Power Supply and Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–11

8.7.2 Drive LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–13

8.7.3 Front-Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–16

8.7.4 I/O Controller Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–21

A. SANnet II 200 FC, SATA, and SATA SE Array Specifications . . . . . . . . . . . . . . . A–1

A.1 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–1

A.2 SANnet II 200 FC, SATA, and SATA SE Array Highlights . . . . . . . . . . . . . . . . A–2

A.3 Agency Approvals and Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–4

B. Using a Standalone JBOD Array (SANnet II 200 FC Array Only) . . . . . . . . . . . . B–1

B.1 Supported Configurations (JBOD Arrays) . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1

B.2 Supported Operating Systems (JBOD Arrays) . . . . . . . . . . . . . . . . . . . . . . . B–2

B.3 Supported Host Platforms and Connection Methods (JBOD Arrays) . . . . . . . B–2

B.4 Known Limitations Affecting SANnet II 200 FC JBOD Arrays . . . . . . . . . . . . B–2

B.5 Using SANnet II Family Software Monitoring and Management Tools with

JBOD Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–3

B.6 Setting the Loop ID on a SANnet II 200 FC JBOD Array . . . . . . . . . . . . . . . . B–4

B.7 Connecting SANnet II 200 FC JBOD Arrays . . . . . . . . . . . . . . . . . . . . . . . . . B–6

B.8 Enabling SANnet II 200 FC JBOD Array Support . . . . . . . . . . . . . . . . . . . . .B–10

B.9 Downloading Firmware to Disk Drives in a JBOD . . . . . . . . . . . . . . . . . . . . .B–11

B.10 Resizing LUNs Greater Than 1 Tbyte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–12

B.11 Troubleshooting SANnet II 200 FC JBOD Arrays . . . . . . . . . . . . . . . . . . . . .B–12

B.12 Converting a JBOD to a RAID array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–16

C. Failed Component Alarm Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–1

D. Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–1

D.1 RJ-45 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–1

D.2 DB9 COM Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–2

E. Configuring a Sun Server Running the Solaris Operating System . . . . . . . . . . .E–1

E.1 Setting Up the Serial Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E–1

Contents vii

E.2 Using the tip Command for Local Access to the Array . . . . . . . . . . . . . . . . E–2

E.3 Determining the WWN in the Solaris Operating System . . . . . . . . . . . . . . . . E–3

F. Configuring a Microsoft Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F–1

F.1 Setting Up the Serial Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F–1

F.2 Accessing the Firmware Application From a Microsoft Windows Server . . . . F–4

F.3 Enabling a Microsoft Windows Server to Recognize New Devices and LUNs F–4

F.4 Determining the Worldwide Name for Microsoft Windows Servers . . . . . . . . F–8

G. Configuring a Linux Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–1

G.1 Setting Up the Serial Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–1

G.2 Accessing the Firmware Application From a Linux Server . . . . . . . . . . . . . . . G–3

G.3 Checking the Adapter BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–4

G.4 Multiple LUN Linux Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–5

G.5 Making an ext3 File System for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–5

G.6 Creating a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–6

G.7 Creating a Mount Point and Mounting the File System Manually . . . . . . . . . . G–7

G.8 Mounting the File System Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–7

G.9 Determining the Worldwide Name for Linux Hosts . . . . . . . . . . . . . . . . . . . . G–8

H. Configuring an IBM Server Running the AIX Operating System . . . . . . . . . . . . . H–1

H.1 Setting Up a Serial Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H–1

H.2 Accessing the Firmware Application From an IBM Server Running AIX . . . . H–2

H.3 Identifying the Device on Which You Will Create a Logical Volume . . . . . . . . H–4

H.4 Using SMIT to Enable an AIX Host to Recognize New LUNs . . . . . . . . . . . . H–4

H.5 Creating a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H–5

H.6 Creating a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H–6

H.7 Creating a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H–6

H.8 Mounting the New File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H–7

H.9 Verifying That the New File System Is Mounted . . . . . . . . . . . . . . . . . . . . . . H–7

H.10 Determining the Worldwide Name for IBM Servers Running AIX . . . . . . . . . . H–8

I. Configuring an HP Server Running the

HP-UX Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–1

I.1 Setting Up a Serial Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–1

I.2 Accessing the Firmware Application From an HP Server Running HP-UX . . . I–2

viii SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

I.3 Attaching the Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–4

I.4 Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–4

I.5 Definitions of Common Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–5

I.6 Creating a Physical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–5

I.7 Creating a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–6

I.8 Creating a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–7

I.9 Creating an HP-UX File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–8

I.10 Mounting the File System Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–8

I.11 Mounting the File System Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–8

I.12 Determining the Worldwide Name for HP-UX Hosts . . . . . . . . . . . . . . . . . . . . I–9

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index–1

Contents ix

x SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Figures

FIGURE 1-1 SANnet II 200 FC, SATA, and SATA SE Array Front View . . . . . . . . . . . . . . . . . 1–2

FIGURE 4-1 Front Bezel and Front Bezel Locks of an Array . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2

FIGURE 4-2 Sequence of Steps to Change Front Bezel Locks So Keys Cannot Be

Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3

FIGURE 4-3 Hardware Connections on the Back of a Dual-Controller SANnet II 200

FC Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5

FIGURE 4-4 Hardware Connections on the Back of a Dual-Controller SANnet II 200

SATA Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6

FIGURE 4-5 Hardware Connections on the Back of a Dual-Controller SANnet II 200 SATA

SE Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7

FIGURE 4-6 Installing a Cord Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9

FIGURE 4-7 SANnet II 200 FC Array Attached to Two Hosts and Two Expansion Units . . . 4–12

FIGURE 4-8 SANnet II 200 SATA Array Attached to Two Hosts and Two Expansion Units . 4–13

FIGURE 4-9 Front Bezel and Front Bezel Locks of an Array . . . . . . . . . . . . . . . . . . . . . . . . . 4–14

FIGURE 4-10 ID Switch Located on the Left Front Side of Arrays and Expansion Units . . . . . 4–14

FIGURE 4-11 Front Panel of the SANnet II 200 FC, SATA, and SATA SE Array With LEDs

Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16

FIGURE 4-12 Dedicated Drive Channels 2 on the Upper Controller and 3 on the Lower

Controller in a Dual-Controller SANnet II 200 FC Array . . . . . . . . . . . . . . . . . . . 4–18

FIGURE 4-13 Dedicated Drive Channels 2 and 3 (on Both Controllers) in a Dual-Controller

SANnet II 200 SATA Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19

FIGURE 4-14 Host Channels on a Dual-Controller SANnet II 200 FC Array . . . . . . . . . . . . . . 4–20

FIGURE 4-15 Host Channels on a Dual-Controller SANnet II 200 SATA Array . . . . . . . . . . . . 4–21

FIGURE 4-16 Host Channels on a Dual-Controller SATA SE Array . . . . . . . . . . . . . . . . . . . . . 4–21

FIGURE 4-17 Default Dual-Controller SANnet II 200 FC Array SFP Placement . . . . . . . . . . . 4–22

FIGURE 4-18 Default Dual-Controller SANnet II 200 SATA Array SFP Placement . . . . . . . . . 4–22

FIGURE 4-19 SANnet II 200 FC Array Default Single Controller SFP Placement . . . . . . . . . . 4–23

FIGURE 4-20 SANnet II 200 SATA Array Default Single-Controller SFP Placement . . . . . . . .4–23

FIGURE 4-21 SANnet II 200 FC JBOD/Expansion Unit Default SFP Placement . . . . . . . . . . . 4–24

FIGURE 4-22 SANnet II 200 SATA Expansion Unit Default SFP Placement . . . . . . . . . . . . . . 4–24

FIGURE 4-23 Typical SFP Connector Used to Connect Cables to Chassis SFP Ports . . . . . .4–25

FIGURE 5-1 A Point-to-Point Configuration with a Dual-Controller SANnet II 200 FC Array

and Two Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7

FIGURE 5-2 A Point-to-Point Configuration With a Dual-Controller SANnet II 200 SATA Array

and Two Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8

FIGURE 5-3 A DAS Configuration With Four Servers, a Dual-Controller SANnet II 200 FC

Array, and Two Expansion Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11

FIGURE 5-4 A DAS Configuration With Four Servers, a Dual-Controller SANnet II 200 SATA

Array, and Two Expansion Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12

FIGURE 6-1 Front-Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2

FIGURE 6-2 Chassis Ear LEDs and Reset Button on Front Panel . . . . . . . . . . . . . . . . . . . . . . 6–2

FIGURE 6-3 SANnet II 200 FC Array I/O Controller Module and Battery Module LEDs . . . . . .6–5

FIGURE 6-4 SANnet II 200 SATA Array I/O Controller Module and Battery Module LEDs . . . 6–6

FIGURE 6-5 SANnet II 200 SATA SE Array RAID Controller I/O and Battery Module LEDs . . 6–6

FIGURE 6-6 I/O Expansion Module for a SANnet II 200 FC Expansion Unit . . . . . . . . . . . . . . 6–8

FIGURE 6-7 I/O Expansion Module for a SANnet II 200 SATA Expansion Unit . . . . . . . . . . . . 6–8

FIGURE 6-8 AC Power Supply and Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10

FIGURE 6-9 DC Power Supply and Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10

FIGURE 8-1 Cooling Fan Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2

FIGURE 8-2 Power Supply or Fan Module Flowchart, 1 of 2 . . . . . . . . . . . . . . . . . . . . . . . . . 8–12

FIGURE 8-3 Power Supply or Fan Module Flowchart, 2 of 2 . . . . . . . . . . . . . . . . . . . . . . . . . 8–13

FIGURE 8-4 Drive LEDs Flowchart, 1 of 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–15

FIGURE 8-5 Drive LEDs Flowchart, 2 of 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–16

FIGURE 8-6 Front-Panel LEDs Flowchart, 1 of 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–17

FIGURE 8-7 Front-Panel LEDs Flowchart, 2 of 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–18

FIGURE 8-8 Front-Panel LEDs Flowchart, 3 of 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–19

FIGURE 8-9 Front-Panel LEDs Flowchart, 4 of 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20

FIGURE 8-10 I/O Controller Module Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–21

FIGURE B-1 ID Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–5

FIGURE B-2 SANnet II 200 FC JBOD Array Attached to a Single HBA Port . . . . . . . . . . . . . B–7

xii SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

FIGURE B-3 SANnet II 200 FC JBOD Array Attached to Two HBA Ports . . . . . . . . . . . . . . . . B–8

FIGURE B-4 JBOD or Expansion Unit Troubleshooting Flowchart, 1 of 2 . . . . . . . . . . . . . . . B–15

FIGURE B-5 JBOD or Expansion Unit Troubleshooting Flowchart, 2 of 2 . . . . . . . . . . . . . . . B–16

FIGURE D-1 Ethernet RJ-45 Socket 10/100BASE-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–1

FIGURE D-2 RS-232 DB9 (EIA/TIA 574) View of the Male End . . . . . . . . . . . . . . . . . . . . . . . .D–2

FIGURE E-1 RAID Array COM Port Connected Locally to the Serial Port of a Workstation . . . E–2

FIGURE E-2 Worldwide Name Information Displayed by the luxadm command. . . . . . . . . . . E–3

FIGURE H-1 RAID Array COM Port Connected Locally to the Serial Port of a Host System . .H–3

FIGURE H-2 Network Address Corresponding to WWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H–8

FIGURE I-1 RAID Array COM Port Connected Locally to the Serial Port of a Host System . . I–3

Figures xiii

xiv SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Tables

TA BL E 1 -1 Comparison of SANnet II 200 FC, SATA, and SATA SE Array Features . . . . . . . . 1–5

TA BL E 1 -2 SANnet II 200 FC, SATA, and SATA SE Array Configuration Options . . . . . . . . . . 1–7

TA BL E 2 -1 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3

TA BL E 2 -2 Power Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4

TA BL E 2 -3 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4

TA BL E 2 -4 Site Preparation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7

TA BL E 2 -5 Host and Fabric Switch Connectivity Summarized . . . . . . . . . . . . . . . . . . . . . . . . . 2–8

TA BL E 3 -1 Contents of SANnet II 200 Array Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2

TA BL E 4 -1 DC Cable Wiring for Cable 35-00000148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10

TA BL E 4 -2 DC Cable Wiring for Cable 35-00000156 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10

TA BL E 4 -3 ID Switch Settings for Expansion Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15

TA BL E 4 -4 Sample Array and Expansion Units With Different Loop IDs and Drive IDs . . . . . 4–15

TA BL E 4 -5 Number of Ports in SANnet II 200 FC, SATA, and SATA SE Arrays . . . . . . . . . . 4–17

TA BL E 4 -6 Number of Host Ports and Supported Host Port Speeds . . . . . . . . . . . . . . . . . . . 4–19

TA BL E 5 -1 Example Point-to-Point Configuration With Two Logical Drives in a Dual-Controller

Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9

TA BL E 5 -2 Connection for Four Servers in a DAS Configuration . . . . . . . . . . . . . . . . . . . . . . 5–10

TA BL E 5 -3 Example Primary and Secondary ID Numbers in a Loop Configuration With Two

IDs per Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13

TA BL E 6 -1 Front-Panel LED Status When Array Is First Powered On . . . . . . . . . . . . . . . . . . . 6–1

TA BL E 6 -2 Front-Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3

TA BL E 6 -3 Drive LED Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4

TA BL E 6 -4 I/O Controller Module and Battery Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7

TA BL E 6 -5 I/O Expansion Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9

TA BL E 6 - 6 Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–9

TA BL E 7 - 1 Battery Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–4

TA BL E 8 - 1 Cooling Element Sensors for FC, SATA, and SATA SE Arrays . . . . . . . . . . . . . . .8–2

TA BL E 8 - 2 Temperature Sensors for FC, SATA, and SATA SE Arrays . . . . . . . . . . . . . . . . . . 8–3

TA BL E 8 - 3 Voltage Sensors for FC Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4

TA BL E 8 - 4 Voltage Sensors for SATA and SATA SE Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4

TA BL E 8 - 5 Power Supply Sensors for FC, SATA, and SATA SE Arrays . . . . . . . . . . . . . . . . . 8–5

TA BL E 8 - 6 Silencing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7

TA BL E A - 1 SANnet II 200 FC, SATA, and SATA SE Array Physical Specifications . . . . . . . . A–1

TA BL E A - 2 SANnet II 200 FC, SATA, and SATA SE Array Highlights . . . . . . . . . . . . . . . . . . A–2

TA BL E A - 3 SANnet II 200 FC, SATA, and SATA SE Array Product Safety & Electromagnetic

Standards A–4

TA BL E B - 1 Supported Sun Servers and Connection Methods (JBOD Arrays) . . . . . . . . . . . . B–2

TA BL E B - 2 ID Switch Settings for SANnet II 200 FC JBOD Arrays . . . . . . . . . . . . . . . . . . . . . B–5

TA BL E B - 3 Example of 12 Drives Shown on a 12-Disk SANnet II 200 FC JBOD Array

Connected to a Host Over a Single FC Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–7

TA BL E B - 4 Example of 24 Drives Shown on a 12-Disk SANnet II 200 FC JBOD Array

Connected to a Host Over Two FC Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–9

TA BL E C - 1 Failed Component Alarm Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–1

TA BL E D - 1 Ethernet RJ-45 Pin Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–1

TA BL E D - 2 Pin Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–2

xvi SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Preface

This manual provides instructions for installing, initially configuring, and operating the SANnet II 200 Fibre Channel (FC), SANnet II 200 SATA, and the SANnet II 200 SATA Special Edition (SE) arrays; hereafter referred to as FC, SATA, and SATA SE arrays for ease of reading.

This guide is written for experienced system administrators who are familiar with Dot Hill hardware and software products.

Caution – Read the SANnet II Family Safety, Regulatory, and Compliance Manual

before beginning any procedure in this manual.

How This Book Is Organized

This book covers the following topics:

Chapter 1 provides an overview of the array’s features.

Chapter 2 covers site planning and basic safety requirements.

Chapter 3 provides general procedures for unpacking and inspecting the array.

Chapter 4 provides procedures for connecting your array to power and to the network.

Chapter 5 provides an overview of the array configuration.

Chapter 6 describes the array’s front and back-panel LEDs.

Chapter 7 describes maintenance procedures.

Chapter 8 describes troubleshooting procedures.

Appendix A provides the SANnet II 200 FC, SATA, and SATA SE array specifications.

Appendix B provides information about standalone JBOD arrays.

Appendix C provides information about failed component alarm codes.

Appendix D provides pinout identification for each connector.

Preface xvii

Appendix E provides instructions on configuring a Sun™ server.

Appendix F provides instructions on configuring a Windows 2000 or Windows 2000 Advanced server.

Appendix G provides instructions on configuring a Linux server.

Appendix H provides instructions on configuring a IBM AIX server.

Appendix I provides instructions on configuring an HP-UX server.

Typographic Conventions

Typ efac e

AaBbCc123 The names of commands, files,

text Computer menu Click Start.

AaBbCc123 Book titles, new words or

1. The settings on your browser might differ from these settings.

Meaning Examples

and directories; on-screen computer output

terms, words to be emphasized. Replace command-line variables with real names or values.

Technical Support

For late-breaking Release Notes and all manuals for this product, go to the SANnet II SCSI array section, or the SANnet II 200 FC array section, depending on which array you have, at:

http://www.dothill.com/manuals

The following information may be required when contacting Technical Support: Dot Hill serial number and part number of hardware; version of Dot Hill supplied software; host computer platform and operating system version; description of the problem and any related error messages.

Supply the following information to facilitate our tracking system and improve our response time: customer name, company name; state and country; telephone number with area code; Internet mail address; maintenance contract number, if applicable.

Placing a Support Call

After obtaining the above information, a support call may be placed by Internet mail, fax, or telephone.

Phone: 1-877-DOT7X24 (877-368-7924)

URL: http://www.dothill.com/support/index.htm

Corporate Headquarters Contacts

United States (California) Corporate Headquarters

Tel: 1-760-931-5500 or 1-800-872-2783 Fax: 1-760-931-5527 E-mail: support@dothill.com

Netherlands: European Headquarters

Dot Hill Systems Corp., B.V. (Netherlands) Tel: 31 (0) 53 428 4980; Fax: 31 (0) 53 428 0562 E-mail: bv@dothill.com

Japan: Japanese Headquarters

Nihon Dot Hill Systems Corp., Ltd.

Tel: 81-3-3251-1690; Fax: 81-3-3251-1691 E-mail: nihon@dothill.com

For additional sales offices in the U.K., China, Sweden, Germany, France, Israel, and Singapore, see our web site:

http://www.dothill.com/company/offices.htm

Preface xix

Dot Hill Welcomes Your Comments

Dot Hill is interested in improving its documentation and welcomes your comments and suggestions. You can email your comments to:

support@dothill.com

Include the part number (83-00003261) of your document in the subject line of your email.

xx SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

CHAPTER

Product and Architecture Overview

This manual describes the SANnet II 200 FC, SATA, and SATA Special Edition (SE) arrays.

The FC, SATA, and SATA SE arrays are rack-mountable, Network Equipment Building System (NEBS) Level 3-compliant, Fibre Channel mass storage subsystems. NEBS Level 3 is the highest level of NEBS criteria used to assure maximum operability of networking equipment in mission-critical environments such as telecommunications central offices.

SANnet II 200 FC Array. The SANnet II 200 FC array is a Fibre Channel (FC) array designed for high availability, high performance, and high capacity.

SANnet II 200 SATA and SATA SE Array. The SANnet II 200 SATA and SATA SE arrays are designed for high availability, and employs Serial ATA (SATA) technology for high-density storage, with a Fibre Channel front end. This provides high capacity with a small footprint, making this array ideal for content management archiving applications.

This chapter provides a brief overview of the FC, SATA, and SATA SE arrays. Topics covered in this chapter are:

■ “Comparison of FC, SATA, and SATA SE Arrays” on page 1-2

■ “Field-Replaceable Units” on page 1-8

■ “Interoperability” on page 1-11

■ “Fibre Channel Technology Overview” on page 1-11

■ “Fibre Channel Architecture” on page 1-14

■ “Additional Software Tools” on page 1-15

Note – Unless otherwise indicated, all features and procedures apply to the FC, SATA,

and SATA SE arrays.

1-1

1.1 Comparison of FC, SATA, and SATA SE Arrays

Figure 1-1 SANnet II 200 FC, SATA, and SATA SE Array Front View

The SANnet II 200 FC array is a next-generation Fibre Channel storage system designed to provide direct attached storage (DAS) to entry-level, mid-range, and enterprise servers, or to serve as the disk storage within a storage area network (SAN). This solution features powerful performance and reliability, availability, and serviceability (RAS) features using modern FC technology. As a result, the SANnet II 200 FC array is ideal for performance-sensitive applications and for environments with many entry-level, mid-range, and enterprise servers, such as:

■ Internet

■ Messaging

■ Database

■ Technical

■ Imaging

The SANnet II 200 SATA and SATA SE arrays are best suited for inexpensive secondary storage applications that are not mission-critical where higher-capacity drives are needed, and where lower performance and less than 7/24 availability is an option. These include near-line applications such as:

■ Information lifecycle management

■ Content addressable storage

■ Backup and restore

■ Secondary SAN storage

■ Near-line DAS storage

■ Static reference data storage

It is possible, though not always desirable, to combine both FC expansion units and SATA expansion units connected to a SANnet II 200 FC RAID array. For instance, you might want to use two SANnet II 200 SATA expansion units for near-line backup and archival storage while the Fibre Channel drives in your RAID array and other expansion units are used for real-time, mission-critical information processing and input/output (I/O) operations.

For an example of such a configuration, refer to the SANnet II 200 FC and SATA Array Best Practices Manual.

1-2 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

1.1.1 Fibre Channel and SATA Array Architectures

The FC, SATA, and SATA SE share many architectural elements. This section discusses those elements, making note of the few ways in which the architecture is implemented differently in the two arrays.

The SANnet II 200 FC array, SATA array, and SATA SE array RAID controllers have six FC channels. RAID controller channels 0, 1, 4, and 5 are normally designated for connection to hosts or Fibre Channel switches. RAID controller channels 2 and 3 are dedicated drive channels that connect to disks. Each channel has a single port connection, except the SANnet II 200 SATA array, which has two extra ports (two connections for channels 0 and 1).

In a dual RAID controller configuration, the architecture of the loops within the chassis provides both RAID controllers the same host channel designators. Each host channel of the top RAID controller shares a loop with the matching host channel on the bottom RAID controller. For example, channel 0 of the top RAID controller shares the same loop as channel 0 of the bottom RAID controller. This provides four distinct loops for connectivity. The individual loops provide logical unit number (LUN) failover without causing host bus adapter (HBA) path failover in the event of a controller failure.

In a single RAID controller configuration, the lower I/O board has drive channels but does not have host channels. Overall, the same number of loops are available, but with only half as many host channel ports. All six fibre channels in a SANnet II 200 FC array’s I/O controller module support 1-Gbit or 2-Gbit data transfer speeds.

1.1.1.1 SANnet II 200 FC Array Features

On the SANnet II 200 FC array, RAID controller channels 0, 1, 4, and 5 are normally designated host channels. Any host channel can be configured as a drive channel. In a dual-controller configuration, each host loop includes two ports per loop, one port on the top controller and one port on the bottom controller.

SANnet II 200 FC RAID controller channels 2 and 3 are dedicated drive channels that connect to expansion units. Each I/O board has two ports designated as disk drive loops. These ports connect to the internal dual-ported FC disk drives and are used to add expansion units to the configuration.

The two drive loop ports on the upper I/O board form FC loop 2 (channel 2) while the two drive ports on the lower I/O board form FC loop 3 (channel 3). FC loop 2 provides a data path from both RAID controllers to the A loop of the internal disk drives, while FC loop 3 provides a data path from both RAID controllers to the B loop of the internal disk drives.

Chapter 1 Product and Architecture Overview 1-3

1.1.1.2 SANnet II 200 SATA and SATA SE Array Features

On the SANnet II 200 SATA and SATA SE arrays, RAID controller channels 0 and 1 are dedicated host channels. Channels 4 and 5 are host channels by default but can be configured as drive channels. RAID controller channels 2 and 3 are dedicated drive channels that connect to expansion units.

Unlike the SANnet II 200 FC array, on the SANnet II 200 SATA RAID controller host channels 0 and 1 include four ports per loop (two ports on the upper controller, and two ports on the lower controller). Channels 0 and 1 support 1-Gbit or 2-Gbit data transfer rates.

SANnet II 200 SATA RAID controller channels 4 and 5 provide two ports per loop (one port on each controller). Channels 4 and 5 support only a 2-Gbit data transfer rate.

Each SANnet II 200 SATA RAID controller has two ports designated as disk drive loops. The drive ports support only a 2-Gbit data transfer rate. These ports connect to the internal SATA disk drives using internal FC-SATA routing technology. These drive ports are also used to add expansion units to the configuration.

Like the host channels, each drive channel of the top RAID controller shares a loop with the matching drive channel on the bottom RAID controller. For example, drive channel 2 of the top RAID controller shares the same loop as channel 2 of the bottom RAID controller.

1.1.2 Differences Between SANnet II 200 FC Arrays and SANnet II 200 SATA Arrays

SANnet II 200 FC arrays use Fibre Channel (FC) disk drives and are supported by Dot Hill in primary online applications as well as secondary and near-line applications. SANnet II 200 SATA arrays use serial ATA (SATA) disk drives and are supported by Dot Hill in either near-line applications such as backup and restore, or in secondary applications, such as static storage. SANnet II 200 SATA arrays can be used in multipath and multi-host configurations. They are not designed to be used in primary online applications.

SANnet II 200 SATA expansion units can be connected to SANnet II 200 FC arrays, either alone or in combination with SANnet II 200 FC expansion units. Up to five expansion units can be used in this configuration.

Before installing and configuring your array, review the key differences between the

FC, SATA, and SATA SE arrays in Table 1-1.

1-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Note – Although the products are very similar in appearance and setup, the

configurations have very important differences. While the FC array can be used for all applications, the SATA and SATA SE arrays cannot. Inappropriate use of the SATA arrays in applications for which the FC array was designed might result in loss of data and/or loss of data access.

Table 1- 1 Comparison of SANnet II 200 FC, SATA, and SATA SE Array Features

SANnet II 200 FC Array SANnet II 200 SATA Array SANnet II 200 SATA SE Array

Applications Best suited for

production applications where the superior features of FC technical characteristics and performance are required. This includes online applications such as:

• Database

• Decision support

• Data warehousing

• Electronic commerce

• Enterprise resource planning

• Messaging, file, and print

Disks Fibre Channel disks:

36, 73, or 146 GB at 10K RPM 36 or 73 GB at 15K RPM

Maximum FC Host Ports per I/O

4 (one SFP port each for

channels 0, 1, 4, and 5) Controller Module

Best suited for inexpensive secondary storage applications that are not mission critical where higher capacity drives are needed, and where lower performance and less than 7/24 availability is an option. This includes near-line applications such as:

• Information lifecycle management

• Content addressable storage

• Backup and restore

• Secondary SAN storage

• Near-line DAS storage

• Static reference data storage

SATA disks: 250 GB at 7200 RPM 400 GB at 7200 RPM

6 (two SFP ports each for channels 1 and 0; one SFP port each for channels 4 and

• Information lifecycle management

• Content addressable storage

• Backup and restore

• Secondary SAN storage

• Near-line DAS storage

• Static reference data storage

SATA disks: 250 GB at 7200 RPM 400 GB at 7200 RPM

6 (two SFP ports each for channels 1 and 0; one SFP port each for channels 4 and

Maximum Number of Expansion Units Connected to a RAID Array

15 15 0

Chapter 1 Product and Architecture Overview 1-5

Table 1- 1 Comparison of SANnet II 200 FC, SATA, and SATA SE Array Features (Continued)

SANnet II 200 FC Array SANnet II 200 SATA Array SANnet II 200 SATA SE Array

Maximum Number of Disks per Configuration

Maximum Number of Logical Drives

Direct hostattached JBOD Support

192 (1 RAID array + 15 expansion units)

32 logical drives 32 logical drives 32 logical drives

One JBOD per server Not supported Not supported

Caution – In FC and SATA configurations with large drive capacities, the size of the

192 (1 RAID array + 15 expansion units)

12 (1 RAID array)

logical drive might exceed the device capacity limitation of your operating system. Be sure to check the device capacity limitation of your operating system before creating the logical drive. If the logical drive size exceeds the capacity limitation, you must partition the logical drive.

Note – For information about the maximum usable storage capacity for the

SANnet II 200 FC, SATA, and SATA SE arrays, refer to the SANnet II 200 FC and SATA Array Best Practices Manual.

1.1.3 SANnet II 200 FC, SATA, and SATA SE Array Configurations

The FC, SATA, and SATA SE arrays can be used in the following configurations:

■ Single-controller configuration. A RAID array can be configured with a single

controller in a non-redundant configuration.

■ A RAID array with two controllers. A RAID array can be configured with two

controllers to provide full redundancy.

■ An expansion unit. An expansion unit consists of a chassis with disk drives and I/O

expansion modules. The expansion unit does not include an I/O controller module. The expansion unit connects to and is managed by a RAID array. The SANnet II 200 SATA Special Edition (SE) does not support expansion units.

■ A Just a Bunch of Disks (JBOD) array. The JBOD array connects to, and is

managed by, a host server. Only the SANnet II 200 FC JBOD is supported.

See Appendix B for detailed information about using SANnet II 200 FC JBOD arrays.

1-6 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Table 1-2 shows the configuration options for SANnet II 200 FC, SATA, and SATA SE arrays.

Table 1- 2 SANnet II 200 FC, SATA, and SATA SE Array Configuration Options

Internal RAID controllers 1 or 2

2-Gbit/sec Fibre Channel disks (SANnet II 200 FC array)

Up to 12 per array or per expansion unit, with a minimum of 4 plus 1 spare

1.5-Gbit/sec serial ATA disks (SANnet II 200 SATA array)

FC expansion units

Up to 8 for a SANnet II 200 FC array. Up to 5 for a SANnet II 200 SATA array

FC JBOD arrays

(SANnet II

200 FC array only)

Connection options • Serial port

•Ethernet

• Fibre Channel Small Form-Factor Pluggable (SFP)

Supported RAID levels 0, 1, 3, 5, 1+0, 3+0, and 5+0

Redundant field-replaceable units (FRUs)

• Power supply and fan modules

• I/O controller modules and I/O expansion modules

• I/O expansion modules

• Battery board module

• Disk drive modules

Configuration management and enclosure event reporting options

• In-band Fibre Channel ports

• Out-of-band 10/100BASE-T Ethernet port

• RS-232 connectivity

• Enclosure monitoring by SCSI Enclosure Services (SES)

1. 1-GHz drives are not supported.

2. A disk array with no controller. Each expansion unit has two Fibre Channel loops that can provide redundant data paths back to the RAID array.

3. A disk array with no controller that is connected directly to a host computer, with no RAID array in the loop. Only SANnet II 200 FC arrays support the JBOD configuration.

4. The host-based SANscape software provides a graphical user interface (GUI) and additional event-reporting capabilities.

A label on the bottom lip of an array chassis, underneath the front bezel, indicates whether the array is a JBOD array or a RAID array. For instance, “SANnet II 200 AC JBOD” refers to an alternating-current version of a SANnet II 200 JBOD array, “SANnet II 200 DC JBOD” refers to a direct-current version of a JBOD array, and “SANnet II 200 AC RAID” refers to an alternating-current version of a RAID array. Similarly, using a OBP command such as

probe-scsi-all provides similar

information, using an “A” designator for RAID arrays and a “D” designator for disks

Chapter 1 Product and Architecture Overview 1-7

in a JBOD array. For example, “SANnet II 200 D1000” identifies a JBOD array with SES firmware version 1000 and “SANnet II 200F A1000” identifies a SANnet II 200 FC RAID array with firmware version 1000.

For a list of supported racks and cabinets, refer to the SANnet II Family Rack Installation Guide for 2U Arrays.

Reliability, availability, and serviceability (RAS) are supported by:

■ Redundant components

■ Notification of failed components

■ Components that are replaceable while the unit is online

For information about specifications and agency approvals, see “SANnet II 200 FC, SATA, and SATA SE Array Specifications” on page A-1.

1.2 Field-Replaceable Units

This section describes the field replaceable units (FRUs) contained in the SANnet II 200 FC, SATA, and SATA SE arrays.

1.2.1 RAID I/O Controller Modules

A dual-controller configuration offers increased reliability and availability because it eliminates a single point of failure, the controller. In a dual-controller configuration, if the primary controller fails, the array automatically fails over to the second controller without an interruption of data flow.

The FC, SATA, and SATA SE array I/O controller modules are hot-serviceable. Hot- serviceable means that the module can be replaced while the array and hosts are powered on, but the connected hosts must be inactive.

■ SANnet II 200 FC array RAID controller modules provide six Fibre Channel ports.

■ SANnet II 200 SATA array I/O controller modules provide eight Fibre Channel

ports.

■ SANnet II 200 SATA SE array I/O controller modules provide six Fibre Channel

ports.

Single- and dual-controller models are available, with the dual-controller version supporting active/passive and active/active configurations. Each RAID controller is configured with 1 Gbyte of cache.

In the unlikely event of an I/O controller module failure, the redundant RAID controller immediately begins servicing all I/O requests. The failure does not affect application programs.

Each RAID I/O controller module can support up to 1 Gbyte of Synchronous Dynamic Random Access Memory (SDRAM) with Error Control Check (ECC) memory. In addition, each controller supports 64 Mbyte of on-board memory. Two Application-

1-8 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Specific Integrated Circuit (ASIC) controller chips handle the interconnection between the controller bus, DRAM memory, and Peripheral Component Interconnect (PCI) internal buses. They also handle the interface between the on-board 2-Mbyte flash memory, 32-Kbyte nonvolatile random access memory (NVRAM), RS-232 port chip, and 10/100 BASE-T Ethernet chip.

The RAID I/O controller module is a multifunction board. I/O controller modules include Small Form-Factor Pluggable (SFP) ports, SCSI Enclosure Services (SES) logic, and the RAID controller. The SES logic monitors various temperature thresholds, fan speed from each fan, voltage status from each power supply, and the FRU ID.

Each RAID I/O controller module incorporates SES direct-attached Fibre Channel capability to monitor and maintain enclosure environmental information. The SES controller chip monitors all internal +12 and +5 voltages, various temperature sensors located throughout the chassis, and each fan. The SES also controls the front-panel and back-panel LEDs and the audible alarm. Both the RAID chassis and the expansion chassis support dual SES failover capabilities for fully redundant event monitoring.

1.2.2 I/O Expansion Modules

The hot-serviceable I/O expansion modules provide four (SANnet II 200 FC array) or eight (SANnet II 200 SATA array), or six (SANnet II 200 SATA SE array) SFP ports but do not have battery modules or controllers. I/O expansion modules are used with I/O controller modules in non-redundant FC arrays, SATA arrays, and SATA SE arrays and in expansion units and JBODs.

You can connect SANnet II 200 SATA expansion units to SANnet II 200 FC arrays. However, certain restrictions and limitations apply to mixed Fibre Channel and SATA environments.

1.2.3 Disk Drives

Each disk drive is mounted in its own sled assembly. Each sled assembly has electromagnetic interference (EMI) shielding, an insertion and locking mechanism, and a compression spring for maximum shock and vibration protection.

Each disk drive is slot independent, meaning that once a logical drive has been initialized, the system can be shut down and the drives can be removed and replaced in any order. In addition, disk drives are field upgradeable to larger drives without interruption of service to user applications. The drive firmware is also field upgradeable, but the firmware upgrade procedure requires interruption of service.

Chapter 1 Product and Architecture Overview 1-9

Caution – You can mix disk drive capacity in the same chassis, but not spindle speed

(RPM). For instance, you can use 36-Gbyte and 73-Gbyte drives with no performance problems if both are 10K RPM drives. Violating this configuration guideline leads to poor performance.

In the event of a single disk drive failure, with the exception of RAID 0, the system continues to service all I/O requests. Either mirrored data or parity data is used to rebuild data from the failed drive to a spare drive, assuming one is assigned. If a spare is not assigned, you must manually rebuild the array.

In the unlikely event that multiple drive failures occur within the same logical drive, data that has not been replicated or backed up might be lost. This is an inherent limitation of all RAID subsystems and could affect application programs.

An air management sled FRU is available for use when you remove a disk drive and do not replace it. Insert an air management sled into the empty slot to maintain optimum airflow through the chassis.

1.2.3.1 SANnet II 200 FC Array Disk Drives

The drives can be ordered in 36-Gbyte, 73-Gbyte, and 146-Gbyte sizes. 36-Gbyte drives have a rotation speed of 15,000 RPM, 146-Gbyte drives have a rotation speed of 10,000 RPM, and 73-Gbyte drives are available with rotation speeds of 10,000 RPM and 15,000 RPM.

1.2.3.2 SANnet II 200 SATA and SATA SE Array Disk Drives

The disk drives incorporate Serial ATA (SATA) technology. They are optimized for capacity, but have performance levels approaching Fibre Channel performance levels. The drives can be ordered in 250-Gbyte and 400-Gbyte sizes and have a rotation speed of 7200 RPM.

1.2.4 Battery Module

The battery module is designed to provide power to system cache for 72 hours in the event of a power failure. When power is reapplied, the cache is purged to disk. The battery module is hot-swappable. Hot-swappable means that a live upgrade can be performed. The FRU can be removed and replaced while the RAID array is powered on and operational. The battery module is mounted on the I/O board with guide rails and a transition board. It also contains the EIA-232 and DB9 serial interface (COM) ports.

1-10 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

1.2.5 Power and Fan Modules

Note – The SATA arrays can only be ordered in an AC configuration. However, DC

power supplies can be ordered in an x-option kit, and the SATA arrays can be reconfigured using the DC power supplies. For details, refer to the SANnet II Family FRU Installation Guide.

Each array contains two redundant power and fan modules. Each module contains a 420-watt power supply and two radial 52-cubic-feet-per-minute (CFM) fans. Power module autoranging capabilities range from 90 volts alternating current (VAC) to 264 VAC for AC power supplies, and from –36 volts direct current (VDC) to –72 VDC for DC power supplies.

A single power and fan module can sustain an array.

1.3 Interoperability

The array is designed for heterogeneous operation and supports multiple host operating systems. Refer to the SANnet II 200 FC, SATA, and SATA SE Array Release Notes to see the current list of supported hosts, operating systems, and application software.

The array does not require any host-based software for configuration, management, and monitoring, which can be handled through the built-in firmware application. The console window can be accessed via the DB9 communications (COM) port using the Solaris Ethernet port using the available and shipped with the array. See “Additional Software Tools” on page 1-15 for more information.

tip command or equivalent means for other operating systems, or with the

telnet command. Management and monitoring software is

1.4 Fibre Channel Technology Overview

As a device protocol capable of high data transfer rates, Fibre Channel simplifies data bus sharing and supports not only greater speed than SCSI, but also more devices on the same bus. Fibre Channel can be used over both copper wire and optical cable. It can be used for concurrent communications among multiple workstations, servers, storage systems, and other peripherals using SCSI and IP protocols. When a Fibre Channel hub or fabric switch is employed, it provides flexible topologies for interconnections.

Chapter 1 Product and Architecture Overview 1-11

1.4.1 FC Protocols

Two common protocols are used to connect Fibre Channel (FC) nodes together:

■ Point-to-point—The point-to-point protocol is straightforward, doing little more

than establishing a permanent communication link between two ports.

■ Arbitrated loop—The arbitrated loop protocol creates a simple network featuring

distributed (arbitrated) management between two or more ports, using a circular (loop) data path. Arbitrated loops can support more nodes than point-to-point connections can.

The FC, SATA, and SATA SE arrays support point-to-point and arbitrated loop protocols. Select the protocol you prefer by setting the desired Fibre Channel Connection Option in the Configuration parameters of the firmware application. For more information, see “Summary of Array Configuration” on page 5-1.

1.4.2 FC Topologies

The presence or lack of switches establishes the topology of an FC environment. In a direct attached storage (DAS) topology, servers connect directly to arrays without switches. In a storage area network (SAN) topology, servers and arrays connect to an FC network created and managed by switches.

Refer to the SANnet II 200 FC and SATA Array Best Practices Manual to see information about optimal configurations for site requirements.

1.4.3 Fibre Hubs and Switches

A storage network built on a Fibre Channel architecture might employ several of the following components: Fibre Channel host adapters, hubs, fabric switches, and fibreto-SCSI bridges.

■ Fibre hubs

An arbitrated loop hub is a wiring concentrator. “Arbitrated” means that all nodes communicating over this fibre loop share a 100-megabits-per-second (Mbps) segment. Whenever more devices are added to a single segment, the bandwidth available to each node is further reduced.

A loop configuration allows different devices in the loop to be configured in a token ring style. With a fibre hub, a fibre loop can be rearranged in a star-like configuration because the hub itself contains port bypass circuitry that forms an internal loop inside. Bypass circuits can automatically reconfigure the loop once a device is removed or added without disrupting the physical connection to other devices.

■ Fabric switches.

1-12 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

A fabric switch functions as a routing engine, which actively directs data transfers from source to destination and arbitrates every connection. Bandwidth per node via a fabric switch remains constant when more nodes are added, and a node on a switch port uses a data path with speed up to 100 Mbps to send or receive data.

1.4.4 Data Availability

Data availability is one of the major requirements for today’s mission-critical applications. Highest availability can be accomplished with the following functionality:

■ Hot-plug capabilities

With proper hardware and software configuration in dual-controller mode, a failed controller can be replaced online while the existing controller is actively serving I/O.

■ Dual-loop configurations

Dual loop provides path redundancy and greater throughput.

■ Controller communications over Fibre Channel

■ This option is selectable either through dedicated loops or all drive loops. It allows

a more flexible configuration of redundant controllers.

1.4.5 Scalability

The Fibre Channel architecture brings scalability and easier upgrades to storage. Storage expansion can be as easy as cascading another expansion unit to a configured RAID array without powering down the running system. The maximum number of expansion units supported by a single SANnet II 200 Fibre Channel or SATA array is:

■ Up to eight SANnet II 200 FC expansion units connected to a SANnet II 200 FC

array.

■ Up to five SANnet II 200 SATA expansion units connected to a SANnet II 200

SATA array.

■ Up to five SANnet II 200 FC expansion units and SANnet II 200 SATA expansion

units, in any combination, can be connected to a SANnet II 200 FC RAID array.

Note – The SANnet II 200 SATA SE array does not support expansion units.

Up to 125 devices can be configured in a single FC loop. By default, the array provides two drive loops and four host loops, and operates in Fibre Channel-Arbitrated Loop (FC-AL) and fabric topologies.

Chapter 1 Product and Architecture Overview 1-13

1.5 Fibre Channel Architecture

Each RAID array has six Fibre Channels with the following defaults:

■ Channels 0, 1, 4, and 5 are host channels connected to servers. Any SANnet II 200

FC array host channels can be reassigned as drive channels to connect to expansion units. SANnet II 200 SATA array channels 3 and 4 can also be reassigned as drive channels.

■ Channels 2 and 3 are dedicated drive channels that connect the internal 12-disk

drives in the RAID chassis, and can also be used to add expansion units to the configuration.

Note – SANnet II 200 SATA SE devices do not support expansion units. Use the

SANnet II 200 SATA device if your array requires expansion units.

■ FC-AL is the default mode. Point-to-point is also available.

The SANnet II 200 FC expansion unit has a total of four FC-AL ports. The SANnet II 200 SATA expansion unit has a total of eight FC-AL ports. The SANnet II 200 SATA SE has a total of six FC-AL ports.

Note – Throughout this manual, Fibre Channel-Arbitrated Loops are referred to

simply as loops.

1.5.1 Redundant Configuration Considerations

This section provides information about setting up redundant configurations for increased reliability. For more detailed information about configuration requirements, refer to the SANnet II 200 FC and SATA Array Best Practices Manual.

1.5.1.1 Host Bus Adapters

Fibre Channel is widely applied to storage configurations with topologies that aim to avoid loss of data due to component failure. As a rule, the connections between source and target should be configured in redundant pairs.

The recommended host-side connection consists of two or more host bus adapters (HBAs). Each HBA is used to configure a Fibre Channel loop between the host computer and the array.

1-14 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

1.5.1.2 Active-to-Active Redundant Controller

In active-to-active redundant controller mode, the primary loop serves the I/O traffic directed to the primary controller, and its pair loop serves the I/O traffic to the secondary controller. The host-side management software directs I/O traffic to the pair loop if one of the redundant loops fails.

Since each fibre interface supports only a single loop ID, two HBAs are necessary for active-to-active redundant controller operation. Using two HBAs in each server ensures continued operation even when one data path fails.

In active-to-active mode, the connection to each host adapter should be considered a data path connecting the host to either the primary or the secondary controller. One adapter should be configured to serve the primary controller and the other adapter to serve the secondary controller. Each target ID on the host channels should be assigned either a primary ID or a secondary ID. If one controller fails, the remaining controller can inherit the ID from its counterpart and activate the standby channel to serve host I/O.

1.5.1.3 Host Redundant Paths

The controller passively supports redundant fibre loops on the host side, provided that the host has implemented software support for this feature.

In the unlikely event of controller failure, the standby channels on the remaining controller become an I/O route serving the host I/O originally directed to the failed channel on its pair of controllers. Application failover software should be running on the host computer to control the transfer of I/O from one HBA to another in case either data path fails.

1.6 Additional Software Tools

The following additional software tools are available:

■ SANscape, a management and monitoring program

■ SANscape Alert, a monitoring utility

■ SANscape CLI, a command-line utility to monitor and manage the array.

Refer to the SANscape Software Installation Guide these tools.

For additional information, refer to the release notes in the SANnet II 200 array hardware section at the following web site:

http://www.dothill.com/manuals.

for information about installing

Chapter 1 Product and Architecture Overview 1-15

1-16 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

CHAPTER

Site Planning

This chapter outlines the site planning requirements and basic safety requirements for the installation and use of the FC arrays, SATA arrays, and SATA Special Edition (SE) arrays. Complete a preinstallation worksheet and prepare the site for installation according to the worksheet details and the specified site planning requirements.

Review the details of this chapter before installing an array. Topics covered in this chapter are:

■ “Customer Obligations” on page 2-1

■ “Safety Precautions” on page 2-2

■ “Environmental Requirements” on page 2-3

■ “Electrical and Power Specifications” on page 2-3

■ “Physical Specifications” on page 2-4

■ “Layout Map” on page 2-4

■ “Console and Other Requirements” on page 2-5

■ “Preinstallation Worksheets” on page 2-6

Note – The SANnet II 200 FC, SATA, and SATA SE Array Release Notes list the

supported operating systems, host platforms, and software.

2.1 Customer Obligations

The customer is obliged to inform Dot Hill, Inc. of any and all ordinances and regulations that would affect installation.

Caution – When selecting an installation site for the FC, SATA, or the SATA SE

arrays, choose a location that avoids excessive heat, direct sunlight, dust, or chemical exposure. Such exposure greatly reduces the product’s longevity and might void your warranty.

2-1

The customer is responsible for meeting all government codes and regulations concerning facilities. The customer is also responsible for compliance with the following requirements:

■ Meeting all local, national, and international codes covered in Appendix A. The

subjects covered include fire and safety, building, and electrical codes.

■ Documenting and informing Dot Hill, Inc. of any deviations from Appendix A.

2.2 Safety Precautions

For your protection, observe the following safety precautions when setting up your equipment:

■ Follow all safety precautions and requirements specified in the SANnet II Family

Safety, Regulatory, and Compliance Manual.

■ A fully loaded array weighs over 59 pounds (27 kilograms). To avoid injury, use

two people to lift the array.

■ Follow all cautions and instructions marked on the equipment.

■ Ensure that the voltage and frequency of your power source match the voltage and

frequency inscribed on the equipment’s electrical rating label.

■ Never push objects of any kind through openings in the equipment. Dangerous

voltages might be present. Conductive foreign objects could produce a short circuit that could cause fire, electric shock, or damage to your equipment.

■ Dot Hill products are designed to work with single-phase power systems having a

grounded neutral conductor. To reduce the risk of electric shock, do not plug Dot Hill products into any other type of power system. Contact your facilities manager or a qualified electrician if you are not sure what type of power is supplied to your building.

■ Your Dot Hill product is shipped with a grounding-type (three-wire) power cord. To

reduce the risk of electric shock, always plug the cord into a grounded power outlet.

■ Do not use household extension cords with your Dot Hill product. Not all power

cords have the same current ratings. Household extension cords do not have overload protection and are not meant for use with computer systems.

■ Do not block or cover the openings of your Dot Hill product. Never place a Dot Hill

product near a radiator or heat register. Failure to follow these guidelines can cause overheating and affect the reliability of your Dot Hill product.

2-2 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

2.3 Environmental Requirements

Table 2- 1 Environmental Specifications

Operating Nonoperating

Altitude To 9000 feet (3000 meters) To 36,000 feet (12,000 meters)

Humidity 10% to 90% RH at 80° F

(27° C) max wet bulb (noncondensing)

Temperature

Standalone Rack

41° F (5° C) to 104° F (40° C) 41° F (5° C) to 95° F (35° C)

93% RH, 100° F (38° C) max wet bulb temperature (noncondensing)

–40° F (–40° C) to +149° F (+65° C) –40° F (–40° C) to +149° F (+65° C)

2.3.1 Electromagnetic Compatibility

The following is required for all installations:

■ All AC mains and supply conductors to power distribution boxes for both the rack-

mounted array and the desktop array must be enclosed in a metal conduit or raceway when specified by local, national, or other applicable government codes and regulations.

■ The supply conductors and power distribution boxes (or equivalent metal enclosure)

must be grounded at both ends.

■ The supplied arrays require voltages within minimum fluctuation. The facilities

voltage supplied by the customer must maintain a voltage with not more than (+/–) 5 percent fluctuation. The customer facilities must provide suitable surge protection.

2.4 Electrical and Power Specifications

The FC, SATA, and SATA SE arrays require two independent power sources. Each array has two power supply and two fan modules for redundancy.

Each AC array requires two 115 VAC/15A or two 240 VAC service outlets. All AC power supplies are autoranging and are automatically configured to a range of 90–264 VAC and 47–63 Hz. There is no need to make special adjustments.

Each DC array requires two –48 VDC service outlets and has an input voltage range of –36 VDC to –72 VDC.

Note – To ensure power redundancy, connect the two array power modules to two

separate circuits (for example, one commercial circuit and one UPS).

Chapter 2 Site Planning 2-3

Table 2- 2 Power Specifications

AC power Voltage and frequency 90 to 264 VAC, 47 to 63 Hz

Input current 5A max

Power supply output voltage +5 VDC and +12 VDC

DC power –48 VDC (

2.5 Physical Specifications

Use the physical specifications in Table 2-3 to plan the location of your array.

Table 2- 3 Physical Specifications

Category Description

Dimensions 2U 3.45 inches (8.76 cm.) height

21 inches (53.34 cm.) chassis depth

17.5 inches (44.6 cm.) width 19 inches (48.26 cm.) width with ears

Installation clearances

Cooling clearances 6 inches (15 cm) is required front and back. No cooling

For FRU component removal and replacement, 15 inches (37 cm) is required front and back.

clearance is required on the sides or the top and bottom of the array.

2.6 Layout Map

–36 VDC to –72 VDC)

It is helpful to create a sketch or layout map to indicate the exact location of the array as well as the location of the hosts, console, and Ethernet connections that will be connected to it.

As you lay out the components, consider the cable lengths that will be used.

2.6.1 Rack Placement

Follow these guidelines when preparing a rackmount placement for your system:

■ Ensure that the floor surface is level.

■ Leave enough space in front of the rack to access components for servicing.

■ Leave enough space in back of the rack to access components for servicing.

■ Keep power and interface cables clear of foot traffic. Route cables inside walls,

under the floor, through the ceiling, or in protective channels or raceways.

2-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

■ Route interface cables away from motors and other sources of magnetic or radio

frequency interference.

■ Stay within the cable length limitations.

■ Provide two separate power sources for the array. These power sources must be

independent of each other, and each must be controlled by a separate circuit breaker at the power distribution point.

2.6.2 Tabletop Placement

SANnet II 200 FC, SATA, and SATA SE arrays can be positioned on a desk or a table. Follow these guidelines when preparing a tabletop placement for your system:

■ Choose a desk or a table that can support 60 pounds (27 kg) for each fully

configured array you plan to place on it.

■ Do not place the arrays on the edge of the table. Set the array so that at least 50

percent of the array is inside the table or desk leg support area. Failure to do this might cause the table to tip over.

■ Leave enough space in front and in back of the array to access components for

servicing. To remove the components requires a clearance of 15 inches (37 cm) in front and in back of the array.

■ Provide a minimum space of 6 inches (15 cm) in front and in back of the array for

adequate airflow.

■ Keep power and interface cables clear of foot traffic. Route cables inside walls,

under the floor, through the ceiling, or in protective channels or raceways.

■ Route interface cables away from motors and other sources of magnetic or radio

frequency interference.

■ Stay within the cable length limitations.

■ Ensure that the operating system for the array does not exceed the specifications.

■ Use two people to lift the array to avoid injury. The array can weigh over 60 pounds

(27 kg).

■ Do not place the array in a vertical position. Place the array horizontally.

■ If you are installing more than one array, you can stack up to five arrays on top of

each other. Do not stack more than five arrays together.

■ Provide two separate power sources for the array. These power sources must be

independent of each other, and each must be controlled by a separate circuit breaker at the power distribution point.

2.7 Console and Other Requirements

A console with at least one serial port connection is necessary for installation and configuration of your FC, SATA, or SATA SE array. Once you have configured your array with an IP address, an Ethernet port can also be useful for configuring the array.

Chapter 2 Site Planning 2-5

Note – SANnet II family arrays require at least CAT-5 Ethernet cable.

See the following preinstallation worksheet for additional preparation details.

2.8 Preinstallation Worksheets

Before ordering an FC, SATA, or SATA SE array, complete the preinstallation worksheets on the following pages and then prepare the site for installation according to the site planning requirements.

Note – If you are connecting to several hosts or fabric switches, make as many copies

of Table 2-5 as you need and label them appropriately.

■ You are responsible for ensuring that the site consistently conforms to all stipulated

standards and that necessary peripherals are made available to the engineer during installation.

■ Review the details of your specific survey before installing your array.

■ If necessary, attach or sketch a network diagram to the survey.

2-6 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Table 2- 4 Site Preparation Worksheet

Rackmounting Customers must ensure that the appropriate service outlets are available for

installation. Requirements vary.

• Will the array be rackmounted? Yes / No

• Is the rack supplied by Dot Hill, Inc.? Yes / No

• If yes, include Dot Hill model number: ____

• If not, make/model: _____________________ /_____________________

• Does the rack mount have:

• Front and back? If so, depth? ______

• Center/Telco? ______

• What cable lengths are required? _________________

• Are there any power strips or power sequencers in the rack? Yes / No

• Are they supplied by Dot Hill, Inc.? Yes / No

• If yes, part number: ___________

• If not, quantity of plugs/outlets required: __________ / __________

IP address Array IP address: ______.______.______.______

Array network mask: ______.______.______.______

Cabling Fiber-optic cable lengths to connect to hosts: _______________

Chapter 2 Site Planning 2-7

Table 2- 5 Host and Fabric Switch Connectivity Summarized

Host or Fabric Switch Connectivity - Host or Fabric Switch #1

Host or fabric switch name: _____________________________________

Host or fabric switch make/model: ________________________________

HBA connector types: _____________________________

Cable distance from the array to the hosts: ___________

Operating system: ________________________________

Patches installed: ________________________________

IP addresses:

• Network ____________________

• Host or switch _______________

Host or Fabric Switch Connectivity - Host or Fabric Switch #2

Host or fabric switch name: _____________________________________

Host or fabric switch make/model: ________________________________

HBA connector types: _____________________________

Cable distance from the array to the hosts: ___________

Operating system: ________________________________

Patches installed: ________________________________

IP addresses:

• Network ____________________

• Host or switch _______________

2-8 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

CHAPTER

Unpacking Your Array

This chapter describes the procedure for unpacking your FC, SATA, or SATA SE array package. The following topics are covered in this chapter:

■ “Opening Your Package” on page 3-1

■ “Checking the Package Contents” on page 3-2

■ “Field-Replaceable Units” on page 3-3

■ “Customer-Provided Cables” on page 3-3

■ “Mounting Your Array in a Rack or Cabinet” on page 3-3

3.1 Opening Your Package

Follow these guidelines for unpacking the equipment.

Caution – To avoid personal injury or damage to the equipment during installation,

always use two people to remove the unit from its container. This unit weighs approximately 60 pounds (27 kg).

1. Select a suitable area for unpacking.

2. Store all packing material and boxes for possible equipment returns.

3. Check the contents sheet in your product package. The contents sheet summarizes the standard contents for your product. See “Checking

the Package Contents” on page 3-2 for more information.

4. Compare the packing slip and the list of parts with the items you received. If the list of parts on your packing slip does not match the items you received, or if any

items appear damaged, immediately notify your carrier agent and the supplier who prepared your shipment.

5. Carefully examine the cables provided in the package. If any cable appears to be damaged, contact the technical service department for an

immediate replacement.

3-1

6. Check the list of “Customer-Provided Cables” on page 3-3. These are required to complete your installation.

Note – You must purchase or provide fiber-optic cables for connecting FC, SATA, and

SATA SE arrays to host servers.

3.2 Checking the Package Contents

Inspect the array package for standard items as well as purchased options before you begin installation. If any parts are missing or damaged, contact your sales representative immediately.

3.2.1 Standard Array Packages

Table 3- 1 Contents of SANnet II 200 Array Packages

Quantity Item

1 One or more of the following arrays:

• SANnet II 200 FC array, SANnet II 200 SATA array, or SANnet II 200 SATA SE array with single controller

• SANnet II 200 FC array, SANnet II 200 SATA array, or SANnet II 200 SATA SE array with dual controllers

• SANnet II 200 FC JBOD, SANnet II 200 FC expansion unit, or SANnet II 200 SATA expansion unit

1 • Contents Sheet for your array

• Quick installation guide for your array

• To download and print the latest release notes, go to the SANnet II 200 FC, SATA, or SATA SE array section and to the software section at the following location:

http://www.dothill.com/manuals

1 CD for user documentation

1 Serial null modem cable

1 or 2 25-foot (7.5 m) shielded CAT-5 Ethernet cable (one per controller)

1 Cable adapter, DB9 to DB25

2 DC power cables if you ordered a DC-powered array

2 AC cord locks in a plastic bag if you ordered an AC-powered array

1 AC cable country kit if the array is AC powered

2 Front bezel keys in a plastic bag, to secure the front bezel onto the chassis

Various Purchased options. These options are ordered at the time of purchase and are integrated

into or added to the unit prior to delivery.

3-2 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

3.3 Field-Replaceable Units

Check that you received all field-replaceable units (FRUs) ordered with your array. For additional FRUs, consult your sales representative. For instructions on how to install or replace FRUs, review the following manuals located on the product web site or on your documentation CD:

■ SANnet II Family Rack Installation Guide for 2U Arrays

■ SANnet II Family FRU Installation Guide

All FRUs are hot-swappable except the I/O controller and I/O expansion modules, which are hot-serviceable. Hot-swappable means that a live upgrade can be performed—the FRU can be removed and replaced while the RAID array is powered on and operational. Hot-serviceable means that the module can be replaced while the array and hosts are powered on but the connected hosts must be inactive.

Caution – You can mix capacity in the same chassis, but not spindle speed revolutions

per minute (RPM) on the same SCSI bus. For instance, you can use 36-Gbyte and 73Gbyte drives with no performance problems if both are 10K RPM drives. Violating this configuration guideline leads to poor performance.

For a list of the FRU part numbers, refer to the SANnet II Family FRU Installation Guide.

3.4 Customer-Provided Cables

Customers must provide a minimum of one fiber-optic cable per host to connect a host to a RAID array. Two fiber-optic cables are required for a redundant path configuration.

To obtain qualified cables, consult your Dot Hill sales representative.

3.5 Mounting Your Array in a Rack or Cabinet

Refer to SANnet II Family Rack Installation Guide for 2U Arrays for instructions on how to install and prepare a rack or cabinet for mounting your array.

Chapter 3 Unpacking Your Array 3-3

3-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

CHAPTER

Connecting Your Array

This chapter describes procedures for cabling a FC, SATA, or SATA SE array and for connecting an array to power and to network devices.

The following topics are covered in this chapter:

■ “Converting Your Front Bezel Locks So the Keys Cannot Be Removed” on

page 4-2

■ “RAID Array Connections” on page 4-4

■ “SANnet II 200 FC Array Connections” on page 4-4

■ “SANnet II 200 SATA Array Connections” on page 4-5

■ “SANnet II 200 SATA SE Array Connections” on page 4-7

■ “Connecting the Chassis to AC Power Outlets” on page 4-7

■ “Connecting the Chassis to DC Power Outlets” on page 4-9

■ “Cabling to Expansion Units” on page 4-11

■ “Setting Loop IDs on Expansion Units” on page 4-13

■ “Powering Up and Checking LEDs” on page 4-16

■ “Reviewing Channels, Ports, and SFPs” on page 4-16

■ “Drive Port Connectivity in a Dual-Controller Array” on page 4-17

■ “Host Port Connectivity in a Dual-Controller Array” on page 4-19

■ “Default SFP Placement” on page 4-21

■ “Changing Your SFP Configuration” on page 4-24

■ “Establishing Communications With An Array” on page 4-25

■ “Configuring a Host COM Port to Connect to a RAID Array” on page 4-26

■ “Manually Setting a Static IP Address” on page 4-27

■ “Setting Up Out-of-Band Management Over Ethernet” on page 4-28

■ “Scaling a SANnet II 200 Fibre Channel Array Into a High-Capacity

Configuration” on page 4-29

■ “Adding an Expansion Unit to an Existing RAID Array” on page 4-30

■ “Connecting Ports to Hosts” on page 4-31

■ “Power-On Sequence” on page 4-32

■ “Powering Off the Array” on page 4-33

4-1

Before you connect the array to the network, position the array in the rack, cabinet, or other location where it will be used.

Caution – When positioning the array, do not block the air vents at the front or back

of the unit. Follow all safety precautions specified in the SANnet II Family Safety, Regulatory, and Compliance Manual.

Caution – When you power off an array, wait five seconds before you power it back

on. If you power the array off and on too quickly, unexpected results can occur. See “Powering Off the Array” on page 4-33.

4.1 Converting Your Front Bezel Locks So the Keys Cannot Be Removed

The bezel on your array has two locks whose keys can be removed when the locks are in either the locked or open position. It is possible to reconfigure the locks so that the keys cannot be removed.

Bezel locks

Figure 4-1 Front Bezel and Front Bezel Locks of an Array

To change the locks so the keys cannot be removed, perform the following steps.

1. Remove the bezel by gently pivoting the swing arms out of their ear sockets. See “Removing the Front Bezel and Ear Caps” on page 7-9 for step-by-step

instructions on how to remove the bezel.

2. Make sure the key is in the locked position, with the pawl extending horizontally past the edge of the bezel.

3. Hold the key in place and use a 3/8-inch (12-mm) nut driver to remove the locking nut that holds the pawl in place, as shown in the first panel of Figure 4-2.

Caution – Be sure to hold the key in place. Otherwise there is a risk of breaking the

small tab on the lock that serves as a stop.

4-2 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

4. Lift the pawl off the threaded part of the lock body, as shown in the second panel of Figure 4-2.

Figure 4-2 Sequence of Steps to Change Front Bezel Locks So Keys Cannot Be Removed

5. Set the pawl aside, face up, so that you can remember its orientation when you replace it.

6. Use the key to turn the lock 180 degrees, as shown in the third panel of Figure 4-2.

7. Replace the pawl in the same orientation as before, as shown in the fourth panel of Figure 4-2.

8. Hold the key in place and use the nut driver to refasten the locking nut that holds the pawl in place, as shown in the fifth panel of Figure 4-2. Be careful not to cross-thread the nut.

Caution – Be sure to hold the key in place. Otherwise there is a risk of breaking the

small tab on the lock that serves as a stop.

Chapter 4 Connecting Your Array 4-3

9. Replace the bezel.

Note – To convert your bezel locks so that the keys can be removed, repeat this

procedure.

4.2 RAID Array Connections

Management is in-band through fibre host connections and out-of-band through the serial port and Ethernet port on the back of each controller.

4.2.1 SANnet II 200 FC Array Connections

Figure 4-3 identifies the hardware connections on the back of a dual-controller SANnet II 200 FC array.

4-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

FC devices

FC expansion units/FC arrays

Servers and consoles

Management console

application/data servers and consoles

FC device connections

Figure 4-3 Hardware Connections on the Back of a Dual-Controller SANnet II 200 FC Array

4.2.2 SANnet II 200 SATA Array Connections

Figure 4-4 identifies the hardware connections on the back of a dual-controller SANnet II 200 SATA array.

Chapter 4 Connecting Your Array 4-5

FC devices

FC expansion units/FC arrays

Servers and consoles

Management console

application/data servers and consoles

FC device connections

Figure 4-4 Hardware Connections on the Back of a Dual-Controller SANnet II 200

SATA Array

4-6 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

4.2.3 SANnet II 200 SATA SE Array Connections

Figure 4-5 identifies the hardware connections on the back of a dual-controller SANnet II 200 SATA SE array.

Servers and consoles

Management console

application/data servers and consoles

Figure 4-5 Hardware Connections on the Back of a Dual-Controller SANnet II 200 SATA SE Array

FC device connections

4.3 Connecting the Chassis to AC Power Outlets

When you connect the AC power cords, install the two provided cord locks at the same time. The AC cord locks are used to securely fasten the AC cable connectors.

Caution – If the array is connected to AC power sources not within the designated

90–135 or 180–264 VAC range, the unit might be damaged.

Note – To ensure power redundancy, be sure to connect the two power supply modules

to two separate circuits (for example, one commercial circuit and one UPS).

To connect the AC power cords, perform the following procedure.

Chapter 4 Connecting Your Array 4-7

1. Use a Phillips screwdriver to remove the screw and cylindrical standoff from one of the two provided cord locks.

Set them aside for reassembly later.

2. Slide the cord lock over the AC power connector.

3. Hold the cylindrical standoff between the two screw holes on the flanges of the cord lock.

4. Insert the screw into the first screw hole, through the standoff, and then into the threaded screw hole on the other flange.

5. Tighten the screw with a screwdriver

standoff.

until the flanges bottom out on the cylindrical

6. Push the power cord into the power supply receptacle until it is firmly seated.

7. Push the green ejector handle forward until it is seated against the power supply.

8. Turn the thumbscrew of the green ejector handle clockwise until it is finger-tight to secure the handle and the cord lock.

Note – To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and

then loosen the thumbscrew counterclockwise a quarter turn.

9. Repeat Step 1 through Step 8 for the second cord lock and second power cable.

4-8 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Figure 4-6 Installing a Cord Lock

4.4 Connecting the Chassis to DC Power Outlets

Note – The SANnet II 200 SATA array can only be ordered in an AC configuration.

However, DC power supplies can be ordered in an x-option kit, and a SANnet II 200 SATA array can be reconfigured using the DC power supplies. Refer to the SANnet II Family FRU Installation Guide for a procedure for removing and replacing power supplies.

Two DC power cords are packaged with each DC array. To connect the DC power cords, perform the following procedure.

1. Check the DC cable part number and wire labels carefully before connecting the cable to the source.

Chapter 4 Connecting Your Array 4-9

Table 4- 1 DC Cable Wiring for Cable 35-00000148

Pin Number Voltage Color

A3 Return Red

A2 GND (Chassis Ground) Green/Yellow

A1 –48 VDC Black

Table 4- 2 DC Cable Wiring for Cable 35-00000156

Pin Number Voltage Color

A3 L+ Red

A2 GND (Chassis Ground) Green/Yellow

A1 L– White

2. Connect a DC power cable to the first power supply and to a power outlet.

Note – Use only the DC power cables provided with the array.

Caution – If the array is connected to DC power sources not within the designated –

48V DC (–36 VDC to –72 VDC) range, the unit might be damaged.

Note – To ensure power redundancy, be sure to connect the two power supply modules

to two separate circuits (for example, one commercial circuit and one UPS).

Note – To extend the length of the DC power cable as needed, strip the last 1/4 inch

of the cable, insert the stripped end into a provided Panduit tube, and crimp the tube.

3. Tighten the cable-locking screws to attach the cable securely to the power supply power outlet.

4. Connect the second power cable to the second power supply and to a second power outlet. Tighten the cable-locking screws.

If one power supply fails, the second power supply automatically takes the full load.

4-10 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

4.5 Cabling to Expansion Units

The instructions in this section apply to the SANnet II 200 FC and the SANnet II 200 SATA arrays only. The SANnet II 200 SATA SE array does not support expansion units.

Caution – When connecting expansion units to a RAID array, always connect channel

2 of the RAID array to the A channel of the expansion units, and connect channel 3 of the RAID array to the B channel of the expansion units. Otherwise, unexpected behavior might occur.

Several cabling configurations are possible, each with its own advantages and disadvantages. Refer to the SANnet II 200 FC and SATA Array Best Practices Manual for more information about the suitability of various configurations for various application requirements, as well as for information about high-capacity configurations.

The maximum number of expansion units attached to a RAID array are:

■ up to eight SANnet II 200 FC expansion units attached to a SANnet II 200 FC array

■ up to five SANnet II 200 SATA expansion units attached to a SANnet II 200 SATA

array

■ up to five SANnet II 200 FC expansion units and SANnet II 200 SATA expansion

units, in any combination, attached to a SANnet II 200 FC array

These configurations are described in the SANnet II 200 FC and SATA Array Best

Practices Manual.

The examples in Figure 4-7 and Figure 4-8 show RAID arrays connected to two expansion units. Connections to expansion units are designed to keep all A drive ports on the same loop and all B drive ports on the same loop.

Caution – To avoid drive assignment conflicts, make sure that each connected array

and expansion unit uses a different loop ID, as described in “Setting Loop IDs on Expansion Units” on page 4-13.

In the RAID array, two of the unused SFP host ports can be used to provide redundant pathing to the two servers, and the remaining unused SFP host ports can be connected to two more servers in a redundant configuration.

Similarly, you can connect expansion units to other channels (which are separate from channels 2 and 3) if you configure them as drive channels. For details, refer to the SANnet II Family RAID Firmware User’s Guide.

Chapter 4 Connecting Your Array 4-11

RAID array

Expansion unit 1

Expansion unit 2

Loop A (top drive ports) Loop B (bottom drive ports)

Cable to drive

Cable to host

Figure 4-7 SANnet II 200 FC Array Attached to Two Hosts and Two Expansion

Units

4-12 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

RAID array

Expansion unit 1

Loop A (left-side drive ports)

Expansion unit 2

H/D/RCC

Cable to drive

Cable to host

Loop B (right-side drive ports)

Figure 4-8 SANnet II 200 SATA Array Attached to Two Hosts and Two Expansion Units

4.6 Setting Loop IDs on Expansion Units

When an expansion unit is attached to a RAID array, unique, hard-assigned loop IDs are assigned to each expansion unit drive. A loop ID is the decimal version of an arbitrated loop physical address (AL_PA). The lowest number loop ID is the lowest priority address on the loop.

On the left front side of an expansion unit, an ID switch is used to set the loop IDs for the disk drives to a different range of values so that the same IDs are not repeated by RAID units and expansion units on the same loop.

Setting the loop ID on an array or expansion unit requires dropping the front bezel out of the way and removing the small vertical plastic cap on the left side of the bezel that covers the left rackmount tab. Rackmount tabs are also referred to as “ears.”

Chapter 4 Connecting Your Array 4-13

Plastic “ear” cap covering loop ID switch

Figure 4-9 Front Bezel and Front Bezel Locks of an Array

1. Use the provided key to unlock both bezel locks.

2. Grasp the front bezel cover on both sides and pull it forward and then down.

3. Remove the plastic cap from the left ear of the array.

a. Squeeze both sides of the cap at the top and the bottom.

b. Turn the cap toward the center of the array until it disengages and pull it free.

Caution – To avoid damage to the cap, do not pull the cap forward directly or pull

from only its top or bottom.

The ID switch is exposed when you remove the plastic cap.

Press to change the ID number

Bezel locks

Figure 4-10 ID Switch Located on the Left Front Side of Arrays and Expansion

Units

4. Press the upper or lower switch button to change the ID number so that each connected RAID array and expansion unit uses a different loop ID.

Caution – The loop ID should only be changed while the expansion unit is powered

off or not in use. After changing the loop ID, a power cycle is required to make the ID switch change take effect. Failure to cycle the power following a loop ID change can lead to unexpected results.

The default ID switch setting for RAID arrays is 0. The default range of available drive IDs for RAID arrays is 0 to 11 for 12 drives (the IDs 12–15 are ignored). The default ID switch setting for expansion units and JBODs is 1.

4-14 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Ensure that the loop IDs of expansion units do not duplicate the loop IDs of other connected expansion units or RAID arrays.

The ID switch offers eight ID ranges. Each range contains 16 IDs (the last four IDs in each range are ignored). These ranges are shown in Table 4-3.

Table 4- 3 ID Switch Settings for Expansion Units

ID Switch Setting Range of IDs

0 0–15

1 16–31

2 32–47

3 48–63

4 64–79

5 80–95

6 96–111

7 112–125

For an example of properly configured loop IDs, consider the configurations shown in Figure 4-7 and Figure 4-8. You must make sure the RAID array and each of the two expansion units have been assigned different loop IDs. Set the loop ID switches so that the RAID array is assigned loop ID 0, expansion unit 1 has loop ID 1, and expansion unit 2 has loop ID 2. The range of IDs assigned to the drives is shown in Table 4-4.

Table 4- 4 Sample Array and Expansion Units With Different Loop IDs and Drive

IDs

Fibre Channel Device

Loop ID Switch Setting

Range of Drive IDs

RAID array 0 0–15

Expansion unit 1 1 16–31

Expansion unit 2 2 32–47

5. Prepare the plastic left ear cap for replacement by aligning the inside round notches of the cap with the round cylindrical posts (ball studs) on the ear.

6. Push the top and bottom of the ear cap onto the ear, pressing in on the top side toward the center of the array first.

7. Continue pushing the top and bottom of the ear cap onto the ear, pressing on the side toward the outside of the array.

Do not use force when placing a cap on an ear.

Chapter 4 Connecting Your Array 4-15

8. Lift the bezel into position and press it onto the front of the chassis until it is flush with the front.

9. Use the key to lock both bezel locks.

4.7 Powering Up and Checking LEDs

Perform the initial check of the array according to the following procedure.

1. Connect two AC or DC power cables to the power and fan modules on the back of the array.

2. Power on the array by turning on each power switch. See “Power-On Sequence” on page 4-32 for the power-up sequence to use when

operating RAID arrays and expansion units. See “Connecting SANnet II 200 FC JBOD Arrays” on page B-6 for the power-up sequence to use when operating standalone SANnet II 200 FC JBODs directly attached to hosts.

3. Check for the following LED activity: All front-panel LEDs turn solid green to indicate good operation.

Disk 0

Disk 1

Disk 2

Disk 3

Disk 4

Disk 5

Disk 6

Disk 7

Disk 8

Disk 9

Disk 10

Disk 11

Figure 4-11 Front Panel of the SANnet II 200 FC, SATA, and SATA SE Array With

LEDs Displayed

See Chapter 6 for more information about your array’s LEDs.

4.8 Reviewing Channels, Ports, and SFPs

I/O controller modules have ports that accept small form-factor pluggable (SFP) transceivers. The SANnet II 200 FC and SATA arrays have ports labeled FC0 through FC5, to indicate channels 0 through 5. The SANnet II 200 SATA SE array has ports

4-16 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

labeled FC0, FC1, FC4, and FC5 to indicate channels 0, 1, 4, and 5. Default configurations do not include an SFP connector in every SFP port. To add or change SFP connectors, see to “Changing Your SFP Configuration” on page 4-24.

The channels and associated ports for the SANnet II 200 FC, SATA, and SATA SE arrays are summarized in Table 4-5.

Table 4- 5 Number of Ports in SANnet II 200 FC, SATA, and SATA SE Arrays

Item

Total number of

SANnet II 200 FC Array

68 6

SANnet II 200 SATA Array

ports

Channel 0 1 FC0 host or drive port;

default: host port

Channel 1 1 FC1 host or drive port;

default: host port

Channel 2

1 FC2 dedicated drive port

Channel 3

1 FC3 dedicated drive port

Channel 4 1 FC4 host or drive port;

default: host port

Channel 5 1 FC5 host or drive port;

default: host port

1. Channel 2 drive ports connect to drive loop A ports on expansion units.

2. Channel 3 drive ports connect to drive loop B ports on expansion units.

3. Only one host port connection per channel is allowed when connecting to a fabric switch.

2 FC0 dedicated host

ports

2 FC1 dedicated host

ports

1 FC2 dedicated drive port

1 FC3 dedicated drive port

1 FC4 host or drive port; default: host port

1 FC5 host or drive port; default: host port

SANnet II 200 SATA SE Array

2 FCO dedicated host ports *

2 FC1 dedicated host ports *

None

1 FC4 host port

1 FC5 host port

4.8.1 Drive Port Connectivity in a Dual-Controller Array

Drive channels connect to the internal drives in the array and can also connect to drives in external expansion units. The key difference between the SANnet II 200 FC and SATA array drive channels is the assignment of two ports for each channel:

■ The SANnet II 200 FC array has a drive channel assigned to two ports on each

I/O controller module. Each drive channel is a pair of ports on a single I/O controller module. In a dual-controller configuration, the top controller has two ports for drive channel 2, and the lower I/O controller module has two ports for drive channel 3.

■ The SANnet II 200 SATA array has a drive channel assigned to one port on

each I/O controller module in a dual-controller configuration.

Chapter 4 Connecting Your Array 4-17

Note – The SANnet II 200 SATA SE array configuration does not include drive ports.

4.8.1.1 SANnet II 200 FC Array Drive Ports

Configured for redundancy, each controller in a dual-controller RAID array has two adjacent dedicated drive channels on one loop to load balance I/O operations (see Figure 4-12). Each drive channel has two SFP ports that can be connected to expansion units. Drive channels 2 and 3 access all the disk drives and are interconnected to loadbalance I/O operations. Each drive channel has an upper and lower port.

Two ports on channel 3

Two drive ports on channel 2

Figure 4-12 Dedicated Drive Channels 2 on the Upper Controller and 3 on the Lower Controller in

a Dual-Controller SANnet II 200 FC Array

The I/O controller module in slot A (the upper slot) houses drive channel 2, which connects to the 12 internal disk drives through their A ports. The I/O controller module in slot B (the lower slot) houses drive channel 3, which connects to the 12 internal disk drives through their B ports.

4.8.1.2 SANnet II 200 SATA Array Drive Ports

Drive channels 2 and 3 are dedicated drive channels. Configured for redundancy, each drive channel of the top I/O controller module shares a loop with the matching drive channel on the bottom I/O controller module. For example, drive channel 2 of the top I/O controller module shares the same loop as channel 2 on the bottom I/O controller module (see Figure 4-13). Each drive channel has two SFP ports that can be connected to expansion units. Drive channels 2 and 3 access all the disk drives using internal FCSATA routing technology and are interconnected to load balance I/O operations.

4-18 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Two drive ports on channel 2

An upper port and a lower port are on each drive channel.

Figure 4-13 Dedicated Drive Channels 2 and 3 (on Both Controllers) in a Dual-Controller SANnet

II 200 SATA Array

Two drive ports on channel 3

4.8.2 Host Port Connectivity in a Dual-Controller Array

Host channels connect to host computers either directly or through storage switches or other devices. In a default dual-controller RAID configuration, each controller has four host channels, channels 0, 1, 4, and 5. Port bypass circuits connect each pair of host SFP ports on a host channel; as a result, each host channel accesses both controllers.

The main differences between the SANnet II 200 FC, SATA, and SATA SE arrays are the number of host ports and the supported speed for each port (see Table 4-6).

Table 4- 6 Number of Host Ports and Supported Host Port Speeds

Data Transfer Speed SANnet II 200 FC Array SANnet II 200 SATA and SATA SE Array

1 Gbit or 2-Gbit Maximum of 4 host ports per

I/O controller module

2 Gbit only N/A Maximum of 2 host ports (FC 4 and FC 5)

Maximum of 4 host ports (FC 0 and FC 1) per I/O controller module

per I/O controller module

4.8.2.1 SANnet II 200 FC Array

In a default dual-controller RAID configuration, each controller has four host ports. Each port connects to one host channel, channels 0, 1, 4, and 5 (see Figure 4-14). All four host channels support 1-Gbit or 2-Gbit data transfer speeds. Each host channel has un upper port and a lower port.

Chapter 4 Connecting Your Array 4-19

Host channel 0

An upper port and a lower port are on each host channel.

Host channel 1

Host channel 4

Host channel 5

Figure 4-14 Host Channels on a Dual-Controller SANnet II 200 FC Array

4.8.2.2 SANnet II 200 SATA and SATA SE Arrays

In a default dual-controller SANnet II 200 SATA and SATA SE RAID configuration, each controller has six host ports, as shown in Figure 4-15:

■ Two host ports connect to channel 0 (FC 0)

■ Two host ports connect to channel 1 (FC 1)

■ One host port connects to channel 4 (FC 4)

■ One host port connects to channel 5 (FC 5)

Channels 0 and 1 support 1-Gbit or 2-Gbit data transfer speeds. Channels 4 and 5 support 2-Gbit data transfer speeds only.

If a fabric switch is connected to one port of channel 0 or channel 1, no connections can be made with the other three ports of that channel. If channel 0 (FC 0) is connected to a fabric switch, for example, the second port for channel 0 on that controller, and both ports on a redundant controller cannot be used. Similarly, if channel 1 (FC 1) is connected to a fabric switch, the second port on that controller and the two FC 1 ports on a redundant controller cannot be used.

Two hosts can be directly connected to either channel 0 (ports FC 0) or channel 1 (ports FC 1), but in that configuration, host filters are required if you want to control host access to storage. Each host channel has an upper port and a lower port.

4-20 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Host channel 4 Host channel 5

Host channel 0

An upper port and a lower port are on each host channel.

Figure 4-15 Host Channels on a Dual-Controller SANnet II 200 SATA Array

Host channel 1

The following figure shows the host channels for a SANnet II 200 SATA SE array.

Host channel 4 Host channel 5

Host channel 0

An upper port and a lower port are on each host channel.

Figure 4-16 Host Channels on a Dual-Controller SATA SE Array

Host channel 1

4.8.3 Default SFP Placement

Default configurations do not include an SFP connector in every SFP port. You might want to add or rearrange SFPs, depending on the configuration mode (loop or point-topoint), the number of planned host connections, the necessary number of redundant connections to hosts, and the number of expansion units needed.

The supported SFP is a single-port, optical SFP transceiver for multimode (short wave) or single-mode (long wave) use. It is compatible with the Small Form Factor Pluggable Multi-Sourcing Agreement (MSA, Sep. 2000), and 1x and 2x Fiber Channel. The optical connector used is the low-profile LC connector.

SFPs are field-replaceable units (FRUs) and can be ordered from Dot Hill. These SFPs have been selected and tested to provide the necessary reliability and performance. SFPs from other vendors are not supported.

Chapter 4 Connecting Your Array 4-21

To review various configuration options, see the discussions following “Summary of Array Configuration” on page 5-1. Refer also to the configuration options presented in the SANnet II 200 FC and SATA Array Best Practices Manual.

In dual-controller arrays, SFPs are initially plugged into one of each pair of host and drive ports. The default port connections are:

■ The upper I/O controller module has SFPs in the FC0, FC2, and FC4 ports.

■ The lower I/O controller module has SFPs in the FC1, FC3, and FC5 ports.

This configuration provides connections to all six host channels as well as to both drive channels (see Figure 4-17 and Figure 4-18).

Host port FC0 Drive port FC2 Host port FC4

Host port FC1

Drive port FC3

Host port FC5

Figure 4-17 Default Dual-Controller SANnet II 200 FC Array SFP Placement

Host port FC0

Host port FC1

Drive port FC2

Drive port FC3

Host port FC4

H/D/RCC

Host port FC5

Figure 4-18 Default Dual-Controller SANnet II 200 SATA Array SFP Placement

Note – The SANnet II 200 SATA SE array configuration does not include SFPs. SFPs

must be ordered separately.

In the default single-controller array, SFPs are initially plugged into the following ports:

■ FC0

■ FC1

■ FC4

■ FC5

4-22 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

No SFPs are plugged into the drive channels. This configuration is appropriate for connecting to up to four hosts or fibre switches, with no connection to expansion units (see Figure 4-19 and Figure 4-20).

Host port FC0

Host port FC1

Host port FC4

Host port FC5

Figure 4-19 SANnet II 200 FC Array Default Single Controller SFP Placement

H/D/RCC

Host port FC0

Host port FC1

Host port FC4

Host port FC5

Figure 4-20 SANnet II 200 SATA Array Default Single-Controller SFP Placement

Note – The SANnet II 200 SATA SE array configuration does not include SFPs. SFPs

must be ordered separately.

In a default SANnet II 200 FC expansion unit, SFPs are initially plugged into the leftmost port of the upper I/O expansion module and right-most port of the lower I/O expansion module (see Figure 4-21).

Note – The SANnet II 200 SATA SE array does not support this configuration.

Chapter 4 Connecting Your Array 4-23

Default SFP Placement

Figure 4-21 SANnet II 200 FC JBOD/Expansion Unit Default SFP Placement

In a default SANnet II 200 SATA expansion unit, SFPs are initially plugged into the left-most Loop A port in the upper I/O expansion module and in the left-most Loop B port in the lower I/O expansion module (Figure 4-22).

Default SFP Placement

Figure 4-22 SANnet II 200 SATA Expansion Unit Default SFP Placement

4.8.4 Changing Your SFP Configuration

The FC and SATA arrays use SFP connectors to attach to hosts and expansion units. SATA SE arrays use SFP connectors to attach to hosts. These SFP connectors resemble the one shown in Figure 4-23, with a single connector at the end that plugs into an SFP port on the array or expansion unit chassis, and a duplex jack into which you insert a cable to make the connection.

■ To connect to an empty port, first slide the SFP connector into the port so that it

connects firmly with the chassis. Then plug the fiber-optic cable’s SFP connector into the duplex jack at the end of the SFP.

■ To remove an SFP connector, remove the cable if one is connected to it, and then

slide the SFP out from the port.

4-24 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Figure 4-23 Typical SFP Connector Used to Connect Cables to Chassis SFP Ports

4.9 Establishing Communications With An Array

Before you can configure an array, you must establish one or more communication links between at least one host and an array. You can use any combination of the array’s RS-232 COM (serial) port, the Ethernet port, and the in-band data connection between the host and the array.

■ A direct RS-232 port connection guarantees that a host can communicate with a

RAID array even if the array’s IP address changes or is unknown, or if the TCP/IP network suffers a temporary outage. See “Configuring a Host COM Port to Connect to a RAID Array” on page 4-26 for more information.

■ SANnet II 200 FC, SATA, and SATA SE arrays ship with the Dynamic Host

Configuration Protocol (DHCP) TCP/IP network support protocol enabled. If your network uses a DHCP server to dynamically and automatically allocate IP addresses to attached devices, as soon as the RAID array is powered up an IP address is assigned to it. You can use this IP address to monitor and manage the array’s firmware through telnet sessions. See “Setting Up Out-of-Band Management Over Ethernet” on page 4-28 for information about setting up a telnet session.

■ A fixed IP address enables you to use telnet or other out-of-band management

sessions to manage the array with no risk of a DHCP server changing its IP address. See “Setting Up Out-of-Band Management Over Ethernet” on page 4-28 for information.

When the array is first powered up, the default IP address setting uses the IP address assigned by a DHCP server. If the RAID array is connected to a network with an active DHCP server, you can determine the IP address assigned to the array in several ways:

■ If you have access to the controller firmware, from the Main Menu choose

Configuration Parameters → Communication Parameters → Internet Protocol (TCP/IP). If the RAID controller is not on a network connected to an active DHCP

server, “DHCP Client” is displayed rather than a DHCP-assigned IP address. Refer to the “Configuration Parameters” chapter in the SANnet II Family RAID Firmware User's Guide for more information.

Chapter 4 Connecting Your Array 4-25

■ Use the show network-parameters CLI command. Refer to the SANscape CLI

User's Guide for more information. If the RAID controller is not on a network

connected to an active DHCP server, an IP address of 0.0.0.0 is displayed. Refer to the SANscape CLI User's Guide for more information.

■ Use the Change Network Settings window in SANscape. Refer to the “Updating the

Configuration” chapter in the SANscape User’s Guide for more information.

■ Enable the controller firmware to send event messages using SNMP. Event

messages sent as SNMP traps to the email address you specify contain the IP address of the array from which it is sent. Refer to the “Configuration Parameters” chapter in the SANnet II Family RAID Firmware User's Guide for more information.

Once you have determined the RAID controller’s IP address using one of these methods, you can establish a telnet session to that IP address. However, because of the dynamic nature of DHCP-assigned IP addresses, the RAID array’s IP address might change in the event of a controller reset, a network outage, or if the DHCP server is rebooted. If this happens, telnet sessions to the previous IP address can no longer communicate with the array, and it is necessary to use one of the methods described above to determine the new IP address.

If you do not have an active DHCP server on the same network as the RAID array, or if you prefer to have a fixed IP address, use the procedures in “Setting Up Out-ofBand Management Over Ethernet” on page 4-28.

4.10 Configuring a Host COM Port to Connect to a RAID Array

The RS-232 COM (serial) port on either controller module can be used to configure and monitor the RAID array using the controller firmware. It can be connected to a VT100 terminal, terminal emulation program, terminal server, or the serial port of a server.

1. Use a null modem serial cable to connect the COM port of the RAID array to the serial port on a host workstation.

A null modem serial cable is included in your package.

2. Set the serial port parameters on the workstation as follows:

■ 38,400 baud

■ 8 bit

■ 1 stop bit

■ No parity

If your host uses the Solaris operating system, see “Using the tip Command for Local Access to the Array” on page E-2 for instructions about setting up a to communicate using the COM port.

To see platform-specific details for other operating systems, see the appendix that describes the operating system your server uses.

tip session

4-26 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

4.11 Manually Setting a Static IP Address

You can manually set an array’s IP address using the controller’s firmware by typing values for the IP address, the subnet mask, and IP address of the gateway. If your network uses a Reverse Address Resolution Protocol (RARP) server or a Dynamic Host Configuration Protocol (DHCP) server to automatically configure IP information for devices on the network, you can specify the appropriate protocol instead of typing the information manually.

Note – If you assign an IP address to an array to manage it out-of-band, for security

reasons consider using an IP address on a private network rather than a publicly routable network.

To set the IP address, subnet mask, and gateway address of the RAID controller, perform the following steps.

1. Access the array through the COM port on the I/O Controller module or through a telnet session to the existing IP address.

2. From the controller firmware’s Main Menu, choose view and edit Configuration parameters → Communication Parameters → Internet Protocol (TCP/IP).

3. Select the chip hardware address and MAC address that is displayed.

4. Choose Set IP Address → Address.

5. Type in the desired IP address, subnet mask (if it is not automatically supplied), and gateway address, choosing each menu option in turn, backspacing over any existing entries.

If your network sets IP addresses using a RARP server and you prefer using it to using a fixed IP address, type mask or gateway address. If your network sets IP addresses using a DHCP server and you prefer using it to using a fixed IP address, type and do not type a subnet mask or gateway address.

6. Press Esc to continue. A confirmation prompt is displayed.

Change/Set IP Address ?

7. Choose Ye s to continue.

Note – You must reset the controller for the configuration to take effect.

You are prompted to reset the controller.

RARP rather than an IP address, and do not type in a subnet

DHCP rather than an IP address,

Chapter 4 Connecting Your Array 4-27

8. Choose Ye s to reset the controller. The controller takes a few minutes to format a small storage sector on each physical

drive before logical drives can be successfully initialized.

4.12 Setting Up Out-of-Band Management Over Ethernet

The controller Ethernet port offers interactive out-of-band management through the following interfaces:

■ The SANscape application. Refer to the SANscape User’s Guide for details.

■ The SANscape Command-Line Interface (CLI). Refer to the SANscape CLI User’s

Guide for details.

■ The firmware application you access when you use the telnet command to

connect to the IP address of the controller.

Using an Ethernet connection, you can configure and monitor RAID arrays and expansion units remotely by using the application on the array and by using the SANscape or SANscape CLI software.

Caution – If you assign an IP address to an array to manage it out-of-band, for

security reasons consider using an IP address on a private network rather than a publicly routable network. Using the controller firmware to set a password for the controller limits unauthorized access to the array. Changing the firmware’s Network Protocol Support settings can provide further security by disabling the ability to remotely connect to the array using individual protocols such as HTTP, HTTPS, telnet, FTP, and SSH. Refer to the “Communication Parameters” section of the SANnet II Family RAID Firmware User’s Guide for more information.

telnet command to access the firmware

1. To access the RAID array over an Ethernet connection, first connect the RAID array’s Ethernet port on each controller to the network.

Note – SANnet II family arrays require at least CAT-5 Ethernet cable.

Note – In a dual-controller RAID array, be sure to connect both Ethernet ports to the

network. This provides failover if one controller fails.

2. Establish the IP address of the RAID array, as described in “Establishing Communications With An Array” on page 4-25.

3. To use the firmware application program from the host server, connect to the IP address of the RAID array controller with the following command:

4-28 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

# telnet IP-address

Note – Alternatively, you can use the Solaris operating system tip command or a

terminal emulation program to access the firmware application program. See “Configuring a Host COM Port to Connect to a RAID Array” on page 4-26 for more information.

4. Press Ctrl-L to refresh the screen and view the Main Menu.

Note – If you reset the controller during a telnet session, you are disconnected from

the RAID array. Use the telnet command to login to the array again.

To connect the SANscape program (on a host server) to a RAID array that has an IP address, refer to the out-of-band management instructions in the SANscape User’s

Guide.

The same document’s “Email and SNMP” appendix provides information about configuring SANscape software to use Simple Network Management Protocol (SNMP) traps and Management Information Bases (MIBs) to provide information to other outof-band enterprise management software. The “Monitoring the Array” chapter explains the use of SANscape agents to redirect event messages into host system logs.

You can also enable the controller firmware to send event messages using SNMP. Refer to the “Configuration Parameters” chapter in the SANnet II Family RAID Firmware User's Guide for more information.

4.13 Scaling a SANnet II 200 Fibre Channel Array Into a High-Capacity Configuration

Note – High-capacity SANnet II 200 FC and SATA array configurations are

supported, with certain limitations. A SANnet II 200 FC array with more than two expansion units is a high-capacity configuration. A SANnet II 200 SATA array with one expansion unit is a high-capacity configuration.

SANnet II 200 FC arrays typically allow the connection of up to two expansion units to support a maximum of 36 disks. However, you can create larger configurations that support as many as eight expansion units and up to 108 disks if you use the guidelines in this section. You can also create larger configurations of SANnet II 200 SATA arrays that support from one to five expansion units and up to 72 disks.

Chapter 4 Connecting Your Array 4-29

Carefully consider the following limitations of special high-capacity configurations. Using multiple SANnet II 200 FC arrays connected to the same SAN normally provides significantly better performance than one high-capacity configuration.

■ Maximize the size of each logical drive (up to 1908 Gbyte) before creating another

logical drive in order to allow for maximum storage capacity.

■ SANnet II 200 FC arrays can be connected to SANnet II 200 FC expansion units.

They can also be connected to a maximum of five SANnet II 200 SATA expansion units and SANnet II 200 FC expansion units, in any combination.

■ SANnet II 200 SATA arrays can only be connected with SANnet II 200 SATA

expansion units.

Refer to the SANnet II 200 FC and SATA Array Best Practices Manual for more information and sample cabling diagrams.

Note – Large configurations might require the use of one or more optional extended-

length cables, part number X9732A. Other items might also be required. Refer to the SANnet II Family FRU Installation Guide for information about supported cables, SFPs, and other user-replaceable items.

4.14 Adding an Expansion Unit to an Existing RAID Array

To install an expansion unit to an existing, configured RAID array, perform the following steps.

1. Stop I/O and shut down the controller to ensure that all data in the cache is written to disk.

For details on shutting down the controller, see “Powering Off the Array” on page 4-33.

2. Verify that the loop ID of the expansion unit is set to a different ID than the RAID unit and any expansion units already attached.

For details on loop IDs, see “Setting Loop IDs on Expansion Units” on page 4-13.

3. Physically cable the new expansion unit to the array using a valid cabling configuration.

Refer to the SANnet II 200 FC and SATA Array Best Practices Manual for more information on expansion unit cabling configurations.

4. Power on the expansion units. For details on the power-on sequence, see “Power-On Sequence” on page 4-32.

5. Power on the RAID array.

4-30 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

6. Verify the SES/PLD (programmable logic device) version of the expansion unit and the RAID array.

To review the version information, using the SANscape CLI, type show using SANscape, open the View Enclosure window.

7. If the SES/PLD version is not the same for the RAID array and the expansion unit, download the latest SES/PLD firmware from the Dot Hill web site:

http://www.dothill.com.

a. Choose Support → Downloads.

b. Click Firmware Downloads.

c. Enter the required information, and click Submit.

d. Choose and download the appropriate SES/PLD firmware.

4.15 Connecting Ports to Hosts

In a default array configuration, channels 0, 1, 4, and 5 are host channels, so you can directly connect an array to four host computers. SFP connectors are plugged into channels 0 and 4 on the upper controller and channels 1 and 5 on the lower controller for this purpose.

You can connect two additional host computers to channels 0 and 1 of a SANnet II 200 SATA array or SATA SE array. To support six host computers, however, you need to insert SFPs in the four unpopulated host ports. Except for some clustering configurations, when you connect two hosts to channel 0 or channel 1 on a SANnet II 200 SATA or SATA SE array, you must use host filtering if you want to control host access in this configuration. Refer to the user documentation for your clustering software to determine whether the clustering software can manage host access in this configuration.

ses. Or,

If you want to connect a SANnet II 200 FC array to more than four host computers, or connect a SATA or SATA SE array to more than six host computers, without changing the default configuration, you can connect these four host channels to ports on storage switches in a storage area network (SAN) configuration.

When a fabric switch is connected to one port of channel 0 or channel 1 of a SATA or SATA SE array, no connections can be made with the other three ports of that channel. If channel 0 (port FC0) is connected to a fabric switch, for example, the second port of channel 0 on that controller and the FC0 ports on a redundant controller cannot be used.

Chapter 4 Connecting Your Array 4-31

Note – The connection of a FC, SATA, or SATA SE array to Fibre Channel HBAs that

use different speeds (1 Gbit and 2 Gbit) on the same channel is not supported. You can, however, mix 1-Gbit and 2-Gbit Fibre Channel HBAs on different channels. This limitation is due to the design of SANnet II 200 Fibre Channel array port bypass circuitry and the inability of Fibre Channel to support auto-negotiation in a multi-drop loop configuration.

Use fiber-optic cables to connect host channels to Fibre Channel HBAs on your host computers or to other devices such as storage switches.

1. Connect a fiber-optic cable to an HBA or FC port on each host or storage switch you want to connect to the array.

2. Connect the SFP connector at the other end of each of these fiber-optic cables to host channel SFP connectors on the back of the array.

If there is no SFP connector in the port you want to use, first insert an SFP connector into the port as described in “Changing Your SFP Configuration” on page 4-24.

4.16 Power-On Sequence

Power on the equipment in the following order so the host computer discovers all connected arrays:

1. Expansion units

2. RAID array

3. Host computers

If an array is connected to a host using a serial port connection and powered on, the host terminal window displays a series of messages, as shown in the following example.

SANnet II FC Array is installed with 1024MBytes SDRAM Total channels: 6 Channel: 0 is a host channel, id: 40 Channel: 1 is a host channel, id: 41 Channel: 2 is a drive channel, id: 14, 15 Channel: 3 is a drive channel, id: 14, 15 Channel: 4 is a host channel, id: 70 Channel: 5 is a host channel, id: 71 Scanning channels. Please wait a few moments! Preparing to restore saved persistent reservations. Type 'skip' to skip:

Do not use the skip option shown at the bottom of the example. This option is reserved for support personnel performing testing.

4-32 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

4.17 Powering Off the Array

You might need to power off the array (both power supplies) if you relocate the array or perform certain maintenance procedures with associated servers. Always shut down the array’s controller before powering off the array.

Caution – If controllers are not shut down from the firmware application or the

SANscape CLI before an array is powered off, data that is written to cache and that has not been completely written to the disks will be lost.

To power off an array, perform the following steps.

1. Stop all I/O activity to the array.

2. Shut down the controller with one of the following commands:

■ Firmware application Shutdown Controller command (system Functions →

Shutdown controller)

■ SANscape CLI shutdown controller command

These commands first halt all I/O activity, and then write the contents of cache to the drives.

3. Power off both power supply/fan modules. See “Power-On Sequence” on page 4-32 for information about turning the array back

on.

Chapter 4 Connecting Your Array 4-33

4-34 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

CHAPTER

Configuration Overview

This chapter highlights the tools and the important limitations and guidelines which must be understood prior to configuring your array.

This chapter covers the following topics:

■ “Summary of Array Configuration” on page 5-1

■ “Point-to-Point Configuration Guidelines” on page 5-3

■ “A Sample SAN Point-to-Point Configuration” on page 5-5

■ “A Sample DAS Loop Configuration” on page 5-10

■ “Connecting Two Hosts to One Host Channel (SATA Only)” on page 5-14

■ “Larger Configurations” on page 5-14

Subsequent chapters in this manual describe further procedures used to complete the installation and configuration of the arrays. The flexible architecture of the SANnet II 200 FC, SATA, and SATA SE arrays makes many configurations possible.

5.1 Summary of Array Configuration

SANnet II 200 FC, SATA, and SATA SE arrays are preconfigured with a single RAID 0 logical drive mapped to LUN 0, and no spare drives. This is not a usable configuration, but it enables in-band connections with management software. You must delete this logical drive and create new logical drives.

All configuration procedures can be performed by using the COM port. You can also perform all procedures except the assignment of an IP address through an Ethernet port connection to a management console.

The following steps describe the typical sequence of steps for completing a first-time configuration of the array.

1. Mount the array on a rack, cabinet, desk, or table.

2. Set up the serial port connection. See “Configuring a Host COM Port to Connect to a RAID Array” on page 4-26.

5-1

3. Set up an IP address for the controller. See “Establishing Communications With An Array” on page 4-25.

Note – For detailed information in performing steps 4–14, refer to the SANnet II

Family RAID Firmware User’s Guide for optimization mode guidelines.

4. Check the status of the available physical drives.

5. Determine whether sequential or random optimization is more appropriate for your applications and configure your array accordingly.

6. Confirm or change the Fibre Connection Option (point-to-point or loop).

7. Revise or add host IDs on host channels. The IDs assigned to controllers take effect only after the controller is reset.

8. Delete default logical drives and create new logical drives.

Note – While the ability to create and manage logical volumes remains a feature of

arrays for legacy reasons, the size and performance of physical and logical drives have made the use of logical volumes obsolete. Logical volumes are unsuited to some modern configurations, such as Sun Cluster environments, and do not work in those configurations. Avoid using logical volumes and use logical drives instead. For more information about logical drives, refer to the SANnet II Family RAID Firmware User’s Guide.

9. (Optional) In dual-controller configurations only, assign logical drives to the secondary controller to load balance the two controllers.

Caution – In single-controller configurations, do not disable the Redundant

Controller setting and do not set the controller as a secondary controller. The primary

controller controls all firmware operations and must be the assignment of the single controller. If you disable the Redundant Controller Function and reconfigure the controller with the Autoconfigure option or as a secondary controller, the controller module becomes inoperable and will need to be replaced.

10. (Optional) Partition the logical drives.

11. Map each logical drive partition to an ID on a host channel, or apply a host LUN filter to the logical drives.

5-2 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Note – Each operating system has a method for recognizing storage devices and LUNs

and might require the use of specific commands or the modification of specific files. Be sure to check the information for your operating system to ensure that you have performed the necessary procedures.

For information about different operating system procedures, see:

■ Appendix E, “Configuring a Sun Server Running the Solaris Operating System” on

page E-1

■ Appendix F, “Configuring a Microsoft Windows Server” on page F-1

■ Appendix G, “Configuring a Linux Server” on page G-1

■ Appendix H, “Configuring an IBM Server Running the AIX Operating System” on

page H-1

■ Appendix I, “Configuring an HP Server Running the HP-UX Operating System” on

page I-1

12. Reset the controller.

Configuration is complete.

Note – Resetting the controller can result in occasional host-side error messages such

as parity error and synchronous error messages. No action is required and the condition corrects itself as soon as reinitialization of the controller is complete.

13. Save the configuration to a disk.

14. Make sure that the cabling from the RAID array to the hosts is complete.

Note – You can reset the controller after each step or at the end of the configuration

process.

Caution – Avoid using in-band and out-of-band connections at the same time to

manage the array. Otherwise, conflicts between multiple operations can cause unexpected results.

5.1.1 Point-to-Point Configuration Guidelines

Remember the following guidelines when implementing point-to-point configurations in your array and connecting to fabric switches:

■ The default mode is “Loop only.” You must change the Fibre Channel Connection

mode to “Point-to-point only” with the firmware application. Refer to the SANnet II Family RAID Firmware User’s Guide for more information.

Chapter 5 Configuration Overview 5-3

Caution – If you keep the default loop mode and connect to a fabric switch, the array

automatically shifts to public loop mode. As a result, communication between the array and the switched fabric runs in half duplex (send or receive) instead of providing the full duplex (send and receive) performance of point-to-point mode.

■ Check the host IDs on all the channels to ensure that there is only one ID per

channel (on the primary controller or on the secondary controller) for point-to-point mode. When viewing the host IDs, there should be one primary controller ID (PID) or one secondary controller ID (SID); the alternate port ID should display N/A. Proper point-to-point mode allows only one ID per channel.

■ On the SANnet II 200 SATA or SATA SE array, if one of the dual-ports of channel

0 is connected to a switch (port FC 0), the other FC 0 port on that controller and the two FC0 ports on a redundant controller cannot be used. Similarly, if one of the channel 1 ports is connected with a switch (port FC 1), the other FC 1 port on that controller, and the two FC 1 port on a redundant controller cannot be used.

■ If you change the mode to Point-to-point only and attempt to add a second ID, the

controller does not allow you to add an ID to the same controller and channel. For example, if you have ID 40 on CH 0 PID, and N/A on CH 0 SID, the controller does not allow you to add another PID to CH 0.

The controller displays a warning if the user is in point-to-point mode and tries to add an ID to the same channel but on the other controller. The warning is displayed because you have the ability to disable the internal connection between the channels on the primary and secondary controller using the SANscape CLI

controller link

command and, by doing this, you can have one ID on the

set inter-

primary and another ID on the secondary as a legal operation. However, if you ignore this warning and add an ID to the other controller, the RAID

controller does not allow a login as a Fabric Loop (FL) port because this would be illegal in a point-to-point configuration.

■ The firmware application allows you to add up to eight IDs per channel (four IDs on

each controller), which forces the fabric switch port type to become fabric loop. To ensure F-port behavior (full fabric/full duplex) when attaching to a switch, only one ID must be present on each channel and the array port must be set to point-to-point mode.

■ Do not connect more than one port per channel on an array to a fabric switch.

Caution – In point-to-point mode or in public loop mode, only one switch port is

allowed per channel. Connecting more than one port per channel to a switch can violate the point-to-point topology of the channel, force two switch ports to “fight” over an AL_PA (arbitrated loop physical address) value of 0 (which is reserved for loop-to-fabric attachment), or both.

■ With four host channels and four host IDs, you should load balance the host ID

setup so that half the IDs are on the primary controller and half the IDs are on the secondary controller. When setting up LUNs, map each LUN to either two PIDs or two SIDs. The hosts are in turn dual-pathed to the same two switched fabrics. When

5-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

attaching the cables for a LUN-mapped channel pair, make sure that the first channel is connected to the upper port and the second channel is connected to the lower port of the second channel.

For example, to provide redundancy, map half of the LUNs across Channel 0 (PID

40) and Channel 4 (PID 42), and then map the other half of your LUNs across Channel 1 (SID 41) and Channel 5 (SID 43).

■ Point-to-point mode allows a maximum of 128 LUNs per array. In a redundant

configuration, 32 LUNs are dual-mapped across two channels on the primary controller, and another 32 LUNs are dual-mapped across the secondary controller, for a total of 64 distinct LUNs.

■ To use more than 64 LUNs, you must change to loop only mode, add host IDs to

one or more channels, and add 32 LUNs for each additional host ID.

Note – When in loop mode and connected to a fabric switch, each host ID is

displayed as a loop device on the switch so that, if all 16 IDs are active on a given channel, the array looks like a loop with 16 nodes attached to a single switch FL port.

In public loop mode, the array can have a maximum of 1024 LUNs, where 512 LUNs are dual-mapped across two channels, primary and secondary controller respectively.

5.1.2 A Sample SAN Point-to-Point Configuration

A point-to-point configuration has the following characteristics:

■ In SAN configurations, the switches communicate with the SANnet II 200 Fibre

Channel array host ports using a fabric point-to-point (F_port) mode.

■ When you use fabric point-to-point (F_port) connections between a FC, SATA, or

SATA SE array and fabric switches, the maximum number of LUNs is limited to 128 LUNs for a nonredundant configuration and 64 LUNs for a redundant configuration.

■ Fibre Channel standards allow only one ID per port when operating point-to-point

protocols, resulting in a maximum of four IDs with a maximum of 32 LUNs for each ID, and a combined maximum of 128 LUNs.

■ The working maximum number of LUNs is actually 64 LUNs in a configuration

where you configure each LUN on two different channels for redundancy and to avoid a single point of failure.

In a dual-controller array, one controller automatically takes over all operation of a second failed controller in all circumstances. However, when an I/O controller module needs to be replaced and a cable to an I/O port is removed, the I/O path is broken unless multipathing software has established a separate path from the host to the operational controller. Supporting hot-swap servicing of a failed controller requires the use of multipathing software, such as SANpath software, on the connected servers.

Chapter 5 Configuration Overview 5-5

Note – Multipathing for FC, SATA, and SATA SE arrays is provided by SANpath

software.

Remember these important rules:

■ A single logical drive can be mapped to only one controller, either the primary

controller or the secondary controller.

■ In a point-to-point configuration, only one host ID per channel is allowed. The host

ID can be assigned to the primary controller and be a PID, or it can be assigned to the secondary controller and be a SID.

■ If you have two switches and set up multipathing (to keep all logical drive

connections operational for any switch failure or the removal of any I/O controller module), ensure that each logical drive is mapped to two ports, one on each I/O controller module, and on two channels. The cables from the two ports mapped to each logical drive must be cabled to two separate switches. See Figure 5-1 and Figure 5-2 for examples of this configuration.

The following figures (Figure 5-1 and Figure 5-2) show the channel numbers (0, 1, 4, and 5) of each host port and the host ID for each channel. N/A means that the port does not have a second ID assignment. The primary controller is the top I/O controller module, and the secondary controller is the bottom I/O controller module.

The dashed lines between two ports indicate a port bypass circuit that functions as a mini-hub. The port bypass circuit on each channel connects the upper and lower ports on the same channel and provides access to both controllers at the same time. If there are two host connections to the upper and lower ports on Channel 0, and one host connection is removed, the other host connection remains operational. Therefore, if you have a redundant multipathing configuration in which you have two host connections to each logical drive and one connection fails, the remaining path maintains a connection to the logical drive.

In Figure 5-1 and Figure 5-2, with multipathing software to reroute the data paths, each logical drive remains fully operational when the following conditions occur:

■ One switch fails or is disconnected, and the logical drive is routed to the second

switch. For example, if switch 0 fails, switch 1 automatically accesses logical drive 0 through the cabling to the lower port on PID 41.

■ One I/O controller module fails, and all the host IDs for that controller are

reassigned (moved) to the second 1/O controller module. For example, if the upper I/O controller module is removed, host IDs 40 and 41 are automatically moved to the lower module and are managed by the second controller.

■ An I/O controller module fails or one cable is removed from an I/O controller

module, and all I/O traffic to the disconnected channel is rerouted through the second port/host LUN assigned to the logical drive. For example, if you remove the cable to channel 4, the data path for logical drive 1 switches to the port on channel

5-6 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Server 0

Server 1

Switch 0

PID 40 PID 43

N/A SID 46

Map LG0 to PIDs 40 and 43 Map LG1 to SIDs 45 and 46

145

N/A

: Host port on channel number N

PID 40 / PID43 : Host IDs on primary controller SID 45 / SID46 : Host IDs on secondary controller N/A : Not applicable (no ID on that controller) : Port bypass circuit

Switch 1

SID 45

N/A0

N/A

Figure 5-1 A Point-to-Point Configuration with a Dual-Controller SANnet II 200 FC Array and Two

Switches

Chapter 5 Configuration Overview 5-7

Server 0

Server 1

Switch 0

PID 40 PID 43

N/A SID 46

Map LG0 to PIDs 40 and 43 Map LG1 to SIDs 45 and 46

: Host port on channel number N

PID 40 / PID43 : Host IDs on primary controller SID 45 / SID46 : Host IDs on secondary controller N/A : Not applicable (no ID on that controller) : Port bypass circuit

N/A

Switch 1

N/A

SID 45

N/A

Figure 5-2 A Point-to-Point Configuration With a Dual-Controller SANnet II 200 SATA Array and

Two Switches

Note – These illustrations show the default controller locations; however, the primary

controller and secondary controller locations can occur in either slot and depend on controller resets and controller replacement operations.

Table 5-1 summarizes the primary and secondary host IDs assigned to logical drives 0 and 1, as shown in Figure 5-1 and Figure 5-2.

5-8 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Table 5- 1 Example Point-to-Point Configuration With Two Logical Drives in a Dual-

Controller Array

Task

Map 32 partitions of LG 0 to

Logical Drive

LG 0 0-31 0 40 N/A

LUN IDs

Channel Number

Primary ID Number

Secondary ID Number

CH 0

Duplicate-map 32 partitions of

LG 0 0-31 1 41 N/A

LG 0 to CH 1

Map 32 partitions of LG 1 to

LG 1 0-31 4 N/A 50

CH 4

Duplicate-map 32 partitions of

LG 1 0-31 5 N/A 51

LG 1 to CH 5

Perform the following steps to set up a typical point-to-point SAN configuration based on Figure 5-1 and Figure 5-2.

1. Check the position of installed SFPs. Move them as necessary to support the connections needed.

2. Connect expansion units, if needed.

3. Create at least two logical drives (logical drive 0 and logical drive 1) and configure spare drives.

Leave half of the logical drives assigned to the primary controller (default assignment). Assign the other half of the logical drives to the secondary controller to load-balance the I/O.

4. Create up to 32 partitions (LUNs) in each logical drive.

5. Change the Fibre Connection Option to Point to point only (view and edit

Configuration parameters → Host-side SCSI Parameters → Fibre Connections Option).

6. For ease of use in configuring LUNs, change the host IDs on the four channels to the following assignments:

Channel 0: PID 40 (assigned to the primary controller) Channel 1: PID 41 (assigned to the primary controller) Channel 4: SID 50 (assigned to the secondary controller) Channel 5: SID 51 (assigned to the secondary controller)

Caution – Do not use the command, Loop preferred, otherwise point to point. This

command is reserved for special use and should be used only if directed by technical support.

Chapter 5 Configuration Overview 5-9

7. Map logical drive 0 to channels 0 and 1 of the primary controller. Map LUN numbers 0 through 31 to the single ID on each host channel.

8. Map logical drive 1 to channels 4 and 5 of the secondary controller. Map LUN numbers 0 through 31 to the single ID on each host channel. Since each set

of LUNs is assigned to two channels for redundancy, the total working maximum number of LUNs is 64 LUNs.

Note – The LUN ID numbers and the number of LUNs available per logical drive can

vary according to the number of logical drives and the ID assignments you want on each channel.

9. Connect the first switch to ports 0 and 4 of the upper controller.

10. Connect the second switch to ports 1 and 5 of the lower controller.

11. Connect each server to each switch.

12. Install and enable multipathing software on each connected server. The multipathing software prevents path failure but does not alter the controller

redundancy through which one controller automatically takes over all functions of a second failed controller.

5.1.3 A Sample DAS Loop Configuration

The typical direct attached storage (DAS) configuration shown in Figure 5-3 and Figure 5-4 includes four servers, a dual-controller array, and two expansion units. Expansion units are optional.

Note – The SATA SE array does not support expansion units.

Servers, as shown in Figure 5-3 and Figure 5-4, are connected to the following channels:

Table 5- 2 Connection for Four Servers in a DAS Configuration

Server Number Upper I/O Controller Module Lower I/O Controller Module

10 5

24 1

35 0

41 4

5-10 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Server 1

Server 2

Server 3

Server 4

Figure 5-3 A DAS Configuration With Four Servers, a Dual-Controller SANnet II

200 FC Array, and Two Expansion Units

Chapter 5 Configuration Overview 5-11

Server 3

Server 4

Server 1

Server 2

H/D/RCC

Figure 5-4 A DAS Configuration With Four Servers, a Dual-Controller SANnet II

200 SATA Array, and Two Expansion Units

Establishing complete redundancy and maintaining high availability requires the use of multipathing software such as SANpath software. To configure for multipathing:

1. Establish two connections between each server and the array.

2. Install and enable multipathing software on the server.

3. Map the logical drive each server is using to the controller channels that the server

is connected to.

5-12 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

DAS configurations are typically implemented using a fabric loop (FL_port) mode. A loop configuration example is described in “A Sample DAS Loop Configuration” on page 5-10.

FL_port connections between a FC, SATA, or SATA SE arrays and multiple servers allow up to 1024 LUNs to be presented to servers. For guidelines on how to create 1024 LUNs, refer to the SANnet II Family RAID Firmware User’s Guide.

Perform the following steps to set up a DAS loop configuration as shown in Figure 5-3 and Figure 5-4.

1. Check the location of installed SFPs. Move them as necessary to support the connections needed.

You must add SFP connectors to support more than four connections between servers and a FC or SATA array. For example, add two SFP connectors to support six connections and add four SFP connectors to support eight connections.

2. Connect expansion units, if needed.

3. Create at least one logical drive per server, and configure spare drives as needed.

4. Create one or more logical drive partitions for each server.

5. Confirm that the Fibre Connection Option is set to Loop only.

Caution – Do not use the command, “Loop preferred, otherwise point to point.” This

command is reserved for special use and should be used only if directed by technical support.

6. Set up to eight IDs on each channel, if needed. For more information, see Table 5-3.

Table 5- 3 Example Primary and Secondary ID Numbers in a Loop Configuration

With Two IDs per Channel

Channel Number

04041

14342

44445

54746

Primary ID Number

Secondary ID Number

7. Map logical drive 0 to channels 0 and 5 of the primary controller.

8. Map logical drive 1 to channels 1 and 4 of the secondary controller.

9. Map logical drive 2 to channels 0 and 5 of the primary controller.

10. Map logical drive 3 to channels 1 and 4 of the secondary controller.

Chapter 5 Configuration Overview 5-13

11. Connect the first server to port FC 0 of the upper controller and port FC5 of the lower controller.

12. Connect the second server to port FC 4 of the upper controller and port FC1 of the lower controller.

13. Connect the third server to port FC 5 of the upper controller and port FC0 of the lower controller.

14. Connect the fourth server to port FC 1 of the upper controller and port FC4 of the lower controller.

15. Install and enable multipathing software on each connected server.

5.1.4 Connecting Two Hosts to One Host Channel (SATA Only)

Except in some clustering configurations, if you connect more than one host to channel 0 or channel 1 in a DAS loop configuration, you must use host filtering when you want to control host access to storage. Refer to the SANnet II Family RAID Firmware User’s Guide for information about host filters. Refer to the user documentation for your clustering software to determine whether the clustering software can manage host access in this configuration.

5.2 Larger Configurations

Larger configurations are possible using additional expansion units connected to FC arrays or SATA arrays:

■ Up to eight expansion units are supported when connected to a SANnet II 200 FC

array.

■ Up to five expansion units are supported when connected to a SANnet II 200 SATA

array.

■ Up to five SANnet II 200 FC expansion units and SANnet II 200 SATA expansion

units can be combined when connected to a SANnet II 200 FC array. This enables you to use FC drives for primary online applications and SATA drives for secondary or near-line applications within the same RAID array.

Note – The SANnet II 200 SATA SE array does not support expansion units.

Certain limitations and considerations apply to these mixed configurations:

■ Connect SANnet II 200 SATA expansion units only to host channels (channels 0, 1,

4, or 5) on the SANnet II 200 FC array that have been converted to drive channels. For information about converting host channels to drive channels, refer to the SANnet II Family RAID Firmware User’s Guide.

5-14 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

■ Do not combine SANnet II 200 FC drives and SANnet II 200 SATA drives on the

same Fibre Channel loop. Use them only on separate loops.

■ Do not connect SANnet II 200 SATA expansion units to SANnet II 200 FC arrays in

single-controller configurations.

■ Make sure at least one additional logical drive is available before adding a SANnet

II 200 SATA expansion unit. It is preferable to make sure a minimum of one available logical drive per SANnet II 200 SATA expansion unit is available.

■ Consider managing and monitoring SATA arrays and expansion units out-of-band,

balancing performance requirements against security issues. Because of the slower performance of SATA drives, managing and monitoring SANnet II 200 SATA arrays and expansion units using in-band connections might result in contention between I/O operations and monitoring operations.

See “Comparison of FC, SATA, and SATA SE Arrays” on page 1-2 for information about appropriate uses of these products to make sure the solutions you choose suit your applications and requirements.

For more detailed information, and for suggestions about the most appropriate configurations for your applications and environment, refer to the SANnet II 200 FC and SATA Array Best Practices Manual.

Chapter 5 Configuration Overview 5-15

5-16 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

CHAPTER

Checking LEDs

This chapter describes the front and back-panel LEDs, which display the operating status of all drives and modules. Topics covered in this chapter are:

■ “LEDs When The Array Is First Powered On” on page 6-1

■ “Front-Panel LEDs” on page 6-2

■ “Drive LED Status” on page 6-4

■ “Correcting SES or PLD Firmware Version Conflicts” on page 6-4

■ “Back-Panel LEDs” on page 6-5

■ “I/O Controller Module LEDs” on page 6-5

■ “I/O Expansion Module LEDs” on page 6-8

■ “Power Supply and Fan Module LEDs” on page 6-9

For troubleshooting flowcharts related to LEDs, see “Troubleshooting Flowcharts” on page 8-11.

6.1 LEDs When The Array Is First Powered On

With the array powered up but not connected to a server, you should see the LED conditions described in Table 6-1.

Table 6- 1 Front-Panel LED Status When Array Is First Powered On

Drive LEDs Blinking green

Chassis ear LEDs Solid green

Note – Whenever media scan is running on a drive, its front-panel LED flashes green.

It is normal for almost all front-panel drive LEDs to flash green unless media scanning is terminated. For more information, refer to the SANnet II Family RAID Firmware User’s Guide.

6-1

6.2 Front-Panel LEDs

The drive LEDs are located between the rows of drives on the front-panel, as shown in Figure 6-1. The system operation LEDs are located on the right ear of the chassis and shown in Figure 6-2.

Drive LED 0

LED 1 LED 2

Disk 0

Disk 1

Disk 2

Disk 3

Disk 4

Disk 5

Drive LED 3

LED 4 LED 5

Disk 6

Disk 7

Disk 8

Disk 9

Disk 10

Disk 11

•Power

•Fan

•Temp

• Event

•Reset

•Reset push button

Figure 6-1 Front-Panel LEDs

Figure 6-2 shows the chassis ear LEDs and reset push button. Use a paper clip to push the Reset button to silence a failed component alarm. See “Silencing Audible Alarms” on page 8-5 for more information about silencing audible alarms.

Power

Fan

Te mp

Event

Reset push button

Figure 6-2 Chassis Ear LEDs and Reset Button on Front Panel

6-2 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005

Dot Hill II 200 FC User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Figures

Tables

Preface

How This Book Is Organized

Typographic Conventions

Related Documentation

Technical Support

Placing a Support Call

Dot Hill Welcomes Your Comments

Product and Architecture Overview

1.1 Comparison of FC, SATA, and SATA SE Arrays

1.1.1 Fibre Channel and SATA Array Architectures

1.1.2 Differences Between SANnet II 200 FC Arrays and SANnet II 200 SATA Arrays

1.1.3 SANnet II 200 FC, SATA, and SATA SE Array Configurations

1.2 Field-Replaceable Units

1.2.1 RAID I/O Controller Modules

1.2.2 I/O Expansion Modules

1.2.3 Disk Drives

1.2.4 Battery Module

1.2.5 Power and Fan Modules

1.3 Interoperability

1.4 Fibre Channel Technology Overview

1.4.1 FC Protocols

1.4.2 FC Topologies

1.4.3 Fibre Hubs and Switches

1.4.4 Data Availability

1.4.5 Scalability

1.5 Fibre Channel Architecture

1.5.1 Redundant Configuration Considerations

1.6 Additional Software Tools

Site Planning

2.1 Customer Obligations

2.2 Safety Precautions

2.3 Environmental Requirements

2.3.1 Electromagnetic Compatibility

2.4 Electrical and Power Specifications

2.5 Physical Specifications

2.6 Layout Map

2.6.1 Rack Placement

2.6.2 Tabletop Placement

2.7 Console and Other Requirements

2.8 Preinstallation Worksheets

Unpacking Your Array

3.1 Opening Your Package

3.2 Checking the Package Contents

3.2.1 Standard Array Packages

3.3 Field-Replaceable Units

3.4 Customer-Provided Cables

3.5 Mounting Your Array in a Rack or Cabinet

Connecting Your Array

4.1 Converting Your Front Bezel Locks So the Keys Cannot Be Removed

4.2 RAID Array Connections

4.2.1 SANnet II 200 FC Array Connections

4.2.2 SANnet II 200 SATA Array Connections

4.2.3 SANnet II 200 SATA SE Array Connections

4.3 Connecting the Chassis to AC Power Outlets

4.4 Connecting the Chassis to DC Power Outlets

4.5 Cabling to Expansion Units

4.6 Setting Loop IDs on Expansion Units

4.7 Powering Up and Checking LEDs

4.8 Reviewing Channels, Ports, and SFPs

4.8.1 Drive Port Connectivity in a Dual-Controller Array

4.8.2 Host Port Connectivity in a Dual-Controller Array

4.8.3 Default SFP Placement

4.8.4 Changing Your SFP Configuration

4.9 Establishing Communications With An Array

4.10 Configuring a Host COM Port to Connect to a RAID Array

4.11 Manually Setting a Static IP Address

4.12 Setting Up Out-of-Band Management Over Ethernet

4.13 Scaling a SANnet II 200 Fibre Channel Array Into a High-Capacity Configuration

4.14 Adding an Expansion Unit to an Existing RAID Array

4.15 Connecting Ports to Hosts

4.16 Power-On Sequence

4.17 Powering Off the Array

Configuration Overview