HP 3PAR StoreServ 7000
Installation, Startup and
Break Fix
Learner Guide
HP ServiceOne
Rev. 14.1
Course : 00722456
HP 3PAR StoreServ 7000
Installation, Startup and
Break Fix
Learner Guide
HP ServiceOne
Rev. 14.1
Course : 00722456
 Copyright 2013 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.
HP 3PAR StoreServ 7000 Installation, Startup and Break Fix
Lab Guide
November 2013
Contents
Course Introduction
Course Objectives ................................................................................................. 1
Agenda .................................................................................................................. 3
Day 1: .................................................................................................................... 3
Day 2: .................................................................................................................... 5
Day 3: .................................................................................................................... 6
Module 1: HP 3PAR StoreServ Product Family Overview
Module Objectives ................................................................................................. 1
HP 3PAR StoreServ Products ................................................................................ 2
HP 3PAR Hardware—Four Simple Building Blocks................................................ 3
HP 3PAR Software components ............................................................................ 4
HP 3PAR virtualization advantage ......................................................................... 7
HP 3PAR ASIC ...................................................................................................... 8
3PAR Hardware Architecture ................................................................................. 9
Persistent Write-Cache Mirroring ......................................................................... 10
Learning check ..................................................................................................... 11
Module 2: HP 3PAR StoreServ 7000 Hardware Components
Objectives.............................................................................................................. 1
3PAR StoreServ 7000 Specification....................................................................... 2
HP 3PAR StoreServ 7000 Hardware Building Blocks............................................. 3
3PAR StoreServ 7000 controller enclosure ............................................................ 4
3PAR StoreServ 7000 controller Serial Number..................................................... 6
3PAR StoreServ 7000 controller ............................................................................ 7
HP 3PAR StoreServ 7000 controller ports ............................................................. 8
HP 3PAR StoreServ 7000 Host Connectivity Options .......................................... 10
HP 3PAR StoreServ 74x0 4-node System ........................................................... 12
Controller Node Block Diagram ........................................................................... 13
HP 3PAR 7000 disk enclosure M6710 ................................................................. 14
HP 3PAR 7000 disk enclosure M6720 ................................................................. 16
Drive Specification Overview ............................................................................... 17
HP 3PAR SSD Drive Options ............................................................................... 18
HP 3PAR 7200 maximum Configurations ............................................................ 19
HP 3PAR 7400 2-node maximum configurations ................................................. 20
HP 3PAR 7400 4-node max Configurations ......................................................... 21
HP 3PAR 7450 maximum configurations ............................................................. 22
Recommended hardware configuration steps ...................................................... 23
Recommended Configuration Rules .................................................................... 25
HA enclosure vs. HA drive ................................................................................... 27
HA enclosure ....................................................................................................... 28
Lab 1 Exercise 1-2:.............................................................................................. 29
Enclosure labeling rules....................................................................................... 30
Enclosure color coding ........................................................................................ 31
Rev. 14.1
i
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 SAS Backend cabling (Node 0/1) ................................................ 32
HP 3PAR 7000 SAS backend cabling (Node 2/3) ................................................ 35
HP 3PAR 7000 SAS backend cabling 4N6E ........................................................ 38
Lab 1 Exercise 3-4............................................................................................... 40
Service Processor overview ................................................................................ 41
SPOCC ............................................................................................................... 42
Using SSH to access SPMAINT .......................................................................... 43
Guided Maintenance ........................................................................................... 44
Learning check .................................................................................................... 45
Module 3: HP 3PAR StoreServ7000 Software
Objectives.............................................................................................................. 1
HP 3PAR 7000 Software Suites ............................................................................. 2
HP 3PAR 7000 Software........................................................................................ 4
HP 3PAR StoreServ 7000 Software Licensing ....................................................... 6
HP 3PAR Management Console ............................................................................ 7
HP 3PAR SmartStart for the StoreServ 7000 ......................................................... 8
Learning check ...................................................................................................... 9
Module 4: HP 3PAR StoreServ 7000 Installation and Setup
Objectives.............................................................................................................. 1
Plan and prepare the Installation ........................................................................... 2
Service Delivery Guide .......................................................................................... 3
Precautions ........................................................................................................... 4
HP 3PAR StoreServ 7000 Site Readiness and Pre Checks ................................... 5
Network connection ............................................................................................... 6
Installation and Setup of the Service Processor ..................................................... 7
Physical Service Processor ................................................................................... 7
Installation and setup of the Service Processor ..................................................... 9
Virtual Service Processor ...................................................................................... 9
Set up a Virtual Service Processor (VSP) ............................................................ 10
Configure IP address in a Non-DHCP Environment .............................................. 11
Final steps after deploying ................................................................................... 12
Setting up the HP StoreServ 7000 by using SmartStart ....................................... 13
SmartStart for HP 3PAR StoreServ 7000 ............................................................. 13
Installing HP 3PAR SmartStart ............................................................................ 14
SmartStart sections and subsections ................................................................... 15
Configuration and Installation .............................................................................. 16
Using SmartStart to configure storage ................................................................. 18
Setting up the Service Processor ......................................................................... 19
Setting up the storage system ............................................................................. 20
Configure Fibre Channel host .............................................................................. 21
Configure an iSCSI host ...................................................................................... 22
Start to configure and setup data storage ............................................................ 23
Troubleshooting ................................................................................................... 24
Behind the Scene of SmartStart .......................................................................... 25
Lab 2 Exercise 1–4: ............................................................................................. 26
Learning check .................................................................................................... 27
ii
Rev. 14.1
Contents
Module 5: HP 3PAR StoreServ Architecture and Concepts
Objectives.............................................................................................................. 1
HP 3PAR Virtualization – the Logical View............................................................. 2
Why are Chunklets so Important? .......................................................................... 4
Common Provisioning Groups (CPG) .................................................................... 5
HP 3PAR Virtualization concepts ........................................................................... 6
How a region maps to a virtual volume .................................................................. 7
HP 3PAR virtualization concepts............................................................................ 8
Host connection ..................................................................................................... 9
Host Connection - Fabric zoning.......................................................................... 10
HP 3PAR Persistent Ports .................................................................................... 11
HP 3PAR World Wide Name ................................................................................ 12
HP Flat SAN Architecture .................................................................................... 13
HP 3PAR Priority Optimization ............................................................................. 14
3PAR Data at Rest Encryption ............................................................................. 19
Learning check .................................................................................................... 26
Module 6: HP 3PAR StoreServ System Management
Objectives.............................................................................................................. 1
HP 3PAR – Management Options.......................................................................... 2
HP 3PAR Management Console ............................................................................ 3
Create CPG(s) ....................................................................................................... 4
Create Virtual Volume(s) ........................................................................................ 5
HP 3PAR Host Explorer ......................................................................................... 7
Export Virtual Volume(s) ........................................................................................ 8
HP 3PAR User management ................................................................................. 9
Learning check .................................................................................................... 10
Module 7: Upgrade of Hardware and Software Components
Objectives.............................................................................................................. 1
Controller Node Upgrade ....................................................................................... 2
Disk Enclosures Upgrade ...................................................................................... 4
Disk Drive Upgrade ............................................................................................... 5
Upgrading PCIe Adapter ........................................................................................ 6
Updating the HP 3PAR OS and Service Processor ................................................ 7
Lab 3, Lab 4, Lab 5................................................................................................ 8
Lab 3: Storage Configuration ................................................................................. 8
Lab 4: CLI Commands ........................................................................................... 8
Lab 5: System upgrade.......................................................................................... 8
Learning check ...................................................................................................... 9
Rev. 14.1
iii
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Module 8: Maintenance Tools and Resources
Objectives.............................................................................................................. 1
Standard user names and passwords.................................................................... 2
Best security practices ........................................................................................... 3
HP 3PAR Remote Support..................................................................................... 4
HP proactive resources ......................................................................................... 6
HP 3PAR STaTS .................................................................................................... 8
STaTS Display tab ................................................................................................. 9
STaTS Sites tab ................................................................................................... 10
STaTS Notify tab................................................................................................... 11
STaTS Support tab ............................................................................................... 11
STaTS Admin....................................................................................................... 12
STaTS Reports .................................................................................................... 12
STaTS Sales Upgrade ......................................................................................... 13
Collecting configuration information from STaTs .................................................. 14
STaTS Data Overview—Configuration Data ........................................................ 15
STaTS Data Overview—Performance data .......................................................... 16
STaTS Data Overview—Event Data .................................................................... 17
STaTS Data Overview—Diagnostic data ............................................................. 18
STaTS Data Overview—Sample log types ........................................................... 19
Service Processor Maintenance Mode ................................................................ 20
Events, Alerts and Local Notification .................................................................... 24
Alerts overview ............................................................................................. 24
Alert message codes .................................................................................... 25
Sample InForm message .............................................................................. 26
Monitoring and managing InForm OS alerts ........................................................ 27
Setting system alerts ........................................................................................... 28
Viewing alerts using InForm GUI ......................................................................... 29
Monitoring and managing the event log ............................................................... 30
Automated Over-Subscribed System Alerts ......................................................... 31
Local Notification ................................................................................................. 32
Setting up Local Notification ......................................................................... 33
Learning check .................................................................................................... 34
Module 9: HP 3PAR StoreServ 7000 Storage Troubleshooting
Objectives.............................................................................................................. 1
Powering Off/On the Storage System .................................................................... 2
Troubleshooting ..................................................................................................... 3
Repair and Replace System Components ........................................................... 10
Repair and Replace System Components .................................................... 12
Disk Drive Repair................................................................................................. 13
Controller Node Repair ........................................................................................ 15
SFP Repair .......................................................................................................... 17
Replacing an I/O Module ..................................................................................... 19
Replacing a Power Cooling Module ..................................................................... 21
Replacing a Battery inside a Power Cooling Module ............................................ 22
Controller Node Internal Component Repair ........................................................ 23
Console mode access ......................................................................................... 25
Node Rescue....................................................................................................... 26
Lab 6: HP 3PAR Service Processor Onsite Customer Care (SPOCC) usage ...... 27
iv
Rev. 14.1
Contents
Lab 7: Node Rescue ............................................................................................ 27
Lab 8: Manage Events and Alerts ........................................................................ 27
Lab 9: De-installation of a 3PAR array ................................................................. 27
Lab 10: Installing the StoreServ 7000 without SmartStart .................................... 27
Lab 11: Configure the Storage System ................................................................ 27
Learning check .................................................................................................... 28
Module 10: HP 3PAR StoreServ File Controller
Objectives.............................................................................................................. 1
HP 3PAR StoreServ File ........................................................................................ 2
3PAR StoreServ file controllers .............................................................................. 3
Manage storage efficiently ..................................................................................... 5
Efficient deduplication ............................................................................................ 6
Secure your files .................................................................................................... 7
Your files are continuously available ...................................................................... 8
Automated disaster recovery ................................................................................. 9
Reduce the impact of maintenance ..................................................................... 10
Learning check ..................................................................................................... 11
Module 11: HP StoreFront Mobile Access for 3PAR StoreServ
Objectives.............................................................................................................. 1
HP StoreFront Mobile Access for 3PAR StoreServ ................................................ 2
Converged Storage Management .......................................................................... 2
Learning check ...................................................................................................... 4
Rev. 14.1
v
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
vi
Rev. 14.1
HP 3PAR StoreServ 7000 Installation,
Startup, and Break Fix
Introduction
Course Objectives
After completing this course you should be able to:



Describe the member and how to position the storage
systems of the HP 3PAR StoreServ product family
Identify the HP 3PAR StoreServ 7000 hardware components
and describe their function
Configure a HP 3PAR StoreServ 7000 storage system based
on the configuration rules

Install and upgrade the hardware components

Setup and upgrade the software components



Understand the HP 3PAR StoreServ architecture and
concept
Demonstrate the base functionality of the storage system
Use provided tools and resources to ease the installation and
for base troubleshooting
Introduction
Welcome to HP 3PAR StoreServ 7000 Installation, Startup and Break Fix
Course
This three day VILT/Virtual-LAB training provides the theoretical as well as the
practical knowledge and experience needed to install HP 3PAR StoreServ 7000
storage systems and identifies and fixes problems on Field Replaceable Unit
(FRU) level. The topics covered include product and documentation overview as
well as practical approaches to manage HP 3PAR systems to perform the
Customer orientation session as part of the installation.
Prerequisites
To benefit from this training, the service engineer should have the following
knowledge:
Rev. 14.1
•
Windows system management knowledge
•
Knowledge of storage technologies - SCSI, Fibre Channel, SAN
switches and SAN networking.
Intro –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Objectives
After completing this course you should be able to:
Intro –2
•
Describe the member and how to position the storage systems of the
HP 3PAR StoreServ product family
•
Identify the HP 3PAR StoreServ 7000 hardware components and
describe their function
•
Configure a HP 3PAR StoreServ 7000 storage system based on the
configuration rules
•
Install and upgrade the hardware components
•
Setup and upgrade the software components
•
Understand the HP 3PAR StoreServ architecture and concept
•
Demonstrate the base functionality of the storage system
•
Use provided tools and resources to ease the installation and for base
troubleshooting
Rev. 14.1
Introduction
Agenda
Day 1:
HP 3PAR StoreServ Product overview and hardware setup

HP 3PAR StoreServ product family overview

HP 3PAR StoreServ 7000 hardware components

Lab1 (Exercise 1 – 4) Hardware familiarization and cabling

HP 3PAR StoreServ7000 Software
HP 3PAR StoreServ 7000 installation and setup

Installation planning and preparation

Installation and setup of the Service Processor

Setup the HP StoreServ 7000 by using SmartStart

Lab 2 (Exercise 1 – 4) Setup the HP StoreServ 7000 by using
SmartStart
Day 1 agenda
During the first day of the training, the lecture, hands-on time, and worksheet
exercise provide you with the information and skills required to successfully install
HP 3PAR StoreServ 7000 storage system.
HP 3PAR StoreServ product family overview

HP 3PAR StoreServ Products

Hardware and Software Building Blocks

HP 3PAR StoreServ Architectural Concepts
HP 3PAR StoreServ 7000 hardware components

Specification

HP 3PAR StoreServ Hardware Building Blocks

Drive Specification

HP 3PAR StoreServ 7000 controller

HP 3PAR StoreServ 7000 controller 4 node configuration

HP 3PAR StoreServ 7000 disk chassis

Backend cabling

System Configuration Rules

Service Processor (physical and virtual)

Service Processor software
HP 3PAR StoreServ 7000 Software
Rev. 14.1
Intro –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix

HP 3PAR 7000 Software Suites

HP 3PAR StoreServ 7000 Licensing

HP 3PAR SmartStart

SPOCC
HP 3PAR StoreServ 7000 installation and setup
Intro –4

Plan and Prepare the Installation

Network Connection

Installation and Setup of physical Service Processor

Installation and Setup of virtual Service Processor

SmartStart to configure the Service Processor (VSP) and StoreServ system
Rev. 14.1
Introduction
Day 2:
HP 3PAR StoreServ architecture and concept
Upgrade of hardware and software components

Lab 3 Configure the Storage System

Lab 4 CLI Commands

Lab 5 System upgrade
Note:


The exact start time of the labs may differ, because of the
different speed of the groups.
Most labs can be only done if the previous lab was finished.
Day 2 agenda
During the second day of the training, the lecture and hands-on time provide you
with the information and skills required to successfully perform a customer
orientation session and be able to manage a HP 3PAR StoreServ system without
additional software products installed. The hardware and software upgrade
procedures are also covered on this day.
HP 3PAR StoreServ architecture and concept

HP 3PAR Virtualization Concept

Host Connection
HP 3PAR StoreServ system management

HP 3PAR – Management Options

HP 3PAR Management Console

HP 3PAR Host Explorer

3PAR User management
Upgrade of hardware and software components
Rev. 14.1

Upgrade HP 3PAR StoreServ 7000 hardware components (disks, disk
chassis, nodes, PCIe adapter)

Updating the HP 3PAR OS and Service Processor

Changing system setting using SPOCC
Intro –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Day 3:
Maintenance / break fix tools and resources

Lab 6 HP 3PAR Service Processor Onsite Customer Care

Lab 7 Node Rescue

Lab 8 Manage Events and Alerts

Lab 9 De-installation of an HP 3PAR array

Lab 10 Installing the StoreServ 7000 without SmartStart

Lab 11 Configure the Storage System (without SmartStart)
Day 3 agenda
During the third day of the training, the lecture and hands-on time provide you with
the information and skills required to successfully perform maintenance activities
at FRU level. This includes how the failing components can be identified and what
is the proper replacement procedure for the failing component.
Maintenance tools and resources

Usernames and password

HP 3PAR Remote Support overview

STaTS usage

Alerts and Events
HP 3PAR StoreServ 7000 system Troubleshooting
Intro –6

Powering Off/On the Storage System

Troubleshooting Methods

Guided Maintenance

Repair and Replace System Components

Node rescue
Rev. 14.1
HP 3PAR StoreServ Product Family
Overview
Module 1
Module Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the differences of the HP 3PAR StoreServ family members

Identify HP 3PAR storage system hardware building Blocks and software
components

Describe the high level architectural concept of HP 3PAR storage systems
1 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR StoreServ Products
The max addressable raw capacities per System are:
1 –2
7200
250TB
7400
864TB
7450
96TB
10400
800TB
10800
1600TB
Rev. 14.1
HP 3PAR StoreServ Product Family Overview
HP 3PAR Hardware—Four Simple Building
Blocks
Service Processor:
With the HP 3PAR StoreServ 7000 array, a virtual Service Processor is included
with the 3PAR Base Operating System. Each HP 3PAR StoreServ 7000 requires
its own Service Processor. The Service Processor can be installed on a VMware
system, provided by the customer, meeting the following specifications.

VMware vSphere 4.1, 5.0, or 5.1

Server listed in VMware Compatibility Guide and with the following features

2GB RAM (minimum)

320GB free disk space

DVD ROM or DVD RW

1Gb Ethernet port
The customer also has the option to choose a physical Service Processor.
Rev. 14.1
1 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR Software components
HP 3PAR OS Software Suite functionality and features for HP 3PAR
StoreServ 7000 arrays (Base license, drive based)
1 –4

HP 3PAR Thin Provisioning: With HP 3PAR Thin Provisioning, capacity is
dedicated and configured autonomic, just-in-time, and without active
management. Rather than create separate pools of storage, the software
creates one pool from which capacity is dedicated only as data is actually
written. HP 3PAR Thin Provisioning uses a fine-grained, 16 KB allocation unit,
to increase system efficiency.

HP 3PAR Thin Conversion: HP 3PAR Thin Conversion Software leverages
the zero-detection capabilities within the HP 3PAR Gen3 ASIC to drive the
conversion of inefficient, "fat" volumes on legacy arrays to more efficient,
higher utilization "thin" volumes on HP 3PAR Storage Systems.

HP 3PAR Thin Persistence: HP 3PAR Thin Persistence Software allows thin
volumes on the HP 3PAR Storage System to stay as lean and efficient as
possible. It does this by leveraging the HP 3PAR Gen3 ASIC to reclaim
unused space associated with deleted data-simply, quickly, and nondisruptively.

HP 3PAR Thin Copy Reclamation: The HP 3PAR Thin Copy Reclamation
feature keeps your storage lean and efficient by reclaiming unused space
resulting from the deletion of virtual copy snapshots associated with virtual
copy and remote copy volumes

HP 3PAR Autonomic Rebalance: Non-disruptively distributes and
redistributes application volumes across tiers to align application requirements
with data QoS levels on demand. Analyzes how volumes use physical disks
and automatically makes intelligent, non-disruptive adjustments to help ensure
optimal volume performance and capacity utilization.
Rev. 14.1
HP 3PAR StoreServ Product Family Overview

HP 3PAR System Tuner: System Tuner maintains peak HP 3PAR StoreServ
Storage performance autonomically and by not disruptively detecting and
resolving performance bottlenecks and storage hotspots. HP 3PAR OS
software autonomic spreads volumes evenly and widely across all available
resources to deliver balanced performance.

HP 3PAR Management Console: The unified HP 3PAR InForm Management
Console simplifies storage management by placing everything you need to
administer and optimize your entire HP 3PAR Utility Storage deployment in a
single window, including remote replication to disaster recovery sites.


EVA to 3PAR Online Import (180 days Online import license): Online
Import allows existing EVA customers to move data quickly and easily from
HP EVA Storage to HP 3PAR StoreServ Storage using Command View EVA.

HP 3PAR Host Explorer: Host Explorer is an autonomic storage
management tool that establishes secure communication channels between
storage and hosts.

HP 3PAR SmartStart: SmartStart simplifies the installation of HP 3PAR
StoreServ 7000 Storage and gets you up and running in six quick and easy
steps. An easy to follow wizards helps set up your storage—including
installation of the HP 3PAR Management Console, HBA drivers, and HP 3PAR
Host Explorer.

HP 3PAR Virtual Service Processor: With the HP 3PAR StoreServ 7000
array, a virtual Service Processor is included with the 3PAR Base Operating
System. Each HP 3PAR StoreServ 7000 requires its own Service Processor.
The Service Processor can be installed on a VMware system (or Hyper-V
system later in 2013).

HP 3PAR Multipath Software for Windows 2003
HP 3PAR Data Optimization Software Suite (drive based license)

HP 3PAR Adaptive Optimization

HP 3PAR Dynamic Optimization

HP 3PAR Peer Motion
HP 3PAR Replication Software Suite (drive based license)

HP 3PAR Virtual Copy

HP 3PAR Remote Copy

HP 3PAR Peer Persistence
HP 3PAR Security Software Suite (drive based license)
Rev. 14.1

HP 3PAR Virtual Domains

HP 3PAR Virtual Lock
1 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR Reporting Software Suite (system based license)

HP 3PAR System Reporter

HP 3PARinfo
HP 3PAR Application Software Suite for Vmware (system based license)

HP 3PAR Recovery Manager for VMware vSphere

HP 3PAR Management Plug-in for VMware vCenter

HP 3PAR VASA provider

HP 3PAR Host Explorer for VMware vSphere
HP 3PAR Application Software Suite for Exchange (system based license)

HP 3PAR Recovery Manager for Exchange

HP 3PAR VSS hardware provider
HP 3PAR Application Software Suite for SQL (system based license)

HP 3PAR Recovery Manager for SQL

HP 3PAR VSS hardware provider
HP 3PAR Application Software Suite for Oracle (system based license)

