Hp Imp Msa Storage Sol Studentguide

Implementing MSA Storage SolutionsTSG20736SG0606HP Restricted

HP Training

Student guide

Implementing MSA Storage SolutionsTSG20736SG0606HP Restricted

© Copyright 2006 Hewlett-Packard Development Company, L.P.

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.

This is an HP copyrighted work that may not be reproduced without the written permission of HP. You may not use these materials to deliver training to any person outside of your organization without the written permission of HP.

Linux® is a U.S. registered trademark of Linus Torvalds.

Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Printed in the US

Implementing MSA Storage Solutions (Course 20736)Student guideJune 2006

HP Restricted — Contact HP Education for customer training materials.

Rev. 6.21 HP Restricted Contents – i

Contents

Course Overview

Introduction..................................................................................................... 1 Course objectives ............................................................................................ 2 Course prerequisites......................................................................................... 3 Course content overview................................................................................... 3 Lab exercises................................................................................................... 5 Additional Information...................................................................................... 6

Related documentation – Documents.......................................................... 6 Related documentation – Web sites ........................................................... 8

Module 1 — Benefits of a SAN Introduction..................................................................................................... 1 Objectives ...................................................................................................... 2 Industry storage trends ..................................................................................... 3 Definition of a SAN ......................................................................................... 4 SAN features and benefits ................................................................................ 5

Features ................................................................................................. 5 Benefits.................................................................................................. 7 SAN model ............................................................................................ 8

SAN topologies............................................................................................... 9 FC-AL .................................................................................................... 9 FC-SW................................................................................................. 10

Supported switches .........................................................................................11 Configuration rules for SAN switches........................................................11 Supported switch models — B Class (Brocade-based).................................12

Fabric maximums ...........................................................................13 Additional fabric rules.....................................................................14 SAN Core and SAN switch addressing mode ....................................15

Supported switch models ― M Class (McData-based) product line ..............16 SAN fabric rules — M Class product line ..........................................16 Fabric maximums ― M Class fabric product line ................................16 Additional fabric rules — M Class switches........................................17

Supported switch models – C-Series product line........................................17 SAN fabric rules – C-Series fabric product line ...................................17 Fabric and switch model maximums ― C-Series product line................18 Zoning and VSANs ........................................................................18

Third-party switch support ...................................................................... 19

Implementing MSA Storage Solutions

Contents – ii HP Restricted Rev. 6.21

Fabric topologies .................................................................................. 19 Cascaded fabric............................................................................ 19 Ring fabric.................................................................................... 20 Mesh fabric .................................................................................. 21 Core/SAN fabric switch configurations examples (Brocade)................ 22 Director/Edge switch configurations examples (McData) .................... 23

1 and 2Gb/s fabric topology recommendations ....................................... 24 Zoning ......................................................................................................... 25

Zone types ........................................................................................... 25 Zone enforcement ................................................................................. 26 Zoning implementation .......................................................................... 27 SAN fabric zoning rules......................................................................... 28

Connectivity rules .......................................................................... 28 MSA zoning considerations.................................................................... 29

Zoning methods ............................................................................ 30 Display zoning...............................................................................31 Configure zoning with CLI ...............................................................31

Storage consolidation .................................................................................... 32 DtS with the MSA .......................................................................................... 33 Tape Libraries Support ................................................................................... 35

SAN backup components....................................................................... 36 NSR and the MSA1000......................................................................... 37 Tape libraries for the MSA1000.............................................................. 39

Learning check .............................................................................................. 40

Contents

Rev. 6.21 HP Restricted Contents – iii

Module 2 — MSA1xxx Product Overview Introduction..................................................................................................... 1 Objectives ...................................................................................................... 2 MSA1xxx product positioning ........................................................................... 3

Entry-level ....................................................................................... 3 Mid-range ...................................................................................... 4 Enterprise-level ................................................................................ 4

MSA1xxx positioning .............................................................................. 4 Customer benefits summary .............................................................................. 5

Performance ........................................................................................... 5 Expandability ......................................................................................... 5 Availability............................................................................................. 5 Investment protection ............................................................................... 5 Management tools .................................................................................. 5

MSA1000 product overview ............................................................................. 6 MSA1500cs product overview........................................................................... 8 MSA1510i product overview.............................................................................. 9 Key features of the MSA array systems ............................................................. 10

Features common to the three systems...................................................... 10 Features of the MSA1000 .......................................................................11 Features of the MSA1500cs.....................................................................12

Active/active controllers ..................................................................13 MSA1500cs active/active limitations.................................................13 Installation best practices.................................................................14 General installation considerations ...................................................14

Features of the MSA1510i........................................................................15 Important initial release information for the MSA1510i ................................16

MSA1510i installation software CD ...................................................16 iSCSI initiator.................................................................................16 100BaseT devices are not supported.................................................17 Clustering ......................................................................................17 Storage migration...........................................................................17 Drive flashing.................................................................................17 MIB-II data reporting is not yet supported ..........................................17

Supported software and hardware....................................................................18 Learning check .............................................................................................. 22


Contents – iv HP Restricted Rev. 6.21

Module 3 — Hardware Components Introduction..................................................................................................... 1 Objectives ...................................................................................................... 2 MSA1000 components..................................................................................... 3

Enclosure status indicators on the MSA1000 .............................................. 4 Rear view............................................................................................... 5 Hot-pluggable components....................................................................... 7 MSA1000 controller................................................................................ 8

Controller display ............................................................................ 8 MSA controller indicators ................................................................. 9 Array Accelerator (battery-backed cache) ......................................... 10 Array Accelerator batteries ..............................................................11

Controller firmware ................................................................................12 Automatic firmware recovery............................................................12 Redundant-controller firmware cloning...............................................12 Controller firmware updates .............................................................13

MSA1000 interconnect devices................................................................14 Fibre Channel I/O module ..............................................................14 MSA SAN Switch 2/8 ....................................................................15 MSA Hub 2/3 ...............................................................................16

Integrated Environmental Monitoring Unit (EMU)/SCSI I/O module..............17 Power supply/blower assembly............................................................... 19 Fibre Channel cables............................................................................. 20

MSA1500cs components ................................................................................ 21 Power and status indicators panel ........................................................... 21 Hot-pluggable components..................................................................... 23 Controller............................................................................................. 23 Fibre Channel I/O module..................................................................... 24 SCSI I/O module .................................................................................. 25 MSA1500cs cooling fans ....................................................................... 28 Power supply ........................................................................................ 30

MSA1510i components................................................................................... 32 Controller, SCSI I/O module, fans, and power supplies ............................. 33 Ethernet iSCSI I/O module..................................................................... 33 Cables................................................................................................. 34 Drive enclosure configurations ................................................................ 34

MSA1000 sample configurations..................................................................... 35 Direct-connect configuration ................................................................... 35

Embedded MSA Fabric Switch 6 configurations................................. 38 Embedded MSA Hub 2/3 configurations ......................................... 40

MSA1500cs sample configurations ...................................................................41 MSA1510i sample configurations..................................................................... 42 Learning Check ............................................................................................. 44

Contents

Rev. 6.21 HP Restricted Contents – v

Module 4 — MSA1000 and MSA1500cs Management Utilities Introduction..................................................................................................... 1 Objectives ...................................................................................................... 2 Array Configuration Utility Overview.................................................................. 3

Features and Benefits............................................................................... 3 Basic procedure for using ACU................................................................. 4 Screen Layout ......................................................................................... 4

The typical Standard Mode screen..................................................... 5 The typical Configuration Wizard Mode screen................................... 6 The Express Configuration Mode screen ............................................. 6

Background information on array storage systems ....................................... 7 Arrays ............................................................................................ 7 Spare drives ................................................................................... 8 Logical drives.................................................................................. 8 RAID levels ..................................................................................... 9 Expansion .....................................................................................12 Extension.......................................................................................13 Array migration..............................................................................13 Stripe size migration .......................................................................14 Selective Storage Presentation (SSP) ..................................................14

Command Line Interface .........................................................................15 Active/active CLI commands............................................................16

Array Diagnostics Utility ..................................................................................17 Performance Monitoring and HP Systems Insight Manager...................................17 MSA SAN Management Tools..........................................................................18

Switch Management Utility......................................................................18 Brocade Web Tools............................................................................... 20

Web Tools views ........................................................................... 21 Web Tools capabilities................................................................... 22

Multipathing applications/drivers .................................................................... 23 Secure Path .......................................................................................... 23

Features ....................................................................................... 23 Installation for Windows 2000 Server.............................................. 24 Installation for NetWare ................................................................. 24 Secure Path Manager..................................................................... 25 Supported Secure Path Configurations.............................................. 26

Microsoft Multipath Input/Output ............................................................ 27 MPIO drivers................................................................................. 28 MPIO DSM................................................................................... 28

QLogic multipathing .............................................................................. 29 Learning check .............................................................................................. 30 Introduction..................................................................................................... 1


Contents – vi HP Restricted Rev. 6.21

Module 5 — MSA1510i Management Utilities Objectives ...................................................................................................... 2

Command Line Interface .......................................................................... 3 Background on TCP/IP, NAS, and ISCSI .................................................... 4

TCP/IP ........................................................................................... 4 NAS .............................................................................................. 5 iSCSI ............................................................................................. 6

Storage Management Utility ............................................................................. 8 SMU features ......................................................................................... 8 SMU requirements................................................................................... 8 SMU best practices ................................................................................. 9 Introduction to iSCSI network terms and concepts.......................................11

Network terms ...............................................................................11 Ethernet iSCSI management and data ports .......................................13 Port names.....................................................................................13 Portals...........................................................................................14

Accessing the SMU ................................................................................15 Choosing an SMU configuration method ...........................................................17

Initial System Configuration Wizard..........................................................17 Step 1: Welcome............................................................................17 Step 2: Storage Configuration..........................................................18 Step 3: iSCSI Configuration ............................................................ 19 Step 4: Redundant iSCSI Configuration ............................................ 20 Step 5: Logon Settings ................................................................... 20 Step 6: Management Settings ......................................................... 22

SMU Configure tab ............................................................................... 25 Performing SMU tasks .................................................................................... 27

Available tasks.............................................................................. 27 System diagrams ........................................................................................... 29

Hardware/device diagram .................................................................... 29 Storage diagram................................................................................... 30 Path/accessibility diagram......................................................................31

Configuring the system ................................................................................... 32 Configuring management and data ports................................................. 32 Configuring hard drives ......................................................................... 33 Configuring storage targets .................................................................... 33 Adding authorized initiators (servers)....................................................... 34 Other tasks .......................................................................................... 34

SMU security ................................................................................................ 35 Setting up ACLs .................................................................................... 35 CHAP authentication ............................................................................. 35 Setting the SSL certificate ....................................................................... 36

Contents

Rev. 6.21 HP Restricted Contents – vii

Managing the system using SMU .................................................................... 37 SMU diagnostics ........................................................................................... 40 SMU icons.....................................................................................................41 Performance Monitoring and HP Systems Insight Manager.................................. 45 Multipathing application/drivers ..................................................................... 46

Microsoft Multipath Input/Output ............................................................ 46 MPIO drivers................................................................................. 47 MPIO DSM................................................................................... 47

Learning check .............................................................................................. 48

Module 6 — StorageWorks MSA30 Hardware Components Introduction..................................................................................................... 1 Objectives ...................................................................................................... 2 MSA30 drive enclosure .................................................................................... 3

Front components.................................................................................... 3 Disk drives...................................................................................... 5

Rear components .................................................................................... 7 EMU.............................................................................................. 8 Power supplies ................................................................................ 9 Blowers ........................................................................................ 10 SCSI I/O module ...........................................................................11

Replacing system components ..........................................................................14 Learning check ...............................................................................................15

Module 7 — StorageWorks MSA20 Hardware Components Introduction..................................................................................................... 1 Objectives ...................................................................................................... 2 MSA20 drive enclosure .................................................................................... 3

Front components.................................................................................... 3 Back view....................................................................................... 4 Disk drives...................................................................................... 4 Drive status LEDs.............................................................................. 5

Rear components .................................................................................... 6 Power supply unit ............................................................................ 7 Controller and SCSI I/O module ....................................................... 8 Fan assembly .................................................................................. 9 Backplane boards ......................................................................... 10 Midplane board............................................................................ 10 UID circuit board ............................................................................11

Replacing system components..................................................................12 Learning check ...............................................................................................13


Contents – viii HP Restricted Rev. 6.21

Module 8 — MSA Service and Support Introduction..................................................................................................... 1 Objectives ...................................................................................................... 2 Troubleshooting techniques ............................................................................... 3

Power on sequence ................................................................................. 3 Visual indicators ..................................................................................... 4 LCD panels — error codes ....................................................................... 4

Removing and replacing component procedures.................................................. 5 Replacing an MSA controller .................................................................... 6 Replacing the MSA controller cache .......................................................... 7 Controller cache battery pack replacement ................................................ 8 MSA hot-plug power supply/blower ........................................................ 10

Replacing a variable speed blower.................................................. 10 Replacing a fan module ..................................................................11 Replacing a power supply ...............................................................12

MSA SCSI I/O module ...........................................................................13 MSA Fibre Channel I/O module ..............................................................14

Service advisories ...........................................................................................15 DOCUMENT NUMBER: OI021115_CW01.........................................15 DOCUMENT NUMBER: EU021120_CW01........................................16 DOCUMENT NUMBER: EC020515_CW01.......................................17 DOCUMENT NUMBER: OI021203_CW01 .......................................18 DOCUMENT NUMBER: EX011221_CW01 ....................................... 19

Learning check .............................................................................................. 21

Learning Check Answers

Appendix – LCD Panel Codes

Rev. 6.21 HP Restricted Overview – 1

Course Overview

Introduction This instructor-led training course introduces the student to the HP StorageWorks Modular Smart Array (MSA) 1000, the MSA1500cs, and the MSA1510i storage array systems. This course focuses on implementing and managing an MSA SAN solution. The student gains an understanding of the features, benefits, and components of each of the three systems and learns the main considerations for installing, configuring, and troubleshooting the systems. The student also learns to use the various tools and utilities available for configuring and managing the array systems.

The classroom instruction is augmented by a number of lab exercises that correlate with the lecture materials.


Overview – 2 HP Restricted Rev. 6.21

Course objectives After completing this two-day course, the student should be able to successfully:

Explain the benefits of a Storage Area Network (SAN)

Explain the product benefits and main features of the three products

Identify, locate, and discuss the functions of the hardware components, including:

• Controllers

• Drive enclosures and hard drives

• Fibre Channel I/O module

• Serial ATA/SCSI I/O module

• Environmental Monitoring Unit

• Power and cooling units

• Related interconnect devices

Identify the software applications supported on the MSA products.

Install, navigate, and utilize the Array Configuration Utility (ACU) and Storage Management Utility (SMU)

Discuss the sample configurations for the MSA products

Discuss and utilize the command line interface commands

Discuss basic operating procedures and associated considerations

Demonstrate the ability to diagnose and troubleshoot a variety of problems

Demonstrate the ability to remove and replace key components

Implement Secure Path for Windows Workgroup Edition

Course Overview


Course prerequisites Students should successfully complete the following courses prior to attending this course:

