Documente Academic
Documente Profesional
Documente Cultură
Learner Guide
HP ServiceOne
Rev. 14.31
Course : 00722456
HP 3PAR StoreServ 7000
Installation, Startup and
Break Fix
Learner Guide
HP ServiceOne
Rev. 14.31
Course : 00722456
Copyright 2014 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
April 2014
Contents
Course Introduction
Course Objectives ................................................................................................. 1
Agenda .................................................................................................................. 2
Day 1: ............................................................................................................. 2
Day 2: ............................................................................................................. 4
Day 3: ............................................................................................................. 5
ii Rev. 14.31
Contents
iv Rev. 14.31
Contents
Rev. 14.31 v
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
vi Rev. 14.31
HP 3PAR StoreServ 7000 Installation,
Startup, and Break Fix
Introduction
Course Objectives
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:
• Microsoft Windows system management knowledge
• Knowledge of storage technologies - SCSI, Fibre Channel, SAN
switches and SAN networking.
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
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
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
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 passwords
HP 3PAR Remote Support overview
STaTS usage
Alerts and Events
HP 3PAR StoreServ 7000 system Troubleshooting
Powering Off/On the Storage System
Troubleshooting Methods
Guided Maintenance
Repair and Replace System Components
Node rescue
Module Objectives
Rev. 14.31 1 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
1 –2 Rev. 14.31
HP 3PAR StoreServ Product Family Overview
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
or Hyper-V system, provided by the customer, meeting the following specifications.
VMware ESXi 4.x, ESXi 5.1, ESXi 5.5 or Hyper-V Server 2008 R2 and Hyper-
V Server 2012
Service Processor server features:
2 GB RAM (minimum for the VSP Virtual Machine)
256 GB free disk space (minimum for the VSP Virtual Machine)
NOTE: VSP storage must not reside on the array it is managing.
DVD ROM or DVD RW
1 Gb Ethernet port
For VSP on VMware, the server must be listed in the VMware Compatibility
Guide
For VSP on Hyper-V, the server must be listed on the Windows Server
Catalog
The customer also has the option to choose a physical Service Processor.
Rev. 14.31 1 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
1 –4 Rev. 14.31
HP 3PAR StoreServ Product Family Overview
Rev. 14.31 1 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
1 –6 Rev. 14.31
HP 3PAR StoreServ Product Family Overview
HP 3PAR ASIC
Hardware-based for performance
1 –8 Rev. 14.31
HP 3PAR StoreServ Product Family Overview
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 write-
caching through rapidly re-mirroring cache to the other nodes in the cluster in the
event of a cache or controller node failure.
Rev. 14.31 1 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Learning check
1. What are the features of the HP 3PAR ASIC?
_________________________________________________
_________________________________________________
_________________________________________________
_________________________________________________
_________________________________________________
2. Which StoreServ system cannot be configured using HDD (Hard disk drive)?
_________________________________________________
Objectives
Rev. 14.31 2 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Max SSDs:
7200 = 120 SSDs
7400/7450 (2/4 nodes) = 120/240 SSDs
Max LFF drives:
7200 = 216 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 3.1.3: 400TB (3.1.2 MU2 was 250TB)
7400 3.1.3: 1.1PB (3.1.2 MU2 was 864TB)
7450 3.1.3: 220TB (3.2.2 MU2 was 96TB)
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.31
HP 3PAR StoreServ 7000 Hardware Components
Rev. 14.31 2 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
2 –4 Rev. 14.31
HP 3PAR StoreServ 7000 Hardware Components
For more Information about System LEDs, refer to the “HP 3PAR StoreServ 7000
Storage Service Guide.”
Rev. 14.31 2 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
2 –6 Rev. 14.31
HP 3PAR StoreServ 7000 Hardware Components
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.
For more Information about System LEDs, refer to the “HP 3PAR StoreServ 7000
Storage Service Guide.”
Rev. 14.31 2 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
2 –8 Rev. 14.31
HP 3PAR StoreServ 7000 Hardware Components
Rev. 14.31 2 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
It looks similar to the 764W PCM (used in the controller enclosure) but it is
different, because the 580W has no Cache Battery.
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.
The chart provides a quick summary of the drive specifications at the time of
writing.
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 MLC, irrespective of 7000, 7450 or 10000 platform) will
be 3 or 5 years. No max write dependency, for example, if max writes are reached
within warranty period, HP will replace the drive.
With Extended Maintenance contract (beyond the 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.
Adaptive Sparing technology is implemented with new 480 GB and 920 GB SSDs
to enhance their endurance (available on HP 3PAR StoreServ 7000 systems)
With Adaptive Sparing, 3PAR storage system is able to release the spare
chunklets present in each SSD media to the SSD itself, allowing SSDs to use that
spare capacity as additional over-provisioned capacity. This increase in over-
provisioned capacity enhances endurance of SSDs within a 3PAR array.
SSD Spare Chunklets space is returned to the SSD Overprovisioning pool so it
can be used for wear leveling. This space will be claimed back when spares are
needed.
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).
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).
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.
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.
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.
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.
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.
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.
Learning check
1. List the HP 3PAR Storage System hardware building blocks!
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
4. Can you mix different types of disk enclosure (SFF, LFF) on a single SAS-
Port?
________________________________________________
5. How many drive enclosure, populated with similar disk, are required to for HA
Enclosure for RAID6 (4+2)?
________________________________________________
Objectives
After completing this module you should be able to:
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
Rev. 14.31 3 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
3 –2 Rev. 14.31
HP 3PAR StoreServ7000 Software
Rev. 14.31 3 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
3 –4 Rev. 14.31
HP 3PAR StoreServ7000 Software
Rev. 14.31 3 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
3 –6 Rev. 14.31
HP 3PAR StoreServ7000 Software
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
Rev. 14.31 3 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.31
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?
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
Rev. 14.31 3 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Objectives
After completing this module you should be able to:
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
Rev. 14.31 4 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
4 –2 Rev. 14.31
HP 3PAR StoreServ 7000 Installation and Setup
Rev. 14.31 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.
At least two people are needed to safely unload the rack
from the pallet.
4 –4 Rev. 14.31
HP 3PAR StoreServ 7000 Installation and Setup
Rev. 14.31 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.31
HP 3PAR StoreServ 7000 Installation and Setup
Rev. 14.31 4 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
4 –8 Rev. 14.31
HP 3PAR StoreServ 7000 Installation and Setup
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:
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.
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
Learning check
1. What is the preferred method the setup the service processor and storage
system?
___________________________________________________________
___________________________________________________________
___________________________________________________________
___________________________________________________________
4. Without DHCP, how does the IP address can be set after Virtual Service
Processor deployment?
___________________________________________________________
___________________________________________________________
___________________________________________________________
___________________________________________________________
Objectives
After completing this module you should be able to:
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
Rev. 14.31 5 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
5 –2 Rev. 14.31
HP 3PAR StoreServ Architecture and Concepts
Rev. 14.31 5 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
5 –4 Rev. 14.31
HP 3PAR StoreServ Architecture and Concepts
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.31 5 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
5 –6 Rev. 14.31
HP 3PAR StoreServ Architecture and Concepts
Rev. 14.31 5 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
5 –8 Rev. 14.31
HP 3PAR StoreServ Architecture and Concepts
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.31 5 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
Persistent Ports support is extended to iSCSI and FCoE array target connectivity.
FCoE uses same underlying NPIV technology as FC.
iSCSI uses i/p failover.(i.e. transfer IP address from one port to another and
broadcast gratuitous ARP.)
Same failover sequence and user experience as FC ports. (i.e. offline port
then transfer identity to partner)
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
Priority Optimization
to assign performance
threshold to a Virtual
Domain
Data logically
separate and secure
Eliminate
unauthorized or
accidental access to
data
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.
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.
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.
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.
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.
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.
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.
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.
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
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
Objectives
Rev. 14.31 6 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
6 –2 Rev. 14.31
HP 3PAR StoreServ System Management
Rev. 14.31 6 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Create CPG(s)
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.31
HP 3PAR StoreServ System Management
Rev. 14.31 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.31
HP 3PAR StoreServ System Management
Rev. 14.31 6 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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 Volume-
LUN pairing (VLUN).
6 –8 Rev. 14.31
HP 3PAR StoreServ System Management
Rev. 14.31 6 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Learning check
1. What is the function of the HP 3PAR Host Explorer?
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
Objectives
Rev. 14.31 7 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
7 –2 Rev. 14.31
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,
Rev. 14.31 7 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
7 –4 Rev. 14.31
Upgrade of Hardware and Software Components
Rev. 14.31 7 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
7 –6 Rev. 14.31
Upgrade of Hardware and Software Components
Rev. 14.31 7 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
However, it is important to note that this new End-to-End process will NOT enable
the 3PAR systems to be considered CSU. That capability will come later and the
development teams are actively working on those enhancements to get to CSU on
the 3PAR systems.
Patches or updates deployed automatically will not be installed – only staged.
Customers will be alerted of newly staged updates/patches through Management
Console and when logging into SPOCC GUI
Auto-deployment configuration setting available on SP and in the STaTS UI
(internal HP only).
What’s new is that the 3PAR OS updates will be staged directly onto the
customer’s 3PAR StoreServ, when running OS 3.1.3 and above.
The updates will not be installed, only staged on the array to support the automatic
drive update beginning with 3.1.3.
So when a new drives are added with the admithw command, the new drives can
be used because the update will already be on the StoreServ.
OS updates will continue to be staged on the SP as well for all-node-down node
recovery. If the nodes are down, customers will be able to recover from the OS on
the SP.
Updates can still be loaded and staged from DVD or ISO files, using SPOCC or
SPMaint as done today.
Updates can be revoked if not already installed. So in case something is pushed
out accidentally, there is a backup plan to revoke an update.
Drive table updates will be automatically installed as needed to support new drives
when a ‘admithw’ is performed.
Rev. 14.31 7 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
SPOCC GUI
Notification of ‘New Updates Available’
New update wizards for both SP update and HP 3PAR OS updates.
Many improvements based on usability testing feedback
The GUI shows both the current version of software that is installed, and it also
shows that there are new sw versions that have been staged and available for
installation.
The hyperlink for the new updates, will take you to the SW Update Wizard to
perform that update.
The second link will bring up a new window for the release notes that are
associated with that specific SW update.
On the Update Status page the progress of the update is shown.
Summary
The drive firmware will be staged by the SP on the
StoreServ as it becomes available.
Initiating an admithw will invoke code to examine the
staging folder for any drive table updates and will load
them “automatically”
The process can be bypassed by including a –nopatch
option on the admithw command.
Learning check
1. How can you merge two two-Node 7400 systems to one four-Node system?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
4. Which command should be use to verifying the Health of the Storage System
before and after the update?
_____________________________________________________________
_____________________________________________________________
Objectives
Rev. 14.31 8 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
8 –2 Rev. 14.31
Maintenance Tools and Resources
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.
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.
Rev. 14.31 8 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
8 –4 Rev. 14.31
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.31 8 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
HP proactive resources
8 –6 Rev. 14.31
Maintenance Tools and Resources
Rev. 14.31 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:
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.
8 –8 Rev. 14.31
Maintenance Tools and Resources
The table shows a description of each filter found on the STaTs Display tab.
Rev. 14.31 8 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
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.
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.
STaTS Data Overview is a collection of files for troubleshooting the 3PAR storage
array or monitoring devices, including:
Insplore (3PAR array troubleshooting files)
Splor (SP troubleshooting files)
Cpsplor (Custodian troubleshooting files)
Application panics
Node Software panics
Firmware Cores
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.
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.
Best Practices
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.
Both management interfaces (SPOCC and SPMAINT) can be used to enable and
disable Service Processor Maintenance Mode
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.
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:
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.
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
___________________________________________________________________
___________________________________________________________________
Objectives
Rev. 14.31 9 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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:
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
9 –2 Rev. 14.31
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.31 9 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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:
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.
9 –4 Rev. 14.31
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.
"The SP does not have an HP 3PAR OS version installed. Use SPOCC to
install an HP 3PAR OS package."
Rev. 14.31 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.31
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.31 9 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
9 –8 Rev. 14.31
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:
SPSETLOG.log Service Processor setup log
ARSETLOG.system_serial_number.log Storage System setup log
errorLog.log General errors
5. 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.31 9 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
The Guided Maintenance page will be displayed. From the Guided Maintenance
page, select the node component that requires service.
Use the HP 3PAR StoreServ 7000 Storage Service Guide: Service Edition for
details.
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.
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.
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:
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.
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
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.
Replacing a PCM
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 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.
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.
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-Security-
Erase), destroying all customer data.
Note: Initializing all chunklets may take several hours to complete.
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).
Learning check
1. What should be the preferred method to replace failed components?
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
Objectives
Rev. 14.31 10 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.31
HP 3PAR StoreServ File Controller
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.
Rev. 14.31 10 –3
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Array Integration
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 array-
assisted 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.)
10 –4 Rev. 14.31
HP 3PAR StoreServ File Controller
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.31 10 –5
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
Efficient deduplication
10 –6 Rev. 14.31
HP 3PAR StoreServ File Controller
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.31 10 –7
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
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)
10 –8 Rev. 14.31
HP 3PAR StoreServ File Controller
3PAR file services with HP Cluster Extension (CLX) for 3PA enables continued
operation in the event of a data center disaster.
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
Rev. 14.31 10 –9
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.
Learning check
1. List the components of the HP 3PAR StoreServ File Controller!
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
Objectives
Rev. 14.31 11 –1
HP 3PAR StoreServ 7000 Installation, Startup, and Break Fix
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.31
HP StoreFront Mobile Access for 3PAR StoreServ
Rev. 14.31 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.31