1 –6
HP 3PAR Recovery Manager for Oracle
Rev. 14.1
HP 3PAR StoreServ Product Family Overview
HP 3PAR virtualization advantage
HP 3PAR virtualization advantage
By using chunklets instead of the whole drive, the 3PAR array is much more
flexible in creating LUNs, spare space, and different RAID levels on the same disk
drives. By using distributed sparing and disk leveling across all available disk
drives, of the same type, capacity utilization and performance is also much more
effective than on traditional arrays. All the features, like Thin Provisioning, System
Tuning, Automatic Rebalance, are based on this design.
Rev. 14.1
1 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR ASIC
Thin Build in Zero Detection
The HP 3PAR ASICs feature a fat-to-thin volume conversion algorithm that is built
into silicon. This built-in, fat-to-thin processing capability works with HP 3PAR
Software to enable users to take “fat” provisioned volumes on legacy storage and
convert them to “thin” provisioned volumes on the system, inline and nondisruptively. During this process, allocated-but-unused capacity within each data
volume is initialized with zeros. The ASICs use built-in zero detection capability to
recognize and virtualize blocks of zeros “on the fly” to drive these conversions
while maintaining high performance levels.
Fast RAID 10, 50 and 60
The XOR engine and the Rapid RAID rebuild functionality are built into the ASIC,
for fastest possible performance. An additional Data Integrity Check is
implemented on the disk drive by fusing extra blocks to store a CRC Logical Block
Guard. This CRC value is checked before every write and during every read.
Tightly-Coupled Cluster
All HP 3PAR Storage Systems feature a unique Mesh-Active controller technology
as part of a next-gen architecture designed for virtual and cloud data centers.
Unlike legacy “active-active” controller architectures—where each LUN (or volume)
is active on only a single controller—this Mesh-Active design allows each LUN to
be active on every mesh controller in the system. This design delivers robust, loadbalanced performance and greater headroom for cost-effective scalability,
overcoming the tradeoffs typically associated with modular and monolithic storage.
The high-speed, full-mesh, passive system backplane joins multiple Controller
Nodes to form a cache-coherent, active-active cluster.
Mixed Workload
Unlike legacy architectures that process I/O commands and move data using the
same processor complex, the HP 3PAR Controller Node design separates the
processing of control commands from data movement. This innovation eliminates
the performance bottlenecks of existing platforms when serving competing
workloads like OLTP and data warehousing simultaneously from a single
processing element.
1 –8
Rev. 14.1
HP 3PAR StoreServ Product Family Overview
3PAR Hardware Architecture
3PAR Hardware Architecture
The HP 3PAR Architecture was designed to provide cost-effective, single-system
scalability through a cache-coherent, multi-node, clustered implementation. This
architecture begins with a multi-function node design and, like a modular array,
requires just two initial Controller Nodes for redundancy.
However, unlike traditional modular arrays, an optimized interconnect is provided
between the Controller Nodes to facilitate Mesh-Active processing. With MeshActive controllers, volumes are not only active on all controllers, but they are
autonomically provisioned and seamlessly load-balanced across all system’s
resources to deliver high and predictable levels of performance. The interconnect
is optimized to deliver low latency, high-bandwidth communication and data
movement between Controller Nodes through dedicated, point-to-point links and a
low overhead protocol which features rapid inter-node messaging and
acknowledgement.
For scalability beyond two Controller Nodes, the HP 3PAR StoreServe 7400 Array
can have up to four Nodes, using cables to interconnect the nodes.
Rev. 14.1
1 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Persistent Write-Cache Mirroring
The HP 3PAR Persistent Cache Software allows systems to maintain a high level
of performance and availability during node failure conditions, and during hardware
and software upgrades.
This feature allows the host to continue to write data and receive
acknowledgments from the system if the backup node is unavailable. Persistent
Cache automatically creates multiple backup nodes for logical disks that have the
same owner. Persistent Cache also maintains service levels by preserving writecaching through rapidly re-mirroring cache to the other nodes in the cluster in the
event of a cache or controller node failure.
1 –10
Rev. 14.1
HP 3PAR StoreServ Product Family Overview
Learning check
1. What are the features of the HP 3PAR ASIC?
_________________________________________________
_________________________________________________
_________________________________________________
_________________________________________________
_________________________________________________
2. Which StoreServ system cannot be configured using HDD (Hard disk drive)?
_________________________________________________
3. What is the minimum number of nodes for a HP 3PAR StoresServ 10800
storage system?
_________________________________________________
4. How many nodes are required to take advantage of HP 3PAR Persistent
Cache functionality?
________________________________________________
Rev. 14.1
1 –11
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
1 –12
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware
Components
Module 2
Objectives
After completing this module you should be able to:
Rev. 14.1

Identify the HP 3PAR StoreServ hardware components

Describe the functionality and characteristic of the individually components

Demonstrate that you can proper cable the backend of the HP 3PAR
StoreServ storage system.

Setup inter node links

Configure the Storage system according the configuration rules

Understand the function of the Service Processor
2 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
3PAR StoreServ 7000 Specification
Max SSDs:
7200 = 120 SSDs
7400 (2/4 nodes) = 120/240 SSDs
Max LFF drives:
7200 = 120 drives
7400 (2/4 nodes) = 216/432 drives (will required expansion rack)
Note that the controller enclosures include 24 SFF slots. Only the add-on drive
enclosures provide LFF slots. That is the reason for the reduced LFF drive count.
Max raw capacity:
7200 = 250TB
7400 (2/4 nodes) = 432/864 TB
For the latest information on supported operating systems refer to Single Point of
Connectivity Knowledge for HP Storage Products (SPOCK):
http://www.hp.com/storage/spock
2 –2
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
HP 3PAR StoreServ 7000 Hardware Building
Blocks
The graphic illustrates “building block” components in the system.
Rev. 14.1
2 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
3PAR StoreServ 7000 controller enclosure
3PAR StoreServer 7000 controller enclosure
Front Bezel
Every controller enclosure can have up to 24 SFF disk drives on the front. There is
also the Front Bezel LEDs located at the front left. These LEDs are status
indicators for power status, enclosure health and the disk drive status together with
a specific disk drive LED.
Power Cooling Module
On the rear of the enclosure there are 2 Power and Cooling Modules, numbered 0
and 1, from left to right. The Power Cooling Module (PCM) is an integrated power
supply, battery, and cooling fan. There are two types of PCMs:
2 –4

The 580W is used in the drive enclosures and does not include a battery

The 764W (includes a replaceable battery) is used in the node enclosures
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Power Cooling Module LEDs
The PCM has LEDs depending on PCM, and all located in the corner of the
module.
For more Information about System LEDs, refer to the “HP 3PAR StoreServ 7000
Storage Service Guide.”
Rev. 14.1
2 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
3PAR StoreServ 7000 controller Serial Number
The system has two serial numbers:
2 –6

HP Serial No. for order processing.

3PAR SN (7 characters) to setup the systems.
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
3PAR StoreServ 7000 controller
Controller Nodes
The Controller Nodes are also located at the rear. Each enclosure has 2 Nodes,
which are numbered from 0 to 3, from bottom to top.
Note: The 2 controllers are identical. When mounted in the enclosure, Node
1 is rotated 180 degrees from Node 0's orientation.
Controller Node LEDs
For more Information about System LEDs, refer to the “HP 3PAR StoreServ 7000
Storage Service Guide.”
Rev. 14.1
2 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR StoreServ 7000 controller ports
HP 3PAR StoreServ 7000 controller Ports
Console Port
The Console Port, labeled Mfg, provides a serial connection to connect to the CLI
interface of the controller. The gray connector for the laptop (PN 180-0055) is used
on the serial port for connection to the controller node Mfg port. You will need a
USB-to-serial adapter on a modern laptop to have a serial port. The default
settings are 57600 Baud, 8 Bit, and no parity.
Cluster Expansion Ports
The two cluster expansion ports are color coded black and white. They are only
used on four Node configurations. Refer to the detailed cabling instructions later in
this module.
SAS Ports
The SAS ports are used to connect the disk drive enclosures. They are labeled
DP1 and DP2. The first port which is used to connect the enclosures is DP2. Refer
to the detailed cabling instructions later in this module.
Embedded Host Ports
The Host ports are labeled FP1 and FP2. They can be used as host ports or
remote copy ports, but need to be configured before they are usable.
2 –8
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Management (MGMT) Port
The Management Port is a standard Ethernet port (1Gb) for array management. If
configured correctly, the array is accessible over only one (cluster) IP-address, on
all management ports of the different nodes. All MGMT ports of all nodes have to
be connected to the same LAN as the Service Processor.
Replication Port
1 GbE port for Remote Copy (labeled RC‐1)
HBA Slot
Only one expansion slot is available for optional 4‐port FC adapter or 2‐port
iSCSI/FCoE adapter.
Rev. 14.1
2 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR StoreServ 7000 Host Connectivity
Options
HP 3Par StoreServ 7000 Host Connectivity Options
There are 2 different Host adapters available:

HP 3PAR StoreServ 7000 4-port 8Gb/sec Fibre Channel Adapter QR486A

HP 3PAR StoreServ 7000 2-port 10Gb/sec iSCSI/FCoE Adapter
QR487A
They are used in 7200, 7400 2-node and 7400 4-node configuration or the
upgrade node pair kit. They are optional, because each controller has two FC host
ports embedded. The following rules apply:
2 –10

Adapters must be purchased in pairs.

Each node in a node pair must have the same number and type of adapters.
(A node pair is composed of the two controller nodes in a single 2U
enclosure.) FC and iSCSI/FCoE adapters may not be intermixed in a node
pair.

The 4 ports of the FC adapter can be individually configured to connect to a
host or to a remote array in an RC configuration.

The two ports of the iSCSI/FCoE adapter can be individually configured by the
user as iSCSI or FCoE (NOTE: FCoE functionality will be enabled in 2013).
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
74x0 4-node Configurations
Rev. 14.1
2 –11
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR StoreServ 74x0 4-node System
Cabling controller nodes
The following shows node cabling for a four-node system. Connection between
nodes 0 and 1 and nodes 2 and 3 use four large interconnect cables that are
directional and must be installed correctly for the storage system to function. The
cables are labeled as A and C. The A end connects to nodes 0 and 1 and the C
end connects to nodes 2 and 3.
2 –12

Insert the cable connector A end into node 0, Intr 0 port. Connect the C end to
node 2, Intr 1 port.

Insert the cable connector A end into node 0, Intr 1 port. Connect the C end to
node 3, Intr 0 port.

Insert the cable connector A end into node 1, Intr 1 port. Connect the C end to
node 2, Intr 0 port.

Insert the cable connector A end into node 1, Intr 0 port. Connect the C end to
node 3, Intr 1 port.
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Controller Node Block Diagram
Controller Node Block Diagram
The 3PAR Gen 4 ASIC is the heart of the array, with its built-in features. It is used
in RAID implementation, the Cluster integration, the hardware RAID engine, zero
detection mechanism, and thin provisioning. To achieve the best performance, the
ASIC controls the data cache.
The Processor Complex has a 1.8GHz processor, its own control cache, and a
SSD disk for the 3PAR inform OS. It connects, controls, and monitors all other
system components on the PCIe switch.
An internal SAS expander allows the connection of the 24 internal SFF disk drives.
The expander is directly connected to the embedded SAS HBA. The external SAS
Ports are used to daisy chain the additional disk enclosures, where each has its
own SAS expander (I/O module).
Note: For all drive enclosures, the ports should be balanced. The internal SAS
Expander is always connected to DP1.
For Host connection, there are the 2 embedded 8Gb/s FC ports or the optional
PCIe HBA Slot available.
Rev. 14.1
2 –13
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 disk enclosure M6710
Disk Enclosure M7610
Each drive enclosure includes 24 drive bays. The HP 3PAR StoreServ 7200
supports up to five (5) additional drive enclosures. The HP 3PAR StoreServ 7400
supports up to nine (9) additional drive enclosures per node pair. The HP 3PAR
StoreServ 7450 supports up to four (4) additional drive enclosures per node pair.
The two drive enclosure types can be intermixed in a single array.
For HP M6710 Drive Enclosures, drives must be added in identical pairs, starting
from slot 0 on the left and filling to the right, leaving no empty slots between drives.
The Best Practice for installing or upgrading a system is to add the same number
of identical drives to every drive enclosure in the system, with a minimum of two
drives added to each enclosure.
2 –14
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
The following shows the I/O Module LEDs
PCM Module 580W
It looks similar to the 764W PCM (used in the controller enclosure) but it is
different, because the 580W has no Cache Battery.
The following show the PCM LEDs.
Rev. 14.1
2 –15
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 disk enclosure M6720
Disk Enclosure M6720
Each drive enclosure includes 24 drive bays. The HP 3PAR StoreServ 7200
supports up to five (5) additional drive enclosures. The HP 3PAR StoreServ 7400
supports up to nine (9) additional drive enclosures per node pair. The HP 3PAR
StoreServ 7450 supports up to four (4) additional drive enclosures per node pair.
The two drive enclosure types can be intermixed in a single array.
Installing disk drives
For HP M6720 Drive Enclosures, drives must be added in identical pairs, starting
from slot 0 on the left and filling to the top, leaving no empty slots between drives.
Columns of drives in the M6720 enclosure must be of the same type (SSD or NL)
and, for HDDs, the same rotational speed. Drives of different types may not be
mixed in a single column. It is permitted to have empty columns between columns
containing drives. Different columns do not have to contain the same number of
drives.
For example, when you need to install 4 NL disk and 4 SSD into the above
enclosure, one supported configuration would be to have the NL drives in Slot
0,4,8,12 and the SSDs in Slot 1,5,9.13.
2 –16
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Drive Specification Overview
The chart provides a quick summary of the drive specifications at the time of
writing.
Rev. 14.1
2 –17
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR SSD Drive Options
MLC (multi-level cell) drives offer a lower $/GB compared to SLC (single level cell)
drives and a lower $/IOP compared to traditional spinning FC or SAS drives.
Required capacity typically dictates when to use MLC drives over SLC drives. MLC
SSDs perform best with greater than 3TB of capacity whereas SLCs are better
used when the requirement is for less than 3TB of capacity.
3PAR Operating System monitors wearing of both SLC and MLC drives in a 3PAR
StoreServ and shows that information to users. It keeps users informed about how
their SSDs are wearing out, and helps them replace SSDs in a planned fashion.
At 95% wear, 3PAR OS warns users of the impending wear out of the specific
SSDs, and puts the SSDs in a degraded state
Our SSD warranty (SLC or eMLC, irrespective of 7000, 7450 or 10000 platform)
will be 3 years.* No max write dependency, for example, if max writes are reached
within warranty 3 year period, HP will replace the drive.
With Extended Maintenance contract (beyond the 3yr warranty), max writes limits
will be a dependency.* Customer will be subject to the duration (number of years
of extended maintenance contract) AND max writes limit on SSD, whichever is
reached sooner.* That is, if max writes limit is reached during the Extended
Maintenance contract period, the customer is responsible for purchasing a new
SSD; HP will not replace under the Extended Maintenance contract.
2 –18
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
HP 3PAR 7200 maximum Configurations
HP 3PAR 7200 Configurations
The HP 3PAR StoreServ 7200 supports up to five additional drive enclosures. The
two drive enclosure types can be intermixed in a single array.
The Best Practice is to balance the drive enclosures across the SAS ports,
remembering that the controller node enclosures include (24) drives attached to
the SAS port labeled DP-1.
The Best Practice when including LFF and SFF drive enclosures in the same array
is to arrange them in the rack so that all of the 2U enclosures that belong to one
node pair are together and all of the 4U enclosures for that node pair are together.
When connecting the backend SAS cables, intermix the M6710 and M6720
enclosures on each SAS port.
To achieve highest availability in multi-enclosure configurations, configure a
minimum of two enclosures per node pair for RAID 1, a minimum of four
enclosures per node pair if RAID 5 is included, and a minimum of three enclosures
per node pair if RAID 6 is included. Include enclosures containing node pairs in the
count with the M6710 enclosures.
Drive bays that are not filled with a drive must be covered with a drive blank to
preserve proper air flow.
If future capacity upgrades are expected, include enough Drive Enclosures so that
there are some empty bays in each enclosure after all drives are added.
Rev. 14.1
2 –19
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7400 2-node maximum configurations
HP 3PAR 7400 2 Node Configurations
The HP 3PAR StoreServ 7400 2 Node configuration supports up to nine additional
drive enclosures
The best practice is to balance the drive enclosures across the SAS ports,
remembering that the controller node enclosures include (24) drives attached to
the SAS port labeled DP-1.
The best practice when including LFF and SFF drive enclosures in the same array
is to arrange them in the rack so that all of the 2U enclosures that belong to one
node pair are together and all of the 4U enclosures for that node pair are together.
When connecting the backend SAS cables, intermix the M6710 and M6720
enclosures on each SAS port.
To achieve highest availability in multi-enclosure configurations, configure a
minimum of two enclosures per node pair for RAID 1, a minimum of four
enclosures per node pair if RAID 5 is included, and a minimum of three enclosures
per node pair if RAID 6 is included. Include enclosures containing node pairs in the
count with the M6710 enclosures.
The HP 3PAR StoreServ 7400 2‐node Storage Base includes two 1U rack filler
panels. The best practice is to install those filler panels in the 2U space directly
above the 2U node enclosure keeping that space empty in case the user wants to
upgrade the array to four nodes in the future.
Drive bays that are not filled with a drive must be covered with a drive blank to
preserve proper air flow.
If future capacity upgrades are expected, include enough Drive Enclosures so that
there are some empty bays in each enclosure after all drives are added.
2 –20
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
HP 3PAR 7400 4-node max Configurations
HP 3PAR 7400 4-node Configurations
The HP 3PAR StoreServ 7400 supports up to nine additional drive enclosures per
node pair. This gives a total of 18 disk enclosures for a 4 Node configuration.
The best practice is to balance the drive enclosures across the SAS ports,
remembering that the controller node enclosures include (24) drives attached to
the SAS port labeled DP-1.
The best practice when including LFF and SFF drive enclosures in the same array
is to arrange them in the rack so that all of the 2U enclosures that belong to one
node pair are together and all of the 4U enclosures for that node pair are together.
When connecting the backend SAS cables, intermix the M6710 and M6720
enclosures on each SAS port.
To achieve highest availability in multi-enclosure configurations, configure a
minimum of two enclosures per node pair for RAID 1, a minimum of four
enclosures per node pair if RAID 5 is included, and a minimum of three enclosures
per node pair if RAID 6 is included. Include enclosures containing node pairs in the
count with the M6710 enclosures.
Drive bays that are not filled with a drive must be covered with a drive blank to
preserve proper air flow.
If future capacity upgrades are expected, include enough Drive Enclosures so that
there are some empty bays in each enclosure after all drives are added.
Rev. 14.1
2 –21
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7450 maximum configurations
HP 3PAR 7450 2/4 Node Configurations
The HP 3PAR StoreServ 7450 configuration supports up to four added drive
enclosures per node pair.
The best practice is to balance the drive enclosures across the SAS ports,
remembering that the controller node enclosures include (24) drives attached to
the SAS port labeled DP-1.
The best practice when including LFF and SFF drive enclosures in the same array
is to arrange them in the rack so that all of the 2U enclosures that belong to one
node pair are together and all of the 4U enclosures for that node pair are together.
When connecting the backend SAS cables, intermix the M6710 and M6720
enclosures on each SAS port.
To achieve highest availability in multi-enclosure configurations, configure a
minimum of two enclosures per node pair for RAID 1, a minimum of four
enclosures per node pair if RAID 5 is included, and a minimum of three enclosures
per node pair if RAID 6 is included. Include enclosures containing node pairs in the
count with the M6710 enclosures.
The HP 3PAR StoreServ 7450 2‐node Storage Base includes two 1U rack filler
panels. The best practice is to install those filler panels in the 2U space directly
above the 2U node enclosure keeping that space empty in case the user wants to
upgrade the array to four nodes in the future.
Drive bays that are not filled with a drive must be covered with a drive blank to
preserve proper air flow.
If future capacity upgrades are expected, include enough Drive Enclosures so that
there are some empty bays in each enclosure after all drives are added.
2 –22
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Recommended hardware configuration steps
Best Practice Configurations Process
HP 3PAR StoreServ 7000 Best Practice confi6gurations can be built through the
following 8‐step process:


Rev. 14.1
Calculate number and type of drives required

Estimate front end IOPS and MB/sec required by application

Use Storage Optimizer to determine drive quantities and types that meet
the performance requirements and capacity requirements.

Verify that number of drives will meet capacity requirements (TB).
Capacity requirements should also reflect needs for sparing, etc. (Note
that the HP 3PAR StoreServ 7000 systems default to one spare drive for
every 24 drives.)

Round up drive count to a multiple of 2

Consider future storage growth
Calculate number of Drive Enclosures required

Divide number of SFF drives by 24 to calculate minimum number of 2U
SFF enclosures required.

Calculate the number of LFF enclosures required by dividing the quantity
of LFF drives by 24.

In most cases, the best practice is to balance drives across enclosures.

If HA Cage is required, ensure that enough enclosures are included to
permit HA Cage for the RAID levels involved.

If future growth is expected, only partially fill the enclosures.
2 –23
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix


Select front end connectivity options

4 8Gb/s FC ports are built in per node pair

Consider need for host connectivity and Remote Copy connectivity.

If necessary, add one optional adapter card per node
Select cables

Select optical cables to connect hosts to Controller Nodes.

SAS cables used to connect nodes with Drive Enclosures are included
with the enclosures.

Select 1GbE copper cables if Remote Copy over IP is desired.

Select cabinets

Add Service Processor


Select options for storage networking

