HP MSA 2040 Array family User Guide

HP MSA 2040
User Guide
Abstract
This document describes initial hardware setup for HP MSA 2040 controller enclosures, and is intended for use by storage system
administrators familiar with servers and computer networks, network administration, storage system installation and configuration,
storage area network management, and relevant protocols.
HP Part Number: 723983-002
Published: September 2013
Edition: 2
© Copyright 2013 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
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.
Acknowledgments
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Warranty
WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website:
http://www.hp.com/go/storagewarranty
Contents
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
MSA 2040 Storage models . . .
MSA 2040 SAN . . . . . . . .
MSA 2040 SAS . . . . . . . .
Features and benefits . . . . . . .
..
..
..
..
..
..
..
..
.
.
.
.
..
..
..
..
.
.
.
.
..
..
..
..
..
..
..
..
.
.
.
.
..
..
..
..
..
..
..
..
.
.
.
.
..
..
..
..
.
.
.
.
..
..
..
..
..
..
..
..
.
.
.
.
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
....
....
....
....
.
.
.
.
.
.
.
.
.
.
.
.
11
11
11
12
2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Front panel components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 Array SFF enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 Array LFF or supported drive expansion enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk drives used in MSA 2040 enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller enclosure—rear panel layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAN controller module—rear panel components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAS controller module—rear panel components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drive enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LFF drive enclosure — rear panel layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFF drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transportable CompactFlash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supercapacitor pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading to MSA 2040 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
13
14
14
15
16
16
16
17
17
17
18
18
3 Installing the enclosures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting controller and drive enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the MSA 2040 controller to the SFF drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the MSA 2040 controller to the LFF drive enclosure. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the MSA 2040 controller to mixed model drive enclosures. . . . . . . . . . . . . . . . . . . . . . . .
Cable requirements for MSA 2040 enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Testing enclosure connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Powering on/powering off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AC power supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC and AC power supplies equipped with a power switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect power cable to DC power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect power cord to legacy AC power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
19
20
20
20
20
27
27
27
28
29
29
29
4 Connecting hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Host system requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the enclosure to data hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fibre Channel protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10GbE iSCSI protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Gb iSCSI protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting direct attach configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single-controller configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One server/one HBA/single path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dual-controller configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One server/one HBA/dual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Two servers/one HBA per server/dual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Four servers/one HBA per server/dual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting switch attach configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dual controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
Contents
31
31
31
31
32
32
33
33
34
34
34
34
34
35
35
35
3
Two servers/two switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Four servers/multiple switches/SAN fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting remote management hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting two storage systems to replicate volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling for replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host ports and replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single-controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One server/single network/two switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dual-controller configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple servers/single network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple servers/different networks/multiple switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
36
36
36
37
38
38
38
38
38
39
41
5 Connecting to the controller CLI port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Device description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing a Linux computer before cabling to the CLI port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading a device driver for Windows computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Obtaining IP values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the MSA Device Discovery Tool to discover a controller IP address . . . . . . . . . . . . . . . . . . . . . .
Setting network port IP addresses using DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting network port IP addresses using the CLI port and cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the CLI port and cable—known issues on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Workaround . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
43
43
43
43
44
44
47
47
47
6 Basic operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Accessing the SMU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring and provisioning the storage system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
USB CLI port connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault isolation methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Options available for performing basic steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use the SMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitor event notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
View the enclosure LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing basic steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gather fault information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Determine where the fault is occurring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Review the event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Isolate the fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If the enclosure does not initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Correcting enclosure IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is the enclosure front panel Fault/Service Required LED amber?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is the enclosure rear panel FRU OK LED off? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is the enclosure rear panel Fault/Service Required LED amber? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Are both disk drive module LEDs off (Online/Activity and Fault/UID)? . . . . . . . . . . . . . . . . . . . . . . . .
Is the disk drive module Fault/UID LED blinking amber? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is a connected host port Host Link Status LED off? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is a connected port Expansion Port Status LED off?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is a connected port Network Port Link Status LED off? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is the power supply Input Power Source LED off? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is the power supply Voltage/Fan Fault/Service Required LED amber? . . . . . . . . . . . . . . . . . . . . . . . .
Controller failure in a single-controller configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If the controller has failed or does not start, is the Cache Status LED on/blinking? . . . . . . . . . . . . . . . .
Transporting cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
Contents
51
51
51
51
51
52
52
52
52
52
52
52
53
53
53
53
54
54
54
55
55
55
56
56
56
57
57
57
58
58
Isolating a host-side connection fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-side connection troubleshooting featuring host ports with SFPs . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-side connection troubleshooting featuring SAS host ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Isolating a controller module expansion port connection fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Isolating Remote Snap replication faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling for replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replication setup and verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic steps for replication setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can you successfully use the Remote Snap feature?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can you view information about remote links? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can you create a replication set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can you replicate a volume? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can you view a replication image?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can you view remote systems? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resolving voltage and temperature warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sensor locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power supply sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cooling fan sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Temperature sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power supply module voltage sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
58
59
60
61
61
61
62
62
62
63
64
64
64
65
65
65
65
66
66
8 Support and other resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Contacting HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rack stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer self repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product warranties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
67
67
67
68
68
68
69
69
70
70
9 Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
A LED descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Front panel LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 Array SFF enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 Array LFF or supported 12-drive expansion enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk drive LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rear panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller enclosure—rear panel layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAN controller module—rear panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAS controller module—rear panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 6 Gb 3.5" 12-drive enclosure—rear panel layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D2700 6Gb drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
73
74
75
76
76
77
79
80
81
81
B Environmental requirements and specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Safety requirements. . . . . . . . . . . . . . . . . . .
Site requirements and guidelines . . . . . . . . .
Site wiring and AC power requirements . .
Site wiring and DC power requirements . .
Weight and placement guidelines . . . . . .
Electrical guidelines . . . . . . . . . . . . . . . .
Ventilation requirements . . . . . . . . . . . . .
Cabling requirements . . . . . . . . . . . . . . .
Management host requirements . . . . . . . . . .
Physical requirements . . . . . . . . . . . . . . . . .
Environmental requirements . . . . . . . . . . . . .
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.........
.........
.........
.........
.........
.........
.........
.........
.........
.........
.........
Contents
83
83
83
83
84
84
84
84
84
85
86
5
Electrical requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Site wiring and power requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Power cord requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
C Electrostatic discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Preventing electrostatic discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Grounding methods to prevent electrostatic discharge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
D SFP option for host ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Locate the SFP transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Install an SFP transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Verify component operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6
Contents
Figures
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
MSA 2040 Array SFF enclosure: front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 Array LFF or supported 12-drive enclosure: front panel . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 Array: rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAN controller module face plate (FC or 10GbE iSCSI). . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAN controller module face plate (1 Gb RJ-45) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAS controller module face plate (HD mini-SAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LFF 12-drive enclosure: rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 CompactFlash card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling connections between the MSA 2040 controller and a single drive enclosure. . . . . . . . . . . . .
Cabling connections between the MSA 2040 controller and a single drive enclosure. . . . . . . . . . . . .
Cabling connections between MSA 2040 controllers and LFF drive enclosures . . . . . . . . . . . . . . . . .
Cabling connections between MSA 2040 controllers and SFF drive enclosures . . . . . . . . . . . . . . . . .
Cabling connections between MSA 2040 controllers and drive enclosures of mixed model type . . . . .
Fault-tolerant cabling connections showing maximum number of enclosures of same type . . . . . . . . . .
Cabling connections showing maximum enclosures of mixed model type . . . . . . . . . . . . . . . . . . . . .
AC power supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC and AC power supplies with power switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC power cable featuring sectioned D-shell and lug connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting hosts: direct attach—one server/one HBA/single path . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting hosts: direct attach—one server/one HBA/dual path . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting hosts: direct attach—two servers/one HBA per server/dual path . . . . . . . . . . . . . . . . . .
Connecting hosts: direct attach—four servers/one HBA per server/dual path . . . . . . . . . . . . . . . . . .
Connecting hosts: switch attach—two servers/two switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting hosts: switch attach—four servers/multiple switches/SAN fabric. . . . . . . . . . . . . . . . . . .
Connecting two storage systems for Remote Snap: one server/two switches/one location. . . . . . . . . .
Connecting two storage systems for Remote Snap: multiple servers/one switch/one location. . . . . . . .
Connecting two storage systems for Remote Snap: multiple servers/switches/one location . . . . . . . . .
Connecting two storage systems for Remote Snap: multiple servers/switches/two locations. . . . . . . . .
Connecting two storage systems for Remote Snap: multiple servers/SAN fabric/two locations . . . . . .
Connecting a USB cable to the CLI port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: MSA 2040 Array SFF enclosure front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: MSA 2040 Array LFF enclosure front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: Disk drive combinations — enclosure front panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSA 2040 SAN Array: rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: MSA 2040 SAN controller module (FC and 10GbE SFPs) . . . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: MSA 2040 SAN controller module (1 Gb RJ-45 SFPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: MSA 2040 SAS controller module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: MSA 2040 Storage system enclosure power supply modules . . . . . . . . . . . . . . . . . . . . . . . . .
LEDs: MSA 2040 6 Gb 3.5" 12-drive enclosure rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install a qualified SFP option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
15
15
16
16
17
21
21
22
23
24
25
26
28
28
29
34
34
34
35
35
36
38
38
39
39
40
45
73
74
75
76
77
78
79
80
81
89
7
8
Figures
Tables
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Terminal emulator display settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Terminal emulator connection settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Diagnostics LED status: Front panel “Fault/Service Required” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Diagnostics LED status: Rear panel “FRU OK” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Diagnostics LED status: Rear panel “Fault/Service Required” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Diagnostics LED status: Front panel disks “Online/Activity” and “Fault/UID” . . . . . . . . . . . . . . . . . . . . 55
Diagnostics LED status: Front panel disks “Fault/UID” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Diagnostics LED status: Rear panel “Host Link Status” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Diagnostics LED status: Rear panel “Expansion Port Status” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Diagnostics LED status: Rear panel “Network Port Link Status” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Diagnostics LED status: Rear panel power supply “Input Power Source” . . . . . . . . . . . . . . . . . . . . . . . 57
Diagnostics LED status: Rear panel power supply: “Voltage/Fan Fault/Service Required” . . . . . . . . . . . 57
Diagnostics LED status: Rear panel “Cache Status”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Diagnostics for replication setup: Using Remote Snap feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Diagnostics for replication setup: Viewing information about remote links . . . . . . . . . . . . . . . . . . . . . . 62
Diagnostics for replication setup: Creating a replication set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Diagnostics for replication setup: Replicating a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Diagnostics for replication setup: Viewing a replication image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Diagnostics for replication setup: Viewing a remote system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Power supply sensor descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Cooling fan sensor descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Controller module temperature sensor descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Power supply temperature sensor descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Voltage sensor descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Rackmount enclosure dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Rackmount enclosure weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Tables
9
10
Tables
1
Overview
HP MSA Storage models are high-performance storage solutions combining outstanding performance with
high reliability, availability, flexibility, and manageability. MSA 2040 enclosure models are designed to
meet NEBS Level 3, MIL-STD-810G (storage requirements), and European Telco specifications.
MSA 2040 Storage models
The MSA 2040 enclosures support either large form factor (LFF 12-disk) or small form factor (SFF 24-disk)
2U chassis, using either AC or DC power supplies. HP MSA Storage models include MSA 2040 SAN and
MSA 2040 SAS controllers, which are introduced below.
NOTE:
For additional information about MSA 2040 controller modules, see the following subsections:
• "Controller enclosure—rear panel layout" (page 14)
• "MSA 2040 SAN controller module—rear panel components" (page 15)
• "MSA 2040 SAS controller module—rear panel components" (page 16)
MSA 2040 SAN
MSA 2040 SAN models use Converged Network Controller technology, allowing you to select the desired
host interface protocol from the available Fibre Channel (FC) or Internet SCSI (iSCSI) host interface
protocols supported by the system. You can use the CLI to set all controller module host ports to use one of
these host interface protocols:
• 16 Gb FC
• 8 Gb FC
• 4 Gb FC
• 10 GbE iSCSI
• 1 GbE iSCSI
Alternatively, you can use the management interfaces to set Converged Network Controller ports to support
a combination of host interface protocols. When configuring a combination of host interface protocols,
host ports 1 and 2 are set to FC (either both16 Gbit/s or both 8 Gbit/s), and host ports 3 and 4 must be
set to iSCSI (either both 10 GbE or both 1 GbE), provided the Converged Network Controller ports use the
qualified SFP connectors and cables required for supporting the selected host interface protocol. See
"MSA 2040 SAN controller module—rear panel LEDs" (page 77) for more information.
IMPORTANT: See the “HP MSA 2040 SAN Storage array and iSCSI SFPs Read This First” document for
important information pertaining to iSCSI SFPs.
TIP: See the “Configuring host ports” topic within the SMU Reference Guide for information about
configuring Converged Network Controller ports with host interface protocols of the same type or a
combination of types.
MSA 2040 SAS
MSA 2040 SAS models provide four high density mini-SAS (HD mini-SAS) ports per controller module. The
HD mini-SAS host interface protocol uses the SFF-8644 external connector interface defined for SAS3.0 to
support a link rate of 12 Gbit/s using the qualified connectors and cable options. See "MSA 2040 SAS
controller module—rear panel LEDs" (page 79) for more information.
MSA 2040 Storage models
11
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. See http://www.hp.com/support/msa2040/QuickSpecs.
12
Overview
2
Components
Front panel components
HP MSA 2040 models support small form factor (SFF) and large form factor (LFF) enclosures. The SFF
chassis, configured with 24 2.5" SFF disks, is used as a controller enclosure. The LFF chassis, configured
with 12 3.5" LFF disks, is used as either a controller enclosure or a drive enclosure.
Supported drive enclosures, used for adding storage, are available in LFF or SFF chassis. The MSA 2040
6 Gb 3.5" 12-drive enclosure is the large form factor drive enclosure used for storage expansion. The HP
D2700 6 Gb enclosure, configured with 25 2.5" SFF disks, is the small form factor drive enclosure used for
storage expansion. See "SFF drive enclosure" (page 17) for a description of the D2700.
MSA 2040 Array SFF enclosure
Right ear
Left ear
1
2
3
4
5
6
7
8
9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 24
4
1
2
5
3
6
Note: Integers on disks indicate drive slot numbering sequence.
1
Enclosure ID LED
4
Unit Identification (UID) LED
2
Disk drive Online/Activity LED
5
Heartbeat LED
3
Disk drive Fault/UID LED
6
Fault ID LED
Figure 1 MSA 2040 Array SFF enclosure: front panel
MSA 2040 Array LFF or supported drive expansion enclosure
Left ear
Right ear
1
4
7
10
2
5
8
11
3
6
9
12
4
7 10
3 6
9 12
1
4
1
2
5
3
6
Note: Integers on disks indicate drive slot numbering sequence.
1
Enclosure ID LED
4
Unit Identification (UID) LED
2
Disk drive Online/Activity LED
5
Heartbeat LED
3
Disk drive Fault/UID LED
6
Fault ID LED
Figure 2 MSA 2040 Array LFF or supported 12-drive enclosure: front panel
Front panel components
13
Disk drives used in MSA 2040 enclosures
MSA 2040 enclosures support LFF/SFF Midline SAS, LFF/SFF Enterprise SAS, and SFF SSD disks. For
information about creating vdisks and adding spares using these different disk drive types, see the
HP MSA 2040 SMU Reference Guide and HP MSA 2040 Solid State Drive Read This First document.
Controller enclosure—rear panel layout
The diagram and table below display and identify important component items comprising the rear panel
layout of the MSA 2040 controller enclosure (MSA 2040 SAN is shown in the example).
1
1
PORT 1
PORT 2
PORT 3
PORT 4
2
6Gb/s
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
PORT 1
PORT 2
PORT 3
PORT 4
3
6Gb/s
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
4
5
MSA 2040 controller enclosure
(rear panel locator illustration)
1
AC Power supplies
4
DC Power supply (2) — (DC model only)
2
Controller module A (see face plate detail figures)
5
DC Power switch
3
Controller module B (see face plate detail figures)
Figure 3 MSA 2040 Array: rear panel
A controller enclosure accommodates two power supply FRUs of the same type—either both AC or both
DC—within the two power supply slots (see two instances of callout 1 above). The controller enclosure
accommodates two controller module FRUs of the same type within the I/O module slots (see callouts 2
and 3 above).
IMPORTANT: If the MSA 2040 controller enclosure is configured with a single controller module, the
controller module must be installed in the upper slot (see callout 2 above), and an I/O module blank must
be installed in the lower slot (see callout 3 above). This configuration is required to allow sufficient air flow
through the enclosure during operation.
The diagrams with tables that immediately follow provide descriptions of the different controller modules
and power supply modules that can be installed into the rear panel of an MSA 2040 controller enclosure.
Showing controller modules and power supply modules separately from the enclosure provides improved
clarity in identifying the component items called out in the diagrams and described in the tables.
Descriptions are also provided for optional drive enclosures supported by MSA 2040 controller enclosures
for expanding storage capacity.
NOTE: MSA 2040 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.
14
Components
MSA 2040 SAN controller module—rear panel components
Figure 4 shows host ports configured with either 8/16 Gb FC or 10GbE iSCSI SFPs. The SFPs look
identical. Refer to the LEDs that apply to the specific configuration of your Converged Network Controller ports.
1
5
7
6
6Gb/s
PORT 1
PORT 2
PORT 3
PORT 4
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
8
2 3 4
= FC LEDs
= 10GbE iSCSI LEDs
1
Host ports: used for host connection or replication
[see "Install an SFP transceiver" (page 89)]
5 Network port
2
CLI port (USB - Type B)
7 Disabled button (used by engineering only)
3
Service port 2 (used by service personnel only)
4
Reserved for future use
6 Service port 1 (used by service personnel only)
(Sticker shown covering the opening)
8 SAS expansion port
Figure 4 MSA 2040 SAN controller module face plate (FC or 10GbE iSCSI)
Figure 5 shows Converged Network Controller ports configured with 1 Gb RJ-45 SFPs.
1
5
7
6
6Gb/s
PORT 1
PORT 2
PORT 3
PORT 4
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
= FC LEDs
8
2 3 4
= 1 Gb iSCSI LEDs (all host ports use 1 Gb RJ-45 SFPs in this figure)
1
Host ports: used for host connection or replication
[see "Install an SFP transceiver" (page 89)]
5 Network port
2
CLI port (USB - Type B)
7 Disabled button (used by engineering only)
3
Service port 2 (used by service personnel only)
4
Reserved for future use
6 Service port 1 (used by service personnel only)
(Sticker shown covering the opening)
8 SAS expansion port
Figure 5 MSA 2040 SAN controller module face plate (1 Gb RJ-45)
NOTE: See "MSA 2040 SAN" (page 11) for more information about Converged Network Controller
technology. For port configuration, see the “Configuring host ports” topic within the
HP MSA 2040 SMU Reference Guide or online help.
Controller enclosure—rear panel layout
15
MSA 2040 SAS controller module—rear panel components
Figure 6 shows host ports configured with 12 Gbit/s HD mini-SAS connectors.
1
LINK
12Gb/s
S
A
S
ACT
5
LINK
LINK
ACT
ACT
12Gb/s
S
A
S
6
7
LINK
ACT
6Gb/s
SAS 1 SAS 2
SAS 3 SAS 4
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
8
2 3 4
1
HD mini-SAS ports: used for host connection
6 Service port 1 (used by service personnel only)
2
CLI port (USB - Type B)
7 Disabled button (used by engineering only)
3
Service port 2 (used by service personnel only)
4
Reserved for future use
5
Network port
(Sticker shown covering the opening)
8 SAS expansion port
Figure 6 MSA 2040 SAS controller module face plate (HD mini-SAS)
IMPORTANT: See Connecting to the controller CLI port for information about enabling the controller
enclosure USB Type - B CLI port for accessing the Command-line Interface via a telnet client.
Drive enclosures
Drive enclosure expansion modules attach to MSA 2040 controller modules via the mini-SAS expansion
port, allowing addition of disk drives to the system. MSA 2040 controller enclosures support adding the
6 Gb drive enclosures described below.
LFF drive enclosure — rear panel layout
MSA 2040 controllers support the MSA 2040 6 Gb 3.5" 12-drive enclosure shown below.
1
4 5 67
0
1
0
2
IN
OUT
0
0
3
IN
1
Power supplies (AC shown)
5
Service port (used by service personnel only)
2
I/O module A
6
SAS In port
3
I/O module B
7
SAS Out port
4
Disabled button (used by engineering only)
Figure 7 LFF 12-drive enclosure: rear panel
16
OUT
Components
SFF drive enclosure
MSA 2040 controllers support the D2700 6 Gb drive enclosure for adding storage. For information about
this product, visit http://www.hp.com/support. Pictorial representations of this drive enclosure are also
provided in the MSA 2040 Quick Start Instructions and MSA 2040 Cable Configuration Guide.
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
a disk access.
NOTE:
See HP MSA 2040 SMU Reference Guide for more information about volume cache options.
Transportable CompactFlash
During a power loss or array controller failure, data stored in cache is saved off to non-volatile memory
(CompactFlash). The data is 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.
The CompactFlash card is located at the midplane-facing end of the controller module as shown below.
Controller module pictorial
(Midplane-facing rear view)
y
ve r
o ve
m co
re e
t r
oe
nh
o c
D ca
r
fo
d
se
U
CompactFlash card
ly
n
o
Figure 8 MSA 2040 CompactFlash card
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" (page 57) for more
information).
Cache
17
CAUTION: The CompactFlash card should only be removed for transportable purposes. 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 MSA Controller Module Replacement
Instructions shipped with the replacement controller module. 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 partner controller, there is no need to
transport failed controller cache to a replacement controller because the cache is duplicated between the
controllers (subject to volume write optimization setting).
Supercapacitor pack
To protect RAID controller cache in case of power failure, MSA 2040 controllers are equipped with
supercapacitor technology, in conjunction with CompactFlash memory, built into each controller module to
provide extended cache memory backup time. The supercapacitor 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 is automatically committed to disk media when power is restored. While the cache
is being maintained by the supercapacitor, the Cache Status LED flashes at a rate of 1/10 second on and
9/10 second off.
Upgrading to MSA 2040
For information about upgrading components for use with MSA 2040 controllers, refer to: Upgrading to
the HP MSA 2040.
18
Components
3
Installing 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.
Installation checklist
Table 1
Step
Task
Where to find procedure
1.
Install the controller enclosure and optional
drive enclosures in the rack, and attach ear
caps.
See the racking instructions poster.
2.
Connect the controller enclosure and LFF/SFF
drive enclosures.
See "Connecting controller and drive enclosures"
(page 19).
3.
Connect power cords.
See the quick start instructions.
4.
Test enclosure connections.
See "Testing enclosure connections" (page 27).
5.
Install required host software.
See "Host system requirements" (page 31).
6.
Connect data hosts.
See "Connecting the enclosure to data hosts" (page 31).
If using the optional Remote Snap feature, also see
"Connecting two storage systems to replicate volumes"
(page 36).
7.
Connect remote management hosts.
See "Connecting remote management hosts" (page 36).
8.
Obtain IP values and set management port IP
properties on the controller enclosure.
See "Obtaining IP values" (page 43).1
See Connecting to the controller CLI port; with Linux and
Windows topics.
9.
Perform initial configuration tasks2:
Topics below correspond to bullets at left:
•
•
Sign in to the web-based Storage
Management Utility (SMU).
Initially configure and provision the
storage system using the SMU.3
See “Getting Started” in the HP MSA 2040 SMU Reference
Guide.
See “Configuring the System” and “Provisioning the
System” topics (SMU Reference Guide or online help).
1MSA
Device Discovery Tool, introduced in Obtaining IP values, provides the optimal method for setting network port IP addresses.
The SMU is introduced in "Accessing the SMU" (page 49). See the SMU Reference Guide or online help for additional information.
3If 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.
2
Connecting controller and drive enclosures
MSA 2040 controller enclosures support up to eight enclosures (including the controller enclosure). You
can cable drive enclosures of the same type or of mixed LFF/SFF model type.
The firmware supports both straight-through and fault-tolerant SAS cabling. Fault-tolerant 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. MSA 2040 controller enclosures support 6 Gbit/s internal disk drive
speeds, together with 6 Gbit/s (SAS2.0) expander link speeds. When connecting multiple drive
enclosures, use fault-tolerant cabling to ensure the highest level of fault tolerance.
For example, the illustration on the left in Figure 11 (page 22) shows controller module 1A 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).
Installation checklist
19
Connecting the MSA 2040 controller to the SFF drive enclosure
The SFF D2700 25-drive enclosure, supporting 6 Gb internal disk drive and expander link speeds, can be
attached to an MSA 2040 controller enclosure using supported mini-SAS to mini-SAS cables of 0.5 m
(1.64') to 2 m (6.56') length [see Figure 10 (page 21)].
Connecting the MSA 2040 controller to the LFF drive enclosure
The LFF MSA 2040 6 Gb 3.5"12-drive enclosure, supporting 6 Gb internal disk drive and expander link
speeds, can be attached to an MSA 2040 controller enclosure using supported mini-SAS to mini-SAS
cables of 0.5 m (1.64') to 2 m (6.56') length [see Figure 10 (page 21)].
Connecting the MSA 2040 controller to mixed model drive enclosures
MSA 2040 controllers support cabling of 6 Gb SAS link-rate LFF and SFF expansion modules—in mixed
model fashion—as shown in Figure 13 (page 24), and further described in the HP MSA 2040 Cable
Configuration Guide; the HP MSA 2040 Quick Start Instructions; QuickSpecs; and HP white papers (listed
below).
Cable requirements for MSA 2040 enclosures
IMPORTANT:
• When installing SAS cables to expansion modules, use only supported mini-SAS x4 cables with
SFF-8088 connectors supporting your 6 Gb application.
• Mini-SAS to mini-SAS 0.5 m (1.64') cables are used to connect cascaded enclosures in the rack.
• See QuickSpecs for information about which cables are provided with your MSA 2040 products.
http://www.hp.com/support/msa2040/QuickSpecs
• If additional or longer cables are required, they must be ordered separately (see relevant MSA 2040
QuickSpecs or P2000 G3 QuickSpecs for your products).
• The maximum expansion cable length allowed in any configuration is 2 m (6.56').
• Cables required, if not included, must be separately purchased.
• When adding more than two drive enclosures, you may need to purchase additional 1 m or 2 m
cables, depending upon number of enclosures and cabling method used:
• Spanning 3, 4, or 5 drive enclosures requires 1 m (3.28') cables.
• Spanning 6 or 7 drive enclosures requires 2 m (6.56') cables.
• See Quickspecs (link provided above) regarding information about cables supported for host connection:
• Qualified Fibre Channel SFP and cable options
• Qualified 10GbE iSCSI SFP and cable options
• Qualified 1 Gb RJ-45 SFP and cable options
• Qualified HD mini-SAS cable options
For additional information concerning cabling of MSA 2040 controllers and D2700 drive enclosures, visit:
http://www.hp.com/support/msa2040
Browse for the following reference documents:
• HP MSA 2040 Cable Configuration Guide
• HP Remote Snap technical white paper
• HP MSA 2040 best practices
20
Installing the enclosures
NOTE: For clarity, the schematic illustrations of controller and expansion modules shown in this section
provide only relevant details such as expansion ports within the module face plate outline. For detailed
illustrations showing all components, see "Controller enclosure—rear panel layout" (page 14).
Controller A
IOM blank
1
In
Out
1A
1A
1B
1B
IOM blank
2A
2A
2
2B
2B
IOM blank
Controller A
1 = LFF 12-drive enclosure
P1
P2
IOM blank
2 = SFF 25-drive enclosure
Figure 9 Cabling connections between the MSA 2040 controller and a single drive enclosure
The figure above shows examples of the MSA 2040 controller enclosure—equipped with a single
controller module—cabled to a single drive enclosure equipped with a single expansion module. The
empty I/O module slot in each of the enclosures is covered with an IOM blank to ensure sufficient air flow
during enclosure operation. The remaining illustrations in the section feature enclosures equipped with dual
IOMs.
IMPORTANT: If the MSA 2040 controller enclosure is configured with a single controller module, the
controller module must be installed in the upper slot, and an I/O module blank must be installed in the
lower slot (shown above). This configuration is required to to allow sufficient air flow through the enclosure
during operation.
Controller A
Controller B
1
In
Out
In
Out
1 = LFF 12-drive enclosure
1A
1A
Controller A
1B
1B
Controller B
2A
2A
2B
2B
2
P1
P2
P1
P2
2 = SFF 25-drive enclosure
Figure 10 Cabling connections between the MSA 2040 controller and a single drive enclosure
Connecting controller and drive enclosures
21
Controller A
1A
1A
Controller A
Controller B
1B
1B
Controller B
2A
2A
Out
2B
2B
Out
3A
3A
Out
3B
3B
Out
4A
4A
Out
4B
4B
5A
5A
5B
5B
Out
In
In
In
Out
In
Out
In
Out
In
Out
In
In
In
In
In
Out
In
Out
Fault-tolerant cabling
Out
In
Out
In
In
Out
In
Out
Straight-through cabling
Figure 11 Cabling connections between MSA 2040 controllers and LFF drive enclosures
The diagram at left (above) shows fault-tolerant cabling of a dual-controller enclosure cabled to MSA 2040
6 Gb 3.5" 12-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). Fault-tolerant cabling allows any drive enclosure to fail—or be removed—while
maintaining access to other enclosures.
The diagram at right (above) shows the same storage components connected using straight-through
cabling. Using this method, if a drive enclosures fails, the enclosures that follow the failed enclosure in the
chain are no longer accessible until the failed enclosure is repaired or replaced.
22
Installing the enclosures
Controller A
1A
1A
Controller A
Controller B
1B
1B
Controller B
P1
P2
P1
P1
P1
P1
P1
P2
P2
P2
P2
P2
P1
P2
P1
P2
Fault-tolerant cabling
P2
2A
2A
P1
2B
2B
P1
3A
3A
P1
3B
3B
4A
4A
P1
4B
4B
P1
5A
5A
P1
P2
5B
5B
P1
P2
P1
P2
P2
P2
P2
P2
Straight-through cabling
Figure 12 Cabling connections between MSA 2040 controllers and SFF drive enclosures
The figure above provides sample diagrams reflecting cabling of MSA 2040 controller enclosures and
D2700 6 Gb drive enclosures.
The diagram at left shows fault-tolerant cabling of a dual-controller enclosure and D2700 6 Gb 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). Fault-tolerant cabling allows any drive enclosure to fail—or be removed—while maintaining
access to other enclosures.
The diagram at right shows the same storage components connected using straight-through cabling. Using
this method, if a drive enclosures fails, the enclosures that follow the failed enclosure in the chain are no
longer accessible until the failed enclosure is repaired or replaced.
Connecting controller and drive enclosures
23
Controller A
1A
1A
Controller A
Controller B
1B
1B
Controller B
2A
2A
2B
2B
1
In
In
1
In
In
2
P1
P1
2
Out
Out
Out
Out
1
In
In
3A
3A
3B
3B
1
In
In
P2
4A
4A
P2
4B
4B
P1
P2
5A
5A
P1
P2
5B
5B
Fault-tolerant cabling
2
P1
P1
2
Out
Out
Out
Out
P2
P2
P1
P2
P1
P2
Straight-through cabling
Drive enclosure IOM face plate key:
1 = LFF 12-drive enclosure
2 = SFF 25-drive enclosure
Figure 13 Cabling connections between MSA 2040 controllers and drive enclosures of mixed model type
The figure above provides sample diagrams reflecting cabling of MSA 2040 controller enclosures and
supported mixed model drive enclosures. In this example, the SFF drive enclosures follow the LFF drive
enclosures. Given that both drive enclosure models use 6 Gb SAS link-rate and SAS2.0 expanders, they
can be ordered in desired sequence within the array, following the controller enclosure.
The diagram at left shows fault-tolerant cabling of a dual-controller enclosure and mixed model drive
enclosures, and the diagram at right shows the same storage components connected using straight-through
cabling.
24
Installing the enclosures
1
Controller A
1A
Controller B
1B
Out
2A
In
In
Out
2B
1A
Controller A
1B
Controller B
2A
2B
3A
1
Out
3A
In
Out
Out
4A
Out
4B
In
In
2
2
4B
5A
Out
5B
In
Out
6A
In
Out
6B
In
Out
7A
In
6A
7A
2
P1
P1
2
8A
7B
In
Out
8A
P1
P1
2
7B
8B
Out
In
P1
P1
6B
1
P2
P2
P2
P2
P2
P2
P2
5A
In
Out
1
P1
P1
5B
1
P2
P1
3B
4A
1
P1
3B
In
1
2
P1
P1
2
P2
P2
P2
P2
P1
P2
P1
P2
Note:
The maximum number of supported drive
enclosures (7) may require purchase of
additional longer cable.
Drive enclosure IOM face plate key:
In
Out
8B
1 = LFF 12-drive enclosure
2 = SFF 25-drive enclosure
Figure 14 Fault-tolerant cabling connections showing maximum number of enclosures of same type
The figure above provides sample diagrams reflecting fault-tolerant cabling of a maximum number of
supported MSA 2040 enclosures. The diagram at left shows fault-tolerant cabling of an MSA 2040
controller enclosure and seven LFF drive enclosures; whereas the diagram at right shows fault-tolerant
cabling of an MSA 2040 controller enclosure and seven D2700 drive enclosures.
Connecting controller and drive enclosures
25
Continued from below left
(see enclosure 4)
1
Controller A
1A
P2
P1
P2
P1
1B
5A
5B
Controller B
2A
1
2B
3A
P1
P1
1
3B
P1
P1
2
P2
P2
In
In
P2
2
In
4B
1
P1
P1
6A
6B
Out
Out
7A
P2
In
4A
Out
7B
Out
P2
2
P2
In
Out
In
Out
8A
8B
Continued above right
(see enclosure 5)
Drive enclosure IOM face plate key:
1 = SFF 25-drive enclosure
2 = LFF 12-drive enclosure
Figure 15 Cabling connections showing maximum enclosures of mixed model type
The illustration above shows a sample maximum enclosures configuration. The diagram shows mixed
model drive enclosures within the dual-controller array using fault-tolerant cabling. In this example, the LFF
drive enclosures follow the SFF drive enclosures. Given that both drive enclosure models use 6 Gb SAS
link-rate and SAS2.0 expanders, they can be ordered in desired sequence within the array, following the
controller enclosure. MSA 2040 controller enclosures support up to eight enclosures (including the
controller enclosure) for adding storage.
IMPORTANT: For comprehensive configuration options and associated illustrations, refer to the HP MSA
2040 Cable Configuration Guide.
26
Installing the enclosures
Testing enclosure connections
NOTE: Once the power-on sequence for enclosures succeeds, the storage system is ready to be
connected to hosts, as described in "Connecting the enclosure to data hosts" (page 31).
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 quick start instructions.
NOTE: MSA 2040 controller enclosures and drive enclosures do not have power switches (they are
switchless). 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 each 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—if no LEDs on the front
and back of the enclosure are amber—the power-on sequence is complete, and no faults have been
detected. See "LED descriptions" (page 73) 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)
TIP:
Generally, when powering off, you will reverse the order of steps used for powering on.
Power cycling procedures vary according to the type of power supply unit included with the enclosure. For
controller and drive enclosures configured with the switchless AC power supplies, refer to the procedure
described under AC power supply below. For procedures pertaining to a) controller enclosures configured
with DC power supplies, or b) previously installed drive enclosures featuring power switches, see "DC and
AC power supplies equipped with a power switch" (page 28).
IMPORTANT: See "Power cord requirements" (page 86) and QuickSpecs for more information about
power cords supported by MSA 2040 enclosures.
AC power supply
Enclosures equipped with switchless power supplies rely on the power cord for power cycling. Connecting
the cord from the power supply power cord connector to the appropriate power source facilitates power
on; whereas disconnecting the cord from the power source facilitates power off.
Testing enclosure connections
27
Power cord connect
Figure 16 AC power supply
To power on the system:
1. Obtain a suitable AC power cord for each AC power supply that will connect to a power source.
2. Plug the power cord into the power cord connector on the back of the drive enclosure (see Figure 16).
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 power supply within each drive enclosure.
3. Plug the power cord into the power cord connector on the back of the controller enclosure (see
Figure 16). Plug the other end of the power cord into the rack power source.
Repeat the sequence for the controller enclosure’s other switchless power supply.
To power off the system:
1. Stop all I/O from hosts to the system [see "Stopping I/O" (page 53)].
2. Shut down both controllers using either method described below:
• Use the SMU (Storage Management Utility) to shut down both controllers, as described in the online
help and web-posted HP MSA 2040 SMU Reference Guide.
Proceed to step 3.
• Use the command-line interface (CLI) to shut down both controllers, as described in the HP MSA
2040 CLI Reference Guide.
3. Disconnect the power cord male plug from the power source.
4. Disconnect the power cord female plug from the power cord connector on the power supply.
NOTE:
Power cycling for enclosures equipped with a power switch is described below.
DC and AC power supplies equipped with a power switch
DC power supplies and legacy AC power supplies are shown below. Each model has a power switch.
Power
switch
Power
switch
Power
cord
connect
Power
cable
connect
DC power supply unit
Figure 17 DC and AC power supplies with power switch
28
Installing the enclosures
Legacy AC power supply unit
Connect power cable to DC power supply
Locate two DC power cables that are compatible with your controller enclosure.
Connector pins (typical 2 places)
+L
+L
+L
+L
GND
-L
GND
-L
GND
-L
GND
-L
Ring/lug connector (typical 3 places)
Connector (front view)
Figure 18 DC power cable featuring sectioned D-shell and lug connectors
See Figure 18 and the illustration at left (in Figure 17) when performing the following steps:
1. Verify that the enclosure 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.
D-shell
(left side view)
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 18 above).
CAUTION: Connecting to a DC power source outside the designated -48V DC nominal range
(-36V DC to -72V DC) may damage the enclosure.
Connect power cord to legacy AC power supply
Obtain two suitable AC power cords: one for each AC power supply that will connect to a separate power
source. See the illustration at right [in Figure 17 (page 28)] when performing the following steps:
1. Verify that the enclosure power switches are in the Off position.
2. Identify the power cord connector on the power supply, and locate the target power source.
3. For each power supply, perform the following actions:
a. Plug one end of the cord into the power cord connector on the power supply.
b. Plug the other end of the power cord into the rack power source.
4. Verify connection of primary power cords from the rack to separate external power sources.
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 [see "Stopping I/O" (page 53)].
2. Shut down both controllers using either method described below:
Powering on/powering off
29
• Use the SMU to shut down both controllers, as described in the online help and HP MSA 2040
SMU Reference Guide.
Proceed to step 3.
• Use the command-line interface to shut down both controllers, as described in the HP MSA 2040
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.
30
Installing the enclosures
4
Connecting hosts
Host system requirements
Data hosts connected to HP MSA 2040 arrays must meet requirements described herein. Depending on
your system configuration, data host operating systems may require that multi-pathing is supported.
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 native Microsoft MPIO DSM support with Windows Server 2008 and Windows Server 2012. 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 Windows 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/storage/spock.
Connecting the enclosure to data hosts
A host identifies an external port to which the storage system is attached. The external port may be a port
in an I/O adapter (such as an FC HBA) in a server. Cable connections vary depending on configuration.
Common cable configurations are shown in this section. A list of supported configurations resides on the
MSA 2040 manuals site at http://www.hp.com/support/msa2040/Manuals:
• HP MSA 2040 Quick Start Instructions
• HP MSA 2040 Cable Configuration Guide
These documents provide installation details and describe newly-supported direct attach, switch-connect,
and storage expansion configuration options for MSA 2040 products. For specific information about
qualified host cabling options, see "Cable requirements for MSA 2040 enclosures" (page 20).
Any number or combination of LUNs can be shared among a maximum of 64 host ports (initiators),
provided the total does not exceed 1,024 LUNs per MSA 2040 SAN storage system (single-controller or
dual-controller configuration).
MSA 2040 SAN
MSA 2040 SAN models use Converged Network Controller technology, allowing you to select the desired
host interface protocol(s) from the available FC or iSCSI host interface protocols supported by the system.
The small form-factor pluggable (SFP transceiver or SFP) connectors used in host ports are further described
in the subsections below. Also see "MSA 2040 SAN" (page 11) for more information concerning use of
these host ports.
NOTE: Controller modules are not shipped with pre-installed SFPs. Within your product kit, you will need
to locate the qualified SFP options, and install them into the host ports. See HP Transceiver Installation
Instructions for information about installing SFPs. See also, "Install an SFP transceiver" (page 89).
Fibre Channel protocol
The MSA 2040 SAN controller enclosures support one or two controller modules using the Fibre Channel
interface protocol for host connection. Each controller module provides four host ports designed for use
with an FC SFP supporting data rates up to 16 Gbit/s. When configured with FC SFPs, MSA 2040 SAN
controller enclosures can also be cabled to support the optionally-licensed Remote Snap replication feature
via the FC ports.
Host system requirements
31
The MSA 2040 SAN controller supports Fibre Channel Arbitrated Loop (public or private) or point-to-point
topologies. 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. See the set host-parameters command
within the HP MSA 2040 CLI Reference Guide for command syntax and details about connection mode
parameter settings relative to supported link speeds.
Fibre Channel ports are used 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 used for the FC traffic.
The first usage option requires valid licensing for the Remote Snap replication feature, whereas the second
option requires that the host computer supports FC and optionally, multipath I/O.
TIP: Use the SMU Configuration Wizard to set FC port speed. Within the SMU Reference Guide, see
“Configuring the system > Using the Configuration Wizard > Configuring host ports,” and scroll to FC port
options. Use the CLI command set host-parameters to set FC port options, and use either the show
host-parameters or show ports commands to view information about host ports.
10GbE iSCSI protocol
The MSA 2040 SAN controller enclosures support one or two controller modules using the Internet SCSI
interface protocol for host connection. Each controller module provides four host ports designed for use
with a 10GbE iSCSI SFP supporting data rates up to 10 Gbit/s, using either one-way or mutual CHAP
(Challenge-Handshake Authentication Protocol).
TIP: See the “Configuring CHAP” topic in the SMU Reference Guide. Also see the important statement
about CHAP preceding the “Using the Replication Setup Wizard” procedure within that guide.
TIP: Use the SMU Configuration Wizard to set iSCSI port options. Within the SMU Reference Guide, see
“Configuring the system > Using the Configuration Wizard > Configuring host ports,” and scroll to iSCSI
port options. Use the CLI command set host-parameters to set iSCSI port options, and use either the
show host-parameters or show ports commands to view information about host ports.
The 10GbE iSCSI ports are used in either of two capacities:
• To connect two storage systems through a switch for use of Remote Snap replication.
• For attachment to 10GbE iSCSI hosts directly, or through a switch used for the 10GbE iSCSI traffic.
The first usage option requires valid licensing for the Remote Snap replication feature, whereas the second
option requires that the host computer supports Ethernet, iSCSI, and optionally, multipath I/O.
1 Gb iSCSI protocol
The MSA 2040 SAN controller enclosures support one or two controller modules using the Internet SCSI
interface protocol for host port connection. Each controller module provides four iSCSI host ports
configured with an RJ-45 SFP supporting data rates up to 1 Gbit/s, using either one-way or mutual CHAP.
TIP: See the “Configuring CHAP” topic in the SMU Reference Guide. Also see the admonition about
CHAP preceding the “Using the Replication Setup Wizard” procedure within that guide.
32
Connecting hosts
TIP: Use the SMU Configuration Wizard to set iSCSI port options. Within the SMU Reference Guide, see
“Configuring the system > Using the Configuration Wizard > Configuring host ports,” and scroll to iSCSI
port options. Use the CLI command set host-parameters to set iSCSI port options, and use either the
show host-parameters or show ports commands to view information about host ports.
The 1 Gb iSCSI ports are used in either of two capacities:
• To connect two storage systems through a switch for use of Remote Snap replication.
• For attachment to 1 Gb iSCSI hosts directly, or through a switch used for the 1 Gb iSCSI traffic.
The first usage option requires valid licensing for the Remote Snap replication feature, whereas the second
option requires that the host computer supports Ethernet, iSCSI, and optionally, multipath I/O.
MSA 2040 SAS
MSA 2040 SAS controller enclosures support one or two controller modules using the Serial Attached SCSI
(Small Computer System Interface) interface protocol for host connection. Each controller module provides
four HD mini-SAS host ports supporting data rates up to 12 Gbit/s. HD mini-SAS host ports connect to hosts
or switches; they are not used for replication.
Connecting direct attach configurations
The MSA 2040 controller enclosures support up to eight direct-connect server connections, four per
controller module. Connect appropriate cables from the server HBAs to the controller host ports as
described below, and shown in the following illustrations.
To connect the MSA 2040 SAN controller to a server or switch—using FC SFPs in controller ports—select
Fibre Channel cables supporting 4/8/16 Gb data rates, that are compatible with the host port SFP
connector (see QuickSpecs). 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.
To connect the MSA 2040 SAN controller to a server or switch—using 10GbE iSCSI SFPs in controller
ports—select the appropriate qualified 10GbE SFP option (see QuickSpecs). 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.
To connect the MSA 2040 SAN controller to a server or switch—using the 1 Gb SFPs in controller
ports—select the appropriate qualified RJ-45 SFP option (see QuickSpecs). 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.
To connect the MSA 2040 SAS controller to a server or switch—using the SFF-8644 dual HD mini-SAS
ports—select the appropriate qualified HD mini-SAS cable option (see QuickSpecs). A qualified SFF-8644
to SFF-8644 cable option is used for connecting to a 12 Gbit/s enabled host; whereas a qualified
SFF-8644 to SFF-8088 cable option is used for connecting to a 6 Gbit/s host.
NOTE: The MSA 2040 SAN diagrams that follow use a single representation for each cabling example.
This is due to the fact that the port locations and labeling are identical for each of the three possible
interchangeable SFPs supported by the system.
Within each cabling connection category, the MSA 2040 SAS model is shown beneath the MSA 2040
SAN model.
Connecting the enclosure to data hosts
33
Single-controller configurations
One server/one HBA/single path
MSA 2040 SAN
Server
6Gb/s
S
A
S
6Gb/s
S
A
S
IOM blank
MSA 2040 SAS
Server
12Gb/s
S
A
S
12Gb/s
S
A
S
IOM blank
Figure 19 Connecting hosts: direct attach—one server/one HBA/single path
Dual-controller configurations
One server/one HBA/dual path
MSA 2040 SAN
Server
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
MSA 2040 SAS
Server
12Gb/s
12Gb/s
S
A
S
S
A
S
12Gb/s
12Gb/s
S
A
S
S
A
S
Figure 20 Connecting hosts: direct attach—one server/one HBA/dual path
Two servers/one HBA per server/dual path
MSA 2040 SAN
Server 1
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
Server 2
MSA 2040 SAS
Server 1
12Gb/s
12Gb/s
S
A
S
S
A
S
12Gb/s
12Gb/s
S
A
S
S
A
S
Figure 21 Connecting hosts: direct attach—two servers/one HBA per server/dual path
34
Connecting hosts
Server 2
Four servers/one HBA per server/dual path
MSA 2040 SAN
Server 1
Server 2
Server 3
6Gb/s
S
A
S
6Gb/s
S
A
S
Server 4
MSA 2040 SAS
Server 1
Server 2
Server 3
12Gb/s
12Gb/s
S
A
S
S
A
S
12Gb/s
12Gb/s
Server 4
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
S
A
S
Figure 22 Connecting hosts: direct attach—four servers/one HBA per server/dual path
Connecting switch attach configurations
Dual controller configuration
Two servers/two switches
MSA 2040 SAN
Server 1
Server 2
Switch A
Switch B
6Gb/s
S
A
S
6Gb/s
S
A
S
Figure 23 Connecting hosts: switch attach—two servers/two switches
Connecting the enclosure to data hosts
35
Four servers/multiple switches/SAN fabric
MSA 2040 SAN
6Gb/s
S
A
S
6Gb/s
S
A
S
Server 1
Server 2
SAN
Server 3
Server 4
Figure 24 Connecting hosts: switch attach—four servers/multiple switches/SAN fabric
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 MSA 2040 SAN controller.
2. Connect the other end of each Ethernet cable to a network that your management host can access
(preferably on the same subnet).
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 NEBS and FCC Rules and
Regulations.
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 local (primary) storage system to a volume that can be
on the same system or a second, independent system. The second system can be located at the same site
as the first system, or at a different site.
The two associated standard 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
MSA 2040 SAN systems on the same network, or on different networks (MSA 2040 SAS systems do not
support replication). 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.
36
Connecting hosts
• 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 at least one port for replication on
each controller module—and possibly more than one port per controller module—depending on
replication traffic load.
• Be sure of the desired link type before creating the replication set, because you cannot change the
replication link type after creating the replication set.
• For the sake of system security, do not unnecessarily expose the controller module 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 MSA 2040 SAN environments support
replication.
IMPORTANT: Remote Snap must be licensed on all systems configured for replication, and the controller
module firmware version must be compatible on all systems licensed for replication.
NOTE: Systems must be correctly cabled before performing replication. See the following documents for
more information about using Remote Snap to perform replication tasks:
• HP Remote Snap technical white paper
• HP MSA 2040 Best Practices
• HP MSA 2040 SMU Reference Guide
• HP MSA 2040 CLI Reference Guide
• HP MSA 2040 Event Descriptions Reference Guide
• HP MSA 2040 Cable Configuration Guide
To access user documents, see the MSA 2040 manuals site:
http://www.hp.com/support/msa2040/Manuals.
To access a technical white paper about Remote Snap replication software, navigate to the link shown:
http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-0977ENW&cc=us&lc=en.
Cabling for replication
This section shows example replication configurations for MSA 2040 SAN controller enclosures. The
following illustrations provide conceptual examples of cabling to support Remote Snap replication. Blue
cables show I/O traffic and green cables show replication traffic.
NOTE: A simplified version of the MSA 2040 SAN controller enclosure rear panel is used in cabling
illustrations to portray either the FC or iSCSI host interface protocol. The rear panel layouts for the three
configurations are identical; only the external connectors used in the host interface ports differ.
Once the MSA 2040 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 the HP MSA 2040 SMU Reference Guide for more information about using Remote Snap to
perform replication tasks. The SMU Replication Setup Wizard guides you through replication setup.
Connecting two storage systems to replicate volumes
37
Host ports and replication
MSA 2040 SAN controller modules can use qualified SFP options of the same type, or they can use a
combination of qualified SFP options supporting different interface protocols. If you use a combination of
different protocols, then host ports 1 and 2 are set to FC (either both16 Gbit/s or both 8 Gbit/s), and host
ports 3 and 4 must be set to iSCSI (either both 10GbE or both 1 Gb). Each host port can perform I/O or
replication. In combination environments one interface—for example FC—might be used for I/O, and the
other interface type—10GbE or 1 Gb iSCSI—might be used for replication.
Single-controller configuration
One server/single network/two switches
The diagram below shows the rear panel of two MSA 2040 SAN controller enclosures with both I/O and
replication occurring on the same network. Each enclosure is equipped with a single controller module.
The controller modules can use qualified SFP options of the same type, or they can use a combination of
qualified SFP options supporting different interface protocols.
MSA 2040 SAN Storage system
6Gb/s
MSA 2040 SAN Storage system
S
A
S
6Gb/s
IOM blank
S
A
S
IOM blank
I/O switch
Switch
(replication)
To host server
Figure 25 Connecting two storage systems for Remote Snap: one server/two switches/one location
Host ports used for replication must be connected to at least one switch. For optimal protection, use two
switches, with one replication port from each controller connected to the first switch, and the other
replication port from each controller connected to the second switch. Using two switches in tandem avoids
the potential single point of failure inherent to using a single switch.
Dual-controller configuration
Each of the following diagrams show the rear panel of two MSA 2040 SAN controller enclosures
equipped with dual-controller modules. The controller modules can use qualified SFP options of the same
type, or they can use a combination of qualified SFP options supporting different interface protocols.
Multiple servers/single network
The diagram below shows the rear panel of two MSA 2040 SAN controller enclosures with both I/O and
replication occurring on the same physical network.
MSA 2040 SAN Storage system
MSA 2040 SAN Storage system
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
Switch
To host server(s)
Figure 26 Connecting two storage systems for Remote Snap: multiple servers/one switch/one location
38
Connecting hosts
The diagram below shows host interface connections and replication, with I/O and replication occurring
on different networks. For optimal protection, use two switches. Connect two ports from each controller
module to the first switch to facilitate I/O traffic, and connect two ports from each controller module to the
second switch to facilitate replication. Using two switches in tandem avoids the potential single point of
failure inherent to using a single switch; however, if one switch fails, either I/O or replication will fail,
depending on which of the switches fails.
MSA 2040 SAN Storage system
MSA 2040 SAN Storage system
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
Switch
(replication)
I/O switch
To host server(s)
Figure 27 Connecting two storage systems for Remote Snap: multiple servers/switches/one location
Virtual Local Area Network (VLAN) and zoning can be employed to provide separate networks for iSCSI
and FC, respectively. Whether using a single switch or multiple switches for a particular interface, you can
create a VLAN or zone for I/O and a VLAN or zone for replication to isolate I/O traffic from replication
traffic. Since each switch would include both VLANs or zones, the configuration would function as multiple
networks.
Multiple servers/different networks/multiple switches
The diagram below shows the rear panel of two MSA 2040 SAN controller enclosures with both I/O and
replication occurring on different networks.
Peer sites with failover
MSA 2040 SAN Storage system
MSA 2040 SAN Storage system
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
I/O switch
I/O switch
To host servers
Remote site "A"
Ethernet
WAN
To host servers
Remote site "B"
Figure 28 Connecting two storage systems for Remote Snap: multiple servers/switches/two locations
The diagram below also shows the rear-panel of two MSA 2040 SAN controller enclosures with both I/O
and replication occurring on different networks. This diagram represents two branch offices cabled to
enable disaster recovery and backup. In case of failure at either the local site or the remote site, you can
fail over the application to the available site.
Connecting two storage systems to replicate volumes
39
Remote site “A”
Remote site “B”
Peer sites with failover
Corporate
end-users
Corporate
end-users
LAN
LAN
A1
B1
Ethernet
WAN
B2
A2
FC
SAN
FC
SAN
MSA 2040 SAN Storage
system (typ. 2 places)
A1
B1
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
6Gb/s
S
A
S
FS “A”
data
App “A”
data
FS “B”
replica
App “B”
replica
Key — Server Codes:
A1
6Gb/s
= "A" File servers
A2 = "A" Application servers
B1 = "B" File servers
B2 = "B" Application servers
A2
A1
B2
B1
FS “A”
replica
App “A”
replica
FS “B”
data
App “B”
data
A2
B2
Data Restore Modes:
- Replicate back over WAN
- Replicate via physical media transfer
Failover Modes
- VMware
- Hyper V failover to servers
Figure 29 Connecting two storage systems for Remote Snap: multiple servers/SAN fabric/two locations
Although not shown in the preceding cabling examples, you can cable replication-enabled MSA 2040
SAN systems and compatible P2000 G3 systems—via switch attach—for performing replication tasks.
40
Connecting hosts
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
the 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.
Optionally, you can update firmware using FTP (File Transfer Protocol) as described in the MSA 2040 SMU
Reference Guide.
IMPORTANT: See the “About firmware update” and “Updating firmware” topics within the MSA 2040
SMU Reference Guide before performing a firmware update.
NOTE: To locate and download the latest software and firmware updates for your product, go to
http://www.hp.com/support.
Updating firmware
41
42
Connecting hosts
5
Connecting to the controller CLI port
Device description
The MSA 2040 controllers feature a command-line interface port used to cable directly to the controller
and initially set IP addresses, or perform other configuration tasks. This port employs a mini-USB Type B
form factor, requiring a cable that is supplied with the controller, 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, the Windows USB device driver must be downloaded from a DVD or HP website,
and installed on the computer that will be cabled directly to the controller command-line interface port.
NOTE: Directly cabling to the command-line interface (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
command-line interface port might not be necessary. The in-band method uses the MSA Device Discovery
utility on the “HP MSA 2040 SW Support and Documentation DVD” that is included with your system, and
is the best way to discover the controller IP addresses automatically, so that you can use them to log into
and manage your controllers using a web browser for the SMU, or telnet for the command-line interface.
See "Using the MSA Device Discovery Tool to discover a controller IP address" (page 43) 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 command-line interface 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 MSA 2040 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
command-line interface 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 support page at http://www.hp.com/support.
The USB device driver is also available from the Software Support and Documentation DVD that shipped
with your product.
Obtaining IP values
Using the MSA Device Discovery Tool to discover a controller IP address
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 MSA 2040 products, see the HP MSA 2040
SW Support and Documentation DVD (DVD hereafter) that shipped with your product.
Device description
43
1. Locate the DVD included with your MSA 2040 storage device.
2. Insert the DVD into the drive on a Linux or Windows computer on the network that is connected to your
controller enclosure.
3. Use Autorun or manually start the DVD.
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 the
SMU or the command-line interface.
Alternatively, you can set network port IP addresses using the command-line interface 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 MSA
Storage.”
2. Use a ping broadcast to try to identify the device through the ARP table of the host.
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 command-line interface 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
command-line interface port and cable. If you have not done so already, you need to enable your system
for using the command-line interface port [also see "Using the CLI port and cable—known issues on
Windows" (page 47)].
NOTE: For Linux systems, see "Preparing a Linux computer before cabling to the CLI port" (page 43). For
Windows systems see "Downloading a device driver for Windows computers" (page 43).
Network ports on controller module A and controller module B are configured with the following
factory-default IP settings:
• 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 command-line interface embedded in each controller module. The command-line
interface 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 the SMU. Be
sure to change the IP address via the 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 the
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 30 (generic controller module is shown).
44
Connecting to the controller CLI port
Host In
te
Not Sh rface
own
CLI
SERV
ICE−2
6Gb/s
CLI
ACT
LINK
SERV
ICE−1
CACH
E
DIRTY
LINK
Connect USB cable to CLI
port on controller faceplate
Figure 30 Connecting a USB cable to the CLI port
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" (page 43).
• Windows customers should locate the downloaded device driver described in "Downloading a
device driver for Windows computers" (page 43), 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 2 (page 45) and the connection settings in Table 3 (page 45) (also, see the note following this
procedure).
Table 2
.
Terminal emulator display settings
Parameter
Value
Terminal emulation mode
VT-100 or ANSI (for color support)
Font
Terminal
Translations
None
Columns
80
Table 3
Terminal emulator connection settings
Parameter
Value
Connector
COM3 (for example)1,2
Baud rate
115,200
Data bits
8
Parity
None
Stop bits
1
Flow control
None
1Your
2
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.
5. In the terminal emulator, connect to controller A.
6. Press Enter to display the CLI prompt (#).
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.
Obtaining IP values
45
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.
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 netmask gateway gateway controller a|b
where:
• address is the IP address of the controller
• netmask is the subnet mask
• gateway 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 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 the 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.
NOTE: When using the USB port of a personal computer or laptop connected to the server to initially
configure the MSA 2040 array, some computers or laptops may not properly connect to the array. If so,
access and configure the MSA storage system using the MSA Device Discovery Tool for Windows.
The Device Discovery Tool discovers MSA storage devices in the network, in the local subnet, and directly
attached to the server. The MSA Device Discovery Tool for Windows is available as a software download.
46
Connecting to the controller CLI port
NOTE:
Access the download from your HP MSA support website at http://www.hp.com/support.
The USB device driver is also available from the Software Support and Documentation DVD that shipped
with your product.
Using the CLI port and cable—known issues on Windows
The MSA Device Discovery Tool provides the optimal approach for setting network port IP addresses. If you
use the out-of-band method for discovering controller IP addresses instead, be aware of the following
known issues on Microsoft Windows platforms.
Problem
On Windows operating systems, the USB CLI port may encounter issues preventing the terminal emulator
from reconnecting to storage after the Management Controller (MC) restarts or the USB cable is unplugged
and reconnected.
Workaround
Follow these steps when using the mini-USB cable and USB Type B CLI port to communicate out-of-band
between the host and controller module for setting network port IP addresses.
To create a new connection or open an existing connection (HyperTerminal):
1. From the Windows Control Panel, select Device Manager.
2. Connect using the USB COM port and Detect Carrier Loss option.
a. Select Connect To > Connect using: > pick a COM port from the list.
b. Select the Detect Carrier Loss check box.
The Device Manager page should show “Ports (COM & LPT)” with an entry entitled “Disk Array USB
Port (COMn)”—where n is your system’s COM port number.
3. Set network port IP addresses using the CLI (see procedure on page 44).
To restore a hung connection when the MC is restarted (any supported terminal emulator):
1. If the connection hangs, disconnect and quit the terminal emulator program.
a. Using Device Manager, locate the COMn port assigned to the Disk Array Port.
b. Right-click on the hung Disk Array USB Port (COMn), and select Disable.
c. Wait for the port to disable.
2. Right-click on the previously hung—now disabled—Disk Array USB Port (COMn), and select Enable.
3. Start the terminal emulator and connect to the COM port.
4. Set network port IP addresses using the CLI (see procedure on page 44).
Using the CLI port and cable—known issues on Windows
47
48
Connecting to the controller CLI port
6
Basic operation
Verify that you have completed the sequential “Installation Checklist” instructions in Table 1 (page 19).
Once you have successfully completed steps 1 through 8 therein, you can access the management
interface using your web browser, to complete the system setup.
Accessing the SMU
Upon completing the hardware installation, you can access the web-based management interface—SMU
(Storage Management Utility)—from the controller module 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 the
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.
This brief Sign In discussion assumes proper web browser setup.
IMPORTANT: For detailed information on accessing and using the SMU, see the “Getting started” section
in the web-posted HP MSA 2040 SMU Reference Guide.
The Getting Started section provides instructions for signing-in to the SMU, introduces key concepts,
addresses browser setup, and provides tips for using the main window and the help window.
TIP:
After signing in to the 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 the 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
NOTE: See the “Installing a license” topic within the SMU Reference Guide for instructions about creating
a temporary license or installing a permanent license.
IMPORTANT: If the system is used in a VMware environment, set the system Missing LUN Response option to
use its Illegal Request setting. To do so, see either the configuration topic “Changing the missing LUN response”
in the SMU Reference Guide or the command topic “set-advanced-settings” in the CLI Reference Guide.
Accessing the SMU
49
50
Basic operation
7
Troubleshooting
USB CLI port connection
MSA 2040 controllers feature a 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" (page 43) for more information.
Fault isolation methodology
MSA 2040 controllers provide many ways to isolate faults. This section presents the basic methodology
used to locate faults within a storage system, and to identify the associated Field-replaceable Units (FRUs)
affected.
As noted in "Basic operation" (page 49), use the SMU to configure and provision the system upon
completing the hardware installation. As part of this process, configure and enable event notification so the
system will notify you when a problem occurs that is at or above the configured severity (see “Using the
Configuration Wizard > Configuring event notification” within the SMU Reference Guide). With event
notification configured and enabled, you can follow the recommended actions in the notification message
to resolve the problem, as further discussed in the options presented below.
Basic steps
The basic fault isolation steps are listed below:
• Gather fault information, including using system LEDs [see "Gather fault information" (page 52)].
• Determine where in the system the fault is occurring [see "Determine where the fault is occurring"
(page 52)].
• Review event logs [see "Review the event logs" (page 52)].
• If required, isolate the fault to a data path component or configuration [see "Isolate the fault"
(page 53)].
Cabling systems to enable use of the licensed Remote Snap feature—to replicate volumes—is another
important fault isolation consideration pertaining to initial system installation. See "Isolating Remote Snap
replication faults" (page 61) for more information about troubleshooting during initial setup.
Options available for performing basic steps
When performing fault isolation and troubleshooting steps, select the option or options that best suit your
site environment. Use of any option (four options are described below) is not mutually-exclusive to the use
of another option. You can use the SMU to check the health icons/values for the system and its
components to ensure that everything is okay, or to drill down to a problem component. If you discover a
problem, both the SMU and the CLI provide recommended-action text online. Options for performing basic
steps are listed according to frequency of use:
• Use the SMU.
• Use the CLI.
• Monitor event notification.
• View the enclosure LEDs.
Use the SMU
The SMU uses health icons to show OK, Degraded, Fault, or Unknown status for the system and its
components. The SMU enables you to monitor the health of the system and its components. If any
component has a problem, the system health will be Degraded, Fault, or Unknown. Use the SMU GUI to
drill down to find each component that has a problem, and follow actions in the Health Recommendations
field for the component to resolve the problem.
USB CLI port connection
51
Use the CLI
As an alternative to using the SMU, you can run the show system command in the CLI to view the health
of the system and its components. If any component has a problem, the system health will be Degraded,
Fault, or Unknown, and those components will be listed as Unhealthy Components. Follow the
recommended actions in the component Health Recommendations field to resolve the problem.
Monitor event notification
With event notification configured and enabled, you can view event logs to monitor the health of the
system and its components. If a message tells you to check whether an event has been logged, or to view
information about an event in the log, you can do so using either the SMU or the CLI. Using the SMU, you
would view the event log and then click on the event message to see detail about that event. Using the CLI,
you would run the show events detail command (with additional parameters to filter the output) to
see the detail for an event.
View the enclosure LEDs
You can view the LEDs on the hardware (while referring to LED descriptions for your enclosure model) to
identify component status. If a problem prevents access to either the SMU or the CLI, this is the only option
available. However, monitoring/management is often done at a management console using storage
management interfaces, rather than relying on line-of-sight to LEDs of racked hardware components.
Performing basic steps
You can use any of the available options in performing the basic steps comprising the fault isolation
methodology.
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 quickly.
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 the enclosure right ear (see "Front panel components"
(page 13)) 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 the SMU to verify any faults found while viewing the LEDs. The 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. The
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. Each event has a numeric code that identifies the type of event that
occurred, and has one of the following severities:
• Critical. A failure occurred that may cause a controller to shut down. Correct the problem immediately.
• Error. A failure occurred that may affect data integrity or system stability. Correct the problem as soon
as possible.
• Warning. A problem occurred that may affect system stability, but not data integrity. Evaluate the
problem and correct it if necessary.
52
Troubleshooting
• Informational. A configuration or state change occurred, or a problem occurred that the system
corrected. No immediate action is required.
See the HP MSA 2040 Event Descriptions Reference Guide for information about specific events, located
at your HP MSA 2040 manuals page: http://www.hp.com/support/msa2040/Manuals.
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 vdisk 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 either hardware or
software.
The Log Collector utility allows customers to gather log information for use during support calls. See the
Software Support and Documentation DVD that shipped 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, connectors, or data host.
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 the 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 the 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.
Stopping I/O
When troubleshooting disk drive and connectivity faults, stop I/O to the affected vdisks from all hosts and
remote systems as a data protection precaution. As an additional data protection precaution, it is helpful to
conduct regularly scheduled backups of your data.
IMPORTANT:
Stopping I/O to a vdisk is a host-side task, and falls outside the scope of this document.
When on-site, you can verify that there is no I/O activity by briefly monitoring the system LEDs; however,
when accessing the storage system remotely, this is not possible. Remotely, you can use the show
vdisk-statistics command to determine if input and output has stopped. Perform these steps:
1. Using the CLI, run the show vdisk-statistics command.
Stopping I/O
53
The Number of Reads and Number of Writes outputs show the number of these operations that
have occurred since the statistic was last reset, or since the controller was restarted.
2. Run the show vdisk-statistics command a second time.
This provides you a specific window of time (the interval between requesting the statistics) to determine
if data is being written to or read from the disk.
3. If any reads or writes occur during this interval, a host is still reading from or writing to this vdisk.
Continue to stop IOPS from hosts, and repeat step 1 until the Number of Reads and Number of
Writes statistics are zero.
See the HP MSA 2040 CLI Reference Guide for additional information, at your HP MSA 2040 manuals
page: http://www.hp.com/support/msa2040/Manuals.
Diagnostic steps
This section describes possible reasons and actions to take when an LED indicates a fault condition during
initial system setup. See "LED descriptions" (page 73) for descriptions of all LED statuses.
NOTE: Once event notification is configured and enabled using the SMU, you can view event logs to
monitor the health of the system and its components using the GUI.
In addition to monitoring LEDs via line-of-sight observation of racked hardware components when
performing diagnostic steps, you can also monitor the health of the system and its components using the
management interfaces. Be mindful of this when reviewing the Actions column in the diagnostics tables,
and when reviewing the step procedures provided in this chapter.
Is the enclosure front panel Fault/Service Required LED amber?
Answer
Possible reasons
Actions
No
System functioning properly.
No action required.
Yes
A fault condition exists/occurred.
•
If installing an I/O module FRU, the
module has not gone online and likely
failed its self-test.
•
•
•
Table 4
Check the LEDs on the back of the controller enclosure to
narrow the fault to a FRU, connection, or both.
Check the event log for specific information regarding the
fault; follow any Recommended Actions.
If installing an IOM FRU, try removing and reinstalling the
new IOM, and check the event log for errors.
If the above actions do not resolve the fault, isolate the
fault, and contact an authorized service provider for
assistance. Replacement may be necessary.
Diagnostics LED status: Front panel “Fault/Service Required”
Is the enclosure rear panel FRU OK LED off?
Answer
Possible reasons
Actions
No
(blinking)
System functioning properly.
System is booting.
No action required.
Wait for system to boot.
Yes
The controller module is not powered
on.
The controller module has failed.
•
Table 5
54
•
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.
Diagnostics LED status: Rear panel “FRU OK”
Troubleshooting
Is the enclosure rear 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:
•
Table 6
•
•
•
Hardware-controlled power-up error
Cache flush error
Cache self-refresh error
•
•
Restart this controller from the other controller using the
SMU or the CLI.
If the above action does not resolve the fault, remove the
controller and reinsert it.
If the above action does not resolve the fault, contact an
authorized service provider for assistance. It may be
necessary to replace the controller.
Diagnostics LED status: Rear panel “Fault/Service Required”
Are both disk drive module LEDs off (Online/Activity and Fault/UID)?
Answer
Possible reasons
Yes
•
•
•
Table 7
There is no power.
The disk is offline.
The disk is not configured.
Actions
•
Check that the disk drive is fully inserted and latched in
place, and that the enclosure is powered on.
Diagnostics LED status: Front panel disks “Online/Activity” and “Fault/UID”
Is the disk drive module Fault/UID LED blinking amber?
Answer
Possible reasons
Actions
No, but the
Online/Activity
LED is blinking.
The disk drive is rebuilding.
No action required.
Yes, and the
Online/Activity
LED is off.
The disk drive is offline. A
predictive failure alert may have
been received for this device.
•
Yes, and the
Online/Activity
LED is blinking.
The disk drive is active, but a
predictive failure alert may have
been received for this device.
•
Table 8
CAUTION: Do not remove a disk drive that is
reconstructing. Removing a reconstructing disk drive
might terminate the current operation and cause data
loss.
•
•
•
•
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.
Diagnostics LED status: Front panel disks “Fault/UID”
Diagnostic steps
55
Is a connected host port Host Link Status LED off?
Answer
Possible reasons
Actions
No
System functioning properly.
No action required.
(see Link LED note: page 79)
Yes
The link is down.
•
•
•
•
•
•
•
•
Table 9
Check cable connections and reseat if necessary.
Inspect cables for damage. Replace cable if necessary.
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 the SMU, review event logs for indicators of a specific fault
in a host data path component; follow any Recommended
Actions.
Contact an authorized service provider for assistance.
See "Isolating a host-side connection fault" (page 58).
Diagnostics LED status: Rear panel “Host Link Status”
Is a connected port Expansion Port Status LED off?
Answer
Possible reasons
Actions
No
System functioning properly.
No action required.
Yes
The link is down.
•
•
•
•
•
•
Table 10
Check cable connections and reseat if necessary.
Inspect cable for damage. Replace cable if necessary.
Swap cables to determine if fault is caused by a defective
cable. Replace cable if necessary.
In the SMU, review event logs for indicators of a specific fault
in a host data path component; follow any Recommended
Actions.
Contact an authorized service provider for assistance.
See "Isolating a controller module expansion port connection
fault" (page 60).
Diagnostics LED status: Rear panel “Expansion Port Status”
Is a connected port 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.
Table 11 Diagnostics LED status: Rear panel “Network Port Link Status”
56
Troubleshooting
Is the power supply 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 to which it connects.
Check that the power supply FRU is firmly locked into
position.
In the SMU, check the event log for specific information
regarding the fault; follow any Recommended Actions.
If the above action does not resolve the fault, isolate the
fault, and contact an authorized service provider for
assistance.
Table 12 Diagnostics LED status: Rear panel power supply “Input Power Source”
Is the power supply 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.
•
•
•
Table 13
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.
Diagnostics LED status: Rear panel power supply: “Voltage/Fan Fault/Service Required”
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 supercapacitor. This process typically takes 60 seconds per 1 Gbyte of cache. After the
cache is copied to CompactFlash, the remaining power left in the supercapacitor is used to refresh the
cache memory. While the cache is being maintained by the supercapacitor, the Cache Status LED flashes
at a rate of 1/10 second on and 9/10 second off.
IMPORTANT: Transportable cache only applies to single-controller configurations. In dual controller
configurations, there is no need to transport cache from a failed controller to a replacement controller
because the cache is duplicated between the peer controllers (subject to volume write optimization setting).
Controller failure in a single-controller configuration
57
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.
If valid data is thought to be in Flash, see Transporting cache;
otherwise, replace the controller module.
No, the Cache Status LED is off, and the
controller boots.
The system has flushed data to disks. If the problem persists,
replace the controller module.
Yes, at a strobe 1:10 rate - 1 Hz, and the
controller does not boot.
See Transporting cache.
Yes, at a strobe 1:10 rate - 1 Hz, and the
controller boots.
The system is flushing data to CompactFlash. If the problem
persists, replace the controller module.
Yes, at a blink 1:1 rate - 1 Hz, and the controller
does not boot.
See Transporting cache.
Yes, at a blink 1:1 rate - 1 Hz, and the controller
boots.
The system is in self-refresh mode. If the problem persists, replace
the controller module.
Table 14 Diagnostics LED status: Rear panel “Cache Status”
NOTE:
See also "Cache Status LED details" (page 80).
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 the procedure outlined in HP MSA Controller Module
Replacement Instructions shipped with the replacement controller module. Failure to use this procedure will
result in the loss of data stored in the cache module.
CAUTION: Remove the controller module only after the copy process is complete, which is indicated by
the Cache Status LED being off, or blinking at 1:10 rate.
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/link activity LED is green. If there is I/O activity, the 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 host ports with SFPs
The procedure below applies to MSA 2040 SAN controller enclosures employing small form factor
pluggable (SFP) transceiver connectors in 4/8/16 Gb FC, 10GbE iSCSI, or 1 Gb iSCSI host interface
ports. In the following procedure, “SFP and host cable” is used to refer to any of the qualified SFP options
supporting Converged Network Controller ports used for I/O or replication.
1. Halt all I/O to the storage system as described in "Stopping I/O" (page 53).
2. Check the host link status/link activity LED.
If there is activity, halt all applications that access the storage system.
58
Troubleshooting
3. Check the Cache Status LED to verify that the controller cached data is flushed to the disk drives.
• Solid – Cache contains data yet to be written to the disk.
• Blinking – Cache data is being written to CompactFlash.
• Flashing at 1/10 second on and 9/10 second off – Cache is being refreshed by the supercapacitor.
• Off – Cache is clean (no unwritten data).
4. Remove the SFP and host cable and inspect for damage.
5. Reseat the SFP and host cable.
Is the host link status/link activity 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.
6. Move the SFP and host 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/link activity 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/link activity LED remains off, you have
isolated the fault to the controller module port. Replace the controller module.
• No – Proceed to the next step.
7. Swap the SFP with the known good one.
Is the host link status/link activity LED on?
• Yes – You have isolated the fault to the SFP. Replace the SFP.
• No – Proceed to the next step.
8. Re-insert the original SFP and swap the cable with a known good one.
Is the host link status/link activity LED on?
• Yes – You have isolated the fault to the cable. Replace the cable.
• No – Proceed to the next step.
9. Verify that the switch, if any, is operating properly. If possible, test with another port.
10. Verify that the HBA is fully seated, and that the PCI slot is powered on and operational.
11. 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/link activity 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.
12. Move the cable and SFP back to its original port.
Is the host link status/link activity LED on?
• No – The controller module 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 damaged SFPs, cables, and HBAs.
Host-side connection troubleshooting featuring SAS host ports
The procedure below applies to MSA 2040 SAS controller enclosures employing 12 Gb SFF-8644
connectors in the HD mini-SAS host ports used for I/O.
1. Halt all I/O to the storage system as described in "Stopping I/O" (page 53).
2. Check the host activity LED.
If there is activity, halt all applications that access the storage system.
3. Check the Cache Status LED to verify that the controller cached data is flushed to the disk drives.
• Solid – Cache contains data yet to be written to the disk.
• Blinking – Cache data is being written to CompactFlash.
Isolating a host-side connection fault
59
• Flashing at 1/10 second on and 9/10 second off – Cache is being refreshed by the supercapacitor.
• Off – Cache is clean (no unwritten data).
4. Reseat the host cable and inspect for damage.
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.
5. Move the host cable to a port with a known good link status.
This step isolates the problem to the external data path (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 host cable and host-side devices are functioning properly. Return the
cable to the original port. If the link status LED remains off, you have isolated the fault to the
controller module port. Replace the controller module.
• No – Proceed to the next step.
6. Verify that the switch, if any, is operating properly. If possible, test with another port.
7. Verify that the HBA is fully seated, and that the PCI slot is powered on and operational.
8. Replace the HBA with a known good HBA, or move the host side cable 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.
9. Move the host cable back to its original port.
Is the host link status LED on?
• No – The controller module 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 damaged cables and HBAs.
Isolating a controller module expansion port connection fault
During normal operation, when a controller module 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 as described in "Stopping I/O" (page 53).
2. Check the host activity LED.
If there is activity, halt all applications that access the storage system.
3. Check the Cache Status LED to verify that the controller cached data is flushed to the disk drives.
• Solid – Cache contains data yet to be written to the disk.
• Blinking – Cache data is being written to CompactFlash.
• Flashing at 1/10 second on and 9/10 second off – Cache is being refreshed by the supercapacitor.
• Off – Cache is clean (no unwritten data).
4. 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.
60
Troubleshooting
• No – Proceed to the next step.
5. Move the expansion cable to a port on the controller enclosure with a known good link status.
This step isolates the problem to the expansion cable or to the controller module expansion port.
Is the expansion port status LED on?
• Yes – You now know that the expansion cable is good. Return the cable to the original port. If the
expansion port status LED remains off, you have isolated the fault to the controller module
expansion port. Replace the controller module.
• No – Proceed to the next step.
6. Move the expansion cable back to the original port on the controller enclosure.
7. 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 port. Replace the expansion module.
• No – Proceed to the next step.
8. 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 must be replaced.
Isolating Remote Snap replication faults
Cabling for replication
Remote Snap replication is a licensed feature for disaster-recovery. This feature performs asynchronous
(batch) replication of block-level data from a volume on a local storage system to a volume that can be on
the same system or a second, independent system. 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" (page 36)
for host connection information concerning Remote Snap.
Replication setup and verification
After storage systems and hosts are cabled for replication, you can use the Replication Setup Wizard in the
SMU 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 HP Remote Snap technical white paper for replication best practices
• See HP MSA 2040 SMU Reference Guide for procedures to setup and manage replications
• See HP MSA 2040 CLI Reference Guide for replication commands and syntax
• See HP MSA 2040 Event Descriptions Reference Guide for replication event reporting
Basic information for enabling the MSA 2040 SAN 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 Reference Guide.
• For best practices concerning replication-related tasks, see the technical white paper.
• Use Wizards > Replication Setup Wizard to prepare to replicate an existing volume to another vdisk in
the 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
Isolating Remote Snap replication faults
61
secondary systems. Once setup is successfully completed, you can initiate replication from the SMU or
the CLI.
• For descriptions of replication-related events, see the Event Descriptions Reference Guide.
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.
Verify licensing of the optional feature per system:
•
•
In the Configuration View panel in the SMU, 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 feature is not enabled, obtain and install a
valid license for Remote Snap.
NOTE: Remote Snap is not supported by MSA 2040 SAS
controller enclosures.
No
Compatible firmware revision
supporting Remote Snap is not
running on each system used for
replication.
Perform the following actions on each system used for replication:
•
•
No
Invalid cabling connection.
(Check cabling for each system)
Verify controller enclosure cabling.
•
•
•
•
•
Table 15
In the Configuration View panel in the SMU, right-click the
system, and select Tools > Update Firmware.
The Update Firmware panel displays currently installed firmware
versions.
If necessary, update the controller module firmware to ensure
compatibility with other systems.
Verify use of proper cables.
Verify proper cabling paths for host connections.
Verify cabling paths between replication ports and switches on
the same fabric or network.
Verify that cable connections are securely fastened.
Inspect cables for damage and replace if necessary.
Diagnostics for replication setup: Using Remote Snap feature
Can you view information about remote links?
Answer
Possible reasons
Actions
Yes
System functioning properly.
No action required.
No
Invalid login credentials
•
•
Verify user name with Manage role on remote system.
Verify user’s password on remote system.
No
Communication link is down.
•
•
Verify controller enclosure cabling (see Table 15).
In the SMU, review event logs for indicators of a specific fault in
a host or replication data path component.
Verify valid IP address of the network port on the remote system.
In the Configuration View panel in the SMU, right-click the
remote system, and select Tools > Check Remote System Link.
Click Check Links.
•
•
Table 16
62
Troubleshooting
Diagnostics for replication setup: Viewing information about remote links
Can you create a replication set?
Answer
Possible reasons
Actions
Yes
System functioning properly.
No action required.
No
Selected link type or port-to-link
connections are incorrect.
• Remote Replication mode: In the Configuration View panel in
the SMU, right-click the remote system, and select Tools > Check
Remote System Link. Click Check Links to verify correct link type
and remote host port-to-link connections.
• Local Replication mode: In the Configuration View panel in the
SMU, right-click the local system, and select Tools > Check Local
System Link. Click Check Links to verify correct link type and
local host port-to-link connections.
No
On controller enclosures with iSCSI
host interface ports, replication set
creation fails due to use of CHAP.
If using CHAP (Challenge-Handshake Authentication Protocol),
configure it as described in the SMU topics “Using the Replication
Setup Wizard” or “Replicating a volume.”
No
Unable to select the replication
mode (Local or Remote)?
•
•
In the SMU, review event logs for indicators of a specific fault in
a host or replication data path component. Follow any
Recommended Actions.
Local Replication mode replicates to a secondary volume
residing in the local storage system.
• Verify valid links
On dual-controller systems, verify that A ports can access B
ports on the partner controller, and vice versa.
•
•
Verify existence of a either a replication-prepared volume of
the same size as the master volume, or a vdisk with sufficient
unused capacity.
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 the vdisk.
• Verify valid IP address of remote system network port.
• Verify user name with Manage role on remote system.
• Verify user password on remote system.
NOTE: If the remote system has not been added, it cannot
be selected.
No
No
Unable to select the secondary
volume (the destination volume on
the vdisk to which you will replicate
data from the primary volume)?
•
Communication link is down.
See actions described in "Can you view information about remote
links?" (page 62).
•
In the SMU, review event logs for indicators of a specific fault in
a replication data path component. Follow any Recommended
Actions.
Verify valid specification of the secondary volume according to
either of the following criteria:
• Creation of new volume on the vdisk
• Selection of replication-prepared volume
Table 17 Diagnostics for replication setup: Creating a replication set
Isolating Remote Snap replication faults
63
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.
See actions described in "Can you successfully use the Remote Snap
feature?" (page 62).
No
Nonexistent replication set.
•
•
•
No
Network error occurred during
in-progress replication.
•
•
•
No
Communication link is down.
Determine existence of primary or secondary volumes.
If a replication set has not been successfully created, use the
SMU Replication Setup Wizard to create one.
In the SMU, review event logs for indicators of a specific fault in
a replication data path component. Follow any Recommended
Actions.
In the SMU, review event logs for indicators of a specific fault in
a replication data path component. Follow any Recommended
Actions.
In the Configuration View panel in the SMU, 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.
See actions described in "Can you view information about remote
links?" (page 62).
Table 18 Diagnostics for replication setup: Replicating a volume
Can you view a replication image?
Answer
Possible reasons
Actions
Yes
System functioning properly.
No action required.
No
Nonexistent replication image.
•
•
No
Communication link is down.
In the Configuration View panel in the SMU, expand vdisks and
their volumes to reveal the existence of a replication image or
images.
If a replication image has not been successfully created, use the
SMU to create one as described in the “Using Remote Snap to
replicate volumes” topic within the SMU Guide.
See actions described in "Can you view information about remote
links?" (page 62).
Table 19 Diagnostics for replication setup: Viewing a replication image
Can you view remote systems?
Answer
Possible reasons
Actions
Yes
System functioning properly.
No action required.
No
Communication link is down.
See actions described in "Can you view information about remote
links?" (page 62).
Table 20
64
Troubleshooting
Diagnostics for replication setup: Viewing a remote system
Resolving voltage and temperature warnings
1. Check that all of the fans are working by making sure the Voltage/Fan Fault/Service Required LED on
each power supply is off, or by using the SMU to check enclosure health status. In the Configuration
View panel, right-click the enclosure and select View > Overview to view the health status of the
enclosure and its components. The Enclosure Overview page enables you to see information about
each enclosure and its physical components in front, rear, and tabular views—using graphical or
tabular presentation—allowing you to view the health status of the enclosure and its components.
See "Options available for performing basic steps" (page 51) for a description of health status icons
and alternatives for monitoring enclosure health.
2. Make sure that all modules are fully seated in their slots with latches 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 module one at a time.
5. Replace the controller modules one at a time.
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 21 Power supply sensor descriptions
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 speed drops below 4,000 RPM, the EMP considers it a failure and posts an alarm in the storage system
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 22
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.
Resolving voltage and temperature warnings
65
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 23
Controller module temperature sensor descriptions
Description
Normal operating
range
Warning operating
range
Critical operating
range
Shutdown values
CPU temperature
3°C–88°C
0°C–3°C,
88°C–90°C
> 90°C
0°C
100°C
FPGA temperature
3°C–97°C
0°C–3°C,
97°C–100°C
None
0°C
105°C
Onboard temperature 1
0°C–70°C
None
None
None
Onboard temperature 2
0°C–70°C
None
None
None
Onboard temperature 3
(Capacitor temperature)
0°C–70°C
None
None
None
CM temperature
5°C–50°C
≤ 5°C,
≥ 50°C
≤ 0°C,
≥ 55°C
None
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 24
Power supply temperature sensor descriptions
Description
Normal operating range
Power Supply 1 temperature
–10°C–80°C
Power Supply 2 temperature
–10°C–80°C
Power supply module voltage sensors
Power supply voltage sensors ensure that the enclosure power supply voltage is within normal ranges.
There are three voltage sensors per power supply.
Table 25
66
Voltage sensor descriptions
Sensor
Event/Fault LED condition
Power supply 1 voltage, 12V
< 11.00V
> 13.00V
Power supply 1 voltage, 5V
< 4.00V
> 6.00V
Power supply 1 voltage, 3.3V
< 3.00V
> 3.80V
Troubleshooting
8
Support and other resources
Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
• Product model names and numbers
• Technical support registration number (if applicable)
• Product serial numbers
• Error messages
• Operating system type and revision level
• Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber’s Choice for Business website:
http://www.hp.com/go/e-updates
After registering, you will receive e-mail notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Related information
The following documents provide related information:
• HP MSA System Racking Instructions
• HP MSA 2040 Quick Start Instructions
• HP MSA 2040 Cable Configuration Guide
• HP MSA 2040 SMU Reference Guide
• HP MSA 2040 CLI Reference Guide
• HP MSA 2040 Event Descriptions Reference Guide
• HP MSA Controller Module Installation Instructions
• HP MSA 2040 I/O Module Installation Instructions
• HP Transceiver Installation Instructions
• HP MSA Controller Module Replacement Instructions
• HP Chassis Replacement Instructions
• HP MSA 2040 I/O Module Replacement Instructions
• HP MSA Power and Cooling Module Replacement Instructions
• HP MSA Bezel Ears Replacement Instructions
• HP Transceiver Replacement Instructions
• HP MSA Drive Module Replacement Instructions
You can find these documents on the HP MSA 2040 user documents page:
http://www.hp.com/support/msa2040/Manuals
Contacting HP
67
Websites
• HP MSA 2040 home page: http://www.hp.com/support/msa2040
• HP MSA 2040 QuickSpecs: http://www.hp.com/support/msa2040/QuickSpecs
• HP MSA 2040 user documents: http://www.hp.com/support/msa2040/Manuals
• HP MSA 2040 best practices: http://www.hp.com/support/msa2040/BestPractices
• HP MSA 2040 firmware downloads: http://www.hp.com/support
• HP MSA 2040 Guided Troubleshooting: http://www.hp.com/support/msa2040/Troubleshooting
• HP Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products:
http://www.hp.com/support/Safety-Compliance-EnterpriseProducts
• HP Systems Insight Manager website: http://www.hp.com/go/hpsim
• HP Technical Support website: http://www.hp.com/support
• Single Point of Connectivity Knowledge (SPOCK) website: http://www.hp.com/storage/spock
• Servers: http://www.hp.com/go/servers
• SAN infrastructure: http://www.hp.com/go/san
Prerequisites
Knowledge of relevant topics is required for installing and using this product:
• Servers and computer networks
• Network administration
• Storage system installation and configuration
• Storage area network management
• Relevant protocols:
• Fibre Channel (FC)
• Internet SCSI (iSCSI)
• Serial Attached SCSI (SAS)
• Ethernet
Troubleshooting resources
See Chapter 7 for simple troubleshooting procedures pertaining to initial setup of the controller enclosure
hardware. The chapter describes fault isolation methodology, basic fault isolation steps, and options
available for performing the basic steps using the Storage Management Utility (SMU), the Command-line
Interface (CLI), event notification, and LEDs. Diagnostics steps are also described.
For additional information see the HP MSA 2040 Guided Troubleshooting website:
http://www.hp.com/support/msa2040/Troubleshooting
68
Support and other resources
Typographic conventions
Table 26
Document conventions
Convention
Element
Blue text: Figure 1
Cross-reference links
Blue, bold, underlined text
Email addresses
Blue, underlined text: http://www.hp.com
Website addresses
Bold text
•
•
•
Italic text
Text emphasis
Monospace text
•
•
•
•
File and directory names
System output
Code
Commands, their arguments, and argument values
Monospace, italic text
•
•
Code variables
Command variables
Monospace, bold text
Emphasized monospace text
Indicates that failure to follow directions could result in bodily harm or death.
WARNING!
CAUTION:
Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT:
NOTE:
TIP:
Keys that are pressed
Text typed into a GUI element, such as a box
GUI elements that are clicked or selected, such as menu and list
items, buttons, and check boxes
Provides clarifying information or specific instructions.
Provides additional information.
Provides helpful hints and shortcuts.
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, fasten racks together securely.
• Extend only one rack component at a time. Racks may become unstable if more than one component is
extended.
Typographic conventions
69
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
70
Support and other resources
9
Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the documentation,
send any errors, suggestions, or comments to Documentation Feedback ([email protected]). Include
the document title and part number, version number, or the URL when submitting your feedback.
Documentation feedback
71
72
Documentation feedback
A
LED descriptions
Front panel LEDs
HP MSA 2040 models support small form factor (SFF) and large form factor (LFF) enclosures. The SFF
chassis, configured with 24 2.5" SFF disks, is used as a controller enclosure. The LFF chassis, configured
with 12 3.5" LFF disks, is used as either a controller enclosure or drive enclosure.
Supported drive enclosures, used for adding storage, are available in LFF or SFF chassis. The MSA 2040
6 Gb 3.5" 12-drive enclosure is the large form factor drive enclosure used for storage expansion. The HP
D2700 6 Gb enclosure, configured with 25 2.5" SFF disks, is the small form factor drive enclosure used for
storage expansion. See "SFF drive enclosure" (page 17) for a description of the D2700.
MSA 2040 Array SFF enclosure
Left ear
1
Right ear
2
3
4
5
6
7
8
9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 24
4
1
2
3
5
Note: Integers on disks indicate drive slot numbering sequence.
6
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" (page 75).
3
Disk drive Fault/UID
See "Disk drive LEDs" (page 75).
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.
Figure 31 LEDs: MSA 2040 Array SFF enclosure front panel
Front panel LEDs
73
MSA 2040 Array LFF or supported 12-drive expansion enclosure
Left ear
Right ear
1
4
7
10
2
5
8
11
3
6
9
12
4
7 10
3 6
9 12
1
4
1
2
3
5
Note: Integers on disks indicate drive slot numbering sequence.
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" (page 75).
3
Disk drive Fault/UID
See "Disk drive LEDs" (page 75).
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.
Figure 32 LEDs: MSA 2040 Array LFF enclosure front panel
74
6
LED descriptions
Disk drive LEDs
3.5" LFF disk drive
2 1
2.5" SFF disk drive
(sled grate is not shown)
Disk drive LED key:
2
1 = Fault/UID (amber/blue)
2 = Online/Activity (green)
1
Online/Activity (green)
Fault/UID (amber/blue)
Description
On
Off
Normal operation. The disk drive is online, but it is not
currently active.
Blinking irregularly
Off
The disk drive is active and operating normally.
Off
Amber; blinking regularly
(1 Hz)
Offline; the disk is not being accessed. A predictive failure
alert may have been received for this device. Further
investigation is required.
On
Amber; blinking regularly
(1 Hz)
Online; possible I/O activity. A predictive failure alert may
have been received for this device. Further investigation is
required.
Blinking irregularly
Amber; blinking regularly
(1 Hz)
The disk drive is active, but a predictive failure alert may
have been received for this disk. Further investigation is
required.
Off
Amber; solid1
Offline; no activity. A failure or critical fault condition has
been identified for this disk.
Off
Blue; solid
Offline. The disk drive has been selected by a
management application such as the SMU.
On or blinking
Blue; solid
The controller is driving I/O to the disk, and it has been
selected by a management application such as the SMU.
Blinking regularly (1 Hz)
Off
CAUTION: Do not remove the disk drive.
Removing a disk may terminate the current
operation and cause data loss. The disk is
reconstructing.
Off
Off
Either there is no power, the drive is offline, or the drive is
not configured.
1This
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.
Figure 33 LEDs: Disk drive combinations — enclosure front panel
Front panel LEDs
75
Rear panel LEDs
Controller enclosure—rear panel layout
The diagram and table below display and identify important component items comprising the rear panel
layout of the MSA 2040 controller enclosure (MSA 2040 SAN is shown in the example). Diagrams and
tables on the following pages further describe rear panel LED behavior for component field-replaceable
units.
1
4
2
8 -
q
1
6Gb/s
PORT 1
PORT 2
PORT 3
PORT 4
CACHE
SERVICE−2
CLI
ACT
LINK
ACT
LINK
SERVICE−1
CLI
3
6Gb/s
PORT 1
PORT 2
PORT 3
PORT 4
CACHE
SERVICE−2
CLI
SERVICE−1
CLI
w 56 7 9
=
MSA 2040 controller enclosure
(rear panel locator illustration)
1
AC Power supplies [see Figure 38 (page 80)]
2
Controller module A [see Figure 35 (page 77)]
3
Controller module B [see Figure 35 (page 77)]
4
Host ports: used for host connection or replication
5
CLI port (USB - Type B)
6
Service port 2 (used by service personnel only)
7
Reserved for future use
8 Network port
9 Service port 1 (used by service personnel only)
10 Disabled button (used by engineering only)
(Stickers shown covering the openings)
11 SAS expansion port
12 DC Power supply (2) — (DC model only)
13 DC Power switch [see Figure 38 (page 80)]
Figure 34 MSA 2040 SAN Array: rear panel
A controller enclosure accommodates two power supply FRUs of the same type—either both AC or both
DC—within the two power supply slots (see two instances of callout 1 above). The controller enclosure
accommodates two controller module FRUs of the same type within the I/O module slots (see callouts 2
and 3 above).
IMPORTANT: If the MSA 2040 controller enclosure is configured with a single controller module, the
controller module must be installed in the upper slot (see callout 2 above), and an I/O module blank must
be installed in the lower slot (see callout 3 above). This configuration is required to allow sufficient air flow
through the enclosure during operation.
The diagrams with tables that immediately follow provide descriptions of the different controller modules
and power supply modules that can be installed into the rear panel of an MSA 2040 controller enclosure.
Showing controller modules and power supply modules separately from the enclosure provides improved
clarity in identifying the component items called out in the diagrams and described in the tables.
Descriptions are also provided for optional drive enclosures supported by MSA 2040 controller enclosures
for expanding storage capacity.
76
LED descriptions
MSA 2040 SAN controller module—rear panel LEDs
5
1
7
6Gb/s
PORT 1
PORT 2
PORT 3
PORT 4
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
= FC LEDs
3
2
4
6
8 9
:
= iSCSI LEDs
LED
Description
Definition
1
Host 4/8/16 Gb FC1
Link Status/
Link Activity
Off — No link detected.
Green — The port is connected and the link is up.
Blinking green — The link has I/O or replication activity.
2
Host 10GbE iSCSI2,3
Link Status/
Link Activity
Off — No link detected.
Green — The port is connected and the link is up.
Blinking green — The link has I/O or replication activity.
3
Network Port Link
Active Status
Off — The Ethernet link is not established, or the link is down.
Green — The Ethernet link is up (applies to all negotiated link speeds).
4
Network Port Link Speed
Off — Link is up at 10/100base-T negotiated speeds.
Amber — Link is up and negotiated at 1000base-T.
5
OK to Remove
Off — The controller module is not prepared for removal.
Blue — The controller module is prepared for removal.
6
Unit Locator
Off — Normal operation.
Blinking white — Physically identifies the controller module.
7
FRU OK
Off — Controller module is not OK.
Blinking green — System is booting.
Green — Controller module is operating normally.
8
Fault/Service Required
Amber — A fault has been detected or a service action is required.
Blinking amber — Hardware-controlled power-up or a cache flush or restore
error.
9
Cache Status
Green — Cache contains unwritten data and operation is normal. The
unwritten information can be log or debug data that remains in the cache, so
a Green cache status LED does not, by itself, indicate that any user data is at
risk or that any action is necessary.
Off — In a working controller, cache is clean (contains no unwritten data).
This is an occasional condition that occurs while the system is booting.
Blinking green — A CompactFlash flush or cache self-refresh is in progress,
indicating cache activity.
See also Cache Status LED details.
10
Expansion Port Status
Off — The port is empty or the link is down.
On — The port is connected and the link is up.
1
When in FC mode, the SFPs must be a qualified 8 Gb or 16 Gb fibre optic option described in QuickSpecs. A 16 Gbit/s SFP can
run at 16 Gbit/s, 8 Gbit/s, 4 Gbit/s, or auto-negotiate its link speed. An 8 Gbit/s SFP can run at 8 Gbit/s, 4 Gbit/s, or
auto-negotiate its link speed.
2
When in 10GbE iSCSI mode, the SFPs must be a qualified 10GbE iSCSI optic option as described in QuickSpecs.
3
When powering up and booting, iSCSI LEDs will be on/blinking momentarily, then they will switch to the mode of operation.
Figure 35 LEDs: MSA 2040 SAN controller module (FC and 10GbE SFPs)
Rear panel LEDs
77
NOTE: See "MSA 2040 SAN" (page 11) for information about supported combinations of host interface
protocols using Converged Network Controller ports.
5
1
7
6Gb/s
PORT 1
PORT 2
PORT 3
PORT 4
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
3
2
= FC LEDs
4
6
8 9
:
= iSCSI LEDs
LED
Description
Definition
1
Not used in example1
iSCSI2,3
The FC SFP is not show in this example [see Figure 35 (page 77)].
2
Host 1 Gb
Link Status/
Link Activity
Off — No link detected.
Green — The port is connected and the link is up; or the link has I/O or
replication activity.
3
Network Port Link
Active Status
Off — The Ethernet link is not established, or the link is down.
Green — The Ethernet link is up (applies to all negotiated link speeds).
4
Network Port Link Speed
Off — Link is up at 10/100base-T negotiated speeds.
Amber — Link is up and negotiated at 1000base-T.
5
OK to Remove
Off — The controller module is not prepared for removal.
Blue — The controller module is prepared for removal.
6
Unit Locator
Off — Normal operation.
Blinking white — Physically identifies the controller module.
7
FRU OK
Off — Controller module is not OK.
Blinking green — System is booting.
Green — Controller module is operating normally.
8
Fault/Service Required
Amber — A fault has been detected or a service action is required.
Blinking amber — Hardware-controlled power-up or a cache flush or restore
error.
9
Cache Status
Green — Cache contains unwritten data and operation is normal. The
unwritten information can be log or debug data that remains in the cache, so
a Green cache status LED does not, by itself, indicate that any user data is at
risk or that any action is necessary.
Off — In a working controller, cache is clean (contains no unwritten data).
This is an occasional condition that occurs while the system is booting.
Blinking green — A CompactFlash flush or cache self-refresh is in progress,
indicating cache activity.
See also Cache Status LED details.
10
Expansion Port Status
Off — The port is empty or the link is down.
On — The port is connected and the link is up.
1When
in FC mode, the SFPs must be a qualified 8 Gb or 16 Gb fibre optic option described in QuickSpecs.
When in 1 Gb iSCSI mode, the SFPs must be a qualified RJ-45 iSCSI option as described in QuickSpecs. The 1 Gb iSCSI mode does
not support an iSCSI optic option.
3
When powering up and booting, iSCSI LEDs will be on/blinking momentarily, then they will switch to the mode of operation.
2
Figure 36 LEDs: MSA 2040 SAN controller module (1 Gb RJ-45 SFPs)
78
LED descriptions
MSA 2040 SAS controller module—rear panel LEDs
5
1
LINK
12Gb/s
S
A
S
ACT
LINK
LINK
ACT
ACT
12Gb/s
S
A
S
7
LINK
ACT
6Gb/s
SAS 1 SAS 2
SAS 3 SAS 4
CACHE
SERVICE−2
CLI
ACT
LINK
SERVICE−1
CLI
3
2
LED
1
Description
4
6
8 9
:
Definition
1
1
Host 6/12 Gb SAS,
Link Status
Off — No link detected.
Green — The port is connected and the link is up.
2
Host 6/12 Gb SAS1
Link Activity
Off — The link is idle.
Blinking green — The link has I/O activity.
3
Network Port Link
Active Status
Off — The Ethernet link is not established, or the link is down.
Green — The Ethernet link is up (applies to all negotiated link speeds).
4
Network Port Link Speed
Off — Link is up at 10/100base-T negotiated speeds.
Amber — Link is up and negotiated at 1000base-T.
5
OK to Remove
Off — The controller module is not prepared for removal.
Blue — The controller module is prepared for removal.
6
Unit Locator
Off — Normal operation.
Blinking white — Physically identifies the controller module.
7
FRU OK
Off — Controller module is not OK.
Blinking green — System is booting.
Green — Controller module is operating normally.
8
Fault/Service Required
Amber — A fault has been detected or a service action is required.
Blinking amber — Hardware-controlled power-up or a cache flush or restore
error.
9
Cache Status
Green — Cache contains unwritten data and operation is normal. The
unwritten information can be log or debug data that remains in the cache, so
a Green cache status LED does not, by itself, indicate that any user data is at
risk or that any action is necessary.
Off — In a working controller, cache is clean (contains no unwritten data).
This is an occasional condition that occurs while the system is booting.
Blinking green — A CompactFlash flush or cache self-refresh is in progress,
indicating cache activity.
See also Cache Status LED details.
10
Expansion Port Status
Off — The port is empty or the link is down.
On — The port is connected and the link is up.
See the qualified HD mini-SAS host cable options described in QuickSpecs.
Figure 37 LEDs: MSA 2040 SAS controller module
NOTE:
Once a Link Status LED is lit, it remains so, even if the controller is shutdown via the 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
Rear panel LEDs
79
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 "Powering on/powering off" (page 27)].
Cache Status LED details
If the LED is blinking evenly, a cache flush is in progress. When a controller module loses power and write
cache contains data that has not been written to disk, the supercapacitor 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 controller cache and one in CompactFlash of each controller. The
Cache Status LED illuminates solid green during the boot-up process. This behavior indicates the cache is
logging all POSTs, which will be flushed to the CompactFlash the next time the controller shuts down.
CAUTION: If the Cache Status LED illuminates solid green—and you wish to shut-down the controller—do
so from the user interface, so unwritten data can be flushed to CompactFlash.
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. Power supplies are used by controller and drive enclosures.
1
1
2
2
AC model
DC model
LED
Description
Definition
1
Input 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.
Figure 38 LEDs: MSA 2040 Storage system enclosure power supply modules
80
LED descriptions
NOTE:
See "Powering on/powering off" (page 27) for information on power-cycling enclosures.
MSA 2040 6 Gb 3.5" 12-drive enclosure—rear panel layout
MSA 2040 controllers support the MSA 2040 6 Gb 3.5" 12-drive enclosure. The front panel of the drive
enclosure looks identical to that of an MSA 2040 Array LFF. The rear panel of the drive enclosure is shown
below.
1
2
1
0
IN
0
IN
3
0
OUT
0
OUT
4 56
7
LED
Description
Definition
1
Power supply LEDs
See "Power supply LEDs" (page 80).
2
Unit Locator
Off — Normal operation.
Blinking white— Physically identifies the expansion module.
3
OK to Remove
Not implemented.
4
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.
5
FRU OK
Green — Expansion module is operating normally.
Blinking green — System is booting.
Off — Expansion module is not OK.
6
SAS In Port Status
Green — Port link is up and connected.
Off — Port is empty or link is down.
7
SAS Out Port Status
Green — Port link is up and connected.
Off — Port is empty or link is down.
Figure 39 LEDs: MSA 2040 6 Gb 3.5" 12-drive enclosure rear panel
The MSA 2040 6 Gb 3.5" 12-drive enclosure is identical in outward physical appearance to the legacy
P2000 G3 6 Gb 3.5" 12-drive enclosure. For information about upgrading P2000 G3 components for use
with MSA 2040 controllers, see "Upgrading to MSA 2040" (page 18).
D2700 6Gb drive enclosure
MSA 2040 SAN controllers support D2700 6Gb drive enclosures. For information about the D2700, visit
http://www.hp.com/support. Pictorial representations of this drive enclosure are also provided in the MSA
2040 Quick Start Instructions and MSA 2040 Cable Configuration Guide.
Rear panel LEDs
81
82
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 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 ± 5 percent fluctuation. The customer facilities must also provide
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).
NOTE:
For power requirements, see QuickSpecs: http://www.hp.com/support/msa2040/QuickSpecs.
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.
Safety requirements
83
• 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.
Weight and placement guidelines
Refer to "Physical requirements" (page 85) 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/level 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" (page 86) 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 15 cm (6 inches) 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 37 cm (15 inches) 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 USB Type B port connection is recommended for the initial
installation and configuration of a controller enclosure. After you configure one or both of the controller
84
Environmental requirements and specifications
modules with an Internet Protocol (IP) address, you then use a remote management host on an Ethernet
network to configure, manage, and monitor.
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 NEBS and 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 of the enclosures, together with sufficient
ventilation to allow a free flow of air to all enclosures.
Table 27 and Table 28 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 (12 disks) and “2U24” denotes the SFF enclosure (24 disks).
Table 28 provides weight data for MSA 2040 controller enclosures and select drive enclosures. For
information about other HP MSA drive enclosures that may be cabled to these systems (i.e., D2700), check
QuickSpecs: http://www.hp.com/support/msa2040/QuickSpecs.
Table 27 Rackmount enclosure dimensions
Specifications
Rackmount
2U Height (y-axis)
8.9 cm (3.5 inches)
Width (x-axis):
•
•
Chassis only
Chassis with bezel ear caps
44.7 cm (17.6 inches)
47.9 cm (18.9 inches)
Depth (z-axis):
SFF drive enclosure (2U24)
•
•
Back of chassis ear to controller latch
Front of chassis ear to back of cable bend
50.5 cm (19.9 inches)
57.9 cm (22.8 inches)
LFF drive enclosure (2U12)
•
•
Back of chassis ear to controller latch
Front of chassis ear to back of cable bend
Table 28
.
Rackmount
MSA 2040 SAN Array SFF enclosure
disks)1,2
Chassis with FRUs (no
Chassis with FRUs (including disk)1,3
MSA 2040 SAN Array LFF enclosure
•
•
disks)1,2
Chassis with FRUs (no
Chassis with FRUs (including disks)1,3
MSA 2040 or P2000 6 Gb 3.5" drive enclosure
•
•
67.1 cm (26.4 inches)
Rackmount enclosure weights
Specifications
•
•
60.2 cm (23.7 inches)
Chassis with FRUs (no disks)1,2
Chassis with FRUs (including disks)1,3
8.6 kg (19.0 lb) [chassis]
19.9 kg (44.0 lb)
25.4 kg (56.0 lb)
9.9 kg (22.0 lb) [chassis]
21.3 kg (47.0 lb)
30.8 kg (68.0 lb)
9.9 kg (22.0 lb) [chassis]
21.3 kg (47.0 lb)
30.8 kg (68.0 lb)
1
Weights shown are nominal, and subject to variances.
Weights may vary due to different power supplies, IOMs, and differing calibrations between scales.
3Weights may vary due to actual number and type of disk drives (SAS or SSD) installed.
2
Physical requirements
85
Environmental requirements
NOTE: For operating and non-operating environmental technical specifications, see QuickSpecs:
http://www.hp.com/support/msa2040/QuickSpecs.
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.
Power cord requirements
Each enclosure is equipped with two power supplies of the same type (both AC or both DC). For
enclosures equipped with AC power supply modules, use two power cords that are appropriate for use in
a typical outlet in the destination country. Whether using AC or DC power supplies, each power cable
connects one of the power supplies 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).
IMPORTANT: See QuickSpecs for information about power cables provided with your MSA 2040
Storage product.
86
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.
Preventing electrostatic discharge
87
88
Electrostatic discharge
D
SFP option for host ports
Locate the SFP transceivers
Locate the qualified SFP option for your Converged Network Controller module within your product ship
kit. You can also obtain the part numbers using QuickSpecs.
NOTE: See the “HP MSA 2040 SAN Storage array and iSCSI SFPs Read This First” document for
important information pertaining to iSCSI SFPs.
The SFP transceiver (SFP) should look similar to the generic SFP shown in the figure below. Follow the
guidelines provided in Electrostatic discharge, page 87 when installing an SFP.
Controller module face plate
PORT
1
PORT
2
PORT
CLI
3
PORT
SERV
ICE−2
4
6Gb/s
CLI
ACT
LINK
SERV
ICE−1
Target host port
CACH
E
DIRTY
LINK
PORT
2
PORT
Align SFP for installation
(plug removed/actuator open)
Installed SFP
(actuator closed)
2
Fibre-optic interface cable
Figure 40 Install a qualified SFP option
TIP: See the “Configuring host ports” topic within the SMU Reference Guide for information about
configuring Converged Network Controller ports with host interface protocols of the same type or a
combination of types.
Install an SFP transceiver
For each target Converged Network Controller port, perform the following procedure to install an SFP.
Refer to the figure above when performing the steps.
1. Orient the SFP as shown above, and align it for insertion into the target host port.
The SFP should be positioned such that the actuator pivot-hinge is on top.
2. If the SFP has a plug, remove it before installing the transceiver. Retain the plug.
3. Flip the actuator open as shown in the figure (near the left detail view).
The actuator on your SFP option may look slightly different than the one shown, and it may not open to
a sweep greater than 90° (as shown in the figure).
4. Slide the SFP into the target host port until it locks into place.
5. Flip the actuator down, as indicated by the down-arrow next to the open actuator in the figure.
Locate the SFP transceivers
89
The installed SFP should look similar to the position shown in the right detail view.
6. When ready to attach to the host, obtain and connect a qualified cable option to the duplex jack at the
end of the SFP connector.
NOTE:
To remove an SFP module, perform the above steps in reverse order.
Verify component operation
View the host port Link Status/Link Activity LED on the controller module face plate. A green LED indicates that
the port is connected and the link is up (see LED descriptions for information about controller module LEDs).
90
SFP option for host ports
Index
Numerics
2U12
large form factor (LFF) enclosure 85
2U24
small form factor (SFF) enclosure 85
A
accessing
CLI (command-line interface) 44
SMU (Storage Management Utility) 49
C
cables
10GbE iSCSI 33
1Gb iSCSI 33
Ethernet 36
FCC compliance statement 36, 85
Fibre Channel 33
HD mini-SAS 33
routing requirements 84
shielded 36, 85
USB for CLI 44
cabling
connecting controller and drive enclosures 19
direct attach configurations 33
switch attach configurations 35
to enable Remote Snap replication 36
cache
read ahead 17
self-refresh mode 80
write-through 17
clearance requirements
service 84
ventilation 84
command-line interface (CLI)
connecting USB cable to CLI port 45
using to set controller IP addresses 44
CompactFlash
card 17
transporting 58
components
MSA 2040
enclosure front panel
LFF enclosure 13
SFF enclosure 13
enclosure rear panel
AC power supply 14
DC power supply 14
supported drive enclosures
LFF drive enclosure 16
SFF drive enclosure 17
MSA 2040 SAN
enclosure rear panel
AC power supply 76
CLI port (USB - Type B) 15, 76
DC power supply 76
DC power switch 76
host ports 15, 76
mini-SAS expansion port 15
network port 15, 76
reserved port 15, 76
SAS expansion port 76
service port 1 15, 76
service port 2 15, 76
MSA 2040 SAS
enclosure rear panel
CLI port (USB - Type B) 16
HD mini-SAS ports 16
mini-SAS expansion port 16
network port 16
reserved port 16
service port 1 16
service port 2 16
configuring
direct attach configurations 33
switch attach configurations 35
connections
verify 27
console requirement 84
controller enclosures
connecting to data hosts 31
connecting to remote management hosts 36
D
data hosts
defined 31
optional software 31
system requirements 31
DHCP
server 44
disk drive
slot numbering
LFF enclosure 13
SFF enclosure 13
E
electromagnetic compatibility (EMC) 83
electrostatic discharge
grounding methods 87
precautions 87
enclosure
cabling 19
dimensions 85
IDs, correcting 53
input frequency requirement 86
input voltage requirement 86
Index
91
installation checklist 19
site requirements 85
troubleshooting 53
web-browser based configuring and
provisioning 49
weight 85
Ethernet cables
requirements 36
F
faults
isolating
expansion port connection fault 60
host-side connection 58
methodology 51
H
host interface ports
FC host interface protocol
loop topology 32
point-to-point protocol 32
iSCSI host interface protocol
1 Gb 32
10GbE 32
mutual CHAP 32
SAS host interface protocol 33
SFP transceivers 31
hosts
defined 31
stopping I/O 53
HP
customer self-repair (CSR) 70
product warranty 70
I
IDs, correcting for enclosure 53
installing enclosures
installation checklist 19
IP addresses
setting using CLI 44
setting using DHCP 44
L
LEDs
disk drives 75
enclosure front panel
Enclosure ID 73, 74
Fault ID 73, 74
Heartbeat 73, 74
Unit Identification (UID) 73, 74
enclosure rear panel
MSA 2040 SAN
10GbE iSCSI Host Link Status/Link Activity 77
1Gb iSCSI Host Link Status/Link Activity 78
Cache Status 77, 78
Expansion Port Status 77, 78
Fault/Service Required 77, 78
FC Host Link Status/Link Activity 77
92
Index
FRU OK 77, 78
Network Port Link Active 77, 78
Network Port Link Speed 77, 78
OK to Remove 77, 78
Unit Locator 77, 78
MSA 2040 SAS
6/12 Gb Host Link Activity 79
6/12 Gb Host Link Status 79
Cache Status 79
Expansion Port Status 79
Fault/Service Required 79
FRU OK 79
Network Port Link Active 79
Network Port Link Speed 79
OK to Remove 79
Unit Locator 79
power supply unit
Input Source Power Good 80
Voltage/Fan Fault/Service Required 80
supported drive enclosures (expansion)
LFF enclosure rear panel
Fault/Service Required 81
FRU OK 81
OK to Remove 81
power supply 81
SAS In Port Status 81
SAS Out Port Status 81
Unit Locator 81
local management host requirement 84
P
physical requirements 85
power cord requirements 86
power cycle
power off 28, 29
power on 28, 29
power supply
AC power requirements 83
DC power requirements 83
site wiring requirements 83
R
regulatory compliance
notices
shielded cables 36, 85
requirements
cabling 20
clearance 84
Ethernet cables 36
host system 31
physical 85
ventilation 84
RFI/EMI connector hoods 36, 85
S
safety precautions 83
sensors
locating 65
power supply 65
temperature 66
voltage 66
site planning
EMC 83
local management host requirement 84
physical requirements 85
safety precautions 83
SMU
accessing web-based management interface 49
defined 49
getting started 49
Remote Snap replication 36
storage system configuring and provisioning 49
storage system setup
configuring 49
provisioning 49
replicating 49
supercapacitor pack 18
T
troubleshooting 51
controller failure, single controller configuration
57
correcting enclosure IDs 53
enclosure does not initialize 53
expansion port connection fault 60
host-side connection fault 58, 59
Remote Snap replication faults 61
using event notification 52
using system LEDs 54
using the CLI 52
using the SMU 51
V
ventilation requirements 84
W
warnings
rack stability 69
voltage and temperature 65
HP MSA 2040 User Guide
93
94
Index
">