HP P2000 User Manual

HP P2000 G3 FC MSA System User Guide

Part number: 590336-004 First edition: July 2011

Legal and notice information

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Com mercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgements

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

UNIX is a registered trademark of The Open Group.

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Rack stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Customer self repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Product warranties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HP websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Features and benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Front panel components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

P2000 G3 FC MSA System LFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

P2000 G3 FC MSA System SFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Disk drive bay numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Rear panel view — controller module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

P2000 G3 FC MSA System controller module face plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Rear panel components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

P2000 G3 FC MSA System SFF and P2000 G3 FC MSA System LFF. . . . . . . . . . . . . . . . . . . . . . . . . 19

D2700 6Gb drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

P2000 6Gb 3.5" 12-drive enclosure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

MSA70 3Gb drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

MSA2000 3Gb 3.5" 12-drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Transportable CompactFlash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Super-capacitor pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Installing the enclosures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Connecting controller and drive enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connecting controller and D2700 6Gb drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connecting controller and P2000 6Gb 3.5" 12-drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connecting controller and MSA70 3Gb drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connecting controller and MSA2000 3Gb 3.5" 12-drive enclosure. . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connecting controller and mixed drive enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Additional cable requirements for drive enclosures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

P2000 G3 MSA System cable requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Additional cabling considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Testing enclosure connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Powering on/powering off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Power Cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

AC model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

DC model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Power cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Connecting hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Host system requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

HP P2000 G3 FC MSA System User Guide 3

Connecting the enclosure to data hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

FC host ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Connecting direct attach configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Single controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

One server/one HBA/single path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Dual controller configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

One server/one HBA/dual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Two servers/one HBA per server/dual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Connecting switch attach configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Dual controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Two servers/two switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Connecting remote management hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Connecting two storage systems to replicate volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Single-controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Multiple servers/single network/two switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Dual controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Multiple servers/different networks/multiple switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Multiple servers/single network/single switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Updating firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5 Connecting to the controller CLI port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Device description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Preparing a Linux computer before cabling to the CLI port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Downloading a device driver for Windows computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Obtaining IP values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using the MSA Device Discovery Tool to discover controller’s IP addresses . . . . . . . . . . . . . . . . . . . . . 45

Setting network port IP addresses using DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Setting network port IP addresses using the CLI port and cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6 Basic operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Accessing SMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring and provisioning the storage system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

CLI port connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Fault isolation methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Gather fault information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Determine where the fault is occurring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Review the event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Isolate the fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

If the enclosure does not initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Correcting enclosure IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Diagnostic steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Is the front panel Fault LED amber? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Is the controller back panel OK LED off? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Is the controller back panel Fault/Service Required LED amber? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Are both disk drive module LEDs off (Online/Activity and Fault/UID)? . . . . . . . . . . . . . . . . . . . . . . . . 53

Is the disk drive module Fault/UID LED blinking amber? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Is a connected host port’s Host Link Status LED off? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Is a connected port’s Expansion Port Status LED off?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Is a connected port’s Network Port Link Status LED off?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Is the power supply’s Input Power Source LED off? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Is the power supply’s Voltage/Fan Fault/Service Required LED amber? . . . . . . . . . . . . . . . . . . . . . . . 55

Controller failure in a single-controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

If the controller has failed or does not start, is the Cache Status LED on/blinking? . . . . . . . . . . . . . . . . 56

Transporting cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Isolating a host-side connection fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Host-side connection troubleshooting featuring SFP transceivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Isolating a controller module expansion port connection fault. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Isolating Remote Snap replication faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4Contents

Cabling for replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Replication setup and verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Diagnostic steps for replication setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Can you successfully use the Remote Snap feature? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Can you view information about remote links? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Can you create a replication set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Can you replicate a volume? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Can you view a replication image?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Can you view remote systems? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Resolving voltage and temperature warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Sensor locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Power supply sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Cooling fan sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Temperature sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Power supply module voltage sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

A LED descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Front panel LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Disk drive LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Rear panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

P2000 G3 FC MSA System SFF and P2000 G3 FC MSA System LFF. . . . . . . . . . . . . . . . . . . . . . . . . 67

D2700 6Gb drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

P2000 6Gb 3.5” 12-drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

MSA70 3Gb drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

MSA2000 3Gb 3.5” 12-drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Power supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

B Environmental requirements and specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Safety requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Site requirements and guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Site wiring and AC power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Site wiring and DC power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Weight and placement guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Electrical guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Ventilation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Cabling requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Management host requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Physical requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Environmental requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Electrical requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Site wiring and power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Power cord requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

C Electrostatic discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Preventing electrostatic discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Grounding methods to prevent electrostatic discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

HP P2000 G3 FC MSA System User Guide 5

6Contents

Figures

1 P2000 G3 MSA System component connection combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2 Cabling connections between P2000 G3 MSA System controllers and P2000 6Gb drive enclosures . . 28

3 Cabling connections between P2000 G3 controllers and D2700 6Gb drive enclosures . . . . . . . . . . . 28

4 Cabling connections between P2000 G3 controllers and MSA2000 3Gb drive enclosures . . . . . . . . 28

5 Cabling connections between P2000 G3 controllers and an MSA70 3Gb drive enclosure . . . . . . . . . 29

6 Fault-tolerant cabling: P2000 G3 controllers and P2000 6Gb drive enclosures . . . . . . . . . . . . . . . . . 29

7 Cabling connections between P2000 G3 controllers and D2700 6Gb drive enclosures . . . . . . . . . . . 30

8 Fault-tolerant cabling: P2000 G3 controllers and MSA2000 3Gb drive enclosures . . . . . . . . . . . . . . 31

9 Fault-tolerant cabling: P2000 G3 controllers and MSA70 3Gb drive enclosures . . . . . . . . . . . . . . . . 31

10 Cabling connections between dual controllers and drive enclosures of mixed type . . . . . . . . . . . . . . . 32

11 AC PSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

12 DC PSU and AC PSU with power switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

13 DC Power cable featuring sectioned D-shell and lug connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

14 Connecting two storage systems for Remote Snap — multiple servers/switches/one location. . . . . . . . 41

15 Connecting two storage systems for Remote Snap — multiple servers/switches/two locations . . . . . . . 41

16 Connecting storage systems for Remote Snap — multiple servers/SAN fabric/two locations . . . . . . . . 42

17 Connecting two storage systems for Remote Snap — multiple servers/one switch/one location . . . . . . 43

18 Connecting a USB cable to the CLI port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

HP P2000 G3 FC MSA System User Guide 7

8Figures

Tables

1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3 SAS expansion cable requirements: controller module to expansion module connection . . . . . . . . . . . . 26

4 SAS expansion cable requirements: expansion module to expansion module connection . . . . . . . . . . . 27

5 Maximum cable lengths for 850nm Fibre Channel SFP transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6 Terminal emulator display settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

7 Terminal emulator connection settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

8 Power supply sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

9 Cooling fan sensor descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

10 Controller module temperature sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

11 Power supply temperature sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

12 Voltage sensor descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

13 LEDs — HP P2000 G3 MSA Systems controller enclosure front panels . . . . . . . . . . . . . . . . . . . . . . . . 65

14 LEDs — Disk drive LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

15 LEDs — Disk drive combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

16 LEDs — HP P2000 G3 FC MSA System LFF and SFF rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

17 LEDs — HP P2000 6Gb rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

18 LEDs — HP MSA2000 3Gb rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

19 LEDs — HP P2000 G3 MSA System power supply units — rear panel . . . . . . . . . . . . . . . . . . . . . . . . 71

20 Rackmount enclosure dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

21 Rackmount enclosure weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

22 Operating environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

23 Non-operating environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

HP P2000 G3 FC MSA System User Guide 9

10 Tables

About this guide

This guide provides information about hardware setup for the HP P2000 G3 FC MSA System controller enclosures.

Intended audience

This guide is intended for storage system administrators.

Prerequisites

Prerequisites for installing and using this product include knowledge of:

• Servers and computer networks

• Network administration

• Storage system installation and configuration

• Storage area network (SAN) management and direct attach storage (DAS)

• Relevant protocols:

• Fibre Channel (FC)

•Ethernet

Document conventions and symbols

Table 1 Document conventions

Convention Element

Medium blue text: Figure 1 Cross-reference links and e-mail addresses