2 –24
Require 1 Service Processor per system. The Virtual service processor is
provided free. Hardware Service Processor is optional and can be
ordered in case Virtual environment is not available.
Select Host Bus Adapters, switches, and cables for connections between
hosts and storage
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Recommended Configuration Rules
Notes:
With the HP 3PAR architecture it is important to balance the workload (i.e., IOPS
and/or bandwidth) as evenly as possible across all available nodes, ports, Drive
Enclosures and Drives, as a system configuration that has nodes with substantially
different load may not deliver the full performance of the hardware.
When nodes are added to the system (e.g., when upgrading from 2 nodes to 4),
the best practice upgrade is to add symmetric number of drive enclosures per
node pair.
If this was an all SSD system then adding new FC class Drives would require a
minimum of 8 new FC Drives of the same type. The last bullet illustrates adding
an Enclosure but does not mean HA Enclosure using 4 additional drives, it will
remain HA Drive. If HA Enclosure is desired, Drives should be balanced as closely
as possible for all Enclosures installed (some rebalancing may be required –
movement of Drives from one Enclosure to another).
Rev. 14.1
2 –25
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
You must have a minimum of 12 LFF NL drives. If you have 1 enclosure, then it is
two columns of 6 LFF NL drives. If you have two LFF enclosures then it will be 1
column of 6 in each enclosure. The smallest increment of LFF NL drives is a full
column of 6 drives
Important note about the SSD drives
Minimum is 8 SSD drives in a system. If you have an empty SFF Base Enclosure
and a LFF Drive Enclosure then you have to start with the minimum number of
SSD drives for a system which is eight (intermixing SFF and LFF Drive slots is
permissible for SSD Drives).
2 –26
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
HA enclosure vs. HA drive
HA Enclosure vs. HA Drive
Traditional RAID protects against one or two disk drive failures depending on the
RAID level. That is called HA Drive.
Protection against a whole enclosure failure is called HA Enclosure.
There is a distinction between traditional RAID groups where a group of drives are
bound together in large RAID groups, rather than with the fine grain virtualization
and the way that HP 3PAR builds RAID sets among much smaller parts of the disk.
With HP 3PAR arrays, the RAID is built with chunklets. The system controls which
physical disk contains the chunklets, and take care about the integrity of the “RAID
chunklets.” Placing the chunklets onto the physical disk drives is the key to HA
enclosure.
How many and which chunklets are located on which physical disk drive is
determined from the RAID level, RAID size, enclosure position, and disk drive
position.
Rev. 14.1
2 –27
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HA enclosure
HA Enclosure
Depending on the RAID level and RAID size, a certain number of enclosures is
required for a given HA Enclosure configuration.
For RAID 1, it is two Enclosures. The chunklets forming RAID 1 are placed
automatically on two different physical disk drives, in different enclosures.
For RAID 5, the minimum is three enclosures for a RAID size of 2+1 (2 data + 1
parity). The chunklets (data or parity) forming RAID 5 are placed automatically on
three different physical disk drives, in different enclosures.
For RAID 6, the minimum number of enclosures is also three, with a RAID size of
4+2 (4 data + 2 parity). The chunklets (data or parity) forming RAID 6 are placed
automatically on six different physical disk drives, When you have three
enclosures, the controller ensures that a maximum of two of these disk drives are
in the same enclosure. When you have an enclosure failure, you lose 2 disk drives
out of the RAID 6 configuration, which is allowed.
RAID 5 2+1 and also RAID 6 4+2 have a high percentage of parity overhead.
2 –28
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Lab 1 Exercise 1-2:
Exercise 1: Best Practice configuration
Exercise 2: Locating system components
Rev. 14.1
2 –29
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Enclosure labeling rules
Enclosure labeling rules
There are certain rules regarding how to label the enclosures. The rules help to
cable the array correctly and to more quickly identify system components. The
rules are independent of the actual hardware configuration.
All labeling and cabling rules for HP 3PAR StoreServ 7400 also apply for HP 3PAR
StoreServ 7450 systems.
2 –30

Labels (A, B, C and D) are provided to help identify the enclosures in the
storage system. The labels should be applied to each enclosure in a location
that is visible without covering other labels.

The A and B labels should be applied starting with the controller enclosures
with node 0 and 1. Alternate the labeling (A/B) on each enclosure below the
controller enclosure.

On four node systems the C and D labels should be applied starting with the
controller enclosure with node 2 and 3. Alternate the labeling (C/D) on each
enclosure above the controller enclosure
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Enclosure color coding
Enclosure color coding
The red and green color coding should be used to aid in correct cabling. Only same color
components will be connected.
Note:
The color coding for HP 3PAR StoreServ 7400 also applies to HP 3PAR StoreServ 7450
systems.
Rev. 14.1
2 –31
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 SAS Backend cabling (Node 0/1)
HP 3PAR 7000 SAS Backend cabling
DP-1 cable routing
Red routing


Connect Node 0 (DP-1) to the I/O 0 (DP-1) on the “A” enclosure closest to the
controller.
Connect all “A” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


2 –32
Connect Node 1 (DP-1) to the I/O 1 (DP-1) on the “A” enclosure farthest away
from the controller.
Connect all “A” drive enclosures from (DP-2)  (DP-1) working towards from
the controller.
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
HP 3PAR 7000 SAS Backend cabling
DP-2 cable routing
Red routing


Connect Node 0 (DP-2) to the I/O 0 (DP-1) on the “B” enclosure closest to the
controller.
Connect all “B” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


Rev. 14.1
Connect Node 1 (DP-2) to the I/O 1 (DP-1) on the “B” enclosure farthest away
from the controller.
Connect all “B” drive enclosures from (DP-2)  (DP-1) working towards from
the controller.
2 –33
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 SAS Backend cabling
DP-1 cable routing
Red routing


Connect Node 0 (DP-1) to the I/O 0 (DP-1) on the “A” enclosure closest to the
controller.
Connect all “A” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


Connect Node 1 (DP-1) to the I/O 1 (DP-1) on the “A” enclosure farthest away
from the controller.
Connect all “A” drive enclosures from (DP-2)  (DP-1), working towards from
the controller.
DP-2 cable routing
Red routing


Connect Node 0 (DP-2) to the I/O 0 (DP-1) on the “B” enclosure closest to the
controller.
Connect all “B” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


2 –34
Connect Node 1 (DP-2) to the I/O 1 (DP-1) on the “B” enclosure farthest away
from the controller.
Connect all “B” drive enclosures from (DP-2)  (DP-1), working towards from
the controller.
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
HP 3PAR 7000 SAS backend cabling (Node 2/3)
HP 3PAR 7000 SAS Backend cabling
DP-1 cable routing
Red routing


Connect Node 2 (DP-1) to the I/O 0 (DP-1) on the “C” enclosure closest to the
controller.
Connect all “C” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


Rev. 14.1
Connect Node 3 (DP-1) to the I/O 1 (DP-1) on the “C” enclosure farthest away
from the controller.
Connect all “C” drive enclosures from (DP-2)  (DP-1), working towards from
the controller.
2 –35
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 SAS Backend cabling
DP-2 cable routing
Red routing


Connect Node 2 (DP-2) to the I/O 0 (DP-1) on the “D” enclosure closest to the
controller.
Connect all “D” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


2 –36
Connect Node 3 (DP-2) to the I/O 1 (DP-1) on the “D” enclosure farthest away
from the controller.
Connect all “D” drive enclosures from (DP-2)  (DP-1), working towards from
the controller.
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
HP 3PAR 7000 SAS Backend cabling
DP-1 cable routing
Red routing


Connect Node 2 (DP-1) to the I/O 0 (DP-1) on the “C” enclosure closest to the
controller.
Connect all “C” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


Connect Node 3 (DP-1) to the I/O 1 (DP-1) on the “C” enclosure farthest away
from the controller.
Connect all “C” drive enclosures from (DP-2)  (DP-1), working towards from
the controller.
DP-2 cable routing
Red routing


Connect Node 2 (DP-2) to the I/O 0 (DP-1) on the “D” enclosure closest to the
controller.
Connect all “D” drive enclosures from (DP-2)  (DP-1), working away from
the controller.
Green routing


Rev. 14.1
Connect Node 3 (DP-2) to the I/O 1 (DP-1) on the “D” enclosure farthest away
from the controller.
Connect all “B” drive enclosures from (DP-2)  (DP-1), working towards from
the controller.
2 –37
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 SAS backend cabling 4N6E
2 –38
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
The following is a cabling example for HP StoreServ 7000
4 Node 10 Drive Enclosures (6S+4L)
Rev. 14.1
2 –39
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Lab 1 Exercise 3-4
Exercise 3: Interconnect Node
Exercise 4: Getting familiar with the Backend (SAS) cabling
2 –40
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Service Processor overview

Designed to support all actions required for the maintenance of the storage
server

Provides real-time, automated monitoring

Enables the service provider to locally and remotely monitor and service the
InServ Storage Server.

Allows HP 3PAR to diagnose and resolve potential problems remotely

Can be implement as physical server or as virtual machine (StoreServ P7000
only)
Service Processor
The SP supports all actions required for maintenance of the storage system,
providing real-time, automated monitoring, and remote access by HP 3PAR
Support to diagnose and resolve potential problems.
Your system may have either a virtual or physical SP.
Rev. 14.1
2 –41
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
SPOCC
SPOCC
Service Processor Onsite Customer Care (SPOCC) is a web-based GUI
alternative to accessing most of the features and functionality available through
SPMAINT, including:

Review logs and files

Store various types of support documentation

Record storage server configuration details not directly available from the
storage server
SPOCC allows you to enable or disable local notification and to manage how and
when you are notified of important system events. These functions are not
possible with SPMAINT.
To log in to SPOCC using a web browser, enter the IP address of the service
processor in the web browser and then press Enter.
2 –42
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Using SSH to access SPMAINT
SPMAINT
The SPMAINT utility is the primary interface for the support (configuration,
maintenance, and firmware update) of both the InServ Storage Server and its SP.
The features of this utility are divided into the following major categories:

Control of the SP.

Communications with HP 3PAR Central or a local service provider.

Setup and administration of local notification.
Using SSH to access SPMAINT
Initiate an SPMAINT session using secure shell (SSH2) software such as PuTTY
or SecureCRT.
Rev. 14.1
2 –43
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Guided Maintenance
Guided maintenance scripts are provided with the service processor to help
facilitate the removal and replacement of Field Replaceable Units (FRUs). The
maintenance scripts execute all CLI commands and, in some cases, select the
appropriate failed component to minimize user error when performing maintenance
procedures.
To access the guided maintenance scripts:
Log in to SPOCC.
Click Support to access the guided maintenance procedures.
2 –44
Rev. 14.1
HP 3PAR StoreServ 7000 Hardware Components
Learning check
1. List the HP 3PAR Storage System hardware building blocks!
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
2. Which serial Number is used to setup a HP 3PAR StoreServ 7000 storage
system?
________________________________________________
3. How many PCIe expansion slots have each storage node?
________________________________________________
4. Can you mix different types of disk enclosure (SFF, LFF) on a single SASPort?
________________________________________________
5. How many drive enclosure, populated with similar disk, are required to for HA
Enclosure for RAID6 (4+2)?
________________________________________________
Rev. 14.1
2 –45
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
2 –46
Rev. 14.1
HP 3PAR StoreServ7000 Software
Module 3
Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the components of the HP 3PAR StoreServ 7000 Software Suites

Understand the HP 3PAR StoreServ 7000 Software licensing

Describe the function of the HP 3PAR Management Console and HP 3PAR
SmartStart
3 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 Software Suites
HP 3PAR 7000 Operating System Software Suite (Required)
HP 3PAR OS SW Suite - 3PAR Operating System, System Setup, and
Management Software

Foundation software of HP 3PAR StoreServ 7000 Storage, combines
advanced virtualization capabilities with simple storage management, high
efficiency, and world class performance.
HP 3PAR 7000 Replication Software Suite
HP 3PAR 7000 Replication Software Suite - Local Replication, Remote Replication
and Transparent Failover

HP 3PAR Replication Software Suite offers automatic replication, transparent
failover and Point-in-Time (PIT) copies enabling seamless disaster recovery
for critical data.
HP 3PAR 7000 Security Software Suite
HP 3PAR 7000 Security Software Suite consists of HP 3PAR Virtual Domains
Software and HP 3PAR Virtual Lock Software

3 –2
HP 3PAR 7000 Security Software Suite provides secure administrative
segregation of users and hosts, allowing individual user groups and
applications to confidently share a 3PAR StoreServ 7000 system. It also
allows you to secure volumes and copies so they cannot be deleted.
Rev. 14.1
HP 3PAR StoreServ7000 Software
HP 3PAR 7000 Data Optimization Software Suite
HP 3PAR 7000 Data Optimization Software Suite - Rebalance, Redistribute, and
Refresh

HP 3PAR 7000 Data Optimization Software Suite consists of HP 3PAR
Dynamic Optimization Software, HP 3PAR Adaptive Optimization Software
and HP 3PAR Peer Motion Software. HP 3PAR Data Optimization Software
Suite v2 also includes HP 3PAR Priority Optimization.
HP 3PAR Reporting Software Suite
HP 3PAR Reporting Software Suite - Historical Performance and Capacity
Management Tool

Rev. 14.1
The HP 3PAR Reporting Software Suite includes System Reporter, a historical
performance and capacity management tool for storage reporting, monitoring,
and troubleshooting. Also included is 3PARInfo.
3 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR 7000 Software
HP 3PAR Application Software Suite for VMware

Provides everything you need to make your VMware environment more agile
and efficient-including Recovery Manager for VMware, Host Explorer for
VMware, VASA support, and three essential plug-ins: the VMware Site
Replication Manager (SRM) Adapter, the 3PAR VAAI plug-in, and the 3PAR
management plug-in for VMware View.
HP 3PAR Application Software Suite for Oracle

Provides everything needed for protecting Oracle databases, including
Recovery Manager for Oracle and Oracle Space Reclamation capabilities.
Recovery Manager for Oracle is an extension to 3PAR Virtual Copy for nearcontinuous data protection, data sharing, and non-disruptive backup.
HP 3PAR Application Software Suite for SQL

Protects Microsoft® SQL databases with Recovery Manager for Microsoft®
SQL and the 3PAR VSS Provider software. 3PAR Recovery Manager for
Microsoft® SQL Server is an extension to 3PAR Virtual Copy to providing
rapid, affordable online recovery of Microsoft® SQL Server databases from
multiple, highly granular point-in-time snapshots.
Quickly recover a database to a known point in time, speeding up a variety of
operations including rapid recovery of the production SQL server.
3 –4
Rev. 14.1
HP 3PAR StoreServ7000 Software
HP 3PAR Application Software Suite for Exchange

Provides the essentials for protecting your Microsoft Exchange data, including
Recovery Manager for Exchange and the VSS Provider software.

Recovery Manager for Exchange is an extension to 3PAR Virtual Copy for
near-continuous data protection.
HP 3PAR Application Software Suite for Microsoft Hyper-V

Rev. 14.1
Provides administrators the power of seamless, rapid online recovery of
Microsoft Hyper-V VMs. It is an extension to Virtual Copy which enables
creation of application consistent snapshots without sacrificing performance,
availability or versatility.
3 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR StoreServ 7000 Software Licensing
HP 3PAR StoreServ 7000 Software Licensing
Two types of software licensing methods are employed with the HP 3PAR
StoreServ 7000, frame-based and drive-based licensing.
Frame Based Licensing
With frame system-based licensing, one license covers the whole array,
independent of configuration or capacity.
Drive Based Licensing
Drive-based licensing, in contrast, is licensed per installed drive. A software title
with drive-based licensing includes two Licenses to Use (LTU), a Base LTU that
enables the software feature for the system and a Drive LTU that licenses the use
of one drive. For each software title, purchase one Base LTU per title per array,
and one Drive LTU, up to a cap, for every drive, independent of drive type, that is
installed in the array, independent of drive type. With just one Drive LTU that is
independent of drive type. The HP 3PAR 7000 drive-based licensing differs from
other 3PAR arrays, which have different drive LTUs for each drive type.
For the HP 3PAR StoreServ 7200, the Drive LTUs cap at 48. For the HP 3PAR
StoreServ 7400, the Drive LTUs cap at 168. After reaching the cap, you do not
need to purchase any more Drive LTUs for that title.
There are no Drive LTU caps for HP 3PAR StoreServ 7450 systems.
3 –6
Rev. 14.1
HP 3PAR StoreServ7000 Software
HP 3PAR Management Console

Simple navigation and layout structure
Benefits

Improved user experience
 Simplified and streamlined navigation

Enhanced wizards for the “Create” functions
 Create hosts, CPG, virtual volume, and VLUN, among
others
 New Defaults (Thin Provisioning, Allocation warnings, etc)


Adds more functions previously available to CLI only
Supports previous hardware and operating system platforms
as well
The Management Console provides:
Rev. 14.1

GUI with a simple navigation and layout structure

Wizards for “Create” functions

Default settings and templates

Functions added to support new OS features and new P7000 array

More functions as previously available only to CLI

Supports previous HW and OS platforms as well
3 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR SmartStart for the StoreServ 7000
Smart Start
We still recommend HP Partners or HP Services to perform the installation to help
with the configuration design and further integration into the data center
environment.
HP 3PAR SmartStart will help to simplify the actual installation process. However,
the installation steps must be known and understood by the one who executes the
process. This enables the person to control the installation and intervene if
something goes wrong. Even though the process is now simplified, the person
performing the installation should still understand how a manual installation can be
performed, in case those skills are needed.
3 –8
Rev. 14.1
HP 3PAR StoreServ7000 Software
Learning check
1.
List the HP 3PAR 7000 Software Suites!
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
2.
What is the meaning of Drive LTU Caps and how this applies to the
StroreServ 7450 storage system?
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
3.
Does Thin Provisioning have to be license separately for StoreServ 7000
storage systems?
______________________________________________________________
______________________________________________________________
Rev. 14.1
3 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
3 –10
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and
Setup
Module 4
Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the planning tasks of a HP 3PAR StoreServ 7000 installation

Identify the resources you can use for planning and performing the
installation and setup.

Install and setup the Service Processor

Install the HP StoreServ 7000 storage controller using SmartStart

Setup the HP StoreServ 7000 storage system and export a virtual volume
the a Window host using SmartStart
4 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Plan and prepare the Installation

Do not install a storage system without planning.

Create an implementation project plan.

Review all installation documents.

Ask customer to provide all required information.

Use the tools provided by HP to prepare for the installation.

Use the installation checklist during the installation.
Installation planning and preparation
It is important for the engineers to plan the installation in advance.
System planning issues such as volume management, SAN implementation, and
currently supported platforms and hardware configurations are discussed in the
HP 3PAR Systems Assurance Document.
Other documents to use to help plan and prepare the installation are:

HP 3PAR StoreServ 7000 Storage Site Planning Manual

HP 3PAR StoreServ 7000 Storage Installation Guide
For the installation process itself, the HP 3PAR StoreServ 7000 Storage
Installation Checklist is very helpful. This document lists all the installation tasks in
sequential order and refers to the Installation Guide and other cited documents, if
necessary. You can fill in required information while performing the tasks and mark
each task complete before you proceed to the next task.
Even though it is not part of this course, the whole integration of the Infrastructure,
such as Virtual Volumes, Remote Copy, VMware Integration, Site Recovery and
Backup must be planed separately.
4 –2
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Service Delivery Guide
Service Delivery Guides (SDG) are developed by Service Capability Engineering
(SCE) with constant feedback from the field consultants.
SDGs are providing value-added templates and guidelines to ensure:


Consistent, quality service delivery — Service is delivered to customers the
same way, each time, worldwide
Increased profit margin — Field Delivery Engineers do not have to develop a
strategy for delivering services to each customer, saving the company time
and money
The latest SDGs can be downloaded from HP Smart Portal. Each SDG is provided
in a compressed (ZIP) file. The filename of the archive clearly states to which
service or product it refers to (i.e. Disk_Arrays.zip).
Service Delivery Guide (SDG) Awareness Training
A recorded training session will be available via The Learning Center. After viewing
this course, the student will have a better understanding of how SDGs can help
Field Delivery Engineers deliver a service the same way every time, which will
increase the profit margin.
Rev. 14.1
4 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Precautions
Follow these general precautions when installing or servicing the storage system
to avoid injury, data loss and damage:

Using improper tools can result in damage to the storage system.

Prepare an Electrostatic Discharge-safe (ESD) work surface by placing an
antistatic mat on the floor, or table, near the storage system. Attach the ground
lead of the mat to an unpainted surface of the rack.

Always use a wrist-grounding strap, provided with the storage system. Attach
the grounding strap clip directly to an unpainted surface of the rack.

Avoid contact between electronic components and clothing, which can carry
an electrostatic charge.

If applicable, ensure all cables are properly labeled and easily identifiable prior
to removing a component.

Observe local occupational safety requirements and guidelines for heavy
equipment handling.

Always load the heaviest item first, and load the rack from the bottom up. This
makes the rack bottom-heavy and helps prevent the rack from becoming
unstable.

Do not attempt to move a fully loaded equipment rack. Remove equipment
from the rack before moving the rack.

4 –4
At least two people are needed to safely unload the rack from the pallet.
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
HP 3PAR StoreServ 7000 Site Readiness and
Pre Checks
HP 3PAR StoreServ 7000 Site Readiness and Pre Checks
Prior to installation, the customer must complete the systems planning document
HP StoreServ 7000 Site Readiness and Pre Checks check list in cooperation with
the local HP 3PAR Sales Representative or HP 3PAR Systems Engineer. The first
part is the identification of the customer (name, 3PAR model, SE name, installation
address).
It is especially important that you fill in the responsible persons for the
power/cabling requirements later on in the document, in case there are different
responsibilities and follow-up is needed.
The document is an Excel spreadsheet and many of the fields have drop-down
option menus for values.
Topics include:

Contact information for customer personnel and for HP technical sales,
support, and service personnel

Configuration information for the storage system to be installed

Shipping and delivery details and requirements

Management workstation, service processor, and network information

Description of the customer environment

Volume and RAID level planning information

Additional notes and comments regarding installation
A detailed description about the HP 3PAR StoreServ 7000 installation and startup
service can be found in the HP 3PAR StoreServ 7000 Storage Installation and
Startup Service Guide http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA42568ENW.pdf .
Rev. 14.1
4 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Network connection
Network Connection
The IP network to manage a HP 3PAR storage system can be configured as a
Shared or Private network.
Each controller node supports one Ethernet connection for management. One
Ethernet connection (normally to the highest number node) is required to setup
and manage the system. However, a connection to at least another node is
required for redundancy. With redundancy, one IP address is shared between the
two connections and only one network connection is active at a time. If the active
network connection fails, the IP address is automatically moved to the surviving
network.
As a minimum, the storage system requires one Fibre Channel (or iSCSI)
connection from host computer to controller node. Separate connections from
each host computer to each of the controller nodes in the storage server with
connections distributed evenly across all nodes are recommended.
Hosts do not need to be connected to all 3PAR nodes, but for high availability,
connect them to at least 2 nodes (as a standard practice).
4 –6
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Installation and Setup of the Service Processor
Physical Service Processor

Unpack and install the physical SP

Set the global LAN IP Address
 Connect the management system (laptop)to ETH0 port
 Connect to the SP
https//:192.168.0.100/sp/SetIpAddress.html
 Log in as setupusr
 Use the Set Service Processor IP Address wizard to set
the IP Address

Connect the SP to the global LAN

Continue SP Setup with SmarStart
 Use the Set up the Service Processor link in the
SmartStart wizard

Optional:
 Use standalone SP Setup Wizard