HP Storage Technologies (eLMS #1822)

HP StorageWorks Full-Line Technical Training (WBT) (eLMS #488)

HP Storage Software and Solutions Full-Line Technical Training (WBT) (eLMS #489)

It is preferred that students also have a working knowledge of one of the following operating systems: Windows 2000 or Windows 2003, Novell NetWare, or Linux.

Course content overview Course Overview

The content of the MSA product line instructor-led training course is introduced in this module.

Module 1 – Benefits of a SAN

This module provides a general overview of storage area networks (SANs). Discussion topics include features and benefits, industry trends, SAN topologies, supported switches, zoning, and storage consolidation.

Module 2 – Product Overview

This module introduces product positioning, key features and benefits, management tools, hardware components, and supported hardware and software.

Module 3 – MSA Hardware Components

This module discusses in detail the components of the three MSA arrays. Discussions cover the controller and its components, the drive enclosures and drives, and sample configurations available for the systems. The module also includes discussions of the various interconnect options available for the MSA arrays.

Module 4 – MSA1000-MSA1500cs Management Utilities

This module discusses the purpose and use of the tools and utilities available for use with the MSA1000 and MSA1500cs arrays. Discussion topics include Array Configuration Utility (ACU), Command Line Interface (CLI), HP Systems Insight Manager, MSA SAN management tools, and available multipathing solutions.

Module 5 – MSA1510i Management Utilities

This module discusses the purpose and use of the tools and utilities available for use with the MSA. Discussion topics include TCP/IP, NAS, iSCSI, Storage Management Utility (SMU), Command Line Interface (CLI), HP Systems Insight Manager, and available multipathing solutions.



Module 6 – MSA30 Hardware Components

The MSA30 drive enclosure components will be covered in greater detail. Discussions include the following components: hot-pluggable components, hard drives, power supplies, blowers, SCSI I/O modules, and the Environmental Monitoring Unit (EMU).

Module 7 – MSA20 Hardware Components

The MSA20 drive enclosure components will be covered in greater detail. Discussions include the following components: hot-pluggable components, Serial ATA (SATA) hard drives, power supplies, blowers, and SCSI I/O modules.

Module 8 – MSA Service and Support

This module discusses basic troubleshooting techniques, replacement procedures, and known service issues for the MSA1000, MSA1500cs, and MSA1510i.


Answers to module learning checks are listed here.

Appendix – LCD Panel Codes

The appendix covers MSA controller LCD display messages, including error code, type, description, and action.

Course Overview


Lab exercises The following lab exercises are included in the course lab guide.

Lab 1 – MSA1000, MSA1500cs, and MSA1510i Hardware Familiarization

Lab 2 – MSA1000/1500cs Installation – Windows 2000

Lab 3 – Agent Exploration

Lab 4 – MSA1000 & MSA1500cs Configuration with ACU

Lab 5 – MSA1000 Controller Firmware Update – Windows 2000

Lab 6a – Command Line Interface (CLI) for the MSA1000 Controller

Lab 6b – Command Line Interface (CLI) for the MSA1510i Controller

Lab 7 – Installing Secure Path for Windows Workgroup Edition

Lab 8 – Migrating to Active/Active Controllers – Windows

Lab 9 – MSA20 SCSI Controller Module Service Procedure

Lab 10 – MSA20 Backplane Removal

Lab 11 – MSA1000/1500cs Configuration with ACU – Red Hat Linux Advanced Server 4

Lab 12 – MSA1500cs QLogic Failover

Lab 13 – Migrating to Active/Active Controllers – Linux

Lab 14 – External Boot from the SAN

Lab 15 – MSA1510i Configuration with SMU

Lab 16 – CLI Troubleshooting

Lab 17 – MSA1000 Basic Troubleshooting

Lab 18 – MSA1500cs Basic Troubleshooting



Additional Information Related documentation – Documents

HP StorageWorks Modular Smart Array 1000 User Guide

HP StorageWorks Smart Array Cluster Storage User Guide

HP StorageWorks MSA Fabric Switch 8 User Guide

HP StorageWorks Modular Smart Array 1000 Installation Overview

HP StorageWorks Modular Smart Array 1000 QuickSpecs

HP StorageWorks Modular Smart Array 1000 Rack Installation Guide

HP StorageWorks Modular Smart Array 1000 Maintenance and Service Guide

HP StorageWorks Modular Smart Array 1000 Installation Card

HP StorageWorks Modular Smart Array 1000 Release Notes

HP StorageWorks modular SAN array 1000 user guide

HP StorageWorks Modular Smart Array 1500 cs User Guide

HP StorageWorks Modular Smart Array 1500 cs Installation Overview

HP StorageWorks Modular Smart Array 1500 cs QuickSpecs

HP StorageWorks Modular Smart Array 1500 cs Rack Installation Guide

HP StorageWorks Modular Smart Array 1500 cs Maintenance and Service Guide

HP StorageWorks Modular Smart Array 1500 cs Installation Card

HP StorageWorks Modular Smart Array 1500 cs Release Notes

HP StorageWorks 1500cs Modular Smart Array with active/active controllers installation guide

HP StorageWorks Modular Smart Array 1500cs application note: Migrating to active/active controllers in Linux environments

HP StorageWorks Modular Smart Array 1500cs application note: Migrating to active/active controllers in Windows environments

HP StorageWorks Modular Smart Array 1500cs application note: Migrating to active/active controllers in HP-UX environments

Course Overview


QuickSpecs, HP StorageWorks 1510i Modular Smart Array

HP StorageWorks Modular Smart Array 1510i installation guide

HP StorageWorks Modular Smart Array 1510i Command Line Interface user guide

HP StorageWorks Modular Smart Array 1510i maintenance and service guide

IMPORTANT HP StorageWorks 1510i Modular Smart Array initial product release

IMPORTANT HP StorageWorks Modular Smart Array 1510i installation software CD

IMPORTANT HP StorageWorks Modular Smart Array products Recommended firmware update

HP StorageWorks Modular Smart Array 1510i installation overview

HP StorageWorks Modular Smart Array 1510i 2-Port Ethernet iSCSI module replacement instructions

HP Storage Management Utility user guide

HP StorageWorks Modular Smart Array controller, cache, and battery replacement instructions

HP StorageWorks Secure Path 4.0c for Windows Workgroup Edition Installation Guide

HP StorageWorks Secure Path 4.0c for Windows Workgroup Edition Release Notes

HP StorageWorks Secure Path 3.0c for Novell NetWare Workgroup Edition Installation Guide

HP StorageWorks Secure Path 3.0c for Novell NetWare Workgroup Edition Release Notes



Related documentation – Web sites http://h18006.www1.hp.com/storage/index.html

http://h18000.www1.hp.com/enterprise/highavailability.html

http://learning1.americas.cpqcorp.net/mcsl-html/home.asp

http://cybrary.inet.cpqcorp.net/HW/STOR/SOLUTIONS/MSA1000/ index.html

http://cybrary.inet.cpqcorp.net/HW/STOR/SOLUTIONS/MSA1000/ index.html?/HW/STOR/SOLUTIONS/MSA1000/advisories.html

http://cybrary.inet.cpqcorp.net/HW/STOR/SOLUTIONS/MSA1500_CS/ index.html

http://cybrary.inet.cpqcorp.net/HW/STOR/SOLUTIONS/MSA1500_CS/ index.html?/HW/STOR/SOLUTIONS/MSA1500_CS/advisories.html

http://h18000.www1.hp.com/products/sanworks/secure-path/index.html

http://h18000.www1.hp.com/products/quickspecs

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

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

http://h18006.www1.hp.com/products/storageworks/msa1510i

These documents are also available on the OARS partner offline link.

Rev. 6.21 HP Restricted 1 – 1

Benefits of a SAN Module 1

Introduction This module provides a general overview of storage area networks (SANs). Topics include:

Features and benefits of a SAN

Industry storage trends

SAN topologies

Supported switches

Zoning

Storage consolidation


1 – 2 HP Restricted Rev. 6.21

Objectives After completing this module, you should be able to:

Discuss industry storage trends.

Define storage area networks (SANs).

Describe the features and benefits of a SAN.

List the entry-level SAN supported switches.

Describe the benefits of zoning.

Explain why storage consolidation is needed in today’s IT environments.

Describe the direct-attach storage (DAS) to SAN (DtS) features and benefits of the HP StorageWorks Modular Smart Array (MSA) SAN solutions.

Discuss support for tape libraries.

Benefits of a SAN


Industry storage trends

Cost of ManagingStorage Rising as Cost per MB Falling

E-Commerce, Email, and Data Mining— Driving Massive Demand for Storage

Centralized Management — Companies Becoming More Information Centric as Knowledge is Recognized as a Corporate Asset

Pressures for Continuous Operation (7 x 24)

Growing IT Labor Shortage Requires Efficient IT Operations



Centralized Management — Companies Becoming More Information Centric as Knowledge Is Recognized as a Corporate Asset





Centralized Management — Companies Becoming More Information Centric as Knowledge is Recognized as a Corporate Asset





Centralized Management — Companies Becoming More Information Centric as Knowledge Is Recognized as a Corporate Asset



Industry storage challenges drive storage trends

Customers are facing an exponential demand for increasing storage capacity as their businesses grow and they continue to deploy more powerful, efficient solutions.

To maintain a competitive advantage, customers must have the ability to scale their solutions dynamically to meet increased resource demands. They also require highly available and easily managed solutions.

These demands have created the following challenges for storage solutions:

Explosive storage growth with data capacities doubling every 18 months

The need to have data online all the time with no interruption

Shrinking backup windows

Limited IT resources to manage their enterprise

Rapidly shifting technologies



Definition of a SAN

A SAN is a dedicated, centrally managed, secure information infrastructure that enables direct physical access to common storage devices or a storage pool.

The Storage Network Industry Association (SNIA) defines a SAN as,

“A network whose primary purpose is the transfer of data between computer systems and storage elements and among storage elements. A SAN consists of a communication infrastructure, which provides physical connections, and a management layer, which organizes the connections, storage elements, and computer systems so that data transfer is secure and robust.”

Within this definition there is no mention of Fibre Channel. SNIA recommends using the term Fibre Channel SAN when the network is based on Fibre Channel technology. Although a SAN typically references Fibre Channel, it can be based on other technologies such as ESCON (Enterprise System Connection).

Benefits of a SAN


SAN features and benefits

SAN example

Features SAN features include:

A secure implementation of storage I/O methods over network transports

A high-speed, scalable, robust network of servers and storage devices

A storage service that:

• Connects to enterprise-wide servers

• Centralizes data

• Moves data automatically for availability and replication

• Provides accelerated data access

• Supports advanced storage management

• Provides for highly available configurations

A natural platform for server clustering applications

Shared Disks/ Tape Devices

File Services Web Services GroupWiseOracle

Clients

Public LAN

Clustered Servers

Shared Disks/Tape Devices

File ServicesWeb Services GroupWiseOracle

Clients

Public LAN

ClusteredServers



SAN implementations from most storage vendors have been fairly simple—such as point-to-point configurations with a few switches between the servers and the storage.

Recent developments include:

Fibre Channel extenders

Fibre Channel-to-ATM gateways

Fibre Channel-to-IP gateways

SAN technology also includes the Internet small computer system interface (iSCSI) protocol. The iSCSI Protocol is an IP-based storage networking standard for linking data storage facilities. By carrying SCSI commands over IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. The iSCSI protocol is among the key technologies expected to help bring about rapid development of the SAN market, by increasing the capabilities and performance of storage data transmission. Because of the size of IP networks, iSCSI can be used to transmit data over LANs, wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval.

iSCSI is one of two main approaches to storage data transmission over IP networks. The other method, Fibre Channel over IP (FC-IP), translates Fibre Channel control codes and data into IP packets for transmission between geographically distant Fibre Channel SANs. FC-IP (also known as Fibre Channel tunneling or storage tunneling) can only be used in conjunction with Fibre Channel technology; in comparison, iSCSI can run over existing Ethernet networks.

Using IP-based storage allows customers to realize SAN functionality and benefits by utilizing existing Ethernet capabilities to store and retrieve data. An iSCSI to Fibre Channel bridge (for example: the HP StorageWorks SR2122 Storage Router), enables access to block storage on a Fibre Channel SAN across an Ethernet network.

Benefits of a SAN


Benefits SANs reduce the cost of managing storage by consolidating storage and sharing the resources across multiple hosts.

Most Fibre Channel-based storage supports changes made to storage configurations through a host operating system. This support allows storage resources to be added or deleted without interrupting production environments, thereby reducing downtime for storage changes.

Scaling storage can be as simple as plugging a storage array into a switch or adding drives into existing storage systems. This capability allows storage to be added on an as-needed basis.

The benefits of a SAN include:

Centralized storage — Consolidating storage (primary and secondary) in a SAN and sharing the resource across multiple servers reduces the cost of storage management.

Elimination of server downtime while adding storage — Using Fibre Channel-based storage, storage resources can be added or deleted without interrupting the production environment.

Improved availability — Implementing advanced SAN designs enables fault-tolerant and disaster-tolerant configurations that are ideal platforms for clustered, mission-critical systems.

Modular scalability — With modular scalability providing support for an unpredictable environment, the infrastructure can be changed as business needs evolve. Bandwidth, availability, redundancy, and capacity can be dynamically scaled on demand, providing maximum flexibility to accommodate business growth.

Serverless backup — Having serverless backup enables direct backup from disk to tape without going through the host, which offloads data from the network. The host initiates the process but another intelligent device, such as the Network Storage Router (NSR), transfers the data.

Online storage migration — Storage can be dynamically allocated and re-allocated among hosts without interruption, resulting in improved storage utilization.



SAN model Value• Zoning and LUN masking• Backup over a SAN• Resource pooling• System resource management• File sharing over a SAN

Connectivity• Fibre Channel switches• Fibre Channel-to-SCSI routers• Fibre Channel-to-ATM gateways• IP over Fibre Channel

Storageplumbing

tier

Value-AddedSAN

Services

Softwaretier

Subnet

Deviceoriented

commandsand status

Value-added SAN

services

Value• Zoning and LUN masking• Backup over a SAN• Resource pooling• System resource management• File sharing over a SAN

Connectivity• Fibre Channel switches• Fibre Channel-to-SCSI routers• Fibre Channel-to-ATM gateways• IP over Fibre Channel

Storageplumbing

tier

Value-AddedSAN

Services

Softwaretier

Subnet

Deviceoriented

commandsand status

Value-added SAN

services

Gartner Group two-tier model

This two-tier model represents how the Gartner Group views SANs:

The first tier, storage plumbing, provides connectivity between nodes in a network fashion and transports device-oriented commands and status. At least one storage node must be connected to this network.

The second tier uses software to provide value-added services that operate over the first tier.

This model definition clearly differentiates network attached storage (NAS) from SANs. With NAS, a client makes a file system call over the network, as opposed to using device-oriented commands with SANs.

To qualify as a SAN, a configuration must provide separate value-added SAN services through software that operates across connected nodes, such as zoning and resource management.

Benefits of a SAN


SAN topologies SANs can use either Fibre Channel Arbitrated Loop (FC-AL) or Fibre Channel Switched Fabric (FC-SW) topologies.

FC-AL

The FC-AL network can be set up in two possible configurations—daisy-chained (loop) or through a hub. In the daisy-chain configuration, the transmit port of one device is connected to the receive port of the next device in the chain. Due to the shared nature of loop topologies, only one device may send data at any time. Access to the loop is determined by winning an arbitration to become the loop master.

Configuring FC-AL in a loop topology presents several limits to the performance of the network because performance is affected by the number of devices attached to the loop. The ability to make changes to the network is limited because the addition or removal of new devices or segments within a loop will bring down the entire loop.

The most common topology used in the deployment of FC-AL uses a hub that forms a physical star interconnection. If a loop or non-responding device appears, the FC-AL hub will bypass the failure, thus maintaining the operational integrity of the network.

The preceding graphic shows the required components of a basic SAN based on an arbitrated loop topology.

These components include:

Host

Host bus adapter (HBA)

Storage subsystem

7- or 12-port Fibre Channel hub or Fibre Channel arbitrated loop switch

Cables and transceivers or GBICs



FC-SW

FC-SW is the abbreviation for the standard governing the form of Fibre Channel network in which nodes are connected to a fabric topology implemented by one or more switches. Each N_Port node of the FC-SW connects to an F_Port on a switch. Pairs of nodes connected to a FC-SW network can communicate concurrently.

A fabric is a Fibre Channel switch or two or more Fibre Channel switches interconnected in such a way that data can be physically transmitted between any two N_Ports on any of the switches. The switches comprising a Fibre Channel fabric are capable of routing frames using only the D_ID (destination identifier) in a FC-2 (protocol level that encompasses signaling protocol rules and the organization of data) frame header.

In a switched fabric topology, many node-to-node connections can occur simultaneously, greatly increasing bandwidth. Cascading fabric switches provides scalability in the SAN solution.

The preceding graphic displays some of the components of a basic SAN based on a switched fabric topology.

The SAN components include:

HBA

Host servers

Storage subsystem

Fibre Channel SAN switch

Cables and transceivers or GBICs

Benefits of a SAN


Supported switches Currently, HP supports numerous switches in one fabric and a maximum of seven hops (depending on the switch) from any initiator to any target.

SAN core 2/64

SAN director 2/64

SAN switch 2/16 EL

SAN switch 2/16

SAN edge 2/32

SAN switch 2/32

FC switch 16B

FC entry switch 8BSAN switch 2/8 EL

business enterprisebusiness entry business midrange

SAN director 2/140

SAN edge 2/24

SAN core 2/64SAN core 2/64

SAN director 2/64

SAN switch 2/16 ELSAN switch 2/16 EL

SAN switch 2/16SAN switch 2/16

SAN edge 2/32

SAN switch 2/32SAN switch 2/32

FC switch 16BFC switch 16B

FC entry switch 8BFC entry switch 8BSAN switch 2/8 ELSAN switch 2/8 EL

business enterprisebusiness entry business midrange

SAN director 2/140

SAN edge 2/24

Configuration rules for SAN switches The HP StorageWorks Modular Smart Array (MSA) 1000 and MSA1500 cs storage systems are supported in the B (Brocade-based), M (McData-based), and C (Cisco-based) class fabric product lines of Fibre Channel switches. The MSA1510i storage system is supported by the 1Gb Ethernet switches. The SAN connectivity rules for both storage systems apply uniformly to all switch products, unless specified otherwise.

In general, all MSA1000s have the same switch configuration specification. However, there could be some device-specific exceptions.



Supported switch models — B Class (Brocade-based) HP supports a range of 1 and 2Gb/s SAN B class product line Fibre Channel switch models. Three broad classes of switches supported by HP include:

Directors — High port count, high-bandwidth switch designed with fully redundant hot-pluggable field replaceable units (FRUs) that provide an availability of 99.999% (approximately 5 minutes of down time per year).

Fabric Switches — Low to medium port count, high-bandwidth switch designed with redundant power supplies and cooling fans that provide an availability of 99.9% (approximately 8.8 hours of down time per year).

Fibre Channel Arbitrated Loop Switches (FC-AL) — Low port count, low-bandwidth products. HP offers related products that act as loop-switching hubs and fabric-attach switches, which allow low-cost or low-bandwidth workgroup (edge) devices to communicate with fabric devices.

HP StorageWorks switch name Number of ports HP StorageWorks SAN Switch 2/32 Power Pak 32 HP StorageWorks Core Switch 2/64 64 (2 switches per chassis, for a total

of 128 ports per chassis)

HP switch name Compaq StorageWorks switch name Number of ports

Brocade 2400 SAN Switch 8 8 N/A SAN Switch 8-EL 8 Brocade 2800 SAN Switch 16 16 N/A SAN Switch 16-EL 16 Surestore FC Switch 6164 (64 ISL Ports)

SAN Switch Integrated/32 (64 ISL Ports)

32 (counts as 6 switches and 2 hops when applying configuration rules)

Surestore FC Switch 6164 (32 ISL Ports

SAN Switch Integrated/64 (32 ISL Ports)

64 (counts as 6 switches and 2 hops when applying configuration rules)

Surestore FC 1Gb/2GB Entry Switch 8B

N/A 8

N/A SAN Switch 2/8-EL 8 N/A SAN Switch 2/16-EL 16 Surestore FC 1Gb/2Gb N/A 8 Surestore FC 1Gb/2GB Switch 16B

SAN Switch 2/16 16

All switch models shown in the table are supported in the HP StorageWorks SAN provided that the same firmware versions and switch settings for each switch model family are used for the corresponding switch models listed.

Note Refer to the SAN Product Support Tables in the HP StorageWorks SAN Design Guide for the current required switch firmware versions for each switch model.

Benefits of a SAN


For SAN fabrics consisting exclusively of Compaq switch models or a mix of pre-merger HP and pre-merger Compaq switch models (Compaq StorageWorks switch name in the above table), use the Compaq default switch settings. Configuration files with these settings are available from HP services.

For SAN fabrics consisting exclusively of pre-merger HP switch models (HP switch name in the above table), use pre-merger HP switch settings. Configuration files with these settings are available from HP services.

Fabric maximums Fabric maximums when using exclusively HP VA storage systems, or a mixture of HP XP or VA and StorageWorks Enterprise Virtual Array, EMA/ESA12000, EMA16000, MA/RA8000, MA6000, MSA1000, RA4000, or RA4100 storage systems:

Up to 16 switches and up to 640 total ports in a single SAN fabric. Each fabric may contain any combination of supported 1Gb/s and 2Gb/s switch models listed, provided the individual switch model fabric limits listed below are not exceeded.

The HP StorageWorks Core Switch 2/64 (maximum of two chassis total per fabric) — Each chassis contains two logical switches and consequently adds two to the fabric switch count. Maximum fabric configuration is two chassis with 12 other 8-, 16-, or 32-port switches (4x12). The Core PID addressing mode is required on all other switches in the same fabric with the hp StorageWorks core switch 2/64. Refer to “SAN Core and SAN Switch Addressing Mode” later in this module.

StorageWorks SAN Switch Integrated 32 or 64, HP Surestore FC Switch 6164 (maximum of two chassis total per fabric) — Each chassis adds six switches to the fabric switch count. Maximum fabric configuration is two chassis with four other SAN switch model switches.

Up to three switch hops (four switches) maximum between any two devices in a SAN fabric. Each SAN Switch Integrated 32 or 64, or HP Surestore FC Switch 6164 model switch used in a fabric adds up to two hops to the hop count between devices depending on the specific device-to-switch connections and device-to-device access.



Additional fabric rules StorageWorks SAN Switch 2/8-EL — By default, this switch is supported in SAN

fabrics with up to four switches total only. A license upgrade is available to allow these switches to be upgraded for support in larger fabrics.

HP Surestore FC 1Gb/2Gb Entry Switch 8B — Supported with a single E-port connection.

Compaq Fibre Channel Switch 8 or Fibre Channel Switch 16 models — Up to four switches total per fabric using these model switches only, or when intermixed with 1Gb/s SAN switches.

Note Intermixing Compaq Fibre Channel 8 and 16 switches and 1Gb/s StorageWorks SAN Switch models requires the compatibility mode (VC Encoded Address Mode) be set in the SAN switches (refer to the SAN switch documentation). Intermixing 1Gb/s Compaq Fibre Channel Switch 8 or Fibre Channel Switch 16 switch models and 2Gb/s switch models is not supported.

The Compaq FC-AL Switch 8 is supported for cascaded attachment to the SAN

through a single FL-port on a Compaq SAN Switch 8, SAN Switch 16, SAN Switch 8-EL, or SAN Switch 16-EL.

Note Cascaded attachment of the FC-AL Switch 8 connected to 2Gb/s switch models is not supported.

Within a single fabric where switches are interconnected, each switch must have

a unique domain number (Domain ID) and a unique World Wide Name (WWN). All switch configuration parameters in each switch must be the same.

Note Do not configure any switches with a domain ID of 8. HP systems reserve domain 8 for Private Loop devices.

Optional switch features may be used on any switch in the fabric if the feature is

supported on that switch. For example, in a fabric consisting of four SAN switch 16 and four SAN Switch 2/16 switches, the Fabric Watch feature may be used on the SAN Switch 2/16 switches. If two 2Gb/s switches are connected together, trunking may be implemented if the feature is supported by both switch models.

Any mix of servers and storage systems is allowed in a SAN provided the specific platform, operating system, and storage system fabric limits and rules are followed. Refer to the HP StorageWorks SAN Design Guide and the documentation listed in the section “Related Documents” in the preface of the SAN Design Guide for specific instruction on the implementation of switches in a SAN environment.

Benefits of a SAN


HP requires that all switches in a single fabric or multi-fabric SAN use the same switch firmware revision for each switch model family. Two successive fabric firmware versions can be temporarily used in one fabric or in multiple fabrics in a SAN during switch firmware rolling upgrades.

SAN Core and SAN switch addressing mode When using products from the HP StorageWorks Core Switch or SAN switch family of products, or pre-merger HP products from Brocade, for the switch firmware versions listed in this document, two different addressing modes are available. As SAN configurations grow to include more switches, we recommend that the “Core Switch” addressing mode should be used. This is obtained by setting the Core Switch PID configuration parameter bit.

All previous switches supplied by HP and Compaq were shipped with the Core Switch PID configuration bit cleared. When the switches are operated in this mode, certain restrictions apply regarding the maximum number of switches in a fabric and the maximum number of ports on a switch. If a StorageWorks Core Switch 2/64 or StorageWorks SAN Switch 2/32 is used anywhere in a fabric, then all the switches in the fabric must have the Core Switch PID configuration bit set. Because HP believes that the use of large port count switches will only become more common as time goes on, all switches are shipped with the bit set. SAN managers with existing fabrics must decide whether to change the Core Switch PID bit now or later. The trade-offs are:

All switches in a fabric must have the same Core Switch PID bit setting, whether it is set or cleared, otherwise the fabric will segment. It must be set on all switches if a StorageWorks Core Switch 2/64 or StorageWorks SAN Switch 2/32 is part of the fabric.

If you have two fabrics, you can change the Core Switch PID on one fabric at a time, so the SAN storage system can continue to operate during the changeover.

HP-UX and IBM systems use the address bits to identify logical units, when the addressing bits are changed the logical unit definitions must also be changed. This requires a reboot of the servers and cannot be done without taking down the entire SAN storage system in a planned maintenance scenario.

If you do not set the Core PID on your existing switches now, you will need to clear this bit on any new switches that you add because they ship with the Core PID bit set.

HP recommends that this change be done now, to avoid potential problems in the future. Additional information on the Core Switch PID is available on the HP SAN Storage website.



Supported switch models ― M Class (McData-based) product line

HP supports a range of 1Gb/s and 2Gb/s high availability fabric product line Fibre Channel switch models.

HP StorageWorks switch name Number of ports HP StorageWorks SAN Edge Switch 2/16 16 HP StorageWorks SAN Edge Switch 2/24 24 HP StorageWorks SAN Edge Switch 2/32 32 HP StorageWorks Core Switch 2/140 140

HP switch name Compaq StorageWorks switch name Number of ports

N/A McData ES-3016 16 N/A McData ES-3032 32 McData ED-5000 32 Surestore FC64 StorageWorks SAN Director 64 64 Surestore Director 2/64 64

SAN fabric rules — M Class product line All switch models shown in table above are supported in the HP StorageWorks SAN provided that the same firmware versions and switch settings are used. The default switch settings for this family of switches (from StorageWorks and Surestore) are the same.

Fabric maximums ― M Class fabric product line Common HP StorageWorks SAN fabric rules for SANs consisting of exclusively HP VA storage systems, or a mix of HP XP or VA and StorageWorks Enterprise Virtual Array, EMA/ESA12000, EMA16000, MA/RA8000, MA6000, MSA1000, RA4000, or RA4100 storage systems. These rules can be considered a subset of the HP StorageWorks SAN fabric rules:

Up to 16 switches with up to 1376 total ports (maximum 1024 user ports) are supported in a single SAN fabric. Each fabric may contain any combination of supported 1 and 2Gb/s switch models listed, provided the individual switch model fabric limits listed below are not exceeded.

Note With eight HP StorageWorks Director 2/140 fully populated Directors, it is physically possible to exceed the 1024 user port maximum. The restriction is in the zoning configuration, as only 1024 unique zone members (user port) can be configured. However, the remaining ports can be used as Inter Switch Link (ISL) connections in the fabric.

Benefits of a SAN


HP StorageWorks Director 2/64 and HP StorageWorks Director 2/140—maximum of eight Directors total per fabric.

McData ES-3016 and ES-3032 switches are not supported on HP VA storage.

Up to three switch hops (four switches) maximum between any two devices in a SAN fabric.

Additional fabric rules — M Class switches Within a single fabric where switches are interconnected, each switch must have

a unique domain number (Domain ID) and a unique World Wide Name (WWN). All switch configuration parameters in each switch must be the same.

Note Do not configure any switches with a domain ID of 8. HP systems reserve domain 8 for Private Loop devices.

Any mix of servers and storage systems is allowed in a SAN provided the

specific platform, operating system, and storage system fabric limits and rules are followed. Refer to the appropriate sections in the SAN Design Guide and the documentation listed in the section “Related Documents” in the Preface of the SAN Design Guide.

HP requires that all switches in a single fabric or multi-fabric SAN use the same switch firmware revision. Two successive fabric firmware versions can be temporarily used in one fabric or multiple fabrics in a SAN during switch firmware rolling upgrades.

Supported switch models – C-Series product line HP currently supports five models of the C-Series product line 2 Gbps Fibre Channel Switches, the Cisco MDS 9506, 9509, 9216, 9120, and 9140.

SAN fabric rules – C-Series fabric product line The MDS 9506 is supported with up to 128 ports, over 4 modular chassis (4-32

port modules). The 32-port module for the MDS 9000 product line utilizes 3.2:1 oversubscription for optimized connectivity of low to mid-range host devices as well as tape libraries. HP recommends the use of the 16 port module for performance intense host applications as well as ISLs. This will decrease the actual port count of the switch.

The MDS 9509 is supported with up to 224 ports, over 7 slots, each filled in with a 32-port module. The 32-port module for the MDS 9000 product line utilizes 3.2:1 oversubscription for optimized connectivity of low to mid-range host devices and low-end tape libraries. HP recommends the use of the 16 port module for performance intense host applications, disk storage systems, and high-end tape libraries. This will decrease the actual port count of the switch.



The MDS 9216 has a basic configuration with 16 ports. It has an expansion slot that supports either a 16 or a 32 port Fibre Channel card.

The MDS 9120 is a fixed 20 port configuration. It has 4 full rate ports and 16 oversubscribed ports.

The MDS 9140 is a fixed 40 port configuration. It has 8 full rate ports and 32 oversubscribed ports.

The MDS 9506, MDS 9509, and MDS 9216 models also support the IP Storage services 8-Port 1xGE module that provides integrated FCIP and iSCSI functionality. HP recommends the use of this blade for integrated deployment and FCIP implementation for business continuity applications.

Fabric and switch model maximums ― C-Series product line The fabric maximums listed are for C-Series switch model SAN fabrics utilizing HP XP128/1024, XP48/512, VA7110/7410, Enterprise Virtual Array (EVA), EMA/ESA12000, EMA16000, MA/RA8000, MA6000, and MSA1000 storage systems. In general, these fabric rules also apply to Continuous Access XP, EVA, and DRM for EMA/ESA12000, EMA16000, and MA/RA8000 storage systems.

Up to 11 MDS switches with up to 512 ports total in a SAN fabric

Up to 2 MDS 9506 or MDS 9509 Directors with up to 9 MDS 9216, 9120, or 9140 Fabric switches

Up to 4 MDS 9506 or 9509 Directors in an all Director fabric

Up to 7 switch hops (8 switches) maximum between any two devices in a SAN fabric

Zoning and VSANs C-Series switches provide a capability to build secure virtual fabrics using the VSAN feature called VSAN. Each VSAN is a separate virtual fabric that can be dedicated to a different type of storage system and zoning can be implemented on a per-VSAN basis for additional security.

In HP C-Series SANs, Virtual Storage Area Networks (VSANs) are defined as separate instances of all fabric services, including address space. HP supports 15 VSANs per physical fabric.

The maximum number of zones across all VSANs is 2048.

The maximum number of zone members across all VSANs is 20,000.

Benefits of a SAN


Third-party switch support Third-party switches and connectivity reliability have been verified through testing. However, support is subject to:

No support for third-party switch functionality. If a defect must be fixed within the switch product, the customer needs to work directly with the third-party switch support organization.

HP will make a best effort attempt to help the customer resolve issues as they pertain to the HP supported products within the environment.

HP can support switches and additional functionality resold through other vendors providing the customer purchases third-party support through the appropriate HP support group.

Example of third-party switches:

McData ED5000 = EMC Connectrix ED-1032

InRange FC 9000

Fabric topologies Cascaded fabric

A cascaded fabric is a line of switches with one connection between each switch and the switch next to it. The switches on the ends are not connected. Cascaded fabrics are well suited for applications where data access is local, but not for applications that require any-to-any connectivity. Device locality implies that groups of servers and the storage they access are connected through the same fabric element, and that ISLs are used primarily for fabric management traffic (Class F traffic) or low-bandwidth SAN applications



Ring fabric

A ring topology is like a cascaded fabric, but with the ends connected. The ring has superior reliability to the cascade because traffic can route around an ISL failure or a switch failure.

Ring fabrics are generally more expensive than cascaded fabrics, but are also easy to deploy, provide a simple solution to add additional fabric devices, and can solve hop-count problems inherent to cascaded fabrics. Ring fabrics also have increased reliability because traffic can rout around a single ISL, director, or switch failure (subject to hop count limitations).

Like cascaded fabrics, ring fabrics are well suited for applications where data access is local, but not for applications that require any-to-any connectivity. In addition, ring fabrics are useful when connecting SANs over WANs, which typically use a ring topology.

Benefits of a SAN


Mesh fabric

In a meshed fabric design, all of the switches are interconnected so there are at least two paths or routes from any one switch to any other switch in the fabric. This type of connectivity provides fabric resiliency. If a single ISL or ISL port interface fails, the fabric can automatically re-route data through an alternate path. The new route can even pass through additional switches in the fabric.

Meshed fabrics are well suited to applications where data access is a mix of local and distributed. The full connectivity (or high connectivity, in the case of modified meshes) supports many-to-many access, while at the same time allowing localized access to individual switches, servers and storage.

Note In a modified mesh design, as switches are added, they are only connected to adjacent switches, not all other switches in the fabric. This still provides the benefits of full many-to-many connectivity without a decrease in connection efficiency.



Core/SAN fabric switch configurations examples (Brocade)

16 switch mesh of fabric switches16 switch mesh of fabric switches

16 switch mesh of fabric switches

TERMINOLOGY1 Core switch chassis

12000 ‘box’ = 2logical 64-port switches

64-port 64-port

1 to 14 SAN fabric switches

64-port64-port

TERMINOLOGY1 Core switch chassis

12000 ‘box’ = 2logical 64-port switches

64-port 64-port

1 to 14 SAN fabric switches

64-port64-port

Core Switch definition and SAN fabric with up to 16 switches

A maximum of 16, with up to four 64-port switches


8/16/32 8/16/32 8/16/32 8/16/32

8/16/32 8/16/32 8/16/32 8/16/32

64-port 64-port 64-port64-port


HA support requires a duplicate

SAN



8/16/32 8/16/32 8/16/32 8/16/32

8/16/32 8/16/32 8/16/32 8/16/32




SAN

Two maximum SANs for high availability

Benefits of a SAN


Director/Edge switch configurations examples (McData)

XP and VA Arrays

fc-64 / Director 2/64

HP-UX HP-UX

XP and VA Arrays

fc-64 / Director 2/64

HP-UX HP-UX

Single Director switch configuration

1 to 12 Edge Switches6 Edge Switchestop and bottom

Edge Edge Edge Edge

Edge Edge Edge Edge




SAN



Edge Edge Edge Edge

Edge Edge Edge Edge




SAN


Director/Edge switch maximum SANs for high availability

Note A maximum of 16 switches are supported with up to eight directors in a single SAN.



1 and 2Gb/s fabric topology recommendations There are no specific topology rules related to mixing of 1 and 2Gb/s components in a fabric. However, HP does strongly recommend these guidelines be followed:

When using 1 and 2Gb/s switches in the same fabric, use 2Gb/s switches in the core for Core to SAN Switch or Director to Edge Switch topologies.

Connect 2Gb/s switches together to take advantage of the ISL Trunking feature when using Fibre Channel switch models that support this feature.

Use 2Gb/s switches for connections to 2Gb/s capable devices. In general, for SANs with 1 and 2Gb/s components, the transfer rate between devices and ports on switches are determined by the speeds supported by the individual ports that are connected. If two 2Gb/s devices or switch ports are connected together the speed will be 2Gb/s for that segment in the fabric. If two 1Gb/s devices or switch ports are connected together the speed will be 1Gb/s for that segment in the fabric. If a 2Gb/s and a 1Gb/s port are connected together the speed will be 1Gb/s for that segment.

Zoning rules, SAN security, and SAN management for 2Gb/s switches are the same as for 1Gb/s switches.

Benefits of a SAN


Zoning A zone is a group of fabric-connected devices (storage, tapes, and hosts) arranged into a specified grouping. Any device connected to a fabric can be included in one or more zones. Devices within a zone possess an awareness of other devices within the same zone—they are not aware of devices outside of their zone.

Zone members (ports, WWNs, or aliases) are grouped into a zone. Zones, in turn, are grouped in a zone configuration (a collection of zones). Zones can overlap—a device can belong to more than one zone. A fabric can consist of multiple zones. A zone configuration can include both hardware-enforced and software-enforced zones and there can be any number of zone configurations resident on a switch.

Note Only one configuration can be active (enabled) at a time. The number of zones allowable is limited only by memory usage.

Use zones to create logical subsets of the fabric to accommodate closed user groups or to create functional areas within the fabric. For example, include selected devices within a zone for the exclusive use of zone members, or create separate test or maintenance areas within the fabric.

Zoning is not used for the purpose of isolating I/O traffic in the SAN or Fibre Channel events from a third-party host such as LIPs. These events are automatically isolated through the switch and fabric topology.

Zone types Zone types are:

Port Zone — A zone containing members specified by switch ports (domain ID and port number), or aliases of switch ports, only. Port zoning is hardware enforced in the HP StorageWorks Fibre Channel SAN Switch 8 or 16 and beyond.

WWN Zone — A zone containing members specified by device World Wide Names (WWN), or aliases of WWNs, only. WWN zones are hardware enforced in the HP StorageWorks Fibre Channel SAN Switch series. WWN zones are software enforced in the SAN switch 8 /16 switches.

Mixed Zone — A zone containing some members specified by WWN and some members specified by switch port. Mixed zones are software enforced through the fabric name server only.

Broadcast Zone — Only one broadcast zone can exist within a fabric. It is named “broadcast” and it is used to specify those nodes that are to receive broadcast traffic. This type of zone is hardware enforced—the switch controls data transfer to a port. When zoning is disabled, devices can communicate without regard to zone restrictions. When zoning is enabled, zoning is enforced throughout the fabric and devices can communicate only within their zones.



Zone enforcement Zones can be hard (hardware enforced), soft (advisory), or broadcast. In a hardware-enforced zone, zone members can be specified by port number or by WWN, but not both. A software-enforced zone is created when a port member and WWN member are in the same zone.

Hardware Enforced Zones — All zone members are specified as either switch ports or by WWN. Any number of ports or WWNs in the fabric can be configured to the zone.

If WWNs are used exclusively in a zone, new devices can be attached without regard to physical location. In hard zones, switch hardware ensures that there is no data transferred between unauthorized zone members. However, devices can transfer data between ports within the same zone. Consequently, hard zoning provides the highest level of security.

Software Enforced Zones — At least one zone member is specified by WWN and one member is specified as a port. In this way, you have a mixed zone that is software enforced. When a device logs in, it queries the name server for devices within the fabric. If zoning is in effect, only the devices in the same zones are returned. Other devices are hidden from the name server query reply.

When using software-enforced zones, the switch does not control data transfer and there is no guarantee of data being transferred from unauthorized zone members. Use software zoning where flexibility and security are ensured by the cooperating hosts.

A switch can maintain any number of zone configurations. However, only one zone configuration can be enabled (enforced) at a time. Because multiple configurations reside in the switch, you can switch from one configuration to another as events dictate. For example, you can write a script to set up a pre-specified zone configuration to be enabled at certain times of the day, or, in the event of a disaster, you can quickly enable a defined configuration to implement your disaster policy.

Note The current version of the HP-UX driver has the issue that the switch port address is part of the device path. If the device is moved to another physical port, the HP-UX system will not be able to see the device until the device files are re-built (ioscan, reboot, and so on). This will be changed in a later HP-UX release when it changes to a worldwide name-based addressing scheme.

Benefits of a SAN


Zoning implementation

Zoning can be implemented and administered from any switch in the fabric. When a change in the configuration is saved, it is automatically distributed to all switches in the fabric. For that reason, zoning requires that all switches in the fabric have an active zoning license. Zoning can be administered through:

Telnet command interface

Web Tools web interface

! Important Zoning is required when HP-UX 11.0 or 11i is used in a heterogeneous SAN with other operating systems. HP-UX is incompatible in zones with all other operating systems.

Members

Configs

Zones

Zone Sets



SAN fabric zoning rules The fabric zoning feature is supported with all HP Fibre Channel switch models. Zoning can be used to logically separate devices and different hardware platforms and operating systems in the same physical SAN. Use of zoning is required under these specific conditions:

When mixing pre-merger HP and pre-merger Compaq storage systems and servers in the same SAN fabric. Refer to Chapter four “Heterogeneous SAN Platform and Storage System Rules” in the hp StorageWorks SAN design reference guide for more information.

When mixing different hardware platforms, operating systems, or storage systems that are currently only supported in homogenous SANs and it is unknown whether there are interaction problems. Refer to table 14 and 15 of the hp StorageWorks SAN design reference guide for specific information about zoning in heterogeneous SANs.

When there are known interaction problems between different hardware platforms or operating systems and specific storage system types.

When the number of nodes or ports in the SAN fabric exceeds a storage system connection support limit.

Connectivity rules In general there is no limit on the maximum number of zones in a SAN and overlapped zones are supported.

Benefits of a SAN


MSA zoning considerations

Zoning is an efficient method of managing, partitioning, and controlling access to SAN devices. Fabric zoning allows you to automatically or dynamically arrange fabric-connected devices into logical groups (zones) across the physical configuration of the fabric. These zones can include selected storage, servers, and workstations within a fabric. Information access is restricted to only the “member” devices in the defined zone.

Although zone members can access only other members in their zones, individual devices can be members of more than one zone. This approach enables the secure sharing of your storage resources, a primary benefit of storage networks. In addition to improving security, zoning can also help you simplify management of heterogeneous fabrics, maximize storage resources, and segregate storage traffic.

In the MSA SAN Switch 2/8, zoning enables you to create isolated Fibre Channel networks with a limited number of connected devices. By limiting the number of devices in a zone, you can obtain more robust performance and enhance your access protection.



Zoning methods

Note Refer to the switch user’s guide for a detailed explanation of zoning methods.

You can perform zoning for the MSA SAN Switch 2/8 using either the Command Line Interface (CLI) or using this MSA Fabric Switch Management Utility.

!

WARNING Never add a zoned switch to an established fabric that has no zoning. If a switch configured with zoning is added to a fabric that has no configured zoning, the fabric’s HBAs and targets will not be able to communicate and the traffic in the fabric will be disrupted. For best results, only add a switch configured with zoning to a fabric configured with the same zoning configuration.

Regardless of which tool you use, you must understand the following zoning elements before you begin to create zoning on a MSA SAN Switch 2/8:

Zones — Logical entities that represent groupings of zone members. Each zone must be assigned a unique zone name when it is defined.

Zone Sets — Logical entities that enable grouping of a set of zones. They define a zoning configuration. Each zone set is assigned a unique zone set name when it is defined.

The embedded MSA Fabric switches allow the storing of multiple zone sets. However, only one of these zone sets can be activated at a time. The other zone sets can be used as backup, trials, or other user-defined configurations.

Zone Members — Fibre Channel devices that are identified by their World Wide Port Names (WWPNs). Any device that you want to include in a zone must be identified as a zone member. Internally the zone members are tracked by their WWPNs, however, you can create a zone member name that acts as an alias for the device, making it easier to identify the devices during configuration and operation.

Examples of Fibre Channel devices that can be named as zone members are:

• Servers

• RAID systems

• Disk drives

• Tape libraries

Note Although Fibre Channel devices do not need to be connected during configuration, HP recommends that all your Fibre Channel devices be connected to the embedded switch when you configure zone members.

Benefits of a SAN


Display zoning The Switch Management Utility allows you to display zoning in two ways:

Merged — Used when you are interested in viewing information for zones merged with other switches on the fabric.

Local — Used when you are interested in viewing, creating, or editing zone sets, zones, and zone members for the switch presently being monitored.

Configure zoning with CLI Use the CLI to configure zones, zone sets, and zone members and to apply the new or edited zone configurations to the switch.

To ensure uninterrupted operation of the integrated switch options, a three-stage process was developed for configuring zoning using CLI:

1. Create the zones, zone sets, and zone members in a temporary area called the pending table.

2. Verify the configuration in the pending table to ensure that the zoning configuration is what you need.

3. Save the pending table permanently in the active table, and then apply the new zoning configuration to the switch.



Storage consolidation • Better disk capacity utilization than DAS

• More efficient storage growth with storage consolidation

• Better disk capacity utilization than DAS

• More efficient storage growth with storage consolidation

Industry experts believe a large number of IT companies are grossly underutilizing their existing storage resources, resulting in unnecessary storage expenditures and added management expenses. According to the experts, average direct-attached utilization rates are approximately 40%.

Storage consolidation saves money by creating a larger pool of storage for the hosts. In the preceding example, it is easy to see that distributed storage can be wasteful. If both servers had 100GB of storage you needed to add 40GB to the server with 95% of its storage used, you would be forced to purchase another 20GB of storage even though the server on the right has 60GB of unused space.

By consolidating storage, both servers can have access to the same shared pool. You can now the storage requirements without purchasing any additional storage.

With storage doubling every year and critical shortages of IT staff, the benefits of storage consolidation for a company are huge. According to a recent article by the Enterprise Storage Group, the average storage in a non-SAN environment that a single administrator can adequately handle is under 500GB.

In a SAN environment, that same administrator can manage up to four to six times that amount. With today’s rapid growth, this could mean the difference between keeping up or shutting down a business.

Benefits of a SAN


DtS with the MSA Direct-attached storage (DAS) to SAN (DtS) architecture is an exclusive HP feature that provides a quick and easy way to migrate stored data protected by Smart Array controllers to the MSA storage systems (MSA1000, MSA1500 cs, MSA1510i).

Smart Array Smart Array writes

configuration information

oneach drive

D11

C22

D1n

C21C2n

D12

B31

B32B1n

When drives are moved, new array recognizes

configuration information immediately

MSA1000

D11

C22

D1n

C21

D12

B31

B32B1n

Instant MigrationInstant

migration

Smart ArraySmart Array Smart Array writes


oneach drive

D11

C22

D1n

C21C2n

D12

B31

B32B1n



MSA1000MSA1000

D11

Drive 1 Drive 2 Drive n

C22

D1n

C21C2n

D12

. . .B31

B32B1n

. . .

RAID LevelConfig Area (RIS)RAID LevelLUN Info

Other Config InfoSpare Drive Info


migration


Other Config Info Spare Drive Info



RAID LevelConfig Area (RIS)RAID Level

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n


LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD12

C22B32


LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoB11

C31B21



oneach drive

D11

C22

D1n

C21C2n

D12

B31

B32B1n



MSA1000MSA1000

D11

C22

D1n

C21

D12

B31

B32B1n


migration



oneach drive

D11

C22

D1n

C21C2n

D12

B31

B32B1n



MSA1000MSA1000

D11

Drive 1 Drive 2 Drive n

C22

D1n

C21C2n

D12

. . .B31

B32B1n

. . .






migration





RAID LevelConfig Area (RIS)RAID LevelRAID LevelConfig Area (RIS)RAID Level

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n


LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD12

C22B32


LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoD1n

C2nB1n

LUN Info

Other config info

Spare drive infoB11

C31B21

DtS process

Data stored on 1-inch universal disk drives (Ultra2 and Ultra3) using newer Smart Array controllers and data stored on direct-attached RA4100 storage systems can be migrated to the MSA1xxx. Following a step-by-step procedure, you simply remove the drives from the older systems and insert them into the MSA1xxx.

The existing data and configuration information remains intact. In addition, the RAID set and data are preserved, allowing migration to be completed in minutes, not hours.

DtS architecture provides:

Instant consolidation of DAS into a SAN environment.

An upgrade path from Smart Array controlled drives and data to a SAN environment.

Simple redeployment of a DtS environment for growth management and capacity utilization.

Support for up to 42 drives and 32 volumes.



HP Array Controllers that support DtS are:

Smart Array 3100ES

Smart Array 3200

Smart Array 4200

Smart Array 4250ES

Smart Array 431

Smart Array 5i

Smart Array 532

Smart Array 5312

Smart Array 5300

RA4100 Controllers

Benefits of a SAN


Tape Libraries Support

A SAN backup configuration—sharing storage resources from behind a Fibre Channel switch out to multiple servers—enables IT staff to achieve the same benefits as a more traditional network backup—up to a 2x increase in tape resource utilization and one consolidated point of management—while also taking full advantage of high speed tape drive technology in order to more easily meet backup windows. In addition, because a SAN provides a dedicated backup network, the backup traffic is removed from the LAN with a subsequent increase in consistent LAN performance.



There are several significant benefits to deploying a SAN-based backup solution:

High Performance — The solution provides performance comparable to direct-attach solutions. It does not suffer from network bandwidth limitations inherent in traditional network backup solutions.

Scalability — Tape resources are pooled and shared across all hosts in the environment. Once the solution is deployed, capacity is easily expanded by adding additional tape drives to the pool.

Flexibility — Backup capacity is readily allocated and reallocated as the environment changes. Tape drives are not dedicated or locked in to specific servers as with direct attach backups.

Leveraged Investment — Tape drives and libraries are pooled. These investments shared across the enterprise data center.

Reduced Administrative Costs — Consolidated backup operations, centrally located and managed hardware result in less administrative effort.

SAN backup components The key components SAN backup solutions add to the SAN are:

Tape Library — Tape library and the tape drives it contains provide the offline storage for backup on the SAN. The tape library provides automated tape handling, which becomes a key requirement when consolidating backups across multiple servers.

Router — Router (sometimes referred to as a bridge) device provides connection between Fibre Channel topologies and SCSI devices. It does this by presenting the SCSI devices as Fibre Channel devices to the SAN and then relaying Fibre Channel commands to these SCSI devices. Routers are typically used for tape drives and libraries.

Backup Software — Backup software is deployed on each of the hosts on a SAN that will perform backups. This typically requires installing server-type licenses and software on each of these hosts.

SAN Management Software — SAN Management software is used to manage resources, security, and functionality on a SAN. This can be integrated with host-based device management utilities or embedded management functionality, such as hub or switch Ethernet ports.

Benefits of a SAN


NSR and the MSA1000

Network Storage Router in a SAN

HP offers Network Storage Routers (NSRs) to span the Entry-Level to Enterprise customer environment. The HP StorageWorks Network Storage Router is a Fibre Channel-to-SCSI bridge that allows multiple host servers to communicate with a tape device over a Fibre Channel link.

Available NSRs include:

e1200 and e2400 —The HP StorageWorks Network Storage Router e1200 and HP StorageWorks Network Storage Router e2400 provide embedded fiber options for the MSL and ESL tape libraries. They provide many of the same benefits as an external Network Storage Router without consuming extra rack space.

• The e1200 is a 1 Fibre Channel x 2 LVD SCSI router/card that will slide into a slot in the back of the MSL5000 libraries. It will support up to four drives and can support multiple libraries.

• The e2400 is a 2 Fibre Channel x 4 LVD SCSI router/card that is embedded into a card cage in the back of the ESL9000 libraries. The E2400 supports up to eight LVD drives and can be upgraded to a 4 Fibre Channel x 8 LVD SCSI router to support 16 LVD drives by purchasing an additional part number with two more cards.



N1200 — A 1U rackmount router with one Fibre Channel port and two SCSI ports. It allows customers to connect SCSI based tape libraries to the SAN increasing backup speeds up to 90%. The N1200 offers enterprise class features at a price point appealing to the low to mid range customers. It is targeted towards customers that want to reduce or remove their backup window. It offers support for serverless backup, 2Gb Fibre Channel and has web-based management allowing for remote management. This is the first router to bring 2Gb Fibre Channel to the midrange environment.

M2402 — A 1U rackmount Fibre Channel-to-SCSI router with two Fibre Channel ports and four SCSI ports on the base model, upgradeable to six fiber ports or twelve SCSI ports. It allows multiple host servers to communicate with a SCSI tape device over a Fibre Channel link making backup speeds five times faster. It is targeted towards customers whose backup window is impacting mission-critical business operations and who need to reduce or remove the backup window. It offers support for serverless backup, LVD/SE and HVD SCSI libraries, 1Gb and 2Gb Fibre Channel and has web-based management enabling remote management.

Note Detailed SAN-based backup implementations are covered in the StorageWorks Heterogeneous Open SAN Design Reference Guide.

Benefits of a SAN


Tape libraries for the MSA1000

EBS example with an MSA1000

The MSA1000 and HP StorageWorks EBS is a Fibre Channel-based tape backup and restore solution, integrated into primary storage SAN configurations and designed to assist backup needs in a SAN environment.

For data protection, the MSA1000 and EBS SAN backup provide:

Shared tape storage

Scalability

Automation

High performance

• Backup rate up to 158.4GB/h

• No network bottlenecks

Snapshot with Virtual Replicator

Virtual Replicator snapshots enable:

Minimal interruption to business (seconds)

Strategy for online and offline data storage

Fast recovery of data from online snapshots

Backup to tape whenever necessary or desired

For a complete listing of supported tape libraries, visit the HP website at: http://h18006.www1.hp.com/storage/tapestorage.html.



Learning check 1. Briefly describe current industry storage trends.

.................................................................................................................

.................................................................................................................

2. Provide a simple definition for a storage area network (SAN).

.................................................................................................................

.................................................................................................................

3. List five features of a SAN.

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

4. List five benefits of a SAN.

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

5. What are the three classes of B class switches supported by HP?

.................................................................................................................

.................................................................................................................

.................................................................................................................

6. What are HP recommended guidelines when mixing 1 and 2Gb/s switches?

.................................................................................................................

.................................................................................................................

.................................................................................................................

7. Describe zoning.

.................................................................................................................

.................................................................................................................

.................................................................................................................

Benefits of a SAN


8. When is zoning required on a HP-UX 11.0 or 11i?

.................................................................................................................

.................................................................................................................

.................................................................................................................

9. Describe two advantages of implementing storage consolidation.

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

10. Describe the DAS to SAN (DtS) architecture.

.................................................................................................................

.................................................................................................................

.................................................................................................................

11. What are three benefits of an EBS SAN backup?

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................




MSA1xxx Product Overview Module 2

Introduction This module discusses the Modular Smart Array (MSA) 1000, MSA1500cs, and MSA1510i array storage systems in general terms. Topics include:

Product positioning and benefits

Product descriptions

Key features and capabilities

Supported hardware and software

References in this training course to MSA array systems apply to only the three systems mentioned above, and do not pertain to other MSA product models.




Explain the positioning of the MSA1000, MSA1500cs, and MSA1510i array systems in the SAN product line

Describe the customer benefits of the MSA array systems

Describe each of the three systems

Identify the basic features and capabilities of the MSA1XXX series array systems

Identify the hardware systems and software applications supported by the MSA array systems

MSA1xxx Product Overview


MSA1xxx product positioning

flexible and scalable entry-level fibre channel storage

• scalable modularity• heterogeneous• ease of adminis tration• price/scalability

ScalabilityScalability

Ava

ilabi

lity

Ava

ilabi

lity

Simple, affordable, fault tolerant Smart

Array technology

• clustering & shared s torage

• minimal infrastructure • DtS convers ion• price/availability

plugged into the data center fabric to

maximize scalability and availability

• high connectivity• high scalability• high efficiency• highes t disaster tolerance

solutions• universal connectivity and

heterogeneity

Branch OfficeBranch Office

high performance internal / external

storage with Smart Array technologies

•price/capacity

WorkgroupsWorkgroups

EVA5000

MSA1000

MSA500EnterpriseEnterprise

DepartmentalDepartmental

XP

EVA3000

MSA30

MSA1500 w/SATA enclosure

flexible and scalable entry-level fibre channel storage

• scalable modularity• heterogeneous• ease of adminis tration• price/scalability

ScalabilityScalability

Ava

ilabi

lity

Ava

ilabi

lity

Simple, affordable, fault tolerant Smart

Array technology

• clustering & shared s torage

• minimal infrastructure • DtS convers ion• price/availability

plugged into the data center fabric to

maximize scalability and availability

• high connectivity• high scalability• high efficiency• highes t disaster tolerance

solutions• universal connectivity and

heterogeneity

Branch OfficeBranch Office

high performance internal / external

storage with Smart Array technologies

•price/capacity

WorkgroupsWorkgroups

EVA5000

MSA1000

MSA500EnterpriseEnterprise

DepartmentalDepartmental

XPXP

EVA3000

MSA30

MSA1500 w/SATA enclosure

MSA1000/1500cs/1510i placement within the SAN product line

The HP online storage systems include a wide range of solutions offering industry-leading features and benefits. These include disk arrays, which offer superior storage solutions for mission-critical applications, with high availability, reliability and redundancy; outstanding performance and scalability; shared and secured heterogeneous environments.

The HP online storage portfolio includes entry-level, mid-range, and enterprise-level storage systems.

Entry-level Entry-level storage products from HP, which includes direct -and SAN-attached SCSI and Fibre Channel solutions, are price sensitive and provide moderate scalability. The Modular SAN Array (MSA) 1000, which includes direct attached storage (DAS)-to-storage area network (SAN) (DtS) support, scales from 2 – 42 drives. The va71x0 family provides Fibre Channel disk arrays featuring scalability, high performance, and advanced data protection. The va7100 includes a single controller enclosure with up to 15 disks and the va7110 supports over 6TB with up to 45 disks. Both the MSA1000 and va71x0 offer heterogeneous operating system support and are well suited for the entry-level environment.

MSA1500cs MSA30

MSA1000

EVA4000, 6000, 8000



Mid-range Mid-range storage systems provide additional scalability and more robust storage capability than the entry-level systems. Typical mid-range application environments can survive minutes of planned downtime. While budget limitations are still an issue, the midrange business values high-end functionality as equally important to affordable prices. Designed with high-end features at midrange prices, the HP va7400 family and MA8000/EMA12000/EMA16000 function in a heterogeneous environment that requires more scalability than entry-level solutions.

Enterprise-level The enterprise-level solution enables the highest levels of continuity, performance, consolidation, and manageability. For those enterprises with Mainframe and Open Systems storage, the HP XP storage system is the ideal choice to consolidate all platforms into a single, manageable storage system. For customers that require the flexibility to consolidate their open systems platforms and gradually increase levels of capacity, scalability, performance, virtualization and high availability, the HP Enterprise Virtual Array is the ideal modular choice.

MSA1xxx positioning The MSA1000 and MSA1500cs (cs = controller shelf) are 2Gb Fibre Channel array storage systems designed for entry-level to mid-range Storage Area Network (SAN) environments. The MSA1510i system provides 1Gb Ethernet capability to the same sized environments over IP networks. At initial release, the MSA1510i supports only 1000BaseT devices and requires Cat5e cabling.

The array controllers used by the three systems are basically the same, with differences in capability provided by unique firmware versions. The MSA1000 and MSA1500cs use the MSA1000 controller, and the MSA1510i system uses the MSA1510i controller. The controllers support up to Ultra320 disk drives, however, they will run at Ultra3 speeds.

The MSA series systems are positioned to reduce the complexity, expense, and investment risk of the customer’s SAN deployment, while providing scalability. The modular design allows customers to easily add storage capacity as needed.

All three systems are scalable to meet future user storage needs, with the MSA1500cs and MSA1510i providing additional flexibility by supporting both SCSI and Serial ATA (SATA) storage enclosures. The MSA1000 can be expanded with two additional 14-bay MSA30 SCSI drive enclosures, for a 42-drive maximum capacity. The MSA1500cs and MSA1510i systems can support up to four 14-bay MSA30 SCSI drive enclosures (56 drives maximum) or up to eight 12-bay MSA20 SATA drive enclosures (96 drives maximum). Both systems are capable of supporting a mix of SCSI and SATA enclosures.



Customer benefits summary Customer benefits can be divided into five categories: performance, expandability, availability, investment protection, and management tools.

Performance The MSA offers affordable performance by providing:

Up to 30,000 I/Os per second and bandwidth up to 200Mb/s

2Gb host-side connections (MSA1000 and MSA1500cs) or 1Gb Ethernet connectivity (MSA1510i)

Ultra320 SCSI drive support

Standard 256MB battery-backed cache, expandable to 512MB

Expandability The modular design of the MSA provides the user with the ability to start with an affordable, entry-level SAN system and expand the array as data processing and storage requirements grow. This is accomplished by adding MSA30 SCSI drive enclosures (all three systems) and/or MSA20 SATA drive enclosures (MSA1500cs and MSA1510i).

Availability MSA system availability is enhanced through the use of redundant, hot-pluggable components. Replacement of hot-pluggable components allows repair of the system without interruption of operational data processing or backup operations. ROM recovery and ROM cloning permit recovery of controller firmware within a controller and between redundant controllers, respectively.

Investment protection Capital investment is protected by providing system expansion capability without having to invest in new controllers. Both the controller and drive firmware can be upgraded to incorporate new capabilities without having to change an entire system. Support of multiple operating systems allows users to choose the system best suited for their needs, knowing that the MSA will support their choice. Support of both SCSI and SATA drives enables customers to provide both online and nearline storage capabilities in one affordable system.

Management tools The availability of multiple management applications and utilities allows the user to configure and manage their MSA array system to meet their specific needs. System monitoring and management operations can be controlled remotely, offering more flexibility to configure, manage, and troubleshoot the systems.



MSA1000 product overview The basic MSA1000 system consists of a 4U unit containing integrated controller enclosure and 14-bay SCSI drive enclosure. The basic unit comes with a single MSA1000 controller and space for an optional second controller. Also included in the basic chassis are a Fibre I/O module with an SFP transceiver, fans, and power supplies. Power supplies and fans located in the disk drive portion of the MSA1000 provide power and cooling to both the controller enclosure and the disk drives. Also included with the basic MSA1000 are power cables, serial management cable, and support CD and documentation. Detailed discussions of the hardware components are included in Module 3, Hardware Components.

The photo below shows the MSA1000 system with the optional redundant controller installed. The drawing shows the back of an MSA1000 with a single controller and I/O module.

MSA1000 front view with dual controllers installed

MSA1000 rear view with single controller and I/O module



The MSA1000 is an expandable system which can vary from 1 – 42 hard drives, depending on user storage needs. The basic system, with fourteen 300GB 1” Universal hard drives, has a maximum storage capacity of 4TB (14 x 300GB ≈ 4TB). With the addition of up to two MSA30 SCSI drive enclosures, the capacity of the system can be expanded to a maximum of 12TB of storage, using forty-two 300GB SCSI hard drives.

The MSA1000 supports only SCSI drives and is used for online storage needs.

A photo of the fully-expanded system, with the optional redundant controller installed, appears below.

The fully expanded MSA1000 with redundant controllers



MSA1500cs product overview The MSA1500 cs array system is a 2Gb Fibre Channel SAN-attached 2U controller shelf that connects to both SCSI and SATA storage enclosures. The enclosure comes with a single MSA1000 controller and space for an optional second controller. Also included in the basic unit is a single Fibre Channel I/O module with an SFP transceiver, one dual-channel SCSI I/O module, dual fans, dual power supplies, power cables, a serial management cable, a rack-mounting kit, and documentation. Drive enclosures, disk drives, and cabling are purchased separately.

The MSA1500cs controller enclosure with redundant controller installed – front view

MSA1500cs controller shelf with single controller - back view

Support for both SCSI and SATA enclosures enables users to perform online storage tasks and disk-to-disk backup (nearline storage) on the same array system. The MSA30 enclosure holds up to 14 SCSI drives per enclosure, and the MSA20 SATA enclosure holds up to 12 SATA drives per enclosure. With the maximum of four MSA30 SCSI storage enclosures, the MSA1500cs provides up to 16TB (56 drives x 300GB≈16.8TB) of online storage capacity. With the maximum of eight MSA20 SATA storage enclosures, the system provides up to 48TB (96 drives x 500GB≈48TB) nearline storage capacity.

The MSA1500cs enclosure supports a maximum of four dual-channel SCSI I/O modules. The SCSI I/O module supports one MSA30 enclosure or up to two MSA20 enclosures per module. SCSI and SATA enclosures cannot be mixed on a single module.

The 1500cs supports Secure Path, MPIO, and QLogic failover drivers, and support active/passive and active/active controller pairs.



MSA1510i product overview The MSA1510i is an iSCSI-based 2U controller enclosure that connects to both SCSI and SATA drive enclosures. Although the controller enclosure resembles the MSA1500cs, it controls storage on an IP network rather than a Fibre Channel network. At initial product release, the MSA1510i supports only a 1000BaseT network.

The basic enclosure comes with a single controller, one iSCSI Ethernet module (with two Ethernet ports), one dual-channel SCSI I/O module, redundant power supplies, redundant fans, a rack-mounting kit, power cables, a serial management cable, and documentation. There is space in the enclosure for an optional second controller. Cables, disk enclosures, and hard drives must be ordered separately.

MSA1510i controller enclosure with redundant controller installed – front view

MSA1510i controller enclosure with redundant controller installed – back view

The capabilities, capacities, and restrictions on the use of SCSI and SATA enclosures that apply to the MSA1500cs also apply to the MSA1510i.

The back of the controller enclosure provides connectivity to the IP network and to the storage array. The iSCSI Ethernet module provides two 1Gb Ethernet interfaces to the IP network. In a dual-controller configuration, a maximum of four Ethernet interfaces are available on the enclosure. For interfacing with storage, there is a maximum of four dual-channel SCSI I/O modules available. SCSI I/O module use and restrictions that apply to the MSA1500cs also apply to the MSA1510i.



Key features of the MSA array systems The features of the MSA array systems are outlined in the following manner:

Features common to the three systems

Features of the MSA1000

Features of the MSA1500cs

Features of the MSA1510i

Features common to the three systems The following features are common to the MSA1000, MSA1500cs, and the MSA1510i array systems:

Direct Attach Storage (DAS)-to-SAN (DtS) architecture The DtS architecture provides a quick and easy way to migrate stored data on SCSI disks protected by most Smart Array controllers to an MSA1000, MSA1500cs, or MSA1510i storage system. DtS works on SCSI enclosures only.

RAID 6 fault tolerance (also known as RAID ADG) RAID 6 is the highest level of RAID protection. It allocates two sets of parity data across drives and allows simultaneous write operations. This level of fault tolerance can withstand two simultaneous drive failures without downtime or data loss. RAID 6 requires a minimum of four disk drives.

Hot-pluggable components The three systems all permit the hot-plug replacement of redundant controllers, disk drives, fans, power supplies, and disk enclosures. The MSA1510i also allows replacement of I/O modules.

Pre-failure Warranty Disk drives on the MSA1000 and the enclosures and hard drives attached to the MSA1500cs and MSA1510i and monitored under Insight Manager are supported by a Pre-failure (replacement) Warranty.



Features of the MSA1000 The following features of the MSA1000 may be common to one, but not both, of the other MSA systems.

A 4U rack-mount design integrating the controller shelf and a disk enclosure

2Gb Fibre Channel host connections The system auto-negotiates to the level of the attached infrastructure (1Gb or 2Gb)

Supports single Fibre Channel I/O module or optional 2Gb 2/6 MSA Fabric Switch (the 2/6 switch is no longer sold but is supported), 2Gb 2/8 Fibre Channel Fabric switch, or 2Gb 3-port Fibre Channel hub

Supports enterprise-class HP Ultra2, Ultra3, and Ultra320 Universal 1” SCSI drives

Scalable from 1 to 42 disk drives by adding up to two optional MSA30 drive enclosures

Compatible with ISV backup and restore software from HP, VERITAS, and others

Supports multipathing using Multipath Input/Output (MPIO) (Windows OSs only), HP Secure Path, or QLogic failover drivers.

Supports single-server and clustered-server environments

The system comes with or is supported by the following configuration and management software applications

• Array Configuration Utility (ACU) ACU is a browser-based disk configuration utility that lets the user view, set up, and configure the array controllers and storage systems.

• Command Line Interface (CLI)

• Systems Insight Manager (SIM)

• Event Monitoring Service (used with HP-UX servers)

• Array Diagnostics Utility (ADU) This utility collects information about the array controllers in the system and generates a list of potential problems it has identified. It produces a report that can be saved to a diskette and analyzed by support technicians to aid in problem resolution.



Features of the MSA1500cs The following features of the MSA1500cs may be common to one, but not both, of the other MSA systems.

A 2U rack-mount design controller shelf

Supports both enterprise-class SCSI and SATA drive enclosures and hard drives

• Up to four MSA30 SCSI drive enclosures

• Up to eight MSA20 SATA drive enclosures

• A mix of both SCSI and SATA enclosures The mix of enclosures is subject to the restrictions on SCSI I/O module utilization.

2Gb host connections The system auto-negotiates to the level of the attached infrastructure (1Gb or 2Gb)

Supports two single-port Fibre Channel I/O modules

Supports enterprise-class HP Ultra3 and Ultra320 Universal 1” SCSI drives

Scalable from 1 to 56 SCSI disk drives or 1 to 96 SATA drives

Supports the 4Gb Fibre Channel Fabric “B-Series” family of switches Although the 4Gb FC Fabric switch is supported, the array and HBAs operate at a maximum of 2Gb/s.

Compatible with several backup and restore applications

Supports single-server and clustered server environments

Supports multipathing using MPIO (Windows OSs only), HP Secure Path, or QLogic failover drivers (Linux)

Supports active/active controller pairs

This system comes with or is supported by the following configuration and management applications:

• ACU (operating system dependent)

• CLI

• SIM

• ADU

• Event Monitoring Service (EMS) (used with HP-UX servers)



Active/active controllers Since the active/active controller capability is new, it is discussed in some detail here.

Previously, the MSA1500cs redundant controller pair was limited to active/passive operations. The passive controller could take over if the active controller failed, but could not process I/O if the active controller was operational. Now, the system supports simultaneous I/O processing on the controller pair. This provides better performance and high availability. LUNs are owned by only one controller at a time, but that ownership can change, either automatically or manually, depending on the user-defined configuration settings.

New MSA1500cs systems will be shipped as active/passive systems and will have to be upgraded. There is an application note for each of the operating systems (Windows, Linux, and HP-UX) explaining the migration process.

LUNs can be assigned to controllers explicitly or implicitly.

Explicit controller ownership is implemented when a LUN is assigned, by the user, to a specific controller. I/O requests for writes or reads to or from the LUN will be sent through the specified controller for processing. Explicit assignments are made using the MSA Command Line Interface (CLI) or HP-UX PVLinks.

Implicit controller ownership is implemented in the controller firmware itself. If the automatic controller path switching is enabled (again by the user), ownership of a LUN can be moved from one controller to the other based on a load balancing algorithm within the controller firmware. New I/O requests for the moved LUN will go to the new controller for processing.

MSA1500cs active/active limitations The following limitations apply to active/active operations of the MSA1500cs system.

MSA supports a maximum of 32 LUNs

MSA supports a maximum LUN size of 2TB

PVLinks supports a maximum of eight paths per LUN



Installation best practices There are some basic things that should be done to ensure a successful migration from an active/passive to active/active configuration.

Prior to installation, go the the MSA1500cs web site to obtain current information on required hardware and software versions supported by the MSA1500cs system. That web site is http://www.hp.com/go/msa1500cs.

Use the MSA1500cs Configuration Overview poster to identify items required for the installation. Record system information on the worksheets provided in the poster. This information will be required when configuring storage, entering connection information, setting up multipathing, making future configuration changes, and for referencing past activities.

Install the MSA1500cs in the sequence listed in the installation guide. Several of the steps have dependencies on preceding steps. Deviation from the installation sequence might require the user to uninstall and reinstall the MSA1500cs. Difficulties encountered by not using the proper sequence might result in lost time, lost revenue, and troubleshooting difficulties.

General installation considerations If installing a redundant controller in the system before migrating from active/passive to active/active, keep these considerations in mind.

Ensure both controllers have the same size cache module

Use installation instructions shipped with the new controller and I/O module

When the components are installed:

• Allow the cloning process to clone firmware from the primary controller to the new controller

• Wait for the controller to automatically restart and for the MSA STARTUP COMPLETE message to display in the controller LCD panel

Refer to the MSA1500cs Configuration Overview poster, the HP StorageWorks 1500 Modular Smart Array with active/active controllers installation guide, HP StorageWorks Modular Smart Array 1500cs application note: Migrating to active/active controllers in Linux environments, HP StorageWorks Modular Smart Array 1500cs application note: Migrating to active/active controllers in Windows environments, and HP StorageWorks Modular Smart Array 1500cs application note: Migrating to active/active controllers in HP-UX environments for installation/migration details.



Features of the MSA1510i The following features of the MSA1510i may be common to one, but not both, of the other MSA systems.

A 2U rack-mount design controller shelf

Supports both enterprise-class SCSI and SATA drive enclosures and hard drives

• Up to four MSA30 SCSI drive enclosures

• Up to eight MSA20 SATA drive enclosures

• A mix of both SCSI and SATA enclosures The mix of enclosures is subject to the restrictions on SCSI I/O module utilization.

1Gb Ethernet connectivity (two 1Gb-ports per iSCSI I/O module)

Supports only Windows OSs

Supports Ultra320 Universal 1” SCSI drives

Scalable from 1 to 56 SCSI drives or 1 to 96 SATA drives

Supports only single-server environments

Supports multipathing using MPIO DSM (Device Specific Module)

Supports a maximum of 20 servers

• Each server must have the iSCSI Initiator

• The MSA1510i supports only Microsoft iSCSI Initiator v2.01

Supports a maximum of 32 LUNs

Supports the following configuration and management applications

• Storage Management Utility (SMU)

• Access controls (embedded in the controller firmware and executed using the SMU)

• SIM

• CLI



Important initial release information for the MSA1510i Because system documentation had to be submitted prior to testing completion, some features and capabilities detailed in MSA1510i documentation were not included in the initial release of the product. Some of the key differences are outlined below, but users and service personnel need to read HP StorageWorks 1510i Modular Smart Array initial product release before unpacking and installing the MSA1510i. See the initial product release document for details of the key differences below and for other changes to system capabilities.

MSA1510i installation software CD The MSA1510i installation software CD should be the only means of installing MSA1510i-specific components on the server. Components on the CD have been tested and approved for use on the MSA1510i. Obtaining components from any other source might result in an unsupported configuration with unexpected results.

iSCSI initiator The iSCSI initiator must be obtained and installed from the Microsoft web site. When installing the iSCSI initiator, do not install the default multipath software included with the Microsoft iSCSI initiator; ensure that “Microsoft MPIO Multipath Support for iSCSI” is not selected. HP-approved MPIO software and the MSA1510i Device Specific Module (DSM) are installed in a separate step from the MSA1510i installation software CD. Because the Microsoft iSCSI DSM cannot co-exist with the HP MSA1510i DSM, if the MSA1510i installation software CD detects the Microsoft iSCSI DSM, the interface prompts the user to remove it from the server. Ensure that servers in the storage network are configured so that the Microsoft iSCSI DSM and the HP MSA1510i DSM are not needed on the same server. The Microsoft iSCSI DSM and HP MSA1510i iSCSI DSM can exist in the same storage network, but not on the same server.



100BaseT devices are not supported The MSA1510i is not supported for use with 100BaseT devices and cabling. Use only 1000BaseT (GigE) devices and qualified Category 5e (or better) Ethernet cables.

Clustering Clustering is not yet supported. This feature will be included in a future release.

Storage migration Existing storage can be migrated to the MSA1510i but cannot move back. Storage migration information was omitted from the initial documentation, but it will be included in the next release of the HP StorageWorks Modular Smart Array 1510i maintenance and service guide.

Drive flashing Documentation omitted this information, but it will be added to the next release of maintenance and service guides.

MIB-II data reporting is not yet supported Currently, Management Information Base II (MIB-II) reporting is not included in MSA1510i firmware. Because the lack of MIB-II reporting results in the loss of device-specific network statistical information, network monitoring should be done at the switch until MIB-II reporting is added to the MSA. This feature will be included in a future firmware release.

! Important Be sure to read the entire HP StorageWorks 1510i Modular Smart Array initial product release document prior to installing the MSA1510i system.



Supported software and hardware The following tables specify the software applications and hardware supported by MSA1000, MSA1500cs, and MSA1510i array systems.

Software/hardware component MSA1000 MSA1500cs MSA1510i

Operating systems Windows NT 4.0, SP6A

Windows 2000 Server-SP3

Windows Server 2003 (32- and 64bit)

NetWare 5.1,.6.0, 6.5 RH Linux 2.1, 3, 4

(32- and 64-bit) SuSE SLES8, SLES9

(32- and 64-bit) Tru64 UNIX

(homogeneous only) OpenVMS

(homogeneous only) HP-UX 11.11, 11.23

(homogeneous only) SCO OpenServer

6.0.0 SCO UnixWare 7.1.3,

7.1.4 (single controller homogeneous only)

Windows 2000 Server Windown 2000 Adv.

Server, SP2 (32- and 64-bit)

Windows EE 2003 (32- and 64-bit)

Windows Standard Ed. 2003 (32- and 64-bit)

NetWare 5.1, 6.5 RH Linux 2.1, 3, 4

(32- and 64-bit) SuSE SLES8, SLES9

(32- and 64-bit) HP-UX 11.11, 11.23

(homogeneous only)

Windows 2000, SP4 (32-bit)

Windows Server 2003 (32-bit)

Multipath software Secure Path 4.0c (Windows NT 4.0)

Secure Path 4.0c, SP2 (Windows 2000 Server, Windows Server 2003 (32- and 64-bit)

MPIO v1.1 (Windows 2000 Server, Windows Server 2003 (32- and 64-bit)

Secure Path 3.0c, SP2.1 (NetWare 5.1, 6.0, 6.5)

Secure Path 3.0c, SP2 (Red Hat Linux 2.1, 3, and SuSE SLES8 [32- and 64-bit])

QLogic Multipath Driver (Red Hat 2.1, 3, 4, SuSE SLES8 [32- and 64-bit], and SuSE SLES9 [32- and 64-bit])

Secure Path 4.0c, SP2 (Windows 2000 Server, Windows Server 2003 [32- and 64-bit])

MPIO v1.1 (Windows 2000 Server, Windows Server 2003 [32- and 64-bit])

Secure Path 3.0c, SP2.1 (NetWare 5.1, 6.0, and 6.5)

Secure Path 3.0c, SP2 (Red Hat Linux 2.1, 3, and SuSE SLES8 [32- and 64-bit])

QLogic Multipath Driver (Red Hat 2.1, 3, 4, SuSE SLES8 [32- and 64-bit], and SuSE SLES9 [32- and 64-bit])

MSA1510i MPIO v1.1




Cluster support Microsoft Cluster Services1 (Windows NT 4.0, Windows 2000 Server, Windows Server 2003 [32- and 64-bit])

NCS 1.01 (NetWare 5.1)2 NCS 1.6 (NetWare 6.0)2 NCS 1.7 (NetWare 6.5)3 Service Guard 11.14.024

(Red Hat EL 2.1) Service Guard 11.15.014

(SuSE SLES8) Service Guard 11.164

(Red Hat EL3, EL4, and SuSE SLES9)

Steeleye LifeKeeper 5.0.15 (All supported Linux OSs)

TruClusters 5.1A (Tru64 UNIX Alpha 5.1A)

TruClusters 5.1B-2 (Tru64 UNIX Alpha 5.1B-2 )

TruClusters 5.1B-3 (Tru64 UNIX Alpha 5.1B-3)

OpenVMS Clusters 7.3-1 (OpenVMS 7.3-1)

OpenVMS Clusters 7.3-2 (OpenVMS 7.3-2)

OpenVMS Clusters 8.2 (OpenVMS Alpha 8-2 and OpenVMS IA64 8.2)

OpenVMS Clusters 8.2-1 (OpenVMS IA64 8.2-1)

Service Guard A.11.14 or later (HP-UX 11.11)

Service Guard A.11.15 or later(HP-UX 11.23 [32- and 64-bit])

Microsoft Cluster Services1 (Windows 2000 Server, Windows Server 2003 [32- and 64-bit])

NCS 1.01 (NetWare 5.1)2



Service Guard 11.14.024 (Red Hat EL 2.1)

Service Guard 11.15.014 (SuSE SLES8)

Service Guard 11.164 (Red Hat EL3, EL4, and SuSE SLES9)

Steeleye LifeKeeper 5.0.15 (All supported Linux OSs)

Service Guard A.11.14 or later (HP-UX 11.11)

Service Guard A.11.15 or later(HP-UX 11.23 [32- and 64-bit])

Clusters are not supported in the initial release. Plans are for support in the next release.

1 For Windows 2000 Server and Windows Server 2003, there is a max of 8 nodes/cluster using Secure Path and 4 nodes/cluster using MPIO. 2 Up to 12 cluster nodes supported with Secure Path 3.0c SP2.1. 3 Up to 16 cluster nodes supported with NetWare 6.5 SP4, otherwise up to 12 nodes. 4 Service Guard requires a multipath solution. 5 SCSI only



Software/hardware component Operating System Array Configuration Utility (ACU) V7.0 (MSA1500) V6.0 (MSA1000)

Windows: online Linux: offline NetWare: offline

Storage Management Utility (MSA1510i only) Windows 2000, Windows 2003 Telnet and SSH Command Line (MSA1510i only) Windows 2000, Windows 2003 Command Line Interface (CLI) (accessed thru RJ-45Z serial port)*

Windows, Linux, NetWare

OpenView Storage Virtual Replicator Windows 2000, Windows 2003 SmartStart V5.5 or later Windows, Linux, NetWare HP Systems Insight Manager Windows, Linux, NetWare * Utilizing the CLI cable spare part number 259992-001


Servers HP ProLiant HP-UX HP Alpha Non-HP x86

HP ProLiant HP-UX HP Alpha Non-HP x86

HP ProLiant

Hard Drives (Universal 1”)

72GB, Ultra3201, 10K rpm 146GB Ultra320, 10K rpm 300GB Ultra320, 10K rpm 36GB Ultra320, 15K rpm 72GB Ultra320, 15K rpm 146GB Ultra320, 15K rpm

SCSI 72GB, Ultra3201, 10K rpm 146GB Ultra320, 10K rpm 300GB Ultra320, 10K rpm 36GB Ultra320, 15K rpm 72GB Ultra320, 15K rpm 146GB Ultra320, 15K rpm SATA 160GB, 7200 rpm 250GB, 7200 rpm 500GB

SCSI 72GB, Ultra3201, 10K rpm 146GB Ultra320, 10K rpm 300GB Ultra320, 10K rpm 36GB Ultra320, 15K rpm 72GB Ultra320, 15K rpm 146GB Ultra320, 15K rpm SATA 160GB, 7200 rpm 250GB, 7200 rpm 500GB

Host bus adapters2 See note 2. See note 2 See note 2 1 All Ultra320 Universal drives are backward compatible to Ultra2 and Ultra3 speeds. 2 See the individual array QuickSpecs or SPOCK streams for the most current HBA support information.




B-Series MSA SAN Switch 2/8

(embedded) SAN Switch 2/8V SAN Switch 2/16V SAN Switch 2/16N SAN Director 2/128 SAN Switch 4/32 (32

active ports) SAN Switch 4/32 (16

active ports)

B-Series MSA SAN Switch 2/8

(embedded) SAN Switch 2/8V SAN Switch 2/16 SAN Switch 2/16V SAN Switch 2/16N SAN Switch 2/8V (with

zero e-ports and with full fabric)

SAN Switch 4/16

HP Procurve 6108 HP Procurve 5308xl HP Procurve 5372xl HP Procurve 3400cl -24G HP Procurve 3400cl-48G HP Procurve 4160gl HP Procurve 4140gl HP Procurve 2848 HP Procurve 2824

M-Series Director 2/140 Director 2/64 Edge Switch 2/32 Edge Switch 2/24 Edge Switch 2/12

M-Series Edge Switch 2/32 Edge Switch 2/24 Edge Switch 2/12

Supported switches (FC switches for MSA1000 and MSA1500cs; 1Gb Ethernet switches for the MSA1510i)

C-Series MDS 9506 Director MDS 9509 Director MDS 9216 MDS 9216A MDS 9216i MDS 9120 MDS 9140

C-Series MDS 9506 Director MDS 9509 Director MDS 9216 MDS 9216A MDS 9216i MDS 9120 MDS 9140



Learning check 1. Which of the three systems discussed in this module contains an integrated

controller and disk drive enclosure? …………………………………………………………………………………………..

2. The MSA1000 can be expanded by the addition of a maximum of________ drive enclosures, for a maximum disk capacity of ________ disks.

3. Complete the statements below:

a. The MSA1000 connects to ______________________________ networks.

b. The MSA1500cs connects to _____________________________ networks.

c. The MSA1510i connects to _______________________________ networks.

4. Identify the type of disk drive supported by the MSA20 and MSA30 disk enclosures and the maximum number of disks supported by each enclosure. ……………………………………………………………………………………………………………………………………………………………………………………

5. What component of the MSA1500cs and MSA1510i limits the way SCSI and SATA disk enclosures can be mixed on those systems? ……………………………………………………………………………………….....

6. The MSA1510i supports only which operating systems? …………………………………………………………………………………………..

7. All three systems discussed in this module support RAID 6. Describe RAID 6 and its advantages. ……………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………


Hardware Components Module 3

Introduction The hardware components module discusses, in some detail, the hardware comprising each of the three MSA array systems covered in this training course. Some of the components are common to each of the systems and will be discussed only once. References to those discussions will be made as required.

The systems will be discussed in the following order:

MSA1000

MSA1500cs

MSA1510i

Discussions will include descriptions of the components and any indicators associated with the components.

There will be no detailed discussion of the MSA30 and MSA20 drive enclosures or disk drives in this module. Modules 6 and 7 of this course are dedicated to those components.



Objectives After completing this module, students should be able to:

Identify the hardware components of each of the three systems

Describe the commonalities and differences between the three systems

Locate and explain the functions of the various components

Describe the possible configurations for the MSA products

Hardware Components


MSA1000 components Call outs in the graphic below identify the components on the front of the MSA1000 array storage system.

Primary controller

Redundant controller

Liquid crystaldisplay

Display controlbuttons

Status LEDsRJ-45

serial port

4U rackheight

14 Universal 1” SCSI drives

MSA1000 – Front view

The MSA1000 integrates an MSA1000 controller enclosure with an MSA30 dual-bus SCSI drive enclosure. The controller portion of the system will be discussed in this module, but the details of the MSA30 drive enclosure will be covered in Module 6.

The controller directs traffic between the SAN and the storage array. The use of redundant controllers enhances system availability but requires a Fibre I/O interconnect module for the second controller and multipathing software.

The Liquid Crystal Display provides the user with information on controller status and system faults. The display is also used, in conjunction with the four pushbuttons, to enter commands and configure the system.

The indicator LEDs provide status and activity information to the user. Details appear later in this module.

The RJ-45Z serial port provides a means for the user to implement commands and configuration actions using Command Line Interface (CLI).



Enclosure status indicators on the MSA1000 Three enclosure status indicators are located on the front panel of the MSA1000.

Enclosure status indicators

! WARNING The system power in the MSA1000 does not shut off completely with the power switch. STANDBY removes power from most of the electronics and the drives, but portions of the power supply and some internal circuitry remain active. To remove power completely, disconnect all power cords from the equipment.

Number Indicator Condition Meaning

Blinking Green EMU is operating normally. 1 EMU Off or On without

blinking EMU is not operating normally.

Green System power is on. 2 Power

Off System in STANDBY or system power has been removed.

Amber Fault detected in one or more subsystems. 3 Fault

Off No faults detected.

Hardware Components


Rear view

2Gb single port I/O module

Redundant I/O cover

Redundant, Hot PlugPower Supplies & Fans

SCSI I/O &EMU Module

SCSI Connections forEnclosure Expansion

Top LED is 1GbBottom LED is 2Gb

2Gb single port I/O module

Redundant I/O cover

Redundant, Hot PlugPower Supplies & Fans

SCSI I/O &EMU Module

SCSI Connections forEnclosure Expansion

Top LED is 1GbBottom LED is 2Gb

MSA1000 – Rear view

(Single controller with I/O module)

The back of the basic MSA1000 is shown above. Components include:

A single-port 2Gb Fibre Channel I/O module with one Small Form-Factor Pluggable (SFP) transceiver

One integrated SCSI I/O and Environmental Monitoring Unit (EMU) module

Redundant power supplies

Redundant fans (one fan mounted on each power supply chassis)

Space for a second interconnect module, which is required if a second controller is installed.



The following photo shows the back of the MSA1000 with an optional MSA Fabric Switch 6 module. Although the MSA Fabric Switch 6 is no longer available, it is still supported by HP. Other optional interconnect devices will be discussed later.

Primary 2Gb Fabric Switch

Redundant 2Gb Fabric Switch

Multi-modeFibre Channel

Cabling

Redundant, Hot Plug Power Supplies & Fans

SCSI I/O & EMU Module

SCSI Connections for Enclosure Expansion

Primary 2Gb Fabric SwitchRedundant 2Gb Fabric Switch

Multi-modeFibre Channel

Cabling

Redundant, Hot Plug Power Supplies & Fans

SCSI I/O & EMU Module

SCSI Connections for Enclosure Expansion

MSA1000 – Rear view (Redundant controllers with redundant MSA Fabric Switch 6s installed)

Hardware Components


Hot-pluggable components Assuming redundant components reside in the system, hot-pluggable components allow a user to remove and replace components without powering down the system. Because of airflow considerations, HP recommends that a replacement part or appropriate blanking panel be available when a component is removed.

The components listed below are hot-pluggable in the MSA1000.

MSA1000 controller — If your system has two controllers, is in a multibus configuration, and one controller fails, you can remove and replace the failed controller without shutting down the system.

Fibre Channel I/O modules — The Fibre Channel I/O module is a single-port, 2Gb Fibre Channel device that includes a 2Gb SW Small Form-Factor Pluggable (SFP) transceiver. This module can be removed and replaced with other interconnects. Refer to the MSA1000 User Guide for specific limitations when replacing hot-pluggable components.

Power supplies — The redundant power supplies share the power load equally. Failure of one power supply results in the other assuming the full power load. A redundant power supply allows you to remove a power supply and replace it without interrupting system operation. Failure of a power supply does not necessarily mean the loss of the fan mounted on that power supply.

Caution Removing a power supply or any other component significantly changes the airflow within the MSA products. The system will shut down in approximately five minutes if the removed component is not replaced or a blanking panel is not inserted.

Cooling fans — The redundant fans share the cooling load. If one fan operates too slowly or fails, the other automatically operates at a higher speed. A failed fan can be removed and replaced while the system is running.

SCSI disk drives ⎯ The SCSI disk drives can be removed and replaced as necessary. Drives should be removed and replaced one at a time or blanks should be placed in the drive bay if a drive is not replaced.



MSA1000 controller Discussion of the controller addresses the following topics:

Controller display

Controller indicators (LEDs)

Battery-backed cache (Array Accelerator)

Controller firmware

Controller display The controller liquid crystal display is used for displaying informational and error messages, showing the status of the module, and providing user input, when required. Traditional Power-On-Self-Test (POST) messages issued by PCI-based array controllers were combined with runtime event notification messages to create a new set of controller display messages. A complete listing of the new messages is found in the Modular Smart Array 1000 Controller User Guide, part number 347281-002.

Control of the display is exercised through the use of four buttons located to the right of the LCD display. The buttons are used to scroll through messages, delete messages, and to make entries, as needed.

MSA1000 controller LCD

Controller display Description

1 Fault indicator (amber) 2 Display area 3 Left push button 4 Up push button 5 Right push button 6 Down push button 7 Redundancy link indicator (green)

Hardware Components


MSA controller indicators During normal runtime, the MSA1000 controller has 18 indicators that indicate activity or malfunction of the controller. Although each indicator is important, the key indicators to look for are numbers 8 (Idle heartbeat), 9 (Active/Standby), 16 (Redundancy activity), and 17 (Fault). A table explaining each indicator follows the graphic.

MSA1000 indicators

Indicator Function Description

0-2 Busy status

These three LEDs are used to progressively represent the processing load on the controller. On – The controller is idle. Off – The controller is operating at full capacity.

3-7 Fibre Channel ID Indicates the 5-bit Arbitrated Loop Physical Address (AL-PA) assigned to this array controller (not valid when in the fabric mode).

8 Idle heartbeat Indicates the controller is idle and functioning.

9 Active/Standby On – Controller is active. Off – Controller is in standby.

10 Direct Memory Access (DMA) active On – DMA transfers are active.

11 Logical I/O activity On – Currently processing logical requests from the host adapter.

12 SCSI Port A (SCSI Bus 2) On – Indicates requests are outstanding on the first SCSI Bus.

13 SCSI Port B (SCSI Bus 3) On – Indicates requests are outstanding on the second SCSI Bus.

14 Cache activity On – Cache active. Off – No cache activity. Blinking – Cache transfer pending.

15 Drive failure On – A configured hard drive has failed in the array.

16 Redundancy active Green indicates two controllers are in a redundant mode of operation.

17 Fault Amber indicates an error message has been sent to the controller display.



Array Accelerator (battery-backed cache) The Array Accelerator is a high-performance, upgradeable 256MB SDRAM DIMM read/write battery-backed cache. The controller comes with one Array Accelerator installed and a vacant slot available for insertion of a second, optional accelerator, giving a total of 512MB capacity.

Primary ArrayAccelerator

Slot for optionalsecond Array Accelerator

MSA1000 controller with primary Array Accelerator and slot for optional accelerator

The Array Accelerator performs protected posted-write caching and read-ahead caching, allowing data to be accessed much faster than from disk storage. In protected posted-write caching, data is written to the cache memory on the Array Accelerator rather than directly to the drives. The controller is then able to optimize writes to the drives.

The read-ahead cache detects sequential accesses to the array, reads ahead data, and stores the data in the cache until the next read access arrives. If the data is of a sequential nature, the data can be loaded immediately into memory, avoiding the latency of a disk access.

If the MSA1000 controller fails before cached data is stored on the disk, the Array Accelerator and its integrated batteries can be removed from one controller and be installed in a replacement controller. Any data in the Array Accelerator that has not been written to the hard drive will be transferred to the replacement controller.

Hardware Components


Other features of the Array Accelerator include:

Mounted on a removable daughterboard (allows stored data to be moved to another controller if the original controller fails)

Backed up with replaceable batteries

Adjustable read/write ratio (usually set during array configuration, but can be changed at any time)

16-bit Error Checking and Correcting (ECC) SDRAM memory

Array Accelerator batteries The Array Accelerator has two rechargeable and replaceable Nickel Metal Hydride (NiMH) battery packs. Under normal operating conditions, the batteries should last for three years before replacement is necessary. They are continuously recharged using a “trickle” charging process whenever the storage system is powered on.

The battery pack protects data on the Array Accelerator against equipment failure or power outage for up to four continuous days.

Note Temperature, age, and cache size can affect battery life.

The batteries on a new controller might be discharged when the board is first installed. In this case, a POST message displays on the controller display panel when the controller is powered on, indicating that the Array Accelerator is temporarily disabled. No action is required. The internal circuitry automatically recharges the batteries. Recharging takes about four hours. The controller functions properly during that time, although without the performance advantage of the Array Accelerator write cache functionality. When the batteries are charged to 90 percent of their capacity, the Array Accelerator is automatically enabled.

When operating with redundant controllers, both must have identical cache configurations.

Refer to the Modular Smart Array 1000 Controller User Guide for cache battery removal and replacement procedures.



Controller firmware Each MSA1000 controller contains Read-Only Memory (ROM) that holds the firmware that operates the controller. When operating in a redundant controller configuration, both controllers must be using the same firmware version.

Should the controller firmware become corrupted, there are two methods for recovery, one for intra-controller recovery and one for recovery between controllers in a redundant configuration.

Automatic firmware recovery The intra-controller recovery method is referred to as automatic firmware recovery.

Two firmware images are stored in the ROM of each controller:

Active image

Backup image

Each time the system is powered on or restarted, the active and backup images are checked to ensure they are valid. If one image is not valid, the valid image is automatically copied over the invalid image. This function is automatic and requires no user intervention.

Redundant-controller firmware cloning The recovery method used between controllers in a redundant configuration is referred to as firmware cloning.

Each time a system with two controllers is powered on, restarted, or if a second controller is hot-plugged in a single-controller configuration, the firmware versions on the controllers are compared.

When a controller is added to a running system with an active controller, if the firmware versions are not the same, the system prompts to clone the firmware from the active controller onto the standby controller, regardless of the firmware level of either controller. The prompt CLONE FIRMWARE ? ‘<’ = NO, ‘>’ = YES appears on the non-active controller. If a “No” response is entered or a response is not made to the prompt within 60 seconds, the firmware is not cloned and the standby controller will not come on line. The system operates from the active controller in a non-redundant mode until the firmware on both controllers is the same.

Hardware Components


If a system is powered on with two controllers using different firmware revisions, the controller with the highest firmware revision becomes the active controller. The system prompts to clone the firmware from the active controller onto the standby controller. The prompt CLONE FIRMWARE ? ‘<’ =NO, ‘>” = YES appears on the non-active controller. If a “NO” response is entered, or a response is not made to the prompt within 60 seconds, the firmware is not cloned and the standby controller will not come online. The system operates from the active controller in a non-redundant mode until the firmware on both controllers is the same.

If a “Yes” response is entered, the following messages are displayed while the controller is updated and automatically restarted:

ROM CLONING STARTED

ARRAY CONTROLLER RESTARTING

MSA1X00 STARTUP COMPLETE

The controllers should now operate in the redundant mode.

Note Cloning is not possible in single-controller configurations.

Controller firmware updates

Controller firmware updates and installation instructions are available on the HP web site.

For the MSA1000, obtain controller firmware from the “Software, Firmware, & Drivers” page of the MSA1000 web site at www.hp.com/go/msa1000.

To determine the firmware currently in use, do one of the following:

On the controller LCD panel, use the arrow keys to scroll backwards through the messages until the “ARRAY CONTROLLER FIRMWARE VER <version>” message displays. Each time the controller is restarted, the first message displayed includes the firmware version.

In the CLI, use the SHOW VERSION command.

In the ACU, highlight the controller and view the details.



MSA1000 interconnect devices The standard interconnect device shipped with the MSA1000 storage array is the 2Gb single-port Fibre Channel I/O module. Available options are the MSA SAN Switch 2/8 and the MSA Hub 2/3. All three devices support 1Gb and 2Gb SAN infrastructures and are embedded in the back of the controller enclosure.

Note Although the MSA Fabric Switch 6 is still supported by HP, it is no longer available and will not be discussed in this section.

Fibre Channel I/O module

The Fibre Channel I/O module is a single-port, 2Gb device that includes a 2Gb/s Small Form-Factor Pluggable (SFP) transceiver port. It can auto-negotiate its speed to support either 1Gb or 2Gb networks, depending on the SAN infrastructure to which it is connected.

The SFP port has two LEDs associated with it. If the top LED is lit, the port is operating at 1Gb/s. If the bottom LED is lit, the port is operating at 2Gb/s.

Fibre Channel I/O module

This module can be removed and replaced with other interconnect devices. In redundant controller configurations, however, the interconnect devices must be of the same type.

Hardware Components


MSA SAN Switch 2/8 The MSA SAN Switch 2/8 is an optional 2Gb integrated 8-port fabric switch that enables full duplex nonblocking performance on all ports. One port is used internally for interface with the controller and seven ports are available for external use. The switch is shipped with four SFP transceivers. If additional transceivers are required, they must be ordered separately.

Each external port has two LEDs associated with it. If the left light is lit, the port is operating at 1Gb/s. If the right light is lit, the port is operating at 2Gb/s.

The MSA SAN Switch 2/8 also has an RJ-45 10BaseT Ethernet port and an RS-232 serial port for interface with configuration and management applications.

MSA SAN Switch 2/8

If using this switch in a redundant controller configuration, a second MSA SAN Switch 2/8 must be ordered and installed, as both interconnect devices in a redundant configuration must be of the same type.



MSA Hub 2/3 The MSA Hub 2/3 is an optional 2Gb interconnect device designed to provide an inexpensive way for a clustered pair of servers to access the storage controller (using the arbitrated loop configuration) without having to buy an external hub or switch. The hub has three ports. One of the ports is for internal interface with the controller and two SFP ports are available for external interface.

Each external port has two LEDs associated with it. The top LED, when lit, indicates the port is operating at 1Gb/s. The bottom LED, when lit, indicates the port is operating at 2Gb/s.

As with the other devices, if the hub is used in a redundant configuration, the second device must also be a hub.

MSA Hub 2/3

Hardware Components


Integrated Environmental Monitoring Unit (EMU)/SCSI I/O module

The integrated EMU/SCSI I/O module performs several functions, including monitoring the enclosure operation, detecting and indicating errors, displaying enclosure status, and providing an interface with optional MSA30 drive enclosures.

Integrated EMU/SCSI I/O module

Environmental Monitoring Unit functions include:

Monitoring power supply voltages

Monitoring power supply and enclosure temperatures

Monitoring the presence and status of hard drives

Detecting and reporting element changes in the enclosure and showing the addition or removal of a hot-pluggable component

Controlling drive status indicators



The module has three LEDs. The location of the LEDs and their meanings are provided below.

EMU/SCSI I/O LEDs


Solid green Power on 1 Power Off Power off/fault Green/flashing On/activity

2 SCSI Port A Off Off Green/flashing On/activity

3 SCSI Port B Off Off

Hardware Components


Power supply/blower assembly The MSA1000 has two identical power supply/blower assemblies. A photo of the assembly is shown below.

Power supply/blower assembly

The MSA1000 is equipped with primary and redundant power supplies and attached variable-speed blowers. The power supplies are hot-pluggable and share the electrical load equally. If one power supply fails or is removed, the other power supply assumes the full electrical load without interruption. In addition, if one of the cooling blowers in the assembly operates too slowly or fails, the other blower automatically operates at a higher speed. A failed blower can be removed and replaced without removing the power supply.

An LED on the left side of the blower housing indicates the status of the assembly. A green light indicates both the power supply and blower are operating properly. When a power supply or blower fault occurs, the power supply indicator goes off. A fault message is sent to the LCD display on the controller.



Fibre Channel cables Hewlett-Packard branded fiber optic cables must be used with the MSA1000. Shortwave, multimode cables with shortwave SFPs should be used and are capable of supporting distances of 2 to 500 meters. Various cable kits are available from HP. Refer to the system QuickSpecs for cable kit and part number information. Kits include one cable with a connector at each end.

While longwave SFPs and 9μm single-mode Fibre Channel cables can be used, performance might not be optimal due to transmission latencies.

Maximum cable lengths depend on the speed of data transmission. Maximum cable lengths are:

1Gb/s – 500m

2Gb/s – 300m

Hardware Components


MSA1500cs components The MSA1500cs components, seen from the front view, include the MSA1000 controller (and a redundant controller, if installed) and the power switch and status indicator panel (upper right on photo). The front view photo below does have the optional second controller installed.

MSA1500 cs front view

Power and status indicators panel The power switch and status indicators are located in the upper right portion on the front of the MSA1500cs.

1 2 3 411 22 33 44 MSA1500cs power and status indicator panel

Number Function Description

1 Unit ID button

On – Lights blue indicating the unit is being identified. The light illuminates for 30 seconds, then goes out. Off – Normal

2 System fault indicator On − Lights amber when fan module cannot access controllers Off − Normal

3 Heartbeat status LED Flashing green − The fans are accessing the controllers Off − Power off or fault exists

4 Power

On − Lights green indicating power is on Off − Lights amber indicating power is off



! WARNING The system power in the MSA1500cs does not shut off completely with the power switch. STANDBY removes power from most of the electronics and the drives, but portions of the power supply and some internal circuitry remain active. To remove power completely, disconnect all power cords from the equipment.

The back view of the MSA1500cs is shown below. The left-most slot remains blank in all configurations.

Fans Powersupplies

FC I/OModules

SCSI I/OModules

Blank FansFans PowersuppliesPowersupplies

FC I/OModulesFC I/OModules

SCSI I/OModulesSCSI I/OModules

BlankBlank

MSA1500 cs back view

In a fully populated MSA1500cs, slots are allocated from left to right as follows:

Slot 1 – Blank

Slot 2 – Single-port Fibre Channel I/O module

Slots 3 and 4 – Dual SCSI ports for connectivity to storage enclosures

Slots 5 and 6 – Redundant fan units

Slot 7 – Single-port Fibre Channel I/O module (redundant configurations)

Slots 8 and 9 – Dual SCSI ports for connectivity to storage enclosures

Slots 10 and 11 – Redundant power supplies

Above the fan units is a slot diagram indicating the use for each slot and a second unit ID indicator.

MSA1500cs slot diagram

Hardware Components


Hot-pluggable components The hot-pluggable components within the MSA1500cs are:

Controller (in redundant configurations)

Fibre Channel I/O module (in redundant configurations)

Fans

Power supplies

Disk drives in attached disk enclosures, though not technically part of the MSA1500cs system, are also hot-pluggable.

Controller Physically, the controller is the same as that found in the MSA1000. The earlier descriptions of the controller (including display, battery-backed cache, and batteries) and its indicators apply to the MSA1500cs also.

Although the firmware versions between the two systems are different, the automatic firmware recovery, firmware cloning, and firmware download processes are the same in both systems. To obtain firmware for the MSA1500cs, go to the “Software, Firmware & Drivers” page of the MSA1500cs web site at www.hp.com/go/msa1500cs.



Fibre Channel I/O module The Fibre Channel I/O module is a single-port, 2Gb interconnect device with an SFP transceiver port. The module auto-negotiates the port speed (1Gb/s or 2Gb/s) based on the infrastructure to which it is attached. For redundant configurations, a second I/O module is required.

MSA1500cs Fibre Channel I/O module

The I/O module has three bi-color (green or amber) LEDs used to indicate status, as explained below.

Fibre Channel I/O module LEDs


Solid green Power on 1 Status Flashing amber A link to the controller is no longer present Solid green Port has auto-negotiated to a good 1Gb link

2 1G Flashing amber Transceiver is either not plugged in or a link is no longer present Solid green Port has auto-negotiated to a good 2Gb link

3 2G Flashing amber Transceiver is either not plugged in or a link is no longer present

Note: Two flashing amber lights indicate that the controller is not present.

Hardware Components


SCSI I/O module Each SCSI I/O module has two Ultra320 ports on it. The right port is designated port A and the left port is port B. The module also has three status LEDs.

12

3

12

3

SCSI I/O module

Number Function LED color Status 1 Power Green Power is on to the SCSI module

Green On 2 SCSI Bus A

Flashing green Activity through the module Green On

3 SCSI Bus B Flashing green Activity through the module



In a fully populated MSA1500cs, there are four SCSI I/O modules. They are, from right to left, designated Bus 0 through Bus 3, as shown below.

Bus0

Bus1

Bus2

Bus3

Bus0

Bus1

Bus0

Bus1

Bus2

Bus3

Bus2

Bus3

SCSI Bus numbering

As mentioned earlier in this training, each dual-channel SCSI I/O module supports one MSA30 SCSI drive enclosure or up to two MSA20 SATA drive enclosures. A SCSI enclosure cannot be mixed on the same I/O module with a SATA enclosure.

When connecting four MSA30 enclosures, plug the cable into port A of each module, starting at Bus 0 and moving to the left. SCSI connections are allowed only on port A.

When connecting four MSA20 enclosures, plug the cable into the A port of each module, starting at Bus 0 and moving to the left. If attaching more than four MSA20 enclosures, plug the fifth unit into port B of Bus 0, the sixth unit into port B of Bus 1, and so on. This concept is shown in table form below. While this is the suggested order for the MSA20s, it is fine to plug them in using a different order. SCSI bus Port SCSI enclosure number SATA enclosure number

A 1 1 0 B Not supported 5 A 2 2

1 B Not supported 6 A 3 3

2 B Not supported 7 A 4 4

3 B Not supported 8

The SATA enclosure number listed for each port above shows up on the LCD display on the back of the MSA20.

Hardware Components


The possible configurations for the use of MSA30 and MSA20 drive enclosures with the MSA1500cs are:

Four MSA30 SCSI enclosures

Eight MSA20 SATA enclosures

One MSA30 and six MSA20 enclosures

Two MSA30 and four MSA20 enclosures

Three MSA30 and two MSA20 enclosures



MSA1500cs cooling fans The MSA1500cs ships with redundant cooling fans located in the back of the enclosure. Each fan has a single, bi-color LED status indicator.

LEDLED

MSA1500cs redundant cooling fans

The LED indications are shown below.

LED color Status Steady green Operational Flashing amber Fault detected

A fan assembly from the MSA15OOcs is shown below.

MSA1500cs cooling fan

Hardware Components


The fans share the cooling load within the MSA1500cs. If one fan runs too slowly or stops altogether, the remaining fan increases its speed to provide the required cooling for the enclosure. A failed fan can be replaced without interrupting operation of the unit.

Removal of the fan assembly for longer than 5 minutes can cause airflow problems within the MSA1500cs, so HP recommends having the replacement unit immediately available.



Power supply The MSA1500cs is shipped with redundant power supplies located in the back of the enclosure. The power supply has a single, bi-color status LED.

LEDLED

MSA1500cs power supplies

The LED indications are explained below.

LED color Status Steady green Operational Flashing amber Fault detected

A photo of a power supply unit is shown below, removed from the enclosure.

MSA1500cs power supply unit

Hardware Components


The redundant power supplies share the power load for the MSA1500cs. If one unit fails or is removed, the other power supply assumes the full electrical load. The units are hot-pluggable and a failed unit can be removed and replaced without interrupting MSA operations.

Removal of the power supply for longer than 5 minutes can cause airflow problems within the MSA1500cs, so HP recommends having the replacement unit immediately available.



MSA1510i components Physically, the MSA1510i and the MSA1500cs are identical from the front. See the MSA1500cs section for detailed information on the components visible in the front view and the indicators located there. The controller labeling will state “Modular Smart Array 1510i”

MSA1510i front view

The rear view of the MSA1510i is also identical to the MSA1500cs, with one exception. The interconnect module is a two-port, 1Gb Ethernet iSCSI module providing interfaces to an IP network rather than a Fibre Channel network. The rear view of the MSA1510i, with the Ethernet interconnect module is shown below.

MSA1510i with redundant controllers and I/O modules – rear view

Number Description 1 Ethernet iSCSI module for controller A, physical port 0 2 Ethernet iSCSI module for controller A, physical port 1 3 Ethernet iSCSI module for controller B, physical port 0 4 Ethernet iSCSI module for controller B, physical port 1

Hardware Components


Controller, SCSI I/O module, fans, and power supplies The discussions in the “MSA1500cs components” section of this module apply to the MSA1510i for these components. Controller firmware updates are available on the Software, Firmware & Drivers page of the MSA1510i web site: http://h18006.www1.hp.com/products/storageworks/msa1510i.

Ethernet iSCSI I/O module The Ethernet iSCSI I/O module has two 1Gb Ethernet ports, one LED to indicate status of the module, and two LEDs for each port to indicate port status and activity. The controller enclosure is shipped with one Ethernet I/O module. A second module is required for a redundant system.

The locations of the LEDs are shown below.

MSA1510i Ethernet I/O module LEDs

The I/O module status indicators are defined in the following table.


Solid green Module is powered on and operational and communication to the controller is established

Blinking amber Communication to the controller is lost or the module is faulty 1 Status

Off Power is off, the module is faulty, or the controller is faulty or not present

Solid green Linked to the network in either 1000Mb/s or 100Mb/s mode (at initial release, only the 1000Mb/s mode is supported) 2 Status

Off No linkage to the network Blinking Linked and activity on the network

3 Activity` Off No network activity



Cables Only Category 5e (or better) Ethernet cables should be used for network connectivity to the MSA1510i.

Drive enclosure configurations The configurations for the use of MSA30 and MSA20 with the MSA1510i are identical with those of the MSA1500cs.

Hardware Components


MSA1000 sample configurations The following diagrams show the MSA1000 in a direct-connect configuration and Fibre Channel network configurations. These diagrams are representative and do not include all possible configurations.

Direct-connect configuration The MSA1000 can be connected directly to a server. The figure below illustrates the most basic configuration of connecting one server directly to the Fibre Channel I/O module.

Fibre Channel I/O module directly connected to a server

MSA30 enclosure

MSA30 enclosure



You can also connect an external SAN switch to the Fibre Channel I/O module. The figure below illustrates multiple servers and multiple MSA1000s connected to a SAN switch in a non-redundant configuration.

Fibre Channel I/O module connected to an external switch, non-redundant configuration

MSA30 enclosure

MSA30 enclosure

Hardware Components


In redundant configurations connected to an external SAN switch, two MSA1000 controllers, two Fibre Channel I/O modules, two SAN switches, and two HBAs in each server are required. The figure below illustrates the redundant configuration of two external SAN switches connected to the Fibre Channel I/O modules.

Fibre Channel I/O module connected to an external san switch, redundant configuration

MSA30 enclosure

MSA30 enclosure



Embedded MSA Fabric Switch 6 configurations The figure below illustrates the MSA Fabric Switch 6 installed in a non-redundant configuration.

MSA Fabric Switch 6, non-redundant configuration

MSA30 enclosure

MSA30 enclosure

Hardware Components


The figure below illustrates the MSA Fabric Switch 6 installed in a redundant configuration.

MSA Fabric Switch 6, redundant configuration

MSA30 enclosure

MSA30 enclosure



Embedded MSA Hub 2/3 configurations Another possible configuration includes using the MSA Hub 2/3 to connect two servers to the storage. The figure below illustrates the MSA Hub 2/3 installed in a redundant configuration.

MSA Hub 2/3 connected to two servers, redundant configuration

MSA30 enclosure

MSA30 enclosure

Hardware Components


MSA1500cs sample configurations The diagrams below show the MSA1500cs in both a non-redundant configuration and a redundant configuration. In each diagram, the MSA1500cs is connected to MSA20 SATA drive enclosures. The attached drive enclosures could just as well be MSA30s or a combination of the two.

MSA1500cs non-redundant configuration

MSA1500cs redundant configuration



MSA1510i sample configurations The diagrams below show both non-redundant and redundant configurations. The diagrams show MSA20 attached storage but could just as well show MSA30 enclosures or a mix of the two.

MSA1510i in a non-redundant configuration

Number Description 1 Server 2 Ethernet network switch 3 MSA1510i 4 Storage enclosure (MSA20) 5 Ethernet cables 6 SCSI cable

Connection to the server is made through 1000BaseT Ethernet network interface cards (NICs), also called gigabit server adapters. HBAs are not used with 1510i. The NICs uses a static IP addressing scheme.

Hardware Components


The diagram below contains the elements from the previous diagram plus the elements required to create a redundant configuration. The table following the diagram describes only the elements added to make the configuration redundant.

MSA1510i in a redundant configuration

Number Description 1 Redundant Ethernet network switch 2 Redundant Ethernet iSCSI module 3 Redundant cabling path



Learning Check 1. What is the maximum number of Fibre Channel I/O modules supported on the

MSA1500 cs?

.................................................................................................................

2. What is the maximum number of drive enclosures supported when utilizing MSA30s attached to an MSA1500cs?

.................................................................................................................

3. In an MSA1500cs or MSA1510i system supporting eight MSA20 SATA drive enclosures, what is the recommended connection order by enclosure number, bus, and port?

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

4. What type of cable is required for MSA1510i connectivity to an external SAN switch?

.................................................................................................................

.................................................................................................................

5. List all possible MSA20/MSA30 configurations when fully populating the four SCSI I/O modules of the MSA1500cs or MSA1510i.

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

6. What information does LED number 8 on the MSA1000 controller provide?

.................................................................................................................


MSA1000 and MSA1500cs Management Utilities

Module 4

Introduction The Management Utilities module discusses the various applications used to configure, manage, and monitor the MSA1000 and MSA1500cs array systems. These utilities include:

Array Configuration Utility (ACU)

Command Line Interface (CLI) - MSA 1510i uses a different CLI

Array Diagnostic Utility (ADU)

Systems Insight Manager (SIM)

MSA SAN Management Tools

Secure Path and native multipathing software

Discussions in this module will be limited to a description of the utilities available for use with the MSA1000 and MSA1500cs array systems, their purpose, and any special requirements or restrictions applicable to them. Procedural information is contained in the lab exercises associated with this module. Specifically, there are labs to cover the use of ACU and CLI.



Objectives After completing this module, and its associated lab exercises, you should be able to:

Describe the management and configuration utilities provided with or supported by the MSA array systems

Explain the use of the HP Systems Insight Manager utility with the MSA arrays

Explain the various multipathing options available with the MSA array systems

Use ACU to configure the MSA1000 and MSA1500cs systems

Use CLI to configure controllers and view settings

Describe the use of management tools for the MSA SAN



Array Configuration Utility Overview The Array Configuration Utility (ACU) is a host-resident, browser-based disk configuration utility used to view, set up, and configure Smart array controllers. Both the MSA1000 and MSA1500cs support ACU. The utility has different operating modes that allow faster configuration or greater control over configuration options. The ACU is available for the following operating systems:

Windows NT (MSA1000 only), Windows 2000, and Windows 2003

Linux

NetWare (offline)

Features and Benefits ACU features and benefits include:

Allows Web-based host and remote configurations.

Provides different operating modes for faster configuration.

• Local Application Mode – Runs as an application on the local machine only and cannot be controlled remotely. This mode does not use a web server, and authentication is accomplished through the operating system rather than through management agents. (Available on Windows OSs only.)

• Remote Service Mode – Runs as a Windows service. It starts automatically and runs in the background continuously. ACU is accessible remotely from the System Management Homepage at https://<hostname>:2381.

Provides a Wizard-based interface for configuring simple systems.

Suggests the optimum configuration for an unconfigured system.

Provides on-screen tips for individual steps of a configuration procedure.

Allows online spares to be assigned.

Allows online array capacity expansion, logical drive capacity extension, and RAID or stripe size migration.

Allows experienced users to have broad control over controller configuration.

Contains its own Command Line Interface capability.



Basic procedure for using ACU The basic steps for using ACU are:

1. Open ACU.

2. Select the controller you want to configure.

3. If using a GUI, select the configuration mode.

4. Configure the controller.

5. Save the configuration.

6. Select another controller to configure or exit ACU

Screen Layout The appearance of a typical ACU screen depends on which of the three possible configuration modes you choose.

Standard mode – This is the default setting. This mode enables you to manually configure all options on the controller.

Configuration Wizards mode – The wizard guides you through each step of a manual configuration process.

Express Configuration mode – Enables ACU to automatically configure the controller after the user answers a few simple questions. ACU uses your answers to determine the optimum default values that it should use for certain configuration options.



The typical Standard Mode screen The Standard Mode screen, the default screen, has three sections:

Device list (left side)

Configuration View (center)

Task list (right side)

All the task options for a selected item in the Configuration View panel are displayed in a frame on the right side of the screen.

ACU Standard Mode screen



The typical Configuration Wizard Mode screen The Configuration Wizard Mode screen has four sections.

Device list (left side) The Device list shows all the identifiable controllers connected to the system.

Configuration View (top center) The Configuration View panel shows all arrays, logical drives, unused space, and unassigned physical drives connected to the selected controller. The logical configuration view is shown by default.

Main menu (bottom center) The Main Menu shows the allowable options.

Frequently Asked Questions (FAQ) (right side) The FAQ column lists information and tips that are relevant to the current screen. Check this region before clicking Help in the upper right corner of the browser screen.

Typical Configuration Wizard Mode screen

The Express Configuration Mode screen Express Configuration mode screens are similar in appearance to Configuration Wizard mode screens, but the directive text is different. In Express Configuration mode, ACU asks a few simple questions about your configuration preferences, then automatically sets up the optimum configuration based on your answers.



Background information on array storage systems Before going further, we will stop to define some of the terms and processes behind the operation of smart array systems. The discussion includes information on the following topics:

Arrays

Spare disks

Logical drives

RAID levels

Expansion

Extension

Array migration

Stripe size migration

Selective Storage Presentation (SSP)

Arrays Hard drives are installed in drive enclosures attached to the MSA controller. The enclosures can be integrated (MSA1000 has one integrated enclosure) or external (the MSA1500cs and MSA1510i systems are connected to external enclosures). Drives within the enclosures can be designated as part of an array, and multiple arrays can be created within an enclosure or between enclosures. Array capacity equals the total capacity of all the drives in the array. One or more virtual drives can be created within the array storage capacity. (Virtual drives will be discussed separately.)

Arrays are created by designating drives through use of a configuration or management utility. Refer to the appropriate utility documentation for procedures for creating arrays.

Drives within an enclosure, and therefore, within an array should be of the same size and type. Mixing drive sizes causes inefficient use of storage space because the MSA controller uses space on a disk equal to that of the smallest drive in the enclosure or array. For example, if you mix drives of 72GB and 300GB, only 72GB of capacity on each 300GB drive will be used, leaving a large amount of system capacity unused and inaccessible. This reduces storage efficiency and increases cost per unit of storage.



Spare drives A spare drive is an extra, empty disk within an enclosure that is not an active member of any particular storage unit. It can be designated as a spare for one or more arrays. Spare drives should be of the same size and type as the other disks within the enclosure. Spares are designated using configuration or management utility applications.

If a spare is present and a physical hard drive fails, the spare automatically replaces the failed drive as a member of the logical storage unit. The process of rebuilding the information onto the spare begins automatically. The system uses the mirrored or parity information from the other member disks to reconstruct the data onto the spare drive. However, in the unlikely event that another drive in the array fails while data is being rewritten to the spare, the logical drive will still fail.

HP recommends including enough hard drives in your enclosures to allow some of the drives to be used as spares.

Logical drives When a storage system is initially configured, the physical hard drives are grouped into one or more arrays. The available space within an array can be divided into logical segments called logical drive units. Depending on your needs and storage capacity, the physical hard drives can be grouped into as many as 32 logical drives.

When planning your logical drives, consider the number of hard drives to include. As a general rule, the greater the number of drives in a logical drive, the greater the performance level that can be achieved. However, the performance considerations are offset by fault tolerance consideration–the greater the number of drives in a logical drive, the higher the probability of one or more disk failures in that logical drive.

When planning the best way to configure your storage, determine the importance of fault tolerance, I/O performance, and storage efficiency needed for the type of data that will be stored on each logical drive. Some configuration methods offer greater fault tolerance, while other configurations methods offer better I/O performance or storage efficiency.

Two configuration tools are available to meet your requirements: striping and the use of Redundant Array of Independent Disks (RAID) levels. Striping will be discussed in this section and RAID levels in the next section.



Striping

Striping refers to the physical location of the hard drives that are included in a logical drive unit. Two types of striping are available.

Vertical striping – Includes hard drives from separate storage enclosures and across different SCSI buses. Vertical striping offers good fault tolerance and performance, but at the price of storage efficiency. Efficiency is degraded by the extra time it takes for reads/writes to be requested or written to multiple enclosures and buses.

Horizontal striping – Includes hard drives contained within the same storage enclosure. Horizontal striping allows for the creation of large logical drives and efficient use of storage capacity, but at the price of I/O performance and slightly less fault tolerance.

RAID levels Fault tolerance can be built into your array system by designating a RAID level for a logical drive unit. A different RAID level can be assigned to each logical drive unit within an array. The five RAID levels are explained below.

RAID 0

RAID 0 is striping only, with no fault tolerance built into the logical drive. If one physical drive within the logical drive fails, data is lost without the ability to recover it. A minimum of one hard drive is required to create a RAID 0 logical drive.

A RAID 0 logical drive is useful for rapid storage of large amounts of non-critical data or when cost is the most important consideration.

Advantages and disadvantages are:

Advantages

• Highest performance method for writes

• Lowest cost per unit of data stored

• All drive capacity is used to store data; none is needed for fault tolerance

Disadvantages

• All data on the logical drive is lost if a physical drive fails

• Cannot use an online spare

• Can preserve data only by backing it up to external drives



RAID 1

RAID 1 configurations contain only two drives. In this configuration, data is duplicated to a second drive. In each mirrored pair, the physical drive that is not busy answering other requests answers any read request sent to the array (called load balancing). If a physical drive fails, the remaining drive in the mirrored pair can provide all necessary data. Several drives in the array can fail without incurring data loss, as long as no two failed drives belong to the same mirrored pair. A minimum of two drives is required for RAID 1.

This fault-tolerance method is useful when high performance and data protection are more important than the cost of physical drives.


Advantages

• Highest read and write performance of any fault-tolerant configuration

• No loss of data as long as no failed drive is mirrored to another failed drive (up to half of the physical drives in the array can fail)

Disadvantages

• Expensive (many drives needed for fault tolerance)

• Only half of total drive capacity is usable for data storage

RAID 1+0

When a RAID 1 array has more than two physical drives, it is referred to as RAID 1+0. In this configuration, the data blocks are striped across half of the drives in the array and then the drives are mirrored in pairs. A minimum of four drives is required for RAID 1+0.

Advantages and disadvantages are the same as for RAID 1.

RAID 5, also known as Distributed Data Guarding

In RAID 5 a block of parity data is calculated for each stripe from the data that is in all other blocks within the stripe. The blocks of parity data are distributed over every physical drive within the logical drive. When a physical drive fails, data that was on the failed drive can be calculated from the user data on the remaining drives and the parity data. This recovered data is usually written to an online spare in a process called a rebuild. This RAID level requires a minimum of three drives.

This configuration is useful when cost, performance, and data availability are equally important.



Advantages and disadvantages of this level are:

Advantages

• High read performance

• No loss of data if one physical drive fails

• More drive capacity is usable than with RAID 1+0 – parity information requires only the storage equivalent of one physical drive

Disadvantages

• Relatively low write performance

• Loss of data if a second drive fails before data from the first failed drive is rebuilt

RAID 6, also known as Advanced Data Guarding (ADG)

RAID 6 is similar to RAID 5 in that parity information is generated to protect against data loss caused by drive failure. With RAID 6, however, two different sets of parity data are used, allowing data to still be preserved if two drives fail. Each set of parity data uses up a capacity equivalent to that of one of the member drives. This level requires a minimum of four drives.

This method is most useful when data loss is unacceptable, but cost must also be minimized. The probability that data loss will occur when arrays are configured in RAID 6 is less than when they are configured in RAID 5.


Advantages

• High read performance

• High data availability–any two drives can fail without loss of critical data

• More drive capacity is usable than with RAID 1+0 – parity information requires the equivalent of two drives

Disadvantages

• Relatively low write performance because of the need for two sets of parity data



The following table summarizes the RAID levels and their characteristics.

RAID level Alternative name I/O performance

Fault tolerance Storage efficiency

RAID 0 Data striping Highest None Highest RAID 1

RAID 1+0

Drive mirroring

Drive striping plus drive mirroring

High* Highest* Low

RAID 5 Data striping, with one set of distributed parity data

Medium Medium High

RAID 6 Data striping, with two sets of distributed parity data

Low High Medium

* When the drives are striped across separate enclosures on different SCSI buses. * 2 drives

Expansion

Expansion is the addition of physical space to an array. Expansion can be accomplished by upgrading drive sizes in the array or by adding one or more blank drives to the array. The added drive or drives must be the same size or larger than those existing in the array.

When the additional space is added, data in the array is automatically redistributed across the array. The expansion process takes about 15 minutes per gigabyte, or considerably longer if the controller does not have battery-backed cache. While array expansion is taking place, not other expansion, extension, or migration can occur simultaneously on the same controller.

The additional space can be used to:

Create new logical drives

Migrate the RAID level or stripe size of existing logical drives

Extend existing logical drives on the array, if the operating system allows logical drive extension

Expansion is accomplished using a supported configuration or management utility.



Extension Extension increases the storage capacity of a logical drive by adding unused space on an array to a logical drive on the same array. The unused space is obtained either by array expansion or by deleting another logical drive on the same array.

Not all operating systems support online logical drive extension through ACU. Also, offline logical drive extension is possible for some operating systems by backing up data, reconfiguring the array, and restoring data from backup. Check operating system documentation for current information.

The extension process takes about 15 minutes per gigabyte, or considerably longer if the controller does not have a battery-backed cache. While logical drive extension is taking place, no other expansion, extension, or migration can occur simultaneously on the same controller.

Extension is accomplished using a supported configuration or management utility.

Array migration Array migration refers to the Direct Attached Storage (DAS) to SAN (DtS) feature common to all three MSA1XXX storage systems. That feature provides a quick and easy way to migrate stored data protected by Smart Array and RA4100 controllers to an MSA1XXX system.

Using a step-by-step procedure, the user simply removes the drives from the older system and inserts them into the MSA1XXX. Existing data, RAID sets, and configuration information remains intact allowing data migration to be completed in minutes, not hours.

Key features and benefits of DtS are:

Instant consolidation of DAS into a SAN environment

Creation of an upgrade path from Smart Array and RA4100 controlled drives and data to a SAN environment



When migrating an array, it is recommended that you record the current configuration of all arrays and note which drives are part of each array prior to performing the migration. If you need to revert to your former configuration, you will be required to re-enter all array and volume information.

The procedure will work with multiple vendor hosts. Refer to the compatibility matrix for your specific MSA system for details on multi-vendor x86 platform support and for operating system versions that support DtS.

More information can be obtained from HP StorageWorks Modular SAN Array 1000 – DtS Data Migration to the MSA1000. That document lists requirements and step-by-step instructions.

Stripe size migration Stripe size migration allows the user to alter the stripe size (data block size) or RAID level, or both, for a selected logical drive. Depending on the initial block size or RAID level and the new block size or RAID level, there might be a need for available unused space on the array for migration to be possible. If space beyond that available on the logical drive is needed, the user would have to extend the logical drive before migrating to a new block size or RAID level.

The migration process takes about 15 minutes per gigabyte, or considerably longer if the controller does not have a battery-backed cache. While stripe size migration is taking place, no other expansion, extension, or migration can occur simultaneously on the same controller.

Stripe size migration is accomplished using a supported configuration or management utility.

Selective Storage Presentation (SSP) Selective Storage Presentation lets the user designate which hosts have access to which logical drives. This is accomplished by specifying which HBA on a host has access to which connections to a logical drive. This process is used to prevent data corruption that might occur when servers using different operating systems access the same data. The Command Line Interface uses an Access Control List (ACL) to maintain the list of LUNs a server can access.

SSP is implemented using the ACU, CLI, or SMU utility.

Note For detailed ACL commands, refer to the Modular Smart Array 1000/1500cs Command Line Interface User Guide and the Modular Smart Array 1510i Command Line Interface User Guide.



Command Line Interface The Command Line Interface (CLI) is built into the firmware of the MSA1000 and MSA1500cs array systems and can be used to configure, manage, and monitor all aspects of the systems. It is a general-purpose ASCII line interface separated by hard returns.

Note The CLI uses a zero-based numbering system. For example, LUN number assignments begin with 0.

The CLI is accessed through a host computer connected to the serial port of the MSA1000 controllers.

Configuration and management tasks include configuring storage units (LUNs), setting the addressing mode, limiting access to storage, and viewing information on MSA components (controller, unit, and cache).

After accessing the interface, the user enters a command string at the CLI prompt (CLI>). Commands are presented using specific, preset syntax. After a declarative command is entered and executed, the results are displayed at the CLI prompt.

In redundant MSA configurations, the same firmware image is run on both controllers. The two controllers communicate with each other through a PCI bus called the inter-controller link (ICL). Each controller has a serial port; and therefore, each controller has a CLI available to the users who connect the serial port to a serial terminal. Controllers in a redundant configuration are referred to as “this_controller” (the controller connected by the serial cable to the host) and “other_controller.”

Some CLI commands are entered from one controller’s CLI prompt, but are for the other controller to execute. Command syntax instructs the controller to accept user input, passes the command to the other controller, and displays the execution result. Commands specifically applicable to the controllers contain the this_controller or other_controller parameter.

Some CLI commands need both of the controllers to act. For example, the command that sets the controller addressing mode is entered at one controller’s CLI prompt, but the other controller needs to set the addressing mode as well. Any CLI command that involves the other controller is called an inter-controller command.

For detailed syntax instructions and CLI command strings, refer to the Modular Smart Array 1000/1500cs Command Line Interface User Guide.



Active/active CLI commands There are four active/active-specific CLI commands.

Setting the preferred path This command allows you to specify the controller to which you want requests for the indicated LUN or LUNs to be sent. Syntax for the command is: set preferred_path {controller | reset} <unit_list> Specifying reset restores the last explicitly configured path for the specified LUN or LUNs.

Showing the preferred path This command generates a display of current controller/LUN assignments. Both explicit and implicit path information is displayed. Syntax for the command is: show preferred_path.

Setting automatic controller path switching This command allows the user to enable or disable automatic path switching and to assign parameters to govern the conditions under which paths will be switched. Syntax for the command is: set auto_path_change {enable | disable} {PRP=#} {MNR=#} {TWP=#} {TWL=#} Proxied Request Percentage (PRP) specifies the minimum percentage of proxied requests required to trigger implicit path change. Minimum Number of Requests (MNR) specifies the minimum number of requests that must be issued to a LUN before path changes are enabled. Time to Wait at Power-up (TWP) specifies the minimum number of minutes (0-255) to wait at power-up before changing LUN ownership. Time to Wait between Ownership Changes for LUN (TWL) specifies the minimum number of minutes (0-255) to wait before changing LUN ownership again for the same unit.

Viewing automatic controller path switching This command generates a display showing automatic controller path switching information. Syntax for the command is: show auto_path_change.



Array Diagnostics Utility The Array Diagnostics Utility (ADU) collects information about the array controllers in the system and generates a list of potential problems it has identified. It produces a report that can be saved to a diskette and analyzed by support technicians to aid in problem resolution.

The ADU is a bootable utility on the system support CD provided with the MSA1000 and MSA1500cs arrays.

Performance Monitoring and HP Systems Insight Manager

HP Systems Insight Manager can be used to monitor the performance of several MSA1000 controller parameters. The displayed parameters include CPU usage, the total number of processed read and write commands, and the average time to process a read or write command. For each logical drive, the total I/O count, number of read/write requests, and number of sectors read or written to are displayed. Use HP Systems Insight Manager to monitor the performance of your drive arrays. HP Systems Insight Manager can also detect failed drives, locally or remotely, across a network. Windows, NetWare, and Linux operating systems are supported.



MSA SAN Management Tools Switch Management Utility

To manage a switch using a browser:

1. Ensure that your browser is configured according to the switch user guide.

2. Point the browser at the switch and log in.

3. Enter public for the read community and private for the write community.

Note The user name and password are case sensitive:

• User Name: user • Password: ADMIN



After a successful login, the GUI displays and enables you to perform various management functions. The GUI also enables you to update the firmware and monitor the switch for error conditions.



Brocade Web Tools

Brocade Web Tools enables the central administration of all the switches in a fabric. This is a standard option with all HP SAN switches.

Using a browser (Netscape 4.0 or later or Internet Explorer 5.0 or later) enables you to point at the IP address of one of the switches in the fabric.

Note A new GUI will be introduced when the firmware 2.2 or greater is supported.



Web Tools views

Web Tools provides access to and information about the fabric through a number of separate windows, making it possible to view several aspects of the fabric simultaneously.

The initial display after launching Web Tools is the Fabric View that displays a control panel. This panel provides access to fabric-wide options, a panel for each switch in the fabric, plus a legend that explains the meaning of the background colors on the Switch icons.

Each panel contains an icon that represents the switch itself, in addition to icons for Switch Events and the Administrative and Telnet interfaces. The background color of the switch icon represents the status of that particular switch or Integrated Fabric (as defined by the legend provided in the window).

Note Switch status is calculated approximately once per second. However, the initial calculation does not occur until 30 to 60 seconds after the switch is booted. It is calculated from the state of data structures in the switch, and stored as the variable “Switch Status.”



Web Tools capabilities Web Tools provides the following information and capabilities:

Monitoring and managing the entire fabric:

• Status of all switches in the fabric

• Event log for entire fabric access

• Zoning functions (optionally licensed)

• Name Server Table access

• Telnet functions

• Switch beaconing for rapid identification in large fabric environments

• Loop diagnostics, query and control of the loop, interface to aid in locating faulty devices

• Ability to name and zone QuickLoops

Monitoring and managing individual switches:

• Summary information about each switch

• Event logs for individual switch access

• Switch configuration and administration

• Ability to upgrade the fabric operating system and license key administration

• Report capability for switch configuration information

Monitoring and managing individual ports:

• Port status

• Information about gigabit interface converter (GBIC) serial IDs

• Information about connected devices

• Loop information

• Port performance including frame counts (frames in, frames out) and error counts



Multipathing applications/drivers There are three methods of creating multipath solutions supported by the MSA array systems: using HP Secure Path, using Microsoft MPIO drivers, and using QLogic drivers. Each will be discussed briefly.

Secure Path Secure Path is a multipath, high-availability software that manages and maintains continuous data access to HP storage systems, enabling no-single-point-of-failure (NSPoF) from server to storage. Secure Path is host-resident software that monitors the data paths between server and storage to increase availability of information. In the event that a path failure is detected, Secure Path fails over to an alternative path. When that path becomes available, Secure Path can automatically fail back to the original path.

Refer to the supported hardware and software tables in Module 2 of this course for Secure Path versions applicable to the supported operating systems.

Features Secure Path provides the following features:

Allows StorageWorks dual-controller RAID systems and host servers, equipped with multiple HBAs, redundant physical connectivity along Fibre Channel arbitrated loop (FC-AL) or Fibre Channel switched fabric (FC-SW) paths.

Monitors each path and automatically reroutes I/O to a functioning alternate path if an HBA, cable, hub, switch, or controller failure occurs.

Determines the “health” of available storage units and physical paths through the implementation of path verification diagnostics.

Monitors and identifies failed paths and failed-over storage units.

Automatically restores failed-over storage units to repaired paths with autofailback capability enabled.

Implements antithrash filters to prevent failover/failback effects caused by marginal or intermittent conditions.

Detects failures reliably without inducing false or unnecessary failovers.

Implements failover/failback actions transparently without disrupting applications.

Provides client/server remote management capability and multiple storage system support.



Installation for Windows 2000 Server The following procedure provides an installation overview of the Secure Path 4.0c for Windows. Refer to the StorageWorks for Secure Path 4.0c for Windows Workgroup Edition Installation Guide for detailed installation instructions.

To install Secure Path 4.0c for Windows:

1. Verify that appropriate Service Packs are installed.

2. Create storagesets and provide unit attributes for LUNs.

3. Using Windows Disk Management, configure your basic disk storage as required.

4. Install Solution Software kits and driver upgrades, if necessary.

5. Install Secure Path Server/Manager software and follow the prompts.

6. Shut down and restart the server. The system takes a few seconds to attach the driver to the newly-discovered LUNs.

7. Verify the Windows application event log displays a successful SP agent start event.

8. Reboot.

9. If installing Secure Path on a cluster configuration, repeat steps 1-8 on the second cluster node; then continue with step 10.

10. Install the cluster service:

a. Shut down Node B.

b. Install the cluster service on Node A and restart the system.

c. After the service is running on Node A, start Node B.

d. Install the cluster service on Node B and restart the system.

e. Redistribute disk resources across the cluster nodes.

Installation for NetWare Refer to the HP StorageWorks Secure Path 3.0c for Novell NetWare Workgroup Edition Installation Guide for detailed instructions on installing Secure Path for NetWare.



Secure Path Manager Characteristics of Secure Path Manager (SPM) are outlined in the following paragraphs.

Secure Path Manager Refresh

Secure Path Manager automatically refreshes the display every 90 seconds. If you want to update the displayed information sooner, use the F5 key.

Secure Path Manager Controller Designations

In the SPM display, controller designations are based on manufacturing serial number assigned to each controller. Always reference the controller serial number if you need to associate information in the SPM display with the controller.

Secure Path Manager Heterogeneous GUI

Secure Path Manager includes a universal Secure Path management web-based utility. This utility supports profiles consisting of mixed heterogeneous operating systems.

Presently, the supported operating systems profiles are:

Windows NT 4.0 (MSA1000 only)

Windows 2000

Windows 2003

Novell NetWare

Linux

Depending on the host operating system within the profile, some or all of the features may be available. These include:

Load-balancing (Depending on the hardware configuration, standalone configurations only)

! Important Currently this is unsupported on the MSA1000 and MSA1500cs.

Path verification

Device identification options

Note Device identification options vary between supported systems.



Supported Secure Path Configurations The following list defines operational configuration limits for Secure Path 4.0c for Windows. The effective limit may be less due to Windows storage constraints, storage system type, or interconnect requirements.

A maximum of 128 storage systems shared by a set of hosts (per profile).

A maximum of 128 hosts (20 host limit for MSAs) per set of shared storage systems (per profile).

A maximum of 256 LUNs (32 LUN limit for MSAs) per target (numbered 0-255) with a maximum of two paths per LUN.

Redundant MSA1500cs controllers cannot be shared with nonredundant servers or clusters.

A LUN on an MSA1500cs owned by a Microsoft Windows 2000 or Windows 2003 cluster cannot be shared with standalone servers.

When using fabric switches and implementing more than one cluster on the same SAN Switch infrastructure (that is, multiclusters), zoning must be applied to isolate the clusters from each other, achieving the highest levels of stability. For more information, see the StorageWorks SAN Switch Zoning Reference Guide.

The following list defines operational configuration limits for Secure Path 3.0c for NetWare. The effective limit may be less due to NetWare storage constraints, storage system type, or interconnect requirements.

A maximum of 8 storage systems shared by a set of hosts (per profile).

A maximum of 16 profiles containing a maximum of 16 hosts.

A maximum of 64 LUNs per target (numbered 0-63) with a maximum of 8 paths per LUN.

A maximum of 24 storagesets per subsystem for parallel SCSI configurations.

A maximum of 64 storagesets per subsystem for Fibre Channel configurations.

The following list defines operational configuration limits for Secure Path 3.0c for Linux.

Automatic failover and failback on up to 32 paths per LUN

Support for up to 16 HBAs per host

Manages up to 8 paths per virtual disk



Microsoft Multipath Input/Output The Microsoft Multipath Input/Output (MPIO) driver software supports only Windows operating systems and is supported on all three of the MSA array systems discussed in this training.

The software is integrated into Windows 2000 Server and Windows Server 2003 operating systems. MPIO is designed to monitor the health of system components between hosts and storage – adapters, cables, and switches. Upon detection of a failure of any of those components, MPIO automatically routes data to a functional path to ensure data availability.

MPIO solutions are designed to work in conjunction with device-specific modules (DSM) written by vendors of storage hardware – the MPIO software, by itself, does not form a complete solution. MPIO provides a generic DSM that hardware vendors must adapt to the specifics of their storage devices. This joint solution allows vendors to design hardware solutions that are tightly integrated with the Windows operating systems and enables Microsoft to correctly accommodate the nongeneric characteristics of each vendor’s storage device.

The success of a multipathing solution depends on identifying each device within a network and identifying if multiple paths go to the same device or different devices. MPIO uses standard information obtainable from the hardware itself, such as serial numbers. Since not all vendors assign their devices a unique hardware serial number, Microsoft includes in its sample generic DSM source code a means of deriving one, using other SCSI INQUIRY data. Alternatively, vendor-specific mechanisms can be implemented in the DSM.

MPIO also enhances system performance by performing load balancing when multiple data paths are available. Load balancing is used to maximize throughput between server and storage. Without multipathing software, a server sending I/O requests down several paths might operate with very heavy workloads on some paths while other are underutilized. The MPIO software supports the ability to transparently balance I/O workload without administrator intervention. MPIO determines which paths to a device are in an active state and can be used for load balancing. Each vendor’s load balancing policy is set in the DSM. This policy determines how the I/O requests are actually routed. If the DSM returns a path that is inactive, MPIO initiates the failover process.



MPIO drivers The MPIO driver package consists of three multipath drivers: the port filter driver, the disk-driver replacement, and the bus driver, all of which are implemented in the kernel mode of the operating system. The driver package works in combination with the Plug and Play Manager, the disk class driver, the port driver, the miniport driver, and each vendor DSM to provide full multipathing functionality.

MPIO DSM The MPIO driver package contains generic code for vendors to adapt to their specific hardware device so that usage and performance of the device can be improved. Device-specific information is abstracted and exported to the bus driver and to the disk objects under its control. Each DSM plays a role in a number of critical events, including device-specific initialization, request handling, and error recovery (retrying and failover). There are different versions of the DSM for the MSA1000/MSA1500cs and the MSA1510i. Only the version intended for a particular storage product should be used. Full-featured MPIO is used for active/active configurations, while Basic MPIO is used for active/passive setups.

Device initialization

Each DSM is contacted in turn to determine whether or not it provides support for a specific device. If the DSM does support the device, it indicates whether the device is a new installation or the same device previously installed but which is now visible through a new path.

Request handling

When an application makes an I/O request to a specific device, the DSM makes a determination, based on its internal load balancing algorithm, as to which path the request should be sent. If the I/O request cannot be sent down a path because the path is broken, the DSM shifts to the error handling mode.

Error handling

The DSM determines whether to retry the I/O request or to treat the error as fatal, making failover necessary. In the case of fatal errors, paths are invalidated, and the request is rebuilt and transmitted to a different device path.

DSM management

Management and monitoring of the DSM can be done through an administrative utility. The preferred interface is through the Windows Management Instrumentation (WMI).



QLogic multipathing Drivers within QLogic HBA firmware support multipathing for Linux OSs supported by the MSA1000 and MSA1500cs systems.

QLogic driver v7.0 for HBA control and multipathing supports the following HBAs and Linux OS versions:

HBAs

• FCA2214 IA32

• FCA2214 DC IA32

• A6826A IA64

Linux OSs

• Redhat EL Advanced Server 2.1 (32- and 64-bit) – U3 or latest

• Redhat Advanced Server 3.0 (32- and 64-bit)

• SLES8/UL 1.0 (32- and 64-bit) – SP3 e340 or latest

QLogic driver v8.0 for HBA control and multipathing supports the following HBAs and Linux OS versions:

HBAs

• FCA2214 IA32

• FCA2214 DC IA32

• A6826A IA64

Linux OSs

• Linux Kernel 2.6 and later

• SLES9



Learning check 1. Which ACU configuration mode automatically configures the controller based

on the answers to questions posed to the user?

.................................................................................................................

.................................................................................................................

2. When using CLI to configure, manage, or monitor the array system, commands involving the controllers in a redundant controller system are addressed to “this_controller” and “other_controller.” What determines which controller is “this_controller?”

.................................................................................................................

.................................................................................................................

3. HP Systems Insight Manager (SIM) monitors controller parameters and logical drive activity on the MSA arrays. Which operating systems does SIM support?

.................................................................................................................

.................................................................................................................

4. List three Web Tools capabilities for managing a fabric switch.

.................................................................................................................

.................................................................................................................

.................................................................................................................

5. MPIO provides native multipathing support for which MSA-supported operating systems?

.................................................................................................................

.................................................................................................................

6. Secure Path v3.0c supports which operating systems?

.................................................................................................................

.................................................................................................................


MSA1510i Management Utilities

Module 5

Introduction The Management Utilities module discusses the various applications used to configure, manage, and monitor the MSA1510i array system. These utilities include:

Command Line Interface (CLI) - MSA1000,1500cs use a different CLI

Storage Management Utility (SMU)

Systems Insight Manager (SIM)

MPIO multipathing software

Discussions in this module will be limited to a description of the utilities available for use with the MSA1510i array system, its purpose, and any special requirements or restrictions applicable to it. Procedural information is contained in the lab exercises associated with this module. Specifically, there are labs to cover the use of CLI and SMU.



Objectives After completing this module, and its associated lab exercises, you should be able to:

Describe the management and configuration utilities provided with or supported by the MSA1510i array system

Explain the use of the HP Systems Insight Manager utility with the MSA1510i

Explain the multipathing available with the MSA1510i system

Use CLI to configure controllers and view settings

Use SMU to configure the MSA1510i system



Command Line Interface The Command Line Interface (CLI) is built into the firmware of the MSA1510i array system and can be used to configure, manage, and monitor all aspects of the systems. It is a general-purpose ASCII line interface separated by hard returns.

The CLI is accessed through a host computer connected to the serial port of the MSA1510i controllers. In addition, the CLI can be accessed via hyperterminal or telnet connection over IP to the management port of the MSA1510i (MA0/MB0). The management port can be any physical port.

Configuration and management tasks include configuring storage units (LUNs), setting the addressing mode, limiting access to storage, and viewing information on MSA components (controller, unit, and cache).

After accessing the interface, the user enters a command string at the CLI prompt (CLI>). Commands are presented using specific, preset syntax. After a declarative command is entered and executed, the results are displayed at the CLI prompt.

In redundant MSA configurations, the same firmware image is run on both controllers. The two controllers communicate with each other through a PCI bus called the inter-controller link (ICL). Each controller has a serial port; and therefore, each controller has a CLI available to the users who connect the serial port to a serial terminal. Controllers in a redundant configuration are referred to as “this_controller” (the controller connected by the serial cable to the host) and “other_controller.”

Some CLI commands are entered from one controller’s CLI prompt, but are for the other controller to execute. Command syntax instructs the controller to accept user input, passes the command to the other controller, and displays the execution result. Commands specifically applicable to the controllers contain the this_controller or other_controller parameter.

Some CLI commands need both of the controllers to act. For example, the command that sets the controller addressing mode is entered at one controller’s CLI prompt, but the other controller needs to set the addressing mode as well. Any CLI command that involves the other controller is called an inter-controller command.

For detailed syntax instructions and CLI command strings, refer to the Modular Smart Array 1510i Command Line Interface user guide.



Background on TCP/IP, NAS, and ISCSI Before discussing the Storage Management Utility, we will look at some background on new concepts being introduced into the MSA world with the introduction of the MSA1510i controller.

TCP/IP Transmission Control Protocol /Internet Protocol (TCP/IP) is a networking protocol that provides communication across interconnected networks between computers with diverse hardware architectures and various operating systems. Its popularity is based on:

Robust client-server framework, excellent for use in WAN environments

Information sharing among diverse organizations and services

General availability with most computer and storage manufacturing companies providing support in their product lines

TCP

TCP is a connection-oriented protocol. It establishes a connection between two systems that intend to exchange data. When an application sends a message to TCP for transmission, it is broken down into chunks of data called packets. To allow the receiver to reconstruct the message, each packet is numbered sequentially.

The receiver needs to be able to not only reconstruct the message, but must be able to verify the accuracy of the data. To accomplish this verification, the sender uses a formula to calculate a checksum for the message. The recipient does the same calculation and if the checksums match, the message is acknowledged. If the checksums differ, the receiver requests a resend. TCP also uses port IDs to specify which application running on the system is sending or receiving the data.

The sequence number, checksum, and port ID are grouped in the packet in a special section called the header. The header appears in the beginning of each packet and is used to reconstruct the message in proper order and verify the information as valid.



IP

IP is the messenger protocol of TCP/IP. It basically addresses and sends packets. IP relies on three pieces of information, which the user provides, to receive and deliver packets: IP address, subnet mask, and the default gateway.

The IP address identifies your system on the network. IP addresses are 32-bit addresses that are globally unique on a network. They are generally represented in dotted decimal notation, which separates the four bytes of the address with periods. An IP address looks like this: 102.54.94.97. Although an IP address is a single value, it contains two pieces fo information: (a) your system’s network ID, and (b) your system’s host (or system) ID.

The subnet mask, also expressed in dotted decimal notation, is used to extract these two values from your IP address. The value of the subnet mask is determined by setting the network ID bits of the IP address to ones and the host ID bits to zeroes. The result allows TCP/IP to determine the host and network IDs of the local workstation. For example, when the IP address is 102.54.94.97 and the subnet mask is 255.255.0.0, the network ID is 102.54 and the host ID is 94.97.

NAS Network Attached Storage (NAS) was developed by Sun Microsystems. It presents storage to a host over an IP network. Although similar in concept to iSCSI, NAS presents storage at the file system layer, whereas iSCSI presents storage at the block layer.

Raw block accessFile system

Operating system

Storage

NAS iSCSI

Raw block accessRaw block accessFile systemFile system

Operating systemOperating system

StorageStorage

NAS iSCSI

NAS versus iSCSI layers

NAS has well-defined file sharing and locking mechanisms, making it an excellent solution for storage shared among many hosts.



iSCSI iSCSI works on a TCP/IP rather than a Fibre Channel network. SCSI commands, from either an application or a file system, are sent to a SCSI class driver which converts the commands into Command Descriptor Blocks (CDBs). The CDBs are then carried to an iSCSI driver, which encapsulates them into Protocol Data Units (PDUs) and passes them to the TCP/IP protocol stack for delivery. This process is depicted graphically below.

SCSI Class Driver

iSCSI Driver

TCP/IP protocol stack

File System Application

CDBs

PDUs

SCSI Class DriverSCSI Class Driver

iSCSI DriveriSCSI Driver

TCP/IP protocol stackTCP/IP protocol stack

File SystemFile System ApplicationApplication

CDBs

PDUs

iSCSI data flow from source to TCP/IP protocol stack

The ISCSI data is then mapped in the host in the manner shown below.

Application or File System

SCSI Commands

iSCSI Protocol

TCP Protocol

IP Protocol

Ethernet (Gigabit Ethernet) Framing

Category 5e Cable Infrastructure

iSCSI data flow from source to system cabling



There are many advantages to iSCSI over Fibre Channel. Some of those advantages are listed below.

IP is the most widely used and accepted networking protocol

Highly developed extended services

• Routing

• Authentication

• Security

• Multicasting

• Hierarchical structure

Cost effective development of NICs versus HBAs

Cost effective deployment of single-protocol switches and routers

Management utilities are well developed

Ethernet has a higher line rate

Ethernet has expanded frame size

Greatly expanded reach of storage networking (deployed in desktops and laptops as well as in data centers)



Storage Management Utility The Storage Management Utility (SMU) is internal to the controller firmware and supports array configuration and management activities on the MSA1510i system. It enables array expansion, logical drive extension, spare drive assignment, and RAID or stripe size migration

SMU features Features of the SMU are:

It works online, meaning its use does not interfere with storage operations

It is accessed from a remote server or workstation using a browser

It is username and password protected

It includes all the capabilities of the ACU

It provides two ways to configure the system, including management of ISCI targets, ports, and portal groups

• An initial configuration wizard

• A user interface for more detailed configuration actions

SMU requirements There are some display and software restrictions for the use of SMU.

Minimum display setting

• 1024 x 768 pixel resolution

• 256 colors

Internet Explorer 6.0 or later

JAVA RTE

Be sure to add the SMU IP address to your browser’s Trusted Sites in Security.



SMU best practices There are a number of things the user can do to make configuration and management of the MSA1510i more effective using the utility.

Get the latest compatibility information, firmware and software downloads, and system documentation from http://www.hp.com/storage.

Follow the procedures outlined in the installation documentation.

Record system configuration information on the checklists and worksheets provided in system documentation. The information will be required for:

• Configuring the storage

• Entering connection information

• Setting up multipathing

• Making future configuration changes

• Referencing current configuration information

• Troubleshooting

Sign up with Support Communications for email notification and alerts about your system.

Provide separate physical LANs or create Virtual LANs (VLANs) to segment the traffic.

Ensure initiators (host/server) and targets (hosted by SMU) are on the same Layer 2 Ethernet LAN. This guarantees the integrity of data traffic and maintains high network performance levels.

Ensure availability of storage by providing redundant power supplies and data paths and by creating fault-tolerant logical storage units.

Assign system names and aliases using only the following characters:

• Uppercase alpha characters (A-Z)

• Lowercase alpha characters (a-z)

• Numeric characters (0-9)

• Special characters (!#=()’;,. and space)

Expand the browser to full screen or a minimum of 1024 x 768 pixels. Using other settings might distort the display or cause items not to be displayed.



When planning and configuring logical drives:

• Stripe drives in the array across separate storage enclosures on different SCSI buses to optimize performance and redundancy, especially when using RAID 1+0.

• Set the drive rebuild priority to high to minimize exposure during a drive failure.

• Customize the RAID level and striping method to the type of data stored on the logical drive.

After configuring storage, remember to:

• Verify that each initiator is granted access to the target

• Control access to the storage using VLANS, CHAP authentication, or Access Control Lists (ACLs) (Selective Storage Presentation)

Draw physical and logical diagrams of your network

• Hardware/device diagram (network physical layout, including device names and cabling)

• Storage diagram (hard drive and storage system configuration, including RAID levels)

• Path/accessibility diagram (access information, including which devices are allowed to communicate with each other)



Introduction to iSCSI network terms and concepts Before going into the configuration of a system using SMU, it would be good to discuss some of the terms used in iSCSI networks and the concept of Ethernet iSCSI management and data ports.

Network terms Some basic terms need to be understood before discussing the configuration of systems.

Initiator − A server on the iSCSI network

Array – A grouping of physical hard drives

Logical drive – A logical segment using space from the array. The MSA1510i supports up to 32 logical drives per array.

Mapped logical drive – A logical drive that is assigned to a target. As logical drives are mapped to a target, they are assigned a number.

Target – A target is a logical grouping of one or more logical drives (mapped logical drives). The target is the unit presented to the network, with the initiator granted access to a specific target (and its assigned LUNs). Each target may have multiple logical drives, but each logical drive can be mapped to but one target.

Portal – A combination of IP address and port number assigned to a physical port. Each physical port may have multiple portals assigned.

Portal Group – A group of portals assigned to a target through which that target may be accessed.

Iqn – An iSCSI qualified name—syntax:

• Iqn.(date of root dns registration).(reverse dns name)



The following graphic and table illustrate the concept.

Legend

= Target

Mapped= Logical

Drive

= LogicalDrive

= SATAarray

Legend

= Target

Mapped= Logical

Drive

= LogicalDrive

= SATAarray

Legend

= Target

Mapped= Logical

Drive

= LogicalDrive

= SATAarray

13 Target 3

12 Target 211 Target 1

When Logical Drive 3 was mapped to this target (Target 3), it was renamed Mapped Logical Drive 1.10 Mapped Logical Drive 1



Uses all space from Array C, with RAID 5 fault tolerance.7 Logical Drive 3

Uses all space from Array B, with RAID 5 fault tolerance.6 Logical Drive 2

Uses all space from Array A, with RAID 1+0 fault tolerance.5 Logical Drive 1

Uses hard drives from bays 8, 9, and 10, with bay 12 as a spare.4 Array C

Uses hard drives from bays 5, 6, and 7, with bay 11 as a spare.3 Array B

Uses hard drives from bays 1,2,3 and 4.2 Array A

Sample includes one array controller with one 2-port Ethernet iSCSI module, with 12 SATA hard drives in the storage enclosure.

1 MSA1510i controllerand MSA20 storage enclosure

DescriptionItem

13 Target 3

12 Target 211 Target 1




Uses all space from Array C, with RAID 5 fault tolerance.7 Logical Drive 3

Uses all space from Array B, with RAID 5 fault tolerance.6 Logical Drive 2

Uses all space from Array A, with RAID 1+0 fault tolerance.5 Logical Drive 1

Uses hard drives from bays 8, 9, and 10, with bay 12 as a spare.4 Array C

Uses hard drives from bays 5, 6, and 7, with bay 11 as a spare.3 Array B

Uses hard drives from bays 1,2,3 and 4.2 Array A

Sample includes one array controller with one 2-port Ethernet iSCSI module, with 12 SATA hard drives in the storage enclosure.

1 MSA1510i controllerand MSA20 storage enclosure

DescriptionItem



Ethernet iSCSI management and data ports The array controller connects to the IP network switch from its Ethernet iSCSI module. In a redundant configuration, an additional Ethernet iSCSI module provides connections to a separate network switch. The following graphic illustrates the Ethernet iSCSI ports on an MSA1510i.

Ethernet iSCSI module physical ports

Port names Each physical port is comprised of one or more logical ports, with a name derived from the physical port number and type of traffic the port is designed to carry. By default, each port on an Ethernet iSCSI module has two logical names to carry both management traffic and iSCSI storage traffic. HP recommends isolating management traffic from iSCSI storage traffic by assigning each logical port an IP address on different subnets.

The following table shows port names.

1 = Port 1 (bottom)1 = Port 1 (bottom)0 = Port 0 (top)0 = Port 0 (top)

B = Controller BB = Controller BB = Controller BB = Controller B

S = Storage dataM = Management dataS = Storage dataM = Management data

Port SB1Port MB1Port SB0Port MB0

Physical port 1Physical port 0

Ethernet iSCSI module for controller B


A = Controller AA = Controller AA = Controller AA = Controller A


Port SA1Port MA1Port SA0Port MA0


Ethernet iSCSI module for controller A


B = Controller BB = Controller BB = Controller BB = Controller B


Port SB1Port MB1Port SB0Port MB0


Ethernet iSCSI module for controller B


A = Controller AA = Controller AA = Controller AA = Controller A


Port SA1Port MA1Port SA0Port MA0


Ethernet iSCSI module for controller A



Note Controller firmware supports management from only one management port at a time. HP recommends configuring and using the default management port (MA0).

Note In redundant configurations, install a redundant Ethernet iSCSI module and controller in the MSA, with each module connected to a separate network switch for true path redundancy. Configure the ports on each module.

Portals

Each Ethernet iSCSI module provides two physical connections to the network, but multiple IP addresses and TCP portals can be assigned to each physical port, creating multiple IP pathways.

Keep the following considerations in mind when thinking about ports and portals.

Multiple IP addresses can be assigned to each Ethernet iSCSI physical port

Multiple TCP portals can be assigned to each IP address

Access to the storage and the flow of storage traffic can be controlled by assigning each target to a specific group of portals

The following graphic illustrates these concepts.

Ethernet iSCSI port, with multiple IP addresses and portals



Note The maximum supported number of IP addresses and portals might differ, depending on the array controller. See your system user documentation for more information.

Accessing the SMU Use the following procedure to access the SMU.

1. To obtain the management port IP address, use the controller arrow buttons to scroll to message 603 Port MA0 IP <address> and record the IP address.

2. From a server or workstation with access to the storage device, open a Web browser and enter the IP address obtained in step 1.

Note For additional security (at a reduced performance level), access the SMU using the secure mode (https://).

3. Enter username and password (default username: root; default password: root).

SMU login screen

Note When accessing the SMU for the first time, a window displays requiring input of a user-defined username and password.



SMU Set The Login Password screen

4. Wait for the utility to load. One of the following happens:

• If key components of the system are not configured, a prompt to go to the Wizard tab displays

• If the system is partially configured, the Configure tab displays

• If the system is configured, the Manage tab displays



Choosing an SMU configuration method There are two methods available for configuring a system using the SMU.

The first is the use of the Initial System Configuration Wizard, and the second is the use of the Configuration tab. Use of the configuration wizard is recommended for users unfamiliar with configuring iSCSI networks. Use of the Configuration tab is available for users who are familiar with configuring iSCSI networks and who want greater control and flexibility in configuring their system.

Initial System Configuration Wizard Use of the wizard is the easiest method to configure simple (single-server) systems. It uses setting inputs to configure the storage as an iSCSI target and make it available to the iSCSI initiator (server). The wizard assigns one IP address to each data port, creates one target, and identifies one initiator.

After accessing SMU, the Wizard is accessed by selecting the Wizards tab on the SMU main page.

Wizards tab on SMU main page

Step 1: Welcome When the Wizards tab is selected, the wizard Welcome page displays. The display consists of two parts: a list of steps on the left, and an input screen on the right. Selecting the drop-down arrow on the left portion of the display (indicated by the arrow in the following graphic) generates the list of steps used to configure the system. As each step is selected in the steps list, the appropriate input screen displays on the right.

SMU Wizard Welcome screen



Step 2: Storage Configuration Clicking Next on the Welcome page highlights step 2 on the step list and generates the Storage Configuration input screen.

Storage Configuration page

The wizard suggests a Fault Tolerance (RAID) level unique to each installation, based on the detected number of storage enclosures, enclosure type (SATA or SCSI), number of available hard drives, drive generation, speed, and size.

Depending on the hardware configuration and selected RAID level, an Assign Spare option might be displayed beneath the Fault Tolerance field. Because the system from which the image was taken didn’t have enough disks available to assign a spare, the Assign Spare option was not displayed.

To change either of the settings assigned by the wizard, click the drop-down arrow on the appropriate input field and select a new value from the listed options.

Click Next to move to step 3.



Step 3: iSCSI Configuration In the iSCSI Configuration step, values are entered for one of the I/O module data ports. Once the Initial System Configuration Wizard process is completed on the first data port, configure additional ports using the Configure tab.

iSCSI Configuration page

By default, the wizard recommends configuring Data Port SA0. HP recommends accepting the default value.

Assign an IP address and Subnet Mask for the designated port.

VLANs are set up on the switch and are used as one method of controlling access to the storage. If VLANs are used, enter the VLAN ID to use (0 = not used).

The wizard suggests a default iSCSI Target Name and iSCSI Target Alias. Accept the default or enter user-defined values.

Be sure to enter the iSCSI Initiator Name exactly as assigned in the iSCSI initiator software utility (on the server). Include all special characters, including periods and spaces. If the initiator name is entered incorrectly, the target cannot be presented to the initiator.



Step 4: Redundant iSCSI Configuration In dual-controller configurations, the Redundant iSCSI Configuration page displays for the user to enter settings for a data port on the redundant modules. Again, configure additional data ports using the Configure tab.

Click Next to move to step 5.

Step 5: Logon Settings The Logon Settings page offers the user the opportunity to change access information.

Logon Settings page

To retain current logon settings, click Next to move to step 6.



To change the logon username and password, clear the Use Existing Administrator ID and Password check box. The Logon Settings page expands, with options to change the Admin ID and Password. When completed, click Next to move to step 6.

Expanded Logon Settings page



Step 6: Management Settings The Management Settings page is used to enter settings for the management port.

Management Settings page

The Port State field must show Enabled (default setting) to use the SMU. To re-enable SMU management, you must use a CLI command. For more information, refer to the Modular Smart Array 1510i Command Line Interface user guide.

Assign a name to the storage system in the Host Name field. (The default name is the chassis serial number.)

By default, the wizard suggests configuring Logical Port Name MA0 as the primary management port. HP recommends accepting the default.



To control the path of management traffic to and from the array controller, and to add one level of system security, HP recommends assigning a static IP address to the management port that is in a different subnet than the data ports. To assign a static IP address, expand the DHCP Setting drop-down box and change the setting to Disabled. The page expands (shown above), showing the current IP address. Change the IP address to what you want to use for the management traffic. After changing the IP address, you might have to re-connect to the SMU, using the newly assigned IP address.

VLANs are set up on the switch and are used as one method of controlling access to the storage. If using VLANs, enter the VLAN ID to use (0 = not used).

Click Next to complete the configuration wizard.

After completing all steps of the wizard, a final confirmation window displays.

Initial System Configuration Complete page



Click Finish to apply the configuration settings, Back to change settings, or Cancel to exit the wizard.

If you clicked Finish, wait for the utility to apply your settings. Once settings are applied, you might have to change the IP address of your management client device to be in the same subnet as the address assigned to the management port.

Note Wizards are available for basic configuration tasks only. Use the Manage and Configure tabs to view and change your configuration.

! Important Perform the following tasks to complete the configuration: − Enter security settings (optional, but recommended). − Enter configuration settings in the iSCSI initiator configuration software utility (on the server), including: − Adding target portals for the initiator to access. − Configuring the target portals. (Be sure to select the option to automatically restore the connection each time the system restarts.) − Logging on to establish an active session.



SMU Configure tab The Configure tab allows the user to take more configuration actions than does the Initial System Configuration Wizard. The Configure tab display contains two parts:

A system components list on the left of the display

A task list on the right of the display

SMU Configure tab display

Items appearing in the components list are dependent upon the option selected in the “View as” drop-down box. Items appearing in the task list are dependent upon the component type selected in the component list.

The “View as” drop-down box offers a choice of three views.

Storage with iSCSI view – Displays all system components and their available tasks

Storage view – Displays only storage-related items; no targets or initiators are shown

iSCSI view – Displays only iSCSI-related items; no arrays, logical drives, or hard drives are shown



“View as” field and Show Physical View displays

Clicking the Show Physical View or Show Logical View field (circled) toggles between the two views. The toggle affects the view only when storage components are shown.



Performing SMU tasks There are four basic steps to performing a task using SMU.

Select a component

Select a task

Enter the requested information for the task

Execute the action

A lab exercise associated with this module will cover the Configure tab capabilities in detail.

Available tasks Tasks available for each system component are provided in the following tables. Three tasks, More Information, Refresh System, and View All System Alerts, are common to all components and will not be listed in the tables.

System component Available tasks Create Array Create iSCSI Target Add iSCSI Initiator Array Accelerator Settings Storage System Settings Reset System Clear Configuration Canonical Target CHAP* Settings iSNS+ Discovery Settings

Top-level storage system

Add iSNS Flash Firmware

Controller Disable Standby Controller

TELNET service SSH service HTTP service HTTPS service SNMP service

Service Settings

* CHAP = Challenge Handshake Authentication Protocol + iSNS – Internet Storage Name Service



System component Available tasks

Add IP Address Data port Enable/Disable Port Create Portal

Data port IP address Delete IP Address

Portal Delete Portal Create Logical Drive Spare Management Delete

Unused space

Expand Array Create Logical Drive Spare Management Delete Array

Expand Array Migrate RAID/Stripe Size

Logical drive Extend Logical Drive Create Portal Group Map Logical Drive to Target CHAP Settings Delete Target Enable/Disable Access Control Discovery Settings

Target

Set Login Parameters Assign Portals Delete Portal Group Portal group Remove Portals from Portal Group Unmap Logical Drive from Target

Mapped logical drive Update Access Control Delete iSCSI Initiator

Initiator CHAP Settings



System diagrams Previously it was recommended that diagrams be made of the finished configuration. An example of each of the recommended diagrams follows.

Hardware/device diagram The hardware/device diagram shows the physical components and connectivity of the configuration.

Item Description

1 MSA1510i controller shelf Example includes two array controllers and two 2-port Ethernet iSCSI modules

2 MSA20 SATA storage enclosure Example includes 12 SATA hard drives 3 Primary Ethernet network switch Example supports 1000BaseT functionality 4 Redundant Ethernet network switch Example supports 1000BaseT functionality

5 Initiator A Example includes two 1000BaseT Ethernet NICs and cabling to the two network switches

6 Initiator B Example includes two 1000BaseT Ethernet NICs and cabling to the two network switches

7 Initiator C Example includes two 1000BaseT Ethernet NICs and cabling to the two network switches



Storage diagram The storage diagram shows the arrays, logical drives, mapped logical drives, and targets associated with the configuration.

Legend

= Target

Mapped= Logical

Drive

= LogicalDrive

= SATAarray

Legend

= Target

Mapped= Logical

Drive

= LogicalDrive

= SATAarray

Legend

= Target

Mapped= Logical

Drive

= LogicalDrive

= SATAarray

Item Description 1 MSA1510i and MSA20 storage enclosure

Example includes one array controller and one two-port Ethernet iSCSI modules with 12 SATA hard drives.

2 Array A Uses hard drives from bays 1, 2, 3, and 4. 3 Array B Uses hard drives from bays 5, 6, and 7, with bay 11 as a spare. 4 Array C Uses hard drives from bays 8, 9, and 10, with bay 12 as a spare. 5 Logical Drive 1 Uses all space from Array A with RAID 1+0 fault tolerance. 6 Logical Drive 2 Uses all space from Array B with RAID 5 fault tolerance. 7 Logical Drive 3 Uses all space from Array C with RAID 5 fault tolerance.

8 Mapped Logical Drive 1 When Logical Drive 1 was mapped to this target (Target 1), it was renamed Mapped Logical Drive 1.



11 Target 1 12 Target 2 13 Target 3



Path/accessibility diagram The path accessibility diagram shows what devices are allowed to communicate with each other.

Path/accessibility diagram

Item Port IP address Portals Portal group Target

1 MA0/MB0 10.10.10.254 Not applicable Not applicable Not applicable

2 SA0 10.10.10.10 Portal 1: 3260 Portal 2: 3261

Group 1 Group 3

Target 1 Target 2

3 SA0 10.10.10.11 Portal 3: 3260 Portal 4: 3261

Group 1 Group 3

Target 1 Target 2

4 SA1 10.10.10.50 Portal 5: 3260 Portal 6: 3261

Group 5 Group 5

Target 3 Target 3

5 SA1 10.10.10.51 Portal 7: 3260 Portal 8: 3261

Group 5 Group 5

Target 3 Target 3

6 SB0 10.20.10.10 Portal 9: 3260 Portal 10: 3261

Group 2 Group 4

Target 1 Target 2

7 SB0 10.20.10.11 Portal 11: 3260 Portal 12: 3261

Group 2 Group 4

Target 1 Target 2

8 SB1 10.20.10.50 Portal 13: 3260 Portal 14: 3261

Group 6 Group 6

Target 3 Target 3

9 SB1 10.20.10.51 Portal 15: 3260 Portal 16: 3261

Group 6 Group 6

Target 3 Target 3



Configuring the system This section discusses, in general terms, the configuration of various parts of the system. More detail will be discussed in lab exercises associated with this module.

For detailed instructions on the configuration processes, refer to the HP Storage Management Utility user guide, part number 383075-001.

Configuring management and data ports The controller connects to the network switch from its Ethernet iSCSI module. In dual controller configurations, two modules are required and ports on both modules must be configured.

Consider the following points when configuring management and data ports.

Isolate management traffic from storage traffic by assigning IP addresses in different LAN segments.

Assign one (or more) IP address to each port, then assign one (or more) TCP portal to each IP address.

Enable or disable management services, as needed. The services and their default settings are listed below.

• TELNET (default: disabled)

• SSH (default: enabled)

• HTTP (default: enabled)

• HTTPS (default: enabled)

• SNMP (default: enabled)

Assign IP addresses and TCP portals to data ports in accordance with the Path/accessibility diagram

Note The maximum number of supported IP addresses and portals might differ, depending on the storage system and the controller model. Refer to system user documentation for more information.



Configuring hard drives There are two steps to configuring hard drives: create arrays and create logical drives. Both of these steps are covered in a lab exercise.

There are a number of considerations when configuring hard drives.

The SMU does not support SCSI and SATA enclosures in the same array.

Hard drives in an array should be of the same size and speed.

For best performance, include drives from different enclosures and connected to different SCSI buses on the array controller.

Consider reserving some drives for use as online spares. When using spares, consider the following:

• A spare must be the same type (SCSI or SATA) as other drives in the array.

• A spare should be the same size (or larger) and speed (or faster) as other drives in the array. Using smaller/slower drives reduces performance of the array should the spare become active.

• A hard drive can be assigned as a spare to more than one array.

• If a spare is assigned to an array, the words “with Spare” are included in the array description.

Configuring storage targets Configuring storage targets requires the completion of several steps.

Create the target

Create portals assigned to the physical ports

Create target portal groups

Assign portals (from the same physical port) to the portal group

Map logical drives to the target

Configure the redundant controller, creating a second portal group bound to the target and a portal off of the second controller

A lab exercise will take you through these steps.



Adding authorized initiators (servers) The three steps to adding authorized initiators are:

Select a storage system.

Input required information.

Execute the action.

Factors to consider when adding initiators are listed below.

The iSCSI Initiator Name is assigned when defining the initiator on the server. The format for the Initiator Name is “iqn.xxx.” The name is obtained from either the network administrator or from iSCSi initiator software on the server.

Enter the iSCSI Initiator Name exactly as assigned. Include all special characters, periods, and spaces. Entry of an incorrect name prevents presentation of the target to the initiator.

The system suggests a default value for the iSCSI Initiator Name Alias. The user can accept the default value or provide a user-defined value.

Other tasks There are a number of other management and configuration tasks available using SMU. Refer to the HP Storage Management Utility user guide for the list of tasks and specific procedures.



SMU security Security methods used with SMU can include one or all of the following:

Set up Access Control Lists (ACLs).

Set up Challenge Handshake Authentication Protocol (CHAP) authentication.

Set the Secure Socket Layer (SSL) certificate.

Refer to the HP Storage Management Utility user guide for specific procedures for each method.

Setting up ACLs The purpose of the ACL is to provide security at the target or LUN level. As the name implies, the ACL specifies the initiators having access to specific or all mapped logical drive units of a target, depending on where the ACL is set. The ACL might be set on a target basis or on a LUN basis. If it is at the target level, all LUNs for that target are exposed to the initiators granted ACL access to the target.

There are a number of considerations when setting up ACLs.

To prevent loss of access to storage, do not modify ACLs during an active session between an initiator and target. Before enabling ACL for a target, open the iSCSI initiator software and verify target status as inactive or disconnected.

When access control is disabled (the default setting), all initiators with access to the controller can access the targets.

When access control is enabled, access to all mapped logical drives on a target is immediately blocked. Access is available only after ACLs are created at the target level or for each mapped logical drive.

CHAP authentication Establishing CHAP authentication requires assigning identical passwords (also called secret) to both storage management software and initiator software. When an initiator accesses the target, the passwords are compared. If passwords match, access is granted. If passwords do not match, access is denied.

Three methods of CHAP authentication are available.

Set up storage system target discovery CHAP authentication.

Set up target-specific initiator-to-target CHAP authentication.

Set up mutual CHAP authentication.



Setting the SSL certificate The SSL certificate provides browser security by ensuring a secure connection between the controller and server. The system works by using a private key to encrypt data transferred over the internet.

The MSA1510i controller ships with a default certificate installed and uses Privacy-Enhanced Mail (PEM) formatted files for certificate implementation. PEM is a UNIX format that is not supported by Microsoft Certificate Services. Therefore, HP recommends using the publicly available OpenSSL toolset for generating keys and certificates and for converting Microsoft private key exports into PEM format. For additional information, refer to the HP StorageWorks Modular Smart Array 1510i Advanced Planning and Configuration Guide.



Managing the system using SMU Management actions using the SMU are accomplished from the Manage tab on the SMU main page. Like the Configure tab, the Manage tab contains a list of components on the left of the display and a list of tasks on the right. The components list is populated based on the view selected in the View field above the component list area. There are three view options and three task options. An example of the Manage tab is shown below.

SMU Manage tab display

The three views available on the Manage tab are displayed by clicking on the drop-down arrow in the View field and selecting the desired view.

All Devices – Displays all system components

Devices with Alerts – Displays components for which any type of alert is generated

Devices with Info Alerts – Displays components with informational alerts generated.

The three tasks are:

View Event Log

Refresh System

Identify Device



The first task has a display associated with it. The second and third tasks do not have displays.

The Refresh System task causes the utility to scan the configuration and update information available in the system.

The Identify Device task allows the user to identify a device by illuminating the LEDs on the device. Simply select the device to be identified from the component list and select Identify Device on the task list. For example, to locate the hard drives comprising a logical drive, select the logical drive on the component list and click on Identify Device. The LEDs on all hard drives associated with the logical drive illuminate.

Status alerts are shown as part of the basic Manage tab display. In the example below, there are no status alerts. However, if there was a status alert, it would be shown in the green area below.

Status Alerts display



An example of the display generated by selection of the View Event Log task is shown below.

View Event Log task display



SMU diagnostics The SMU Diagnose tab is used to generate diagnostic information about the array controller.

SMU Diagnose tab display

Clicking the Generate Report button creates a report in a separate window. As needed, use the options available in the report window menu bar to edit or save the diagnostic information to a file. The file can be uploaded to an XML parser that can provide a human-readable document.

SMU diagnostic report



SMU icons The SMU uses a number of icons to represent various components in an iSCSI network. The following tables provide the icons and their meanings.

Icon Meaning

Top-level storage system

Controller – Active

Controller – Standby

Management or data port – Disabled

Management or data port – Enabled

IP address

Portal

Target



Icon Meaning

Mapped logical drive

Portal group

Initiator

Logical drive

Logical drive – Being expanded (animated icon)

Logical drive – Being rebuilt (animated icon)

SATA array

SATA hard drive (blue icon)

SATA hard drive – Spare (green icon)



Icon Meaning

SATA hard drive – Active spare (animated icon) (green icon)

SATA hard drive – Being rebuilt (animated icon) (blue icon)

SATA hard drive – Active spare – Being rebuilt (animated icon) (green icon)

SCSI array

SCSI hard drive (blue icon)

SCSI hard drive – Spare (green icon)

SCSI hard drive – Active spare (animated icon) (green icon)

SCSI hard drive – Being rebuilt (animated icon) (blue icon)



Icon Meaning

SCSI hard drive – Active spare – Being rebuilt (animated icon) (green drive icon)

Status – Critical

Status – Degraded

Status - Okay

Status – Pause/standby

Help

More information is available for this component. View the status alerts.



Performance Monitoring and HP Systems Insight Manager

HP Systems Insight Manager (SIM) can be used to monitor the performance of several MSA1000 and MSA1510i controller parameters. The displayed parameters include CPU usage, the total number of processed read and write commands, and the average time to process a read or write command. For each logical drive, the total I/O count, number of read/write requests, and number of sectors read or written to are displayed. Use HP Systems Insight Manager to monitor the performance of your drive arrays. HP Systems Insight Manager can also detect failed drives, locally or remotely, across a network. Windows, NetWare, and Linux operating systems are supported.



Multipathing application/drivers The MSA1510i uses Microsoft MPIO drivers for multipathing.

Microsoft Multipath Input/Output The Microsoft Multipath Input/Output (MPIO) driver software supports only Windows operating systems and is supported on all three of the MSA array systems discussed in this training.

The software is integrated into Windows 2000 Server and Windows Server 2003 operating systems. MPIO is designed to monitor the health of system components between hosts and storage – adapters, cables, and switches. Upon detection of a failure of any of those components, MPIO automatically routes data to a functional path to ensure data availability.

MPIO solutions are designed to work in conjunction with device-specific modules (DSM) written by vendors of storage hardware – the MPIO software, by itself, does not form a complete solution. MPIO provides a generic DSM that hardware vendors must adapt to the specifics of their storage devices. This joint solution allows vendors to design hardware solutions that are tightly integrated with the Windows operating systems and enables Microsoft to correctly accommodate the nongeneric characteristics of each vendor’s storage device.

The success of a multipathing solution depends on identifying each device within a network and identifying if multiple paths go to the same device or different devices. MPIO uses standard information obtainable from the hardware itself, such as serial numbers. Since not all vendors assign their devices a unique hardware serial number, Microsoft includes in its sample generic DSM source code a means of deriving one, using other SCSI INQUIRY data. Alternatively, vendor-specific mechanisms can be implemented in the DSM.

MPIO also enhances system performance by performing load balancing when multiple data paths are available. Load balancing is used to maximize throughput between server and storage. Without multipathing software, a server sending I/O requests down several paths might operate with very heavy workloads on some paths while other are underutilized. The MPIO software supports the ability to transparently balance I/O workload without administrator intervention. MPIO determines which paths to a device are in an active state and can be used for load balancing. Each vendor’s load balancing policy is set in the DSM. This policy determines how the I/O requests are actually routed. If the DSM returns a path that is inactive, MPIO initiates the failover process.



MPIO drivers The MPIO driver package consists of three multipath drivers: the port filter driver, the disk-driver replacement, and the bus driver, all of which are implemented in the kernel mode of the operating system. The driver package works in combination with the Plug and Play Manager, the disk class driver, the port driver, the miniport driver, and each vendor DSM to provide full multipathing functionality.

MPIO DSM The MPIO driver package contains generic code for vendors to adapt to their specific hardware device so that usage and performance of the device can be improved. Device-specific information is abstracted and exported to the bus driver and to the disk objects under its control. Each DSM plays a role in a number of critical events, including device-specific initialization, request handling, and error recovery (retrying and failover). There are different versions of the DSM for the MSA1000/MSA1500cs and the MSA1510i. Only the version intended for a particular storage product should be used.

Device initialization

Each DSM is contacted in turn to determine whether or not it provides support for a specific device. If the DSM does support the device, it indicates whether the device is a new installation or the same device previously installed but which is now visible through a new path.

Request handling

When an application makes an I/O request to a specific device, the DSM makes a determination, based on its internal load balancing algorithm, as to which path the request should be sent. If the I/O request cannot be sent down a path because the path is broken, the DSM shifts to the error handling mode.

Error handling

The DSM determines whether to retry the I/O request or to treat the error as fatal, making failover necessary. In the case of fatal errors, paths are invalidated, and the request is rebuilt and transmitted to a different device path.

DSM management

Management and monitoring of the DSM can be done through an administrative utility. The preferred interface is through the Windows Management Instrumentation (WMI).



Learning check 1. Which of the following array systems supports Storage Management Utility

(SMU)?

a. MSA1000 and MSA1510i

b. MSA1510i

c. MSA1000 and MSA1500cs

d. All three systems

2. The SMU Initial System Configuration Wizard is best used for what kind of storage systems?

.................................................................................................................

.................................................................................................................

3. Which SMU tab allows the user to exercise more flexible and detailed control of system configuration tasks?

.................................................................................................................

.................................................................................................................

Rev. 6.21 HP Restricted 6 -1

StorageWorks MSA30 Hardware Components

Module 6

Introduction This module discusses the hardware components associated with the MSA30 product.

Components of the MSA30 include:

Chassis

Hard drives

Environmental Monitoring Unit (EMU)

Power supplies/blowers

SCSI I/O module


6 -2 HP Restricted Rev. 6.21


Locate and explain the function of the following MSA30 components:

• Hard drives and associated elements

• EMU

• Power supply/blower assemblies

• SCSI I/O module

Identify and discuss component replacement considerations for the MSA30

Describe port numbering of single-bus and dual-bus configurations



MSA30 drive enclosure The MSA30 drive enclosure is a 3U unit housing up to 14 Universal 1” hot-pluggable SCSI drives. Each MSA30 includes the following standard components:

Dual hot-pluggable power supplies and fans

Environmental monitoring unit (EMU)

Single-bus or dual-bus SCSI I/O module

14 drive blanks

SCSI cable (one for single-bus module, two for dual-bus module)

Documentation, SmartStart CD

Components in the front and rear of the MSA30 enclosure are different and each will be explained below.

Front components

Front view MSA30 Storage Enclosure

The front of the MSA30 has 14 slots for Universal 1” disk drives or drive blanks. The 15th slot is blank on the front of the enclosure. However, at the bottom of the 15th slot are three system status LEDs (circled in white on the graphic). The MSA30 supports only SCSI disk drives.



The status LEDs are explained in the following graphic and table.

MSA30 system status LEDs

Item Color Description Normal state 1 Green Status (heartbeat) Blinking 2 Green Power On 3 Amber Fault Off



Disk drives Each disk drive in the enclosure has its own status LEDs, which are shown and explained in the following graphic and table.

Disk drive LEDs

Item Color Description 1 Green Activity LED 2 Green Online LED 3 Amber Fault or failure LED

Interpretations of the various combinations of LED indications are shown below.

Activity LED (1)

Online LED (2)

Fault LED (3) Interpretation

On, off, or blinking

On or off Blinking A predictive failure alert was received for this drive. Replace the drive as soon as possible.

On, off, or blinking

On Off The drive is online and is configured as part of an array If the array is configured for fault tolerance and all other drives in the array are online, you can replace the drive.

On or off Blinking Off The drive is rebuilding or undergoing capacity expansion. Do not remove the drive. Removing a drive could terminate the current operation and cause data loss.

On Off Off The drive is being accessed, but (1) it is not configured as part of an array; (2) it is a replacement drive and rebuild has not yet started; or (3) it is spinning up during the POST sequence. Do not remove the drive. Removing the drive could cause data loss.

Blinking Blinking Blinking Either (1) the drive is part of an array being selected by an array configuration utility, or (2) Drive Identification has been selected in Systems Insight Manager. Do not remove the drive. Removing a drive could cause data loss in non-fault-tolerant configurations.

Off Off On The drive failed and was placed offline. You can replace the drive.

Off Off Off Either (1) the drive is not configured as part of an array; (2) the drive is configured as part of an array, but a powered-up controller is not accessing the drive; or (3) the drive is configured as an online spare. If the drive is connected to an array controller, you can replace the drive online.



Universal 1” disk drives supported in the MSA30 enclosure are listed below.

72GB, Ultra320, 10K rpm






Note The Ultra320 drives are backward compatible to Ultra2 and Ultra3 speeds. Although the MSA1XXX arrays support the Ultra320 drives, they will run at only Ultra3 speed.



Rear components Components in the rear of the MSA30 enclosure include the:

EMU

Power supplies

Blowers

SCSI I/O module

MSA30 rear view

Item Description 1 EMU 2 Power supplies

3 I/O module (single-port or dual-port)

4 Blowers

! WARNING Do not use the handles on the EMU and I/O module to lift or hold the enclosure. The handles are designed only for holding the units or removing them from the enclosure, not for supporting the weight of the enclosure.



EMU The EMU is located in the left-most slot of the back of the MSA30 enclosure. It controls the system status LEDs on the front of the enclosure and performs the functions listed below.

In conjunction with the I/O module, assigns device SCSI addresses

Monitors system and room temperatures

• If the internal system temperature reaches 45 degrees C (113 degrees F), the EMU lights the amber System Fault LED

• If the room ambient temperature reaches 50 degrees C (122 degrees F) and Systems Insight Manager is running on the system, the EMU sends a signal to SIM, which in turn indicates an alarm condition.

• If the internal temperature of a power supply unit exceeds 85 degrees C (185 degrees F), the power supply automatically shuts down.

Monitors and reports the status of the power supplies, blowers, and system.

MSA30 Environmental Monitoring Unit (EMU)

The connector on the EMU is not used at the present time.

The EMU itself has a single LED indicator located at the top of the module. Status indicators and recommended actions are shown below.



LED indication EMU status Recommended actions

Flashing once per second EMU and enclosure are operational. None

Flashing twice per second

EMU and enclosure are operational, but there is a single-ended drive installed in the enclosure.

Replace the drive. The Ultra3 LVD enclosure does not support single-ended drives.

Lit solid (no flashing) Internal EMU problem. Replace the EMU.

Off No enclosure power or there is an internal EMU problem.

1. Check power supplies for proper operation. Replace if defective.

2. Replace the EMU.

Power supplies The MSA30 is equipped with redundant power supplies. The power supplies are hot-pluggable and share the electrical load equally. If one power supply fails or is removed, the other power supply assumes the full electrical load without interruption. If the power supply temperature exceeds a preset value, the power supply shuts down. The enclosure can run on a single power supply, but redundant supplies are recommended for system availability reasons.

Note As long as there is one operational power supply, you can replace a defective power supply without stopping data transfers. This is true whether the power supply has failed or is failing.

Blower installed on the power supply

Power supply and blower status LED



Power supply and blower shown removed from enclosure.

Blowers The MSA30 enclosure comes with redundant blowers attached to each power supply chassis. A power supply connector interfaces the blower and the enclosure. The blowers are variable speed and can run at higher speeds if temperature in the power supply increases. Power supply temperature is monitored by the EMU and if the temperature rises, the EMU directs the blowers to speed up. If a blower operates too slowly or stops – blower failure – the operational blower automatically operates at a faster speed.

For enclosures configured with a single power supply, a second blower is installed using a blower mounting assembly in the slot normally occupied by the second power supply.

Note The failure of a power supply +12.5 VDC circuit disables the associated blower.

Caution When replacing a fan for service, remove and replace the fan with a correct service part immediately. Allowing the MSA30 to run with one cooling fan could cause damage to the unit or cause the storage unit to shut down.



A single status LED is located on the blower assembly. The state of the LED indicates the status of the blower and the power supply. This LED can be in any one of three states – on, flashing, or off. These are described in the following table. LED Status Description Solid green The power supply and blower are operational Flashing green Either the power supply or the blower locate function is active.

Off Either the blower or power supply is not operational. If there is a second blower in the enclosure, it is running at higher speed.

SCSI I/O module

The SCSI I/O module allows the storage enclosure to be attached to a variety of SCSI controllers. The I/O module supports up to 14 Universal 1” Ultra320 disk drives. The MSA30 enclosure supports the use of either a single-port or dual-port SCSI I/O module. If a single-port module is used, the enclosure automatically places all installed drives on a single bus (bus A). If a dual-port module is used, the enclosure automatically uses two buses, assigning seven bays to each. If fewer than 14 drives are used with a dual-port module, the bus used depends on the location of the drives in the enclosure. Drives located in bays 1-7 are on bus A, while drives in bays 8-14 are on bus B.

Installing the I/O module automatically configures the enclosure for single-bus or dual- bus operation. Replacing a single-port I/O module with a dual-port I/O module converts the enclosure from a single-bus to a dual-bus. HP supports the conversion of a single-bus enclosure to a dual-bus enclosure, or a dual-bus enclosure to a single-bus enclosure, by replacing the I/O module.

Caution Always have a current backup available before changing the bus configuration. Changing from a single bus to a dual bus, or a dual bus to a single bus, changes the SCSI IDs. Depending on the controller, this ID change could cause the loss of data.

The I/O module is a pluggable, but not a hot-pluggable, component. Replacing either the I/O module or a cable requires stopping all data transfers to prevent the loss of data.

Caution To prevent errors, always stop all data transfers on the SCSI bus before removing or installing an I/O module or SCSI cable.



MSA30 SCSI I/O modules – single- and dual-port

Item Description 1 Release latch 2 SCSI bus A connector, dual-port module 3 Status LEDs, with Ultra320 designator 4 SCSI bus B connector, dual-port module 5 SCSI bus A connector, single-port module

The LEDs on the I/O module display the status of the external SCSI bus terminators and the power connection. The single-port module has just two LEDs – power and bus A.

MSA30 I/O module LEDs

Item Function indicated Normal state 1 5.1V DC power is connected Blinking 2 SCSI bus A is active Blinking (or On if very busy) 3 SCSI bus B is active Blinking (or On if very busy)



Enclosure and port numbering

Drive numbers are based on the location of the drive within the enclosure and the SCSI I/O module. Shown below is the drive numbering for a single-bus and a dual-bus configuration.

14-disk enclosure with single-port I/O module

14-disk enclosure with dual-port I/O module



Replacing system components Before removing a component from the system:

Be sure that a replacement component is immediately available.

Refer to the following table to determine whether the component can be removed without stopping data transfer or disconnecting the power.

Component Comment

Blower Disk drive Power supply unit

These devices are hot-pluggable. You can replace these devices at any time, even when the system power is on and data is being transferred. They are distinguishable from non-hot-pluggable devices by means of a purple handle, tab, or release latch.

I/O module SCSI cable

These items are warm-pluggable. Before removing or installing these items, you must first stop all data transfer to or through the item. You do not need to disconnect AC power from the system.

EMU

Depending on the type of controller connected to the system, the EMU could be hot-pluggable or cold-pluggable. Unless the controller documentation indicates otherwise, assume that the EMU can only be cold-plugged. Stop all transfer and disconnect AC power from the system before removing or installing this device.

Caution Removing a power supply or any other component significantly changes the airflow within the MSA30! A replacement part or blank panel should be immediately available to cover the vacated slot.

! Important Do not remove the EMU while the system is functioning. If this happens, monitoring of the storage enclosure stops and it must be power cycled to restore function.



Learning check 1. The system status LEDs on the front of the MSA30 enclosure are driven by which

component? …………………………………………………………………………………………..

2. What are the three status LEDs on the Universal 1” SCSI drive? ………………………………………………………………………………………….. …………………………………………………………………………………………..

3. What are the main functions of the EMU? ………………………………………………………………………………………….. …………………………………………………………………………………………..

4. Blower speed is controlled by which component? …………………………………………………………………………………………..

5. Explain the difference in bus assignments resulting from use of a single-port I/O module versus a dual-port module. ………………………………………………………………………………………….. ………………………………………………………………………………………….. ………………………………………………………………………………………….. …………………………………………………………………………………………..





Module 7

Introduction This module discusses the hardware components associated with the MSA20 drive enclosure.

Components of the MSA20 include:

Chassis

SATA disk drives

Redundant power supplies

Interconnect I/O module

Redundant fan assemblies




Locate and explain the function of the following components:

• Hard drives and associated elements

• Power supply

• Controller module/SCSI I/O module

• Fan assembly

• Drive backplane

• Midplane interface board

Identify and describe component replacement considerations for the MSA20.



MSA20 drive enclosure The MSA20 drive enclosure is a 2U unit housing up to 12 Universal 1” hot-pluggable Serial ATA (SATA) 1.5Gb drives. Each MSA20 includes the following standard components:

Dual hot-pluggable power supplies and fans

MSA20 controller module with Ultra320 SCSI I/O connectivity

Two power cords

One 3’ VHDCI SCSI cable.

Components in the front and rear of the MSA20 enclosure are different and each will be explained below.

Front components

Front view MSA20 Serial ATA (SATA) Storage Enclosure

The front of the MSA20 enclosure has 12 slots for the hot-pluggable Universal 1” SATA drives. The drive bays are numbered 1 through 12 with bay 1 at the top left and bay 12 at the lower right. The first column bays are 1 through 3, second column bays are 4 through 6, and so forth. Bay numbering is shown below.

123

456

789

101112

123

123

456

456

789

789

101112

101112

MSA20 bay numbering

Bays that do not contain actual disk drives must be filled with drive blanks to ensure proper airflow within the enclosure.



Back view

Controller/SCSII/O Module

Power supplies

Fault status indicatorFan assemblies



Power suppliesPower supplies

Fault status indicatorFault status indicatorFan assembliesFan assemblies

Disk drives The following graphic and table depict and explain the parts of the drive or drive blank.

MSA20 SATA disk drive and blank

Item Description 1 Drive carrier 2 Release lever 3 Release button 4 Fault/ID bicolor LED (amber and blue) 5 Online LED (green) 6 Drive blank 7 Release latch



Drive status LEDs The blue ID LED illuminates when you press the unit identification button on the rear of the enclosure. It also illuminates when the drive, or an array containing the drive, is selected in a management application, such as Array Configuration Utility (ACU).

The amber light illuminates when the drive fails or is predicted to fail in the near future.

The meanings of the various hard drive LED illumination patterns are explained in the following table. Online LED (green)

Fault/ID LED (amber/blue) Meaning

On, off, or flashing

Alternating between amber and blue

The drive has failed, or a predictive failure alert1 has been received for this drive. It has also been selected by a management application.

On, off, or flashing

Steadily blue The drive is operating normally, and it has been selected by a management application.

On Amber, flashing regularly (1Hz)

A predictive failure alert has been received for this drive. Replace the drive as soon as possible.

On Off The drive is online, but it is not currently active.

Flashing regularly (1Hz)

Amber, flashing regularly (1Hz)

The drive is part of an array that is undergoing capacity expansion or stripe migration, but a predictive failure alert has been received for this drive. To minimize the risk of data loss, do not replace the drive until the expansion or migration is complete.

Flashing regularly (1Hz)

Off The drive is rebuilding or is part of an array that is undergoing capacity expansion or stripe migration.

Flashing irregularly

Amber, flashing regularly (1Hz)

The drive is active, but a predictive failure alert has bee received for this drive. Replace the drive as soon as possible.

Flashing irregularly Off The drive is active and operating normally.

Off Steadily amber A critical fault condition has been identified for this drive, and the controller has placed it offline. Replace the drive as soon as possible.

Off Flashing regularly (1Hz)

A predictive failure alert has been received for this drive. Replace the drive as soon as possible.

Off Off The drive is either offline, a spare, or not configured as part of an array.

1 Predictive failure alerts can occur only when the MSA20 is connected to a Smart Array Controller. Universal 1” SATA disk drives supported in the MSA20 enclosure are listed below.

160GB, 7200 rpm

250GB, 7200 rpm

500GB



Rear components The components in the rear of the MSA20 are depicted in the graphic below and described in the table.

Rear view MSA20 Serial ATA (SATA) Storage Enclosure

Item Description 1 Arrow buttons (reserved for future use).

2 Enclosure ID display − Indicates the box ID number assigned to the enclosure during drive configuration.

3 Unit identification button – Pressing the button causes the blue LED on all drives in the enclosure to be illuminated.

4 Enclosure Monitor status LED – Glows green to indicate that the enclosure monitor (Global Service Indicator, or GSI) is functional.

5 Enclosure fault LED – Glows amber when any other LED in the enclosure is amber, if the GSI is functional.

6 Enclosure power button. 7 Power supply units. 8 Fan assemblies 9 Controller/SCSI I/O connector

Caution Removing a power supply or controller module significantly changes the airflow within the MSA20. When removing and replacing these components, the replacement part should be immediately available to avoid automatic shutdown of the enclosure because of airflow problems. When a fan module is removed, a dropdown panel closes the slot and prevents the airflow problems presented by removal of the other components.



Power supply unit The power supply unit is described below.

MSA20 power supply unit

Item Description 1 Handle 2 AC power connector 3 Release lever 4 Bicolor status LED (green or amber)

! WARNING Do not use the handles on the power supply units to lift or hold the enclosure. The handles are designed only for holding the units or removing them from the enclosure, not for supporting the weight of the enclosure.

There are two power supply units within the enclosure that share the electrical load equally. Each unit is capable of powering the entire enclosure for a short time period. Upon the failure of a power supply unit, the operational unit assumes responsibility for the entire electrical load. Because running from a single power supply tends to shorten the life of the power supply, HP recommends replacing a defective unit as soon as possible after the failure.

The status LED lights green when the unit is operational and amber when there is a failure.



Controller and SCSI I/O module The controller module is shown below and components of the module are explained in the table.

MSA20 controller module

Item Description 1 Upper cache battery 2 Finger hook 3 Bicolor status LED (green or amber) 4 SCSI connector 5 Service port (for HP service technicians only) 6 Release lever 7 Controller cache (lower cache battery is just visible )

The MSA20 has an internal controller module with 128MB of battery-backed write cache. The cache allows data to be transferred rapidly to the SATA drives, and the battery-backed feature protects data held in the cache for up to four days if power to the enclosure is interrupted. Both the upper and lower battery packs are replaceable items. Procedures for replacing the battery packs can be found in the HP StorageWorks Modular Smart Array 20 User Guide or the HP StorageWorks Modular Smart Array 20 Maintenance and Service Guide. Servicing the controller module is also addressed in a lab accompanying this training course.

After installing a new battery pack and inserting the controller module in the enclosure, it can take up to 45 minutes for the battery to recharge and the battery-backed write cache to become fully enabled.

! WARNING There is a risk of explosion, fire, or personal injury if battery packs are not properly handled. Refer to the Battery Replacement Notice in Appendix A of the HP StorageWorks Modular Smart Array User Guide before installing or removing a battery pack.



The face of the controller module has a standard VHDCI SCSI connector through which the MSA20 enclosure is connected to the MSA1500cs or MSA1510i.

The service port is used by HP technicians to connect to a terminal application for use in troubleshooting the enclosure.

Fan assembly The MSA20 fan assembly is depicted and described below.

MSA20 fan assembly

Item Description 1 Bicolor status LED (green or amber) 2 Release lever

There are two variable-speed, hot-pluggable fan assemblies that share the cooling load equally. Each unit is capable of cooling the entire enclosure for a short time period. Upon the failure of a fan unit, the operational unit assumes responsibility for the entire cooling load and runs at a higher speed. Because running from a single fan assembly tends to shorten the life of the assembly, HP recommends replacing a defective unit as soon as possible after a failure.

A feature of the MSA20 is that upon removal of a fan assembly from the enclosure, a drop-down cover closes the opening to aid in maintenance of proper airflow in the enclosure.

The status LED lights green when the unit is operational and amber when there is a failure.



Backplane boards The backplane board is shown below.

MSA20 backplane board

Two identical backplane boards provide the interface between the enclosure and the disk drives. Each board supports up to six SATA drives. The disk drive LEDs are driven by the backplane boards. Each board contains micro code, but it cannot be flashed by either the customer or field service.

The left and right backplane boards have the same part number. When ordering replacement boards, you must specify which board you want − left or right.

Midplane board The midplane board provides an interface between the backplane boards and the controllers, fans and power supplies. This board also supports one Voltage Regulator Module (VRM) that provides the correct voltage levels to the components located in the enclosure.



UID circuit board The UID circuit board is shown below and components are described in the table.

MSA20 ID circuit board

Item Description 1 Unit ID indicator (blue) 2 Enclosure monitor status LED (green) 3 On/standby switch (enclosure power switch) 4 System fault indicator (amber)

5 Seven-segment, two digit display; provides the box ID number

6 Up/down buttons (reserved for future use) The ID circuit board provides two main functions:

Power/standby switch – There is no power switch on the front of the enclosure, it is located on the rear of the enclosure.

Unit ID – The unit ID LEDs (two-digit display) display the “box” number based on the controller enclosure bus and port to which it is attached.



Replacing system components Before removing a component from the system:

Be sure that a replacement part is immediately available

Refer to the following table to determine whether the component can be removed without stopping data transfer or disconnecting the power.

Component Comment Drive and drive blank Power supply Fan assembly Controller module

These devices are hot-pluggable. You can replace them at any time, even when the system power is on and data is being transferred. They are distinguishable by means of a purple handle, tab, or release latch.

Midplane board Backplane board UID circuit board VRM power supply

These devices are not hot-pluggable. They are all located inside the enclosure. Data transfer must be stopped and power cords on both power supplies must be removed before attempting to remove the devices.



Learning check 1. List the components located in the MSA20 drive enclosure that are

hot-pluggable.

.................................................................................................................

.................................................................................................................

2. List the components located in the MSA20 that are not hot-pluggable.

.................................................................................................................

.................................................................................................................

3. Describe the drive bay layout for the MSA20 drive enclosure.

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

4. Explain the function of the backplane boards.

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

5. Explain the function of the midplane board.

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................




MSA Service and Support Module 8

Introduction This module discusses basic troubleshooting techniques, replacement procedures, and known service issues.




Discuss basic troubleshooting techniques:

Explain the replacement procedures of the major components of the MSA.

Identify some of the known service issues involving the MSA.

MSA Service and Support


Troubleshooting techniques Power on sequence

Before applying power to the MSA1xxx, all components of the storage system must be installed and connected to the supported interconnect options. Hard drives should be installed in the MSA1xxx so that they can be identified and configured at power on.

The MSA1xxx components must be powered on in the following order:

1. Power on all storage expansion enclosures and interconnect devices.

2. Power on the MSA1xxx using the power switch located in the far-right lower area of the front panel. After powering on, wait until the message “MSA1xxx Startup Complete” displays on your screen. This process might take up to two minutes.

3. Power on the servers.

The system power in the MSA1xxx does not shut off completely with the power switch, but instead goes into STANDBY, which removes power from most of the electronics and the drives, but portions of the power supply and some internal circuitry remain active. To remove the power completely, disconnect all power cords from the equipment.



Visual indicators When you have connected all the components of the MSA1xxx SAN solution and powered on the respective components, the first indication of problems can be easily detected by observing the LEDs on the various components.

If the fault indicator on any of the MSA1xxx components is amber, or if Insight Manager indicates a fault, determine the reason for this alert by examining the component indicators.

The MSA1xxx has visual indicators on LCD panels for the:

Controller.

Fibre Channel I/O module.

Fibre Channel I/O module link status.

Hard drives.

Power and blower assemblies.

Refer to Module 3 Hardware Components for descriptions on the visual indicators and their functions.

LCD panels — error codes Each array controller in an MSA contains an integrated display. This module is used for displaying informational and error messages showing the current status of the module, and for providing user input when required. Traditional POST messages, issued by PCI-based array controllers, are combined with runtime event notification messages to create a new set of controller display messages.

The display module consists of:

A 2-line, 20-column text display window.

Four buttons arranged in a circular shape.

Two status indicator lights.

Note For detailed information on using the LCD panel and operation messages, including errors, refer to Appendix LCD Panel Codes.



Removing and replacing component procedures The following diagram shows the location of the main components of the MSA1000 system.

10

7

1

6

9

2

8

3

4

10

7

1

6

9

2

8

3

4

Number Description 1 Chassis, 4U, with backplane 2 Controller blank 3 Power/cooling assembly 4 Shelf blower 5 AC power cord (not shown) 6 Controller 7 SCSI I/O module with Integrated EMU 8 Wide Ultra320 SCSI hard drive, 1 inch (Ultra2 and Ultra3 drives also supported) 9 Power switch assembly 10 Fibre Channel I/O module



Replacing an MSA controller The following steps explain how to replace a failed MSA controller. Before replacing your controller, follow these guidelines:

If your system is equipped with a single controller and that controller fails, it is recommended that the cache module from the failed controller be migrated to a new controller. Migrating the cache module to the new controller enables the completion of disk writes that might have been pending in the failed controller.

If an expand process is occurring, a dual controller system transitions into a nonredundant state. If a controller failure occurs during an expand process, the cache module from the failed controller must be migrated to the replacement controller to complete the expand process. It the expand process does not complete the array contents will be invalid.

To replace the MSA controller:

1. Press the thumb latch on the controller and rotate the latch handle towards you.

2. Remove the MSA controller by pulling it straight out of the chassis.

3. Insert the replacement controller into the chassis.

4. Push the controller in as far as it will go and press the latch handle inwards until it is flush against the front panel.



Replacing the MSA controller cache

! Important If your MSA is equipped with a single controller and you replace the controller cache, you must power off the system before replacing it. If your MSA has two controllers and you want to replace a failed cache module with another of the same size, you can replace the module while the system is running. If your MSA has two controllers and you are replacing the cache module with a module of a different size, you must power off the system before changing the cache module on both controllers at the same time.

1. Press the thumb latch on the controller and pull the latch handle towards you.

2. Remove the MSA controller by pulling it straight out of the chassis.

3. Unlatch the clips holding the MSA controller cover and raise the cover.

4. Simultaneously unlatch both clips holding the MSA controller cache module in place.

5. Carefully pull the cache module away from the controller board.

6. Slide the new MSA controller cache module into the controller. Be sure the side latches are fully engaged.

7. Close the MSA controller cover and be sure the clips are latched.

8. Push the controller in until it engages with the gear and then rotate the latch to engage the controller connector with the backplane.



Controller cache battery pack replacement

!

WARNING There is a risk of explosion, fire, or personal injury if the battery pack is replaced incorrectly or is mistreated. To reduce the risk: • Do not attempt to recharge the battery outside of the controller. • Do not expose to water or temperatures higher than 60°C (140°F). • Do not abuse, disassemble, crush, puncture, short external contacts, or

dispose of in fire or water. • Replace only with the HP spare designated for this product. • Cache module battery disposal should comply with local regulations.

Alternatively, return them by established parts return methods to HP for disposal.

To remove the old NiMH battery pack:

1. Push down on the bottom clip of the battery pack attached near the lower corner of the cache module.

2. Swing the battery pack away from the cache module to a 30-degree angle.

3. Lift the pack upward to unhook the top of the battery pack.

4. Repeat steps 1 to 3 for every battery pack you are replacing.



To install a new NiMH battery pack:

1. Wait about 15 seconds after removing the old battery pack to allow the battery charge monitor to reset.

2. Hook the top of the battery pack to the top of the cache module with the pack held at a 30-degree angle to the plane of the cache module board.

3. After the pack is hooked in position, swing the pack downward ensuring the bottom clip and two pegs line up with the holes in the cache module.

4. Be sure that the top hook and bottom clip on the battery pack are securely attached to the cache module. Installation of the new battery pack is complete. Repeat for the other battery pack.



MSA hot-plug power supply/blower Replacing a variable speed blower

MSA1000 blower

Caution Removing a power supply significantly changes the airflow within the MSA. After power supply removal, the remaining power supply starts a timer that will shut down the MSA in five minutes.

1. To remove the blower from the power supply, push in the two port-colored

blower tabs while pulling the blower element.

Caution Pressing the center section of the blower can damage the blades. To prevent damage to the blades, press only the outer edge of the blower.

2. Align guidepost of the new blower with the power supply connector. Slide the

replacement blower into the blower base until the tabs snap into place.

3. Be sure the following operational blower indications occur:

a. The blower starts operating immediately.

b. The blower indicator is On.



Replacing a fan module

MSA1500 cs/MSA1510i fan module

1. To remove the fan module, lift the port-colored fan module latch and pull the module out of the enclosure.

2. To install a fan module, slide the replacement fan module into the bay until it clicks into place.

3. After replacing the failed fan module, verify that:

• The system fault indicator on the enclosure is off.

• The heartbeat LED is flashing green.

• The fan module indicator on the rear of the module is solid green.



Replacing a power supply

1. Disconnect the AC power cord from the failed power supply. While lifting up the power supply port-colored module latch, grasp the blower element and pull the failed power supply out of the enclosure.

MSA1000

MSA1500 cs/MSA1510i

2. Install the replacement power supply by lifting up the power supply module latch and pushing in the base until the assembly is fully seated in the enclosure.



MSA SCSI I/O module To remove the SCSI I/O module, press the port-colored I/O module latch and pull the SCSI I/O module out of the MSA.

MSA1000

MSA1500 cs/MSA1510i

To replace an MSA SCSI I/O module, slide it into the bay until it clicks into place.



MSA Fibre Channel I/O module

To remove an MSA Fibre Channel I/O module, slide to the right (or lift) the port-colored module latch and slide the I/O module out of the enclosure.

To replace the I/O module, slide it into the bay until the module clicks into place.



Service advisories

! Important Refer to Cybrary (http://cybrary.inet.cpqcorp.net) or Services Access Workbench (SAW) (http://saw.cce.hp.com/km/saw/home.do) for the latest MSA1xxx related Service Advisories.

DOCUMENT NUMBER: OI021115_CW01

Service Pack 3 (SP3) for Microsoft Windows 2000 is not currently supported on systems running Secure Path 3.1B for Windows Workgroup Edition with an MSA1000

Due to architectural incompatibilities with Secure Path, Service Pack 3 for Microsoft Windows 2000 is not currently supported on systems running Secure Path V3.1B for Windows Workgroup Edition with an MSA1000 using firmware version 1.16. As a result, if Service Pack 3 is installed, these systems will fill the System Event Log with Event ID 772 errors that falsely indicate a redundant fiber path failover. There may be subsequent performance degradation due to the frequency of these messages being posted to the event log. These Event ID 772s will occur primarily during system start-up and intermittently during system operation.

Note MSA1000 and RA4X00 systems not running Secure Path are not affected.

Any systems running Secure Path V3.1A for Windows for RA4x00 or Secure Path V3.1B for Windows Workgroup Edition with Microsoft Windows 2000 Service Pack 3 installed are affected.

Note This issue does not affect HP EVA, HSG, MA or other HP storage solutions. This only occurs if Secure Path is installed on an RA4000, RA4100 or MSA1000 Storage System.

MSA1000: There are 2 methods to permanently resolve this issue:

1. The first method only requires an upgrade to the MSA1000 controller ROM to version 1.18. This is available for download from the 1.18 firmware link on: http://h18000.www1.hp.com/products/storageworks/MSA1000/ index.html



2. The second method is to upgrade the controller to firmware 2.38 or later. As this firmware upgrade also enables multi-node cluster support and other enhancements it does require that the following components are also upgraded:

a. FCA2101 HBA driver 5.4.82A9 or later, EMU firmware 1.86 or later, ACU 6.0 or later, Secure Path 4.0 Workgroup Edition

Note Microsoft is developing a Hotfix that resolves this issue. Upon successful completion of qualification and regression testing it will be made available.

DOCUMENT NUMBER: EU021120_CW01 MSA1000 Will Not Be Displayed By Storage Agents For Linux After Array Configuration Utility-XE (ACU-XE) Is Started.

HP StorageWorks Modular SAN Array 1000 (MSA1000) and its components (physical disk drives, logical disk drives, switches, etc.) will no longer be displayed by the Storage Agents for Linux 6.10.0-6 when the Array Configuration Utility-XE (ACU-XE) is started on any ProLiant server.

Any ProLiant server configured with the MSA1000 and running the Storage Agents for Linux 6.10.0-6 and the Array Configuration Utility-XE (ACU-XE) with any of the following operating systems:

Red Hat Linux 7.2 Professional

Red Hat Linux Advanced Server 2.1

SuSE Linux Enterprise Server 7

To avoid this issue, restart the Storage Agents for Linux after running the Array Configuration Utility-XE (ACU-XE). To restart the Storage Agents, run the following command: /etc/init.d/cmastor restart

HARDWARE PLATFORMS AFFECTED: ProLiant Cluster HA/F100 for MSA1000, ProLiant Cluster HA/F200 for MSA1000, ProLiant DL380, ProLiant DL380 G2, ProLiant DL380 G3, ProLiant DL580, ProLiant DL760, ProLiant ML370, ProLiant ML370 G2, ProLiant ML370 G3, ProLiant ML530, ProLiant ML530 G2, ProLiant ML570, ProLiant ML570 G2, ProLiant ML750



DOCUMENT NUMBER: EC020515_CW01 MSA1000 Controller Failure May Cause Some Node(s) To Drop Out Of Multi-Node Oracle 9i Real Application Cluster (RAC).

The failure of one array controller in a Parallel Database Cluster (PDC/O2000) for a StorageWorks Modular SAN Array 1000 (MSA1000) storage enclosure in a multi-node Oracle 9i Real Application Clusters (RAC) cluster may cause one or more server nodes to drop out of the cluster. The Windows Event Log messages on the node(s) that dropped out will have an entry listing the following error message: Disk event error 15 indicating that "The device [hard drive location] is not ready for access yet". The Oracle Alert Log on the node(s) that dropped out reports: "O/S-Error: (OS 1167) The device is not connected". Any ProLiant server configured as a node in a PDC/O2000 for Oracle 9i RAC cluster with Microsoft Windows 2000 Advanced Server and the MSA1000 storage solution using StorageWorks Secure Path Software Version 3.1B.

After the problem occurs, recover the node(s) that dropped out by rebooting each node and allow the node(s) to rejoin the Oracle 9i RAC cluster and restart the database instance.

To prevent this problem from occurring, apply SoftPaq SP19812, "PDC/O2000 for MSA1000 Patch," to each server in the Oracle 9i RAC cluster. SP19812 can be downloaded from the following URL:

ftp://ftp.compaq.com/pub/softpaq/sp19501-20000/SP19812.EXE



DOCUMENT NUMBER: OI021203_CW01 Novell Secure Path 3.0c Workgroup Edition/ Large Cluster Issue

In a SAN configuration with multiple MSA1000 storage arrays, HP Secure Path 3.0c for Netware Workgroup Edition may cause Abends in some or all of the clustered servers when complete power loss has occurred to an MSA1000 in the SAN or when the MSA1000 is accidentally removed from the SAN due to a cable pull:

1. Limit Clusters to 2 or less nodes.

2. Increase polling interval from the default of 90 seconds to greater than 300 seconds.

3. Ensure steps are taken to keep the MSA1000 from being abruptly removed from the SAN i.e. ensure cables are run off the floor, use separate power sources and battery backups are in use.

4. Ensure steps are taken to keep any attached storage shelves attached to the MSAs from being powered off or disconnected. Ensure cables are run off the floor, use separate power sources and battery backups are in use.

This condition is primarily visible with HP Secure Path 3.0c with NetWare 5.1 clustered server configurations with nodes exceeding more than 2 (i.e. 4, 6, 12) and more than one MSA1000 is accessed from the same host. This condition can also occur when one of the MSAs is totally removed from the SAN, by a total loss of power, or by both fiber I/O cables being pulled or disconnected.

The issue is being investigated and as soon as a fix is found, tested, and qualified then a patch will be posted to the following website: http://h18000.www1.hp.com/products/storageworks/MSA1000/index.html



DOCUMENT NUMBER: EX011221_CW01 Mandatory Firmware Upgrade Needed To Support Stripe Size Greater Than The Default 16 KB For A Logical Drive Using Advanced Data Guarding (ADG).

When configuring logical drives on the controllers listed in the "Scope" section of this document, a controller firmware upgrade is MANDATORY if both of the following conditions are true:

A logical drive is configured for Advanced Data Guarding (ADG)

A stripe size of 32 KB or 64 KB is selected (the default is 16 KB)

A logical drive is not affected by this issue if any of the following are true:

The controller firmware has been upgraded as described in the Resolution.

The logical drive is NOT using ADG (even if it resides on the same physical drive(s) configured with ADG).

The logical drive is configured for RAID 1+0, RAID 5, RAID 1 or RAID 0.

The logical drive is configured for ADG with a stripe size of 8 KB or 16 KB. This configuration is fully supported without the firmware upgrade listed in the Resolution.

HP strongly recommends that all affected controllers be upgraded in order to avoid potential problems that may occur if logical drives are later configured with ADG and a stripe size of 32 KB or 64 KB. Even if this configuration is used, potential problems would only occur if a physical drive also fails.

Note This issue was discovered by HP and has NOT been reported by customers. This issue affects the following HP storage products with the specified firmware version

This issue affects the following HP storage products with the specified firmware version:

HP ProLiant Cluster HA/F100 for MSA1000 with firmware version 1.14

HP ProLiant Cluster HA/F200 for MSA1000 with firmware version 1.14

HP ProLiant DL380 G2 Packaged Cluster with controller firmware version 1.08

HP Smart Array 5302 Controller with firmware version 2.18 or lower

HP Smart Array 5304 Controller with firmware version 2.18 or lower

HP Smart Array Cluster Storage with firmware version 1.08

HP StorageWorks Modular SAN Array 1000 (MSA1000) with firmware version 1.14

For a HP StorageWorks Modular SAN Array 1000 with firmware version 1.14, upgrade to MSA1000 Firmware Release Version 1.16A.



For information on the HP StorageWorks Modular SAN Array 1000 firmware, the SoftPaq text file can be viewed at the following URL: ftp://ftp.compaq.com/pub/softpaq/sp19501-20000/sp19663.txt

SoftPaq SP19663, "Compaq StorageWorks Modular SAN Array 1000 firmware," can be downloaded at the following URL: ftp://ftp.compaq.com/pub/softpaq/sp19501-20000/sp19663.exe

Note This upgrade allows the use of the Array Configuration Utility (ACU) with stripe sizes larger than the default stripe size of 16 KB.



Learning check 1. What is the correct power on sequence for the MSA?

a. Power on everything simultaneously

b. Interconnect, MSA, and secondary storage, servers

c. Expansion storage enclosures, MSA, and then server

d. Servers, external primary and secondary storage, interconnect

2. What guidelines should you follow when replacing your controller?

.................................................................................................................

.................................................................................................................

.................................................................................................................

.................................................................................................................

3. What documents provide information on known issues and their resolution with the MSA1xxx?

.................................................................................................................

.................................................................................................................

.................................................................................................................



Rev. 6.21 HP Restricted Answers – 1


Module 1 Benefits of a SAN 1. Briefly describe current industry storage trends.

Customers are facing an exponential demand for increasing storage capacity as their businesses grow and they continue to deploy more powerful, efficient solutions. Provide a simple definition for a storage area network (SAN).

2. Provide a simple definition for a storage area network (SAN).

A dedicated, centrally managed, secure information infrastructure that enables direct physical access to common storage devices or a storage pool.

3. List five features of a SAN.

A secure implementation of storage I/O methods over network transports A high-speed, scalable, robust network of servers and storage devices A storage service that:

Connects to enterprise-wide servers Centralizes data Moves data automatically for availability and replication Provides accelerated data access Supports advanced storage management Provides for highly available configurations A natural platform for server clustering applications

4. List five benefits of a SAN.

Centralized storage Elimination of server downtime while adding storage Improved availability Modular scalability Serverless backup Online storage migration

5. What are the three classes of B class switches supported by HP?

Directors Fabric Switches Arbitrated Loop Switches


Answers – 2 HP Restricted Rev. 6.21

6. What are HP recommended guidelines when mixing 1 and 2Gb/s switches?

Use 2Gb/s switches in the core for Core to SAN Switch or Director to Edge Switch topologies. Connect 2Gb/s switches together to take advantage of the ISL Trunking feature when using Fibre Channel switch models that support this feature. Use 2Gb/s switches for connections to 2Gb/s capable devices. Zoning rules, SAN security, and SAN management for 2Gb/s switches are the same as for 1Gb/s switches.

7. Describe zoning.

Group of fabric-connected devices (storage, tapes, hosts) arranged into a specified grouping

8. When is zoning required on a HP-UX 11.0 or 11i?

In a heterogeneous SAN

9. Describe two advantages of implementing storage consolidation.

Saves money by creating a larger pool of storage for the hosts Servers can have access to the same-shared pool Administrator can now meet his storage requirements without having to purchase any additional storage. The average storage in a non-SAN environment that a single administrator can adequately handle is under 500GB. In a SAN environment, that same administrator can manage up to four to six times that amount.

10. Describe DAS to SAN (DtS) architecture.

Exclusive HP feature that provides a quick and easy way to migrate stored data protected by Smart Array controllers to a MSA1000 storage system. DtS architecture is a direct-attached storage-to-storage area network that provides:

Instant consolidation of DAS into a SAN environment. An upgrade path from Smart Array controlled drives and data to a SAN environment. Simple redeployment of DtS environment for growth management and capacity utilization that supports up to 42 drives and 32 volumes.

11. What are three benefits of an EBS SAN backup? Shared tape storage Scalability Automation High performance Backup up to 158.4GB/h No network bottlenecks Snapshot with Virtual Replicator

Answers


Module 2 MSA1xxx Product Overview 1. Which of the three systems discussed in this module contains an integrated

controller and disk drive enclosure? MSA1000

2. The MSA1000 can be expanded by the addition of a maximum of_________ drive enclosures, for a maximum disk capacity of ________ disks. Two drive enclosures; 42 disks

3. Complete the statements below:

a. The MSA1000 connects to ______________________________ networks.

b. The MSA1500cs connects to _____________________________ networks.

c. The MSA1510i connects to _______________________________ networks. a. Fibre Channel; b. Fibre Channel; c. IP

4. Identify the type of disk drive supported by the MSA20 and MSA30 disk enclosures and the maximum number of disks supported by each enclosure. The MSA20 supports 12 SATA disk drives. The MSA30 supports 14 SCSI disk drives.

5. What component of the MSA1500cs and MSA1510i limits the way SCSI and SATA disk enclosures can be mixed on those systems? The SCSI I/O module

6. The MSA1510i supports only which operating systems? Windows 2000 SP4 (32-bit) and Windows Server 2003 (32-bit)

7. All three systems discussed in this module support RAID 6. Describe RAID 6 and its advantages. RAID 6 provides the highest level of protection. It allocates two sets of parity data and allows simultaneous write operations. It can withstand two simultaneous drive failures without downtime or data loss. RAID 6 requires a minimum of four disks.



Module 3 Hardware Components 1. What is the maximum number of Fibre Channel I/O modules supported on the

MSA1500 cs? Two

2. What is the maximum number of drive enclosures supported when utilizing MSA30s attached to an MSA1500cs? Four

3. In an MSA1500cs or MSA1510i system supporting eight MSA20 SATA drive enclosures, what is the recommended connection order by enclosure number, bus, and port?

Enclosure 1, bus 0, port a; Enclosure 2, bus 1, port a; Enclosure 3, bus 2, port a; Enclosure 4, bus 3, port a; Enclosure 5, bus 0, port b; Enclosure 6, bus 1, port b; Enclosure 7, bus 2, port b; Enclosure 8, bus 3, port b

4. What type of cable is required for MSA1510i connectivity to an external SAN switch? Category 5e or better Ethernet cables

5. List all possible MSA20/MSA30 configurations when fully populating the four SCSI I/O modules of the MSA1500cs or MSA1510i.

Four MSA30s Eight MSA20s One MSA30; six MSA20s Two MSA30s; four MSA20s Three MSA30s; two MSA20s

6. What information does LED number 8 on the MSA1000 controller provide? Idle heartbeat

Answers


Module 4 MSA1000 and MSA1500cs Management Utilities

1. Which ACU configuration mode automatically configures the controller based on the answers to questions posed to the user? Express Configuration Mode

2. When using CLI to configure, manage, or monitor the array system, commands involving the controllers in a redundant controller system are addressed to “this_controller” and “other_controller.” What determines which controller is “this_controller?” The controller to which the management server is connected is “this_controller”

3. HP Systems Insight Manager (SIM) monitors controller parameters and logical drive activity on the MSA arrays. Which operating systems does SIM support? Windows, NetWare, and Linux

4. List three Web Tools capabilities for managing a fabric switch. Monitor and manage the entire fabric Monitor and manage individual switches Monitor and manage individual ports

5. MPIO provides native multipathing support for which MSA-supported operating systems? Windows 2000 Server and Windows Server 2003

6. Secure Path v3.0c supports which operating system(s)? NetWare (SP 3.0c for NetWare) and Linux (SP 3.0c for Linux)



Module 5 MSA1510i Management Utilities 1. Which of the following array systems supports Storage Management Utility

(SMU)?

a. MSA1000 and MSA1510i

a. MSA1510i

b. MSA1000 and MSA1500cs

c. All three systems

2. The SMU Initial System Configuration Wizard is best used for what kind of storage systems? Simple systems (single-server)

3. Which SMU tab allows the user to exercise more flexible and detailed control of system configuration tasks? Configure Tab

Answers


Module 6 StorageWorks MSA30 Hardware Components

1. The system status LEDs on the front of the MSA30 enclosure are driven by which component? The EMU

2. What are the three status LEDs on the Universal 1” SCSI drive? Activity LED, Online LED, and Fault (failure) LED

3. What are the main functions of the EMU? The EMU operates system status LEDs on the front of the enclosure; assigns SCSI addresses (in conjunction with the I/O module); monitors system and room temperatures; and monitors and reports status of the power supplies, blowers, and system.

4. Blower speed is controlled by which component? EMU

5. Explain the difference in bus assignments resulting from use of a single-port I/O module versus a dual-port module. With a single-port I/O module, all 14 drives are directed through port A of the module. With a dual-port module, a split bus is activated with drives 1-7 directed through port A and drives 8-14 directed through port B.



Module 7 StorageWorks MSA20 Hardware Components

1. List the components located in the MSA20 drive enclosure that are hot-pluggable. Drive and drive blank, power supply, fan assembly, and controller/I/O module

2. List the components located in the MSA20 that are not hot-pluggable. Midplane board, backplane boards, UID circuit board, and VRM power supply

3. Describe the drive bay layout for the MSA20 drive enclosure. The drives are numbered 1-12 with bay 1 at the top left and bay 12 at the bottom right. The first column bays are 1-3, the sencon column 4-6, and so on.

4. Explain the function of the backplane boards. Two identical boards provide the interface between the enclosure and the disk drives. Each board supports up to six drives. The board also drives the disk LEDs.

5. Explain the function of the midplane board. The midplane board provides an interface between the backplane boards and the controllers, fans, and power supplies. The board also supports one Voltage Regulator Module (VRM) that provides correct voltage levels to the enclosure components.

Answers


Module 8 MSA Service and Support 1. The correct power on sequence for the MSA1000 is?

a. Power on everything simultaneously

b. Interconnect, MSA1000, and servers

c. Expansion storage enclosures, MSA1000, and then server

d. Servers, external primary and secondary storage, interconnect

2. What guidelines should you follow when replacing your controller?

If your system is equipped with a single controller, and that controller fails, it is recommended that the cache module from the failed controller be migrated to a new controller. Migrating the cache module to the new controller allows the completion of disk writes that may have been pending in the failed controller’s.

If an expand process is occurring, a dual controller system will transition into a non-redundant state. If a controller failure occurs during an expand process, it is required that the cache module from the failed controller be migrated to the replacement controller to complete the expand process. It the expand process does not complete the array contents will be invalid.

3. What documents provide information on known issues and their resolution with the MSA1000?

Service Advisory



Rev. 6.21 HP Restricted Appendix – 1

LCD Panel Codes Appendix

Controller display messages Each array controller in an MSA1xxx contains an integrated display. This display is used for presenting informational and error messages, which indicate the current status of the module. The display also accepts user input as required. The traditional POST messages issued by PCI-based array controllers have been combined with runtime event notification messages to create a new set of controller display messages.

The display module consists of the following components:

A two line, twenty column display text display window

Four push buttons arranged in a circular “pie” shape

Two status indicator lights


Appendix – 2 HP Restricted Rev. 6.21

Operation Messages

The display module is capable of holding up to 100 messages. Once this maximum size has been reached, older messages will be removed to make room for newer ones. Messages can be of three types: error, informational and user input.

Error messages Error messages indicate that a problem has occurred and may require user action to correct it.

An amber indicator to the left of the display text display window will be turned on when ever an error message is being viewed. This indicator will also be turned on if an error message was sent to the display module but has not been viewed because non-error type messages were sent to the display module afterwards.

After scrolling backwards and viewing all error messages, the indicator will return to only lighting up when currently on an error message.

Informational messages Informational messages indicate non-critical changes in the system that are provided as feedback to the user.

The amber indicator to the left of the display text display window will normally be turned off whenever an informational message is being viewed unless an unviewed error message was previously sent to the display module.

After scrolling backwards and viewing all error messages, the indicator will return to only lighting up when currently on an error message.

User input messages User input messages indicate that the system has encountered an issue that can be handled in two different ways. It allows the user to choose which way to handle the issue or it will default to a standard choice after a set period of time. These input messages only occur during system power on and not during run time.

The amber indicator to the left of the display text display window will blink on and off when a user input message is being viewed and is available for input.

Press the left or right button on the LCD panel to respond to the prompt. If the user has not provided input within the time-out period, the message will remain but the indicator will stop blinking.

LCD Panel Codes


Scrolling Older messages can be viewed by scrolling backwards using the up push button (with the up arrow on it). More recent messages can be viewed by scrolling forwards using the down push button (with the down arrow on it). When a new message is sent to the LCD, the display will display that message ignoring any previous scrolling position it had. This new message will now be the most recent message available.

User input User input messages will allow the user two options which are selected by either pushing the left push button (with the left arrow on it) or the right push button (with the right arrow on it). The meaning of each button will be defined in the display text display window.

Deleting messages The currently displayed message can be deleted from the display module by pressing the left push button and the right push button at the same time.

Redundancy link light There is a green indicator to the left of the display text display window that will be lit when two array controllers have been inserted into the MSA system and controller redundancy is enabled. The indicator will not be lit if there is only one array controller inserted or if the array controllers are not redundant due to some type of failure. (There is no transparent failover with this unit.)

Note You must have redundant cables connected to order for the redundancy controller function correctly.

Special notes

Box numbering

The display message may specify a box number. The following box numbers are defined.

Box 1 is the MSA1xxx chassis.

Box 2 is the storage enclosure attached to SCSI port A of the MSA1xxx.

Box 3 is the storage enclosure attached to SCSI port B of the MSA1xxx.



Responding to LCD messages When a new message is sent to the LCD, the display will automatically show that message and ignore any previous scrolling position.

The display panel consists of a two-line, twenty-character text display window and four push buttons arranged in a circular “pie” shape. The push buttons are used to scroll through the messages, respond to prompts, and delete messages, as described in the following illustration and table.

Controller push buttons

Button Use Up Scroll to an older message Down Scroll to an newer message Left User input response, as defined by the LCD display Right User input response, as defined by the LCD display Simultaneous left and right Delete the displayed message

LCD Panel Codes


LCD message descriptions The following table contains the defined messages and their components.

Message Type Description Action 00 ARRAY CONTROLLER FIRMWARE VER <version>

Informational Displays the current version of the firmware running on the array controller

01 MSAxxxx STARTUP COMPLETE

Informational The array controller has completed its power on sequence and is now operational.

02 ENABLE VOLUME <n>? ‘<’=NO, ‘>’=YES

User Input An issue has been found with a configured volume that may result in data loss. The exact nature of the issue will be detailed in a previous display message.

Selecting the no option will result in the volume being disabled so the user can attempt to fix the issue. Selecting the yes option will result in the volume being enabled regardless of the issue.

03 CRITICAL LOCK-UP DETECTED. CODE=<n>h

Error A critical error has been detected by the array controller firmware. In order to prevent any possible data loss, the firmware has entered a lock-up state. The code contains engineering specific information about the lock-up condition. HP support should be contacted.

Remove the failing array controller, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. Should the issue persist please contact HP support.

04 ENABLE VOLUMES ? ‘<’=NO, ‘>’=YES

User Input An issue has been found with all of the configured volumes that may result in data loss. The exact nature of the issue will be detailed in a previous display message.

An issue has been found with all of the configured volumes that may result in data loss. The exact nature of the issue will be detailed in a previous display message



LCD message descriptions Message Type Description Action 05 SYSTEM NAME: <name>

Informational Displays the user assigned name for the system. This name can be assigned using the Array Configuration Utility (ACU).

06 RESTARTING SYSTEM Informational Indicates that the system has been reset and is being restarted.

07 CLONE FIRMWARE? ‘<'=NO, ‘>'=YES

User Input The array controller has detected a firmware version mismatch with the other controller in a redundant system and needs to perform a firmware clone to proceed.

10 FIRMWARE FLASH FAILED

Error ROM flash failed. Download a new image and retry. If the issue persists, contact HP support.

11 CLONING REFUSED, SYSTEM HALTED

Error A firmware mismatch was detected (Error 07) and the user selected No.

You must clone the firmware.

20 INITIALIZING SCSI SUBSYSTEM

Informational The SCSI subsystem is being initialized as part of the power on sequence

21 SCANNING FOR SCSI DEVICES

Informational The firmware is searching for SCSI devices attached to the system as part of the power on sequence

22 INITIALIZING SCSI DEVICES

Informational The firmware is initializing all SCSI devices attached to the system as part of the power on sequence

23 SCSI SUBSYSTEM HARDWARE FAILURE

Error The SCSI subsystem has experienced a hardware failure and is not operating correctly. The array controller has halted itself and cannot continue

Please contact HP support

24 BAD SCSI BUS MODE NON-LVD DEVICE FOUND

Error The system does not support SCSI Single Ended (SE) devices, it only supports SCSI Low Voltage Differential (LVD) devices. all

The system should be powered off and then SCSI devices attached to it should be examined. Any SE devices found should be removed and replaced with LVD devices.

FW VERSION IS NOT SUPPORTED

Error The array controller has been inserted in an MSA1000 chassis, which is not supported.

LCD Panel Codes


LCD message descriptions Message Type Description Action 30 I2C READ FAILURE <I2C device name>

Error The system has a number of internal devices that are accessed via an I2C hardware bus. One of these devices failed when attempting to read from it. Certain I2C devices are considered critical and will result in a failure of the array controller while others may result in some loss of functionality (such as lost display messages).

Should the issue persist please contact HP support.

31 I2C WRITE FAILURE <I2C device name>

Error The system has a number of internal devices that are accessed via an I2C hardware bus. One of these devices failed when attempting to write to it. Certain I2C devices are considered critical and will result in a failure of the array controller while others may result in some loss of functionality (such as lost display messages).

Should the issue persist please contact HP support

32 CHASSIS NVRAM CONTENTS CORRUPTED

Error The system has non-volatile memory on it that contains required information which is needed to operate. This non-volatile memory appears to be corrupted and the information is not valid. The system cannot continue to operate and will halt.

Please contact HP support.

40 BEGIN REDUNDANCY SUPPORT

Informational The array controllers are attempting to enter redundant mode.



LCD message descriptions Message Type Description Action 41 REDUNDANCY ACTIVE-ACTIVE CONTROLLER

Informational The array controllers are now in redundant mode and this array controller is active which means that it is allowed to access the configured volumes on the system

42 REDUNDANCY ACTIVE STANDBY CONTROLLER

Informational The array controllers are now in redundant mode and this array controller is standby which means that it can be made active should the current active array controller fail, assuming you have all cables, I/O module or embedded switch installed

43 REDUNDANCY FAILED HARDWARE FAILURE

Error While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers encountered a hardware failure on the communication channel between the two array controllers. Redundancy is disabled at this time

If the system is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. If this does not resolve the issue then wait until down-time is available. Power off the system, remove both array controllers and reinsert them insuring they are fully seated in the chassis. Should the issue persist please contact HP support

44 REDUNDANCY FAILED MISMATCH HARDWARE

Error Both array controllers must contain the same hardware for them to successfully enter redundant mode. The current array controllers do not contain the same hardware, possibly because one has an attached Ethernet daughter card and the other does not.

If the system is currently involved in host I/O, remove the standby array controller, add or remove the Ethernet daughter card as needed, wait 10 seconds, and then reinsert it, ensuring that it is fully seated in the chassis. If this does not resolve the issue, wait until down-time is available. Power off the system, remove both array controllers, add or remove Ethernet daughter cards as needed on both, and then reinsert them, ensuring they are fully seated in the chassis. If the issue persists, contact HP support.

LCD Panel Codes


LCD message descriptions Message Type Description Action 45 REDUNDANCY FAILED MISMATCH FIRMWARE

Error Both array controllers must be running the same version of firmware for them to successfully enter redundant mode. A process called firmware cloning that attempts to make them both the same version has failed.

Manually update the firmware on the older array controller.

47 REDUNDANCY FAILED CACHE SIZE MISMATCH

Error Both array controllers must have the same size of cache memory for them to successfully enter redundant mode

If the system is currently involved in host I/O, remove the standby array controller, add or remove cache memory as needed, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. If this does not resolve the issue then wait until down-time is available. Power off the system, remove both array controllers, add or remove cache memory as needed on both, and reinsert them insuring they are fully seated in the chassis. Should the issue persist please contact HP support

48 REDUNDANCY HALTED FIRMWARE CLONED

Informational Both array controllers must be running the same version of firmware for them to successfully enter redundant mode. A process called firmware cloning has been successfully completed in order to make them both the same firmware level. The standby array controller will now be restarted automatically so they can attempt to achieve redundancy again



LCD message descriptions Message Type Description Action 49 REDUNDANCY FAILED FIRMWARE LOCKUP

Error While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers encountered a critical condition resulting in a firmware lockup. Redundancy is disabled at this time

If the system is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. If this does not resolve the issue then wait until down-time is available. Power off the system, remove both array controllers, and reinsert them insuring they are fully seated in the chassis. Should the issue persist please contact HP support

50 REDUNDANCY FAILED OUT OF MEMORY

Error While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers failed to allocate required memory. Redundancy is disabled at this time.

If the system is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. If this does not resolve the issue then you wait until down-time is available. Power off the system, remove both array controllers, and reinsert them insuring they are fully seated in the chassis Should the issue persist please contact HP support.

LCD Panel Codes


LCD message descriptions Message Type Description Action 51 REDUNDANCY FAILED I/O REQUEST ERROR

Error While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers encountered an error while sending I/O between the two array controllers over the communication channel between them. Redundancy is disabled at this time

If the system is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. If this does not resolve the issue then wait until down-time is available. Power off the system, remove both array controllers, and reinsert them insuring they are fully seated in the chassis. Should the issue persist please contact HP support.

52 REDUNDANCY FAILED PCI BUS

Error While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers encountered a PCI bus error on the communication channel used between the two array controllers. Redundancy is disabled at this time.

If the system is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. If this does not resolve the issue then wait until down-time is available. Power off the system, remove both array controllers, and reinsert them insuring they are fully seated in the chassis. Should the issue persist please contact HP support.

53 REDUNDANCY FAILED NO SECOND CONTROLLER

Error While operating in redundant mode, one of the array controllers was removed Redundancy is disabled at this time

Reinsert the missing array controller insuring that it is fully seated in the chassis



LCD message descriptions Message Type Description Action 54 REDUNDANCY FAILED CACHE DIMMS MISMATCH.

Error The cache memory modules on two different controllers are not the same size. All cache memory modules must be the same size for redundancy to operate

Remove the array controller that has been halted, replace the cache modules with the appropriately sized ones, wait 10 seconds, and then reinsert the array controller insuring that it is fully seated in the chassis

57 REMOVE OTHER CONTROLLER NOW!

Informational The standby controller has been disabled at the user's request, and may now be safely removed from the chassis.

Remove the standby controller.

60 NO CACHE MODULE FOUND.

Error The array controller requires at least one cache module in order to operate. Either there is not one present or it has failed

Remove the failed array controller, either add a cache module or replace the failed one, wait 10 seconds, and then reinsert it insuring that it is fully seated in the chassis. Should the issue persist please contact HP support

61 DUAL CACHE MODULE SIZE MISMATCH.

Error The array controller has two cache modules attached but they are of different sizes. Both cache modules must be the same size

Remove the failed array controller, replace one of the cache modules with a different one that is of the correct size, wait 10 seconds, and then reinsert it, insuring that it is fully seated in the chassis.

62 CACHE MODULE #<n> <n>MB.

Informational Displays the size of the cache module inserted into the respective cache module slot

63 VALID CACHE DATA FOUND AT POWER-UP.

Informational Valid host data was found in the battery backed cache memory at power up. This data has been flushed to the drives

64 CACHE DATA LOST BATTERY DEAD

Error The battery on the cache memory was no longer charged. If there was data in the cache memory then it has been lost.

LCD Panel Codes


LCD message descriptions Message Type Description Action 65 CACHE HARDWARE ENABLED.

Informational The cache hardware had been temporarily disabled but is now enabled again. This may have been due to insufficient charge on the batteries that have now charged up to capacity

66 CACHE HARDWARE FAILED AND DISABLED

Error The cache memory has experienced a hardware failure.

If the failure has occurred on the standby array controller, then remove the standby array controller, replace the cache modules, wait 10 seconds, and then reinsert the array controller insuring that it is fully seated in the chassis. If the failure has occurred on the active array controller, then wait until downtime is available. Power off the system, remove the array controller, replace the cache modules, and reinsert the array controller insuring it is fully seated in the chassis. Should the issue persist please contact HP support

67 CACHE HARDWARE TEMPORARILY DISABLED.

Informational The cache memory hardware has temporarily been disabled typically because either the battery is not charged up or a capacity expansion operation is occurring. The cache will automatically be enabled once the condition has been corrected



LCD message descriptions Message Type Description Action 68 OBSOLETE CACHE DATA DELETED.

Informational Old data that no longer belongs to any current configured volumes was found in the cache memory at power up. This data has been deleted. This typically happens if cache modules are moved between array controllers

69 CACHE BATTERIES LOW, RECHARGING

Informational The batteries on the cache module are low and are being recharged.

70 CACHE DISABLED NO CONFIGURATION

Informational Informational The cache has not been configured and therefore is disabled. The cache can be configured by using the Array Configuration Utility (ACU).

LCD Panel Codes


LCD message descriptions Message Type Description Action 71 SYSTEM HALTED FOR CACHE ERROR

Error This message is generated if the user chooses to ignore a critical cache error condition. It is always preceded by message #72 (although message #72 is removed from the LCD display once it has accepted user input).

The no option will cause the array controller to halt itself, providing the user an opportunity to resolve the issue. Selecting the yes option will result in the cache data being erased. Operation of the array controller will continue normally. Error 1.1 and 1.2: There is only one cache board in the array controller at present but it was previously configured with a second cache board that is now missing (dual cache module configuration). Error 2.1 and 2.2: A second cache board that contained valid data was removed from its original array controller and added to this array controller (dual cache module configuration). Error 2.3: A cache board that contained valid data was removed from its original array controller and added to this array controller (single cache module configuration). Return all cache boards to their original array controllers. Power up the systems without allowing any host I/O and wait for the cache data to be written to the drives. This will take a few minutes after the systems have finished the power on sequence. The systems can be powered off and cache boards moved to their new locations.



LCD message descriptions Message Type Description Action 72 CACHE ERROR <n> IGNORE? <=NO >=YES.

User Input During power up, data was found in the cache that could not be flushed to the drives. The reason is either because the data does not belong to this array controller (the cache board was moved from a different array controller) or the cache data is partial (the rest of the data is in another cache board that was removed from the array controller). This error could occur if cache boards are moved improperly.

The no option will cause the array controller to halt itself, providing the user an opportunity to resolve the issue. Selecting the yes option will result in the cache data being erased. Operation of the array controller will continue normally. Error 1.1 and 1.2: There is only one cache board in the array controller at present but it was previously configured with a second cache board that is now missing (dual cache module configuration). Error 2.1 and 2.2: A second cache board that contained valid data was removed from its original array controller and added to this array controller (dual cache module configuration). Error 2.3: A cache board that contained valid data was removed from its original array controller and added to this array controller (single cache module configuration). Return all cache boards to their original array controllers. Power up the systems without allowing any host I/O and wait for the cache data to be written to the drives. This will take a few minutes after the systems have finished the power on sequence. The systems can be powered off and cache boards moved to their new locations.

LCD Panel Codes


LCD message descriptions Message Type Description Action 73 CACHE HARDWARE BATTERIES MISSING.

Error The cache memory does not have its required batteries attached to it.

If the failure has occurred on the standby array controller, then remove the standby array controller, replace the cache modules, wait 10 seconds, and then reinsert the array controller insuring that it is fully seated in the chassis. If the failure has occurred on the active array controller, then wait until down-time is available. Power off the system, remove the array controller, replace the cache modules, and reinsert the array controller insuring it is fully seated in the chassis. Should the issue persist please contact HP support

80 REPLACEMENT DRIVE FOUND BOX #<n> BAY <n>

Informational A SCSI drive that was previously missing or failed has now been replaced with a working SCSI drive.

81 SMART DRIVE ALERT BOX #<n>, BAY <n>

Informational A SCSI drive may be close to failing. This was determined either by the drive firmware itself using SMART technology or by the array controller using monitor and performance testing.

The drive should be replaced as soon as possible.

82 DRIVE HOT ADDED BOX #<n>, BAY <n>

Informational A SCSI drive has been added to the system.



LCD message descriptions Message Type Description Action 83 DRIVE HOT REMOVED BOX #<n>, BAY <n>.

Informational A SCSI drive has been removed from the system.

84 DRIVE FAILURE BOX #<n>, BAY <n> 84

Error A SCSI drive in the system has failed. If the drive was part of a configured volume, then the state of the volume will depend on the fault tolerance used.

The drive should be replaced as soon as possible.

85 BAD DRIVE FRMWARE BOX #<n>, BAY <n>

Error A SCSI drive has been detected that has known bad firmware on it. Continued usage of this drive could result in drive failure, decreased performance or data loss.

Either the drive firmware should be updated or the drive should be replaced as soon as possible.

86 DRIVE POSITION CHANGE DETECTED

Informational The SCSI drives that make up a configured volume have been physically moved within the system. The array controller has updated its configuration information accordingly.

87 DRIVE POSITION CHANGE INVALID

Informational The SCSI drives that make up a configured volume have been physically moved in such a way that the array controller can no longer access the configured volume.

The system should be powered off and the drives restored to their original positions.

88 NON-HP DRIVE BOX #<n>, BAY <n>

Error A non-HP disk drive has been detected in a storage enclosure.

89 INVALID CONFIG BOX #<n>, BAY <n>

Error The indicated disk drive contains unrecognized configuration information from another system, and therefore will not be used.

100 VOLUME #<n> STATE OK

Informational The configured volume has returned to its normal operating state. This typically occurs after a rebuild operation has completed.

LCD Panel Codes


LCD message descriptions Message Type Description Action 101 VOLUME #<n> STATE FAILED

Error The configured volume has been failed because too many SCSI drives that it is composed of have failed exceeding the fault tolerance level. The data on the configured volume is no longer available.

102 VOLUME #<n> STATE INTERIM RECOVERY

Informational The array controller has failed one or more SCSI drives that the configured volume is composed of but no data loss has occurred because fault tolerance is allowing the data to be recovered.

The failed drives should be replaced as soon as possible.

103 VOLUME #<n> STATE REBUILDING.

Informational The configured volume is rebuilding data on a SCSI drive that replaced a previously failed drive

104 VOLUME #<n> STATE DISABLED.

Error The configured volume has been disabled because too many of the SCSI drives that it is composed of are missing.

Power off the system and then all attached storage enclosures. Unplug and reinsert all SCSI drives insuring they are fully seated in their bays. Check the cables connecting the system to any attached storage enclosures. Power on the attached storage enclosures and then the system.

105 VOLUME #<n> STATE EXPANSION ACTIVE

Informational The configured volume is currently performing a volume expansion operation.



LCD message descriptions Message Type Description Action 106 VOLUME #<n> STATE WAITING TO REBUILD

Informational The configured volume is waiting to start rebuilding data on a SCSI drive that replaces a previously failed drive. The rebuild may not have started yet because the array controller is already performing a rebuild on another configured volume.

107 VOLUME #<n> STATE WAITING TO EXPAND

Informational The configured volume is waiting to start a volume expansion operation. The expansion may have not started yet because another configured volume is undergoing expansion or a rebuild is occurring on the configured volume.

108 VOLUME #<n> STATE MISSING DRIVES

Error The configured volume is missing too many of the SCSI drives that it is composed of making it unusable. The volume will be disabled.

Power off the system and then all attached storage enclosures. Unplug and reinsert all SCSI drives insuring they are fully seated in their bays. Check the cables connecting the system to any attached storage enclosures. Power on the attached storage enclosures and then the system.

109 VOLUME #<n> STATE WRONG DRIVE REPLACED

Error The configured volume appears to have had known, good SCSI drives replaced instead of known, failed drives.

The system should be powered off and the good drives should be restored while the failed drives should be replaced.

LCD Panel Codes


LCD message descriptions Message Type Description Action 110 VOLUME #<n> EXPANSION DISABLED

Informational The volume expansion operation on the configured volume has been disabled. This may be because a rebuild operation is ongoing, another expansion is already running, or the cache memory is disabled due to a low battery. The expansion will start once the condition has been cleared.

111 VOLUME #<n> INITIALIZING PARITY

Informational The array controller is calculating and storing parity information for the configured volume and therefore performance may be lower until it completes.

112 VOLUME #<n> REBUILD FAILURE

Error The rebuild operation on the configured volume has failed.

If the volume is still operating in regenerative mode, remove the new SCSI drive that was added as a replacement for the original failed drive and replace it with a different new drive.

113 VOLUME #<n> EXPANSION FAILURE

Error The volume expansion operation on the configured volume has failed.

Run the Array Configuration Utility (ACU) and use it to determine the state of the volume. If the volume is still operational then it is possible to reattempt the operation.

114 VOLUME #<n> STATE DELETED

Informational The configured volume has been deleted and is no longer available. Volumes are deleted by using the Array Configuration Utility (ACU).

120 CONFIGURED VOLUMES <n>

Informational The specified number of configured volumes were detected at power up.



LCD message descriptions Message Type Description Action 121 NO VOLUMES DETECTED

Informational No configured volumes were detected at power up.

If there are supposed to be configured volumes, power off the system and then all attached storage enclosures. Unplug and reinsert all SCSI drives insuring they are fully seated in their bays. Check the cables connecting the system to any attached storage enclosures. Power on the attached storage enclosures and then the system.

122 NEW VOLUME(S) DETECTED has been updated.

Informational Configured volumes from another array controller were migrated to this array controller. The configuration information has been updated.

123 TOO MANY VOLUMES DETECTED

Error The array controller only supports a maximum of 32 configured volumes. More volumes then that were detected at power up. This typically occurs when migrating a set of volumes from one array controller to a different array controller that already has configured volumes on it. The migrated volumes have not been added.

Remove the migrated drives and run the Array Configuration Utility (ACU). Delete any unneeded volumes until the number of existing volumes plus the number of migrated volumes is 32 or less. Add the migrated drives back.

LCD Panel Codes


LCD message descriptions Message Type Description Action 125 ACCESS CONTROL CONFLICT DETECTED

Error A set of volumes have been migrated from one array controller to a different array controller that already has configured volumes on it. The migrated volumes have access controls defined for them that conflicts with the existing configuration. The access controls has been modified so as to allow the migration to proceed.

Run the Array Configuration Utility (ACU) to check the new access controls and modify them if needed.

126 ACCESS CONTROL RESOURCES EXCEEDED

Error A set of volumes have been migrated from one array controller to a different array controllers that already has configured volumes on it. The migrated volumes have access controls defined for them that conflicts with the existing configuration. The access controls has been modified so as to allow the migration to proceed.

Run the Array Configuration Utility (ACU) to check the new access controls and modify them if needed.

151 BEACON OFF Informational The array controller has deactivated its UID beacon.

201 ARRAY CONTROLLER TEMPERATURE OK

Informational The temperature sensor on the array controller indicates that the temperature which was previously exceeding the normal operating range is now back within the range.



LCD message descriptions Message Type Description Action 202 ARRAY CONTROLLER OVERHEATING

Error The temperature sensor on the array controller indicates that the array controller is starting to exceed the normal operating range.

Check all system fans and insure they are operating. Any failed fans should be replaced. Insure that there are drive blank cartridges in any empty drive bays of the system chassis. If only one array controller is inserted, insure that there are cover plates installed in the empty array controller bay and the Fibre Channel bay of the chassis.

203 ARRAY CONTROLLER OVERHEATED

Error The temperature sensor on the array controller indicates that the array controller has exceeded the safe operating range.

The system should be powered off as soon as possible to avoid hardware failure. Check all system fans and insure they are operating. Any failed fans should be replaced. Insure that there are drive blank cartridges in any empty drive bays of the system chassis. If only one array controller is inserted, insure that there are cover plates installed in the empty array controller bay and the Fibre Channel bay of the chassis.

204 ARRAY CONTROLLER DISABLED.

Error The array controller has been disabled due to a redundancy failure.

Remove the failed array controller, wait 10 seconds, and then reinsert the array controller insuring that it is fully seated in the chassis. Should the issue persist please contact HP support.

205 ARRAY CONTROLLER RESTARTING.

Informational The array controller has completed firmware cloning and will be restarted automatically.

LCD Panel Codes


LCD message descriptions Message Type Description Action 300 RECOVERY ROM AUTOFLASH STARTED

Informational Indicates that the array controller has detected that the firmware’s backup recovery ROM image is invalid and is copying the current active firmware image into the backup recovery ROM.

301 RECOVERY ROM AUTOFLASH DONE

Informational Indicates that the array controller has successfully completed the process of copying the current active firmware image into the backup recovery ROM.

302 RECOVERY ROM AUTOFLASH FAILED.

Error Indicates that the array controller failed to copy the current active firmware image into the backup recovery ROM. Recovery ROM support is disabled.

Remove the failing array controller, wait 10 seconds, and then reinsert the array controller insuring that it is fully seated in the chassis. The ROM autoflash process will be attempted again. Should the issue persist please contact HP support



LCD message descriptions Message Type Description Action 303 ROM CLONING STARTED

Informational Indicates that the two array controllers in the system do not have the same version of firmware on them. Therefore, one array controller’s version of the firmware will be copied on to the other array controller. Both controllers must be running the same version of firmware in order for controller redundancy to operate. If both array controllers are in the power up sequence, then the most recent version of firmware will be used. If one array controller has already completed the power up sequence and is now active, then its version of firmware will be used even if less recent.

304 ROM CLONING DONE

Informational Indicates that the two array controllers in the system have finished copying one array controller’s version of firmware to the other array controller. Both controllers must be running the same version of firmware in order for controller redundancy to operate.

305 ROM CLONING FAILED.

Error Indicates that the two array controllers in the system failed to copy one array controller’s version of firmware to the other array controller. Both controllers must be running the same version of firmware in order for controller redundancy to operate.

Remove the standby array controller, wait 10 seconds, and then reinsert the array controller insuring that it is fully seated in the chassis. The ROM cloning process will be attempted again. Should the issue persist please contact HP support.

LCD Panel Codes


LCD message descriptions Message Type Description Action 306 FIRMWARE FLASH STARTED

Informational Indicates that the array controller in the system has started the firmware flash process. Do not turn off power to the system until it has completed. This could take several minutes.

307 FIRMWARE FLASH DONE

Informational Indicates that the array controller in the system has completed the firmware flash process. It is now safe to turn off power to the system.

308 FIRMWARE FLASH FAILED

Error Indicates that the array controller in the system has failed the firmware flash process.

Attempt the flash process again. Should the issue persist, please contact HP support.

309 EMU FLASH STARTED Informational Indicates that the EMU in the system has started the firmware flash process. Do not turn off the power to the system until it has completed. This could take five minutes.

310 EMU FLASH DONE Informational Indicates that the EMU in an system has completed the firmware flash process. It is now safe to turn off power to the system.

311 EMU FLASH FAILED Error Indicates that the EMU in an system has failed the firmware flash process.


312 FIRMWARE FLASH STARTED ON BOX <n>

Informational Indicates that the specified storage enclosure has started the firmware flash process. Do not turn off the power to the system until it has completed. This could take five minutes.

313 FIRMWARE FLASH DONE ON BOX <n>

Informational Indicates that the specified storage enclosure has completed the firmware flash process.

314 FIRMWARE FLASH FAILED ON BOX <n>

Error Indicates that the specified storage enclosure has failed the firmware flash process.




LCD message descriptions Message Type Description Action 315 ISCSI MODULE FLASH STARTED

Informational Indicates that the array controller has detected out-of-date firmware on the iSCSI daughterboard and is updating the firmware. Do not turn off power to the system until it has completed. This could take several minutes.

316 ISCSI MODULE FLASH DONE

Informational Indicates that the array controller has completed updating the firmware on the iSCSI daughterboard. Restart the system to activate the new firmware.

Restart the system to activate the new iSCSI firmware before using iSCSI functionality.

317 ISCSI MODULE FLASH FAILED

Error Indicates that the array controller was unable to update the firmware on the iSCSI daughterboard.

Retry the operation. Contact HP support if the problem persists.

318 FAN FLASH STARTED ON BOX #<n>

Informational Indicates that the array controller has detected out-of-date firmware on a fan module in the indicated storage enclosure and is updating the firmware. Do not turn off power to the system until it has completed. This could take several minutes.

319 FAN FLASH DONE ON BOX #<n>

Informational Indicates that the array controller has completed updating the firmware on a fan module.

320 FAN FLASH FAILED ON BOX #<n>

Error Indicates that the array controller was unable to update the firmware on a fan module.

Retry the operation. Contact HP support if the problem persists.

321 BATTERIES LOW, FLASH REFUSED

Error The array controller was unable to proceed with a firmware flashing or cloning operation because the cache batteries are low and there is a risk of data loss if the operation fails.

Allow the controller to charge its batteries, and then retry the flash operation.

330 AUTO-UPGRADE IN PROGRESS

Informational The array controller has detected that firmware upgrades are needed to other system components and is preparing to perform the upgrade.

LCD Panel Codes


LCD message descriptions Message Type Description Action 331 AUTO-UPGRADE DONE

Informational The array controller has completed upgrading system components.

332 AUTO-UPGRADE FAILED

Error The array controller was unable to upgrade all system components.

Check previous error messages to determine which components failed to upgrade, and verify that these components are working properly. The upgrade can be retried the next time the system is rebooted.

333 AUTO-UPGRADE REQUIRES REBOOT

Informational The array controller completed upgrading system components and requires the system to be rebooted before the upgrades can take effect.

Reboot the system to complete the upgrade process.

400 STORAGE BOX #<n> FAN OK

Informational The specified storage enclosure indicates that one of its fans which previously had been failed or degraded is now operating normally.

401 STORAGE BOX #<n> FAN FAILED.

Error The specified storage enclosure indicates that one of its fans has failed. The storage enclosure and any devices in it may now be susceptible to overheating if corrective action is not taken.

Check all fans and insure they are operating. Any failed fans should be replaced

402 STORAGE BOX #<n> FAN DEGRADED.

Error The specified storage enclosure indicates that one of its fans is not operating at full efficiency. The fan may eventually fail.

Check all fans and insure they are operating. Any failed fans should be replaced.

403 STORAGE BOX #<n> FAN HOT INSERTED

Informational The specified storage enclosure indicates that a fan has been added.

404 STORAGE BOX #<n> FAN HOT REMOVED.

Informational The specified storage enclosure indicates that a fan has been removed.

405 STORAGE BOX #<n> TEMPERATURE OK

Informational The temperature sensor in the storage enclosure indicates that the temperature is now back in the normal operating range.



LCD message descriptions Message Type Description Action 406 STORAGE BOX #<n> OVERHEATING

Error The temperature sensor in the storage enclosure indicates that the enclosure is starting to exceed the normal operating range.

Check all fans and insure they are operating. Any failed fans should be replaced. Insure that there are drive blank cartridges in any empty drive bays in the enclosure. If the enclosure is an MSA1000 and only one array controller is inserted, insure that there are cover plates installed in the empty array controller bay and the Fibre Channel bay in the chassis.

407 STORAGE BOX #<n> OVERHEATED

Error The temperature sensor in the storage enclosure indicates that the enclosure has exceeded the safe operating range.

The system should be powered off as soon as possible and immediately after that, the enclosure should be powered off, to avoid hardware failure. Check all fans and insure they are operating. Any failed fans should be replaced. Insure that there are drive blank cartridges in any empty drive bays in the enclosure. If the enclosure is an MSA1000 and only one array controller is inserted, insure that there are cover plates installed in the empty array controller bay and the Fibre Channel bay in the chassis.

408 STORAGE BOX #<n> POWER SUPPLY OK

Informational The specified storage enclosure indicates that one of its power supplies which previously had been failed is now operating normally.

LCD Panel Codes


LCD message descriptions Message Type Description Action 409 STORAGE BOX #<n> POWER SUPPLY FAILED

Error The specified storage enclosure indicates that one of its power supplies has failed.

Check all power supplies and insure they are operating. Any failed power supplies should be replaced.

410 STORAGE BOX #<n> POWER SUPPLY ADDED

Informational The specified storage enclosure indicates that a power supply has been added.

411 STORAGE BOX #<n> POWER SUPPLY REMOVED

Informational The specified storage enclosure indicates that a power supply has been removed.

412 STORAGE BOX #<n> EMU NOT RESPONDING

Error The specified storage enclosure is not responding to commands.

Insure the storage box is powered on. Insure all cables are connected securely. Power off the system and the storage box. Power on the storage box first and then the system. Should the issue persist, please contact HP support.

413 STORAGE BOX #<n> EMU VERSION <version>

Informational The version of the firmware running on the EMU. This is only displayed for the internal EMU of the system. It is not displayed for externally connected storage boxes.

414 STORAGE BOX HOT REMOVED

Informational A HP StorageWorks SCSI expansion storage enclosure has been removed from the system.

415 STORAGE BOX #2 OR #3 HOT ADDED

Informational A HP StorageWorks SCSI expansion storage enclosure has been hot-added to the system.

500 INITIALIZING PCI SUBSYSTEM

Informational The array controller’s PCI subsystem is being initialized as part of the power up sequence.



LCD message descriptions Message Type Description Action 501 PCI SUBSYSTEM HARDWARE FAILURE

Error The array controller’s PCI subsystem has encountered a critical error during the power up sequence.


502 PCI BRIDGE ASIC SELF TEST FAILURE

Error The array controller’s PCI bridge ASIC has encountered a critical error during the power up sequence.


510 INITIALIZING FIBRE SUBSYSTEM

Informational The array controller’s Fibre Channel subsystem is being initialized as part of the power up sequence.

512 ECC CORRECTED MEMORY ERROR SEEN

Error The array controller has detected an uncorrectable ECC error in the data cache memory.

Contact HP Support.

513 UNCORRECTED ECC MEMORY ERROR SEEN

Error The array controller has detected an uncorrectable error in the ECC memory on the memory cache board.

Remove the failed array controller and replace the memory cache board with a new one.

514 FIBRE SWITCH HARDWARE FAILURE

Error The MSA SAN Switch 2/8 that is installed in the MSA1000 failed to establish a connection with the array controller over Fibre Channel.

Remove the MSA Fabric Switch 6 switch, wait one minute and then reinsert it insuring it is fully seated in the chassis. Wait one minute and check the LCD to see if a new copy of this error message is created. The service indicator LED on the back of the switch should turn solid green if the switch is operating normally. The service indicator LED will flash amber if it has failed again. Should the issue persist please contact HP support.

LCD Panel Codes


LCD message descriptions Message Type Description Action 515 FIBRE DEVICE HARDWARE FAILURE

Error The Fibre Channel device, which is installed in the MSA1000 Fibre Channel bay was not recognized by the array controller.

Verify the Fibre Channel device is supported by the MSA1000 by checking the documentation that came with it. If it is supported then remove the Fibre Channel device, wait one minute and then reinsert it insuring it is fully seated in the chassis. Wait one minute and check the LCD to see if a new copy of this error message is created. The service indicator LED on the back of the switch should turn solid green if the device is operating normally. The service indicator LED will flash amber if it has failed again. Should the issue persist, please contact HP support.

516 FIBRE SUSBYSTEM LINK FAILURE

Error There is no active Fibre Channel connection to this array controller (Laser OFF). If the Fibre Channel connection is a direct-connect from an HBA to the MSA, this message is expected when the server is powered off or restarted.

Power on the server and load the HBA drivers. If the status does not change to OK, check cables, Fibre Channel bay board, SFP, and HBA.

517 FIBRE SUBSYSTEM LINK OK

Informational There is an active Fibre Channel connection to this array controller (Laser On). This message is only displayed when preceded by message 516.

518 PERSISTENT MEM ENABLED

Informational Global variables such as system prompts and profile information remain persistent in cache over power cycles of the system. This message is displayed each time the system is powered up.

521 ISCSI PARAM LOAD ERROR

Error An error occurred while programming iSCSI configuration to the iSCSI hardware.

Contact HP support if the problem persists.

522 INITIALIZING ISCSI SUBSYSTEM

Informational The iSCSI subsystem is being initialized as part of the power on sequence.



LCD message descriptions Message Type Description Action 523 LOADING ISCSI PARAMS

Informational The iSCSI configuration is being loaded into the iSCSI hardware as part of the power on sequence.

524 ISCSI MODULE HARDWARE FAILURE

Error The array controller has detected a hardware failure in the iSCSI daughterboard.

Contact HP support.

525 ISCSI MODULE BIST FAILED

Error The iSCSI daughterboard has detected a failure during its Built-in Self Test (BIST).

Contact HP support.

526 ETHERNET MODULE DETECTED

Informational A 2-Port Ethernet iSCSI module has been inserted or detected during POST.

527 ETHERNET MODULE MISSING

Error No 2-Port Ethernet iSCSI module was detected during POST. Network connectivity is unavailable.

Insert a 2-Port Ethernet iSCSI module into the appropriate slot in the rear of the chassis.

528 ETHERNET MODULE INVALID

Error The module in the Ethernet module bay is not a valid 2-Port Ethernet iSCSI module, or the module has failed.

Verify that the module is inserted properly into the bay. If the problem persists, replace the module.

600 INITIALIZING TARGET-BASED MGMT

Informational The Target-Based Management subsystem is being initialized as part of the power on sequence.

601 PORT <n> LINK FAILURE

Error The system has detected a link failure on the indicated GBE port.

Check the network cable attached to the port.

602 PORT <n> LINK OK <speed> Mb/s

Informational The system has detected an active link on the indicated GBE port.

603 PORT <n> IP <ip> Informational The management IP address on the indicated port has been changed, and the new address is displayed for user reference.

Check that a DHCP server exists on your network, or reconfigure Target-Based Management to use a static IP address.

604 PORT <n> DHCP FAILED

Error The system has failed to obtain an IP address for the management port via DHCP, and will fall back to zeroconf IP address.

605 MANAGEMENT PORT <n> ENABLED

Informational The system has enabled management access through the indicated port as part of the power on sequence or due to a hardware failure on the configured port.

LCD Panel Codes


LCD message descriptions Message Type Description Action 606 MANAGEMENT PORT <n> DISABLED

Informational The system has disabled management access through the indicated port.

607 NO MANAGEMENT HARDWARE FOUND

Error The array controller is unable to locate any Ethernet hardware that can be used to provide management access. Target-Based Management functionality is disabled.

Contact HP support.

608 PORT <n> <ip> CONFLICT

Error The system has detected an IP address conflict with another device on the network.

Reconfigure the system to use an unused IP address, or remove the conflicting device from the network.

611 PROCESSOR REV <n> Informational The array controller is displaying the detected system processor revision.

612 PORT <n> 10 Mb/s NOT SUPPORTED

Error The array controller has detected a 10 Mb/s link on the indicated Ethernet port. The MSA1510i does not support 10 Mb/s, and so communication with this port is not possible.

Connect the port to a switch capable of 100 Mb/s or 1000 Mb/s.