Medium blue, underlined text (http://www.hp.com)

Bold font • Key names

Italics font Text emphasis

Monospace font • File and directory names

Monospace, italic font

Monospace, bold font Emphasis of file and directory names, system output, code, and text

Web site addresses

• Text typed into a GUI element, such as into a box

• GUI elements that are clicked or selected, such as menu and list

items, buttons, and check boxes

• System output

• Code

• Text typed at the command-line

• Code variables

• Command-line variables

typed at the command-line

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

12 About this guide

Rack stability

WARNING! To reduce the risk of personal injury or damage to equipment:

• Extend leveling jacks to the floor.

• Ensure that the full weight of the rack rests on the leveling jacks.

• Install stabilizing feet on the rack.

• In multiple-rack installations, secure racks together.

• Extend only one rack component at a time. Racks may become unstable if more than one component is

extended.

HP technical support

Telephone numbers for worldwide technical support are listed on the HP support web site:

http://www.hp.com/support

Collect the following information before calling:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Applicable error messages

• Operating system type and revision level

• Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

Customer self repair

HP customer self repair (CSR) programs allow you to repair your storage product. If a CSR part needs replacing, HP ships the part directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your HP-authorized service provider will determine whether a repair can be accomplished by CSR.

For more information about CSR, contact your local service provider. For North America, see the CSR website:

http://www.hp.com/go/selfrepair

Product warranties

For information about HP storage product warranties, see the warranty information website:

http://www.hp.com/go/storagewarranty

Subscription service

HP strongly recommends that customers sign up online using the Subscriber's choice web site:

http://www.hp.com/go/e-updates

• Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest

versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources.

• After signing up, you can quickly locate your products by selecting Business support and then Storage

under Product Category.

HP P2000 G3 FC MSA System User Guide 13

HP websites

For additional information, see the following HP websites:

• http://www.hp.com

• http://www.hp.com/go/storage

• http://www.hp.com/service_locator

• http://www.hp.com/support/manuals

• http://www.hp.com/support/downloads

• http://www.hp.com/storage/whitepapers

• http://www.hp.com/go/p2000

Documentation feedback

HP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message to

storagedocs.feedback@hp.com. All submissions become the property of HP.

14 About this guide

1Overview

The HP P2000 G3 FC MSA System is a high-performance storage solution combining outstanding performance with high reliability, availability, flexibility, and manageability.

Features and benefits

Product features and supported options are subject to change. Online documentation describes the latest product and product family characteristics, including currently supported features, options, technical specifications, configuration data, related optional software, and product warranty information.

NOTE: Check the Quickspecs for a complete list of supported servers, operating systems, disk drives, and

options. Quickspecs can be found from your HP MSA products page at http://www.hp.com/go/ Quickspecs links are located on the right.

p2000.

HP P2000 G3 FC MSA System User Guide 15

16 Overview

2Components

P2000

132

P2000

Front panel components

P2000 G3 FC MSA System LFF

Left ear

1 Enclosure ID LED 2 Disk drive Online/Activity LED 3 Disk drive Fault/UID LED

P2000 G3 FC MSA System SFF

Left ear

Right ear

4 Unit Identification (UID) LED 5 Heartbeat LED 6 Fault ID LED

Right ear

1 Enclosure ID LED 2 Disk drive Online/Activity LED 3 Disk drive Fault/UID LED

4 Unit Identification (UID) LED 5 Heartbeat LED 6 Fault ID LED

HP P2000 G3 FC MSA System User Guide 17

Disk drive bay numbers

P2000

1 2

4 5

7 8

10 11

P2000

12345678 9101112131415161718192021222324

P2000 G3 FC MSA System LFF

P2000 G3 FC MSA System SFF

Rear panel view — controller module

The P2000 G3 MSA System controller module shown below is not proportionately sized relative to preceding controller enclosure views. The controller module face plate is enlarged to show relevant detail.

P2000 G3 FC MSA System controller module face plate

2,4G

CLI CLI HOST

ACT

SERVICE

LINK

6Gb/s

CACHE

18 Components

Rear panel components

SERVICE

FC 2

FC 1

CACHE

CLI CLI HOST

2,4G

SERVICE

FC 2

FC 1

CACHE

CLI CLI HOST

2,4G

6Gb/s

ACT

LINK

ACT

LINK

1357:1

4 6 8

;

P2000 G3 FC MSA System SFF and P2000 G3 FC MSA System LFF

1 AC Power supplies 2 Controller module A 3 FC ports: host interface or replication 4 Reserved for future use 5 CLI port (USB - Type B) 6 USB - Type A port: reserved for future use

7 Network port 8 Service port (used by service personnel only)

9 Disabled button (used by engineering only) 10 SAS expansion port 11 Controller module B 12 DC Power supply (2) — (DC model only) 13 DC Power switch

IMPORTANT: See Connecting to the controller CLI port for information on enabling the controller

enclosure’s USB Type B CLI port.

Drive enclosures attach to the controller enclosure for the purpose of expanding storage capacity. Drive enclosures supported by the P2000 G3 MSA System controllers are described in the following sections. The 3Gb drive enclosures supported by the newer controller enclosures are listed for customers upgrading existing legacy systems.

NOTE: For optimal performance, 6Gb P2000 G3 MSA System controller enclosures should be cabled to

6Gb P2000 G3 MSA System drive enclosures when expanding storage capacity.

D2700 6Gb drive enclosure

P2000 G3 MSA System controllers support D2700 6Gb drive enclosures. For information about P2000G3MSA System products, visit http://www.hp.com/go/p2000

. Select Related products, select your drive enclosure, select Support > HP Support & Drivers from the right side of the page, select your product name, and select Manuals.

HP P2000 G3 FC MSA System User Guide 19

P2000 6Gb 3.5" 12-drive enclosure

IN OUT

1346

1562 12

1 Power supplies 2 I/O module A 3 Disabled button (used by engineering only) 4 Service port (used by service personnel only)

MSA70 3Gb drive enclosure

P2000 G3 MSA System controllers can also be attached to an MSA70 3Gb drive enclosure that is running firmware version 2.18 or later. For information about the MSA70 3Gb drive enclosure, see the HP

StorageWorks 70 Modular Smart Array Enclosure user guide located on the MSA2000 Software Support/Documentation CD shipped with your product, or accessible from your HP MSA products page at

http://hp.com/support/manuals

MSA2000 3Gb 3.5" 12-drive enclosure

5 SAS In port 6 SAS Out port 7 I/O module B

1 Power supplies 2 Power switches (not applicable to newer models) 3 I/O module A 4 SAS In port

5 Service port (used by service personnel only) 6 SAS Out port 7 I/O module B

Cache

To enable faster data access from disk storage, the following types of caching are performed:

• Write-back or write-through caching. The controller writes user data in the cache memory on the

module rather than directly to the drives. Later, when the storage system is either idle or aging — and continuing to receive new I/O data — the controller writes the data to the drive array.

• Read-ahead caching. The controller detects sequential array access, reads ahead into the next

sequence of data, and stores the data in the read-ahead cache. Then, if the next read access is for cached data, the controller immediately loads the data into the system memory, avoiding the latency of

20 Components

a disk access.

NOTE: See HP P2000G3MSA System SMU Reference Guide for more information about volume cache

Controller Module

CompactFlash

options.

Transportable CompactFlash

During a power loss or array controller failure, data stored in cache are saved off to non-volatile memory (CompactFlash). These data are then written to disk after the issue is corrected. To protect against writing incomplete data to disk, the image stored on the CompactFlash is verified before committing to disk.

In single-controller configurations, if the controller has failed or does not start, and the Cache Status LED is on or blinking, the CompactFlash will need to be transported to a replacement controller to recover data not flushed to disk (See Controller failure in a single-controller configuration on page 55 for more information).

CAUTION: To preserve the existing data stored in the CompactFlash, you must transport the

CompactFlash from the failed controller to the replacement controller using a procedure outlined in the HP Controller Module Replacement Instructions, shipped with the replacement controller. Failure to use this

procedure will result in the loss of data stored in the cache module. The CompactFlash must stay with the same enclosure. If the CompactFlash is used/installed in a different enclosure, data loss/data corruption will occur.

IMPORTANT: In dual controller configurations featuring one healthy peer controller, there is no need to

transport a failed controller’s cache to a replacement controller because the cache is duplicated between the controllers.

Super-capacitor pack

To protect RAID controller cache in case of power failure, P2000 G3 MSA System controllers are equipped with super-capacitor technology, in conjunction with CompactFlash memory, built into each controller module to provide unlimited cache memory backup time. The super-capacitor pack provides energy for backing up unwritten data in the write cache to the CompactFlash in the event of a power failure. Unwritten data in CompactFlash memory are automatically committed to disk media when power is restored. While the cache is being maintained by the super-capacitor, the Cache Status LED flashes at a rate of 1/10 second on and 9/10 second off.

HP P2000 G3 FC MSA System User Guide 21

22 Components

3Installing the enclosures

Installation checklist

The following table outlines the steps required to install the enclosures and initially configure the system. To ensure a successful installation, perform the tasks in the order they are presented.

Table 2 Installation checklist

Step

1. Install the controller enclosure and

Task Where to find procedure

See the racking instructions poster. optional drive enclosures in the rack, and attach ear caps.

2. Connect controller enclosure and LFF/SFF

drive enclosures.

See Connecting controller and drive enclosures on

page 24.

3. Connect power cords. See the installation poster.

4. Test enclosure connections. See Testing enclosure connections on page 33.

5. Install required host software. See Host system requirements on page 37.

6. Connect data hosts. See Connecting the enclosure to data hosts on

page 37.

If using the optional Remote Snap feature, also see

Connecting two storage systems to replicate volumes

on page 40.

7. Connect remote management hosts. See Connecting remote management hosts on

page 39.

8. Obtain IP values and set management

port IP properties on the controller enclosure.

9. Perform initial configuration tasks

See Obtaining IP values on page 45.

See Connecting to the controller CLI port; with Linux

and Windows topics.

Topics below correspond to bullets at left:

• Sign in to the web-based storage

management application (SMU).

• Initially configure and provision the

storage system using SMU.

MSA Device Discovery Tool, introduced in Obtaining IP values, provides the optimal method for setting network port IP addresses.

SMU is introduced in Accessing SMU on page 49. See the SMU reference guide or online help for additional information.

If the systems are cabled for replication and licensed to use the Remote Snap feature, you can use the Replication Setup Wizard to

prepare to replicate an existing volume to another vdisk. See the SMU reference guide for additional information.

See “Getting Started” in the HP P2000G3MSA

System SMU Reference Guide.

See “Configuring the System” and “Provisioning the

System” topics (SMU reference guide or online help).

NOTE: For optimal performance, 6Gb P2000 G3 MSA System controller enclosures should be cabled to

6Gb P2000 G3 MSA System drive enclosures when expanding storage capacity.

P2000 G3 MSA System controller to drive enclosure cabling is described within this chapter. Cabling of 3Gb drive enclosures to newer 6Gb controllers is addressed for customers upgrading existing legacy systems.

NOTE: For information on NEBS Level 3-compliant carrier-grade enclosures, see

http://www.hp.com/products1/servers/carrier_grade/products/cgblades/enclosure

HP P2000 G3 FC MSA System User Guide 23

Connecting controller and drive enclosures

P2000 G3 MSA System controller enclosures — available in either 24-drive (2.5”) or 12-drive (3.5”) chassis — support up to eight enclosures (including the controller enclosure) for storage/expansion, or a maximum of 149 disk drives. You can also configure drive enclosures of mixed type, as shown in Table 3 on page 26.

The firmware supports both straight-through and reverse SAS cabling. Reverse cabling allows any drive enclosure to fail — or be removed — while maintaining access to other enclosures. Fault tolerance and performance requirements determine whether to optimize the configuration for high availability or high performance when cabling. P2000 G3 MSA System controller enclosures support both 3Gbps and 6Gbps internal disk drive speeds, together with 3Gbps and 6Gbps expander link speeds. Controller and expansion modules are identified by <enclosure-ID><controller-ID>. When connecting multiple drive enclosures, use reverse cabling to ensure the highest level of fault tolerance.

For example, Figure 6 on page 29 shows controller module 1A is connected to expansion module 2A, with a chain of connections cascading down (blue). Controller module 1B is connected to the lower expansion module (5B) of the last drive enclosure, with connections moving in the opposite (reverse) direction (green).

NOTE: P2000 G3 MSA System controller enclosures support hot-plug replacement of redundant

controller modules, fans, power supplies, and I/O modules. Hot-add of drive enclosures is also supported.

Connecting controller and D2700 6Gb drive enclosure

A D2700 6Gb drive enclosure, supporting 6Gb internal disk drive and expander link speeds, can be attached to a P2000 G3 FC MSA System LFF or P2000 G3 FC MSA System SFF controller enclosure using supported mini-SAS to mini-SAS cables of 0.5m to 2m length (see Figure 3 on page 28).

Connecting controller and P2000 6Gb 3.5" 12-drive enclosure

A P2000 6Gb 3.5" 12-drive enclosure, supporting 6Gb internal disk drive and expander link speeds, can be attached to a P2000 G3 FC MSA System LFF or P2000 G3 FC MSA System SFF controller enclosure using supported mini-SAS to mini-SAS cables of 0.5m to 2m length (see Figure 2 on page 28).

Connecting controller and MSA70 3Gb drive enclosure

P2000 G3 MSA System controllers support MSA70 3Gb drive enclosures running firmware version 2.18 or later.

For information about the MSA70 3Gb drive enclosure, including detailed steps to upgrade the firmware, see the HP StorageWorks 70 Modular Smart Array Enclosure User Guide located on the MSA2000 Software Support/Documentation CD shipped with your product, or at http://hp.com/support/manuals

If you connect a 3Gb drive enclosure to a 6Gb controller enclosure, data throughput occurs at the drive enclosure’s 3Gb data rate (see Figure 5 on page 29).

Diagrams within this document use IOM (I/O Module: also referred to as expansion module).

Connecting controller and MSA2000 3Gb 3.5" 12-drive enclosure

Connecting an MSA2000 3.5” 12-drive enclosure to a P2000 G3 FC MSA System LFF or P2000 G3 FC MSA System SFF requires supported mini-SAS to SAS cables. If you connect a 3Gb drive enclosure to a 6Gb controller enclosure, data throughput occurs at the drive enclosure’s 3Gbps data rate (see Figure 4 on page 28).

IMPORTANT: Adding a fourth drive enclosure may require a separate, longer cable. For a current list of

supported cables, check the MSA2000 G2 Quickspecs located on the HP MSA products page at

http://www.hp.com/go/msa

24 Installing the enclosures

. Select your product. Quickspecs links are located on the right.

Connecting controller and mixed drive enclosures

P2000 G3 Controller Enclosure

6Gbps 6Gbps 3Gbps 3Gbps

LFFSFF

6Gbps

MSA70 3Gb IOMP2000 6Gb IOM D2700 6Gb IOM MSA2000 3Gb IOM

D2700 P2000 6Gb

MSA70 MSA2000

D2700 P2000 6Gb

MSA70 MSA2000

D2700* P2000 6Gb*

MSA70 MSA2000

MSA2000

*Cabling a 6Gbps drive enclosure behind the MSA70 3Gb drive enclosure will adjust its link-rate speed to 3Gbps.

SAS2.0 SAS2.0 SAS1.1 SAS1.1

P2000 G3 MSA System controller modules support cabling of 3Gb and 6Gb SAS link-rate LFF and SFF expansion modules — in mixed fashion — as shown in Figure 10 on page 32, and as further described in Additional cabling considerations (below); the HP P2000 G3 MSA System Cable Configuration Guide; and HP white papers (listed on the following page).

Additional cable requirements for drive enclosures

IMPORTANT:

• When installing SAS cables, use only supported SAS 4x cables with connectors supporting your

application (6Gb, 3Gb, or both).

• Mini-SAS to mini-SAS 0.5m cables are provided with each of the following drive enclosures (one per

expansion module): P2000 6Gb 3.5" 12-drive enclosure and D2700 6Gb drive enclosure.

• If additional or longer cables are required, they must be ordered separately (see relevant MSA2000

G2 Quickspecs or P2000 G3 Quickspecs for your products).

• The maximum cable length allowed in any configuration is 2m.

• When expanding storage capacity, a maximum of eight enclosures — including the controller

enclosure — or one hundred forty nine (149) disk drives are allowed in the array.

P2000 G3 MSA System cable requirements

Figure 1 (below) and Table 4 on page 27 jointly describe cabling requirements and connection

combinations for P2000G3MSA System components. Components are labeled with back-end SAS data rates and other relevant attributes. Simplified IOM face plates are shown.

Figure 1 P2000 G3 MSA System component connection combinations

Table 3 below provides SAS cable requirements for connection combinations between MSA controller and

expansion modules. Table 4 on page 27 provides details for cabling expansion modules.

NOTE: Check Quickspecs addressing your respective product with regard to cabling. Quickspecs can be

found from your HP MSA products page http://www.hp.com/go/p2000 on the right.

HP P2000 G3 FC MSA System User Guide 25

. Quickspecs links are located

Table 3 SAS expansion cable requirements: controller module to expansion module connection

Product model-to-model storage component attachment SAS Expansion (In/Out) cable data Controller module Drive enclosure Type Length Connectors P2000 G3 FC MSA SFF and

P2000 G3 FC MSA LFF

One 0.5m cable is required per controller module to I/O (expansion) module connection.

One 0.5m, 1.0m, or 2.0m cable is required per controller module to expansion module connection.

P2000 6Gb drive enclosure mini-SAS to mini-SAS10.5m 6Gbps

D2700 6Gb drive enclosure mini-SAS to mini-SAS10.5m 6Gbps

MSA2000 3Gb drive enclosure mini-SAS to SAS

MSA70 3Gb drive enclosure mini-SAS to mini-SAS

0.5m, 1m, 2m

0.5m 6Gbps

6Gbps 3Gbps

3Gbps

NOTE: Additional cabling notes:

• Cables required, if not included, must be separately purchased.

• When adding more than two drive enclosures, you may need to purchase additional 1m or 2m cables:

• Spanning 3, 4, or 5 drive enclosures requires 1m cables.

• Spanning 6 or 7 drive enclosures requires 2m cables.

• See Table 4 on page 27 and related footnotes for cabling multiple drive enclosures.

IMPORTANT: Controller modules within the enclosure must be of the same type. Do not install an HP

P2000 G3 FC MSA System and HP P2000 G3 SAS MSA System controller module in the same chassis.

IMPORTANT: Connecting 3Gb and 6Gb drive enclosures limits performance and should be done only

when upgrading legacy product configurations.

For additional information concerning cabling of P2000 G3 MSA System controllers and MSA2000 G1 or G2 drive enclosures, visit your HP MSA products page http://www.hp.com/go/p2000 MSA products page, browse for the following reference documents:

• HP P2000 G3 MSA Best practices

• HP MSA2000 Family Best practices

• Upgrading the HP M SA2000 G2 to the P2000 G3 MSA

• Upgrading the HP M SA2000 G1 to the P2000 G3 MSA

Additional cabling considerations

P2000 G3 MSA System controller enclosures (both LFF and SFF models) support each of the drive enclosures listed above. However, when cabling supported drive enclosures of mixed type, consider the following factors regarding components equipped with SAS2.0 and SAS1.1 expanders (labeled in Figure 1 on page 25):

• P2000 G3 MSA System controller enclosures support 6Gb and 3Gb drive enclosures.

• To avoid performance limitations in a mixed-type drive enclosure environment, cable 3Gb drive

enclosures after 6Gb drive enclosures as shown in Figure 10 on page 32. Do not mix 6Gb and 3Gb disk drives in the same enclosure.

• Performance will be limited if a 3Gb drive enclosure is cabled before a 6Gb drive enclosure

cannot be avoided rate if cabled after a 3Gb drive enclosure.

— if reverse cabled. A 6Gb drive enclosure will perform at a 3Gbps data transfer

. From the HP

— and

26 Installing the enclosures

• If used together with mixed drive enclosures, an MSA2000 3Gb drive enclosure should be cabled after

other supported models, using straight-through cabling.

Table 4 SAS expansion cable requirements: expansion module to expansion module connection

Product model-to-model storage component attachment SAS expansion (In/Out) cable data Expansion module Expansion module Type Length Connec tors

1, 2

0.5m 6Gbps

1, 2

0.5m 6Gbps

0.6m 6Gbps

0.5m 6Gbps

1, 2

0.5m 6Gbps

1, 2

0.5m 6Gbps

0.5m 3Gbps

0.6m 3Gbps

3Gbps

6Gbps

P2000 6Gb drive enclosure

D2700 6Gb drive enclosure

MSA70 3Gb drive enclosure

MSA2000 3Gb drive

P2000 6Gb drive enclosure mini-SAS to mini-SAS

D2700 6Gb drive enclosure mini-SAS to mini-SAS

MSA70 3Gb drive enclosure mini-SAS to mini-SAS

MSA2000 3Gb drive enclosure mini-SAS to SAS

D2700 6Gb drive enclosure mini-SAS to mini-SAS

P2000 6Gb drive enclosure mini-SAS to mini-SAS

MSA2000 3Gb drive enclosure mini-SAS to SAS

MSA70 3Gb drive enclosure mini-SAS to mini-SAS

P2000 6Gb drive enclosure mini-SAS to mini-SAS

D2700 6Gb drive enclosure mini-SAS to mini-SAS

MSA2000 3Gb drive enclosure mini-SAS to SAS

MSA2000 3Gb drive enclosure SAS to SAS

enclosure

One 0.5m cable required per I/O module to I/O module connection.

Cables required, if not included, must be separately purchased.

One 0.6m cable required per I/O module to I/O connection.

NOTE: Additional cabling notes:

When adding more than two drive enclosures, you may need to purchase additional 1m or 2m cables:

• Spanning 3, 4, or 5 drive enclosures requires 1m cables.

• Spanning 6 or 7 drive enclosures requires 2m cables.

HP P2000 G3 FC MSA System User Guide 27

NOTE: For clarity, the schematic illustrations of controller and expansion modules shown in this section

In Out

Controller A

In Out

Controller A

Controller B

In Out

P1 P2

Controller A

P1 P2

Controller A

Controller B

P1 P2

In Out

Controller A

Controller B

In Out

Controller A

provide only relevant details such as expansion ports within the module face plate outline. For detailed illustrations showing all components, see Rear panel components on page 19.

Figure 2 Cabling connections between P2000 G3 MSA System controllers and P2000 6Gb drive

enclosures

Figures 2 - 4 show a single controller module connected to a single expansion module (illustrations on left), with dual controller modules connected to dual expansion modules (illustrations on right).

Figure 3 Cabling connections between P2000 G3 controllers and D2700 6Gb drive enclosures

Figure 4 Cabling connections between P2000 G3 controllers and MSA2000 3Gb drive enclosures

28 Installing the enclosures

Figure 5 Cabling connections between P2000 G3 controllers and an MSA70 3Gb drive enclosure

Controller A

Controller B

2A 2B

In Out In Out

Controller A

Controller B

Out

The diagram above shows dual-controller modules connected to dual-expansion modules.

Figure 6 Fault-tolerant cabling: P2000 G3 controllers and P2000 6Gb drive enclosures

The diagram above shows a dual-controller enclosure cabled to P2000 6Gb drive enclosures featuring dual-expansion modules. Controller module 1A is connected to expansion module 2A, with a chain of connections cascading down (blue). Controller module 1B is connected to the lower expansion module (5B), of the last drive enclosure, with connections moving in the opposite direction (green). This logic applies to the fault tolerant cabling diagrams that follow.

HP P2000 G3 FC MSA System User Guide 29

Figure 7 Cabling connections between P2000 G3 controllers and D2700 6Gb drive enclosures

Controller A

Controller B

P2P1

Controller A

Controller B

P1 P2

Fault-tolerant cabling Straight-through cabling

The figure above provides sample diagrams reflecting cabling of P2000 G3 controller enclosures and D2700 6Gb drive enclosures.

The diagram at left shows a dual-controller enclosure cabled to D2700 6Gb drive enclosures featuring dual-expansion modules. Controller module 1A is connected to expansion module 2A, with a chain of connections cascading down (blue). Controller module 1B is connected to the lower expansion module (5B), of the last drive enclosure, with connections moving in the opposite direction (green).

The diagram at right shows the same storage components connected using straight-through cabling.

30 Installing the enclosures

Figure 8 Fault-tolerant cabling: P2000 G3 controllers and MSA2000 3Gb drive enclosures

Out

Controller A

Controller B

Out

Controller B

Controller A

In Out

Figure 9 Fault-tolerant cabling: P2000 G3 controllers and MSA70 3Gb drive enclosures

HP P2000 G3 FC MSA System User Guide 31

Controller B

Controller A

Out

Controller B

Controller A1A

Fault-tolerant cabling

Straight-through cabling

Out

4A 4B

P1P1P2

OutIn

Out

OutIn

= P2000 6Gb drive enclosure

= D2700 6Gb drive enclosure

= MSA70 3Gb drive enclosure

= MSA2000 3Gb drive enclosure

Drive enclosure IOM face plate key:

Figure 10 Cabling connections between dual controllers and drive enclosures of mixed type

The figure above shows a sample fault-tolerant cabling scenario on left, and a straight-through cabling scenario on right. Both diagrams show drive enclosures of mixed type. Do not mix SAS1.1 and SAS2.0 expanders, except as described in Additional cabling considerations on page 26. Avoid mixing them except when upgrading legacy systems.

In the illustration on the left, note that the D2700 6Gb drive enclosures could alternatively be cabled before the P2000 6Gb drive enclosures. The illustration at the right shows a D2700 6Gb drive enclosure before a P2000 6Gb drive enclosure, MSA70 3Gb drive enclosure, and MSA2000 3Gb drive enclosure. Note that the MSA2000 3Gb drive enclosure is cabled after the other drive enclosures, using straight-through cabling.

Although 6Gb drive enclosures can be cabled after an MSA70 3Gb drive enclosure, performance of the 6Gb devices will be limited to 3Gb.

IMPORTANT: For comprehensive configuration options and associated illustrations, refer to the HP

32 Installing the enclosures

P2000G3MSA System Cable Configuration Guide.

Testing enclosure connections

Power cord connect

NOTE: Once the enclosures’ power-on sequence succeeds, the storage system is ready to be connected to

hosts, as described in Connecting the enclosure to data hosts on page 37.

Powering on/powering off

Before powering on the enclosure for the first time:

• Install all disk drives in the enclosure so the controller can identify and configure them at power-up.

• Connect the cables and power cords to the enclosures as explained in the installation sheet.

NOTE: P2000 G3 controller enclosures and some P2000 G3 drive enclosures do not have power

switches. They power on when connected to a power source, and they power off when disconnected.

• Generally, when powering up, make sure to power up the enclosures and associated data host in the

following order:

•Drive enclosures first

This ensures that disks in the drive enclosure have enough time to completely spin up before being scanned by the controller modules within the controller enclosure.

While enclosures power up, their LEDs blink. After the LEDs stop blinking — and back of the enclosure are amber — been detected. See LED descriptions on page 65 for descriptions of LED behavior.

• Controller enclosure next

Depending upon the number and type of disks in the system, it may take several minutes for the system to become ready.

• Data host last (if powered down for maintenance purposes).

if no LEDs on the front

the power-on sequence is complete, and no faults have

Power supply

Many controller and expansion enclosures rely on the power cord for power cycling. Connecting the cord from the PSU power cord connector to the appropriate power source facilitates power on; whereas disconnecting the cord from the power source facilitates power off.

Figure 11 AC PSU

To power on the system:

1. Obtain a suitable AC power cord for each AC PSU that will connect to a power source.

TIP: Generally, when powering off, you will reverse the order of steps used for powering on.

HP P2000 G3 FC MSA System User Guide 33

2. Plug the power cord into the power cord connector on the back of the drive enclosure (see Figure 11).

Power switch

Power cable connect

Power switch

Power cord connect

DC power supply unit Legacy AC power supply unit

Plug the other end of the power cord into the rack power source. Wait several seconds to allow the disks to spin up.

Repeat this sequence for each PSU within each drive enclosure.

3. Plug the power cord into the power cord connector on the back of the controller enclosure (see

Figure 11). Plug the other end of the power cord into the rack power source.

Repeat the sequence for the controller enclosure’s other PSU.

To power off the system:

1. Stop all I/O from hosts to the system.

2. Shut down both controllers using either method described below:

• Use SMU to shut down both controllers, as described in the online help and web-posted HP P2000G3MSA System SMU Reference Guide.

Proceed to step 3.

• Use the command-line interface (CLI) to shut down both controllers, as described in the HP P2000G3MSA System CLI Reference Guide.

3. Disconnect the power cord’s male plug from the power source.

4. Disconnect the power cord’s female plug from the power cord connector on the PSU.

Figure 12 DC PSU and AC PSU with power switch

Power Cords

IMPORTANT: See Environmental requirements and specifications for additional information.

AC model

Obtain two suitable AC power cords: one for each AC PSU that will connect to a separate power source. See the illustration at right (in Figure 12 on page 34) when performing the following steps:

1. Verify that the enclosure’s power switches are in the Off position.

2. Identify the power cord connector on the PSU, and locate the target power source.

3. For each PSU, perform the following actions:

4. Verify connection of primary power cords from the rack to separate external power sources.

a. Plug one end of the cord into the power cord connector on the PSU. b. Plug the other end of the power cord into the rack power source.

See Power cycle on page 35.

34 Installing the enclosures

DC model

GND

-L

GND

-L

GND

-L

GND

-L

Connector pins (typical 2 places)

Connector (front view)

Ring/lug connector (typical 3 places)

D-shell

(left side view)

Locate the two DC power cables provided with your controller enclosure.

Figure 13 DC Power cable featuring sectioned D-shell and lug connectors

See Figure 13 and the illustration at left (in Figure 12) when performing the following steps:

1. Verify that the enclosure’s power switches are in the Off position.

2. Connect a DC power cable to each DC power supply using the D-shell connector.

Use the UP> arrow on the connector shell to ensure proper positioning (see adjacent left side view of D-shell connector).

3. Tighten the screws at the top and bottom of the shell, applying a torque between 1.7

N-m (15 in-lb) and 2.3 N-m (20 in-lb), to securely attach the cable to the DC power supply module.

4. To complete the DC connection, secure the other end of each cable wire component

of the DC power cable to the target DC power source. Check the three individual DC cable wire labels before connecting each cable wire lug to its power

source. One cable wire is labeled ground (GND) and the other two wires are labeled positive (+L) and negative (-L), respectively (shown in Figure 13 above).

CAUTION: Connecting to a DC power source outside the designated -48V DC nominal range

(-36V DC to -72V DC) may damage the enclosure.

Power cycle

To power on the system:

1. Power up drive enclosure(s).

Press the power switches at the back of each drive enclosure to the On position. Allow several seconds for the disks to spin up.

2. Power up the controller enclosure next.

Press the power switches at the back of the controller enclosure to the On position. Allow several seconds for the disks to spin up.

To power off the system:

1. Stop all I/O from hosts to the system.

2. Shut down both controllers using either method described below:

• Use SMU to shut down both controllers, as described in the online help and HP P2000 G3 MSA System SMU Reference Guide.

Proceed to step 3.

• Use the command-line interface (CLI) to shut down both controllers, as described in the HP P2000G3MSA System CLI Reference Guide.

3. Press the power switches at the back of the controller enclosure to the Off position.

4. Press the power switches at the back of each drive enclosure to the Off position.

HP P2000 G3 FC MSA System User Guide 35

36 Installing the enclosures

4 Connecting hosts

Host system requirements

Data hosts connected to P2000 G3 MSA System arrays must meet the following requirements:

• Depending on your system configuration, data host operating systems may require that multi-pathing is

supported.

TIP: See the HP MSA System VDS and VSS Hardware Providers Installation Guide and HP MSA

System MPIO DSM Installation Guide to aid in planning and implementing your MPIO DSM

installation.

If fault tolerance is required, then multi-pathing software may be required. Host-based multi-path software should be used in any configuration where two logical paths between the host and any storage volume may exist at the same time. This would include most configurations where there are multiple connections to the host or multiple connections between a switch and the storage.

• Use Windows Server MPIO DSM with Windows Server 2003. To obtain the MPIO DSM, go to the HP MSA products page at http://www.hp.com/go/msa Products.

• Use native Microsoft MPIO DSM support with Windows Server 2008. Use either the Server Manager or the command-line interface (mpclaim CLI tool) to perform the installation. Refer to the following web sites for information about using the Windows 2008 native MPIO DSM:

http://support.microsoft.com/gp/assistsupport http://technet.microsoft.com (search the site for “multipath I/O overview”)

• Use the HP Multi-path Device Mapper for Linux Software with Linux servers. To download the appropriate device mapper multi-path enablement kit for your specific enterprise Linux operating system, go to http://www.hp.com/go/devicemapper

• To prevent Microsoft Windows 2003 data hosts from displaying the Found New Hardware Wizard

when the storage system is discovered, install the SCSI Enclosure Services driver. Download your product’s SCSI Enclosure Services (SES) driver package from h product and go to Related Products.

. Select your product and go to Related

ttp://www.hp.com/go/msa. Select your

NOTE: P2000 Family SCSI Enclosure Services driver is required for Microsoft Windows 2003.

Connecting the enclosure to data hosts

A host identifies an external port to which the storage system is attached. Cable connections vary depending on configuration. Common cable configurations are shown in this section. A list of supported configurations resides on the P2000 G3 product site at http://www.hp.com/go/p2000

Support & Drivers, select your product, select Manuals:

•

HP P2000G3MSA Systems Installation Instructions

• HP P2000G3MSA System Cable Configuration Guide

These documents provide installation details and describe newly-supported direct connect, switch-connect, and expansion configuration options for P2000 G3 MSA System products.

Any number or combination of LUNs can be shared among a maximum of 64 host ports, provided the total does not exceed 512 LUNs per P2000 G3 storage system (single or dual controller configuration).

FC host ports

P2000 G3 FC MSA System controllers use Fibre Channel interface protocol for host port connection, featuring either one or two controller modules. Each controller module provides two host ports configured with a Fibre Channel small form-factor pluggable (SFP transceiver) connector, supporting data rates up to

. Select HP

HP P2000 G3 FC MSA System User Guide 37

8Gb per second. The P2000 G3 FC MSA System controller enclosures can also be cabled to support the

Server

Remote Snap replication feature (licensed option) via the FC ports. These models support Fibre Channel Arbitrated Loop (FC-AL or “loop”) topology by default. Connection mode can be set to loop or point-to-point. Loop protocol can be used in a physical loop or in a direct connection between two devices. Point-to-point protocol is used to connect to a fabric switch. P2000 G3 FC MSA System controllers employ FC ports in either of two capacities:

• To connect two storage systems through a Fibre Channel switch for use of Remote Snap replication.

• For attachment to FC hosts directly, or through a switch.

The first usage option requires valid licensing for the Remote Snap replication feature, whereas the second option requires that the host computer supports Ethernet, FC, and optionally, multipath I/O.

Connecting direct attach configurations

P2000 G3 FC MSA System LFF and P2000 G3 FC MSA System SFF support up to four direct-connect server connections, two per controller module. Connect appropriate cables from the servers’ HBAs to the controller host ports as described below, and shown in the following illustrations.

To connect the P2000 G3 FC MSA System controller to a server or HBA switch — using the controller’s FC host ports — select Fibre Channel cables supporting 2/4/8Gb data rates, that are compatible with the controller module’s host port SFP connector. Such cables are also used for connecting a local storage system to a remote storage system via a switch, to facilitate use of the optional Remote Snap replication feature.

The table below maps SFP transceiver data rates to relative fiber optic cable characteristics (i.e., cable length, multimode fiber type (MMF), and ISO/IEC optical multimode cable performance standards). When transferring data through FC connections, cable lengths should not exceed the lengths listed for each given fiber type and performance code within the applicable data rate (2/4/8Gb) class.

Table 5 Maximum cable lengths for 850nm Fibre Channel SFP transceivers

SFP data Representative FC cable types Data rate 8Gbps

4Gbps

2Gbps

MMF FC cable length designators

21m with 62.5μm fiber type X

50m with 50μm fiber type X

150 m w i t h 5 0 μm fiber type X

70m with 62.5μm fiber type X

150 m w i t h 5 0 μm fiber type X

380m with 50μm fiber type X

150 m w i t h 62 . 5 μm fiber type X

300m with 50μm fiber type X

500m with 50μm fiber type X

Single controller configuration

One server/one HBA/single path

Cable performance code

OM1 OM2 OM3

38 Connecting hosts

6Gb/s

Dual controller configurations

Server

6Gb/s

Server 1 Server 2

Switch A

Switch B

One server/one HBA/dual path

Two servers/one HBA per server/dual path

Connecting switch attach configurations

Dual controller configuration

6Gb/s

Two servers/two switches

Connecting remote management hosts

The management host directly manages systems out-of-band over an Ethernet network.

1. Connect an RJ-45 Ethernet cable to the network management port on each P2000 G3 MSA System

controller.

2. Connect the other end of each Ethernet cable to a network that your management host can access

(preferably on the same subnet).

6Gb/s

NOTE: Connections to this device must be made with shielded cables – grounded at both ends – with

metallic RFI/EMI connector hoods, in order to maintain compliance with FCC Rules and Regulations.

HP P2000 G3 FC MSA System User Guide 39

Connecting two storage systems to replicate volumes

Remote Snap replication is a licensed disaster-recovery feature that performs asynchronous (batch) replication of block-level data from a volume on a primary P2000 G3 MSA System to a volume that can be on the same system, or on a second, independent P2000 G3 MSA System. The second system can be located at the same site as the first system, or at a different site.

The two associated master volumes form a replication set, and only the primary volume (source of data) can be mapped for access by a server. Both systems must be licensed to use Remote Snap, and must be connected through switches to the same fabric or network (i.e., no direct attach). The server accessing the replication set need only be connected to the primary system. If the primary system goes offline, a connected server can access the replicated data from the secondary system.

Replication configuration possibilities are many, and can be cabled – in switch attach fashion – to support P2000 G3 MSA Systems on the same network, or on physically split networks. As you consider the physical connections of your system – specifically connections for replication – keep several important points in mind:

• Ensure that controllers have connectivity between systems, whether local or remote.

• Assign specific ports for replication whenever possible. By specifically assigning ports available for

replication, you free the controller from scanning and assigning the ports at the time replication is performed.

• For remote replication, ensure that all ports assigned for replication are able to communicate

appropriately with the remote replication system (see verify remote-link in the CLI reference guide for more information).

• Allow two ports to perform replication. This permits the system to balance the load across those ports as

I/O demands rise and fall. On dual-controller enclosures, if some of the volumes replicated are owned by controller A and others are owned by controller B, then allow one port for replication on each controller module of P2000 G3 FC MSA Systems, and possibly more than one port per controller module on P2000 G3 FC/iSCSI MSA Systems, depending on replication traffic load.

• Do not unnecessarily expose the controller module’s network port to an external network connection.

Conceptual cabling examples are provided addressing cabling on the same network and cabling relative to physically-split networks. Both single and dual-controller environments support replication. A single-controller system can replicate data to another single-controller system, and a dual-controller system can replicate data to another dual-controller system. Replication services do not support mixed single and dual-controller environments.

CAUTION: When replacing a P2000 G3 MSA System controller set supporting Remote Snap with a

P2000 G3 MSA System controller set that does not support this licensed feature (i.e., SAS controller modules), you must first delete all replication sets before swapping the controller modules. Not doing so will lead to unexpected results, and there is not way to delete replication sets after the installation. See the upgrade documentation supporting your product.

IMPORTANT: Remote Snap must be licensed on all systems configured for replication, and the controller

module firmware version must be the same on all systems licensed for replication (see Updating firmware on page 43).

40 Connecting hosts

Single-controller configuration

P2000 G3 FC MSA System

I/O switch Switch

(replication)

To server

P2000 G3 FC MSA System

FC I/O switch

(replication)

FC switch

I/O switch

To host servers

Remote site “A”

To host ser vers

Remote site “B”

P2000 G3 FC MSA System

Multiple servers/single network/two switches

The diagram below shows the rear-panel of two P2000 G3 FC MSA Systems featuring 2/4/8Gb FC host interface connection and 2/4/8Gb FC-based replication, with both I/O and replication occurring on the same network.

Figure 14 Connecting two storage systems for Remote Snap — multiple servers/switches/one location

Dual controller configuration

The following illustrations provide conceptual examples of cabling to support Remote Snap replication. Once the P2000 G3 MSA Systems are physically cabled, see the SMU reference guide or online help for information about configuring, provisioning, and using the optional Remote Snap feature.

NOTE: See HP P2000G3MSA System SMU Reference Guide for more information about using Remote

Snap to perform replication tasks. SMU’s Replication Setup Wizard guides you through replication setup.

Multiple servers/different networks/multiple switches

The diagram below shows the rear-panel of two P2000 G3 MSA System FC controller enclosures featuring 2/4/8Gb FC host interface connection and 2/4/8Gb FC-based replication, with both I/O and replication occurring on different networks.

Figure 15 Connecting two storage systems for Remote Snap — multiple servers/switches/two locations

HP P2000 G3 FC MSA System User Guide 41

The diagram below shows FC host interface connection and FC-based replication, with both I/O and

Data Restore Modes:

- Replicate back over FC SAN

- Replicate via physical media transfer Failover Modes:

- VMware

- Hyper V failover to servers

Building “B”Building “A”

Corporate end-users

LAN

Local campus

File servers

Application servers “A”

Application servers “B”

SAN

P2000 G3 FC MSA System (typical 2 places)

FS data

App “A”

data

App “B”

replica

App “B”

data

replica

App “A”

replica

replication occurring on different networks.

Figure 16 Connecting storage systems for Remote Snap — multiple servers/SAN fabric/two locations

42 Connecting hosts

Multiple servers/single network/single switch

Host servers Single site

P2000 G3 FC MSA System

Switch

P2000 G3 FC MSA System

The diagram below shows FC connection and FC-based replication, with both I/O and replication occurring on the same network.

Figure 17 Connecting two storage systems for Remote Snap — multiple servers/one switch/one location

With the replication configuration shown in the previous figure, employ zoning to provide separate virtual networks. Whether using a single switch or multiple switches, you can create a zone for I/O and a zone for replication to isolate I/O traffic from replication traffic. Since each switch would include both zones, the configuration would appear physically as a single network; while logically, it would function as multiple networks.

Although not shown in the preceding cabling examples, you can cable replication-enabled P2000 G3 MSA Systems of different model types together — via switch attach — for performing replication tasks.

Updating firmware

After installing the hardware and powering on the storage system components for the first time, verify that the controller modules, expansion modules, and disk drives are using the current firmware release. Using SMU, right-click the system in the Configuration View panel, and select Tools > Update Firmware. The Update Firmware panel displays the currently installed firmware versions, and enables you to update them.

When upgrading from TS100 or TS201 firmware code versions to TS230, replications in progress will temporarily halt, and report that the replications have incompatible code versions. Once the partner system is successfully upgraded, the replications will resume if they have not suspended. If the replications have suspended, they can be manually resumed. See the “Suspending replication” and “Resuming replication” topics in the SMU reference guide or online help.

NOTE: To locate and download the latest software and firmware update for your product, go to

http://www.hp.com/go/p2000

then select Download drivers and software.

. Select Models — select your product — select HP Support & Drivers,

HP P2000 G3 FC MSA System User Guide 43

44 Connecting hosts

5 Connecting to the controller CLI port

Device description

P2000 G3 MSA System controllers feature a new command-line interface (CLI) port used to cable directly to the controller and initially set IP addresses, or perform other configuration tasks. This port differs from G1 and G2 controllers. It employs a mini-USB Type B form factor, and requires a new cable and additional support so that a server or other computer running a Linux or Windows operating system can recognize the controller enclosure as a connected device. Without this support, the computer might not recognize that a new device is connected or might not be able to communicate with it. For Linux computers, no new driver files are needed, but a Linux configuration file must be created or modified.

For Windows computers, a special device driver, gserial.inf, must be downloaded from a CD or HP website, and installed on the computer that will be cabled directly to the controller’s CLI port.

NOTE: Directly cabling to the CLI port is an out-of-band connection because it communicates outside the

data paths used to transfer information from a computer or network to the controller enclosure.

An in-band connection can also be used to configure a new controller. If used, cabling to the CLI port might not be necessary. The in-band method uses the MSA Device Discovery utility on the Software Support/Documentation CD that is included with your system, and is the best way to discover the controller’s IP addresses automatically, so that you can use them to log into and manage your controllers using a web browser for SMU, or telnet for the CLI. See Using the MSA Device Discovery Tool to discover

controller’s IP addresses for instructions about how to use the MSA Device Discovery Tool over your existing

in-band connection to discover controller IP addresses without using the CLI port.

Preparing a Linux computer before cabling to the CLI port

Although Linux operating systems do not require installation of a device driver, certain parameters must be provided during driver loading to enable recognition of the P2000 G3 MSA System controller enclosures. To load the Linux device driver with the correct parameters, the following command is required:

modprobe usbserial vendor=0x210c product=0xa4a7 use_acm=1

Optionally, the information can be incorporated into the /etc/modules.conf file.

Downloading a device driver for Windows computers

A Windows USB device driver download is provided for communicating directly with the controller’s CLI port using a USB cable to connect the controller enclosure and the computer. If you use the MSA Device Discovery Tool you may not need the download. However, you can download it and install it for future use.

NOTE: Access the download from your HP MSA products page at http://www.hp.com/go/p2000.

Select Models — select your product — select HP Support & Drivers, then select Download drivers and software.

The USB device driver is also available from the P2000 G3 Software Support/Documentation CD that shipped with your product.

Obtaining IP values

Using the MSA Device Discovery Tool to discover controller’s IP addresses

The MSA Device Discovery Tool provides the optimal approach for setting network port IP addresses on Windows or Linux platforms. For help with configuring your P2000 G3 MSA System products, see the P2000 G3 Software Support/Documentation CD that shipped with your product.

1. Locate the P2000 G3 Software Support/Documentation CD included with your P2000 G3 MSA

System storage device.

HP P2000 G3 FC MSA System User Guide 45

2. Insert the P2000 G3 Software Support/Documentation CD into the CD drive on a Linux or Windows

computer on the network that is connected to your controller enclosure.

3. Use Autorun or manually start the CD.

The MSA Device Discovery Tool will run.

4. Follow the instructions to discover the IP addresses of the controller or controllers.

Record these IP addresses so that you can specify them whenever you manage the controllers using SMU or the CLI.

Alternatively, you can set network port IP addresses using CLI on HP-UX, Windows, and Linux platforms.

Setting network port IP addresses using DHCP

1. Look in the DHCP server’s pool of leased addresses for two IP addresses assigned to “HP

StorageWorks MSA Storage.”

2. Use a ping broadcast to try to identify the device through the host’s ARP table.

If you do not have a DHCP server, you will need to ask your system administrator to allocate two IP addresses, and set them using the CLI during initial configuration (described below).

Setting network port IP addresses using the CLI port and cable

If you did not use the MSA Device Discovery Tool to set network port IP values, set them manually using the CLI port and cable. If you have not done so already, you need to enable your system for using the CLI port.

NOTE: For Linux systems, see Preparing a Linux computer before cabling to the CLI port on page 45. For

Windows systems see Downloading a device driver for Windows computers on page 45.

Network ports on controller module A and controller module B are configured with the following default values:

• Management Port IP Address: 10.0.0.2 (controller A), 10.0.0.3 (controller B)

• IP Subnet Mask: 255.255.255.0

• Gateway IP Address: 10.0.0.1

If the default IP addresses are not compatible with your network, you must set an IP address for each network port using the CLI embedded in each controller module. The CLI enables you to access the system using the USB (universal serial bus) communication interface and terminal emulation software. The USB cable and CLI port support USB version 2.0.

Use the CLI commands described in the steps below to set the IP address for the network port on each controller module. Once new IP addresses are set, you can change them as needed using SMU. Be sure to change the IP address via SMU before changing the network configuration.

NOTE: Changing IP settings can cause management hosts to lose access to the storage system.

1. From your network administrator, obtain an IP address, subnet mask, and gateway address for

controller A, and another for controller B. Record these IP addresses so that you can specify them whenever you manage the controllers using

SMU or the CLI.

2. Use the provided USB cable to connect controller A to a USB port on a host computer. The USB mini 5

male connector plugs into the CLI port as shown in Figure 18 (generic controller module is shown).

46 Connecting to the controller CLI port

Figure 18 Connecting a USB cable to the CLI port

Service

CACHE

ACTIVITY

LINK

DIRTY

Host Interface

Not Shown

LINK

CLI CLI HOST

Host Interface

Not Shown

CLI

Connect USB cable to CLI

port on controller faceplate

3. Enable the CLI port for subsequent communication:

• Linux customers should enter the command syntax provided in Preparing a Linux computer before

cabling to the CLI port on page 45.

• Windows customers should locate the downloaded device driver described in Downloading a

device driver for Windows computers on page 45, and follow the instructions provided for proper

installation.

4. Start and configure a terminal emulator, such as HyperTerminal or VT-100, using the display settings in

Table 6 on page 47 and the connection settings in Table 7 on page 47 (also, see the note following

this procedure).

Table 6 Terminal emulator display settings

Parameter Value

Terminal emulation mode VT-100 or ANSI (for color support)

Font Terminal

Translations None

Columns 80

Table 7 Terminal emulator connection settings

Parameter Value

Connector COM3 (for example)

1, 2

5. In the terminal emulator, connect to controller A.

6. Press Enter to display the CLI prompt (#).

Baud rate 115,200

Data bits 8

Parity None

Stop bits 1

Flow control None

Your server or laptop configuration determines which COM port is used for Disk Array USB Port. Verify the appropriate COM port for use with the CLI.

The CLI displays the system version, MC version, and login prompt:

a. At the login prompt, enter the default user manage. b. Enter the default password !manage.

If the default user or password — or both — have been changed for security reasons, enter the secure login credentials instead of the defaults shown above.

HP P2000 G3 FC MSA System User Guide 47

7. At the prompt, type the following command to set the values you obtained in Step 1 for each network

port, first for controller A and then for controller B:

set network-parameters ip

address

netmask

gateway

controller a|b

where:

•

address

•

netmask

•

gateway

is the IP address of the controller is the subnet mask

is the IP address of the subnet router

• a|b specifies the controller whose network parameters you are setting For example:

# set network-parameters ip 192.168.0.10 netmask 255.255.255.0 gateway

192.168.0.1 controller a

# set network-parameters ip 192.168.0.11 netmask 255.255.255.0 gateway

192.168.0.1 controller b

8. Type the following command to verify the new IP addresses:

show network-parameters

Network parameters, including the IP address, subnet mask, and gateway address are displayed for each controller.

9. Use the ping command to verify network connectivity.

For example:

# ping 192.168.0.1 (gateway) Info: Pinging 192.168.0.1 with 4 packets. Success: Command completed successfully. - The remote computer responded with 4

packets.

10. In the host computer's command window, type the following command to verify connectivity, first for

controller A and then for controller B:

ping controller-

IP-address

If you cannot your access your system for at least three minutes after changing the IP address, your network might require you to restart the Management Controller(s) using the CLI.

When you restart a Management Controller, communication with it is temporarily lost until it successfully restarts.

Type the following command to restart the management controller on both controllers:

restart mc both

11. When you are done using the CLI, exit the emulator.

12. Retain the new IP addresses to access and manage the controllers, using either SMU or the CLI.

NOTE: Using HyperTerminal with the CLI on a Microsoft Windows host:

On a host computer connected to a controller module’s mini-USB CLI port, incorrect command syntax in a HyperTerminal session can cause the CLI to hang. To avoid this problem, use correct syntax, use a different terminal emulator, or connect to the CLI using telnet rather than the mini-USB cable.

Be sure to close the HyperTerminal session before shutting down the controller or restarting its Management Controller. Otherwise, the host’s CPU cycles may rise unacceptably.

48 Connecting to the controller CLI port

6 Basic operation

Verify that you have completed the sequential “Installation Checklist” instructions in Table 2 on page 23. Once you have successfully completed steps 1 through 8 therein, you can access the management interface using your web-browser.

Accessing SMU

Upon completing the hardware installation, you can access the controller module’s web-based management interface, SMU (Storage Management Utility), to monitor and manage the storage system. Invoke your web browser, and enter the IP address of the controller module’s network port in the address field (obtained during completion of “Installation Checklist” step 8), then press Enter. To Sign In to SMU, use the default user name manage and password !manage. If the default user or password — or both — have been changed for security reasons, enter the secure login credentials instead of the defaults shown above. This brief Sign In discussion assumes proper web browser setup.

IMPORTANT: For detailed information on accessing and using SMU, see the “Getting started” section in

the web-posted HP P2000 G3 MSA System SMU Reference Guide.

The Getting Started section provides instructions for signing-in to SMU, introduces key concepts, addresses browser setup, and provides tips for using the main window and the help window.

TIP: After signing in to SMU, you can use online help as an alternative to consulting the reference guide.

Configuring and provisioning the storage system

Once you have familiarized yourself with SMU, use it to configure and provision the storage system. If you are licensed to use the optional Remote Snap feature, you may also need to set up storage systems for replication. Refer to the following topics within the SMU reference guide or online help:

• Configuring the system

• Provisioning the system

• Using Remote Snap to replicate volumes

HP P2000 G3 FC MSA System User Guide 49

50 Basic operation

7Troubleshooting

CLI port connection

P2000 G3 MSA System controllers feature a new CLI port employing a mini-USB Type B form factor. If you encounter problems communicating with the port after cabling your computer to the USB device, you may need to either download a device driver (Windows), or set appropriate parameters via an operating system command (Linux). See Connecting to the controller CLI port for more information.

Fault isolation methodology

P2000 G3 MSA System controllers provide many ways to isolate faults within the system. This section presents the basic methodology used to locate faults and the associated FRUs (Field Replaceable Units).

The basic fault isolation steps are:

• Gather fault information, including using system LEDs.

• Determine where in the system the fault is occurring.

• Review event logs.

• If required, isolate the fault to a data path component or configuration.

Gather fault information

When a fault occurs, it is important to gather as much information as possible. Doing so will help you determine the correct action needed to remedy the fault.

Begin by reviewing the reported fault. Is the fault related to an internal data path or an external data path? Is the fault related to a hardware component such as a disk drive module, controller module, or power supply? By isolating the fault to one of the components within the storage system, you will be able to determine the necessary action more rapidly.

Determine where the fault is occurring

Once you have an understanding of the reported fault, review the enclosure LEDs. The enclosure LEDs are designed to alert users of any system faults, and might be what alerted the user to a fault in the first place.

When a fault occurs, the Fault ID status LED on an enclosure’s right ear (see Front panel components on page 17) illuminates. Check the LEDs on the back of the enclosure to narrow the fault to a FRU, connection, or both. The LEDs also help you identify the location of a FRU reporting a fault.

Use SMU to verify any faults found while viewing the LEDs. SMU is also a good tool to use in determining where the fault is occurring if the LEDs cannot be viewed due to the location of the system. SMU provides you with a visual representation of the system and where the fault is occurring. It can also provide more detailed information about FRUs, data, and faults.

Review the event logs

The event logs record all system events. It is very important to review the logs, not only to identify the fault, but also to search for events that might have caused the fault to occur. For example, a host could lose connectivity to a virtual disk if a user changes channel settings without taking the storage resources assigned to it into consideration. In addition, the type of fault can help you isolate the problem to hardware or software.

The Log Collector utility allows customers to gather log information for use during support calls. See the P2000 G3 Software Support/Documentation CD that ships with your product for details.

Isolate the fault

Occasionally it might become necessary to isolate a fault. This is particularly true with data paths, due to the number of components comprising the data path. For example, if a host-side data error occurs, it could be caused by any of the components in the data path: controller module, cable, or data host.

HP P2000 G3 FC MSA System User Guide 51

If the enclosure does not initialize

It may take up to two minutes for the enclosures to initialize. If the enclosure does not initialize:

• Perform a rescan.

• Power cycle the system.

• Make sure the power cord is properly connected, and check the power source that it is connected to.

• Check the event log for errors.

Correcting enclosure IDs

When installing a system with drive enclosures attached, the enclosure IDs might not agree with the physical cabling order. This is because the controller might have been previously attached to some of the same enclosures during factory testing and it attempts to preserve the previous enclosure IDs if possible. To correct this condition, make sure that both controllers are up, and perform a rescan using SMU or the CLI. This will reorder the enclosures, but can take up to two minutes for the enclosure IDs to be corrected.

To perform a rescan using the CLI, type the following command:

rescan

To rescan using SMU:

1. Verify that both controllers are operating normally.

2. In the Configuration View panel, right-click the system and select Tools > Rescan Disk Channels.

3. Click Rescan.

Diagnostic steps

This section describes possible reasons and actions to take when an LED indicates a fault condition. See

LED descriptions on page 65 for descriptions of all LED statuses.

Is the front panel Fault LED amber?

Answer Possible reasons Actions

No System functioning properly. No action required. Yes A fault condition exists. • Check the LEDs on the back of the controller to narrow

Yes A fault o ccurred.

If installing an I/O module FRU, the module has not gone online and likely failed its self-test.

the fault to a FRU, connection, or both.

• Check the event log for specific information regarding

the fault.

• Check the event log for specific information regarding

the fault.

• Isolate the fault.

• Contact an authorized service provider for assistance.

• Replace if necessary.

• If installing an I/O module FRU, try removing and

reinstalling the new I/O module, and check the event log for errors.

52 Troubleshooting

Is the controller back panel OK LED off?

Answer Possible reasons Actions

No System functioning properly. No action required.

Yes The controller module is not

powered on.

The controller module has failed.

• Check that the controller module is fully inserted and

latched in place, and that the enclosure is powered on.

• Check the event log for specific information regarding

the failure.

Is the controller back panel Fault/Service Required LED amber?

Answer Possible reasons Actions

No System functioning properly. No action required.

Yes (blinking)

One of the following errors occurred:

• Hardware-controlled

power-up error

• Cache flush error

• Cache self-refresh error

• Restart this controller from the other controller using

SMU or the CLI.

• Remove the controller and reinsert it.

• Contact an authorized service provider for assistance.

• Replace the controller.

Are both disk drive module LEDs off (Online/Activity and Fault/UID)?

Answer Possible reasons Actions

Yes • There is no power.

• The disk is offline.

• The disk is not configured.

Check that the disk drive is fully inserted and latched in place, and that the enclosure is powered on.

Is the disk drive module Fault/UID LED blinking amber?

Answer Possible reasons Actions

No, but the

Online/Activity LED is blinking.

Yes, and the

Online/Activity LED is off.

Yes, and the

Online/Activity LED is blinking.

The disk drive is rebuilding. No action required.

The disk drive is offline. A predictive failure alert may have been received for this device.

The disk drive is active, but a predictive failure alert may have been received for this device.

• Check the event log for specific information

regarding the fault.

• Isolate the fault.

• Contact an authorized service provider for

assistance.

• Check the event log for specific information

regarding the fault.

• Isolate the fault.

• Contact an authorized service provider for

assistance.

CAUTION: Do not remove a drive that

is rebuilding. Removing a drive might terminate the current operation and cause data loss.

HP P2000 G3 FC MSA System User Guide 53

Is a connected host port’s Host Link Status LED off?

Answer Possible reasons Acti ons

No System functioning properly. No action required.

(see Link LED note: page 68)

Yes The link is down. • Check cable connections and reseat if necessary.

• Inspect cables for damage.

• Swap cables to determine if fault is caused by a

defective cable. Replace cable if necessary.

• Verify that the switch, if any, is operating properly. If

possible, test with another port.

• Verify that the HBA is fully seated, and that the PCI slot is

powered on and operational.

• In SMU, review event logs for indicators of a specific

fault in a host data path component.

• Contact an authorized service provider for assistance.

• See Isolating a host-side connection fault on page 56.

Is a connected port’s Expansion Port Status LED off?

Answer Possible reasons Actions

No System functioning properly. No action required. Yes The link is down. • Check cable connections and reseat if necessary.

• Inspect cable for damage.

• Swap cables to determine if fault is caused by a

defective cable. Replace cable if necessary.

• In SMU, review event logs for indicators of a specific

fault in a host data path component.

• Contact an authorized service provider for assistance.

• See Isolating a controller module expansion port

connection fault on page 57.

Is a connected port’s Network Port Link Status LED off?

Answer Possible reasons Actions

No System functioning properly. No action required.

Yes The link is down. Use standard networking troubleshooting procedures to

isolate faults on the network.

54 Troubleshooting

Is the power supply’s Input Power Source LED off?

Answer Possible reasons Actions

No System functioning properly. No action required.

Yes The power supply is not

receiving adequate power.

• Verify that the power cord is properly connected and

check the power source it is connected to.

• Check that the power supply FRU is firmly locked into

position.

• Check the event log for specific information regarding

the fault.

• Isolate the fault.

• Contact an authorized service provider for assistance.

Is the power supply’s Voltage/Fan Fault/Service Required LED amber?

Answer Possible reasons Actions

No System functioning properly. No action required.

Yes The power supply unit or a fan

is operating at an unacceptable voltage/RPM level, or has failed.

When isolating faults in the power supply, remember that the fans in both modules receive power through a common bus on the midplane, so if a power supply unit fails, the fans continue to operate normally.

• Check that the power supply FRU is firmly locked into

position.

• Check that the power cable is connected to a power

source.

• Check that the power cable is connected to the power

supply module.

Controller failure in a single-controller configuration

Cache memory is flushed to CompactFlash in the case of a controller failure or power loss. During the write to CompactFlash process, only the components needed to write the cache to the CompactFlash are powered by the super-capacitor. This process typically takes 60 seconds per 1 Gbyte of cache. After the cache is copied to CompactFlash, the remaining power left in the super-capacitor is used to refresh the cache memory. While the cache is being maintained by the super-capacitor, the Cache Status LED flashes at a rate of 1/10 second off and 9/10 second on.

IMPORTANT: Transportable cache only applies to single-controller configurations. In dual controller

configurations, there is no need to transport a failed controller’s cache to a replacement controller because the cache is duplicated between the peer controllers.

HP P2000 G3 FC MSA System User Guide 55

If the controller has failed or does not start, is the Cache Status LED on/blinking?

Answer Actions

No, the Cache LED status is off, and the controller does not boot.

No, the Cache Status LED is off, and the controller boots.

Yes, at a strobe 1:10 rate - 1 Hz, and the controller does not boot.

Yes, at a strobe 1:10 rate - 1 Hz, and the controller boots.

Yes, at a blink 1:1 rate - 1 Hz, and the controller does not boot.

Yes, at a blink 1:1 rate - 1 Hz, and the controller boots.

Transporting cache

To preserve the existing data stored in the CompactFlash, you must transport the CompactFlash from the failed controller to a replacement controller using a procedure outlined in the HP P2000 G3 MSA System controller replacement instructions, shipped with the replacement controller. Failure to use this procedure will result in the loss of data stored in the cache module.

CAUTION: Remove the controller only after the copy process is complete, which is indicated by the

Cache Status LED being off.

If valid data is thought to be in Flash, see Transporting

cache; otherwise, replace the controller.

The system is flushing data to disks. If the problem persists, replace the controller.

See Transporting cache.

The system is flushing data to disks. If the problem persists, replace the controller.

See Transporting cache.

The system is flushing data to disks. If the problem persists, replace the controller.

Isolating a host-side connection fault

During normal operation, when a controller module host port is connected to a data host, the port’s host link status LED and host link activity LED are green. If there is I/O activity, the host activity LED blinks green. If data hosts are having trouble accessing the storage system, and you cannot locate a specific fault or cannot access the event logs, use the following procedure. This procedure requires scheduled downtime.

IMPORTANT: Do not perform more than one step at a time. Changing more than one variable at a time

can complicate the troubleshooting process.

Host-side connection troubleshooting featuring SFP transceivers

The procedure below applies to P2000 G3 MSA controller enclosures employing small form factor pluggable (SFP) transceiver connectors in 2/4/8Gb FC host interface ports.

1. Halt all I/O to the storage system.

2. Check the host activity LED.

If there is activity, halt all applications that access the storage system.

3. Remove the SFP and FC cable and inspect for damage.

4. Reseat the SFP and FC cable.

Is the host link status LED on?

• Yes – Monitor the status to ensure that there is no intermittent error present. If the fault occurs again, clean the connections to ensure that a dirty connector is not interfering with the data path.

• No – Proceed to the next step.

56 Troubleshooting

5. Move the SFP and FC cable to a port with a known good link status.

This step isolates the problem to the external data path (SFP, host cable, and host-side devices) or to the controller module port.

Is the host link status LED on?

• Yes – You now know that the SFP, host cable, and host-side devices are functioning properly. Return the SFP and cable to the original port. If the link status LED remains off, you have isolated the fault to the controller module’s port. Replace the controller module.

• No – Proceed to the next step.

6. Swap the SFP with the known good one.

Is the host link status LED on?

• Yes – You have isolated the fault to the SFP. Replace the SFP.

• No – Proceed to the next step.

7. Re-insert the original SFP and swap the cable with a known good one.

Is the host link status LED on?

• Yes – You have isolated the fault to the cable. Replace the cable.

• No – Proceed to the next step.

8. Verify that the switch, if any, is operating properly. If possible, test with another port.

9. Verify that the HBA is fully seated, and that the PCI slot is powered on and operational.

10. Replace the HBA with a known good HBA, or move the host side cable and SFP to a known good

HBA. Is the host link status LED on?

• Yes – You have isolated the fault to the HBA. Replace the HBA.

• No – It is likely that the controller module needs to be replaced.

11. Move the cable and SFP back to its original port.

Is the host link status LED on?

• No – The controller module’s port has failed. Replace the controller module.

• Yes – Monitor the connection for a period of time. It may be an intermittent problem, which can occur with SFPs, damaged cables, and HBAs.

Isolating a controller module expansion port connection fault

During normal operation, when a controller module’s expansion port is connected to a drive enclosure, the expansion port status LED is green. If the connected port’s expansion port LED is off, the link is down. Use the following procedure to isolate the fault.

This procedure requires scheduled downtime.

NOTE: Do not perform more than one step at a time. Changing more than one variable at a time can

complicate the troubleshooting process.

1. Halt all I/O to the storage system.

2. Check the host activity LED.

If there is activity, halt all applications that access the storage system.

3. Reseat the expansion cable, and inspect it for damage.

Is the expansion port status LED on?

• Yes – Monitor the status to ensure there is no intermittent error present. If the fault occurs again, clean the connections to ensure that a dirty connector is not interfering with the data path.

• No – Proceed to the next step.

4. Move the expansion cable to a port on the RAID enclosure with a known good link status.

This step isolates the problem to the expansion cable or to the controller module’s expansion port. Is the expansion port status LED on?

HP P2000 G3 FC MSA System User Guide 57

• Yes – You now know that the expansion cable is good. Return cable to the original port. If the expansion port status LED remains off, you have isolated the fault to the controller module’s expansion port. Replace the controller module.

• No – Proceed to the next step.

5. Move the expansion cable back to the original port on the controller enclosure.

6. Move the expansion cable on the drive enclosure to a known good expansion port on the drive

enclosure. Is the expansion port status LED on?

• Yes – You have isolated the problem to the drive enclosure’s port. Replace the expansion module.

• No – Proceed to the next step.

7. Replace the cable with a known good cable, ensuring the cable is attached to the original ports used

by the previous cable. Is the host link status LED on?

• Yes – Replace the original cable. The fault has been isolated.

• No – It is likely that the controller module needs to be replaced.

Isolating Remote Snap replication faults

Cabling for replication

Remote Snap replication is a disaster-recovery feature that performs batch replication of block-level data from a primary volume in one P2000 G3 MSA System controller enclosure to a secondary volume in the same system, or in a second, independent P2000 G3 MSA System controller enclosure. The second system can be located at the same site as the first system, or at a different site. See Connecting two storage

systems to replicate volumes on page 40 for host connection information concerning Remote Snap. Your

product’s installation instructions and cabling configuration guide provide additional information.

Replication setup and verification

After storage systems and hosts are cabled for replication, you can use SMU’s Replication Setup Wizard to prepare to use the Remote Snap feature. Optionally, you can use telnet to access the IP address of the controller module and access the Remote Snap feature using the CLI.

NOTE: Refer to the following manuals for more information on replication setup:

• See P2000G3MSA System SMU Reference Guide for procedures to setup and manage replications

• See P2000G3MSA System CLI Reference Guide for replication commands and syntax

• See P2000 G3 MSA System Event Descriptions Reference Guide for replication event reporting

Basic information for enabling the P2000 G3 MSA System controller enclosures for replication supplements the troubleshooting procedures that follow:

• Familiarize yourself with Remote Snap by reviewing the “Getting started” and “Using Remote Snap to

replicate volumes” chapters in the SMU guide.

• Use Wizards > Replication Setup Wizard to prepare to replicate an existing volume to another vdisk in

the primary system or a secondary system. Follow the wizard to select the primary volume, replication mode, and secondary volume, and to

confirm your replication settings. The wizard verifies the communication links between the primary and secondary systems. Once setup is successfully completed, you can initiate replication from SMU.

• For descriptions of replication-related events, see the Event Descriptions Reference Guide.

58 Troubleshooting

Diagnostic steps for replication setup

Can you successfully use the Remote Snap feature?

Answer Possible reasons Actions

Yes System functioning properly. No action required.

No Remote Snap is not licensed on

each controller enclosure used for replication.

Can you view information about remote links?

Answer Possible reasons Actions

Yes System functioning properly. No action required. No Communication link is down. • Check cable connections and reseat if necessary.

Verify that the optional software feature is licensed on each storage system used for replication.

• In SMU’s Configuration View panel, right-click the system,

and select View > Overview. Within the System Overview table, select the Licensed Features component to display the status of licensed features.

• If the Replication property is not enabled, obtain and

install a valid license for Remote Snap.

NOTE: Remote Snap is not supported by P2000 G3

SAS MSA System controllers.

• Inspect cable for damage.

• Swap cables to determine if fault is caused by a defective

cable; replace cable if necessary.

• In SMU, review event logs for indicators of a specific fault

in a host or replication data path component.

• In SMU’s Configuration View panel, right-click the remote

system, and select Tools > Check Remote System Link. Click Check Links.

Can you create a replication set?

Answer Possible reasons Actions

Yes System functioning properly. No action required.

No Unable to select the primary

volume (the volume containing the data to replicate)?

• In SMU’s Configuration View panel, expand vdisk entries

to show secondary volumes.

• In SMU, review event logs for indicators of a specific fault

in a host or replication data path component.

HP P2000 G3 FC MSA System User Guide 59

Answer Possible reasons Actions

No Unable to select the replication

mode?

No Unable to select the secondary

volume (the destination volume on the vdisk to which you will replicate data from the primary volume)?

• In SMU, review event logs for indicators of a specific fault

in a host or replication data path component.

• In SMU’s Configuration View panel, right-click a

subordinate volume, and select View > Overview to view links.

• Local Replication mode replicates to a secondary volume

residing in the local storage system. Verify selection of a valid local volume on vdisk.

• Remote Replication mode replicates to a secondary

volume residing in an independent storage system:

• Verify selection of valid remote vdisk

• Verify selection of valid remote volume on vdisk

• Verify valid IP address of remote system’s network port

• Verify user name with Manage role on remote system

• Verify user’s password on remote system

NOTE: If the remote system has not been added, it

cannot be selected.

• In SMU, review event logs for indicators of a specific fault

in a replication data path component.

• Verify valid specification of the secondary volume

according to either of the following criteria:

• Creation of new volume on vdisk

• Selection of replication-prepared volume

• In SMU’s Configuration View panel, right-click the

secondary volume, and select View > Overview to display the Replication Volume Overview table.

• Verify the type and numbering of ports used for the inter-system link

• Verify that the vdisk volume has sufficient space to accommodate replicated data

No Communication link is down. See actions described in Can you view information about

Can you replicate a volume?

Answer Possible reasons Actions

Yes System functioning properly. No action required.

No Remote Snap is not licensed on

each controller enclosure used for replication.

No Nonexistent replication set. • Determine existence of primary or secondary volumes.

60 Troubleshooting

remote links? on page 59.

See actions described in Can you successfully use the Remote

Snap feature? on page 59.

• If a replication set has not been successfully created, use

SMU’s Replication Setup Wizard to create one.

• In SMU, review event logs for indicators of a specific fault

in a replication data path component.

Answer Possible reasons Actions

No Network error occurred during

in-progress replication.

No Communication link is down. See actions described in Can you view information about

Can you view a replication image?

Answer Possible reasons Actions

Yes System functioning properly. No action required. No Nonexistent replication image. • In SMU’s Configuration View panel, expand vdisks and

• In SMU, review event logs for indicators of a specific fault

in a replication data path component.

• In SMU’s Configuration View panel, right-click the

secondary volume, and select View > Overview to display the Replication Volume Overview table:

• Check for replication interruption (suspended) status

• Check for inconsistent status

•Check for offline status

• Replications that enter the suspended state must be

resumed manually.

remote links? on page 59.

subordinate volumes to reveal the existence of a replication image or images.

• If a replication image has not been successfully created,

use SMU to create one as described in the “Using Remote Snap to replicate volumes” topic within the SMU guide.

No Communication link is down. See actions described in Can you view information about

remote links? on page 59.

Can you view remote systems?

Answer Possible reasons Actions

Yes System functioning properly. No action required.

No Non-existent replication set. See actions described in Can you replicate a volume? on

page 60.

No Communication link is down. See actions described in Can you view information about

remote links? on page 59.

Resolving voltage and temperature warnings

1. Check that all of the fans are working by making sure each power supply’s Voltage/Fan Fault/Service

Required LED is off or by using SMU to check for yellow yield icon hardware warnings. (In the Configuration View panel, right-click the enclosure and select View > Overview.)

2. Make sure that all modules are fully seated in their slots and that their latches are locked.

3. Make sure that no slots are left open for more than two minutes.

If you need to replace a module, leave the old module in place until you have the replacement or use a blank module to fill the slot. Leaving a slot open negatively affects the airflow and can cause the enclosure to overheat.

4. Try replacing each power supply one at a time.

5. Replace the controller modules one at a time.

HP P2000 G3 FC MSA System User Guide 61

Sensor locations

The storage system monitors conditions at different points within each enclosure to alert you to problems. Power, cooling fan, temperature, and voltage sensors are located at key points in the enclosure. In each controller module and expansion module, the enclosure management processor (EMP) monitors the status of these sensors to perform SCSI enclosure services (SES) functions.

The following sections describe each element and its sensors.

Power supply sensors

Each enclosure has two fully redundant power supplies with load-sharing capabilities. The power supply sensors described in the following table monitor the voltage, current, temperature, and fans in each power supply. If the power supply sensors report a voltage that is under or over the threshold, check the input voltage.

Table 8 Power supply sensors

Description Event/Fault ID LED condition

Power supply 1 Voltage, current, temperature, or fan fault

Power supply 2 Voltage, current, temperature, or fan fault

Cooling fan sensors

Each power supply includes two fans. The normal range for fan speed is 4,000 to 6,000 RPM. When a fan’s speed drops below 4,000 RPM, the EMP considers it a failure and posts an alarm in the storage system’s event log. The following table lists the description, location, and alarm condition for each fan. If the fan speed remains under the 4,000 RPM threshold, the internal enclosure temperature may continue to rise. Replace the power supply reporting the fault.

Table 9 Cooling fan sensor descriptions

Description Location Event/Fault ID LED condition

Fan 1 Power supply 1 < 4,000 RPM

Fan 2 Power supply 1 < 4,000 RPM

Fan 3 Power supply 2 < 4,000 RPM

Fan 4 Power supply 2 < 4,000 RPM

During a shutdown, the cooling fans do not shut off. This allows the enclosure to continue cooling.

Temperature sensors

Extreme high and low temperatures can cause significant damage if they go unnoticed. Each controller module has six temperature sensors. Of these, if the CPU or FPGA (Field Programmable Gate Array) temperature reaches a shutdown value, the controller module is automatically shut down. Each power supply has one temperature sensor.

When a temperature fault is reported, it must be remedied as quickly as possible to avoid system damage. This can be done by warming or cooling the installation location.

Table 10 Controller module temperature sensors

Description Normal operating

range

Warning operating range

Critical operating range

Shutdown values

CPU temperature 3–88°C0–3°C,

FPGA temperature 3–97°C0–3°C,

Onboard temperature 1 0–70°CNoneNoneNone

62 Troubleshooting

88–90°C

97–100°C

> 90°C0°C

100 °C

None 0°C

105°C

Table 10 Controller module temperature sensors (continued)

Description Normal operating

range

Onboard temperature 2 0–70°CNoneNoneNone

Onboard temperature 3 (Capacitor temperature)

CM temperature 5–50°C

0–70°CNoneNoneNone

When a power supply sensor goes out of range, the Fault/ID LED illuminates amber and an event is logged to the event log.

Table 11 Power supply temperature sensors

Description Normal operating range

Power Supply 1 temperature –10–80°C

Power Supply 2 temperature –10–80°C

Power supply module voltage sensors

Power supply voltage sensors ensure that an enclosure’s power supply voltage is within normal ranges. There are three voltage sensors per power supply.

Table 12 Voltage sensor descriptions

Warning operating range

≤ 5°C, ≥ 50°C

Critical operating range

≤ 0°C, ≥ 55°C

Shutdown values

None

Sensor Event/Fault LED condition

Power supply 1 volta ge, 12V < 11. 0 0 V

> 13.00V

Power supply 1 voltage, 5V < 4.00V

> 6.00V

Power supply 1 voltage, 3.3V < 3.00V

> 3.80V

HP P2000 G3 FC MSA System User Guide 63

64 Troubleshooting

A LED descriptions

P2000

1 2 3

Left ear Right ear

P2000

Left ear Right ear

Front panel LEDs

312

Table 13 LEDs — HP P2000 G3 MSA Systems controller enclosure front panels

LED Description Definition

1 Enclosure ID Green — On

Enables you to correlate the enclosure with logical views presented by management software. Sequential enclosure ID numbering of controller enclosures begins with the integer 1. The enclosure ID for an attached drive enclosure is nonzero.

2 Disk drive Online/Activity See Disk drive LEDs on page 66.

3 Disk drive Fault/UID See Disk drive LEDs on page 66.

4 Unit Identification (UID) Blue — Identified.

Off — Identity LED off.

5 Heartbeat Green — The enclosure is powered on with at least one power

supply operating normally. Off — Both power supplies are off; the system is powered off.

6 Fault ID Amber — Fault condition exists. The event has been identified, but

the problem needs attention. Off — No fault condition exists.

HP P2000 G3 FC MSA System User Guide 65

Disk drive LEDs

3.5" LFF disk drive

2.5" SFF disk drive

Table 14 LEDs — Disk drive LEDs

LED Description

1 Fault/UID (amber/blue)

2Online/Activity (green)

Table 15 LEDs — Disk drive combinations

Online/Activity (green) Fault/UID (amber/blue) Description

On Off Normal operation. The drive is online, but it is not

currently active.

Blinking irregularly Off The drive is active and operating normally.

Off Amber; blinking regularly

(1 H z )

On Amber; blinking regularly

(1 H z )

Blinking irregularly Amber; blinking regularly

(1 H z )

Off Amber; solid

Offline; the drive is not being accessed. A predictive failure alert may have been received for this device. Further investigation is required.

Online; possible I/O activity. A predictive failure alert may have been received for this device. Further investigation is required.

The drive is active, but a predictive failure alert may have been received for this drive. Further investigation is required.

Offline; no activity. A failure or critical fault condition has been identified for this drive.

Off Blue; solid Offline. The drive has been selected by a

On or blinking Blue; solid The controller is driving I/O to the drive, and it has

66 LED descriptions

management application (SMU).

been selected by a management application (SMU).

Table 15 LEDs — Disk drive combinations

SERVICE

FC 2

FC 1

CACHE

CLI CLI HOST

2,4G

SERVICE

FC 2

FC 1

CACHE

CLI CLI HOST

2,4G

6Gb/s

ACT

LINK

ACT

LINK

13456

7 8 9

Online/Activity (green) Fault/UID (amber/blue) Description

Blinking regularly (1 Hz) Off

CAUTION: Do not remove the drive.

Removing a drive may terminate the current operation and cause data loss. The drive is rebuilding.

Off Off Either there is no power, the drive is offline, or the

drive is not configured.

This Fault/UID state can indicate that the disk is a leftover. The fault may involve metadata on the disk rather than the disk itself.

See the Clearing disk metadata topic in the SMU reference guide or online help.

Rear panel LEDs

P2000 G3 FC MSA System SFF and P2000 G3 FC MSA System LFF

Table 16 LEDs — HP P2000 G3 FC MSA System LFF and SFF rear panel

LED Description Definition

1 Power supply LEDs See Power supply LEDs on page 71.

2 Host 2/4/8 Gb FC

Link Status/ Link Activity

3 OK to Remove Off — The controller module is not prepared for removal.

4 Unit Locator Off — Normal operation.

5 FRU OK Off — Controller module is not OK.

6 Fault/Service Required Amber — A fault has been detected or a service action is required.

7 Network Port Activity Off — The Ethernet link has no I/O activity.

8 Network Port Link Status Off — The Network port is not connected or the link is down.

Green — The port is connected and the link is up.

2,4G LED illuminates — link speed is 2 or 4-Gbps 8G LED illuminates — link speed is 8-Gbps

Both LEDs off — link speed is 1-Gbps

Blink — no link detected.

Blue — The controller module is prepared for removal.

Blinking white — Physically identifies the controller module.

Blinking green — System is booting. Green — Controller module is operating normally.

Blinking amber — Hardware-controlled power-up or a cache flush or restore error.

Blinking green — The Ethernet link has I/O activity.

Green — The Network link is up.

HP P2000 G3 FC MSA System User Guide 67

Table 16 LEDs — HP P2000 G3 FC MSA System LFF and SFF rear panel

LED Description Definition

9 Cache Status Green — Cache is dirty (contains unwritten data) and operation is

normal. Off — In a working controller, cache is clean (contains no unwritten data). Blinking green — A CompactFlash flush or cache self-refresh is in progress. Indicates cache activity (See also If the controller has

failed or does not start, is the Cache Status LED on/blinking? on

page 56).

If the LED is blinking evenly, a cache flush is in progress. When a controller module loses power and write cache is dirty (contains data that has not been written to disk), the super-capacitor pack provides backup power to flush (copy) data from write cache to CompactFlash memory. When cache flush is complete, the cache transitions into self-refresh mode.

If the LED is blinking momentarily slowly, the cache is in a self-refresh mode. In self-refresh mode, if primary power is restored before the backup power is depleted (3–30 minutes, depending on various factors), the system boots, finds data preserved in cache, and writes it to disk. This means the system can be operational within 30 seconds, and before the typical host I/O time-out of 60 seconds, at which point system failure would cause host-application failure. If primary power is restored after the backup power is depleted, the system boots and restores data to cache from CompactFlash, which can take about 90 seconds.

The cache flush and self-refresh mechanism is an important data protection feature; essentially four copies of user data are preserved: one in each controller’s cache and one in each controller’s CompactFlash.

10 Expansion Port Status Off — The port is empty or the link is down.

The 8 Gb SFP modules do not support 1 Gbps link speeds.

IMPORTANT: Early versions of the P2000 G3 MSA System controller modules show network port LED

labels in reversed position: LINK is shown on the left and ACT is shown on the right. On such units, the LED labeled LINK reports ACT behavior and the LED labeled ACT reports LINK behavior.

NOTE: Once a Link Status LED is lit, it remains so, even if the controller is shutdown via SMU or CLI.

When a controller is shutdown or otherwise rendered inactive —its Link Status LED remains illuminated—falsely indicating that the controller can communicate with the host. Though a link exists between the host and the chip on the controller, the controller is not communicating with the chip. To reset the LED, the controller must be properly power-cycled (see Accessing SMU on page 49).

D2700 6Gb drive enclosure

P2000 G3 MSA System controllers support D2700 6Gb drive enclosures. For information about P2000G3MSA System products, visit http://www.hp.com/go/p2000 your drive enclosure, select Support > HP Support & Drivers from the right side of the page, select your product name, and select Manuals.

On — The port is connected and the link is up.

. Select Related products, select

68 LED descriptions

P2000 6Gb 3.5” 12-drive enclosure

IN OUT

3 4 5

Table 17 LEDs — HP P2000 6Gb rear panel

LED Description Definition

1 Power supply LEDs See Power supply LEDs on page 71.

2 Unit Locator Off — Normal operation.

3 OK to Remove Not implemented.

4 Fault/Service Required Amber — A fault has been detected or a service action is required.

Blinking white— Physically identifies the expansion module.

Blinking amber — Hardware-controlled powerup or a cache flush or restore error.

5 FRU OK Green — Expansion module is operating normally.

6 SAS In Port Status Green — Port link is up and connected.

7 SAS Out Port Status Green — Port link is up and connected.

MSA70 3Gb drive enclosure

A P2000 G3 MSA System controller can also be attached to an MSA70 3Gb drive enclosure running firmware version 2.18 or later. For information about the MSA70 3Gb drive enclosure, including detailed steps to upgrade the firmware, see the HP StorageWorks 70 Modular Smart Array Enclosure User Guid e located on the MSA2000 G2 Softw are Support/Documentation CD shipped with your product, or at

http://hp.com/support/manuals

Blinking green — System is booting. Off — Expansion module is not OK.

Off — Port is empty or link is down.

HP P2000 G3 FC MSA System User Guide 69

MSA2000 3Gb 3.5” 12-drive enclosure

1 2

4356 7

Table 18 LEDs — HP MSA2000 3Gb rear panel

LED Description Definition

1 Power supply LEDs See Power supply LEDs on page 71.

2 Unit Locator Off — Normal operation.

3 SAS In Port Status Green — Port link is up and connected.

Blinking white— Physically identifies the expansion module.

Off — Port is empty or link is down.

4 OK to Remove Not implemented.

5 Fault/Service Required Amber — A fault has been detected or a service action is required.

Blinking amber — Hardware-controlled powerup or a cache flush or restore error.

6 FRU OK Green — Expansion module is operating normally.

Blinking green — System is booting. Off — Expansion module is not OK.

7 SAS Out Port Status Green — Port link is up and connected.

Off — Port is empty or link is down.

70 LED descriptions

Power supply LEDs

Power redundancy is achieved through two independent load-sharing power supplies. In the event of a power supply failure, or the failure of the power source, the storage system can operate continuously on a single power supply. Greater redundancy can be achieved by connecting the power supplies to separate circuits. DC power supplies are equipped with a power switch. AC power supplies may or may not have a power switch (model shown below has no power switch). Whether a power supply has a power switch is significant to powering on/off.

AC model DC model

Table 19 LEDs — HP P2000 G3 MSA System power supply units — rear panel

LED Description Definition

1 I nput Source Power Good Green — Power is on and input voltage is normal.

Off — Power is off or input voltage is below the minimum threshold.

2 Voltage/Fan Fault/Service Required Amber — Output voltage is out of range or a fan is operating

below the minimum required RPM.

Off — Output voltage is normal.

NOTE: See Powering on/powering off on page 33 for information on power-cycling enclosures.

HP P2000 G3 FC MSA System User Guide 71

72 LED descriptions

B Environmental requirements and specifications

Safety requirements

Install the system in accordance with the local safety codes and regulations at the facility site. Follow all cautions and instructions marked on the equipment. Also, refer to the documentation included with your product’s ship kit.

Site requirements and guidelines

The following sections provide requirements and guidelines that you must address when preparing your site for the installation.

When selecting an installation site for the system, choose a location not subject to excessive heat, direct sunlight, dust, or chemical exposure. These conditions greatly reduce the system’s longevity and might void your warranty.

Site wiring and AC power requirements

The following are required for all installations using AC power supplies:

• All AC mains and supply conductors to power distribution boxes for the rack-mounted system must be

enclosed in a metal conduit or raceway when specified by local, national, or other applicable government codes and regulations.

• Ensure that the voltage and frequency of your power source match the voltage and frequency inscribed

on the equipment’s electrical rating label.

• To ensure redundancy, provide two separate power sources for the enclosures. These power sources

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

• The system requires voltages within minimum fluctuation. The customer-supplied facilities’ voltage must

maintain a voltage with not more than suitable surge protection.

• Site wiring must include an earth ground connection to the AC power source. The supply conductors

and power distribution boxes (or equivalent metal enclosure) must be grounded at both ends.

• Power circuits and associated circuit breakers must provide sufficient power and overload protection. To

prevent possible damage to the AC power distribution boxes and other components in the rack, use an external, independent power source that is isolated from large switching loads (such as air conditioning motors, elevator motors, and factory loads).

± 5 percent fluctuation. The customer facilities must also provide

Site wiring and DC power requirements

The following are required for all installations using DC power supplies:

• All DC mains and supply conductors to power distribution boxes for the rack-mounted system must

comply with local, national, or other applicable government codes and regulations.

• Ensure that the voltage of your power source matches the voltage inscribed on the equipment’s

electrical label.

• To ensure redundancy, provide two separate power sources for the enclosures. These power sources

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

• The system requires voltages within minimum fluctuation. The customer-supplied facilities’ voltage must

maintain a voltage within the range specified on the equipment’s electrical rating label. The customer facilities must also provide suitable surge protection.

• Site wiring must include an earth ground connection to the DC power source. Grounding must comply

with local, national, or other applicable government codes and regulations.

• Power circuits and associated circuit breakers must provide sufficient power and overload protection.

HP P2000 G3 FC MSA System User Guide 73

Weight and placement guidelines

Refer to Physical requirements on page 75 for detailed size and weight specifications.

• The weight of an enclosure depends on the number and type of modules installed.

• Ideally, use two people to lift an enclosure. However, one person can safely lift an enclosure if its

weight is reduced by removing the power supply modules and disk drive modules.

• Do not place enclosures in a vertical position. Always install and operate the enclosures in a horizontal

orientation.

• When installing enclosures in a rack, make sure that any surfaces over which you might move the rack

can support the weight. To prevent accidents when moving equipment, especially on sloped loading docks and up ramps to raised floors, ensure you have a sufficient number of helpers. Remove obstacles such as cables and other objects from the floor.

• To prevent the rack from tipping, and to minimize personnel injury in the event of a seismic occurrence,

securely anchor the rack to a wall or other rigid structure that is attached to both the floor and to the ceiling of the room.

Electrical guidelines

• These enclosures work with single-phase power systems having an earth ground connection. To reduce

the risk of electric shock, do not plug an enclosure 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.

• Enclosures are 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 the enclosures. 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.

Ventilation requirements

Refer to Environmental requirements on page 76 for detailed environmental requirements.

• Do not block or cover ventilation openings at the front and rear of an enclosure. Never place an

enclosure near a radiator or heating vent. Failure to follow these guidelines can cause overheating and affect the reliability and warranty of your enclosure.

• Leave a minimum of 6 inches (15 cm) at the front and back of each enclosure to ensure adequate

airflow for cooling. No cooling clearance is required on the sides, top, or bottom of enclosures.

• Leave enough space in front and in back of an enclosure to allow access to enclosure components for

servicing. Removing a component requires a clearance of at least 15 inches (37 cm) in front of and behind the enclosure.

Cabling requirements

• Keep power and interface cables clear of foot traffic. Route cables in locations that protect the cables

from damage.

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

interference.

• Stay within the cable length limitations.

Management host requirements

A local management host with at least one serial port connection is recommended for the initial installation and configuration of a controller enclosure. After you configure one or both of the controller modules with an Internet Protocol (IP) address, you then use a remote management host on an Ethernet network to configure, manage, and monitor.

74 Environmental requirements and specifications

NOTE: Connections to this device must be made with shielded cables – grounded at both ends – with

metallic RFI/EMI connector hoods, in order to maintain compliance with FCC Rules and Regulations.

Physical requirements

The floor space at the installation site must be strong enough to support the combined weight of the rack, controller enclosures, drive enclosures (expansion), and any additional equipment. The site also requires sufficient space for installation, operation, and servicing the enclosures, and sufficient ventilation to allow a free flow of air to all enclosures.

Table 20 and Table 21 list enclosure dimensions and weights. Weights are based on an enclosure having

a full complement of disk drives, two controller or expansion modules, and two power supplies installed. “2U12” denotes the LFF enclosure and “2U24” denotes the SFF enclosure. The SFF is further delineated by the standard-depth 2U24 and the new reduced-depth (short) 2U24.

Table 21 provides weight data for P2000 G3 controller enclosures and select drive enclosures. For

information about other HP MSA drive enclosures that may be cabled to these systems (e.g., MSA70 or D2700), check Quickspecs, which can be found from your HP MSA products page

http://www.hp.com/go/msa

Table 20 Rackmount enclosure dimensions

Specifications Rackmount

2U Height (y-axis) 3.5 inches (8.9 cm)

. Select your product. Quickspecs links are located on the right.

Width (x-axis):

• Chassis only

• Chassis with bezel ear caps

Depth (z-axis): SFF standard-depth drive enclosure (2U24)

• Back of chassis ear to controller latch

• Front of chassis ear to back of cable bend

SFF reduced-depth drive enclosure (2U24)

• Back of chassis ear to controller latch

• Front of chassis ear to back of cable bend

LFF drive enclosure (2U12)

• Back of chassis ear to controller latch

• Front of chassis ear to back of cable bend

Table 21 Rackmount enclosure weights

17.6 inches (44.7 cm)

18.9 inches (47.9 cm)

20.7 inches (52.6 cm)

23.6 inches (59.9 cm)

19.9 inches (50.5 cm)

22.8 inches (57.9 cm)

23.7 inches (60.2 cm)

26.4 inches (67.1 cm)

Specifications Rackmount

P2000 G3 MSA SFF controller enclosure (standard)

• Chassis with FRUs (no disks)

• Chassis with FRUs (including disk)

1, 2

1, 3

21.4 lb (9.7 kg) [chassis]

46.4 lb (21.0 kg)

58.4 lb (26.5 kg)

P2000 G3 MSA SFF controller enclosure (reduced)

• Chassis with FRUs (no disks)

• Chassis with FRUs (including disk)

P2000 G3 MSA LFF controller enclosure

• Chassis with FRUs (no disks)

• Chassis with FRUs (including disks)

1, 2

1, 3

1, 2

1, 3

19.0 lb (8.6 kg) [chassis]

44.0 lb (19.9 kg)

56.0 lb (25.4 kg)

22.0 lb (9.9 kg) [chassis]

47.0 lb ( 21.3 kg)

68.0 lb (30.8 kg)

HP P2000 G3 FC MSA System User Guide 75

Table 21 Rackmount enclosure weights

Specifications Rackmount

MSA2000 3.5” 12-drive enclosure (12 di sk s)

• Chassis with FRUs (no disks)

• Chassis with FRUs (including disks)

P2000 6Gb 3.5” drive enclosure (12 di sk s)

• Chassis with FRUs (no disks)

• Chassis with FRUs (including disks)

Weights shown are nominal, and subject to variances.

Weights may vary due to different power supplies, IOMs, and differing calibrations between scales.

Weights may vary due to actual number and type of disk drives (SAS, SATA, SSD) installed.

1, 2

Environmental requirements

Table 22 Operating environmental specifications

Specification Range

Altitude To 10,000 feet (3,000 meters)

Temperature* 41ºF to 104ºF (5ºC to 40ºC)

Humidity 10% to 90% RH up to 104ºF (40ºC) non-condensing

Shock 5.0 g, 11 ms, ½ sine pulses, X, Y, Z

1, 3

22.0 lb (9.9 kg) [chassis]

47.0 lb ( 21.3 kg)

68.0 lb (30.8 kg)

22.0 lb (9.9 kg) [chassis]

47.0 lb ( 21.3 kg)

68.0 lb (30.8 kg)

Vibration (Shaped spectrum)

5 Hz to 500 Hz, 0.114 G

* Temperature is de-rated by 3.6ºF (2ºC) for every 3,281 feet (1 km) above sea level.

Table 23 Non-operating environmental specifications

Specification Range

Altitude To 39,370 feet (12,000 meters)

Temperature -40ºF to 158ºF (-40ºC to 70ºC)

Humidity Up to 93% RH at 104ºF (40ºC) non-condensing

Shock 15.0 g, 11 ms, ½ sine pulses, X, Y, Z

Vibration (Shaped spectrum)

2.8 Hz to 365.4 Hz, 0.852 G

2.8 Hz to 365.4 Hz, 1.222 G

Electrical requirements

Site wiring and power requirements

Each enclosure has two power supply modules for redundancy. If full redundancy is required, use a separate power source for each module. The AC power supply unit in each power supply module is auto-ranging and is automatically configured to an input voltage range from 88–264 VAC with an input frequency of 47–63 Hz. The power supply modules meet standard voltage requirements for both U.S. and international operation. The power supply modules use standard industrial wiring with line-to-neutral or line-to-line power connections.

total X, Y, Z

rms

total (horizontal)

total (vertical)

76 Environmental requirements and specifications

Power cord requirements

Each enclosure equipped with AC power supply modules requires two AC power cords that are appropriate for use in a typical outlet in the destination country. Each power cord connects one of the power supply modules to an independent, external power source. To ensure power redundancy, connect the two suitable power cords to two separate circuits; for example, to one commercial circuit and one uninterruptible power source (UPS).

HP P2000 G3 FC MSA System User Guide 77

78 Environmental requirements and specifications

C Electrostatic discharge

Preventing electrostatic discharge

To prevent damaging the system, be aware of the precautions you need to follow when setting up the system or handling parts. A discharge of static electricity from a finger or other conductor may damage system boards or other static-sensitive devices. This type of damage may reduce the life expectancy of the device.

To prevent electrostatic damage:

• Avoid hand contact by transporting and storing products in static-safe containers.

• Keep electrostatic-sensitive parts in their containers until they arrive at static-protected workstations.

• Place parts in a static-protected area before removing them from their containers.

• Avoid touching pins, leads, or circuitry.

• Always be properly grounded when touching a static-sensitive component or assembly.

Grounding methods to prevent electrostatic discharge

Several methods are used for grounding. Use one or more of the following methods when handling or installing electrostatic-sensitive parts:

• Use a wrist strap connected by a ground card to a grounded workstation or computer chassis. Wrist

straps are flexible straps with a minimum of 1 megohm (± 10 percent) resistance in the ground cords. To provide proper ground, wear the strap snug against the skin.

• Use heel straps, toe straps or boot straps at standing workstations. Wear the straps on both feet when

standing on conductive floors or dissipating floor mats.

• Use conductive field service tools.

• Use a portable field service kit with a folding static-dissipating work mat.

If you do not have any of the suggested equipment for proper grounding, have an authorized reseller install the part.

For more information on static electricity or assistance with product installation, contact an authorized reseller.

HP P2000 G3 FC MSA System User Guide 79

80 Electrostatic discharge

Index

Numerics

2U12

large form factor (LFF) enclosure

2U24

small form factor (SFF) enclosure

accessing

CLI (command-line interface) SMU (storage management utility) web-posted documentation

audience

cables

Ethernet FCC compliance statement Fibre Channel routing requirements SAS expansion cable requirements shielded USB for CLI

cabling

connecting controller and drive enclosures direct attach configurations switch attach configurations to enable Remote Snap replication

cache

read ahead self-refresh mode write-through

clearance requirements

service ventilation

command-line interface (CLI)

connecting USB cable to CLI port using to set controller IP addresses

CompactFlash

transporting

components

controller module face plate

P2000 G3 FC MSA System

P2000 G3 MSA Systems

39, 75

P2000 G3 FC MSA System

rear panel

AC PSU CLI port (mini-USB) DC power switch DC PSU FC ports (host interface/replication) network port SAS expansion port service port

19 19

supported drive enclosures

D2700 6Gb drive enclosure MSA2000 3Gb drive enclosure MSA70 3Gb drive enclosure P2000 6Gb drive enclosure

configuring

direct attach configurations switch attach configurations

connections

verify

console requirement controller enclosures

connecting to data hosts connecting to remote management hosts

conventions

document

data hosts

defined optional software system requirements

DHCP

server

disk drive

slot numbering

document

conventions prerequisite knowledge related documentation

documentation, HP web site

LFF enclosure SFF enclosure

electromagnetic compatibility (EMC) 73

electrostatic discharge

grounding methods precautions

enclosure

cabling dimensions IDs, correcting initial configuration input frequency requirement input voltage requirement installation checklist site requirements troubleshooting web-browser based configuring and provisioning weight

Ethernet cables

requirements

HP P2000 G3 FC MSA System User Guide 81

faults

isolating

expansion port connection fault host-side connection methodology

help, obtaining 13

host interface ports

FC host interface protocol

loop topology point-to-point protocol SFP transceiver

customer self-repair (CSR) product warranty related documentation Subscriber’s choice web site technical support

web sites humidity non-operating range humidity operating range

MSA2000 3Gb rear panel

Fault/Service Required FRU OK OK to Remove Power supply SAS In Port Status SAS Out Port Status Unit Locator

P2000 G3 6Gb rear panel

Fault/Service Required FRU OK OK to Remove Power supply SAS In Port Status SAS Out Port Status Unit Locator

local management host requirement

MPIO DSM, obtaining 37

non-operating ranges, environmental 76

IDs, correcting for enclosure 52

installing enclosures

installation checklist IP addresses

setting using CLI

setting using DHCP

LEDs

disk drive

Fault/UID Online/Activity

enclosure front panel

Enclosure ID Fault ID Heartbeat Unit Identification (UID)

P2000 G3 MSA System

FC rear panel

power supply unit

Input Source Power Good Voltage/Fan Fault/Service Required

supported drive enclosures (expansion)

Cache Status Expansion Port Status Fault/Service Required FRU OK Host Link Status/Activity Network Port Activity Network Port Link Status OK to Remove Power supply Unit Locator

operating ranges, environmental 76

P2000 Family SCSI Enclosure Services (SES) driver 37

physical requirements power cord requirements power cycle

power off power on

power supply

AC power requirements DC power requirements site wiring requirements

prerequisite knowledge

34, 35 33, 35

73 73 73

regulatory compliance

notices

shielded cables related documentation requirements

cabling clearance Ethernet cables host system physical ventilation

RFI/EMI connector hoods

39, 75

safety precautions 73

sensors

locating

82 Index

power supply 62

temperature

voltage shock non-operating range shock operating range site planning

EMC

local management host requirement

physical requirements

safety precautions SMU

accessing web-based management interface

defined

getting started

Remote Snap replication

storage system configuring and provisioning storage system setup

configuring

provisioning

replicating Subscriber’s choice, HP super-capacitor pack switch attach configurations

technical support, HP 13

temperature non-operating range temperature operating range troubleshooting

controller failure, single controller configuration

correcting enclosure IDs

enclosure does not initialize

expansion port connection fault

host-side connection fault

Remote Snap replication faults

using system LEDs

ventilation requirements 74

vibration non-operating range vibration operating range

warnings

rack stability

voltage and temperature web sites

HP documentation

HP Subscriber’s choice

HP P2000 G3 FC MSA System User Guide 83

84 Index

HP P2000 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

HP P2000 G3 FC MSA System User Guide

Contents

Figures

Tables

About this guide

Intended audience

Prerequisites

Related documentation

Document conventions and symbols

Rack stability

HP technical support

Customer self repair

Product warranties

Subscription service

HP websites

Documentation feedback

Features and benefits

Front panel components

Disk drive bay numbers

Rear panel components

D2700 6Gb drive enclosure

P2000 6Gb 3.5" 12-drive enclosure

MSA70 3Gb drive enclosure

MSA2000 3Gb 3.5" 12-drive enclosure

Cache

Transportable CompactFlash

Super-capacitor pack

Installation checklist

Connecting controller and drive enclosures

Testing enclosure connections

Powering on/powering off

4 Connecting hosts

Host system requirements

Connecting the enclosure to data hosts

Connecting switch attach configurations

Connecting remote management hosts

Connecting two storage systems to replicate volumes

Updating firmware

5 Connecting to the controller CLI port

Device description

Obtaining IP values

6 Basic operation

Accessing SMU

Configuring and provisioning the storage system

CLI port connection

Fault isolation methodology

Diagnostic steps

Controller failure in a single-controller configuration

Isolating a host-side connection fault

Isolating a controller module expansion port connection fault

Isolating Remote Snap replication faults

Resolving voltage and temperature warnings

A LED descriptions

Front panel LEDs

Disk drive LEDs

Rear panel LEDs

B Environmental requirements and specifications

Safety requirements

Site requirements and guidelines

Management host requirements

Physical requirements

Environmental requirements

Electrical requirements

C Electrostatic discharge

Preventing electrostatic discharge

Grounding methods to prevent electrostatic discharge

Index