(https://<sp_ip_addr>/sp/SpSetupWizard.html)
 Set up and configure the SP manually using MOB
(Moment of Birth) script
Assigning the Permanent Service Processor IP Address to the Physical SP
Your system may have either a virtual or physical SP.
If you have a physical Service processor, use the installation guide for installation
and setup details.
Connecting a Laptop to the SP:
1. At the rear of the storage system, connect the network cable to the
ETH0 port on the SP.
2. Connect the free end of the cable to the Ethernet port on the laptop.
3. Configure LAN settings.
Rev. 14.1
4 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
4. Log in as setupusr. No password is required.
5. In a browser window, enter https://192.168.0.100/sp/SetIpAddress.html
6. In the Set Service Processor IP Address wizard, enter the desired SP
IP address to be used on the global LAN.
7. Disconnect the network cable from the SP ETH0 port and laptop.
8. Connect the network cable from SP ETH0 to the public network.
Configuring the laptop LAN Settings:
1. Go to Control Panel > Network and Internet > Network and Sharing
Center and click Change adapter settings.
2. Double–click the ETH0 connection (Local Area Connection #).
3. In the Local Area Connection Properties dialog, on the Networking tab,
double-click Internet Protocol Version 4 (TCP/IPv4) from the list.
4. On the Internet Protocol Version 4 (TCP/IPv4) Properties dialog, select
the Use the following IP address: radio button and enter the following:
5. IP address: 192.168.0.2 f(for example)
6. Subnet mask: 255.255.255.0
7. Default gateway: 192.168.0.1
8. Click OK.
4 –8
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Installation and setup of the Service Processor
Virtual Service Processor


Have a VMware vSphere system available
Deploy a VM by importing the VSP (VM) OVF file using the
VMware client

Obtain the assigned IP Address of the VSP

Continue SP Setup with SmarStart



Use the Set up the Service Processor link in SmartStart
wizard
Optional:
Use standalone SP Setup Wizard
(https://<sp_ip_addr>/sp/SpSetupWizard.html)
Installation and setup of a virtual Service Processor
Your system may have either a virtual or physical SP.
If you like to use a virtual Service Processor (VSP), make sure you have a
supported VMware environment to install and setup the VSP. Use the installation
guide for installation and setup details.
Requirements:
Rev. 14.1

The machine must have VMware vSphere 5.0 Client or higher installed. You
can download VMware at: https://my.vmware.com/web/vmware/downloads.

End user must first install the VMware client before importing the VSP (VM)
OVF file.

End user should have DHCP installed on the server for the VSP setup to
work.

The OVF file is located on the DVD included with your storage system.
Download the files or mount the ISO image to your computer and start the
deployment of the VSP.

The VSP must be on a system that can be accessed by HP Support for
storage system remote support.
4 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Set up a Virtual Service Processor (VSP)
The HP StoreServ 7000 works with either a Virtual Service Processor or physical
Service Processor.
Setup of a Virtual Service Processor (VSP)
The VSP is a collection of files that define the virtual machine and its disk. The
definition of the VM is distributed as a Open Virtualization Format (OVF) file along
with a virtual disk (VMDK) file and an MF file that contains the SHA1 hash values
of the OVF and VMDK. The OVF file can be imported into an ESXi 5 host as a VM
using the VMware vSphere client.
Important!
The VSP should NOT be deployed onto the storage system that it will be
managing.
To import the VSP (VM) OVF file:
4 –10
1.
In the VMware vSphere Client window, select File, Deploy OVF template.
2.
On the Source page, click Browse to import the OVF from its location, and
then click Next.
3.
On the OVF Template Details page, verify the OVF template, then click Next.
4.
On the Name and Location page, enter a name for the VSP (key, SP ID and
serial number), then click Next.
5.
On the Disk Format page, select Thin Provision, then click Next.
6.
On the Network Mapping page, map your virtual machine to networks in your
inventory, and then click Next.
7.
On the Ready to Complete page, review the deployment settings and select
the Power on after Deployment checkbox, then click Finish.
8.
A Deployment Completed Successfully message displays after a few minutes.
Click OK.
9.
To verify that the system is connected, right-click the VSP in the virtual
machine list, select Open Console, and confirm a green LED icon displays
and the console opens.
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Configure IP address in a Non-DHCP
Environment
To set the IP address of the VSP in a Non-DHCP environment:
1.
In the VMware vSphere Client window, select the Console tab, click anywhere
on the screen, and press Enter.
2.
Log on as setupusr. Press Enter. A password is not required to configure the
network settings.
3.
Enter the service processor IP address and press Enter.
4.
Enter the Netmask address and press Enter.
5.
Enter the default gateway address and press Enter.
6.
Enter Y to configure the network and press Enter.
7.
Review the configuration confirmation and record the VSP IP address for
reference during subsequent setup procedures with HP 3PAR SmartStart or
the SpSetupWizard.
8.
Press Enter to exit. (“any key” doesn’t work)
9.
Press Ctrl-Alt to release the cursor.
10. Continue to set up the VSP with SmartStart over the public network.
Rev. 14.1
4 –11
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Final steps after deploying
Setup of a Virtual Service Processor (VSP)
Obtaining the SP IP Address
4 –12
1.
After you have verified connection to the VSP, you must obtain the SP IP
address that you will use in “Setting Up the Service Processor”.
2.
To obtain the SP IP:

In the VMware vSphere Client window, select the Summary tab and wait
5–10 minutes for the IP address to display (in the General section, IP
address field).

Make note of this IP address and launch HP 3PAR Smart Start or access
the Service Processor Setup wizard.
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Setting up the HP StoreServ 7000 by using
SmartStart
SmartStart for HP 3PAR StoreServ 7000
SmartStart for HP 3PAR StoreServ 7000
SmartStart is a new enhancement to HP 3PAR storage systems. It is a carryover
from the HP EVA, which was initially deployed to help first-time users deploy an
HP EVA without any technical help. SmartStart has been successfully
demonstrated by allowing non-IT personnel to deploy an array.
Note:
The HP 3PAR SmartStart software should not be confused with the
SmartStart product used to deploy HP ProLiant servers. They are different
products.
The software is divided into sections and subsections to accomplish the required
installation steps.
Rev. 14.1
4 –13
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Installing HP 3PAR SmartStart
Installing 3PAR 7000 storage system software using SmartStart
Before you can initialize the 3PAR storage system software, you must connect to a
physical or virtual SP.
Important: If you are not running Microsoft Windows 2008 R2, x64 Edition or 2012,
you cannot use SmartStart and must manually set up the storage system software.
System requirements
Before inserting the SmartStart CD, the following minimum system requirements
must be met:

1.0 GHz or faster processor

1 GB of installed RAM (2 GB recommended)

CD-ROM or DVD-ROM drive

1280x1024 or better screen resolution
SmartStart Online Help is supported in the following browser versions:

Internet Explorer 8 and 9

Mozilla Firefox 10 and 11

Google Chrome 17 and 18

Opera 10 and 11
To install SmartStart, insert the SmartStart CD or mount the ISO and follow the
onscreen instructions.
4 –14
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
SmartStart sections and subsections
SmartStart sections and subsections
SmartStart offers the following sections for installing and configuring the 3PAR
7000 system:

Prepare to configure



Set up systems

Set up Service Processor

Set up storage system
Connect to storage systems


Connect to a configured array
Configure hosts

Rev. 14.1
Documentation
Configure Fibre Channel or iSCSI hosts

Configure storage

Install the Management Console
4 –15
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Configuration and Installation
Make sure you have all the information you need:


Administrator access to the Windows host systems you plan
to configure
To configure a remote host system


Be able to gain administrator access to local and remote hosts
To configure storage

User account on the storage system must be assigned a Super or Edit
role
Verify that all preliminary tasks are complete



Cabling is complete and the storage system's LEDs indicate
the system is operating normally
HP 3PAR Service Processor and the HP 3PAR 7000 system
are on the same network
Either HP 3PAR Service Processor is powered on, or launch
the virtual Service Processor
Configuration and installation
Before you begin, make sure you have all the information you need:
4 –16

You must have administrator access to the Windows host systems you plan to
configure.

If you are planning to configure a remote host system (a machine other than
the machine into which you inserted the SmartStart media), you must be able
to use the same ID and password to gain administrator access to both the
system running SmartStart (the local host) and the remote host.

To configure storage, your user account on the storage system must be
assigned either a Super or Edit role, or be granted these rights:

host_create

vv_create

vlun_create
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Then verify that all preliminary tasks are complete:
Rev. 14.1

Cabling is complete and the storage system's LEDs indicate that cables are
properly installed and the storage system is operating normally.

The Service Processor and the 7000 Storage system are on the same internal
network (same subnet) as the machine from which you are using SmartStart.

Ensure that either the Service Processor is powered on, or you have installed
and launched the virtual Service Processor.
4 –17
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Using SmartStart to configure storage
1. Gather information and ensure that

All components are installed

Storage system setup is verified, storage system is powered on, and
LEDs are functioning

Service Processor is installed and powered on—or VSP is installed and
connected
2. Initialize Service Processor and the HP 3PAR StoreServ 7000
storage system
3. Connect to the new storage system
4. Configure Fibre Channel or iSCSI host connections
5. Create storage

Enable the use of virtual volumes on Windows Server 2012 server host
systems
6. Install the HP3PAR Management Console

Manage storage and access additional features and functionality
Using SmartStart to configure storage
To configure storage on an HP 3PAR 7000 storage system, follow these steps:

Gather the information you will need to use SmartStart to configure the 7000
storage system. Ensure that:

All components are installed.

The storage system setup is verified, the storage system is powered on,
and the LEDs are functioning correctly.

Either the Service Processor is installed and powered on or the VSP is
installed and connected.

Initialize the Service Processor and the 7000 storage system.

Connect to the storage system.

Configure Fibre Channel host connections or iSCSI host connections.

Create storage and enable the use of virtual volumes on Microsoft Windows
Server 2012 server host systems.

Install Management Console to manage storage and access additional
features and functionality.
Note: For more detailed information on configuring storage with SmartStart, see
the HP 3PAR StoreServ 7000 Storage SmartStart Software User’s Guide available
from the HP website.
4 –18
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Setting up the Service Processor
Setting up the Service Processor
Generate SP ID


Enter the StoreServ Serial Number
The 12-character SP ID is built from the literal “SP000” string (5 characters) +
the HP 3PAR StoreServ 7000 7-digit 3PAR serial number. For example, if the
HP 3PAR StoreServ 7000 3PAR serial number is 1601234, the Service
Processor ID will be SP0001601234.
Configure SP networking

The name to assign to the Service Processor

IP address (IPv4 only)

Subnet mask and gateway

DNS settings, if you plan to enable Domain Name System (DNS
Configure Remote Support

To enables HP to provide you the best possible support
Configure Your Time Zone

Manual

Using NTP Server
Change Passwords
Rev. 14.1

The password to assign to the setupusr username

The password to assign to the 3parcust username
4 –19
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Setting up the storage system
Setting up the storage system
You must initialize the storage system before you configure storage system
software. The Storage System Setup wizard verifies your hardware setup and
initializes and tests your storage system software.
To set up and configure the storage system:
4 –20

Verify the Service Processor is on the same network as the HP 3PAR
StoreServ 7000 storage system you are setting up.

Click the Set up the Storage System link in SmartStart wizard Step 2, Set up
systems.
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Configure Fibre Channel host
Configure Fibre Channel host
To configure the Fibre Channel host:
Rev. 14.1

Connect to the Fibre Channel host (localhost or remote host).

Validate the Fibre Channel HBA setup on the host.

Validate the Fibre Channel connection between the host and the storage
system.

Configure multipath I/O.

Install and start HP 3PAR Host Explorer.
4 –21
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Configure an iSCSI host
Configure an iSCSI host
To configure an iSCSI host:

Connect to the iSCSI host.

4 –22
Either localhost or remote host

Configure multipath I/O.

Start the iSCSI initiator on the host.

Configure the iSCSI port on the 3PAR storage system.

Configure the iSCSI target on the host.

Install and start HP 3PAR Host Explorer.
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Start to configure and setup data storage
SmartStart reuses Management Console functions

Create host

Create virtual volume

Export virtual volume to host

Add virtual volumes to Windows

Initialize, format, and mount the HP 3PAR virtual volume device on the
Windows host
Best practices—SmartStart usage



Use SmartStart on Microsoft Windows 2008 R2, x64 Edition
or 2012 servers only
Use SmartStart for 7000 installation and initialization
Use Management Console to manage storage and create
new storage after installation is complete

Start to configure and setup data storage
To configure and setup data storage, SmartSart reuse the Management Console
(MC) functions to perform the following tasks:

Create a host.

Create a virtual volume.

Export the virtual volume to the host.

Add virtual volumes to Windows.

Initialize, format, and mount the 3PAR virtual volume device on the
Windows host.
Best Practices
Rev. 14.1

Use SmartStart for installation and initialization on Microsoft Windows 2008
R2, x64 Edition or 2012 servers only.

Use the MC to manage storage and create new storage after installation is
complete.
4 –23
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Troubleshooting
To troubleshoot SmartStart, gather the following files (file name
and path)


SmartStart log files
To collect the SmartStart log files for HP support, zip all the
files in this folder:

C:\Users\<username>\SmartStart\log

Service Processor log files

SPSETLOG.log—Service Processor setup log


ARSETLOG.system_serial_number.log—Storage System
setup log
errorLog.log—General errors
Troubleshooting
To troubleshoot SmartStart, gather the following files (file name and path):

SmartStart log files


To collect the SmartStart log files for HP support, zip all the files in this
folder:
C:\Users\<username>\SmartStart\log
Service Processor log files

SPSETLOG.log—Service Processor setup log

ARSETLOG.system_serial_number.log—Storage System setup log

errorLog.log—General errors
Note: For more information, follow the instructions in
Additional resources Troubleshooting SmartStart, or follow the instructions in the
HP 3PAR OS StoreServ 7000 Storage Troubleshooting Guide.
4 –24
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Behind the Scene of SmartStart

Setting Up the Storage system


Service Processor Moment of Birth


The Service Processor Moment of Birth script (MOB) sets up and
configures the SP.
Installing HP 3PAR InForm OS Files


The Out-of-the-Box (OOTB)script guides you through setting up and
configuring the storage system software
HP 3PAR InForm OS files must first be installed onto the SP in order to
communicate and add a storage system
Adding a Storage System to the Service Processor

After successfully completing the Service Processor Moment of Birth
(SPMOB), you must add the storage system to the configuration
database of the service processor
Setting Up the Storage system

The Out-of-the-Box script guides you through setting up and configuring the
storage system software.
Service Processor Moment of Birth

The Service Processor Moment of Birth script (SPMOB) sets up and
configures the SP.
Installing HP 3PAR InForm OS Files

HP 3PAR InForm OS files must first be installed onto the SP in order to
communicate and add a storage system.
Adding a Storage System to the Service Processor

After successfully completing the Service Processor Moment of Birth
(SPMOB), you must add the storage system to the configuration database of
the service processor.
Adding a storage system permits the SP to communicate with the storage system,
service and monitor the health of the storage system.
Rev. 14.1
4 –25
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Lab 2 Exercise 1–4:
Exercise 1: Install a Virtual Service Processor
Exercise 2: Install a Storage System using HP 3PAR
SmartStart
Exercise 3: Configure the Storage System using HP 3PAR
SmartStart
Exercise 4: Install the HP 3PAR Management Console using
HP 3PAR SmartStart
4 –26
Rev. 14.1
HP 3PAR StoreServ 7000 Installation and Setup
Learning check
1.
What is the preferred method the setup the service processor and storage
system?
___________________________________________________________
___________________________________________________________
2.
Which type of file is used to deploy the Virtual Service Processor?
___________________________________________________________
3.
Which document provides all information about activities required to install a
HP 3PAR StoreServ system according to the installation service offered by
HP?
___________________________________________________________
4.
Without DHCP, how does the IP address can be set after Virtual Service
Processor deployment?
___________________________________________________________
___________________________________________________________
___________________________________________________________
___________________________________________________________
Rev. 14.1
4 –27
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
4 –28
Rev. 14.1
HP 3PAR StoreServ Architecture and
Concepts
Module 5
Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the HP 3PAR virtualization concept.

Describe possible host connection and the configuration rules.

Setup Fibre Channel host connection using HP 3PAR Persistent Port
functionality

Understand the concept of HP 3PAR Priority Optimization

Setup and configure HP 3 PAR StoreServ storage systems using 3PAR Data
at Rest Encryption
1 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR Virtualization – the Logical View
An HP 3PAR storage system is composed of the following logical data layers:
Physical Disks
Physical Disks are divided in Chunklets (E-, F-, S- and T-Class: 256MB; 7000 and
10000: 1GB). The majority is used to build Logical Disks (LD), some for
distributed sparing
Chunklets
Physical disks are divided into chunklets. Each chunklet occupies contiguous
space on a physical disk. On HP 3PAR StoreServ 7000 and 10000 Storage
systems, all chunklets are 1 GB. Chunklets are automatically created by the HP
3PAR Operating System, and they are used to create logical disks. A chunklet is
assigned to only one logical disk.
Logical Disks

Are collections of Raidlets - Chunklets arranged as rows of RAID sets (Raid
0, 10, 50, 60)

Are automatically created when required and provide the space for Virtual
Volumes, Snapshot and Logging Disks
Common Provisioning Groups

User created virtual pools of Logical Disks that allocates space to virtual
volumes on demand

CPG defines RAID level, disk type and number, striping pattern etc.
A Common Provisioning Group (CPG) is a shared pool of storage space
(specifically, a virtual pool of logical disks) that allocates space to virtual volumes
on demand. A CPG allows up to 4,095 virtual volumes to share the CPG's
resources. You can create fully provisioned virtual volumes and Thinly Provisioned
Virtual Volumes (TPVVs or Thin volumes) that draw space from a CPG's storage
pool.
1 –2
Rev. 14.1
complete learner guide
Virtual Volumes (VV) – Exported LUNs

User created fat or thin provisioned volumes composed of LDs according to
the specified CPG policies

User exports VV as LUN
Virtual volumes make use of their resources as defined by Common Provisioning
Groups (CPGs). In order to make storage available to hosts, volumes are exported
as Logical Unit Numbers (LUNs) to hosts. Virtual volumes are the only data layer
visible to the hosts.
You can create physical copies or virtual copy snapshots of virtual volumes; both
types of copies remain available if the original base volume becomes unavailable.
When you create virtual volumes, you must assign CPGs in order to allocate
space to the virtual volumes. Therefore, to create virtual volumes, you must either
use the default CPG created during the process of initializing the storage system,
or you must create custom CPGs.
You can create the following types of virtual volumes:
Rev. 14.1

Fully Provisioned Virtual Volumes: Volume size is fixed. Creating fully
provisioned virtual volumes does not require a separate license.

Thinly Provisioned Virtual Volumes: Also known as Thin volumes, these
volumes allocate space on demand in small increments. Creating Thin
volumes requires the HP 3PAR Thin Provisioning Software license.

Physical Copies: A full copy of a volume. Creating physical copies does not
require a separate license.

Virtual Copies: A snapshot of a base volume that only records changes to the
base volume. Creating virtual copies requires the HP 3PAR Virtual Copy
license.
1 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Why are Chunklets so Important?
Chunklets
When a physical disk is admitted to the system, it is divided into chunklets (256MB
or 1GB depending on the class of system) that become available to the system.
Some chunklets are used by logical disks and other chunklets are designated as
spares to hold relocated data during a disk failure or during maintenance
procedures.
Creating, moving, and removing chunklets and spares can only be performed with
the HP 3PAR InForm Command Line Interface (CLI).
Viewing chunklets and spares can be performed with both the HP 3PAR InForm
Command Line Interface (CLI) and the HP 3PAR InForm Management Console.
Some chunklets are identified as spares. These spare chunklets are used to hold
relocated data during disk failures and during maintenance procedures.
This initial spare storage totals the amount of storage in a single drive magazine,
using the largest size physical disks.
1 –4
Rev. 14.1
complete learner guide
Common Provisioning Groups (CPG)
CPGs are Policies that define Service and Availability level by
 Drive type (SSD, Fast Class, Nearline)
 Number of Drives (striping width)
 RAID level (R10 / R50 2:1 to 8:1 / R60 4:2; 6:2; 8:2; 10:2;
14:2)
Multiple CPGs can be configured and optionally use same drives
 For example, a System with 200 drives can have one CPG
containing all 200 drives and other CPGs with subsets of
200 drives that overlap
CPGs have many functions:
 They are policies by which free Chunklets are assembled
into logical disks
 They are a container for existing volumes and used for
reporting
 They are basis for service levels and our optimization
products
CPG
A Common Provisioning Group (CPG) is a policy which defines a virtual pool of
logical disks.
It allows up to 4,095 volumes to share the CPG's resources and allocate space on
demand. However, CPGs still require careful planning and monitoring to prevent
them from becoming so large that they set off the system's built-in safety
mechanisms.
These safety mechanisms are designed to prevent a CPG from consuming all free
space on the system, but they only work properly on systems that are planned
carefully and monitored closely. The maximum number of CPGs per system is
2,048.
Rev. 14.1
1 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR Virtualization concepts
Chunklets, Regions, Virtual Volumes
The set size is the number of chunklets in a set. Also known as mirror depth for
RAID 1 sets and parity set for RAID 5 sets.
A region is a subdivision of a logical disk or virtual volume. The size of a region is
always a multiple of 32 MB.
The step size is the number of contiguous bytes that the system accesses before
moving to the next chunklet.
Summary (from bottom to top):
1 –6
1.
Physical Disks are formatted in Chunklets
2.
Logical Disks (LD) are built from Chunklets of different Physical Disks
according to CPG settings – RAID level, Set Size
3.
Chunklets are split in LD Regions – LD Regions (Raidlets) across Chunklets
4.
LD Regions of different LDs are mapped to Virtual Volumes ( i.e. A1 – A7 of
LD1 –> I1 – I7 of LD2 …)
5.
Host IO enters the array and gets chunked in Steps (Step Size depending on
RAID level)
6.
Steps are striped across VV Regions
Rev. 14.1
complete learner guide
How a region maps to a virtual volume
How a region maps to a virtual volume
A logical disk is a collection of physical disk chunklets arranged as rows of RAID
sets. Each RAID set is made up of chunklets from different physical disks. Logical
disks are pooled together in CPGs, which allocate space to virtual volumes.
Creating CPGs maps out the data layout parameters for the creating logical disks.
Logical disks are created automatically by the system when virtual volumes are
created from CPGs. The RAID type, space allocation, growth increments, and
other logical disk parameters can be set when you create a CPG or can be
modified after you create a CPG.
Mapping is the correspondence of logical disk regions to the virtual volume
regions. Virtual volumes are made up of multiple logical disks, and each logical
disk contains regions that are mapped to the VV. All types of volumes are created
by mapping data from one or more logical disks to the VV.
Rev. 14.1
1 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR virtualization concepts
Virtualization Concept
HP 3PAR Storage can scale non-disruptively from two to eight cache coherent
active/active storage controller nodes.
As soon as the HP 3PAR system detects that four or more storage controller
nodes are installed, a resilient feature called persistent cache is autonomically
enabled.
Persistent cache helps ensure that no storage controller node is placed into
performance, limiting “cache write thru” mode, as any node that loses its adjacent
node will dynamically form a mirrored cache relationship with another storage
controller node.
1 –8
Rev. 14.1
complete learner guide
Host connection
Host Connection
To export (or present) virtual volumes to hosts—which enables the host system to
write data to and read data from the storage system—you must configure either
Fibre Channel host connections or iSCSI host connections.
To ensure that your storage system remains available if a component fails, connect
the host system to the storage system using multiple paths.
The system sees a host as a set of initiator port World Wide Names (WWNs) or
iSCSI Names. Hosts that are physically connected to ports on the system are
automatically detected.
Defining host characteristics includes the assignment of a name to a host, and the
assignment of a path to that host. Two types of host paths can be assigned: FC or
iSCSI paths. You should create multiple paths to each host.
In addition to assigning FC or iSCSI paths when creating a host, you can also
annotate the host with descriptive information such as the host’s location, IP
address, operating system, model, and owner.
“Host personas” are a set of behaviors that permit hosts connected to FC or iSCSI
ports on the system to deviate from the default host behavior. By assigning a
persona to a host, multiple host types that require distinct customized responses
can share a single system port.
Front-end port cabling Best Practice:
Each HP 3PAR StoreServ controller node should be connected to two fabrics. This
is to enable HP 3PAR Persistence Ports, a feature that allows a node pair to
transparently failover and back with no interruption or pause of host I/O. Host ports
should be zoned in partner pairs. For example, if a host is zoned into point 0:1:2
(node 0, slot 1, port 2), then it should also be zoned into port 1:1:2 (node 1, slot 1,
port 2).
Ports of the same pair of nodes with the same ID should be connected to the same
fabric.
Rev. 14.1
1 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Host Connection - Fabric zoning
Fabric zoning controls which Fibre Channel end-devices have access to each
other in the fabric. Zoning also isolates the host server and HP 3PAR StoreServ
Storage ports from Registered State Change Notifications (RSCNs) that are
irrelevant to these ports.
You can set up fabric zoning by associating the device World Wide Names
(WWNs) or the switch ports with specified zones in the fabric. Although you can
use either the WWN method or the port zoning method with the HP 3PAR
StoreServ Storage, the WWN zoning method is recommended because the zone
survives the changes of switch ports when cables are moved around on a fabric.
The HP 3PAR arrays support the following zoning configurations:

One initiator to one target per zone

One initiator to multiple targets per zone (zoning by HBA). This zoning
configuration is recommended for the HP 3PAR StoreServ Storage. Zoning by
HBA is required for coexistence with other HP Storage arrays.
NOTE: For high availability/clustered environments that require multiple initiators
to access the same set of target ports, HP recommends that separate zones be
created for each initiator with the same set of target ports.
NOTE: The storage targets in the zone can be from the same HP 3PAR StoreServ
Storage, multiple HP 3PAR StoreServ Storages, or a mixture of HP 3PAR and
other HP storage systems.
The HP 3PAR StoreServ Storage array can coexist with other HP array families.
For supported HP arrays combinations and rules, see the HP SAN Design
Reference Guide. Use this guide also for more information about using one
initiator to multiple targets per zone in the Zoning by HBA in the Best Practices
chapter of this guide.
1 –10
Rev. 14.1
complete learner guide
HP 3PAR Persistent Ports
HP 3PAR Persistent Ports
Every Port on Node 0 and 1 can represent 2 port IDs, its own or “Native Port ID”
and a “Guest Port ID”. In normal operation it represents only its own “Native Port
ID” to the Fabric, it is connected to. In failover state, the surviving ports also
represent the “Guest Port IDs” to the Fabric.
For the Servers there is no change visible. All I/O`s can be done to the unchanged
target, even if the target was hosted by the failed node. Using this method, no
MPIO path failover is required if a node fails.
MPIO is still required to be protected if a path from the Host to the fabric or if a
fabric fails.
Rev. 14.1
1 –11
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR World Wide Name
WWN
World-Wide Name: A unique 64-bit or 128-bit value used to identify Fibre Channel
devices on an arbitrated loop. The WWN consists of a prefix issued by the IEEE to
uniquely identify the company and a suffix that is issued by the company.
The WWN of HP 3PAR storage system FC-ports can be used to identify individual
ports of the storage system.
Note:
The 3PAR system ID is built from the last five digits of the 3PAR serial number.
Example: 3PAR Serial Number: 1620503;
Last five digits in decimal 20503 => Hex: 5017
1 –12
Rev. 14.1
complete learner guide
HP Flat SAN Architecture
HP Flat SAN Architecture
HP Flat SAN Architecture provides the capability to “direct connect” 3PAR storage
to VitualConnect Flex Fabric Modules in a C-Class Blade Enclosure. By using this
approach, the need for buying extra FC-HBA`s and external FC-Switches is
eliminated.
http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA4-1557ENW.pdf
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00814156/c008141
56.pdf
Rev. 14.1
1 –13
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR Priority Optimization
If all resources were unlimited from a performance perspective, there would be no
need for QoS, however:

Storage performance resources are limited and expensive and will have
periods of contention which may disrupt business operations unpredictably.

Without storage QoS, hot or active data will utilize more storage performance
resources, which can starve other storage resources.
HP 3PAR Priority Optimization operates by applying an upper-limit control on I/O
traffic to and from hosts connected via Fibre Channel, iSCSI, or FCoE to an HP
3PAR StoreServ Storage system. These limits, called QoS rules, are defined for
front-end IOPS and bandwidth, and are applied via Autonomic Groups (VV sets).
Every QoS rule is associated with a single target object. The smallest target object
to which a QoS rule can be applied is a VV set. Because a VV set can contain a
single VV, a QoS rule can target one volume. A QoS rule operates on all volumes
inside a VV set.
HP 3PAR Priority Optimization is resident on the storage system and runs
completely on the HP 3PAR StoreServ Storage system. There are no host-based
components to install.
1 –14
Rev. 14.1
complete learner guide
Priority Optimization can be used to make sure the right customers and
applications fully utilize the available resources while controlling less important
applications.
In all environments, production workloads take precedence over test and
development activities. Performance and scale-up test scenarios of software may
deplete resources inside the array, impacting production applications running on
the same storage system. Snapshots of the Production database for analysis,
backup, and development purposes can be made available to the Test &
Development organization with a lower I/O priority using QoS.
HP 3PAR Priority Optimization is a feature of HP 3PAR OS 3.1.2 MU2 and is
supported on all HP 3PAR StoreServ Storage systems that are certified for this
version of HP 3PAR OS. This includes the HP 3PAR F-Class and T-Class systems
and HP 3PAR StoreServ 7000 and 10000 Storage systems.
To enable the software, only the license key for it has to be installed.
All major Operating Systems and connectivity modes are supported with HP 3PAR
Priority Optimization; any incompatibility will be listed on the HP Single Point of
Connectivity Knowledge (SPOCK) website.
Rev. 14.1
1 –15
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Creating and managing QoS definitions requires HP 3PAR Management Console
4.4 and later. To use the command line, you must install HP 3PAR Command Line
Interface 3.1.2 MU2.
Reports on HP 3PAR Priority Optimization are available via HP 3PAR System
Reporter 3.1 MU1 and HP 3PAR Management Console 4.4.
Every QoS rule has four attributes:

Name—the name of the QoS rule is the same as the name of the VV set

State—the QoS rule can be active or disabled

I/O Limit—the limit on the IOPS for the target object

Bandwidth limit—the limit on transfer rates for the target object
Overlapping QoS rules
A virtual volume can be a member of up to eight VV sets that each have a QoS
rule defined. In such a case, the I/O to and from the volume is governed by
multiple, possibly overlapping rules. All active rules for a particular VV set are
combined using wired-OR logic: the QoS limit that is reached first takes
precedence. There is no requirement that all volumes in a VV set be exported to
hosts for a QoS rule to be applied to the VV set.
1 –16
Rev. 14.1
complete learner guide
“all_others” rule
HP 3PAR Priority Optimization features a system-wide, built-in system rule called
“all_others” that is disabled, by default. This rule is used to specify an IOPS and/or
bandwidth limit for all volumes and VV sets that are not subject to a named rule.
Enabling this rule averts the need to define a named rule for all volumes on the
storage system.
HP highly recommends that the “all_others” rule be enabled to help ensure that
volumes not placed explicitly into named QoS rules won’t disrupt the system by
using an inordinate amount of IOPS or bandwidth. Care should be taken to help
ensure that the “all_others” rule is allocated enough IOPS and bandwidth
resources to satisfy the requirements of the volumes it governs.
If the upper limit for IOPS or bandwidth for a particular VV set has been reached,
HP 3PAR Priority Optimization delays I/O request responses for the volumes
contained in that VV set. These delayed I/O requests are pushed onto an
outstanding I/O queue for the VV(s) in the VV set experiencing the limit breach.
Every QoS rule maintains its own queue for delayed I/O requests. These queues
are constructed inside each HP 3PAR StoreServ Storage controller node receiving
an I/O request that needs to be delayed.
Rev. 14.1
1 –17
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
The controller node’s cache is not impacted because the QoS rules are applied
before write I/O data hits the cache. Only the I/O request descriptions are queued,
not the actual data. The size of a request queue varies by maximum delay time
and QoS limits.
When I/O requests reside longer than 200 ms in a QoS queue, any more incoming
I/O requests to the volumes in the VV set are rejected and a QFULL response is
returned to the host using the volumes.
QFULL prevents delayed I/O from holding all system resources such as buffers
and queues on the host, HBA, and VV layer. Hosts should respond to the QFULL
message appropriately and throttle I/O. The I/O delay and the eventual QFULL
response applies to all members of the VV set, even if only one of the VVs caused
the QoS threshold breach.
What can go wrong?
Problems occur when apps / hosts exceed set limits:

Small excesses => Increased response times

Big excesses => QFULL returned
QFULL storm
If a VV Set is asked to go significantly beyond the limits that have been set, hosts
can receive a large number of QFULLs in a reasonably short amount of time.
Invalid Assumption
An assumption relied on is that throttling one VV Set will benefit other VV Sets.
This doesn’t always hold true.
Capacity Overprovisioning
The total of all limits may be higher than the system can handle, which may result
in insufficient throttling.
1 –18
Rev. 14.1
complete learner guide
3PAR Data at Rest Encryption
The 3PAR DAR Encryption enables compliance with most internal, private, and
governmental standards including HIPPA for Healthcare and the Payment Card
Industry Data Security Standard (PCI DSS), two of the most widely applicable
compliance standards in use today.
The data at rest encryption (DAR) will be supported on new 7000, 7450 or 10000
systems. DAR Encryption is only supported on new 3PAR arrays, and will not be
supported on existing customer arrays. For example, a customer will not be able to
swap out their existing non-encrypted drives for encrypted drives on an existing
3PAR system. The customer’s decision to encrypt the data on the array is made at
the time of purchase.
Data on the array will be 100% encrypted, or not at all. A mixed configuration of
encrypted and non-encrypted storage is not supported.
Customers will buy the standard array configuration but will order encrypted drives
with the initial order, and for any additional capacity. In addition, customers will
purchase a frame-based (one license per system) encryption license key that
enables the encryption functionality in the system. Note that encryption must be
explicitly enabled (turned on) by the customer.
The drives, either Solid State or HDD, are industry standard self-encrypting drives
(SEDs) that have on-board circuitry which will encrypt / decrypt all data to the drive
without any user intervention. This encryption will protect data from exposure due
to loss, theft or replacement of equipment.
For example, in the event a drive failure occurs, any data resident on the disk drive
is protected from unauthorized use due to the encryption.
There are no performance impacts at the drive level.
Rev. 14.1
1 –19
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
The HP 3PAR OS is used for Key Management of each disk but does not
participate in the encryption/de-encryption of the data. 3PAR StoreServ
virtualization is separate from disk encryption and encryption occurs once data is
presented to the disk as write or when a request is received from the host as a
read operation.
When setting up Remote Copy or Peer Motion, if the target system’s Data
Encryption state does not match the source system’s state, the user will get a
warning that they must acknowledge in order to set up Remote Copy.
Self-Encrypting Drives (SED) contain special firmware and an ASIC that provides
encryption, so there are no data delays.
The drives are Closed Encryption Devices.
1 –20

Each drive has its own encryption key that never leaves the drive, but can be
changed.

The drive exposes an open interface (datastore) for authentication key
management which is handled at the array level.

All data on the disk is encrypted (full disk encryption) using AES 256
encryptions standard.
Rev. 14.1
complete learner guide

The enabled instant and secure erasure of the SED (cryptograpic erase) by
changing the drive encryption key rendering the data unintelligible.
The authentication key controls access to that band. For the StoreServ
implementation, the entire disk is in one band (full disk encryption). Authentication
keys can be changed (key rotation, rekey) at any time by the customer.
The disks will go into a locked state whenever they lose power, which will be used
to guarantee that any disk removed from a StoreServ will not be accessible except
in its original array.
When the drive is unlocked, all I/O behaves exactly as a non-SED would behave
and encryption/decryption happens at full interface speed.
The local key manager is a part of the 3PAR OS and runs on each node in the
cluster. The LKM is used to maintain the authentication keys used to unlock the
drives. For high availability purposes, the key file must be backed up and
protected.
Rev. 14.1
1 –21
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Local Key Management is done via the HP 3PAR Management Console (MC). All
the key management functionality is handled by the Local Key Manager (LKM)
module which integrated into the Management Console. All key functions are
controlled through the Local Key Management (LKM):

Encryption Enablement

Backup of keys

Rekey

Recovery of Keys
Encryption is not enabled by default and is the customer’s responsibility to enable
encryption and backup. the key file Encryption should be enabled BEFORE writing
data to the array.
When HP 3PAR Data Encryption is enabled, the system verifies:

The system is licensed for Data Encryption

All drives in the system are Self Encrypting Drives

There are no failed drives in the system
If all of these are true, the system:

Generates an authentication key and returns the backed up key file to the user

Creates Local Key Manager and initial key

Takes ownership of all drives in the system

After the key has been acknowledged by the user, the authentication key is
set on all the drives in the system
If any of these are not true, Data Encryption will not be enabled.
1 –22
Rev. 14.1
complete learner guide
Backup Keys
After a successful entitlement license is entered onto the array, the user will notice
a new icon labeled “Encryption” placed on the top right of the MC screen. Under
this new icon, the user is required to immediately backup the array encryption
keys.

Enable Encryption

Backup Encryption Key

Restore Encryption Key

Change Encryption Key
The user should chose immediately to backup the storage array encryption key.
Choosing this option will prompt the user to supply a location for the backup
process. Once the key is properly backed up, a pop up screen will appear notifying
the user of a successful backup.
Key Store Restore
If the user has the need to restore a lost or corrupted key, the user can choose to
restore the key file from the same drop down box. The user is prompted for the
location of the key file and the password which was used to store the original key
file. Once both requirements are satisfied, the key file will be restored to the array.
Change Key
The last operation in key management is to rekey (CLI Command) or Change Key
using the GUI dropdown box. If a key needs to be changed, the process for
changing the key is as follows:
1. Generate a new key
2. Request user back up the new key
3. Rekey operation completes when new key is applied to all SEDs.
Rev. 14.1
1 –23
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Once the drives are unlocked, all functions behave as they do in any other system.
The only thing that causes drives to lock is if they lose power.
There is a delay for:

Booting- each drive must be unlocked before the system can come up.

Data Encryption management functions: Each disk must be updated
whenever keys are changed on the system
Each of these operations takes up to 3 seconds per disk and happens in several
threads.
On a system with 160 disks, enabling encryption takes ~30 seconds and booting
takes an additional ~5 seconds. A rekey under light load takes ~15 seconds.
1 –24
Rev. 14.1
complete learner guide
Drive Removal
Drive removal from the array will immediately lock access to the disk drives data. A
drive can be admitted or dismissed by the same CLI commands that are used with
the HP 3PAR OS. There are no special commands needed to admit a drive into
the array. Once admitted into the array, the drive will authenticate with the current
key store stored on the array and allow complete access to the drives media.
Node Rescue:
Node Rescue functions exactly the same as on a system without Data Encryption
enabled. The contents of the IDE drive are copied from a good node to the
rescued node, which copies over the LKM necessary for all Data Encryption
functions.
Power Failure on the Array
In the event of an untimely power failure within the data center, each drive is
protected by a unique encryption key and data cannot be accessed without that
unique key. Drives cannot be removed and put into another array for data retrieval.
Once power is restored to the data center, a normal startup of the array will restore
availability to access data stored on the array by the host systems.
Powering Down the Array
User should follow standard procedures in powering down the array. There is no
special process in powering off the array. Upon powering on the array, the local
key manager will unlock access to the hosts to allow host access to data. In testing
it was found that booting up the array with SED disks could take up to 2 minutes
more due to the key mechanism; in general it was observed that boot time was
increased by 20 – 30 seconds.
Cryptographic Erase
Cryptographic erase is the secure erasure of all data on a SED. This erasure can
be accomplished via the changes in the drive encryption key which renders the
data unintelligible or by using the CLI command “controlpd cryptoerase” to set the
bands back to initial state and crypto erase the customer data.
Rev. 14.1
1 –25
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Learning check
1.
Where the data encryption does takes place using 3PAR Data at Rest
Encryption? (Choose one.) _______________________________
a) Disk drive
b) Storage node
c) Management Server
d) Service Processor
2.
Which host-based component has to be installed for HP 3PAR Priority
Optimization?
______________________________________________________
______________________________________________________
3.
What is required to take advantage of HP 3PAR Persistent Port functionality?
______________________________________________________
______________________________________________________
______________________________________________________
4.
Can a disk be part of more than one CPG?
______________________________________________________
______________________________________________________
1 –26
Rev. 14.1
HP 3PAR StoreServ System Management
Module 6
Objectives

Rev. 14.1
After completing this module you should be able to:

Describe the different options to manage a HP 3PAR storage system

Configure and export fully and thin provisioned Virtual Volumes using HP
3PAR Management Console

Perform the Customer Orientation Session which is as part of the system
installation
6 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR – Management Options
HP 3PAR Management Client (GUI)

Storage Management GUI - Windows, RedHat Linux
CLI

HP 3PAR CLI, SSH

Storage Management Interface (very rich, complete command set)
SMI-S

Management from third party management tools (Storage Essential)
Web API

API to automate provisioning in preference to interfacing with the CLI. Input,
output, and errors are more formally defined than the CLI. RESTful Interface
(Representational State Transfer)
Service Processor
6 –2

Health checks by collecting configuration and performance data

Reporting to HP 3PAR Central

Anomalies reported back to customer

Array management
Rev. 14.1
HP 3PAR StoreServ System Management
HP 3PAR Management Console
HP 3PAR Management Console
The entire storage environment can be managed from a single window…the HP
3PAR Management Console.
The latest version of the Management Console is fully integrated with signature
3PAR applications like 3PAR Thin Provisioning, Virtual Copy, Dynamic
Optimization, Virtual Domains, and Remote Copy. Everything you need to
provision, manage, optimize, and protect your entire utility storage deployment is
at your fingertips.
For storage administrators, the Management Console provides simplicity through a
unified point-and-click interface. It provides rich instrumentation and complete
reporting capabilities. Most importantly, it eliminates the need for add-on software
tools and consulting services related to diagnosis and troubleshooting.
Rev. 14.1
6 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Create CPG(s)
System Guidelines for Creating CPGs
Use the following guidelines to ensure maximum performance and optimal
reliability in the volumes supported by those logical disks:

To provide the highest availability, chunklets in the same RAID set should
be from different drive cages, and then different drive magazines.

The system should use as many physical disks as possible.

The load on all physical disks should be balanced.
NOTE:
The system may “round up” capacities/sizes when creating logical disks to support
virtual volumes and CPGs, resulting in a discrepancy between the user-specified
size or growth increment and the actual space allocated to logical disks created by
the system.
6 –4
Rev. 14.1
HP 3PAR StoreServ System Management
Create Virtual Volume(s)
Fully provisioned virtual volumes
Fully provisioned virtual volumes have a set amount of user space allocated in the
system for user data. They require the system to reserve the entire amount of
space required by the fully provisioned virtual volume whether or not the space is
actually used. The fully provisioned virtual volume size is fixed, and the size limit is
16 TB.
Fully provisioned virtual volumes and TPVVs have three separate data
components:

The user space contains the user data and is exported as a LUN to the
host.

Snapshot space, also known as copy space, is the area containing copies
of user data that changed since the previous snapshot of the volume was
created.

Administration space, also known as admin space, contains pointers to
copies of user data in the snapshot space. Administration space is
managed by the system, not with the tools you use to manage user and
snapshot space.
Thinly Provisioned Virtual Volumes
Thinly Provisioned Virtual Volumes (TPVVs) associated with a CPG draw user
space from that pool as needed, allocating space on demand in one chunklet
increments per controller node.
Rev. 14.1
6 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
As the volumes that draw space from the CPG require additional storage, the
system automatically creates additional logical disks and adds them to the pool
until the CPG reaches the user-defined growth limit that restricts the CPG’s
maximum size. The TPVV volume size limit is 16 TB.
CAUTION:
Use of allocation limits is recommended to prevent consumption of physical raw
capacity beyond a tolerable limit. However, you should exercise caution when
setting the value of the allocation limit. Upon reaching the allocation limit, any new
writes to TPVVs will fail and/or snapshot volumes associated with the CPG may
become invalid. Under this condition, some host applications do not handle write
failures gracefully and may produce unexpected failures.
Do not allow the volumes that draw from a CPG to exceed the CPG’s growth limit.
6 –6
Rev. 14.1
HP 3PAR StoreServ System Management
HP 3PAR Host Explorer
HP 3PAR Host Explorer
The 3PAR Host Explorer is a program that runs on a host connected to an InServ
Storage Server. The Host Explorer is an agent that runs as a service on Windows
and as a daemon on Linux and Solaris operating systems. No license is required
to use the 3PAR Host Explorer.
The Host Explorer communicates with the storage server over an FC or iSCSI
connection and enables the host to send detailed host configuration information to
the storage server. The information gathered from the Host Explorer is visible for
uncreated hosts and assists with host creation and diagnosing host connectivity
issues.
The Host Explorer collects the following information and sends it to the storage
server:
Rev. 14.1

Host operating system and version

Fibre Channel and iSCSI HBA details.

Multipath driver and current multipath configuration.

Cluster configuration information.

Device and path Information.
6 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Export Virtual Volume(s)
Virtual volumes are the only data layer component visible to hosts.
You export a virtual volume to make it available to one or more hosts by creating
an association between the volume and a logical unit number (LUN). The
characteristics of this association are defined when you create a Virtual VolumeLUN pairing (VLUN).
6 –8
Rev. 14.1
HP 3PAR StoreServ System Management
HP 3PAR User management
HP 3PAR User Management
In order to access an HP Storage System, you must have a user account. Each
InForm OS user is assigned a role, and each role is assigned a set of rights. The
roles and rights assigned to the user determine which tasks the user can perform
with a system. Assign roles to users based on the tasks you intend the users to
perform.
Users accessing the HP 3PAR Storage System with the Management Console
(GUI), InForm OS CLI client, or Secure Shell (SSH) connections are authenticated
and authorized directly on the system. These users are referred to as local users.
The information used to authenticate and authorize a local user is stored on the
system.
An LDAP user is authenticated and authorized using information from a
Lightweight Directory Access Protocol (LDAP) server.
Local user roles and rights are associated with an individual. LDAP user roles and
rights are the same for all members of the group. If you want to authenticate and
authorize LDAP users with different roles, you must create an LDAP group for
each role.
Rev. 14.1
6 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Learning check
1.
What is the function of the HP 3PAR Host Explorer?
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
2.
What is the “Copy CPG” setting used for?
____________________________________________________________
____________________________________________________________
____________________________________________________________
3.
Cage Availability can be set on which level Choose one: _____________
A.
System
B.
CPG
C. Volume
6 –10
Rev. 14.1
Upgrade of Hardware and Software
Components
Module 7
Objectives
After completing this module you should be able to:
Rev. 14.1

Upgrade Controller Node

Upgrade Disk Enclosures

Upgrade Disk Drives

Upgrade PCIe Adapter

Install and upgrade HP 3PAR OS and Service Processor software
7 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Controller Node Upgrade
Controller Node upgrade
CAUTION: When performing any upgrade while concurrently using the system,
use extra precaution because an incorrect action during the upgrade process may
cause the system to fail.
Verify with the system administrator if a complete backup of all data on the storage
system has been performed. It is preferred to install controller nodes into an active
system.
Issue the following commands:
showsys to verify that your system is listed as a 7400 model and the number of
nodes is listed as 2
showhost to verify that all hosts are attached to at least two nodes
checkhealth –svc cabling to verify existing cabling is correct and output displays
as: “The following components are healthy: cabling” (no quotes on the actual
message.)
7 –2

Install the controller node enclosure

Install all drive enclosures

Install the disk drives

Cable the drive enclosures to the new controller nodes

Install node interconnect cables between nodes 0, 1 and 2

Connect Ethernet cables to the MGMT port for each new node.

Without removing any cables, pull the gray node rod to unseat node 3 from
the enclosure.

Turn power switches to ON for the new controller node enclosure PCMs.

Node rescue for node 2 auto-starts and the HP 3PAR OS is copied across the
local area network (LAN).

When the HP 3PAR OS is installed, node 2 should reboot and join the cluster.
Rev. 14.1
Upgrade of Hardware and Software Components

Wait and verify that all nodes indicate a good status and have joined the
cluster.

Install node interconnect cables between nodes 0, 1 and 3.

Push the gray node rod in to seat node 3.

Node rescue for node 3 auto-starts and the HP 3PAR OS is copied across the
local area network (LAN).

When the HP 3PAR OS is installed, node 3 should reboot and join the cluster.

Wait and verify that all nodes indicate a good status and have joined the
cluster,
Issue the following commands:
•
•
•
•
•
Rev. 14.1
showtask and locate the task ID to view the node rescue progress of
node 2 and 3
showtask -d <taskID> to view detailed node rescue status
shownode to view the new nodes
showcage to view the new enclosure
showpd to view the new disk drives
7 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Disk Enclosures Upgrade
Two types of drive enclosures are used for expansion:

HP M6710 Drive Enclosure (2U24) holds up to 24, 2.5 inch SFF SAS disk
drives

HP M6720 Drive Enclosure (4U24) holds up to 24, 3.5 inch LFF SAS disk
drives
The number of drive enclosures attached to a specific node pair should be
determined by the desired RAID set size and HA Cage protection requirements.
The first expansion drive enclosure added to a system must be populated with the
same number of disk drives as the node enclosure.
The distribution of drive enclosures between DP-1 and DP-2 of the node should be
done to achieve maximum balance across the ports.
When adding both 2U and 4U drive enclosures, they should be mixed on SAS
chains (DP1 and DP2), added in pairs across node pairs on a four-node system,
and balanced across SAS ports on each controller pair.
7 –4
Rev. 14.1
Upgrade of Hardware and Software Components
Disk Drive Upgrade
Steps for adding hard drives:
1.
Check initial status of the StoreServ system and all physical disks
2.
Verify all applicable licenses associated with the system are registered.
3.
Inserting hard drives
4.
5.

Review how to load the drives based on drive type, speed, and capacity.

Drives must added in identical pairs, leaving no empty slots between
drives

For the HP M6720 Drive Enclosure (4U24), column must filled up with
drives of the same type and rotational speed
Checking status

Inserted disk drives as New in the State column.

They are ready to be admitted into the system, which occurs
automatically
Checking progress

6.
Rev. 14.1
The State of the new disk drives changes to Normal and the system starts
to initialize the chunklets to ready for use.
Completing the upgrade

On the Physical Disks tab, in the drop-down list, select Chunklet Usage

Chunklet initialization can take several hours to complete and the output
of the available capacity is displayed.
7 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Upgrading PCIe Adapter
7 –6

Fibre Channel HBA and iSCSI CNA upgrade on the HP 3PAR StoreServ 7400
Storage system must be done by authorized service personnel and cannot be
done by a customer.

Upgrade in HP 3PAR StoreServ 7200 Storage system may be performed by
the customer.

To avoid possible data loss, only one node at a time should be upgraded. To
prevent overheating, node replacement requires a maximum service time of
30 minutes.

If two FC HBAs and two CNAs are added in a system, the FC HBAs should be
installed in nodes 0 and 1, and the CNAs should be installed in nodes 2 and 3.

The first two FC HBAs or CNAs added in a system should be added to nodes
0 and 1 for the initially installed system and for field HBA upgrades only.
Rev. 14.1
Upgrade of Hardware and Software Components
Updating the HP 3PAR OS and Service
Processor
If you need to install/update the Firmware
Launch a web browser and enter the IP address of the SP and login using the
default credentials.
Rev. 14.1

Once the main Service Processor Onsite Customer Care (SPOCC) screen is
displayed, click Update from the left menu.

Select 1 or 2 to upgrade the Service Processor software or the HP 3PAR OS
(TPD code/3 PAR Data Code)

Follow the steps that are listed on the following screens that display.
7 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Lab 3, Lab 4, Lab 5
Lab 3: Storage Configuration
Lab 4: CLI Commands
Lab 5: System upgrade
7 –8
Rev. 14.1
Upgrade of Hardware and Software Components
Learning check
1.
How can you merge two two-Node 7400 systems to one four-Node system?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
2.
What is the minimum number of disk you must add to an enclosure?
_____________________________________________________________
3.
When it is supported to install differed type of additional PCIe adapter in a
node pair?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
4.
Which command should be use to verifying the Health of the Storage System
before and after the update?
_____________________________________________________________
_____________________________________________________________
Rev. 14.1
7 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
7 –10
Rev. 14.1
Maintenance Tools and Resources
Module 8
Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the HP 3PAR Remote Support infrastructure

Access call home data using STaTS

Set Service Processor in Maintenance Mode

Use Events and Alerts to monitor system status

Setup local notification
8 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Standard user names and passwords
Standard user names and passwords
Available common and standard user names and passwords are shown in the
graphic.
8 –2
Rev. 14.1
Maintenance Tools and Resources
Best security practices

Change the password for the 3paradm user

Change the 3parcim user if the CIM/SMI-S service is enabled

Do not change the password or remove user accounts

3parsvc

3parservice

3paredit

3parbrowse

Create a different user for each system administrator

Configure the system to use Active Directory

Make sure each user uses their own account to log in to the
system

Use the lowest privilege level required

Use a Browse account

For scripts that require read-only access

If Adaptive Optimization is not required

Do not use a Super user for the System Reporter user

Use a 3PAR_AO user if Adaptive Optimization is required
Best Practices
HP best practices for 3PAR system management include:

Change the password for the 3paradm user. The password of the 3parcim
user should also be changed if the CIM/SMI-S service is enabled.

Rev. 14.1
Important! Do not change the password or remove the accounts for the
3parsvc, 3parservice, 3paredit or 3parbrowse users. These are randomly
generated at the time of the initialization of the system and are required
for communication between the Service Processor and the system.

Create a different user for each system administrator who will use the system,
or configure the system to use Active Directory. Make sure that users use their
own accounts to log in to the system.

When scripting, use the lowest privilege level required. If a script requires only
read access to the system, use a Browse account. If a script does not need to
remove objects, use a Create account. Do not use a Super user (such as
3paradm) for the System Reporter user. Use a Browse user if Adaptive
Optimization is not required, or a 3PAR_AO user if Adaptive Optimization is
required.
8 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR Remote Support
HP 3PAR Remote Support
HP provides a global support infrastructure for 3PAR arrays that leverages
advanced system and support architectures for fast, predictive response and
remediation. HP leverages an advanced services model whereby HP 3PAR array
expertise is maintained remotely. An advanced toolset, coupled with the HP 3PAR
Secure Service Architecture, extends the capabilities of a smaller number of
trained, onsite technicians complemented by highly experienced experts via the
HP’s 3PAR Central infrastructure.
HP 3PAR Global Services and Support team support with a combination of expertonly support staff; automated analysis and reporting that assures accuracy and
consistency. It includes full system information in-hand that reduces onsite
dependencies; and fully-scripted and tested, automated point-and-click service
actions that reduce can human error.
HP 3PAR Global Services and Support team delivers rapid, proactive response
with complete 24x7 remote monitoring and analysis to identify issues and
proactively communicate them to customers. They provide integrated support
model with shared information access for quick problem resolution; and “lights out”
online remote software updates and service actions that eliminate scheduling and
onsite visit delays.
8 –4
Rev. 14.1
Maintenance Tools and Resources
HP 3PAR Central
HP 3PAR Central represents HP’s 3PAR 24x7 Support Centers, along with an
infrastructure that combines integrated processes, tools, procedures, and people
that work in unison to solve customers’ problems.
HP 3PAR Secure Service Collector Server
The HP 3PAR Secure Service Collector Server serves as the central collection
point at HP’s 3PAR Central for all diagnostic data transfers from the HP 3PAR
Storage Systems and also serves as the gateway for all remote connections to the
HP 3PAR systems at the client sites. The Collector Server does not initiate the
remote connection. Instead, the Collector Server embeds a remote connection
request in its response to the normal periodic communication with the Service
Processor. The Collector Server communicates with the Secure Service Custodian
by posting requests for the Custodian and receiving its responses. These can be
requests to perform actions, including uploading files, running applications,
restarting, executing packages, setting data values on the Custodians, and so
forth. The requests are discovered by the Custodian upon subsequent pings. If a
Custodian is managed by the Policy Manager, the Custodian will first reference its
policy to determine whether or not it can perform the action.
Policy Manager
Policy Manager is an optional feature, purchased separately, that is designed to
work together with Secure Network Mode (SNM). The software is loaded onto a
customer server and is completely customer-controlled. Policy Manager enables
customers to control and monitor communications between the 3PAR Secure
Service Custodian (Custodian) and the 3PAR Secure Service Collector Server
(Collector Server). Policy Manager can be installed to enable only authorized
access and use of the managed Custodians. It manages all operations the
Collector Server requests to perform on Custodians, and a subset of actions a
Custodian will perform based on its own configuration. The list of managed
operations includes Custodian-specific actions, remote access connections to the
Custodian, file uploads, script and package registration and execution, and more.
Note: Secure Service Custodian resides on the SP.
Rev. 14.1
8 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP proactive resources
Secure Network Mode
This is the recommended method of connectivity. It is secure, easy for customers
to implement in their firewalls, and offers customers more access control options.
Secure Network Mode (SNM) utilizes the HP-3PAR Secure Service Architecture
(SSA). The HP-3PAR SSA provides secure service communication between the
HP-3PAR InServ Storage Servers at a customer’s site and HP-3PAR Support
Portal, enabling secure diagnostic data transmission and remote service
connections. Diagnostic data can be transferred frequently and maintained
centrally on a historical basis. As a result, manual intervention in the support
process is minimized and pro-active fault detection and analysis is enhanced.
Further, with remote operations connectivity for troubleshooting, HP-3PAR
Customer Service and Engineering can deliver the fastest, most reliable response
and quickest resolution time.
The Secure Service Architecture leverages the industry-standard HTTP over
Secure Socket Layer (HTTPS) protocol for all external communication, ensuring
that the communication is secure and any data transmission is encrypted. The
Secure Service Architecture is also firewall friendly. HP-3PAR only requires that
HTTPS Port 443 be enabled on the customer’s external firewall, and all
communication with HP-3PAR support portal is initiated in an outbound manner.
If all of the information required is provided, SNM is usually configured during
installation time.
8 –6
Rev. 14.1
Maintenance Tools and Resources
The customer requirements for SNM are as follows:
Port 443 open (industry standard HTTPS port) for file transfer and remote
operations. This can also be enabled anytime after the install by scheduling the
change with the HP-3PAR Service Planning Specialist (SPS) team. The HP-3PAR
SPS team will engage the HP-3PAR National Technical Support Specialist (NTSS)
or 3PAR Deployment Center (3DC) team to plan and support the activity. The SPS
team will also schedule the activity with the customer. Please note that the inbound
connection is only needed for remote operations and it does not need to remain
open constantly. Both the inbound and outbound access can be controlled by the
customer via the Customer Controlled Access (CCA) setting on the Service
Processor. This setting can be modified by the customer at any time.
Rev. 14.1
8 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR STaTS
HP 3PAR STaTS
HP 3PAR Service Tools and Technical Support (STaTS) is the main tool that TS
uses to access call home data. Use HP Smart Portal to access STaTS:
Axeda facilitates the communication between the remote array and the support
center.
STaTS is the tool that internal support uses to view and retrieve that data AFTER it
has been communicated back.
Overall, the process would be:
8 –8

Customer configures the SP (SPOCC) to send data to 3PAR

Array sends data (Using Axeda) to 3PAR, securely

Support staff uses STaTS to retrieve the data sent home.
Rev. 14.1
Maintenance Tools and Resources
STaTS Display tab
STaTS Display tab
The STaTS Display tab enables you to filter on log files sent home.
The table shows a description of each filter found on the STaTs Display tab.
Rev. 14.1
8 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
STaTS Sites tab
STaTS Sites tab
The Sites tab enables you to look at site information and detailed views of
products associated with the site.

The Search box can be used to enter serial numbers or customer names.

The Results list allows you to view the site to drill down for more information.
The detail on the STaTS Sites tab provides an overview of the site. The top section
details the site Name, Location, and Site Specific Details. The bottom section
details each serial number associated with the site.
8 –10
Rev. 14.1
Maintenance Tools and Resources
STaTS Notify tab
STaTS Notify tab
The STaTS Notify tab allows you to set up email notifications.

Add—Create a notification record.

Manage—Search is available to make managing notifications easier.

Symptom—Configuration option to enable a specific notification.

Suppression—Configuration option to disable a specific notification.
STaTS Support tab
STaTS Support tab
The FRU Parts-DB is under the Support tab.
Rev. 14.1
8 –11
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
This is important for part number lookup for 3PAR legacy products.
The other functions within this section are utilized specifically by the 3PAR support
center to support legacy 3PAR products.
STaTS Admin
STaTS Admin
The Admin menu provides a user with access to administrative functions. Some of
the utilities allow you to organize users and products. Other utilities are provided
for controlling how products are handled.
STaTS Reports
STaTS Reports
Several different reports are available from the reports tab.
8 –12
Rev. 14.1
Maintenance Tools and Resources
STaTS Sales Upgrade
STaTS Admin—Sales Upgrade
The sales upgrade tool allows you to retrieve configuration data based on the

7-digit 3PAR serial number or

10-digit HP serial number
This window displays an overview of the configuration, as well as additional
information on Licenses, Nodes and Cages. This information is gathered from the
config file and put into a more user friendly format.
Rev. 14.1
8 –13
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Collecting configuration information from
STaTs
Locate the report you want and click the adjacent view.
On the Log Display, click View catalog.
Click the File Name hyperlink and select Save As.
You can change the name of the file, adding htm to the end of the name
(recommended), and select Save.
After you save the file, you can open it to view the configuration of the storage
system.
8 –14
Rev. 14.1
Maintenance Tools and Resources
STaTS Data Overview—Configuration Data
Customer Configuration—How the customer has configured the
HP 3PAR storage array.

Domains, Hosts, CPGs, VVs, VLUNs, etc.
Hardware Configuration—What hardware makes up the HP
3PAR storage array.

Nodes, Memory, Ports, Drive Cages, Drives, etc.
Software Configuration—What software levels and features are
used.

Licenses, Levels, Patches, Firmware, etc.
Customer Configuration shows the customer configuration of the HP 3PAR storage
system, including:

Domains, Hosts, CPGs, VVs, VLUNs, etc.
Hardware Configuration is what hardware makes up the HP 3PAR storage array,
including:

Nodes, Memory, Ports, Drive Cages, Drives, etc.
Software Configurationis shows what software levels and features are used,
including:

Rev. 14.1
Licenses, Levels, Patches, Firmware, etc.
8 –15
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
STaTS Data Overview—Performance data
Snapshots in time on how the 3PAR storage array is performing.

Node Performance
 Memory usage, CPU utilization, Port bandwidth.

Cage Performance
 Disk Port Bandwidth.

PD Performance
 Disk IOPs, Disk throughput.

Configuration Performance
 VLUNs, VVs.
STaTS Data Overview—Performance data
Snapshots in time on how the 3PAR storage array is performing:

Node Performance


Cage Performance


Disk IOPs, Disk throughput.
Configuration Performance

8 –16
Disk Port Bandwidth.
PD Performance


Memory usage, CPU utilization, Port bandwidth.
VLUNs, VVs.
Rev. 14.1
Maintenance Tools and Resources
STaTS Data Overview—Event Data
Real Time event monitoring
System events are sent home real-time for pro-active system
monitoring:

Node failures


Cage failures


Disks, FCALs, drive magazines, disks, etc.
Configuration failures


Memory, IDE Disk, Port failures, software panics, etc.
Growth failures, capacity usage information, etc.
Feature failures

Remote Copy, System Tuning, etc.
STaTS Data Overview—Event Data
In STaTS Data Overview, system events are sent “home” real-time for pro-active
system monitoring, including:

Node failures


Cage failures


Growth failures, capacity usage information, etc.
Feature failures

Rev. 14.1
Disks, FCALs, drive magazines, disks, etc.
Configuration failures


Memory, IDE Disk, Port failures, software panics, etc.
Remote Copy, System Tuning, etc.
8 –17
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
STaTS Data Overview—Diagnostic data
Collection of files for troubleshooting the 3PAR storage array or
monitoring devices.

Insplore (3PAR array troubleshooting files)

Splor (SP troubleshooting files)

Cpsplor (Custodian troubleshooting files)

Application panics

Node Software panics

Firmware Cores
STaTS Data Overview is a collection of files for troubleshooting the 3PAR storage
array or monitoring devices, including:
8 –18

Insplore (3PAR array troubleshooting files)

Splor (SP troubleshooting files)

Cpsplor (Custodian troubleshooting files)

Application panics

Node Software panics

Firmware Cores
Rev. 14.1
Maintenance Tools and Resources
STaTS Data Overview—Sample log types
STaTS Data Overview—Sample log types
The table shows a sample of log type filenames with a system name, description,
and interval for each.
Rev. 14.1
8 –19
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Service Processor Maintenance Mode
Time-based setting on the SP that will turn-off pro-active
monitoring

Should be used during

Installation

Hardware Upgrades

Software Updates

Repair Activities

Available in SP-2.3.1 and above.

Timer “expires” after time specified

Can be set off at any time

Events are forced to “low” urgency

Provides local control for repair activities
Maintenance mode is a time-based setting on the SP that will effectively turn-off
pro-active monitoring while set. This will reduce the burden on the pro-active
monitoring team when performing maintenance.
File transfer will still be operational. However, since the spevent and the spcollect
processes are stopped when maintenance mode is set, the SP will not be
collecting periodic files or events from the storage server.
While in maintenance mode, remote operations is not impacted.
Installation
After installation, demos on the system may be performed which cause call home
activity that may not be necessary.
8 –20
1.
Put a system is into maintenance mode right after the system is configured on
the SP.
2.
The system should be removed from maintenance mode once all onsite
activity is complete.
3.
System health should be verified.
Rev. 14.1
Maintenance Tools and Resources
Hardware Upgrades
Adding hardware to the system will generate a lot of events. Maintenance mode is
ideal for these situations.
1.
Put a system into maintenance prior to performing a hardware upgrade.
2.
The system should be removed from maintenance mode once all onsite
activity is complete.
3.
System health should be verified.
Software Updates
Software updates will generate a lot of events. Maintenance mode is ideal for
these situations.
1.
Put a system is into maintenance mode prior to performing a software update.
2.
The system should be removed from maintenance mode once all the software
update activity is complete.
3.
System health should be verified.
Repair Activities
Repair activities may be soft in nature (rebooting a node) or the replacement of a
hardware component. Maintenance mode should be used for these activities.
Rev. 14.1
1.
Put a system is into maintenance mode prior to performing a repair activity.
2.
The system should be removed from maintenance mode once all activity is
complete.
3.
System health should be verified.
8 –21
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Best Practices
8 –22

The system health should be verified after completion of any activity.

At anytime, maintenance mode can be exited, so that the SP can collect and
transfer files.

Better to set for longer duration and then manually set off when the activity is
completed.
Rev. 14.1
Maintenance Tools and Resources
Both management interfaces (SPOCC and SPMAINT) can be used to enable and
disable Service Processor Maintenance Mode
Rev. 14.1
8 –23
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Events, Alerts and Local Notification
Alerts overview
When a critical threshold is encountered or a component fails, an
alert is:


Triggered by the InForm OS
Sent to the CLI, Management Console, and the HP 3PAR
service processor

HP 3PAR Central is notified

Alert is recorded in a log file
The system uses alerts to:

Trigger automated action

Notify service personnel

That action has been taken

That action might need to be scheduled
Alerts overview
Alerts are system events that require immediate attention. An alert might be
triggered by a single event, a combination of events, or by repeated occurrences
of the same event. The system administrator is responsible for responding to
alerts.
When a critical threshold is encountered or a component fails, an alert is triggered
by the InForm OS and is sent to the CLI, Management Console (MC), and the HP
3PAR Service Processor (which either notifies HP 3PAR Central, the HP 3PAR
centralized support center, or records the alert in a log file). These alerts are used
by the system to trigger automated action and to notify service personnel that
action has been taken (or might need to be scheduled).
Note: For detailed information about alerts, refer to the InForm OS Messages and
Operator’s Guide available from the HP website.
8 –24
Rev. 14.1
Maintenance Tools and Resources
Alert message codes
Alerts are triggered by events that require intervention by the
system administrator.
To view the alerts, use showalert
Alert message codes have seven digits in the following schema

AAABBBB, where:

AAA is a 3-digit "major code"

BBBB is a 4-digit sub-code

0x precedes the code to indicate hexadecimal notation
Alert message codes
Alert message codes have seven digits, as follows:

AAABBBB, where:

AAA is a three-digit major code.

BBBB is a four-digit sub-code.

0x precedes the code to indicate hexadecimal notation.
Message codes ending in de indicate a degraded state alert.
Message codes ending in “fa” indicate a failed state alert.
Rev. 14.1
8 –25
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Sample InForm message
Message code

0x0030009
Type

Excessive retransmits on RCFC port or excessive RCFC
retransmits
Message

Excessive RCFC retransmits at nn% on node x (where
x=node number)
State


Alert is generated when a node detects that the RCFC
retransmit rate has exceeded 2%
Alert will clear after the rate drops below 0.5%
Suggested action

8 –26
The Fibre Channel fabric might have issues that could affect
the throughput

Wait 10 minutes until the RCFC statistics are polled

Alert should be cleared after the rate drops below 0.5
Rev. 14.1
Maintenance Tools and Resources
Monitoring and managing InForm OS alerts
Viewing alerts

To display system alerts, issue the showalert command

You can additionally display alerts by type
Setting an alert state



New, fixed, or acknowledged
Issue the setalert new|fixed|ack <alert_ID>
command
<alert_ID> is the alert whose status you wish to
acknowledge
Removing an alert

Issue the removealert <alert_ID> command

<alert_ID> is the alert you wish to remove
Monitoring and managing alerts


Viewing alerts

To display system alerts, issue the showalert command.

You can additionally display alerts by type (fixed alerts, acknowledged
alerts, and so forth). Refer to the InForm OS Command Line Interface
Reference for information about alert display options.
Setting an alert state


Removing an alert

Rev. 14.1
To mark an alert as new, fixed, or acknowledged, issue the setalert
new|fixed|ack <alert_ID> command, where <alert_ID> is the alert whose
status you wish to acknowledge.
To remove an alert, issue the removealert <alert_ID> command, where
<alert_ID> is the alert you wish to remove
8 –27
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Setting system alerts
Most system alerts are generated automatically
Several types of alerts can be configured to trigger alerts:

Limits relating to CPG

Limits for virtual volumes

Raw space alert
Four default system thresholds alert when available space
falls below

50%

75%

85%

95%
Setting system alerts
Although most system alerts are generated automatically without any need for
user configuration, there are several types of alerts that you can specifically
configure.

Limits relating to Common Provisioning Groups (CPG) can be set when
creating a CPG and can later trigger alerts.
For details about CPG creation precautions, refer to the InForm OS Concepts
Guide.

Limits for virtual volumes capable of allocating space on demand are also
user-configurable and can trigger alerts. For information about on-demand
virtual volume space allocation, refer to the InForm OS Concepts Guide.

The raw space alert is a global threshold that can be set for the storage
system in order to alert administrators when available space on the system
falls below a user-specified level. When the available space on the storage
system falls below this user-specified threshold, an alert is generated.
There are also four default system thresholds, which alert you when the available
space on the system falls below 50%, 75%, 85%, and 95% of the total available
space on the system. When the user-defined threshold is set, alerts for system
thresholds below the user-defined threshold are suppressed.
8 –28
Rev. 14.1
Maintenance Tools and Resources
Viewing alerts using InForm GUI
Viewing alerts using InForm GUI
The InForm OS GUI provides two methods for viewing alerts:
Rev. 14.1

View the Alert Pane.

Select Events from the InForm GUI.
8 –29
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Monitoring and managing the event log
Eventlog has information about all notable occurrences on
the system
System events include

All alerts the system has generated

Alerts marked as acknowledged or fixed
Viewing the event log

Issue the showeventlog command
Removing the Event Log

Issue the removeeventlog command
Monitoring and managing the event log
The eventlog has information about all notable occurrences on the storage system.
System events include all alerts the system has generated and alerts marked as
acknowledged or fixed. These system events are generated and logged in the
system events log.
Note: For detailed information about the events log, see the InForm OS Concepts
Guide.


Viewing the Event Log

To view the events log, issue the showeventlog command. The
eventlog display can be refined to include only events occurring before or
after a specified time, within a specified time period, and that match a
specified pattern.

Note: For complete information on the events log’s display options, see
the InForm OS Command Line Interface Reference.
Removing the Event Log

8 –30
To remove all event logs with severity Debug from the system, issue the
removeeventlog command. The removeeventlog command
removes all event logs with severity Debug from the system.
Rev. 14.1
Maintenance Tools and Resources
Automated Over-Subscribed System Alerts
OSSA



Performs proactive utilization checks on key system elements
using data that resides at HP
Collects data periodically from the storage server and sent to
HP
Provide clients with valuable information to keep the storage
systems running optimally
System Reporter software


Enables customers to set thresholds and alert on
components and configure a custom set of alerts
Adds new metrics dynamically as needed
Automated Over-Subscribed System Alerts
All HP 3PAR storage systems support a complimentary support service, known as
Over-Subscribed System Alerts (OSSA), in addition to and concurrent with
automated remote monitoring, alerting, and notification. This automated monitoring
tool performs proactive utilization checks on key system elements using data that
resides at HP. This data is collected periodically from the HP 3PAR storage server
and sent to HP. The intent is to provide clients with valuable information to keep
the HP 3PAR storage systems running optimally.
In addition, System Reporter software enables customers to set thresholds and
alert on components and configure a custom set of alerts.
New metrics are added dynamically as needed.
Some of the metrics currently checked include:
Rev. 14.1

Storage node controller CPU utilization

Disk IOPS (per device type, to highlight potential spindle-bound applications
and overloaded systems)

The amount of host initiators per port (guards against over-subscription and
untested configurations)

Total host initiators per system

PCIe bus bandwidth

Port bandwidth (per host and disk facing system ports)
8 –31
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Local Notification
Local Notification
The Service Processor’s local notification features enable you to request that they
be notified of important storage system events and alerts on a subscription basis.
Notifications are sent through email to all subscribers, with each subscriber
specifying up to three email addresses.
When Real-time Alert Processing (RAP) forwarding is enabled, copies of all
notification messages sent to subscribers are automatically forwarded to HP 3PAR
Central as well. (no longer supported)
Before you can create a notification record and receive local notification
messages, at least one user profile must be created.
There are three types of local notification records:
8 –32

Normal - This type of notification record is for when you want to be notified of
events and alerts concerning a particular storage system.

Symptom - This type of notification record is for when you want to be notified
of a particular symptom concerning a particular storage system.

Suppression - This type of notification record enables you to selectively
suppress notifications generated as a result of a specific symptom.
Rev. 14.1
Maintenance Tools and Resources
Setting up Local Notification
Local Notification setup
To enable local notification access:
Rev. 14.1

In the SPOCC menu, click Setup.

Under Notification Maintenance Utilities, click Configure Mailhost.

Under Notification Maintenance Utilities, click Enable Local Notification.

In the SPOCC menu, click Notify.

Add User to User Profiles and Records to the Notification List as required.
8 –33
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Learning check
1. When you should set the Service Processor in Maintenance Mode?
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
2. Where does Local E-Mail Notification can be set? Choose one: _____________
a) Storage Node
b) Service Processor
c) Server running HP 3PAR Management Console
3. Which tool can be used to access call home data?
___________________________________________________________________
4. Which port needs to be enabled to allow remote access?
___________________________________________________________________
8 –34
Rev. 14.1
HP 3PAR StoreServ 7000 Storage
Troubleshooting
Module 9
Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the power on/off procedures

Use “checkhealth” to verify system status

Interpret the various error indicators/LED-codes

Remove and replace System Components using Guided Maintenance

Remove and replace System Components using CLI command as described
in the related troubleshooting guides.

Perform a Node Rescue
9 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Powering Off/On the Storage System
Powering Off

Use either SPmaint or SPOCC to shut down and power off

This will not switch off the power line
Powering On

Power on the drive enclosure first
Powering Off

Shutdown the node:
a) To use the CLI in SPmaint, access the 3PAR Service Processor Menu,
select:

4 InServ Product Maintenance

6 Halt an InServ cluster/node

the desired node and confirm all prompts to halt the node
b) Or to use Guided Maintenance in SPOCC, access Guided Maintenance:


In the Guided Maintenance window, click Controller Node

In the Node Rescue Task Information section, select the node to shut
down from the Node ID field, and then click Shutdown Node.

In the Node Status Information section, click Refresh to confirm the
node has been shut down and the node is no longer in the cluster.
Allow 2-3 minutes for the node to halt, and then verify that the node Status
LED is flashing green and the node Hot–plug LED is blue indicating that the
node has been halted.
Powering On
The following is the power on sequence for the storage system:
9 –2
1.
Set the circuit breakers on the PDUs to the ON position.
2.
Set the switches on the power strips to the ON position.
3.
Power on the drive enclosure PCMs.
4.
Power on the node enclosure PCMs.
5.
Verify the status of the LEDs
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Troubleshooting
checkhealth command

checks the status of a system hardware and software components, and
reports any issues
CBIOS Error Codes

LED Blink Codes
InForm OS Failed Error Codes and Resolution

code, sub-code and a message
checkhealth command
The HP 3PAR OS CLI checkhealth command checks and displays the status of
storage system hardware and software components. For example, the checkhealth
command can check for unresolved system alerts, display issues with hardware
components or display information about virtual volumes that are not optimal.
The checkhealth-svc option is hidden to all users and it is only available to users
with Super CLI accounts. The -svc option provides a summary of service related
issues by default; if you use the -detail option, both a summary and a detailed list
of service issues are displayed. The service information displayed is for service
providers only because it may produce cryptic output that only a service provider
would understand, or display issues that only a service provider can resolve. The
-svc option displays the service related information in addition to the customer
related information.
Use the checkhealth-list command to list all the components that can be analyzed
by the checkhealth command.
CBIOS Error Codes
The two stacked LEDs located on the face of each node in the chassis are used by
the CBIOS to communicate status and error conditions.
InForm OS Failed Error Codes and Resolution
These hardware error codes occur while the InForm OS is running, not in CBIOS
mode. Each error will present the following data when triggered: code, sub-code
and a message.
Rev. 14.1
9 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Troubleshooting Storage System Setup

Storage System Setup Wizard Errors

Collecting SmartStart Log Files

Collecting Service Processor Log Files
If you are unable to access the SP setup wizard, the SP, or the Storage System
Setup wizard:
1. Collect the SmartStart log files.
2. Collect the SP log files.
3. Contact HP support and request support for your StoreServ 7000
Storage product.
You may see the following error messages in the Storage System Setup
Wizard.
Common error strings that appear in multiple places:

“The specified system is currently in the storage system initialization process.
Only one initialization process can run at one time.”
This message displays when the wizards of two users try to initialize the same
storage system on the same SP. Only one wizard can initialize a storage
system. Two options are available when this error displays in a dialog box; you
can click Retry or Cancel. When the error does not display in a dialog box,
but rather inline, look for another SP by serial number or wait a while and try
again later.

“Unable to start SysManager. Make sure the storage system is running and in
manual startup mode.”
Turn the storage system on and make sure it is running in manual startup
mode. This message displays either in a dialog box or inline. If the message
displays in a dialog box, you can click Retry or Cancel in the wizard. If the
message appears inline, you can only click Next in the wizard.

“Could not communicate with the server. Make sure you are currently
connected to the network.”
This message displays when the client computer that is running the wizard
cannot communicate with the SP, such as when network connectivity is lost.
The error can occur for one of the following reasons:
9 –4

Network connectivity is lost.

The SP is no longer running.

The SP is not plugged into the network.

The SP IP address has been changed.
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting

"Could not communicate with the storage system. Make sure it is running and
connected to the network."
This message can display if the HP 3PAR OS loses network connectivity,
either by becoming unplugged or by going down for some other reason. This
message displays either in a dialog box or inline. If the message displays in a
dialog box, you can click Retry or Cancel in the wizard. If the message
appears inline, you can only click Next in the wizard.

"Setup encountered an unknown error ({0}). Contact HP support for help."
This message displays in a dialog box with Retry and Cancel buttons, where
{0} is the error number.

"Unable to execute the command. All required data was not sent to the SP
server. Contact HP support for help."
This message displays as an inline error on the bottom of the wizard page.

"No uninitialized storage system with the specified serial number could be
found. Make sure the SP is on the same network as the specified storage
system. "
This message displays as an inline error on the bottom of the wizard page. In
order for the Storage System Setup Wizard to work, the storage system must
be on the same network as the SP, and you must type in the serial number of
the storage system in order for the SP to find it. If either of these conditions is
not met, this error message displays.
Verify that the serial number you entered for the SP is correct, and then do
one of the following:


Move the SP or storage system so that they are on the same network.

Use a different SP to set up the storage system.
“Unable to gather the storage system information. Make sure the specified
storage system is running HP 3PAR OS 3.1.2 or later. For more help, contact
HP support."
This message displays as an inline error on the bottom of the wizard page.
The error might be caused by a defect in the Storage System Setup Wizard
code or by unexpected information being returned in the CLI.

“The SP encountered an unknown error while finding the specified storage
system. Contact HP support for help.”
This message displays as an inline error on the bottom of the wizard page.

“The SP does not have a suitable HP 3PAR OS version installed for the
specified storage system. Use SPOCC to install HP 3PAR OS version {0}."
This message displays as an inline error on the bottom of the wizard page.
The SP needs to have the same Major.Minor.Patch TPD package as the
storage system’s HP 3PAR OS. If the package is not the same, then the SP
does not know how to communicate with the HP 3PAR OS. {0} will be the
version of the TPD package that the user must install so that the SP will work
with the storage system.

Rev. 14.1
"The SP does not have an HP 3PAR OS version installed. Use SPOCC to
install an HP 3PAR OS package."
9 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
This message displays as an inline error on the bottom of the wizard page
when no TPD package is installed. The SP needs a TPD package installed in
order to communicate with an HP 3PAR StoreServ Storage system.

"The storage system has not yet discovered all the drive types. Make sure
there are no cage problems.”
This error message displays in a dialog box with Retry and Cancel buttons. It
occurs when the HP 3PAR StoreServ Storage is unable to determine all the
drive types that are connected to the cage. Wait for about 5 minutes for drive
discovery to complete. If the error persists, contact HP Support.

"The storage system has not yet discovered all the drive positions. Make sure
there are no cage problems."
Wait for about 5 minutes for drive position discovery to complete. If the error
persists, contact HP Support.

“The storage system found an error while checking node health. Details are
listed below. {0} appears to be offline. Make sure the node is plugged in all the
way and powered on."
This error message displays in a dialog box with Retry and Cancel buttons. {0}
is the name of the node that appears to be offline. Turn the storage system on
and make sure the node is plugged into the backplane.

"The storage system found an error while checking node health. Details are
listed below."
This error message displays in a dialog box with Retry and Cancel buttons. {0}
is the port location with the problem. Make sure the port is plugged into the
node.

"The storage system found an error while checking port health. Details are
listed below. Port {0} appears to be offline."
This error message displays in a dialog box with Retry and Cancel buttons.
Information listed below the message is the CLI output for the chechhwconfig
command, which occurs when the SP does not recognize the command,
allowing you to see the output.

"The storage system found an error while checking port health. Details are
listed below."
This error message displays in a dialog box with Retry and Cancel buttons. {0}
is the location of the port with the problem.

“The storage system found an error while checking cage health. The firmware
upgrade succeeded, but cage {0} has not come back. Contact HP support for
help."
This error message displays in a dialog box with Retry and Cancel buttons.
This error might occur after the drive cages have had a firmware upgrade. {0}
will be the name of the cage with the problem. Although the firmware upgrade
may have succeeded, this error might occur if the cage does not boot back up.
Contact HP Support. For information about contacting HP Support, see
“Contacting HP Support about System Setup ” .
9 –6
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting

"The storage system found an error while checking cage health. Details are
listed below."
This error message displays in a dialog box with Retry and Cancel buttons.
Information listed below the message is the CLI output for the chechhwconfig
command, which occurs when the SP does not recognize the command,
allowing you to see the output. For information about contacting HP Support,
see “Contacting HP Support about System Setup”.

“The storage system found an error while checking cage health. There is a
problem with a drive cage that has had a firmware upgrade. Cage {0} did not
come back after the firmware upgrade. Contact HP support for help.”
This error message displays in a dialog box with Retry and Cancel buttons.
This error might occur after the drive cages have had a firmware upgrade. {0}
will be the name of the cage with the problem. Contact HP Support.

"Unable to set the storage system network configuration. The storage
system's admin volume has not been created. This must be created before
any networking information is set. Contact HP support for help."
This message displays in a dialog box with Retry and Cancel buttons. This
error occurs if a previous command failed and the wizard did not detect the
error, or if the system is rebooted for any reason during the installation. Click
Cancel to close the wizard, and then begin the setup process again. For
information about contacting HP Support, see “Contacting HP Support about
System Setup ” .

"Unable to set the storage system network configuration. An invalid name was
specified. A storage system name must start with an alphanumeric character
followed by any combination of the following characters: a-z, A-Z, 0-9, period
(.), hyphen (-), or underscore (_)."
This message displays in a dialog box with Retry and Cancel buttons. A
storage system name must contain at least 6 characters, must begin with an
alphanumeric character, and must include at least one of each of the following
characters: lowercase letters (a-z); uppercase letters (A-Z); numbers (0-9);
and a period (.), a hyphen (-), or an underscore (_). Click Cancel to close the
wizard, and then begin the setup process again.

"Unable to set the storage system network configuration. An invalid IPv4
address was specified."
This message displays in a dialog box. The error occurs if the storage system
detects that the defined storage system name is invalid. Click Back and
specify a valid IPv4 address.

"Unable to set the storage system network configuration. An invalid subnet
was specified."
This message displays in a dialog box. The error occurs if the storage system
detects that the defined subnet address is invalid. Click Back and specify a
valid subnet address.
Rev. 14.1
9 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix

"Unable to set the storage system network configuration. An invalid IPv4
gateway was specified."
This message displays in a dialog box. The error occurs if the storage system
detects that the defined IPv4 gateway address is invalid. Click Back and
specify a valid IPv4 gateway address.

"Unable to set the storage system network configuration. The specified IPv4
gateway address is not reachable by using the specified storage system IPv4
address."
This message displays in a dialog box. The error occurs if the storage system
detects that the defined IPv4 gateway address could not be reached. Click
Back and specify a valid IPv4 gateway address. If the error persists, contact
HP Support.

"Unable to set the storage system network configuration. The storage system
IPv4 address cannot be the same as the IPv4 gateway."
This message displays in a dialog box. The error occurs if the storage system
detects that the defined IPv4 gateway address is the same as the configured
IPv4 address. Click Back and specify a different address for the IPv4 gateway
address.

"Unable to set the storage system network configuration. The specified
address is already in use by another machine."
This message displays in a dialog box. The error occurs if the storage system
detects that the defined IPv4 address is already in use by another machine.
Click Back and specify a different IPv4 address.

"Unable to set the storage system network configuration. The storage system
could not be reached at the new IP address. Make sure your network settings
are configured correctly."
This error message displays in a dialog box with Retry and Cancel buttons.
This error displays when the SP is unable to reach the storage system at the
new IP address. Click Cancel to close the wizard, and then begin the setup
process again.

"Unable to set the storage system network configuration. The storage system
did not recognize its new IP address as being validated."
This error message displays in a dialog box with Retry and Cancel buttons.
This error displays when the SP reaches the storage system at the new IP but
fails to recognize that the SP was able to do this. Click Back and specify a
valid IP address. if the error persists, contact HP Support.

"Unable to set the storage system NTP server. An invalid address was
specified."
This error message displays in a dialog box. This error displays if the storage
system detects that the NTP address is invalid. Click Cancel to close the
wizard, and then begin the setup process again.

9 –8
"Unable to set the storage system NTP server. The storage system's admin
volume has not been created. This must be created before any networking
information is created. Contact HP support for help."
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
This error message displays in a dialog box with Retry and Cancel buttons.
This error occurs if a previous command failed and the wizard did not detect
the error, or if the system was rebooted for any reason during installation.
Click Cancel to close the wizard, and then begin the setup process again. For
information about contacting HP Support, see “Contacting HP Support about
System Setup”.

"Unable to set the storage system time zone. An invalid time zone was
specified."
This error message displays in a dialog box. This error occurs if the storage
system detects that an unfamiliar time zone was selected. Click Back and
specify a valid time zone.
Collecting SmartStart Log Files
To collect the SmartStart log files for HP support, zip all the files in this folder:
C:\Users\<username>\SmartStart\log .
Collecting Service Processor Log Files
To collect the SP log files for HP support:
1.
Connect to Service Processor Onsite Customer Care (SPOCC): type the
SP IP address in a browser.
2.
From the navigation pane, click Files .
3.
Click the folder icons for files, syslog, apilogs .
4.
In the Action column, click Download for each log file:
5.

SPSETLOG.log
Service Processor setup log

ARSETLOG.system_serial_number.log
Storage System setup log

errorLog.log
General errors
Zip the downloaded log files.
Contacting HP Support about System Setup
Before contacting HP, collect the following information:

SmartStart log files

SP log files

Product model names and numbers

Technical support registration number (if applicable)

Product serial numbers

Error messages

Operating system type and revision level

Detailed questions
When you contact HP, specify that you are requesting support for your
StoreServ 7000 Storage product.
Rev. 14.1
9 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Remove and Replace System Components
Guided Maintenance
When a system component is marked as failed, the preferred method of isolating
the component for service is by accessing the Guided Maintenance portion of the
SPOCC page on the SP.
To open SPOCC, enter the SP IP address in a web browser and enter your user
name and password. Use Guided Maintenance when servicing the following
hardware components:
•
controller node
•
node disk
•
DIMMs
•
Time of date battery
•
HBA
To access Guided Maintenance:
1. On the left side of the SPOCC homepage, click Support.
2. On the Service Processor - Support page, under InServ, click Guided
Maintenance in the Action column.
9 –10
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Customer Self Repair
HP products are designed with many Customer Self Repair (CSR) parts to
minimize repair time and allow for greater flexibility in performing defective parts
replacement. If during the diagnosis period HP (or HP service providers or service
partners) identifies that the repair can be accomplished by the use of a CSR part,
HP will ship that part directly to you for replacement.
NOTE: Some HP parts are not designed for customer self repair. In order to satisfy
the customer warranty, HP requires that an authorized service provider replace the
part.
Additional help can be found using customer self-repair videos, available on the
HP Service Media Library at http://www.hp.com/go/sml
The Guided Maintenance page will be displayed. From the Guided Maintenance
page, select the node component that requires service.
Rev. 14.1
9 –11
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Repair and Replace System Components

Disk Drive Repair

Controller Node Repair

SFP Repair

Replacing an I/O Module

Replacing a Power Cooling Module

Controller Node Internal Component Repair

Node Drive

Clock Battery

DIMM

PCIe Adapter
Use the HP 3PAR StoreServ 7000 Storage Service Guide: Service Edition for
details.
9 –12
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Disk Drive Repair
Disk Drive Repair
Open the HP 3PAR Management Console, then do the following.
1.
Select the disk under Physical Disks that displays as Failed to open the
Physical Disks tab.
2.
Verify that State is listed as Failed and the Free Capacity and Allocated
Capacity columns display as zeroes.
3.
The Alert tab will display a filtered Alert table showing only the critical alerts
associated with the disk drive. Select the Alert tab, take note of the Message
Code and click the link for alert actions under Recommended Actions, then
follow the prompts on the Guided Troubleshooting website: select your
product then select the HP 3PAR Alert Message.
4.
On the storage system, identify the disk drive and verify that the disk status
LED is lit amber.
5.
Replace the disk drive and wait 5-10 minutes.
6.
Verify that the disk drive was successfully replaced. The new drive displays in
the same position as the failed drive and the State is listed as Normal
(indicated by a green icon).
NOTE: The failed drive will continue to display as Failed until the disk rebuild is
complete. This may take several hours.
Rev. 14.1
9 –13
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Replacing a Disk Drive
CAUTION:

If you require more than 30 minutes to replace a disk drive, install a blank disk
drive to prevent overheating while you are working.

To avoid damage to hardware and the loss of data, never remove a disk drive
without confirming that the disk status LED is lit.
Before you begin, use either option to verify that the disk drive is ready to be
replaced:
1.
Access SPmaint and issue the servicemag status command to verify the disk
status. When Succeeded displays as the last line in the output, it is safe to
replace the disk.
cli% servicemag status
Cage 0, magazine 3:
The magazine was successfully brought offline by a
servicemag start command.
The command completed Sat Jun 16 13:18:20 2012.
servicemag start -pdid 7 – Succeeded
2.
Verify that the disk status LED is amber and the disk is failed. While replacing
a disk drive, the disk status LED will turn and remain green until it is serviced.
3.
Replace the disk drive and wait 5-10 minutes.
4.
Issue the servicemag status command. When No servicemag operations
logged displays as the last line in the output, the disk as been successfully
replaced.
cli% servicemag status
No servicemag operations logged
9 –14
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Controller Node Repair
Controller Node Repair
Open the HP 3PAR Management Console and then do the following:
1.
On the Summary tab, click the node link to open the node's tab. Note the
number of nodes listed next to the link.
2.
The Alert tab will display a filtered Alert table showing only the critical alerts
associated with the node. Select the Alert tab, take note of the Message Code
and click the link for alert actions under Recommended Actions, then follow
the prompts on the Guided Troubleshooting website: select your product, then
select the HP 3PAR Alert Message.
3.
On the storage system, identify the node and verify that the status LED is lit
amber.
4.
Shutdown the node to be replaced, if required:
A. Log into SPOCC and access Guided Maintenance. In the Guided
Maintenance window, click Controller Node.
B. In the Node Rescue Task Information section, select the node to shut
down from the Node ID field, and then click Shutdown Node.
C. In the Node Status Information section, click Refresh to confirm the node
has been shut down and the node is no longer in the cluster.
Rev. 14.1
5.
Replace the node.
6.
Verify that the node was successfully replaced and the original number of
nodes display. The new node's State is listed as Normal (indicated by a green
icon).
9 –15
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Before you begin, use either SPmaint or the HP 3PAR Management Console
to identify the failed node:
1.
In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an
InServ.
2.
Issue the shownode command to see if the node is listed as Degraded or
missing from the output.
NOTE:
If the node's state is degraded, it will need to be shutdown to be serviced. If
the node is missing from the output, it may already be shutdown and is ready
to be serviced.
9 –16
3.
Type exit to return to the 3PAR Service Processor Menu.
4.
Select option 4 InServ Product Maintenance, then select the desired system.
5.
Select option 6 Halt an InServ cluster/node, then select the desired system.
Select the desired node and confirm all prompts to halt the node.
6.
Replace the node.
7.
In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an
InServ.
8.
Issue the shownode command to verify that the node has been successfully
replaced and the node’s state display as OK.
9.
Issue checkhealth -svc -detail to verify the system is healthy.
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
SFP Repair
SFP Repair
Before you begin, use either the HP 3PAR Management Console or SPmaint to
identify the failed SFP:
Open the HP 3PAR Management Console and do the following:
Rev. 14.1
1.
On the Summary tab, click the Port link to open the port's tab.
2.
Verify that State is listed as Loss Sync, the Mode is listed as Initiator and the
Connected Device Type is listed as Free.
3.
Replace the SFP.
4.
Verify that the SFP was successfully replaced. The replaced port State is
listed as Ready and the Mode is listed as Target and the Connected Device
Type is listed as Host.
9 –17
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
To perform maintenance using CLI, access SPmaint:
1.
In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an
InServ.
2.
Issue the showport commands to view the port state.
3.
Issue the showport –sfp to verify which SFP requires replacement.
cli%showport -sfp
N:S:P -State- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM
0:1:1 OK
HP-F
8.5
No
No
No
Yes
0:1:2 OK
HP-F
8.5
No
No
No
Yes
0:2:1 OK
AVAGO
10.3
No
No
Yes
Yes
0:2:2 OK
AVAGO
10.3
No
No
Yes
Yes
1:1:1 OK
HP-F
8.5
No
No
No
Yes
1:1:2 -
-
-
-
-
-
-
1:2:1 OK
HP-F
8.5
No
No
Yes
Yes
1:2:2 OK
HP-F
8.5
No
No
Yes
Yes
1:2:3 OK
HP-F
8.5
No
No
Yes
Yes
1:2:4 OK
HP-F
8.5
No
No
Yes
Yes
9 –18
4.
Replace the SFP.
5.
Issue the showport and showport –sfp to verify that the port is in good
condition and the State is listed as ready.
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Replacing an I/O Module
Removing an I/O Module
CAUTION:
Do not remove an I/O module unless it can be immediately replaced. Storage
systems operate using two I/O modules per enclosure and can temporarily operate
using one I/O module when removing the other I/O module for servicing.
Rev. 14.1
9 –19
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Before you begin, verify the location of the I/O module in an enclosure:
1.
Access SPmaint and issue the showcage command. A “-----“ indicates the
location of the module in the enclosure. Refer to the Name field in the output,
then issue the locatecage cagex command (where x is the name of the cagex
in the Name field).
cli% showcage
Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side
0 cage0 1:0:1 0 0:0:1 0 7 25-34 3202 3202 DCN1 n/a
1 cage1 1:0:1 0 0:0:1 1 0 0-0 3202 3202 DCS1 n/a
2 cage2 1:0:1 3 0:0:1 2 2 33-34 3202 3202 DCS2 n/a
3 cage3 1:0:1 2 ------- 3 2 33-33 3202 3202 DCS2 n/a
4 cage4 1:0:1 1 0:0:1 0 2 34-34 3202 3202 DCS2 n/a
6 cage6 1:0:2 2 0:0:2 1 6 33-35 3202 3202 DCS1 n/a
7 cage7 1:0:2 1 0:0:2 2 6 34-34 3202 3202 DCS1 n/a
8 cage8 1:0:2 0 0:0:2 0 6 35-36 3202 3202 DCS1 n/a
9 cage9 1:0:2 3 0:0:2 0 8 34-48 220c 220c DCS1 n/a
9 –20
2.
Identify the enclosure location where the I/O module resides by verifying the
LED number on the front of the enclosure.
3.
Remove and replace the I/O module
4.
Issue the showcage command to verify that the I/O module has been
successfully replaced and the ----- is replaced with output.
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Replacing a Power Cooling Module
Replacing a PCM
To perform maintenance using CLI, access SPmaint:
Rev. 14.1
1.
In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an
InServ.
2.
Issue the shownode –ps command to identify the failing PCM.
3.
Replace the PCM.
4.
In t he CLI, issue the shownode -ps command to verify that the PCM has
been successfully replaced.
9 –21
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Replacing a Battery inside a Power Cooling
Module
Replacing a Battery inside a Power Cooling Module
Before you begin, verify that at least one PCM battery in each node enclosure is
functional and identify which battery needs to be replaced.
To perform maintenance using CLI, access SPmaint:
1.
In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an
InServ and issue the following commands:

showbattery to verify the battery is failed:

checkhealth –svc –detail node:
NOTE: Because each battery is a backup for both nodes, node 0 and 1 will both
report a problem with a single battery. The Qty will appear as 2 in output because
two nodes are reporting the problem. Battery 0 for node 0 is in the left PCM, and
battery 0 for node 1 is in the right side PCM (when looking at the node enclosure
from the rear).
2.
Remove the PCM
3.
Remove the replacement PCM battery pack from its packaging
4.
Reinstall the PCM
5.
In the CLI, issue the following commands:
A. showbattery to confirm the battery is function and the serial ID has
changed:
B. checkhealth –svc –detail node to verify State as OK
9 –22
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Controller Node Internal Component Repair
Controller Node internal component repair
The following node internal component procedures are very complicated and may
result in loss of data. These procedures, including node repair, can be performed
using instructions in Guided Maintenance via SPOCC.
NOTE: Before beginning any internal node component procedure, the node must
be removed from the system and the node cover is removed.
Replacing a Node Drive
CAUTION: Verify that you are not installing the node disk upside down. You must
reinstall the node disk the same side up as it was removed.
NOTE: There are four plastic guide pins that hold the node disk in place. To
correctly seat the node disk, push the node disk down on the guide pins.
After you replace a node drive, node rescue must be performed.
Replacing a Clock Battery
NOTE: The clock inside the controller node uses a 3-V lithium coin battery. The
lithium coin battery may explode if it is incorrectly installed in the controller node.
Replace the clock battery only with a battery supplied by HP. Do not use non-HP
supplied batteries. Dispose of used batteries according to the manufacturer’s
instructions.
In the CLI, issue the showdate command to confirm the clock setting is correct.
Rev. 14.1
9 –23
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Replacing a DIMM
Controller nodes contain two types of DIMMs, control cache and data cache.
To perform maintenance using CLI, access SPmaint:
1.
Issue the shownode –mem and shownode –Ii commands to identify if the
DIMM is cache or data and the manufacturer and part number.
2.
Physically identify the failed DIMM in the node. The Control Cache (CC) and
Data Cache (DC) DIMMs can be identified by locating white silk-screen word,
DIMM, on the board.
3.
Replace the DIMM.
4.
In the CLI, issue the shownode -i command to verify the memory is
operational.
Replacing a PCIe Adapter Assembly
This procedure is shown on the inside label of the controller node cover, where it is
described in more detail. Use the label to assist in replacing the following
components.
1.
In the CLI, issue the shownode –pci command to verify the replacement
card manufacturer and model are the same as what is currently installed.
2.
Replace the PCIe card.
NOTE: If replacing a CNA card, you have to configure the new card after installing
it. Issue the showport command to identify the ports on the new card, then enter
controlport config iscsi <N:S:P> to configure the card.
9 –24
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Console mode access
The maintenance menu for service providers was added to the storage system
node serial-console port to perform many standard operations that previously
required root access.
Operations which are of interest for installation and basic troubleshooting are:
1. Out Of The Box Procedure will initialize an HP 3PAR storage system by
performing the following: creating the necessary system volumes, initializing disks,
upgrading cage and disk firmware if needed, creating spare chunklets, and setting
the system name and network information.
2. Re-enter network configuration is similar to the network setting portion of the
OOTB procedure.
5. Perform a Node-to-Node rescue is used to rebuild the boot disk on a node
from a working node on the same storage system.
6. Set up the system to wipe and rerun ootb should only be used when you are
preparing a storage system to have all data destroyed (wiped).
8. Perform a deinstallation is used to prepare the storage system for
deinstallation and the optional re-initialization of all chunklets on all drives (erasing
all customer data). This is similar to option 7 (wiping the system), but you will also
be asked if you want to re-initialize all chunklets. If you answer no, it will wipe all
meta-information from the storage system (such as VV and host information), but
the underlying customer data will remain on the chunklets; a response of “yes” will
also write zeroes to the chunklet regions of all disks (such as Data-SecurityErase), destroying all customer data.
Note: Initializing all chunklets may take several hours to complete.
Rev. 14.1
9 –25
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Node Rescue

Rebuild of the node boot disk
When replacing a node disk, or the existing node disk has
corrupt data, reimages the disk at the correct version,
including patches

Auto Node to Node Rescue

Service Processor (Physical) Node Rescue
Node Rescue
After the node disk drive has been replaced and the controller node is powered on,
node rescue can be performed.
Auto Node to Node Rescue
Auto node-to-node rescue is started automatically when a node is removed, then
replaced, in a storage system, and when there is at least one node in the cluster,
perform an auto node-to-node rescue. Always perform the automatic node rescue
procedures unless otherwise instructed.
NOTE: Make sure that the management ports (Mgmt) of all nodes are connected
to the same LAN!
To monitor rescue operation use the showtask -d command to view detailed
status information.
Service Processor (Physical) Node Rescue
The SP node rescue should only be used in cases when the storage system
includes a physical SP and no nodes are remaining in the cluster or when all
nodes are down.
By using this rescue method, the storage node gets directed to initiate a network
boot instead of booting from the built-in disk.
NOTE: For SP node rescue, you can specify whether to use the public Ethernet
port (eth0) or the private Ethernet port and a crossover cable (eth1).
9 –26
Rev. 14.1
HP 3PAR StoreServ 7000 Storage Troubleshooting
Lab 6, Lab 7, Lab8, Lab 9, Lab 10, Lab 11
Lab 6: HP 3PAR Service Processor Onsite Customer Care
(SPOCC) usage
Lab 7: Node Rescue
Lab 8: Manage Events and Alerts
Lab 9: De-installation of a 3PAR array
Lab 10: Installing the StoreServ 7000 without SmartStart
Lab 11: Configure the Storage System
Rev. 14.1
9 –27
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Learning check
1. What should be the preferred method to replace failed components?
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
2. What is imported to check before replacing a failed node?
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
9 –28
Rev. 14.1
HP 3PAR StoreServ File Controller
Module 10
Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the functionality of the HP 3PAR StoreServ File Controller

Understand how the HP 3PAR storage system get managed in this
environment
10 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP 3PAR StoreServ File
This solution (two node HP StoreEasy 3830 Gateway Storage cluster with HP
3PAR StoreServ Storage) delivers a tightly integrated, converged solution that
allows to easily provision file shares and block volumes from a single user
interface via native SMI - S capability on HP 3PAR Store Serv Storage.
HP 3PAR StoreServ File Services provide integrated capabilities not found on
unified storage, enabling you to deploy cost effective solutions with advanced file serving capabilities, and maximize efficiency, security, and high availability.
This solution enables you to meet the unpredictability of changing workloads in
today’s storage environments - Today, you’re running VMware over fibre channel,
tomorrow you want to run Hyper-V over SMB3? - dynamically reprovision storage
on the same platform as your business evolves.
The difference compared to other solutions is in the underlying storage platform –
3PAR StoreServ.
Unlike other platforms, 3PAR’s federated, scale-out architecture is not burdened
with legacy of designs created decades ago. This is why we are able to offer
guarantees to double the VM density and save 50% capacity. It is why we are able
to deliver the All Flash 3PAR 7450 Array we’ve just announced.
The setup consists of a two node HP StoreEasy 3830 Gateway Storage cluster
with HP 3PAR StoreServ Storage.
10 –2
Rev. 14.1
HP 3PAR StoreServ File Controller
3PAR StoreServ file controllers
Rev. 14.1

With the 3PAR StoreServ File Controller you can provision file shares and
volumes on 3PAR from a single management interface.

It automatically identifies thinly provisioned volumes and can alert the
administrator when thresholds are reached. When a user deletes a file on a
share, storage on the underlying 3Par volume is also automatically released
for thin persistence. This also means that the granular block-level dedup
which saves capacity on the file system, also saves capacity on the 3PAR
LUN.

When a user copies files between shares, the copy operation is offloaded to
the 3Par array which is orders of magnitude faster and saves network
bandwidth. This is especially useful for copying large files such as database
log files and videos.

Coupled with CLX for 3PAR, failovers are automatic and transparent across
sites.

Runs Windows Storage Server 2012 OS so it offers the best experience for
windows clients, but is also very capable of serving files to Linux/Unix users.
10 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Array Integration
10 –4

3PAR runs SMI-S natively on the controller.

Easy Provisioning of file shares for heterogeneous clients, such as Linux,
UNIX and Windows Clients or even for Applications such as SQL Server,
Hyper-V or VMWare.

Supports a variety of protocols out of the box, including iSCSI, CIFS/ SMB 1,
SMB 2.x, SMB 3.0, NFSv3, NFSv4.1, FTP(s), HTTP(s) and WebDAV.

Allocate less data and reclaim storage automatically with Thin Provisioning
integration that provides standardized notifications when storage thresholds
are reached, and releases storage automatically when it is no longer needed.

Offloaded Data Transfer (ODX) enables protocol agnostic, storage arrayassisted data transfer (conceptually similar to VMware VAAI) which is orders
of magnitude faster, and practically eliminates load on the file server and
saves network bandwidth. It can be used for VM Migration, general bulk data
movement (such as Large Database Files, HD Video, etc.)
Rev. 14.1
HP 3PAR StoreServ File Controller
Manage storage efficiently
The 3PAR file controller is able to provision file shares and volumes on 3Par via
SMI-S which runs natively on the 3PAR Controller – all from a single management
interface.
Rev. 14.1
10 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Efficient deduplication
Scale and performance.
Deduplication can run on multiple volumes simultaneously without affecting other
workloads on the server (Deduplication scope is a Volume). Low impact on the
server workloads is maintained by throttling the CPU and memory resources that
are consumed. If the server gets very busy, deduplication can stop completely. In
addition, administrators have the flexibility to run data deduplication jobs at any
time, set schedules for when data deduplication should run, and establish file
selection policies.
Reliability and data integrity.
When data deduplication is applied, the integrity of the data is maintained.
Windows Server 2012 uses checksum, consistency, and identity validation to
ensure data integrity. For all metadata and the most frequently referenced data,
data deduplication maintains redundancy to ensure that the data is recoverable in
the event of data corruption.
Bandwidth efficiency with BranchCache.
Through integration with BranchCache, the same optimization techniques are
applied to data transferred over the WAN to a branch office. The result is faster file
download times and reduced bandwidth consumption.
http://technet.microsoft.com/en-us/library/hh831602.aspx
10 –6
Rev. 14.1
HP 3PAR StoreServ File Controller
Secure your files
3PAR File Controllers are a secure platform with built in encryption for data “in
flight” and for data at rest. Files are encrypted when they reside on the NAS, and
encrypted while they are being served out to clients over SMB 3.0.
You can run practically any antivirus software directly on the file controllers
themselves, and the most interesting security feature, is the ability to protect
business critical files via centrally managed policies.
Rev. 14.1
10 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Your files are continuously available
Failovers are transparent for SMB3 and NFS clients, which mean you have zero
downtime for both planned and unplanned failovers. The clients just see a short IO
pause during failover but are able to continue operations where they left off.
3PAR file controllers support online patching of the OS. They use Cluster Aware
Updating which scans nodes to find out which updates are needed. It identifies the
node with the fewest workload and fails it over, then updates it, fails back and
moves to the next node in the cluster.
Because failovers are transparent, the file serving to the clients continues during
upgrades.
Also because this is an automated process, you can be sure that every node in the
cluster (and you can have up to 64 nodes) are at the same patch level. This is
especially important if applications use the NAS, as the same software level
ensures they will run equally well on any node.
The File System is very resilient. CHKDSK, which previously could take hours,
now just takes seconds. You can deploy large multi-terabyte volumes with
confidence.
10 –8

With the improved CHKDSK, downtime proportional only to the number of
logged corruptions that cannot be fixed with the online repair (Self-healing)
capability.

Zero offline time to fix corruption on Cluster Shared Volumes (CSV)
Rev. 14.1
HP 3PAR StoreServ File Controller
Automated disaster recovery
3PAR file services with HP Cluster Extension (CLX) for 3PA enables continued
operation in the event of a data center disaster.
Rev. 14.1

CLX is host-based software that integrates seamlessly with 3PAR replication
and windows clustering, providing rapid automatic failover/failback and
enhances overall solution availability with failovers in seconds to minutes
compared to hours.

CLX enables Live Migration of Hyper-V VMs on Cluster Shared Volumes
between sites
10 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Reduce the impact of maintenance
Customers want to ensure that the services they invest in are always available to
their customers and information workers. Downtime that causes most problems:
planned outages, unplanned outages, and service/application availability.
For the most common planned outages, HP implemented a new feature called
“Cluster-Aware Updating” or CAU. This helps automate cluster update activities
and perform them in a way that eliminates downtime associated with cluster
update tasks while making it much easier for administrators to deploy updates to
clusters.
Part of being able to perform cluster updates without service interruption depends
on new transparent failover capabilities, which keep the storage that applications
depend upon up and available even through node outages.
10 –10
Rev. 14.1
HP 3PAR StoreServ File Controller
Learning check
1. List the components of the HP 3PAR StoreServ File Controller!
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
2. Which interface is used to provide storage array management capabilities to the
3PAR StoreServ File Controller management software?
____________________________________________________________________
____________________________________________________________________
Rev. 14.1
10 –11
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
10 –12
Rev. 14.1
HP StoreFront Mobile Access for 3PAR
StoreServ
Module 11
Objectives
After completing this module you should be able to:
Rev. 14.1

Describe the “HP StoreFront Mobile Access for 3PAR StoreServ”

Identify the component required to remotely manage the HP 3PAR system
11 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP StoreFront Mobile Access for 3PAR
StoreServ
Converged Storage Management

Access: 24x7 access from virtually any location
Remote access to 3PAR StoreServ using Android and now
also iOS based devices

Insight: Monitor Storage system statistics and properties
Capacity utilization, CPGs, Virtual volumes, Device types and
more

Automation: Receive critical alerts real time to reduce risk
Instant notification of error conditions or issues that need
immediate action

Security: Encrypted login for secure remote access
Browse-only enforcement access integrated with 3PAR rolebased security
Two components:

A handheld device app (runs on the Smartphone) downloadable from the
Android App store ; iOS devices

A back-end application (linked to the device management software)
downloadable from HP Software Depot
Access: This solution enables storage administrators to gain real-time, remote
access to HP storage arrays, at any time and from anywhere. Using a smartphone,
you can monitor your key performance metrics and system statistics like IOPS,
throughput, and more.
Insight: Monitor storage performance and meet service-level agreements (SLAs).
Automation: With HP StoreFront Mobile Access, you get an instant alert or
notification on your smartphone if an error happens. You can therefore act on
information faster than ever before. Share the details with a colleague. You can
also take the necessary corrective action and resolve problems quickly. Receive
alerts and notifications of error conditions
Security: One of the characteristics of a mobile workforce is that they’re often
logging in from a remote location. By its nature, remote login is fraught with
security risks. A solution for monitoring and managing storage in these situations
must be as secure as possible. The HP StoreFront Mobile Access is just that. It
provides a no-risk, encrypted login with browse-only enforcement access. This
means the entire communication is encrypted for your protection. It’s integrated
with current HP 3PAR StoreServ role-based security, and offers a simple, intuitive
user interface that’s consistent with HP 3PAR Management Console.
11 –2
Rev. 14.1
HP StoreFront Mobile Access for 3PAR StoreServ
HP StoreFront Mobile Access includes server software, an Android app and an
iOS app. The server software and apps work together to provide secure access for
monitoring HP 3PAR StoreServ storage from mobile devices.
Mobile phones can connect to HP StoreFront Mobile Access servers by Wi-Fi and
cellular networks.
Rev. 14.1
11 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Learning check
1. List the components (hw/sw) of the HP StoreFront Mobile Access for 3PAR
SoreServ?
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
2. HP StoreFront Mobile Access for 3PAR StoreServ can be used to create and export
virtual volumes. True or False? Answer: _______________
11 –4
Rev. 14.1